Develop Bugs

[REQ][HOW TO] Relock or Unroot EVO

I have been searching the web for how to relock my EVO. This is because i am taking it back to sprint for a screen fix and I have learned from the PPCGEEKS thread all the problems and warranty stuff related to rooting as well as the odds of them discovering that I have rooted it. I just don't want to risk it and I would like to know how to relock, just for the knowledge.
Does anyone have specific instructions how??
PPCGEEKS Thread: http://forum.ppcgeeks.com/showthread.php?t=126849

http://shipped-roms.com/shipped/Supersonic/
Download first and last, and flash in the same sequence.

So thats all?? its done? It's unrooted? That seems simple.

Yep, that's how easy it is.
On some phones (one out 5 I "control") I had to get all 3 and flash in the same sequence, otherwise last one wouldn't flash over the first - not sure why.

redsolar said:
last one wouldn't flash over the first - not sure why.
Click to expand...
Click to collapse
that surprises me. the latest RUU should flash over anything *theoretically*.
what error did it give you when you attempted?
yes, it should be easy to restore the phone to stock. think of all their service departments fixing/refurb'n phones. one simple flash and its all completely stock no matter what was loaded before.
for those more technically included, since this is the dev board, if the eng build RUU is loaded the PRI is downgraded and as of now, no currently released RUU is able to upgrade the PRI ... but thats such a small issue, can almost guarantee nobody will notice.

Damn screen... I have to do the same thing, and just one other question, besides those files I will just have to use Htc Sync to flash them right?

Yellowcard8992 said:
Damn screen... I have to do the same thing, and just one other question, besides those files I will just have to use Htc Sync to flash them right?
Click to expand...
Click to collapse
Those RUUs are just exe files. So sync will provide you with drivers yes, but after downloading you just run from that download with your phone plugged in.

wow after reading that thread on ppcgeeks i dont think i ever want to leave xda! must be a young crowd over there. i ran the latest 1.47 RUU that i downloaded from HTC before I returned my phone. much to my surprise they didn't even take the phone out of the box! still, since it only takes 10 minutes might as well do it.

barnacles10 said:
Those RUUs are just exe files. So sync will provide you with drivers yes, but after downloading you just run from that download with your phone plugged in.
Click to expand...
Click to collapse
are you talking about just using the volume down and power button method?

redsolar said:
Yep, that's how easy it is.
On some phones (one out 5 I "control") I had to get all 3 and flash in the same sequence, otherwise last one wouldn't flash over the first - not sure why.
Click to expand...
Click to collapse
whats the point in running all 3 on a phone you are returning? just running the first one is good enough to unroot and restore to stock. i only ran the most recent one, because i had already upgraded the baseband and was unable to run the earlier ones because of it.

joeykrim said:
that surprises me. the latest RUU should flash over anything *theoretically*.
what error did it give you when you attempted?
yes, it should be easy to restore the phone to stock. think of all their service departments fixing/refurb'n phones. one simple flash and its all completely stock no matter what was loaded before.
for those more technically included, since this is the dev board, if the eng build RUU is loaded the PRI is downgraded and as of now, no currently released RUU is able to upgrade the PRI ... but thats such a small issue, can almost guarantee nobody will notice.
Click to expand...
Click to collapse
I was surprised too when I tried first.
The 1.47 RUU just sat on the "waiting for bootloader" screen and timed out after ~90 seconds, "unable to find phone" (tried multiple times) and the screen would get stuck in white bootloader/RUU message (battery pull required) - so i am guessing 0.76.2 bootloader was too low for it. That was flashing from 3.2.2+ DamageControl ROM, didn't try from any other one, since the DC -> 1.36 -> 1.47 stock worked well.
And yes, the PRI caveat is there, but as joeykrim said, that's minor, plus you can always say "PRI what - huh?", right?

OneStepAhead said:
whats the point in running all 3 on a phone you are returning? just running the first one is good enough to unroot and restore to stock. i only ran the most recent one, because i had already upgraded the baseband and was unable to run the earlier ones because of it.
Click to expand...
Click to collapse
Running latest OTA makes you seem more of a "dumb user" who wouldn't even know what root is?

Yellowcard8992 said:
are you talking about just using the volume down and power button method?
Click to expand...
Click to collapse
No. RUUs are handled differently. You download the file. And run it on your computer with the phone plugged in. It does everything for you. You DO NOT flash these via recovery.

