Hi all,
I updated my flyer to honeycomb, then decided to return to stock gingerbread. After a while i missed the way how honeycomb uses the stylus. Now I tried to return to honeycomb. But unlocking the relocked bootloader fails (fastboot oem unlock does not work. Also using htc unlock webpage results in errors when sending token).
Is there any possibility to unlock the relocked bootloader and return to honeycomb??? Thanks in advance!
ranzassel said:
Hi all,
I updated my flyer to honeycomb, then decided to return to stock gingerbread. After a while i missed the way how honeycomb uses the stylus. Now I tried to return to honeycomb. But unlocking the relocked bootloader fails (fastboot oem unlock does not work. Also using htc unlock webpage results in errors when sending token).
Is there any possibility to unlock the relocked bootloader and return to honeycomb??? Thanks in advance!
Click to expand...
Click to collapse
Do you still have your orginal Unlock_code.bin
If so ... use that with "fastboot flash unlocktoken Unlock_code.bin" command
I wasn't aware there is a way to re-S-ON your Flyer. How did you do that?
hssuhle said:
I wasn't aware there is a way to re-S-ON your Flyer. How did you do that?
Click to expand...
Click to collapse
If you revert with a RUU everything goes back to stock including S-ON
DigitalMD said:
If you revert with a RUU everything goes back to stock including S-ON
Click to expand...
Click to collapse
This didn't work in my case, I reverted with RUU but still S-OFF RL.
kego said:
This didn't work in my case, I reverted with RUU but still S-OFF RL.
Click to expand...
Click to collapse
That's because you made a mess of both the upgrade and rollback.
globatron said:
That's because you made a mess of both the upgrade and rollback.
Click to expand...
Click to collapse
That's the problem. I cannot go fully rollback with original hboot (1.11.0006) and s-on even I rolled back to GB 2.3.4 radio.
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?
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.
Hello! I'm running Scott's ROM ICS S-ON. I'm not looking to S-OFF unless absolutely necessary; I don't prefer messing up with a bricked phone.
I want to update to the official ICS OTA distributed by Verizon. I haven't found a post that has any information on how to do this with S-ON Relocked and a Relocked Bootloader.
In my bootloader, the information at the top is
Code:
***RELOCKED***
***SECURITY WARNING***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
RADIO-0.95.00.1118r/0.95.00.1223r
OpenDSP-v10.6.0.7611.00.0919
eMMC-boot
Oct 6 2011, 15:43:22
Any help would be appreciated. Thanks!
Download the latest RUU. If you locked your bootloader after using htc dev, all you would have to do is flash the new global RUU as normal and unlock (If you want) the bootloader again.
HTC Rezound
luis86dr said:
Download the latest RUU. If you locked your bootloader after using htc dev, all you would have to do is flash the new global RUU as normal and unlock (If you want) the bootloader again.
HTC Rezound
Click to expand...
Click to collapse
Is the new RUU the one from the Android Police website? Yes, I unlocked the bootloader via HTC Dev, and I just relocked "fastboot oem lock".
I have it rooted, so I guess now it can't boot, as it only boots into bootloader.
QuintonS said:
Is the new RUU the one from the Android Police website? Yes, I unlocked the bootloader via HTC Dev, and I just relocked "fastboot oem lock".
I have it rooted, so I guess now it can't boot, as it only boots into bootloader.
Click to expand...
Click to collapse
I downloaded the RUU from Nils Sense 4 thread. First page, third post.
http://forum.xda-developers.com/showthread.php?t=1757357
Since your relocked, just place it on root sd as PH98IMG.zip and reboot into bootloader to flash.
HTC Rezound
Alright, I'll try that. If I come up with any errors (I'll be sure if it's one), I'll come back and talk of it.
...As soon as I'm about to type what was going wrong, it decided to fix itself SOMEHOW and continue.
...Well, so far, it has appeared to be working fine! Not sure if this will fix the blue screen problem, but all I was really hoping for was to get the stock Rezound ICS update.
Thanks so much! You've been really helpful. It was much simpler than I was expecting. I'll see about rooting at a later date
Not sure how it works or the slang around here but "bump"? or "thanks" button pressed xD
QuintonS said:
...As soon as I'm about to type what was going wrong, it decided to fix itself SOMEHOW and continue.
...Well, so far, it has appeared to be working fine! Not sure if this will fix the blue screen problem, but all I was really hoping for was to get the stock Rezound ICS update.
Thanks so much! You've been really helpful. It was much simpler than I was expecting. I'll see about rooting at a later date
Not sure how it works or the slang around here but "bump"? or "thanks" button pressed xD
Click to expand...
Click to collapse
Lol. No problem.
HTC Rezound
luis86dr said:
Lol. No problem.
HTC Rezound
Click to expand...
Click to collapse
I am in a similar state and I have one follow up question. I read in another thread that before relocking my bootloader, I would need to Flash stock recovery because I have Amon-Ra installed. Is flashing the stock recovery absolutely required before relocking and flashing the new global ruu?
Thanks in advance.
layneja said:
I am in a similar state and I have one follow up question. I read in another thread that before relocking my bootloader, I would need to Flash stock recovery because I have Amon-Ra installed. Is flashing the stock recovery absolutely required before relocking and flashing the new global ruu?
Thanks in advance.
Click to expand...
Click to collapse
No, you don't need to flash stock recovery. The RUU will do that for you. Just make sure you're locked before you flash the RUU. Unlock and re flash your choice of recovery after RUU is complete.
HTC Rezound
I'd like to restore my phone to its absolute default. I would like to return my phone tomorrow. Can you help explain to me how a rooted phone can be restored?
WARNING: If you have flashed a custom bootloader make sure you flash it back to a stock bootloader before you do S-ON or you WILL brick.
First read the revone one thread on how to lock everything back up. First and second post have all the info you need to make it look untouched.
http://forum.xda-developers.com/showthread.php?t=2314582
Then flash the RUU after you have S-ON and Locked in the bootloader.
http://dl3.htc.com/application/tmo/....20_10.40.1150.04_release_324846_signed_2.exe
designgears said:
WARNING: If you have flashed a custom bootloader make sure you flash it back to a stock bootloader before you do S-ON or you WILL brick.
First read the revone one thread on how to lock everything back up. First and second post have all the info you need to make it look untouched.
http://forum.xda-developers.com/showthread.php?t=2314582
Then flash the RUU after you have S-ON and Locked in the bootloader.
http://dl3.htc.com/application/tmo/....20_10.40.1150.04_release_324846_signed_2.exe
Click to expand...
Click to collapse
I currently have "unlocked" and "tampered," so do I just need to flash the RUU?
hammettorchandler said:
I currently have "unlocked" and "tampered," so do I just need to flash the RUU?
Click to expand...
Click to collapse
Do you have hboot version 1.44? If so run this from bootloader:
fastboot oem lock
Then run the ruu. If you're s-off check the thread designgears just shared with you and go s-on last.
Sent from my HTC One using xda premium
mikeyinid said:
Do you have hboot version 1.44? If so run this from bootloader:
fastboot oem lock
Then run the ruu. If you're s-off check the thread designgears just shared with you and go s-on last.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
He should use revone first to make it look untouched because the motochopper root method is blocked. Otherwise he will have to go back to the state he is in now and do it all in the right ordered
designgears said:
He should use revone first to make it look untouched because the motochopper root method is blocked. Otherwise he will have to go back to the state he is in now and do it all in the right ordered
Click to expand...
Click to collapse
ah, you are correct.
Many thanks to you both. Mission accomplished. I re-rooted too afterwards.
Sorry for the newbish questions, but if I'm getting a replacement phone because my screen cracked and I need to send my current phone back to Asurion. I'm currently on the 1.54 hboot from the international firmware, so do simply need to flash back to the stock 1.44 hboot, use REVONE to revert to S-On, lock the bootloader and then flash the RUU? Also, can I flash the decrypted RUU zip instead of the RUU.exe after I've relocked the bootloader? I'm a Linux user and would prefer not having to install Windows to bring the phone back to stock.
RobBull69 said:
Sorry for the newbish questions, but if I'm getting a replacement phone because my screen cracked and I need to send my current phone back to Asurion. I'm currently on the 1.54 hboot from the international firmware, so do simply need to flash back to the stock 1.44 hboot, use REVONE to revert to S-On, lock the bootloader and then flash the RUU? Also, can I flash the decrypted RUU zip instead of the RUU.exe after I've relocked the bootloader? I'm a Linux user and would prefer not having to install Windows to bring the phone back to stock.
Click to expand...
Click to collapse
Insurance doesn't care what state you are in. Because you are paying them a deductible. No need to go through a that
Sent from my HTC One using xda app-developers app
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).