boot loops after battery replacement - One (M9) Q&A, Help & Troubleshooting

so here's the deal :
have an m9, stopped using it because i wanted to change a battery, got a different phone meanwhile (xiaomi 4a)
before sending the phone to have the battery replaced, it booted into TWRP touch recovery without any issues.
=====
after the lab installed the new battery, i'm stuck in a loop.
https://image.ibb.co/gQC5sw/IMG_20171129_011920.jpg
software status : modified
Unlocked
s-on
security warning
the following options and their outcomes :
reboot - boot loops (no rom installed, so normal behavior.)
reboot to bootloader = reboots into bootloader normally.
boot to download mode = failed to boot into download mode
boot to recovery = boot loop with the htc logo on a black background
power down =
1. when plugged in, shuts the phone off for about 3 seconds, then boots immediatley into bootloader again.
2. when unplugged, turns phone off.
also, when the device is off and i plug in a charger (from wall or pc) it turns on by itself and boots into bootloader.
i've tried charging the device but it doesn't seem to help, even with the script that constantly boots into bootloader to try and remedy that issue.

These are symptoms for a dead nand.

lucyr03 said:
These are symptoms for a dead nand.
Click to expand...
Click to collapse
is it worth repairing? or just getting a new phone?

kent4ro said:
is it worth repairing? or just getting a new phone?
Click to expand...
Click to collapse
Flash the firmware. Find the zip of whatever firmware it is running now and flash via download mode. Eg if it is running 3.35.401.12 then flash 3.35.401.12. You'll be amazed what stock firmwares fix.

shivadow said:
Flash the firmware. Find the zip of whatever firmware it is running now and flash via bootloader. Eg if it is running 3.35.401.12 then flash 3.35.401.12. You'll be amazed what stock firmwares fix.
Click to expand...
Click to collapse
once i'll get home i'll try to find out what version its currently running - hopfully you're right.

Mine did the same thing. I thought it was just an oddity but it appears to be quite common. If you have nfc issues let me know as mine is borked but I don't know if it is related or not yet.

shivadow said:
Flash the firmware. Find the zip of whatever firmware it is running now and flash via download mode. Eg if it is running 3.35.401.12 then flash 3.35.401.12. You'll be amazed what stock firmwares fix.
Click to expand...
Click to collapse
From what he write in first post, he can't access download mode.

lucyr03 said:
From what he write in first post, he can't access download mode.
Click to expand...
Click to collapse
but he can access TWRP and flash the zip there. ive never done adb side load, maybe thats a possibility also. i just know when flashing firmware through adb the system.img is too large and theres a tool that separates it or something like that, like i said im not too familiar, i tried it once and said forget that. i personally wouldnt give up on the phone, its worth learning how to fix the issue in case similar problems happen in the future with any phone, take it as a learning curve.

Warwick555 said:
but he can access TWRP and flash the zip there. ive never done adb side load, maybe thats a possibility also. i just know when flashing firmware through adb the system.img is too large and theres a tool that separates it or something like that, like i said im not too familiar, i tried it once and said forget that. i personally wouldnt give up on the phone, its worth learning how to fix the issue in case similar problems happen in the future with any phone, take it as a learning curve.
Click to expand...
Click to collapse
I don't think he can access recovery
Sent from my HTC One M9 using Tapatalk

kent4ro said:
so here's the deal :
have an m9, stopped using it because i wanted to change a battery, got a different phone meanwhile (xiaomi 4a)
before sending the phone to have the battery replaced, it booted into TWRP touch recovery without any issues.
=====
after the lab installed the new battery, i'm stuck in a loop.
https://image.ibb.co/gQC5sw/IMG_20171129_011920.jpg
software status : modified
Unlocked
s-on
security warning
the following options and their outcomes :
reboot - boot loops (no rom installed, so normal behavior.)
reboot to bootloader = reboots into bootloader normally.
boot to download mode = failed to boot into download mode
boot to recovery = boot loop with the htc logo on a black background
power down =
1. when plugged in, shuts the phone off for about 3 seconds, then boots immediatley into bootloader again.
2. when unplugged, turns phone off.
also, when the device is off and i plug in a charger (from wall or pc) it turns on by itself and boots into bootloader.
i've tried charging the device but it doesn't seem to help, even with the script that constantly boots into bootloader to try and remedy that issue.
Click to expand...
Click to collapse
lucyr03 said:
I don't think he can access recovery
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
he states in his first post "it booted into TWRP touch recovery without any issues."

Warwick555 said:
he states in his first post "it booted into TWRP touch recovery without any issues."
Click to expand...
Click to collapse
Yeah, before battery replacement, after that he only can access the bootloader, read it again...
Sent from my HTC One M9 using Tapatalk