Update on my phone
I took it to the sprint store yesterday and against everything I have heard the guy at the store turned my phone and checked it. Thank god I used redsolar's posted method. I must have the appearance of someone who would root there phone. It passed his inspection, luckily.
Thanks for the help

I rooted with the new Simpleroot OTA Edition, with Fresh Rom 053, and RA-Rec.
I'm trying to start over from stock so I can re-root my phone, but I can't get the RUU's to work. The oldest one will actually try and put the phone in bootloader, but while its waiting for bootloader it eventually just stops and gives me the 170 error, usb connector problem.
So is there any other way to go about this? Any help would be greatly appreciated.

murdercitydan said:
I rooted with the new Simpleroot OTA Edition, with Fresh Rom 053, and RA-Rec.
I'm trying to start over from stock so I can re-root my phone, but I can't get the RUU's to work. The oldest one will actually try and put the phone in bootloader, but while its waiting for bootloader it eventually just stops and gives me the 170 error, usb connector problem.
So is there any other way to go about this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
ya what I do is replug the usb coord then try ruu again while the phone is stuck on the HTC sign,then if that doesn't work I just manually go into bootloader myself (power+volume down) then use the ruu.exe, works everytime but then it tells me my current version is not valid, so if you ota'd you probably won't ever be able to go back to 1.32.651.1/.6 stock but you can just use the new 1.47.651.1 ruu to regain stock after ota.

Tundricles said:
ya what I do is replug the usb coord then try ruu again while the phone is stuck on the HTC sign,then if that doesn't work I just manually go into bootloader myself (power+volume down) then use the ruu.exe, works everytime but then it tells me my current version is not valid, so if you ota'd you probably won't ever be able to go back to 1.32.651.1/.6 stock but you can just use the new 1.47.651.1 ruu to regain stock after ota.
Click to expand...
Click to collapse
Thanks a **** load Tundricles, you saved my ass.
I was getting so pissed, I'd run the RUU and once it got to opening the bootloader on my phone it was get frozen on the HTC screen, and the RUU would get the use connection error. So I unplugged my phone, and noticed it was in the bootloader, but if the usb was plugged in, it wouldn't show the bootloader screen for some reason. So I just plugged it back in and started the RUU back up, it instantly went past the "Waiting for bootloader..." message and started updating.
Thank you, and for anyone else having similar problems, READ THIS!

Flashing the RUU doesn't restore the stock recovery does it?
I ran Unrevoked 2 a while back and I have RUU'd but I'm pretty sure Clockwork Mod is still there.
Sent from my EVO 4G using the XDA App.

ViViDboarder said:
Flashing the RUU doesn't restore the stock recovery does it?
I ran Unrevoked 2 a while back and I have RUU'd but I'm pretty sure Clockwork Mod is still there.
Sent from my EVO 4G using the XDA App.
Click to expand...
Click to collapse
It should. RUU replaces everything but PRI
Sent from my PC36100 using XDA App

murdercitydan said:
Thanks a **** load Tundricles, you saved my ass.
I was getting so pissed, I'd run the RUU and once it got to opening the bootloader on my phone it was get frozen on the HTC screen, and the RUU would get the use connection error. So I unplugged my phone, and noticed it was in the bootloader, but if the usb was plugged in, it wouldn't show the bootloader screen for some reason. So I just plugged it back in and started the RUU back up, it instantly went past the "Waiting for bootloader..." message and started updating.
Thank you, and for anyone else having similar problems, READ THIS!
Click to expand...
Click to collapse
np glad I could help

[Q] Trouble rebooting into recovery and ROM

Hey all,
***ISSUE*** I can only boot into recovery or a ROM once. ***ISSUE***
I recently replaced my EVO through Sprint, and rooted. (unsuccessfully with unRevoked, but successfully with AutoRoot). After I used unRevoked (but before using AutoRoot) this issue started popping up.
I can flash a recovery image via Bootloader/Hboot or PARTICULAR ROMs, Sprint Lover's seems to be the most reliable, CM7 does not seem to work at all, and be able to access them once, and upon reboot I get the white "htc EVO 4G" screen and it hangs there until I reboot. Once that happens I cannot access recovery or boot into the ROM until I reflash from a PC36IMG.zip in Hboot/bootloader.
Here's my hardware info:
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Hardware Revision #3
My Evo was originally on HBOOT 2.10, but I flashed an eng-PC36IMG.zip that let me install the ENG bootloader on it, which has made it so things flash more reliably.
Anyone have any advice? It seems really odd to me that software would work once and not again. Any suggestions would be appreciated.

