Database Info

[Q] Bootloader No Image - Wrong Image

Hi all,
After flashing numerous ROMS on my Sensation, when I'm in the Bootloader, I notice the following:-
PG58DIAG - Shows up as No Image or Wrong Image
PG58IMG - Also shows up as No Image or Wrong Image
Any ideas what it means and how I correct it?
Thank You

someone please correct me if im wrong, just trying to spread some knowledge that I've learned in my adventures.
PG58IMG is the radio
so maybe whatever rom your currently trying to flash requires a certain radio. check the posting for recommended radio and apply before flashing
again just my assumption maybe an elder can step in and give a more accurate answer.

well i ma not here to solve your problem but i have the same problem with you , just for the precesion i thing The pg58img is a zip file with which you can install a radio img file and recovery img file and perhaps boot.img ( but for that i am not sure at all) .
this wrong image thing made me conclude that my recovery is corrupted ( precision my recovery is stock and i am s on ) so if anybody has a solution i will take it .
for your problem try to copy on the root of sdcard the PG58IMG.zip file corresponding to the stock recovery or the clockwork recovery, and reboot again in boot loader
---------- Post added at 09:27 AM ---------- Previous post was at 09:13 AM ----------
i began a new quote not to begin a new question: infact the "Do you want to start the update" does not show up on my sensation on bootloader, i tried to flash the recovery by adb no succes , terminal emulator with temp root , no success also , could somebody help please

kurtish said:
Hi all,
After flashing numerous ROMS on my Sensation, when I'm in the Bootloader, I notice the following:-
PG58DIAG - Shows up as No Image or Wrong Image
PG58IMG - Also shows up as No Image or Wrong Image
Any ideas what it means and how I correct it?
Thank You
Click to expand...
Click to collapse
So was there ever an answer for this? I'm getting the same thing... as well has a whole pile of roms that just wont boot past the splash screen.
One rom loaded, but couldn't start the wifi

[Q] HTC sensation bootscreen loop

Hi there. I've read some advices for similar problem, but i couldnt find any solution to this.
My girlfriend tried to flash her rom in Sens and i think she made it bad
I know, that she unlocked her bootloader (1.27) with htc dev page. She flashed touch CWM as a recovery.img and she used partitioning function on her SD card by CWM. It earased her backups etc (yea, cool , isnt it ? ). Form this moment she couldnt mount usb storage and connect phone to the pc in CWM mode. She rebooted system and copied OrDRoid and Sharpy ROM's to the SD. Rebooted to recovery, and she... did full wipe and dalvik cache wipe. Flashed with Sharpy ROM and now... it's the best moment
She forgot to flash the radio, and she didn't read any of instructions in the topic of rom. She just did it like I do it in my desire
So, the question is, how to bring it all alive ? Now there's unending bootscreen loop and i rly donno what to do... I hope u guys will help me with this coz she's now shou ting etc all the time
---
more info::
modelid: PG5813000
cidnum: HTC__032
hboot 1.27.1100

If bootloader is still accessible, i would recommend the following steps
1- Get superCID (i would recommed but its not neccesary)
2- Flash the latest firmware 3.32.x.x (Put the PG851MG file on root of sd card)
3- delete the PG851MG file from sd card
4- do a full wipe and then flash the ROM. (which should be on the root of sd card)
http://forum.xda-developers.com/showthread.php?t=1192300
Use the link. Its quite usefull.

Yeah. She did all that but she needed you to post this question. This question that's been asked a billion times and answered 2 billion times already.

debarox said:
If bootloader is still accessible, i would recommend the following steps
1- Get superCID (i would recommed but its not neccesary)
2- Flash the latest firmware 3.32.x.x (Put the PG851MG file on root of sd card)
3- delete the PG851MG file from sd card
4- do a full wipe and then flash the ROM. (which should be on the root of sd card)
http://forum.xda-developers.com/showthread.php?t=1192300
Use the link. Its quite usefull.
Click to expand...
Click to collapse
NO!!! HTC DEV DOESN'T GIVE S OFF! DON'T DO THIS.
Please follow this guide.
Skip the HTC Dev step since you have already done it.

@debarox.
i tried it, but it's all ending at parsing, rebooting the phone to bootloader, parsing and phone goes off ;] with no effect
@kgs1992
mhm
you're right, there is still s-on coz she only unlocked access to flashing the rcovery
i'll try later to do it
@Kevc44485
successfull troll is succesfull isnt it?
I tried your 2 billions advices and all of them ends with no effect

