help plzzz my m9 dead failed to boot to download mode - One (M9) Q&A, Help & Troubleshooting

no recovery
no download mode
***LOKED***
***S-ON***

Details please.
What can you boot into, if anything? (Bootloader, system, recovery & download mode).
What variant do you have (CID & MID, if possible)?
What did you do that brought your phone to this point?

computerslayer said:
Details please.
What can you boot into, if anything? (Bootloader, system, recovery & download mode).
What variant do you have (CID & MID, if possible)?
What did you do that brought your phone to this point?
Click to expand...
Click to collapse
Reading information...
Using Fastboot mode...
Reading common information
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT53SYJ09030
Execution time is 140(ms)
all:
Reading secure flag information
... (bootloader) read secure flag: 3
Execution time is 15(ms)
OKAY
Reading CID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Reading MEID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Read information failed

aboelgasim said:
Reading information...
Using Fastboot mode...
Reading common information
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT53SYJ09030
Execution time is 140(ms)
all:
Reading secure flag information
... (bootloader) read secure flag: 3
Execution time is 15(ms)
OKAY
Reading CID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Reading MEID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Read information failed
Click to expand...
Click to collapse
mod- 0PJA110
CID 11111111

aboelgasim said:
mod- 0PJA110
CID 11111111
Click to expand...
Click to collapse
Excellent. Tell us about what happened to get to this point. Also, what can you boot into, if anything?

Your MID indicates that you have the unlocked/developer edition of the phone, so my advice would be to use the RUU for that device. You'll have to boot into the bootloader and connect your phone to a PC (this RUU won't run on any other operating system), but it should restore your phone completely to stock.
Be aware that using a RUU is a destructive restore - it'll wipe everything on the phone.
(It's weird that you're S-ON and yet have a CID of 11111111, which is the SuperCID. Changing the CID is only possible after S-OFF.)

extract hosd.img from your firmware.zip and flash via fastboot in bootloader. You should be able to boot to DL mode again.

side_flip15 said:
extract hosd.img from your firmware.zip and flash via fastboot in bootloader. You should be able to boot to DL mode again.
Click to expand...
Click to collapse
Awesome! I would never have thought of that. Another reason I love XDA.

computerslayer said:
Excellent. Tell us about what happened to get to this point. Also, what can you boot into, if anything?
Click to expand...
Click to collapse
after back s-on

computerslayer said:
Awesome! I would never have thought of that. Another reason I love XDA.
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (38128 KB)...
OKAY [ 1.544s]
writing 'hosd'...
OKAY [ 0.671s]
finished. total time: 2.231s
but i still cant open download mode

I notice there is still no explanation on how the device got to this stage. I advise waiting until op explains before committing.
Sent from my HTC One M9 using Tapatalk

My suggestion was based from my experience. I got the same problem before. Not sure how it happened but flashing hosd fixes my device.
You can try flashing hosd from any 3.35.xxx firmware. I'm on dev edition firmware but hosd does not work, tried hosd from 401 and it worked.

shivadow said:
I notice there is still no explanation on how the device got to this stage. I advise waiting until op explains before committing.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I wanted to back s-on

side_flip15 said:
My suggestion was based from my experience. I got the same problem before. Not sure how it happened but flashing hosd fixes my device.
You can try flashing hosd from any 3.35.xxx firmware. I'm on dev edition firmware but hosd does not work, tried hosd from 401 and it worked.
Click to expand...
Click to collapse
search abote 3.35.401 firmware ???

So what did you do? Tell us the steps you took that caused your phone to be in this state.

aboelgasim said:
no recovery
no download mode
***LOKED***
***S-ON***
Click to expand...
Click to collapse
What have you done to get the phone into this state?.
If you do not tell us what you have done so far, we cannot help you.
computerslayer said:
Your MID indicates that you have the unlocked/developer edition of the phone, so my advice would be to use the RUU for that device. You'll have to boot into the bootloader and connect your phone to a PC (this RUU won't run on any other operating system), but it should restore your phone completely to stock.
Be aware that using a RUU is a destructive restore - it'll wipe everything on the phone.
(It's weird that you're S-ON and yet have a CID of 11111111, which is the SuperCID. Changing the CID is only possible after S-OFF.)
Click to expand...
Click to collapse
Borked it trying to get supercid on an s-on phone?
Sent from my HTC One M9 using Tapatalk

computerslayer said:
So what did you do? Tell us the steps you took that caused your phone to be in this state.
Click to expand...
Click to collapse
try back s-on by xtc2clip by SD mode editor

aboelgasim said:
try back s-on by xtc2clip by SD mode editor
Click to expand...
Click to collapse
Right. So, what steps did you take? Describe, in detail, what you did.
Then describe the state of your phone right now. For example, can your phone boot into the a)system or b)the bootloader or c)download mode or d)recovery or e)more than one of these (which ones)?
One sentence descriptions are not enough - you're giving answers with so little detail that we can't give reliable advice.

