Related
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
winwiz said:
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
Click to expand...
Click to collapse
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
htc one m7 said:
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
Click to expand...
Click to collapse
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
winwiz said:
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
Click to expand...
Click to collapse
me i have my stuck rom running also nandroid pulled by cmd
but no chance for me
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
thanks next time when i need a root i will get s-off before that .now my chance is getting s-off wich is not available now
if u dint tell me dont search i would search for ever XD
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
i just want to get updates from htc
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
htc one m7 said:
i just want to get updates from htc
Click to expand...
Click to collapse
Then you should've left the phone stock
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. If you used the revone method to root, it should take care of it. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Click to expand...
Click to collapse
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
winwiz said:
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
Click to expand...
Click to collapse
You could run the all in one toolkit and remove the tampered and relocked flags.
---------- Post added at 02:06 AM ---------- Previous post was at 01:17 AM ----------
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
This thread is open for questions like these. Flame on elsewhere.
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
Click to expand...
Click to collapse
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
htc one m7 said:
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
Click to expand...
Click to collapse
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
kibmikey1 said:
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
Click to expand...
Click to collapse
Who's flaming and complaining, and I did help ... I wouldn't help you now but that's another story. As for noobs, If you can't be bothered to read and search then that says something about you. For starters, even though you were wrong (and not the OP) I did help, I have also spent more time helping on here than I have posting anything else, so if you don't like it, you know what you can do.
You might want to give correct advice aswell, if he's on Hboot 1.54 then he'd need S-Off to flash an older Hboot, which he cannot do. Thanks
iElvis said:
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
Click to expand...
Click to collapse
when i red your reply it seemed too easy but no
stuck recovery when you mean that ''fastboot flash recovery recovery.img'' pulled from nandroid back up ? yes ur right i manged to do that it was succesful but no change even a systim rom is not available getting signature failure 'seems promising yah
i know my thing is hard but it shouldnt be like that right im runing a rom now 4.3 im fine with it but i really want to F*** htcdev members :v
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
iElvis said:
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
Click to expand...
Click to collapse
if you want to help me help me now
i have my reovery.img and it flashes perfectly
how to get stuck rom ?
you mean the file with date it is bout 1.8GB named 2013-08-27.19.58.35 that i should put it in supfic folder do i can flash it with recovery cwm ?
since i have my back up and since it is S-on i wont mind flashing any thing
Hi
My HTC One keeps rebooting into the bootloader every time i turn it on, but if i say reboot, it boots up normally.
I decided to unlock my bootloader and the root the device, but i regret after unlocking the bootloader, so i decided to lock it. But now it just says "relocked" and "security warning". The reason it annoys me, is that i can't install the latest OTA update, because it just reboots into bootloader, and when i say "reboot" it boots up normally and the update is NOT installed.
What do you think i should do?
BTW, sorry if my english isn't perfect...
FML1234 said:
Hi
My HTC One keeps rebooting into the bootloader every time i turn it on, but if i say reboot, it boots up normally.
I decided to unlock my bootloader and the root the device, but i regret after unlocking the bootloader, so i decided to lock it. But now it just says "relocked" and "security warning". The reason it annoys me, is that i can't install the latest OTA update, because it just reboots into bootloader, and when i say "reboot" it boots up normally and the update is NOT installed.
What do you think i should do?
BTW, sorry if my english isn't perfect...
Click to expand...
Click to collapse
Are you still using a custom recovery? You have to flash stock recovery for OTAs.
Cant help you in detail but...
-you can change "Unlocked" to "Locked" with revone S Off
-it seems like you dont have any rom installed... you should flash a stock nandroid backup.. you can found it in the general forum.
nkk71 said:
Are you still using a custom recovery? You have to flash stock recovery for OTAs.
Click to expand...
Click to collapse
Yes, and it is S-OFF, so nothing wrong there either. Should i run an ruu? And if so should where can i find the right one? BTW, it doesn't say "security warning".
FML1234 said:
Yes, and it is S-OFF, so nothing wrong there either. Should i run an ruu? And if so should where can i find the right one? BTW, it doesn't say "security warning".
Click to expand...
Click to collapse
Well custom recovery won't let you get OTA. But your are S-Off :good: excellent.
So first thing I would do, is use revone to get rid of "TAMPERED" and change "RELOCKED" to "LOCKED".
Keep S-Off !!
And finally run your RUU, that would reflash hboot, stock recovery, stock radio, stock ROM... all back to stock, and you should receive the OTAs.
(Remember keep S-Off, cause once you receive the OTA it has an updated hboot which will not allow you to S-Off again)
kehi said:
Cant help you in detail but...
-you can change "Unlocked" to "Locked" with revone S Off
-it seems like you dont have any rom installed... you should flash a stock nandroid backup.. you can found it in the general forum.
Click to expand...
Click to collapse
It is "relocked", and i have the stock rom, the problem is that whenever i run out of juice, and boot it back up, it boots into the bootloader.
nkk71 said:
Well custom recovery won't let you get OTA. But your are S-Off :good: excellent.
So first thing I would do, is use revone to get rid of "TAMPERED" and change "RELOCKED" to "LOCKED".
Keep S-Off !!
And finally run your RUU, that would reflash hboot, stock recovery, stock radio, stock ROM... all back to stock, and you should receive the OTAs.
(Remember keep S-Off, cause once you receive the OTA it has an updated hboot which will not allow you to S-Off again)
Click to expand...
Click to collapse
But my HBOOT is 1.54 and revone doesn't support that
FML1234 said:
But my HBOOT is 1.54 and revone doesn't support that
Click to expand...
Click to collapse
Are you still S-Off? If yes, then you can downgrade your hboot to 1.44 no problem. You can either use a RUU or look if you can find an hboot image to flash using fastboot.
nkk71 said:
Are you still S-Off? If yes, then you can downgrade your hboot to 1.44 no problem. You can either use a RUU or look if you can find an hboot image to flash using fastboot.
Click to expand...
Click to collapse
No, i am not, i thought i was sorry, but thanks a lot for the help. Where can i find the right RUU? I already have one, but it is not the right one.
FML1234 said:
No, i am not, i thought i was sorry, but thanks a lot for the help. Where can i find the right RUU? I already have one, but it is not the right one.
Click to expand...
Click to collapse
There are plenty of RUUs here: http://www.androidruu.com/?developer=M7
if you can't find one for your CID, just change it to SuperCID for the duration of the process; remember you'll only need to downgrade to be able to run revone successfully, after that you can reflash whatever ROM, firmware, etc you choose.
EDIT: nevermind the above, i misread and thought you still had s-off. my bad.
EDIT 2: did you at least flash back stock recovery? if you're still on custom recovery that will cause problems.
nkk71 said:
There are plenty of RUUs here: http://www.androidruu.com/?developer=M7
if you can't find one for your CID, just change it to SuperCID for the duration of the process; remember you'll only need to downgrade to be able to run revone successfully, after that you can reflash whatever ROM, firmware, etc you choose.
EDIT: nevermind the above, i misread and thought you still had s-off. my bad.
EDIT 2: did you at least flash back stock recovery? if you're still on custom recovery that will cause problems.
Click to expand...
Click to collapse
Yes, i have stock recovery.
FML1234 said:
Yes, i have stock recovery.
Click to expand...
Click to collapse
Ok, so I misunderstood a bit.
Back to the original problem:
The reason it annoys me, is that i can't install the latest OTA update, because it just reboots into bootloader, and when i say "reboot" it boots up normally and the update is NOT installed.
Click to expand...
Click to collapse
If I understand correctly after downloading the OTA, you try to install it. The OTA will reboot into bootloader during that process. Correct?
Can't really think of a reason it's doing that, but if it is try going to "recovery" from the bootloader menu not "reboot", and see if it starts installing.
nkk71 said:
Ok, so I misunderstood a bit.
Back to the original problem:
If I understand correctly after downloading the OTA, you try to install it. The OTA will reboot into bootloader during that process. Correct?
Can't really think of a reason it's doing that, but if it is try going to "recovery" from the bootloader menu not "reboot", and see if it starts installing.
Click to expand...
Click to collapse
I'll try that and tell you if it works.
nkk71 said:
Ok, so I misunderstood a bit.
Back to the original problem:
If I understand correctly after downloading the OTA, you try to install it. The OTA will reboot into bootloader during that process. Correct?
Can't really think of a reason it's doing that, but if it is try going to "recovery" from the bootloader menu not "reboot", and see if it starts installing.
Click to expand...
Click to collapse
It didn't work Guess im gonna wait until S-OFF is available on HBOOT 1.54 and then do it.
FML1234 said:
It didn't work Guess im gonna wait until S-OFF is available on HBOOT 1.54 and then do it.
Click to expand...
Click to collapse
Sorry to hear that. Maybe you can post a video, so that we can follow your steps.
Anyway, wish you good luck
Sent from my HTC One using xda app-developers app
nkk71 said:
Sorry to hear that. Maybe you can post a video, so that we can follow your steps.
Anyway, wish you good luck
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I might consider doing that. I'm pretty newish to rooting and stuff like that, but i'll try
So I've run into a problem with my new Htc First phone, the wifi doesnt locate any access points.
Its unlocked,rooted and S-off-ed.
I can unroot and lock the bootloader but does anyone know how to S-on it?
Yea, you just have to ruu first and then follow this guide.
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Kendosis said:
Yea, you just have to ruu first and then follow this guide.
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Click to expand...
Click to collapse
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
dramon said:
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
Click to expand...
Click to collapse
You usually have to run a factory reset, cache/dalvik cache wipe before you flash roms. I get that wifi problem sometimes when trying to flash a rom before wiping.
dramon said:
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
Click to expand...
Click to collapse
DUDE QUICK THING ! you can't flash any roms in till you RELOCK THE BOOTLOADER ! I know it sounds weird but trust me you will keep the S-off status (assuming you have s-off) and everything works fine, I couldn't flash any roms in till I relocked and I heard others have this problem too.
Now the WiFi problem, if factory resetting doesn't work, try flashing the stock rooted ROM around these threads, if that doesn't work try JMZ's kernel, and if that doesn't work then you have a hardware problem, good luck.
Sent from my HTC first
If he just RUU's it he won't have to worry about relocking his boot loader, he should just use titainium backup and ruu to save time.
Kendosis said:
If he just RUU's it he won't have to worry about relocking his boot loader, he should just use titainium backup and ruu to save time.
Click to expand...
Click to collapse
Trust me I've tried RUU and even that didn't work for me, in till I relocked , it was weird but its worth a shot since relocking keeps the s-off anyways
Sent from my HTC first
SneakyGuyDavid said:
Trust me I've tried RUU and even that didn't work for me, in till I relocked , it was weird but its worth a shot since relocking keeps the s-off anyways
Sent from my HTC first
Click to expand...
Click to collapse
I've tried it many times already it works, after you ruu it you just have to turn s-on before you try to unlock the boot loader again otherwise you'll get bootloop.
Kendosis said:
I've tried it many times already it works, after you ruu it you just have to turn s-on before you try to unlock the boot loader again otherwise you'll get bootloop.
Click to expand...
Click to collapse
guys guys, you've lost me.
All I need to do is wipe away all traces of my rooting and bootloader unlocking etc as I'm returning it for warranty.
Now my First is rooted, custom recovery and s-off and unlocked .
I want it unrooted, s-on and boot loader locked.
Someone please guide me through the steps :/
btw im not a n00b, but this is my first HTC phone so I'm not too familiar with these ruu's and s-offs
dramon said:
guys guys, you've lost me.
All I need to do is wipe away all traces of my rooting and bootloader unlocking etc as I'm returning it for warranty.
Now my First is rooted, custom recovery and s-off and unlocked .
I want it unrooted, s-on and boot loader locked.
Someone please guide me through the steps :/
btw im not a n00b, but this is my first HTC phone so I'm not too familiar with these ruu's and s-offs
Click to expand...
Click to collapse
Step 1. RUU your device
Step 2. After it reboots when it's done ruu'ing just start it and go through the set up.
Step 3. Turn on USB debugging mode.
Step 4. Turn on CMD on your PC then just follow the commands below
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writecid xxxxxxxx (where xxxxxxxx is your stock CID.) Mines is CWS__001 on the HTC first I'm not sure if it's the same on all devices just check to see if yours it the same, if it is just use fastboot oem writecid CWS__001
fastboot reboot-bootloader
fastboot getvar cid (It should say CWS__001 if that is your cid.)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
And that's it, it is a extremely simple process lol, I've done it at least 20 times since I tend to ruu my device a lot off of S-OFF, when messing around with different roms.
http://forum.xda-developers.com/showthread.php?t=841890
So its okay if I flash the ruu by the second method as in this thread?
And will custom recovery be overwritten with stock recovery?
OK Update!
I was well on my way to relock,s-on my phone etc and here's what happened
@Kendosis
@SneakyGuyDavid
1) Sucessfully RUU'd
As it happened I didnt have my sim inserted and when I rebooted, the wifi was working! When I inserted the sim the wifi stopped working. I did some bit of research and it turns out it has something to do with wifi country codes. Apparently it can be fixed by this app
https://play.google.com/store/apps/details?id=com.fardjad.android.wifixmanager
2) Since the app required root, I was going to get root again.
(Flashing RUU gave me bootloader locked)
I unlocked and then flashed CWM
3) Since I had no roms on my phone storage and the CWM doesnt mount storage, I had to sideload the ROMS.
4) No matter which roms I flashed, I was stuck in a bootloop. I relocked and tried flashing again but I was again stuck in a bootloop. CWM works fine though.
Current status: Bootloader Locked, S-off.
What do I do to fix this bootloop :/
@dramon
I told you to s-on after you ruu first otherwise you get boot loop lol.
Now RUU again and right after don't install nothing just start up the phone and turn usb debugging on and follow the steps to S-ON.
Kendosis said:
@dramon
I told you to s-on after you ruu first otherwise you get boot loop lol.
Now RUU again and right after don't install nothing just start up the phone and turn usb debugging on and follow the steps to S-ON.
Click to expand...
Click to collapse
also sideload sucks ass, if you flash TWRP then you can run adb from it and use adb push, so in cmd you would run " adb push
ROMZIPNAME.ZIP /sdcard "
Thanks guys, I now have an idea of how the rooting and unlocking works for HTC (Y)
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
ajr901 said:
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
Click to expand...
Click to collapse
Post a fastboot getvar all except for the imei and serialno! I hope you restored the MID!
majmoz said:
Post a fastboot getvar all except for the imei and serialno! I hope you restored the MID!
Click to expand...
Click to collapse
LOL @ randomly clicking and ending up with S-On and locked bootloader. That's a great way to mess up your phone .
Deepening on your fastboot output, you are probably SOL.
oh no,
locked bootloader + GPE =
http://forum.xda-developers.com/showthread.php?t=2547894
alray said:
oh no,
locked bootloader + GPE =
http://forum.xda-developers.com/showthread.php?t=2547894
Click to expand...
Click to collapse
Yup. Shows how easy it is to mess up . maybe hope depending on fastboot output
SaHiLzZ said:
maybe hope depending on fastboot output
Click to expand...
Click to collapse
yep we will see.
I also heard of someone lucky here who had a rep from HTC helping him. That guy from HTC compiled a custom firmware package signed with HTC private key (which will allow it to be flashed with s-on and locked bootloader). Once the firmware is flashed, it will unlock the bootloader. That was the only time I heard about this kind of thing and i'm not sure its approved by HTC and will probably not happen soon again.
Similar situation, but haven't gone backwards yet
I just bought a AT&T-locked HTC One M7 and mistakenly thought that rooting and s-off would unlock the SIM. I've also requested an unlock code from AT&T, but if what he's saying is true, I'm going to have to revert to a stock AT&T phone as well.
So my question is, How do I go backward without screwing up the same way? I have made some recovery backups of the original ROM but the bootloader was unlocked already. Took me a long time to figure out how to go forward in the process and I wasn't really concerned about having to re-lock anything because it's beyond the warranty period.
I'm running the following:
Bootloader unlocked
CWM Touch Recovery backups along the way
Firewater for S-Off
Venom ViperOne ROM installed
Bulletproof kernel
Firmware upgraded to 6.09.401.5
I'd really like to un-do as little of this as possible. I'm wondering what part of the modification is detected by the SIM unlock code process.
I'm kind of a noob, but this is my second Android phone that I've rooted and modded in the past couple of weeks, so I'm getting better. I'm very frustrated that unlocking the SIM is such a big deal. Any help you can offer is appreciated.
lamonster26 said:
I just bought a AT&T-locked HTC One M7 and mistakenly thought that rooting and s-off would unlock the SIM. I've also requested an unlock code from AT&T, but if what he's saying is true, I'm going to have to revert to a stock AT&T phone as well.
So my question is, How do I go backward without screwing up the same way? I have made some recovery backups of the original ROM but the bootloader was unlocked already. Took me a long time to figure out how to go forward in the process and I wasn't really concerned about having to re-lock anything because it's beyond the warranty period.
I'm running the following:
Bootloader unlocked
CWM Touch Recovery backups along the way
Firewater for S-Off
Venom ViperOne ROM installed
Bulletproof kernel
Firmware upgraded to 6.09.401.5
I'd really like to un-do as little of this as possible. I'm wondering what part of the modification is detected by the SIM unlock code process.
I'm kind of a noob, but this is my second Android phone that I've rooted and modded in the past couple of weeks, so I'm getting better. I'm very frustrated that unlocking the SIM is such a big deal. Any help you can offer is appreciated.
Click to expand...
Click to collapse
your situation isnt really comparable to OP's situation.
You just have to use the sim unlock code on a stock rom or "close-to-stock" rom like arhd (might also work on venom idk)
If you have to return stock to use the sim unlock code, you can use the stock odexed rom of 6.09.401.5 on available arhd blog download section. just make a nandroid backup of your current setup, flash the stock odexed rom, sim unlock using the code and then revert back to your venom rom using your nandroid backup.
or with s-off, simply ruu your phone, use the unlock code then flash the rom you want to use.
Got it working
alray said:
your situation isnt really comparable to OP's situation.
You just have to use the sim unlock code on a stock rom or "close-to-stock" rom like arhd (might also work on venom idk)
If you have to return stock to use the sim unlock code, you can use the stock odexed rom of 6.09.401.5 on available arhd blog download section. just make a nandroid backup of your current setup, flash the stock odexed rom, sim unlock using the code and then revert back to your venom rom using your nandroid backup.
or with s-off, simply ruu your phone, use the unlock code then flash the rom you want to use.
Click to expand...
Click to collapse
Thanks again. Just bought an unlock code for $5 off one of those sites and it worked without doing any changes to the ROMs and other mods. Thanks for the tip about going back to stock easily though. Might want to set that up just as a backup.
HTC ONE (M7) Sprint
hboot 1.57
s-on
unlocked
recently used guru reset to go back to stock rom, worked fine until I tried to update the phone and get stuck on boot screen. loaded up twrp again and sideloaded another guru reset... did the same thing, worked until i did an update and gets stuck at boot screen when update is complete.
What kind of update are you talking about?
Sent from my HTC One using Tapatalk
ota android update
OTAs don't work with TWRP.. But I'm really not sure what is going on with your phone. Maybe just flash a ROM that's already up to date?
Sent from my HTC One using Tapatalk
guru reset installs stock rom and recovery. used the latest one available. right now i'm just going to try to get s-off and run a ruu.
Just tried again one more time to see... it seems to take the first update just fine, and only bricks on update 4.06.651.9
Mud3 said:
Just tried again one more time to see... it seems to take the first update just fine, and only bricks on update 4.06.651.9
Click to expand...
Click to collapse
What is your fastboot getvar all (minus serial no and imei)
What guru reset have you been using?
Did you ever fix this, I am having the same problem.
bigpedro36 said:
Did you ever fix this, I am having the same problem.
Click to expand...
Click to collapse
The reason it fails is because the guru reset is too old, it doesn't contain major system files, only radio and recovery plus the Rom zip file, therefore your hboot remains on the latest, probably 1.57, now when the ota comes and tries to update your hboot to 1.56 from the old Rom files that the reset put on there, it fails because you can't back flash an s-on device, s-off is the only answer unless you can find a newer reset Rom.
My HBoot is actually 1.6.. and im having trouble finding anything that will make 1.6 into s-off .
bigpedro36 said:
My HBoot is actually 1.6.. and im having trouble finding anything that will make 1.6 into s-off .
Click to expand...
Click to collapse
Have you tried sunshine s-off ? Not sure if it supports 1.6 yet though but it's worth a try, you only pay if it can s-off your phone after its run some tests. But that's my point, your on the latest hboot and the ota files are assuming you on something like 1.54 (estimate) and trying to update it, fails because you already have a newer hboot.
Seanie280672 said:
Have you tried sunshine s-off ? Not sure if it supports 1.6 yet though but it's worth a try, you only pay if it can s-off your phone after its run some tests. But that's my point, your on the latest hboot and the ota files are assuming you on something like 1.54 (estimate) and trying to update it, fails because you already have a newer hboot.
Click to expand...
Click to collapse
Cool I got S-off now. I'm trying to OTA again and will go from there.
bigpedro36 said:
Cool I got S-off now. I'm trying to OTA again and will go from there.
Click to expand...
Click to collapse
Not sure if the ota will work, you may have to just grab a full Sprint ruu and just run that which will back flash everything.
Seanie280672 said:
Not sure if the ota will work, you may have to just grab a full Sprint ruu and just run that which will back flash everything.
Click to expand...
Click to collapse
The OTA worked.. Thanks a ton.. you explained exactly what the problem was.