Not sound at all - Flashing something a long time ago - One (M8) Q&A, Help & Troubleshooting

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.

Related

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

[SOLVED] - [Q] Htc m8 Wifi wont turn on.

Hi to all, recently i got my m8 but wifi wont turn on at all. I got soff, unlocked by htcdev, rooted and arhd rom and elemental kernel.
I need help pls i read in a thread about flashing boot. Img for fixing my issue but im confused.
all-in said:
Hi to all, recently i got my m8 but wifi wont turn on at all. I got soff, unlocked by htcdev, rooted and arhd rom and elemental kernel.
I need help pls i read in a thread about flashing boot. Img for fixing my issue but im confused.
Click to expand...
Click to collapse
Check your firmware against your installed rom version - happens when firmware needs update
Htc
Forgot to mention that it wouldnt turn on since it came out the box.
Kernel - 3.4.0 elemental
Baseband - 1.19.21331147a1
Build numb - 3.28.401.9
Htc
Hboot - 3.18.0.0000
Radio- 1.19.21331147a1
Os - doesn't mention anything at all
all-in said:
Forgot to mention that it wouldnt turn on since it came out the box.
Kernel - 3.4.0 elemental
Baseband - 1.19.21331147a1
Build numb - 3.28.401.9
Click to expand...
Click to collapse
Yeah, that baseband is wrong against that 3.28.401.9, update firmware, should be 1.22.223.....
So which firmware you suggest, any link to download a zip to flash?
What about the os that is empty?
all-in said:
So which firmware you suggest, any link to download a zip to flash?
What about the os that is empty?
Click to expand...
Click to collapse
OS is blank because you got custom recovery, probably TWRP - flash firmware from within fastboot -- http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One_M8/401/3.28.401.9.zip
ill try this and let u know with what i came up.
i got a message : sending 'zip' (43011 KB)... OKAY [ 4.162s]
writing 'zip'... INFOadopting the signature contained in this image
FAILED (remote: not allowed)
all-in said:
ill try this and let u know with what i came up.
i got a message : sending 'zip' (43011 KB)... OKAY [ 4.162s]
writing 'zip'... INFOadopting the signature contained in this image
FAILED (remote: not allowed)
Click to expand...
Click to collapse
You gotta do - fastboot oem rebootRUU and only then execute the next command
fastboot oem rebootRUU command doesnt do anything so i booted in fastboot my own and this message came up. wana smash the phone on the wall. really omg.
target reported max download size of 1830612992 bytes
sending 'zip' (43011 KB)...
OKAY [ 2.599s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.858s
the baseband is still 1.19.21.....
is baseband = radio? cant get this to work.
soff
Ok what i need is s-off as i thought i had it. firewater doesnt work anymore as it mentiones in thread. there is sunshine method but it costs 25 dollars. lolz no way. is there another way to gain s off?
Im a bit confused . Please some help guys. I got s-on,does that mean i cant flash another firmware to get my wifi to work?
all-in said:
Im a bit confused . Please some help guys. I got s-on,does that mean i cant flash another firmware to get my wifi to work?
Click to expand...
Click to collapse
I would really recommend you S-Off your device, if you want to flash firmware
otherwise:
1- flash signed firmware incrementally, signed firmware expects previous updates to already be there, so if you skip directly to the last, you'll end up stuck with a high version firmware, but missing previous updates!!!!!!
2- you need to relock your bootloader, for fastboot oem rebootRUU mode flashes to work
Thanks for the response.
i tryed to s-off with firewater but i think this service has stopped?or does it still work as a method?
Device is s-on with unlocked bootloader. I read that with s-on u cant flash kernels-radios-baseband. Is radio equal to baseband? a guy in earlier post said that to get my wifi working i have to update the firmware. Exactly he said that baseband is wrong against that 3.28.401.9, update firmware, should be 1.22.223.
So how do i get that firmware + how i flash it + in what state should the device be?
thats what im asking
all-in said:
Thanks for the response.
i tryed to s-off with firewater but i think this service has stopped?or does it still work as a method?
Device is s-on with unlocked bootloader. I read that with s-on u cant flash kernels-radios-baseband. Is radio equal to baseband? a guy in earlier post said that to get my wifi working i have to update the firmware. Exactly he said that baseband is wrong against that 3.28.401.9, update firmware, should be 1.22.223.
So how do i get that firmware + how i flash it + in what state should the device be?
thats what im asking
Click to expand...
Click to collapse
hi, just a quick FYI, you need to quote (ie reply) or mention (for example @ nkk71 <- without the space) someone, for them to get notified ... otherwise it may go unnoticed.
anyway,
1- firewater is discontinued and in either case was not very suited for the M8 anyway, except for some of the very early models it would have failed. sunshine ($25) is the only known software solution for s-off
2- the response earlier about what you see in Settings->About (3.28.401.9) only refers to the version the ROM (not firmware) is based on
3- the firmware you get from a "fastboot getvar all" from version-main; if that's missing (a bug in some twrp versions), you can make an educated guess by looking at hboot version + radio + date in bootloader
4- radio is equal to baseband, but not equal to firmware.... firmware contains a lot more than just hboot and radio
5- with s-on, you can only flash signed firmwares (these are usually extracted from OTA.zips), and have to match your MID and CID... you also need to have bootloader relocked for RUU mode flash to work
^^ plus, since those are updates, they will only contain whatever was changed from the previous OTA update, that's why if you intend on staying s-on, you should flash those incrementally, and not skip a version
(for example, the "latest" signed firmware could just be an update to hboot or something, but missing all the previous radio, touchscreen, etc updates.... because and official update [by definition] implies all the previous updates were already installed)
hope that helps a bit
nkk71 said:
hi, just a quick FYI, you need to quote (ie reply) or mention (for example @ nkk71 <- without the space) someone, for them to get notified ... otherwise it may go unnoticed.
anyway,
1- firewater is discontinued and in either case was not very suited for the M8 anyway, except for some of the very early models it would have failed. sunshine ($25) is the only known software solution for s-off
2- the response earlier about what you see in Settings->About (3.28.401.9) only refers to the version the ROM (not firmware) is based on
3- the firmware you get from a "fastboot getvar all" from version-main; if that's missing (a bug in some twrp versions), you can make an educated guess by looking at hboot version + radio + date in bootloader
4- radio is equal to baseband, but not equal to firmware.... firmware contains a lot more than just hboot and radio
5- with s-on, you can only flash signed firmwares (these are usually extracted from OTA.zips), and have to match your MID and CID... you also need to have bootloader relocked for RUU mode flash to work
^^ plus, since those are updates, they will only contain whatever was changed from the previous OTA update, that's why if you intend on staying s-on, you should flash those incrementally, and not skip a version
(for example, the "latest" signed firmware could just be an update to hboot or something, but missing all the previous radio, touchscreen, etc updates.... because and official update [by definition] implies all the previous updates were already installed)
hope that helps a bit
Click to expand...
Click to collapse
Ok for start ill relock the device and i come back for further steps.i hope we can fix this.
all-in said:
Ok for start ill relock the device and i come back for further steps.i hope we can fix this.
Click to expand...
Click to collapse
i relocked my device.so what steps do i follow now?
any thread i should follow to get this updates step by step to reach the latest firware.
after some search on the forum i found these http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F which i think is the right step, but im confused in which folder should i pick and which firmware updates should i download and flash.
this is my getvar command layout :
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4ADWM03441
(bootloader) imei: ----------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__304
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all-in said:
i relocked my device.so what steps do i follow now?
any thread i should follow to get this updates step by step to reach the latest firware.
after some search on the forum i found these http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One_M8%2F which i think is the right step, but im confused in which folder should i pick and which firmware updates should i download and flash.
this is my getvar command layout :
C:\adb>fastboot getvar all
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__304
Click to expand...
Click to collapse
your hboot+baseband version would indicate you are either on 2.22.401.4 or .5 (minor difference)
you should flash in increasing order:
3.28.401.6.zip
3.28.401.7.zip
3.28.401.9.zip
from here: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/
fastboot oem rebootRUU
fastboot flash zip 3.28.401.6.zip
fastboot flash zip 3.28.401.6.zip <- yes twice, make sure it says successful/finished
fastboot reboot-bootloader
once you are back in bootloader, make sure the OS- line has been updated to the version you flashed, and is not in red (if it is in red, that means the flash didnt complete properly)
then repeat the above commands for the 2 other firmwares
Note: the higher the firmware, the less chances of getting S-OFF, just to let you know

help plzzz my m9 dead failed to boot to download mode

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

[SOLVED] Need some help update my phone from 5.0.1 to 6.0

Hi.
first off i have to say im completely new to this, and been googling all day for how to update my phone from 5.0.1 to 6.0 as it doesnt get it automatic but cant find what i feel is the right way for me. so i feel pretty stuck
this far i figure i most likely have an asian modell of m8, would like to upgrade it so i later on will get automatic updates (if it will ever be more coming for this one )
so as a noob i need some help on how to solve this issue
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **************
(bootloader) imei: **************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
you can update it using RUU.zip
however you have s-off device which is heavily modified ( supercid,dev ed or t mobile mid and Asian firmware )
so if you want t update the current firmware then
downoad this RUU
https://mega.nz/#!nQUTEQgS!705whK7tyPvtUgUQwLenweGTJepoHQDeBgsiHhrYVlQ
and follow this instruction to flash it
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
start from "2. Download htc_fastboot.exe" all the steps and files before this step is not for you
p.s backup your files before flashing as the RUU will wipe your internal storage
that didnt work to well, tryed several times (even with different usb ports, same result)
C:\htc>htc_fastboot.exe flash zip RUU.zip
sending 'zip'... (53966 KB) OKAY
sending time = 3.056 secs
writing 'zip'... (bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 3(s)
rmhalvorsen said:
that didnt work to well, tryed several times (even with different usb ports, same result)
C:\htc>htc_fastboot.exe flash zip RUU.zip
sending 'zip'... (53966 KB) OKAY
sending time = 3.056 secs
writing 'zip'... (bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 3(s)
Click to expand...
Click to collapse
try the other method to flash the RUU
rename the RUU to 0P6BIMG.zip then put it in sd card ( formatted as fat32 ) and reboot to bootloader ( hboot )
it will scan for the file and asks to flash it just confirm
let's see how this goes
uhm, nope thats not working eighter
cant see/mount card when booted normally eighter
rmhalvorsen said:
uhm, nope thats not working eighter
cant see/mount card when booted normally eighter
Click to expand...
Click to collapse
try to flash this firmware first ( flash using the same commands i the earlier guide i linked above )
https://mega.nz/#!bMpgkRrY!74hn2pGPKaX6aQhNDchSany6JmRtROm-zeozzhoSWac
note: if you are not on the stock rom/kernel flashing the firmware will wipe the os so you will need to flash the firmware then flash the RUU
after flash the firmware with success reboot to bootloader then reboot to RUU mode and flash the RUU again
if you see this error “Error 90 hboot pre-update..." repeat the flashing command again immediately
Failed
C:\htc>htc_fastboot flash zip fw_6.16.708.1.zip
sending 'zip'... (53849 KB) OKAY
sending time = 3.025 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 4(s)
rmhalvorsen said:
Failed
C:\htc>htc_fastboot flash zip fw_6.16.708.1.zip
sending 'zip'... (53849 KB) OKAY
sending time = 3.025 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 4(s)
Click to expand...
Click to collapse
that's because your mid is 0P6B13000 and cid supercid
the right mid for this firmware is 0P6B63000 and cid HTC__622
you have tow options
1- flash the developer edition marshmallow firmware and RRU.exe
2-change the MID to 0P6B63000 and flash the asian firmware/RUU again
your choice and i think both options are valid for you
option 1
flash this firmware https://mega.nz/#!iZJHDKZK!wKL6TkHz8u5eXA6HfhUfgPDdfeTcCZMxygc9Mm_GGg8
then reboot to bootloader and run this RUU.exe from your pc as a normal app http://www.htc.com/us/support/htc-one-m8/news/
direct link for the RUU.exe
http://dl3.htc.com/application/RUU_...2.1540.4.exe?_ga=1.5739063.5870829.1473114560
option 2
change the mid to 0P6B63000
reboot to twrp ( flash it if you don't yet ) and connect your device to pc
type this 4 commands in cmd window ( press enter after each command )
adb shell
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x36\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
the above command is very sensitive and long command just copy and paste it not write it your self
exit
adb reboot bootloader
then flash the firmware again and followed by the RUU
source for change mid https://forum.xda-developers.com/showthread.php?t=2708581
your mid command isn't available in this thread i edited a close one to be valid for 0P6B63000 ( i'm not an expert )
and i recommend you to choose option 1 ( any way it's your choice following my own command or use the most trusted option 1 )
flash firmware was sucessful.
but the ruu.exe loads up and i accept the terms and hit next, then the app just dies/quits, only thing i see is that languagebar icon flashes when this happends
im running genuine windows 7 64bit, does it need to be runned in a compability mode of some sort ?
rmhalvorsen said:
flash firmware was sucessful.
but the ruu.exe loads up and i accept the terms and hit next, then the app just dies/quits, only thing i see is that languagebar icon flashes when this happends
im running genuine windows 7 64bit, does it need to be runned in a compability mode of some sort ?
Click to expand...
Click to collapse
Try again with RUU and if possible reboot both devices ( pc and phone )
try with another usb port
Windows 7 is the most compatible os to run the RUU so try again
Sent from my HTC M8 using XDA Labs
still a no go, tried all 4 availible usb ports and rebooted between them all, downloaded ruu once more . still app just dies when i accept and hit next
now i have tried from another two computers, with just the same result, ruu.exe dies upon accepting terms and hitting next.
rmhalvorsen said:
now i have tried from another two computers, with just the same result, ruu.exe dies upon accepting terms and hitting next.
Click to expand...
Click to collapse
you are missing some libraries
download and install this
https://www.microsoft.com/en-us/download/details.aspx?id=26368
then run the RUU again
there it goes, worked perfectly and now up and running updated
thanks a lot for your time struggeling with my noobyness, would not have get this done right without you.
atleast now i know what to do next time i buy a new phone on ebay
just one last question, if i now go into meny or hboot and do factory reset, will it restores it to current flashed image again or mess things up? just so i dont mess this up in a year or so, if things starts to hang up
rmhalvorsen said:
there it goes, worked perfectly and now up and running updated
thanks a lot for your time struggeling with my noobyness, would not have get this done right without you.
Click to expand...
Click to collapse
there is a button for that
rmhalvorsen said:
just one last question, if i now go into meny or hboot and do factory reset, will it restores it to current flashed image again or mess things up? just so i dont mess this up in a year or so, if things starts to hang up
Click to expand...
Click to collapse
no worry you are on complete stock state anytime you will make a factory reset it will just wipe the user data
but no need for that now as it already wiped everything on the device :good:
Good to know
Guess this thread can me marked as SOLVED! :good:
rmhalvorsen said:
Guess this thread can me marked as SOLVED! :good:
Click to expand...
Click to collapse
If you like, you can do that yourself, by going to the top post and editing the thread title to add [SOLVED].
The mods don't go around looking for threads to mark as solved.
will it be possible to flash my phone with this one ? 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
.zip
maybe im wrong but i think maybe this would be my solution to get lte/4g working for telenor norway, as it wont connect to other then gprs/hspa now.
??
rmhalvorsen said:
will it be possible to flash my phone with this one ? 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
.zip
maybe im wrong but i think maybe this would be my solution to get lte/4g working for telenor norway, as it wont connect to other then gprs/hspa now.
??
Click to expand...
Click to collapse
Looks like you already answered this question yourself based on the thread you started here: https://forum.xda-developers.com/htc-one-m8/help/help-to-change-radio-basebands-htc-one-t3582804
Please try to avoid bouncing around to different threads. Or at a minimum, if you answer your own question, go back and post what the solution was, so folks don't waste time trying to help you with a question which was already self answered.
noted edited this to solved
well, can atleast say that the rom worked on my phone....(but did not solve the problem in my other thread.)

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

Categories

Resources