Database Users

[Guide] Easiest way from root to stock :)

I have read many posts, and did many tries.........we all know that Froyo ver that is out, is not a official one. In order to get Official OTA update, our phones must be in complete factory stage. Unlocked boot-loader is not an issue. Trust me, i tried many different ways to "unroot" my N1. Following many "how to's" uproot your N, in order to get OTA (Froyo), all tries have failed. I was flashing original roms (ERD79), replaced recovery image, and then i GOT an OTA with 2.1-update1, no sweat! Then, when it tried to install, there was an error every time. I was able to install that (ER27) update manually, but it was NOT the thing i wanted to accomplish. I knew that i will be able to receive next OTA with ver 2.2 (Froyo), but i also knew that this update will NOT install either. The problem is a recovery image! After been running many different custom roms, i have decide to try again to go back to the state from the beginning, so i can be sure i can be able to install official Froyo, when it is out. I was afraid to do this, but i did it anyway.............and it was successful. I restored my Nexus to the original state (except boot-loader of course), and after i got back to ERD79, momentarily i got OTA with ver 2.1-1. But this time, it has installed with no problem!!! I am running it right now, waiting for next (2.2) OTA update.
Ok, here we go:
Just go there and grab Google OEM file (PASSIMG.zip). Put it on your SD card (root dir).
Then restart your phone into boot-loader (trackball+power button).
Once there, top power button again. It will look for passimg file as always. It will load the passimg file. Note the blue status bar at right-upper corner of your screen.
Then, it will check that file, and finally you will see "do you want to start update?"
Press Volume UP, for YES............and wait.
After phone reboots - you are done! Completely back to stock!
Then you can go to "menu-settings-about-system updates" and you should see that your phone is already downloading update 2.1-1.
That is it.
If for some reason you end up with android screen with triangle and exclamation mark, just press VOL up and Power, at the same time, you will get into recovery screen, and reboot your phone from there.
One more thing...........i did that in my own risk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, please do not blame me, if something would happen to you Nexus (phone just exploded, or something....
)

Wow..can't get any simpler than that..thx for this.

Thanks. Very simple.

this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?

This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
-------------------------------------
Sent via the XDA Tapatalk App

Wow... Much appreciated!

laughter95 said:
this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?
Click to expand...
Click to collapse
Nope. Even if you unroot your phone, your bootloader cannot be locked back again (if you unlocked it). Rooted or not, if your bootloader was unlocked, you always get that unlocked padlock image on your first screen when you turn on your phone. However, I read somewhere that someone has sent his phone back for warranty exchange, after he revert everything to factory stage (except bootloader of course) and they (HTC) accepted. I don’t know how that happened...maybe they (HTC) overlooked that first screen??

As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.

justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse
HA ha ha! You did NOT understand what i wrote! Read it again....and what if one does NOT have a Nan backup at all??
" You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. " <= that's total BS!!

Would this work on the AT&T N1?

RogerPodacter said:
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850

This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Th
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850
Click to expand...
Click to collapse
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.

RogerPodacter said:
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.
Click to expand...
Click to collapse
Yeah, it should be something like "HTP123990" which is your device number. Click once more and it'll show all the backups for that device.
Or just browse your SD card to the nandroid folder with a file manager like Linda:

wow thanks! it's so easy to use..and works!
i had so many problems with the froyo 2.2..though i really LOVE the speed and the new interface...but afterwards decided to switch back to 2.1 wait for official OTA...
thanks op!

shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.

http://forum.xda-developers.com/showthread.php?t=686593

Well coming from a rooted MoDaCo rom, I performed the steps and am now running the stock ROM and just been informed that there is an update available. Update is installing now and it works great.
Now I have my stock OS back while still rooted, and getting updates.
I just recently got my Nexus one a few days before Froyo hit. I've been sporting Froyo while traveling and getting barely any coverage. So this is a good test.
I'm on Fringe coverage now. With Froyo and its radio, I kept getting network disconnects. Flashing back to stock+update = 2/3 bars of EDGE.
Finally!

RogerPodacter said:
shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.
Click to expand...
Click to collapse
It's the fastest way to reload stock recovery/image/radio altogether.

Not true. I can confirm the method in this thread.
justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse

If i use mybackup pro to backup apps and data, how do I restore that stuff once I'm unrooted? Do you have to redownload mybackup pro? Sorry if this is obvious to some, I'm new to android and really want to be able to get the OTA update. Basically I'm wondering how the people that have used this method got all their info and apps back, Thanks.

Unroot...

im actually trying to unroot my phone. i rooted it using unrevoked and was wondering where i can find a manual on how to unroot. thanks

