Successfully unrooting? - EVO 4G Q&A, Help & Troubleshooting

So I've had my evo for 2 days and am already having trouble resisting rooting it. However, do we know that unrooting through the RUU is 100% successful. There have been some issues with the evo (like the screen peeling up) and I wanna make sure I can exchange if I need to. (although I wouldn't HAVE to unroot to exchange, it provides some peace of mind). So anyway, I remember on the hero there was the all too common error 110 which I ran into and bricked my first one before a fix came up. So anyone successfully RUUd back to stock? Any errors anyone has heard of?

i did 2 with no problem 1 using the ruu with thye computer the other using the zip from the ruu and flashing it as a pc36img.zip file. both work 100%

red man said:
i did 2 with no problem 1 using the ruu with thye computer the other using the zip from the ruu and flashing it as a pc36img.zip file. both work 100%
Click to expand...
Click to collapse
Awesome, thank you. Do you or anyone else know if there are different RUUs. I bought mine a few days ago which came pre loaded with the firmware update, I remember there was a 1.29 and a 1.56 RUU floating around for the hero and you had to use what came pre loaded on your phone. Is this the same case, or does the RUU contain this update already and will it just work on all evos?

Go to this page. It has the stock RUU and the RUU with the first OTA update in the first section.

Dave2582 said:
Go to this page. It has the stock RUU and the RUU with the first OTA update in the first section.
Click to expand...
Click to collapse
Thank you sir! I am correct in assuming it was shipping with the OTA if I wasn't able to find any firmware updates through the phones settings right?

Well, I picked up the EVO for my dad on launch day, and when they booted it up in front of me, the screen was already showing that there was an update available. So the phone that you just got, already had that particular RUU on it.

Dave2582 said:
Well, I picked up the EVO for my dad on launch day, and when they booted it up in front of me, the screen was already showing that there was an update available. So the phone that you just got, already had that particular RUU on it.
Click to expand...
Click to collapse
Sounds good. Thanks again.

Related

Evo corrupted after Monday OTA update

I downloaded the OTA update and it killed my phone. It is a non rooted stock phone.
I can access the bootloader so its not fully bricked. It just sits there on the first screen like its having issues with its rom.
The info on the bootloader screen.
Supersonic EVT2-2 Ship S-On
HBOOT-0.79.0000
MICROP=041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.05.00.06.10
APR 14 2010,15:14:34
I roamed around and tried several of the rooting tools and such but nothing worked. The .exe files to set the thing back wont work.
Just wondering if I am SOL atm or there some way I can fix this?
What happened when you tried using the RUU? Did you try using the zip file?
I tried all 3 of the current .exe files on the roms page. All of the give bootloader veerson error. The .zip files most of them give a older verson error.
The RUU_Supersonic_1.32.651.6 .zip does nothing. Gives no error, no options just back to the bootloader.
Least the bootloader works. If there is a new rooter out maby i can fix it myself because the sprint dealers can not do anything.
you can have them fill out in the paperwork to get you another one..
its still under 30 day warranty
but so far your SOL.
there are no root methods for the OTA.
so either way, you have to wait it out.
CYBERxNUKE said:
you can have them fill out in the paperwork to get you another one..
its still under 30 day warranty
but so far your SOL.
there are no root methods for the OTA.
so either way, you have to wait it out.
Click to expand...
Click to collapse
Yea I got it from radioshack. They know whats up and when they get a phone im getting it replaced. I do not want to root it, i just want to a working state. Yet if i get one with a old rom/bootloader on it... hell ya im rooting it.
If anyone has any ideas on how to simply flash it to stock, like a ligit htc/sprint way im all ears.
Well I was able to fix it using the rru exe that was posted yesterday. \o/
firefoxinc said:
Well I was able to fix it using the rru exe that was posted yesterday. \o/
Click to expand...
Click to collapse
got a link you could throw my way of what you used?
My phone isn't bricked, but when I try to use the sprint .exe RRU, once it goes into boot loader mode it gives me some error about version.
I don't know if my phone is only 1/2 bricked or what, or if it's just an issue with the latest over the air update screwing things up. I never flashed any new roms, just did Unrevoked 1 method before I did the OTA. I would guess my phone is 100% stock at this point.
accelerus said:
got a link you could throw my way of what you used?
My phone isn't bricked, but when I try to use the sprint .exe RRU, once it goes into boot loader mode it gives me some error about version.
I don't know if my phone is only 1/2 bricked or what, or if it's just an issue with the latest over the air update screwing things up. I never flashed any new roms, just did Unrevoked 1 method before I did the OTA. I would guess my phone is 100% stock at this point.
Click to expand...
Click to collapse
There is no "half bricked" a bricked phone is one that no longer works appropriately. You've got a brick instead of a phone because it doesn't work.
If you do the OTA, or have done the OTA, you cannot root and cannot restore to factory settings. I think the exe the OP is referring to is of the OTA update, ie, he won't be able to root.
If you can boot to Android, you're phone is fine, just not rootable.
accelerus said:
got a link you could throw my way of what you used?
My phone isn't bricked, but when I try to use the sprint .exe RRU, once it goes into boot loader mode it gives me some error about version.
I don't know if my phone is only 1/2 bricked or what, or if it's just an issue with the latest over the air update screwing things up. I never flashed any new roms, just did Unrevoked 1 method before I did the OTA. I would guess my phone is 100% stock at this point.
Click to expand...
Click to collapse
Here is to the thread
http://forum.xda-developers.com/showthread.php?t=717024