There could be something from the rooting process that's affecting your phone somehow, although that's really strange. I would suggest unrooting, getting fully back to stock, & rooting again. If you're not going to be able to reboot your phone without reflashing, which seems like a pain, it might be best to redo it.
Other than that, I'm baffled :/
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App

Thanks for the reply, plainjane!
I am in the process of unrooting now to see if that works. I installed the unrevoked-son via ClockworkMod Recovery 3.0.0.5, but I still had S-OFF when I went to HBoot. I'm not sure, but I think I remember somewhere that the ENG bootloader does that.
Regardless, I'm installing the latest (3.70) RUU now and will see what that does.

RandomViolence said:
Thanks for the reply, plainjane!
I am in the process of unrooting now to see if that works. I installed the unrevoked-son via ClockworkMod Recovery 3.0.0.5, but I still had S-OFF when I went to HBoot. I'm not sure, but I think I remember somewhere that the ENG bootloader does that.
Regardless, I'm installing the latest (3.70) RUU now and will see what that does.
Click to expand...
Click to collapse
Yea, im pretty sure the. 76 eng hboot is permanently s off. Also, I was unaware that hboot version 2.1 was downgradeable, I thought it wasn't able to be changed. Interesting. Maybe that's part of your problem, im really not sure. Sounds annoying though. Hopefully unrooting and starting fresh will help.
Sent from my PC36100 using XDA App

Thanks for the reply k2buckley!
I've now run the S-ON tool and used the 3.70 RUU to unroot my Evo. After the RUU completed its process my EVO rebooted and has not left the white "HTC EVO 4G" screen. (EDIT: I checked in Hboot and am now S-ON and on the 2.10 bootloader.) I've let it run for about ten minutes now and I'm not hopeful.
Now that I have it in a state where I can return it to Sprint I don't think I'm going I'm going to mess with it any more. It's such a shame. My first Evo was wonderful until an odd software glitch bricked it, and now this. It's been a really frustrating couple of weeks.
After this experience I don't think I'll be using unrevoked again. I loved having the speed and features of CM7 on my first Evo, but I'm debating rooting at all at this point.

RandomViolence said:
Thanks for the reply k2buckley!
I've now run the S-ON tool and used the 3.70 RUU to unroot my Evo. After the RUU completed its process my EVO rebooted and has not left the white "HTC EVO 4G" screen. (EDIT: I checked in Hboot and am now S-ON and on the 2.10 bootloader.) I've let it run for about ten minutes now and I'm not hopeful.
Now that I have it in a state where I can return it to Sprint I don't think I'm going I'm going to mess with it any more. It's such a shame. My first Evo was wonderful until an odd software glitch bricked it, and now this. It's been a really frustrating couple of weeks.
After this experience I don't think I'll be using unrevoked again. I loved having the speed and features of CM7 on my first Evo, but I'm debating rooting at all at this point.
Click to expand...
Click to collapse
If you do, root it manually - save yourself from all these headaches of the autoroot programs.

Thanks for the advice Heaterz16!
I'd love to root manually to ensure everything goes well. The guide that I saw indicating how to manually root was taken down and linked to AutoRoot as the way to go. Could you point me towards a guide for manual rooting?

Take it back to Sprint. I had one that would rarely boot, it would take 20 or so tries. When it finally did boot, the screen would freeze up & I'd have to pull the battery. They gave me a new one, no questions asked & I had it the next day. That phone was never rooted, it was only two weeks old. I have insurance, so all of my replacements have been free. I had the one before that 3-4 weeks before the usb port gave out. I got my third one three months ago, rooted it, and have had no problems since. I hated the Evo for about a month when mine kept breaking.
I would also suggest manually rooting. The "one-click" methods are easy to do but difficult to troubleshoot. Manual methods are a little more difficult to do but cause far less problems.
Just remember to delete any evidence of rooting from your sd card or just remove it entirely before taking the phone to Sprint. I hope everything works out for you!
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App

