Database Users

The ultimate "get back to stock" thread.

I've seen a few threads out there that have instructions on how to get back to stock. Well, they're either incomplete, or not very easy/quick. So I'm going to make this thread with the different "stocks" you can go to.
Part 1: rooted/s-off -> 2.1 stock for OTA upgrade
Part 2: rooted/s-off -> 2.2 stock using the OTA RUU
Part 0:
1. Make sure you have ADB working, there are many tutorials around XDA/the internet on how to get it working on your computer.
2. After you've setup ADB, download the fastboot binary and put it in the tools folder with the adb binary, so that you can run the "fastboot" command.
Part 1: 2.1 stock for OTA upgrade
1. Make sure you're rooted with clockworkmod recovery.
1A. If you're s-off, download http://www.fourty.net/~berzerker/stockstuff/unrevoked-forever-son.zip
(NOTE: the unrevoked s-on tool does *not* support the 2.15.00.09.01 radio. If you're running that radio, download this, and flash that PB31IMG.zip in HBOOT before continuing.)
1B. Push that to your SDCard and flash it via clockworkmod recovery.
2. Download these two zip files: http://www.fourty.net/~berzerker/stockstuff/revert.zip and http://www.fourty.net/~berzerker/stockstuff/PB31IMG-77-1.00-2.1.zip
2A. Push PB31IMG-77-1.00-2.1.zip to your SDCard, renaming it to "PB31IMG.zip" (no quotes)(delete any other PB31IMG.zip you might have on there before pushing).
3. Unzip revert.zip to your desktop, reboot into recovery and execute the following commands from your cmd prompt/terminal:
Code:
adb shell
~ # mount data
~ # exit
adb push flash_image /data
adb push mtd0.img /data
adb shell
~ # cd /data
~ # chmod 755 flash_image
~ # flash_image misc mtd0.img
~ # exit
adb reboot oem-78
[b]MAKE SURE YOU TYPE [i]78[/i] and not any other number![/b]
You should see a black screen with a silver HTC logo. Now type:
Code:
fastboot devices
You should see something like HT056HJ01462 pop up. If that does, you're good.
4. Pull the battery, leave the phone off for about 10 seconds, then put the battery back in. Hold the volume *down* button as you put the battery back in, then press the power button (while still holding the volume down button). You should boot into HBOOT, and it should recognize the PB31IMG.zip. Start the update and go get a drink (it might reboot once or twice, don't worry about it).
(4B: If it keeps booting back into HBOOT, you'll need to apply it a second time, but you will not need to reflash misc, so just apply it again, it should take.)
5. When that's done, reboot, and you're done! You are now at 2.1 stock!
6. If you want to go through the OTA upgrade to 2.2, download this, rename it to update.zip and push it to your sdcard. Then, upgrade manually through recovery using the "apply sdcard:update.zip" option. After you reboot back into Android after that's done, you should be able to upgrade normally to 2.2 using the OTA.
Part 2: 2.2 stock using OTA RUU
1. Make sure you're rooted with clockworkmod recovery.
1A. If you're s-off, download http://www.fourty.net/~berzerker/stockstuff/unrevoked-forever-son.zip
(NOTE: the unrevoked s-on tool does *not* support the 2.15.00.09.01 radio. If you're running that radio, download this, and flash that PB31IMG.zip in HBOOT before continuing.)
1B. Push that to your SDCard and flash it via clockworkmod recovery.
2. Download this zip file: http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.26.605.1_RUU.zip
3. Push PB31IMG-3.21.605.1_RUU.zip to your SDCard, renaming it to "PB31IMG.zip" (no quotes)(delete any other PB31IMG.zip you might have on there before pushing).
4. Boot into HBOOT, and it should recognize the PB31IMG.zip. Start the update and go get a drink (it might reboot once or twice, don't worry about it).
5. When that's done, reboot and you're at 2.2 stock!
That's it! These steps should bring you back to either 2.1 stock or 2.2 stock for a send-in!
I suggest a sticky as well.

Berzerker for pres.

Download links are down
EDIT: NVM, and thanks for the guide will become helpful in the future.

Yes sir!
Mod pls make it a sticky.
ThX

Thanks Berzerker!!!

I would suggest sticky also. Things have changed a bit over the last few months and these instructions are current. In fact I just followed the exact steps in part 2 a week ago before sending in for a warranty. Did a nandroid before those steps and when I got my replacement all I had to do was run unrevoked 3.2 and restore my nandroid, right back where I left off!
Almost don't even see the need for part 1 though as 2.2 has become stock?
anyways, Thanks!

The link for the RUU has a dash instead of an underscore. Here is a corrected link:http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.21.605.1_RUU.zip

lordv8r said:
The link for the RUU has a dash instead of an underscore. Here is a corrected link:http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.21.605.1_RUU.zip
Click to expand...
Click to collapse
Fixed in OP.
spjoneser said:
I would suggest sticky also. Things have changed a bit over the last few months and these instructions are current. In fact I just followed the exact steps in part 2 a week ago before sending in for a warranty. Did a nandroid before those steps and when I got my replacement all I had to do was run unrevoked 3.2 and restore my nandroid, right back where I left off!
Almost don't even see the need for part 1 though as 2.2 has become stock?
anyways, Thanks!
Click to expand...
Click to collapse
Some people might want 2.1 for some odd reason, so I thought I'd include instructions (maybe they don't trust the 2.2 RUU or something, or want faster battery charging).

(NOTE: the unrevoked s-on tool does *not* support the 2.15.00.09.01 radio. If you're running that radio, download this, and flash that PB31IMG.zip in HBOOT before continuing.)
Click to expand...
Click to collapse
FYI you tried to link something in the word "this" and it didn't work.
Anyway, I put the PB31IMG-3.21.605.1_RUU.zip on my SD card as PB31IMG.zip and it wasn't recognized in HBOOT. I tried flashing the 2.15.00.07.28 radio as PB31IMG.zip and it wasn't recognized either.
Running Skyraider Sense 2.5.2, 2.05.00.06.11 radio. I ran unrevoked forever yesterday but then flashed the s-on file from your step 1A of part 2.

dg32 said:
FYI you tried to link something in the word "this" and it didn't work.
Anyway, I put the PB31IMG-3.21.605.1_RUU.zip on my SD card as PB31IMG.zip and it wasn't recognized in HBOOT. I tried flashing the 2.15.00.07.28 radio as PB31IMG.zip and it wasn't recognized either.
Running Skyraider Sense 2.5.2, 2.05.00.06.11 radio. I ran unrevoked forever yesterday but then flashed the s-on file from your step 1A of part 2.
Click to expand...
Click to collapse
Fixed link in OP.
If you're S-ON, you'll have to flash signed RUU's. Since your radio seems to be older than the 2.2 RUU, you can just flash the 2.2 RUU and it should recognize it.

Will part 2 work if I'm rooted/s-off using the 100% stock 2.2 ROM found in this forum?

JoeyBert said:
Will part 2 work if I'm rooted/s-off using the 100% stock 2.2 ROM found in this forum?
Click to expand...
Click to collapse
Yes. /10char

Berzerker7 said:
Yes. /10char
Click to expand...
Click to collapse
enabling my to get all future OTA updates?

JoeyBert said:
enabling my to get all future OTA updates?
Click to expand...
Click to collapse
Berzerker7 said:
Yes. /10char
Click to expand...
Click to collapse
/10characters.

Berzerker7 said:
/10characters.
Click to expand...
Click to collapse
appreciate it

Last question, still new to this - can you still get OTA updates after rooting/s-off?

Thank you for this thread! Got my phone all stock ready for an exchange!

JoeyBert said:
Last question, still new to this - can you still get OTA updates after rooting/s-off?
Click to expand...
Click to collapse
No, you cannot.

JoeyBert said:
Last question, still new to this - can you still get OTA updates after rooting/s-off?
Click to expand...
Click to collapse
No, nope, non, нет, não, iie, nehe, nada, 沒有, ne, he, ei, 없음, keine, ingen, geen, لا, aon, yok, nema, няма, هیچ, không có, brez, نہیں, tidak ada...
Just wanted to make sure everyone knew.

JoeyBert said:
Last question, still new to this - can you still get OTA updates after rooting/s-off?
Click to expand...
Click to collapse
The answer is not a simple no. If the phone is rooted and a certain thing is removed then you wont get the OTA. Also if you are not rooted but S-off you will get the OTA (s-off and root is not the same thing)

New way to downgrade from 2.2 to 2.1

Ok so found by mistake but will help ones with no sd slot to make goldcard
Ok so first dl. Superoneclick root then the auto rooter for 2.1 will let u know what its called later(ultra easy rooter)
Next 1a.open super1click and ulter easy rooter
2a.in super1click do the shell root
3a.the run ulter easy rooter,once finished u will be at the fastboot screen
4a.click fast boot to go to boot loader screen and then hit vol up to update"esrpimg" once that is done u will be back to 2.1.
5a.once the phone has loaded back up to 2.1 and root just go to recovery and load a rom
NOTE: put update.zip on root of sd so u can load cwm other wish u only get root
AND sry still no way to get soff....
HOPE that is better........for the pickie ones

That is by far the longest run on sentence ive ever seen. You should edit and complete your thoughts. As well as add info on to what your actually explaining. Such as a complete history of the problem. And links to the original related post.
Sent from my T-Mobile myTouch 3G Slide using XDA Premium App

Is this just another root method or will this also downgrade H-Boot, allowing someone to achieve S-Off after downgrading from 2.2 and H-Boot 1.0+
Your phone info in your sig says that your mytouch slide is S-Off'd. If it's true that you can achieve S-Off using this method, that would be huge news.

From what I have tryed alparev does not get soff when I did the downgrade all got changed buttbut the bootloader and the hboot will not allow me to get soff so so far no luck
the hoboot i have after downgrade is hboot 1.02.0000
now i dont know what the old hboot was so if anyone knows plz let me know so I can try to push it sum how
Thats sig is because I have muti slides so plz don't mistake it for what I'm posting now all this was tryed on new slide with 2.2.1

Has anyone ever tested this? I don't have a MT3GS anymore but this seems like a pretty awesome and pain free process to gain root.

I would also like to know if this works?

Yes it does work have done it muti times just to check and check YES it works.....

YES this surprisingly does work. The only problem I had was that the update file wasn't on my SD card so I continued to get a signature filed message when I tried to update. All I did was to copy the file from the mtg rooter fille over to my SD card and ran the update and it worked perfectly. I'm rooted and very happy!

Had to get my slide replaced and the new one came with 2.2.1. I used this method and it got me back to a rooted 2.1 state just like it says. Thanks for coming up with this one.

Really quick and easy! Thanks so much. Too bad T-Mobile is shipping these with 2.2.1 on them, no more S-Off...

Outstanding! Thanks for the tip. Worked flawlessly.

This would be awesome if there were links to where to download everything so someone doesn't download the wrong thing by mistake

important links
I agree with the last post ... links are critical here. This was the easiest rooting process I have ever encountered. Below are links left out by OP. Follow OP's instructions with these files and you'll be rooted quickly and painlessly.
super one click (v1.7 worked flawlessly for me)
http://forum.xda-developers.com/attachment.php?attachmentid=526223&d=1298565480
ultra easy rooter (mt3gslide specific)
http://www.fileserve.com/file/y8yFvWb
This method should be the new rooting method for folks receiving replacement or new slides with 2.2. This should, IMO, be in development.

Thank god for this method. My phone up and died and the replacement came with 2.2.1. I tried a few other methods that failed. This one worked like a charm.

nice
wish i would have stopped back here would have saved me from having to downgrade, root, then upgrade back too 2.2 smh.... lol but nice to know yeah!!!!

Very helpful
I am going to try this method soon. Do we need anything else other than those two files to get our phones operational again? I want to try cm7 nightly, but want to make sure the phone would work before trying to put on another rom.

dudas
hello friends xda congratulate you for helping and answering all our Unknowns but I wanted to ask for help with root touch me slide my'm total newbie at this and am having problems with the root of my phone if I do not understand and this is the only place to do this is here and we wanted to have some aid perire video on how to do it : Confused:: Confused:

crazygerz said:
hello friends xda congratulate you for helping and answering all our Unknowns but I wanted to ask for help with root touch me slide my'm total newbie at this and am having problems with the root of my phone if I do not understand and this is the only place to do this is here and we wanted to have some aid perire video on how to do it : Confused:: Confused:
Click to expand...
Click to collapse
1. Download the 2 files in post #13/ thanks NJAZ (SuperOneClickv1.7-ShortFuse.zip and mt3srooter.zip)
2. Extract them to their own folders on the desktop of your computer
3. Run the .exe files within each of the folders (open the programs SuperOneClick and mt3srooter--run as admin if using Vista or Win7)
4.In the Super1Click program, click "Shell Root", wait a moment til it does its thing
5.In the mt3gs rooter program, click on "Root Me"
It will tell you to turn on the wifi on your phone, and you must do it within 30 seconds, so hurry
6.Your phone will reboot into bootloader mode if all goes well. Use your volume buttons to navigate down to the fastboot option, and choose it with the power button. The phone will scan your sd card and find ESPRIMG.zip, and take a while checking the file. When it is finished checking the file, press the volume up button to confirm that you want to flash the file. Once it is finished flashing, you're rooted on stock 2.1 Eclair ROM.
I dont know if these programs put the update.zip for CWM onto your sd card too, I already had that and the ESPRIMG.zip on my card when I used this method, so if all else fails you, put a card into your phone with these files on the root of it into your phone and then use the 2 programs to gain root. Dont be afraid to try it a couple of times if it doesn't work the first time, and make sure that you have the correct drivers for your phone installed on your computer. To get into CWM Recovery to be able to flash custom ROMs, boot into bootloade by starting your phone and holding the vol-down button, and you will get a black screen with a red triangle. Then press power and vol-down and choose "Apply Update.zip" and in a moment you will be in CWM Recovery,as long as you have the file on the root of your sd card.
Just thought I'd spell it all out very detailed and simple for anybody less familiar with all this kind of stuff, makes for less "please explain step #...." posts.

ugh
this is soooo lame!!!!!!!!!!! n not ur post but my situation i cant get it!!!! it goes thru the process on ultra easy but one it get to the writting on cmd it says it wasnt "cd /sqlite_stmt_journals" then it says that the exploidcant be found and the rest of the other things that the program tries to push....im getting so frustrated..ived rooted g1 mytouch droid evo ived unlocked jailbroken all iphone models from 1st gen to iphone 4 all ipods unlocked blackberrys gotten to root on hd7 put android and wp7 on a hd2.... but this devices i am having so many problems!!!! ived tried every method and get to the same stop forget this phone im getting on craigslist n trading!

this worked for me....im still having problems with the a2sd tho...

[Q] another noob with a rooting issue

sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
ok so i used this: themikmik dot com/showthread.php?11114-GUIDE-WIP-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark
after using the HTCDEV to unlock.
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
i am stuck in between step 10 and 11.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
i downloaded su, root checker,and busy box. root checker says the phone is rooted. i know i need to get the h boot to a lower level inorder to do the unrevoked3 program.
tried flashing the recovery and says "cant open /sdcard/pc36img.zip (bad)"
made sure it wasn't zip.zip and it was so i fixed that and still wouldn't work.
the only thing i am not sure of is step 10 and wether i did it right :Once the misc partition has been updated, you can downgrade your Bootloader and HBOOT to a non-watermarked version rootable with unrevoked.
does the partition auto update or do i need to do something to make it update? i didn't see any option for this. eveything up to this point went exacty liek it should have so now i am lost. i have searched numerous forums and found similar problems but none that were exactly the same. and none of the solutions worked for me. i tried all the basics rebooting, etc and nothing. any info would be greatly appriciated.
the only other thing that i may have done wrong that i can tell is what file i am trying to make the pc36img. at the bottom of post # 1 it has 2 attachments listed as pc36img files those are the ones i am trying to use. when i try to click the hyperlinks thru the rest of the post i get an error message from that site thats says " This account's public links are generating too much traffic and have been temporarily disabled! " so i dont know if that site has the same zip files or i am completely using the wrong zip file.
sorry for the long winded post i know the noob video says make it brief but i figured the more info the better.
thank you.

sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
Click to expand...
Click to collapse
Oh brother was it!
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
Click to expand...
Click to collapse
Your S-On,so your not rooted.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
Click to expand...
Click to collapse
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.

Diablo67 said:
Oh brother was it!
Your S-On,so your not rooted.
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Click to expand...
Click to collapse
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App

when i check with root checker it says i am rooted and have su. maybe it just means unlocked? busy box also says rooted?
pc36img is in all caps.
thanks for the quick response!

evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible

evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
Click to expand...
Click to collapse
Ok,thanks for clearing that up,serious dudes i hate giving the wrong info when trying to help someone and i don't mind admitting when i'm wrong,lol.Your never to smart or old to learn something new.
Sent from my Dell computer.

I can probably help here.
If all you want is to be rooted, then you are. There's no reason to do the rest, especially if you're out of warranty. Since you already have a custom recovery installed, you can feel free to flash a custom ROM, and not even worry about the rest of the process.
The Dropbox links thing should be fixed now. I had to move them all to 4shared.
As far as the misc partition flashing, as long as you didn't get any errors when in the command prompt/adb shell, then I'm sure it flashed successfully. The only way to tell is if the Froyo PC36IMG.zip flashes successfully without a "main version fail."
I can assure you the PC36IMG works, as I've used it many times myself. Did you confirm the md5? Is it possible your SD card got corrupted somehow? Those are the only reasons it wouldn't pick it up.

thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?

98tib said:
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
Click to expand...
Click to collapse
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .

Captain_Throwback said:
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Click to expand...
Click to collapse
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.

98tib said:
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
Click to expand...
Click to collapse
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.

This is what's cool about this forum a noob asking a question and you get 4 big time contributors helping out!
Sent from my PC36100 using xda premium

Captain_Throwback said:
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
Click to expand...
Click to collapse
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem

98tib said:
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
Click to expand...
Click to collapse
What kind of sd card are you using? You might want to try a different card, or reformat the stock card, if that's what you're using. That's the only other reason it wouldn't pick up the file, provided it's named correctly. And I assume you verified the md5 and it's good? And you're certain the file is on the root of the sd card as well? I cant think of anything else that could be causing the problem. Let me make sure my bootloader reads the file just to make sure.
EDIT: Scratch everything I said above. If your phone still says "unlocked" at the top of the bootloader, the misc partition wasn't updated successfully. Did you already complete that part, with no errors? You need to reconnect the device while booted up, with USB Debugging enabled, and run those commands from the command prompt from the folder with adb in it. Make sure you have the files "flash_image" (extracted from zip file) and "mtd-eng.img" (extracted from zip file) on the root of your sd card. If you're using Windows 7, run Command Prompt as an administrator. Let me know the output of those commands before continuing. If you got any errors on that part, that would be why you can't flash the Froyo ROM.
I saw you mentioned that in your OP, but I guess I didn't realize you skipped that part. That'a really the most important part of the process. It's the part right before the sentence you mention about the misc partition being downgraded. That last command flashes the mtd-eng.img file to the misc partition.

both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.

98tib said:
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
Click to expand...
Click to collapse
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".

Captain_Throwback said:
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Click to expand...
Click to collapse
thank you, you are my savior! its always the dumb things that you think you did right that you did wrong! lol. thank you again!

now i'm off to screw something else up!

Serious Issues With Rooting

I have spent over a week trying to root my HTC Legend (running 2.2 froyo HBOOT 1.01).
Ive tried a dozen guides everywhere but I cant seem to get past the downgrade process :/
I tried this guide here (http://forum.xda-developers.com/showthread.php?t=894465) but i got "permission denied" when i tried to "adb reboot bootloader"
I get the cr--rw---- error when i try other guides.
Nothing seems to work.
Can anyone please write a simplified guide at one place for all this?
or tell me What really could be going wrong?

Use the "Hboot made easy guide" which is somewhere in this forum section. Very simple and I used the guide to root my legend after having fruitless tries with other guides.
Sent from my Legend using xda premium

The Legend just got added to the htc dev site so you should be able to unlock the bootloader now, might make things much easier for you.

Hi,
Did you find a solution ?
I'm in the same situation as you, my legend is froyo 2.2 and HBOOT 1.0.
If we use the htcdev, after that can we root the legend ?

makak06 said:
If we use the htcdev, after that can we root the legend ?
Click to expand...
Click to collapse
Yes, with "HTC Super tool v3"

first of all download an application called visionary+
http://content.modaco.net/dropzone/c...ryplus.r13.apk
make sure that the usb debugging is turned on.
i hope you know how to create a gold card and that you have done it.
put the gold card in the phone.
then instead of running the crackin.bat file open it in word pad.
then temp root the phone using visionary+
type in each command one by one in the command prompt.
then when you reach the step where they show "adb shell" followed by commands.
then type
adb shell
then you will get a '$' symbol
then type su
then you will get a '#' symbol
then continue typing the commands without the 'adb shell'
after you type 'reboot' ignore the 'wait_for_device'
once the phone is back on temp root it again before you proceed.
finish the procedure this way.
Remember that you will get many error messages while you type each command. ignore the messages.
You wont get the full crwxrwxrwx. But what you get will be good enough.
now you can run the RUU
please reply if you have any doubts.

just try Unlock Bootloader http://htcdev.com/

yup... agree to the guy above..
unlock your boot loader than, flash CWM, after that. flash what ever rom you want as long as its for legend roms... ^^

hi guys,
i unlocked my device via htcdev its hboot version is now 1.02.000 and i flashed recovery_legend_5.0.2.8.img but i am not able to flash a new rom
after i booted in to recovery mode i chose flash zip from sd card option in the list it couldn't pass to next screen, options listed in the main menu goes off and i can see only cwm icon (a black hat over a yellow circle) i waited 2-3 minutes but nothing happened when i press power button it returns to main menu again.
Also other options listed in the cwm main menu not goes further, reboot system and power off, wipe data... either, same thing happens as described above.
i am waiting your suggestions

inside the cwm menu you have to make a selection by hitting the trackball (when you press the power-button, only the image you've descriped will appear)

mph_aut said:
inside the cwm menu you have to make a selection by hitting the trackball (when you press the power-button, only the image you've descriped will appear)
Click to expand...
Click to collapse
damn it!.. what a silly mistake
i left left my phone at the office tomorrow i should give a try

and tbather
thanks, i use trackball to select menu options and installed custom rom fuse 2

Try the rc4b. A very good rom.

Also try zeubea's ICS alpha, just for giggles.
(read the op's post in there before trying it, it is alpha rom at this stage, getting better all the time).

zivilist said:
just try Unlock Bootloader htcdev
Click to expand...
Click to collapse
Can I also get rid of the S-ON on my phone by using this ??

timonmulder said:
Can I also get rid of the S-ON on my phone by using this ??
Click to expand...
Click to collapse
Yes you can, but be warned you can't go back (voids warranty)
Sent from my Legend using xda premium

Nice hmm now I have to find a simple guide for turning S-on to S-off, because my phone is already rooted
Sent from my Legend using XDA

Damn, I'm trying to get Hboot 1.02 on my phone, but it said my ROM isn't supported (yet).

timonmulder said:
Damn, I'm trying to get Hboot 1.02 on my phone, but it said my ROM isn't supported (yet).
Click to expand...
Click to collapse
you can flash the bootloader with the method BlaY0 provided here, regardless which rom you're currently using

mph_aut said:
you can flash the bootloader with the method BlaY0 provided here, regardless which rom you're currently using
Click to expand...
Click to collapse
Yeah I tried that one, and I got stuck everytime at step 7. He finds my LEGEIMG.zip, but when he wants to install that one he keeps saying:
Main version is older!
Update Fail!
Do you want to reboot device?

[GUIDE] 2-step unroot back to stock 2.3.4 from s-off and ANY ROM

I noticed a lot of people asking "How do I unroot back to stock 2.3.4 with s-off bootloader when the ruu's will not work with s-off bootloader?"
So in light of this there is a simple way to do this without installing the froyo PG06IMG.zip and going through the hassle of downloading all the firmware OTA's to get back to stock 2.3.4 firmware. I have used this method and it works great. You must be rooted with s-off for this to work. If your running a custom rom that is not sense based or based of the stock HTC sense roms, attempting to run a RUU will fail which makes this method usefull for anyone on any rom
More information can be referenced from HERE
Requirements:
Note: if you rooted using the method from HERE then you should already have all the requirements for this to work.
1) Windows
2) Android SDK
Once you download the sdk place it in the root of your C: drive and rename it to something easy like "android" or "sdk". Go into your sdk\tools folder and double click on the android file or right click on the file and select open. It should open a command prompt and then load the sdk.
INSTALL PLATFORM-TOOLS ONLY!
3) Download and install HTC Sync necessary for drivers in using adb and fastboot
4) Install a md5 utility like WinMD5Free for checking the hashsums of the files.
===============================================
Unrooting back to stock 2.3.4 firmware
WARNING: This will completely unroot your device. I or xda will not be held responsible for anything that may occur to your device if you do not follow the instructions properly. You have been warned!
5) Download the 2.3.4 hboot
Check the MD5sums of the file hboot_0.99.0000.img: 3008853f805b107fda434ce623f43318
If the MD5sums do not match the above numbers DO NOT CONTINUE
Place the file in your platform-tools folder in the android sdk
6) Download the 2.3.4 ruu
Note: MUST DOWNLOAD THIS FILE ON WIFI ONLY BECAUSE OF THE SIZE
Check the MD5sums of the file RUU_Speedy_S_Sprint_WWE_2.77.651.3_Radio_1.08.01.0111_NV_SPCS_2.97_01206_PRL60674_release_237263_signed.exe:
6e624a8ab1e1caa523a547c1fa54953b
Again if the MD5sums don't match the above numbers DO NOT CONTINUE
7)Plug your phone into your usb cable to your PC and make sure "USB debugging" is enabled on your device under Menu >> Settings >> Applications >> Development
open a cmd prompt (start button then type cmd and enter) and cd to your sdk\platform-tools folder.
Example: cd C:\android\platform-tools or cd C:\sdk\platform-tools
8) adb reboot bootloader
Make sure the device is in fastboot mode (a lot of times it's not). It should say fastboot in red letters on the top.
9) fastboot flash hboot hboot_0.99.0000.img
10)fastboot reboot-bootloader
If all goes well you should see "s-on locked"
11) Make sure your phone is in fastboot mode once again. Next run the ruu file and follow the instructions to install the factory images of 2.3.4
Congrats your phone is now back to stock 2.3.4 :victory:

