Yeah, i used to have a rooted droid 1. Did a lot of things to that phone... Anyways, I'll be sure to throw a 'thanks' to onfire4g05's post. Again, thank you!
The Following User Says Thank You to eagle nexus For This Useful Post:
It sure will! That's OTA RootKeeper for those that don't read URL () and I mention that in the first post as a great thing to have in your back pocket--especially if you plan on rooting with an locked bootloader after getting an OTA.
I've used it several times now--its actually very clever how it works in making itself survive an OTA (it does this my making the /system folder where it installs itself "immutable" (unchangeable)--a property of the filesystem).
Okay, I've updated the first post to include onfire4g05's version of the shell script for Mac/OSX: root-unroot-for-mac-osx.sh.
Check it out and let me know...
I'm still working on your bootloader questions...I'm pretty sure that lickwidravr was spot-on, but it's good to have personal experience and confirmation .
Cheers!
Hey Scary,
Sorry for any delays in response. I used your absolutely incredible and simple non-unlock/root meathod. The addition of the .bat really made this about as easy as double clicking a file........actually thats exactly all you have to do! :-).
You are correct, i did mean that i used ROM Manager after rooting with your method. After rooting with your method i downloaded "OTA RootKeeper by Project VOODOO and backed up root(this allows you to restore root after updating to 4.0.4, I then copied the 4.0.4 update zip (after renaming it "update.zip") to the /root of the storage of the phone. Then within Rom manager i rebooted to recovery. From there you scroll to the update option and select the update.zip and confirm you want to update. Thats it, once it finished, the phone rebooted and tada, i was running 4.0.4 without issue. All i had to do from there was run OTA RootKeeper to restore root and i was done with the update. Officially on 4.0.4 rooted with your method originally and just restored your root with OTA RootKeeper after updating. :-)
The Following User Says Thank You to lickwidravr For This Useful Post:
Sorry for any delays in response. I used your absolutely incredible and simple non-unlock/root meathod. The addition of the .bat really made this about as easy as double clicking a file........actually thats exactly all you have to do! :-).
You are correct, i did mean that i used ROM Manager after rooting with your method. After rooting with your method i downloaded "OTA RootKeeper by Project VOODOO and backed up root(this allows you to restore root after updating to 4.0.4, I then copied the 4.0.4 update zip (after renaming it "update.zip") to the /root of the storage of the phone. Then within Rom manager i rebooted to recovery. From there you scroll to the update option and select the update.zip and confirm you want to update. Thats it, once it finished, the phone rebooted and tada, i was running 4.0.4 without issue. All i had to do from there was run OTA RootKeeper to restore root and i was done with the update. Officially on 4.0.4 rooted with your method originally and just restored your root with OTA RootKeeper after updating. :-)
Excellent, lickwidravr! Thank you for the reply .
Yeah, I also restored back to stock and re-locked my bootloader to verify the flashing of custom recovery can be done while still locked.
You can't use fastboot to flash it (or soft-boot it), though... ROM Manager will flash it, but its obviously not being done with the flash_image utility... I still can't figure-out how it does it because manually using flash_image fails for me.
I'm guessing that its either a coded routine in ROM Manager or a reference to something other than the recovery partition in "flash_image recovery <recovery image file>".
I'll keep digging and report back when I figure this out .
Cheers!
The Following User Says Thank You to scary alien For This Useful Post:
If you you flash clockwork mod recovery with rom manager, will you still get ota's and be able to update your phone "officially"?
If you have not installed a custom ROM, but have only rooted and installed a custom recovery (like ClockworkMod), then you will receive the OTA, but it won't be able to be applied because you don't have the stock recovery installed.
Its pretty easy to restore the stock recovery if you have an unlocked bootloader, but the only way I can see that you can while being stock and rooted with a locked bootloader is to make sure you have the /system/etc/install-recovery.sh and /system/recovery-from-boot.p file present and installed.
I'm trying to figure-out a way to manually flash a recovery (stock or otherwise) outside of ROM Manager and without having to use fastboot...still searching for the key piece of information re. that...
Ok, cool. One last thing, how would i deoxed the stock rom so that I can get custom mods. Is it even possible?
I'm sure you could find a deodexed stock ROM to install / flash through ClockworkMod.
Just keep in mind that if you're not careful, you might find yourself in a position to have to unlock your bootloader in order to use fastboot (depending on what you've done, of course ).
The first thing I would do if I were you would be to take a Nandroid backup of your stock (but obviously newly-rooted) setup...that way, you should be able to restore that if things ever go south on you (assuming that custom recovery is still available).
At some point though, depending on how many mods / changes, etc. you made, you might as well unlock the bootloader .
Okay, just wanted to report back here and follow-up re. the flashing of recovery outside of fastboot or via the something like the ROM Manager app.
Its actually pretty simple--just use the flash_image utiltity to write to the proper block device that maps to the recovery partition. The recovery partition is actually /dev/block/mmcblk0p8.
This could be used to re-flash stock recovery--something that ROM Manager doesn't do which folks would want/need in order to install OTAs, etc.
I was actually tinkering with the idea of making an app that would allow you to select and flash a selectable file (i.e., stock recovery for various versions, various versions of ClockworkMod, etc.). I'd release it for others if I could find a way to help ensure you couldn't goober-up your phone like flashing an improper file (i.e., keep a verified list of files' MD5 checksums and only allow those to be flashed).
Anyway, I'll keep you posted if I make something .
Cheers!
Last edited by scary alien; March 6th, 2012 at 09:32 PM.
Location: Northern Virginia but from Southeast Ohio
Posts: 143
Device(s): Verizon Galaxy Nexus, Motorola Xoom 4G
Carrier: Not Provided
Thanks: 57
Thanked 54 Times in 43 Posts
scary,
Make it 2 GNex's rooted this way. Used this to root and update my wife's brand new GNex today. A bummer was that the 4.0.4 OTA would not install and kept giving me an error type 7 message on her phone so I restored hers to stock using the files from before and then re-rooted. The 4.0.4 OTA installed no problem after that. Anyhow thank you again for all that you do.
Paul
The Following User Says Thank You to Paul1201 For This Useful Post:
Pleh (help), lol.
First off, Many thanks to Scary for setting up this nice lil batch file for us.
This Galaxy Nexus is my first Android device and it shows up in the windows explorer as such. When I select it to view, I am only presented with internal storage to select further. Looking into that, I do not see any folder labeled cache, but there are several cache folders in the Android/data/ com**** folders. There is an SD card in the list of folders.
Is the SD card the cache everybody is referring to where the 4.0.4 update goes?
I am an Android noob and don't want to turn this phone into a paper weight.
Thanks.
Pleh (help), lol.
First off, Many thanks to Scary for setting up this nice lil batch file for us.
This Galaxy Nexus is my first Android device and it shows up in the windows explorer as such. When I select it to view, I am only presented with internal storage to select further. Looking into that, I do not see any folder labeled cache, but there are several cache folders in the Android/data/ com**** folders. There is an SD card in the list of folders.
Is the SD card the cache everybody is referring to where the 4.0.4 update goes?
I am an Android noob and don't want to turn this phone into a paper weight.
Thanks.
Larzzzz,
Thanks and welcome to the AndroidForums!
I'm guessing you're talking about copying the 4.0.4 update.zip file to the /cache folder, eh?
And, you have successfully rooted your 4.0.2 device with my script?
Well, Astro File Manager is not a root-enabled app, so it won't be able to see the files and folders in the /cache directory like Root Explorer (paid app) or ES File Explorer (free app) can.
Since I don't use Root Explorer (great app, though, from all reports that I've read and fully worth it), I typically navigate the phone's filesystem manually via adb or with ES File Explorer if I'm not near my computer. Since ES File Explorer does not start-out with root enabled, you have to tell it to be, so that you'll be able to see /cache and other protected files, etc. Here's my notes for how to do this (assumes you are already rooted, by the way):
- download / install / launch ES File Explorer
- press the menu icon (bottom right)
- select Settings
- select Home Directory
- change your Home Directory to "/" (without the quotes, of course)
- return to the Settings screen
- scroll down to the bottom of the screen
- check the "Root Explorer" box in the Root Settings area (you'll get the Superuser whitelist app's pop-up asking for permission for this app)
- when you want to mount / and /system as writeable, check the "Mount File System" box under the "Root Explorer" checkbox
- hit the back button to return to the file navigation
- press the "Up" directory icon in the toolbar at the top of the screen--that should take you to the / (root) filesystem
Take your time, read-up, and ask questions..., someone will be around to help you out [although I myself might be signing-off pretty soon for the evening].
Hope that helps!
Cheers!
The Following User Says Thank You to scary alien For This Useful Post:
Wow, ty for the speedy reply!
I am, and I have. I unrooted it before I dug a hole I couldn't get out of.
The adb is part of the Android sdk I D/Ld from Google? I've installed it but haven't messed with it yet.
Wow, ty for the speedy reply!
I am, and I have. I unrooted it before I dug a hole I couldn't get out of.
The adb is part of the Android sdk I D/Ld from Google? I've installed it but haven't messed with it yet.
Thanks again.
Well, the adb (Android debug bridge) is a PC client (Windows, Linux, Mac) that can communicate with the adb server (daemon) on your Android device to do some special things.
Its pretty handy when you'd rather have manual control from your PC vs. using a GUI tool / file manager, etc.
adb does with the Android SDK, but you can also just download it from a mini-SDK package I created--see this thread (especially the "Mini-SDK" section):
hahahaha, it's been a loooooooooooooooong time since I've played in a DOS box. Anyone remember the TRS 80, or the Commodore 64?
So, I got the adb installed and the daemon is communicating with moi and my DOS box; but I think my syntax is wrong when I try to push the update.zip folder to the cache. I moved the update.zip folder to the same folder where my adb commands are located because I thought it would be easier, not, for me rather than typing and typing and typing.
Here is the line I use when trying to push the zip folder to the cache and I either get something saying the folder or file doesn't exist...
hahahaha, it's been a loooooooooooooooong time since I've played in a DOS box. Anyone remember the TRS 80, or the Commodore 64?
So, I got the adb installed and the daemon is communicating with moi and my DOS box; but I think my syntax is wrong when I try to push the update.zip folder to the cache. I moved the update.zip folder to the same folder where my adb commands are located because I thought it would be easier, not, for me rather than typing and typing and typing.
Here is the line I use when trying to push the zip folder to the cache and I either get something saying the folder or file doesn't exist...
grrrrr. Running Scary's "root-for-windows" now. OTA says I am rooted, but when I push the update file to the cache, I am getting a permission denied response.... lol. Maybe I haven't had enough coffee yet.
grrrrr. Running Scary's "root-for-windows" now. OTA says I am rooted, but when I push the update file to the cache, I am getting a permission denied response.... lol. Maybe I haven't had enough coffee yet.
Larzzzz,
How exactly are you trying to push the file over?
Did you invoke "su" from your adb shell to get root? (you need to have root permissions in order to write to /cache)
Or re-use the mempodroid binary to run the shell it starts with root access to do your copy...
Typically, you would use a root-enabled app like Root Explorer or ES File Explorer (as we discussed last night) to copy / paste your update.zip file to /cache.
If you are wanting to use adb, you'll have to do something like this (after you've rooted, of course):
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
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
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....
....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!!!
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.
The Following User Says Thank You to Larzzzz For This Useful Post:
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.
Thanks
Quote:
Originally Posted by scary alien
No problem!
Okay, I've updated the first post to include onfire4g05's version of the shell script for Mac/OSX: root-unroot-for-mac-osx.sh.
Check it out and let me know...
I'm still working on your bootloader questions...I'm pretty sure that lickwidravr was spot-on, but it's good to have personal experience and confirmation .
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.
Thanks
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 .
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.
Quote:
Originally Posted by scary alien
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 .
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.
Nope, you don't need to be rooted to unlock and/or return to stock.
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.
Thanks
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.
Cheers!
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...)
Last edited by scary alien; March 12th, 2012 at 06:29 PM.
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
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
Answering back in the other thread...(still typing ).
Wait, so this method for rooting works exactly the same as other methods do with an unlocked bootloader too (in the process of unlocking )?
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).
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).
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 ).
.
Introducing the Samsung Galaxy Nexus root / un-root without needing to unlock your bootloader. Yep!
Note: it appears that this will only work for GNex phones running Android ICS 4.0.2--the exploit that this method utilizes does not seem to work for 4.0.4; if you use this method to gain root in 4.0.2 and wish to retain it later in 4.0.4, be sure to use a utility like OTA RootKeeper to save root in 4.0.2 so that you don't lose it when you install the 4.0.4 OTA.
Thanks for the work so far!
Unfortunately I'm stuck at connecting the Samsung Galaxy Nexus (4.0.2, without branding):
Code:
C:\Users\USER\Downloads\simple-gnex-root-unroot\simple-gnex-root-unroot>adb devices
List of devices attached
Also the batchfile won't run to the end:
Code:
C:\Users\USER\Downloads\simple-gnex-root-unroot\simple-gnex-root-unroot>unroot
-for-windows.bat
ECHO ist ausgeschaltet (OFF).
# ==========================================================================
# Samsung Galaxy Nexus Simple Un-Root by AndroidForums "scary alien"
#
# Written for and tested on Samsung Galaxy Nexus running stock Android 4.0.2
#
# This script will remove the root binaries (su, Superuser.apk) from
# an rooted GNex without needing to unlock the bootloader
#
# For additional details, credits, etc., please visit:
#
# http://androidforums.com/verizon-galaxy-nexus-all-things-root/499117-root-gnex
-without-unlocking-bootloader-yep.html
#
# Instructions:
#
# 1) Make sure you have the adb USB device drivers installed
#
# 2) Make sure you have USB debugging enabled on your phone
#
# 3) Connect your phone and computer via your USB cable
#
# 4) Run this script from the same directory where the rest of the
# files from the extracted .zip file are located
#
# ==========================================================================
#
Das System kann die angegebene Datei nicht finden.
Drücken Sie eine beliebige Taste . . .[*] waiting for adb USB connectivity to your device
"Das System kann die angegebene Datei nicht finden." is the standard-message if windows can't find a file. I think it's about the missing dir from the second line
Code:
cd "%~dp0"
would love to use root without deleting all userfiles, though this doesn't seem to work yet... I manually uninstalled the drivers and installed pdanet and its drivers. The phone appears in the devicemanager in the category "SAMSUNG Android Phone" with the device-name "SAMSUNG Android ADB Interface", driver-date: 16.02.2012 driver-version: 2.9.317.215 from "SAMSUNG Electronics Co., Ltd."
And of course I did set USB-Debugging on, too. Tried also Recoverymode and the Fastboot(?) menu... nothing.
Any help?
Thanks and kind regards!
Last edited by PhinPhin; March 17th, 2012 at 11:22 PM.
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:
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:
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:
press any key to continiue . . .[*] waiting for adb USB connectivity to your device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
^CCancel Batch (Y/N)? y
C:\Users\USER\Downloads\simple-gnex-root-unroot\simple-gnex-root-unroot>adb devices
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...
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.
LinkBack to this Thread: http://androidforums.com/verizon-galaxy-nexus-all-things-root/499117-galaxy-nexus-root-un-root-without-unlocking-bootloader.html
11Likes
-- take your time and read and learn...tons of folks and threads around here to help you along your journey.