plainjane said:
Take it back to Sprint. I had one that would rarely boot, it would take 20 or so tries. When it finally did boot, the screen would freeze up & I'd have to pull the battery. They gave me a new one, no questions asked & I had it the next day. That phone was never rooted, it was only two weeks old. I have insurance, so all of my replacements have been free. I had the one before that 3-4 weeks before the usb port gave out. I got my third one three months ago, rooted it, and have had no problems since. I hated the Evo for about a month when mine kept breaking.
I would also suggest manually rooting. The "one-click" methods are easy to do but difficult to troubleshoot. Manual methods are a little more difficult to do but cause far less problems.
Just remember to delete any evidence of rooting from your sd card or just remove it entirely before taking the phone to Sprint. I hope everything works out for you!
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App
Click to expand...
Click to collapse
Thanks for the advice. I plan to just go to Sprint without my SD card and tell them the situation.
If you could point me towards a good guide for manual rooting I'd be grateful. After this last experience I'd much rather just do it myself and ensure it goes correctly.

Unrevoked gives issues like this. Try to start with autoroot this time.
Do not try to downgrade your bootloader this time. Make sure you nandroid back up and flash different ROMs and ensure things are working before you set anything up. Also make sure you are wiping everything. I suggest using Caulkin's Format All and flashing that in recovery.

sekigah84 said:
Unrevoked gives issues like this. Try to start with autoroot this time.
Do not try to downgrade your bootloader this time. Make sure you nandroid back up and flash different ROMs and ensure things are working before you set anything up. Also make sure you are wiping everything. I suggest using Caulkin's Format All and flashing that in recovery.
Click to expand...
Click to collapse
Thanks for chiming in, sekigah84.
The reason I tried downgrading my bootloader last time was that the issue appeared consistently with the 2.10 bootloader (tried flashing various recoveries, ROMs, radio versions, etc, over four days on that bootloader) and I thought reverting to ENG 0.76 might help correct the problem. I was very careful about doing nandroid backups and wiping cache, dalvik before installing ROMs, etc. when I could access recovery. Restoring from a backup was never possible because upon reboot I'd simply get the white HTC screen.
The problem seemed to start immediately after using unrevoked and didn't go away regardless of what I flashed or how many times I RUUed.
I definitely won't use unrevoked again. I'd consider using AutoRoot, but I'd prefer just to do a manual root process, or maybe not root at all.

RandomViolence said:
Thanks for the advice. I plan to just go to Sprint without my SD card and tell them the situation.
If you could point me towards a good guide for manual rooting I'd be grateful. After this last experience I'd much rather just do it myself and ensure it goes correctly.
Click to expand...
Click to collapse
Here's a link for you. As you said, this post has been retired, and it links you to xhausx's autoroot, however it still contains all of the info and instructions, and that method will still work for you. It's not outdated yet. So if you want to run it manually, follow Zikronix's instructions within the first post of this thread. Have fun!
http://forum.xda-developers.com/showthread.php?t=829045&highlight=root

[Q] Evo stuck in boot loop

Hi guys, I just got an Evo that will Boot up to saying "HTC EVO 4g" on the white screen, then "evo 4g" with the Android caracter, then Says "Droid" with the droid voice... after that it gets stuck in loop.... specifics are below
NO FACTORY SD Card in it... Though I have a 16gb micro sd i can put in it.
I can boot into where I see this info.
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-AMTEL224_16ab
RADIO-1.39.00.04.26
Apr 14 2010, 15:41:34
showing these options below that say
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I'm sure there are probably files that might be needed to be on the SD card to get it back booting up properly
What do I need to do, or what files do I need?
Thanks in advance!

02busa said:
Hi guys, I just got an Evo that will Boot up to saying "HTC EVO 4g" on the white screen, then "evo 4g" with the Android caracter, then Says "Droid" with the droid voice... after that it gets stuck in loop.... specifics are below
NO FACTORY SD Card in it... Though I have a 16gb micro sd i can put in it.
I can boot into where I see this info.
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-AMTEL224_16ab
RADIO-1.39.00.04.26
Apr 14 2010, 15:41:34
showing these options below that
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I'm sure there are probably files that are needed to be on the SD card that it uses to boot...
What do I need to do, or what files do I need?
Thanks in advance!
Click to expand...
Click to collapse
Okay. A few problems I see. Problem number one. You are S-on. You need to be S-off in order to flash anything. Two, your radio version is waay out of date. Did you just get the phone, used? because you said "i just got an Evo..." Have you ever had it running? If not, I probably suggest flashing back to stock, then re rooting. Do you have a custom recovery right now? From the bootloader screen (the screen you posted the info above from), what happens when you select the 'recovery' option? Do you get a red triangle? Or do you get to a custom recovery screen? (would be clockwork or Amon Ra)

