So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
Yes, it worths at least for myself. I have hboot 1.50 too and i rooted fast with no problems.
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
More than likely, yes. Most users who follow the guides don't seem to have issues.
The HTC unlock method changes the dynamics a bit from previous common and accepted methods. Many "new" users become between old and current guides.
As far as I've seen, there are only three limitations to hboot 1.5, compared with early "compromised" versions using the AlphaRevX revolutionary method.
1) Kernel is not able to be flashed from recovery mode. Work arounds include: flashing from normal Android mode, my app is great for that, Flash Image GUI. Loading the custom recovery from fastboot. Flashing the kernel from fastboot. Using the "dumlock" method with TWRP.
2) Unable to selectively flash radio images
3) Unable to selectively flash intial splash screens
If I'm missing anything, I'm sure somebody else can post up.
None of those seem like deal breakers to me. Thanks for the fast replies.
It's kind of a ***** just because you have to do a few extra steps but if you know what your doing you won't screw it up.
Yarr. I think I'm going to keep stock for probably just a bit longer. Maybe 1.5 S-Off wont be a problem then. Not bored of it yet, and coming from HTC Hero the thing is a dream.
Root is the way to go Get rid of bloat Also adb isn't hard I always fastboot boot recovery.img and wipe flash no issues
Should I start a new thread on this? I tried to root my HBoot1.5 with 2.17.651.5. When I have went through the HTC unlock process it stays locked. I tried to install the 2.08 version through the original RUU, but it keeps failing. Not sure where I should go from there.
ls3mach said:
Should I start a new thread on this? I tried to root my HBoot1.5 with 2.17.651.5. When I have went through the HTC unlock process it stays locked. I tried to install the 2.08 version through the original RUU, but it keeps failing. Not sure where I should go from there.
Click to expand...
Click to collapse
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
xcpefrmreality said:
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
Click to expand...
Click to collapse
That is what he needs to do to fix .
Sent from my PG86100 using xda premium
DjNawo said:
Yarr. I think I'm going to keep stock for probably just a bit longer. Maybe 1.5 S-Off wont be a problem then. Not bored of it yet, and coming from HTC Hero the thing is a dream.
Click to expand...
Click to collapse
You have Hboot 1.5 with S-off?
G.Newton said:
You have Hboot 1.5 with S-off?
Click to expand...
Click to collapse
No he doesn't from what he said he is stock and asking if he should root
xcpefrmreality said:
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
Click to expand...
Click to collapse
Much obliged!
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
I think some people just got ahead of themselves flashing wrong files. I got a bit worried too first go round after coming from a.Transform.
In my signature I've got a guide/flashing notes that are a bit more updated than some of the stickied threads that may help clear some things up.
Sent from my PG86100 using Tapatalk
What root did you use
Sent from my EVO 3D using XDA Premium
[/COLOR]
Yoyodude1124 said:
What root did you use
Click to expand...
Click to collapse
I used the HTC Unlock (zedomax's video), CWM Recovery, Su 3.07 zip, BusyBox (market), all layed out here:
[Guide] My Hboot 1.50 HTC Unlock/recovery/rom/kernel flashing notes http://forum.xda-developers.com/show....php?t=1495358
Hey thanks again. Yeah I have the newest update, so i would need to get the 2.17 that xcp mentioned. Also, thanks for the guide above.
Related
Hey everyone, I am unable to unlock my bootloader after accepting this OTA. I just got an EVO 3D yesterday and I updated it as soon as I got it. I first checked to see if it was an HBOOT below 1.5, it wasn't so I went ahead and updated. However when i get to step 12 i believe on the htc dev site, I flash the unlock_code.bin and nothing happens just sits there. I read around and found people saying you need to take the 2.08 RUU, I tried that and when it gets to the black HTC screen I get an error 140. I was so excited to get this phone and already downloaded the rom i wanted before owning it. If someone can please help me out I would appreciate it. Thanks
No one? Dam..
Sent from my PG86100 using XDA App
majid25 said:
No one? Dam..
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Did you try factory reset or battery pull then give it another go? Also did you follow all the steps anyways give her another go.
frustrated
majid25 said:
Hey everyone, I am unable to unlock my bootloader after accepting this OTA. I just got an EVO 3D yesterday and I updated it as soon as I got it. I first checked to see if it was an HBOOT below 1.5, it wasn't so I went ahead and updated. However when i get to step 12 i believe on the htc dev site, I flash the unlock_code.bin and nothing happens just sits there. I read around and found people saying you need to take the 2.08 RUU, I tried that and when it gets to the black HTC screen I get an error 140. I was so excited to get this phone and already downloaded the rom i wanted before owning it. If someone can please help me out I would appreciate it. Thanks
Click to expand...
Click to collapse
Same here.
The same RUU I used to revert to the .2sw update to unlock two other evo3d's with hboot 1.5, will not work. Im unbelievably frustrated right now as Ive been sitting at this computer for over three hours. Please, if you find a way to downgrade your software, please let me know. thanks
not sure why you wanted to be on hboot 1.50. but shouldnt be a problem to unlock the bootloader, since it was just minor updates and still on hboot 1.50. id just try doing the process again.
i unlocked mine with unlock_code.bin that i used when i rooted my evo 3d for 1st time.....it worked fine.
Tried 5 times and failed..
Sent from my PG86100 using XDA App
evoRomz said:
not sure why you wanted to be on hboot 1.50. but shouldnt be a problem to unlock the bootloader, since it was just minor updates and still on hboot 1.50. id just try doing the process again.
Click to expand...
Click to collapse
I didn't want to be on hboot 1.5, I wanted to be below it. But when I first got my phone I checked the bootloader and was already at 1.5. If it was below that I would've been rooted right now...
to be a bit more clear it was hboot 1.5 with an OTA 2.08 when I first received the phone.
Sent from my PG86100 using XDA App
majid25 said:
I didn't want to be on hboot 1.5, I wanted to be below it. But when I first got my phone I checked the bootloader and was already at 1.5. If it was below that I would've been rooted right now...
to be a bit more clear it was hboot 1.5 with an OTA 2.08 when I first received the phone.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
1st Check you bootloader .What it says at the top .(locked/unlocked/relocked) if it says unlocked you do not need unlock_code.bin.
Try these from step 13:
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/
You can flash another recovery in step 18 .....
mnomaanw said:
1st Check you bootloader .What it says at the
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/
Click to expand...
Click to collapse
That's the guide I used to HTC Unlock. Video helped. There is a post somewhere about needing to Re-flash the stock RUU.exe or Ruu.zip (renamed to PG86IMG.zip) to get the phone past the "nothing happens" step where you're supposed to get the "unlock" option screen on the phone. I haven't seen the 651.5 released as a complete RUU, but you could probably flash the 651.3 RUU, finish the HTC unlock and then run the 651.5 update. Heck, the unlock would probably work after the update, idk for sure.
I have some links and my issue with this below.
SOLVED-Stock Hboot1.50 HTC Unlock/ RUU 651.3 flash problems (1-14-12) http://forum.sdx-developers.com/?topic=18852.0
Evo3d Useful Links(md5's): http://forum.sdx-developers.com/?topic=18827.0
Edit: Here's where I saw the info about flashing the RUU to get a good unlock:
(XDA) JTniggle's [GUIDE] HTC Unlock Hboot 1.50 + TWRP Recovery + Root + Flash!! [9.11.11] (All via ADB)
http://forum.xda-developers.com/showthread.php?t=1239821
Says locked.
mpgrimm2 said:
That's the guide I used to HTC Unlock. Video helped. There is a post somewhere about needing to Re-flash the stock RUU.exe or Ruu.zip (renamed to PG86IMG.zip) to get the phone past the "nothing happens" step where you're supposed to get the "unlock" option screen on the phone. I haven't seen the 651.5 released as a complete RUU, but you could probably flash the 651.3 RUU, finish the HTC unlock and then run the 651.5 update. Heck, the unlock would probably work after the update, idk for sure.
I have some links and my issue with this below.
SOLVED-Stock Hboot1.50 HTC Unlock/ RUU 651.3 flash problems (1-14-12) http://forum.sdx-developers.com/?topic=18852.0
Evo3d Useful Links(md5's): http://forum.sdx-developers.com/?topic=18827.0
Edit: Here's where I saw the info about flashing the RUU to get a good unlock:
(XDA) JTniggle's [GUIDE] HTC Unlock Hboot 1.50 + TWRP Recovery + Root + Flash!! [9.11.11] (All via ADB)
http://forum.xda-developers.com/showthread.php?t=1239821
Click to expand...
Click to collapse
Thank your for all the help. However I tried doing what is said in these links, I ran the 2.08.651.3 RUU and at the black HTC screen I get the error 140. Can I downgrade OTA's or no? Cuz that what it looks like I have to do here.
majid25 said:
Thank your for all the help. However I tried doing what is said in these links, I ran the 2.08.651.3 RUU and at the black HTC screen I get the error 140. Can I downgrade OTA's or no? Cuz that what it looks like I have to do here.
Click to expand...
Click to collapse
I could before the .5 update. Had to get a new phone last night and it will not downgrade to the .2 software so I can then unlock. Frustrating to say the least. Actually, I'm pissed about it.
Sent from my Google Nexus S 4G via XDA Premium
How did you get a new phone, through Sprint? And yea this sucks, hope there is a solution soon I've been posting everywhere like an idiot haha
majid25 said:
How did you get a new phone, through Sprint? And yea this sucks, hope there is a solution soon I've been posting everywhere like an idiot haha
Click to expand...
Click to collapse
Yeah, returned it. Dead pixel. Now I'm stuck with this bs bloat on here cause I can't downgrade and unlock.
Sent from my Google Nexus S 4G via XDA Premium
Edit: I cant even get a damn temp root! Stuff is pissing me off. Bout to go iphone so I dont have to nerd it up and waste my damn time, which isnt even that valuable.
I say you try to just wait it out a bit. Give it a week...but don't go iPhone!!!
majid25 said:
I say you try to just wait it out a bit. Give it a week...but don't go iPhone!!!
Click to expand...
Click to collapse
At the rate devs are dropping off, a week is an eternity. And I'm new to the evo3d. Sad face.
Sent from my Google Nexus S 4G via XDA Premium
tailsthecat3 said:
Yeah, returned it. Dead pixel. Now I'm stuck with this bs bloat on here cause I can't downgrade and unlock.
Sent from my Google Nexus S 4G via XDA Premium
Edit: I cant even get a damn temp root! Stuff is pissing me off. Bout to go iphone so I dont have to nerd it up and waste my damn time, which isnt even that valuable.
Click to expand...
Click to collapse
What method did you try for temp root?
Crackanug said:
What method did you try for temp root?
Click to expand...
Click to collapse
Frevo.
Sent from my Google Nexus S 4G via XDA Premium
tailsthecat3 said:
Frevo.
Sent from my Google Nexus S 4G via XDA Premium
Click to expand...
Click to collapse
I have some tools and files for you to use that will give you temp root and allow a downgrade to 2.08.651.2 rom, hboot will still be 1.50 though. However from there you should be able to unlock via HTCdev method. I gotta upload the files and write the code which I will post up here in a second. I hope you are ok with using adb and fastboot.
Hi I need help going back to completely stock and my hboot is 1.50 any help or direction thanks!!
Kratz17 said:
Hi I need help going back to completely stock and my hboot is 1.50 any help or direction thanks!!
Click to expand...
Click to collapse
In the general section look into the sticky there is a guide for you there to go to stock relock . Here ya go http://forum.xda-developers.com/showthread.php?t=1388501
Weeping with frustration
reaper24 said:
In the general section look into the sticky there is a guide for you there to go to stock relock . Here ya go http://forum.xda-developers.com/showthread.php?t=1388501
Click to expand...
Click to collapse
Why the **** will this image you linked NOT flash my phone?! It loads, checks then just dumps me at the hboot screen! Ive got hboot 1.5(obviously) and the latest software 2.17.651.5. Even the .2 RUU exe will NOT work, continuously gives me hboot version error. I believe its error 140. I NEED to unlock this thing...or get pissed and hit it with a hammer.
reaper24 said:
In the general section look into the sticky there is a guide for you there to go to stock relock . Here ya go http://forum.xda-developers.com/showthread.php?t=1388501
Click to expand...
Click to collapse
Thanks a lot I'll try when I get home tonight.
Sent From My RED 3Dimension
tailsthecat3 said:
Why the **** will this image you linked NOT flash my phone?! It loads, checks then just dumps me at the hboot screen! Ive got hboot 1.5(obviously) and the latest software 2.17.651.5. Even the .2 RUU exe will NOT work, continuously gives me hboot version error. I believe its error 140. I NEED to unlock this thing...or get pissed and hit it with a hammer.
Click to expand...
Click to collapse
If you hit it with a hammer it will be broken for good lol. Did you try to re root with HTC dev way? The link was for this guy to relock his phone .
reaper24 said:
If you hit it with a hammer it will be broken for good lol. Did you try to re root with HTC dev way? The link was for this guy to relock his phone .
Click to expand...
Click to collapse
HTC unlock method will not work. I flash the token and it just sits there...Im trying to revert to .2 so I can actually unlock, like I have with two other 3d's but the friggin RUU exe tells me bootloader version error which is 140, I believe. I should know, I saw it 356 times last night.
tailsthecat3 said:
HTC unlock method will not work. I flash the token and it just sits there...Im trying to revert to .2 so I can actually unlock, like I have with two other 3d's but the friggin RUU exe tells me bootloader version error which is 140, I believe. I should know, I saw it 356 times last night.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1337379. Read this might help you. Hope it works for you. Sounds like the issue a few folks were having.
Weeping with frustration
reaper24 said:
http://forum.xda-developers.com/showthread.php?t=1337379. Read this might help you. Hope it works for you. Sounds like the issue a few folks were having.
Click to expand...
Click to collapse
Tried that a million times last night. And just now, just because.
I took a video of the process because I couldnt read what the RUU was saying. After updating signature, very quickly it says Checking Header...then it says checking MID/CID and then I get the screen that is attached! [Expletive deleted!]
tailsthecat3 said:
Tried that a million times last night. And just now, just because.
I took a video of the process because I couldnt read what the RUU was saying. After updating signature, very quickly it says Checking Header...then it says checking MID/CID and then I get the screen that is attached! [Expletive deleted!]
Click to expand...
Click to collapse
Have you tried it with adb ? What program are you using ? Though u could flash it in hboot . After using adb to relock it.
reaper24 said:
Have you tried it with adb ? What program are you using ? Though u could flash it in hboot . After using adb to relock it.
Click to expand...
Click to collapse
It is locked. Its new. That screen comes from the .2 RUU exe.
I havent tried anything with adb. I havent used adb since the Evo4g. Have a link?
I have tried running the RUU with windows, I have tried PG86IMG.zip's, Ive tried RUU's while already being in fastboot. When I try using PG86IMG's through hboot, it loads the file, checks the file then dumps me back at the Hboot screen.
tailsthecat3 said:
It is locked. Its new. That screen comes from the .2 RUU exe.
I havent tried anything with adb. I havent used adb since the Evo4g. Have a link?
I have tried running the RUU with windows, I have tried PG86IMG.zip's, Ive tried RUU's while already being in fastboot. When I try using PG86IMG's through hboot, it loads the file, checks the file then dumps me back at the Hboot screen.
Click to expand...
Click to collapse
Adb is what most folks use to do all there stuff. You have to have adb installed to do the HTC devs route from what I have read. So the phone is locked and your tryin to root it. But are gettin errors ?
So your phone now is hboot 1.5 and is currently up to date and your tryin to root it HTC dev route but get errors?
Got the pistol in my hand, thumb on the hammer.
reaper24 said:
Adb is what most folks use to do all there stuff. You have to have adb installed to do the HTC devs route from what I have read. So the phone is locked and your tryin to root it. But are gettin errors ?
So your phone now is hboot 1.5 and is currently up to date and your tryin to root it HTC dev route but get errors?
Click to expand...
Click to collapse
Yeah exactly. But posted on xda, you cant htc dev it with any software other than 2.08.651.2, which for some bizarre ass reason, I cant downgrade to!
I tweeted the other day "when the **** did adb move?!". so thats how long ago I used it. Im familiar with it, I used to delete all my bloat with adb, which was a painstaking process.
tailsthecat3 said:
Yeah exactly. But posted on xda, you cant htc dev it with any software other than 2.08.651.2, which for some bizarre ass reason, I cant downgrade to!
I tweeted the other day "when the **** did adb move?!". so thats how long ago I used it. Im familiar with it, I used to delete all my bloat with adb, which was a painstaking process.
Click to expand...
Click to collapse
That sucks I am on the newer software was gonna root soon . I'm sure HTC will have a update on the dev to allow root.
tailsthecat3 said:
Yeah exactly. But posted on xda, you cant htc dev it with any software other than 2.08.651.2, which for some bizarre ass reason, I cant downgrade to!
I tweeted the other day "when the **** did adb move?!". so thats how long ago I used it. Im familiar with it, I used to delete all my bloat with adb, which was a painstaking process.
Click to expand...
Click to collapse
This looks similar:
http://forum.xda-developers.com/showthread.php?t=1447839&page=5
reaper24 said:
That sucks I am on the newer software was gonna root soon . I'm sure HTC will have a update on the dev to allow root.
Click to expand...
Click to collapse
I am gonna look more into it when I get to my computer.
Finger on the trigger, hammer pulled back. Just unlock already!!
reaper24 said:
I am gonna look more into it when I get to my computer.
Click to expand...
Click to collapse
Thanks dude. Hopefully we can unlocked and junk. Did I mention I also love the reaper? Multiple reaper tattoos inspired by children of bodom album art. But I digress.
It would be nice if HTC updated their bootloader unlock method but frankly, I dont see that happening. I called them today and they dont support anything.
tailsthecat3 said:
Thanks dude. Hopefully we can unlocked and junk. Did I mention I also love the reaper? Multiple reaper tattoos inspired by children of bodom album art. But I digress.
It would be nice if HTC updated their bootloader unlock method but frankly, I dont see that happening. I called them today and they dont support anything.
Click to expand...
Click to collapse
I'm sure there is a way to do it . Even on the new update cause hboot is still the same . I never had trouble back in the og EVO days when it came to root.
reaper24 said:
I'm sure there is a way to do it . Even on the new update cause hboot is still the same . I never had trouble back in the og EVO days when it came to root.
Click to expand...
Click to collapse
Who's stock with the latest update? Try the .2 RUU?
I'm absolutely stumped. My brain is hot because of it.
Sent from my Google Nexus S 4G via XDA Premium
Just rooted my phone Htc devs way no issues on the latest update and hboot 1.5
reaper24 said:
Just rooted my phone Htc devs way no issues on the latest update and hboot 1.5
Click to expand...
Click to collapse
How did you do it???? Please help me/us out..I have the exact same problems, tried using the 2.08 RUU's and get an error 140. And when I try the HTC unlock method at step 12 when I flash the unlock_code.bin nothing happens, no disclaimer shows up. I am on 2.17.651.5 latest OTA and HBOOT 1.5.
So someone mentioned in a thread I read that they were on hboot 1.4 with s-off and they were having issues (that aren't important to the topic of this thread) so they used a 2.08 RUU to return to stock, which flashed hboot 1.5 onto their phone. This person said they checked their bootloader and saw that it was indeed hboot 1.5, then they RUU'd back to an older stock ROM and their bootloader was hboot 1.4.
So, was this workaround for being able to Revolutionary unlock an HTC Evo 3D common knowledge before and it's old news now, or had nobody thought of doing this earlier to get rid of hboot 1.5? I was one of the lucky ones who first got my 3vo less than a month ago, yet it came with hboot 1.3 (now it's on the eng bootloader of course ). so I'm too afraid of losing my revolutionary root to try this myself, but I figured I'd at least put this out there in its own thread so that all you adventurous types stuck with hboot 1.5 can try this out and report your findings.
NOTE: as stated before, I did not try this myself and the person who said they tried this did not prove it to me or anyone else, they merely stated it and since this is the internet, I go by "pics or it didn't happen" if information comes from an untrusted source. I'm not responsible for bricks and impregnation of your daughter(s), and all that other stuff devs usually claim no responsibility for in their disclaimers.
You can change the bootloader if you're s-off, you can't if you're s-on
Twolazyg said:
You can change the bootloader if you're s-off, you can't if you're s-on
Click to expand...
Click to collapse
Does that apply even if you're using an RUU? I knew you couldn't change the bootloader if you tried to flash using fastboot, but I didn't remember seeing anything about not being able to through RUU (though I guess I never saw anything that said you could through RUU either...)
w0rdOo said:
Does that apply even if you're using an RUU? I knew you couldn't change the bootloader if you tried to flash using fastboot, but I didn't remember seeing anything about not being able to through RUU (though I guess I never saw anything that said you could through RUU either...)
Click to expand...
Click to collapse
yes, you will remain s-off
t3project said:
yes, you will remain s-off
Click to expand...
Click to collapse
Well I should've known it was too good to be true, that you could get to an old bootloader through an RUU. Thanks to both of you for the quick and helpful responses.
w0rdOo said:
Well I should've known it was too good to be true, that you could get to an old bootloader through an RUU. Thanks to both of you for the quick and helpful responses.
Click to expand...
Click to collapse
sounded like a good idea. would love to get back to hboot 1.40
will it work how does it work and if so how do i do it im stuck with a hboot 1.5 im rooted but s on still
tashsru said:
will it work how does it work and if so how do i do it im stuck with a hboot 1.5 im rooted but s on still
Click to expand...
Click to collapse
You are stuck with 1.50 with no changes in sight. At present time you can only change hboot if you are S-off.
Hello everyone
I am new to this forum, well I have been downloading roms for about 6 months but I registered today, anyhow I took my evo 3d to the sprint repair center the other day because my lcd went out, that's what the sprint employee had told me anyway and so two days later I received a replacement evo 3d, it was hboot 1.5 obviously and I took it home and installed the 2.17.651.5 RUU because sprint puts a version of the 2.17.651.5 ruu on their evo 3d's that does not communicate well during the unlock process of HTCdev.com, so here is my problem, after flashing the ruu I unlocked my bootloader via the htcdev unlock method, and began to flash my first custom rom, and I have run into the same problem over and over, I would boot into clockwordmod recovery via fastboot and then flash the rom after performing a super-wipe and every single time I would get a boot loop, no matter which rom I used, it would boot up and get to the setup screen and boot loop constant boot loop, every single rom I tried, I have not experienced this before when flashing roms, I then looked at a few threads of the roms I tried to flash and one recommended that I extract the boot.img from the zip and flash it via fastboot, some people say that you are required to do that with hboot 1.5 but in the past when I used my old evo 3d I never had to do that and it was hboot 1.5 s-on, please if someone has an answer I would gladly appreciate it, thanks in advance
UndefinedUser said:
Hello everyone
I am new to this forum, well I have been downloading roms for about 6 months but I registered today, anyhow I took my evo 3d to the sprint repair center the other day because my lcd went out, that's what the sprint employee had told me anyway and so two days later I received a replacement evo 3d, it was hboot 1.5 obviously and I took it home and installed the 2.17.651.5 RUU because sprint puts a version of the 2.17.651.5 ruu on their evo 3d's that does not communicate well during the unlock process of HTCdev.com, so here is my problem, after flashing the ruu I unlocked my bootloader via the htcdev unlock method, and began to flash my first custom rom, and I have run into the same problem over and over, I would boot into clockwordmod recovery via fastboot and then flash the rom after performing a super-wipe and every single time I would get a boot loop, no matter which rom I used, it would boot up and get to the setup screen and boot loop constant boot loop, every single rom I tried, I have not experienced this before when flashing roms, I then looked at a few threads of the roms I tried to flash and one recommended that I extract the boot.img from the zip and flash it via fastboot, some people say that you are required to do that with hboot 1.5 but in the past when I used my old evo 3d I never had to do that and it was hboot 1.5 s-on, please if someone has an answer I would gladly appreciate it, thanks in advance
Click to expand...
Click to collapse
the problem is just that.....youre s-on..you either must do the wire trick...or unknownforces downgrade method to obtain s-off and then flashing will be easier bc of permissions needed to write to the boot partition...
wloftus said:
the problem is just that.....youre s-on..you either must do the wire trick...or unknownforces downgrade method to obtain s-off and then flashing will be easier bc of permissions needed to write to the boot partition...
Click to expand...
Click to collapse
That may be true but there are a lot of users on this forum who are s-on and still flash plenty of roms, most roms do not require you to be s-off and it's not a normal boot loop, the phone starts up and then gets to the setup screen and that's when it reboots, most boot loops occur at the boot animation, so why is this happening now when my old when which was hboot 1.5 s-on worked fine when flashing roms, someone please help
UndefinedUser said:
That may be true but there are a lot of users on this forum who are s-on and still flash plenty of roms, most roms do not require you to be s-off and it's not a normal boot loop, the phone starts up and then gets to the setup screen and that's when it reboots, most boot loops occur at the boot animation, so why is this happening now when my old when which was hboot 1.5 s-on worked fine when flashing roms, someone please help
Click to expand...
Click to collapse
youre right they do flash...they use an app called flash gui...unless you want to manually go and flash the boot image through fastboot
wloftus said:
youre right they do flash...they use an app called flash gui...unless you want to manually go and flash the boot image through fastboot
Click to expand...
Click to collapse
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
UndefinedUser said:
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
Click to expand...
Click to collapse
well then...maybe you should also try scanning the posts better... if youre upset that you have 2.17 and think thats the issue...do a downgrade...oh wait..you already knew that now if you had 2.17 before and had no problems maybe its not the phone...oh btw...my phone is a replacement from asurion as well...i had no issues doing what i needed.. now maybe...JUST maybe someone might know a bit more than you and you should try not to argue with them
UndefinedUser said:
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
Click to expand...
Click to collapse
I didn't really believe that all evo 3d's act differently until I got my replacement. Now I know that their not all the same, even when they have the same hardware version. I'm sure you can see that too. You just have to figure out what works for that phone. I think a sure fire way to get a good install when you have s-on is to use fastboot to boot to recovery. Have you tried that yet? It doesn't sound like you've got a normal bootloop and I haven't encountered your issue before but fastbooting to recovery is worth a try. I'm sure you've heard this a lot but I'm gonna suggest it anyway, get s-off, you won't regret it.
Also, does the phone reboot like that after you run an ruu?
wloftus said:
well then...maybe you should also try scanning the posts better... if youre upset that you have 2.17 and think thats the issue...do a downgrade...oh wait..you already knew that now if you had 2.17 before and had no problems maybe its not the phone...oh btw...my phone is a replacement from asurion as well...i had no issues doing what i needed.. now maybe...JUST maybe someone might know a bit more than you and you should try not to argue with them
Click to expand...
Click to collapse
I was not trying to argue, I was trying to get my point across, I know all about flashing on hboot 1.5 with s-on, like I said I owned a device that was not downgraded, all I am asking is for a simple answer to original problem, what is different about this device? if anyone could help I would appreciate it
UndefinedUser said:
I was not trying to argue, I was trying to get my point across, I know all about flashing on hboot 1.5 with s-on, like I said I owned a device that was not downgraded, all I am asking is for a simple answer to original problem, what is different about this device? if anyone could help I would appreciate it
Click to expand...
Click to collapse
What wikdNoob said. Some phones do fine flashing ICS ROMs with S-on, but from my reading of the forums, many phones bootloop when flashing ICS ROMs with S-on. Since you are 1.5 S-on, you should do the wire trick to get S-off.
I've read so many times how people use the same procedures to flash the same ROM with the same radios, hboot, etc where one gets bootloops and the other does not. Each phone is different.
coal686 said:
What wikdNoob said. Some phones do fine flashing ICS ROMs with S-on, but from my reading of the forums, many phones bootloop when flashing ICS ROMs with S-on. Since you are 1.5 S-on, you should do the wire trick to get S-off.
I've read so many times how people use the same procedures to flash the same ROM with the same radios, hboot, etc where one gets bootloops and the other does not. Each phone is different.
Click to expand...
Click to collapse
I just decided to do the wire trick and now i'm s-off, I love being s-off, I feel so free now
UndefinedUser said:
I just decided to do the wire trick and now i'm s-off, I love being s-off, I feel so free now
Click to expand...
Click to collapse
see how much easier that was now...?
wloftus said:
see how much easier that was now...?
Click to expand...
Click to collapse
yes I should not have argued with your logic, thanks for the help
UndefinedUser said:
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
Click to expand...
Click to collapse
Its A Problem With Certain Phones Because I Have A Replacement Right Now And I Can Flash ICS Roms With Ease But On My Purchased Phone I Would Get Bootloops.
NexusS4gFreak said:
Its A Problem With Certain Phones Because I Have A Replacement Right Now And I Can Flash ICS Roms With Ease But On My Purchased Phone I Would Get Bootloops.
Click to expand...
Click to collapse
I am now s-off, I feel so free, no more boot loops ever, I am so happy that I can flash roms with ease and in my own custom recovery, I don't ever have to touch fastboot again!
UndefinedUser said:
I am now s-off, I feel so free, no more boot loops ever, I am so happy that I can flash roms with ease and in my own custom recovery, I don't ever have to touch fastboot again!
Click to expand...
Click to collapse
Lol Congrats, I Was Thinking About S-OFF But With My Replacement I Dont Need To!
UndefinedUser said:
I am now s-off, I feel so free, no more boot loops ever, I am so happy that I can flash roms with ease and in my own custom recovery, I don't ever have to touch fastboot again!
Click to expand...
Click to collapse
Now that you're s-off you can change your boot splash screen, a lot of choices in the the themes and apps section. You can check mine out from the link in my Sig.
NexusS4gFreak said:
Lol Congrats, I Was Thinking About S-OFF But With My Replacement I Dont Need To!
Click to expand...
Click to collapse
you really should go s-off, I thought the wire trick method would be difficult it was literally the easiest thing I have ever done, I don't know if you are familiar with JTAG xboxes, I used to jtag a **** load xbox's back in the day, in high school, so all this **** is easy, no soldering involved with this ****
Hello. Never made a thread before and was really hoping I wouldn't have to or would find an answer elsewhere.
Since that didn't work out, here's my problem:
Background: Evo 3d, virgin mobile, unlocked bootloader, s-off, hboot was at 1.50, and I don't remember what the radio was at. I was running CM11 and was quite happy until two days ago when I stopped receiving texts! No clue why, just stopped. Hangouts, etc etc. Called VM and they had no idea why that was happening either. Tried switching roms, reinstalling backups, etc etc. Clean wipes and all. Then I saw someone said they had to [for some reason] reinstall everything stock and then they had messaging back. So that's what I set out to do.
In Between: Used the RUU that I'm fairly certain came with my phone. Everything was good, it erased everything, and "updated system" and signatures. It was almost finished when BAM, popped up with error 152 Image Update Error; right at the very end. Quite disappointing. Tried it multiple times again with the same result. Not sure what to do.
Current: Only screen I can see (looks like shortened bootloader screen) says "***locked***" at the top, hboot 1.57.0000, radio 1.06.00.126, then says openADSP-v02.6.0.2226.00.0217eMMc-boot
Also tried flashing the unlock_code.bin, and while it took it, it changed nothing. One screen I did see very briefly but cannot replicate said that everything was there except system. Not really sure how to take that or what to do. Any and all help would be helpful. As is it sits on the HTC screen with exclamation points in each corner. When unplugged from usb it gives me that above screen. Removing battering and restarting to bootloader still gives the same screen.
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Through Windows; the RUU exe.
SammyMak said:
Through Windows; the RUU exe.
Click to expand...
Click to collapse
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
So I have my phone working now. I think it was the RUU.exe that I was using. I downloaded a different one from here http://androidruu.com/Shooter/ after much googling. That finally restored it to original VM stock rom etc. I couldn't use your method of placing the zip onto the root of my SD because despite it being there, it wouldn't go through the normal search for the file. I would remove the battery, put it back in, use the button key combo to try and open to bootloader, and it would go but it would be the page with the status and then it would instantly go back to the black screen with HTC logo.
Thank you for your help though!
Also I'm not sure how useful exactly this will be for anyone else, but if you find yourself ruu'd and needing better files...
The hboot ENG 1.04 I got from here: http://forum.xda-developers.com/showthread.php?t=1817513
ALL other downloads of that hboot did not work AT ALL.
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
The hboots on that site however are stock and most likely won't run the custom roms as well, if at all, as 1.04.
SammyMak said:
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
But the hboots on the site aren't helpful fyi
Click to expand...
Click to collapse
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
hossman said:
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
thank you!
Brian706 said:
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
Click to expand...
Click to collapse
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
SammyMak said:
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
Click to expand...
Click to collapse
Thanks for clarifying that! I see what you meant now.
No worries, I didn't take offense or think you were disrespectful; I just wanted to make sure the downloads were working properly!
And for the record, the stock hboots will work just fine with custom roms. Hboot 1.50 for example will be compatible with the same selection of roms as JuopunutBear 1.50.5050. The difference is that JuopunutBear is patched and will allow for extra fastboot commands and allow them to be run on a locked bootloader.
The eng 1.04 hboot allows for extra fastboot commands that the stock hboot cannot. But you can boot any rom out there on the stock hboots. I've used stock 1.50 forever on this device.