Hey guys. Long time reader, since back when I had a g1. Everything here has always been so well written that I never had to ask a question and by following exact directions I never had an issue. Today I rooted my phone, trying to install the leaked ICS update. No matter where I put the PH85img file, it keeps opening on my phone and saying No image! I've placed it in my root folder, my ext_sd folder, even random folders hoping that would work. I've downloaded and checksumed 3 different times. Anybody else getting stuck at this point? Or am I missing something?
have you relocked your bootloader? Seems like you rooted then tried to install without relocking the bootloader.
No, I didn't think it was necessary to relock the bootloader. I tried it first when it was locked, and I got the same no image error message. That's actually why I rooted it in the first place.
are you using recovery or rom manager to install it? If you are you need to put the file on the root of your ext sd and boot the phone in h boot then it should load automatically
Yeah but when it flashes all I got are error messages that say flashing PH85IMG error: no image!" I've tried downloading and reloading it several times and that's still the message I get.
Stolenbikes said:
Yeah but when it flashes all I got are error messages that say flashing PH85IMG error: no image!" I've tried downloading and reloading it several times and that's still the message I get.
Click to expand...
Click to collapse
Did you rename it as PH85IMG.zip? If you actually added the .zip extension after it then your phone is reading it as PH85IMG.zip.zip so make sure you didn't add the .zip extension
Sent from my HTC_Amaze_4G using XDA
It does not have the extra zip extension. The only thing left to try is a new external sd card. Which makes no sense to me because I've been able to access that sd card fine.
Related
I was putting my Titan back down to stock so I could enable GPS (I had it working, but it stopped when I activated my Centro to get data back). Anyways, I forgot to unplug and plug back in the USB. Now no matter what I do It's telling me that the ROM Update utility has encountered communication errors with the device. I should also probably mention that I can still get to the boot loader itself. Any ideas?
Flash via sd card method.
drewcam888 said:
Flash via sd card method.
Click to expand...
Click to collapse
How do I do that if I can't get to Windows Mobile to run the nueSPL executable?
Maybe you should have done some reading before you got into this flashing.
http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
I actually did quite a bit of reading before flashing. My problem is that I didn't disconnect the USB cable like I should have when flashing back to the original boot loader. It stopped and now I'm stuck. I tried putting the bootloader the relocker tried to install on the SD card and named it TITAIMG, but it gets stuck at the gray screen saying "loading...". I tried the exitbl but it tells me that it can't find any sessions. I tried running the program again, but I wind up with communication errors. That's why I'm asking for help now, I've tried everything I've found to try...
MrPenguin_2 said:
I actually did quite a bit of reading before flashing. My problem is that I didn't disconnect the USB cable like I should have when flashing back to the original boot loader. It stopped and now I'm stuck. I tried putting the bootloader the relocker tried to install on the SD card and named it TITAIMG, but it gets stuck at the gray screen saying "loading...". I tried the exitbl but it tells me that it can't find any sessions. I tried running the program again, but I wind up with communication errors. That's why I'm asking for help now, I've tried everything I've found to try...
Click to expand...
Click to collapse
What carrier do you have? Did you run the "GetBackToStockXV6800"?
What radio, Bootloader are you running?
"I tried putting the bootloader the relocker tried to install" (PLEASE CLAIRIFY).
I think it may be working now. I went back to what drew said about using the SD and I tried the one file I hadn't tried. I had tried all of the .nbh files in the directory (stock radio and bootloader), but not the stock ROM itself. I had assumed that since the program quit halfway through flashing the bootloader hadn't installed properly. It would appear I was wrong. So, thanks for the help, Drew, and thanks for being so willing to help cac2us.
MrPenguin_2 said:
I think it may be working now. I went back to what drew said about using the SD and I tried the one file I hadn't tried. I had tried all of the .nbh files in the directory (stock radio and bootloader), but not the stock ROM itself. I had assumed that since the program quit halfway through flashing the bootloader hadn't installed properly. It would appear I was wrong. So, thanks for the help, Drew, and thanks for being so willing to help cac2us.
Click to expand...
Click to collapse
Your welcome,
Have you decided to go with a custom ROM, or are you ready to try PPC Kitchen (BuildOS)?
Keep in mind, if you flash a custom ROM with programs that you later want to update with newer versions, you may not be able to uninstall the original versions.
I'm thinking I'll try PPC kitchen. My biggest problem now is deciding how badly I want windows mobile 6.5. I love the touch friendly GUI and the desktop version of IE, but I'm not able to run TVU or Pandora because they use more memory than I have available.
MrPenguin_2 said:
I'm thinking I'll try PPC kitchen. My biggest problem now is deciding how badly I want windows mobile 6.5. I love the touch friendly GUI and the desktop version of IE, but I'm not able to run TVU or Pandora because they use more memory than I have available.
Click to expand...
Click to collapse
I found that "ZOOM BROWSER" is quite a hog. And "Titanium" eats more than "SPB Mobile Shell 3".
And with "NueKernel", 6+mb. from the camera is just a soft reset away.
But I mainly load apps that I can't find a cab file for, so when an update comes out, I can just update without re-coocking the ROM.
Enjoy.
Hi everyone,
I'm trying to update the ROM on my phone, but when the phone started loading up it got stuck at the Thunderbolt screen.
I removed the battery and planned on going into the CWR recovery to either reinstall the ROM or flash to an old one, but I'm not sure how to do that.
Because I have a PG05IMG.zip file on my SD card from flashing a new radio, the bootloader automatically tries to flash that. When I tell it not to update, the only option I have is to reboot the phone.
So how would I go about getting into the CWR recovery since I can't do it through the Rom Manager app since my phone won't load.
Thanks!
You need to put your SD card into a card reader then into your computer to dename or delete the PG05IMG.zip file or you are pretty much stuck.
stojakapimp said:
Hi everyone,
I'm trying to update the ROM on my phone, but when the phone started loading up it got stuck at the Thunderbolt screen.
I removed the battery and planned on going into the CWR recovery to either reinstall the ROM or flash to an old one, but I'm not sure how to do that.
Because I have a PG05IMG.zip file on my SD card from flashing a new radio, the bootloader automatically tries to flash that. When I tell it not to update, the only option I have is to reboot the phone.
So how would I go about getting into the CWR recovery since I can't do it through the Rom Manager app since my phone won't load.
Thanks!
Click to expand...
Click to collapse
gonna have to find an sd card adapter (or another phone that receives micro sd) and remove the PG05IMG from your sd...i made this same mistake before. bootloader will automatically look for the PG05IMG and once it finds it you are stuck.
Use adb to reboot recovery
Thanks guys, I was afraid of that. Guess I'll have no phone until I get into work tomorrow morning. Appreciate the help, and glad to know I'm not the only one that's had to do this.
jaydizzle333 said:
Use adb to reboot recovery
Click to expand...
Click to collapse
Worked like a charm! I didn't realize I'd still be able to push through adb commands even though the phone was giving me all these force closes. I was able to reload my old ROM and started up just fine. Thanks for the help!
Hello.
My phone is starting to act funny, it has the quite common problem where the touch function on the bottom half of the screen stops working properly.
Since I'm going to send it in, I'd like to return everything to as close to the shipping state as possible. I don't care if I still have Clockworkmod left on it or if I make it unrootable, since I'm going to buy a new phone and sell this one when the contract runs out in a few months anyway.
I've tried searching for the info I need but there are still some things I'm unclear about.
The phone is currently running VillainMod and has ClockWorkMod installed as a bootloader. I was running CM on it until a few days ago, but I tried installing a Sense-based ROM to see if I could get the RUU .exe method to work, but it fails after the phone has rebooted and just says that it cannot update the phone. Any ideas what's causing this? (I used the file RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6.35.15.11_release_signed.exe)
So since the "official" method failed I found the rom.zip that is unpacked by the RUU program and copied it.
Here is where I'm not sure how to proceed. Should I sign the zip-file (using testsign.jar) and then do "apply update.zip" from ClockWorkMod OR should I extract the boot.img, data.img, recovery.img, system.img and radio.img files from the zip, generate a md5 file (how?) and restore it using the backup feature in Clockwork?
Or is maybe both of these ideas totally of the mark?
Any help is appreciated. Do tell if there is some more info you need.
I personally don't think you should go with that plan. I'm not a big scientist when it comes to phone development since I'm still learning. But I think you should go backwards and check what went wrong.
Edit:
I also think that the new rom might have different requirements from the previous one. Usually that causes a problem if you try to flash a rom without fitting the requirements.
No you need to rename the Rom.zip to heroimg.zip then shut down phone and reboot into hboot mode by using power and vol down
First let me affirm that a little knowledge is dangerous and I am proof to that.
I unlocked, rooted, originally had Amon Ra, but was used to CWM on my Droid, so loaded it. Tried Scott's Ice Cream Sand, only to find myself staring at the 4G screen. Went into CWM recovery, recovered from several days earlier, but froze at the "htc" screen.
Still had access to CWM so wiped data/cache, tried again w/ no result. After several battery pulls w/ frozen screen, when booted, I got the FASTBOOT screen w/ the other choices, but before I could make any selections, it scrolled through several items saying "no image", then droped me at HBOOT.
Now I'm looking for the umteenth time at a screen saying:
****UNLOCKED****
VIGOR PUT SHIP S-ON RL
HBOOT-2.11.0000
eMMc-boot
Oct 6 2011.15.43.22
Parsihng...[SD ZIP]
[1] BOOT
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
I have tried the "update" and it processes, I reboot, but am left in the same loop. The drivers in my Win 7/64 are up to date. The phone is recognized as a device, but I have no USB access to try flashing from the PC.m to be back w/ Amon Ra and no access to CWM. I have pulled the SD and deleted PH98IMG, but suspect another is on the phone's memory. I have pulled the SD and the SIM, but still can't get into the phone to reset, flast, or whatever.
I suspect I am "bricked"... don't want to hear confirmation, but better than another 36hrs of repetitious nonsense.
Did you flash the boot.img that goes with the rom you restored? Restoring doesn't restore the boot.img, so you gotta do that manually. It won't boot otherwise. And I'm assuming the PHxxx.zip you have in there already is the boot.img for Scott's rom.
Sent from my bad**s mofo HTC Rezound
Using the PC, I removed the SD and copied the PH98IMG file from CleanFLASH 1.0 to the SD card. When I got into FASTBOOT it looped, but took me back to the standard AmonRa menu w/ Recovery. I selected Recovery, then toggled the USB setting. That allowed me to get the PC linked. Then I flashed the PH98IMG again, it worked, and then flashed the "Stock Rooted ROM-Vigor-WWE2.01.605". It went, but FAILED at the reboot/bootloader command.
Again, I took out the SD card, removed the PH98IMG from it, replaced it, got into Recovery and flashed the ROM from the SD. I now am back in business.
I thought I was pretty handy with PC's, but like troubleshooting them, I found that often it boils down to persistence, trial and error, and luck. I DO SO UNDERSTAND THE PANICKED MESSAGES THAT SO OFTEN FREQUENT THESE FORUMS, and also understand the way they must tax the patience of the more proficient. Even so, please be patient and forgive me for adding to the mess. Maybe this will assist someone else.
Thank you for your help
wfpabst said:
Using the PC, I removed the SD and copied the PH98IMG file from CleanFLASH 1.0 to the SD card. When I got into FASTBOOT it looped, but took me back to the standard AmonRa menu w/ Recovery. I selected Recovery, then toggled the USB setting. That allowed me to get the PC linked. Then I flashed the PH98IMG again, it worked, and then flashed the "Stock Rooted ROM-Vigor-WWE2.01.605". It went, but FAILED at the reboot/bootloader command.
Again, I took out the SD card, removed the PH98IMG from it, replaced it, got into Recovery and flashed the ROM from the SD. I now am back in business.
I thought I was pretty handy with PC's, but like troubleshooting them, I found that often it boils down to persistence, trial and error, and luck. I DO SO UNDERSTAND THE PANICKED MESSAGES THAT SO OFTEN FREQUENT THESE FORUMS, and also understand the way they must tax the patience of the more proficient. Even so, please be patient and forgive me for adding to the mess. Maybe this will assist someone else.
Thank you for your help
Click to expand...
Click to collapse
It isn't that it taxes our patience it is the fact that there are about a dozen threads on this already. A little time spent searching and you would have had your answer.
Sent from my ADR6425LVW using XDA
these threads make me want to never come here again!!
how hard is it to use google. I mean cmon!!
andybones said:
these threads make me want to never come here again!!
how hard is it to use google. I mean cmon!!
Click to expand...
Click to collapse
No kidding.
Just run the RUU if you are that messed up.
I do understand the use of the search function to not clutter the forums but at least he posted in the right section.
Sent from my ADR6425LVW using XDA App
This question has been answered...search
Again I do appreciate the response, but rest assured, I spent nearly two days searching through forums for answers, and none seemed to specifically answer my problem... although I'm sure I missed some. The searching did provide me with alternatives, when combined, appeared to deal with the problem...
wfpabst said:
Again I do appreciate the response, but rest assured, I spent nearly two days searching through forums for answers, and none seemed to specifically answer my problem... although I'm sure I missed some. The searching did provide me with alternatives, when combined, appeared to deal with the problem...
Click to expand...
Click to collapse
So you're up and running again?
Sent from my ADR6425LVW using Tapatalk
Thanks
Boots fine into the 2.01.605 system. The only thing I am trying to deal with is that if I go into fastboot, it still runs through a script and I get the "no image"... however everything works. I did a fastboot recovery of the boot img file that was with the CleanFlash Stock-Rooted Rom, but it doesn't seem to make any difference.
Tried copying the same PH98IMG file to the SD and when asked if I want to update, I did that too... but still get the "no image" when I reboot into FASTBOOT. I am going to rest now... and allow the phone to be a phone for a few days, then retackle the issue.
But, thank you so much for your
If you have the PH98IMG.zip on your sd card when you are in hboot, then you will have to make a choice to do the update or not. That is the only option you will ever have, thus the reason for deleting it as part of the first things that you do on an install.
If you do not have the PH98IMG.zip on your sd card and boot into hboot, it will run that script that you see and say "no image" That is just the way it is. It is checking for the .zip file. Its nothing to worry about.
I read the wonderful "Don't Panic" sticky, but I think I need a more drastic fix.
SHORT VERSION:
TWRP keeps saying, "Unable to mount /sdcard", and "unable to mount internal storage". I can't boot past the HTC screen, and my attempts to flash a ROM have failed due to those errors.
LONG VERSION:
I tried using TWRP 2.2.1 and Cyanogenmod 10 today, my first time flashing a custom ROM.
My phone (HTC EVO 4G LTE) was already rooted using the plain ol' HTC bootloader unlocking method.
I booted into recovery and performed a backup first. That appeared to go okay, and verified a backup existed on my external SD card.
I booted back into the OS and used ROM Toolbox to download the ROM and gapps thingy, wiped the cache and dalvik's cache. The phone rebooted and started wiping the cache and stuff. I went away for a bit.
When I came back thirty or so minutes later, the phone was all black. No lights at all despite being plugged into the AC adapter.
I came back about thirty minutes after that, and the same thing. I rebooted. The phone went to the HTC screen and then blacked out again. I rebooted into recovery. I figured the ROM didn't get flashed right, so I went to flash it again. I used the file manager in TWRP and saw that the directories /sdcard /sdcard2 and /sd-ext were completely empty, except /sdcard had a TWRP directory, which was empty. I didn't see any of my storage!
I set up ADB on my Mac and tried mounting my sdcard. No dice. I tried using fastboot to flash a ROM. Everytime I tried to do that, I got an error in TWRP, "unable to mount /sdcard", "unable to mount internal storage". I tried using fastboot to flash the .zip on my Mac, and tried using "adb put" to move the .zip to the phone and install from there. Same result.
Any ideas?
GoogleFap said:
I read the wonderful "Don't Panic" sticky, but I think I need a more drastic fix.
SHORT VERSION:
TWRP keeps saying, "Unable to mount /sdcard", and "unable to mount internal storage". I can't boot past the HTC screen, and my attempts to flash a ROM have failed due to those errors.
LONG VERSION:
I tried using TWRP 2.2.1 and Cyanogenmod 10 today, my first time flashing a custom ROM.
My phone (HTC EVO 4G LTE) was already rooted using the plain ol' HTC bootloader unlocking method.
I booted into recovery and performed a backup first. That appeared to go okay, and verified a backup existed on my external SD card.
I booted back into the OS and used ROM Toolbox to download the ROM and gapps thingy, wiped the cache and dalvik's cache. The phone rebooted and started wiping the cache and stuff. I went away for a bit.
When I came back thirty or so minutes later, the phone was all black. No lights at all despite being plugged into the AC adapter.
I came back about thirty minutes after that, and the same thing. I rebooted. The phone went to the HTC screen and then blacked out again. I rebooted into recovery. I figured the ROM didn't get flashed right, so I went to flash it again. I used the file manager in TWRP and saw that the directories /sdcard /sdcard2 and /sd-ext were completely empty, except /sdcard had a TWRP directory, which was empty. I didn't see any of my storage!
I set up ADB on my Mac and tried mounting my sdcard. No dice. I tried using fastboot to flash a ROM. Everytime I tried to do that, I got an error in TWRP, "unable to mount /sdcard", "unable to mount internal storage". I tried using fastboot to flash the .zip on my Mac, and tried using "adb put" to move the .zip to the phone and install from there. Same result.
Any ideas?
Click to expand...
Click to collapse
this seem to becoming a more frequent problem maybe something TWRP is responsible for i came to this same obstacle when trying to flash a new rom like a week ago. i tried all the nifty moves i could but no luck even went to sprint looking for answers ultimately i was forced to format (with windows) both internal and external SD. end result. yep u got it i lost everything almost 26gigs of music and files i had backed up no where else. so i formatted (heart broken) got over it now i back up files daily on my laptop thats the only way ive come to see out of this one. but check around forums a solution might work for i saw a couple didnt work for me tho.
JB ROMs rewrites the addresses of your SD cards, good chance the internal is corrupted. Boot to recovery and go to mount/mount USB storage, if you have windows then as soon as you plug it in windows will tell you to reformat, if you have Mac or Linux manually reformat the card
Thanks for the replies, guys.
Tried reformatting, but that didn't seem to help. On #twrp on freenode, they said it looked from my recovery.log that the internal and sdcard storage is hosed, and the maintainer of TWRP said to RUU back to stock. SIGH. . . .
So, since I don't have Windows at work, going to try these at home tonight:
(Great. Was trying to post links, but wasn't allowed. Suffice it to say, I was going to post my recovery.log link and the links to the instructions I am going to follow to RUU back to stock.)
Well that sucks, I'm lucky that I haven't hosed my emmc yet. I can't decide whether to stay on aosp or not, must have flashed back and forth a million times by now
Argh!
I have tried every RUU scenario I can find, and remain unable to mount my sdcard or my internal storage, have no ROM, am contemplating getting drunk. Anyone have any other ideas?
Anyone know if Sprint will fix this, or should I just cash in on my phone replacement plan?
I'd like to know what happened to mess this up so I can avoid it next time. What must have happened for my internal storage to not only be wiped -- I think I get that part -- but why can't it be mounted???? I don't get it.
GoogleFap said:
Argh!
I have tried every RUU scenario I can find, and remain unable to mount my sdcard or my internal storage, have no ROM, am contemplating getting drunk. Anyone have any other ideas?
Anyone know if Sprint will fix this, or should I just cash in on my phone replacement plan?
I'd like to know what happened to mess this up so I can avoid it next time. What must have happened for my internal storage to not only be wiped -- I think I get that part -- but why can't it be mounted???? I don't get it.
Click to expand...
Click to collapse
Did you ever find a solution to this? I'm in the same boat...
llaen said:
Did you ever find a solution to this? I'm in the same boat...
Click to expand...
Click to collapse
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
onefasttreopro said:
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I had backed up my sdcard so I didn't really care about not losing it. I think the problem was at least partially caused by having it encrypted.
I ended up flashing to stock and it let me format the sdcard from within the phone - that did it.
Thanks for the suggestion.
onefasttreopro said:
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
This just advice just saved my life. I thought for sure I bricked my phone, and right before memorial day weekend toooo! I did run into issue with the latest Lollipop RUU. I had to resort to using the old Kit Kat RUU I had saved to my computer from before. It worked like a charm.