HTCRALEIGHFAN, I got the phone without the original sd card, so no backup that I know of.
k2buckley, phone is used, never booted up completely since i've had it, It does go into recovery with a red triangle. I do have a good 16gb micro sd card for it. I'm just trying to get it back up and running to stock first then go from there. Thanks

02busa said:
HTCRALEIGHFAN, I got the phone without the original sd card, so no backup that I know of.
k2buckley, phone is used, It does go into recovery with a red triangle. I do have a good 16gb micro sd card for it. just trying to get it back to stock first then go from there. Thanks
Click to expand...
Click to collapse
Okay cool. I agree, that getting back to stock is your best option from where you are right now. At that point, you can leave it, or root it and get into flashing custom roms and what not. To get back to stock, you have two options. You can either run an RUU, or flash a PC36IMG from your bootloader. Here is a link to the RUU's and PC36IMG's. http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
To run the RUU, you need to have HTC Sync installed on your computer. You need to set your Evo into 'fastboot' mode, from the bootloader screen. Once it's in fastboot, connect to the computer and run the RUU. I'm not sure if you can run the most recent RUU (3.70 software), or if you need to run an older one, to match to the .79 hboot that you have. I would first try the 3.70 RUU, and see if that works. That should put you on the latest software, and update all your radios to the most recent, and update your hboot to 2.10. If you have trouble with the RUU, you can download the PC36IMG, be sure it's named exactly PC36IMG, put it on the main directory of your sd card (then put the sd card in the phone), and boot to the bootloader (power and volume down). The bootloader should then find the PC36IMG and ask you if you want to update, Select volume up to say yes. Either of those methods should flash you back to stock.

k2buckley said:
Okay cool. I agree, that getting back to stock is your best option from where you are right now. At that point, you can leave it, or root it and get into flashing custom roms and what not. To get back to stock, you have two options. You can either run an RUU, or flash a PC36IMG from your bootloader. Here is a link to the RUU's and PC36IMG's. http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
To run the RUU, you need to have HTC Sync installed on your computer. You need to set your Evo into 'fastboot' mode, from the bootloader screen. Once it's in fastboot, connect to the computer and run the RUU. I'm not sure if you can run the most recent RUU (3.70 software), or if you need to run an older one, to match to the .79 hboot that you have. I would first try the 3.70 RUU, and see if that works. That should put you on the latest software, and update all your radios to the most recent, and update your hboot to 2.10. If you have trouble with the RUU, you can download the PC36IMG, be sure it's named exactly PC36IMG, put it on the main directory of your sd card (then put the sd card in the phone), and boot to the bootloader (power and volume down). The bootloader should then find the PC36IMG and ask you if you want to update, Select volume up to say yes. Either of those methods should flash you back to stock.
Click to expand...
Click to collapse
Thanks, ran the Original RUU and that got it up and rolling! thanks again! gonna update to the latest RUU next then go from there... What's the best root option Unrevoked???
EDIT: ran the latest RUU, and now on Froyo 2.2

02busa said:
Thanks, ran the Original RUU and that got it up and rolling! thanks again! gonna update to the latest RUU next then go from there... What's the best root option Unrevoked???
EDIT: ran the latest RUU, and now on Froyo 2.2
Click to expand...
Click to collapse
Nice, glad it worked for you. Unrevoked is easy, and has worked fine for me many times. Just uninstall htc sync from your computer, install the hboot drivers, be sure no programs on your computer can try to communicate with your evo, and run unrevoked. That's it. Just read up before diving in.
Edit: Here's a good tutorial on how to properly use Unrevoked. I've seen a bunch of people have problems with it, but I've always followed these instructions, and I've never had trouble on any of the Evo's I've rooted. Just don't use the files linked in that post, as they're most likely out of date. Download Unrevoked and the hboot drivers from the Unrevoked site, in the 'more info' section. Good luck.
instructions:
http://forum.xda-developers.com/showthread.php?t=787304
Download Unrevoked 3.xx
http://unrevoked.com/recovery/
download hboot drivers here
http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
Sent from my PC36100 using XDA App

