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 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.
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Wrong thread. Need to be posted in q&a
sent from my EVO LTE with it's security flags down.
jrgalioto said:
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Click to expand...
Click to collapse
Similar thing happened to me. I have hboot 1.15. I relocked the the phone ran the RUU. Phone booted up normal with the everything stock. I then took the OTA and when it rebooted it was updating then it rebooted and the phone never turned on again. I sent it to HTC for warranty. They will get it tuesday. I'll see how this goes.
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
closeone said:
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
Click to expand...
Click to collapse
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
jrgalioto said:
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
Click to expand...
Click to collapse
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
jrgalioto said:
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
Click to expand...
Click to collapse
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
00mred00 said:
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
jrgalioto said:
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
Click to expand...
Click to collapse
Hi jrgalioto,
I was able to get a link to the new RUU for you. This one should work fine for you.
~co~
Yep...... sprint doesnt care that you're rooted.
I frequently tell them mine is so they dont go messing with things they shouldnt be
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
il Duce said:
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
Click to expand...
Click to collapse
Sorry duce
Sent from the depths of hell
Hey I try to help and I have even written a guide with a ton of info, I even went so far as to write down troubleshooting stuff and they still post the exact same stuff over and over, some times its a bit frustrating. I even gave instructions on what they need to do should they completely ruin the file tree, when have you seen anyone completely destroy the internal memory lol
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
Any luck on the mirror for the new RUU download? I'm using the latest one I can find and I am stuck and can't get my phone to reboot, shutdown or anything. I can't run fastboot either. all I see is ***Tampered*** unlocked*** ....RUU update fail!
My phone won't respond to the volume down and power button either.
any suggestions?
Hey guys....
I feel really stupid about this entire thing but I've finally decided to post here because I'm getting desperate.
The guide in question (http://forum.xda-developers.com/showthread.php?t=1563342) is fairly striaghtforward. Except the links are really scattered, at least for me. I'm on HBOOT 1.58, and I've had numerous problems even getting to the point where my phone is relocked (it's currently HTC unlocked because I use an MIUI port ROM) successfully. I would bring my problems to that thread, but I don't have 10 posts, which is a questionable rule but w/e.
Anyway, here's my problem. First, I'll tell you what I've done so far, and the problem I've come across both times.
1. Place a "2.89 RUU" or whatever onto my SD card and call it PG86IMG. This is where most of my confusion is. OP of that thread hasn't yet covered what the difference between 2.17 and 2.89 is, but my understand is that 2.17 corresponds with HBOOT 1.5 and 2.89 to 1.58. Honestly, all these numbers piss me off when there's little to no documentation of what the hell they even mean. This file is about 448 MB and my understanding was that it was a stock RUU and would make it so I could access my phone while it was still locked, which you can't do with a 3rd party ROM like the one I usually use.
2. Lock my phone's bootloader. I just did fastboot oem lock in Windows and it rebooted to *** RELOCKED *** *** Security Warning ***. Apparently this is normal, and now I need to flash said RUU.
3. Flash the RUU. This took an EXTREMELY long time, and it went through Loading PG86IMG.zip.. then to some other stage that took much less time to complete. After that it just sits in the bootloader.
Here's my concern... I can't access my SD card. Why? Because I can't even get out of the bootloader or fastboot. All it does is sit here, and since I can't remove the update file PG86IMG.zip, if I try to enter recovery (which I'm sure won't work anyway) it will try to start loading that file again. I don't really know what step I missed here, but it's probably because I'm fairly clueless when it comes to this stuff, lol.
So, I did this once, and then I waited about 6 hours for HTCdev's site to stop crashing so I could unlock my phone again. Made it through a school day with my old ROM and stuff, deleted the update files so they wouldn't run again, etc. etc.
Now, I'm doing it again today with this new 2.89 RUU or whatever and the same exact problem is happening. So now I'm at a stage where my phone is entirely useless until HTCdev.com starts actually sending e-mails. I swear, these crashes on HTCdev's part could not be more untimely.
So basically, what am I doing wrong with relocking my phone? OP implies that I should be able to start my phone (not the bootloader, but actually start it) because they ask after you've supposedly re-locked the bootloader for you to move a new PG86IMG.zip file onto your SD card, which I'm unable to do because my phone can't get out of fastboot/bootloader screen. That's the next step, which is actually doing the downgrading.
And yes, I know that it's possible for HBOOT 1.58 because someone else already did it (last post in the thread).
At this point, I don't really care when I get it to work, man. This is proving to be such a gigantic pain in the ass just to install a new Jelly Bean ROM. I JUST WANT JELLY BEAN!
If anyone can send a noob in the right direction, that'd be great. I have all week and all weekend, but I've run out of time to waste on this for today. I guess most of what I need is to know what files I'm supposed to be downloading, because I have a feeling that's most of what I'm getting wrong.
I hope I've explained my problem well enough, and thanks a ton to anyone who just suffered through reading my essay and can offer help. I'll be sending this to OP of the guide as a PM so hopefully if none of you guys can help they can.
Thanks a ton everyone, I just want to get Jelly Bean on my phone and stop dealing with MIUI :laugh:
Update: Found this thread: http://forum.xda-developers.com/showthread.php?t=1495358. I believe this will probably help me out a lot! Wish I would've seen it sooner.
TL;DR: Need better explanation of how to relock 1.58 hboot bootloader with a stock rom, and where to find the rom.
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
coal686 said:
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
Click to expand...
Click to collapse
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Logic33 said:
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Click to expand...
Click to collapse
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
raptoro07 said:
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
Click to expand...
Click to collapse
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Logic33 said:
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Click to expand...
Click to collapse
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
coal686 said:
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
Click to expand...
Click to collapse
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Logic33 said:
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Click to expand...
Click to collapse
Good! :thumbup:
Keep posting questions, we'll do our best to help.
coal686 said:
Good! :thumbup:
Keep posting questions, we'll do our best to help.
Click to expand...
Click to collapse
LOLJK. I swear, at this point HTC must be trolling me. It's loaded up now. Thanks for trying to help everyone! I can't wait to get Jelly Bean on here soon!
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
coal686 said:
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
Click to expand...
Click to collapse
I have a feeling you didn't see my update It magically decided to work. Here comes double bricking action... this should be (un)fun D:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
chubaan said:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
Click to expand...
Click to collapse
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
fdavila17 said:
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
Click to expand...
Click to collapse
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
ruckstande said:
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
Click to expand...
Click to collapse
Just download the hboot you want, 1.50 or below to get PACMAN to.boot, rename it as PG86IMG.zip place it on the root of your sd card, go to.the bootloader and select yes to apply update , and your done
Sent from my PG86100 using xda premium
Thank you.. that's what I did. And after you're done make sure to wipe dalvik and cache from recovery, at least in my case I had to. And then flash the rom. And that's it..
Sent from my PG86100 using XDA Premium App