Tell your girlfriend, I.e. yourself, to start the phone in boot loader, click on fast boot, plug in her (your) phone to the PC and run the proper ruu. And next time make sure your girlfriend (you) pays attention to what she's (you are) doing. Maybe she (you) shouldn't flash anymore phones.

man ... the computer won't see my phone in fastboot if it doesnt work in usb storage mode in cwm so i can't use RUU. this is the reason why i'm here writing these posts
maybe u're schizophrenic and you can mistake hand with another person, whatever, i'm not you .
I didn't have problems with flashing any of MY phones but i can't (yes u're right, i can't) fix up someone's mistakes if i don't know the phone ;]

I think when its plugged into the computer in fastboot mode the computer should install the drivers automatically. Mine did.
---------- Post added at 04:51 AM ---------- Previous post was at 04:48 AM ----------
evnee said:
man ... the computer won't see my phone in fastboot
Click to expand...
Click to collapse
Ah lol caught you. It is your phone. Haha LMAO!!!
Who's a schizophrenic?

Another possible problem might be that you don't have the appropriate firmware.
Do you have 3.32.x.x firmware? If not, follow this, Use 3rd method:
Step 1. Flashing 4EXT recovery touch
To dowload and install the newest version of 4ext recovery TOUCH (v1.0.0.5 RC3). Use one of the following methods provided:
Third method: Download this file, check the MD5 of the zip and install it following the steps 4 and 5 from post#1 in this thread.
NOTE: File used in third method WILL NOT install the needed 3.32 firmware in any way, only contains the recovery.img to flash 4ext recovery touch.
Updating the firmware
This step is MANDATORY otherwise your ROM will not boot.
After updating the firmware you will have the 3.32 firmware with unlocked bootloader. Which basically means that you can use advanced fastboot commands, such as: flash new radios and splashscreens
Download compatible firmware from here.
Copy the PG58IMG.zip file you've downloaded to the root of the sdcard. Root of the sd card mean that you can't put the file inside any folder. Also, you can't rename the file. Please keep the PG58IMG otherwise the bootloader won't recognize it.
Power off your phone or remove the batt and put it back again.
Hold volume-down + power button to boot into the bootloader
Wait for the firmware package to be found and confirm to update as prompted
Once it completed successfully and prompted you to reboot, pull the battery out.
Connect your SD card to the PC and remove the PG58IMG.zip file.
Quoted from here
.
Click to expand...
Click to collapse
Perform a SuperWipe. It can be found at the end of this post.
Now, just flash a compatible ROM & you're good to go.
If you follow all these steps, I am a 100% positive your device will boot perfectly.

yea we have another problem
it's completely disharged and when i try to connect and charge it only blinks the orange light ; o

Well princess, you're **** outta luck.

Do you have any other way of charging it?
Try plugging in the charger elsewhere. Remove & re-insert the battery.
Also, I have edited the previous post with steps for you to follow since you can't use adb or fastboot. Please read through that and follow it.

k. not bad. i''ve got fully chargd battery and 4-ext recovery touch. firmware 3.32.
now i need any rom for that firmware and s-on... xd

HTC Status AT&T rom 2.14.502.2