Though I have seen no manuals, there are plenty of tutorials, walk-throughs, wiki's, etc... Just a search box away.
*hint check the stickies as well

just did this the other day.
Am still new xda user so i cant post the links, but the general steps are to get the 'unrevoked s-on' tool from the unrevoked site & follow their steps to reflash to S=ON.
After your phone is s-on download htcsync from the HTC site and install that (for latest usb drivers). If need be uninstall old versions first.
after htc sync is installed grab the RRU version you want to flash back to and double click the exe. From there its idiot proof, click 'next' to continue.
I used RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe (md5: 26dcb19a186128e46f6d52a29cccd7cc) from the shipped-roms site
needless to say, once you unroot dont get the OTAs from sprint, youll get hosed trying to root again until 2.3.3 (hboot 2.16) method is released.

Flash this in your custom recovery. S-on.zip
Download this and rename it to PC36IMG.zip and then put it on the root of your SDCARD, boot into your bootloader and select yes to the update.
Didn't mean to interrupt anyone's helping but it's easier with links.

mattykinsx said:
Flash this in your custom recovery. S-on.zip
Download this and rename it to PC36IMG.zip and then put it on the root of your SDCARD, boot into your bootloader and select yes to the update.
Didn't mean to interrupt anyone's helping but it's easier with links.
Click to expand...
Click to collapse
you don't happen to have the newest RUU?

evolishesh said:
you don't happen to have the newest RUU?
Click to expand...
Click to collapse
Not released yet.
Easiest way is to run that RUU and update OTA.
Warning if you do update to 2.3.3, root has NOT been achieved so you'll be stuck there.

mattykinsx said:
Didn't mean to interrupt anyone's helping but it's easier with links.
Click to expand...
Click to collapse
No sweat. You linked him to exactly what he needs. Good man!

Worked great! Thanks guys!!
Sent from my PG86100 using XDA Premium App

Thanks matty

sling said:
Thanks matty
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

My power button is busted and need to take it to Sprint for repair. I used unrevoked to root and went into bootloader and see i have s-off, hboot 0.97 and radio 2.15.00.04.08. How am I able to get s-on if i cant flash the s-on tool due to my power button? Help is much needed, thanks.

Deadbolt said:
My power button is busted and need to take it to Sprint for repair. I used unrevoked to root and went into bootloader and see i have s-off, hboot 0.97 and radio 2.15.00.04.08. How am I able to get s-on if i cant flash the s-on tool due to my power button? Help is much needed, thanks.
Click to expand...
Click to collapse
Honestly, if you just run a RUU so that it looks stock they're not gonna notice.

mattykinsx said:
Honestly, if you just run a RUU so that it looks stock they're not gonna notice.
Click to expand...
Click to collapse
Which RUU do I run? And then how do I root it back when the power button is fixed?

Deadbolt said:
Which RUU do I run? And then how do I root it back when the power button is fixed?
Click to expand...
Click to collapse
Read the first post, part that's bolded for your s-on/power button issue:
http://forum.xda-developers.com/showthread.php?t=998372
Which RUU...well you can run the latest since you're returning it...
http://www.mediafire.com/file/bjxvu....651.1-4.24.651.1_release2dk2r14ngv5s3bvl.zip
Rename it PC36IMG.zip
When you get a replacement it will likely have 2.3.3 installed so you have to use the revolutionary way.
http://forum.xda-developers.com/showthread.php?t=1228566

mattykinsx said:
Read the first post, part that's bolded for your s-on/power button issue:
http://forum.xda-developers.com/showthread.php?t=998372
Click to expand...
Click to collapse
I looked at that thread but ROM manager won't work from what I gathered when i ran the app. I don't have clockworkmod recovery installed to flash it through ROM manager. I currently have Amon RA recovery.
mattykinsx said:
Which RUU...well you can run the latest since you're returning it...
http://www.mediafire.com/file/bjxvu....651.1-4.24.651.1_release2dk2r14ngv5s3bvl.zip
Rename it PC36IMG.zip
Click to expand...
Click to collapse
Most likely I won't be getting a replacement because the problem is repairable. I'd like an RUU that I can easily root after they repair the phone.

Deadbolt said:
I looked at that thread but ROM manager won't work from what I gathered when i ran the app. I don't have clockworkmod recovery installed to flash it through ROM manager. I currently have Amon RA recovery.
Click to expand...
Click to collapse
You can just change your recovery to clockworkmod via ROM Manager...
Deadbolt said:
Most likely I won't be getting a replacement because the problem is repairable. I'd like an RUU that I can easily root after they repair the phone.
Click to expand...
Click to collapse
No reason that you can't easily root the newest RUU.
Also, I had this same issue and they couldn't repair it. Had to replace the Evo.

