So, I have tried very very hard to fix this, but now I'm out of ideas completely.
My problem is that I have no clue how to get from the ICS RUU leak to the most recent software update from HTC. There probably is a way to do it, but that isn't the only problem. I have no cable to do it with and my phone constantly restarts due to jacked software installation. So please, anybody who can assist me I would forever love you and such.
Thanks anybody
Also don't hate me if this belongs in Q&A, I wasn't sure.
ο χάκερ said:
So, I have tried very very hard to fix this, but now I'm out of ideas completely.
My problem is that I have no clue how to get from the ICS RUU leak to the most recent software update from HTC. There probably is a way to do it, but that isn't the only problem. I have no cable to do it with and my phone constantly restarts due to jacked software installation. So please, anybody who can assist me I would forever love you and such.
Thanks anybody
Also don't hate me if this belongs in Q&A, I wasn't sure.
Click to expand...
Click to collapse
So uh, not to be a smartass, but how do you charge your phone without a cable?
all you should have to do is go into hboot and flash the latest RUU. If you get the mainver error use one the many tools/tutorials on here.
tekhna said:
So uh, not to be a smartass, but how do you charge your phone without a cable?
Click to expand...
Click to collapse
I worded that bad. I have a cable, but it doesn't have the ability to transfer data between my phone and any computer. (I don't have the original cable, it was replaced by a mini-usb)
EDIT: I also can transfer data from my SD card to my computer, just not directly through the phone.
brando56894 said:
all you should have to do is go into hboot and flash the latest RUU. If you get the mainver error use one the many tools/tutorials on here.
Click to expand...
Click to collapse
I have flashed the RUU but it always gets stuck at the HTC white splash screen, unless I have the wrong file or something.
ο; χάκε;ρ;24502700 said:
I have flashed the RUU but it always gets stuck at the HTC white splash screen, unless I have the wrong file or something.
Click to expand...
Click to collapse
You have to go through the RUU twice.
first run updates hboot. second runs through the rest.
Sent from my ADR6425LVW using XDA
Snuzzo said:
You have to go through the RUU twice.
first run updates hboot. second runs through the rest.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
I think I have the wrong file then or something. I did run it twice because I thought that I did it wrong
You can't go back to the latest GB RUU from the leaked ICS RUU. This is because the new RUU has a higher HBOOT version than the old, and even though you can reduce your mainver, you can't go back to an older HBOOT. You do have some options though:
1) Try to fix the issues you are having by reflashing the leaked RUU.
2) Wait for the ICS OTA, and you should be able to upgrade to that
3) Beta testing for Juopunutbear S-Off is now over, and it has been proven successful. Once this method is released, you can do it to your phone, and once you have S-Off, you should be able to run downgrade your HBOOT and run any RUU (newer or older) that you want.
Spend less time working on your sig, and more time reading the actual forums.
isdnmatt said:
Spend less time working on your sig, and more time reading the actual forums.
Click to expand...
Click to collapse
I needed help, not your smart ass comments
Related
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.
Ok, so impatience got the best of me. I bought the Rezound earlier this week when I heard ICS was coming on 4/6. I was sick of my droid x2 so it was a win win for me, I love HTC.
When I found out there was no update in the near future I decided to give the leaked ROM a try. I am NOT rooted, my bootloader is locked.
I flashed the update and now I have no signal on my device.
Frantically i tried to flash back to the current stock to no avail. I tried the RUU but of course it failed due to the difference in hboot versions.
WTF do I do now???
Having an awesome phone you cant use sucks. Any help would be greatly appreciated. I would like to avoid rooting if possible...
weasel87 said:
Ok, so impatience got the best of me. I bought the Rezound earlier this week when I heard ICS was coming on 4/6. I was sick of my droid x2 so it was a win win for me, I love HTC.
When I found out there was no update in the near future I decided to give the leaked ROM a try. I am NOT rooted, my bootloader is locked.
I flashed the update and now I have no signal on my device.
Frantically i tried to flash back to the current stock to no avail. I tried the RUU but of course it failed due to the difference in hboot versions.
WTF do I do now???
Having an awesome phone you cant use sucks. Any help would be greatly appreciated. I would like to avoid rooting if possible...
Click to expand...
Click to collapse
Which leak did you flash? Pre-rooted or stock? Also, this might sound like a dumb question, but is your battery door off? You won't be able to get any signal of any kind with the battery door off.
Stock. Battery door is on and still all i get is the little x over the bars. tried in cdma only mode. tried with the sim out, etc
maybe re-flashing the leaked ruu?
weasel87 said:
Stock. Battery door is on and still all i get is the little x over the bars. tried in cdma only mode. tried with the sim out, etc
Click to expand...
Click to collapse
Did you run the RUU twice? It might not have finished updating. It needs to flash in hboot, then reboot and you'll flash it again. Try it over and make sure you do it twice if you didn't. That should fix it.
WasabiWa83 said:
Did you run the RUU twice? It might not have finished updating. It needs to flash in hboot, then reboot and you'll flash it again. Try it over and make sure you do it twice if you didn't. That should fix it.
Click to expand...
Click to collapse
The old RUU or the ICS? The old one failed due to hboot mismatch. The ICS update I flashed from a PH98IMG. And yes, did it twice.
weasel87 said:
The old RUU or the ICS? The old one failed due to hboot mismatch. The ICS update I flashed from a PH98IMG. And yes, did it twice.
Click to expand...
Click to collapse
The leak. You won't be able to flash any old ruu. I would relock your bootloader, then flash the leaked ics ruu twice again.
EDIT: Just make sure you follow the instructions HERE that Scott has provided.
Double check your md5. May have gotten a bad download.
Sent from my ADR6425LVW using XDA
sounds like he didnt run the ruu twice... please run it twice again and let us know
I know this might sound dumb but, awhile ago I was having a similar problem. I went frantic like you. Turns out I must have accidentally bumped the mobile data button in the quick settings pull down bar. Just wondering if you might have data turned it off and didn't think about checking it cause you are figuring it's a problem with the leak.
Sent from my ADR6425LVW using xda premium
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
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.