HTC One M9 Down - Need Help - One (M9) Q&A, Help & Troubleshooting

HI all. I am in serious need of help please.
My wifes M9 is stuck on a screen with only a backlight. How this came about is after several failed attempts of updating the system via Wi-Fi. South Africa does not have a RUU available and only over the air updates are available
After about 2 days on the net, searching and reading and trying and failing I have determined the following.
What I have tried
1. Boot to Bootloader and tried recovery. This give me an Error - "Failed to boot to recovery"
2. Tried a Official RUU from HTC, this failed due to CID - Error wrong Customer ID
3. Learned a bit of ADB but this is no use as It seems USB debugging is disabled on the phone
4. Tried Custom ROM's via the SD card but this is blocked as the phone is **Locked** and **S-On**
5. Fastboot sees the phone as I can push reboot commands but because of locked status I can not do much
6. I can not get a unlock token as OEM is locked and this must be unlocked for ADB command to get token to get unlock.bin from HTCDEV
Basically it seems like I am at a dead end as it appears that I need to get into a boot status to enable debugging and enable developer mode from phone settings to be able to work from ADB
So here is the Million dollar question, How can I "wipe" the phone with a SD card boot image/loader or does any one know of a RUU-.exe for South Africa CID_016 that I could flash the phone with or possibly any other methods to get a ROM on it that we can use it again
I repeat, phone goes to blank screen with only backlight after HTC Logo, S-on, USB debugging seems to be disabled and it is in Locked status. I am able to boot in download mode and bootloader and fastboor does see the device. ADB devices does not see the phone, even after trying loads of different drivers, ADB USB ADB Interface etc etc
Please I need help

I'm suffering from the same fate. Except I had rooted it before, then I tried to update it to 5.1 and I relocked my bootloader. Android 5.1 loaded successfully but it got stuck while booting and now I can't unlock my bootloader. I have tried EVERYTHING!

https://www.google.com/url?q=https:...261000&usg=AFQjCNEBlBxkVmymaiJO1eaxKcHsKsE-wg
1.download this zip file
2. Rename the file to 0PJAIMG.zip (zero not O)
03. Copy the file to the root directory of a SD card which is formatted to fat32
04. Put the card into your phone and boot to Download Mode.
05. You will be asked whether you want to flash the file. Confirm with the volume up button.
06. Your phone will reboot at least one time. Depending on your current firmware version it may reboot to Android instead of rebooting to Download Mode. If this happens you just need to shut your phone down and manually boot it to Download Mode.
07. Flashing may take some time.
08. At the end you will be asked to push the power button. You phone will shut down if you do so.
09. Wait some seconds and then turn your phone on, again.
10. First boot may take a while.
11. Congrats! thanks to flippy

YES!!! OP I tried this and it works!!! My phone is finally alive again thanks to flippy's instructions.

Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Thank you so much for taking the time to answer this Degerli43! I know virtually every answer possible is available on this forum, but finding it is the trick!
Note to anybody else doing this, be sure to locate the correct image file for your provider and area, as the link above and the one below may not be the correct one for you. I am a T-Mobile US customer and used this one -
https://www.androidfilehost.com/?w=...6ce7fb817fc1524b58f67fe05270f032107d2306abcd4
This worked perfectly after I could not boot or enter TWRP recovery. Anybody who can still access Android Recovery the Downloader should be able to use it to get un-bricked to a clean carrier state if the image file will take.

ksnax said:
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Click to expand...
Click to collapse
Did you ever visit the general section? :silly: There's a sticky thread with stock files and linked instructions for recovering TWRP backups and flashing RUUs. Read the OP, follow it's instructions to my google sheet and you will see where the steps that helped you out are taken from.
Sent from my HTC One S using XDA Labs

Related

Wildfire S digitizer and GoldCard

