Related
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
ok, i thought the 1.47 OTA would download to my sdcard...it didn't. But i wasn't quite convinced it was on the device so i clicked "install update" w/ the sd card pulled...as soon as it began i pulled the battery. Now, whenever i boot it automatically goes straight to the black update screen (with the hard drive icon) trying to install the OTA !!!
How can i stop this and boot normally back into 1.32??? w/o forcing the 1.47 update!!
(i am unrooted btw) THANKS FOR ANY TIPS!!
adeyo said:
ok, i thought the 1.47 OTA would download to my sdcard...it didn't. But i wasn't quite convinced it was on the device so i clicked "install update" w/ the sd card pulled...as soon as it began i pulled the battery. Now, whenever i boot it automatically goes straight to the black update screen (with the hard drive icon) trying to install the OTA !!!
How can i stop this and boot normally back into 1.32??? w/o forcing the 1.47 update!!
(i am unrooted btw) THANKS FOR ANY TIPS!!
Click to expand...
Click to collapse
I could be wrong but i dont think there is a way to stop it if unrooted. in good news even if you let it update to 1.47 you can still root (just dont go to 2.2) so not sure why you would want to stay at 1.32
omegasun18 said:
I could be wrong but i dont think there is a way to stop it if unrooted. in good news even if you let it update to 1.47 you can still root (just dont go to 2.2) so not sure why you would want to stay at 1.32
Click to expand...
Click to collapse
thanks. i hadn't backed up everything yet. also, i had unrevoked so i hope this doesn't drop my pri down to 1.32 from 1.40 (i guess i lose free tethering too)...other than those things, i was just about to root and get froyo!
so, you don't think i can boot into recovery and wipe something before it completely installs upon reboot??
adeyo said:
thanks. i hadn't backed up everything yet. also, i had unrevoked so i hope this doesn't drop my pri down to 1.32 from 1.40 (i guess i lose free tethering too)...other than those things, i was just about to root and get froyo!
so, you don't think i can boot into recovery and wipe something before it completely installs upon reboot??
Click to expand...
Click to collapse
Not without root. Whatever is trying to run is almost certainly on /system, which is not writable without root access. Just let it go and root after that.
Also, NEVER PULL THE BATTERY WHILE THE SYSTEM IS FLASHING! That's a real good way to end up with a half-written (bricked) ROM.
Just let it update to 1.47 and then use Simple Root or whitslacks method to gain root again. Then flash back to 1.32 if you so desire. As mentioned before, do not allow it to update to 2.2 as there is not yet a method to gain root for the OTA 2.2.
Furthermore, check the dev forum for the PRI issue. They need someone with an unrooted OTA 1.47 with a PRI 1.40_003. You could be everyone's hero.
Sent from my PC36100 using XDA App
SilverZero said:
Not without root. Whatever is trying to run is almost certainly on /system, which is not writable without root access. Just let it go and root after that.
Also, NEVER PULL THE BATTERY WHILE THE SYSTEM IS FLASHING! That's a real good way to end up with a half-written (bricked) ROM.
Click to expand...
Click to collapse
wow...thanks!!! i hope i didn't screw anything up! i'm letting it finish up now...EHHH...THIS IS WIERD??? this time i was just going to let it flash and so i went ahead and plugged in my usb, but instead of flashing it went to the boot animations and back to my phone????...i'll check to see if i screwed anything up??
**EDIT: wow, it prompted me to install the update again, looks like i am back. I will try cancelling installation this time... (it gives me a discard update option) i click yes, it says "this will wipe the update from your phone" ....so I guess all is well!!!!
adeyo said:
wow...thanks!!! i hope i didn't screw anything up! i'm letting it finish up now...EHHH...THIS IS WIERD??? this time i was just going to let it flash and so i went ahead and plugged in my usb, but instead of flashing it went to the boot animations and back to my phone????...i'll check to see if i screwed anything up??
Click to expand...
Click to collapse
It probably tried to flash, found nothing there, and removed the instructions from the boot process. So you may have gotten away with it. Check your software version in Settings - About Phone to see where you ended up. Also, is your SD card still out of the phone? It may be waiting to spring back on you when you put it back in, but just let it go anyway if that's the case.
sombdy said:
Just let it update to 1.47 and then use Simple Root or whitslacks method to gain root again. Then flash back to 1.32 if you so desire. As mentioned before, do not allow it to update to 2.2 as there is not yet a method to gain root for the OTA 2.2.
Furthermore, check the dev forum for the PRI issue. They need someone with an unrooted OTA 1.47 with a PRI 1.40_003. You could be everyone's hero.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
everyone's hero?? haha...that PRI thread is why i was trying to download the 1.47 OTA in the first place anyway, i am still at 1.32 now. do you have a tip as to how i can help them??
SilverZero said:
It probably tried to flash, found nothing there, and removed the instructions from the boot process. So you may have gotten away with it. Check your software version in Settings - About Phone to see where you ended up. Also, is your SD card still out of the phone? It may be waiting to spring back on you when you put it back in, but just let it go anyway if that's the case.
Click to expand...
Click to collapse
ahh...maybe you are right? maybe it was a phantom flash anyway b/c i never put my sd card back in, also, i did delete that update.zip that was on there anyway...so i'll see if anything happens when i put the card back in. my settings show 1.32 still
**UPDATE: no attempt to reload/reboot system with update after sd card is in. Looks good!
Then you're the **** of the walk!
now, should i root and then go straight to 2.2 or go to 1.47 first?? what is the best way to keep my PRI 1.40_003 intact????
adeyo said:
now, should i root and then go straight to 2.2 or go to 1.47 first?? what is the best way to keep my PRI 1.40_003 intact????
Click to expand...
Click to collapse
I don't think you can, that's why there's a bounty out for it. When you root, your PRI will change to 1.34 because you have to use the engineering ROMs. Correct me if I'm wrong.
You don't want to just upgrade to 2.2 OTA . . . unless you WANT to block root until somebody finds a way to root Froyo on the Evo.
PRI aside, you should probably root from 1.32, no reason to go up through 1.47 and you'll avoid the "Main Version is Older" problem.
SilverZero said:
I don't think you can, that's why there's a bounty out for it. When you root, your PRI will change to 1.34 because you have to use the engineering ROMs. Correct me if I'm wrong.
You don't want to just upgrade to 2.2 OTA . . . unless you WANT to block root until somebody finds a way to root Froyo on the Evo.
PRI aside, you should probably root from 1.32, no reason to go up through 1.47 and you'll avoid the "Main Version is Older" problem.
Click to expand...
Click to collapse
great, thanks! i will root and go straight to 2.2. I guess there is no known way to keep PPI 1.4 and actually root. ...it just gets to me that unrevoked users can keep PRI 1.40 and full rooters can't...there should be some way!
adeyo said:
great, thanks! i will root and go straight to 2.2. I guess there is no known way to keep PPI 1.4 and actually root. ...it just gets to me that unrevoked users can keep PRI 1.40 and full rooters can't...there should be some way!
Click to expand...
Click to collapse
I wasn't aware of that, but the reason is probably that Unrevoked users can't flash any ROMs that would update the PRI anyway.
SilverZero said:
I wasn't aware of that, but the reason is probably that Unrevoked users can't flash any ROMs that would update the PRI anyway.
Click to expand...
Click to collapse
oh...what ROMs wouldn't update the PRI? My friend is an unrevoked 2?3? user and i know he has tried a few different ROMs ...one of them being DamageControl, most recently. He has also tried a few different kernels.
***EDIT: Here are the steps he took:
1) Started w/ Unrevoked 1
2) OTA'd 1.47
3) Unrevoked 3 from 1.47 (then was able to flash froyo rooted roms
4) He still doesn't have nand access, but he flashed the following roms: Fresh (most recent), Burnt Droid, the odexed Stock "FINAL" by netarchy, and DamageControl. Burnt droid didn't take, but neither did DamageControl at first, but now works fine. His recovery is ClockworkMod.
So before I decided to flash unrevoked forever I was happily flashing through roms
without any worries..maybe flip flopping between the GB and Froyo without going above
And beyond a standard 2x wipe had something to do with this?
I go back to the 6.11 radio from 5.6 so I can flash the unrevoked forever. I flash the radio,get
rid of the pmb file and put URF in the root of SD and flash it in recovery,no error messages
and next I boot a custom splash,all is well..
I decide to go back to the new radio leak
I realize hours later that I can't send or receive txt or make calls;big red basically was
Rejecting my phone. After much searching I give up
I turned s back on and gave em a ring,basically I had to use the dialer to open up the radio and change like one #,then all was gravy with service. I'm now happily re rooted and running magnolia(i love this Rom)
Sorry it was so long winded but,what did I do wrong?
Did URF screw the radio?
Do I even need to use URF?
Was it the ROM switching?
pastalero said:
So before I decided to flash unrevoked forever I was happily flashing through roms
without any worries..maybe flip flopping between the GB and Froyo without going above
And beyond a standard 2x wipe had something to do with this?
I go back to the 6.11 radio from 5.6 so I can flash the unrevoked forever. I flash the radio,get
rid of the pmb file and put URF in the root of SD and flash it in recovery,no error messages
and next I boot a custom splash,all is well..
I decide to go back to the new radio leak
I realize hours later that I can't send or receive txt or make calls;big red basically was
Rejecting my phone. After much searching I give up
I turned s back on and gave em a ring,basically I had to use the dialer to open up the radio and change like one #,then all was gravy with service. I'm now happily re rooted and running magnolia(i love this Rom)
Sorry it was so long winded but,what did I do wrong?
Did URF screw the radio?
Do I even need to use URF?
Was it the ROM switching?
Click to expand...
Click to collapse
To go to s-off all you do is flash the s-off file in clockwork, there is no other steps... Maybe I'm not understanding your problem.
But flashing radios can cause the problems you had.
Well from what I'm reading,after rooting with unrevoked I don't need URF...it says s-off
In hboot as is. My main concern is what could I have done to loose service to my phone.
Was it flashing the radio back and forth?
Was it from flashing too many roms and not wiping properly?
Was it because I ran Unrevoked Forever when I didn't need to?
I just want to make sure that something like this does not happen again
pastalero said:
Was it from flashing too many roms and not wiping properly?
Was it because I ran Unrevoked Forever when I didn't need to?
Click to expand...
Click to collapse
I would say maybe, but I also have noticed that after I flash a radio my phone won't connect to verizon. A couple of Airplane Toggles here and there kicks it back up....I always thought it was these CM7 nightlys
Or maybe I have a different problem all together and I'm just adding to the mess!
What I'm wondering is,do I even need to run unrevoked forever if I ran unrevoked? It says s-off in the bootloader. Is it possible that its a bug in URF¿
Unrevoked is supposed to be a one step program, roots the phone and ads s-off so there is no reason to run Unrevoked Forever and doing so could possibly mess up your phone. The instructions for Unrevoked were very clear about this when I used it last. And yes flashing radios can result in your phone not working thats why they usually come with a discalimer, flash at your own risk.
Might be noobish advice, but have you tried *228?
My wife got her replacement Inc2 today after the one she got last week just died. She was on Froyo so I might of.. swapped her phones.. anyways, I rooted, went to the bathroom and the stupid ota ran I guess because when I came back the phone was on GB 2.3.3 however my boot screen shows S-OFF. Can anyone help me to verify that S-OFF is indeed still off. I can post any screen shots etc.. I am still a noob when it comes to the Inc2.
If your boot screen says S-Off, you are S-Off
Sent from my stock, bloated ADR6350 using XDA Premium App
Did you flash clockworkmod recovery when you rooted? I didn't think the OTA would take if you had a custom recovery. In any event, since you're still s-off, you're fine.
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
kujayhawks77 said:
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
Click to expand...
Click to collapse
Alpharev changed ur hboot to a higer version than the one in the OTA.. this is why it kept you S-OFF.. if I'm wrong someone correct me.
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
kujayhawks77 said:
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
Click to expand...
Click to collapse
No. stock hboot is .97. alpharev bumped you up to 1.something.. idk I used XTC clip.. since your hboot is newer than the OTA.. it keeps you S-OFF, pretty smart by alpha.
So does this open a gateway to first root in Froyo and then go gingerbread and retain the root?
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Now when I use the term "gateway" I say this loosely because it doesn't fix anything for anyone who is already on GB. If indeed this works, it would only work for a small percentage who get Froyo and don't flash clockwork before running the OTA.
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
tnez said:
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
Click to expand...
Click to collapse
2.1??? I think you are mistaken, sir
beenz said:
2.1??? I think you are mistaken, sir
Click to expand...
Click to collapse
He was mistaken cause it is sense 2.1 but android 2.2
Sent from my Incredible 2 using XDA Premium App
kujayhawks77 said:
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Click to expand...
Click to collapse
I've been wondering about this. I got my Dinc2 early July and I'm still on stock, unrooted Froyo. Somehow the OTA update to GB hasn't hit yet. Could I run ApharevX to get S-off and stop there for now? I am happy with bloated stock for the time being and want to be able to receive OTA updates, but would like to have the option down the road to add Clockworkmod and flash custom ROMs. From kujayhawks experience it seems that this should be possible.
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
P.S. First post, though I've been lurking around for a while. Great forum/community.
xenakis said:
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
Click to expand...
Click to collapse
It appears from reports that S-off stays after the OTA to 2.3, so yea, that would seem to be the case.
If you turn S-off with AlphaRev, you might want to just go ahead and install Clockwork recovery at the same time. Doing so won't root or install SuperUser or anything, but you would be able to then backup your phone and be ready to flash if you wanted.
If you install clockwork recovery you won't be able to receive OTAs though, just keep that in mind. You can flash back to the stock recovery, but unless you are familiar with ADB, it won't necessarily be an easy process.
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