Related
Followed the guide from Paul on Modac, while attempting to unlock the bootloader I ran into an error that was resolved by updating fastboot. I successfully rooted,flashed custom rom and booted. I noticed that while in bootloader I went from S-OFF to S-ON. The fast boot error came attempting " 'fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img' " The error 'Locked' the bootloader. After I updated fastboot above command worked, BUT I was now back to S-On.
What part of the process should I redo in order to get S-OFF back?
What are my limitations with S-ON?
Any thoughts, comments, suggestions and especially solutions are appreciated.
Also the haptic buttons ( same row as pen button) do NOT work. They do not light and are not usable
Yeah the buttons don't work in honeycomb because you have the on screen buttons to do the job.
And It's normal to have s-on. HTC's method only unlocks the bootloader. I'm pretty sure you aren't able to flash kernels or something like that.
Sent from my HTC Evo 3D using XDA App
Gumby63 said:
Yeah the buttons don't work in honeycomb because you have the on screen buttons to do the job.
And It's normal to have s-on. HTC's method only unlocks the bootloader. I'm pretty sure you aren't able to flash kernels or something like that.
Sent from my HTC Evo 3D using XDA App
Click to expand...
Click to collapse
I was able to flash a custom rom.
Just got home from work. Revolutionary does not support the HC bootloader version 1.11.0006.
My question is, what part of the process caused my device to go from S-ON->S-OFF-> Back to S-ON?
I know I'm limited now, can I downgrade my bootloader version 1.11.0003 or 1.11.0000?
Thank for your help
ATownI20 said:
I was able to flash a custom rom.
Just got home from work. Revolutionary does not support the HC bootloader version 1.11.0006.
My question is, what part of the process caused my device to go from S-ON->S-OFF-> Back to S-ON?
I know I'm limited now, can I downgrade my bootloader version 1.11.0003 or 1.11.0000?
Thank for your help
Click to expand...
Click to collapse
When you first used revolutionary you got complete s-off, and then during the process of upgrading to honeycomb you flashed a new hboot which gave you s-on again because well..It's a new hboot. Lol. And the only way you can downgrade your hboot is to run the ruu for your model flyer to revert back to gingerbread. If you have the US 16gb version then you cannot go back to gingerbread because there isn't a ruu yet.
Hopefully I'm not confusing you more
Revolutionary does not support the HC bootloader version 1.11.0006.
but after unlock bootloader go htc dev.com and unlock bootloader from step by step guaid....after you see in fastboot
"""""""unlocked""""""""
FLYER PVT SHIP S-ON
And flash castom recovery
copy revolutionary-cwm-4.0.1.4-flyer.newhboot.img in to dir (you create dir ,by htc dev guaid)
and run command in cmd
fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img' this recovery support all castom Rom based on Honeycomb
S-Off not needed for you.
Sorry my bad English...
Gumby63 said:
When you first used revolutionary you got complete s-off, and then during the process of upgrading to honeycomb you flashed a new hboot which gave you s-on again because well..It's a new hboot. Lol. And the only way you can downgrade your hboot is to run the ruu for your model flyer to revert back to gingerbread. If you have the US 16gb version then you cannot go back to gingerbread because there isn't a ruu yet.
Hopefully I'm not confusing you more
Click to expand...
Click to collapse
No not really confused by your explanation. What confuses me if is the process was suppose to give me S-OFF in the first place. I understand the logic of the new hboot being S-ON. But if you're following me you kinda see where I'm thinking 0_o lol.
piramida13 said:
Revolutionary does support the HC bootloader version 1.11.0006.
but only after unlock bootloader , go htc dev.com and unlock bootloader from step by step guaid....after you see in fastboot
"""""""unlocked""""""""
FLYER PVT SHIP S-ON
copy revolutionary-cwm-4.0.1.4-flyer.newhboot.img in to dir (you create dir ,by htc dev guaid)
and run command in cmd
fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img'
Click to expand...
Click to collapse
So I'm not suppose to have S-OFF after running that command?
I think that's what he is saying. My bootloader was a totally different one. So I don't really have any knowledge. What I would do is go into the development forum and do a quick search and see if anyone answered the question or had a similar problem and fixed. It helps out a lot. I don't want to give you knowledge and mess anything up on your end.
ATownI20 said:
No not really confused by your explanation. What confuses me if is the process was suppose to give me S-OFF in the first place. I understand the logic of the new hboot being S-ON. But if you're following me you kinda see where I'm thinking 0_o lol.
Click to expand...
Click to collapse
haha the process of going to honeycomb was not supposed to give you s-off, simply an unlocked bootloader. I think i'm following you
My understanding of the situation is the hboot that is required to install HC sets s-on, and currently it is not possible to change it back to s-off without reverting back to the original hboot using the RUU. Even if you changed back to the original hboot, honeycomb would no longer boot.
At least, that's my understanding.
The only way right now to get S-OFF is with HBOOT versions 1.11.0000 and 1.11.0003. Since you have 1.11.0006, needed for running HC on the Flyer, Revolutionary doesn't support it, so right now you can only have the unlocked boot loader and S-ON. If you run the Revolutionary tool with HBOOT 1.11.0006, it will tell you it is not supported, and won't run.
The only way it would be supported is when the AlphaRev/Unrevoked team update their tool to support it. So running that command listed above does cause this, but it is required in order to run HC on the Flyer. Without it, I don't know if you'd have a $300 brick or what.
Parastie said:
My understanding of the situation is the hboot that is required to install HC sets s-on, and currently it is not possible to change it back to s-off without reverting back to the original hboot using the RUU. Even if you changed back to the original hboot, honeycomb would no longer boot.
At least, that's my understanding.
Click to expand...
Click to collapse
Thanks chief... I was just a little confused as the guides talked about permanent S-OFF... But if S-ON is how I'm suppose to be right now, then S-ON it is! lol...
I am in the same boat
Just Upgraded and noticed S-on as well...
what am I limited to with S-ON.. and whats the *UNLOCKED* mean?
*UNLOCKED*
FLYER PVT SHIP S_ON RL
HBOOT 1.11.006
MICROP 0850
Radio-3821.08.00.26
eMM-BOOT
*UNLOCKED*
FLYER PVT SHIP S_ON RL
HBOOT 1.11.006
MICROP 0850
Radio-3821.08.00.26
eMM-BOOT
I have exactly the same issue.
is there anyway out of S-ON?
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 was trying to root my CDMA EVO 3d earlier and failed. It kept sticking on the sprint loading screen no matter what rom I flashed to it. I unlocked the bootloader through HTCDev. I then loaded the teamwin recovery and tried to flash a rom through that. I'm guessing I missed a few steps (first time messing with a droid) and locked it up. Now I got it relocked and tried to load the:
RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445_signed.zip
but it was the wrong version appearently and I'm out of ideas as I've been working on this all day long. I just want to be able to use my phone again but if I could obtain a full root in the process that would be nice! I hope someone here can help because you guys are my last hope! I've done lots of reading and searching but nothing that has really explained my situation. Thanks in advance for any help!
Specs:
RELOCKED
shooter xc ship s-on rl
hboot 1.58.0000
radio 1.09.00.0706
OpenADSP v02.6.0.226.00.0217
eMMc-boot
Did you try the 2.17 one?
Save the Drama for your Mama with Tapatalk 2
Yes I did try that one along with the newt rom, mikrom and a few others to no avail. :crying: I'm at a loss, I loaded the teamwin recovery back on, every time I flash a rom it gets stuck on the loading screen and never fully boots.
I just read that apparently, none of the old ruu work in the new hboot if s-on. I recommend you get s-off.
Edit: Not sure if that'strue as I've heard conflicting information.
Save the Drama for your Mama with Tapatalk 2
Okay I'll try that next, thanks for the input!
I tried getting s-off by the Live CD method, booted it from a flash drive, locked it back up and when I went to brick it, it said the ruu was the wrong version. I used the version listed in the guide so I'm not too sure which version I need.
So I was told there is nothing that supports hboot 1.58? Is this correct? Can anyone confirm this? Guess I just have to wait for someone to put something together that supports it?
Fixed thanks to this thread: http://forum.xda-developers.com/showthread.php?t=1813818&highlight=hboot+1+58
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]
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