04-28-2016 09:54 PM
306 1234 ...
tools
  1. dmmarck's Avatar
    Thanks for the guide!

    I am using this guide and trying to build for the nexus 7 (grouper) with the nexus 7 drivers instead of the tuna drivers listed in this post. When I get to the lunch command and make my selection, i get a bunch of permission denied errors. I re-did this section of the guide, but did a sudo su command first to see if that cured the issues and it appears that it has. Android is building at the moment, so we'll see if it works.

    Any ideas why i would have to be logged in as full root?
    That's a good question. On my first build (I've done two with two different source compiles), I also had permissions problems with the drivers. I manually changed the owner and the permissions in terminal to each and every file/folder and that seemed to solve it. "Sudo" itself did not and it really left me perplexed...

    ...yet, on the second compile after the second source was downloaded (I deleted everything from the first go 'round to essentially do it again), all was fine.

    Funky, eh?
    07-14-2012 05:19 PM
  2. nmyeti's Avatar
    yeah, that is strange. I've had file permission issues with Ubuntu building before. Sudo su seems to fix it, but it would be nice not to have to resort to a sledgehammer
    07-14-2012 05:36 PM
  3. dmmarck's Avatar
    yeah, that is strange. I've had file permission issues with Ubuntu building before. Sudo su seems to fix it, but it would be nice not to have to resort to a sledgehammer
    I agree; a lot of this process, for better for worse, takes some ingenuity. For example, on the second compile I ran into about ~6 fetch errors when syncing source. The first one, which was done minutes after JBQ gave the go ahead? None.
    07-14-2012 05:38 PM
  4. dmmarck's Avatar
    UPDATE:

    I updated the second post with git tag verification. Some guides have this, some don't, but I think it's a good step and I have decided to include it for those who want it.
    07-14-2012 06:00 PM
  5. cj100570's Avatar
    I'm running into an permission denied issue. Any ideas? I'm also not seeing an option for a toro build.


    cj@Chimera:~/WORKING_DIRECTORY$ lunch

    You're building on Linux

    Lunch menu... pick a combo:
    1. full-eng
    2. full_x86-eng
    3. vbox_x86-eng
    4. full_grouper-userdebug
    5. mini_armv7a_neon-userdebug
    6. mini_armv7a-userdebug
    7. full_wingray-userdebug
    8. full_crespo-userdebug
    9. full_maguro-userdebug
    10. full_panda-userdebug

    Which would you like? [full-eng] 9
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied

    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    ============================================
    PLATFORM_VERSION_CODENAME=REL
    PLATFORM_VERSION=4.1.1
    TARGET_PRODUCT=full_maguro
    TARGET_BUILD_VARIANT=userdebug
    TARGET_BUILD_TYPE=release
    TARGET_BUILD_APPS=
    TARGET_ARCH=arm
    TARGET_ARCH_VARIANT=armv7-a-neon
    HOST_ARCH=x86
    HOST_OS=linux
    HOST_OS_EXTRA=Linux-3.2.0-26-generic-x86_64-with-Ubuntu-12.04-precise
    HOST_BUILD_TYPE=release
    BUILD_ID=JRO03C
    OUT_DIR=out
    ============================================
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    07-14-2012 07:29 PM
  6. dmmarck's Avatar
    I'm running into an permission denied issue. Any ideas? I'm also not seeing an option for a toro build.


    cj@Chimera:~/WORKING_DIRECTORY$ lunch

    You're building on Linux

    Lunch menu... pick a combo:
    1. full-eng
    2. full_x86-eng
    3. vbox_x86-eng
    4. full_grouper-userdebug
    5. mini_armv7a_neon-userdebug
    6. mini_armv7a-userdebug
    7. full_wingray-userdebug
    8. full_crespo-userdebug
    9. full_maguro-userdebug
    10. full_panda-userdebug

    Which would you like? [full-eng] 9
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied

    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    find: `vendor': Permission denied
    ============================================
    PLATFORM_VERSION_CODENAME=REL
    PLATFORM_VERSION=4.1.1
    TARGET_PRODUCT=full_maguro
    TARGET_BUILD_VARIANT=userdebug
    TARGET_BUILD_TYPE=release
    TARGET_BUILD_APPS=
    TARGET_ARCH=arm
    TARGET_ARCH_VARIANT=armv7-a-neon
    HOST_ARCH=x86
    HOST_OS=linux
    HOST_OS_EXTRA=Linux-3.2.0-26-generic-x86_64-with-Ubuntu-12.04-precise
    HOST_BUILD_TYPE=release
    BUILD_ID=JRO03C
    OUT_DIR=out
    ============================================
    make: stat: vendor/samsung/tuna/BoardConfigVendor.mk: Permission denied
    make: stat: vendor/samsung/maguro/BoardConfigVendor.mk: Permission denied
    I had that happen on my first compile--try changing the permissions of the vendor folder or try using "sudo su."

    I solved it by using the long way--I changed ownership to everything by typing this in:

    $ sudo chown dmmarck
    (Use your username, not mine obviously lol)

    (Make sure to have a space after your username/before the file/folder!)

    And then after typing that, I dragged and dropped each folder/file on each level of the /vendor folder. Thankfully, that worked. I'm sure there's a way to do it quicker and more efficiently (it was very late at night, so sue me ), but that worked for me.

    EDIT: I'm a dummy, you can do this as well and it should work (my apologies )

    sudo chown -R dmmarck /vendorfolderhere
    You can also change permissions with chmod instead of chown.
    2defmouze likes this.
    07-14-2012 07:33 PM
  7. cj100570's Avatar
    I'll give that a try.
    07-14-2012 07:35 PM
  8. dmmarck's Avatar
    I'll give that a try.
    Should work. Also try a lowercase - r, was headed out the door when I replied. Keep me posted!

    Sent swiftly by Oliver using Android Central Forums
    07-14-2012 07:53 PM
  9. zero neck's Avatar
    great front page write up for the guide, d!
    07-14-2012 08:18 PM
  10. Andrew Ruffolo's Avatar
    [YT]http://www.youtube.com/watch?v=d-_G0RP9J1U[/YT]

    Here's my video how-to. Didn't go as in-depth as this tutorial (it rocks), but its at least a visual for those that may need something more like a class. I have other videos on my channel as well (shameless plug). Feel free to insert video wherever you like.
    07-14-2012 08:26 PM
  11. Incrediboy's Avatar
    Will this work on a VMware Ubuntu installation?
    07-14-2012 08:52 PM
  12. ttk1opc's Avatar
    Can the OTA package just be flashed over stock ICS and not lose any data like a regular OTA update?
    Incrediboy likes this.
    07-14-2012 08:59 PM
  13. Channan's Avatar


    Dafuq did I just read?

    I'd like to take this moment to thank all the people who do the hard work of building custom ROMs so I can just download a single file and select yes to install it.

    Thank you for making my life easier.
    zero neck likes this.
    07-14-2012 09:24 PM
  14. jackstraw's Avatar
    Probably the best guide Ive seen for anything, nice job!!
    zero neck and dmmarck like this.
    07-14-2012 09:35 PM
  15. Andrew Ruffolo's Avatar
    Click to view quoted image


    Dafuq did I just read?

    I'd like to take this moment to thank all the people who do the hard work of building custom ROMs so I can just download a single file and select yes to install it.

    Thank you for making my life easier. Click to view quoted image
    lol. this was an awesome post

    Sent from my Transformer TF101 using Android Central Forums
    Channan likes this.
    07-14-2012 09:35 PM
  16. zero neck's Avatar
    Can the OTA package just be flashed over stock ICS and not lose any data like a regular OTA update?
    what this method compiles isnt an ota, it's a rom from source. (d - correct me if i'm wrong this isnt my area of expertise at all).

    when the jb ota is available down the road, there will be a method in which you can update to jb from ics without wiping data, most likely ahead of the ota release itself or at least concurrent with it.
    07-14-2012 09:37 PM
  17. Andrew Ruffolo's Avatar
    Can the OTA package just be flashed over stock ICS and not lose any data like a regular OTA update?
    i wouldnt... you could try backing up and then wiping all 3 (data, cache, dalvik) and then install rom, then restore data from backup. this is very hit or miss with me, though... mostly miss.

    Sent from my Transformer TF101 using Android Central Forums
    07-14-2012 09:37 PM
  18. zero neck's Avatar
    Probably the best guide Ive seen for anything, nice job!!
    same jackstraw from rootz?
    07-14-2012 09:37 PM
  19. Andrew Ruffolo's Avatar
    Will this work on a VMware Ubuntu installation?


    It should. I'm going to do a video tonight in a vmware installation on installing java, I'll test a build afterwards.

    Sent from my Transformer TF101 using Android Central Forums
    07-14-2012 09:38 PM
  20. dmmarck's Avatar


    Here's my video how-to. Didn't go as in-depth as this tutorial (it rocks), but its at least a visual for those that may need something more like a class. I have other videos on my channel as well (shameless plug). Feel free to insert video wherever you like.
    Thank you! I'll be sure
    to check it out later.




    Will this work on a VMware Ubuntu installation?

    Yes. Make sure you have enough ram though!




    Can the OTA package just be flashed over stock ICS and not lose any data like a regular OTA update?



    No, you want to wipe everything.


    Click to view quoted image


    Dafuq did I just read?

    I'd like to take this moment to thank all the people who do the hard work of building custom ROMs so I can just download a single file and select yes to install it.

    Thank you for making my life easier. Click to view quoted image
    Lol

    Sent swiftly by Oliver using Android Central Forums
    07-14-2012 09:39 PM
  21. Andrew Ruffolo's Avatar
    what this method compiles isnt an ota, it's a rom from source. (d - correct me if i'm wrong this isnt my area of expertise at all).

    when the jb ota is available down the road, there will be a method in which you can update to jb from ics without wiping data, most likely ahead of the ota release itself or at least concurrent with it.
    You can compile 2 different ways.
    1) make otapackage -j* which makes a flashable .zip file
    2) make -j* which makes a .img file you can flash through fastboot.

    You could theoretically try installing this on top of a stock ROM, but I wouldn't even try it without a lot of free time, backup on the phone and on the computer (just in case you need to restore using a stock ICS image).

    Sent from my Transformer TF101 using Android Central Forums
    zero neck likes this.
    07-14-2012 09:42 PM
  22. dmmarck's Avatar
    You can compile 2 different ways.
    1) make otapackage -j* which makes a flashable .zip file
    2) make -j* which makes a .img file you can flash through fastboot.

    You could theoretically try installing this on top of a stock ROM, but I wouldn't even try it without a lot of free time, backup on the phone and on the computer (just in case you need to restore using a stock ICS image).

    Sent from my Transformer TF101 using Android Central Forums
    I wouldn't even risk it. Test it properly and wipe everything including system.

    Sent swiftly by Oliver using Android Central Forums
    07-14-2012 10:12 PM
  23. dually's Avatar
    I removed the recovery folder, removed the 2 lines from the updater script that contained the word "recovery", put the su apk in /system/app, and replaced the su executable in /system/xbin, and then rezipped the ota.

    But when I tried to flash with cwm, installation aborted. So I tried Nexus Bean instead and that works fine.
    07-14-2012 10:31 PM
  24. dmmarck's Avatar
    I removed the recovery folder, removed the 2 lines from the updater script that contained the word "recovery", put the su apk in /system/app, and replaced the su executable in /system/xbin, and then rezipped the ota.

    But when I tried to flash with cwm, installation aborted. So I tried Nexus Bean instead and that works fine.
    The best way I've done it is simply editing within the zip.

    Sent swiftly by Oliver using Android Central Forums
    07-14-2012 10:37 PM
  25. dually's Avatar
    I wondered about that.
    07-14-2012 10:47 PM
306 1234 ...
LINK TO POST COPIED TO CLIPBOARD