I just unrooted my phone yesterday using the 2.3 RUU. Well actually I accidentally used the 2.2 RUU first and when I realized I then used the 2.3 RUU. It worked fine for me doing it that way.

BigSplit said:
I just unrooted my phone yesterday using the 2.3 RUU. Well actually I accidentally used the 2.2 RUU first and when I realized I then used the 2.3 RUU. It worked fine for me doing it that way.
Click to expand...
Click to collapse
This isn't for getting to 2.3.3 it's for 2.3.4...
And you can't even use a ruu on s-off because the bootloader verification fails.

Oh sorry, it wasn't the RUU, it was the 2.2 PGxxx zip I flashed in fastboot first. Then used the 2.3 RUU. Same outcome, back to factory 2.3.4 in 2 steps.
...And now it's time to re-root since they replaced my touch screen right there on the spot... I was surprised

BigSplit said:
Oh sorry, it wasn't the RUU, it was the 2.2 PGxxx zip I flashed in fastboot first. Then used the 2.3 RUU. Same outcome, back to factory 2.3.4 in 2 steps.
Click to expand...
Click to collapse
No not two steps... This is much faster and easier. And stop changing your story lol. Don't like the method don't use it...

i thought you could RUU with s-off?

VICODAN said:
i thought you could RUU with s-off?
Click to expand...
Click to collapse
It's basicly the same as this:
http://androidforums.com/evo-v-4g-a...evo-v-4g-ruu-flashing-guide-unroot-guide.html
Execpt for we're not doing fastboot oem lock'ing our bootloaders. We're just straight up flashing the locked s-on 2.3.4 bootloader so the ruu can think we're already on a stock firmware even though we're not.
Edit: if your running a custom rom attempting to run a ruu can cause a lot of issues which makes this method a lot easier for everyone OP updated with more info.

