Develop Bugs

[Q] Help w/ Warranty Replacement

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.

Un-Rooted phone won't update to 2.2

Hey all, I am new here and have a frustrating problem.
A while ago I rooted my HTC EVO with unrevoked. Everything was working fine but due to some complications I wanted to restore my phone to stock.
I used the following software linked below to "unroot" my phone. After I completed this everything seemed fine, my phone was updating firmware,software, etc... However my phone firmware is currently at 2.1 and when I check for updates it tells me there are NONE!
I am with Sprint by the way.
Software I used to "unroot"
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe
(sorry can't post links)
Any help/advise would be appreciated.
Thanks in advance.

Did you flash the s-on zip first? If you're still s-off, you can flash a recovery through the bootloader. Then go into the recovery and flash the s-on zip. You can then run an RUU of the latest OTA from your computer or through the bootloader.
If you're s-off, I would think you could just run a newer RUU. I guess you don't have to turn s-on, but you might as well while you're doing the update so that you don't have to worry about it later if you have to take your phone in.
(from... Evo/MIUI/Tapatalk)

You were correct, the phone was in S-OFF and I suspect this is what's causing the issue.
Thanks again.

hmmm, i actually had to unroot my phone yesterday too, and i used the same RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_rele ase_CL195459.exe file. when everything was done, I was able to update everything, and i just looked, and my phone still says s-off, is that a problem? Should i turn s-off to s-on?

~CR7~ said:
hmmm, i actually had to unroot my phone yesterday too, and i used the same RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_rele ase_CL195459.exe file. when everything was done, I was able to update everything, and i just looked, and my phone still says s-off, is that a problem? Should i turn s-off to s-on?
Click to expand...
Click to collapse
S off means that the phone is still rooted, as security is still turned off. If you were to bring it to the Sprint store for any reason while it says S off, there is a chance that they wouldn't provide service for you, due to rooting the phone voiding the warranty. It is always advised to be S on prior to taking the phone in for any type of software related issues. If you have no intentions of going to the Sprint store any time soon, leaving it S off won't hurt anything, and will make it rather easy for you to start flashing roms again if you were to choose to do so.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

How to tell which root method you used?

I am in desperate need of unrooting my phone now, but due to it being almost 2 years that I've owned this phone I can't remember how I rooted it in the beginning. Any way to figure this out?

Need to know your Hboot version and radio, and also is the phone S-ON or S-OFF (power off, then volume down and power buttons simultaeously).

HBOOT-2.18.0001
RADIO-2.15.00.12.19
Phone is S-OFF
Thanks for your help.
On a side note, my phone is in an infinite boot loop that only loads to the white evo screen, I can't flash custom recoveries, roms, or RUU. I think the problem is the fact that it says LOCKED in the pink label at the top of my bootloader. I tried using the command fastboot oem lock and it says it's already locked and doesn't unlock it or anything of the sort. If you know any way to aid my problem I thank you for the help.

Most infinite bootloops are never fixed, however;
The best advice that I can give you right now is to download these two files.
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
http://goo.im/stock/supersonic/ruu/...15.00.12.19_NV_2.33_release_234563_signed.exe
Connect your phone to your computer, then boot into your bootloader and click on FASTBOOT. The phone should be in FASTBOOT USB. Install the HTCDrivers exe file to your computer. Then try to run the RUU file with the phone still in FASTBOOT USB.
If that doesn't work, then the phone may already be permanently bricked. Interestingly, the phone was rooted nearly 2 years ago, but you have the latest everything. I hope you did not do that with OTA updates.

Thanks shortyydoggg, unfortunately I've tried that method with those exact files already and had no such luck. My last resort is that if I can change the LOCKED pink label to RELOCKED or UNLOCKED, I'll be able to flash through the bootloader again, and temporarily use my phone once more until i can get the EVO LTE. Also, there is basically no way to tell now which root method I used?

Yea, Unlocking the bootloader was going to be my other suggestion after trying the RUU. It's not much else you can do after that.
Sent from my PC36100 using xda premium

Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?

djs415 said:
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
Click to expand...
Click to collapse
That's the wrong command. You need to go to the htcdev site (www.htcdev.com), register, and unlock the bootloader. Since you're already S-OFF, have you tried running a PC36IMG file for a custom RECOVERY. You might not need to be unlocked to do that.

I'm almost positive I tried to flash a custom recovery through the bootloader and it didn't work... however, you were right and my bootloader is now unlocked so THANK YOU! Will post back after flashing the recovery you attached.

To answer your previous question about which root method you used, unrevoked-forever was used at some point to S-OFF the phone, since you are on Hboot 2.18 and still S-OFF and not on the old Engineering S-OFF Hboot. Whether the phone was rooted with Unrevoked, Toast Method 2, Simple Root or AutoRoot, there is no exact way to tell right now, but it can be guesstimated that it might have been Unrevoked.
Now for the confusion if you dare to read:
AutoRoot is Toast Method 1, unrevoked-forever, and a custom ROM inside a program, and Simple Root is Toast Method 1 and a custom ROM inside a program along with the engineering S-OFF bootloader. Unrevoked is uh, Unrevoked and Unrevoked forever inside a program. Toast method 2 is just a custom ROM flashed along with the same S-OFF bootloader as SimpleRoot. If you used Toast Method 2, then you did everything AutoRoot did in order to S-OFF the phone. You just needed unrevoked-forever to keep it S-OFF for any other and your bootloader. Toast Method 1 alone does not S-OFF the phone. If you used SimpleRoot, which does not use unrevoked-forever, you needed unrevoked-forever at some point again to keep the phone S-OFF on any other Hboot (your 2.18). So again, you would have done everything AutoRoot did.
So that brings it down to AutoRoot and Unrevoked, since everything else you did is the same thing that AutoRoot does. Since you rooted nearly 2 years ago, and Unrevoked-forever is inside AutoRoot, AutoRoot has to be newer than unrevoked-forever to contain it inside its program. Also Unrevoked is newer than AutoRoot and already contained Unrevoked-forever. So the likely-hood that you used Unrevoked is very great, but not for sure. It is also the easier method and the one that nearly everyone else used at that time.

Somehow, still no luck. Flashed that file you linked and it goes through successfully, asks to reboot and then back to white screen boot loop. How can this be possible at this point, with the bootloader unlocked it goes through with the process but the actual writing of the data seems to fail. Trying the RUU one last time now that it is unlocked, but if this doesn't work I'm stumped.
I thought the whole beauty of the the bootloader, and more importantly being able to reach it, was that it meant your phone couldn't be bricked. Last try, will report back.
Bootloader unlocked, RUU flashed this time through PC. Nothing, and completely out of ideas here.

Shortydoggs been doing a lot of help around here for similar situations. There have been cases (maybe a dozen I've seen) where people get into a situation like yours where bootloader is accessible , but that is about it. And from what I've read, in those cases, when the phone tries to boot, it does 4 or 5 short vibrates before going back to bootloader.
Your situation is also strange in that, you rooted 2yrs ago, but don't have S-off, a locked bootloader. Hboot 2.18, which is the latest but is unlockable thru HTC dev, but no S-off available for it yet. And your radios are latest, too (mostly irrelevant).
First there was toasts root for baseband 1.37 (which downgraded you to 1.17 with eng hboot to get s-off before bringing you back up to 1.37). Then there was simple root by jiqqaman, which worked for people who took the baseband 1.47 OTA. Then when froyo came out, anyone who took that OTA (baseband 3.25, or 3.26, I forget) had to wait for unrevoked to be developed. I think hboot at that point was 2.08 and 2.10. Unrevoked forever worked on that, and gave you S-off.
I know none of that info helps you necessarily. It's just puzzling how you rooted 2yrs ago, bit have the latest hboot with S-on. Maybe you didn't finish toasts part 2 S-off guide, then sometime recently updated your radio and hboot? No. You need S-off to flash radio. Were you recently on a stock rooted ROM and took an OTA (is that even possible) when you were still S-on (from not finishing toasts guide)?
Sorry, I know it's not a lot of help. Just trying to figure out how things could not match up so much, and if that's how you ended up in this situation (that could be helpful info for others). I hope you don't have the bootloop of death and can get it sorted. Between shortydogg and captain throwback, I HAVE seen some phones saved.
sent from 2yr old Evo on ICS

Yea, I'm not going to waste your time any further. There's not much else to do.

Ya unfortunately I'm quite confused myself... however, if this information helps you at all... For starters, I have S-OFF and until recently (2 weeks or so since my phone started acting up like this) I was running a ROM perfectly fine until one day it restarted into this never ending boot loop. I'm not sure how my HBOOT is the most up to date, seeing as I was always very careful not to do something stupid like change my HBOOT for no reason. The interesting thing is that I had never seen that pink label before on my bootloader saying unlocked or locked OOW until the problem started occuring 2 weeks ago.
Also something I'm realizing... are you telling me that the HBOOT I have does not have S-OFF yet, and therefore you can't flash roms or custom recoveries... but my bootloader still says I am S-OFF. So the problem is I am S-OFF for the most recent HBOOT which can't be changed to S-OFF yet? Could downgrading hboots work?

He did not realize that you were S-OFF. Your phone is set to stay S-OFF regardless of what Hboot you have or how that Hboot usually comes.
Also, your phone appears to have a hardware, and not software issue, so, changing Hboots, might not hurt to try, but may not help much. In case I'm wrong, do not try anything below Hboot 2.10. Here is one for 2.16.

What rom were you running up until the time the bootloops started happening? This sounds alot like the cyanogen mod bootloop of death which no one has ever fixed I believe.

I believe I was using some version of SOS or a sense rom, but I'm leaning more towards SOS.
Just tried using that HBOOT thought it's still not working. Would going to the engineering hboot make any difference?
What could be the hardware problem causing this?

I see that shortydogg is in here taking good care of you .
The bottom line is, if you can't flash/get into recovery from HBOOT, you're probably in an unrecoverable situation.
It's unclear after my review of the thread, but you have tried flashing a recovery through HBOOT using a PC36IMG.zip file, right? And then after flashing, you choose not to reboot, but to boot into Recovery?
If you can get into recovery, then we can resolve your issue (if in fact it is software related).
If the problem is bad NAND blocks on your recovery or boot partitions, then there's nothing that can be done.
Also, the watermark on your bootloader (LOCKED, UNLOCKED, etc) has nothing to do with your issue. That's just connected to the version you were running. As long as you're S-OFF, that's irrelevant.

[Q] Is stock possible?

Recently been looking into purchasing a new HTC One for myself, but after reading up on it, I see that there are a ton of S-Off and stock issues flying around. I guess I have a few clarifying questions then...
If I buy the phone today, is S-Off still possible?
Is S-Off risky?
Can I return to 100% complete stock yet if I need to or not? If yes, how?
Really I'm wondering if it's worth it to even purchase this phone as I don't want to be without flashing ROMs but at the same time, I resell my phones after awhile so I'm going to need to go back to 100% stock eventually. Sorry if these questions have already been asked, my xda search function is a bit broken. Thanks for reading this far.
Edit - Did some more searching and found the HTC One m8 now has the RUU's? Could someone also explain this? I'm new to HTC devices, coming from a nexus 5 here.

Nobody knows at all...?
Sent from my HTC M8

DinoSoup said:
Recently been looking into purchasing a new HTC One for myself, but after reading up on it, I see that there are a ton of S-Off and stock issues flying around. I guess I have a few clarifying questions then...
If I buy the phone today, is S-Off still possible?
Is S-Off risky?
Can I return to 100% complete stock yet if I need to or not? If yes, how?
Really I'm wondering if it's worth it to even purchase this phone as I don't want to be without flashing ROMs but at the same time, I resell my phones after awhile so I'm going to need to go back to 100% stock eventually. Sorry if these questions have already been asked, my xda search function is a bit broken. Thanks for reading this far.
Edit - Did some more searching and found the HTC One m8 now has the RUU's? Could someone also explain this? I'm new to HTC devices, coming from a nexus 5 here.
Click to expand...
Click to collapse
Probably, it will be. But it's not for certain. If your phone comes with the stock 1.12 software, then you can do it. But there's also a possibility of your phone being one of those unlucky "Whelp, this sucks..." phones. If it comes with the latest 1.57 software installed, it won't be possible.
That being said, if it comes with 1.12, which it probably will, and you unlock the bootloader, root, and S-Off, you can always go back to 100% stock with no trace at all of it ever being rooted if you want to return it for warranty, exc.
IF it is one of the unlucky "Whelp, this sucks..." phones, and you unlock your bootloader, root, and try to S-Off, but can't, then you can re lock the bootloader, run the stock RUU, and the only trace of it being unlocked and rooted would be that in the bootloader, it would say "Relocked" instead of "Locked."
Remember that if the phone comes with the 1.12 software, NEVER accept the OTA update. If you do accept the update, you will never be able to S-Off.
But again, chances are you will probably get the 1.12 software and be able to S-Off your phone. Hope this helped.

XxKINGxX2580 said:
Probably, it will be. But it's not for certain. If your phone comes with the stock 1.12 software, then you can do it. But there's also a possibility of your phone being one of those unlucky "Whelp, this sucks..." phones. If it comes with the latest 1.57 software installed, it won't be possible.
That being said, if it comes with 1.12, which it probably will, and you unlock the bootloader, root, and S-Off, you can always go back to 100% stock with no trace at all of it ever being rooted if you want to return it for warranty, exc.
IF it is one of the unlucky "Whelp, this sucks..." phones, and you unlock your bootloader, root, and try to S-Off, but can't, then you can re lock the bootloader, run the stock RUU, and the only trace of it being unlocked and rooted would be that in the bootloader, it would say "Relocked" instead of "Locked."
But again, chances are you will probably get the 1.12 software and be able to S-Off your phone. Hope this helped.
Click to expand...
Click to collapse
Thanks a ton, this is exactly what I was hoping for. Final question - how do I go about getting to stock. I found the RUU and stock files but I don't know at all what to do. After I know that, I'll be ready to root!
Sent from my HTC M8

DinoSoup said:
Thanks a ton, this is exactly what I was hoping for. Final question - how do I go about getting to stock. I found the RUU and stock files but I don't know at all what to do. After I know that, I'll be ready to root!
Sent from my HTC M8
Click to expand...
Click to collapse
Sorry for the late reply,
To get to complete 100% stock, you have to download and run the RUU. It's a simple EXE file. There are a bunch of Youtube videos on how to run RUUs. Before running the RUU, you have to re-lock the bootloader. But, to go to 100% stock, you first have to to reset the tampered flag, LOCK, not re-lock the bootloader (there is a thread on how to make the bootloader say LOCKED, not Re-Locked) and then S-ON. After that, run the RUU file, and it will take you back to complete stock. Like you never unlocked the bootloader or rooted.
But, I would do everything except S-ON. If you go to S-ON and run the RUU, you will not be able to go back to S-Off again. The RUU will install the 1.57 software, and that version isn't supported by Firewater.
The only thing you really have to do is a simple re-lock of the bootloader before running the RUU. But, doing what I said would make the phone look like it was never rooted. Again, I would do everything I said except going back to S-ON.

I just successfully achieved completely stock with S-On. I gave my details here: http://forum.xda-developers.com/showpost.php?p=55374644&postcount=2