I know there are already a few threads like this around but needed a little more concise answer... so apologies!
I'm returning my phone for issues with the power button being unresponsive and wanted to relock the bootloader and return it to stock software and recovery. I'm good on everything except the recovery. After the latest ota update I can't get any RUU file to work that would relock everything since the 2.35 RUU isn't out yet I guess. What is my best solution for getting this back to day 1 so I can return the phone? Do I need to just manually flash the recovery? Will that get rid of 'tampered' on the bootloader?
Thanks everyone!
fbihawk said:
I know there are already a few threads like this around but needed a little more concise answer... so apologies!
I'm returning my phone for issues with the power button being unresponsive and wanted to relock the bootloader and return it to stock software and recovery. I'm good on everything except the recovery. After the latest ota update I can't get any RUU file to work that would relock everything since the 2.35 RUU isn't out yet I guess. What is my best solution for getting this back to day 1 so I can return the phone? Do I need to just manually flash the recovery? Will that get rid of 'tampered' on the bootloader?
Thanks everyone!
Click to expand...
Click to collapse
Now also having issues with HTC Development text showing up every time you start the phone. Kind of a dead giveaway. Anybody have thoughts?
Related
So I will be returning the One S, albeit a great phone, back to TMobile to get my slice of the SIII tomorrow (last day of 14 day period) -- I have a general understanding on returning it back to stock, but as far as getting it completely back to the way I had it, maybe not so much. Anyone have a walkthrough on turning S-On and getting it entirely back to the way I bought it?
Thanks in advance.
id_twin said:
So I will be returning the One S, albeit a great phone, back to TMobile to get my slice of the SIII tomorrow (last day of 14 day period) -- I have a general understanding on returning it back to stock, but as far as getting it completely back to the way I had it, maybe not so much. Anyone have a walkthrough on turning S-On and getting it entirely back to the way I bought it?
Thanks in advance.
Click to expand...
Click to collapse
Did you flash a custom rom or just rooted and nothing else?
relock the bootloader and run the Tmobile RUU.
job done !!
PS. You may need to revert to stock recovery before running RUU.
azzledazzle said:
relock the bootloader and run the Tmobile RUU.
job done !!
PS. You may need to revert to stock recovery before running RUU.
Click to expand...
Click to collapse
All I did was run cmd " fastboot oem lock" and run T-mobile RUU.
Waiting for my exchange ONE S
Ok, so I'm sick to death of waiting for HTC to fix the touch button issue so I want to send it back for repairs, so I need to bring it back to complete stock.
Now, I have a backup of the stock rom with root but when I restore it I get stuck in a boot loop. Does anyone know what the problem might be?
Next, I have CM9 running at the moment, so If I just relock the bootloader can I run the RUU and will it restore back to stock?
Sorry for being a noob but I've looked and I cant find a straight answer for question 2.
shoffobroff said:
Ok, so I'm sick to death of waiting for HTC to fix the touch button issue so I want to send it back for repairs, so I need to bring it back to complete stock.
Now, I have a backup of the stock rom with root but when I restore it I get stuck in a boot loop. Does anyone know what the problem might be?
Next, I have CM9 running at the moment, so If I just relock the bootloader can I run the RUU and will it restore back to stock?
Sorry for being a noob but I've looked and I cant find a straight answer for question 2.
Click to expand...
Click to collapse
Are you wiping before you restore your stock ROM? Yes relock using fastboot OEM lock. Then run the RUU.
Sent from my HTC One S using Xparent Blue Tapatalk 2
shoffobroff said:
Ok, so I'm sick to death of waiting for HTC to fix the touch button issue so I want to send it back for repairs, so I need to bring it back to complete stock.
Now, I have a backup of the stock rom with root but when I restore it I get stuck in a boot loop. Does anyone know what the problem might be?
Next, I have CM9 running at the moment, so If I just relock the bootloader can I run the RUU and will it restore back to stock?
Sorry for being a noob but I've looked and I cant find a straight answer for question 2.
Click to expand...
Click to collapse
Hi This thread should help you and point you to the right direction.
http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
Does anyone know any way to get the One S back to as close to stock as possible? I'm returning my phone to T-mobile for service and I can't get 'TAMPERED' to disappear from HBoot without the RUU. Also, now having an issue with every time I turn on the phone it has the developer text on the splash screen even though it isn't entering hboot or recovery.
Does anyone have any ideas on either issue? The only threads I can find are people with pretty much the same issue and no solution or pre 2.35 updates.
fbihawk said:
Does anyone know any way to get the One S back to as close to stock as possible? I'm returning my phone to T-mobile for service and I can't get 'TAMPERED' to disappear from HBoot without the RUU. Also, now having an issue with every time I turn on the phone it has the developer text on the splash screen even though it isn't entering hboot or recovery.
Does anyone have any ideas on either issue? The only threads I can find are people with pretty much the same issue and no solution or pre 2.35 updates.
Click to expand...
Click to collapse
Sorry, I should also mention I've loaded a nandroid backup of the stock rom without root and attempted to flash the "stock" recovery. I'm not sure about the recovery because I don't believe it came from the 2.35 software and that's when I started to have issues with the splash screen. Loaded TWRP back on and still same issue.
Also, was having issues after with the device not loading to anything but bootloader until I re-unlocked it then it started fine.
I don't think you're gonna be able to do anything without ruu
mbernusg said:
I don't think you're gonna be able to do anything without ruu
Click to expand...
Click to collapse
That's kind of what I was afraid of. Any ideas on when that could be? Or if HTC would have that file?
from personal experience, dont worry about it, t-mobile wont care.
I had a sidekick that I bricked, and there was no way to even power it on, went to tmobile with custom sw and recovery...
also I had a sensation that i sent back with custom rom and a custom recovery because the phone would not get power, never heard anything about.
I read somewhere online that tmobile returns the phones to stock even before they check them.
if you send it back as is, you SHOULD be fine... ive done it twice.
jahnbodah said:
from personal experience, dont worry about it, t-mobile wont care.
I had a sidekick that I bricked, and there was no way to even power it on, went to tmobile with customer sw and recovery...
also I had a sensation that i sent back with custom rom and a custom recovery because the phone would not get power, never heard anything about.
I read somewhere online that tmobile returns the phones to stock even before they check them.
if you send it back as is, you SHOULD be fine... ive done it twice.
Click to expand...
Click to collapse
That definitely relieves a little stress. Thanks!
fbihawk said:
Sorry, I should also mention I've loaded a nandroid backup of the stock rom without root and attempted to flash the "stock" recovery. I'm not sure about the recovery because I don't believe it came from the 2.35 software and that's when I started to have issues with the splash screen. Loaded TWRP back on and still same issue.
Also, was having issues after with the device not loading to anything but bootloader until I re-unlocked it then it started fine.
Click to expand...
Click to collapse
Could you provide a link for the stock nandroid? It would be much appreciated! I am on CM 10 but can't get back to stock. The stock nandroid I downloaded the other day fails upon restoring everytime.
jaker.the.skater said:
Could you provide a link for the stock nandroid? It would be much appreciated! I am on CM 10 but can't get back to stock. The stock nandroid I downloaded the other day fails upon restoring everytime.
Click to expand...
Click to collapse
I just used the one in the dev section.
Hey guys new to the fourm here but im having some trouble getting my Inc2 back to stock im running the zip in bootloader but is says main version is older...the bootloader has been relocked Any thoughts
Savagemanmn said:
Hey guys new to the fourm here but im having some trouble getting my Inc2 back to stock im running the zip in bootloader but is says main version is older...the bootloader has been relocked Any thoughts
Click to expand...
Click to collapse
I am in the same boat man. I have the newest firmware, v6 and radio v312...I need to get back to full stock in order to be able to gain access to the stock recovery so I can use the tacoroot method to S-off my phone. I can't seem to find what I am looking for. I have tried flashing the PG32IMG file. However, it starts off like its working, it runs a blue status bar then a brown one and that is it. I am pretty much losing hope. :/
So, my phone is running 4.1.2 rooted, and it got an OTA recently. The OTA failed because the bootloader was unlocked.
I thought easy-peasy, just odin flash the locked boot loader and download/apply OTA again, right?
Flashed fine, locked and clean for initial boot. But when it went to install the OTA, same problem happened, the bootloader was miraculously unlocked again, and the OTA failed.
Any ideas on how I can get past this? I really don't mind loosing root, just trying to avoid a complete odin reflash and loosing everything...
I am just curious ... why would you want to update to the OTA 4.3 and forever lock down the bootloader? Once the verizon 4.3 update takes hold, you might be able to root, but (so far) will not be able to load custom roms without bricking the device.
vax1170 said:
I am just curious ... why would you want to update to the OTA 4.3 and forever lock down the bootloader? Once the verizon 4.3 update takes hold, you might be able to root, but (so far) will not be able to load custom roms without bricking the device.
Click to expand...
Click to collapse
Well your almost right. First off you for sure can root. Second you can install custom roms with safestrap. Its limited to tw roms atm. There have been a hand full of people who upgraded just to use safestrap. I wouldnt recomend it right now because its alittle buggy.
RedBullet said:
So, my phone is running 4.1.2 rooted, and it got an OTA recently. The OTA failed because the bootloader was unlocked.
I thought easy-peasy, just odin flash the locked boot loader and download/apply OTA again, right?
Flashed fine, locked and clean for initial boot. But when it went to install the OTA, same problem happened, the bootloader was miraculously unlocked again, and the OTA failed.
Any ideas on how I can get past this? I really don't mind loosing root, just trying to avoid a complete odin reflash and loosing everything...
Click to expand...
Click to collapse
Wife's phone. She doesn't want to mess with it.
I think I figured it out, looks like I had a custom recovery installed. Flashed that to stock and locked bootloader and all is fine now. Running latest and greatest. Just what the missus is looking for...
RedBullet - Ah, I fully understand now I'm having a similar conversation with my misses.
ThePagel - Thanks. One one of my phones was cursed with an accidental OTA 4.3 upgrade. Nice to know something is in the works, I'll dig up that thread and watch it.
vax1170 said:
RedBullet - Ah, I fully understand now I'm having a similar conversation with my misses.
Click to expand...
Click to collapse
I assume if one wants to go the custom ROM route they would simply need to odin flash one of the older stock images and go from there. Doesn't seem like a big problem. Of course > 50% chance I have no idea what I'm talking about...
RedBullet said:
I assume if one wants to go the custom ROM route they would simply need to odin flash one of the older stock images and go from there. Doesn't seem like a big problem. Of course > 50% chance I have no idea what I'm talking about...
Click to expand...
Click to collapse
If you take the 4.3 OTA, you cannot odin flash an older stock image. Will brick your device.
landshark68 said:
If you take the 4.3 OTA, you cannot odin flash an older stock image. Will brick your device.
Click to expand...
Click to collapse
Really? That is pretty tragic. I may only buy unlocked devices from here on out; they seem to be getting better and better at making their devices less and less useful...
It sure is sad but true. Im thankful google blessed us with the nexus 5
RedBullet said:
Really? That is pretty tragic. I may only buy unlocked devices from here on out; they seem to be getting better and better at making their devices less and less useful...
Click to expand...
Click to collapse