k2buckley said:
Nice, glad it worked for you. Unrevoked is easy, and has worked fine for me many times. Just uninstall htc sync from your computer, install the hboot drivers, be sure no programs on your computer can try to communicate with your evo, and run unrevoked. That's it. Just read up before diving in.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks again for your help! I'm very familiar with Android. But HTC's are just totally different than my Samsung Galaxy so the processes are different. Bought the EVO with the Intent on fixing the boot Issue, and using it as an "Android Alternative" to an iPod Touch/MP3 Player. I don't have service with Sprint either. But I paid $50 for the EVO, and it's specs simply B****slap the iPod's. Gonna Root it, Throw an Otterbox on it, and give Steve Jobs the finger once again!

02busa said:
Thanks again for your help! I'm very familiar with Android. But HTC's are just totally different than my Samsung Galaxy so the processes are different. Bought the EVO with the Intent on fixing the boot Issue, and using it as an "Android Alternative" to an iPod Touch/MP3 Player. I don't have service with Sprint either. But I paid $50 for the EVO, and it's specs simply B****slap the iPod's. Gonna Root it, Throw an Otterbox on it, and give Steve Jobs the finger once again!
Click to expand...
Click to collapse
You're welcome
Haha, nice! Damn, you bought it for $50 dollars [email protected]@>>?? I should try to find an evo that won't boot for 50 bucks and see if I can fix it. You got a good deal on it, is it in otherwise good shape? You can still use it on wifi too, don't forget. And you'll still have a ton more functions to use in addition to Mp3. (video, other cools apps/games, and don't forget, we have FULL HDMI mirroring for the Evo now) Good luck with your Evo, and I edited my previous post with more clear instructions on how to use unrevoked.
And yea, the Samsung Galaxy S is completely different, as far as flashing methods and terminology at least. I was just reading up on rooting and flashing for Fascinate's (to help a friend out), and I felt like a complete noob again. I had to read quite a bit to catch on to things over there. It was a completely different world!

As k2buckley said, always need to keep the radios up to date, but you should be fine now. And though rooting is the same, its different for each device. I'm soon gona root my girl friend's desire, and I had to get all the things now and do my reading so when she comes to visit I know what I'm doing.

k2buckley said:
You're welcome
Haha, nice! Damn, you bought it for $50 dollars [email protected]@>>?? I should try to find an evo that won't boot for 50 bucks and see if I can fix it. You got a good deal on it, is it in otherwise good shape? You can still use it on wifi too, don't forget. And you'll still have a ton more functions to use in addition to Mp3. (video, other cools apps/games, and don't forget, we have FULL HDMI mirroring for the Evo now) Good luck with your Evo, and I edited my previous post with more clear instructions on how to use unrevoked.
And yea, the Samsung Galaxy S is completely different, as far as flashing methods and terminology at least. I was just reading up on rooting and flashing for Fascinate's (to help a friend out), and I felt like a complete noob again. I had to read quite a bit to catch on to things over there. It was a completely different world!
Click to expand...
Click to collapse
Yeah, I've gotta replace the digitizer.. Ordered one already. Got an Otterbox Commuter on the way also.. I'll have roughly $100 in it, and it kicks the $hit outta any iPod or iPhone out there...
Yeah, The Galaxy S line of phones is waaaaaaaaaaaaaaaaay more of a pain in the ass considering every variant has a different firmware version. Thinking i'm gonna jump to GSM soon and pop my sim card in whatever phone i wanna use that day.. lol. I like the specs of the Galaxy S II http://galaxys2.samsungmobile.com/html/specification.html
Also thanks for the help, it can definately be a pain jumping from dealing with one phone to the other.. especially at 2a.m. things start to run together.. lol

teh roxxorz said:
As k2buckley said, always need to keep the radios up to date, but you should be fine now. And though rooting is the same, its different for each device. I'm soon gona root my girl friend's desire, and I had to get all the things now and do my reading so when she comes to visit I know what I'm doing.
Click to expand...
Click to collapse
Yeah can definately be annoying jumping between phones...

Please help with unroot, i messed up and and going crazy here.

