Related
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.
Hi !
One of my friend ask me to try to save his One M9 phone, that seems to be bricked.
Here is the context :
- I absolutely don't know what he did, and it seems he don't either...
- The phone state is : Software status : Modifed, S-ON, and LOCKED
- I can't have another screen that Fastboot bootloader
The only options in the bootloader menu are :
REBOOT : it works
REBOOT TO BOOTLOADER : it works
BOOT TO DOWNLOAD MODE : does not work (Failed to boot to download mode)
BOOT TO RECOVERY MODE : does not work (Failed to boot to recovery mode)
POWER DOWN : it works
I tried a lt of things, and read a lot of threads before posting this one.
What i can say for the moment is :
- RUU flash using exe : does not work, i get an error saying the battery is too low
- RUU flash using SD card (extract rom.zip, renamed 0PJAIMG.zip, and put on the root of SD card) : zip is not detected at boot
- Getting bootloader unlocked : does not work, because fatboot oem get_token_identifier command seems unknown (probably because oem commands only work in download mode for this phone)
- Getting S-OFF : seems impossible without OS, as it needs Sunshine app installed...
- Few fastboot commands are OK (devices, getvar all, ...) but most of it are refused because of S-ON
- No adb commands are working
Here is the output of fastboot getvar all :
Code:
D:\ANDROID\RUU\RUU>htc_fastboot getvar all
(bootloader) version: 0.5
(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: FA56GYJ01267
all:
finished. total time: 0.094s
htc_fastboot finished. total time: 0.718s
So, from your experts point of view, is this phone definitely bricked, or is there a way to save it ?
Thanks for your precious help guys !
Hey! I have the exact same problem. Anyone knows how to fix that?
I unrooted, stocked and relocked the bootloader. Everything went fine first, was using the phone about two days. But after a restart I'm stuck in bootloader and can't boot to download nor recovery mode.
Phone is only working with fastboot commands.
I also tried these steps OP tried and everything is the same.
I tried to flash hosd file and this works, but still not able to boot to download mode.
The HTC One is an unbranded EU model with 3.35.401.12 (<- but I think there's nothing on the phone right now)
i am also facing same problem with 2 htc one m9 which i have, i also have XTC2CLIP box which is professional tool for all htc devices, i can S-off with this box of all htc phone even no os needed, but phone should accept bootloader mode & ftm mode, & in this case where we can only goto fastboot mode, S-off command not working in state... i spend lot of time but no luck... but i still believe its only software bug & can be solve with fastboot commands. because i aslo read about same problem on htc X model. & they use fastboot command for this problem. but these commands not working on m9 case.
no solution for this? I have one m9 here exatly with the same situation, already did all your debuging with the same results
Hi there! I'm new here, created an account specially for replying to this thread:
So I'm having the same problem, phone (EU M9) died on it's own. Everything is stock.
Tried all of the above, also no results...
Here is my log from "fastboot getvar all"
Code:
C:\Android>fastboot getvar all
(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:HT54NYJ04596
all:
finished. total time: 0.147s
If anyone has any ideas left, I'm happy to try them. For now, it's an ugly paperweight
If it died on its own and in a stock state then you can safely assume it's dead. Most likely nand failure.
Ps, dont all m9 serials start with an "F"?.
Beamed in by telepathy.
thank you
My guess is it tried to do an OTA update overnight, don't know exactly where it went wrong.
By the way, I do get some ADB communication:
First reboot to bootloader (so it doesn't say "Security Warning"), then select 'boot to Recovery Mode' and wait for the red triangle.
If it doesn't reach that point, reboot to bootloader once more. If it does reach the red triangle: hold the Power button and press the Volume Up button once. You can then release the Power button and Recovery Mode should become visible. Note that I tried several options in this menu including "Install from ADB" and "Install from SD Card", but both gave errors.
Hope someone can use this information.
I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?
KaiLoi said:
I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?
Click to expand...
Click to collapse
If it's spewing failed to mount errors then yes, dead phone. Only htc will be able to fix it.
Beamed in by telepathy.
For some reason after returned from a trip that i had my phone turned off , my phone won't boot normally.
It boots to a menu where my only options are:
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
On top it says :
Software status modified
Locked
S-ON
I haven't flashed anything before i get this error.
I tried to see what i can do now but it seems allow unlock bootloader is not checked and since i can't boot to ROM there is no way to flash anything.
I can boot to download mode only and reboot to bootloader. boot to recovery fails and says this build is for development purposes only.
thats my phone info
(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:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357662244637936
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__032
all:
I tried to flash 3.35.401.12 RUU renaming it to 0PJAIMG from SD card and it gets in a loop with HTC logo. going off and on doing nothing.
Every other RUU i tried to flash fails with RUU security warning because S-ON and locked i guess.
So is there a way to fix this? Any RUU that can be flashed ? Any way to flash as recovery image being S-ON and Locked?
Thank you anyway.
@thrylosss: For your own safety you should remove your IMEI. It can be used for scam by others.
Did you boot to Download Mode for flashing the RUU? If the RUU didn't reboot to Download Mode by it's own during the flash what happened after you manually rebooted to that mode?
There is no newer, publicly available RUU you could use. The only alternative to the RUU you already tried is Llabtoofer's RUU service. There is a direct link in the ReadMe thread.
I reboot to download mode and pressed vol up to start flashing. Then i got updating UI sign and then mobile restarted and got into fast loops showing HTC logo. i had to press all 3 button (POWER + VOL buttons ) to get back to the first menu.
Whats the link to the Llabtoofer's RUU?
if its this you mean
SKU: 401 - CID: HTC__001, HTC__J15, HTC__102, HTC__Y13, HTC__A07, HTC__032, HTC__016, HTC__M27, HTC__002 or HTC__031
1.32.401.8
1.32.401.15
1.40.401.8
2.10.401.1
3.35.401.12
i am trying them all right now.
But is there a 3.35.401.32 RUU?
When the device started to "fast loop", how long did you let it do that for?.
I remember mine taking an update and it did that for a while. I eventually took over an hour to update.
Beamed in by telepathy.
I let it for a while but it was obvious was doing the same thing. restarting after 2-3 seconds.
I contacted with Llabtoofer's RUU service and told me it can't be fixed without using extra hardware specialized in unlocking and removing security.
Thank you anyway.
thrylosss said:
I let it for a while but it was obvious was doing the same thing. restarting after 2-3 seconds.
I contacted with Llabtoofer's RUU service and told me it can't be fixed without using extra hardware specialized in unlocking and removing security.
Thank you anyway.
Click to expand...
Click to collapse
Did you find a solution yet? I have the same situation for a week now. My phone is locked, s-on and on a bootloader loop even though I haven't done any flashing, rooting etc. I just can't reinstall 3.35.401.32 because my phone is s-on. Is there a solution for that?
Could anyone help please?
tunceratan said:
Did you find a solution yet? I have the same situation for a week now. My phone is locked, s-on and on a bootloader loop even though I haven't done any flashing, rooting etc. I just can't reinstall 3.35.401.32 because my phone is s-on. Is there a solution for that?
Could anyone help please?
Click to expand...
Click to collapse
As i said there is nothing you can do with just a PC and a software. You need a different equipment. You have to take it to a service center.
thrylosss said:
As i said there is nothing you can do with just a PC and a software. You need a different equipment. You have to take it to a service center.
Click to expand...
Click to collapse
There is plenty that can be done with PC and software - please don't offer blanket advice like this without a clear explanation applicable to the specific situation of the thread. Other users having similar difficulties may come across this conversation and give up without realizing that they have many options.
[EDIT]@thrylosss - It sounds like in your case, your phone is not serviceable without specialized equipment, as indicated by Llabtoofer's RUU service. This isn't necessarily the case with all folks having similar issues.[/EDIT]
Hey sorry for my late response. But there is nothing can be done since it is S-ON , is LOCKED and allow unlock bootloader is not checked . So when these 3 conditions meet there is nothing you can do without extra equipment.
So
1) LOCKED
2) S-ON
3)Allow unlock bootloader : NOT checked.
And of course can not boot to recovery mode.
More clear now?
Hi, seems this is a really common issue. Has anyone managed to successfully get the phone working from this state? If so what did you have to do to get it back?
Htc m9 s-off locked update android 7
My phone is htc m9 s off locked t mobile usa
While i update to android 7 from phone i got message mobile is modified
Previous software is marshmallow
If i tried htc official software manually wil it be okay? Or can damage my previous software?
I know its late, but ive come across a file with flashtool and (unfortunately) the wrong firmware. Mine is a verizon which HTC says cannot be flashed, and the file i found is for Sprint firmware. However, I was able to get the phone to react and do believe that if i had the correct firmware it would flash. here is the link: https://htcstockrom.com/htc-one-m9
Hi all,
I'v really a big problem , my M9 is hanging in a bootloop.
My last installed ROm was a ViperOneM9 6.1.0. I used it for around 2 month. But from one day to the next my phone is in a bootloop.
Now it won't boot into the download boot (TWRP 3.0.2 is installed ), it won't boot into recovery mode (bootloop) ant it won't boot.
The only mode that is possible is the Bootloader mode.
I tried to flash with the fastboot command. I tried different 0PJAIMG files but I got allways the same error message:
C:\adb>htc_fastboot.exe flash zip 0PJAIMG_HIMA_UHL_L50_SENSE70_Vodafone_CH-DE_1.32.166.6_R1_Radio_01.01_U11440261_56.01.
50303G_3_F_release_425117_signed.zip > error.txt
sending 'zip'... (126768 KB) OKAY
writing 'zip'... FAILcannot flash this partition in s-on state
FAILED (remote: cannot flash this partition in s-on state)
Software status is modified
*** Unlocked ***
*** S-ON ***
*** Security warning ***
and fastboot getvar all:
C:\adb>htc_fastboot.exe getvar all
(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:FA58XXXXX
all:
Execution time is 146(ms)
It'll be great if someone could help me
thx
That's the dead nand issue (c.f. the FAQ of the ReadMe thread).
Sent from my HTC One M9 using XDA Labs
I have the same problem.Its just restart,i didnt have any problems before .I cant now go in download ,or recovery mode.I had twrp recovery installed. When try downoad mode,its just says to me failed to boot to download mode . Any solutions for that NAND issue ,how Flippy498 says ?
As said before, read the FAQ of the ReadMe thread. It's already explained there.
Same problem but I'm not rooted...
HTC One M9 Sprint, stuck in boot loop
I just checked the Dead NAND post in the FAQ... matches my issue too.
Q17: My phone is completely stock and started bootlooping during normal usage. Now I can only enter the Bootloader since I face booting errors as soon as I try to enter the Download Mode or the Stock Recovery. How can I fix this problem?
A: This seems to be another symptom of the NAND death (c.f. the black download mode error screen in Q8). So far, it's not fixable without HTC's help. In other words: You need to send your phone to HTC's repair service if you want to keep it.
So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still disabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?
PirateNL said:
So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still enabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?
Click to expand...
Click to collapse
im in the same situation ,i'm currently looking at data recovery option from gillware since apparently they literally go the extra mile physically to extract data. but im hoping there is options for me to unbrick it before deciding on that option
venom55521 said:
im in the same situation ,i'm currently looking at data recovery option from gillware since apparently they literally go the extra mile physically to extract data. but im hoping there is options for me to unbrick it before deciding on that option
Click to expand...
Click to collapse
Well at least the data on the device is not worth much to my friend. Let me know if you find were able to unbrick it
PirateNL said:
So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still disabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?
Click to expand...
Click to collapse
ADB won't detect it if USB debugging is turned off.
Can you boot to RUU mode? If so you could restore it perhaps that way. If you are booted to that you can run an RUU.exe
The command is:
fastboot oem rebootRUU
xunholyx said:
ADB won't detect it if USB debugging is turned off.
Can you boot to RUU mode? If so you could restore it perhaps that way. If you are booted to that you can run an RUU.exe
The command is:
fastboot oem rebootRUU
Click to expand...
Click to collapse
Thanks for your reply. I'm not sure on how I can execute that command without ADB/USB debugging being enabled? Any advice there?
PirateNL said:
Thanks for your reply. I'm not sure on how I can execute that command without ADB/USB debugging being enabled? Any advice there?
Click to expand...
Click to collapse
You don't have to have USB debugging on to use fastboot commands, only ADB commands. For many fastboot commands, you need an unlocked bootloader. For this one you don't. Or at least you didn't on the M8 before HTC introduced download mode. I'm pretty sure it will still work.
xunholyx said:
You don't have to have USB debugging on to use fastboot commands, only ADB commands. For many fastboot commands, you need an unlocked bootloader. For this one you don't. Or at least you didn't on the M8 before HTC introduced download mode. I'm pretty sure it will still work.
Click to expand...
Click to collapse
So I only had time to test this today. And you were right i was able to trigger this command:
fastboot oem rebootRUU
The phone then rebooted showed the grey HTC boot screen and soon after it started the boot loop sequence again. What am I suppose to do now? Is there anything I can flash in this RUU mode? Thanks again for your help.
PirateNL said:
So I only had time to test this today. And you were right i was able to trigger this command:
fastboot oem rebootRUU
The phone then rebooted showed the grey HTC boot screen and soon after it started the boot loop sequence again. What am I suppose to do now? Is there anything I can flash in this RUU mode? Thanks again for your help.
Click to expand...
Click to collapse
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.
xunholyx said:
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.
Click to expand...
Click to collapse
Unfortunately I do not see the red security warning, it just a grey HTC logo for a few seconds, then it reboots and then shows a white HTC logo + "powered by android" and then its stuck in the boot loop again.
The phone is an EU-model, this is the output you requested:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA69KBN01219
all:
finished. total time: 0.360s
The version-main variable does not seem to be there
xunholyx said:
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.
Click to expand...
Click to collapse
Hey man, if you have some time today. Could you please look at the output I sent? Im not sure what to do next.
Thanks in advance
PirateNL said:
Hey man, if you have some time today. Could you please look at the output I sent? Im not sure what to do next.
Thanks in advance
Click to expand...
Click to collapse
The readout doesn't really say anything. With the HTC 10, and starting with the M9 I believe (I never owned one), you can only get a proper getvar from download mode or RUU mode. You can't get one from bootloader anymore like you used to be able to.
You said it was a EU model, so I would suspect it's WWE. The RUUs for that are available, but you can't flash it in bootloader, only download or RUU mode.
exactly the same problem here
PirateNL said:
Unfortunately I do not see the red security warning, it just a grey HTC logo for a few seconds, then it reboots and then shows a white HTC logo + "powered by android" and then its stuck in the boot loop again.
The phone is an EU-model, this is the output you requested:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA69KBN01219
all:
finished. total time: 0.360s
The version-main variable does not seem to be there
Click to expand...
Click to collapse
I have exactly the same problem with my HTC10, i don't have access to download mode, recovey, system, i even tried to boot to an image of twrp and i can't.
Code:
D:\Android\platform-tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA661BN06728
all:
Finished. Total time: 0.393s
Click to expand...
Click to collapse
Click to expand...
Click to collapse
xunholyx said:
The readout doesn't really say anything. With the HTC 10, and starting with the M9 I believe (I never owned one), you can only get a proper getvar from download mode or RUU mode. You can't get one from bootloader anymore like you used to be able to.
You said it was a EU model, so I would suspect it's WWE. The RUUs for that are available, but you can't flash it in bootloader, only download or RUU mode.
Click to expand...
Click to collapse
OK that makes sense. But as you know I cannot get into RUU nor download mode. I guess it really is bricked then. Oh well thanks for your time and help.
PirateNL said:
OK that makes sense. But as you know I cannot get into RUU nor download mode. I guess it really is bricked then. Oh well thanks for your time and help.
Click to expand...
Click to collapse
It might not be. A friend reminded me of a method in a conversation about something else. I'm at work right now, but I'll reply again later on when I'm home
Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.
no luck
xunholyx said:
Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.
Click to expand...
Click to collapse
D:\Android\platform-tools>fastboot flash radio radio.img
Sending 'radio' (54629 KB) OKAY [ 1.341s]
Writing 'radio' FAILED (remote: 'cannot flash
this partition in s-on state')
fastboot: error: Command failed
it says that because it is in S-On state, any ideia ohow can i change the S state?
thank you mate
xunholyx said:
Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.
Click to expand...
Click to collapse
Tried to revive it today. Unfortunately getting the same error as our friend in the post above me:
Code:
C:\adb>fastboot flash radio radio.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (54629 KB)...
OKAY [ 1.366s]
writing 'radio'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.456s
So to summarize:
- Not able to boot into download/recovery/RUU mode
- Cannot flash images using fastboot due to S-ON
I guess that's it, RIP HTC 10.
PirateNL said:
Tried to revive it today. Unfortunately getting the same error as our friend in the post above me:
Code:
C:\adb>fastboot flash radio radio.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (54629 KB)...
OKAY [ 1.366s]
writing 'radio'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.456s
So to summarize:
- Not able to boot into download/recovery/RUU mode
- Cannot flash images using fastboot due to S-ON
I guess that's it, RIP HTC 10.
Click to expand...
Click to collapse
costum rom was installed on my phone I deleted everything with trwp normally I should have installed a new rom file but I didn't now the htc logo is stuck, there is twrp unlocked but I can't access it the boot loader does not open, because there is no rom, it does not open normally, there is only htc logo and red warning, maybe I can open the security mode or something else I am very tired