Hello!
I've changed digitizer but now it doesn't react on any touch. I tried to make GoldCard, but I can't enter to menu to change connection to debug mode. There is any other solution to make the GoldCard?
Thx for help.
haller said:
Hello!
I've changed digitizer but now it doesn't react on any touch. I tried to make GoldCard, but I can't enter to menu to change connection to debug mode. There is any other solution to make the GoldCard?
Thx for help.
Click to expand...
Click to collapse
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
jocke888 said:
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
Click to expand...
Click to collapse
I have had the same problem with the screen and the debugging, I did however find a kind of workaround for the debugging issue.
I searched for hours and hours for posts on how to enable debugging via ADB command line. The bottom line is that you can't. When I say you I mean "us plebs" can't. I have read the arguments about security and I say cool fair enough. I also noticed that when you run the RUU with the phone connected via USB the RUU activates "USB Debugging" on the handset irrespective of if it was enabled via the handset menu. I can understand this is done for obvious reasons as the RUU is supposed to be an easy way for end users to update their ROM's. It does however beg the question of how a stock ROM can alter the USB debugging switch on the phone via software/usb interface and the rest of the internet claims it is not possible via ADB/command line. Anyone who seems to ask about it is immediately suspected of being a phone thief and the forum responses become a mud slinging match.
So I did some experimenting with the HTC Wildfire S:
Basically I ran the RUU and left it on the Readme page running in the background I could then access the handset via ADB. I don't know ADB well but I was able to see the device listed using adb devices where as before I got nothing. When in Fastboot mode I saw that the handset was also receiving data via the Console on the PC using the fastboot reboot type commands.
It didn't really help me too much as all I wanted to do was update the stock ROM to see if it resolved my touchscreen issue. Unfortunately it didn't. So I'm still stuck with a fully functional handset minus the touchscreen.
I then decided to try and unlock the bootloader so that I could try with a custom ROM. Following the process on HTCdev I got a "Radio" update for the handset. At first I couldn't load it because the base ROM was too old. I found the latest update. It failed with a USB connection error. I found an older version about halfway back between what I had (X.1.33.X) and the new (X.2.16.X) this was (X.1.66.X). It worked but the "Radio" update still needed the latest version. I re-ran the latest RUU and it failed with the same error.
Determined to get it done here is what I did:
1. Re-Ran the (X.2.16.X) Installer
2. At Readme screen I navigated to the standard %TEMP% directory (it helps if u empty this first then you will see the dir the install creates easily)
3. I copied the entire contents to a folder on my desktop
4. Closed the (X.2.16.X) Installer and re-ran the (X.1.66.X) Installer
5. At the Readme screen I navigated back to the %TEMP% directory (it helps if u empty this first then you will see the dir the install creates easily)
6. I pasted and replaced all the files back. Now you get a lot of failures because the Intaller is runnning so I just skipped those files.
7. Went back to the installer running in the background and completed the process.
I used the older installer to flash the newer ROM. I have no idea which files (apart from the rom.zip) were critical but if you copy only the rom.zip it fails on the device when checking the security certificates.
After that I successfully flashed the "Radio" update. The next step in the HTCdev process is to get a device ID via a Flashboot command. I still couldn't do this because the touchscreen still wasn't working after the update. So I Re-Ran the (X.1.66.X) Installer and left it in the background. The phone went into debug mode and I could run the command. I got the info and completed the process with HTCdev. This gave me a unique file to unlock the boot loader.
I then used the same method to get into debug mode and used the HTC Wildfire S All-In-One Toolkit (http://forum.xda-developers.com/showthread.php?t=1809751) to unlock the bootloader with the file HTC sent me.
I now have an HTC Wildfire S with the latest stock ROM, Bootloader unlocked and still no working touchscreen. This took me the better part of 10 hours. When I have the energy to continue I'll try a installing Root and custom ROM.
I apologise in advance for the RUU version number above being severely shortened but they have so many versions of the RUU depending on where you are and who your provider is and such, you will need to do your own research on the specific RUU's you will need and where to get them. The method to get debug I have illustrated should not change if you use a different version of RUU. If you're lucky your stock ROM is also updated and you can skip that part or the RUU you do download works without the tweaking l had to do.
jocke888 said:
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
Click to expand...
Click to collapse
You have to install a custom recovery (CMW). If you enter recovery mode you can choose mounts and storage, and then mount USB storage. This way you enable usb mass storage. now you are able to get your CID

Stuck on splash screen

Hi guys I have a mytouch 3G slide and I was able to get the bootloader unlocked. However even before I unlocked the bootloader I was unable to get the phone to work it would stay at the mytouch slide splash screen. Im on the new hboot and a am able to get into fastboot and hboot. However when I click recovery in hboot it takes me to the tmobile slash screen and never gets into recovery. I have flashed the original recovery but still no luck. I can't reboot the phone all they way. Anyone know what's wrong?
Sent from my MB611 using Tapatalk 2
Anyone have a solution
Sent from my MB611 using Tapatalk 2
Hey Moe92,
I'm pretty much in the same situation as you!
I was given a phone to fix that has water damage, the owner disclosed that up front and I can see this based on the moisture sensor on the device.
The phone boots up and is stuck on the splash screen with out any activity after this. This is the same screen that I see when trying to enter recovery.
The only thing the phone can do is go into fastboot and hboot. Let me make a list of all the activities I have tried to perform and what ended up happening. As of now I still cannot fix the phone.
Device Details in Hboot
Code:
ESPRESSO PVT SHIP S-ON
HBOOT-1.02.0002
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.15.35.16
Dec 13 2001,11:34:01
The items I've performed so far are:
* Downloaded two different versions of ESPRIMG.zip and placed them on the SDCARD for the device. Neither loads up by the device and they both fail.
The MD5 hash for each version is: 892b885010563208edc3037dfec40425 and 9e80d53b4afa73ecf0d58f703831ac82
* Created a goldcard and tried to run the above two files with the same result.
* Tried to enter recovery from the device; ends up on the boot splash screen and hangs
* Tried to use fastboot to flash several recovery images: Clockwork 2.5.0.7, recovery-RA-Saphire-v1.7.0, recovery.img from the ESPRIMG.zip files
* Each time fastboot flashes the recovery sucessfully, but trying to get to it ends up with a boot splash screen hang.
I'm starting to believe the phone is bricked, or something occurred internally when it became wet. I have no idea what the software was on it prior to it being wet.
From your experience does this phone have any luck of being restored? I've spent two days looking over the threads and trying to avoid asking a question that may be answered; but have had no success.
Any help would be greatly appreciated.
dustbyter said:
Hey Moe92,
I'm pretty much in the same situation as you!
I was given a phone to fix that has water damage, the owner disclosed that up front and I can see this based on the moisture sensor on the device.
The phone boots up and is stuck on the splash screen with out any activity after this. This is the same screen that I see when trying to enter recovery.
The only thing the phone can do is go into fastboot and hboot. Let me make a list of all the activities I have tried to perform and what ended up happening. As of now I still cannot fix the phone.
Device Details in Hboot
Code:
ESPRESSO PVT SHIP S-ON
HBOOT-1.02.0002
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.15.35.16
Dec 13 2001,11:34:01
The items I've performed so far are:
* Downloaded two different versions of ESPRIMG.zip and placed them on the SDCARD for the device. Neither loads up by the device and they both fail.
The MD5 hash for each version is: 892b885010563208edc3037dfec40425 and 9e80d53b4afa73ecf0d58f703831ac82
* Created a goldcard and tried to run the above two files with the same result.
* Tried to enter recovery from the device; ends up on the boot splash screen and hangs
* Tried to use fastboot to flash several recovery images: Clockwork 2.5.0.7, recovery-RA-Saphire-v1.7.0, recovery.img from the ESPRIMG.zip files
* Each time fastboot flashes the recovery sucessfully, but trying to get to it ends up with a boot splash screen hang.
I'm starting to believe the phone is bricked, or something occurred internally when it became wet. I have no idea what the software was on it prior to it being wet.
From your experience does this phone have any luck of being restored? I've spent two days looking over the threads and trying to avoid asking a question that may be answered; but have had no success.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Actually sometimes and this rarely happens... I can load into the welcome screen but everythine that happens, the phone is in safe mode. When I power down the phone it goes back to the splash screen and hangs there. I have to keep flashing the Tom many many time and pray that it gets into the welcome screen again.
BTW I can unlock the bootloader. Does anyone know what I can do after I unlock the boot loader?. I tried to flash zips via fadtboot but got the error where it cannot determine the signature. When unlocking the hboot, are there specific things I can do via fastboot? Please let me know. Thanks
I have also unlocked the bootloader by using the token provided by htcdev.
What zip did you try to flash to yours? I haven't tried that from fastboot yet. I only tried to flash each component of the ESPRIMG using fastboot with out any luck.
Moe,
Do you have any information on how to boot the device into safe mode?
I tried to use fastboot to flash an update.zip but that method did not work either :crying:
Does anyone have access to the ESPDIAG.zip for this device?
Ran out of ideas at this point .
dustbyter said:
I have also unlocked the bootloader by using the token provided by htcdev.
What zip did you try to flash to yours? I haven't tried that from fastboot yet. I only tried to flash each component of the ESPRIMG using fastboot with out any luck.
Click to expand...
Click to collapse
well when i unlocked the bootloader. i then decided to relock it. once i relocked it. i went to the HTC website and got the 2.2.1 RUU. once the RUU downloaded, i reloaded the phone with the firmware and once it was done, it booted o the entire OS but it was in safe mode. i didnt press any buttons for it to get into safe mode. it went in by itself...
also when i shut the phone off and truend it back on, i was back in square one where i was stuck in the boot loader screen.
Also you can extract the original ESPRIMG.zip file from the offical 2.2.1 ruu. In order to extract the .zip file, you first have to run the RUU. Once you click on the Downloaded RUU program, let it run. once the first page of the RUU comes up, follwo the below directions to extract the .zip file. DO NOT flash the phone with RUU if you want to extract the .zip file.
Here are the step by step instructions
1. open my computer
2. click on the main drive. (for me it was the C: drive)
3. click on users
4. click on you computer name (the one that has the lock on it)
5. click Appdata. (appdata is a hidden folder. to un-hide it, click---> Organize/Folder and search options/view/ scroll down to hidden files and folders/ click on show all files and folders)
6. click on Local (NOT Locallow or Roaming)
7. click on Temp
8. when you get into the folder, sort the files to the DATE MODIFIED
9. when you have it sorted, you will see some folders such as ({95153F7E-B880-4656-B55D-54DD7869F984}), the name of the folders can and will be different. open each folder and when you come across a folder that has the ADB application, scroll down the folder until you reach the LETTER "R". you will then see a .zip file named "rom". copy that file onto the desktop or any other folder. rename it to ESPRIMG.ZIP.
10. format your SD CARD to FAT32. once the format is complete, copy/move the extracted rom/ESPRIMG.zip file into the sd card.
11. put SD card in the phone.
12. Hboot should then detect the esprimg file.
google for mt3srooter
---------- Post added at 06:11 AM ---------- Previous post was at 06:03 AM ----------
open folder u would find esprimg dat de file mt3gs
Thanks! I'll check this out. Unfortunately I returned the phone to its owner, I'll have to get it back to see if I can resolve his issue.

Please help - seemingly bricked M9 after attempting to restore to stock

Hi all,
I'm in desperate need of help here, I purchased an already modified HTC One M9 (which i wasn't aware of when purchased) and have attempted to flash it back to Stock.
well i've made a real mess of it and I really don't understand what to do now if someone could help it would be greatly appreciated. as the phone currently stands:
I've somehow removed the TWRP and it boots into standard recovery
Its been wiped as a pre-req of a guide i followed to install the stock image so it wont boot at all
I can't get my PC to see it when i boot into Download mode, so ADB and fastboot do not see it.
I'm tearing my hair out and really wondering where i can go from here.
Any help is greatly appreciated.
Many thanks.
Several things that would be helpful to know, if you can:
About your phone
- your phone's carrier variant (AT&T, T-Mobile, developer, et cetera)
- what you can boot into (recovery, bootloader, download)
- are you S-ON or S-OFF (boot into bootloader, see upper left hand corner)
About your computer
- what drivers have you installed on your PC
- whether or not HTC Sync is installed on your PC
Depending on what you can boot into, an RUU is your safest option - you'll need to download the RUU that corresponds to your phone's carrier variant. Barring that, if you can boot into download mode, you should be able to install TWRP - which may open up some other options.
The carrier is a UK model unlocked factory so i'd imagine just the standard EU model.
I can get into Recovery which is the standard Android one, Bootloader and Download mode
S-ON which is what confuses me, alot of these posts are regarding S-OFF devices
UPDATE: I managed to figure out i was running 2.10.401.1 so i downloaded the corresponding file for it. Formatted an SD Card to FAT32 and put the file on named 0PJAIMG.zip
It looked like it was working but failed on System.img, the device rebooted and now its stuck on white HTC screen with the Green HTC logo.
I can't turn it off, its just stuck there, any ideas?
andyobmonkey said:
I can't turn it off, its just stuck there, any ideas?
Click to expand...
Click to collapse
I'm sorry for the late reply. I hope you've had better luck in the meantime. If not, you can force a reboot by pushing and holding the power button & volume up.
If you can reboot, see what you can boot into. From what little research I've attempted on your carrier's software offerings, I'm not seeing an executable RUU (ie, installable from Windows). If there is one, that is by far the most dependable way to restore your phone to stock condition.
If you're intent on using the SD card install method (or it is the only way), you might consider ensuring that it is a reliable card. A read failure in the middle of a firmware update might explain the install issues you're having.
Beyond that, I'm afraid I don't have any further advice; I've reached the end of my experience! But if you still need help, please post an update and let us know what is going on.
Get a fresh SD card and pop TWRP or CWM on it along with the stock image. Automatic recovery and 3 wipe there we go. I only got boot loops when I was using a corrupted SD. Also, try both the ones with the underscores replacing spaces and regular names. One of them seem to be a decoy, as far as I can see.
andyobmonkey said:
UPDATE: I managed to figure out i was running 2.10.401.1 so i downloaded the corresponding file for it. Formatted an SD Card to FAT32 and put the file on named 0PJAIMG.zip
Click to expand...
Click to collapse
That file is corrupted and shouldn't be used. You can try reviving your phone by using this RUU service since there is no working 2.10.401.1 RUU you could use.

