Hi, I'm sending in my phone for HTC uh-oh protection because I noticed my camera sapphire glass cracked. I want to return my phone to stock. Can someone point me towards a guide to get rid of all the tampered flags and such? A refresher on how to lock the bootloader and turn s-on again would also be helpful.
I'd appreciate any help. So far I know I have to:
1. flash a stock rom
2. turn s-on
3. lock the bootloader
4. get rid of any flags that say I tampered with my device.
anything I'm missing?
I've been trying to do the same thing. Following HERE but I keep getting an error on last step of flashboot flash pg2fs xxxx.img. I get an Error 35. I can't seem to find out why I can't get it.
easy way is to flash latest RUU, that will get you back to stock
to relock boot loader: fastboot oem lock
for s-on, you'll have to do some research, this thread shows this cmd fastboot oem writesecureflag 3 but its for M7, not sure if it's different for M9
or you could ask @schmeggy929 to make a custom aboot that masks s-off & unlocked...that way if u get the same phone back (repaired), you'll still be unlocked & s-off
OMJ said:
easy way is to flash latest RUU, that will get you back to stock
to relock boot loader: fastboot oem lock
for s-on, you'll have to do some research, this thread shows this cmd fastboot oem writesecureflag 3 but its for M7, not sure if it's different for M9
or you could ask @schmeggy929 to make a custom aboot that masks s-off & unlocked...that way if u get the same phone back (repaired), you'll still be unlocked & s-off
Click to expand...
Click to collapse
Thanks OMJ. I already have done all of that...The only thing I'm having a problem accomplishing is changing MODIFIED to ORIGINAL status! I can do all of the above, no sweat! But thanks for your help, and the fastboot oem writesecureflag 3 does reset S-ON
As for the OP, if you need some help doing any of the things mentioned, I'll help ya out!!
I also can confirm that you can change MODIFIED to ORIGINAL. I do not remember what thread it was on, but it does work. I worked hard on setting it up so I could take my m9 back to sprint for a free replacement before I went on vacation. I just recently got back and that is why it has taken me a while to reply!!
Related
If I run the 1.02.605.6 RUU (version on rooted device now) will it return the phone to "locked" status? Just want to know before hand.
Considering a return because this thing is eating battery bad. And I have the extended battery. Had extended battery on my thunderbolt and I made it through a day easy. Today with the resound, I went to work didn't really use the phone. Mabe browsed for 10 minutes, walked out of work with 38%. It's not normal, I think I got a bad phone. I don't believe its the battery. I've just used about 10% while typing this
So if I flash the ruu will it return everything to fresh out of the box? The only reason I ask is cuz this unlocked bootloader, S-on thing is a little different then I'm used to.
I've also read that someone had to relock the bootloader through adb before the ruu would work, is this the case?
On a side note, I LOVE THIS PHONE! Just gotta get the battery thing straight!
EDIT: for the record, i'm unlocked(via htcdev) and rooted, amon ra recovery, running BAMF 1.02
The only way to re-lock the bootloaded is to use the fastboot command to relock it.
Then it will say RE-LOCKED.... you cannot get it back to LOCKED.
Fastboot command is:
Code:
fastboot oem lock
So once I "relock" it, and run the ruu, it will still say "relocked"?
It says here that it will be unlocked 5) Download the RUU for your mainver to your computer.
This is an exe filesojustrun it on your pc with your phone attached. You need to be locked and you need HTC Sync installed. Now you are back to stock.
5a) Unlock your phone again using the same unlock bin file you got before by putting it in the same folder you are now using for sdk. Type the following command:
fastboot flash unlocktoken Unlock_code.bin
If you don't have it obtain a new one by following the same steps you did before to get it originally. Here is a guide for that: http://forum.xda-developers.com/show...79&postcount=1
Now you should be stock and unlocked.
Yes, it will still say "relocked" but people have returned their phones like this.
It will only be unlocked if you unlock it again as it states in step 5a. I wrote those instructions and it must've been for someone who wanted to be unlocked and rooted again. So if you stop after step 5 you will be stock and relocked and factory fresh.
Once you unlock, there is no way to return it to Locked. The chances the guy at the Verizon store will boot it into the bootloader are slim to none though.
Ok thanks guys. I'm back to stock and its getting returned tomorrow. I hope I get a better one this time.
Alright guys, I've searched and searched and I think I have it all down, just want to lay out my steps and get verification.
I'm on T-Mo ICS, not from OTA, flashed myself
Root
S-Off
4-Ext
I'm sending my phone in and need to go back to stock. I think I would prefer to go back to GB so it's just like from factory with no OTA.
- Download the Stock GB RUU from here - HTC Ruby/Amaze 4G Stock ROMs
- The RUU I want is - PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed
- Following These Directions I connect via ADB and fastboot oem lock This will show it as Re-Locked, correct?
- Reboot
- Flash the stock RUU I got by placing it in the root of my external sd card and renaming it PH85IMG.zip and rebooting to bootloader. Which is Volume Down + Power? Can someone verify that?
- Then I set the security lock by doing "fastboot oem writesecureflag 3" - This will change the bootloader to show locked, not re-locked, correct? I thought you had to have root to ADB?
At that point I'm back as if I took the phone out of the box for the first time? 4ext will be replaced with Stock Recovery? Thanks in advance. Like I said, I've searched, but there are many conflicting reports. :good:
Minker17 said:
Alright guys, I've searched and searched and I think I have it all down, just want to lay out my steps and get verification.
I'm on T-Mo ICS, not from OTA, flashed myself
Root
S-Off
4-Ext
I'm sending my phone in and need to go back to stock. I think I would prefer to go back to GB so it's just like from factory with no OTA.
- Download the Stock GB RUU from here - HTC Ruby/Amaze 4G Stock ROMs
- The RUU I want is - PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed
- Following These Directions I connect via ADB and fastboot oem lock This will show it as Re-Locked, correct?
- Reboot
- Flash the stock RUU I got by placing it in the root of my external sd card and renaming it PH85IMG.zip and rebooting to bootloader. Which is Volume Down + Power? Can someone verify that?
- Then I set the security lock by doing "fastboot oem writesecureflag 3" - This will change the bootloader to show locked, not re-locked, correct? I thought you had to have root to ADB?
At that point I'm back as if I took the phone out of the box for the first time? 4ext will be replaced with Stock Recovery? Thanks in advance. Like I said, I've searched, but there are many conflicting reports. :good:
Click to expand...
Click to collapse
In order to flash the factory RUU you need to be either locked or relocked. Then when you flash the factory RUU it should overwrite your hboot which will reset from "relocked" to "locked" then the writesecureflasg function will turn S-ON and you'll be factory.
freakasis said:
In order to flash the factory RUU you need to be either locked or relocked. Then when you flash the factory RUU it should overwrite your hboot which will reset from "relocked" to "locked" then the writesecureflasg function will turn S-ON and you'll be factory.
Click to expand...
Click to collapse
If you're s-off you don't need to lock or relock to flash a stock ruu.
Sent from my SGH-T999 using xda app-developers app
Dark Nightmare said:
If you're s-off you don't need to lock or relock to flash a stock ruu.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Guess that does make sense, huh?
But everything looks OK then?
Update - Downloaded and renamed the RUU, rebooted into recovery and installed everything. Bootloader shows locked and I went ahead and did the ICS Update. Everything is back to factory and I'm ready to send it back.
Final Steps
Minker17 said:
Update - Downloaded and renamed the RUU, rebooted into recovery and installed everything. Bootloader shows locked and I went ahead and did the ICS Update. Everything is back to factory and I'm ready to send it back.
Click to expand...
Click to collapse
Rick. Like you, I want to bring my T-Mobile HTC Amaze back to stock so that I can upgrade to ICS. The phone was bought on eBay with GB and a custom rom. I'd like to follow your steps but it had a lot of question marks and/or needed confirmation. Will you post exactly what you did?
Your steps seems a lot easier than what I've been researching. Is it really that simple? It makes sense. Everyone else uses hasoon2000 toolkit. Thanks for your time!
TheCount01 said:
Rick. Like you, I want to bring my T-Mobile HTC Amaze back to stock so that I can upgrade to ICS. The phone was bought on eBay with GB and a custom rom. I'd like to follow your steps but it had a lot of question marks and/or needed confirmation. Will you post exactly what you did?
Your steps seems a lot easier than what I've been researching. Is it really that simple? It makes sense. Everyone else uses hasoon2000 toolkit. Thanks for your time!
Click to expand...
Click to collapse
You don't need to go back to stock you just need to download the factory ics ruu or a rom that stock like. The hasoon toolkit is more of a guide to help you with the process try to read it an maybe you can rom your cell with a better one!
Sent from my HTC_Amaze_4G using xda app-developers app
S-off
FutureAirways said:
You don't need to go back to stock you just need to download the factory ics ruu or a rom that stock like. The hasoon toolkit is more of a guide to help you with the process try to read it an maybe you can rom your cell with a better one!
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply. That makes sense, too. Plus, it'll save me a step. I'm new to Android and got a lot to learn. With the help of xda-developers, I've learned a lot these past three weeks.
From what I've been reading, it's apparent that I need to have S-off before I do any flashing. Like I mentioned, I bought the phone with a custom rom. I'm guessing if it has a custom rom, then it was S-off at one time. If so, I should be able to S-off easily. Since I didn't flash the phone, I'm not sure what program is installed. Your knowledge and experience will be greatly appreciated if you can tell me if I'm able to S-off easily and how. Whenever I go into HBOOT I see the following:
***UNLOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0008
eMMC-boot
FASTBOOT
<vol up> to previous item
<vol Down> to next item
<Power>
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Edit:
Thanks for the below suggestions - think I have it figured out.
Installing the stock recovery will removed the tampered error, there's no way while you're s-on to set the bootloader to locked, it will list as re-locked if you run the lock command against it.
You'd need to s-off to return it fully back to the stock settings.
I recently s offed my phone and as long as you read and reread the instructions you will be fine. Make sure that whichever ROM you are using is rooted, at first I ran an RUU and attempted to s off without root and it didn't work so I gave up for a month. Also I found Hansoons s off tool helpful.
Sent from my ADR6425LVW using xda app-developers app
mjones73 said:
Installing the stock recovery will removed the tampered error, there's no way while you're s-on to set the bootloader to locked, it will list as re-locked if you run the lock command against it.
You'd need to s-off to return it fully back to the stock settings.
Click to expand...
Click to collapse
Could you list the order in which I should do things? Like first I should get S-Off - then are there two things I have to install? I really need baby instructions.....Re:
1) S-Off
2) Run this
3) Run this
I'm debating whether I should just say f* it and leave it "Re-Locked" by following the instructions listed on that site and running the ICS RUU.
But I dunno....just wanna get the phone back to them ASAP and hoping to not have to spend hrs on it.....
Alright people, I need help. I have an HTC Rezound (obviously) for verizon. I want to go back to Complete Stock, (as if it were brand new).
It was unlocked using HTC devs method
Its rooted
It is s-on
The recovery file i used is : recovery-ra-vigor-3.16-gnm
I installed a custom rom: Business_ICS4.0.3_Sense3.6-v6.3
Android version 4.03.605.2
HTC Sense 3.6
How do i get my phone to be:
Completely stock
Stock rom
no root
Locked title in Hboot
fix the tampered title in hboot
Any help is much apreciated
Are you doing this to warranty it? It will say "relocked" when you are done. It hasn't been a problem for anyone in the past though, you should still be able to return it to Verizon.
Instructions on how to return to stock are here:
http://forum.xda-developers.com/showpost.php?p=38244272&postcount=10
You probably should use the latest official RUU (prior to the OTA they just rolled out a couple days ago) which is 3.14.605.12. The link I have is to an .exe file. You just connect your phone to your pc and then double click. It will take you through the steps.
Get it here:
http://androidfiles.org/ruu/?dir=Vigor
That will get you back to stock, unrooted and it will say "relocked".
There was a global leak that wasn't official. If you want to use that, get it here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
This is a zip file you put on your external sd card. Follow instructions in the first link I gave you.
THANK YOU
feralicious said:
Are you doing this to warranty it? It will say "relocked" when you are done. It hasn't been a problem for anyone in the past though, you should still be able to return it to Verizon.
Instructions on how to return to stock are here:
http://forum.xda-developers.com/showpost.php?p=38244272&postcount=10
You probably should use the latest OTA, prior to the one they just rolled out a couple days ago which is 3.14.605.12. The link I have is to an .exe file. You just connect your phone to your pc and then double click. It will take you through the steps.
Get it here:
http://androidfiles.org/ruu/?dir=Vigor
That will get you back to stock, unrooted and it will say "relocked".
There was a global leak that wasn't official. If you want to use that, get it here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
This is a zip file you put on your external sd card. Follow instructions in the first link I gave you.
Click to expand...
Click to collapse
Thank you so much it worked like a charm!!! You just saved me from a weeks worth of searching i did and a couple of headaches.. Thank you very much
You're welcome, glad it worked for you!
I noticed I typed the wrong thing when I said "latest OTA", I should have said "latest official RUU" (don't know what was going on in my head) so I'm going to edit that post to fix it for any future readers.
okay, im having the same problem, except im s-off. i need to send my rez back for warranty reasons, i have a custom rom, my h-boot says locked, s-off, 2.27.000. any help would be awsome! thanks!
motodanr1 said:
okay, im having the same problem, except im s-off. i need to send my rez back for warranty reasons, i have a custom rom, my h-boot says locked, s-off, 2.27.000. any help would be awsome! thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=
Sweet, thanks! When I click on the link I get "no thread specified" though ..?
Sent from my ADR6300 using xda app-developers app
Go into dev, sticky, roll up thread. Click on back to s-on link
Phaded said:
http://forum.xda-developers.com/showthread.php?t=
Click to expand...
Click to collapse
I was Tampered/Locked and s-off. I ran the 4.03.605.2 RUU twice then its said locked the tampered was removed. I used the mini-adb_vigor program to achieve S-ON. Open a Command prompt wtih admin privileges and enter these commands pressing enter after each one. Now I am completely back to Locked S-ON. Hope this helps.
cd c:\mini-adb_vigor
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
netookska05 said:
I was Tampered/Locked and s-off. I ran the 4.03.605.2 RUU twice then its said locked the tampered was removed. I used the mini-adb_vigor program to achieve S-ON. Open a Command prompt wtih admin privileges and enter these commands pressing enter after each one. Now I am completely back to Locked S-ON. Hope this helps.
cd c:\mini-adb_vigor
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Click to expand...
Click to collapse
Make sure to run this on a stock hboot or it will brick.
I am having a similar issue. I am rooted, I never relocked my bootloader, stock minus a few mods, but the ota update keeps failing. What do I need to do to be able to accept the update so it stops rebooting my phone?
Been a lurker for a while, now I need some input if possible. I have a Thunderbolt whose touchscreen is not fully working, there is a strip about 1/4" wide top to bottom that does not respond to input. I rooted it using trter's Thunderbolt Tool and have been running Santod's ICS. When I decided to return to stock I did not read anything and merely ran trtr's tool and used the unroot option. This has me stuck now with a weird state.
Boot screen:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011, 14:51:08
4ext recovery is still installed for some reason.
Here are things I have tried:
1. Unroot using trtr's tool - leaves me in a non-booting state with a Security warning and Main Version failure.
2. Used HTCDev unlock and pushed PG05IMG.zip of 2.11.605. This allows me to boot to a seemingly stock ROM.
3. OTA's get pushed, device reboots but OTA's fail to install.
4. Tried recovering Nandroid backups with 4ext, no matter which one I try to restore I get stuck in a boot loop (BAMF SoaB, ICS Santod, Liquid ICS, Multi-source ICS, ICS stock deodex).
5. Tried using 4ext to install the above ROMS directly, along with full wipes and partition formats before each attempt. They seem to install but get stuck in a boot loop on each.
6. Other various combinations of HTCdev, Thunderbolt Tool, FastBoot boot.img pushes, etc. Trtr's tool connecting in booted and fastboot modes fails to unroot or root or change S-ON state.
7. Did step 2 again to get me a working phone (except touch screen problem) until I can figure out WTH is going on.
Current state - the above Boot Screen details, 2.11.605.19 deodexed-signed image, and lucky I have not totally bricked it yet.
Help please? I've googled for the last 3 days and read countless posts and am not sure what to do from here. All I need is to get it back to stock so I can send it back to HTC and get a replacement. I have a working ADB set up and am willing to follow steps exactly or read whatever page you believe I have missed, or call me a dumb n00b, berate me for not reading something, anything... at this point I have no interest in retaining data on the phone or SD card or my dignity, just a stock phone that I can send back.
Thanks all!
Me too
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
That's major coincidence I have exact same problem, down to dead touch screen strip. I've been trying to get unrooted for a week and was supposed to mail the thing back last Friday . .
Here's hoping a solution gets posted. I don't want to pay cuz the insurance refurb was fail, when my warranty service is supposed to be free replacement and it is stupid hardware failure.
All I can say is trter supposedly updated his tool to work with the latest ota, but its been about a week and he hasn't released it yet.
He did say something about having a problem with his host though.
washuai said:
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Click to expand...
Click to collapse
This is how I fixed the security warning when I first got it, using HTCDev unlock. I also used adb fastboot relock to lock back before trying the tool.
washuai said:
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
Click to expand...
Click to collapse
Yep - got that too...
Weird. Guess I'll wait for the new tool and see what it does...
As far as the identical touchscreen issue, this phone is also a refurb, my second with a touchscreen problem. The really weird part is that it works sometimes, particularly after all this work flashing and re-flashing, but I don't think it has anything to do with the ROMS or software, rather the fact that during all this work I am constantly doing battery pulls and SD card swaps and maybe it's because of a flaky ribbon connection or something - if it was not under warranty I would open it up and just try reseating anything I could find inside.
Have you tried to RUU back? It is a way manufacturers refurb or make the software new again without having to figure out what state it is in.
As long as you can get in fastboot it will work... Also could you possibly fastboot an ENG HBOOT? It doesn't show if it's unlocked nor does
it have any of those pink banners up at top.... Those I believe allow you to flash anything you couldn't normally do before... Try that.. Also I
ALWAYS manually push and flash my stuff through ADB and fastboot. It is faster (if you know what you are doing) AND it has better control
over what I am doing. I made a tut on how to flash boot screens (the very first image that comes up when you turn it on) and it is just about
same commands to flash normally stuff.
I run a Linux Box and always use root terminal so I am not certain at what point you would need superuser if any but as follows
#fastboot devices
#fastboot flash zip "name of zip" (no it doesn't have to be called anything specific, it could be called file1.zip)
#fastboot erase [option] /cache /data /system
to force it into the special RUU mode to use HTC's RUU, this is the command
#fastboot oem rebootRUU
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
jnorth said:
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
Click to expand...
Click to collapse
If you can give me today and I'll send you either the link to download the RUU or the exe itself.
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
The ota's don't install because of the custom recovery.
Backups don't work because your s-on and the kernel can be installed.
You may be able to install santod's ota rom in recovery and install the boot.IMG from the rom (kernel) in fasboot = ./fastboot flash boot boot.img
Relock the boot loader and send it in looking like stock.
There is also a way to spoof your main version and downgrade from ICS to GB Ruu stock. That is posted on another site.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
tburns said:
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
Click to expand...
Click to collapse
Working on this now, as soon as I figure out how to get s-off again. Thanks!
http://androidfiles.org/ruu/?developer=Mecha
The RUU's to take you back to stock
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
jnorth said:
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
Click to expand...
Click to collapse
that is what the community is all about , right?
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
you could ALWAYS use an ENG and nobody would be non-the-wiser if you rooted or not! It would look like a developer phone instead..
when it says ***RELOCKED*** it tells anybody and everybody you have been rooted at one point or another (no bueno for warranty)
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
this -SHOULD- take care of the pink banner up at top BE CAREFUL WITH THIS!!!
there again... I run constant root terminal so I do not know if it requires root or not soooo.....
#fastboot oem mw 8d08ac54 1 31302E30
#fastboot flash hboot whateverhbootfile.nb0