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
Related
I was having a problem with my screen being unresponsive so i needed to take it into a sprint store. i ran a signed 2.17 exe and now I have hboot 1.5 but still have s-off. in the bootloader screen it says locked but still shows s-off. i am confused as to what to do next. i assume i need to unlock but didn't know if i could do this via revolutionary. I tried to do a search but everything i found was related to s-on. I am trying to restore my phone to its rooted state since I have already had the repairs made. Any help and links would be greatly appreciated.
Brandon
Sent from my iPad using Tapatalk HD
brandonb8 said:
I was having a problem with my screen being unresponsive so i needed to take it into a sprint store. i ran a signed 2.17 exe and now I have hboot 1.5 but still have s-off. in the bootloader screen it says locked but still shows s-off. i am confused as to what to do next. i assume i need to unlock but didn't know if i could do this via revolutionary. I tried to do a search but everything i found was related to s-on. Any help and links would be greatly appreciated.
Brandon
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
fastboot oem writesecureflag3 or fastboot oem writesecureflag 3 , one of those will turn s-on
Edit... This might help http://forum.xda-developers.com/showthread.php?t=1578977
Thanks for the quick response. Sorry I was not more clear about what I am wanting to do. I am keeping the phone and the repairs have been made. I now have hboot 1.50 with s-off. I am wanting to flash a custom rom again and need to install a recovery. I didn't know what the process is currently for "unlocking" my phone now. When I rooted the phone originally, i was on hboot 1.4 and used revolutionary. I just do not know what to do to get my phone rooted again. I understand I have part of it with s-off still being on my phone, but the "locked" text at the top of the bootloader screen tells me I need to rectify this before I can flash a recovery. Is this correct?
Thanks.
Brandon
brandonb8 said:
Thanks for the quick response. Sorry I was not more clear about what I am wanting to do. I am keeping the phone and the repairs have been made. I now have hboot 1.50 with s-off. I am wanting to flash a custom rom again and need to install a recovery. I didn't know what the process is currently for "unlocking" my phone now. When I rooted the phone originally, i was on hboot 1.4 and used revolutionary. I just do not know what to do to get my phone rooted again. I understand I have part of it with s-off still being on my phone, but the "locked" text at the top of the bootloader screen tells me I need to rectify this before I can flash a recovery. Is this correct?
Thanks.
Brandon
Click to expand...
Click to collapse
Oh I see, well, your s-off and that locked banner means nothing because s-off should override it. Just flash a PG86IMG.zip of a recovery of your choice and you're good to go. Or you can flash it via fastboot by typing fastboot flash recovery "yourrecovery.img" once you do that, flash a rooted Rom. You could flash a lower hboot with a PG86IMG.zip if you want but its not really necessary.
If you want, I could dig up hboot 1.4 or revs hboot for ya. I think I have em in dropbox.
I got it. Thanks for all the help.
Sent from my PG86100 using Tapatalk 2
read this: the purpose of this post is to let folks know that if you htcdev unlock with s-off,your device will go back to reading unlocked until you relock it,at wich time it will read relocked,just like before you s-offed.
what does this mean?! if you dont care about getting back to a locked state for warranty purposes,then it doesnt mean anything. if one of the big reasons that you s-offed in the first place was to get back to locked,then,as the title says,dont unlock with htcdev after s-off. you can install recoveries and hboots via hboot in a PH98IMG files,or you can install available patched hboots to enable engineering commands.
i hope this helps clarify it for those who were confused by the title. my intention was not to cause panic,simply to educate folks in what id found,as i know the subject of locked/relocked is very important to some.
_______________________________________________________________________________________
ok,i have been posting in several threads that the unlocking after s-off is no big deal. i still maintain that.
however...
on my other s-off,htcdev devices,reflashing the hboot/running an RUU makes the device locked again. after more discussion with con,i decided i better test if i was gonna keep saying it.
i stand corrected!
i started by flashing back the 2.11.000 hboot and unlocking it. i flashed it again. still unlocked.. hmmm. so i flashed jp patched hboot,now juopunutbear flashed 2.11 back. still unlocked. hmmm.
so i relocked. reflashed 2.11. still relocked. uh oh. flashed the eng hboot. now relocked eng 2.11.20005,lol... relocked engineering hboot. flashed the 2.05.0000 ship hboot. still relocked.
at this point i ran the entire RUU for 2.01.605.11. still relocked
i plan to try flashing the leak ruu,then 2.01.605.11 again,but for now,im tired. 6am comes very shortly.
i should have known this phone would somehow be different
moral of the story is that if you are one of the folks whom care about your hboot saying locked,dont unlock it
sorry for any misconceptions based on my experiences with other devices
scotty1223 said:
ok,i have been seen posting in several threads that the unlocking after s-off is no big deal. i still maintain that.
however...
on my other s-off,htcdev devices,reflashing the hboot/running an RUU makes the device locked again. after more discussion with con,i decided i better test if i was gonna keep saying it.
i stand corrected!
i started by flashing back the 2.11.000 hboot and unlocking it. i flashed it again. still unlocked.. hmmm. so i flashed jp patched hboot,now juopunutbear flashed 2.11 back. still unlocked. hmmm.
so i relocked. reflashed 2.11. still relocked. uh oh. flashed the eng hboot. now unlocked eng 2.11.20005,lol... unlocked engineering hboot. flashed the 2.05.0000 ship hboot. still relocked.
at this point i ran the entire RUU for 2.01.605.11. still relocked
i plan to try flashing the leak ruu,then 2.01.605.11 again,but for now,im tired. 6am comes very shortly.
i should have known this phone would somehow be different
moral of the story is that if you are one of the folks whom care about your hboot saying locked,dont unlock it
sorry for any misconceptions based on my experiences with other devices
Click to expand...
Click to collapse
I am betting you can s-on the phone then re s-off and have it say locked. Or someone could edit an hboot to just say locked.
Sent from my ADR6425LVW using XDA
nosympathy said:
I am betting you can s-on the phone then re s-off and have it say locked. Or someone could edit an hboot to just say locked.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
im sure it can be edited,im sure thats how we became locked again after s-off. and yeah im certain re-s-off-ing would do it too
i dont personally care,my device has no mfg warranty and its kinda neat to me that it appears to stay unlocked thru up/downgrades,and if i want to run the eng or patched hboots,i still can.
i just wanted to prevent others who do care from becoming entrapped back in the situation because of other advice i may have given. should have tested first,spoke later
When I did my S-OFF I was on 2.11 hboot and the ICS firmware. I flashed the juonoptioeefianwefo hboot and then the ENG hboot and old firmware patch. My end result was it saying "locked" in hboot.
I was rather pissed off since I the reason I flashed the ENG hboot was so that it would say "unlocked" instead of juonoptionaofewhf.
My warranty is voided several times over in other ways* so it doesn't matter much to me and after the huge amount of time getting the darn wire trick to work I was rather proud to have my phone say S-OFF and "unlocked".
*apparently living in a high humidity area is enough to trigger the wetness seals.
jefffeely said:
When I did my S-OFF I was on 2.11 hboot and the ICS firmware. I flashed the juonoptioeefianwefo hboot and then the ENG hboot and old firmware patch. My end result was it saying "locked" in hboot.
I was rather pissed off since I the reason I flashed the ENG hboot was so that it would say "unlocked" instead of juonoptionaofewhf.
My warranty is voided several times over in other ways* so it doesn't matter much to me and after the huge amount of time getting the darn wire trick to work I was rather proud to have my phone say S-OFF and "unlocked".
*apparently living in a high humidity area is enough to trigger the wetness seals.
Click to expand...
Click to collapse
Yeah high humidity trips em lol. I had an iPhone 3G back in the day trip both the headphone Jack and charging port water markers on a 70% humidity day.
Sent from my ADR6425LVW using XDA
The number of things that can happen to invalidate your warranty really is annoying. My cousin has a completely stock Inspire that is stuck on hboot but AT&T won't touch it because it has a small ding in the case from when she dropped it.
After S-OFF (GB stock, amon ra, rooted system), I erroneously thought I needed to unlock. Then I locked the bootloader for any future OTA update and it showed Relocked.
I reinstalled the ENG hboot, but it still shows Relocked.
I asked in the sbear chat room, and the answer was
there is no simple way to get the ENG hboot to change from displaying Relocked to display just plain Locked.
But...It is just cosmetic and doesn't really matter.
Howard
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
I don't know what any of this means...
I just think this makes it more confusing for people..
Mine said 'Locked' after S-Off so I just unlocked it and everything seemed better..
Irieone said:
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
Click to expand...
Click to collapse
That is because you kept the stock hboot which doesn't allow for fastboot commands without being unlocked. By choosing one of Jp's hboot's or the eng hboot you could have installed recovery without unlocking. I did the same thing. So I went back to s-on and redid the s-off procedure and installed jb's hboot. Now I am s-off and locked again. Whew!
Sent from my ADR6425LVW using Tapatalk 2
Irieone said:
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
Click to expand...
Click to collapse
I second this. I had to unlock before I could flash recovery. I don't care that my phone says unlocked, just wanted to point out that for one reason or another some have had to unlock again.
Good usage of Smileys.
I agree with scotty, my hboot says locked and I have s-off so far I have flashed everything except for ruu's. Even recoveries worked.
Sent from my ADR6425LVW using xda premium
I was on the latest firmware and RezROM ICS. Performed S-OFF and never seen an option to install JB-Hboot so I didnt. At that time mine said UNLOCKED/TAMPERED.
Then after a couple of days of reading and trying to decide what to do next I decided to RUU down to the latest official and as soon as that was finished I went back to boot loader and it said LOCKED / S-OFF. I flashed the ENG Hboot with no issues and Now it says LOCKED / VIGOR PVT ENG S-OFF RL.
I also made a backup of RezROM before all this. Restored my backup, flashed the firmware patch, flashed PH that came with RezROM and rebooted and have had no issues at all.
I am not in a 4G area so I might actually have the issue others were having with 4G dropping out. Will have to wait and see.
zone23 said:
I don't know what any of this means...
I just think this makes it more confusing for people..
Mine said 'Locked' after S-Off so I just unlocked it and everything seemed better..
Click to expand...
Click to collapse
Ditto
I was/am on the stock GB firmware, completed S-OFF, phone said locked (still on stock GB HBOOT), I unlocked it ... no problems since.
HowardZ said:
After S-OFF (GB stock, amon ra, rooted system), I erroneously thought I needed to unlock. Then I locked the bootloader for any future OTA update and it showed Relocked.
I reinstalled the ENG hboot, but it still shows Relocked.
I asked in the sbear chat room, and the answer was
there is no simple way to get the ENG hboot to change from displaying Relocked to display just plain Locked.
But...It is just cosmetic and doesn't really matter.
Howard
Click to expand...
Click to collapse
I saw you sign on. Did they ever answer my question about running the tool multiple times?
Sent from my ADR6425LVW using XDA
Irieone said:
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
Click to expand...
Click to collapse
No,I won't change the title. To some folks its important to stay locked. I will try and clarify the op later today.
You don't need to unlock to install a recovery. It's easily permanently flashed via a PH98IMG,or fastboot booted via the jpbear patched hboots.
Sent from my ADR6425LVW using XDA
dmoses1969 said:
I was on the latest firmware and RezROM ICS. Performed S-OFF and never seen an option to install JB-Hboot so I didnt. At that time mine said UNLOCKED/TAMPERED.
Then after a couple of days of reading and trying to decide what to do next I decided to RUU down to the latest official and as soon as that was finished I went back to boot loader and it said LOCKED / S-OFF. I flashed the ENG Hboot with no issues and Now it says LOCKED / VIGOR PVT ENG S-OFF RL.
I also made a backup of RezROM before all this. Restored my backup, flashed the firmware patch, flashed PH that came with RezROM and rebooted and have had no issues at all.
I am not in a 4G area so I might actually have the issue others were having with 4G dropping out. Will have to wait and see.
Click to expand...
Click to collapse
I'm in the same situation. There's a thread here on how to fix it but I guarantee your 4G is whacked. I flashed back to a GB stock ROM then flashed an ICS ROM. Seemed to work okay when in my 3G only area but I visited a 4G area yesterday and it was just messed up. I flashed the latest GB RUU and did a reset from the stock hboot, flashed JuopunutBear hboot for GB, then AmonRa 3.15 and CleanROM DE. I'm going back to a 4G area tomorrow so if it doesn't work I'll post in that thread. Could just be me but everything about the phone seems better/cooler/faster after the RUU.
TheEnzyteGuy said:
I agree with scotty, my hboot says locked and I have s-off so far I have flashed everything except for ruu's. Even recoveries worked.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I've flashed JuopunutBear hboot (GB and ICS), eng hboot, stock hboot, AmonRa, a nandroid, and a few roms after locked/s-off and have had no problem. Just flash eng or juopunutbear hboot before flashing recovery and you're good to go.
Edit: I was on the appropriate firmware when flashing the GB and ICS hboots.
Recovery can still be flashed as a PH file on the regular HBOOT.
D
HTC having last laugh?
Sent from my ADR6425LVW using xda premium
Hi there, I know its sounds repeating problems but I seriously need help...
I'm new to android.
I got a GSM EVO 3D with arabic ruu installed months ago, and of course, already updated to ics few weeks ago.
I tried root my EVO 3D from this newbie guide {Complete Newbie's Guide to rooting and flashing Evo 3D ROMs/Kernels using fastboot} from androidforum and things turn well, but then I wanted to tried out virtuous eclipse rom, but I forgot to s-off the device, maybe thats the MAIN CAUSE.
And so, after flashing the virtuous eclipse, it just won't started, keep hanging on the V splash screen and reboot over and over again.
I did two serious mistakes due to my stupidity
1: I didn't backup my original rom
2: I didn's s-off before flashin a custom rom
I tried to boot into recovery (revolutionary), and perform a full wipe, EVERYTHING, SYSTEM and data.
Now my problem is, I have an =empty= evo 3d without any system files in it, and I tried to install back stock rom, searchin and tourin xda and some other websites, i do get a lot of downloadable contents and methods.
But it didnt work, which means I put the zip files(gsm arabic shipped gingerbread stock rom extracted from ruu), which renamed as PG86IMG.zip onto the root of sd card, but the bootloader failed scan the zip.
Tried to install it from recovery, but shows bad file.
I even tried the boot boot.img method which some nice guy posting here, but it won't works for me.:crying:
And even tried to relocked the phone and installed from ruu exe via usb, but it stops halfway and shows error update.
my current stat
***UNLOCKED***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
May 22 2012, 01:06:07
Is there any other way to fix this?or am I doing it wrong? like using wrong ruu or outdated recovery?:crying:
Please help me, I just want to get my htc works again.:crying:
Thanks In Advance.
You said you locked the bootloader but it is showing unlocked. Maybe that is why running the ruu by USB failed.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
You said you locked the bootloader but it is showing unlocked. Maybe that is why running the ruu by USB failed.
Save the Drama for your Mama with Tapatalk 2
Click to expand...
Click to collapse
hi there, yes im relocked before and running the ruu but failed, so now i unlocked it back.:crying:
I cant figure out what to do, is it im using wrong method? or am I missing many things?
I'm surprised the ruu didn't work. Is it the latest? It must be the one with hboot 1.57 (or later).
Save the Drama for your Mama with Tapatalk 2
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 hate to post a new thread on this, but I need help and quick (also, I literally have read through about 20 different threads and have tried numerous solutions)...
CDMA HTC EVO 3d
I originally was on Hboot 1.4, rooted using Revolutionary, updated to ENG Hboot and unlocked bootloader.
1. I flashed a stock ROOTED rom for 1.13.651.7
2. Switched backed to Ship Hboot 1.40 ( I saw that was required before relocking bootloader) [Something went wrong here I guess; although it appeared to work but got stuck at HTC white screen afterwards]
3. Ran RUU for 1.13.651.7 for Hboot 1.40 - appeared to work but still stuck
4. Relocked bootloader: Read somewhere I had to relock bootloader to run RUU properly
5. Ran RUU for 1.13.651.7 for Hboot 1.40 again - again it went through the whole process and said success but still stuck on htc white screen after reboot
6. Flashed thru bootloader 2.17.xxx.5 Hboot 1.5: Felt like I was out of options and saw a post to update to 2.17.xxx.5 Hboot 1.5
7. After doing #6, I ran the RUU for 2.17.xxx.5 Hboot 1.5 - ran successfully and after reboot still stuck at htc white screen then bootloops
Here is what phone currently shows:
***LOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
RADIO-1.06.00.1216
eMMC-boot
Aug 7 2011, 10:21:40
I need to turn this phone back in to work - I am at a loss - any help is appreciated! To top it off, my battery won't charge and I have to keep asking a friend at work with same phone to switch batteries and charge it for me.
Maybe try running the latest ICS ruu exe.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Since it doesn't say RElocked on the bootloader is there anyway to tell that I messed with it?
I don't think so. I would try running the latest ICS ruu exe just to see if it fixes things. If not, just play dumb when you turn it in.
Read, Search, Read again, ... Then Ask with Tapatalk 2
I guess I can give it a go...is this the latest:
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
Yes. Connect your phone to your computer and boot into bootloader. It should say fastboot USB. Run the ruu and hopefully you'll be set.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Run over it with your car and tell them it fell off your lap while getting gas.....
sudo passwd root
Odd...newest RUU won't run - it says USB connection error, although I have ran the older RUU's without issue. I am going to run the one prior to ICS again and if it doesn't work turning it in as is. I will just say did factory reset and after that it no longer will boot... Thx for your help
No luck - I'm done...very surprised the RUU's even after successfully updating and running didn't resolve the issue - I have never seen something like this before. Oh well, hopefully it doesn't happen to anyone else. I switched to the S3 so I won't be visiting the Evo 3d forums anymore.