HTC One M8s propably bricked HELP GUYS

Hi,
i just got an HTC One M8s and i think its propably bricked. I don't know whats owner of that phone done here. Its Software status : Modified, Bootloader: Locked, and S-ON.
I can't turn on the phone, i just can go to bootloader option and cant access recovery bc its popably didn't exist anymore.
I was trying to flash RUU for my CID T-MOB009 but htc_fastboot says "data length is too large" and sometimes "remote:signature verify fail", and i was trying to unlock this bootloader with HTCDev, but when i clicked yes it looks like that(means 1st photo) and just reboot to fastboot in bootloader and it's still locked
Is there's a way to unbrick this phone ? I just spend like 4 hours of trying some tips but it doesn't work for it.
Some screens (remove spaces cause i can't post link before 10posts):
s14.postimg .org/b35qjqt6p/DSC_0001_1.jpg
s22.postimg .org/iiihlx2tt/DSC_0002_1.jpg
image.prntscr .com/image/85f19f6602fe4776b993affe62e959c1.png
Please understand my bad english, it's not my primary language
Mikkal said:
Hi,
i just got an HTC One M8s and i think its propably bricked. I don't know whats owner of that phone done here. Its Software status : Modified, Bootloader: Locked, and S-ON.
I can't turn on the phone, i just can go to bootloader option and cant access recovery bc its popably didn't exist anymore.
I was trying to flash RUU for my CID T-MOB009 but htc_fastboot says "data length is too large" and sometimes "remote:signature verify fail", and i was trying to unlock this bootloader with HTCDev, but when i clicked yes it looks like that(means 1st photo) and just reboot to fastboot in bootloader and it's still locked
Is there's a way to unbrick this phone ? I just spend like 4 hours of trying some tips but it doesn't work for it.
Some screens (remove spaces cause i can't post link before 10posts):
s14.postimg .org/b35qjqt6p/DSC_0001_1.jpg
s22.postimg .org/iiihlx2tt/DSC_0002_1.jpg
image.prntscr .com/image/85f19f6602fe4776b993affe62e959c1.png
Please understand my bad english, it's not my primary language
Click to expand...
Click to collapse
Yeah maybe there's a problem with the "Security warning" it shouldn't be there. What you can do is to reflash the RUU. But not with fastboot but from your sdcard.
Probably this is the firmware that you should use. I'm not sure though you can go one directory back and search for another one if that doesn't suit to you.
Now to flash it follow the steps
1) Download it and if you can check the md5sum so as to ensure it has downloaded correctly.
2) Rename it to 0PKVIMG.zip (note the first character is a zero and not a O
3) Take out the sdcard of your phone.
4) Insert it on your pc and format it to Fat32 or exfat.
5) Copy the above file into your sdcard.
6) Power off your phone and insert the sdcard
7) Go into the bootloader mode. It should automatically detect the firmware
8) When it asks you if you want to install choose "Yes"
9) Wait until it is done. It will flash multiple times the system partion. WAIT patiently
10) Hope that fixed it!
PS: When you enter fastboot you probably see some green letters. This means the hboot is searching for the software file i said above. If it finds it's ok. I had problems copying the file with windows though.
root-expert said:
Yeah maybe there's a problem with the "Security warning" it shouldn't be there. What you can do is to reflash the RUU. But not with fastboot but from your sdcard.
Probably is the firmware that you should use. I'm not sure though you can go one directory back and search for another one if that doesn't suit to you.
Now to flash it follow the steps
1) Download it and if you can check the md5sum so as to ensure it has downloaded correctly.
2) Rename it to 0PKVIMG.zip (note the first character is a zero and not a O
3) Take out the sdcard of your phone.
4) Insert it on your pc and format it to Fat32 or exfat.
5) Copy the above file into your sdcard.
6) Power off your phone and insert the sdcard
7) Go into the bootloader mode. It should automatically detect the firmware
8) When it asks you if you want to install choose "Yes"
9) Wait until it is done. It will flash multiple times the system partion. WAIT patiently
10) Hope that fixed it!
PS: When you enter fastboot you probably see some green letters. This means the hboot is searching for the software file i said above. If it finds it's ok. I had problems copying the file with windows though.
Click to expand...
Click to collapse
Yeah thanks for that great advice man! Unfortunately i was trying to copy this on Windows and when i try to Hboot that it just skip process (but stops for sec on a 0PKVIMG.zip) and going back to bootloader. Any advice how to do that properly on windows ? I checked md5 on sd card and its the same as on my computer disk and same as on this site what youre sent to me . Thanks for replies
Mikkal said:
Yeah thanks for that great advice man! Unfortunately i was trying to copy this on Windows and when i try to Hboot that it just skip process (but stops for sec on a 0PKVIMG.zip) and going back to bootloader. Any advice how to do that properly on windows ? I checked md5 on sd card and its the same as on my computer disk and same as on this site what youre sent to me . Thanks for replies
Click to expand...
Click to collapse
I couldn't get it that done on windows. Dunno what's going wrong. Hopefully i had a linux distro installed and i copied the file from there. Maybe you can do that.
If you haven't installed any linux then create a live cd and boot it up.
root-expert said:
I couldn't get it that done on windows. Dunno what's going wrong. Hopefully i had a linux distro installed and i copied the file from there. Maybe you can do that.
If you haven't installed any linux then create a live cd and boot it up.
Click to expand...
Click to collapse
Okay so now its the trick. I have done copied that properly, bc it start to loading when i put sd card. I click yes for update, and its start to flashing. Some of first steps failed so it wasn't look good. It called ROM failed to flashed click POWER to restart, and when i clicked it phone goes off and now its propably close to hardbricked cause i cant turn on bootloader. When i take it to charger there is no battery on screen informating its already charging. Only LED is working when charging and sound on windows when plug it on and off. Any suggestions guys? I'am scared now
Similar situation
Hi,
I appear to be in a similar situation with my M8 that I tried to convert to GPE. Something went wrong and although the ROM booted, I kept getting told my data was corrupt or encrypted... Tried a few reboots, and refreshed but still got the same...
A thread on here suggested formatting one of the partitions from TWRP which just returned an error, since then the phone appears to be 'hard bricked'.
No display, no charging indication, not recognised in ADB, and I can't force boot into recovery or fast boot.
However, I do still get the notification sound when I plug it into my PC...
It appears in the Device Manager as Qualcomm Mass Storage Device, and Windows shows ~20 drives most of which are unformatted, a few of which seem to contain system info...
I was wondering, would it be possible to re-image the Device? Given that the PC recognises the partitions, would anyway know what -should- be on them?
Alternatively, can anyone provide an image of a stock drive, partitions etc which I could apply?
Apologies if this is nonsense, but I'd imagine the reason it can't boot is the Bootloader partition is 'missing' or corrupted.
The same may be true for your device Mikkal.
Thanks in advance,
Mikkal said:
Okay so now its the trick. I have done copied that properly, bc it start to loading when i put sd card. I click yes for update, and its start to flashing. Some of first steps failed so it wasn't look good. It called ROM failed to flashed click POWER to restart, and when i clicked it phone goes off and now its propably close to hardbricked cause i cant turn on bootloader. When i take it to charger there is no battery on screen informating its already charging. Only LED is working when charging and sound on windows when plug it on and off. Any suggestions guys? I'am scared now
Click to expand...
Click to collapse
Exactly the same problem here, I followed the same steps as you, and had same errors as you.. Is there any help for this?
funjai said:
Exactly the same problem here, I followed the same steps as you, and had same errors as you.. Is there any help for this?
Click to expand...
Click to collapse
What is your CID , software version
No idea mate.. I can't turn on the phone so I can't check that..
For those who can't flash a RUU, unlock the bootloader install TWRP recovery, and install a custom ROM. Voila!
LoneWolfO2Se said:
For those who can't flash a RUU, unlock the bootloader install TWRP recovery, and install a custom ROM. Voila!
Click to expand...
Click to collapse
Oh really? You never noticed that there are no custom roms for M8S ?
funjai said:
Oh really? You never noticed that there are no custom roms for M8S ?
Click to expand...
Click to collapse
You sure about that ?
Hi can you paste info from your phone use this command in fasboot
fastboot getvar all
also tell me what software did you try to flash
Regards

