Develop Bugs

[Q] fastboot problem, lots of error

hi!
I have htc one x tegra 3. I have a few problem with it.
My main problem now, i don't can use fastboot rebootruu option.
Code:
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) write sector fail !
(bootloader) [MSG] OKAY
OKAY [ 12.231s]
finished. total time: 12.231s
And it just give me black screen. After i need hold power button for reboot.
But anyway i have problem, with fastboot, if i want relock my phone or unlock again, or flash boot.img, or recovery. Most of time i get some error. I try to flash from android, and win8. From pc and notebook. I need do same command for 2-3 times.
Thats why, i want update frimware, (i want install this: http://arhd.onedroid.net/db_mirror/Firmware/HTC/HTC_One_X/401/3.14.401.31.zip)
I think it have problem, if phone need to write something.
Code:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.162A.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.20.401.1
(bootloader) serialno: ********************
(bootloader) imei: ****************
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 3681mV
(bootloader) devpower: 8
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
error codes:
if i want unlock the phone:
Code:
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
(but the phone unlocked after restart)
same when i want relock
if i want install recovery:
Code:
(bootloader) Format partition SOS done
FAILED (remote: err = 0x30000)
(same if i want flash boot.img)
if i want erase cache
Code:
erasing 'cache'...
FAILED (remote: err = 0x19000008)

You can't downgrade from 3.20 to 3.14 !!! And there is no RUU. if you want to go to stock you have to restore a nandroid backup via a custom recovery.
Unlock the bootloader :
Fastboot flash unlocktoken Unlock_code.bin
Flash a recovery :
Fastboot flash recovery recovery.img
Flash a boot.img :
Fastboot flash boot boot.img

Mr Hofs said:
You can't downgrade from 3.20 to 3.14 !!! And there is no RUU. if you want to go to stock you have to restore a nandroid backup via a custom recovery.
Unlock the bootloader :
Fastboot flash unlocktoken Unlock_code.bin
Flash a recovery :
Fastboot flash recovery recovery.img
Flash a boot.img :
Fastboot flash boot boot.img
Click to expand...
Click to collapse
I want to do this many times, but sometimes work, sometiomes not. I always get error for fastboot commands.

Then you should check your drivers,and be sure that you are in Fastboot..
Check yor conectivity:
fastboot devices

Only use the original HTC usb cable, only use a 2.0 usb port directly connected. Not via hubs or anything.
It can always be hardware related at the end, but lets try to rule that out !

big noob said:
Then you should check your drivers,and be sure that you are in Fastboot..
Check yor conectivity:
fastboot devices
Click to expand...
Click to collapse
I think, connection not problem, becouse, if i use for example fastboot reboot-bootloader, my phone restart. Or just turn off, and don't restart, until i press and hold pwr button...
Mr Hofs said:
Only use the original HTC usb cable, only use a 2.0 usb port directly connected. Not via hubs or anything.
It can always be hardware related at the end, but lets try to rule that out !
Click to expand...
Click to collapse
Im using another phone cable, i search the original and tray again...

Oh, and i forgot, if i connect the phone to my pc i hear it disconnect and connect few time befor bootloader start up.

Get the original and try again. Otter cables can cause many connection troubles

ok i get back my original usb cable from my ex soooo, now i try unlock the phone:
Code:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (remote: loading custom splash failed)
finished. total time: 0.388s
erase cache can help me befor, if i had this problem, but now, erase chace failed.

can you perform the command :
fastboot getvar version-main
post the outcome back here please !

Mr Hofs said:
can you perform the command :
fastboot getvar version-main
post the outcome back here please !
Click to expand...
Click to collapse
Code:
version-main: 3.20.401.1
btw now i try erase again after i wait, and now i can erase cache. Now unlock it, i get the unlock menu, where i can choose unlock. But in cmd line i have rerror again. The to many link error...

tejeskifly said:
Code:
version-main: 3.20.401.1
btw now i try erase again after i wait, and now i can erase cache. Now unlock it, i get the unlock menu, where i can choose unlock. But in cmd line i have rerror again. The to many link error...
Click to expand...
Click to collapse
ah yeah sorry that was on page 1 already. so the bootloader is unlocked ? yes the error is normal. is the phone still booting into OS And try to flash a recovery now

another strange thing, if i turn my phone on, with usb connected everithing looks ok
Code:
battery-voltage: 3730mV
but if i disconnect the usb and turn the phone on, it say, battery to low to flash.

Then you have to run the battery script
https://www.dropbox.com/s/aaah8gqz8j024xz/Batt script.bat
Phone in the bootloader and run the script from the fastboot folder with admin rights.
It will continuously reboot the phone and charge it little by little
When it hits 3800mV you flash again

Mr Hofs said:
Then you have to run the battery script
https://www.dropbox.com/s/aaah8gqz8j024xz/Batt script.bat
Phone in the bootloader and run the script from the fastboot folder with admin rights.
It will continuously reboot the phone and charge it little by little
When it hits 3800mV you flash again
Click to expand...
Click to collapse
Don't work, the phone don't reboot. If i try reboot it with fastboot reboot-bootlader, or from bootloader or with this script, it just turn off, and i need turn it on by hand.
Yesterday i can use the script, but today not.
yesterday when i finaly can turn on the phone and boot into android, i charge it, around 60% than i go to bed, and i also need to charge my primary phone, so i disconnect hox from charger, and turn it off. Now it say in bootloader baterry low for flash, funny...
Anyway i order a htc one x+ battery from ebay, so i need a few day, and i can test with new battery...
But i try to search some solution until i get the new battery.
edit:
btw my goal now, i just want to make it workable, and sell it. Thats why, i want relock, and install stock rom.
Or i just install THIS rom with custom recovery, or android revolution hd....

Unable to install stock RUU "FAILED (remote: 12 signature verify fail)"

Hi there, I've been trying to update my firmware all day. When using the RUU tool supplied by HTC, I get told I need to use the correct RUU for my device.
Code:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) product: m8_ul
(bootloader) cidnum: HTC__001
It is clear to see that I have the unlocked M8 so I don't understand why the m8_ul RUU seems to think otherwise.
As an alternative, I tried flashing the RUU zip file manually using the .401 file found here (lollipop version) but I get the following error:
Code:
sending 'zip' (1536838 KB)...
OKAY [ 48.278s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 120.166s
Just a few extra notes:
I have CWM recovery installed.
I have tried this both with and without a locked bootloader (locked makes more progress).
MID = 0P6B10000
Any help would be greatly appreciated as I really want to get Android Revolution HD running on my new (off ebay) phone

andyladd said:
When using the RUU tool supplied by HTC, I get told I need to use the correct RUU for my device.
Code:
(bootloader) cidnum: HTC__001
Click to expand...
Click to collapse
Do you mean you go the RUU from HTC's website? One that is a Windows executable (.exe) format?
If yes to either of those, its not for your CID; as I don't believe your CID has an "official" exe format RUU. And that is why its failing (trying to run an RUU for wrong CID/MID).
andyladd said:
As an alternative, I tried flashing the RUU zip file manually using the .401 file found here (lollipop version) but I get the following error:
Code:
sending 'zip' (1536838 KB)...
OKAY [ 48.278s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 120.166s
Click to expand...
Click to collapse
There are a few different 4.16.401 firmware zips floating around.
If you are s-on, you can only run one that is properly signed by HTC. I'm guessing that is the reason why it is failing (trying to run an unsigned firmware with s-on).
What exactly are you trying to flash? I know you don't have enough posts on XDA to post a link. But describe as best you can, where you got the firmware.
andyladd said:
[*]I have tried this both with and without a locked bootloader (locked makes more progress).
Click to expand...
Click to collapse
Are you s-on or s-off? If s-on, you absolutely need to relock the bootloader to install RUU or firmware.

redpoint73 said:
Do you mean you go the RUU from HTC's website? One that is a Windows executable (.exe) format?
Click to expand...
Click to collapse
Hi there, thanks for the response. Yes the RUU executable states that I am using the wrong RUU tool when I definitely am not (i'm using a European unlocked M8).
I have also tried flashing the 4.16.401 firmware zip through fastboot and HBOOT
HBOOT loads and checks the zip before requesting a press of the power button to restart however, upon restart it is clear that no flashing has taken place as the HBOOT and RADIO versions are unchanged.
The firmware is the lollipop .401 firmware from here
I believe this may have something to do with it (fastboot oem lock)
Code:
(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 (No such device))
finished. total time: 6.126s
If I S-OFF my device, am I right in assuming that the bootloader will not check the zip signature and install regardless?

andyladd said:
The firmware is the lollipop .401 firmware from here
Click to expand...
Click to collapse
I don't know if that one is signed or not. Try the one linked here: http://forum.xda-developers.com/showthread.php?t=2696282
andyladd said:
Hi there, thanks for the response. Yes the RUU executable states that I am using the wrong RUU tool when I definitely am not (i'm using a European unlocked M8).
Click to expand...
Click to collapse
As I mentioned, I haven't seen an executable RUU for the Euro CIDs (4.16.401). Where did you get it from, and what is the exact filename?
andyladd said:
I believe this may have something to do with it (fastboot oem lock)
Code:
(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 (No such device))
finished. total time: 6.126s
Click to expand...
Click to collapse
Does the bootloader screen say UNLOCKED or RELOCKED?
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
andyladd said:
If I S-OFF my device, am I right in assuming that the bootloader will not check the zip signature and install regardless?
Click to expand...
Click to collapse
You would be wrong to assume that. CID and MID checks are still enforced with s-off.
What s-off does do, is bypasses the need to relock the bootloader to flash an RUU or firmware.
s-off will also allow you to flash unsigned firmware, so it may help you getting the firmware flashed.

redpoint73 said:
I don't know if that one is signed or not. Try the one linked here: http://forum.xda-developers.com/showthread.php?t=2696282
As I mentioned, I haven't seen an executable RUU for the Euro CIDs (4.16.401). Where did you get it from, and what is the exact filename?
Does the bootloader screen say UNLOCKED or RELOCKED?
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
You would be wrong to assume that. CID and MID checks are still enforced with s-off.
What s-off does do, is bypasses the need to relock the bootloader to flash an RUU or firmware.
s-off will also allow you to flash unsigned firmware, so it may help you getting the firmware flashed.
Click to expand...
Click to collapse
I can't even flash stock recovery files through fastboot when my bootloader is locked. I get this error:
Code:
FAILED (remote: signature verify fail).
This device clearly has some kind of authentication issues.
The only alternative I haven't tried is to somehow attain a stock (kitkat/lollipop?) m8 rom and do the OTA through that. Would that work? If so where would I find such a rom?

andyladd said:
I can't even flash stock recovery files through fastboot when my bootloader is locked. I get this error:
Code:
FAILED (remote: signature verify fail).
This device clearly has some kind of authentication issues.
Click to expand...
Click to collapse
This is totally normal. You can't manually flash any recovery with the bootloader locked, stock or otherwise.
andyladd said:
The only alternative I haven't tried is to somehow attain a stock (kitkat/lollipop?) m8 rom and do the OTA through that. Would that work? If so where would I find such a rom?
Click to expand...
Click to collapse
You can get the stock nandroid and stock recovery from the following collection: http://forum.xda-developers.com/showthread.php?t=2701376
You will need the stock nandroid (and stock recovery) that corresponds with your firmware. Based on your hboot number (3.16) the nandroid you want is either 1.12.401 or 1.54.401. You may be able to determine the exact one needed by looking at the OS number listed on the bootloader screen, or main version on getvar all.
A nandroid is not a flashable ROM.zip, but rather a TWRP backup. Restore using the instructions provided in Post #3 of the collection thread under Questions & Answers. But in general, you will need to unlock the bootloader again, install TWRP (older version, since more recent versions won't work with your older hboot version) then restore the stock nandroid. Restore stock recovery. Boot into OS and check for updates in Settings. You will need to install a few updates to get up to the current 4.16.401 software and firmware.
After that, you can flash latest TWRP to the phone and install a custom ROM.

redpoint73 said:
This is totally normal. You can't manually flash any recovery with the bootloader locked, stock or otherwise.
You can get the stock nandroid and stock recovery from the following collection: http://forum.xda-developers.com/showthread.php?t=2701376
You will need the stock nandroid (and stock recovery) that corresponds with your firmware. Based on your hboot number (3.16) the nandroid you want is either 1.12.401 or 1.54.401. You may be able to determine the exact one needed by looking at the OS number listed on the bootloader screen, or main version on getvar all.
A nandroid is not a flashable ROM.zip, but rather a TWRP backup. Restore using the instructions provided in Post #3 of the collection thread under Questions & Answers. But in general, you will need to unlock the bootloader again, install TWRP (older version, since more recent versions won't work with your older hboot version) then restore the stock nandroid. Restore stock recovery. Boot into OS and check for updates in Settings. You will need to install a few updates to get up to the current 4.16.401 software and firmware.
After that, you can flash latest TWRP to the phone and install a custom ROM.
Click to expand...
Click to collapse
This is going to be a long night! Thanks for the help, I'll keep you posted.

Help me fix BRICK

hi,
someone gave me a bricked HTC M8 and i wanna fix it for him. i don't know what got him to be bricked...
the situation is this:
- Boot Loop
- Fastboot working
- Unlocking Worked
- Able to flash TWRP and enter recovery mode
- mounting for all partition fails with unable to mount
- TWRP "Repair" fails: "E:/sbin/e2fck -fp /dev/block/mmcnlk0p47 proccess ended with ERROR=8 ; unable to repair /data ; Error repairing fail system"
- TWRP "Change File System" to ESX4 not working: "unable to mount /data ; Unknown MTP message type: 1 ; Error changing file system; unable to mount /system ; unable to mount /data ; unable to mount /devlog ; unable to mount storage"
fastboot getvar all:
(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.17.1540.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 55eb39ab
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
PLS HELP what doo?

Install the dev edition ruu.....

Mr Hofs said:
Install the dev edition ruu.....
Click to expand...
Click to collapse
how?

omer323 said:
hi,
someone gave me a bricked HTC M8 and i wanna fix it for him. i don't know what got him to be bricked...
the situation is this:
- Boot Loop
- Fastboot working
- Unlocking Worked
- Able to flash TWRP and enter recovery mode
- mounting for all partition fails with unable to mount
- TWRP "Repair" fails: "E:/sbin/e2fck -fp /dev/block/mmcnlk0p47 proccess ended with ERROR=8 ; unable to repair /data ; Error repairing fail system"
- TWRP "Change File System" to ESX4 not working: "unable to mount /data ; Unknown MTP message type: 1 ; Error changing file system; unable to mount /system ; unable to mount /data ; unable to mount /devlog ; unable to mount storage"
fastboot getvar all:
(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.17.1540.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 55eb39ab
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
PLS HELP what doo?
Click to expand...
Click to collapse
You CID number BS_US001 is developper edition M8. As @Mr Hofs suggested, Download Dev edition RUU, Boot into fastboot and install RUU.

Grab this RUU.exe (not OTA, RUU): https://onedrive.live.com/?authkey=!AJ5pbUC2atPkSaA&id=8B8E71545D3D985B!1658&cid=8B8E71545D3D985B
Turn On phone and go to bootloader, connect it to PC, install drivers and run RUU.exe on PC.

omer323 said:
- Unlocking Worked
Click to expand...
Click to collapse
I assume you mean bootloader unlock, as the term "unlock" is vague and can mean several things.
You will need to relock to run the RUU, since you are s-on. Do so with the command:
fastboot oem lock
Also, this isn't a brick. A brick by definition is not fixable. At least not without opening the phone, and JTAG, replacing motherboard, etc.
What you have is no boot, and you don't know how to recover. That isn't a brick.

WTF.
i did "fastboot oem lock" which resulted with:
[PGFS] partition_update_pgfs: pg1fs_security
TZ_HTC_SVC_ENC ret = 0
[PGFS] partition_update_pgfs: pg2fs_sec_recover
Lock successfully...
deinit_lcd
mipi display off
mdp_clock_off
turn off fd8c2308 failed 1 times. Try again...
disable_mmss_clk done
pll1_disable done
TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7
[CRITICAL] SPMI write command failure:
= 4
[CRITICAL] SPMI write command failure:
= 4
[ERR] Cannot halt SPMI arbiter!!
[INFO] Rebooting device
us read failed (No such file or directory))
tal time: 1.227s
than i run RUU, which failed, i pressed recover, it told to me to unplug the device and shut it down.
and not it won't turn on no mather what!! not even battery logo....
WHAT HAVE I DONE

omer323 said:
WTF.
i did "fastboot oem lock" which resulted with:
Click to expand...
Click to collapse
Was it unlocked before, or not? This wan't clear to me, from what you posted.
After the command, was it RELOCKED or UNLOCKED?
omer323 said:
than i run RUU, which failed
Click to expand...
Click to collapse
What was the failure message and/or error number?
RUU failed before sending or writing anything?
You need to be specific, and provide as much detail as necessary.
omer323 said:
i pressed recover, it told to me to unplug the device and shut it down.
and not it won't turn on no mather what!! not even battery logo....
Click to expand...
Click to collapse
What does that mean "no matter what"? I doesn't tell us anything about what you tried, or didn't try. Please be specific instead of vague statements, that tell us nothing.
Try holding power and vol up for 30 to 60 seconds, and see if there is any change.
I don't think you did anything serious, that wasn't already screwed up. You are s-on, and assuming the RUU failed before sending/writing anything, then a true brick is unlikely.

redpoint73 said:
Was it unlocked before, or not? This wan't clear to me, from what you posted.
Click to expand...
Click to collapse
UNLOCKED
redpoint73 said:
After the command, was it RELOCKED or UNLOCKED?
Click to expand...
Click to collapse
RELOCKED
redpoint73 said:
What was the failure message and/or error number?
RUU failed before sending or writing anything?
You need to be specific, and provide as much detail as necessary.
Click to expand...
Click to collapse
i don't remember exactly what heppened, BUT i found RUU log file on my computer,
i attached the log.
redpoint73 said:
What does that mean "no matter what"? I doesn't tell us anything about what you tried, or didn't try. Please be specific instead of vague statements, that tell us nothing.
Try holding power and vol up for 30 to 60 seconds, and see if there is any change.
I don't think you did anything serious, that wasn't already screwed up. You are s-on, and assuming the RUU failed before sending/writing anything, then a true brick is unlikely.
Click to expand...
Click to collapse
the screen is black.
every combination of buttons i try results NOTHING - nothing on screen, no vibrations...
i tried holding all the combinations for a long time...
the only thing i get - if i plug the device via USB, every ~20 seconds i see in device manager that it disconnect for a second and connected again as QHSUSB_BULK
THANK YOU SO MUCH FOR HELPING~!!!

omer323 said:
every combination of buttons i try results NOTHING - nothing on screen, no vibrations...
i tried holding all the combinations for a long time...
Click to expand...
Click to collapse
You shouldn't be trying "every" combination. You should be trying the one I specified.
Put the phone on wall charger (not connected to computer) or a few hours, and try again.
Then try the combo I specified. Try it with and without the wall charger connected.
---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------
What RUU did you run exactly? Was it the one linked in Post #5 above? What was the exact file name?
I don't have any reason to be suspicious of this link, specifically. But on the other hand, this RUU is easily downloaded direct from HTC, and I don't see a reason to download from some other (unconfirmed) source. Or for all we know, the download was corrupt/damaged.

redpoint73 said:
You shouldn't be trying "every" combination. You should be trying the one I specified.
Click to expand...
Click to collapse
tried it.... nothing...
redpoint73 said:
Put the phone on wall charger (not connected to computer) or a few hours, and try again.
Then try the combo I specified. Try it with and without the wall charger connected.
Click to expand...
Click to collapse
ill try that...
redpoint73 said:
---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------
Click to expand...
Click to collapse
redpoint73 said:
What RUU did you run exactly? Was it the one linked in Post #5 above? What was the exact file name?
I don't have any reason to be suspicious of this link, specifically. But on the other hand, this RUU is easily downloaded direct from HTC, and I don't see a reason to download from some other (unconfirmed) source. Or for all we know, the download was corrupt/damaged.
Click to expand...
Click to collapse
yes, the link he gave me.
filename: RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2

omer323 said:
filename: RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2
Click to expand...
Click to collapse
Well, the file name is right. Assuming the file is what it says it is, and not damaged or corrupt during download, it possible for the correct RUU to brick the phone. It doesn't happen often, but I have seen it happen a few times, even on completely stock (unmodified) M8 devices and the correct, official RUU.
Or its possible that it was messed up before, such as bad emmc, and the RUU just made it worse.
In any case, charging for a few hours, then trying power+vol up is about all you can do at this point.

QHUSB is Qualcomm emergency mode. Try to get out of it by pressing (for long) Vol UP + Power.
For me it looks like fried eMMC chip... Sometimes it happens. Some time ago my One M7 died at me because of this in exactly the same way.
eMMC chip was corrupted before running RUU - unable to mount partition and errors during "fastboot oem lock".
redpoint73 said:
I don't have any reason to be suspicious of this link, specifically. But on the other hand, this RUU is easily downloaded direct from HTC, and I don't see a reason to download from some other (unconfirmed) source.
Click to expand...
Click to collapse
It's from this thread: http://forum.xda-developers.com/showthread.php?t=2701376
I don't think it's suspicious or unconfirmed.
I'm pretty sure that this RUU.exe is correct, because I was flashing with it few times.
Please check MD5 checksum. My working RUU.exe (downloaded from thread linked above) checksum is: c661c073d368274c3137d5080c88a45c and file size of 1 548 439 552 bytes (on disk).

radkor said:
It's from this thread: http://forum.xda-developers.com/showthread.php?t=2701376
I don't think it's suspicious or unconfirmed.
I'm pretty sure that this RUU.exe is correct, because I was flashing with it few times.
Click to expand...
Click to collapse
As I said, I don't have any reason to doubt the source. But for lack of any other evidence (the subsequent report that you did use it a few times does count for something there) I have no reason to trust it more than the official source. The RUU is available for download direct from HTC, so I don't see a reason to use a mirror (unless its faster): http://www.htc.com/us/support/htc-one-m8/news/
Again, I don't doubt the mirror. Mr Hofs has made valuable contributions here, so if he posted it; I trust it. But I was just trying to consider every possibility for the OP's issue.

redpoint73 said:
The RUU is available for download direct from HTC, so I don't see a reason to use a mirror (unless its faster): http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
OK, but on HTC's site it's only newest MM update available for download.
I can't see a link for older LP ROM which OP was using. Best for him (as he has S-ON) was to reflash ROM version that he already have, basing on pasted "fastboot getvar all" result.
If he would flash newer version (MM) with S-ON, then he will be stuck on this newer version without possibility to downgrade, unless he's S-OFF.
As I said earlier, phone supposedly "bricked" earlier, what you can see during "fastboot oem lock" and resulting error messages after issuing this command.
QHSUSB_DLOAD mode is because of bad NAND.
I've had similiar issue with my M7: http://forum.xda-developers.com/htc-one/help/bricked-device-swap-to-dev-ed-partially-t3015574/
I hope you're not blaming me for unsuccessful OP's phone flashing or earlier bricking?

radkor said:
OK, but on HTC's site it's only newest MM update available for download.
Click to expand...
Click to collapse
You're right, I forgot we were talking about LP (OP's current state).
The direct HTC link for OP's current LP version is here: http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2.exe
radkor said:
I hope you're not blaming me for unsuccessful OP's phone flashing or earlier bricking?
Click to expand...
Click to collapse
Of course not! I never stated any such thing. Just considering every possibility, like a corrupt RUU file. But as I already stated, the fact that you reported using it successfully (and more than once) tells me the file is good.

redpoint73 said:
The direct HTC link for OP's current LP version is here: http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2.exe
Click to expand...
Click to collapse
I'm downloading it right now just to compare it with RUU.exe posted on Mr Hofs' thread.
EDIT:
OK, CRC is exactly the same. Everyone can check this. So I think we can exclude corrupted RUU.exe linked on Mr Hofs' thread. It's exactly the same as the file on HTC servers.

charged for hours, pressed VOL-UP+POWER for 2 minutes with or without charging, and..... NOTHING
the only response i get is the red led when charged and the QHUSB when plugged to computer
so i guess it's bricked for ever

omer323 said:
charged for hours, pressed VOL-UP+POWER for 2 minutes with or without charging, and..... NOTHING
the only response i get is the red led when charged and the QHUSB when plugged to computer
so i guess it's bricked for ever
Click to expand...
Click to collapse
Most likely, yes.
I mentioned early in the thread that this wasn't a brick. As long as the screen comes on (as it did earlier), it almost never is. But this is the relatively uncommon exception, which can be caused by a bad emmc or radio brick.

omer323 said:
charged for hours, pressed VOL-UP+POWER for 2 minutes with or without charging, and..... NOTHING
the only response i get is the red led when charged and the QHUSB when plugged to computer
so i guess it's bricked for ever
Click to expand...
Click to collapse
Try Power + Volume Up + Volume Down more that 2 minutes ... usually about to close 3 minutes, it should up. This is how I got out from QHUSD many times...
But a bad emmc is also possible .. if that is the reason, then only HTC can fix it.
Also after fastboot oem lock, did you do fastboot reboot-bootloader to confirm the bootloader is relocked then only run RUU ?
I don't see you mentioned that except after fastboot oem lock you ran the RUU right away.

HELP - Can't relock bootloader

Originally unlocked bootloader through HTC-DEV
CID: 11111111
Hboot 3.19.0.0000
Radio-1.2121331147A1.19_2G
M8_UL_CA PVT SHIP S-OFF
I'm trying to relock the bootloader so I can RUU, however keep getting the following error when running "fastboot oem lock"
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(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 = -131073 (0xFFFDFFFF)
(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.230s
After the above message, the phone goes from unlocked -> relocked. However I believe the phone is still actually unlocked because I'm getting Error: 155 when I try to run an RUU. I also can see the red text on the charging screen indicating the phone is unlocked.
I have also used this method http://forum.xda-developers.com/showthread.php?t=2708571 to try unlock/relock, and also tried to relock and use HTC-DEV to lock but no matter what, I'm still getting Error 155.
Also, none of the user data is being wiped when I use fastboot flash unlocktoken Unlock_code.bin

blazerxzero said:
Originally unlocked bootloader through HTC-DEV
CID: 11111111
Hboot 3.19.0.0000
Radio-1.2121331147A1.19_2G
M8_UL_CA PVT SHIP S-OFF
1. I'm trying to relock the bootloader so I can RUU, however keep getting the following error when running "fastboot oem lock"
2. After the above message, the phone goes from unlocked -> relocked. However I believe the phone is still actually unlocked because I'm getting Error: 155 when I try to run an RUU. I also can see the red text on the charging screen indicating the phone is unlocked.
Click to expand...
Click to collapse
1. You don't need to relock bootloader to run RUU on S-Off device.
2. Are you trying to run Marshmallow RUU ? You'll get error 155 if the current firmware is lower than Marshmallow. You need to flash its Marshmallow firmware first then run RUU.

Thanks for the reply, I tried your method of matching the RUU with the firmware version and got a different error.
Error couldn't allocate space, even though the RUU image was smaller than the available storage.
The solution which resolved the problem was to rename the correct RUU version zip load onto SD card and flash using the bootloader auto-detection method.

Cant relock bootloader on Htc One M8

Hi, can anyone tell me whats the problem with my phone? I used to be able to relock the bootloader for upgrade. Unlocked and install CM roms. Try to relock for upgrades again but I cant do so anymore...
This is what I get from fastboot:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(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) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.304s
Can anyone shed me some lights? Thanks in advance...

HTC doesn't use the standard commands for this. Check out http://forum.xda-developers.com/showthread.php?t=2708571

jshamlet said:
HTC doesn't use the standard commands for this. Check out http://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
fastboot oem lock typically works just fine on this device to make the bootloader RELOCKED (for RUU, etc.).
The thread you linked, is to make it say LOCKED (only possible with s-off) such as for warranty purpose.
---------- Post added at 02:01 PM ---------- Previous post was at 01:58 PM ----------
Veydron said:
This is what I get from fastboot:
Can anyone shed me some lights? Thanks in advance...
Click to expand...
Click to collapse
The errors may indicate a hardware (emmc) failure. The bootloader screen still says UNLOCKED, correct? I've seen a few cases, there the fastboot oem lock command yields error messages, but the bootloader is RELOCKED regardless.

Thanks redpoint73. Initially I thought my battery having problem cos everytime when it reached below 15% it just went auto off without a proper powering down. After that once recharged, either app datas or radio will be corrupted. Apps i can reinstall again but if radio, I need to rerun the ruu. This happened twice already. So the problem that I have, isnt entirely due to the battery?

Sometimes I cant even switch it on. I need to remove the battery for sometime and it might work sometimes.

Veydron said:
Thanks redpoint73. Initially I thought my battery having problem cos everytime when it reached below 15% it just went auto off without a proper powering down. After that once recharged, either app datas or radio will be corrupted. Apps i can reinstall again but if radio, I need to rerun the ruu. This happened twice already. So the problem that I have, isnt entirely due to the battery?
Click to expand...
Click to collapse
Exactly same problem. After recharging, some apps were forced error and require re-installing. It's happened to me 4-5 times.

LOL so im not alone...which i thought i am lol