[GUIDE] MAC Rooting Nexus S - Nexus S General

1/27/11 Update: Some members have commented that the MoDaCo Superboot method is easier, and although I haven't used it myself, it does look easier. If you want to go that route instead, you'll still need to unlock your bootloader, which means completing Steps 1-5 below. After that, you can go with the method given here: http://forum.xda-developers.com/showthread.php?t=927838
________________________________________________________
The following directions should let you root your Nexus S using an Intel Mac running OS 10.5 or 10.6. Thanks to Koush for providing the method and the recovery img, to ChainsDD for providing Superuser, and to Luxferro for providing a workaround for 2.3.1.
You should apply the 2.3.1 OTA update before obtaining root. Otherwise you'll have to do it over again after the update. If you installed a rooted/insecure boot image with the original instructions and now find yourself unable to upgrade to 2.3.1 (Status 7 error), one option is to use ROM Manager to restore the 2.3.1 Nandroid backup kindly provided by momohammed20 in this thread. From there, you will have stock 2.3.1 and can follow the steps below to obtain root again.
Warning: If you break your phone trying this, I am not responsible. I do not guarantee that the following is safe or that the steps are correct. Rooting your phone voids the warranty. I have no responsibility for anything that occurs as a result of your following these directions! I cannot provide any support nor guide you in undoing this process and restoring the phone to factory condition.
This process will wipe your phone. Ie, you will lose all your apps/data on your phone and have to reinstall them. It will also wipe your external storage, so back that up prior to proceeding if you want to keep anything.
1) Download the "androidsdk.zip" file from here: http://www.box.net/shared/ljhg8t5sjh
Unzip that file (if not already unzipped automatically upon download), and place the "androidsdk" folder on your Desktop. It has to be in this location for the rest of the steps to work.
2) On your phone, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
3) Connect the phone to your Mac via the USB cable
4) Open a Terminal window on your Mac (Applications>Utilities>Terminal), and copy/paste the following into the Terminal:
Code:
~/Desktop/androidsdk/platform-tools/adb reboot bootloader
Hit "Return" and wait for your phone to to reboot into Bootloader/Fastboot mode
5) If your Bootloader screen says "LOCK STATE - UNLOCKED" then skip to Step 6. If it says "LOCK STATE - LOCKED" then copy/paste the following into the Terminal:
Code:
~/Desktop/androidsdk/tools/fastboot oem unlock
Hit "Return" and on your phone will prompt you to confirm and warn you that you are going to lose everything. Confirm. At this point you will have an unlocked bootloader.
6) Copy/paste the following into the Terminal window:
Code:
~/Desktop/androidsdk/tools/fastboot flash recovery ~/Desktop/androidsdk/tools/recovery-clockwork-3.0.0.0-crespo.img
Hit "Return" again and wait for recovery to flash.
7) At this point you should still be in Bootloader/Fastboot mode. DO NOT REBOOT YOUR PHONE*. Press the "Volume Down" key until "RECOVERY" is highlighted, and press the "Power" key to select this option.
*Note: You must go to Recovery directly from Bootloader/Fastboot mode after Step 6 without rebooting your phone in between, or else your phone will replace ClockworkMod Recovery, hang at the "Google" splash screen requiring a battery pull, and you'll need to start again from Step 6.
For the following steps while in Recovery, use "Volume Down" to highlight a selection and "Power" to choose that selection:
8) Choose "mounts and storage"
9) Choose "mount USB storage". Your phone should now be mounted on the Mac as a Device called "NO NAME"
10) Look inside the "androidsdk" folder on your Desktop for a file called "su2361ef.zip", and using the Finder on your Mac, copy that file (without unzipping it) to the main directory of your mounted phone ("NO NAME").
11) Eject/unmount your phone in the Finder on your Mac.
12) On your phone, choose "Unmount"
13) Choose "mount /system"
14) Choose "+++++Go Back+++++"
15) Choose "install zip from sdcard"
16) Choose "choose zip from sdcard"
17) Choose "su2361ef.zip"
At this point you have root, but your phone will continue to replace ClockworkMod Recovery on reboot. To prevent this, do the following:
1) Reboot your phone, and download the app "Root Explorer" from the Market
2) Open Root Explorer and navigate to the "etc" directory.
3) Tap on the gray box that says "Mount R/W"
4) Tap and hold on the file "install-recovery.sh" and rename this file to "install-recovery.sh.old"
5) Download the app "ROM Manager"
6) Open ROM Manager and choose "Flash ClockworkMod Recovery". At this point you are all set .
---------------------------------------------
To re-lock your bootloader (Optional step):
1) With your phone connected and "USB Debugging" still enabled (which it will be unless you disabled it after the above), copy/paste the following to the Terminal:
Code:
~/Desktop/androidsdk/platform-tools/adb reboot bootloader
Hit "Return" and wait for your phone to to reboot into Bootloader/Fastboot mode
2) Copy/paste the following to the Terminal:
Code:
~/Desktop/androidsdk/tools/fastboot oem lock
Hit "Return".
Reboot your phone.
---------------------------------------------
Major thanks to Koush, ChainsDD, momohammed20, and Luxferro!

Your gonna need the recompiled fastboot. Then it makes it super easy.

So whats the advantage of having a rooted/insecure boot image as opposed to not? Sorry for the noob question

thanks x1,000,000
I would be lost without this, thanks a lot!!!
took me about 10-15 minutes
Didn't know I was going to lose all my data though, luckily I've only had it a few days and it all can be replaced

You freaking rock man! Thanks for this. Ill be rooting mine very soon.

I'm a little confused here...
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Linked File As..." Save that file (called "su2361ef") to your desktop and then copy it to the main directory of your mounted phone ("NO NAME").
Am I to change the name of this file to "su2361ef" or leave it as is... "su-2.3.6.1-ef-signed.zip" than place it into my main directory?
Thanks

Help please.
I'm down to the final steps, but when I try to get into recovery mode I keep getting a little Android with an "!" over it.
What am I doing wrong? I've pulled the battery, and tried it over a few times, but I keep getting the same thing.

rashad1 said:
thanks x1,000,000
I would be lost without this, thanks a lot!!!
took me about 10-15 minutes
Didn't know I was going to lose all my data though, luckily I've only had it a few days and it all can be replaced
Click to expand...
Click to collapse
Glad it was helpful. You should have gotten a warning on your phone screen about losing the data in Step 10, and you could have turned back at that point. I've now edited the post above to make it clear there as well.

WilliamStern said:
I'm a little confused here...
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Linked File As..." Save that file (called "su2361ef") to your desktop and then copy it to the main directory of your mounted phone ("NO NAME").
Am I to change the name of this file to "su2361ef" or leave it as is... "su-2.3.6.1-ef-signed.zip" than place it into my main directory?
Thanks
Click to expand...
Click to collapse
When I did it, the zip was already called "su2361ef". If yours is called "su-2.3.6.1-ef-signed.zip", I would leave it like that without renaming. Just remember the name so you can choose it in Step 21.
WilliamStern said:
Help please.
I'm down to the final steps, but when I try to get into recovery mode I keep getting a little Android with an "!" over it.
What am I doing wrong? I've pulled the battery, and tried it over a few times, but I keep getting the same thing.
Click to expand...
Click to collapse
Which step were you at? I hope someone can help you. I don't have any expertise . I only shared the steps above because they worked for me.

Amin Sabet said:
When I did it, the zip was already called "su2361ef". If yours is called "su-2.3.6.1-ef-signed.zip", I would leave it like that without renaming. Just remember the name so you can choose it in Step 20.
Which step were you at? I hope someone can help you. I don't have any expertise . I only shared the steps above because they worked for me.
Click to expand...
Click to collapse
I keep getting the "!" above the little Android, but when press power button plus volume up I only get 4 options.
-reboot system now
-apply update from /sdcard
-wipe data/factory reset
-wipe cache partition
I'm not seeing any of the other options you mention above.
I WANT ROOT! lol

WilliamStern said:
I keep getting the "!" above the little Android, but when press power button plus volume up I only get 4 options.
-reboot system now
-apply update from /sdcard
-wipe data/factory reset
-wipe cache partition
I'm not seeing any of the other options you mention above.
I WANT ROOT! lol
Click to expand...
Click to collapse
You did not flash the clockworkmod recovery correctly. The Triangle with exclamation point is the stock recovery image.
Redo the step that says fastboot flash recovery etc..etc..
Sent from my Nexus S

How about a noob guide for windows also Not that I wont be able to figure out from other sources when I want to root for the first time. But a noob guide here will come handy as well ;-)

