Develop Bugs

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

Can't get past loading screen after factory reset

Hi, my name is Quinn.
Cards on the table, I don't know anything about phones and very little about computers.
So I rooted my phone About two years back and my phone has been acting sluggish for a while so I decided to try putting it back in stock software and updating it to see if it would become quicker. When I tried to install the update there was a thing that said the startup wizard has stopped working so I was trying to delete it and did an advanced wipe on my phone for some reason. Now when I boot it up, it only brings me to the loading screen. The big thing for me is that the factory reset turned off usb debugging and I have no idea how to access my phone from my computer.
I can get to the recovery page, and my bootloader(I think) is unlocked.
Any help would be appreciated.

Let's walk this back for a second. If you had a car with some problems, would you just randomly open the hood, without knowing what you are doing, and start pulling stuff out, without knowing what it was, or what the effect would be? Because that is kinda what you did, by going into the TWRP "Advanced" wipe options.
What you did was not a factory reset. You probably wiped "system" which is the OS (operating system - Android), and therefore you have no OS to boot.
My constructive advise to you, in moving forward, is only do what other experienced users have directed you to do. Don't guess solutions, make things up, etc. Don't do anything unless you have a good understanding of what the result will be; or if you were instructed to do so by a knowledgeable person. Make sense?
Now let's get you back up and running. Doing so will take some steps, and take some time. You may (almost certainly) learns some things in the process.
Do you by any chance remember if you ever made a backup of the ROM using TWRP? You can check this by booting into TWRP, selecting RESTORE, and seeing if it identifies any available backups. However, if you wipe internal storage and/or the SD card; even if you had previously made a backup, it would be gone now.
On the bootloader screen (the white screen where you can select recovery) what does it say for OS number? If its blank, what does it say for hboot number and radio number?
On that same bootloader screen, it will indicate at the top whether the bootloader is UNLOCKED or RELOCKED (or LOCKED, but its probably not that one). Tell us which one.
ShaferQ said:
The big thing for me is that the factory reset turned off usb debugging and I have no idea how to access my phone from my computer.
Click to expand...
Click to collapse
This only affects adb commands. You will find fastboot commands will still work, when booted properly into bootloader-fastboot mode.
Also, if booted into TWRP, you should be able to access the phone's internal storage and SD card (if one is inserted) from your computer.
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
ShaferQ said:
I decided to try putting it back in stock software and updating it to see if it would become quicker. When I tried to install the update there was a thing that said the startup wizard has stopped working
Click to expand...
Click to collapse
How far exactly did you get with this process (restoring stock software, and update)?
Describe step by step, what you did, and in as much detail as possible (files used - exact names, results of each step, any other observations).

Yeah, I don't know what I was thinking. Thanks for the help though.
My Bootloader is unlocked
OS is blank
HBOOT is 3.19.0.0000
RADIO is 1.09.20.0209
No backups
I didn't get far at all with installing stock. I just had the intention. I tried to use some program to install the stock firmware, but my phone couldn't connect to my computer.

ShaferQ said:
I tried to use some program to install the stock firmware, but my phone couldn't connect to my computer.
Click to expand...
Click to collapse
Then how did you get to the point where it said "Setup Wizard has stopped working"? Isn't that the error that prompted you to wipe everything in TWRP?
Also, you must realize that saying "some program" doesn't really tell us what you used? You have any idea what it was? Is it still on your computer?
Do you have any idea how to use fastboot, and issue fastboot commands?

redpoint73 said:
Then how did you get to the point where it said "Setup Wizard has stopped working"? Isn't that the error that prompted you to wipe everything in TWRP?
Also, you must realize that saying "some program" doesn't really tell us what you used? You have any idea what it was? Is it still on your computer?
Do you have any idea how to use fastboot, and issue fastboot commands?
Click to expand...
Click to collapse
No, I did the factory reset, thinking that would undo my rooting, but it didn't. At this point it was still working and I thought that it was fine, but then I couldn't take pictures or anything so I installed major update from my phone and that's when the startup wizard wouldn't work. I then did the wipe and used a program I got from htc rom downloads from their support page. I thought it was a program that installed stock roms on your phone? But it couldn't connect and did nothing to my phone.

redpoint73 said:
Do you have any idea how to use fastboot, and issue fastboot commands?
Click to expand...
Click to collapse
I know how to get there, but I don't really know anything other than that.

