Related
I've read revone leaves hboot stock... is that even after changing the flag? Is it safe to s-on again?
After hunreds of pages read I haven't seen it explicitly stated so just wanted to confirm I am not set up for failure.
Also will it still not say tampered?
Thanks!
I'd just leave it S-OFF. It's recommended only to go back to S-ON again if you're running a 100% stock device (e.g. you've just run an RUU) as it can brick the phone otherwise
EddyOS said:
I'd just leave it S-OFF. It's recommended only to go back to S-ON again if you're running a 100% stock device (e.g. you've just run an RUU) as it can brick the phone otherwise
Click to expand...
Click to collapse
How about with an adb backup restored, flag off and relocked?
I guess my concern is what does the flag change and should I turn it back on before s-on or just leave it? This is purely informative.
Turning your security flag back on will re enable the checks the phone does when booting. It's making sure all the parts (hboot, radio, etc....) are signed. If you flashed a radio or hboot that's unsigned (like the one from revone or moonshine) the device will simply not boot. One of the ways to cause a Perma brick which can only be fixed with a jtag jig which doesn't exist yet for the one
Sent from my Tricked out HTC One
The first post of the thread used to say it's safe to do (although as I type it I feel like I spelt it wrong)
fastboot oem writesecureflag 3
It's fine, if you want to do it, but there's little point before flashing everything else to stock and returning it for warranty.
Guys pls help, I need to unroot and relock my HTC One device for repair purposes.. I want to send it back to HTC Service Center and claim back the warranty to fix the camera problem. Thanks alot
[SOLVED]
Fully stock and downgraded to H-Boot 1.44 Android 4.1.2
Thanks to @nkk71
mctodd said:
Guys pls help, I need to unroot and relock my HTC One device for repair purposes.. I want to send it back to HTC Service Center and claim back the warranty to fix the camera problem. Thanks alot
Click to expand...
Click to collapse
Their are guides and even Youtube videos that give you step by step directions on how to accomplish this. Just check the threads and or Youtube
blakphoenix said:
Their are guides and even Youtube videos that give you step by step directions on how to accomplish this. Just check the threads and or Youtube
Click to expand...
Click to collapse
Thanks for the reply, but mostly in youtube where out of date..
mctodd said:
Thanks for the reply, but mostly in youtube where out of date..
Click to expand...
Click to collapse
mctodd said:
Hi nkk71, I know it's a bit annoying to have someone bothering you but seems like your the one the good guys that can patiently help some one frustrated on going back to stock (like brand new). I am having a problem on going back to stock. Here is my spec on Bootloader mode.
M7_U Htc One model
Hboot-1.54.0000
Radio-4A.17.3250.14
OpebDSP-v31.120.272.0617
OS-2.24.707.3
EMMC-boot
HTC_044
One of my problem also is i rooted it with mac and there is no unrooting instructions for mac.. Pls help if you have any idea, i just have to send it back to repair. Thanks.
P. S i am willing to pay via paypal if necessary
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (and remove IMEI and s/n before posting)
Also what ROM are you on now?
EDIT: payment will not be necessary, all I ask is if I helped you hit the thanks button
nkk71 said:
can you post a "fastboot getvar all" (and remove IMEI and s/n before posting)
Also what ROM are you on now?
EDIT: payment will not be necessary, all I ask is if I helped you hit the thanks button
Click to expand...
Click to collapse
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
mctodd said:
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
Click to expand...
Click to collapse
No worries, do it later, as I'm not on s computer either for the time being. I'll be on again later, but only for an hour or two, so it might have to wait till tomorrow anyway.
Sent from my HTC One using Tapatalk
This your firmware ? 2.24.707.3
Do you have a nandroid backup of it ?
What does it say on your bootloader ?
also, on a mac you will need to type the following before any command:
./
so ./adb devices
./fastboot devices
mctodd said:
I am not in my computer at the moment cuz im at work im just using my One, the Rom that i am using at the moment is Android Revolution HD 13.1. Is it ok to fastboot through fx app so i can send you the info..
Click to expand...
Click to collapse
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Thanks for yours patient on making this replies and research man.. i really do appreciate it.
Heres the screen shot that you requested earlier.
I am a bit confused with this OS-2.24.707.3 and build number 2.24.401.8 Which one is really my ROm version?? Any idea?
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi nkk71, I am confused which version of ROM that i have.. Im afraid to download it might be a wrong one.
In bootloader Mode I can see this O.S-2.24.707.3
but in settings i can see a build number 2.24.401.8 CL235216 release keys which one will i download for RUU Stock
mctodd said:
Hi nkk71, I am confused which version of ROM that i have.. Im afraid to download it might be a wrong one.
In bootloader Mode I can see this O.S-2.24.707.3
but in settings i can see a build number 2.24.401.8 CL235216 release keys which one will i download for RUU Stock
Click to expand...
Click to collapse
Bootloader shows the "more" correct version x.xx.707.x
In settings it only shows the ROM you are based on.
Go for the RUU with .707. in it.
Keep s-off for the time being, that will allow u to change in case u need to. I have to sign off for today...
Sent from my HTC One using Tapatalk
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
nkk71 said:
Bootloader shows the "more" correct version x.xx.707.x
In settings it only shows the ROM you are based on.
Go for the RUU with .707. in it.
Keep s-off for the time being, that will allow u to change in case u need to. I have to sign off for today...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks alot man.. Your such a help..
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi nkk71, is it possible to flash the ruu that you linked above to back to stock so i'll be able to run rumrunner S-off.. Cuz i tried in ARHD 13.1 didnt work after 8 pouring it says "please wait 30 seconds and run rumrunner again,press enter to exit" I had multiple attempts already and never worked..
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
Hi there nkk71, did you see my new THREAD?? Pls help me man im in big trouble now. cannot flash a rom. Even though its successfully installed keeps bringing me back to recovery. thanks in advance
mctodd said:
Hi there nkk71, did you see my new THREAD?? Pls help me man im in big trouble now. cannot flash a rom. Even though its successfully installed keeps bringing me back to recovery. thanks in advance
Click to expand...
Click to collapse
I'll get back to u in an hour or two...
Sent from my HTC One using Tapatalk
nkk71 said:
Well this is going to be a bit of good news / bad news.
Good news, there's a full RUU exe for you:
http://www.htc1guru.com/dld/ruu_m7_..._10-30-1131-05_release_309365_signed_2_4-exe/
Bad news it's a Windows executable, so you'll need to run that from a Windows PC. This will however allow you to go 100% stock!!!!
BUT, BEFORE THAT, there are some prerequisites. I'll outline the steps:
1- You need to get S-Off. since you're on 1.54 you need to use rumrunner.us method (which is either Windows or Linux, I think). This would involve a stock ROM as well, I don't know if ARHD 13.1 will do or not. It's something you have to check on the rumrunner thread. I havent looked into it much, so you're going to need help from someone else and/or do some reading into this.
2- Once S-Off, you need to remove the TAMPERED sign: http://forum.xda-developers.com/showthread.php?t=2477792
3- While still on S-Off, you need to "LOCKED" your bootloader (not "RELOCKED"): http://forum.xda-developers.com/showthread.php?t=2475914
4- Finally run the above RUU, because you are S-Off it WILL allow you to downgrade. Since it's a full RUU it should put your phone completely back to stock (and not even break the touchscreen drivers, the way nandroid backups do).
EDIT: and it will update everything to stock: hboot, recovery, ROM, etc. so no need to mess with all that, unlike most users
IMHO, keep S-Off, as some phones do ship S-Off. The only dead giveaways that you "messed" with your phone, are the TAMPERED, RELOCKED, and red text at boot-up.
However if you are more comfortable with S-On ("fastboot oem writesecureflag 3") ONLY do so after you are completely satisfied that everything is back to stock.
So it looks like you're going to need a Windows PC, but other than that, you can go back to fully 100% stock "relatively" easily compared to what many have and are going through.
Click to expand...
Click to collapse
At number 4. Did mean that i have to manually downgrade or it is automatic??
mctodd said:
At number 4. Did mean that i have to manually downgrade or it is automatic??
Click to expand...
Click to collapse
It's automatic. If there's an error let me know
Keep S-Off !!
nkk71 said:
It's automatic. If there's an error let me know
Keep S-Off !!
Click to expand...
Click to collapse
I did run the RUU 2.26.707.5, it didnt succeed..I says wrong MID..!!Could i change MID since im S-Off at the moment? but my bootloader is already locked.
mctodd said:
I did run the RUU 2.26.707.5, it didnt succeed..I says wrong MID..!!Could i change MID since im S-Off at the moment? but my bootloader is already locked.
Click to expand...
Click to collapse
my bad, didnt check your MID, anyway instead of changing it download this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
for simplicity, rename the file to "ruu.zip" and place it in your adb folder.
it's a RUU zip file not exe, so you need to flash it:
so get to bootloader/FASTBOOT USB (either using "adb reboot bootloader" or POWER + VOLDOWN buttons)
then:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes twice, the first time it will come back with "failed flush again", the second time it should report success
fastboot reboot-bootloader
fastboot getvar all <- to confirm it downgraded
nkk71 said:
my bad, didnt check your MID, anyway instead of changing it download this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
for simplicity, rename the file to "ruu.zip" and place it in your adb folder.
it's a RUU zip file not exe, so you need to flash it:
so get to bootloader/FASTBOOT USB (either using "adb reboot bootloader" or POWER + VOLDOWN buttons)
then:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes twice, the first time it will come back with "failed flush again", the second time it should report success
fastboot reboot-bootloader
fastboot getvar all <- to confirm it downgraded
Click to expand...
Click to collapse
Once it succeeded it is ready for service repair to claim warranty? Thanks
There is no ruu for my phone (02___001) so now I have s off I was going to run a stock ruu and update to the latest firmware. If I send the phone back for repair and change my cid to HTC_001 would HTC know I have changed my cid even if I s on?
Anyone help me at all?
stovie_steve said:
Anyone help me at all?
Click to expand...
Click to collapse
Two things:
1- I dont know if they keep a record of IMEI (or s/n) <--> carrier, but I think they have to and do.
2- the CID is stored in several partitions, not only the one you change with fastboot writecid.
HOWEVER, it really depends on how far they're going to dig into this, if they are going to check their IMEI database or check the different partitions on the phone, just to "prove you wrong", I guess they could.
But then again, would it be worth all that hassle for them?
I dont have any experience with repair centers or how far they would go to prove that you changed something on your phone, and it's really quite country (and HTC people) dependent; for some they have no problem with an unlocked or relocked phone, and other even have a problem with S-Off (though they can't prove the phone didn't ship that way in the first place)
Better have someone from your region (O2 so UK?) post their experience(s)
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
stovie_steve said:
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
Click to expand...
Click to collapse
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
nkk71 said:
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
Click to expand...
Click to collapse
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
stovie_steve said:
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
Click to expand...
Click to collapse
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
nkk71 said:
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
Click to expand...
Click to collapse
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
stovie_steve said:
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
Click to expand...
Click to collapse
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
stovie_steve said:
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
Click to expand...
Click to collapse
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
stovie_steve said:
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
Click to expand...
Click to collapse
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
nkk71 said:
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
Click to expand...
Click to collapse
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
stovie_steve said:
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
Click to expand...
Click to collapse
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
nkk71 said:
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
Click to expand...
Click to collapse
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
stovie_steve said:
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
Click to expand...
Click to collapse
Ok, my thoughts, in a nutshell
1. Unlock bootloader via HTC dev <- YES
2----- try rumrunner 3.62
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off <- Ok, try, if it fails use above rumrunner 3.62
Once S-Off:
--- remove tampered: revone or http://forum.xda-developers.com/showthread.php?t=2477792
5. Restore nandroid backup for my 02 version 1.28.206.7
--- set phone to LOCKED, using revone (or http://forum.xda-developers.com/showthread.php?t=2475914)
------- you will need to have SU privileges which you can get using revone or flashing SuperSU; if you do flash SuperSU, uninstall it after getting LOCKED
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match) <- Yep
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Once you have your bootloader "LOCKED", no TAMPERED, no red text on bootup, do "fastboot oem writesecureflag 3"
reboot three times and see if everything sticks, and don't take any other OTAs.
Hit me with a thanks if this was useful
So you think I shouldn't upgrade to the latest OTA once I get s on?
stovie_steve said:
So you think I shouldn't upgrade to the latest OTA once I get s on?
Click to expand...
Click to collapse
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
nkk71 said:
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
Click to expand...
Click to collapse
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
nkk71 said:
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
Click to expand...
Click to collapse
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
stovie_steve said:
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
Click to expand...
Click to collapse
the touchscreen drivers were part of the 2.xx firmware package, not hboot, so if you don't use a full RUU, it will break the touchscreen drivers, but you can use an OTG cable + mouse.
stovie_steve said:
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
Click to expand...
Click to collapse
Unfortunately you can't (anymore), but this one should be close enough: http://d-h.st/users/guich/?fld_id=25920#files, or the best thing is to get a hold of the OTA 3.62.206.1 file and extract it from it.
Anyway, in my humble opinion, first things first: unlock using HTCdev and see if you can get rumrunner to S-Off on 3.62.
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
kenzorio said:
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
Click to expand...
Click to collapse
You can go S On again any time
He advised you should not make it S On
because keep your SOff is beneficial
your phone is GPE so that's had firmware problem after 1.55 locking Bootloader it cant be unlocked if you are on S On that time
if you keep S Off you can Unlock your phone easily
as you know 1st time you need Unlock Bootloader then you make S Off but if you update Hboot then Lock Bootloader then S On its quiet hard to make it S Off again and using root custom Roms etc
IF YOU NOT UNDERSTAND ANSWER DONT WRITE A NEW THREAD ASK AGAIN IN SAME THREAD WE WILL HELP YOU THERE
kenzorio said:
In response to my Q below, a user wrote that if I go S-ON (to take the phone into repair) I can never go S-ON again. Is that true? I've restored my phone 100% to stock HBOOT, recovery OS etc. and I'm presently at HBOOT 1.57 and have locked the bootloader and have "*** LOCKED ***". So the only thing left is to go S-ON. But I'm wondering if this means I can never go S-ON again.
Thanks!
The original question: http://forum.xda-developers.com/htc-one/help/restore-m7-to-stock-q-hboot-t2999854
Click to expand...
Click to collapse
I did not mean you can never go s-off again. Most likely you phone will be returned with the latest software and hboot 1.57 installed and you'll have to pay to s-off. Many here have sent their phone to repair with s-off and had no problems getting repair.
and their phones were returned to them still s-off
clsA said:
I did not mean you can never go s-off again. Most likely you phone will be returned with the latest software and hboot 1.57 installed and you'll have to pay to s-off. Many here have sent their phone to repair with s-off and had no problems getting repair.
and their phones were returned to them still s-off
Click to expand...
Click to collapse
OK just to clarify - it originally wasn't a GPE. I converted it to GPE, and now I converted it back to stock (incl HBOOT, recovery etc.). Btw, in the post I mistakenly asked if it meant I could never go S-ON again. What I meant to ask was if I couldn't get S-OFF again!
But you say I have to pay to get S-OFF again. Is that because Sunshine is the only way to get S-OFF with HBOOT >= 1.57? Any chance that a free tool will come out that works as well?
Thanks
Moderator Information,
I will keep this thread open as you are getting help on it, but in future can you please keep to one thread per topic.
Thanks.
Hi guys
Basically I need to send my device into HTC for repair. It is S-OFF and I have a stock HTC European _001 rom on it. I really really need to restore to the UK O2_001 stock rom and get back to S-ON to avoid any possible issues with the warranty.
The problem is I can't find any O2 UK zips or nandroid backups to flash. For some reason the RUU files do not work for me, and I really don't have the time to be troubleshooting this.
I would really appreciate it if someone could upload a nandroid backup that I can use very soon? Otherwise I'll need to stick with the unbranded HTC Europe rom and risk them knowing I've unlocked the device.
Thanks for any help.
fade2black101 said:
Hi guys
Basically I need to send my device into HTC for repair. It is S-OFF and I have a stock HTC European _001 rom on it. I really really need to restore to the UK O2_001 stock rom and get back to S-ON to avoid any possible issues with the warranty.
The problem is I can't find any O2 UK zips or nandroid backups to flash. For some reason the RUU files do not work for me, and I really don't have the time to be troubleshooting this.
I would really appreciate it if someone could upload a nandroid backup that I can use very soon? Otherwise I'll need to stick with the unbranded HTC Europe rom and risk them knowing I've unlocked the device.
Thanks for any help.
Click to expand...
Click to collapse
if you want to follow my guide http://forum.xda-developers.com/showthread.php?t=2541082
Files you'll need are in post #7 under "HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102"
EDIT: there's also this RUU http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353143_signed_2.exe
but as mentioned in my guide, i don't encourage going s-off to s-on on newer firmware
nkk71 said:
if you want to follow my guide http://forum.xda-developers.com/showthread.php?t=2541082
Files you'll need are in post #7 under "HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102"
EDIT: there's also this RUU http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353143_signed_2.exe
but as mentioned in my guide, i don't encourage going s-off to s-on on newer firmware
Click to expand...
Click to collapse
Hello, thanks for that
Unfortunately I can't seem to downgrade the bootloader. I'm on 1.61.
Not entirely sure what to do now.. Will it be possible to achieve S-ON again and lock the bootloader without downgrading the hboot?
I don't really have time to spend ages on this, as the phone will be getting collected on Friday and I'm busy with work. I also don't really have time to troubleshoot the 100000 reasons why RUU.exe files aren't working for me and why I can't downgrade the bootloader. May just have to send it in unlocked and hope for the best.
fade2black101 said:
Hello, thanks for that
Unfortunately I can't seem to downgrade the bootloader. I'm on 1.61.
Not entirely sure what to do now.. Will it be possible to achieve S-ON again and lock the bootloader without downgrading the hboot?
I don't really have time to spend ages on this, as the phone will be getting collected on Friday and I'm busy with work. I also don't really have time to troubleshoot the 100000 reasons why RUU.exe files aren't working for me and why I can't downgrade the bootloader. May just have to send it in unlocked and hope for the best.
Click to expand...
Click to collapse
so quick and dirty? (and hope for the best)... did you use sunshine to s-off? before i post the steps.
haha
And yes I did. And I plan to use it again when I get phone back. Let me know your suggestion and I'll give it a go when I have some time
fade2black101 said:
haha
And yes I did. And I plan to use it again when I get phone back. Let me know your suggestion and I'll give it a go when I have some time
Click to expand...
Click to collapse
okay cool, i only asked because sunshine will work again (without needing to pay again), in case that infamous "tamper detected - rebooting" happens (shouldnt in your case but just in case it does)
gimme a few minutes, and i'll post instructions with links....
Thanks
I will check this out tomorrow when I have some time
fade2black101 said:
Thanks
I will check this out tomorrow when I have some time
Click to expand...
Click to collapse
okay, should be easy enough:
1) download Guru_Bootloader_Reset_1.0.zip and put it on your virtual storage
2) download 4.19.401.9-TWRP2633_combined_nowipe.zip
if need be change cid to a compatible one:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
flash firmware
Code:
fastboot oem rebootRUU
fastboot flash zip 4.19.401.9-TWRP2633_combined_nowipe.zip
fastboot flash zip 4.19.401.9-TWRP2633_combined_nowipe.zip
fastboot reboot-bootloader
set back O2 UK cid:
Code:
fastboot oem writecid O2___001
fastboot reboot-bootloader
3) go to RECOVERY (it should be TWRP 2.6.3.3 from the file above) and run the Bootloader Reset
--> remove TAMPERED
--> set LOCKED
4) go back to bootloader, and check it says LOCKED, and no more TAMPERED
5) download RUU_4.20.206.16.EXE
and run it
(if it "exits" for some unknown reason, make sure you have this installed vcredist)
6) reboot the phone to make sure it boots up fine, do not take OTA updates
7) if you really insist, go s-on
Code:
fastboot oem writesecureflag 3
8) reboot three times (do not take any OTAs, especially above 6.xx), and make sure no TAMPERED is triggered
nkk71
You're a star! Thank you so much for that. After hours spent fumbling about I spent 20 minutes following your instructions today and everything worked perfectly. The Visual C++ file you suggested did the trick too, even after I installed several other (wrong ones) yesterday. Really happy this is finally sorted
Just a quick question. I haven't gone back to S-ON yet. I think it may not be neccessary for the warranty, but maybe I shouldn't risk it as I can always just gain S-OFF again via Sunshine once I get the phone back (unless they inexplicably change the motherboard). I'm wondering if there is a high risk of bricking my device if I run that S-ON command?
Cheers once again!
fade2black101 said:
nkk71
You're a star! Thank you so much for that. After hours spent fumbling about I spent 20 minutes following your instructions today and everything worked perfectly. The Visual C++ file you suggested did the trick too, even after I installed several other (wrong ones) yesterday. Really happy this is finally sorted
Just a quick question. I haven't gone back to S-ON yet. I think it may not be neccessary for the warranty, but maybe I shouldn't risk it as I can always just gain S-OFF again via Sunshine once I get the phone back (unless they inexplicably change the motherboard). I'm wondering if there is a high risk of bricking my device if I run that S-ON command?
Cheers once again!
Click to expand...
Click to collapse
there's no risk in bricking using that "fastboot oem writesecureflag 3" command to set s-on; the RUU would have set everything back to stock; if in the unlikely event the "TAMPERED" comes back, you'll need to s-off again, and use my guide with the 1.xx RUU + nandroid method
as for sending it in S-OFF, it's really country/carrier/service centre/person specific.... from what i've seen UK is one of the most tolerant countries (some people have even sent the phone in with tamperd and running a custom rom, and still got the camera fixed)
but it's your call, i cant really say for sure how they would react.
and if all is good now, could you also edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks and good luck