|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
| LinkBack | Thread Tools | Display Modes |
07-03-2018, 16:00 | #1 (permalink) |
Junior Member Join Date: May 2008
Posts: 36
Member: 783157 Status: Offline Thanks Meter: 0 | HTC One M9 only Bootloader, no Download or Recovery modes The symptoms are that when started from off condition the white screen with green HTC logo appears with the red text 'This build is for development purposes only..... etc' underneath for a few seconds then goes to the Bootloader screen with 'Software status: Modified', 'LOCKED' and 'S-OFF' at the top. If 'Boot to Download Mode' is selected it goes to a black screen with HTC logo also with the red text underneath as above. After about 30 seconds the screen goes to the white HTC screen for a few seconds then back to Bootloader. I've tried fastboot flashing various hosd files, but without any change in condition. Unfortunately I don't know the history of this phone so don't know what the version-main number is. I've read in various places that this condition can be as a result of emmc hardware failure, however I would like to explore possible cures before writing the phone off as dead. Is there any way of getting more information from the phone using commands in bootloader mode? |
07-05-2018, 19:14 | #2 (permalink) |
No Life Poster Join Date: Jun 2015
Posts: 6,556
Member: 2416253 Status: Offline Thanks Meter: 4,162 | Hello! You can't get more info in bootloader, there are no commands for this. Good that your phone is S-OFF. Were you able to flash at least one HOSD successfully? If so, what was the name of the file? |
07-09-2018, 14:21 | #3 (permalink) |
Junior Member Join Date: May 2008
Posts: 36
Member: 783157 Status: Offline Thanks Meter: 0 | I tried to reply with more detail, but was not allowed to send because the message said that I cannot use links until I've submitted at least 10 posts. However there were no links in the post so I've informed the Webmaster and waiting for a reply. I have a total of 7 posts (8 with this one). |
07-12-2018, 17:02 | #6 (permalink) |
Junior Member Join Date: Jun 2016
Posts: 23
Member: 2588765 Status: Offline Thanks Meter: 1 | You can download this: https://mega.nz/#!QplzCLwD!BgbjHl-Gn...1EuNNPWTsnI28k Unpack and copy all files from HTC_M9_Repacked into xtc2clip except 0PJAIMG_UnZipped.zip Then boot into FTM mode. You can check Flash & H/W info. |
07-13-2018, 01:59 | #7 (permalink) | |
Freak Poster Join Date: Jul 2015
Posts: 127
Member: 2424855 Status: Offline Thanks Meter: 17 | Quote:
| |
07-17-2018, 20:36 | #11 (permalink) |
Junior Member Join Date: May 2008
Posts: 36
Member: 783157 Status: Offline Thanks Meter: 0 | Since my original post I did boot into TWRP from the bootloader using HTC_fastboot boot twrp-3.2.2-0-hima.img and then was able to to use ADB shell getprop to get more information. In the result there are references to OmniROM. The main one being [ro.modversion]: [OmniROM-6.0.1-20171209-hima-HOMEMADE]. I assume that someone has previously flashed OmniROM and this has caused the brick. As far as I know HTC One M9 is not supported by OmniROM. The CID is O2___001. I tried all the hosd files without success. Also tried various functions within TWRP but always end up with: Failed to mount '/cache' '/system' '/data' (Invalid argument). |
07-18-2018, 07:45 | #13 (permalink) |
Junior Member Join Date: May 2008
Posts: 36
Member: 783157 Status: Offline Thanks Meter: 0 | I acquired the phone with the condition existing so unfortunately I don't know its history. I assume that it originally had O2 UK stock ROM. I've tried restoring TWRP O2 L50 and M60 back-ups, but get the 'Failed to mount' messages as mentioned previously. |
07-18-2018, 11:02 | #15 (permalink) |
Junior Member Join Date: Jun 2016
Posts: 23
Member: 2588765 Status: Offline Thanks Meter: 1 | It looks like eMMC, then you need a in circuit programmer to check eMMC. Here is a nice example how to do this. https://www.mobiledit.com/news/2018/...ata-extraction You could boot into stock recovery, if you get a red exclamation mark then press and hold power and pres vol-up and release. You should get into terminal mode and able to wipe. If you get CRC errors mounting partitions then eMMC is bad. Also in download mode > System info you can see eMMC type & SMART life bytes. Only thing you can do then is to replace the eMMC chip. There are Samsung and Hynix chips, the last is known to go bad within 2 years. |
Bookmarks |
| |
|