Err... I give up. I just can't seem to get anything to work. I've followed everything step by step and nothing. I think it's my bootloader that won't unlock?

WilliamStern said:
Err... I give up. I just can't seem to get anything to work. I've followed everything step by step and nothing. I think it's my bootloader that won't unlock?
Click to expand...
Click to collapse
we can't help you much if you don't provide any detailed info other than you're not in the right recovery. Boot the phone on again and type this in terminal:
Code:
./adb reboot bootloader
check status of bootloader: LOCKED / UNLOCKED
and we go from there.

jroid said:
we can't help you much if you don't provide any detailed info other than you're not in the right recovery. Boot the phone on again and type this in terminal:
Code:
./adb reboot bootloader
check status of bootloader: LOCKED / UNLOCKED
and we go from there.
Click to expand...
Click to collapse
I think this is where I'm having an issue? Nothing seems to happen whenever I input a command into my terminal on my computer.

WilliamStern said:
I think this is where I'm having an issue? Nothing seems to happen whenever I input a command into my terminal on my computer.
Click to expand...
Click to collapse
What happens if you plug your phone into the USB and type adb devices?

Michael.B. said:
What happens if you plug your phone into the USB and type adb devices?
Click to expand...
Click to collapse
I'm new at all this, so I'm sorry.
this is what I get
-bash: adb: command not found

WilliamStern said:
I'm new at all this, so I'm sorry.
this is what I get
-bash: adb: command not found
Click to expand...
Click to collapse
Seems like you have not installed adb yet. What OS are you on?
EDIT: Duh, looked at the thread title. I may not be of much help, but did you update your path directory to look at the correct folders?

Michael.B. said:
Seems like you have not installed adb yet. What OS are you on?
EDIT: Duh, looked at the thread title. I may not be of much help, but did you update your path directory to look at the correct folders?
Click to expand...
Click to collapse
Yeah, I did the updates.
I'm gonna try again from scratch. Thanks for the help.

William, what happens when you plug your phone into the Mac, open Terminal, and copy/paste the following command (don't forget to change "Amin" to the name of YOUR home directory):
Code:
/Users/Amin/Desktop/androidsdk/platform-tools/adb devices
Typing just "adb devices" won't work because we never set the path to adb, but the above code should work (and give you a list of connected devices, which would be just your Nexus represented as a number) if you correctly did Steps 1-4 above.

Related

Free Unlock For I9000 - I897 - T959 To All Users

I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone
I9000 drivers
I9000 drivers
This solution is is not working for me. The problem is that the Update.zip says:
E: Signature verfication failed
Installation aborted
Any advice? How to install that update.zip package?
cellularhut said:
I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone
Click to expand...
Click to collapse
Fantastic find if it works, my phone is unlocked so I can't test it but thanks a lot for sharing!!! Priceless
N.B. The first 8 steps are the process for rooting your phone, since you need to be root to do step 11. If you already have a rooted phone, start from step 10.
tyxerakias said:
fantastic find if it works, my phone is unlocked so i can't test it but thanks a lot for sharing!!! Priceless
n.b. The first 8 steps are the process for rooting your phone, since you need to be root to do step 11. If you already have a rooted phone, start from step 10.
Click to expand...
Click to collapse
1000000000000000% working tested before post here !!!!!
I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks
erreterr said:
I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks
Click to expand...
Click to collapse
Please read my post above. By doing this, you are rooting your phone.
It seems that the update.zip has not been properly signed, I see that it contains a new busybox, maybe the OP tried to optimise it and failed?
Use the original update.zip from the FAQ (http://www.multiupload.com/JHIFK9K80P) to root your phone, then continue from step 9.
The same happens with the file that I downloaded from your posted link!!!
Whats going wrong here?
Tyxerakias said:
Please read my post above. By doing this, you are rooting your phone.
It seems that the update.zip has not been properly signed, I see that it contains a new busybox, maybe the OP tried to optimise it and failed?
Use the original update.zip from the FAQ (http://www.multiupload.com/JHIFK9K80P) to root your phone, then continue from step 9.
Click to expand...
Click to collapse
No idea. Have you rooted your phone already? Have you installed any mods or firmwares?
No need to root
You dont need to root your phone to get to Step 11. The Terminal Emulator I installed from the Market let me do Step 11 directly.
All I then just did was email the nv_data.bin file to my inbox and later just open it in Textpad.
So, it was a bad tutorial. I tried to go step by step but now I begin from step 11 and everything is OK. My first I9000 unlocked like a charm
Thanks
knkartha said:
You dont need to root your phone to get to Step 11. The Terminal Emulator I installed from the Market let me do Step 11 directly.
All I then just did was email the nv_data.bin file to my inbox and later just open it in Textpad.
Click to expand...
Click to collapse
Huh. Interesting. I would have thought /efs is a protected folder.
I have a Bell one, i asked their staff when i bought my phone if i still on WARRANTY when i unlock the phone by Bell, they said yes.
Anybody know if i will lose my phone WARRANTY after i unlock the phone? Or can i lock it back if my phone have any problem in the future?
Thanks
could somebody point out which value in the address 00181460 says the unlock code?
erreterr said:
The same happens with the file that I downloaded from your posted link!!!
Whats going wrong here?
Click to expand...
Click to collapse
you should put the update.zip file on your internal sd card directory.
i encountered the same error when i put the update.zip file in the external sd card
erreterr said:
So, it was a bad tutorial. I tried to go step by step but now I begin from step 11 and everything is OK. My first I9000 unlocked like a charm
Thanks
Click to expand...
Click to collapse
which of the values in the said address gives the unlock code?
Hi,
I have a NSPRO box and read the unlock code, but as I insert it, it doesn't unlock the phone.
As this didn't work, I tried your method, and the code that showes up is the same as read by NSPRO box, and... it still doesn't work.
Attached is the printscreen of the HEX area where the code is. I've noticed it says "18146D" and not "181460" as your indicated. Could this be the reason why the code doesn't work?
Please help...
Samsung Vibrant SGH-T959 Recovery Mode
I've tried all sorts of button combinations to get the Samsung Vibrant T959 into recovery mode. I think since this device is a T-Mobile phone, the firmware has been modified for VolUp+VolDn+Pwr recovery mode.
As of now, the only way I know how to get the phone into recovery mode is by using the Android SDK and sending off a command: adb reboot recovery
I've been putting together an Android SDK & Rooting tutorial as well as other Samsung Vibrant T959 findings here: jordanpeterson.me/content/t-mobile-samsung-vibrant-sgh-t959
Sorry.. the external references aren't working.. Good spam rules on new users.
Thanks
Jordan
It worked great, althoug the address on my I9000 was 00181462. My suggestion is try to find closest address to the given by the tuturial....
Thanks for everything
Don't need to root the device. Download terminal emulater from Market. Went straight to step 10. Works like a charm. Thanks for the instructions.
Sent from my GT-I9000M using XDA App

[GUIDE] Root 2.3.3 On a Mac WITH OEM Unlock!

***
If you're looking for a guide on how to root on Windows, there is a fantastic guide here written by W0lv3r1n3!!
***
I know there is a stickied guide for this but it hasn't been updated since 2.3.1 so I decided to update it a little bit just to make things easier for people. Credit for this goes to Amin Sabet and DistortedLoop with a few changes/additions by me.
Warning: If you break your phone trying this, I am not responsible. I do not guarantee that the following is safe or that the steps are correct. Rooting your phone voids the warranty. I have no responsibility for anything that occurs as a result of your following these directions! I cannot provide any support nor guide you in undoing this process and restoring the phone to factory condition.
This process will wipe your phone. Ie, you will lose all your apps/data on your phone and have to reinstall them. It will also wipe your external storage, so back that up prior to proceeding if you want to keep anything.
1) Download this file (http://dl.dropbox.com/u/22368847/adb-fastboot.zip) and unzip it to your desktop (Inside you'll find all the files you need to proceed including "adb", "fastboot", "recovery-clockwork-3.0.0.5-crespo.img", and "su-2.3.6.1-ef-signed.zip").
2) On your phone, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
3) Connect the phone to your Mac via the USB cable
4) Open a Terminal window on your Mac (Applications>Utilities>Terminal), and copy/paste the following into the Terminal:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
Hit "Return" and wait for your phone to to reboot into Bootloader/Fastboot mode
5) If your Bootloader screen says "LOCK STATE - UNLOCKED" then skip to Step 6. If it says "LOCK STATE - LOCKED" then copy/paste the following into the Terminal:
Code:
~/Desktop/adb-fastboot/fastboot oem unlock
Hit "Return" and on your phone will prompt you to confirm and warn you that you are going to lose everything. Confirm. At this point you will have an unlocked bootloader.
6) Copy/paste the following into the Terminal window:
Code:
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery-clockwork-3.0.0.5-crespo.img
Hit "Return" again and wait for recovery to boot.
For the following steps while in Recovery, use "Volume Down" to highlight a selection and "Power" to choose that selection:
8) Choose "mounts and storage"
9) Choose "mount USB storage". Your phone should now be mounted on the Mac as a Device called "NO NAME"
10) Move the zip file "su-2.3.6.1-ef-signed.zip" from the "adb-fastboot" folder to the "NO NAME" Device on you computer.
11) Eject/unmount your phone in the Finder on your Mac.
12) On your phone, choose "Unmount"
13) Choose "mount /system"
14) Choose "+++++Go Back+++++"
15) Choose "install zip from sdcard"
16) Choose "choose zip from sdcard"
17) Choose "su-2.3.6.1-ef-signed.zip"
Some people with new Nexus S' are finding that the file discussed in the following steps does not exist. If you cannot find it but can still reboot into Clock Work Recovery Mod then don't worry, you're still rooted and fine!
At this point you have root, but your phone will continue to replace ClockworkMod Recovery on reboot. To prevent this, do the following:
1) Reboot your phone, and download the app "Root Explorer" from the Market
2) Open Root Explorer and navigate to the "etc" directory.
3) Tap on the gray box that says "Mount R/W"
4) Tap and hold on the file "install-recovery.sh" and rename this file to "install-recovery.sh.old"
~~~~~~~~~~~~~~~~~~~~~​
Updated for ICS and included instructions in the zip!
5) Download the app "ROM Manager"
6) Open ROM Manager and choose "Flash ClockworkMod Recovery". At this point you are all set .
Mods any chance we can get this stickied to replace the old one? There seems to be some confusion about using the old version to root.
Nicely done.
any guides to root 2.3.3 for windows?
J__ said:
any guides to root 2.3.3 for windows?
Click to expand...
Click to collapse
Honestly, its a very similar process. Just download a different version of the SDK and make sure you put the recovery image in the folder of the installed SDK called tools. Then when you get to executing the commands do this:
Code:
cd *remove the asterisks and type the file path to the directory for the tools folder of your SDK folder in program files*
Then remove the
Code:
desktop/adb-fastboot/
and just type the other parts.
jlevy73 said:
Nicely done.
Click to expand...
Click to collapse
You think its enough of a difference to switch this with the other stickied thread on rooting for a mac jlevy?
im getting this error message "cannot load 'recovery-clockwork-3.0.0.5-crespo.img'"
so stuck on step 6. any advice?
thanks
Also, curious because now I have an unlocked bootloader but nothing else has been done. This shouldn't be an issue I assume.....
I've never heard of someone having that issue. Try the command fastboot flash recovery recovery-clockwork-3.0.0.5-crespo.img
Sent from my MattedBlues CM7 Google Nexus S!
kenvan19 said:
You think its enough of a difference to switch this with the other stickied thread on rooting for a mac jlevy?
Click to expand...
Click to collapse
I don't think it's enough but it would make a great add-on to the original rooting for mac thread.
-bash: fastboot: command not found
Is what it staid after trying that. Not sure what I am doing wrong. Have rooted several phones before.
owlmatt said:
-bash: fastboot: command not found
Is what it staid after trying that. Not sure what I am doing wrong. Have rooted several phones before.
Click to expand...
Click to collapse
Did you install the android SDK? I'm a little lost, I'm not sure what could be going wrong...I used this method to root both my and my wife's phones with no issues.
This could be the place I screwed up. I've never used the SDK on a mac and don't have a pc. I downloaded the files, used eclipse and loaded up everything it asked me to do.
I will look around for others guides on this maybe.
Maybe I need to learn more about android SDK, but I tried to follow all the instructions. One thing that was a problem was using the newest version of eclipse. It wouldn't install any add ons so I went to the older 3.4 version.
I would go to help, install new software, click on development tools, sign the terms then always get an error loading the software. This step does work on version 3.4. I guess I'm a real new noob at SDK.
owlmatt said:
This could be the place I screwed up. I've never used the SDK on a mac and don't have a pc. I downloaded the files, used eclipse and loaded up everything it asked me to do.
I will look around for others guides on this maybe.
Maybe I need to learn more about android SDK, but I tried to follow all the instructions. One thing that was a problem was using the newest version of eclipse. It wouldn't install any add ons so I went to the older 3.4 version.
I would go to help, install new software, click on development tools, sign the terms then always get an error loading the software. This step does work on version 3.4. I guess I'm a real new noob at SDK.
Click to expand...
Click to collapse
Oh no! I see where I screwed up in my guide...I'm sorry I see it clearly now...don't know how I missed it before.
instead of
Code:
~/Desktop/androidsdk/tools/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
type
Code:
~/Desktop/adb-fastboot/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Still the same result for me. Sucks. I had moved the recovery image into the SDK to match you code, previously as I i've been trying everything I know.
owlmatt said:
Still the same result for me. Sucks. I had moved the recovery image into the SDK to match you code, previously as I i've been trying everything I know.
Click to expand...
Click to collapse
Okay I have one last idea...I'll grab the link then edit this with the stuff...brb
Download this SDK http://www.box.net/shared/ljhg8t5sjh it should have everything including an older version of CWM which should still work (again unzip it to your desktop) and try using this command:
Code:
~/Desktop/androidsdk/tools/fastboot flash recovery ~/Desktop/androidsdk/tools/recovery-clockwork-3.0.0.0-crespo.img
If it works you can flash the newest version of CWM through rom manager later.
I AM ROOTED!!! How do I buy you a beer?
owlmatt said:
I AM ROOTED!!! How do I buy you a beer?
Click to expand...
Click to collapse
Haha don't worry about it man! Just glad you're rooted now
Happy to if you change your mind. Just post your paypal. Otherwise Thanks again. I hit thanks on the site as well a bunch of times.
Time to start flashing and overclocking.
owlmatt said:
Happy to if you change your mind. Just post your paypal. Otherwise Thanks again. I hit thanks on the site as well a bunch of times.
Time to start flashing and overclocking.
Click to expand...
Click to collapse
If you really want to do something, I'd suggest buying the XDA Premium app from the market and help support XDA as a whole.
Consider it done.