[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][RUU] extracting rom.zip file and flashing not rooted and s-on

Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
To be honest, I would say just wait for the OTA, Verizon themselves have confirmed it has been/will be released today 8/27. Then there will be no worrying, since you don't want root this would be the best way.
boomertwo said:
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
Click to expand...
Click to collapse
I'm sorry this has nothing to do with what you're asking, I've read, and don't know sorry man, but I do have a quick question for you. I see you have never rooted, or maybe or have, I thought maybe you hadn't for some reason, but anyway, I see you HBOOT it .77, how long have you had your phone since?
Yes I had rooted the phone recently for about 2 weeks then it got messed up but thanks to an unrevoked member I was able to recover the phone. It wasn't bricked or anything but some how the NAM was messed up which prevented me from using *228 to update roaming or my ability to activate the phone after a factory reset. I do remember it having hboot .79 before rooting though.
Update: I verified that the hboot in the stock restore img file I used had only hboot 77 in it and not 79. This means I downgraded to 77 without knowing it at first. (From the threads I have read it is stated that .77 and .79 are interchangeable so I don't think I need to worry about it when the ota comes I hope..)
I've had it for about 3 months now so I'm out of the return policy and I do like the phone and have no intention of returning it.
After trying root out for those 2 weeks I found that for me I didn't really gain anything that seemed worth it for my personal needs.
Also I like to tinker with stuff but since I'm in a 2 year contract I rather not take the risk of bricking it and having to pay for the next 2 years for service I can't even use due to my own fault of breaking the device.
Right now I'm just wondering if it is safe to apply the file that can be found in the ruu without root and without breaking the device since it has the same build number and radio number as the update that verizon has stated on the update page.
.77
I am on my third incredible, and all 3 shipped to me with v.77. Last one shipped was 8/9 (wow, maybe this one is a keeper).
jdmba said:
I am on my third incredible, and all 3 shipped to me with v.77. Last one shipped was 8/9 (wow, maybe this one is a keeper).
Click to expand...
Click to collapse
were these all brand new phones, refurbs..?
To my understanding of this whole .77, .79 HBOOT is that these two are interchangeable and doesn't matter which one you have. I was just curious because at first I used the RUU that gave me software 1.22.605.0 and the latest is 1.22.605.2 and I never got an OTA update for the latest 2.1. but I think this is normal since the servers are doing the new thing.
and from what I think, if you had .77, and got the OTA for the latest 2.1 that came out a while ago, it kept the .77, but if you did the latest 2.1 through the RUU on ur computer instead of OTA it updated the HBOOT to .79 as well.
This is how it was with the Droid Eris with the leaks and stuff which blocked you out of root.
...
BlazeD OnE said:
were these all brand new phones, refurbs..?
Click to expand...
Click to collapse
Phone # 1 - New ... would get hotter and hotter (even when not in use) until it would enter a reboot cycle. It would also reboot randomly during the day.
Phone # 2 - Refurb ... got it with a bad speaker, but otherwise it worked perfectly.
Phone # 3 - Refurb ... still going.
boomertwo said:
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
Click to expand...
Click to collapse
in theory that should work.
k.electron said:
in theory that should work.
Click to expand...
Click to collapse
Well I took the plunge and can confirm that the method in my original post does work and without a hitch(For me at least.)I did this after reading another question thread that had a guy basically asking the same thing and was recommended just to follow to step 6. I cannot link to anything yet so I will just give you the thread title that is located in the Q&A section of this forum for the droid incredible.
Thread Title: "[Q] Applying RUU update to stock phone"
The phone did however reboot the bootloader and put me into fastboot. I did not pull the battery but instead selected bootloader again and it continued the update on its own.
I'm successfully not root and s-on with android 2.2(HTC stock)
Hboot .92
Stock Recovery.
*Before you say it.. I know I'm now not able to get root till unrevoked or another dev team releases new tools for this version. I did this by choice*
*I in no way will recommend anyone to do this and will not take responsibility for your phone being turned into a paper weight* < You have been warned..
Sooooo.. anyone want to clarify how to extract rom.zip from the RUU please?
Just download the extracted ROM. It's on page 6 or 7 in the RUU thread.
NinjaRicky said:
Sooooo.. anyone want to clarify how to extract rom.zip from the RUU please?
Click to expand...
Click to collapse
did you get it?

[Q] EVO 4g Unroot - I have read everything on here about it and am still stumped!

I rooted my EVO last night and with my luck, the earpiece speaker blew today. I have to take it in for an exchange.
Here is my current situation:
I ran unrevoked-forever-son.zip so my phone is SON right now.
My current radio version is 2.15.00.09.01
My current image version is 3.29.651.5
I have hardware version 3
Android 2.2
Everything is completely functional other than the earpiece speaker.
Here is what I did:
Last night:
I used Unrevoked 3.21 to root it. It rooted fine. I installed WiFi Tether and tested it and it worked great. That is the only app I have installed since the root.
Today:
Speaker crapped out on me during the day.
I came home from work and followed the instructions here: www(dot)thedroiddemos(dot)com/forum/viewtopic.php?f=18&t=13&p=115#p115
The SON program ran fine. But when I tried to load the PC36IMG.zip file from the SD card, it responded with a "main is older" error and would not install it.
So then, I went here: forum(dot)xda-developers(dot)com/showthread.php?t=721843. It told me to go to shipped-roms.com to get files that would automatically unroot my phone.
I tried the earliest one and it got all the way to the end and gave me error 140: Bootloader version error. I got the same thing with the second and third oldest.
Both of the most recent files for the the "Waiting for bootloader" error and froze, giving me the dreaded 170 USB error.
I also tried letting it get to the HTC screen and then restarting the RUU program as directed in the XDA post mentioned above. It always led to the 170 error.
I am wits end. I have a 7 day old phone that I can't use until I somehow unroot it and exchange it.
Thanks in advance for your help.
Are you returning it to Sprint or directly to HTC? Chances are, if you just put a stock ROM on it & just use adb or Root Explorer to remove SuperUser.apk they're not even going to realize it's rooted.
Also, this really goes in Q&A, not Development.
Welcome to the forums!
I am returning it to Sprint. Sorry about putting this in the wrong place. I will move it over to Q&A immediately. I was trying to put a stock ROM on it with the above procedures. I just wasn't able to do it.
Thanks for the advice.
Go to this thread and run the RUU. You are unrooted and completely reset. Just make sure you use the S-ON tool from unrevoked.
http://forum.xda-developers.com/showthread.php?t=800582
swillardo said:
I am returning it to Sprint. Sorry about putting this in the wrong place. I will move it over to Q&A immediately. I was trying to put a stock ROM on it with the above procedures. I just wasn't able to do it.
Thanks for the advice.
Click to expand...
Click to collapse
No problem, hope it works out for you. Let us know how it goes
Cosine,
Do I want to run the S ON tool before or after I do the RUU? I am at S on status now.
Thanks for the help.
I will do that and thanks again.
I tried Cosine's RUU and I am still getting the 170 USB error when I run it. Any ideas?
Thanks.
swillardo said:
I tried Cosine's RUU and I am still getting the 170 USB error when I run it. Any ideas?
Thanks.
Click to expand...
Click to collapse
Do you have HTC Sync installed? It looks like that error was coming up for users that didn't have the latest version / wasn't installed.
No, I uninstalled it to do the root. I am installing it again now. Thank you.
If you really want someone to cover everything good. I've got all night so just let me know. If not, good luck.
Sent from my PC36100 using XDA App
Well, I reinstalled HTC Sync and the ROM flashed just fine. This ROM reflashed everything. There is no evidence of root whatsover! I did have to set the entire phone back up, but that was well worth it! Thanks to Veritas06 and Cosine for helping me out.

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

Categories

Resources