mattykinsx said:
You can just change your recovery to clockworkmod via ROM Manager...
Most likely I won't be getting a replacement because the problem is repairable. I'd like an RUU that I can easily root after they repair the phone.
Click to expand...
Click to collapse
No reason that you can't easily root the newest RUU.
Also, I had this same issue and they couldn't repair it. Had to replace the Evo.[/QUOTE]
Lemme see if I can get ROM manager to flash the s-on tool...
I called the sprint repair store and they told me it was repairable and I wouldn't need a replacement but who knows if they were blowing smoke up my ass. I really don't want to pay a deductible...

Deadbolt said:
Lemme see if I can get ROM manager to flash the s-on tool...
I called the sprint repair store and they told me it was repairable and I wouldn't need a replacement but who knows if they were blowing smoke up my ass. I really don't want to pay a deductible...
Click to expand...
Click to collapse
It can be repairable.
It just depends on if it's the button itself or the board.
In my case it was the board and therefore was a defect.
As long as it's not due to physical/water damage they will replace it [if necessary] without a deductible.

mattykinsx said:
No reason that you can't easily root the newest RUU.
Also, I had this same issue and they couldn't repair it. Had to replace the Evo.
Click to expand...
Click to collapse
Currently trying to get ROM manager to flash the clockworkmod recovery...is there an RUU still available that allows me to flash to root with the capability of unrooting after I re-root my phone if needed? I've read revolutionary, you can't unroot.

Deadbolt said:
Currently trying to get ROM manager to flash the clockworkmod recovery...is there an RUU still available that allows me to flash to root with the capability of unrooting after I re-root my phone if needed? I've read revolutionary, you can't unroot.
Click to expand...
Click to collapse
I've read you can't get s-on but I saw a post in the thread in Q&A (asking how) with a response that might tell you how.
I'd give you the link but I'm in bed now.
I believe its still I page one on that sub.forum

