I ran unrevoked 3 and tried a few things and decided it was not for me, I ran the Sprint RUU and it all worked fine. But under the bootloader screen it still shows S-off. Can I renable it?
venom_762 said:
I ran unrevoked 3 and tried a few things and decided it was not for me, I ran the Sprint RUU and it all worked fine. But under the bootloader screen it still shows S-off. Can I renable it?
Click to expand...
Click to collapse
Sry to hear that. See if THIS helps.
oooh that sucks. you have to re-root (you can just use unrevoked 3 again), then put the unrevoked s-on tool (found in the FAQ section of this thread http://unrevoked.com/rootwiki/doku.php/public/forever ) on the root of your sdcard. boot into recovery, and flash it as you would a rom. then check bootloader to make sure it is s-on. if it is, run the ruu again.
just curious, why dont u like root?
I just tried to re-run Unrevoked 3 and it will not reconnect, the tool just says waiting for device.
And I don't like root because of too much power.
venom_762 said:
I just tried to re-run Unrevoked 3 and it will not reconnect, the tool just says waiting for device.
And I don't like root because of too much power.
Click to expand...
Click to collapse
usb debugging is probably not on. try that.
too much power? like too much battery consumption (wtf?) or too much power over the phone?
too much stuff for me to f-with.
venom_762 said:
too much stuff for me to f-with.
Click to expand...
Click to collapse
hahah ok then. so ya turn debugging on (settings, applications, development, usb debugging) and put the phone on charge only and run unrevoked.
ok I found it, I was trying to root from the hboot screen.
Can't I just wait for the OTA from sprint and that would just turn S-back on?
venom_762 said:
Can't I just wait for the OTA from sprint and that would just turn S-back on?
Click to expand...
Click to collapse
no, it wouldnt turn s-on, and you might not even be able to accept it. if you are having a hard time using unrevoked, seeing as your rom no longer has root permissions, i can lead you through manually flashing amon-ra recovery to your phone and you can flash ur s-on from there.
I just got it to root again using Unrevoked 3 and restored to right after my first root. I should be able to now install the S-on tool and install it from the recovery menu?
venom_762 said:
I just got it to root again using Unrevoked 3 and restored to right after my first root. I should be able to now install the S-on tool and install it from the recovery menu?
Click to expand...
Click to collapse
That is correct. Also, I'm pretty sure that since you were still S off, you could've just flashed a pc36img of a recovery from the bootloader, flashed the s on tool, and then ran RUU.
Edit : just saw that dk already suggested that. Sorry.
Sent from my PC36100 using XDA App
Update I figured it out and ran the S-on tool, booted into the bootloaded and verified it was back on. I then ran the RUU and it should be fully stock and ready to install the OTA?
I just don't want to be that guy does not or has a failed update when the official OTA is out.
Anyone? I dying to know if I can install the next ota.
venom_762 said:
Anyone? I dying to know if I can install the next ota.
Click to expand...
Click to collapse
If you're back to stock, s on, and aren't on the latest OTA, then yes, you can take the OTA if you'd like to. That will bring you up to the latest software update.
Sent from my PC36100 using XDA App
Great I am relieved, I just wondered if when its pushed out if I have problems seeing it. Thank you guys for all of your help.
venom_762 said:
Great I am relieved, I just wondered if when its pushed out if I have problems seeing it. Thank you guys for all of your help.
Click to expand...
Click to collapse
sorry for leaving you in the dark for a while. that was one crazy day. but i'm at my comp now so i can help (not that there's anything left to do).
if i were you, i'd double check you are fully unrooted. boot into bootloader, and make sure you are s-on. then boot into recovery and make sure you have no custom recovery, just the stock htc one. also make sure your rom has no superuser app installed. if not, you are all good.
No prob man, I booted into the bootloader and S-On is back on and then tried to boot into recovery, a black screen with a red triangle came up so I assume there's no recovery installed. There is also no superuser Icon in the app draw.
The main reason I returned to stock is,is that this is my primary and only phone. I plan on getting the Nexus S when it come to sprint so I will see you guys again. That way if I bork the NS I got my trusty evo to activate.
Again thank you all for the help.
venom_762 said:
No prob man, I booted into the bootloader and S-On is back on and then tried to boot into recovery, a black screen with a red triangle came up so I assume there's no recovery installed. There is also no superuser Icon in the app draw.
The main reason I returned to stock is,is that this is my primary and only phone. I plan on getting the Nexus S when it come to sprint so I will see you guys again. That way if I bork the NS I got my trusty evo to activate.
Again thank you all for the help.
Click to expand...
Click to collapse
ok ya ur totally unrooted. enjoy the cage some prefer it there.
just saying, the evo is freaking hard to brick.
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
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Is the phone s-off?
Sent from my PC36100 using XDA App
badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
animal7296 said:
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
Click to expand...
Click to collapse
Are either of these rootable yet?
and can someone explain what S-on and off means?
badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
1. 2.02 is rootable 2.10 is not and is the newest one.
2.0 S-ON means you can not flash roms s-off means you can. It is the security of the phone kind of.
If you can not get into bootloader then you can try running the oldest ruu and then the next. It wont hurt the phone at all (I just did it today) it will just give you an error and reboot the phone.
pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Sent from my PC36100 using Tapatalk
badutahboy said:
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
Click to expand...
Click to collapse
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
luckylui said:
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Click to expand...
Click to collapse
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Sent from my PC36100 using Tapatalk
tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
True this, but when i did it i was at 0.76.2 and now screw at 2.10 cause it updated all the way n i didnt want to do that.. Got lost in the tangle haha
Sent from my PC36100 using Tapatalk
tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
Yea, I heard about this in the IRC; too bad these guys can do that... unfortunate; but I'm sure the Unrevoked team will have a fix soon enough.
luckylui said:
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Click to expand...
Click to collapse
Good luck with Sprint; I don't know how helpful they're going to be, but you never know...
@luckylui and animal7296, check out the 2.02/2.10 rooting thread again, it seems they got something working. Good luck.
badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
There actually is a way to downgrade without rooting, all you need to do is flash the mtd-eng.img file to your misc partition as explained in toast's rooting part 2 thread. After you do that it will let you flash any ruu that is compatible with your phone
Sent from my PC36100 using XDA App
Long story short, my microphone broke on my old EVO, so I unrooted to take it back. I got a new one and tried to root it again used UnrEVOked3 again and it not work. Recovery does not work, there is no superuser options. On the hboot menu it does say S-OFF. I have tried to reuse the UnrEVOked3 and it will not recognize my device. I am just looking for some form of help so that I can get my phone rooted so I can get CM7.
Thanks
have you tried to dl superuser (the one from Chains) from the market?
Just did, still will not let me use root apps or anything, only difference is now I have the app.
Did you reboot?
Use this thread as a reference to completely unroot your phone, then retry unrEVOked...
http://forum.xda-developers.com/showthread.php?t=780141
mrpurplehawk said:
Long story short, my microphone broke on my old EVO, so I unrooted to take it back. I got a new one and tried to root it again used UnrEVOked3 again and it not work. Recovery does not work, there is no superuser options. On the hboot menu it does say S-OFF. I have tried to reuse the UnrEVOked3 and it will not recognize my device. I am just looking for some form of help so that I can get my phone rooted so I can get CM7.
Thanks
Click to expand...
Click to collapse
Well, since you show S off, I'd just flash a PC36IMG of Amon Ra recovery, and then flash a new rom. I've seen people report of Unrevoked having a difficult time for whatever reason. I've never had a hiccup with it, but taht doesn't matter. Perhaps there was something on your computer causing you issues, such as HTC sync, PDAnet, an anti virus program, etc. Anyways, download this PC36IMG, put it on the root of your SD card. Shut your phone off, then boot to the bootloader. It'll ask you to update, and select vol up to say yes. Once it's done, you can boot into recovery and flash away. That should all work just fine, because you're S off already.
Try what he ^^^ said first...if that still fails, try what I said lol
what h-boot do u have and were u runing 3.70 when u did unrevoked 3 cause it should not work at all u need tun another method to root
lcorona056248 said:
what h-boot do u have and were u runing 3.70 when u did unrevoked 3 cause it should not work at all u need tun another method to root
Click to expand...
Click to collapse
Not sure what you're talking about. I think your info is outdated. Unrevoked works with all hardware and software versions for the Evo (3.70) included. I've used it more than a few times. Unrevoked was updated months ago, like right after Christmas.
k2buckley said:
Not sure what you're talking about. I think your info is outdated. Unrevoked works with all hardware and software versions for the Evo (3.70) included. I've used it more than a few times. Unrevoked was updated months ago, like right after Christmas.
Click to expand...
Click to collapse
cool i didnt know that i still have the first production hardware 002 so no need for me to keep up to date.. but i will keep that in mind when i get my next one thanks bro
i would do what k2buckley said and run amon ra recovery should help u a ton
that worked, thank you so much!!!
mrpurplehawk said:
that worked, thank you so much!!!
Click to expand...
Click to collapse
You're welcome man, glad it worked for ya!
' Evening, All! I'll get right to it. I have to send my EVO back to HTC because my USB port is broken, and I can't charge or sync my phone. I "installed" an older Shipped ROM (PC36IMG) via HBOOT. I still see s-off. So, I thought I would try the UnRevoked S-ON tool. Well, when I try to reboot into "recovery" via hboot, I get the picture of the phone with the red exclamation point/triangle. Am I unrooted? I REALLY need my phone to show "S-ON". Am I going to have to root my phone again, and use the UnRevoked S-On tool prior to the PC36IMG? I don't have the RUU option, seeing how my USB port is broken. Very frustrating/frustrated. Thank you.
masterninja said:
' Evening, All! I'll get right to it. I have to send my EVO back to HTC because my USB port is broken, and I can't charge or sync my phone. I "installed" an older Shipped ROM (PC36IMG) via HBOOT. I still see s-off. So, I thought I would try the UnRevoked S-ON tool. Well, when I try to reboot into "recovery" via hboot, I get the picture of the phone with the red exclamation point/triangle. Am I unrooted? I REALLY need my phone to show "S-ON". Am I going to have to root my phone again, and use the UnRevoked S-On tool prior to the PC36IMG? I don't have the RUU option, seeing how my USB port is broken. Very frustrating/frustrated. Thank you.
Click to expand...
Click to collapse
You need to reflash recovery. Since you're still S off, that's very easy and quick. Download the PC36IMG I attatched (it's Amon Ra V2.3 recovery), place it on your SD card. Then boot to the bootloader, and say yes to the update. Once it's done flashing, you'll have recovery back. Then boot to recovery, and flash the Unrevoked S on tool. Then go back to the bootloader, and confirm that it worked, and that you're S on. Once done, run the RUU again, and that will flash you back to stock, and get rid of your custom recovery. You'll then be back to stock, S on, and stock recovery image.
Thank you! I will do this, now.
masterninja said:
Thank you! I will do this, now.
Click to expand...
Click to collapse
You're welcome. You should be good to go with that, let me know how you make out.
Alright! I think it worked! Although, instead of installing the "shipped ROM .zip" I had, I booted up the phone and was given the option to download and install the official OTA update. So, I did. And my bootloader says "S-ON"! Thanks! I've been at this ALL day and my head was a-spinnin'! It was time for "outside" help. I am truly grateful. Thank you!
masterninja said:
Alright! I think it worked! Although, instead of installing the "shipped ROM .zip" I had, I booted up the phone and was given the option to download and install the official OTA update. So, I did. And my bootloader says "S-ON"! Thanks! I've been at this ALL day and my head was a-spinnin'! It was time for "outside" help. I am truly grateful. Thank you!
Click to expand...
Click to collapse
You're welcome. Glad to have helped. Sometimes all ya gotta do is ask!
k2buckley said:
You're welcome. Glad to have helped. Sometimes all ya gotta do is ask!
Click to expand...
Click to collapse
Asking is half the battle.
Hello all, I'm in serious need of some help, I've been working at this for a couple of hours now and can't figure it out, so I turn to you, o mighty forum.
I have an HTC Incredible and I'm currently running MIUI and clockwork recovery mod. I've been having all kinds of problems lately, and I want to just delete everything on my phone and get it back to stock, the way it was when I turned it on for the first time out of the box. If anyone can help me get this done I will be forever grateful, because I'm at my wits end. I have no idea what to do, or where to start, so if anyone could provide me with a step-by-step instructions, I would be very happy.
Thank you
bobrea said:
Hello all, I'm in serious need of some help, I've been working at this for a couple of hours now and can't figure it out, so I turn to you, o mighty forum.
I have an HTC Incredible and I'm currently running MIUI and clockwork recovery mod. I've been having all kinds of problems lately, and I want to just delete everything on my phone and get it back to stock, the way it was when I turned it on for the first time out of the box. If anyone can help me get this done I will be forever grateful, because I'm at my wits end. I have no idea what to do, or where to start, so if anyone could provide me with a step-by-step instructions, I would be very happy.
Thank you
Click to expand...
Click to collapse
Id be glad to help you. First off though are you s-off, and once you go stock again do you plan on rerooting in the future?
cmlusco said:
Id be glad to help you. First off though are you s-off, and once you go stock again do you plan on rerooting in the future?
Click to expand...
Click to collapse
Thanks for the reply. Right now I am S-On. And no, I don't plan on rooting again.
bobrea said:
Thanks for the reply. Right now I am S-On. And no, I don't plan on rooting again.
Click to expand...
Click to collapse
Ok then all you need to do is flash an ruu thru hboot.
Go here (http://pvillecomp.com/?page_id=22)and download the Gingerbread PB31IMG.zip
From the home screen of the phone hit Menu - Settings - Applications, and make sure fastboot is NOT checked.
Then go here (http://pvillecomp.com/?page_id=79) to learn how to flash the ruu thru hboot.
If you have any issues i will be keeping an eye on the thread.
I think I tried this earlier but it didn't work due to something about a newer version already be installed. I'll keep you posted.
bobrea said:
I think I tried this earlier but it didn't work due to something about a newer version already be installed. I'll keep you posted.
Click to expand...
Click to collapse
What android version are you on now? If its 4.08.605.2 then you will need to do the ruu exe with a pc. Its the first one on the pvillecomp link where the PB31IMG is.
To be totally honest I'm not sure. I tried using an RUU earlier but it kept saying my phone wasnt plugged in and it couldn't run, even though the phone was plugged in.
bobrea said:
To be totally honest I'm not sure. I tried using an RUU earlier but it kept saying my phone wasnt plugged in and it couldn't run, even though the phone was plugged in.
Click to expand...
Click to collapse
To do the ruu exe you need to have htc sync installed on your pc, to get the right drivers. Im not positive but you may need to remove the adb drivers first.
Baseband version: 2.15.00.07.28
Kernel Version:
2.6.37.6-cyanogenmod+
Android Version: 2.3.7
bobrea said:
Baseband version: 2.15.00.07.28
Kernel Version:
2.6.37.6-cyanogenmod+
Android Version: 2.3.7
Click to expand...
Click to collapse
Thats the problem your on a custom rom thats ported, and a higher android version than the latest stock ruu for the inc, so the ruu thinks yout trying to downgrade. Since your still on the correct radio needed for unrevoked to achieve s-off, i would reroot and s-off the phone with unrevoked, then flash a stock ota based inc rom (perferably 4.06.605.3), then go s-on again with the s-on patch, then do the ruu and it shouldnt give the firmware too new error anymore, and should get you back to complete stock.
What does that mean/how do I do it? I'm totally clueless here.
What does that mean/how do I do it? I'm totally clueless here. I just downloaded unrevoked 3.
bobrea said:
What does that mean/how do I do it? I'm totally clueless here.
Click to expand...
Click to collapse
Go here (http://unrevoked.com/#inc) get the unrevoked program and run it to root your phone and get s-off again. Instructions are on that page for using it.
Then flash this rom thru clockworkmod recoveryrecovery (http://forum.xda-developers.com/showthread.php?t=1247253), and reboot.
Then flash the s-on tool thru recovery (http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip)
Then do the PB31IMG.zip ruu again, it should work this time, and you will be complete stock.
Not exactly sure what's going on here. I used unrevoked 3 and got the original OS back on there, but when unrevoked runs, it asks if I want to install that PB31IMG file. I chose to not update with that and just reboot into recovery (which if I'm correct should be clockwork,) so I could flash that ROM, but when I reboot the device, I get a black screen wiith a picture of the phone and an ! in a red triangle. The unrevoked program just says "waiting for reboot..."
bobrea said:
Not exactly sure what's going on here. I used unrevoked 3 and got the original OS back on there, but when unrevoked runs, it asks if I want to install that PB31IMG file. I chose to not update with that and just reboot into recovery (which if I'm correct should be clockwork,) so I could flash that ROM, but when I reboot the device, I get a black screen wiith a picture of the phone and an ! in a red triangle. The unrevoked program just says "waiting for reboot..."
Click to expand...
Click to collapse
Go aheda and let unrevoked do the PB31IMG, that is the cwm recovery. The red triangle is still the stock recovery. Are you s-off now?
Nope, I'm still S-on. Not really sure what happened, but I have the original OS on the phone and from what I can tell, it's working fine. But I'm still S-on
I'm going to call it a night. I'll check this thread tomorrow when I get back from work and class. Thanks so much for all of your help so far.
bobrea said:
Nope, I'm still S-on. Not really sure what happened, but I have the original OS on the phone and from what I can tell, it's working fine. But I'm still S-on
Click to expand...
Click to collapse
Welk then you are stock just like the day you got it. If you want you can do the gingerbread ruu now, and it should not give the firmware too new error, ir you can stick with froyo, and at some point it will pop up with the latest ota to install.
Thanks so much, again. This was driving me crazy.