It appears the link to the 2.3.4 hboot file is dead! Any way you could re-upload it? Please and thank you!

capn-tightpants said:
It appears the link to the 2.3.4 hboot file is dead! Any way you could re-upload it? Please and thank you!
Click to expand...
Click to collapse
Link is fixed I accidentally deleted it from mediafire :laugh:

My screen broke and I need to return my phone to Sprint. I spent 3 hours looking through other unrooting guides until I found yours. Works flawlessly. My most sincere gratitude to you.

Peon the Professional said:
My screen broke and I need to return my phone to Sprint. I spent 3 hours looking through other unrooting guides until I found yours. Works flawlessly. My most sincere gratitude to you.
Click to expand...
Click to collapse
Thanks glad it worked out for you. Please hit the thanks button on the OP if it helped you.
Sent from my HTC Evo Shift using xda premium

No luck
I flashed the hboot, and it seemed fine through there, but cannot get the RUU to work. It keeps telling me that the usb connection isn't connected. Any thoughts?

dyebhai said:
I flashed the hboot, and it seemed fine through there, but cannot get the RUU to work. It keeps telling me that the usb connection isn't connected. Any thoughts?
Click to expand...
Click to collapse
Sounds like your missing some drivers. HTC sync or pdanet? Did you follow all the instructions?
Sent from my HTC Evo Shift using xda premium

