So the phone is bootlooping. I don't have recovery installed and my phone is S-ON. I tried flashing the 605.5 RUU, it updated the bootloader, but the phone is still bootlooping. I have access to HBOOT, and can use fastboot usb, but I am unsure of how to proceed.
Stats:
*** LOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0906w_1
eMMC-boot
Jul 19 2011, 14:51:08
FASTBOOT (Working)
RECOVERY (Bootloops)
FACTORY RESET (Bootloops)
SIMLOCK (Don't know what this is/does)
HBOOT USB (Don't know what this is/does)
IMAGE CRC (Gives values for osbl, amss, hboot, boot, recovery)
What can I do to fix this phone?
This is bad. You may be bricked. Might want to talk to the people in #thunderbolt irc.
The RUU you used, was it an exe or zip file. If it's a zip did you put it on the root of the SD card and rename it pg05img and then flash it in hboot? That's how i fixed mine.
nxslt1 said:
The RUU you used, was it an exe or zip file. If it's a zip did you put it on the root of the SD card and rename it pg05img and then flash it in hboot? That's how i fixed mine.
Click to expand...
Click to collapse
This you? Haha...
Thank you for telling me that I have to rename it to PG05IMG before using Hboot to flash. I didn't know that. I've rooted 4/5 phones manually using adb and fastboot. I have a complicated problem that may not have a solution. Suggestions like, "Is your battery charged? / Did you turn your phone on with down button and power button? / Did you rename the Stock RUU correctly?" are not helpful in this situation.
Suggestions like talking to the IRC guys like Adry, Jcase, Scotty and the like is solid advice. Unfortunately, they think it appears to be a lost cause. I am merely exploring other alternatives by asking an fairly open ended question.
Bottom line, thanks for your 'help', now please move along.
theherkman said:
This you? Haha...
Thank you for telling me that I have to rename it to PG05IMG before using Hboot to flash. I didn't know that. I've rooted 4/5 phones manually using adb and fastboot. I have a complicated problem that may not have a solution. Suggestions like, "Is your battery charged? / Did you turn your phone on with down button and power button? / Did you rename the Stock RUU correctly?" are not helpful in this situation.
Suggestions like talking to the IRC guys like Adry, Jcase, Scotty and the like is solid advice. Unfortunately, they think it appears to be a lost cause. I am merely exploring other alternatives by asking an fairly open ended question.
Bottom line, thanks for your 'help', now please move along.
Click to expand...
Click to collapse
And was this you? Not really a complete answer to that question. Guess we all make a mistake now and then...
This is uncalled for. You asked for help, he tried to give it. While you did say that you had tried flashing stock, you didn't specify how. You didn't say you had done it before. Chill out.
mrkite38 said:
And was this you? Not really a complete answer to that question. Guess we all make a mistake now and then...
This is uncalled for. You asked for help, he tried to give it. While you did say that you had tried flashing stock, you didn't specify how. You didn't say you had done it before. Chill out.
Click to expand...
Click to collapse
Way to take a post out of context. Completely ignore this.
Trolling much? 'Cause it doesn't look like you added anything useful to this thread either.
theherkman said:
Way to take a post out of context. Completely ignore this.
Trolling much? 'Cause it doesn't look like you added anything useful to this thread either.
Click to expand...
Click to collapse
Not trolling, just pointing out the obvious. And "useful" includes keeping threads respectful and on track in my opinion which, in this situation, is the one that matters. There is no room here for debate or attempts at witty replies. If you have a problem with my moderation then PM me and we can take it from there. Otherwise, please review my previous advice.
ok im just trying to help so dont bite my head off but im not sure but if you could use the revolutionary tool in hboot and get S-OFF then you could try reflashing a older hboot and i would even try reflashing the radio while your in bootloader since its the only thing you can get into
Also i would download from somewhere else the RUU and flash it again through HBOOT this video shows
http://www.youtube.com/watch?v=tE8BiIFUOpk
If that dont work try this
http://revolutionary.io/
plus i found this but dont know if it would help
http://forum.xda-developers.com/archive/index.php/t-1293180.html
resolved?
Old thread I happened to stumble across...
Bootloops are almost always are kernel related.
My advice:
1) see if football hasn't got an official RUU.. RUU reset may work on its own and would be the simplest solution.
2) if no, open up the last known good working Rom or RUU you had before this soft brick.
Steal the boot.img out of the zip file; reflash boot.img from this (stolen file) through fastboot.
Also, if needed, prep by unlocking the bootloader through fastboot (unlock.bin from htcdev).
If you happen to have been using a2sd, d2sd or some other method to allow data or cache to be written to your SD, this also could be caused by /sdext (not communicating with kernel).
Solution for that is fairly simple:
Pull SD card and reformat the /ext partition(s) via a SD reader/writer.
Doesn't seem like the worst case I've seen, but I know not having your phone work can frustrate anyone. Hope that helps.
Rob
Related
It has come to my attention that a number of regional OTA updates are now rolling out, specifically US and some Asian areas appear to be in progress.
The reason for this post is for those users who specifically want the regional HoneyComb variant for their region and language, which is perfectly natural and
something which I completely understand.
Firstly some ground rules, so that nobody feels I'm ignoring them specifically:
1. Do not PM me if you "soft brick" ( white screen with HTC logo )
2. Do no PM me with questions about what to do next.
3. Do not PM me about anything to do with upgrades PERIOD.
I will not answer PMs about OTA upgrades unless I specifically request that you PM me. So as you can see I'm not ignoring anyone specifically, I'm ignoring everyone who PM's me about upgrades. The reason for this is as my signature says, questions should be asked in the open forums so everyone can benefit from the information.
Please post any questions or problems encountered in this thread and not in multiple other threads. I will do what I can to help when I can as I'm sure will others.
Above all else don't panic. If your are S-OFF almost anything is fixable provided to don't panic and do something foolish.
What I need in order to give you the simplest and most painless upgrade process is a copy of the OTA zip file for your region.
If you have already gone ahead and tried to apply the OTA and are now stuck on a white screen with the HTC logo, here is what you need to do.
You need to have fastboot working to do this.
1. Get the OTA zip file from you device. Is should be located somewhere on the SD card.
2. Unzip the file using 7-zip or some other zip tool that ignore the signature on the file, windows built-in zip will not work.
3. Inside the file you will find a file called "firmware.zip", copy this file to the directory where you have fastboot installed.
4. Download this hboot file:
http://www.multiupload.com/8BI4CWZWMU the MD5SUM is: 6812365feef394e2d1e3c1cd5ab67d24
CHECK the md5sum before proceeding
Copy this file to where you have fastboot installed.
5. boot to fastboot mode and run the following:
Code:
fastboot flash hboot hboot-6.11.1111.nb0
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
You should then reboot into Honeycomb.
If you continue to encounter the white screen or otherwise cannot boot, then go to the easy upgrade thread in the development forum, download and flash the "light" version appropriate for your device from post 1.
You should then boot to recovery. Post a message here and wait for assistance.
If this information makes you unsure of whether or not to take the upgrade, that's fine. Please do yourself an everyone else like you a service, when presented with the option to upgrade "Select the download and install later" option and upload the downloaded OTA zip file somewhere where I can get it.
Works !
Just to confirm that OTA from s-off indeed caused white HTC screen (probably due to incompatability of s-off old version of hboot which remained on machine and recovery).
But solution in post 1 worked. Now on HC with new hboot s-off (but w/o CWM...).
Thanks.http://media.xda-developers.com/images/smilies/smile.gif
Just want to say thanks
This is my first post in the XDA forums. I don't even know if I am putting this in the correct section. Just want to say thank you for enabling me to make a seamless transition to honeycomb and making it a thing of beauty. I would have done this earlier but I couldn't find the donate button and then once I did I forgot I didn't have enough posts to post this into the developer section. So it is quite evident that if a complete NOOB like me can do this the process couldn't have been made any easier. Once again thank you. A couple of beers on the way (I think that's the correct term lol)
Confirmation number:5EM64938GA251543B
GMAN1722 said:
This is my first post in the XDA forums. I don't even know if I am putting this in the correct section. Just want to say thank you for enabling me to make a seamless transition to honeycomb and making it a thing of beauty. I would have done this earlier but I couldn't find the donate button and then once I did I forgot I didn't have enough posts to post this into the developer section. So it is quite evident that if a complete NOOB like me can do this the process couldn't have been made any easier. Once again thank you. A couple of beers on the way (I think that's the correct term lol)
Confirmation number:5EM64938GA251543B
Click to expand...
Click to collapse
My thanks to you very much appreciated.
Need help stuck on white screen with s-off
Okay, I need assistance please. I bought a Flyer on the Marketplace and gave it to my Mom as a gift, I ran the RUU to go back to stock. I carelessly did not check that the device had s-off Revolitionary and tried to install the HC update. Now I am stuck on the white screen. I have ADB on my pc, I have used it many times. If I cannot boot past the white screen how can I extract the Firmware from my sd card? I checked the developement thread mentioned above and this is one of the steps. I currently do not have a copy of the OTA on my pc. I have the US wifi version of the Flyer from Best Buy.
I tried to run the GB RUU but since my device won't boot past the white screen the pc does not see the device when attempting to run the RUU.
I really need to get this back up and running for my Mom, she loves it and is pretty upset that it is unusable currently.
I am trying not to panic, can anyone help me?
you have come to the right place. Standby for a little and I'm sure Globaltron can fix you up. He's seen this a hundred times. Just be patient. He's in Europe so may already be asleep.
In the meantime if you know how to get into fastboot from the white screen, put the Flyer into fastboot and try executing the RUU again.
DigitalMD said:
you have come to the right place. Standby for a little and I'm sure Globaltron can fix you up. He's seen this a hundred times. Just be patient. He's in Europe so may already be asleep.
Click to expand...
Click to collapse
Thanks, I feel like an idiot noob, I should've read all of Globatron's warnings before being too quick to update to HC I was careless. I don't use the Flyer so I don't check here often, now I wish I had.
Brilliant idea about trying to run the RUU from Fastboot, I was thinking about trying that. Thanks!
edit; update, I tried running the RUU from fastboot, I am below 30% battery, I will let it charge and try later.
Rhiannon224 said:
Thanks, I feel like an idiot noob, I should've read all of Globatron's warnings before being too quick to update to HC I was careless. I don't use the Flyer so I don't check here often, now I wish I had.
Brilliant idea about trying to run the RUU from Fastboot, I was thinking about trying that. Thanks!
edit; update, I tried running the RUU from fastboot, I am below 30% battery, I will let it charge and try later.
Click to expand...
Click to collapse
You are welcome, nice to see your smile here.
Rhiannon224 said:
Thanks, I feel like an idiot noob, I should've read all of Globatron's warnings before being too quick to update to HC I was careless. I don't use the Flyer so I don't check here often, now I wish I had.
Brilliant idea about trying to run the RUU from Fastboot, I was thinking about trying that. Thanks!
edit; update, I tried running the RUU from fastboot, I am below 30% battery, I will let it charge and try later.
Click to expand...
Click to collapse
Don't worry Rhiannon224, you'll be fine. There will be a flashable file up within the hour that will sort you out.
He never sleeps
Sent from my HTC Flyer P510e using xda premium
US WIFI up now in the s-off upgrade thread.
Mcord, I'm off to bed now, work in 5 1/2 hours.
I'm unable to get into Bootloader or Fastboot.
Press and hold power & volume-down keys. Am I missing something? Thanks.
I'm sorry for PM'ing you Globatron, and appreciate you helping me!
Full day on HC and I honestly could not be happier with the performance.
sabesh said:
I'm unable to get into Bootloader or Fastboot.
Press and hold power & volume-down keys. Am I missing something? Thanks.
Click to expand...
Click to collapse
Hold the volume down first, before hitting power. Don't let volume go until you are in.
Sent from my HTC Flyer P512 using Tapatalk
Just wanted to say thank you Globatron. Easy directions to follow.
error cannot load hboot-6.11.1111.nbo
as the title states....
all files in same folder on desktop
firmware. zip
fastboot.exe
hboot-6.11.1111.nbo
assistance please oh wise and toothless one
the filename is hboot-6.11.1111.nb0 (NB-zero) not hboot-6.11.1111.nbo
While Running The Risk Of Sounding Like An Idiot I Don't Have Any Idea How To Access The SD Card To Retrieve The File All I Am Able To Get Is The White HTC Screen When I Plug My Device Into The Computer It Doesn't Recognize It As A Drive For Me To Explore.
Cannot find OTA zip
globatron said:
1. Get the OTA zip file from you device. Is should be located somewhere on the SD card.
Click to expand...
Click to collapse
Sorry but I've spent countless hours looking for the OTA zip file from my device but I really can't find it. Would really appreciate some help. Thank you.
Edit: Can't find the zip file so I ended up doing the manual upgrade. Thanks.
MACHONM said:
While Running The Risk Of Sounding Like An Idiot I Don't Have Any Idea How To Access The SD Card To Retrieve The File All I Am Able To Get Is The White HTC Screen When I Plug My Device Into The Computer It Doesn't Recognize It As A Drive For Me To Explore.
Click to expand...
Click to collapse
Now I've seen people type in all lowercase, and (of course) all caps. But this is a new one!
OTA_Flyer_HC_S_hTC_Asia_WWE Honeycomb OTA zip
Just sharing my OTA zip for anyone who might need it (those who can't find the zip file from SD card with the same CID).
http://www.filefactory.com/file/c220471/n/OTA_Flyer_HC_S_hTC_Asia_WWE_3.60.707.4-2.27.707.2_release_232509pocw00jj5fcwbeoe.zip
MD5 Checksum: 37039d88d7a9442685cf64f8fc55cd81
Long story short. Flashed a ROM in EXT4. Something went wrong and I screwed up my partitions. Cant get anything to load. Was directed to flash the RUU in fastboot.
Problem is, I cant figure out how and YES, I looked at the guide. I"m either a dumbass or really cant read. Where do I put the RUU zip? One I get into bootloader how do I run fastboot in usb mode and have it find the RUU zip....
What shall I name the RUU.
Any responses would be most helpful. I need the phone for work tomorrow
Rename RUU to PH85IMG and put it on the root of external sd card (not in any folders). Pull battery, replace, and hold volume down while powering on device. When it asks of you want to update select yes, then let it sit for awhile. It will reboot a couple of times while it does it's thing. When it's done reboot phone and you should be all good
Sent from my CM10 Defy
Trying it now, will let you know how I fare. Thank yo for the prompt reply.
Hope it works
Edit: Do I have to re-add 4EXT etc to flash ROMS or should it still be there?
If you did read then you would have figured everything out for yourself. People claim they read but comprehension is a big factor as well.
To answer your question... Flashing an RUU is like turning the phone back to stock. Depending if you're s-off then you will need to unlock and reflash a recovery.
Double0EK said:
If you did read then you would have figured everything out for yourself. People claim they read but comprehension is a big factor as well.
To answer your question... Flashing an RUU is like turning the phone back to stock. Depending if you're s-off then you will need to unlock and reflash a recovery.
Click to expand...
Click to collapse
Dude...who the EFF are you saying If I did read I would have figured it out. The guide I read from the Amaze bible didn't lay it out as it was in an earlier reply to the thread.
Apparently everyone isn't as wise as you are or doesn't "comprehend" as well as you do. Sorry I asked a question on a forum made for...wait for it...ASKING questions. People like you are the ones that make folks give up and say fvck it.
The question was answered, I appropriately thanked the person, no need for your .02 thanks anyway.
mahgninnuc93 said:
Long story short. Flashed a ROM in EXT4. Something went wrong and I screwed up my partitions. Cant get anything to load. Was directed to flash the RUU in fastboot.
Problem is, I cant figure out how and YES, I looked at the guide. I"m either a dumbass or really cant read. Where do I put the RUU zip? One I get into bootloader how do I run fastboot in usb mode and have it find the RUU zip....
What shall I name the RUU.
Any responses would be most helpful. I need the phone for work tomorrow
Click to expand...
Click to collapse
Just in case people missed it we noted at the beginning of ICS specific section..
3. ICS Specific
tools/how-to’s/mods
How to switch from Gingerbread to ICS with leaked RUU’s - General instructions are in section 2 under roms, for international carriers like Wind..
Click to expand...
Click to collapse
under section 2..
12. How to flash firmware/custom bootloaders
Click to expand...
Click to collapse
which when clicked leads to..(in the same google document)
Expanded articles(saves space)
2. General How-to’s: expanded
How to flash firmware/custom bootloaders
YOU MUST BE S=OFF TO FLASH FIRMWARE AND/OR CUSTOM BOOTLOADERS. Download desired firmware/custom bootloader. Rename the .zip file to PH85IMG.zip and store it on the root of your sd card. Reboot into bootloader by holding Volume down button and power button. Once in hboot, push power button to access bootloader. Allow update and done. A list of the leaked RUU’s that can be used this way are here
Click to expand...
Click to collapse
All information is definitely in the bible, maybe it can be cleared up a bit, but in your case, if you control+f(for find) and typed RUU, the 5th of 6 times it appears in the document would have shown you the answer.
You could look at threads by our mod, he has posted that this is NOT a place just for people to find answers.. and I don't really mind helping people find answers.. but it IS clearly explained in the bible.
This is just to squash any debate over people's reading ability- the answers are ALWAYS there, and I and a few others did our best to reduce how much time is spent searching.. if you want to contribute to the bible, you can always do so in that thread.
I went ahead and changed the link in section 2 to read "12. How to flash firmware/custom bootloaders - this is how you flash a RUU" just to make it easier to find.
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
-DISCLAIMER: DO THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE THIS GUIDE CAUSES YOU TO DO. THIS WORKED FOR ME, BUT RESULTS MAY VARY.-
-PLEASE READ THE ENTIRE GUIDE BEFORE FOLLOWING ANY STEPS TO AVOID ANY CONFUSION-
-THIS GUIDE ONLY APPLIES IF YOU ARE ROOTED WITH S-OFF ON HBOOT 1.58-
-IF YOU HAVE INSTALLED THE ICS OTA UPDATE THEN YOU SHOULD HAVE HBOOT 1.58, UNLESS YOU HAVE DOWNGRADED.-
-IF YOU HAVE DOWNGRADED YOUR BOOTLOADER AND ARE NOT ON HBOOT 1.58, LEAVE THIS PAGE-
-I ALSO RECOMMEND THAT YOU HAVE TWO SEPARATE SD CARDS YOU CAN USE FOR THIS. NO DATA WILL BE DELETED OFF OF EITHER-
-KEEP IN MIND, THAT IF YOU DO THIS, YOU MAY NOT BE ABLE TO BOOT BACK INTO YOUR STOCK ICS ROM FROM THE OTA UPDATE-
-YOU WILL ALSO NEED A MICRO SD CARD READER TO PLUG YOUR SD CARD STRAIGHT INTO YOUR COMPUTER-
If you are not rooted, and do not have S-OFF, check out this guide by crimsy. It has all the instructions you need to root and obtain S-OFF. It worked for me.
Now for the fun part. You're positive you're on HBoot 1.58, and you're getting bootloops when you flash roms. The fix is actually quite simple.
First, go to this thread by mpgrimm2
Scroll down until you see a post on the thread by ramjet73. This post contains a list of HBoot downloads. These are all free.
First, find the one that says "PG86IMG_JBear_1.58.5858_hboot_Sprint_ICS.zip". Download that to use as a backup.
Now, we're gonna go by exactly what I did. But I recommend you do your own research on which Hboot is the best for whatever ROM you're trying to flash.
First off, all of these are already S-OFF, so you wont need to redo the wire trick.
Anyway, I downloaded the first one on the list, "PG86IMG_1.40-hboot.zip".
Now, to install this, you're pretty much gonna trick your phone into "updating" to it.
To do this, just download the HBoot you've chosen to be the best for you (in my case it was the first one on the list, 1.4).
Now just rename that file to "PG86IMG" without quotation marks.
Next, copy it to the root of your SD card.
The rest takes place on your phone. Power off your phone, and boot into the bootloader (Hold volume down + power button).
If you've done the previous steps correctly, your bootloader should detect the HBoot you downloaded, and ask if you want to update.
Volume up= Yes
Volume down = No
If you're positive about this, then choose "Yes".
It should update and tell you to reboot.
This is where I ran into a problem. I was still running stock ICS from the OTA update, and I got stuck in a bootloop. My phone would freeze at the the Sprint animation, turn off, and repeat. I thought I could just disregard it, boot into recovery, and flash my new ROM. But every time I booted into the bootloader all I could do was either update or reboot. This is where that micro SD card reader comes in. Just pop your SD card into your computer, and remove the HBoot you downloaded. Then put your SD card back in your phone and try rebooting into the bootloader again.
If it boots into your bootloader as normal, then that should be it. You should be on whatever HBoot version you chose to download (this worked for me with 1.4)
Now try flashing that ROM again and let me know how it goes.
Keep in mind, different ROMS may have different results. You may still need to flash certain kernals or wipe specific partitions as instructed by the developer of the ROM you want to flash.
Feedback is appreciated.
I prefer to put the PG86IMG file on my sd card while booted up normally. Then reboot straight into recovery bypassing the hboot screen. Wipe, flash rom then boot into bootloader and run the update. This prevents getting bootloops and keeps you from having to use the computer to rename or remove the file. Saves you some work!
Sent from my PG86100 using Tapatalk 2
If you are S-OFF you can also flash a different bootloader from fastboot on a PC avoiding the need to deal with the PG86IMG.zip file at all, then boot directly into recovery from the new bootloader. See my post here for alternative methods to flash a new bootloader when S-OFF, including multiple ways to delete the the PG86IMG.zip file when flashing one from the current bootloader.
ramjet73
Theres also
fastboot oem rebootRUU
fastboot flash zip PG86IMG.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
enter recovery & clear cache then reboot.
I believe this is the fastest way to flash a different hboot
iTzLOLtrain said:
I believe this is the fastest way to flash a different hboot
Click to expand...
Click to collapse
If you look at the guide I linked in my previous post which has similar instructions that I took from the unlimited.io website and tested, you can do this fastboot sequence to clear cache, flash a different bootloader, then reboot back to your current ROM:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip new_hboot.zip
fastboot reboot
Click to expand...
Click to collapse
The hboot filename can be anything you want, and doesn't necessarily have to be "PG86IMG.zip" using this method.
If you need to flash another ROM before the reboot or do something else in recovery, you can issue the "fastboot boot recovery.img" command instead of "fastboot reboot" to go directly to your custom recovery since there is no "fastboot reboot-recovery" command.
ramjet73
ramjet73 said:
The hboot filename can be anything you want, and doesn't necessarily have to be "PG86IMG.zip" using this method.
Click to expand...
Click to collapse
I know.. & because this thread is about bootloaders I thought that's how I would explain myself. Instead of going into more detail & say how you can flash .img files through that process....
iTzLOLtrain said:
I know.. & because this thread is about bootloaders I thought that's how I would explain myself. Instead of going into more detail & say how you can flash .img files through that process....
Click to expand...
Click to collapse
That's fine.
For clarification, the command I suggested to get back to recovery (fastboot boot recovery.img) is not flashing it, only booting it directly to avoid having to go to the bootloader first to get to recovery.
ramjet73
Guys, I made this guide because it seemed like the most basic and simple way to do it. I speak from experience when I say that the command prompt can be a little intimidating. It can be get pretty nerve wrecking when you dont have a back up phone and you feel like you have lots of room for error and you're terrified you might brick your device. This guide doesn't use any sort of external commands, making it seem a lot less manual. I wasn't trying to show people the fastest way. Just the easiest, less nerve wrecking way.
sawyerbenjamin said:
Guys, I made this guide because it seemed like the most basic and simple way to do it. I speak from experience when I say that the command prompt can be a little intimidating. It can be get pretty nerve wrecking when you dont have a back up phone and you feel like you have lots of room for error and you're terrified you might brick your device. This guide doesn't use any sort of external commands, making it seem a lot less manual. I wasn't trying to show people the fastest way. Just the easiest, less nerve wrecking way.
Click to expand...
Click to collapse
The guide I linked in post #3 of this thread provides alternatives for flashing a different bootloader and for deleting the PG86IMG.zip file if you choose that method. Some people are very comfortable with the fastboot commands and that method saves having to worry about deleting the PG86IMG.zip. It's always good to have alternatives because one size never fits all.
You asked for feedback in the OP and we're providing that.
ramjet73
ramjet73 said:
The guide I linked in post #3 of this thread provides alternatives for flashing a different bootloader and for deleting the PG86IMG.zip file if you choose that method. Some people are very comfortable with the fastboot commands and that method saves having to worry about deleting the PG86IMG.zip. It's always good to have alternatives because one size never fits all.
You asked for feedback in the OP and we're providing that.
ramjet73
Click to expand...
Click to collapse
Feedback - Information about reactions to a product, a person's performance of a task, etc., used as a basis for improvement.
You were promoting your own threads, not giving feedback. I have to thank you for the post that helped in making this guide, but your alternate methods aren't really necessary. I'm not sure how to say that without sounding rude or hostile, but Im sure you get my point.
sawyerbenjamin said:
You were promoting your own threads, not giving feedback. I have to thank you for the post that helped in making this guide, but your alternate methods aren't really necessary. I'm not sure how to say that without sounding rude or hostile, but Im sure you get my point.
Click to expand...
Click to collapse
OK, and if you want to be blunt my point was that your guide wasn't really necessary, and I think that's feedback on your "product", since the content was already covered in the guide I setup for people that want to change bootloaders when S-OFF, but if people prefer to use your version in the OP of this thread that's fine with me.
As I already stated, alternatives are good.
ramjet73
ramjet73 said:
OK, and if you want to be blunt my point was that your guide wasn't really necessary, and I think that's feedback on your "product", since the content was already covered in the guide I setup for people that want to change bootloaders when S-OFF, but if people prefer to use your version in the OP of this thread that's fine with me.
As I already stated, alternatives are good.
ramjet73
Click to expand...
Click to collapse
Ouch. That was uncalled for. To far bro. This is just a guide trying to help people. Not a place to get all ugly. Lol.
Dear sir
i have the same problem my phone get stuck on white htc screen
unrooted
s-on
relocked
hboot 1.5.0007
so can any one help me how to solve this problem
thanks
i also tried factory reset and to setup ICS ruu but it got stop when it try to reboot boat-loader and still the same problem
when trying to flash any thing recovery or boot failed and trying to put rom as pg86img also failed any one help me please this phone part of my daily life:crying::crying::crying:
The problem with s-on is that the kernel does not flash when you flash a rom. That is why it won't boot.
To fix the issue after flashing a rom, you need to pull the boot.img from the rom.zip and use fastboot to flash it.
fastboot flash boot boot.img
There are two options when you are s-on and flashing roms to flash the kernel with the rom and avoid bootloop.
The no pc method:
The easiest method is to use 4ext recovery with smart flash enabled. That will allow you to flash roms and kernel and avoid bootloop.
The PC method:
Keep a recovery.img in your fastboot directory. When you want to flash a rom, boot your recovery into the phones memory which allows you to flash the kernel with the rom.
You use: fastboot boot recovery.img
Then just install the rom once booted into recovery. While it seems the same, Booting into recovery using fastboot is different and will allow the kernel to flash.
Help... I have rooted my droid x2 in the past a couple of times, but this Rezound is something different and for some reason I just cannot get it. I really need some assistance. I have been reading all over androidcentral and xda-developers all day and night but It's just overwhelming or something has to go wrong. I tried Hasoon's kit, my device wasn't recognized... then I tried HTCdev website... that was successful, but then I locked it after unlocking it, and I figured out that I probably need it unlocked so I can flash a rom... It would just be easier if someone could chat with me on Skype or something and I'd really appreciate if someone could get me going again and maybe chat with me and give me step by step help. My username is mikeonabike11.
Thanks again,
Confused.
gs3noob said:
Help... I have rooted my droid x2 in the past a couple of times, but this Rezound is something different and for some reason I just cannot get it. I really need some assistance. I have been reading all over androidcentral and xda-developers all day and night but It's just overwhelming or something has to go wrong. I tried Hasoon's kit, my device wasn't recognized... then I tried HTCdev website... that was successful, but then I locked it after unlocking it, and I figured out that I probably need it unlocked so I can flash a rom... It would just be easier if someone could chat with me on Skype or something and I'd really appreciate if someone could get me going again and maybe chat with me and give me step by step help. My username is mikeonabike11.
Thanks again,
Confused.
Click to expand...
Click to collapse
unlock it again. then install amon ra. and then flash a rom. really easy. its over complicated when you read a bunch of forums and try to figure it out yourself
cslingerland said:
unlock it again. then install amon ra. and then flash a rom. really easy. its over complicated when you read a bunch of forums and try to figure it out yourself
Click to expand...
Click to collapse
alright. i got it unlocked. i cant figure out the amon ra part...
gs3noob said:
alright. i got it unlocked. i cant figure out the amon ra part...
Click to expand...
Click to collapse
1) Grab the PH98IMG.zip from the Amon-Ra thread
2) Stick it on the root of your sdcard
3) Reboot into bootloader
4) Press power - the bootloader will scan for an update package, you should then be prompted to hit volume up to install it. If nothing is found, you didn't place the PH98IMG.zip in the right place.
5) Hit volume up to install
6) Reboot when asked
7) Remove the PH98IMG.zip asap.
You can now reboot back into the bootloader then pick recovery from the menu to get into Amon-Ra. Make sure you back up your existing rom before wiping and installing a new one.
One thing you need to know is that a PH98IMG file can be many things. It is only the name of a file that your phone looks for to use when booted into hboot. So it can be a kernel, an entire RUU (OS), a custom recovery or ROM... basically anything. It just means that item was packed into a PH98IMG file in order to run automatically off your SD card when the phone boots. So you need to know what the PH98IMG file is that you are using or you might flash something you don't want that can possibly cause your phone to not work properly.
You'd be doing yourself a favor by learning to use fastboot for things first so you understand the process more before using the "automated" way of doing everything using a PH98IMG file.
Also, as soon as you have Amon Ra installed and have rooted the phone, make a nandroid of your phone at stock and save that in case you need it if something goes wrong flashing the ROM, as mjones mentioned above. It's much easier to restore the nandroid than getting the RUU to get back to stock.
Another thing to think about is whether or not you want to go s-off or not. It unlocks the security of the phone making it both easier to flash ROMs by letting the kernel flash immediately afterwards by itself and also easier to brick the phone by doing something by mistake. You don't have to s-off, you'll just have to manually flash the kernel after flashing a ROM if you don't. If you don't flash ROMs often you might want to read up about it more before you s-off. I rarely change ROMs and I'm still s-on and it doesn't affect me negatively at all.
Also, there's a "Help" thread in the General section, I think it's a sticky, and some guys have posted their gtalks so that people can hit them up for help. Maybe one of those guys can walk you through it. I would be willing to do it but I'm not as experienced as they are and haven't rooted/flashed anything for a year now.
cslingerland is helping me with mine thanks for the help!
feralicious said:
One thing you need to know is that a PH98IMG file can be many things. It is only the name of a file that your phone looks for to use when booted into hboot. So it can be a kernel, an entire RUU (OS), a custom recovery or ROM... basically anything. It just means that item was packed into a PH98IMG file in order to run automatically off your SD card when the phone boots. So you need to know what the PH98IMG file is that you are using or you might flash something you don't want that can possibly cause your phone to not work properly.
You'd be doing yourself a favor by learning to use fastboot for things first so you understand the process more before using the "automated" way of doing everything using a PH98IMG file.
Also, as soon as you have Amon Ra installed and have rooted the phone, make a nandroid of your phone at stock and save that in case you need it if something goes wrong flashing the ROM, as mjones mentioned above. It's much easier to restore the nandroid than getting the RUU to get back to stock.
Another thing to think about is whether or not you want to go s-off or not. It unlocks the security of the phone making it both easier to flash ROMs by letting the kernel flash immediately afterwards by itself and also easier to brick the phone by doing something by mistake. You don't have to s-off, you'll just have to manually flash the kernel after flashing a ROM if you don't. If you don't flash ROMs often you might want to read up about it more before you s-off. I rarely change ROMs and I'm still s-on and it doesn't affect me negatively at all.
Also, there's a "Help" thread in the General section, I think it's a sticky, and some guys have posted their gtalks so that people can hit them up for help. Maybe one of those guys can walk you through it. I would be willing to do it but I'm not as experienced as they are and haven't rooted/flashed anything for a year now.
Click to expand...
Click to collapse