Hi all,
I have installed a custom recovery on my ATT HTC One M8. It is rooted and I am trying to install an OTA update. I am fairly new to this and I need help. I can try provide any information necessary. I am currently on 4.28.502.1 and the OTA update is 4.28.502.2. I keep getting ERROR 155 and I don't know what I am doing wrong. Thank you
Not for the M8.....it might help.
http://forum.xda-developers.com/showthread.php?t=1655832
I downloaded MyAndroidTools and actually shut down my HTC DM service. There are 2 of them. I went into HTCDM and unchecked DmService . I no longer see the update prompt.
I am waiting a few days to see how this pans out.... I really don't feel like unrooting and relocking.
Kelvala said:
Not for the M8.....it might help.
http://forum.xda-developers.com/showthread.php?t=1655832
I downloaded MyAndroidTools and actually shut down my HTC DM service. There are 2 of them. I went into HTCDM and unchecked DmService . I no longer see the update prompt.
I am waiting a few days to see how this pans out.... I really don't feel like unrooting and relocking.
Click to expand...
Click to collapse
I need to have S-OFF to relock my bootloader, but I can't find a program to help me achieve that. There was firewater and that has become discontinued. There is SunShine ( I think that is what its called ) which you have to pay $25 for. I don't know if it's worth it.
Error 155 is because of unlocked bootloader. Only way to have unlocked and run an ruu successful is with s-off. Just relock and ruu you can always unlock again via HTCdev. Type the command below to relock when s-on.
Fastboot oem lock
It will show relocked, so it won't help with warranty, but if you are planning to unlock again, it will work.
Uzephi said:
Error 155 is because of unlocked bootloader. Only way to have unlocked and run an ruu successful is with s-off. Just relock and ruu you can always unlock again via HTCdev. Type the command below to relock when s-on.
Fastboot oem lock
It will show relocked, so it won't help with warranty, but if you are planning to unlock again, it will work.
Click to expand...
Click to collapse
Are you sure I can relock my bootloader with S-ON? I've looked all around and it says I need to be S-OFF.
Give it a shot. If the ruu is the same version or higher, you can ruu easily with s-on
Uzephi said:
Give it a shot. If the ruu is the same version or higher, you can ruu easily with s-on
Click to expand...
Click to collapse
Do I just run that command in cmd? Or there is something else ?
xChaosLegion said:
Do I just run that command in cmd? Or there is something else ?
Click to expand...
Click to collapse
You just run it in cmd while the phone is in fastboot mode
Ok, so new to HTC and all this s-off/on stuff....If I have my bootloader unlocked now and am stock rooted, all I need to do is buy Sunshine, s-off and I can install the OTA update without losing my apps and homescreen setting etc...?
Kelvala said:
Ok, so new to HTC and all this s-off/on stuff....If I have my bootloader unlocked now and am stock rooted, all I need to do is buy Sunshine, s-off and I can install the OTA update without losing my apps and homescreen setting etc...?
Click to expand...
Click to collapse
/system has to be unmodified. This means most things that require root to change (E.G. removing system apps, changing build.prop, xposed, etc) have to be reverted to stock for an ota to work. You do not need s-off to take an ota. Just uproot, put /system back to stock and flash the stock recovery.
xChaosLegion said:
Are you sure I can relock my bootloader with S-ON? I've looked all around and it says I need to be S-OFF.
Click to expand...
Click to collapse
You need s-off to make it say LOCKED. With s-on, you can only make it RELOCKED.
The only reason to make it LOCKED is for warranty purposes through HTC (AT&T warranty actually doesn't care of the phone is modded).
Related
These steps will get you completely back to stock.
I want to first say thanks to the unlimited.io team for making S-OFF possible.
Secondly, by following these instructions you are acknowledging that should something go wrong and you brick your device, I am not at fault nor are the developers of the S-OFF method for the HTC RUBY. Follow these instructions at your own risk! I am NOT a dev, just stupid enough to be the first one (I think) To try this. I am not going to give instructions on how to use fastboot, if you are S-Off, then you should already know.
Third, you WILL be able to re-unlock your bootloader and regain S-OFF after you have followed these instructions. If you want to do so, there are other threads on how to do that.
And 4th, I have only tried this on a tmobile branded device. I have no idea if this works on any other device. I think it should, but I don't know for sure. If anybody wants to give it a try and let me know, then i will update the OP.
Now to the steps.
1. Download the stock ruu from here
2. Lock your bootloader by using the fastboot command "fastboot oem lock"
3. Reboot to system
4. Flash the stock RUU you downloaded by placing it in the root of your external sd card and renaming it PH85IMG.zip and rebooting to bootloader.
5. Once you have the stock rom reinstalled, set the security lock by using fastboot command " fastboot oem writesecureflag 3"
6. Profit?
That's it!
Special thanks to frodoboy for the idea and to krook6023 for posting the stock RUU's.
If this helped you at all, please remember to hit the thanks button!
Security lock by using fastboot command (S-ON) requires a stock RUU beforehand?
interesting
kaabob said:
Security lock by using fastboot command (S-ON) requires a stock RUU beforehand?
interesting
Click to expand...
Click to collapse
I should have clarified, the steps are if you want to go completely stock, will update the OP.
Will it read "relocked" or "locked"? I thought being "completely stock" was not totally possible because it would always say "relocked".
Sent from my HTC_Amaze_4G using XDA
bjcolema said:
Will it read "relocked" or "locked"? I thought being "completely stock" was not totally possible because it would always say "relocked".
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
kishon120 said:
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
Click to expand...
Click to collapse
That's good to know. Thanks.
Sent from my HTC_Amaze_4G using XDA
kishon120 said:
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
Click to expand...
Click to collapse
Thanks for replying.
This is correct, my phone said locked, not relocked.
I would like to stress that YOU NEED A FULL RUU, not a stock nandroid backup. Otherwise, you are going to need that link on my sig
Sent from my HTC Sensation using XDA
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Thaxtonator said:
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Click to expand...
Click to collapse
You can't downgrade back to GB once you've updated to ICS, if that's what you're trying to do. At least not very easily.
electronicrice said:
You can't downgrade back to GB once you've updated to ICS, if that's what you're trying to do. At least not very easily.
Click to expand...
Click to collapse
If you are S-Off, then following this guide will put you back to stock gingerbread.
Thaxtonator said:
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Click to expand...
Click to collapse
I dont know a way for going back to stock without being s=off. You could possibly flash the newest official release (ics, one that hasnt been modified) then relock your bootloader, but i think that it will show relocked rather than locked. Worth a try though.
Okay thanks for the input guys. It isn't a huge deal, I just didn't think there was enough "goodies" rom-wise for ICS, but there are some hardworking devs on here. Looking forward to the Sense 4.0 rom.
dcmtnbkr said:
Special thanks to frodoboy for the idea and to krook6023 for posting the stock RUU's.
If this helped you at all, please remember to hit the thanks button!
Click to expand...
Click to collapse
Thanks for the "thanks" dcm. Question though. I'm sure you've gone back to S-Off so did you have to do the wire trick again or just try the fastboot oem writesecureflag 0 or whatever it needs to be to go S-Off again?
frodoboy said:
Thanks for the "thanks" dcm. Question though. I'm sure you've gone back to S-Off so did you have to do the wire trick again or just try the fastboot oem writesecureflag 0 or whatever it needs to be to go S-Off again?
Click to expand...
Click to collapse
When s-on, you can't go back to s-off by writing the security flag again . You have to do again the juopunutbear procedure including the wire trick
Sent from my HTC Sensation Z710e
Just curious which RUU one should flash if returning to stock?
RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14. 550L.17DC_30.78.550L.15_release_257469_signed.zip
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip
3oudreaux said:
Just curious which RUU one should flash if returning to stock?
RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14. 550L.17DC_30.78.550L.15_release_257469_signed.zip
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip
Click to expand...
Click to collapse
This one would be best: RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
I spent 3 hrs trying to solve the relocked and locked issue until finally I got it resolved. with the manual option to lock with hasoon tool, places *** RELOCKED *** in hboot, which clearly and obvious for any technician to see you tampered with the hboot files from stock. my reason for doing this to get my warranty back.
how did i fixed "RELOCKED" to show as *** LOCKED *** ? after the hasoon tool 3.2 relocked the bootloader i was challenged, but decided the first step would be switching the security off and on (s-off/ s-on)
first return to stock RUU through boot loader, then adb command fastboot oem writesecureflag 3 to enable s-on. *toggled it on
i reinstalled juopunutbear s-off again carefully following the instructions. with a paperclip grounding the phone and selecting for juopunutbear's modified files "y" enter.
then your *** RELOCKED *** shows as *** juopunutbear *** in hboot. (at first i thought I dig myself a bigger hole)
I used Hasoon tool 3.2 again to RELOCK bootloader, with the intention of reinstall the stock RUU again. however it still showed as *** juopunutbear *** with the message its already locked.
Now I installed the the Stock RUU again from bootloader. once complete back to the hboot, to show *** LOCKED *** and s-off Progress!!!
repeat enable s-on instructions by writing adb: fastboot oem writesecureflag 3,
now shows
*** LOCKED ***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
OpenADSP-02.6.0.2226.00.0202
eMMC-boot
a step closer for the warranty being back to the device, without a dispute with the warehouse/ carrier
how do we delete the line -OpenADSP-02.6.0.2226.00.0202?
it was added with the juopunutbear s-off hboot files, without that file the hboot would be 100 percent legit for the warranty!
aoakes said:
how do we delete the line -OpenADSP-02.6.0.2226.00.0202?
it was added with the juopunutbear s-off hboot files, without that file the hboot would be 100 percent legit for the warranty!
Click to expand...
Click to collapse
No need to get rid of that. New phone from T-Mobile with HBOOT 1.93 and it had that line it . It looks like 1.90 is the one that doesn't have that line. Because my wife's phone is on 1.90 and she doesn't have it.
I'm going to be following the method in a few days. Can you guys confirm this all works as it should?
I had my HTC amaze unlocked with s-off and a modded hboot I then updated to a new ICS firmware to run ICS however when the firmware flashed to my phone it locked my phone and reset my hboot but still kept s-off. Is there anyway to unlock my phone again? If anyone has any help please let me know I already tried to unlock it through HTdev website and it did not work!!!
If you are s=off, then you don't need to unlock your bootloader. I'm assuming you have eng bootloader, and with that, you don't need to unlock anything.
Sent from my HTC_Amaze_4G using xda premium
pharmhand said:
I had my HTC amaze unlocked with s-off and a modded hboot I then updated to a new ICS firmware to run ICS however when the firmware flashed to my phone it locked my phone and reset my hboot but still kept s-off. Is there anyway to unlock my phone again? If anyone has any help please let me know I already tried to unlock it through HTdev website and it did not work!!!
Click to expand...
Click to collapse
HTC dev website is the way i did it, and it worked perfect for me. What method did you use that didn't allow you to unlock your phone?
Sent from my HTC_Amaze_4G using Tapatalk 2
If any of you read correctly, he said he unlocked it before, therefore, all he has to do is place the unlock_code file in hasoon's tool's data folder and run the unlock bootloader option, voila he's back to being unlocked, though the relocking sounds kind of odd, but it could probably be due to the hboot he was using, I'm guessing was Juopunutbear's or something.
Dark Nightmare said:
If any of you read correctly, he said he unlocked it before, therefore, all he has to do is place the unlock_code file in hasoon's tool's data folder and run the unlock bootloader option, voila he's back to being unlocked, though the relocking sounds kind of odd, but it could probably be due to the hboot he was using, I'm guessing was Juopunutbear's or something.
Click to expand...
Click to collapse
I did read it, the old unlock bin does not work with new ics so he has to redo everything once more....
Sent from my HTC_Amaze_4G using Tapatalk 2
Well my old unlock bin worked fine for me re-unlocking on ICS, guess I was lucky, okay cool, my bad.
Yes I had hboot from Juopunutbear when I did the s-off it asked to install his hboot but after I upgraded it changed my hboot back to 1.93.0002 and it is SHIP s-off not eng which I am not totally sure what the difference is but is there a way to change SHIP back to ENG????? I am going to give HTCdev another chance and see what happens... thanks for the input and help
ok so I just tried HTCdev again and it unlocked my phone however it did a hard reset the only thing I have to do now is to have eng s-off instead of ship s-off.
pharmhand said:
ok so I just tried HTCdev again and it unlocked my phone however it did a hard reset the only thing I have to do now is to have eng s-off instead of ship s-off.
Click to expand...
Click to collapse
Just flash the eng hboot via bootloader, though you don't need to, unless you plan to do fastboot commands, which the average user doesn't have much need for, hasoon's tool does everything you need, recovery, root, etc, though I do recommend 4EXT recovery, which you can easily install after obtaining root.
anyone have accomplish this? I've been trying for last few days. I run the gb ruu the latest Ota twice (yesterday I ran it 4 times) and then the s-on command trough fastboot/adb and I'm left whit stock gb, s-on and RE-LOCKED HBOOT.
Is there anyway to get it to LOCKED?
Thanks in Advance
Edit: I've been running the 2.01.605.11 Ota gb ruu.
You need to S-OFF first and then relock it. Running RUU will give you RELOCKED or TAMPERED.
Cares said:
You need to S-OFF first and then relock it. Running RUU will give you RELOCKED or TAMPERED.
Click to expand...
Click to collapse
While s-off run the fastboot commands to relock the HBOOT? Can you tell me those commands? Thanks.
Did you unlock while s-off? If you did, you need to s-off again. After s-off you will have a locked bootloader again. Than ruu to gb ota, and send the s-on commands through fastboot.
That will leave you with stock gb, s-on and lock bootloader.
Do not send the s-on command unless your are 100% sure you have an ota stock hboot. Or you will have a brick
I am pretty sure that there is no way to get it to say locked. It will just say relocked. Someone was working on a way to change that but I think they decided not to continue because they didn't want to be accused of encouraging fraud.
Cares said:
You need to S-OFF first and then relock it. Running RUU will give you RELOCKED or TAMPERED.
Click to expand...
Click to collapse
No no, just do the S-OFF. If you attempt to lock after S-OFF, it will say RELOCKED.
The S-OFF process is the only way to get back to LOCKED. If you unlock or run the fastboot command to lock again after that, it will show RELOCKED.
a.mcdear said:
No no, just do the S-OFF. If you attempt to lock after S-OFF, it will say RELOCKED.
The S-OFF process is the only way to get back to LOCKED. If you unlock or run the fastboot command to lock again after that, it will show RELOCKED.
Click to expand...
Click to collapse
I meant turning security flag on.
Alright thanks guys gonna try again tonight after work. I'll report back later.
You can definitely return to **Locked** without question if you have s-off. Just run the newest leak RUU twice and it should take it back to locked but S-OFF, did it to my girl's unlocked+s-off rezound two nights ago. I didn't even have to manually run it twice, it just keep rebooting and did the 2nd run on it's own. It's now the stock hboot, locked, s-off. Then if you want GB there shouldn't be any issue flashing the GB RUU since you'd maintain S-OFF
PhantomApollyon said:
You can definitely return to **Locked** without question if you have s-off. Just run the newest leak RUU twice and it should take it back to locked but S-OFF, did it to my girl's unlocked+s-off rezound two nights ago. I didn't even have to manually run it twice, it just keep rebooting and did the 2nd run on it's own. It's now the stock hboot, locked, s-off. Then if you want GB there shouldn't be any issue flashing the GB RUU since you'd maintain S-OFF
Click to expand...
Click to collapse
So the newest one is this one?
3.14.605.10
Kratz17 said:
So the newest one is this one?
3.14.605.10
Click to expand...
Click to collapse
right
PhantomApollyon said:
right
Click to expand...
Click to collapse
Ok gonna give a shot to that. Thanks.
I think my wife's Rezound is starting to have issues. It is randomly freezing and you need to power it off and on for it to come back. Even happened right after a clean flash while in the setup screens.
I do have ICS on it and my bootloader is unlocked and I am s-off. What are the steps needed before sending it back to Verizon and has anyone had any issues when sending the device back after re-locking it?
I looked for a thread on this but had no luck on a step by step process......
Appreciate the help in advance.
Reflash the factory RUU and then revert to S-ON. If your bootloader is unlocked, you'll need to relock it before you flash the RUU.
shrike1978 said:
Reflash the factory RUU and then revert to S-ON. If your bootloader is unlocked, you'll need to relock it before you flash the RUU.
Click to expand...
Click to collapse
Where can we get the latest update RUU? Does it need to be flashed in the bootlader screen? How does one get back to S-ON?
So step one is to relock the bootloader which I know can be done with the tool.
Then flash the RUU, (waiting for correct way)
Then back to S-On (waiting on instructions how)
i'll help
Are you unlocked or locked?
You are s-off right?
What is you're hboot? is it modified?
I am unlocked
I am s-off
Not sure which hboot I am on. Can't get my wife's phone right now. I am not on the latest hboot I don't think but the one right before it.
As far as it being modified, was that something it asked when doing the s-off? If yes, then I believe I did it. Can no for sure tomorrow when I check the device.
Relock with the toolkit or with "fastboot oem lock"
Latest OTA RUU: http://forum.xda-developers.com/showthread.php?t=1810931&highlight=+12+ruu
How to S-ON: http://forum.xda-developers.com/showthread.php?p=25167284
Do it in that order
Search is your friend.
Also, when you S-OFF, it will relock your bootloader. You do not need to unlock it again. S-OFF > unlock.
Hi,
Is it possible to remove the tampered flag without unlocking the bootloader through htcdev? The phone is S-ON again, but still has root. I ask, because somehow after locking bootloader and reverting to S-ON after downgrade to JB, the tampered flag appeared. I wouldn't like to go through the htcdev unlock process because it factory resets the phone and I got it all setup again.
Thanks.
Yes u can do it with s-off. http://forum.xda-developers.com/showthread.php?t=2808912
Child's Play said:
Yes u can do it with s-off. http://forum.xda-developers.com/showthread.php?t=2808912
Click to expand...
Click to collapse
So is there a way for me to gain S-OFF without actually unlocking the bootloader, now that I have root?
rocky7x said:
So is there a way for me to gain S-OFF without actually unlocking the bootloader, now that I have root?
Click to expand...
Click to collapse
Rumrunners website claims you only need htcdev unlock "or" root. Everyone seems to have different results though. Would be worth giving it a shot.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Yes but dont know if its possible to get s-off again. Try it
Child's Play said:
Yes but dont know if its possible to get s-off again. Try it
Click to expand...
Click to collapse
Hmmm I've just read on a HTC One related forum that tampered flag is set because of root. And since I don't want to scrap root, I think that even if I used rumrunner, got S-OFF, then did the revone stuff and locked it back to S-ON, the tampered would jump up again, because of root with stock bootloader. Not really sure if that is somehow related - does anyone have a stock Jellybean with everything stock (bootloader, recovery etc), bootloader locked and S-ON AND with root? Does it show tampered?
It has nothing to do with root. It appears when u unlock the bootloader.
Remove the tampered banner- http://forum.xda-developers.com/showpost.php?p=47576052&postcount=7&nocache=1&z=8527302977163345
Recovery, roms, hboots, etc- http://forum.xda-developers.com/des...x-roms-mods-recoveries-backups-tools-t2804427
Child's Play said:
It has nothing to do with root. It appears when u unlock the bootloader.
Remove the tampered banner- http://forum.xda-developers.com/showpost.php?p=47576052&postcount=7&nocache=1&z=8527302977163345
Recovery, roms, hboots, etc- http://forum.xda-developers.com/des...x-roms-mods-recoveries-backups-tools-t2804427
Click to expand...
Click to collapse
Hi, OK so I've tried it and unfortunately I couldn't get S-OFF. Rumrunner just crashed after message:
Code:
must sanitize, skunky rum is nasty
hold please..............................................
[TTTT********************************************************]
So I guess it's not possible to get S-OFF without unlocked bootloader (only with root).
U need to grant supersu permission. Try again