Exactly what happened to me.
Was playing with the xtc2clip returning back to s-on using sd mode. Ended up with corrupted download mode.
Try flashing hosd from .401. It should fix the problem.

side_flip15 said:
Exactly what happened to me.
Was playing with the xtc2clip returning back to s-on using sd mode. Ended up with corrupted download mode.
Try flashing hosd from .401. It should fix the problem.
Click to expand...
Click to collapse
send any link blzzz

Related

How to resolve bootloop in a S-ON desire

Hi there,
I've got a desire that keeps looping on the HTC screen. Stays there for a few seconds and then restarts.
I can go into the HBOOT menu and FASTBOOT mode, I can easily access it through the fastboot from windows as well. But I wasn't able to get revolutionary to detect it. (I guess it needs the device to be in the OS which can't happen cuz of the boot loop).
I tried to fastboot boot into 4ext recovery through recovery.img file it says:
downloading 'boot.img'...
OKAY [ 0.563s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.568s
When I try to fastboot flash an img it says:
sending 'recovery' (3784 KB)...
OKAY [ 0.564s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.227s
I also can't use the method on htcdevs for unlocking the bootloader cuz it says :
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
Here's my fastboot vars dump:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0001
(bootloader) version-baseband: 5.17.05.23
(bootloader) version-cpld: None
(bootloader) version-microp: 031d
(bootloader) version-main: 3.14.405.1
(bootloader) serialno: HT047PL00475
(bootloader) imei: 357841032013118
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3982mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a7cdbe26
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.030s
I've also tried creating a goldcard but I can't read the goldcard's CID from windows, none of the applications work for me, even when I am using a card slot on my laptop and not a USB card reader.
Can anyone guide me here?
I am pretty much banging my head on the wall right now
Thanks a ton.
Did you unlock your bootloader?
Two beer or not two beer, that's the question
Nope, I couldn't unlock the bootloader cuz I couldn't complete the htcdev tutorial.
Neither could i use revolutionary
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
eddiehk6 said:
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
Click to expand...
Click to collapse
Great!
So, looking at my fastboot vars dump above, can you recommend a link for the RUU, cuz I've tried a number of RUUs but most of them give that "you need to upgrade" message and don't work .
eddiehk6 said:
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
Click to expand...
Click to collapse
In fact, I am trying this one: http://www.htcdev.com/process/legal_download/152 as mentioned in the thread http://forum.xda-developers.com/showthread.php?t=1931014.
Lets hope it works.
Is this the right one?
shabeepk said:
Nope, I couldn't unlock the bootloader cuz I couldn't complete the htcdev tutorial.
Neither could i use revolutionary
Click to expand...
Click to collapse
Why can't you use revolutionary?
Your hboot is supported and you have obviously fastboot working.
So this should be the easiest method for you to unlock and get s-off!
tom0769 said:
Why can't you use revolutionary?
Your hboot is supported and you have obviously fastboot working.
So this should be the easiest method for you to unlock and get s-off!
Click to expand...
Click to collapse
Revolutionary stays stuck at "waiting for device". I don't know why but for some reason it does. It seems to be that it needs the phone to be in the OS loaded with usb debugging enabled.
No?
shabeepk said:
In fact, I am trying this one: http://www.htcdev.com/process/legal_download/152 as mentioned in the thread http://forum.xda-developers.com/showthread.php?t=1931014.
Lets hope it works.
Is this the right one?
Click to expand...
Click to collapse
:S I downloaded the RUU, and now it keeps saying ur battery is less than 30% ...
eddiehk6 said:
At this point RUU would be safest bet
Try the 2.3.3 gingerbread RUU
Click to expand...
Click to collapse
Eddie,
Do you think you could help me with this battery issue?
I downloaded the RUU, and now it keeps saying ur battery is less than 30%, even though I think I've charged the battery, the charge LED shows green and fastboot vars say:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
Do you know what might be wrong ?
shabeepk said:
Eddie,
Do you think you could help me with this battery issue?
I downloaded the RUU, and now it keeps saying ur battery is less than 30%, even though I think I've charged the battery, the charge LED shows green and fastboot vars say:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
Do you know what might be wrong ?
Click to expand...
Click to collapse
Okay, after trying for a few hours I was finally able to run the RUU... some how :S. I really don't know how.
However, the update process went smooth, no issues, BUT ! :s the bootloop is still there.
Do you think this might be a hardware fault? Do you think this phone doesn't have its actual stuff i.e. the ROM. the RADIO and HBOOT? Do you think I should check other info on the phone tag or something to guess the correct firmware?
This RUU seemed like an all Desire one. No ?
Dead end ... :S
So the RUU successfully flashed but it still won't even boot? Strange
Try revolutionary again, did you install the relevant hboot drivers? Find the revolutionary.io documentation page, instructions should be on there
eddiehk6 said:
So the RUU successfully flashed but it still won't even boot? Strange
Try revolutionary again, did you install the relevant hboot drivers? Find the revolutionary.io documentation page, instructions should be on there
Click to expand...
Click to collapse
Yes, I know its very strange :S
I did try that, however, it wasn't that simple. The drivers present on the revolutionary website didn't detect my device in HBOOT, it was only detecting the device in FASTBOOT, and in FASTBOOT revolutionary still didn't detect the device.
Then I had to download the altered driver and then install it manually. Now My device is detected in both; Fastboot and HBOOT mode. But revolutionary still can't detect it, in neither of the modes.
Any Idea why ? And what I may have done wrong there.
Try and follow this exactly, see if it makes any difference. The video helps
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/
eddiehk6 said:
Try and follow this exactly, see if it makes any difference. The video helps
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/
Click to expand...
Click to collapse
Tried that, but the problem I am probably facing is that to gain s-off, revolutionary needs to phone to be in USB debugging mode i.e. adb mode with the OS running ofcourse. While I can't get past HBOOT / FASTBOOT. So revolutionary ain't working for me.
I don't know what to do now.
Any suggestions?
ah...
Only thing I can think of is keep trying the RUU until it boots properly.
Print out any error messages if it has any.

Tmo Htc One M8 error 12 "Remote Signature verify failed"

I am fixing a TMO Htc One M8 for a friend. He currently has TWRP recovery but nothing will wipe or flash. I have posted the get var information and the log below along with all the steps I've taken, please share any insight into the matter.
Here is the Get VAR Information. I have tried to fix this device by relocking the Bootloader, flashing stock RUU RUU_M8_TMOUS_1.57.531.7 , Flashing modified firmware.zip, flashing recovery.img, nothing. Then unlocking the bootloader, flashing Philz recovery.img, Twrp.img, still same error. Current TWRP recovery registers nothing but errors. No wiping data, cache, system, etc. No installing backup nandroid, no flashing new rom through external SD card or adb sideload. Literally the phone won't flash anything and the error is error 12, "Remote signature verifiey failed" What kinda insight do you have into this? Anyway to get back to stock?
Thanks!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA446WM02874
(bootloader) imei: 352628060329457
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
LOG: D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash TMOUS-M8-1.12.53
1.19.recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.691s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.953s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash philz_touch_6.48
.4-m8.img
sending 'flash' (14436 KB)...
OKAY [ 1.467s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.293s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash T_Mo_1.57.531.7_
recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.688s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.753s
D:\All Android Devices\T Mobile HTC One M8>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.132s
twill1987 said:
I am fixing a TMO Htc One M8 for a friend. He currently has TWRP recovery but nothing will wipe or flash. I have posted the get var information and the log below along with all the steps I've taken, please share any insight into the matter.
Here is the Get VAR Information. I have tried to fix this device by relocking the Bootloader, flashing stock RUU RUU_M8_TMOUS_1.57.531.7 , Flashing modified firmware.zip, flashing recovery.img, nothing. Then unlocking the bootloader, flashing Philz recovery.img, Twrp.img, still same error. Current TWRP recovery registers nothing but errors. No wiping data, cache, system, etc. No installing backup nandroid, no flashing new rom through external SD card or adb sideload. Literally the phone won't flash anything and the error is error 12, "Remote signature verifiey failed" What kinda insight do you have into this? Anyway to get back to stock?
Thanks!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA446WM02874
(bootloader) imei: 352628060329457
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
LOG: D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash TMOUS-M8-1.12.53
1.19.recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.691s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.953s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash philz_touch_6.48
.4-m8.img
sending 'flash' (14436 KB)...
OKAY [ 1.467s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.293s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash T_Mo_1.57.531.7_
recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.688s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.753s
D:\All Android Devices\T Mobile HTC One M8>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.132s
Click to expand...
Click to collapse
okay I'm wondering why the bootloader is 3.18. I just converted my T-Mobile HTC one m8 to dev edition and that's what my bootloader is now.
That device must have been s-off before if it has the 3.18 bootloader. the problem is now you're s-on with the wrong bootloader in the phone. So it's not gonna verify something it can't. U need to unlock the bootloader then try to s-off again. Let me know if u need more help
twinnfamous said:
okay I'm wondering why the bootloader is 3.18. I just converted my T-Mobile HTC one m8 to dev edition and that's what my bootloader is now.
That device must have been s-off before if it has the 3.18 bootloader. the problem is now you're s-on with the wrong bootloader in the phone. So it's not gonna verify something it can't. U need to unlock the bootloader then try to s-off again. Let me know if u need more help
Click to expand...
Click to collapse
Yes, I think the device was S-off before was well. But how can I get the device S-off when I can't load any rom to establish an internet connection?
There's no way to get back to stock, or get an internet connection through the device to obtain S-off. I can unlock the boot-loader,
I've done that a few times, but how to get S-Off when the only two screens I can access are the bootloader and twrp? When bootloader is unlocked. I have used firewater before for S-off and it requires active internet connection on device.
Thanks again for helping
twill1987 said:
Yes, I think the device was S-off before was well. But how can I get the device S-off when I can't load any rom to establish an internet connection?
There's no way to get back to stock, or get an internet connection through the device to obtain S-off. I can unlock the boot-loader,
I've done that a few times, but how to get S-Off when the only two screens I can access are the bootloader and twrp? When bootloader is unlocked. I have used firewater before for S-off and it requires active internet connection on device.
Thanks again for helping
Click to expand...
Click to collapse
Unlock bootloader try to flash the latest open twrp recovery and try to install another Rom or backup. If you can see the roms in the sdcard then you should be able to flash the roms or backup.
If there was a way to get into adb YOU would be able to s-off again.
twinnfamous said:
Unlock bootloader try to flash the latest open twrp recovery and try to install another Rom or backup. If you can see the roms in the sdcard then you should be able to flash the roms or backup.
If there was a way to get into adb YOU would be able to s-off again.
Click to expand...
Click to collapse
I've tried to flash TWRP but I get that error. I tried to flash the newest twrp but it wouldn't flash.
I think the system is no longer mounted, that's why I get this error :"E: Unable to mount 'data'" and "E: Unable to mount internal storage"
twill1987 said:
I've tried to flash TWRP but I get that error. I tried to flash the newest twrp but it wouldn't flash.
I think the system is no longer mounted, that's why I get this error :"E: Unable to mount 'data'" and "E: Unable to mount internal storage"
Click to expand...
Click to collapse
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Well first your doing the wrong command. Its fastboot flash recovery recovery.img, not fastboot flash flash recovery.img.
x714x said:
Well first your doing the wrong command. Its fastboot flash recovery recovery.img, not fastboot flash flash recovery.img.
Click to expand...
Click to collapse
Yes, that was a typo. Every fastboot flash ends with error 12. Remote Signature.
I have tried literally everything with this device. Tried flashing new TWRP, Radio, Firmware, Etc. Nothing works.
Inside TWRP everything finishes with "failed" or "E: Unable to mount cache"
I tried to select cache under the mount in TWRP and it's greyed out. I fastboot erase cache, and it is literally
the only thing that worked for me. But still no way to restore previous Android. Tried flashing stock RUU's for 4.4.2 and 4.4.3, no dice.
Both RUU's get to 6 percent and then say failed. I'm wondering if the device thinks it's a different phone possibly a GPE edition so it won't
go back to stock? Just a thought. I have unlocked, and relocked the bootloader a million times trying different methods as well, not
sure what else there is to do next. This might be the end of the road for this customers phone.
twinnfamous said:
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Click to expand...
Click to collapse
Yes, that was a typo. Every fastboot flash ends with error 12. Remote Signature.
I have tried literally everything with this device. Tried flashing new TWRP, Radio, Firmware, Etc. Nothing works.
Inside TWRP everything finishes with "failed" or "E: Unable to mount cache"
I tried to select cache under the mount in TWRP and it's greyed out. I fastboot erase cache, and it is literally
the only thing that worked for me. But still no way to restore previous Android. Tried flashing stock RUU's for 4.4.2 and 4.4.3, no dice.
Both RUU's get to 6 percent and then say failed. I'm wondering if the device thinks it's a different phone possibly a GPE edition so it won't
go back to stock? Just a thought. I have unlocked, and relocked the bootloader a million times trying different methods as well, not
sure what else there is to do next. This might be the end of the road for this customers phone.
twinnfamous said:
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Click to expand...
Click to collapse
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
twill1987 said:
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
Click to expand...
Click to collapse
I just tried to reformat data again and it says same error in TWRP E: Cannot mount cache
I am able to flash Viper Rom though, but because it is S ON the rom won't boot past start up screen.
What a bizarre issue
twill1987 said:
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
Click to expand...
Click to collapse
There should be a way now that the new T-Mobile update to flash ruu if we can find one.
Edit: found one
http://www.htcdev.com/devcenter/downloads/P00
Just select T-Mobile as carrier and USA as region then you Wil see the latest ruu to download.
twinnfamous said:
There should be a way now that the new T-Mobile update to flash ruu if we can find one.
Click to expand...
Click to collapse
I flashed the 4.4.3 RUU update at HTCDEV.com It failed at the 6 percent mark. http://www.htcdev.com/devcenter/downloads
twill1987 said:
I just tried to reformat data again and it says same error in TWRP E: Cannot mount cache
I am able to flash Viper Rom though, but because it is S ON the rom won't boot past start up screen.
What a bizarre issue
Click to expand...
Click to collapse
the latest viper is from New firmware base so it takes 15 to 20 minutes to boot. Have you waited that long?
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
twill1987 said:
I flashed the 4.4.3 RUU update at HTCDEV.com It failed at the 6 percent mark. http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
Sorry it seems I'm getting posts in different orders.
Flash viper and wait 15 to 20 minutes. And we can go from there.
I'm pretty sure we can get this resolved.
twinnfamous said:
the latest viper is from New firmware base so it takes 15 to 20 minutes to boot. Have you waited that long?
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
Sorry it seems I'm getting posts in different orders.
Flash viper and wait 15 to 20 minutes. And we can go from there.
I'm pretty sure we can get this resolved.
Click to expand...
Click to collapse
I'll try to flash the latest Viper. The 1.6.0 it says everything flashed correctly, but gets stuck at the HTC boot screen.
I just flashed the 1.8.0 OTA update and everything installs but it sticks at the boot screen.
I see the 2.2.0 update is out so I'm downloading that now, I'll flash and see how it goes.
I'll update, thanks for your help!
Ruu requires the bootloader be locked
Sent from my HTC One_M8 using XDA Free mobile app

HTC m8 not starting up correctly. Tried everything i can think of and find.

Hello there!
I have now searched and searched and come upon many great threads in this massive forum however i have yet to find a solution to my current problem. Every time i have went here i have always managed to find something to help me fix my phones over the years but this this time I've hit a wall it seems.
What happened was that my phone started to crash the google apps like gallery etc. No big deal at first but then i decided to do a factory reset thinking that might fix the problem but then my phone just starts up to the HTC logo and throws several different error messages that Google.xxx.xxx could not start/has crashed. IF i click these away they appear after a while again and the phone will be stuck like that.
I can start the phone in fastboot mode to be able to use ADB etc..
The phone is currently bootloader unlocked and with S-on
Now this is what i have done:
First of all the phone wasn't in debugging mode when it crashed so I'm guessing its still not which might complicate the matter further.
* Using a TWRP.img file i managed to get the phone in to the TWRP mode on the phone. (Fastboot boot TWRPfilename.img)
I do not have any TWRP files on my phone nor any apps this was all from the files on the PC. I just mention this because thats the only sign of life the phone has given me so far.
*I tried to go in from the adb shell and enabling it using the following code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
I have no idea as to if it worked or not but the phone rebooted again.
* Tried to reflash with the right RUU for my phone with the right CID thanks to guides on this forum -- i get error 159 (this is because the CID is wrong from what ive read in other threads)
* Tried changing the CID to 11111111 but that did not work i got another error doing that:
C:\adb>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 3
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 0
(bootloader) sdhci_open: id=0
(bootloader) Initializing MMC host data structure and clock!
(bootloader) mmc slot#2 clock enabled
(bootloader) sdhci_set_clock: slot 2, freq 192000000
(bootloader) GPLL0 is enabled
(bootloader) clock_update_cfg_sd is done
(bootloader) sd clock set done
(bootloader) sdhci_set_bus_width: bus width 0
(bootloader) sdhci_clk_supply: freq 400000
(bootloader) Decoded CID fields:
(bootloader) Manufacturer ID: 2
(bootloader) OEM ID: 0x544d
(bootloader) Product Name: SA16G
(bootloader) Product revision: 1.1
(bootloader) Product serial number: 37A24E6D
(bootloader) Manufacturing date: 10 2013
(bootloader) sdhci_clk_supply: freq 50000000
(bootloader) sdhci_set_bus_width: bus width 1
(bootloader) Done initialization of the card
(bootloader) erase_grpsize: -16777216
(bootloader) erase_grpmult: 261077976
(bootloader) wp_grpsize: 0
(bootloader) wp_grpen: 0
(bootloader) perm_wp: 0
(bootloader) temp_wp: 0
(bootloader) [Tuxera][Error] No exFAT partition found
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.132s]
finished. total time: 0.132s
* Tried flashing from a .zip file with the fastboot commands.
ALL of these things I have tried with the bootloader locked and unlocked. (if this is any important info)
The phone ran the 6.12.401.4 version at the moment of the crash and that's what shows in the RUUs ive tried as well. Also the phone is not rooted.
Now is there a way to completely flush the phone out of any info and just reinstalling it like you can do with windows on a PC for example since whatever i try is met by an error message or a failed flash etc..?
some more info about the phone from getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
1. remove your serial & imei no. on your post
2. http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
3. relock bootloader with command -
fastboot oem lock
fastboot reboot-bootloader
4. http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Thank you for your fast reply!
I have removed the lines from the post as you said and tried your links unfortunately without success. This is why im hoping you like a challange! hehe.
This is the result from the cmd when trying to flash the new RUU:
C:\Users\Genocide\Desktop\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\Genocide\Desktop\RUU>htc_fastboot flash zipp RUU.zip
sending 'zipp' (1687272 KB)... OKAY
writing 'zipp'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 109(s)
C:\Users\Genocide\Desktop\RUU>htc_fastboot flash zipp RUU.zip
sending 'zipp' (1687272 KB)... OKAY
writing 'zipp'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 109(s)
I followed your steps 1 by 1 downloaded all needed files and installs etc... Something is terribly wrong with my device it seems.
Any further ideas?
Did you skip no.3 ?
Why it is zipp not zip ?
Try again ..
If still fails, tomorrow I'll give you another method.. already in bed.
oh! ive done goofed!
It was my bad with some **** spelling there.
IT WORKED!!
I thank you sooooo much from the bottom of my heart I was sure my phone was unsaveable for a moment.
what was the difference with that RUU and the ones I've tried before? I must have tried like 4 different ones in the end out of desperation.
or was it the fastboot that was the trick?
I'm just curious on how you could spot the problem so that i can learn more about how it works.
Thanks again! Truly great work!
Sambeg said:
what was the difference with that RUU and the ones I've tried before? I must have tried like 4 different ones in the end out of desperation.
or was it the fastboot that was the trick?
Click to expand...
Click to collapse
We can't say if the RUUs you tried were correct or not, as you didn't give any specific on those (file names, where you found them, etc.).
But you do need the htc_fastboot to run the RUU.zip with fastboot command, the "generic" fastboot.exe does not work.
And you absolutely need to have a LOCKED or RELOCKED bootloader to RUU with s-on (this requirement is bypassed with s-off). So you were also compounding one wrong thing with another (when trying to flash RUU with bootloader UNLOCKED) making it even less likely you would have the successful combination of variables.
Unlocked bootloader is okay to OTA, so that is where I think some folks get confused on when to have the bootloader locked or not. But OTA and RUU are two very different things (with different requirement), and its important to remember that fact.
redpoint73 said:
We can't say if the RUUs you tried were correct or not, as you didn't give any specific on those (file names, where you found them, etc.).
Click to expand...
Click to collapse
I found them all in XDA guides/lists of stock roms, checked with my CID and European versions etc...
redpoint73 said:
But you do need the htc_fastboot to run the RUU.zip with fastboot command, the "generic" fastboot.exe does not work.
Click to expand...
Click to collapse
I think this is where all else failed since all the ones i tried had either the ADB or a file called only Fastboot.exe not this one that said HTC_fastboot.exe
redpoint73 said:
And you absolutely need to have a LOCKED or RELOCKED bootloader to RUU with s-on (this requirement is bypassed with s-off). So you were also compounding one wrong thing with another (when trying to flash RUU with bootloader UNLOCKED) making it even less likely you would have the successful combination of variables.
Click to expand...
Click to collapse
I tried all the solutions in both locked/relocked state just to be sure i had no real understanding of this before but I am now enlighten thanks to you
redpoint73 said:
Unlocked bootloader is okay to OTA, so that is where I think some folks get confused on when to have the bootloader locked or not. But OTA and RUU are two very different things (with different requirement), and its important to remember that fact.
Click to expand...
Click to collapse
Yeah those things are clear for me as well. I just had the problem with the RUU not working for me. Thanks again for all the help and the good information provided even after my problem has been solved
Sambeg said:
I found them all in XDA guides/lists of stock roms, checked with my CID and European versions etc...
Click to expand...
Click to collapse
That still doesn't tell me much about what RUUs you tried. What are the actual file names, version numbers, etc.?
Only if you are still curious why the RUUs didn't work, of course. I understand its somewhat of a moot (or purely academic) point, now that the phone is working.
redpoint73 said:
That still doesn't tell me much about what RUUs you tried. What are the actual file names, version numbers, etc.?
Click to expand...
Click to collapse
these two I've tried and it was the ones in most of the guides etc. However I tried a few more as well but i had them deleted now.
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
These 2 i just tried in the end when i had given up. I know they are not really for my phone.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
Sambeg said:
these two I've tried and it was the ones in most of the guides etc. However I tried a few more as well but i had them deleted now.
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
These 2 i just tried in the end when i had given up. I know they are not really for my phone.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
Click to expand...
Click to collapse
Somewhat as I figured. All those RUUs failed for good reason.
First and second ones: These RUUs are older (lower version number) than the main version that was on the phone (6.12.401.4), otherwise known as a "downgrade" in version. With s-on, that isn't allowed. You can only flash the same or higher version (later) RUUs; and the only way to bypass that requirement is with s-off.
Third RUU: As you know, this isn't for your phone. You can run it a million times, and it will still fail every time; as its intended to fail since the CID and MID on your device doesn't match what the RUU is looking for. The only way to run this RUU is to s-off and change your phone's CID and MID.
Forth RUU: Again, not for your phone. Plus, the Sprint version, which has partition differences from your M8 version (and most other M8 versions). You absolutely should stay away from any Sprint or Verizon firmware, as if they do manage to flash, will often lead to a radio brick on your device.
This would never flash anyway with s-on, and the safeguards of the CID and MID did their job and saved you, in this case.
So in short, you can only run RUUs that have the "401" in the spot x.xx.401.x as these are for your CID and MID. And you can only run versions equal or greater than 6.12.401.4, of which there is currently the only one (the one that worked - 6.12.401.4).
Hope that clears things up a bit for you.
redpoint73 said:
Somewhat as I figured. All those RUUs failed for good reason.
First and second ones: These RUUs are older (lower version number) than the main version that was on the phone (6.12.401.4), otherwise known as a "downgrade" in version. With s-on, that isn't allowed. You can only flash the same or higher version (later) RUUs; and the only way to bypass that requirement is with s-off.
So in short, you can only run RUUs that have the "401" in the spot x.xx.401.x as these are for your CID and MID. And you can only run versions equal or greater than 6.12.401.4, of which there is currently the only one (the one that worked - 6.12.401.4).
Hope that clears things up a bit for you.
Click to expand...
Click to collapse
Yes indeed this cleared up most of my suspicions as well as i said i knew the 3rd and 4th was wrong from the get go it was more of a test..
Thank you for all this good info i feel like im starting to get a good grip on whats good and whats working etc... I really appreciate it! Thumbs up indeed.
I have another question tho.... Why would it not let me change the CID to the supercid 11111111?
IS that due to the phone not being in debug mode or the S-on option perhaps since i know that is a security feature from the get go.
Sambeg said:
I have another question tho.... Why would it not let me change the CID to the supercid 11111111?
IS that due to the phone not being in debug mode or the S-on option perhaps since i know that is a security feature from the get go.
Click to expand...
Click to collapse
You can only change the CID (and also MID) with s-off.
redpoint73 said:
You can only change the CID (and also MID) with s-off.
Click to expand...
Click to collapse
Right as I thought then Well thanks again for helping out and clearing up my questions.
I shall now retire from this thread in peace

HTC M8 eye with official rom stuck in fastboot

Hey guys
Last night my phone(HTC m8 eye 5.07.401.1) slowed down badly, after a while it restarted automatically and fastboot screen showed up.
Things I've tried:
1-Restarting the phone after fully charging it for 1 billion times (worked once but the phone was frozen and restarted automatically again)
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
3-Trying to flash the official rom , didn't work
4-removing the SIM and SD card and restarting the phone, didn't work
by the way, usb debugging was not active last time the phone was working normally, Also the phone have not experienced any unusual activity like rooting or flashing custom roms or...
What can I do?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA00000000000
(bootloader) imei: 3580000000000000
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mels_tuhl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B81000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5c9466dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
------------------------------------------------------------------------------------------- fastboot results----------------------
C:\fastboot>fastboot devices
FA57LY901038 fastboot
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.041s]
finished. total time: 10.041s
C:\fastboot>fastboot flash zip update.zip
target reported max download size of 1826332672 bytes
sending 'zip' (1687274 KB)...
OKAY [ 57.179s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 118.969s
---------------------------------------------------------------------------------------
I don't have the "eye", only the "standard" M8, but I'll try to help as much as I can, as far as anything that I believe is common between the two M8 versions (unlocking bootloader, flash RUU, etc.).
bahmaniq said:
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
Click to expand...
Click to collapse
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
bahmaniq said:
3-Trying to flash the official rom , didn't work
Click to expand...
Click to collapse
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.
redpoint73 said:
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
Click to expand...
Click to collapse
Yes, *****LOCKED***** it says, I guess it is very serious on this one. Based on knowledge I gathered in these 2 days, I think it should show a black confirmation screen after I try to unlock it (using *.bin file), but it simply does not.
redpoint73 said:
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
Click to expand...
Click to collapse
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
redpoint73 said:
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.
Click to expand...
Click to collapse
So, that's it, I'm gonna play "One last goodbye" and let the history judge. 2 years of EMERGENCY CALLS ONLY, 2 years of zero antenna...
After a silent peaceful night
You took my heart away
oh I wish, I wish you could have stayed
bahmaniq said:
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Click to expand...
Click to collapse
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.
redpoint73 said:
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.
Click to expand...
Click to collapse
It has been a long time since the last time I was here but the problem is not solved. Sorry for the delay, and No the black screen with HTC logo does not appear.
Is there anything I can do to get rid of this fastboot screen? or the phone is useless

Not sound at all - Flashing something a long time ago

So, like I found in another threads my old phone, has not sound at all. I tried to fix it years ago, with not luck, but I wanna give it another chance since still it's a great phone.
This is my getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---------
(bootloader) imei: ----------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I tried almost everything, it's currently S-ON, I tried a millon times going S-OFF with HTCDev steps, but nothing. It's UNLOCKED.
If anyone would give me a hand with this, would be awesome.. since my actual phone is broke, like my wallet. :crying:
Thanks! :fingers-crossed:
Stranyer said:
I tried almost everything, it's currently S-ON, I tried a millon times going S-OFF with HTCDev steps, but nothing.
Click to expand...
Click to collapse
HTCDev is not a process to get s-off. It is a process to unlock the bootloader (but you say it's already UNLOCKED). Sunshine is the only valid method to s-off. You can try anything else a billion times, and it will never work.
You most likely also do not need s-off to get the phone working properly again.
I have a feeling that no sound is due to outdated firmware, possibly in conjunction with a custom ROM (ROM - firmware mismatch).
My suggestion, try to relock the bootloader (command: fastboot oem lock) then the following RUU:
http://gsm-firmware.com/index.php?a=downloads&b=file&id=14070
The RUU will wipe all personal data on the phone.
redpoint73 said:
HTCDev is not a process to get s-off. It is a process to unlock the bootloader (but you say it's already UNLOCKED). Sunshine is the only valid method to s-off. You can try anything else a billion times, and it will never work.
You most likely also do not need s-off to get the phone working properly again.
I have a feeling that no sound is due to outdated firmware, possibly in conjunction with a custom ROM (ROM - firmware mismatch).
My suggestion, try to relock the bootloader (command: fastboot oem lock) then the following RUU:
http://gsm-firmware.com/index.php?a=downloads&b=file&id=14070
The RUU will wipe all personal data on the phone.
Click to expand...
Click to collapse
Hey thanks for replying!
I tried that, I keep getting this error
Code:
target reported max download size of 1826418688 bytes
sending 'zip' (1734001 KB)...
OKAY [ 49.344s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 112.683s
I tried doing a reboot and reinstaling.. but still getting error 12 :/
Any clue?
Stranyer said:
I tried that, I keep getting this error
Code:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
"Signature verify fail" usually means the bootloader is unlocked. Did you relock the bootloader as I advised (mandatory in order to install the RUU)? Or if you did, can you verify is says RELOCKED near the top of the bootloader screen?
redpoint73 said:
"Signature verify fail" usually means the bootloader is unlocked. Did you relock the bootloader as I advised (mandatory in order to install the RUU)? Or if you did, can you verify is says RELOCKED near the top of the bootloader screen?
Click to expand...
Click to collapse
Yeah, I did relocked the bootloader. And it does says RELOCKED.
Stranyer said:
Yeah, I did relocked the bootloader. And it does says RELOCKED.
Click to expand...
Click to collapse
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
ckpv5 said:
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
Click to expand...
Click to collapse
Good point, and makes sense, as most of the US M8 variants require firmware to be flashed for Marshmallow RUU. Even though Rogers is Canadian, that version tends to follow the same rules as the US versions!
ckpv5 said:
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
Click to expand...
Click to collapse
redpoint73 said:
Good point, and makes sense, as most of the US M8 variants require firmware to be flashed for Marshmallow RUU. Even though Rogers is Canadian, that version tends to follow the same rules as the US versions!
Click to expand...
Click to collapse
Sorry I took long time to reply.
I tried flashing the firmware, using htc_fasboot and fastboot. Both will give me this error.
Code:
c:\adb>htc_fastboot flash zip fw.zip
sending 'zip'... (53849 KB) OKAY
sending time = 2.408 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 5(s)
And still, won't flash RUU.zip
----
I retried a few more times, and it worked! It flashed firmware and ruu
But now is stuck on HTC logo boot. Won't let install a rom over fastboot :/
Code:
sending 'zip'... (360264 KB) OKAY
sending time = 10.763 secs
writing 'zip'... FAILnot allowed
FAILED (remote: not allowed)
Execution time is 11(s)
Stranyer said:
But now is stuck on HTC logo boot. Won't let install a rom over fastboot :/
Code:
sending 'zip'... (360264 KB) OKAY
sending time = 10.763 secs
writing 'zip'... FAILnot allowed
FAILED (remote: not allowed)
Execution time is 11(s)
Click to expand...
Click to collapse
Hard to tell exactly what you tried to do here, since you didn't include the actual command, name of the file you tried to flash, etc. Always include as much specific info as possible. "install a rom" is not sufficient info.
You tried flashing a custom ROM over fastboot? If so, that isn't the proper way to flash a custom ROM. You need custom recovery (TWRP) to do that. So that is the reason for "not allowed" (since it isn't).
But before doing so, we should look closer at the RUU (why it isn't booting) first. Since installing TWRP requires unlocking the bootloader, etc. Better to eliminate the RUU as a solution first, so we don't have to keep going back and forth unlocking/relocking bootloader.
Did the RUU finish successfully without any errors? If there were errors, what did it say specifically? If you don't know the answers to those questions, you can run the RUU again. Even cut/paste the output so we can look at it.

Categories

Resources