lucyr03 said:
Yeah, before battery replacement, after that he only can access the bootloader, read it again...
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
snaps, my bad. i guess i should have read that better

Warwick555 said:
he states in his first post "it booted into TWRP touch recovery without any issues."
Click to expand...
Click to collapse
that was before the battery replacement, now my recovery is inaccessible
however i managed to pull these details :
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(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:FA57FYJ00151
all:
Also, can anyone please link me to a good RUU in a zip format? i'm looking for this version :
RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1
i have the EXE one, but need a zip version to flash the img's or at least try.

kent4ro said:
that was before the battery replacement, now my recovery is inaccessible
however i managed to pull these details :
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(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:FA57FYJ00151
all:
Also, can anyone please link me to a good RUU in a zip format? i'm looking for this version :
RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1
i have the EXE one, but need a zip version to flash the img's or at least try.
Click to expand...
Click to collapse
You can't flash any ruu on a dead nand, ruu can be flashed only from download(sdcard method) or RUU mode("fastboot oem rebootRUU" from download).

so to try and conclude, is there really a possibility of reimaging the device with its original software via fastboot? or should i just scrap it and get a new one?

lucyr03 said:
From what he write in first post, he can't access download mode.
Click to expand...
Click to collapse
My bad, you're right. I've been suffering from a migraine for the last 5 days after an eye test so I mustn't have been concentrating enough. Today is the first day I've felt reasonably normal.
No download mode means no ruu. No recovery means no custom rom.
If it was booting fine before the battery replacement then I suggest taking it back to whoever did the replacement and ask them to double check the connections. Ask if the phone booted up correctly after they did the repair.
My battery took a whole weekend to respond to even the original htc charger. Picked the phone up on friday and it wouldn't accept a charge til sunday. It was connected to the charger the whole time. Turns out li-on batteries don't like sitting at 0% and it needs a balanced input to jolt it to life. The phone simply refused to do anything until the battery was fully charged and then it was as normal.
If anything but the above occured then I would have to say it's not right.

Related

My phone is probably bricked... possible suggestions?

So I was trying to get the Viper 4.3.1 to work. I installed newest twrp, flashed my rom but the home button doesn't work.
So I thought it was because I have the wrong firmware. I installed a new one, but everything starts going down.
Download mode now says failed to boot to download mode, just boots to bootloader when I choose to boot to recovery. Nothing is working.
I tried to download the RUU online, but even when i phone is fully charged, it says it is lower than 30%.
I tried to flash the newest recovery again, but boots me back to bootloader.
Try to simply reboot, boots me back to bootloader.
So any help would be appreciated. Thanks.
what i get after entering "fastboot 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
all:
finished. total time: 0.366s
Update:
Now I can't even turn it off. When I plug it into a power supply, it automatically turns to bootloader.
So basically I am stuck at bootloaer mode.
Seems to be a lot of firmware-related bricking going on. If you flash the wrong firmware in the wrong way kiss your phone goodbye.
.
Ryanchan97 said:
So I was trying to get the Viper 4.3.1 to work. I installed newest twrp, flashed my rom but the home button doesn't work.
So I thought it was because I have the wrong firmware. I installed a new one, but everything starts going down.
Download mode now says failed to boot to download mode, just boots to bootloader when I choose to boot to recovery. Nothing is working.
I tried to download the RUU online, but even when i phone is fully charged, it says it is lower than 30%.
I tried to flash the newest recovery again, but boots me back to bootloader.
Try to simply reboot, boots me back to bootloader.
So any help would be appreciated. Thanks.
what i get after entering "fastboot 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:FA68BBN00327
all:
finished. total time: 0.366s
Update:
Now I can't even turn it off. When I plug it into a power supply, it automatically turns to bootloader.
So basically I am stuck at bootloaer mode.
Click to expand...
Click to collapse
Did you try fastboot reboot? Nevermind. If you are in bootloader mode, leave it there. Get the ruu.exe file for your original phone. Nuke everything by running the ruu.exe on your computer. Original rom with the correct firmware will be installed. You will start over from scratch but at least you will have your phone back.
comstockload said:
Did you try fastboot reboot? Nevermind. If you are in bootloader mode, leave it there. Get the ruu.exe file for your original phone. Nuke everything by running the ruu.exe on your computer. Original rom with the correct firmware will be installed. You will start over from scratch but at least you will have your phone back.
Click to expand...
Click to collapse
Thanks for the suggestion. I am trying it right now, but it says my battery is lower than 30% so it doesnt let me run. I dont know how much battery it has but now i just have to let it charge for maybe an hour or so and see if it lets me do it.
This is probably the last and only solution to this.
Method of installing RUU? I always use and suggest SD-CARD. just curious. Sorry to read this.
andybones said:
Method of installing RUU? I always use and suggest SD-CARD. just curious. Sorry to read this.
Click to expand...
Click to collapse
I tried both through SD and through RUU.exe. Both don't work. So now I really don't have a clue on what to do....
Ryanchan97 said:
I tried both through SD and through RUU.exe. Both don't work. So now I really don't have a clue on what to do....
Click to expand...
Click to collapse
You may find help from someone much smarter than myself with this such as the sunshine team of Dottat. No idea if they can or will hell but the worst they can say is no. Just tossing out ideas.
Even if bricked, I'd hide your serial number. It's in post 1 & 3
Ryanchan97 said:
So I was trying to get the Viper 4.3.1 to work. I installed newest twrp, flashed my rom but the home button doesn't work.
So I thought it was because I have the wrong firmware. I installed a new one, but everything starts going down.
Download mode now says failed to boot to download mode, just boots to bootloader when I choose to boot to recovery. Nothing is working.
I tried to download the RUU online, but even when i phone is fully charged, it says it is lower than 30%.
I tried to flash the newest recovery again, but boots me back to bootloader.
Try to simply reboot, boots me back to bootloader.
So any help would be appreciated. Thanks.
what i get after entering "fastboot 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
all:
finished. total time: 0.366s
Update:
Now I can't even turn it off. When I plug it into a power supply, it automatically turns to bootloader.
So basically I am stuck at bootloaer mode.
Click to expand...
Click to collapse
I can fix this....Wanna do a TeamViewer session at some point?
Sent from my HTC6545LVW using Tapatalk
Sorry i am not too familiar with tech. How doed Team View work?
dottat said:
I can fix this....Wanna do a TeamViewer session at some point?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Is it okay if you give me a breif instruction on how to do it? I dont usually have time during the day sorry. But thank you for the offer!
Ryanchan97 said:
Is it okay if you give me a breif instruction on how to do it? I dont usually have time during the day sorry. But thank you for the offer!
Click to expand...
Click to collapse
Your issue is mismatched firmware. Extract the lastest ruu and flash each IMG by name manually in bootloader. When done you should have your phone back. If you still have an issue tonight lemme know. This same symptom goes back to the HTC m9 days.
dottat said:
Your issue is mismatched firmware. Extract the lastest ruu and flash each IMG by name manually in bootloader. When done you should have your phone back. If you still have an issue tonight lemme know. This same symptom goes back to the HTC m9 days.
Click to expand...
Click to collapse
So will the command be "fastboot flash recovery filename"?
Or is there a specific one for img files?
Ryanchan97 said:
So will the command be "fastboot flash recovery filename"?
Or is there a specific one for img files?
Click to expand...
Click to collapse
the phone can be turned off from pretty much anywhere by holding down vol- and power. the touch lights will flash about 15 times and the shut off.
secondly, I havnt seen any mention or ask if you are s-off or not. of you are s-on, it is virtually impossible to permanently brick. because from bootloader/download a recovery can be flashed and from there, custom ROM etc.
unless you've altered your cid or mid, it is usually not possible to flash just any old RUU.
Ryanchan97 said:
So will the command be "fastboot flash recovery filename"?
Or is there a specific one for img files?
Click to expand...
Click to collapse
Use the default name of the image. If radio use radio.
Sent from my HTC6545LVW using Tapatalk
dottat said:
Use the default name of the image. If radio use radio.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
So I tried to do that just now. But the phone doesn't even turn on now. Like I clicked reboot but now it is just a black screen with nothing. I tried volume down + power button but doesn't seem to work. Doesnt even seem to be charging also. I am going to let to charge for the night and see if it works.
silegeek said:
the phone can be turned off from pretty much anywhere by holding down vol- and power. the touch lights will flash about 15 times and the shut off.
secondly, I havnt seen any mention or ask if you are s-off or not. of you are s-on, it is virtually impossible to permanently brick. because from bootloader/download a recovery can be flashed and from there, custom ROM etc.
unless you've altered your cid or mid, it is usually not possible to flash just any old RUU.
Click to expand...
Click to collapse
Sorry I forgot to mention. It is s-off. And i also changed the CID to 11111111. But if i do getvar all, it doesnt show what cid i have. I am assuming this has something to do with the broken firmware also. Any suggestions? Thanks!
Ryanchan97 said:
Sorry I forgot to mention. It is s-off. And i also changed the CID to 11111111. But if i do getvar all, it doesnt show what cid i have. I am assuming this has something to do with the broken firmware also. Any suggestions? Thanks!
Click to expand...
Click to collapse
if you tried "fastboot getvar cid" and its blank then I would say yes something might be wrong. in my experience "getvar all" doesn't always show all the information. and when I was super cid, it came up blank. but "getvar cid" usually worked. but since being HTC__001 (WWE) it's always shown up regardless of method.
you can usually flash an appropriate RUU by altering either your cid or mid. for instance I was able to successfully install the US Nougat RUU by changing my cid to BS_US001 and my mid to 2PS650000. Afterwards I changed back to HTC__001 and 2PS620000
i would not recommend flashing 2PSIMG.zip from the SD card unless you are totally sure it is suitable for your phone, and even then, check again. if it gives you warnings, pay attention to what they are.
have you tried flashing the RUU manually? by using a 2PS6img.zip file? it will run in recovery on your phone automatically when you have it on there. I had trouble flashing RUUs before on my 10, had to relock the bootloader and manually install a stock img.
kazuki1 said:
have you tried flashing the RUU manually? by using a 2PS6img.zip file? it will run in recovery on your phone automatically when you have it on there. I had trouble flashing RUUs before on my 10, had to relock the bootloader and manually install a stock img.
Click to expand...
Click to collapse
All sorts of wrong advice there. No need to relock on this device. Also, the ruu will not run in recovery.
Sent from my HTC6545LVW using Tapatalk
dottat said:
All sorts of wrong advice there. No need to relock on this device. Also, the ruu will not run in recovery.
Click to expand...
Click to collapse
Meant download mode not recovery sorry. And I actually had to relock my device, but tysm.

HTC one M9 - s-on, cannot flash, mount issues, soft brick with odd behaviour

Hi Guys,
I have an interesting one here, which I have been battling for a couple of days!
My nephew some time ago decided to put some custom ROM’s on his M9. Recently he had some odd happenings relating to encryption (something about asking for passwords), he tried to recover it and bricked it slightly!
Twrp 3.0.2-0 is on the device, but I cannot flash anything to the recovery, even 3.0.1-0. I cannot lock/relock the bootloader and when I try to flash the Unlock_code.bin it hands in download mode and does not give me onscreen instructions. Twrp tells me it cannot mount any partitions with a crypto footer missing message. I have tired reformatting some partitions (cache and data) as well as writing zero’s to the start of the partition and they still cannot mount with an invalid argument message. It also boots straight to the bootloader (with a flash of the HTC logo screen) and I have dd’ed the boot partition off the device and it’s all zeros (not sure if some kind of protection is stopping this).
Together with this these issues, I need to hold volume up and volume down to get to the bootloader (without it flashing the htc logo), but documentation I have read says down and power. When I hold down the volume up, it boots to a white screen with HTC logo. When I hold down the volume down it boot loops the black HTC logo.
Download mode is version 3.35.401.12 and CID HTC__001.
Any help would be appreciated,
Thanks,
FlangeMonkey said:
Hi Guys,
I have an interesting one here, which I have been battling for a couple of days!
My nephew some time ago decided to put some custom ROM’s on his M9. Recently he had some odd happenings relating to encryption (something about asking for passwords), he tried to recover it and bricked it slightly!
Twrp 3.0.2-0 is on the device, but I cannot flash anything to the recovery, even 3.0.1-0. I cannot lock/relock the bootloader and when I try to flash the Unlock_code.bin it hands in download mode and does not give me onscreen instructions. Twrp tells me it cannot mount any partitions with a crypto footer missing message. I have tired reformatting some partitions (cache and data) as well as writing zero’s to the start of the partition and they still cannot mount with an invalid argument message. It also boots straight to the bootloader (with a flash of the HTC logo screen) and I have dd’ed the boot partition off the device and it’s all zeros (not sure if some kind of protection is stopping this).
Together with this these issues, I need to hold volume up and volume down to get to the bootloader (without it flashing the htc logo), but documentation I have read says down and power. When I hold down the volume up, it boots to a white screen with HTC logo. When I hold down the volume down it boot loops the black HTC logo.
Download mode is version 3.35.401.12 and CID HTC__001.
Any help would be appreciated,
Thanks,
Click to expand...
Click to collapse
Oofta. If there ever was a candidate for restoring to stock via RUU, this would be it. From the OS version you list, your SKU is 401. Head to the readme thread and follow the instructions there.
computerslayer said:
Oofta. If there ever was a candidate for restoring to stock via RUU, this would be it. From the OS version you list, your SKU is 401. Head to the readme thread and follow the instructions there.
Click to expand...
Click to collapse
Thank you for the reply, I have an RUU zip that doesn't flag any errors via SD card (not the same story via fastboot, as I get RU security errors). However when it reboots, it goes to the bootloader and not the expected rebootRUU. If I execute 'fastboot oem rebootRUU', it goes into a bootloop. I did some checking and although I could be wrong, it appears to need the boot strap to do RUU, which could be hosed.
FlangeMonkey said:
Thank you for the reply, I have an RUU zip that doesn't flag any errors via SD card (not the same story via fastboot, as I get RU security errors). However when it reboots, it goes to the bootloader and not the expected rebootRUU. If I execute 'fastboot oem rebootRUU', it goes into a bootloop. I did some checking and although I could be wrong, it appears to need the boot strap to do RUU, which could be hosed.
Click to expand...
Click to collapse
Have you tried the backup files in flippy's thread?
Beamed in by telepathy.
shivadow said:
Have you tried the backup files in flippy's thread?
Beamed in by telepathy.
Click to expand...
Click to collapse
Can you please point me to the thread your referring to?
edit: I think I have found what your refering to, I'm just looking at this (Stock_Backup_3.35.401.12.zip), I'll check it out and see if I can do anything with it.
So I tired the flippy "TWRP Backup Section II" and after the restore and selecting boot to system, it boots to the bootloader and it appears retain the original recovery, so it isn't restoring anything by the looks of it. I've also just found out that this phone is a M9u, if that makes any difference and the RUU that doesn't flag any errors is signed_2_4.
FlangeMonkey said:
So I tired the flippy "TWRP Backup Section II" and after the restore and selecting boot to system, it boots to the bootloader and it appears retain the original recovery, so it isn't restoring anything by the looks of it. I've also just found out that this phone is a M9u, if that makes any difference and the RUU that doesn't flag any errors is signed_2_4.
Click to expand...
Click to collapse
It makes a difference all right. Let's back up a step and get all of your phone's information straight. What is it's model and OS version? You can find out by running the command "fastboot getvar all" after installing the HTC adb drivers (via HTC Sync Manager) with your phone plugged into your computer.
Under fastboot:
(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:*redacted*
Under Download Mode:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: *redacted*
(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__001
On the back of the phone it reads: 0PJA100... FCC... M9u
FlangeMonkey said:
(bootloader) product: htc_himauhl
(bootloader) version-main: 3.35.401.12
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
Click to expand...
Click to collapse
These are the pieces that I find most helpful. From everything provided, I can't see why the M9u shouldn't be able to accept the RUU under normal circumstances.
I notice that in the instructions for the SD card method there is this note in step 6:
"Depending on your current firmware version it may reboot to Android or the Bootloader instead of rebooting to Download Mode. If this happens you just need to manually boot it to Download Mode."
Have you given that a shot? That may solve the problem.
computerslayer said:
These are the pieces that I find most helpful. From everything provided, I can't see why the M9u shouldn't be able to accept the RUU under normal circumstances.
I notice that in the instructions for the SD card method there is this note in step 6:
"Depending on your current firmware version it may reboot to Android or the Bootloader instead of rebooting to Download Mode. If this happens you just need to manually boot it to Download Mode."
Have you given that a shot? That may solve the problem.
Click to expand...
Click to collapse
Yea I did try that as well as a slew of different modes and options, which none of seem to work. I just performed it again for good messure and it bootloops on rebootRUU. I've also found an old backup from the phone itself that was performed back in October with twrp and that has no effect.
I have performed backups using TWRP after restores and examined the images but they are all zeroed! Additionally I do recall seeing write speeds in DD at the 50mb mark, which is way to fast in my opinion and using twrp restore is quick.
It’s very much like nothing is being written, but I have no idea why or if it’s possible to fix.
Could it be possible that something is physically broken, which is preventing writes?
FlangeMonkey said:
Yea I did try that as well as a slew of different modes and options, which none of seem to work. I just performed it again for good messure and it bootloops on rebootRUU. I've also found an old backup from the phone itself that was performed back in October with twrp and that has no effect.
I have performed backups using TWRP after restores and examined the images but they are all zeroed! Additionally I do recall seeing write speeds in DD at the 50mb mark, which is way to fast in my opinion and using twrp restore is quick.
It’s very much like nothing is being written, but I have no idea why or if it’s possible to fix.
Could it be possible that something is physically broken, which is preventing writes?
Click to expand...
Click to collapse
Bummer - it would have been nice if it had been a simple fix there.
It's entirely possible that something is physically broken, but that would probably involve some sort of corrupt memory chip or something. I don't know how you would confirm that though, at least without a professional tearing the phone apart.
From posts I've read elsewhere, it may be possible to flash individual partitions, but that's beyond me. Apart from exploring that option, I'm afraid I'm at a loss.
computerslayer said:
Bummer - it would have been nice if it had been a simple fix there.
It's entirely possible that something is physically broken, but that would probably involve some sort of corrupt memory chip or something. I don't know how you would confirm that though, at least without a professional tearing the phone apart.
From posts I've read elsewhere, it may be possible to flash individual partitions, but that's beyond me. Apart from exploring that option, I'm afraid I'm at a loss.
Click to expand...
Click to collapse
I appreciate your efforts. I have tried flashing partitions via DD and fastboot, but its the same result. Unless anyone can tell me another means to try?
On another note, is it possible to s-OFF in this state (paid or otherwise)?
FlangeMonkey said:
I appreciate your efforts. I have tried flashing partitions via DD and fastboot, but its the same result. Unless anyone can tell me another means to try?
On another note, is it possible to s-OFF in this state (paid or otherwise)?
Click to expand...
Click to collapse
Maybe with a Java Clip. The common method (Sunshine) requires a working ROM

Failed to boot download mode

Please help, very, very need firmware 4.16.118.3, or the file itself pulled "hosd.img".
Sorry for my english, but I read better than I write.
As far as I know HTC haven't released the nougat ruu for any M9's.
Beamed in by telepathy.
The 118 SKU doesn't seem to have a Nougat (4.x.xxx.xx) update. Where are you getting that version number?
If your goal is getting Android Nougat: Assuming your phone boots to Android, you may be able to achieve S-OFF via Sunshine, change your SKU and update to Nougat.
If your goal is fixing the download mode issue: a RUU associated with your SKU & OS version should set your phone straight. Could you post the output of the "fastboot getvar all" (be sure to remove the IMEI information)?
Android does not start, only works Bootloader and Recovery. Phone is T-mobile Poland.
First was Android 6.0 Marshmallow version number 3.35.118.12, then on February 25 she appeared update Android 7.0 Nougat version number 4.16.118.3.
After a week when I turn on the phone appeared application errors, then I made Wipe cache, after the phone hung up on the HTC logo and constantly reboot.
When I entered the Bootloader I saw that changed status ***Software status Modified**, phone all the time was ***Locked*** and ***S-ON***
C:\fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(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:************
all:
finished. total time: 0.146s
That getvar all is the response from bootloader. You need to do that in download mode.
To save you the hassle I can tell you that your nand is corrupt and beyond repair. Only HTC can fix it.
"status modified" on a totally stock phone that wont boot means corrupt nand and as dead as a door stop.
Dead nands are becoming more and more popular it seems..
Beamed in by telepathy.
Thank you for your help, phone sent to the service.
shivadow said:
That getvar all is the response from bootloader. You need to do that in download mode.
To save you the hassle I can tell you that your nand is corrupt and beyond repair. Only HTC can fix it.
"status modified" on a totally stock phone that wont boot means corrupt nand and as dead as a door stop.
Dead nands are becoming more and more popular it seems..
Beamed in by telepathy.
Click to expand...
Click to collapse
What about a stock m9 which shows "status modified", does boot to Android, but does not boot to download or recovery modes (black screen with red text - "Failed to boot to download mode ..."). Is this also the sign of a corrupt NAND?
-Tim
LindwurmPL said:
Thank you for your help, phone sent to the service.
Click to expand...
Click to collapse
what problem about your phone? i have same problem too
TimR1 said:
What about a stock m9 which shows "status modified", does boot to Android, but does not boot to download or recovery modes (black screen with red text - "Failed to boot to download mode ..."). Is this also the sign of a corrupt NAND?
-Tim
Click to expand...
Click to collapse
Yes Tim, it can very well be a corrupt nand. The problem you have there is without download mode you can't flash any stock firmware to reset the device to what i call "stock stock". Only htc would be able to repair that.

Stuck in boot loop and can't enter Download or Recovery mode, only bootloader

So this Saturday I was using my phone with low battery (it was plugged in), the buttons stopped responding so I restarted it and it has not booted since, I have tried the suggestions laid out in this thread - https://forum.xda-developers.com/htc-10/help/enter-download-mode-t3406529/page3 to no avail.
My phone is S-OFF and unlocked, I have tried flashing an RUU but it says the battery is too low and the phone will not charge, or at least it won't recognise it's charging even when left plugged in for hours.
I have tried flashing each partition individually from one of the firmware .zips on here with the same version it was on, apart from aboot as the thread said to not flash that.
And I have also tried flashing the RUU .zip from a freshly formatted FAT32 SD card but my download mode just shows the silver HTC logo for a while and then reboots into the boot loop. The only mode my phone will stay in is the bootloader, recovery doesn't work either and I have tried flashing TWRP as well as the stock one via fastboot to no avail.
My phone is under warranty so I don't want to disassemble it and it is S-OFF so I don't know if they will claim it's caused by this, although I was going to send it in for a repair as it has a bright spot on the screen anyway but it seems to have killed itself before I had a chance
I do not want to lose the contents of the internal storage either. So I have been searching online for a solution but nothing has worked so far.
I see that a lot of these posts relate to S-ON phones so I was wondering if this could be the reason it didn't work. But I don't want to S-ON my phone as there will be no way back without being able to boot into Android to run Sunshine.
Any help would be greatly appreciated as I'm really stuck.
Thanks.
Edit: GetVar commands get the following output (if this helps):
C:\Android\com>fastboot getvar cid
cid:
finished. total time: 0.010s
C:\Android\com>fastboot getvar mid
mid:
finished. total time: 0.036s
C:\Android\com>fastboot 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:FA6xxxxxxxxx
all:
finished. total time: 0.387s
What about downloading the data partition in this state? Can it be done?
Man, this happened to me a month or 2 ago. Seems a lot of people are having similar issues. Haven't found a solution yet. Hopefully soon. Tired of using my old M8
Help, I'm in the same situation since yesterday, I think it's time to change the motherboard
I have the same exact issue. Anyone find a fix?
New motherboard, if it's unlocked and s-off wipe aboot (bricks the phone) and chance a warranty repair. I did, but apparently I had water damage which is bull**** but had it replaced by insurance instead in the end. I've never sent back a phone with an unlock showing so I don't know if they'd warrant it if they see it, but you have nothing to lose as if you moan enough they'll just send it back for free anyway as at least in the UK they can't keep it without consent...
Thanks alot for your response. I was hoping there was an easy fix, oh well (i also have s off and unlocked)... I think im done with HTC. It happened for no reason in my case. Is there a way to extract my files some way given its current condition?
I wasn't able to but maybe someone smarter may know a way. You should be able to get it warranted if you do as I said above as you have nothing to lose at this point
gr8icu said:
I have the same exact issue. Anyone find a fix?
Click to expand...
Click to collapse
Well i was in that bootloop, so i did this to access the htc download mode, plug your cable in pc, then power off phone, plug in the cable then keep presing volume down, he's gonna restart alot, just keep press the volume down till it boot in download mode.
hope you fix this
If that worked it's not the same issue as when the phone ends up in this state you cannot access download mode anymore. It seems to be a firmware/hardware issue specific to the 10.
Like the SD card corruption issue HTC never addressed, my U11 hasn't had a single SD card issue but on my 10 every few months I had to format it.
I'm really disappointed in HTC, I would've bought the U12 but the button issues majorly put me off.
Good luck to anyone with this issue though, I wish mine could've been saved as I lost some data.
same issue with my u ultra.
i also got it s.on bootloader unlocked. cant get to twrp .what should i do now i was on ressrction remix os
Supun_rupasingha said:
i also got it s.on bootloader unlocked. cant get to twrp .what should i do now i was on ressrction remix os
Click to expand...
Click to collapse
If you can ONLY access the bootloader a RUU.exe for your specific firmware could save you.
hopefully you know on what firmware your device is, not the resurrection rom numbers.
You can enter ruu mode from the bootloader and execute a ruu.exe ....... That would be an option

bricked htc one m8s

Hi all,
@THE company I work we found a htc one m8s that when I booted it went straight to bootloader menu.
I want to get it working again so I started reading here on the forums, download some stuff from ruu.lalleman.net that I found in one of the other treads. In the end i'm still stuck and i'm hoping to get some advice through this channel.
Here is my current status
when the devices is connected to the PC it boots ALWAYS straight to bootloader with the following info
software status : Modified
unlocked
m8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.000
[email protected]
OS-1.16.401.10
eMMC-boot 2048MB
aug 13 2015
Fastboot USB with the normal stuff
when I try to load a RUU through the exe I reboot the device and then keeps waiting with in the end a disconnect (saying I need to connect my device) the device itself is already back in bootloader window.
when I try to use htc_fastboot to flash a recovery it gives me
fastboot flash recovery recovery.img
sending 'recovery' (6002 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 1(s)
but then on reboot it's straight back to bootloader menu no recovery
when I try to lock the device I get
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) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: 15
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
(bootloader) [INFO] Rebooting device arbiter!!I PMIC arbitery-
FAILED (unknown status code)
Execution time is 1(s)
I did get it unlocked (as it was locked before but relocking is not working)
Also fastboot devices shows me the devices but adb devices shows nothing (tried both htc drives and general android ones)
These are my var all info
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__031
(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: 1d456ef7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
Execution time is 28(ms)
Hoping on any help from here
Greetings
Tom
Little update:
I kept on trying different versions from recovery / boot / ruu's in the hope that one works but nothing so far.
In another topic somewhere I did found that as long as my device is unlocked it will not work to use RUU, so locking the device again will be my first step.
I did notice that when I ended my adventure yesterday evening I wasn't able to turn the phone off, I always rebooted (in like a millisecond) back to bootloader as long as it was connected to the pc. I had to remove the usb connection and then try couple of times with volume-up / power to turn it off.
I did do the 2 minutes bright licht / volume up + down + power button trick to reset the battery but that didn't change anything.
also as a last minute addition
when I do the fastboot -> image CRC i'm getting a 0X0 on sbl2 - sbl3 - boot and recovery so it seems that what ever I do with htc_fastboot flash is not sticking.
Going to look into trying to get it locked again now first in combination with trying to find out why I can't write to the damn phone (adb isn't working ether so maybe driver problem also ?)
The adventure continues
Tom
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
ckpv5 said:
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
Click to expand...
Click to collapse
That is indeed the RUU i tried, i got it based on the fastboot var all i did.
Still trying to get my Phone locked again as that is holding back the ruu upgrade now from what i see.
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
ckpv5 said:
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
Click to expand...
Click to collapse
Yhea i did it with the htc_fastboot version.
another update,
After some more trial and error while aiming for the locking of my phone i'm still stuck.
Both my boot and my recovery are empty it seems (the 0x0 from the image crc) and all the others still have 0xA.....B or what ever value in them
All the writing I do like
C:\tel>htc_fastboot.exe flash recovery recovery_signed.img
sending 'recovery' (30080 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
seems to be working but that doesn't change the crc value's nether does it allow me to use the recovery from the hboot menu.
also when I type stuff like htc_fastboot oem rebootRUU it brings me straight back to the bootloader menu, no black screen to do htc_fastboot flash zip rom.zip.
What I didn't try yet is using a SD-card and see if that fixes it (I could put that card in my other phone, write stuff to it and use it in the M8s.
Anybody got any expereance for using a sdcard to flash the device back to stock.
@ this moment I will be kind of happy with anything that advances me a step
Tom
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
kruc Ire said:
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
Click to expand...
Click to collapse
How do you mean give up ?
is there no way arround based on your opinion from what i posted above ?
I Always hoped it was my lack of knowledge that was holding me back in fixing it ...
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
kruc Ire said:
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
Click to expand...
Click to collapse
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
TomBrunson said:
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
Click to expand...
Click to collapse
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
I made that video but if the F'N censors won't let me put up the lyrics of a song they HATE in their pinheads then I won't be posting their garbage they WOULD view.
I'll keep putting up large videos though just to chew up this sh!tty world's resources. If it's a world of creeps it's
Music videos mostly. Ooh how they HATE my beautiful music...and I can hear the little b##ch there in her fuzzy chair. Like she spoke directly into my head. And if it hadn't taken me so long to make a thumbnail she wouldn't have been able to install her trick. Literally FFFF youtube.
kruc Ire said:
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
Click to expand...
Click to collapse
Is there a different command to Relock as to Lock ?
I couldn't find anything else then htc_fastboot oem lock
Tom
Ok i'm over it. I attached a different (worse) song and reuploaded it. No censorship now.
HTC M8s firmware flash in photos:
Please note I only started making a video because I noticed that time bar on upper right about 15 minutes into the (uninterrupted) flash. So that took a long time and I was concerned about the messed up and overprinted text and made photos during every new screen between the third or fourth at the start (when I caught up with my camera) up till the time of video starting.
So yeah what I am trying to say is it seemed to take very long, with many seemingly false starts and failures. Only by waiting did it finally achieve correctness.
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
TomBrunson said:
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
Click to expand...
Click to collapse
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
kruc Ire said:
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
Click to expand...
Click to collapse
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
You have never gotten it to lock? I thought you said you couldn't get the zip to work?
---------- Post added at 06:53 PM ---------- Previous post was at 06:38 PM ----------
TomBrunson said:
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
Click to expand...
Click to collapse
What output does your cmd window give u? Can you show a screenshot of what your command is and the output.
I see. You are trying to put a lollipop. Still first ya gotta lock it does anyone remember the rules for firmware flash? Is it going to screw up the phone to flash the MM 60 sense 70 ? Dude are you in Europe? The 60 70 I flashed from my microSd was a EUROPE.

Categories

Resources