HTC M9 Stuck in loop after trying to root

So I followed this thread https://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
All was going fine, after finishing rooting and rebooting the phone went straight to download mode and at the bottom it says "File /mnt/media_rw\ext_sd\0PJAIMG.ZIP FILE NOT FOUND" and it is now stuck in the reboot loop with the screen only displaying the logo and the message "this build is for development purposes only...."
I then tried this thread https://forum.xda-developers.com/showthread.php?t=1996665 to recover from it, but the links needed were down.
So I went into the recovery mode and tried to restore, but found that there was nothing to restore from. Then I rebooted it and now I'm not able to go into the recovery mode "failed to boot to recovery mode". Also adb will no longer display my device after trying the command "adb devices".
Tried uninstalling and installing the drivers, but no luck.
Horagino said:
So I followed this thread https://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
All was going fine, after finishing rooting and rebooting the phone went straight to download mode and at the bottom it says "File /mnt/media_rw\ext_sd\0PJAIMG.ZIP FILE NOT FOUND" and it is now stuck in the reboot loop with the screen only displaying the logo and the message "this build is for development purposes only...."
I then tried this thread https://forum.xda-developers.com/showthread.php?t=1996665 to recover from it, but the links needed were down.
So I went into the recovery mode and tried to restore, but found that there was nothing to restore from. Then I rebooted it and now I'm not able to go into the recovery mode "failed to boot to recovery mode". Also adb will no longer display my device after trying the command "adb devices".
Tried uninstalling and installing the drivers, but no luck.
Click to expand...
Click to collapse
Okay, so first of all you're using old threads to guide you and in the latter case, a guide build for another model phone. Assuming you are using an HTC One M9, your one-stop resource is the readme thread in this forum.
It sounds like you're going to need a RUU for your device. Before you ask ANYTHING about that, read the readme thread. It answers most every common question (and many uncommon ones), provides guides, and has links.
Once you've read the thread, if you have questions, post them here. We're absolutely happy to help - the readme thread ensures that we all start from the same level of understanding.
computerslayer said:
Okay, so first of all you're using old threads to guide you and in the latter case, a guide build for another model phone. Assuming you are using an HTC One M9, your one-stop resource is the readme thread in this forum.
It sounds like you're going to need a RUU for your device. Before you ask ANYTHING about that, read the readme thread. It answers most every common question (and many uncommon ones), provides guides, and has links.
Once you've read the thread, if you have questions, post them here. We're absolutely happy to help - the readme thread ensures that we all start from the same level of understanding.
Click to expand...
Click to collapse
Hi there, thanks for the reply. I have checked out the thread and I'm trying to follow the instructions in the RUU section, however I'm bit stuck. The third step requires me to copy the file into the SD Card, but I unfortunately have no direct access to that sd card with my PC. And like I said I cannot really use my phone to copy that file, nor can I use adb to copy it, since it doesn't detect my phone, although fastboot does.
You will need a pc to recover your phone in any circumstances. No pc = no recovered phone.
Beamed in by telepathy.
shivadow said:
You will need a pc to recover your phone in any circumstances. No pc = no recovered phone.
Beamed in by telepathy.
Click to expand...
Click to collapse
Not quite sure what you mean by pc, or if I explained it poorly. I do have a computer, but my computer does not have slots for sd cards, hence why I can't put any files on there, and adb won't detect my phone any more.
@edit: I think I know why I goofed up, the sd card I was using is 2GB only, and so I can't even use the RUU provided in the link above, since it is 2.2GB. I will shortly get a new sd card and see how it goes from there. Although if there is a way of doing this without the sd card and just my PC, I'm happy to hear it.
Horagino said:
Not quite sure what you mean by pc, or if I explained it poorly. I do have a computer, but my computer does not have slots for sd cards, hence why I can't put any files on there, and adb won't detect my phone any more.
@edit: I think I know why I goofed up, the sd card I was using is 2GB only, and so I can't even use the RUU provided in the link above, since it is 2.2GB. I will shortly get a new sd card and see how it goes from there. Although if there is a way of doing this without the sd card and just my PC, I'm happy to hear it.
Click to expand...
Click to collapse
There is no easier way to move forward than using a computer (PC, not a Mac). Yes, you could use another device to copy the RUU file to a SD card, but the guides are written with a computer in mind.
Like I said I DO have a PC, it's what I'm using to view and write this thread. My question is, is there a way to execute the RUU file from the PC to the Phone via the usb cable? Since my SD card is too small for that file. The guide says that it is theoretically possible that do it through HTC_fastboot, however it warns that there have been to many problems, so I don't want to risk it, since my phone also has the security features on.
Horagino said:
Like I said I DO have a PC, it's what I'm using to view and write this thread. My question is, is there a way to execute the RUU file from the PC to the Phone via the usb cable? Since my SD card is too small for that file. The guide says that it is theoretically possible that do it through HTC_fastboot, however it warns that there have been to many problems, so I don't want to risk it, since my phone also has the security features on.
Click to expand...
Click to collapse
Yes it's possible. The readme thread doesn't explore how because there are so many different ways a PC-to-phone flash can fail, where as the SD card method is dead simple.
You need a pc to transfer any updates or files to internal memory.
As you said, your memory card is too small for that file. Your other choices are to flash from pc, copy files from pc to phone, copy files from internet to phone.
If the phone doesn't boot to os then your only option is adb. You need a pc to use adb. You will need to access the phones recovery for adb too.
You can get another memory card but if your phone wont boot to os you'll need a pc for adb as your pc doesn't have sd slots.
So basically, you need a pc unless you know some voodoo or something to magic the file onto the phone..
Beamed in by telepathy.
I got a new sd card, 16gb. I also put the file on it using adb commands "adb push C:\adb\0PJAIMG.zip /sdcard" and using the rather broken recovery mode of TWRP I was able to confirm that the file is on there. However, step 5 says that I should be asked if I want to flash the file after booting to download mode, well... That is not happening
Tried installing it via TWRP recovery, however it says that the ZIP file is corrupted somehow.
So I just redownloaded the RUU file, it still says it is corrupted. Any clues as to how to fix it?
Nevermind, fixed it by using another phone to format the sd card and download the file straight to the sd card, then I could follow the instructions without a problem.
I however have one more question, how can I root my phone without going through all this sh** again?
Horagino said:
I however have one more question, how can I root my phone without going through all this sh** again?
Click to expand...
Click to collapse
The readme thread has a section on rooting. Be sure you pay attention to the guide's directions about versions - some versions of SuperSU are incompatible with the M9 and certain versions of TWRP correspond to your firmware version.
Congratulations on getting your phone functioning. Always nice to hear a success story.
If you have marshmallow 6.0 and a gsm phone just:
1, unlock your bootloader via htcdev.com.
2, Flash twrp and mount as "read only" (seems to be version dependent, i used 2.9.0.1 for 6.0 and have no issues to date).
3, make a backup of everything except data (or just system, up to you), you WILL need it one day so make a copy and store it somewhere very, very safe as it is your only fallback.
4, in twrp mount system as read/write and flash chainfires supersu.zip (like twrp, it seems to be version dependent. I used supersu 2.65 for 6.0 and have no issues to date). (use systemless root if asked, not sure if an actual system root is any good for this phone?).
5, buy s-off via sunshine app for $25. This is essential if you want a reasonable chance of recovery should anything go drastically wrong later on. Being able to flash unsigned stuff gives an extra option towards recovery.
It's not too difficult once you get the hang of it, I was panicking too when I did mine. Rightly so, these things brick too easy!. I implore you to cross reference the steps against other material from other xda members just incase I missed something by accident. The last thing you need to do is bugger it up now but I'm confident I have it pretty damn close.
Beamed in by telepathy.
I decided to flash a different ROM; Android HD revolution. Everything went fine and everything works fine.
However, I do have one more question. Whenever I go into the download mode, I still get this message in yellow at the bottom of the screen "File /mnt/media_rw\ext_sd\0PJAIMG.ZIP FILE NOT FOUND", not sure if it's a left over from previous failures or if I'm missing something.

Categories

Resources