RTFM - Then more problems
sparksco said:
Did you follow ALL the instructions?
Click to expand...
Click to collapse
Boy do I feel like a tool. The answer, of course, is no. I hadn't installed HTC Sync.
That said, it still wouldn't update the thing.
"The ROM Update utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again."
Error[131]: Customer ID Error
So, who has any idea why this happens?

After you flash the 2.3.4 bootloader you need to reboot bootloader so the rom utility can see the new bootloader as one it recognizes. After that you should be good to go.
Sent from my HTC Evo Shift using xda premium

Anyone have alternate links for the OP? It's kinda urgent
Thanks really appreciate it
---------- Post added at 03:18 PM ---------- Previous post was at 02:56 PM ----------
I found the RUU but still can't find the Hboot file. if anyone has it I'd greatly appreciate it.

bbedward said:
Anyone have alternate links for the OP? It's kinda urgent
Thanks really appreciate it
---------- Post added at 03:18 PM ---------- Previous post was at 02:56 PM ----------
I found the RUU but still can't find the Hboot file. if anyone has it I'd greatly appreciate it.
Click to expand...
Click to collapse
I had them, but I can't remember where I put them. Needed to create a seperate folder and didn't . You might want to PM Sparksco, see if he'll repost them.

I'll put the on too manager beta tonight. Apparently my Dropbox account was almost banned for too much traffic from these files. Luckily they just suspended it for 3 days. Didn't think it was in that much demand as hardly anyone post on this thread.
Sent from my Nexus 7 using Tapatalk 2

Links updated to goo.im

Thank you.
TEAM MiK
MikROMs Since 3/13/11