So the usb port on my EVO is messed up. Sometimes I have to wiggle it around in order for it to charge and if I move the usb cable it disconnects. This also makes it a hassle to transfer files between my phone and PC. I want to bring in my phone to repair, so I have to unroot it. I just want to make sure I go about this correctly. I want to unroot it and have it still be rootable again. I don't know what information you guys need, I'll give you as much as I can.
Hardware 0003
I rooted it with unrEVOked 3 and I didn't have to use the unrEVOked forever s-off patch, the unrEVOked 3 did that. I rooted it stock (did not update ever). I'm currently running a 2.3.5 rom with HTC Sense 3.5.
Would flashing Forever S-ON and then a PC36IMG through hboot be all I would need to do? Would the phone be rootable again after they repair it?
Yes, put a pc36img of a stock rom on the root of the card, then reboot and run s-on tool. Or run s-on tool and then run a stock ruu.
My radios or anything like that don't matter?
Also can I have a link to a stock PC36IMG? I have one but I don't know if it's 2.2 or 2.3.
Edit: Nvm it's froyo! I will unroot and update you on my progress.
When I attempted to flash S-ON, I got an error:
Unsupported radio version.
I booted into HBOOT, my radio is currently 2.15.00.05.02
How do I downgrade (or upgrade, whatever I need to do) my radio?
vulf search for calkulkin's thread about radios. The thread has every radio starting from the beginning to the newest radio. Take an older one and flash it in recovery. You should be good to go.
Sent from my PC36100 using Tapatalk
Related
I have to send my phone back for a warranty replacement because it won't charge the batteries. Anyways, I'm a bit unclear as to the exact steps required to return my phone to its stock conditions.
I restored my original nandroid backup (with 2.1-update1).
This is what I want to do:
remove root
restore the stock recovery
wipe all data to factory defaults
turn S-OFF back to S-ON
Is this the correct order to do these things? Am I missing anything?
I found how to do #2 at showthread.php?t=756850 and #4 is described on the Unrevoked Forever Wiki.
I do NOT know how to do #1 or #3.
Don't forget to format the internal Phone Storage. You can do that from in Settings.
You need Clockwork to flash S-ON, so do that before restoring stock recovery.
So, if I put back on the stock recovery, will I be unrooted?
Look?
This thread could have been found by searching. The only thing it did not cover is S-ON, which can be found on the unrEVOked forever FAQ
http://forum.xda-developers.com/showthread.php?t=732497
Thanks for your reply. I did multiple searches and have been reading for the last few hours, but obviously didn't find your helpful thread.
Any recommendations on which RUU would be best? Will it also flash my radio back to 1.x?
Thanks!
...
I would take the one right above the HBOOT .79 one ... because that would be the last one with HBOOT .77. I have gotten 3 Incredibles so far (2 warranty replacements for my original) and all 3 came with HBOOT .77.
Please note, that was written long before S-OFF so figure out where in the process S-ON should go.
Thank you very much. I'm downloading the executable now.
Just wanted to make sure that this won't brick the phone since I have a newer radio. Correct?
If I read the Unrevoked Forever instructions properly, I'll need to do the S-ON before running the RUU since the RUU will replace the rooted recovery with the stock recovery. Sound right to you?
Thanks again for your help.
YMMV
While YMMV, running a RUU in the ordinary course should not brick the phone (although pulling out the battery when you lose patience might). It will either run or it wont with your radio. There are other threads to downgrade if you need to.
The double-radio-flash issue was a one time thing when unrEVOked issued a radio ****PATCH**** in their efforts. Applying the Patch to a Patched radio would brick. That has nothing to flashing two radios, although it certainly morphed into that in the hearts and minds of the flasher community.
I think I have figured this .77 .79 HBOOT thang out.
if you had .77 then got the latest 2.1 update OTA you kept .77,
BUT the latest 2.1 RUU changes the HBOOT to .79, so if you got it OTA hboot stayed, if you did RUU you have .79
I think.
So I cracked my screen Monday at work but I'm Not to worried about it .I'm going to take it to a service center and shell out the 35 to have the screen replaced. But Here's the thing. I'm having problems unrooting this damn thing. I have All HTC Sync drivers, all ADB Drivers I have tested moving files to and from sd and sys mem via adb. I have the last two Current RUU's and PC36IMG files stock 2.2 no root, no nothing, just as sprint would like us to have it. I have runned unrevoked forever and have run the S-on Tool before flashing but I always keep getting Bootloader Main Version is older and it fails. I can flash any and all roms but I just can't seem to unroot this damn thing. I have tested the new Radio's and the Rooted 2.3.3 release for our phone. Wasn't much to write home about. I flash S-off and I can Flash anything but once i flash S-on I cant get the ruu's or the pc36img to work.. Always with this Main Version is older. Myabe I have to use a certian combo of radio's or something I'm still running the Gingerbread radios.
Little about my phone
Hardware:0004
Baseband: 2.15.00.11.19
Android:3.70.651.1
PRI: 2.15_003
PRL60679
Hboot. 2.10.0001(S-OFF as of right now)
If someone could please PM me of what I may be missing. Thanks everyone Untill then I will continue searching and reading.
1. http://unrevoked.com/rootwiki/doku.php/public/forever ; Scroll down to the FAQs, then download the unrevoked s-on zip. This places the security back on your phone, because rooting makes it s-off, and if s-on, quickest way to tell your phone was rooted.
2. Flash that file from recovery, then boot back into the bootloader [vol+down while turning phone on] and verify until its s-on.
3. http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip ; rename that file to PC36IMG, place on the root of your sdcard [not in a folder] then flash it in the bootloader. When the scan that normally does nothing, it'll detect that file. Apply the update then reboot. That's a stock 3.70 firmware file, it'll take you back to stock, unrooted, s-on.
You shouldn't get the 'main version is older' message, it meant you were using the wrong ruu.
Like mentioned above, you are simply trying to flash a rom that is older than your current HBoot requires basically. PC36IMG for Stock HBOOT 2.10.0001 EVO
Best of luck!
This will set everything back to the way it was before you did anything to the phone. However unlikely, be sure to remove any further traces of your "root" by deleting stuff like Titanium backup, clockwork mod .. and any other Apps that required root to use (like wireless tether)
Thats where backups come in handy, because you can backup your current EVERYTHING (Rom with Clockwork - Apps with Titanium), transfer the folders to your PC, and when you get your phone back.. drag and drop, re-root and recover and you are back to the way you like it.. like nothing changed.
I have seen some threads about un-rooting for warranty claims, but want a definite answer before doing anything.
My DHD has ENG S-OFF, Radio S-OFF and Clockwork Mod Recovery, and basically I want someone to be able to tell me/ point me in the direction of files and instructions for returning my handset to 1.32 stock with no superuser, custom recovery or s-off's of any kind.
Also, if the engineers where to update my phone like i know their prone to doing, is it still possible to downgrade back to 1.32 and root again to get my beloved MIUI back?
jamiegoldsworthy said:
I have seen some threads about un-rooting for warranty claims, but want a definite answer before doing anything.
My DHD has ENG S-OFF, Radio S-OFF and Clockwork Mod Recovery, and basically I want someone to be able to tell me/ point me in the direction of files and instructions for returning my handset to 1.32 stock with no superuser, custom recovery or s-off's of any kind.
Also, if the engineers where to update my phone like i know their prone to doing, is it still possible to downgrade back to 1.32 and root again to get my beloved MIUI back?
Click to expand...
Click to collapse
you can download a stock rom from the links on this thread:
http://forum.xda-developers.com/showthread.php?t=846248
And It'll take the HTC back to it's factory defaults, as if it was new. It'll probably be best to use the RUU (that's what it's called) for Orange UK (if your phone's locked to that, assuming you updated your operator)
HOWEVER! Running an OTA update to gingerbread from the new system'll leave you with a probably unrootable Desire HD (to check if it's still got the radio S-off at least, go into fastboot and check that the CID is just 1's)
hmohammed43 said:
you can download a stock rom from the links on this thread:
http://forum.xda-developers.com/showthread.php?t=846248
And It'll take the HTC back to it's factory defaults, as if it was new. It'll probably be best to use the RUU (that's what it's called) for Orange UK (if your phone's locked to that, assuming you updated your operator)
HOWEVER! Running an OTA update to gingerbread from the new system'll leave you with a probably unrootable Desire HD (to check if it's still got the radio S-off at least, go into fastboot and check that the CID is just 1's)
Click to expand...
Click to collapse
So I would install this like a ROM through Clockwork Mod?
So would this RUU remove all of my custom recovery, and S-OFF's? It's just I wanna make sure it's all gone just in case....
So there is no way that these can be downgraded like 1.72 can be?
Narh, you don't flash it through clockwork mod, it's run from your computer. You'll need the HTC Sync application installed on your computer, and a sense rom to connect the phone via htc sync.
When you run the RUU, it'll tell you what to do. I think it removes a ENG S-OFF but but a radio S-OFF'll stay on the phone (it is more or less permanent). However, I don't think the radio s-off'll show up in fastboot that obviously.
The reason you can't downgrade the firmware on RUUs is because in the process of rooting, the phone's CID changes to 111111111 (or something) so the PD98IMG file for downgrading will refuse to work with the phone because of an "Incorrect CID"
Sent from my Desire HD using XDA Premium App
hmohammed43 said:
Narh, you don't flash it through clockwork mod, it's run from your computer. You'll need the HTC Sync application installed on your computer, and a sense rom to connect the phone via htc sync.
When you run the RUU, it'll tell you what to do. I think it removes a ENG S-OFF but but a radio S-OFF'll stay on the phone (it is more or less permanent). However, I don't think the radio s-off'll show up in fastboot that obviously.
The reason you can't downgrade the firmware on RUUs is because in the process of rooting, the phone's CID changes to 111111111 (or something) so the PD98IMG file for downgrading will refuse to work with the phone because of an "Incorrect CID"
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
So I need to flash a sense ROM, and then how do I use the RUU? Sorry if I'm a pain!
Right so i can't get rod of radio s-off :/ and if they upgraded my phone I can't root again? damn :/
jamiegoldsworthy said:
So I need to flash a sense ROM, and then how do I use the RUU? Sorry if I'm a pain!
Right so i can't get rod of radio s-off :/ and if they upgraded my phone I can't root again? damn :/
Click to expand...
Click to collapse
It's been a while since i had to use a RUU, but I believe it should work with any rom.
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
What problems are you having with the RUU that you flashed? You can't downgrade, as you found out, so being stock S-ON you don't have many options other than flashing a different 2.3 stock image, and/or waiting for the actual OTA.
resyek83 said:
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
Click to expand...
Click to collapse
The only way i know to get back to 2.2 is to s-off your phone then ruu the 2.2. which will get you back to s-on 2.2, but you will be get the update nag every day once they start pushing the OTA out again.
resyek83 said:
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
Click to expand...
Click to collapse
For the moment, I think you are SOL, only because the same thing happened to me.
If you have 2.3.4 and S-ON, there's not really a way to downgrade back to 2.2, as HBOOT won't allow a downgrade. In fact, only PB31IMG.zip files that are signed by HTC will allow to be flashed. All others will not be recognized by HBOOT.
Unrevoked will no longer root after you have flashed RUU and have S-ON. You will get the error you are describing.
I have also tried newer root tools, such as Revolutionary, which is in the Beta phase.
Unfortunately, this method is not supported for the Incredible, and per Unrevoked's support channel on IRC, this is not likely, as apparently a phone that is only over a year old is considered a 'Legacy' device.
At this point we can only hope for the following:
HTC unlocks the Bootloader for the Droid Incredible on HTCdev.com. Only a handful of devices are listed at the moment.
Team Unrevoked releases a new version of Unrevoked that can find an exploit for 2.3.4 and enable root.
Revolutionary adds support for 'legacy' devices such as the incredible.
We are in a small minority, but hopefully enough devices will get the OTA, or refurbs get sent out with 2.3.4 that users will eventually require a new way to root.
Hang in there.
Yeah, if you're s on then from everything I've read, your screwed for now.
ahh ok....yea i kinda figured. I should have done a tad more research before I did it....everything works ok at the moment, except my battery life isnt as good as it was, but its not terrible. I guess I'll wait for the official OTA or wait and see if Unrevoked can come up with a solution.
your best option woulda been to root first. While you still had S-off flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-on.
TheBr0ken said:
your best option woulda been to root first. While you still had S-on flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-off.
Click to expand...
Click to collapse
Doing that with S-On is what has OP in this position in the first place. You have the right idea but mixed up S-On and S-Off.
TheBr0ken said:
your best option woulda been to root first. While you still had S-on flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-off.
Click to expand...
Click to collapse
Thank you, Captain Hindsight. In my situation, I was coming from a Rooted, 2.3 Sense 3.0 ROM, with S-Off.
I believe S-off is swicthed back to S-ON when you flash the RUU.
In the mean time, my phone is borked. Too new of a firmware on too "old" of a device.
SlimSnoopOS said:
Doing that with S-On is what has OP in this position in the first place. You have the right idea but mixed up S-On and S-Off.
Click to expand...
Click to collapse
yup, fixed.
deadsoulboy said:
Thank you, Captain Hindsight. In my situation, I was coming from a Rooted, 2.3 Sense 3.0 ROM, with S-Off.
I believe S-off is swicthed back to S-ON when you flash the RUU.
In the mean time, my phone is borked. Too new of a firmware on too "old" of a device.
Click to expand...
Click to collapse
what killed you was you musta flashed the s-on patch for some reason. I ran the same file you did. I still have s-off
The RUU does NOT turn the security flag to -ON. You do lose root until you flash a custom recovery and superuser, which is done easily.
Any hope for us S-ONs with 2.3.4? Is there something by way of unrevoked or something we can flash to try and get back to root?
There has to be something...
So I have a droid inc that I'm sending back in, and I want to revert it to stock. Right now, I'm running s-off, with a rooted stock OTA 2.3.4 (Incubusj's, I think) with the latest CWM. What do I need to do to make this thing bone stock to return it? I've done a search, and maybe I just suck at searching, but I can't find good, concise directions, and I don't want to screw it up.
sk8erord said:
So I have a droid inc that I'm sending back in, and I want to revert it to stock. Right now, I'm running s-off, with a rooted stock OTA 2.3.4 (Incubusj's, I think) with the latest CWM. What do I need to do to make this thing bone stock to return it? I've done a search, and maybe I just suck at searching, but I can't find good, concise directions, and I don't want to screw it up.
Click to expand...
Click to collapse
Search for the Ultimate get back to stock thread. It'll tell you what you need to to to get back to Stock 2.2 with S-ON.
That thread seems rather old. I'm running the 2.15.10.07.07 radio on hboot .92. Do I still just run the s-on and then run the RUU?
Well, was probably unnecessary, but I reverted to the old radio, flashed a rooted stock rom, then ran s-on through recovery, then a stock pb31img rom through bootloader. So it is bone stock again.
sk8erord said:
That thread seems rather old. I'm running the 2.15.10.07.07 radio on hboot .92. Do I still just run the s-on and then run the RUU?
Click to expand...
Click to collapse
True, that thread is old, but the info is still good. Good call on reverting back the radio, as you don't want that to cause any troubles. Pretty easy to get back to stock and S-ON huh?
i may need to go to bone stock for warranty purposes and then go s-on. if i flash the latest ruu (2.3.4) and then go to s-on (how do i go to s-on?) then can i get back to s-off if they actually fix my piece and send it back?
No. S-on via Clockworkmod, then flash 2.2 RUU. Then, when you want to root, use unrevoked
No need to go to newest stock, any stock with s-on should work. If they send you back an updated phone you can still downgrade and s-off from 2.3.4. Search forum for s-off and downgrade. It's doable - i've done it with help from here.
Just get the phone back to stock s-on. It doesn't matter if its 2.2 or 2.3 as long as its stock. They will send you a new phone that is updated already. Then to re root just downgrade and use unrevoked3
Sent from my Incredible Stock+ Ginger Tiny
oh so with s-on i can downgrade using an ruu and then unrevoked it? i thought some updates could block root forever a.k.a. u cant downgrade anymore to unrevoke. guess i was wrong. gonna submit my claim to square trade soon. hope they send me an upgraded phone lol.. rezound would be nice.
Ya that would be nice but you will either get the original incredible or the incredible 2. Any ways, the original 2.2 downgrade should work. I have tried it my self and I don't see where people have problems. I bricked my phone really bad and had to install the actual bootloader. But point is I had no problems downgrading and rooting again. Let me know if it worked for you. It should since you have a bootloader still.
Sent from my Incredible hd / gingedtiney