[Q] HTC One Backup SMS without ROOT - One (M7) Q&A, Help & Troubleshooting

I have a customer who's unrooted HTC One is bootlooping after he did an update that he doesn't recall the name of. He doesn't have nor has he ever had root or a custom ROM. He is extremely keen to get his text messages from the phone, and I am wondering if there is a step by step process I could undertake to try and recover those ?
I can get to download mode and to another mode which offers factory reset etc..

Anyone able to help please?

networkn said:
I have a customer who's unrooted HTC One is bootlooping after he did an update that he doesn't recall the name of. He doesn't have nor has he ever had root or a custom ROM. He is extremely keen to get his text messages from the phone, and I am wondering if there is a step by step process I could undertake to try and recover those ?
I can get to download mode and to another mode which offers factory reset etc..
Click to expand...
Click to collapse
I won't be able to help, but maybe this COULD help:
1- are you still on hboot 1.44? that COULD give a glimmer of hope, as you could use revone to unlock without wiping
2a- if however you are on hboot 1.54+, then (to the best of my knowledge) you need to use HTCdev to unlock, and that WILL WIPE everything
2b- if you are on hboot 1.54+, you could use a Java Card to get S-Off, then downgrade to hboot 1.44 (NB: I do not know if a Java Card wipes anything!!!)
why hboot 1.44, because it allows for "fastboot boot <name of custom recovery>.img", where you would be able to use adb commands to pull the sms database (I think it's stored in "/data/data/com.android.providers.telephony/databases/") though you would still need to find a way to decode the sql db.
I use this: https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore&hl=en to backup SMS messages to an xml file (doesnt work for MMS), but you need a functioning ROM for that.

nkk71 said:
I won't be able to help, but maybe this COULD help:
1- are you still on hboot 1.44? that COULD give a glimmer of hope, as you could use revone to unlock without wiping
2a- if however you are on hboot 1.54+, then (to the best of my knowledge) you need to use HTCdev to unlock, and that WILL WIPE everything
2b- if you are on hboot 1.54+, you could use a Java Card to get S-Off, then downgrade to hboot 1.44 (NB: I do not know if a Java Card wipes anything!!!)
why hboot 1.44, because it allows for "fastboot boot <name of custom recovery>.img", where you would be able to use adb commands to pull the sms database (I think it's stored in "/data/data/com.android.providers.telephony/databases/") though you would still need to find a way to decode the sql db.
I use this: https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore&hl=en to backup SMS messages to an xml file (doesnt work for MMS), but you need a functioning ROM for that.
Click to expand...
Click to collapse
Thanks for your help, how do I determine what versions of whatever I have?

Hmm what is the best step by step guide I can follow to recover my device if it's bootlooping? I can get into download mode and recovery mode.

networkn said:
Thanks for your help, how do I determine what versions of whatever I have?
Click to expand...
Click to collapse
in bootloader: HBOOT-1.xx.xxxx

Related

Vivid will not reboot after flash or Juopunut S-off

I was trying to obtain S-off through Juopunut Bear, but after it finds my device and tries to reboot it into its program, it simply doesn't reboot. The phone then will not start at all unless I pull the battery and boot into Hboot. From there I flashed my backup img through fastboot and I was good. I found this thread that said I need to ICS 3.32 firmware. On my phone I noticed I am on Software number 3.26.502.56, so I tried to flash the provided download of 3.32 using fastboot. And it did the same exact thing! Would not reboot, and had to battery-pull and re-flash my backup to get it to work.
What is my problem here?
I am on a unlocked and rooted HTC Vivid running stock ICS and stock Kernel.
I really hope I am not committing a stupid error and wasting everyone's time, but it is possible. Thanks in advance for any help!
lonehunter65 said:
I was trying to obtain S-off through Juopunut Bear, but after it finds my device and tries to reboot it into its program, it simply doesn't reboot. The phone then will not start at all unless I pull the battery and boot into Hboot. From there I flashed my backup img through fastboot and I was good. I found this thread that said I need to ICS 3.32 firmware. On my phone I noticed I am on Software number 3.26.502.56, so I tried to flash the provided download of 3.32 using fastboot. And it did the same exact thing! Would not reboot, and had to battery-pull and re-flash my backup to get it to work.
What is my problem here?
I am on a unlocked and rooted HTC Vivid running stock ICS and stock Kernel.
I really hope I am not committing a stupid error and wasting everyone's time, but it is possible. Thanks in advance for any help!
Click to expand...
Click to collapse
If you can get hboot relock the bootloader and run the stock ruu file seems to work for ant errors I've ever gotten , then just go back and redo every thing but s off it should stay off .
Bigtjmc said:
If you can get hboot relock the bootloader and run the stock ruu file seems to work for ant errors I've ever gotten , then just go back and redo every thing but s off it should stay off .
Click to expand...
Click to collapse
Not sure I'm completely understanding you. I need to relock and run stock ruu, then redo everything except s-off? That kind of defeats the purpose, I am trying to s-off
lonehunter65 said:
Not sure I'm completely understanding you. I need to relock and run stock ruu, then redo everything except s-off? That kind of defeats the purpose, I am trying to s-off
Click to expand...
Click to collapse
Yes if you are having problems after any mod to the os just relock the bootloader and run the stock ruu file and it will fix the issue , then go back after you got the phone working right and then unlock the bootloader , flash recovery , root , ect .
But the s-off should stay off and you won't have to redo that step .
So basically you will be on a stock ics with s-off
Then just redo the process to get it where you want it .
Bigtjmc said:
Yes if you are having problems after any mod to the os just relock the bootloader and run the stock ruu file and it will fix the issue , then go back after you got the phone working right and then unlock the bootloader , flash recovery , root , ect .
But the s-off should stay off and you won't have to redo that step .
So basically you will be on a stock ics with s-off
Then just redo the process to get it where you want it .
Click to expand...
Click to collapse
I'm sorry but this just doesn't make sense, the phone is automatically S-On not S-Off, so it won't 'stay s-off'. You understand what I mean?
lonehunter65 said:
I'm sorry but this just doesn't make sense, the phone is automatically S-On not S-Off, so it won't 'stay s-off'. You understand what I mean?
Click to expand...
Click to collapse
did you succeed s-off ?
if you did the s-off procedure via " wire trick " was successful the relocking the boot loader will not change the s-off it will stay off ,
Then relock. Run ruu now you are stock ics with the s-off still , and all the errors should be fixed .
Then just re unlock bl , flash recovery , root , flash New custom Rom / kernel, ect.
All I'm saying is if you have s-off then your good ,
To fix all the errors run the ruu , only reason you need to relock bl is the ruu will reject the install if you are unlocked .
Bigtjmc said:
did you succeed s-off ?
if you did the s-off procedure via " wire trick " was successful the relocking the boot loader will not change the s-off it will stay off ,
Then relock. Run ruu now you are stock ics with the s-off still , and all the errors should be fixed .
Then just re unlock bl , flash recovery , root , flash New custom Rom / kernel, ect.
All I'm saying is if you have s-off then your good ,
To fix all the errors run the ruu , only reason you need to relock bl is the ruu will reject the install if you are unlocked .
Click to expand...
Click to collapse
Oh, we are talking past each other. I did not succeed s-off, when it reboots my phone via Control Bear it does not boot into the Juopunut program, and I have never had a chance to do the wire trick! Thanks for the help though.
lonehunter65 said:
Oh, we are talking past each other. I did not succeed s-off, when it reboots my phone via Control Bear it does not boot into the Juopunut program, and I have never had a chance to do the wire trick! Thanks for the help though.
Click to expand...
Click to collapse
I had trouble on my first S-OFF attempt. I had made a mistake (I missed one of the S-OFF prep steps in section 2 of the SuperGuide, which is at http://forum.xda-developers.com/showthread.php?t=1416836 ).
If you want to try again?
-If you have relocked your bootloader, flash your phone stock using your appropriate RUU while phone is in Fastboot mode.
*** If you haven't relocked bootloader yet, you can do it first via fastboot ("fastboot oem lock")
-Start at section 1 of the superguide (unlocking the bootloader, yeah it sucks to do the process again but thankfully htc makes it easy!)
-And then you can try S-OFF process again (section 2 in superguide)
I know this is for the Vivid but I have the same problem with my EVO 3D. And Can get any help from anyone over there. I just relocked the evo but dont know the next step. Can anybody help me here?
gaarak54 said:
I know this is for the Vivid but I have the same problem with my EVO 3D. And Can get any help from anyone over there. I just relocked the evo but dont know the next step. Can anybody help me here?
Click to expand...
Click to collapse
Download the ruu from HTC or you should be able to download it from the EVO 3d forum while in fastboot mode hook you phone up to your computer fastboot should change to fastbootusb then double click on the ruu and let it do its thing do not unplug till it is finished then you will be out of box stock
Sent from my HTC PH39100 using Tapatalk 2

[Solved]how to unroot and relock htc one devise in Mac and use full stock rom

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

S-Off issues... need help!

i apologize in advance for the noob issues... I am having issues trying to achieve s-off on my htc one. i am rooted right now, running stock 4.3 GPE rom. I have TWRP recovery installed. everything works perfectly. however i would like to do a complete conversion so i will recieve OTA updates from google, and not have to worry about flashing roms. so when i first tried to achieve s-off , i was using revone method. i was getting an error code (-1) then i read that that method wouldnt work, if you were running 4.3. so i then restored my nandroid backup, which i was running 4.1.2. but before flashing my backup i did a system wipe, just to be safe. so i tried revone method again. only now i get error code (-6) so i gave up. but i think when i did my system wipe , i lost my stock back up? so my 2 questions are, where is my nandroid backup? did i lose it when i did a system wipe? and how can i achieve s-off? i am not sure how to tell what firmware version i am running, i didnt see it in settings anywhere, nor do i know what hboot i have (1.44 or 1.54?) how do i tell? thanks guys!
ssreynolds said:
i apologize in advance for the noob issues... I am having issues trying to achieve s-off on my htc one. i am rooted right now, running stock 4.3 GPE rom. I have TWRP recovery installed. everything works perfectly. however i would like to do a complete conversion so i will recieve OTA updates from google, and not have to worry about flashing roms. so when i first tried to achieve s-off , i was using revone method. i was getting an error code (-1) then i read that that method wouldnt work, if you were running 4.3. so i then restored my nandroid backup, which i was running 4.1.2. but before flashing my backup i did a system wipe, just to be safe. so i tried revone method again. only now i get error code (-6) so i gave up. but i think when i did my system wipe , i lost my stock back up? so my 2 questions are, where is my nandroid backup? did i lose it when i did a system wipe? and how can i achieve s-off? i am not sure how to tell what firmware version i am running, i didnt see it in settings anywhere, nor do i know what hboot i have (1.44 or 1.54?) how do i tell? thanks guys!
Click to expand...
Click to collapse
Ok sir, I try to help you.
First, you need to have knowledge with ADB and fastboot, but you should have them both in a folder since you unlocked your device through HTCdev. Then open a terminal and navigate to this particular folder. When you connected your HTC One M7 with the computer and UNINSTALLED HTCSync you can type "adb devices" to ensure you have a connection to your cell phone. Then you have to boot into the bootloader with this command "adb reboot bootloader" and there you see on the first couple of lines your HBOOT version. You'll see it! Then you boot into the recovery from the bootloader and install a ROM from this side that matches a version of rumrunner s off: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html
Secondly then getting updates from Google you need to proceed these steps:
http://forum.xda-developers.com/showthread.php?t=2358781
This will turn your device into a Google Play Edition!
Hit the thanks button if you understood it, for questions simply ask again
LibertyMarine said:
Ok sir, I try to help you.
First, you need to have knowledge with ADB and fastboot, but you should have them both in a folder since you unlocked your device through HTCdev. Then open a terminal and navigate to this particular folder. When you connected your HTC One M7 with the computer and UNINSTALLED HTCSync you can type "adb devices" to ensure you have a connection to your cell phone. Then you have to boot into the bootloader with this command "adb reboot bootloader" and there you see on the first couple of lines your HBOOT version. You'll see it! Then you boot into the recovery from the bootloader and install a ROM from this side that matches a version of rumrunner s off: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html
Secondly then getting updates from Google you need to proceed these steps:
http://forum.xda-developers.com/showthread.php?t=2358781
This will turn your device into a Google Play Edition!
Hit the thanks button if you understood it, for questions simply ask again
Click to expand...
Click to collapse
that helps some, lol. so i now know how to find out what hboot version i have (i'm assuming that because i have 4.3 i am running hboot 1.54).... so thank you! i saw the rumrunner thread for the latest s-off. i will proceed with those steps... as far as completing the full google play conversion that actually sounds pretty easy once you have s-off. i can handle that. ( change cid to googl0001 and flash the new ruu, and stock recovery done!)
so now i just need to know what firmware version i have?
did i delete my back up when i did a system wipe?
To reiterate...
I am on hboot 1.44, rooted running a stock GPE 4.3 Rom. Also, I feel stupid, but I can't seem to find out what firmware version I have? So I have tried twice with no avail. First I tried the typical revone method , but i was getting an error code -1, because I was on 4.3. So I flashed my backup, and returned to my stock rom on 4.1.2, and tried again. This time I was getting an error code -6? So I temporarely gave up, until I saw the rumrunner method here on xda. Worst part is when I returned to stock, I did a system wipe before flashing back to my 4.3 GPE rom, and deleted my backup! So I am nervous about flashing anything else, being that I dont have a backup! Long story short, all I want to do is finish a complete GPE conversion, and I need s-off to change my CID. At this point, all I need to do is achieve s-off, flash the GPE CID, and then flash a stock recovery and I'm done! So any thoughts on how to help me achieve s-off without potentionally bricking this thing?
edit: my build number is JWR66Y.H1 , does this mean I am on 3.07.1700.1
ssreynolds said:
To reiterate...
I am on hboot 1.44, rooted running a stock GPE 4.3 Rom. Also, I feel stupid, but I can't seem to find out what firmware version I have? So I have tried twice with no avail. First I tried the typical revone method , but i was getting an error code -1, because I was on 4.3. So I flashed my backup, and returned to my stock rom on 4.1.2, and tried again. This time I was getting an error code -6? So I temporarely gave up, until I saw the rumrunner method here on xda. Worst part is when I returned to stock, I did a system wipe before flashing back to my 4.3 GPE rom, and deleted my backup! So I am nervous about flashing anything else, being that I dont have a backup! Long story short, all I want to do is finish a complete GPE conversion, and I need s-off to change my CID. At this point, all I need to do is achieve s-off, flash the GPE CID, and then flash a stock recovery and I'm done! So any thoughts on how to help me achieve s-off without potentionally bricking this thing?
edit: my build number is JWR66Y.H1 , does this mean I am on 3.07.1700.1
Click to expand...
Click to collapse
boot to bootloader -> FASTBOOT, connect your phone to PC and it will change to FASTBOOT USB (picture attached)
then type "fastboot getvar all" and post it (remove IMEI and s/n before posting), also post the date it shows on that white screen.
nkk71 said:
boot to bootloader -> FASTBOOT, connect your phone to PC and it will change to FASTBOOT USB (picture attached)
then type "fastboot getvar all" and post it (remove IMEI and s/n before posting), also post the date it shows on that white screen.
Click to expand...
Click to collapse
I don't have a camera to take a pic right now, but I can tell you the date is July 5th
ssreynolds said:
I don't have a camera to take a pic right now, but I can tell you the date is July 5th
Click to expand...
Click to collapse
no need for camera, but you still need to post a "fastboot getvar all" (remove IMEI and s/n)
nkk71 said:
no need for camera, but you still need to post a "fastboot getvar all" (remove IMEI and s/n)
Click to expand...
Click to collapse
will do, as soon as I get home!
however if I flash a stock rom like the one I have attached, couldnt I just use revone method (./revone -P)?
http://forum.xda-developers.com/showthread.php?t=2370507 > this rom would put me on firmware version 2.24.401.1
ssreynolds said:
will do, as soon as I get home!
however if I flash a stock rom like the one I have attached, couldnt I just use revone method (./revone -P)?
http://forum.xda-developers.com/showthread.php?t=2370507 > this rom would put me on firmware version 2.24.401.1
Click to expand...
Click to collapse
Why don't you use a RUU and flash the stock recovery, so you can recieve OTA updates and then you can just choose the correct rumrunner s off file and let it do the work. Then you don't really have to worry about the version number and btw. you can simply look it up in the settings. Can you pls ask if I didn't explane it well? Because this is very probable^^

[SOLVED] CID change and repairs

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.

[SOLVED][Q] Hboot 1.54, S-ON - Debrand, receive ota, without htc-dev unlock

Hello,
probably silly question and you will order me to study xda.
Unfortunately, i have came through almost every single topic, and can't get to "move" from my situation.
I received Htc One with Hboot v 1.54.000, locked bootloader - S-ON.
Software number 2.24.111.5 (android 4.2.2 with Sense 5). My cid (read through CidGetter from playstore) - T-MOB101.
I am trying to avoid unlocking bootloader via htc-dev, as afaik it voids the warranty.
I am not interested in custom roms. Rather, i would like to "fool" the phone and make it like it was European distribution, with no branding, so i would receive OTA as anyone else with unbranded phone.
If i understood correctly, to achieve this, basically i need to change my CID to european or supercid, which will enable to install any ruu from htc. But european otas would be enough for me. To change cid, i need S-OFF, right ?
There are basically three methods, if i read correctly, right ?
1, Revone - doesn't work with Hboot 1.54
2, Moonshine - Works without htc-dev unlocking, but installs custom bootloader, which will disable otas to install.
3, Rumrunner - Works with 1.54 bootloader, but i need to htc dev unlock ?
So, am i understanding correctly, that as long as i dont want to htc dev unlock, i am stuck to my cid, and dependent from german t-mobile ? So i can only hope, some dev will find exploit in Hboot 1.54 ?
Isn't there any miracle, that could help to solve my problem ?
Thanks
Rumrunners is the only solution with an htc dev unlock...
If you will remove the cid and put an european is the best thing to do.
You can always put the locked string
Yes,
but Htc will know, that i requested unlock keys.
Won't be that problem ?
Also, does htc-dev unlock automatically mean warranty void ?
remusator said:
Yes,
but Htc will know, that i requested unlock keys.
Won't be that problem ?
Also, does htc-dev unlock automatically mean warranty void ?
Click to expand...
Click to collapse
Yeah, i know that htc will know, but i never had a problem.
When i had the Evo 3D i unlocked with htcdev and after s-offed, so i relocked and s-on for warranty e no prob
MY friends with this phone didn't had any problem with warranty also with an unlocked with htcdev...
Remusator - I'm looking for the same thing: I have UK orange firmware, and was hoping to get stock/unbranded CID so I can get regular OTAs. Please let me know if you figure it out
Desperately waiting and hoping for some dev to soff without dev.
Today an arcticle came through my hands, saying "Unlocked htc one - kitkat till end of the month". Still don't have even Jelly :/
Is someone working on this ? Please
Guich said:
Yeah, i know that htc will know, but i never had a problem.
When i had the Evo 3D i unlocked with htcdev and after s-offed, so i relocked and s-on for warranty e no prob
MY friends with this phone didn't had any problem with warranty also with an unlocked with htcdev...
Click to expand...
Click to collapse
Hello, thanks for answer. :good:
If i agree to unlock my bootloader, could i achieve things mentioned in first post ?
Could you please give me some more detailed guide (alternatively steps with topic links), which i need to proceed ?
Al i need is to fool the phone to think, that it's unlocked and receive ota's like any other european unlocked htc one.
Thanks
remusator said:
Hello, thanks for answer. :good:
If i agree to unlock my bootloader, could i achieve things mentioned in first post ?
Could you please give me some more detailed guide (alternatively steps with topic links), which i need to proceed ?
Al i need is to fool the phone to think, that it's unlocked and receive ota's like any other european unlocked htc one.
Thanks
Click to expand...
Click to collapse
OK, European unbranded:
1- get s-off: http://rumrunner.us/ (follow instructions !)
2- change CID to European unbranded such as HTC__001
fastboot oem writecid HTC__001 <- two underscores
3- I assume your model number (MID) is already PN0710000
4- remove TAMPERED, and set your phone back to LOCKED, you can use this tool from within CWM recovery: http://forum.xda-developers.com/showthread.php?t=2527194
5- Run the following RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
after the above, your phone will not be fooled into thinking it's European unbranded, it will be European unbranded, and you'll receive the OTAs.
Let me know if you need more explanations, and hit the thanks button if I've helped
Hello, thanks.
However, i am completely stock. So i don't have CWM recovery yet.
In which step will i get it ? Or am i missing something ?
Also, CID change - is it really so easy ? I have seen some guides where people needed to download, edit and then flash some hex files.
remusator said:
Hello, thanks.
However, i am completely stock. So i don't have CWM recovery yet.
In which step will i get it ? Or am i missing something ?
Also, CID change - is it really so easy ? I have seen some guides where people needed to download, edit and then flash some hex files.
Click to expand...
Click to collapse
OK, so before point 1 above:
a) use HTCdev to unlock
b) download CWM http://forum.xda-developers.com/showthread.php?t=2173863 and flash it in bootloader/FASTBOOT USB:
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
--> enter recovery
c) for rumrunner to work, you need a close to stock rom with root access, so get one from here: http://www.htc1guru.com/downloads/stock-rom-downloads/, probably this one should work: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
you need to push that to your phone:
adb push <name of rom>.zip /data/media/ <- this will take 5 to 10 minutes without any progress bar, then report success
d) in CWM recovery, now select "install zip" -> "choose zip" and flash the rom
If you're using the Guru Reset ROM, then select WIPE, select ROOT, unselect "stock recovery"
and then proceed to rumrunner
"Also, CID change - is it really so easy ?" <- yes with S-off, it is easy, and you wont have any hex-editing to do, now or in future OTAs
Hit the thanks button if i've helped
Thanks, and what will be my phone status after this procedure ?
What hboot version, son/soff, unlocked/locked.
And what recovery ? Original, or cwm ?
remusator said:
Thanks, and what will be my phone status after this procedure ?
What hboot version, son/soff, unlocked/locked.
And what recovery ? Original, or cwm ?
Click to expand...
Click to collapse
the phone will be unTAMPERED, LOCKED (not relocked), 100% out-of-the box European unbranded, HTC Sense 5 ROM v1.28.401.7, but you'll receive OTAs up to 4.3 I think.
recovery will be stock recovery not CWM, so you can receive OTA
The phone will remain S-Off, and I suggest keeping it, if YOU INSIST on going S-On you can do so after running the RUU, but before taking any OTAs, by using "fastboot oem writesecureflag 3"
nkk71 said:
the phone will be unTAMPERED, LOCKED (not relocked), 100% out-of-the box European unbranded, HTC Sense 5 ROM v1.28.401.7, but you'll receive OTAs up to 4.3 I think.
recovery will be stock recovery not CWM, so you can receive OTA
The phone will remain S-Off, and I suggest keeping it, if YOU INSIST on going S-On you can do so after running the RUU, but before taking any OTAs, by using "fastboot oem writesecureflag 3"
Click to expand...
Click to collapse
Ok, just to make sure.
When will be CWM recovery replaced with original one ? After running RUU ?
I definitely don't insist on S-ON. My warranty will be void anyways because of htc-dev unlock. And in case my phone would break down, i need S-OFF to restore everything to original.
Are there any security risks when i'm S-OFF ? Such as malware android applications etc ? As i have understood, no.
Can / should i take some full backup of my original rom, device, bootloader, recovery in case that something goes totally wrong ?
Many many thanks
What you gave me here is most complete tutorial imho
remusator said:
Ok, just to make sure.
When will be CWM recovery replaced with original one ? After running RUU ?
Click to expand...
Click to collapse
Exactly after running the RUU.exe it will restore EVERYTHING back to stock: hboot, recovery, firmware, kernel, ROM, radio
remusator said:
I definitely don't insist on S-ON. My warranty will be void anyways because of htc-dev unlock. And in case my phone would break down, i need S-OFF to restore everything to original.
Click to expand...
Click to collapse
I don't know much about warranty and what IS and IS NOT allowed, every users experience seems different, just read one today: he sent it s-off, rooted, custom rom, etc. but the blown speakers were fixed, and no questions asked.
remusator said:
Are there any security risks when i'm S-OFF ? Such as malware android applications etc ? As i have understood, no.
Click to expand...
Click to collapse
No security issues whatsoever, S-Off will only allow you to write to certain partitions you can't with S-On. The ROM (Android 4.x.x) is responsible for the malware etc.
remusator said:
Can / should i take some full backup of my original rom, device, bootloader, recovery in case that something goes totally wrong ?
Click to expand...
Click to collapse
Sure, backups are always good.
And I just checked, there's also a Guru Reset here: http://www.htc1guru.com/downloads/stock-rom-downloads/ (not your version but close enough)
And there are a couple of nandroids around as well.
remusator said:
Many many thanks
What you gave me here is most complete tutorial imho
Click to expand...
Click to collapse
You're welcome, you can always press that little THANKS button to say I was helpful
I will definitely give you thx-es
One last question.
Do i need the root ? Do i need root for rumrunner to work ?
Can't I just insted running programs from htcguru use these commands ?
http://forum.xda-developers.com/showthread.php?t=2477792 ?
Will it be the same ?
Aand how can i make full backup of whole phone ? Without installing CWM recovery and then nandroid.
remusator said:
I will definitely give you thx-es
One last question.
Do i need the root ? Do i need root for rumrunner to work ?
Can't I just insted running programs from htcguru use these commands ?
http://forum.xda-developers.com/showthread.php?t=2477792 ?
Will it be the same ?
Aand how can i make full backup of whole phone ? Without installing CWM recovery and then nandroid.
Click to expand...
Click to collapse
Yeah, su is required for rumrunner.
Yes, htcguru file use that command.
After the flash of recovery, a nandroid will backup only the OS.
For the sd you've to copy it into your pc.
remusator said:
I will definitely give you thx-es
One last question.
Do i need the root ? Do i need root for rumrunner to work ?
Can't I just insted running programs from htcguru use these commands ?
http://forum.xda-developers.com/showthread.php?t=2477792 ?
Will it be the same ?
Aand how can i make full backup of whole phone ? Without installing CWM recovery and then nandroid.
Click to expand...
Click to collapse
Guich said:
Yeah, su is required for rumrunner.
Yes, htcguru file use that command.
After the flash of recovery, a nandroid will backup only the OS.
For the sd you've to copy it into your pc.
Click to expand...
Click to collapse
Guich beat me to it
1- Yes you need root
2- the link you provided only works if you are S-Off already
3- backup everything to PC (pics, music, etc)
4- use Call Logs Backup & Restore and SMS Backup & Restore if you need them (free apps in Play Store)
5- use Helium for apps+data, since you can't use Titanium
6- backup ROM using nandroid
7- dont worry too much about the nandroid, there are ones on @crushalots site
nkk71 said:
--> enter recovery
c) for rumrunner to work, you need a close to stock rom with root access, so get one from here: http://www.htc1guru.com/downloads/stock-rom-downloads/, probably this one should work: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
you need to push that to your phone:
adb push <name of rom>.zip /data/media/ <- this will take 5 to 10 minutes without any progress bar, then report success
Click to expand...
Click to collapse
Hello, i cannot get through this point. I have installed HTC Sync, then uninstalled, so only drivers remained on my system.
I can use adb when the phone is normally booted, but then i don't have permission to write to that location.
When i reboot to recovery, adb devices shows empty list. Also that funny thing in windows taskbar starts spinning, finds "One", but fail to install driver.
Update1:
Ok, i managed to update adb driver to Android one. (http://forum.xda-developers.com/showthread.php?t=1830108 device manager section)
Now i'm at next step. I pushed zip to /data/media/, but after choosing install zip, there is none on sdcard.
Trying to push that again.
Update2:
File appeared after second push. Installing right now. Hope phone will wake after this procedure. Fingers crossed, holding breath.
Update3
Ok, i flashed RUU, everything is fine until now.
Slovak language / Slovakia as location is missing. Should / can i change my CID for something and install corresponding RUU for that CID, so i would have Slovak Language ? I also get red text saying "THIS IS TEST DEVICE...."
I think, the correct CID for my region is HTC__032 - East Europe
What is the language dependent on ? Because the same RUU you recommended for me is also for HTC__032. Is the file same and languages are allowed based on CID, or how does this work ?
Also HTC_001 is in the first wave of updates ?
Thanks
delete pls
remusator said:
Hello, i cannot get through this point. I have installed HTC Sync, then uninstalled, so only drivers remained on my system.
I can use adb when the phone is normally booted, but then i don't have permission to write to that location.
When i reboot to recovery, adb devices shows empty list. Also that funny thing in windows taskbar starts spinning, finds "One", but fail to install driver.
Update1:
Ok, i managed to update adb driver to Android one. (http://forum.xda-developers.com/showthread.php?t=1830108 device manager section)
Now i'm at next step. I pushed zip to /data/media/, but after choosing install zip, there is none on sdcard.
Trying to push that again.
Update2:
File appeared after second push. Installing right now. Hope phone will wake after this procedure. Fingers crossed, holding breath.
Update3
Ok, i flashed RUU, everything is fine until now.
Slovak language / Slovakia as location is missing. Should / can i change my CID for something and install corresponding RUU for that CID, so i would have Slovak Language ? I also get red text saying "THIS IS TEST DEVICE...."
I think, the correct CID for my region is HTC_032 - East Europe
Click to expand...
Click to collapse
Been gone for a while, so what's your status now? How far did you get.

Categories

Resources