ShaferQ said:
so I installed major update from my phone and that's when the startup wizard wouldn't work.
Click to expand...
Click to collapse
You mean an over-the-air (OTA) official update? I'm confused how that would even install. It normally will fail if the phone is rooted, and also won't install with TWRP on the phone.
---------- Post added at 01:13 PM ---------- Previous post was at 01:06 PM ----------
ShaferQ said:
I know how to get there, but I don't really know anything other than that.
Click to expand...
Click to collapse
When you say you know how to get there, you mean only know how to boot into fastooot mode on the phone?
You'll need to also issue fastboot command from your PC's command prompt (with phone connected, and booted to fastboot mode). To do that, you'll need to find where fastboot.exe is on the PC. You might find it at (where it is on my PC): C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
After you find it, hovering the mouse cursor over the window (where fastboot.exe is located) do Shift + Right Mouse Click, and from the pulldown menu, select "Open command window here".
In the command window, type: fastboot getvar all
Then copy and paste the output, and post it (delete IMEI and serial number before posting). To copy in command prompt, right mouse click, select "Mark" then highlight the area you want to copy. Press Ctrl + C to copy. Then go to your forum post window, and Ctrl + V to paste. And remember again to delete IMEI and serial number before posting.

Well, I was also the one who rooted the phone, so I probably did it poorly somehow. Yeah the over the wifi one. The update failed the first time, but then I just tried again and it went though and that was the point where I got the startup wizard is not responding message that wouldn't let me pass.
Ok, give me a second to do that.

C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499185667
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 631e3609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
htc_fastboot finished. total time: 0.120s

Okay, great. That confirms some things I had figured out earlier. One that this is a Sprint version, and it looks to be the Harman Kardon version. Is Sprint your current cell provider?

redpoint73 said:
Okay, great. That confirms some things I had figured out earlier. One that this is a Sprint version, and it looks to be the Harman Kardon version. Is Sprint your current cell provider?
Click to expand...
Click to collapse
Yes sir, it is.

ShaferQ said:
Yes sir, it is.
Click to expand...
Click to collapse
Ok, good. That makes the rest somewhat easier.
Another fastboot command. Enter the following:
fastboot oem lock
On the bootloader screen (after an auto reboot, I believe) you should see the bootloader say RELOCKED near the top.
Next go to the following page, and download the 4.25.654.18 RUU under where it says "Previous RUUs":https://forum.xda-developers.com/showthread.php?t=2729173
After you download the RUU, open it, and it should install the full stock factory image, Lollipop version. The phone should be running after that. And since you are connected to Sprint, you should soon get an update, which will bring you up to Marshmallow.
You can also RUU right to Marshmallow, but it takes more steps. You would have to flash MM firmware (more fastboot steps) before you can do the MM RUU. So that is why the LP RUU may be easier for your. But if you are interested in doing RUU right to MM (instead or LP RUU, then OTA update) then let me know, and I'll walk you through it.

I got it re-locked and everything, but my phone still wont connect to my computer. The Rom utility still says that it cannot connect.
View attachment 4009482
And I know that it's not just the USB because I already issued fastboot commands perfectly fine.
Does the phone still have to be in fastboot?

ShaferQ said:
Does the phone still have to be in fastboot?
Click to expand...
Click to collapse
Yes. Is that how you are trying to run the RUU? If so, try a different USB port, different cable, if possible. The RUU is much more finicky than fastboot commands.
If all fails, and you have an SD card, you can use the SD method of RUU (no PC needed): Go back to the thread, download the zip version of the RUU. Rename to 0P6BIMG.zip, put on the SD, then reboot to bootloader, it will detect the RUU and auto install it.

You are a freakin life saver, thank you so much for helping me. I really really appreciate it.

ShaferQ said:
I got it re-locked and everything, but my phone still wont connect to my computer. The Rom utility still says that it cannot connect.
And I know that it's not just the USB because I already issued fastboot commands perfectly fine.
Does the phone still have to be in fastboot?
Click to expand...
Click to collapse
As redpoint73 said
Try another USB port ( USB 2 not 3 )
Un install HTC sync manager if you installed it earlier
But the main reason i post here is to tell you to remove meid numbers from this post ( as it's personal info and not to share on public forum )
https://forum.xda-developers.com/ht...ng-screen-factory-reset-t3541234/post70630772
Sent from my HTC M8 using XDA Labs

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

boot loops after battery replacement

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.