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
Related
hello! I have to send my HTC One in for warrenty:
I am now s-off, bootloader locked, super-CID, custom Rom, HBoot 1.44.0000, custom recovery.
What do i have to do bevore sending it in? My One is from T-Mobile germany. Firmware version 1.29.111.11
If i runn an RUU does it flash stock recovery? or do have have to do this manually?
Instead of running a RUU (i cant find an t-mobile germany ruu) is it possible to flash a stock nanadroid backup (http://bugsylawson.com/files/file/444-m7-cwm-nandroid-backup-cid-t-mob101-1281116/ ?)?
how do i get S-on again?
OK, now i am back to T-MOB101 cid! Am i now able to flash this nandroid backup (http://bugsylawson.com/files/file/444-m7-cwm-nandroid-backup-cid-t-mob101-1281116/ ) ? Or is there anything to do before?
does anyone know where to find stock T-Mobile germy revovery? or can i simply use the 401 one?
MICH_** said:
does anyone know where to find stock T-Mobile germy revovery? or can i simply use the 401 one?
Click to expand...
Click to collapse
there is no specific recovery for t-mobile. just use the stock recovery.
herwegan said:
there is no specific recovery for t-mobile. just use the stock recovery.
Click to expand...
Click to collapse
which one did i flash then? but it works! i now restored a nandroid and flashed stock recovery, locked bootloader
But there is one more prolem...Bootloader is now `RELOCKED` and i am still s-off. is there any way to `LOCK` bootloader?
MICH_** said:
which one did i flash then? but it works! i now restored a nandroid and flashed stock recovery, locked bootloader
But there is one more prolem...Bootloader is now `RELOCKED` and i am still s-off. is there any way to `LOCK` bootloader?
Click to expand...
Click to collapse
yes since you have s-off you can use revone again to "lock" your bootloader and remove "tampered" flag after this, don't forget to go back to s-on again. then you should be completely stock.
MICH_** said:
which one did i flash then? but it works! i now restored a nandroid and flashed stock recovery, locked bootloader
But there is one more prolem...Bootloader is now `RELOCKED` and i am still s-off. is there any way to `LOCK` bootloader?
Click to expand...
Click to collapse
Read the revone thread. (revone -l)
Sent from my HTC One using xda premium
herwegan said:
yes since you have s-off you can use revone again to "lock" your bootloader and remove "tampered" flag after this, don't forget to go back to s-on again. then you should be completely stock.
Click to expand...
Click to collapse
can i use revone with stock rom? Could you please tell me which steps to make? thanks!
MICH_** said:
can i use revone with stock rom? Could you please tell me which steps to make? thanks!
Click to expand...
Click to collapse
of course, you only need s-off. here:
http://forum.xda-developers.com/showthread.php?t=2314582
and to go back to s-on use hasoon2000's toolkit: http://forum.xda-developers.com/showthread.php?t=2183942
:good:
herwegan said:
of course, you only need s-off. here:
http://forum.xda-developers.com/showthread.php?t=2314582
and to go back to s-on use hasoon2000's toolkit: http://forum.xda-developers.com/showthread.php?t=2183942
:good:
Click to expand...
Click to collapse
can i `LOCK` the bootloader with this toolkit? but my current rom in not rooted
MICH_** said:
can i `LOCK` the bootloader with this toolkit? but my current rom in not rooted
Click to expand...
Click to collapse
no, use "revone" to "lock" (first link), after this use the toolkit to s-on (second link). root is not needed for these steps.
herwegan said:
no, use "revone" to "lock" (first link), after this use the toolkit to s-on (second link). root is not needed for these steps.
Click to expand...
Click to collapse
i have a massive problem now: my One recieved an official OTA from T-Mobile. i downloaded it and installed it. Now the OTA is installing but its stuck :crying: I think the recovery i flashed was not thr right.
what should i do?
MICH_** said:
i have a massive problem now: my One recieved an official OTA from T-Mobile. i downloaded it and installed it. Now the OTA is installing but its stuck :crying: I think the recovery i flashed was not thr right.
what should i do?
Click to expand...
Click to collapse
dude... great job...
hold power + volume down and see what happens.
herwegan said:
dude... great job...
hold power + volume down and see what happens.
Click to expand...
Click to collapse
i saw the splash screen a view times...but now it simple installs the update
Hope for the best
now its completly black
MICH_** said:
i saw the splash screen a view times...but now it simple installs the update
Hope for the best
now its completly black
Click to expand...
Click to collapse
can you access the recovery or bootloader?
herwegan said:
dude... great job...
hold power + volume down and see what happens.
Click to expand...
Click to collapse
wohooo working again!
But now i have to lock the bootloader and dont really know how :/ in this toolkit there is an option to lock it! can i use that?
in that toolkit it says (when i push on `return to s-on`) that i need s-on ?
MICH_** said:
wohooo working again!
But now i have to lock the bootloader and dont really know how :/ in this toolkit there is an option to lock it! can i use that?
in that toolkit it says (when i push on `return to s-on`) that i need s-on ?
Click to expand...
Click to collapse
i can't say for sure. i'd recommend you to use revone, it's safer in my opinion. you've used revone to get s-off, didn't you? so just do the same again and use the instructions in the revone thread (i already postet the link for you)
the s-on function should work fine, but WAIT, first "lock" the bootloader..
herwegan said:
i can't say for sure. i'd recommend you to use revone, it's safer in my opinion. you've used revone to get s-off, didn't you? so just do the same again and use the instructions in the revone thread (i already postet the link for you)
the s-on function should work fine, but WAIT, first "lock" the bootloader..
Click to expand...
Click to collapse
when i got s-off, i did everything on terminal on my phone (had problems with fastboot)
MICH_** said:
when i got s-off, i did everything on terminal on my phone (had problems with fastboot)
Click to expand...
Click to collapse
:/ never used this before, can't say how to lock with this method..
herwegan said:
:/ never used this before, can't say how to lock with this method..
Click to expand...
Click to collapse
going to try now...i will report (have to go to other pc)
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 guys,
After few months with my HTC One rooted and unlocked (running the Google developer edition 4.3), I wanted to unroot my phone (especially to use Barclay's app which doesn't work if the phone is rooted).
after a "fastboot oem lock", I have an "***Security warning ***" at boot. I know that I have to install everything using a RUU file, but when I try to, I've got another error message which say something like "can't install, hboot older".
Tried everything since few days and can't make it work. Any idea would be appreciated!
More details about my phone:
HTC One EE mobile UK (unbranded)
HBOOT-1.54.0000
Radio-4A.17.3250.14
OpenDSP-v31.120.274.0617
cid-HTC_001
Thanks!
Do you have the stock rom?
And however, for unroot you don't have to relock bootloader, but unroot lol
For the ruu, yes, you can downgrande only if you have the S-OFF
Guich said:
Do you have the stock rom?
And however, for unroot you don't have to relock bootloader, but unroot lol
For the ruu, yes, you can downgrande only if you have the S-OFF
Click to expand...
Click to collapse
Yep, I currently got the stock rom.
What I would like is actually get my phone exactly the same than before I made all these geeky things (unroot, unlock...).
Thanks for your answer!
Is there anyway for me to run an "unlock" using fastboot?
MickCoelho said:
Is there anyway for me to run an "unlock" using fastboot?
Click to expand...
Click to collapse
Re-unlock the bootloader with the code.bin of htc.
After flash the stock rom and the stock recovery and then relock the bootloader for returning stock and get the OTA
Guich said:
Re-unlock the bootloader with the code.bin of htc.
After flash the stock rom and the stock recovery and then relock the bootloader for returning stock and get the OTA
Click to expand...
Click to collapse
Thanks mate.
Hopefully I'll find the correct way to do that, I guess there's thousands of tutorials relative to that
MickCoelho said:
Thanks mate.
Hopefully I'll find the correct way to do that, I guess there's thousands of tutorials relative to that
Click to expand...
Click to collapse
I got the same situation..did you manage to fix it?
cz4r3n said:
I got the same situation..did you manage to fix it?
Click to expand...
Click to collapse
Yep, it worked fine, I unlocked it back using the code.bin provided by HTC dev website and followed instructions to do it.
So my problem is the further, I had a fully working HTC first with the latest Hboot update previously moonshined with the old one. So I had S-off, root, JMZ's custom kernel and an unlocked bootloader but then after a while I've done alot of flashes, zip installs tweaks and modifications that created pesky problems that wouldn't go away with a simple wipe in CWM. That's okay though I could just do a complete restore with the RUU. And i did, no I didn't re-lock the bootloader because I had S-off anyways. Everything came out great. But then I went ahead and the problems started to happen.. After unlocking the bootloader I had an eternal bootloop that wouldn't go away, but did a simple re-lock and booted up just fine.
My question is what the hell am I doing wrong? does it have to do with the version of RUU im using?
abrahammmmmmm_ said:
So my problem is the further, I had a fully working HTC first with the latest Hboot update previously moonshined with the old one. So I had S-off, root, JMZ's custom kernel and an unlocked bootloader but then after a while I've done alot of flashes, zip installs tweaks and modifications that created pesky problems that wouldn't go away with a simple wipe in CWM. That's okay though I could just do a complete restore with the RUU. And i did, no I didn't re-lock the bootloader because I had S-off anyways. Everything came out great. But then I went ahead and the problems started to happen.. After unlocking the bootloader I had an eternal bootloop that wouldn't go away, but did a simple re-lock and booted up just fine.
My question is what the hell am I doing wrong? does it have to do with the version of RUU im using?
Click to expand...
Click to collapse
You got to turn S-ON after you RUU a previously S-OFF'd device.
Kendosis said:
You got to turn S-ON after you RUU a previously S-OFF'd device.
Click to expand...
Click to collapse
Wow, well I was completely unaware of that. Sorry for the noob question but how would i go about in doing that?
abrahammmmmmm_ said:
Wow, well I was completely unaware of that. Sorry for the noob question but how would i go about in doing that?
Click to expand...
Click to collapse
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Kendosis said:
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Click to expand...
Click to collapse
Thanks! One question: what's the stock cid number for the RUU the first has? I now have S-on but when I tried to run the RUU again to see if everything was working I got error 131 which shows when there's a CID mismatch. The CID I used was cws__001. I have the first with a t-mobile simcard by the way if that changes anything
abrahammmmmmm_ said:
Thanks! One question: what's the stock cid number for the RUU the first has? I now have S-on but when I tried to run the RUU again to see if everything was working I got error 131 which shows when there's a CID mismatch. The CID I used was cws__001. I have the first with a t-mobile simcard by the way if that changes anything
Click to expand...
Click to collapse
Try a different version of the ruu, there's two iirc. Try version 1.08.502.1 if that doesn't work try the next version.
Kendosis said:
Try a different version of the ruu, there's two iirc. Try version 1.08.502.1 if that doesn't work try the next version.
Click to expand...
Click to collapse
I tried both and it's a no go. Pretty sure it has to do with me changing the cid number on without knowing to the one I said earlier. But I guess if I would ever want to run the ruu I'd have to s-off it first and do it the long way then but at least I can successfully unlock the boot loader now with no problems, or at least I think. (Haven't tried it yet)
Edit:
Problem solved I unlocked the bootloader once more moonshined and set a supercid on the phone
hey yall I been searching and reading all forums on going back to stock. theres only regular sprint htc m8 version and nothing on the hk edition so I can get the new ota and remain on stock. ive lost my back up file when I upload a custom rom. ive tried a bunch of things like using ruu and that but kept getting an error like a 32 and a 99. I cant get the s-on to turn off to get more. idk if im doing something wrong or what but im hoping someone can shine some light this way and help me out. yes I tired the sunshine apk but it pops up need based rom etc. so.........
You have to relock to use an RUU when you're still S-ON, and you must make sure that you're using an HK RUU.
Captain_Throwback said:
You have to relock to use an RUU when you're still S-ON, and you must make sure that you're using an HK RUU.
Click to expand...
Click to collapse
not to seem stupid but this is a learning process for me coming from iphone to android. so when u say relock u mean bootloader? n do I need to have original recovery. and when I do the ruu im using fastboot it wont cuz me to have an error again right?
Jeffymclovin said:
not to seem stupid but this is a learning process for me coming from iphone to android. so when u say relock u mean bootloader? n do I need to have original recovery. and when I do the ruu im using fastboot it wont cuz me to have an error again right?
Click to expand...
Click to collapse
Yes, relock the bootloader (fastboot oem lock). That'll prevent the error 92 or whichever it was. It doesn't matter what recovery is on there, as the RUU will overwrite it with stock.
Captain_Throwback said:
Yes, relock the bootloader (fastboot oem lock). That'll prevent the error 92 or whichever it was. It doesn't matter what recovery is on there, as the RUU will overwrite it with stock.
Click to expand...
Click to collapse
ok im gonna give that a try right now
Captain_Throwback said:
Yes, relock the bootloader (fastboot oem lock). That'll prevent the error 92 or whichever it was. It doesn't matter what recovery is on there, as the RUU will overwrite it with stock.
Click to expand...
Click to collapse
ok I relocked the bootloader and fastboot the Sprint_HTC_One_M8_Harman_2.16.654.4_RUU it still wouldn't let me go any further {failed<remote: 12 signature verify fail>} is what I got
Jeffymclovin said:
ok I relocked the bootloader and fastboot the Sprint_HTC_One_M8_Harman_2.16.654.4_RUU it still wouldn't let me go any further {failed<remote: 12 signature verify fail>} is what I got
Click to expand...
Click to collapse
Did you review the instructions on how to flash it? I believe you extract the 0P6BIMG.zip from the larger zip file, and put it on your external SD.
Captain_Throwback said:
Did you review the instructions on how to flash it? I believe you extract the 0P6BIMG.zip from the larger zip file, and put it on your external SD.
Click to expand...
Click to collapse
yea it would kinda help if I read the instructions the right way lol I finally got it back to normal I greatly appreciate it my man but do got one more thing tho the s-on am I able to use firewater to get it off now or use sunshine apk cuz I was also having issues with that too
Jeffymclovin said:
yea it would kinda help if I read the instructions the right way lol I finally got it back to normal I greatly appreciate it my man but do got one more thing tho the s-on am I able to use firewater to get it off now or use sunshine apk cuz I was also having issues with that too
Click to expand...
Click to collapse
You can try Firewater, but most likely you'll need to use SunShine.