[Verizon] Galaxy Nexus root / un-root without unlocking bootloader

Last Updated:

  1. Larzzzz

    Larzzzz Active Member

    Scary, thank you very much for your help and in dealing with my ineptitude while doing this.
    I did not invoke "su" per se'. I thought that happened with the "root-for-windows" batch file in your scripts. OTA told me that the device was rooted, that root permission was granted, file system supports root protection, and that a protected su copy is available. OTA also tells me that the superuser app is installed.
    But, if I understand you correctly, I could copy the update.zip folder to the sd card, then use ES to move it over to the cache folder?
    Thanks again

  2. scary alien

    scary alien not really so scary Moderator

    That sounds right! :)

    Nah, my scripts just give you root for 4.0.2. Don't forget about OTA RootKeeper if you want to stay rooted when you get to 4.0.4....

  3. Larzzzz

    Larzzzz Active Member

    ....writing the CDMA radio as I type... thank you thank you thank you
    re-booted.....optimizing aaplications...of 37..... SCORE!!!!! <insert happy dance here>
    Ze phone is now updated to 4.0.4!!!
  4. Larzzzz

    Larzzzz Active Member

    Oooooooooook, one more post to say thanks to Scary, for not having a life like me and answering my post at 11:38 last night, as well as all of my subsequent posts. Your expertise has been invaluable and very much appreciated.
    And thanks to diverbelow, his post, #13 in this thread, told me the steps to take to get to the update from cache screen.

    All of my apps are still there (yay), and with some more reading of various threads, I'll try a ROM or 3.

    Mucho gracias, komsomnida, domo arigato.
    scary alien likes this.
  5. nexususer7

    nexususer7 New Member

    Scary Alien, Thanks for your awesome instructions updating to 4.0.4.

    Need your help again... I need to return my galaxy nexus phone as there is a hardware problem, but I have updated to 4.0.4 using your technique in this thread without unlocking bootloader.

    Can I return the phone for replacement without getting into trouble? I am assuming it should be ok since i didnt unlock the bootloader.

    Your feedback is greatly appreciated.

  6. scary alien

    scary alien not really so scary Moderator

    Well, I can't say 100% for sure, but VZW probably will only check to see that you've still got a locked bootloader and may not notice or care that you've got 4.0.4 installed (and/or root, if you still have it).

    I'm not sure that you could revert back to 4.0.2 without unlocking and relocking your bootloader, though...

    By the way, welcome to the AndroidForums! Hope you continue to hang around with us :).
  7. nexususer7

    nexususer7 New Member

    Thanks for the quick response Scary. I am thinking for reverting it to stock to be on the safer side. I guess I will need to root it first right? I found different threads on this forum to do that.. which one do you recommend in my case?

    Thanks a trillion for your help.

  8. scary alien

    scary alien not really so scary Moderator

    Nope, you don't need to be rooted to unlock and/or return to stock.

    Here's How to unlock your bootloader.

    Here's How to un-root (return to stock).

    Here's How to re-lock your bootloader

    Be sure to click the "Show" buttons to expand that posts.

    Its pretty simple...just take your time and you'll be fine (I've done this process more than 15 times).

    nexususer7 likes this.
  9. nexususer7

    nexususer7 New Member

    scary alien likes this.
  10. Larzzzz

    Larzzzz Active Member

    I wish I could've said that.... lmaoooo. But yeah, I concur with your last sentence.
    scary alien likes this.
  11. eagle nexus

    eagle nexus Active Member

  12. scary alien

    scary alien not really so scary Moderator

    Hey, nexususer7!

    Sorry to re-quote and re-reply re. this... I just realized that you should be able to re-flash an update.zip-type of file (were one to exist) that could put you back to stock 4.0.2.

    I'm not sure that such a .zip exists or not, but I might try making such a file for others since I don't think you need this anymore...(haven't made one before, but there's a few templates I could reference for this). I will, of course, search before I attempt to make it myself ;) :).

    Sorry for not thinking about this sooner, but I must've had a brain-fart and forgot that such a thing should be possible.


    edit: also, I'm pretty sure there's at least one stock 4.0.2 ROM out there...gotta find it (think fabolous made it...)
  13. scary alien

    scary alien not really so scary Moderator

  14. eagle nexus

    eagle nexus Active Member

    Can i flash clockworkmod with rom manager even though i have a locked bootloader and am rooted (using your method)? Also, should i just wipe my phone and unlock the bootloader and root with a different method? Kind of confused on what to do and if it'll work :)
  15. scary alien

    scary alien not really so scary Moderator

    Answering back in the other thread...(still typing ;) :)).
  16. xiutian

    xiutian Active Member

    Thanks so much for this. I'm pretty happy with the stock rom, just needed root for stuff like screenshots and backup. Script ran smoothly, I'm rooted!
    scary alien likes this.
  17. eagle nexus

    eagle nexus Active Member

    Wait, so this method for rooting works exactly the same as other methods do with an unlocked bootloader too (in the process of unlocking :) )?
  18. scary alien

    scary alien not really so scary Moderator

    Well, its better to say that this process will work regardless of whether your bootloader is unlocked or not--there's nothing inherent to this thread's method that "knows" (or cares) about the lock status of your bootloader (except the member, of course ;) :)).

    The other methods that require an unlocked bootloader utilize fastboot to at some point flash or soft-boot an img file that allows you achieve root (either directly or indirectly, depending on the exact method used).

    Does that make sense? :)
  19. eagle nexus

    eagle nexus Active Member

    So it'll work the same afterwards, right?
  20. scary alien

    scary alien not really so scary Moderator

    If you mean after you unlock, then yes :).

    This mempodipper exploit that works for stock 4.0.2 will gain you root regardless of the status of your bootloader. I.e., you could use the mempodroid pre-compiled binary to gain yourself superuser/root access without actually installing the root binaries--its just that I utilized this process to install the root binaries (it seemed like the most useful purpose for it, after all :)).
  21. PhinPhin

    PhinPhin Active Member

    Thanks for the work so far!

    Unfortunately I'm stuck at connecting the Samsung Galaxy Nexus (4.0.2, without branding):

    Code (Text):
    1. C:\Users\USER\Downloads\simple-gnex-root-unroot\simple-gnex-root-unroot>adb devices
    2. List of devices attached
    Also the batchfile won't run to the end:

    Code (Text):
    1. C:\Users\USER\Downloads\simple-gnex-root-unroot\simple-gnex-root-unroot>unroot
    2. -for-windows.bat
    3. ECHO ist ausgeschaltet (OFF).
    4. # ==========================================================================
    5. # Samsung Galaxy Nexus Simple Un-Root by AndroidForums "scary alien"
    6. #
    7. # Written for and tested on Samsung Galaxy Nexus running stock Android 4.0.2
    8. #
    9. # This script will remove the root binaries (su, Superuser.apk) from
    10. # an rooted GNex without needing to unlock the bootloader
    11. #
    12. # For additional details, credits, etc., please visit:
    13. #
    14. # http://androidforums.com/verizon-galaxy-nexus-all-things-root/499117-root-gnex
    15. -without-unlocking-bootloader-yep.html
    16. #
    17. # Instructions:
    18. #
    19. # 1) Make sure you have the adb USB device drivers installed
    20. #
    21. # 2) Make sure you have USB debugging enabled on your phone
    22. #
    23. # 3) Connect your phone and computer via your USB cable
    24. #
    25. # 4) Run this script from the same directory where the rest of the
    26. #    files from the extracted .zip file are located
    27. #
    28. # ==========================================================================
    29. #
    30. Das System kann die angegebene Datei nicht finden.
    31. Dr
  22. scary alien

    scary alien not really so scary Moderator


    Welcome to the AndroidForums! :)

    Wow, you are bringing back memories! I lived in Heidelberg for three years back in the mid 70's (yep, I'm old-ish ;) :)). I wished I had retained and practiced my German, but unfortunately I couldn't :).

    Anyway, it does indeed sound like you've got USB driver issues...see if Steven's thread here helps:


    That will hopefully get you going...if not, check-out this post: How to install the adb & fastboot USB drivers (MS/Windows users only), especially click on the "Show" button in the bullet #2 for the Naked drivers.

    Let us know how this goes!

  23. PhinPhin

    PhinPhin Active Member

    Thanks for your fast reply! :)

    I already tried different drivers, I have no idea where the magic lies...
    something changed now(I translated the german stuff for your convinience :) ):

    Code (Text):
    1. press any key to continiue . . .
    2. [*] waiting for adb USB connectivity to your device
    3. * daemon not running. starting it now on port 5037 *
    4. * daemon started successfully *
    5. ^CCancel Batch (Y/N)? y
    7. C:\Users\USER\Downloads\simple-gnex-root-unroot\simple-gnex-root-unroot>adb devices
    8. List of devices attached
    on the first try before a reboot "adb devices" showed me the device-id marked as "offline", but only one time...
  24. scary alien

    scary alien not really so scary Moderator

    Hmmm, PhinPhin...not sure what else to tell you re. the adb drivers...those were my go-to links...

    I have heard the PDAnet drivers work very well for folks, too...perhaps its actually a cable issue? (i.e., it works well-enough to charge but not to transfer data reliably?).

    Do you have a different cable and/or USB port to try?

    By the way, if you have a Linux or a Mac system available, those machines don't suffer from the USB driver issues that MS/Windows machines do.


    Also, just to make sure there's not confusion about when you can use fastboot and adb:

    This method doesn't need fastboot or for you to be in fastboot / bootloader mode on your phone (adb won't work in that mode).

    adb works when USB debugging is enabled for a normally booted-up Android device or while the device is in custom recovery (like ClockworkMod).


    Hope that helps a little...I'm sort of not sure what might be next for you to try and I'm heading to sleep soon. I will check back in the morning, though.
  25. PhinPhin

    PhinPhin Active Member

    I think I gonna try it under Ubuntu then :) Thanks for the advice, I will tell if it did work :D

Share This Page