Here it is for those who need it. I needed it to flash my phone back to stock. The update that was pushed out recently would not work on my rooted phone because I was using a UK rom when I rooted it so I need a stock ('merica) AT&T Status rom that no one seemed to have for any reason. I found the latest update on the HTC website and downloaded their installer, and that failed too. It wouldn't authorize... So into the trash InstallShield exe I went a digging and riped this out of the .cab
I used fastboot to flash the userdata.img, system.img, boot.img and recovery.img to my Status. Rebooted and did a factory reset. SUCCESS. :good:
Download Here:
http://www.mediafire.com/download.php?ncwqh41qa4ry7hi

Lucky-Casper said:
Here it is for those who need it. I needed it to flash my phone back to stock. The update that was pushed out recently would not work on my rooted phone because I was using a UK rom when I rooted it so I need a stock ('merica) AT&T Status rom that no one seemed to have for any reason. I found the latest update on the HTC website and downloaded their installer, and that failed too. It wouldn't authorize... So into the trash InstallShield exe I went a digging and riped this out of the .cab
I used fastboot to flash the userdata.img, system.img, boot.img and recovery.img to my Status. Rebooted and did a factory reset. SUCCESS. :good:
***Going to have to message me to get the download link because this wont let me post it yet.***
Click to expand...
Click to collapse
Have you found something new with this update?

bungphe said:
Have you found something new with this update?
Click to expand...
Click to collapse
Haven't seen anything new yet.
Just pulled this from HTC's website:
"HTC Status™ for AT&T ROM Update | 05.3.2012
Starting May 3rd 2012, HTC will be rolling out a system update for the HTC Status.
This update will only be available for AT&T HTC Status customers and will be sent to the device over the air. Once the release is ready, users will receive a notification on their device advising them of this update and provide instructions to receive and install it. Users can proactively check for this update by going to Home > Menu> Settings > AT&T Software Update > Check for updates.
As an alternative solution, the system update can be downloaded to a PC and manually applied to the device. See the section at the bottom of these instructions for more information.
This system update includes:
Memory allocation fixes to improve low memory issues
Data throttling fix"

So the device is unrooted again?
Did they really solve the low memory issue?
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
Please tell me how to download and flash the rom, thanks.

slow_kknd said:
So the device is unrooted again?
Did they really solve the low memory issue?
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
Please tell me how to download and flash the rom, thanks.
Click to expand...
Click to collapse
My device is now unrooted and I don't really see a reason to root it again. I also never ran into the low memory issue so I can not answer that question. I'll pm you the link...

thanks
Lucky-Casper said:
Here it is for those who need it. I needed it to flash my phone back to stock. The update that was pushed out recently would not work on my rooted phone because I was using a UK rom when I rooted it so I need a stock ('merica) AT&T Status rom that no one seemed to have for any reason. I found the latest update on the HTC website and downloaded their installer, and that failed too. It wouldn't authorize... So into the trash InstallShield exe I went a digging and riped this out of the .cab
I used fastboot to flash the userdata.img, system.img, boot.img and recovery.img to my Status. Rebooted and did a factory reset. SUCCESS. :good:
***Going to have to message me to get the download link because this wont let me post it yet.***
Click to expand...
Click to collapse
nice, i need to fix one, the one you downloaded is htc_status_mr_update_2.14.502.2_us.exe? and when i 7unzip, i only see:
.rsrc - folder
.data
.rdata.text
certificate and
a [0] file of 161,869 kb
so how did you got userdata, system and boot from this file?
thank you very much indeed
atv

atv said:
nice, i need to fix one, the one you downloaded is htc_status_mr_update_2.14.502.2_us.exe? and when i 7unzip, i only see:
.rsrc - folder
.data
.rdata.text
certificate and
a [0] file of 161,869 kb
so how did you got userdata, system and boot from this file?
thank you very much indeed
atv
Click to expand...
Click to collapse
First I used Universal Extractor to extract the files properly from htc_status_mr_update_2.14.502.2_us.exe, because of it being an Install Shield installer. Once it extracted the files in the correct structure I then had to use ZIP Scan on the data1.cab file because Install Shield uses its cab format and very few programs can export them correctly. Once you extract data1.cab you will have all that you need.

hi again
i really want to thank you for your help, the phone was stuck at cmw (s-on) and now its back, but i think that as your post, i should have flashed, userdata.img before, and i did it boot.img then system.img and then i could not flash the userdata.img but the phone turned on finally.
see attached
take care
wilston
atv

atv said:
i really want to thank you for your help, the phone was stuck at cmw (s-on) and now its back, but i think that as your post, i should have flashed, userdata.img before, and i did it boot.img then system.img and then i could not flash the userdata.img but the phone turned on finally.
see attached
take care
wilston
atv
Click to expand...
Click to collapse
Glad I could help my friend!

this is not ICS?

stayfidz said:
this is not ICS?
Click to expand...
Click to collapse
Of course it is! This is the official ICS from HTC, you can read it here: http://www.htc.com/www/help/android4faq/?cid=android4blog

stayfidz said:
this is not ICS?
Click to expand...
Click to collapse
Still GB.

stayfidz said:
Alex C.
1.You confused me, saying it was just a kernel!
2. I've a uk phone, can i install this US on mine?
3. CM9 is way Tard right now?
Re
Click to expand...
Click to collapse
You can install any one your phone. I have had the Asian and UK roms installed before but I would still suggest staying with your region.

Some issues with RUUs and ROMs

Hey all,
I've had my T-Mobile One S for a while. I finally rooted it about a month ago, after I switched to Verizon and picked up a Droid DNA. I'm only using my One S for apps that are not updated to support my DNA. My issues are a little strange, I haven't found anyone else posting the RUU errors I get or having the same issue changing ROMs as I am having after reading for almost a month.
I can only install JellyBam 4.0.0 and fully boot. I have tried many ROMs and only JellyBam works with my phone. Since I was having so much trouble with ROMs, I decided I would go back to stock and start over. NONE of the RUUs will complete successfully. I get this error: FAILED (remote: 02 data length is too large). Basically the RUU is telling me that my phone's system partition is too small to be flashed with the RUU image.
I have been rooted and flashing since the early days of my G1, before Cupcake was released, I am not new to that aspect. I have followed the methods as written in each respective thread. With the RUUs, I have tried locked, unlocked, stock recovery, TWRP, and CWM. I also tried flashing it by grabbing the firmware.zip out of the temp folder and doing a fastboot flash zip firmware.zip in RUU mode. I have tried this with superCIDs 11111111 and 88888888 as well as HTC__001 and the T-MOB010. I pass the CID check.
It would be nice to install different ROMs, but I would rather be able to put in stock firmware from a RUU that can get OTA updates so that I could sell it if I feel like it.
Anyone have any idea as to what is going on with my phone? Did my partition size change somehow with S-ON?
HBOOT is 1.14 and I was on the 4.0.4 OTA before rooting.

dclaw_fantum said:
Hey all,
I've had my T-Mobile One S for a while. I finally rooted it about a month ago, after I switched to Verizon and picked up a Droid DNA. I'm only using my One S for apps that are not updated to support my DNA. My issues are a little strange, I haven't found anyone else posting the RUU errors I get or having the same issue changing ROMs as I am having after reading for almost a month.
I can only install JellyBam 4.0.0 and fully boot. I have tried many ROMs and only JellyBam works with my phone. Since I was having so much trouble with ROMs, I decided I would go back to stock and start over. NONE of the RUUs will complete successfully. I get this error: FAILED (remote: 02 data length is too large). Basically the RUU is telling me that my phone's system partition is too small to be flashed with the RUU image.
I have been rooted and flashing since the early days of my G1, before Cupcake was released, I am not new to that aspect. I have followed the methods as written in each respective thread. With the RUUs, I have tried locked, unlocked, stock recovery, TWRP, and CWM. I also tried flashing it by grabbing the firmware.zip out of the temp folder and doing a fastboot flash zip firmware.zip in RUU mode. I have tried this with superCIDs 11111111 and 88888888 as well as HTC__001 and the T-MOB010. I pass the CID check.
It would be nice to install different ROMs, but I would rather be able to put in stock firmware from a RUU that can get OTA updates so that I could sell it if I feel like it.
Anyone have any idea as to what is going on with my phone? Did my partition size change somehow with S-ON?
HBOOT is 1.14 and I was on the 4.0.4 OTA before rooting.
Click to expand...
Click to collapse
I imagine you know all about relocking your bootloader and having your phone in bootloader before trying the RUU... I also imagine you have verified your RUU downloadusing md5 checksums? And of course, flashed stock recovery before relocking?
You can also wait for the OTA update for T Mobile... There are a few custom ROMs that will allow a download of it... Even if they dont im sure someone will post the OTA, which you can then download to your SD Card, flash stock recovery and update from there...

Yep. I've been through a bunch of steps. Started in bootloader and locked. I have tried OTAs already, the stock recovery errors, then if I choose any option it errors an reboots my phone. MD5s are good.
Sent from my HTC6435LVW using xda app-developers app

dclaw_fantum said:
Yep. I've been through a bunch of steps. Started in bootloader and locked. I have tried OTAs already, the stock recovery errors, then if I choose any option it errors an reboots my phone. MD5s are good.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
The fact that the stock recovery errors is a big flag... You need the stock recovery to pus the RUUs since its the stock recovery that has proprietary processes to flash all the relevant partitions for updates.
I would try finding another download for the stock recovery... Get that right first.... See what you can do there.
You may have already tried this though but Im just suggesting... It may be your phone is S3 and not S4? Its probably S4 but again, just asking..
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
Also,
If your having issues flashing stock recovery, or accessing any type of recovery for that matter, I wonder if you have somehow corrupted that partition. You may need to use busybox and linux commands to reformat that particular partition. It would be something similar to what I have here http://forum.xda-developers.com/showthread.php?t=2086156 but you may need to use some mkfs or some sort of emmc formatter (TWRP recovery logs suggest its an emmc file system), and also point towards the recovery partition which I believe is mmcblk0p22. However, Im not entirely sure you would have write access to that partition...
Anyways I would only try that if I am 100% sure I have a proper signed stock recovery (ie properly downloaded md5sumed etc) and I am 100% sure of the mmcblk partition I am formating
---------- Post added at 01:23 PM ---------- Previous post was at 01:12 PM ----------
AKToronto said:
The fact that the stock recovery errors is a big flag... You need the stock recovery to pus the RUUs since its the stock recovery that has proprietary processes to flash all the relevant partitions for updates.
I would try finding another download for the stock recovery... Get that right first.... See what you can do there.
You may have already tried this though but Im just suggesting... It may be your phone is S3 and not S4? Its probably S4 but again, just asking..
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
Also,
If your having issues flashing stock recovery, or accessing any type of recovery for that matter, I wonder if you have somehow corrupted that partition. You may need to use busybox and linux commands to reformat that particular partition. It would be something similar to what I have here http://forum.xda-developers.com/showthread.php?t=2086156 but you may need to use some mkfs or some sort of emmc formatter (TWRP recovery logs suggest its an emmc file system), and also point towards the recovery partition which I believe is mmcblk0p22. However, Im not entirely sure you would have write access to that partition...
Anyways I would only try that if I am 100% sure I have a proper signed stock recovery (ie properly downloaded md5sumed etc) and I am 100% sure of the mmcblk partition I am formating
Click to expand...
Click to collapse
As an absolute last resort, I would try using the bootloader downgrade method shown in the Dev section but instead of reflashing a bootloader, flash an image to the recovery partition. This would more or less force the image to take... I think... But I cant say ive tried it. Could have other risks

Couple questions
AKToronto said:
I .. I also imagine you have verified your RUU downloadusing md5 checksums? And of course, flashed stock recovery before relocking?
Click to expand...
Click to collapse
How do you verify checksums?
Do you mean we need to flash stock recovery before we start the process and lock bootloader initially?
Where would we find the stock recovery or do we use the one in the temp folder during the install?

AKToronto said:
The fact that the stock recovery errors is a big flag... You need the stock recovery to pus the RUUs since its the stock recovery that has proprietary processes to flash all the relevant partitions for updates.
I would try finding another download for the stock recovery... Get that right first.... See what you can do there.
You may have already tried this though but Im just suggesting... It may be your phone is S3 and not S4? Its probably S4 but again, just asking..
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
Also,
If your having issues flashing stock recovery, or accessing any type of recovery for that matter, I wonder if you have somehow corrupted that partition. You may need to use busybox and linux commands to reformat that particular partition. It would be something similar to what I have here http://forum.xda-developers.com/showthread.php?t=2086156 but you may need to use some mkfs or some sort of emmc formatter (TWRP recovery logs suggest its an emmc file system), and also point towards the recovery partition which I believe is mmcblk0p22. However, Im not entirely sure you would have write access to that partition...
Anyways I would only try that if I am 100% sure I have a proper signed stock recovery (ie properly downloaded md5sumed etc) and I am 100% sure of the mmcblk partition I am formating
---------- Post added at 01:23 PM ---------- Previous post was at 01:12 PM ----------
As an absolute last resort, I would try using the bootloader downgrade method shown in the Dev section but instead of reflashing a bootloader, flash an image to the recovery partition. This would more or less force the image to take... I think... But I cant say ive tried it. Could have other risks
Click to expand...
Click to collapse
The stock recovery is working, it errors when it tries to mount cache or the SD card. I can mount the SD in TWRP and CWM. It also mounts as a USB drive in Windows. I'm trying my hardest to get this to take other files without doing the HBOOT downgrade. I don't like bringing down my main PC for any reason. I have checked the MD5s each time, all is good with that. I have a sneaking suspicion that it the FS on one or more partitions may be different than factory and is causing the issue. Going to have to find a table of the factory partition FS structure before I jump to messing with the HBOOT downgrade.

I have just recently ran an RUU, however, I did not flash the stock recovery beforehand. All I did was relock the bootloader and run the RUU. It seemed to work fine, but I am having some wifi and airplane mode issues and I also can not update the software. Is this because I did not flash the stock recovery beforehand? and if so, what can I do to fix the problem? I ran the 2.35 RUU that was recently posted, thanks in advance

MY BRICKED HTC ONE A9 won't flash custom ROM via TWRP

Somebody should please help me, if I'm posting wrongly or in the wrong section, I do not know, I am new here and I need help. I have searched and read countless posts on here but I still can't get a solution.
I modified a build.prop file in the root explorer of my phone (in an attempt to increase the "max. number of connections" under my Hotspot settings which was limited to 1 and I restarted, phone got stuck on the HTC white screen. After 24hours, I decided to install the stock rom back on it.
I downloaded this officially from the HTC website
RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.10
when I run the file, it will start then disappear into thin air (I use windows 8.1 on my computer).
so I decided to go in the way of custom roms, phone is already S-OFF and Bootloader UNLOCKED. I installed adb & fastboot, I flashed TWRP and was able to boot into twrp recovery.
I downloaded the first custom rom (can't remember from where I downloaded that) and from the instructions, I was told to rename it to 2PQ9IMG.zip which I did and in attempt to flash it, got this error code,
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
Error flashng zip '/sdcard/2PQ9IMG.zip'
I had to go download another custom rom with the below file name
OTA_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.1-1.57.617.60_release_493556mv4q5xb4fbi8qvyk
and in attempt to install this as well, I got the errors below
Checking for MD5file...
Skipping MD5 check: no MD5 file found
N70QCT.01.000.004
E:unknown command [set_err_msg]
E3004: This package is for "htc_hiaeul" devices; this is a "htc_hiaewhl"
E:Updater process ended with ERROR=7
Error flashing zip '/sdcard/OTA....................
then this fourth rom again.
Sprint-A9-1.57.651.1
which I believed should work perfectly after a lot of research and in attempt to install this rom, I got this error
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
I am now totally fed up, I have been having a bad phone for 4 days now and I need my phone back ASAP. Somebody should please help me as a noob with the simplest well understood instructions, I will show gratitude.

mneynaire said:
Somebody should please help me, if I'm posting wrongly or in the wrong section, I do not know, I am new here and I need help. I have searched and read countless posts on here but I still can't get a solution.
I modified a build.prop file in the root explorer of my phone (in an attempt to increase the "max. number of connections" under my Hotspot settings which was limited to 1 and I restarted, phone got stuck on the HTC white screen. After 24hours, I decided to install the stock rom back on it.
I downloaded this officially from the HTC website
RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.10
when I run the file, it will start then disappear into thin air (I use windows 8.1 on my computer).
so I decided to go in the way of custom roms, phone is already S-OFF and Bootloader UNLOCKED. I installed adb & fastboot, I flashed TWRP and was able to boot into twrp recovery.
I downloaded the first custom rom (can't remember from where I downloaded that) and from the instructions, I was told to rename it to 2PQ9IMG.zip which I did and in attempt to flash it, got this error code,
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
Error flashng zip '/sdcard/2PQ9IMG.zip'
I had to go download another custom rom with the below file name
OTA_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.1 8.617.1-1.57.617.60_release_493556mv4q5xb4fbi8qvyk
and in attempt to install this as well, I got the errors below
Checking for MD5file...
Skipping MD5 check: no MD5 file found
N70QCT.01.000.004
E:unknown command [set_err_msg]
E3004: This package is for "htc_hiaeul" devices; this is a "htc_hiaewhl"
E:Updater process ended with ERROR=7
Error flashing zip '/sdcard/OTA....................
then this fourth rom again.
Sprint-A9-1.57.651.1
which I believed should work perfectly after a lot of research and in attempt to install this rom, I got this error
E:Could not find 'METAINF/com/google/android/update-binary' in the zip file.
I am now totally fed up, I have been having a bad phone for 4 days now and I need my phone back ASAP. Somebody should please help me as a noob with the simplest well understood instructions, I will show gratitude.
Click to expand...
Click to collapse
File name starting with "OTA" are ota updates (patches) not full rom and can't be used to restore a phone. Renaming files "2PQ9IMG.zip" is used only when flashing RUU.zip or Firmware.zip in bootloader mode using the sdcard, not for flashing custom rom in TWRP. TWRP can't be used to flash RUU.zip or Firmware.zip. If your phone is a whl variant (Sprint) use the Sprint RUU or follow the guide to convert to Us Unlocked. Good information about RUU in the ruu collection thread at post #2. If you need more help tell us your CID, MID and version-main and what your goal is (re-flash the sprint RUU or convert to US Unlocked).

mneynaire said:
I modified a build.prop file in the root explorer of my phone (in an attempt to increase the "max. number of connections" under my Hotspot settings which was limited to 1 and I restarted, phone got stuck on the HTC white screen. After 24hours, I decided to install the stock rom back on it.
Click to expand...
Click to collapse
How are you rooted? If you can, boot into TWRP, pull your data off it, and then I'd say your easiest option is to start fresh using an RUU. Download and run the full RUU.exe for your Sprint phone following the instructions from the RUU thread.