[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!

UPDATED XOOM FLASHING GUIDE 02/02/12​
I recently bought a US Xoom MZ604 and had trouble flashing it initially. I came to a realization that the newer models of Xoom reinstalls the Stock Recovery after you flash a custom Recovery (eg. CWM, Rogue Recovery etc). This is uber frustrating for newer Xoom owners, especially those who are new to the flashing community, simply because you don not know exactly what's going on.
Also, I could not find any proper, full and updated guide to flashing your Xoom. So i decided to take the initiative to do so.
WARNING: I DO NOT TAKE ANY RESPONSIBILITY IF YOUR XOOM TURNS INTO A USELESS BRICK. BY FOLLOWING THIS GUIDE, YOU WILL VOID YOUR XOOM WARRANTY WITH MOTOROLA. YOU HAVE BEEN WARNED TO EXERCISE CAUTION WHILE FOLLOWING THIS GUIDE. STRICTLY FOLLOW THIS GUIDE AND I ASSURE YOU, NOTHING WOULD GO WRONG.
In order to follow this guide, you need fundamental knowledge of ADB and Fastboot for Android. Search around the forum for this knowledge.
STEP 1: Obtaining Required Materials
a.) Download the latest version of Android SDK from HERE and install it into your the root of your C: drive.
b.) Download the latest version of Java SE from HERE and install.
c.) Download and Install the latest version of Motorola USB Drivers from HERE.
STEP 2: Unlocking your Bootloader
What is a Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. Source: http://www.addictivetips.com/mobile/what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide/
Click to expand...
Click to collapse
1.) Make sure your Xoom is turned on. Connect it to your PC via USB.
2.) On your PC, open up File Explorer and Browse to:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
3.) In that directory, make sure nothing is selected, SHIFT+Right Click into empty space and select "Open command window here".
4.) Command Prompt will open up. Type the following command:
adb reboot bootloader
Click to expand...
Click to collapse
Your XOOM will reboot into the bootloader showing "Starting Fastboot Support Protocol".
6.) Type the following command into the Command Prompt to unlock your bootloader:
fastboot oem unlock
Click to expand...
Click to collapse
7.) Read the warning and follow the instructions on the Xoom Tablet itself from this point onwards. Use the Volume Down key to navigate to 'Accept' the agreement and press Volume Up to select.
8.) Once selected, your Xoom will now unlock and format itself, meaning, all data will be cleared and you will back to a factory rest.
9.) Reboot your Xoom with the following command:
fastboot reboot
Click to expand...
Click to collapse
10.) Exit Command Prompt.
STEP 3: Rooting your Xoom
1.) Download the latest version of "Universal Xoom Root" from this thread. Place the .ZIP file into the root of your SD card.
2. Download this version of "ClockworkMod Recovery - Modified for Motorola Xoom" and place it into this directory:
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
This will your new Recovery. MAKE SURE THAT IT IS IN .IMG FORMAT.
2.) With your Xoom still connected to your PC, type the following commands into Command Prompt (open up using the same method as STEP 1) to install your new Recovery.
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
3.) Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery. If you miss this window and somehow end up booting your Xoom normally, repeat from STEP 3, section 2 onwards again. DO NOT CLOSE THE COMMAND PROMPT WINDOW.
4.)To root your Xoom, please perform the following:
"install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Click to expand...
Click to collapse
After the root flashes itself, DO NOT REBOOT YOUR XOOM!
5.) Now you have to rename the 2 notorious files, that reinstall your Stock Recovery over CWM, into a format that is unreadable by the bootloader. In the already opened Command Prompt, type the following commands:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
6.) Reboot with CWM. Let your Xoom boot normally.
To test whether the root and flashing of CWM has been successful, type the following into your command prompt:
adb reboot recovery
Click to expand...
Click to collapse
If you are able to access the new Recovery, CONGRATULATIONS, you have successfully UNLOCKED & ROOTED your Xoom.
I would like to thank the Xoom Android community for your valuable commitment to into Xoom Android Development. Without you guys, the Xoom wouldn't feel much powerful in terms of usage. Also, I'd like to extend my gratitude to okantomi for his help when I first started out.
Those those experienced users of Xoom, please kindly help the newbies like me answer their questions in this thread. Could I also request the mods to sticky this thread for reference.
NOTE: For users who would like to revert to the original recovery, type the following into ADB: (tip provided by wontoniii)
adb shell mv /system/recovery-from-boot.p.old /system/recovery-from-boot.p
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
adb reboot
Click to expand...
Click to collapse
Reference Threads:
1.) [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]
2.) [ROM][Nightly][ICS] Team Eos WiFi Nightlies (Wingray/MZ604)
3.) [Root] Universal Xoom Root - ANY XOOM ANY UPDATE
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
Click to expand...
Click to collapse
This can be easily reverted with:
adb remount
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
Click to expand...
Click to collapse
In case someone could want the old recovery back without flashing anything
wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I believe your method is better, at least there's still a recovery to revert to in case something goes wrong. I'll add it to the guide. Thanks for the suggestion!
Sent from my Xoom using Tapatalk
My tool can do it automatically, check on the signature LordAIOTool, and if you guys can please test and tell me the results
---------- Post added at 08:57 PM ---------- Previous post was at 08:39 PM ----------
wontoniii said:
Just my opinion, I would not recommend to everybody the step3/point6 as you do it...
I would just do something like:
This can be easily reverted with:
In case someone could want the old recovery back without flashing anything
Click to expand...
Click to collapse
I liked your idea too, will put on my tool (can I?)
XxLordxX said:
I liked your idea too, will put on my tool (can I?)
Click to expand...
Click to collapse
Sure, no prob
Thread moved to General.
This seams to be a good guide can anyone tell me if it works it is more detailed than the other guide ???? and why was it moved to general
This guide is great and easy and very updated i dont know why other people dont use it. One thing tho you should be more clear on how to reboot into recovery tell them to press volume up + power then let go then wait three seconds and after logo and press only the volume down
Having a problem with using your guide
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7
Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
dstruble said:
Ok, I'm a noob. I am probably missing something simple. When I type "adb reboot bootloader" at the command prompt it says "Device not found." My Xoom is connected via USB (Same cable it came with). Xoom appears in my explorer window I can browse through the files; I even transferred files to the SD card. It is just not detected from the command prompt window when I start the unlocking procedure. Any assistance would be appreciated. Using Xoom 4G, Android 3.2.4; Windows 7
Click to expand...
Click to collapse
kewlguru said:
Make sure that adb debugging is checked. You can find this under Applications > Development settings.
Before you type, check if your device is listed
Code:
adb devices
This should list your device.
Click to expand...
Click to collapse
That did the trick I figured it was something simple like that. Thanks for the help.
Superb Guide!
Many thanks, I spent the best part of a day trying various methods but found this to be the most n00b friendly
1 point it may be worth adding is to use adb you must have java installed on your pc, without you get error "adb.exe is not a valid win32 application"
first time root/flash rom question
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance
Don_Don said:
Hi all..to start with sorry if im asking in the wrong place. I have a stock Xoom with an unmodded ICS I also own the Bionic. Also I have never rooted or flashed anything so I am a super noob (soon to change though).
I wated to be able to have USB host functionality and be able to have SD card read/write assess so last week I started searching Google which led me to this wonderful sight of great help. There might be too much help because after tons of reading there is more than one way to do what I want. Can someone please point me in the best way to root and which rom I should use that will give me the least about of trouble.
Thanks in advance
Click to expand...
Click to collapse
Ihave similar story m8. I spent the majority of yesterday reading and learning how to root. This is by far the easiest guide to follow to ulock and root your xoom.
I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.
At which point do I back up data already on Xoom? Will there be any data loss?
Don_Don said:
At which point do I back up data already on Xoom? Will there be any data loss?
Click to expand...
Click to collapse
You have to backup your data before unlocking the bootloader, which is the VERY FIRST step.
gbenj said:
I just want to correct a small error here.
In Step 6 of Step 3, you say you want to check and make sure that the new bootloader is on there correctly.
I think you mean to say check and make sure the new "Recovery" is on there and the adb command would be "adb reboot recovery".
Am I wrong? If so, please disregard.
Click to expand...
Click to collapse
Yes you are right. Thanks for pointing that it, it could have confused some. I'll rectify that right away.
Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?
TADitto said:
Ok so I have a question about this rooting process and I haven't seen the answer yet. My question is will this process work weather your xoom is running ICS or HC?
Click to expand...
Click to collapse
Yes, this process will work regardless of your OS.