Ok, I rooted with unrevoked a long time ago. Broke my screen and need to unroot. I followed the unroot unrevoked guide as closely as I could, but the rom in the link was not found. So I downloaded a different ruu.zip of factory rom, don't ask me which one, because I can't find the link anymore, but currently here is where I stand. Hboot kept saying that the img was older or something, and wouldn't flash. So I did a stupid thing and pushed the zip with clockwork. So now I'm running s-on with clockwork recovery and a stock unrooted rom. So, I tried the next thing, downloaded an 3.7 ruu .exe and tried to run that from windows, but it gives me an hboot usb connection error f*ucking **** 1 thing after another.
This is the unrooting guide I used http://forum.xda-developers.com/showthread.php?t=780141
I got s-on, and tried that pc36img but it wouldn't work, originally. Before I went on to screw things up.
I've been at this for hours, something that should have taken 10 minutes if I wasn't an idiot, or bad links, or what ever. Can someone tell me or point me in the right direction, of what to do here, preferably not to a 2 year old thread with outdated links? What should I do?`
A List of android stock RUU zips with radio, pri, recovery all in one would be great, but I give up on trying to find that, its buried or does not exist.
I found this list http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs but its just the rom not everything.
So here is where my phone stands
S-ON
Hboot .97
Clockwork recovery 2.5.0.7<<<<<<
Android version 2.2.2
Build number 4.54
PRI 1.90_003

Angrychair420 here is a stock RUU that I know is good you should be able to run the RUU from windows.
http://geekfor.me/evo/ruu/evo_ruu_1326511/

thanks, that says its img version 1.32.651.1, assume thats safe to use. I assume thats andoid 3.26 which is what came on my phone. Ugh I'm in over my head. Why did my screen have to break, i was totally happy with CM7 and everything the way it was.
what if I wipe my data and caches, remove SD card, put on a PC36IMG.zip and boot the phone into hboot, will it still give me the older version error?
edit: the link you gave me gives me the same error as the other ruu.exe:
The ROM Update Utility cannot update your android phone
Please get the correct ROM Update Utility and try again

Possibly but I did have to return mine for repair and I know that using it as a .exe file trough windows I had no problem. Not sure about making it into a PC36IMG.zip file though I have not tried it that way.

Angrychair420 said:
thanks, that says its img version 1.32.651.1, assume thats safe to use. I assume thats andoid 3.26 which is what came on my phone. Ugh I'm in over my head. Why did my screen have to break, i was totally happy with CM7 and everything the way it was.
what if I wipe my data and caches, remove SD card, put on a PC36IMG.zip and boot the phone into hboot, will it still give me the older version error?
Click to expand...
Click to collapse
It might. There are 3 PC36IMG files in the first "My Links" link in my signature. You can try them in order if you'd like, if you get the "main version is older" message, but if the first two don't work, the last one definitely will.

Thanks cpt, about to give them a try. Sigh man, this is frustratingly harder than rooting :-D If it was as easy as doing the s-on and copy the pc36img.zip to the root of sd and booting into hboot and DONE, I would of been having a much better day.

Try the latest RUUs from this link man:
http://www.filefactory.com/f/acf0b850b0f70d7b/

Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
You can also try this
http://www.goodandevo.net/2011/03/how-to-unroot-your-htc-evo-4g.html

I appreciate the help guys. I will keep posted. You know how much it sucks to slide on a touchscreen thats broken? lol
partyman1971 said:
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
Click to expand...
Click to collapse
Yes, that's the first RUU.exe I tried. said this RUU can't update
ok i got a pc36img.zip installing from hboot right now.
edit:dang main version is older error. Trying a wipe then hboot then pc36img.zip
Same outcome, main version is older.
partyman1971 said:
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
You can also try this
http://www.goodandevo.net/2011/03/how-to-unroot-your-htc-evo-4g.html
Click to expand...
Click to collapse
yes, they are basically the same method I used in my OP from xda forums.
On to captain_throwbacks second ruu.
Just to make sure, this all isn't in vain, and make you all hate me, after applying one of these successfully, my recovery should go back to factory and no longer be clockwork, right? or wrong, because I'm starting to think I am. But won't taking your device in for service with clockwork be a dead giveaway that it was rooted.
I think I'm just going to go get a new phone for a $100 deductible at this point. and replace the screen my self on my old one and keep it as a backup/test device. Thanks for all the help, but I am surrendering :-D hopefully I can reroot this thing again with unrevoked, since my hboot is still .97 and fix the screen my self.

It generally doesn't matter if its rooted. I've never unrooted since launch day. And I've had 3 screen replacements, 3 speaker rwolacements , a bezel replaced, and camera lens cover replaced (last time, I dropped it off with ICS), about to go get my 4th screen (just cracked it again lol).
Sorry for your experience/frustration.
sent from AOKP heaven

well last stupid question i promise, since i still have clockwork isntalled, i can just restore my CM7 backup, but how do i get s-off back, re unrevoked it i assume?

If your'e worried about the warranty thing, just flash a stock rooted rom, or use a phone repair service. i see three or four repair places on craigslist (granted, that you live in a large city).

yeah no worries. Got it back to S-OFF, and CM7 back on it, just going to fix the screen my self, ordered one for $15.
thread can be locked, deleted, or what ever.

Seriously. Dude, isn't there a sprint store near you?. Just take it in. Put a stockish rom on it if you're that worried about it. They should replace it for free.
sent from AOKP heaven

[Q] Stuck in a loop please help

Incrediblec XD ship S-On
Hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Hello, first thank you for an amazing and current forum, I'd been researching my issue for a while, but most things are dated around 2010. I've experience rooting and ROMing a Droid X with multiple ROMS, but I use the original Incredible as my main phone because I still love it. Well, I originally rooted my Inc with Unrevoked3 I believe. I left the ROM as stock up until a couple months ago when I put CM7.2.0 on it.
About a week ago, the phone would always have working mobile data. Yet, if I received or tried to make a call, I couldn't and then I would lose texting ability. Then, a couple days ago, I was using the Inc for wifi tethering when suddenly it went into an Incredible bootloop. I tried booting to the cyanogen recovery, but it will quickly loop out of it as well.
I went to pvillecomp.com/ and downloaded all the stock Inc software. I individually renamed files to PB31IMG.zip and tried to have HBoot pick up on them. Hboot will see the files, but then do nothing. Except, the originally ROM will get checked and come back and say that the current version is older and can't be flashed.
I've always tried the RUU software for hboot and the original ROM. I either get a usb error or a low battery error even if the battery is charged. Granted, I'm trying the RUU from the phone's bootloader screen.
Does anyone have some support they could throw this way? I use my phone for internet and everything. Thank you all.
-Nevin

BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin

NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
did you flash any radios? Flashing radios always ends up bad.

NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.

I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
123421342 said:
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
Click to expand...
Click to collapse

Btw, no I didn't flash the radio. That was the only thing I didn't attempt to flash. Yet, when attempting to flash anything else, nothing worked. Still wondering about getting S-off before using TWRP, but hopeful to still get it working. Thank you again.
NevinInc said:
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
Click to expand...
Click to collapse

BUMP/UPDATE:
Yes, I'm still at it trying to get my Dinc out of it's bootloop and up/running. It's difficult at this point to say what all I've tried. At one point I wanted to use htcdev.com to ensure the bootloader was unlocked/etc. I've had much trouble trying to get fastboot to work correctly on my pc. I've seem to get stuck on "waiting for device" which appears to be a driver error.
I gave up on that and started focusing on the RUU process. I've tried to install the entire Gingerbread 605.3 file. I fixed the error usb 170 by updated or changing htc sync software. Now I'm left with error 140 bootloader error.
I've also updated hboot using the ruu process for version 605.2. This worked on my pc and got me partially excited. Now my hboot shows up as "Locked" now at the top. I also downloaded a different Stock.img file. Hboot detected this and begun the install process. Everything came up as complete and upon reboot went right back into the white screen/incredible bootloop.
So since posting before I've updated htc sync on my pc and have officially relocked my bootloader. I don't mind RUU'ing things to stock, but now gotta get past the Error 140. Any ideas?

So I'm not sure how many are looking at this or have had ideas, but I was able to use htcdev to unlock the bootloader.
Before unlocking the bootloader I was able to RUU to image .15. After this is when I unlocked the booloader. The RUU said it was complete, but I still only bootloop on the incredible white screen. Now, some of the pb31img.zip files I've come across don't even try to install. This includes signed and unsigned .15 img files. Currently these are the new settings to the phone:
Bootloader: unlocked, s-on
hboot 1.07.0000
radio - 2.15.10.12.20
Image version: 4.08.605.15
The last option I can think of is to try using fastboot, but won't that essentially do the same thing? If you think fastboot is the way to go, can u link me or give me some basics on using it. Obviously I used it for unlocking the bootloader so it can't be that complicated.
Are there any other ideas or should I give up on my Dinc? Looking forward to hear what you think. Thanx.
-Nevin

somebody recommended you install TWRP and install a stable Jellybean ROM. Did you try that?