I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
anonimoyque said:
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
Click to expand...
Click to collapse
Remove/replace the battery and restart the bootloader and try flashing the RUU again. If that doesn't work you can try flashing the RUU.exe from Windows with the bootloader in "fastboot USB" mode.
ramjet73
anonimoyque said:
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
Click to expand...
Click to collapse
one thing i have learned is when flashing roms, make sure you have the correct firmware package, and hboot.. because some Roms use the VM Firmware from the leak a few months back, while others use the Sprint Firmware, also depending on the base of the rom you may need to flash a newer or older hboot
anonimoyque said:
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
Click to expand...
Click to collapse
try unlocking your bootloader again and THEN flashing that gingerbread RUU best to also have s-off... but if not you should still be ok .... but the unlocked bootloader is a must... you said youre relocked...
wloftus said:
try unlocking your bootloader again and THEN flashing that gingerbread RUU best to also have s-off... but if not you should still be ok .... but the unlocked bootloader is a must... you said youre relocked...
Click to expand...
Click to collapse
I agree about being s-off, but the ruu.exe will error out if the bootloader is unlocked. You must relock the bootloader first.
coal686 said:
I agree about being s-off, but the ruu.exe will error out if the bootloader is unlocked. You must relock the bootloader first.
Click to expand...
Click to collapse
i use linux so i dont do the EXE's... i take the RUU and rename it to PG86IMG.zip and it still works unlocked or not... just different approaches depending on the OS you use i guess
wloftus said:
i use linux so i dont do the EXE's... i take the RUU and rename it to PG86IMG.zip and it still works unlocked or not... just different approaches depending on the OS you use i guess
Click to expand...
Click to collapse
That should be the same thing as long as the RUU.zip is extracted from the RUU.exe and properly signed.
But coal is right about needing the bootloader locked/relocked to flash the RUU if you are S-ON (which the OP said he is), regardless of whether you use the RUU.exe or RUU.zip.
ramjet73
ramjet73 said:
That should be the same thing as long as the RUU.zip is extracted from the RUU.exe and properly signed.
But coal is right about needing the bootloader locked/relocked to flash the RUU if you are S-ON (which the OP said he is), regardless of whether you use the RUU.exe or RUU.zip.
ramjet73
Click to expand...
Click to collapse
no he is not...ive reloaded GB and ICS manually while being unlocked you cant tell me what i have and have not done considering IM the one thats done it
wloftus said:
no he is not...ive reloaded GB and ICS manually while being unlocked you cant tell me what i have and have not done considering IM the one thats done it
Click to expand...
Click to collapse
Unlocked and S-OFF, right? That works fine but an RUU flash with S-ON and an unlocked bootloader will fail, regardless of how you do it.
If you don't believe me set your phone back to S-ON and try it.
From the OP:
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
Click to expand...
Click to collapse
That sure looks like S-ON to me. The reason I jumped back into this thread is that I don't want other users getting incorrect information.
ramjet73
ramjet73 said:
Unlocked and S-OFF, right? That works fine but an RUU flash with S-ON and an unlocked bootloader will fail, regardless of how you do it.
If you don't believe me set your phone back to S-ON and try it.
From the OP:
That sure looks like S-ON to me. The reason I jumped back into this thread is that I don't want other users getting incorrect information.
ramjet73
Click to expand...
Click to collapse
make up your mind you first said its the locked relocked status... now you say its the s-on , s-off status....if iive still done flashes with the s-on status and while still unlocked so i dont know what problems you all are running into
wloftus said:
make up your mind you first said its the locked relocked status... now you say its the s-on , s-off status....if iive still done flashes with the s-on status and while still unlocked so i dont know what problems you all are running into
Click to expand...
Click to collapse
I don't think so.
You really should try flashing an RUU (.exe or .zip) with radio S-ON and an unlocked bootloader before you advise other users to try that. If you can do that successfully I will admit I am wrong in this thread. Otherwise, please stop insisting that it will work.
You have been ignoring the fact that the OP is S-ON throughout this thread and that really isn't going to help him at all.
ramjet73
ramjet73 said:
I don't think so.
You really should try flashing an RUU (.exe or .zip) with radio S-ON and an unlocked bootloader before you advise other users to try that. If you can do that successfully I will admit I am wrong in this thread. Otherwise, please stop insisting that it will work.
You have been ignoring the fact that the OP is S-ON throughout this thread and that really isn't going to help him at all.
ramjet73
Click to expand...
Click to collapse
i have... i infact did it earlier with the upgrade to ICS while flashing the firmware.zip file after renameing it to PG86IMG.zip and WOW it worked... im done arguing ... this is my last post... post again if you feel you need the last word....
wloftus said:
im done arguing ... this is my last post... post again if you feel you need the last word....
Click to expand...
Click to collapse
Thank you. I will make one last post just so people are clear on the requirements for flashing an RUU with S-ON.
Here's a quote from mpgrimm2's My Running stock RUU Reference info post:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
That guide has been around for a long time on XDA and another website and it has been used by a lot of people, including myself. If that information was wrong, I'm sure mpgrimm2 would have corrected it by now.
If you want to flash an RUU with S-ON and an unlocked bootloader, make sure that you relock it before flashing or you will get an error.
ramjet73
wloftus, I'm not saying you're lying since as you said, you were the one who did it and you say it worked for you. But, if one is s-on and unlocked, the ruu will error out with error 155. I google searched ruu lock bootloader error and found many sites that say the bootloader must be locked if s-on (see below). But, if one wants to try while leaving the bootloader unlocked, then be my guest. If it works, great; if not, then relock the bootloader.
Sources:
Should I relock my bootloader
[HOW TO] Flash RUU / OTA when getting ERROR 155 although phone is back to stock
And one specific to the Evo3d: http://forums.androidcentral.com/htc-evo-3d/198402-ruu-2-89-651-2-hboot-1-58-a.html#post2084625
wloftus said:
try unlocking your bootloader again and THEN flashing that gingerbread RUU best to also have s-off... but if not you should still be ok .... but the unlocked bootloader is a must... you said youre relocked...
Click to expand...
Click to collapse
Hey thanks for your comment, yes it says relocked but also Security Warning... do you know how can I remove this? so I can leave it locked again and try to reinstall the stock RUU?
ramjet73 said:
Unlocked and S-OFF, right? That works fine but an RUU flash with S-ON and an unlocked bootloader will fail, regardless of how you do it.
If you don't believe me set your phone back to S-ON and try it.
From the OP:
That sure looks like S-ON to me. The reason I jumped back into this thread is that I don't want other users getting incorrect information.
ramjet73
Click to expand...
Click to collapse
I agree with you... the probllem is that I cannot relock the cell phone... when I try I get the message relocked but also the message security warning!!
how can I remove it??
anonimoyque said:
I agree with you... the probllem is that I cannot relock the cell phone... when I try I get the message relocked but also the message security warning!!
how can I remove it??
Click to expand...
Click to collapse
There's a thread here that discusses, but people seem to have used various methods to solve it from restarting the bootloader to reflashing their unlock token. That's why I recommended in my first post of this thread that you remove/replace the battery and restart the bootoader.
ramjet73
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?
So I just spent a long time trying to get s-off on my evo lte. Well after a few hours and linux running on my windows pc I got lazy panda to give me s-off. Well I then decided to go ahead and install a firmware update with the new 1.19 hboot(I obviously wasn't thinking). My phone still has s-off but now has a locked boot loader. I'm pretty pissed and I don't think theres much I can do at this point, am I correct?
kvnbrkbl said:
So I just spent a long time trying to get s-off on my evo lte. Well after a few hours and linux running on my windows pc I got lazy panda to give me s-off. Well I then decided to go ahead and install a firmware update with the new 1.19 hboot(I obviously wasn't thinking). My phone still has s-off but now has a locked boot loader. I'm pretty pissed and I don't think theres much I can do at this point, am I correct?
Click to expand...
Click to collapse
try flashing a recovery with adb or fasboot in the bootloader
kvnbrkbl said:
So I just spent a long time trying to get s-off on my evo lte. Well after a few hours and linux running on my windows pc I got lazy panda to give me s-off. Well I then decided to go ahead and install a firmware update with the new 1.19 hboot(I obviously wasn't thinking). My phone still has s-off but now has a locked boot loader. I'm pretty pissed and I don't think theres much I can do at this point, am I correct?
Click to expand...
Click to collapse
click on the link below and fallow the tutorial. you will be able to get the bootloader unlocked and root.
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
Hit the thanks button.
You are S-OFF still. It doesnt matter if the bootloader says **Locked**
chico1983 said:
click on the link below and fallow the tutorial. you will be able to get the bootloader unlocked and root.
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
Hit the thanks button.
Click to expand...
Click to collapse
Dont do this ^^^^^^^^
I did the samething and I'm still able to flash twrp via bootloader. Don't need to adb or anything.
Sent from my EVO using xda app-developers app
Rxpert said:
You are S-OFF still. It doesnt matter if the bootloader says **Locked**
Dont do this ^^^^^^^^
All you have to do is reinstall the old lazypanda 1.12.222 bootloader
Click to expand...
Click to collapse
Thank you very much! That was so easy. I'm so glad I have the s-off, that really saved me here.
send me the steps to get s-off on my evo lte
kvnbrkbl said:
So I just spent a long time trying to get s-off on my evo lte. Well after a few hours and linux running on my windows pc I got lazy panda to give me s-off. Well I then decided to go ahead and install a firmware update with the new 1.19 hboot(I obviously wasn't thinking). My phone still has s-off but now has a locked boot loader. I'm pretty pissed and I don't think theres much I can do at this point, am I correct?
Click to expand...
Click to collapse
can you send me the link or email the step on how to s-off on my evo lte email: [email protected]
kvnbrkbl said:
So I just spent a long time trying to get s-off on my evo lte. Well after a few hours and linux running on my windows pc I got lazy panda to give me s-off. Well I then decided to go ahead and install a firmware update with the new 1.19 hboot(I obviously wasn't thinking). My phone still has s-off but now has a locked boot loader. I'm pretty pissed and I don't think theres much I can do at this point, am I correct?
Click to expand...
Click to collapse
Question did you get S-OFF from hboot 1.19 directory or did you get S-OF with hboot 1.12?
He got it with 1.12
Sent from my EVO using xda premium
You can't get it with anything but 1.12, so that should answer your question
Sent from my EVO using Tapatalk 2
Rxpert said:
You can't get it with anything but 1.12, so that should answer your question
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I've been s-off (1.12) since the exploit was found. Always thought you'd lose s-off or root if I updated the bootloader but after reading this thread, it sounds like I can update to 1.19 and just reinstall twrp?
Currently running Mean 3.6 with just the radio updates. Phone is running fine, any reason to update the bootloader?
Appreciate your help, there's a lot of info out there that contradicts itself.
You don't want hboot 1.19
There's absolutely no reason to do that
Sent from my EVO using Tapatalk 2
Rxpert said:
You don't want hboot 1.19
There's absolutely no reason to do that
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the advise, will leave well enough alone. Did read a little about bootloaders and thought I might be missing out on optimized updates etc.
mhmobile said:
...
there's a lot of info out there that contradicts itself.
Click to expand...
Click to collapse
if there's 4 people with advice, you get 6 different opinions !
thinking back ...
after S-OFF, i think yer at 12.1111
and then i flashed the fastboot enabled hboot that is at lazypanda site.
i think that brings you to 12.2222
something like that
i used Dan's customizer and put the stock look back in bootloader
and got rid of the red text
similar problem huge please help
i cant load any roms i have the team win but whenever i try to load a rom it hust stays booting
****tampared***
***unlocked***
jewel pvt ship s-on rl
hboot 1.9.0000
radio 1.12.11.0809
opendsp-v29 1.0.45.0622
emmc-boot
what rom can i load that will let me use my phone
i tried cyanogenmod 10 nightly and i cant load it at all just stuck at the cyanogenmod logo
any help would be helpfull just to be able to use my phone....
darkcardcaptor said:
i cant load any roms i have the team win but whenever i try to load a rom it hust stays booting
****tampared***
***unlocked***
jewel pvt ship s-on rl
hboot 1.9.0000
radio 1.12.11.0809
opendsp-v29 1.0.45.0622
emmc-boot
what rom can i load that will let me use my phone
i tried cyanogenmod 10 nightly and i cant load it at all just stuck at the cyanogenmod logo
any help would be helpfull just to be able to use my phone....
Click to expand...
Click to collapse
I already answered your thread with the solution. check there
http://forum.xda-developers.com/showthread.php?p=31144126#post31144126
mhmobile said:
I've been s-off (1.12) since the exploit was found. Always thought you'd lose s-off or root if I updated the bootloader but after reading this thread, it sounds like I can update to 1.19 and just reinstall twrp?
Currently running Mean 3.6 with just the radio updates. Phone is running fine, any reason to update the bootloader?
Appreciate your help, there's a lot of info out there that contradicts itself.
Click to expand...
Click to collapse
mana your lucky i had a hardware issue so i went from a S-Off 1.12 hboot with MeanRom on it to a PoS S-On 1.19 hboot. Stupid HTC and there premium PoS locked system. Its damn annoying. Im so Frustrated!!!!
Rxpert said:
You are S-OFF still. It doesnt matter if the bootloader says **Locked**
Dont do this ^^^^^^^^
Click to expand...
Click to collapse
Why souldn't he do this?
Not arguing, just curious
essextrain said:
Why souldn't he do this?
Not arguing, just curious
Click to expand...
Click to collapse
Never a problem with asking questions. The user was S-OFF, so it doesnt matter that his H-boot said locked. He can do whatever he pleases.
The poster was suggesting he use an overly complicated method (HTC dev to unlock the bootloader and either fastboot flashing the recovery or using an app to do it) when all he had to do was install the recovery via the bootloader
He probably could just have easily installed the old 1.12 bootloader.
stuck @ boot
Reflash boot image through recovery you have to mount USB to get the file on your sf card then reboot system then go back to fastboot and accept the update
stuck @ boot rdcaptor;31143925]i cant load any roms i have the team win but whenever i try to load a rom it hust stays booting
****tampared***
***unlocked***
jewel pvt ship s-on rl
hboot 1.9.0000
radio 1.12.11.0809
opendsp-v29 1.0.45.0622
emmc-boot
what rom can i load that will let me use my phone
i tried cyanogenmod 10 nightly and i cant load it at all just stuck at the cyanogenmod logo
any help would be helpfull just to be able to use my phone....[/QUOTE]
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
Well first of all I will say that I am running a CDMA EVO3D with HBOOT 1.58 and S-ON.​
Now with that out of the way, I will explain myself. After rooting my phone after the ICS update, i installed some ROMs and encountered some problems. After researching what the problem was I had managed to keep S-ON and that is why some of the features were broke. Then after doing more research I decided that it would be best to go back to stock and redo everything. So right now I have relocked my phone and am still running a custom ICS ROM. I have tried numerous RUU attempts and I always get the ERROR [140]: Bootloader Version Error after it try's "Sending/Updating Signature". So what in the world do I do next
Which RUU are trying to flash and where did you get it?
ramjet73
ramjet73 said:
Which RUU are trying to flash and where did you get it?
ramjet73
Click to expand...
Click to collapse
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed -Just copied the whole name if that works lol, and I got it from this thread
lxbeale said:
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed -Just copied the whole name if that works lol, and I got it from this thread
Click to expand...
Click to collapse
That's a GB RUU and you are on the Sprint ICS build now so it won't let you downgrade with S-ON. You can get S-OFF if you need to flash GB for some reason, or use this Sprint ICS RUU instead.
ramjet73
ramjet73 said:
That's a GB RUU and you are on the Sprint ICS build now so it won't let you downgrade with S-ON. You can get S-OFF if you need to flash GB for some reason, or use this instead.
ramjet73
Click to expand...
Click to collapse
I just tried that RUU and I got Error 132 after it was erasing my data
lxbeale said:
I just tried that RUU and I got Error 132 after it was erasing my data
Click to expand...
Click to collapse
Did your relock your bootloader before trying to flash it?
Here's a post with some troubleshooting info for flashing an RUU.
ramjet73
ramjet73 said:
Did your relock your bootloader before trying to flash it?
with some troubleshooting info for flashing an RUU.
ramjet73
Click to expand...
Click to collapse
It is relocked and the main version as well as the cid is at the appropriate settings for Sprint. I also tried using a different wire and PC, still getting the same results
lxbeale said:
It is relocked and the main version as well as the cid is at the appropriate settings for Sprint. I also tried using a different wire and PC, still getting the same results
Click to expand...
Click to collapse
I kind of lost track of where things stand now. Could you please supply the following information:
1. The heading information (top 3 lines) from your bootloader
2. The RUU you are currently trying to flash and where you got it
3. How you are flashing the RUU and when you get the error
The 132 error is a signature problem that is usually caused by an unlocked bootloader and I don't understand how you are getting it unless the RUU you are flashing is corrupted.
You could try downloading the RUU.exe from here and make sure the MD5 matches.
ramjet73
ramjet73 said:
I kind of lost track of where things stand now. Could you please supply the following information:
1. The heading information (top 3 lines) from your bootloader
2. The RUU you are currently trying to flash and where you got it
3. How you are flashing the RUU and when you get the error
The 132 error is a signature problem that is usually caused by an unlocked bootloader and I don't understand how you are getting it unless the RUU you are flashing is corrupted.
You could try downloading the RUU.exe from and make sure the MD5 matches.
ramjet73
Click to expand...
Click to collapse
Sorry it took me so long to reply, but this is the first three lines:
SHOOTER XC SHIP S-ON RL
HBOOT=1.58.000
RADIO-1.09.00.0706
The RUU that I tried was the one you recommended in the comments and then how I am doing it is having USB Debuging on while in fastboot usb then running the RUU
How did you fix this?
lxbeale said:
Sorry it took me so long to reply, but this is the first three lines:
SHOOTER XC SHIP S-ON RL
HBOOT=1.58.000
RADIO-1.09.00.0706
The RUU that I tried was the one you recommended in the comments and then how I am doing it is having USB Debuging on while in fastboot usb then running the RUU
Click to expand...
Click to collapse
How did you fix this? I have the same issue.
I have read pages and pages from the Android Development forum for the HTC Evo 4G LTE and I can't seem to find a solution that works for me because going S-OFF or re-locking bootloader and loading RUU does not seem feasible for my situation.
The phone has custom recovery (TWRP) and we successfully loaded Viperboy's deodexed 3.15 stock ROM.
Baseband is 1.02.12.0427 (super outdated)
This phone was bought second hand and is a HTC dev unlocked phone, S-ON
I would like to update the baseband to 1.12.11.1200 and update the firmware to 3.16
Caveats: I don't have access to the phone, my friend can reload custom ROMs through TWRP, but beyond that I don't think we can go through Dirty Racun and S-Off, I don't know how we can easily check the HBOOT version to determine if the HBOOT version is 1.12
What would happen if we accepted the Sprint OTA? Are we SOL with the baseband because we are S-ON?
Is there any way we can get on MeanBean 3 or stock rooted 3.16?
Any advise would be greatly appreciated.
I wouldnt accept the OTA update to 3.16
I actually did just that when I relocked my phone on Saturday and had all sort of problems after that. Now, I'm not too sure you would even be able to install the update being that your phone is unlocked *citation needed*.
http://forum.xda-developers.com/showthread.php?t=2135670 - talks about the 3.16 OTA problems
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
BaconMunch said:
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
Click to expand...
Click to collapse
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
tilltheend714 said:
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
Click to expand...
Click to collapse
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
BaconMunch said:
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
Click to expand...
Click to collapse
Relocking the phone is done through fastboot on the computer. Nothing to do with HTC. And Dev unlocked means you get an unlock token from HTC to the email that you signed up with. So if you make your own account on HTC dev and request a token, it should send nothing to the other owner.
And sorry, but I don't understand what you mean by having Hboot 1.12. You mean only flashing the radio through recovery? If that's what you mean than I can't help with that. Not sure how that works or if there are problems with that.
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
BaconMunch said:
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
Click to expand...
Click to collapse
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
xlxcrossing said:
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
Click to expand...
Click to collapse
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
My advice is get s-off it will save alot of headaches down the road
Sent from my PoS MoPho
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
Sent you a PM
The advice is free....the bandwidth, not so much
Just wanted to say thank you all for the support and advice.
I finally walked my friend over gtalk and successfully achieved S-OFF after relock, 1.15 RUU, unlock with HTC DEV, dirtyracun
Then updated full firmwares incrementally to 3.16
Then while trying to load MeanBean, realized we lost TWRP (and possibly root, need to confirm), I can only guess that went away with the RUU? That's not really documented anywhere unless that's a known thing.
TWRP installation via goomanager failed (maybe due to lack of root), I was able to find TWRP v2.3.1 bootloader, installed that and installed MeanBean 3.0.4
I think that makes us up to date, however we will likely install SuperSU via TWRP once we customize and ensure the phone is running smoothly.
Thanks again all!
Super su is included with the ROM
Sent from my EVO using xda premium