[Guide] Ultimate Nexus 4 Root Guide

Post One: Unlocking and Rooting
Post Two: Installing Roms / Kernels / Tweaks
Post Three: Panic Section / FAQ / Miscellaneous
Unlocking The Bootloader And Obtaining Root
*This part of the tutorial is geared towards Windows users. The MAC instructions are very similar, from what I understand. Install the package the same way. All ADB/Fastboot commands may need to start with "adb-mac" (no quotes) rather than "adb" (no quotes). Due to the vast amount of Linux distros available; instructions will vary for your device. Once ADB/Fastboot are set up all command will begin with "./adb" (no quotes) rather than "adb" (no quotes). Once ADB/Fastboot are set up; this guide is relevant to everyone.*
Time required:
20-40 minutes.
Setting up ADB for our device:
Download the AndroidSDK onto your computer.
Note: Google changes their mind every other week as to if this will be distributed as a .zip or an .exe. If you get an .zip file, simply extract the contents to your C:\ drive. For an .exe install it like you would any other program, but set the path directly to the C:\ drive when the installer asks.
Or...you can use this page to download the "ADB for Dummies AIO App."
This will automatically install ADB for you to your C:\ directory. It's very very simple this way.
If your platform-tools folder doesn't have a fastboot.exe, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder.
Now you have ADB installed! Congratulations.
Unlocking the Bootloader:
***NOTE***
This will perform a factory reset on your device. You will lose all applications. Even the data on your SD Card! I'd recommend making a Backup to your computer BEFORE performing this. There is a method for backing your data up, detailed HERE.
For the time being, there is a method available that will allow you to unlock your device (and root it) without losing your data.
For instructions, click HERE. Please note: this is a hack and isn't the "conventional" and "accepted" way of unlocking your bootloader on a nexus device. The wipe requirement is there for your safety, really, and I'm certain this will be patched in the upcoming releases.
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
Option One:
Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
While that is downloading, on your Nexus 4: turn USB debugging on.
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Once the drivers are installed, navigate to the C:\android-sdk-windows\platform-tools folder on your computer.
Hold shift and right click. Select "Open Command Window Here."
Plug your phone into the computer. Now in this command window type:
Code:
adb reboot bootloader
(Hit Enter)
Your phone should now boot into a screen with a green android with his chest exposed.
Type this:
Code:
fastboot oem unlock
(Hit Enter)
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Driver with the newest date and install it. Now retry the code above.
Your phone will ask if you want to unlock it. Select "Yes" by using the volume keys and use power to select it.
Now, navigate to "Recovery Mode" with the volume keys. Use power to select.
A screen with another Android will pop up. Press Volume Up and Power at the same time.
Select Factory Reset. This process may take a few minutes. Be patient and let it work.
Once finished, select "Reboot."
Your phone is now unlocked!
Obtaining Root Access and Custom Recovery:
Turn on USB Debugging.
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Download the following:
SuperSU (CWM .zip)
CWM (Pick the version for your device)
Place the recovery-clockwork-VERSIONNUMBER-mako.img file into your C:\android-sdk-windows\platform-tools folder.
Put the SuperSU.zip on your phone.
Open another Command Prompt if it isn't still open. (Navigate to C:\android-sdk-windows\platform-tools and shift + right click. Select "Open Command Window Here.")
With your phone plugged in type:
Code:
adb reboot bootloader
(Hit Enter)
And wait for your phone to boot into the android again.
Now type:
Code:
fastboot flash recovery IMAGENAME.img
(Change the file name to the correct file name and Hit Enter)
Once that is finished: select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the SuperSU.zip that you transferred earlier and select "Yes" to installing.
Navigate back to "Reboot" and reboot your phone.
You're now rooted!
However, ClockworkMod Recovery won't continue to load after this.
To fix this, find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option.
If your recovery still doesn't stick around after a reboot, you have another couple options. Find a file explorer that allows root access, such as Root Explorer. Use this program to rename /system/etc/install-recovery.sh to /system/etc/install-recovery.bak. You'll need to mount the system as r/w to do this. Root Explorer provides a button at the top to do so.
Or, you can do this completely manually by firing up ADB again and running a few commands:
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
(Hit Enter)
Congratulations!
Your phone is now unlocked, rooted, and has a custom recovery!
Continue reading the next posts for info on getting custom roms, kernels, tweaks, and more!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Thanks:
Google, for making Android a reality.
VanillaTbone, for the ADB AIO app.
Efrant, for posting about a bootloader locking utility without USB.
ClockworkMod team, for being a part of making our phones as awesome as they are.
The assorted developers, who continue to push out amazing material for us to use.
The awesome community, for endlessly supporting both Android itself and its users.
Installing Custom Roms Kernels and Tweaks
All of the instructions below require your bootloader to be unlocked. Please follow the guide above and return here when you're done.
Backing Your Files Up:
Time required:
15-25 minutes.
Making a Nandroid
The first thing you're going to want to do is back up your phone's entire system. This is done by making a "nandroid."
To do this, boot into ClockworkMod Recovery. To accomplish this: Turn your phone off. Once it is completely off: hold both volume buttons and the power button until the Android with his chest exposed is displayed. Navigate to the "Recovery Mode" option and select "backup."
This will take some time. Be patient and let it finish. This process is important! You should always have a recent nandroid available on your device.
Backing Your Data Up
Install Titanium Backup from the market.
Open Titanium Backup. A Superuser request should pop up. Allow it. Note: if Titanium Backup then says it failed to obtain root access; press the menu button and select more>reload application.
Press menu>batch. Select "Backup all User Apps." Select all and "Run the Batch Operation."
Let the process complete. This may take quite some time: depending on how many applications you have installed.
You can now backup your Text Messages, Bookmarks, and WiFi addresses with Titanium Backup as well.
Press Menu>Backup Data To XML to do so.
Backing Your Contacts Up
Note: This process may or not be useful to you. The Google servers should automatically import any contacts you have stored back whenever you install a new rom. Also note that Facebook/Google+/etc contacts will need to be synced again through their respective applications.
Open the Contacts application.
Press the Menu button.
Select import/export.
Export to storage.
Installing A Rom (Or Kernel/Radios/Tweaks/Themes/etc.)
Time Required:
5-10 minutes.
Note:
Follow the guide above about backing your phone up before attempting!
This guide will also work for flashing kernels/radios/themes/tweaks/etc. Simply ignore the part about wiping data and wipe whatever the thread says you should. You only need to restore data after a rom install.
Find a Rom You'd Like To Try:
Nexus 4 Original Development
Nexus 4 Development
Download the rom you'd like to try on your device.
Most roms also require you to install "gapps" as well.
You can find the correct ones for the rom you're using in the rom thread.
Make sure the Rom and Gapps are on your SD card.
Now, open Google Wallet (if you have it installed) and press Options>Settings>Reset Google Wallet. This will prevent the "Secure Element" errors some users have experienced.
Boot into ClockworkMod Recovery by turning your device completely off. Hold volume up, volume down, and power until the green Android with the open chest is displayed. Navigate to "Recovery Mode" with the volume buttons and select using the power button.
Remember to have a recent nandroid before continuing!
Navigate to "wipe data/factory reset" and select it. Select "yes."
Wait for the process to complete. This may take some time. Be patient!
Once complete: Navigate to "Install Zip from SD card" and "Choose zip from SD card."
Find the rom's .zip and install it. Once that completes install any applicable gapps' .zip.
Select the "Reboot" option.
Congratulations! Your phone should now boot into the custom rom!
Follow the prompts to re-activate your phone.
Restoring Your Applications / Contacts / Nandroid
Time Required:
5-15 minutes.
Restoring Your Applicaions
Install Titanium Backup. Note: you may want the pro key. If you have it, you won't have to manually click "install" on each application. The process is completely automated. Open Titanium Backup (grant root access. If titanium says it failed to obtain root access, press menu>more>reload application). Press menu>batch>restore missing apps with data. Now, here you have a choice to make. Do you want a completely clean install? Select "app only" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). Do you want all of your application data (saved games/settings/etc)? Select "app+data" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). This MAY cause you problems or it may not. Personally, I often restore application data and seldom run into any trouble. If you do find that restoring data caused problems, follow the guide above to re-install your rom and restore without data. This process will take some time. Be patient (I'd suggest turning your screen off so the screen doesn't burn, but that's just me.) It will vibrate upon completion.
You can now restore your Text Messages, Bookmarks, and WiFi addresses if you backed them up by pressing Menu>Restore Data From XML.
Note:
Overclocking/CPU tweaking applications should never be restored with data. Simply deselect it from the list.
Facebook/Haxsync/Google+ may have problems restoring your contacts when installed through Titanium Backup. Simply uninstall and reinstall through the market (and be sure to log in and select to sync your contacts again).
Also, if you have NFC Task Launcher successfully launching Tasker tasks with your stickers: they may not immediately work.
Through my testing, it's as simple to fix as uninstalling NFC Task Launcher and Tasker. Restore Tasker first. Then restore NFC task launcher.
Restoring Your Contacts
If google fails to restore your contacts (not facebook/haxsync/google+/etc) you may import them manually if you backed them up.
Open the contacts application and press menu>import/export>import from storage.
Restoring A Nandroid
If your phone is acting funny or won't boot...restore a nandroid from a previous rom or working set-up.
You may also use a Nandroid to switch back to a previous rom if you decide you don't like the one you're on.
Do this by booting into ClockworkMod Recovery (hold volume up, volume down, and power while your phone is off and navigate to "Recovery Mode").
Simply select "restore" and find the most recent (or relevant) backup.
This process will take some time. Be patient and let it complete! Once done, select "Reboot."
Note:
Nandroids are stored in the "clockworkmod" folder on your SD card. They take up quite a bit of space. ALWAYS have at least one recent one on your SD card. However, since these are huge files: you may like to delete old ones to save space. You must delete backups by booting into CWM and navigating to Backup and Restore>Delete.
Important Notes About Restoration
I outline the method of using Titanium Backup above for a reason. Restoring system applications and data is the most common cause of problems on custom roms. For this reason, always ONLY restore "missing applications" from "user applications" that were backed up when restoring onto a new rom. Every time you restore system data or applications a narwhal sodomizes your favorite childhood cartoon. This is FACT.
Installing Alternate Custom Recoveries
If you find a custom recovery (such as the touch-recovery options) that came as a .img file:
Use these instructions to flash. Plug your phone into the computer. Open up ADB. Move the .img to the C:\android-sdk-windows\platform-tools folder.
Type the following:
Code:
adb reboot bootloader
(Hit Enter)
You can also manually boot to the bootloader by powering off and holding volume down, volume up, power buttons until the green Android with his chest exposed is displayed.
Then type:
Code:
fastboot flash recovery FILENAME.img
(Replace the file name with whatever the .img is called and Hit Enter).
Wait for the process to complete and reboot.
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu). Navigate to recovery and select it with the power button.
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Code:
adb push NAMEOFZIP.zip /sdcard/NAMEOFZIP.zip
(Hit enter)
You may have to reboot recovery to get the file to show up. Now follow the guide above for flashing a rom to get you booting again.
Did you install a tweak that modified only a file or two on your phone? (Find this out by opening the .zip and looking in the folders (ignore META-INF). Good news! We MAY be able to recover you completely. If this doesn't work...you'll have to follow another method.
Get your phone into fastboot (the boot-menu that allows you to select recovery/reboot/etc). Navigate to Recovery. Start up ADB. Pull the files that were modified out of the stock rom's .zip (using whatever tweak you were installing as reference to find what was changed) that you're on into the C:\android-sdk-windows\platform-tools folder. Now we're going to push these files onto your phone...replacing the tweaked ones and hopefully getting you booted again. Use this code, but change the values of the file name and where it should reside. This is only an example!
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
This will mount your system so you can write to it.
Code:
exit
(Hit Enter)
This should exit shell and allow the use of adb commands again. You may need to type it a couple of times (until the #_ changes back to the platform_tools> prompt).
Code:
adb push framework-res.apk /system/framework/framework-res.apk
(Press enter after each file that you need to replace).
Note: This last option probably won't work. I'd just skip over it unless you're absolutely adamant about restoring your current setup and want to try everything possible.
Q: I want my SDcard files from my phone...but I'm in a situation where I need to flash stock images! This will erase my SD content. What can I do to save it?
A: Do you have a custom recovery installed? If not, download a custom recovery from post one in this guide and flash it using those instructions. You'll need to be in a custom recovery in order to obtain ADB access without booting your phone. Boot into recovery (With phone turned off: hold Power and Volume+ and Volume- until the bootloader pops up and navigate to "Recovery"). Run the command:
Code:
adb pull /sdcard/ /SDCARD/
(Hit Enter)
This will put all of your files into a folder called "SDCARD" in your C:\ drive. Keep in mind that this will take a LONG time. Maybe a couple of hours.
To restore once you're booting again:
Move the "SDCARD" folder you created from your C:\ drive to the platform-tools folder. *Then input:
Code:
adb push SDCARD /sdcard/
(Hit Enter)
Q: How do I make an "ADB Backup?"
A: An ADB Backup will backup your phones data (applications and their settings). Follow the guide HERE about ADB Backups.
Q: My phone gets really sluggish and often turns off or reboots on its own.
A: Without knowing anything about your situation...I'd say you either have severely bad data somewhere or some bad kernel tweaks. Use the rom install guide above, paying close attention to the part about backing up and restoring if you haven't already. In the case of a kernel problem, you're likely undervolting too low. Restore the stock kernel values and see if your problems subside.
Q: My phone screen won't turn on! This requires a battery pull to fix.
A: This is called a "Black Screen of Death" or BSOD. This is generally due to using a hotplug governor (one that turns cores off with the screen off) or possibly undervolting your device too low. Change governors or up your slots a bit.
Q: My phone is doing really weird things. Regardless of kernel/rom and even if I don't restore any data at all! Either that or I simply cannot boot up! My phone is possessed no matter what I do!
Download the stock IMAGES for your device and extract the files using 7-zip. Move all of the extracted files to your platform-tools folder. Open the flash-all.sh file with a text editor. Copy and paste the commands (one by one) and wait for each process to complete for continuing.
FAQ
Roms/Kernels
Q: What is the best rom?
A: The "best" rom is a matter of opinion. Do you like a certain customization and can't live without it? Use a rom that has that option.
Q: What is the best rom for battery life?
A: Roms themselves really shouldn't impact your battery all that much. They can have an impact, but if you're really looking for better battery I'd suggest swapping kernels or tweaking yours.
Q: What is the best rom for stability?
A: All of the roms out are "stable." They may have options that don't work correctly, but generally: this is user error. If you follow my advice on installing a rom, you'll end up with MUCH fewer bugs.
Q: What is the best kernel?
A: The best kernel is a matter of opinion. Some users may love one, while others swear by another. Find one you like and tweak it accordingly.
Q: How do I tweak a kernel for better battery?
A: Generally, you'll want to either change your governor and or undervolt and or underclock your kernel. This is done either by using SetCPU or similar apps, or with an option in your rom (usually labeled "performance" or something similar). Take note: extremely high/low voltages may cause instability. Never "set at boot" until you've thoroughly tested the options you've set. Testing includes low strain (like turning your screen off for an hour) and high strain (like playing a game for an hour) scenarios. To be extra safe: run the values for a couple days before setting them at boot. Follow the users ideas in the kernel's threads for some guidelines. However, remember that not all values will play nicely with all phones.
Miscellaneous
Q: Why isn't Google Wallet working at [store]?
A: I'm not sure if it's a Google Wallet problem, or a problem with the terminal. But I personally struggle to find a terminal that consistently works in my area. Something that has generally worked for me is to open wallet and go to Options>Reset Google Wallet. You must then re-add any cards you had.
Q: Does my ass look good in these shorts?
A: Yes.
Neat Ideas / How to Show Off the Nexus 4
-Get some NFC stickers. Tagstand has them available.
You can use these to make your phone perform certain tasks when you touch the sticker. Use NFC Task Launcher to define the tasks. These are capable of doing simple things like muting your volume to the more complex like turning on Tasker tasks that do things like auto-reply to text messages while you're at work.
-Do you have any suggestions? Submit them below!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
ADB Backups:
SDcard backup:
Code:
adb pull /sdcard/ /sdcard/
(This will pull all of your sdcard contents to an "sdcard" folder in your C:\ directory)
Applications and their data:
Take note, that you'll need to be using CyanogenMod's method for setting up ADB to do this. The ADB AIO application installs an older SDK without this functionality. First, get your drivers installed (detailed in post one). Once you get ADB installed (post one), navigate to the C:\android-sdk-windows\platform-tools folder on your computer. Hold shift and right click. Select "Open Command Window Here."
Input this while your phone is turned on and USB Debugging is Enabled:
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Type this:
Code:
adb backup -apk -noshared -all -nosystem
(Hit Enter)
Your phone will ask for a password. Input one and remember it.
Once the process completes: continue with unlocking and rooting your phone.
Restoration:
Upon unlocking and rooting your phone: open up ADB again.
Enter this code:
Code:
adb restore backup.ab
(Hit Enter)
Input the password you saved to this file earlier, and wait for the restore to complete.
To restore your SDcard backup, first move the "sdcard" folder that was made in the backup process to your platform-tools folder.
Then run:
Code:
adb push sdcard /sdcard/
Do you have to install "ADB" ?
As far as like...clicking it and letting the windows installer install...no.
The exe file will read the commands in cmd without "installation."
Nice Work!
I've just added this guide to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Great work!!! nice and clean reading!
Can this guide include information on how to re-lock bootloader and unroot the device? Does this informaiton exist?
I need to RMA my phone due to dead pixels and I want to make sure I dont have any issues with the warranty.
jayluke said:
Can this guide include information on how to re-lock bootloader and unroot the device? Does this informaiton exist?
I need to RMA my phone due to dead pixels and I want to make sure I dont have any issues with the warranty.
Click to expand...
Click to collapse
Post 3.
fastboot oem lock
Locks the device.
How long is the first boot, after unlocking the bootloader, supposed to take? Mine's sitting there for quite a while already. (I had a lot of stuff installed, but still, this is really long.)
EDIT: When rebooting the custom recovery, you have to say "yes" to the message it gives you, something about keeping some recovery. I had originally said no because I didn't flash it, I just booted it once.
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
Edit: Got an app to enable it... still not in the menu though.
wizshaw said:
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
Edit: Got an app to enable it... still not in the menu though.
Click to expand...
Click to collapse
Oh geeze!
I forgot.
Settings>about>version number I think...
Click 7 times to enable developer options.
Will update op soon.
Quick question: is there a reason the first post links to SuperSU version 0.98, when version 0.99 is the most recent? If version 0.99 has known issues with the Nexus 4, I don't want to use it on my device.
The 0.99 version came out after this guide was posted. I was offered to upgrade to the new version of supersu from 0.98 and so far no problem at all.
Does this work on the latest version of JB (4.2.1)?
When installing a new ROM it says to perform a factory reset through CWM, which will remove all apps and data but should keep all your pictures, videos, songs etc.
It doesn't mention to wipe the System partition as well. Is this not necessary when flashing ROMs on a Nexus?
Prior to owning the N4 I had the Galaxy S 2 and it was always stated in the OP instructions to wipe data/factory reset, wipe system, clear cache, clear dalvik and then flash ROM and Gapps.
However, I don't notice in any guides or instructions for N4 ROMS to wipe the system partition, just the data partition. Is there a reason for this or is it not necessary to wipe the system partition? Thanks. Great guide by the way.
Peace
thank u for ur effort
Chochiwpg said:
When installing a new ROM it says to perform a factory reset through CWM, which will remove all apps and data but should keep all your pictures, videos, songs etc.
It doesn't mention to wipe the System partition as well. Is this not necessary when flashing ROMs on a Nexus?
Prior to owning the N4 I had the Galaxy S 2 and it was always stated in the OP instructions to wipe data/factory reset, wipe system, clear cache, clear dalvik and then flash ROM and Gapps.
However, I don't notice in any guides or instructions for N4 ROMS to wipe the system partition, just the data partition. Is there a reason for this or is it not necessary to wipe the system partition? Thanks. Great guide by the way.
Peace
Click to expand...
Click to collapse
I actually have a question along these lines.
I just came from a LG G2X so things were different for me whenever I flashed ROM's/kernels. For one thing, I had an external sd card so whenever CWM made it's backups, they went to that automatically and I didn't have to worry about wiping since everything was on the external. This phone doesn't have an external so where do the backups go? From the looks of the new CWM 6.0.2.0, the backups (and blobs now apparently) go to /data/media/clockworkmod. Well I guess my question here is if you have to wipe /data for installing new ROM's, how would I restore a backup because they would have been deleted off the /data partition. I tried adb pulling /data/media/clockworkmod to my computer but it won't go. Don't know if it's because that partition is mounted while the phone is in use or what. I tried the mount/umount command that OP listed but it won't work for me. Don't want to flash ANYTHING on this phone until I know for a fact I can get to the backups that I'm creating.

[GUIDE] Rooting G1, ADB/Fastboot Setup, Partitioning, etc.

This guide is compiled of various guides and threads that I've read and I want
to sum it all up in one post so you can root your HTC Dream (G1)
*many if not all rooting guides are incomplete or missing download links – I will do my best to keep links
posted and alive!
!!READ AND FOLLOW DIRECTIONS!! DO AT OWN RISK. I AM NOT RESPONSIBLE
FOR BRICKING YOUR PHONE.
I've compiled all of the files necessary and uploaded them to my drop
box
INDEX:​
-|1|: Setting up adb and fastboot
-|2|: Rooting
-|3|: Changing hboot versions
-|4|: No recovery?
-|5|: Un-Root
*This guide assumes you are using Windows but Linux and iOS will be able to use most of it.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
First off thanks to Demkantor since he was my sensai in a way (wax on wax off style)
Then thanks to HTCDreamOn, EzTerry, Cyanogenmod and all the developers out there that make all of this possible!
This is the optional ADB and Driver setup. I recommend you follow it through as it would make things easier in the future. This is more a reference post.
---------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------
1: ADB and Fastboot setup with HTC Drivers
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------
In order to do certain things that pertain of flashing radios and hboots you are going to need ADB and
fastboot. This is also useful for The Google Bypass if you dont have data or an activated sim card.
Go ahead and download this zip
Extract the zip file straight to your local disk. (You should get something like this
afterwards "X:\Android" x being the letter of your local disk)
Now that you have that on your local disk. Go to X:\Android and install HTCDriver3.0.0.007.exe. (This
has most if not all HTC USB drivers)
Finally add a path in order to access ADB and Fastboot from cmd on the computer.
Click on the Start button and right click "My Computer" and choose
"Properties".
Now you should be in "System Properties" under the
"General" tab, go to the "Advanced" tab and click
"Environment Variables".
Now you'll be in "Environment Variables", Now under the
"System Variables" scroll down to "Path" and highlight
it by clicking on it and now click "edit".
IMPORTANT be sure to not delete ANY of the
variable values already in the "Variable Value" section. Now that that is
clear, go ahead and ADD this to the "Variable Value"
section: ";X:\Android" (Obviously replace X with your appropriate local disk letter and without
quotations)
You now have setup ADB and Fastboot.
But in order to use ADB and Fastboot you must go back to "Start" click or search
for run, type in cmd and you will now have command prompt open.
NOTE: I will not post what the command are since all you have to do is type in "adb" or "fastboot" in the command prompt and it will show you the sub
commands for each perspective command.
---------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------
2: Rooting
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------
-----------------
Step 1
-----------------
Assuming you're not on stock Android 1.0 follow steps 1-6, if already on android 1.0 skip to step 7 (1 when item is hidden).
This link is for RC29 (US)
*Optional is the update.zip as it seems to not work for some other wise you can skip the update.zip flash*
But if you need RC7 (UK) then use this link
Now plug in your phone and go to USB-MS. Go ahead and right click your USB-MS drive that appears
on your computer and hit "Format..". Now under file system be sure to set it
as FAT32 then hit format. Depending on how much memory your SD card is will
effect how long it will take. Once it is done move the DREAIM.NBH and update.zip into the
root of the SD card.
*only do this step if you got the update.zip file otherwise skip this step* Now power down your phone and boot up into Recovery mode (Home+Power).
You'll see an exclamation point with a triangle if you booted correctly. At this point
press "ALT+L" then you want to wipe all data so press
"ALT+W" then press "ALT+S" to
apply the update from the SD card.
Power down your device and boot it back up into fastboot mode (Camera+Power). It'll prompt you
if you'd like to install update hit prompted button and wait, this may take a bit and it won't be done
untill it prompts you that it is done so do not worry if it seems like its taking long and DO
NOT battery pull while it is installing.
Power down and now boot normally. You now have android 1.0 stock.
Sign-in into google.
GOOGLE BYPASS METHOD : only necessary if you do not
have data or an activated sim card or no sim card at all. But Wifi is required.
("<enter>" is actually the actual enter button so when it says "<enter>" press the enter button AKA return button)
Power on your phone but do not press anything. Plug your phone in via USB.
Slide your keyboard up type this is: "<enter>setprop persist.service.adb.enable 1<enter>". (Since you are on 1.0 this actually a command to enable USB Debugging although
you can't see anything)
Your pc will detect another device and begin installing drivers. (This is what HTC drivers installer was
for so your device will be installed correctly)
Now open cmd via run on your computer. Type in "adb devices" and it should show your device.
Example :
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT844GZ64748 device
C:\Documents and Settings\Owner>adb devices
List of devices attached
HT844GZ64748 device
C:\Documents and Settings\Owner>
Click to expand...
Click to collapse
(You only see this: "adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *" when its the first adb command your run when you open cmd)
type: telnetd<enter>
now on the computer using the command prompt type: adb forward tcp:23 tcp:23
then press enter
type: telnet localhost
press enter and you should see a # as you should have a root shell (while in this shell in order to backspace you must press the "Delete" button on your keyboard as pressing backspace will not do anything)
type: setprop app.setupwizard.disable 1
press enter
type: ps
press enter, this will show all the running processes
on the right column look for "com.android.setupwizard" then once that is located follow that line on to the second column from the left, the number in that column is the PID
type: kill PID
replace PID with the number that you found from the second column
It should now be at the home screen, if not press the "Emergency Call" button and press back and then you should be able to unlock the phone with the "Menu" button.
Now you can go to the settings connect with wifi and then bring down the notification that says you need to set up your account to sign in with your google email
Go to the market and download "TelNet" app. Once you have
it installed, go to USB-MS and put this recovery image onto the root of your SD card. reboot your device but do not press
anything or unlock the screen.
Once booted up slide your keyboard up, will unlock the device, and press the enter button twice and
type this in "telnetd" then hit enter (It’ll be a contact search but it’s okay). Now
go open Telnet app, and hit connect. If you did the telnetd part correctly you
will be prompted with a #. Otherwise you'll get a connection failed message, if
so reboot device and attempt the telnetd command again.
Type these commands in on your phone:
Press enter after each line
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
You now successfully flashed Amon_RA_ Recovery. :good:
You may reboot into your new recovery (power on holding home button) and flash a custom ROM. But
I do suggest upgrading your bootloader and radio first as the amount of ROMs available to you will be
much greater!
-----------------
Step 2
-----------------
Okay so now we will be updating to radio2.22.23.02 and DangerSPL.
Reboot into recovery mode (POWER+HOME), plug your phone in via USB and toggle USB-ms and delete everything off your SD card and placethese files onto the root of your SD card. Exit USB toggle.
Scroll down to wipe data and do so.. than go to "flash .zip file" now the first file you want to flash is the radio2.22.23.02 let finish then press home+back to apply update, it should reboot back to recovery after this.
Now go to wipe again and do so.. the next file you want to flash is the G1 Spl (Hard SPL) so flash the .zip file and let finish than press home+back to apply update.
Go to wipe data 1 more time. now go to flash zip and select the "Danger SPL.zip" let finish and press home+back to apply update.
Power back on into bootloader (camera+power) and check if device says.
Dream PVT 32b ENG S-off
HBOOT 1.33.2005 (drea10000)
CPLD-4
RADIO 2.22.23.02
APR 20, 2009, 15:30:43
Click to expand...
Click to collapse
If so you can move on to the next part!
-----------------------------------------*
Step 3
-----------------------------------------
Again delete the old files off your sd card and place these files on it!!
Quick note this is the last radio update for this section, radio2.22.27.08, now if you want radio update 2.22.28.25 refer to the changing hboot section and it will have the steps to do so.
Radio 2.22.28.25 may have better reception in your area but will drain your battery quicker.
Boot up into recovery mode, go to flash zip from sd and select Ohsaka superwipe. wait till finish then go to power down!! now boot back up into recovery again.
Now do a manual wipe of data and cache.
Now flash the radio2.22.27.08 file.. let finish than flash the hboot1.33.0013d file and let it finish! then reboot the device for update to apply.
Power off the device, then reboot into bootloader (camera+power) and check if device says.
Dream PVT 32b SHIP S-on
HBOOT 1.33.0013d (drea10000)
CPLD-4
RADIO 2.22.27.08
OCT 21,2009,22:33:27
Click to expand...
Click to collapse
*If so you now have updated both your radio and SPL and you can now flash any ROM you'd like.
But if you'd like you can follow the next step and install a custom ROM and I will show you how to partition your SD card as well.
-----------------------------------------*
Step 4
-----------------------------------------
Okay so now that you have completed step 3 you can flash a custom rom but now we must partition the SDcard.
Reboot into recovery mode and go to Partition SDcard
Partition SD. Press home.
Now I have 4GB micro SD hc. My partition settings are*
Swap: 128mb (swap is not needed and is purely optional)
Ext: 576mb ( or whichever option is closest to that I can't remember, this is for apps2ext so you can save your apps to your sd card)
Rest: FAT32 (this will once again delete everything but you should have all your backed up data on your pc)
This is what I have for my partitionings and it's works fine for me and it should for you too!
Once that is done go to SD:ext2 to ext3 and once that is done upgrade the ext3 to ext4. You now have a partitioned SD card with EXT4!!
Now all that is needed is to flash the custom ROM. I am currently running this ROM.
Now return to toggle USB-ms and place the ROM zip file from the link above as well with Ohsaka superwipe from the previous step (download it once again)
Go to flash zip file and flash Ohsaka superwipe.
Power down. Reboot into recovery.
Now return to flash zip file and flash the ROM which should be named FroyoCreamSandwhich. Once it is done it will prompt you to press HOME+BACK do so.
Now reboot your phone normally and allow it to boot up (it may take a bit the first time but this is normal when you flash a new ROM). You will now be given the option to sign in create an new account or skip (although I believe it has the option to connect to wifi built in). You now have flashed your New ROM!!!!
---------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------
3: Changing HBOOT version
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------
This option is for which ever reason you need the flash recovery/radio/etc you need the Engineer SPL. which is the SPL from step 2 in rooting. although since if you are already rooted and have the latest HBOOT then that route is not the way to go.
So in order to go back to that engineer SPL all you need to do is flash Engineering SPL zip in recovery.
Then you can proceed to update radio/ recovery etc and then flash back to the latest HBOOT which is 0013d so just download
Hboot0013dand flash it through fastboot with this command: fastboot flash hboot hboot.img
--------------------------------
No Recovery?
--------------------------------
Download: http://d-h.st/v9b2erpqfyd7/orange-1.58.73.2.nbh
Like always place the file in the same folder as the fast boot directory.
Enter fastboot and run "fastboot flash nbh orange-1.58.73.2.nbh"
Wait for it complete the flash
Boot into boot loader again and you will have an engineer SPL 1.42.2000
Now you can flash any hboot/recovery/radio via fastboot.
--------------------------------
Unroot
--------------------------------
ldrifta said:
---------------------------------------------------------------------------------------------------------------------------------------------
5~Un-Rooting
---------------------------------------------------------------------------------------------------------------------------------------------
Download these files...
DREAIMG.nbh
update.zip
Now would be a good time to un partition your sd card since there will no longer be a custom recovery..
1. first you take the "DREAIMG.nbh" file and the first "update.zip" file and place on root of sdcard!
2. start phone in recovery mode (home+power) do a quick wipe of everything! than flash the update.zip file.. wait for finish than reboot or power off.. whatever prompts tell you. than make sure device is powered off after finished installing!
3. power on via fastboot (camera+power) and wait for selection to pop up asking to install the update! press confirmation button to apply and let it work its magic!!
Now your phone will be on stock android 1.0 firmware! you have 2 options..
a. wait for automated updates.. could take up to 48 hrs..
b. flash updates to 1.5 and or 1.6 via stock recovery!
if you chose option b than you are smart! lol who wants to wait for updates for a G1 nowadays? lol
ok so now to apply updates via stock recovery you do what you would normally do.
Download these files...
Stock 1.5 (OTA)
Stock 1.6 (OTA)
(the stock 1.5 and 1.6 files are also "update.zip" so be sure not to mix them up and confuse the proccess!!)
1. Place files on root of sd.. DO NOT RENAME FILES, the stock recovery will only flash an "update.zip" so please dont make any changes to file.names...
2. boot into recovery mode (home+power) and wait for screen with yellow triangle and this thing ! now press alt+L together untill you see more words pop up on screen..
3. Now press alt+w to wipe the data on phone... (just do it dont ask why) lol after wipe is complete press alt+s to apply update! once it's finished reboot your device and you are ready to go!!
unfortunately the 1.6 i provided is not the DMD40, you still have to wait for that automatic update lol i have the 1.6 before the update... it is the official tmobile firmware its just not the latest.. never really bothered to search for latest one..
Click to expand...
Click to collapse
if any of those links are down post a reply and i will get a mirror up as soon as possible!
Hi mate, welcome to the G1 forums, good comprehensive guide, added to The G1 Oracle :good:
Thanks for this, watching for the rest with baited breath! You have written up the bit I have done but really cant seem to get through the next phase properly lol.
Your welcome guys. I ran up with some problems and my pc isn't available so ill try finishing this soon (probably in my iPod).
Okay yes this is perfect I can generate the links via the Dropbox app so hopefully this should be done soon!
Wow phew that took longer than expected (about 3 hours) safari is a horrible browser. Kept on crashing. Finally did all of it on notes and just pasted it on, revised and posted I hope this helps out! I will have the next steps up soon but for now you should be able to root your htc g1 with no problems what so ever have fun rooting guys. :laugh: I'm heading off to sleep. I'm exhausted. Later.:silly:
HTCDreamOn said:
Hi mate, welcome to the G1 forums, good comprehensive guide, added to The G1 Oracle :good:
Click to expand...
Click to collapse
Thanks!
I decided to finish up the rooting part since there was activity on the topic. Feel free to look over it just in case I may have missed something. I doubt it but hey we're not all perfect. Exhausted but pretty satisfied on how things are coming out. Mainly I'm happy to see that this is on the G1 oracle and that this this is recognized as a contribution to the g1 forums!
luggag3 said:
Thanks for this, watching for the rest with baited breath! You have written up the bit I have done but really cant seem to get through the next phase properly lol.
Click to expand...
Click to collapse
The rest is up for rooting! Have fun rooting!
Can anyone repost the file from part 1? It doesnt work...
Good work, thread stickied.
Thank you,
mf2112
XDA Moderator
duse1986 said:
Can anyone repost the file from part 1? It doesnt work...
Click to expand...
Click to collapse
Which one?
duse1986 said:
Can anyone repost the file from part 1? It doesnt work...
Click to expand...
Click to collapse
Sorry for the incovienience but since majority of this post was made on my iPod using notes since safari is higly unreliable with desktop version sites. This the format of notes is kept when copying to the post editor. Thus this is how the link was copied:
https://www.dropbox.com/s/y3slprukiqrt9nv/
EXAMPLE.DOC
Click to expand...
Click to collapse
Instead of like this:
https://www.dropbox.com/s/y3slprukiqrt9nv/EXAMPLE.DOC
Click to expand...
Click to collapse
Thus making it believe that there is a "RETURN" in the link giving you a 404 error. I fixed this along with some other 404 error links but it is all fixed. Either way next time there is a link that is not working quote it and I'll have it back up.
So I am no longer using my G1 but I will still finish this guide. I'm sorry for the wait guys.
Sent from my Nexus 4 using xda app-developers app
Nice guide.. you left 'adb shell' in the bypass google section
Thnxxx

Categories

Resources