[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions

[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions
This is a guide on how to go from Froyo to rooted Gingerbread. Also, I'm on AT&T. Others beware. I take no responsibility if you hard or soft brick your phone.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
I didn't actually discover or develop any of this, but I figured someone might like to have a comprehensive guide, instead of searching through 500 different threads like I did.​Known/potential issues:
- Fingerprint scanner not functional False alarm
- Avoid using RSDLite for *anything* if you installed the OTA 2.3.4 build
- Battery reading is sometimes inaccurate
- If you have a limited RAM issue, read here http://forum.xda-developers.com/showthread.php?t=1169409​Step 0 - BACK UP EVERYTHING. Use Titanium backup, or just copy everything off your phone, whatever. This will leave you with an unlocked, rooted, but otherwise stock Motorola phone. Once this is done, set your USB mode to "None"
Step 1 - Install moto drivers
For x64 windows, use these: http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
For x32, http://www.multiupload.com/QNFILE4F07 (I havent tested these, I run Win7 x64)
Step 2 - Unlock your bootloader Note: some have hard bricked using RSDLite to install 1.8.3 over 4.5.91. Read warning here: http://forum.xda-developers.com/showthread.php?t=1160408
Download latest moto-fastboot from here: http://forum.xda-developers.com/showthread.php?t=1138092 *the win32 version worked for me, and I run 64bit windows 7*
Follow instructions here: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Step 3 - Flash stock Gingerbread image (you can do this without restarting your phone from the unlock bootloader step)
Follow instructions here: http://forum.xda-developers.com/showthread.php?t=1163342
Step 4 - Flash CWM Recovery
Instructions here: http://forum.xda-developers.com/showthread.php?t=1138541
Step 5 - Install root
Instructions here: http://forum.xda-developers.com/showthread.php?t=1159572
Note: I used my phone's USB Mass Storage mode to put the .zip on my external SD card. To get to recovery mode, shut down the phone. Then hold the power and volume up buttons until you see "fastboot." Use the volume down key to cycle through until you see "Android Recovery" then press volume up again. This will get you into the CWM environment, where you can navigate the menus to install the root .zip.
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.​
Feel free to make any corrections, or ask questions. Hopefully someone finds this useful. All credit to the OP of each thread I linked to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nice for you to localize everything, ATT users will be grateful.

I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
Click to expand...
Click to collapse
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.

From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.

humjaba said:
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
Click to expand...
Click to collapse
I didn't either. I downloaded a .zip and installed via stock recovery from a thread in the General Atrix forum.

Deggy said:
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
Click to expand...
Click to collapse
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.

Magnetox said:
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Click to expand...
Click to collapse
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?

Deggy said:
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Click to expand...
Click to collapse
What firmware did you flash? Can you link me to the thread you downloaded from?

Magnetox said:
What firmware did you flash? Can you link me to the thread you downloaded from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1159604

Deggy said:
http://forum.xda-developers.com/showthread.php?t=1159604
Click to expand...
Click to collapse
Ah you have the deadly firmware
You simply cannot use RSD to flash down to 1.83 or 1.26 etc.
Or you will brick.
Clarify in Q&A, make your own thread with your question.
Taken from this thread kennethpenn said:
"What if I already flashed the official 4.5.91?
If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though."
So it looks like you can flash 2.3.4 builds via CWM. But double check by asking in Q&A.

Check out this thread.
http://forum.xda-developers.com/showthread.php?t=1163009
Fruit cakes basically dont touch your bootloader, they're basically modified sbf files that only contain the needed files to flash stuff. There's a 1.8.3 fruitcake in there as well as a 2.3.4 fruitcake.
An HKTW fruitcake is in development.
Fruitcake is the .sbf equivalent file that is flashable via CWM.

The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer

theres the moto-fastboot file i was looking for!
much appreciated.

Now there's a guide
I just did this like 3 hours before this guide came out. Though it at least seems like I was going to all the right threads that are in this guide anyways.

humjaba said:
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
Click to expand...
Click to collapse
From my understanding, if you flashed the official firmware of death you CANNOT use RSD in any way. All of your flashing has to be done via CWM and fruitcakes. Full .sbfs will brick your phone. Hard brick. As in #@$% ME hard brick.

humjaba said:
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Click to expand...
Click to collapse
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.

So I guess no sweet Roms for me. Still haven't found a good thread to root my phone. I'm not sure if the FOD would mess with the rooting part of it.

SoberGuy said:
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
Click to expand...
Click to collapse
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.

humjaba said:
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
Click to expand...
Click to collapse
Perhaps it was settings then and not apps. Appreciate the information. I'll be doing that tonight

after i unlocked the bootloader
i flashed CWM
then i use CWM to flash 2.3.4 GB beta 4 zip from kenn
i like it better my way

[GUIDE]How to Root & unROOT Revolutionary PLUS 2.3.5/4.67.651.3 BL 2.18.0001

Disclaimer: Not responsible for anything that may happen to your device!
Updated with Stock 5.07.651.1 rooted and odexed ROM : I had flashed this update on the 4.67.651.3 with no problems and just need to full wipe data/cache/dalvich and make sure to back up everything, this will erase all the System data and SD card would be fine.
UPDATED Video GUIDES ROOT and UNLOCK Bootloader 2.18 and Build 4.67.651.3.
UNLOCK 2.18.0001
ROOT 4.67.651.0001
To save me the trouble typing out a written GUIDE for the 2 Videos on top, it has been done already, And Please THANK "THC Butterz" for the awesome GUIDE HERE!
******************************************************************************
Guide Below for v2.3.3 builds 4.24/4.53/4.54 softwares to ROOT and unROOT revolutionary method.
We must first gather the tools needed for the process, written and visual step by step below, I am simply not saying “This works better than other methods” but am saying it worked for me and able to replace my usb port on my device at the “S” store. Make sure the sd card is not inside when you take it in?
Now assuming that your rooted with the latest from “UnRevoked & AlphaRev” with a custom ROM installed on your device, in this case I was currently on “NewToRoot” 2.3.5/3.5 with a custom Kernel. The two zip files below Download and place them on the Root of the SD card, steps below is simply renaming the first one that will be used for removing the “Root.” You can rename them on the computer and place it on the SD or on the device itself, which ever you prefer but cannot have the same file name. Since I am removing UnRevoke & AlphaRev Root, I used the Number one first..
Files and there functions.
1. HEX file: This will remove you Root access and Returns Security on (S-ON).
2. PC36IMG_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15.00.0808 just rename this and flash it from HBOOT by Holding Vol+PWR button will take you there but shutdown completely or remove battery to be sure.
*How to Unroot your Evo 4G*[/SIZE][/U]
1. Renamed the “HEX” file to “PC36IMG” and placed inside the ROOT of the SD Card, disable FastBoot my case newer rom’s are located inside settings>power>fastboot and stock would be in settings>application>fastboot and uncheck it to disable. Complete Shutdown.
2. Boot to HBoot Screen by Holding “Volume down & Power Button” same time until you get to the white screen with your device info and “Revolutionary” ontop.
3. After system scanning, It will ask “Parsing?” select “Yes” by using volume up key.
4. Done!
What just happened? “Unrevoked & AlphaRev” root is now removed, Boot Loader remains the same with your Security now enabled “S-ON.”
Now there are a lot of way’s to proceed in loading the most updated version of the Stock Rom or RUU from “S”, but for now I will use what was documented(Documentation Beats Conversation). From removing the Root and putting Security On(S-ON).
Boot Loader Flashed and Return to Stock!
1. Reboot system and not forgetting that I am still on a Custom Rom, renamed PC36IMG back to Hex this would allow system not to keep reading it over and over.
2. With the number 2 file PC36IMG4.53.651.1 Simply rename it "PC36IMG" and flash from HBOOT screen by holding vol+power button will take you there,
3. FastBoot, you must have latest Drivers install get it from the "Rooting" guide below and install it on your machine, now put you deivce in HBscreen by holding "power" down and "volume" key down same time til' in a white screen, let sys scan read and when done use volume key scroll to "fastboot". It should highlight in Red at the top if connection is made Comp&Device, then load from your computer same thing as a step 2 above.
Now upon updating the system partitions, PC36IMG zipped with the latest “S” stock ROM or RUU is going to flash the Boot Loader as you will see in the video guides below, that would be the first step it’s going to take as you will see your device screen turn’s off for like a millisecond and comes back on(Flicker), when it returns as you will look to the top information your Boot Loader is now removed from 6.17.1002(mod) to stock 2.16.0001.
Only takes not even a 1 1/2mins and it will return to all the partitions and starts to update them one by one splash, boot, wimax etc;
RUU Link 4..54.651.1
Waiting on uploading The latest 4.67.651.3 I know a rooted version is somewhere on this forum
Screen Shots From Guide Part 3 of 3 **12:46 to 14:02**
Modify HBOOT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stock HBOOT
How can I confirm that this is the correct information? Well for one fact, it is the STOCK RUU from the Carrier themselves leaked onto the community, and how can we forget Teams “Unrevoke and AlphaRev” released Root method for Android Version 2.3.3.
I created a Tutorial on it and simply read through the process as I was recording, my device info before rooting is recorded and visiualy documented on video, just looked back at it and it read the same thing on this thread.
I even created 3 part Video GUIDE through this whole process, and show exactly what the step's above talks about.
Part 1 of 3
Part 2 of 3
Part 3 of 3
"READ READ READ!"
Steps to prepare device for the following installation below, enable usb debugging goto Settings>applications>development>debugging and select.
usb chord must be able to transfer data, it some cases you will loose this but still be able to charge. check connections usb>device and usb>computer.
Disable HTC Sync or exit out of it but make sure it's not showing on the task bar bottom right corner, and temporarily disable your virus software you may have. For at least 10mins, this method will only take like 5mins.
"PERFER" to use a notepad to COPY N PASTE your Beta key, to paste inside Command prompt(CMD or DOS), copy from notepad and on the black cmd/dos screen click on the "icon" top left corner, menu drops down, scroll down to edit and select paste!
Now let's ROOT your Evo!
Video using this method!
1. Download zip
http://revolutionary.io/ "
Donate to these guys who released it today"
"SETUP UP UR BETA-KEY AND SERIAL AS YOU WILL NEED IT IN THE INSTALLATION"
2. HTC Fast Boot Drivers
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
3. Installing "Super user" Flash from recovery, BOTH LINKS ARE FOR THE SAME FILE.
http://depositfiles.com/files/kfg1tupnx OR
http://depositfiles.com/files/5qasu3fyi
How to ROOT you Evo 4G
On to rooting your EVO!!!!!
1.ok so download the revoltionary file and extract it somewhere on your desktop.
2.run the executable revolutionary file.
3.it will detect your phone's specific serial number. use that to generate the beta key on the revolutionary website.
4.enter the beta key in the revolutionary dos window on your computer. people have been reporting that the key is invalid. so just copy and paste the key from the revolutionary website to the dos window.
5.it should then run and do its thing.
6.next we need to go and verify that s-off and if you have recovery
7.select bootloader then recovery
8.on the hboot screen at the top it should say s-off, if it does then congrats!
next we need to flash the superuser so
9.select recovery in bootloader
10.select install .zip from sdcard
11.find the superuser file and flash it
time to make a nandroid backup
11in recovery select backup and restore
12.select backup
13.after it is done you can reboot
CONGRATS YOU ARE NOW ROOTED!

You may want to run an RUU first, just so you have the stock, unrooted rom on your phone before you turn s-on. I know it's usually done the other way around, but I'm not sure of the hboot version you posted (I'm too lazy at the moment) and you'll want to avoid any "main version is older" errors when running an RUU.
Sent from my PC36100 using Tapatalk

Updated....

Tekn010933 said:
S-ON, pretty much all stock with the latest 4.53.651/2.3.3 with HB 6.17.0001 and ready to take it in for repairs....not really.
Click to expand...
Click to collapse
You need to run the RUU (or stock PC36IMG) to replace the modified HBOOT version with the "official" HBOOT version. THEN you will be completely stock, and ready for warranty returns. There is a newer RUU than the one you posted (4.67), posted by Football, and I have the PC36IMG extracted from that, which I will share once I'm at a computer.
Thanks for posting this; it's less work for me to do. However, it is common courtesy around here to give credit to the people that either created the files you're referring to, or generally helped out. While you're "not taking any credit", you're not giving any either, which is really like taking credit by omission. I'm just saying .... But I digress.
UPDATED ON 31-January-2012
EDIT
Newest stock RUU - 4.67.651.3 (thanks to Football): thread link
MD5: 045E93A459183B144D29F18FC2A332FA
PC36IMG.zip for latest ROM (4.67.651.3) - Rename to PC36IMG.zip, place on root of SD card, then flash from bootloader: 4shared Link
MD5: E6B8E2B01C18043790B8E66C91085733
EDIT 2: I also just noticed you have a multiupload link for the modded HBOOT file? The file is under 300KB - why not just attach it to the first post? For anyone interested in simply downloading the file (provided you're already a member here, and logged in), you can get it directly from HERE (zip I created) or HERE (zip posted by shortydoggg - not sure if it's mine or not). The file will just need to be renamed to PC36IMG.zip, and placed on root of SD card as described in OP, to flash via bootloader.

Awesome work, Captain_Throwback. This worked perfectly! Been helping a co-worker with a bad screen get ready to take his EVO in for service. He took the OTA to 2.3.3 in the past, so Revolutionary was the only way to get rooted. A slight moment of panic when I realized that the 6.16 HBOOT was supposedly not downgradeable. This method works a treat, and is very easy, reliable and fast.
I tracked this method down in one of the other threads it was posted in, but putting it in a sticky would be a great idea, or even better, the Revolutionary Guide OP.
Thanks again!
<edit> Just to clarify, the latest RUU from Football is just a radio update, and is still fully 'rootable' with Revolutionary, correct?

OwenW71 said:
Awesome work, Captain_Throwback. This worked perfectly! Been helping a co-worker with a bad screen get ready to take his EVO in for service. He took the OTA to 2.3.3 in the past, so Revolutionary was the only way to get rooted. A slight moment of panic when I realized that the 6.16 HBOOT was supposedly not downgradeable. This method works a treat, and is very easy, reliable and fast.
I tracked this method down in one of the other threads it was posted in, but putting it in a sticky would be a great idea, or even better, the Revolutionary Guide OP.
Thanks again!
<edit> Just to clarify, the latest RUU from Football is just a radio update, and is still fully 'rootable' with Revolutionary, correct?
Click to expand...
Click to collapse
You're welcome.
And no, the latest RUU from Football is the newest FULL ROM that includes the OTA updates AND the new radio. And yes, it's still fully rootable via Revolutionary, as the Bootloader version is still 2.16.

Updated....

Updated.....

My usb is broken and I'm sending the phone back, can't run the RUU, the link for the zip above is not working. Does anyone have the latest stock RUU zip they could post so I can unroot? I've searched around here quite a bit and cannot find it.
Thanks,

dbd1313 said:
My usb is broken and I'm sending the phone back, can't run the RUU, the link for the zip above is not working. Does anyone have the latest stock RUU zip they could post so I can unroot? I've searched around here quite a bit and cannot find it.
Thanks,
Click to expand...
Click to collapse
Try the link from my post now. I'm not sure how the link got broken.

Ok guys could you please clarify for us? What step should be done first, renaming the new HBoot zip to PC36IMG.zip and flash from HBoot? Or run the RUU (or flash the PC36IMG) of the latest stock ROM?

wherestheanykey said:
Ok guys could you please clarify for us? What step should be done first, renaming the new HBoot zip to PC36IMG.zip and flash from HBoot? Or run the RUU (or flash the PC36IMG) of the latest stock ROM?
Click to expand...
Click to collapse
Personally, the safest, most preferred order is flash stock ROM, then flash modded HBoot, then re-flash stock ROM.
"I hope you brought an umbrella, 'cause it's raining cold hard facts up in here."

Captain_Throwback said:
Personally, the safest, most preferred order is flash stock ROM, then flash modded HBoot, then re-flash stock ROM.
"I hope you brought an umbrella, 'cause it's raining cold hard facts up in here."
Click to expand...
Click to collapse
Ok thanks a lot.

Ok so before I found this thread I tried downloading the pc36img file and loading it in hboot but when I load the file I got a fail on the rom part of the update then I got a fail update notification so I tried to reboot the phone and now its stuck on the white screen that says "htc evo 4g" I tried the recovery and all I get is a phone with a exclamation mark...point being idk what to run first in my situation thanks for the help

Updated.....

erupt323 said:
Ok so before I found this thread I tried downloading the pc36img file and loading it in hboot but when I load the file I got a fail on the rom part of the update then I got a fail update notification so I tried to reboot the phone and now its stuck on the white screen that says "htc evo 4g" I tried the recovery and all I get is a phone with a exclamation mark...point being idk what to run first in my situation thanks for the help
Click to expand...
Click to collapse
You need to boot into HBOOT (bootloader) and report back what HBOOT version you're on, and the status of your NAND (S-OFF or S-ON). Then we can determine what you need to do next.

Updated ....

Tekn010933 said:
Not to get off track here but did Sprint release a new update? Haven't searched so busy with school/work sorry Bro.
Sent from my 3voED using xda premium
Click to expand...
Click to collapse
The latest update is from 8/23 - 4.53.651.1.
http://community.sprint.com/baw/com.../blog/2010/11/05/htc-evo-maintenance-releases

Captain_Throwback said:
You need to boot into HBOOT (bootloader) and report back what HBOOT version you're on, and the status of your NAND (S-OFF or S-ON). Then we can determine what you need to do next.
Click to expand...
Click to collapse
I'm S~Off and I'm on hboot 6.16

VZW 2.3.5 update borked my tab, can I ODIN/Heimdal over?

My wife carries the orginal G-Tab and we did the 2.3 update when it became available OTA. Ever since this, the thing is in a violent loop of force closing to the point that she can not really use it. The FC pop ups are out of control.
Verizon will replace the unit, but I thought that since it worked perfectly up until the 2.3.5 OTA, it has to be something that did not work according to the plan with the OTA.
We have done a factory wipe and that did not help anything.
I am set up with ODIN3 and Heimdal on this PC, so If there is a way to push back to 2.2 so that I can try the OTA again, or if I can push a clean non borked 2.3 in that would likely solve the issue and not force me to send it back for a refurb as we purchased this new and up until the OTA have had no issue.
Thank you.

Am I out of luck on getting a stock image to push?
Sent from my HTC Thunderbolt 4G using Tapatalk.

here ya go! no need to go back to 2.2!
http://forum.xda-developers.com/showthread.php?t=1362016&highlight=stock

Yoshi, thank you very much for that link, but may I ask if there is also a non rooted version for if I needed to send the unit back to Verizon for warranty exchange? I would fear that the mighty VZW might attempt to deny warranty coverage on the device because it is rooted... As has been suggested to me over the phone from the customer support rep.
Sent from my HTC Thunderbolt 4G using Tapatalk.

larry0071 said:
Yoshi, thank you very much for that link, but may I ask if there is also a non rooted version for if I needed to send the unit back to Verizon for warranty exchange? I would fear that the mighty VZW might attempt to deny warranty coverage on the device because it is rooted... As has been suggested to me over the phone from the customer support rep.
Sent from my HTC Thunderbolt 4G using Tapatalk.
Click to expand...
Click to collapse
I posted a link to a heimdall file from droidforums.net that worked for me - look in this general forum for "vzw update fix" topic
Sent from my SCH-I800 using XDA App

U can easily un root it with superoneclick
Sent from my SCH-I800 using XDA App

YoshiFan501 said:
U can easily un root it with superoneclick
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
I pushed the stock image with root, but with Superoneclick V 2.2, I go to debugging mode and open the program, i do nothing else but click on Unroot. It goes through steps 1-7, then says install busybox pushfile, then it goes to installing busybox changemode and just stops.
What am I missing?
HTC Thunderbolt 4G using Tapatalk.

Ok, shut down both the pc and the galaxy tab, restarted both and opened up Superoneclick, clicked Unroot and it stopped at the same place.
This where I get to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HTC Thunderbolt 4G using Tapatalk.

Honestly, just delete any root apparently like superuser titanium setcpu and the like if you need to return it. Think about it. These guys get HUNDREDS of rma devices a day. They aren't adbing or checking file systems for each one. They check it for water damage/physical damage then package and ship a refurbished model.
larry0071 said:
I pushed the stock image with root, but with Superoneclick V 2.2, I go to debugging mode and open the program, i do nothing else but click on Unroot. It goes through steps 1-7, then says install busybox pushfile, then it goes to installing busybox changemode and just stops.
What am I missing?
HTC Thunderbolt 4G using Tapatalk.
Click to expand...
Click to collapse
Sent from my LG-P999

Well, for warranty they now make you ship your defective unit in first and then they ship another unit out.
If they turn mine on, within 30 seconds they will see this, assuming they are even moderately intelligent.
I am worried that setting that in kernal will have them doing back flips and voiding the warranty.
HTC Thunderbolt 4G using Tapatalk.

And the update from 2.2 that it wants to install fails as expected because it sees that the thing is rooted. Not that the update is important, but it further indicates to them that I have issues related to a non stock system.

OK, this is what has me confused. I used the files from post #7 on this thread. I loaded in Heimdal, did it twice. Wiped before and after each time.
In his post #1 he talks about applying his update.zip, but that does not exist at his link any longer, nor does he repeat that step in post #7.
So downloading and running these files does throw me back to stock-ish 2.2, but the kernal shows rooted in the about device.
Superoneclick seems helpless for me. It goes so far and dies.
Getting frustrated!

larry0071 said:
OK, this is what has me confused. I used the files from post #7 on this thread. I loaded in Heimdal, did it twice. Wiped before and after each time.
In his post #1 he talks about applying his update.zip, but that does not exist at his link any longer, nor does he repeat that step in post #7.
So downloading and running these files does throw me back to stock-ish 2.2, but the kernal shows rooted in the about device.
Superoneclick seems helpless for me. It goes so far and dies.
Getting frustrated!
Click to expand...
Click to collapse
Use the instructions in this thread
http://www.droidforums.net/forum/sa...-how-flash-stock-rooted-ec02-froyo-2-2-a.html
This will bring you to stock version after dj11, and allow you to download and install verizon 2.3.5 official ota update - after flashing this version, go to settings, system updates, and you should be ready downloading update - follow on screen instructions and you will be good to go

Here is a set of heimdall files that will take you back to stock Verizon EC02 unrooted. Just unzip the file and put the appropriate files in each box. That means zimage in both kernel and recovery along with the other files in their boxes. I have used this many times and it definitely takes it back to stock.
Get the zip (EDIT: UPDATED LINK) here:

leapinlar said:
Here is a set of heimdall files that will take you back to stock Verizon EC02 unrooted. Just unzip the file and put the appropriate files in each box. That means zimage in both kernel and recovery along with the other files in their boxes. I have used this many times and it definitely takes it back to stock.
Get the zip (EDIT: UPDATED LINK) here:
Click to expand...
Click to collapse
That link goes to a DL page but I can not DL it. Can you drop box it for me?
I've downloaded 8 supposedly stock non-rooted VZW Glaxy Tab heimdal packages, and every one of them leaves me rooted with Kernal version 2.6.32.9 [email protected] #3. I really want rid of this so that I do not get burned when I send it in.
What I have tried so far today to get rid of root:
Real_Stock_for_galaxy_tab
Verizon-GTab-Stock-non-root
VZW.2.3.5.Stock.Root
I also tried SuperOneClickv2.2-ShortFuse, but this freezes on my tablet about 8 or 10 steps into the Unroot process.
Anyone know how to get my Kernal to show up as stock?

I went in to your DL link with Chrome and it worked. FOr some reason... IE did not play nice with that Megashares. I'll try yours and let you know what happens.
Larry

OK, the version you provided (SCH-I800_VZW_EC02.zip) does also still show the kernal as 2.6.32.9 [email protected] #3 and it also has SuperUser in the application lists.

So, I give up. I went back to one of the ROMs that has the kernal still listed as rooted but does not have SU installed or anything that is obviously indicating root.
I will send it in, and cross my fingers. Lets hope the guys getting in warranty exchange hardware do not take the time to really look, or I am screwed, blued, and tatooed.

I see no signs of rooting on that page. Or do you mean the [email protected] part? That's normal, and shows on an unrooted device as well! I don't have a VZW (mine's a European GSM), but my Tab is 100% original and unrooted, and it shows Kernel version 2.6.35.7 [email protected] #2. For an ordinary user it's actually not that simple to see if a Tab is rooted. One sign that may show is the presence of the app SuperUser. If you've rooted your Tab with SuperOneClick, it will be present as a system application which you can't remove by ordinary means. You can tell if a ROM is UNrooted by installing an app that needs root and running it, it will complain it needs root.
So the unrooted ROM's you tried may well actually have been unrooted if all you checked is the root part in the Kernel Version!