Develop Bugs

Nearly Bricked, Please Help

The phone is a VZW HTC One. I have S-off with Hboot 1.55, bootloader unlocked and I was rooted prior to the flashing of TIKTAK going sideways. Now I can ADB when i'm in recovery and I can flash new recovery mods. I know this means that I'm not completely done for.
When I let the phone try to boot without going into the boot loader it sits at the green HTC screen with the red distribution statement. In this state it tries to make an MTP connection with windows but it doesn't install the drivers properly.
I don't seem to have an internal file structure. I tried downloading HTC1guru's nandroid backup but TWRP doesn't recognize it in either its zipped form or extracted. CWM doesn't seem to recognize any file system at all. I have to use someone elses backup because I was dumb and didn't move my backup off the device before dropping a bomb in the file system.
TWRP is asking for a password that I don't know (and didn't set) every time it opens
I also tried RUU but I never get to the silver HTC screen.
I'm at a loss as to how to proceed. Any thoughts would be most appreciated. I'm pretty handy in the IT world but this is my first time flashing a custom ROM, it may be the last. Thanks in advance.
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000428178272
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Just do the 2.10.605.1 ruu (found in santods rom/radio/kernel thread), then " fastboot erase cache ", then " fastboot flash recovery name_of_recovery.img ". From there you can flash a rom, or just flash superuser and be stock rooted.

I can't get the phone into RUU. any reboot that doesn't go to recovery or fastboot just hangs on the green HTC screen.
>fastboot oem rebootRUU
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: read fifo failed, retry
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 17
(bootloader) Start Verify: 0
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 2.156s]
finished. total time: 2.156s

Are there any other thoughts out there on how I might proceed before I put the phone in a bucket of water and use my warranty?
Sent from my Galaxy Nexus using Tapatalk

Any luck?
jbeavis19 said:
Are there any other thoughts out there on how I might proceed before I put the phone in a bucket of water and use my warranty?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
JBeavis, I am in a very similar situation to the one you are in. Have you had any luck with fixing it or getting a warranty repair?
Thanks!

I'm also in a similar situation
One critical difference between the HTC One and the thunderbolt... no SDCard. Which would not be a big deal had I not wiped the phone with no backup (stupid I know) before loading a new rom image to replace it. Now I can't get ADB to recognize my phone in CWM recovery. No sideload. Nothing. I do have S-off and CWM 6.0.4.7 installed successfully. If anybody has any advice I'd really appreciate it.

@wantasmartcookie @eicos
@jbeavis19
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html?m=1
Try this out.

Thanks, @Gizmoe, but I've already been down that road. I think my EMMC is fried. When I get the adb shell going and check /dev/block, I don't see any mmc devices - only ram and loop devices. And when I run cat /proc/emmc, all of the entries are mmcblk0. As with the others, when I try to relock the device, I get a CMD25 error.
I am open to suggestions but fear I will have to try to get a new device. Does anyone have any suggestions about how to do that? Should I go to Verizon or try HTC? And what should I say? This is really a bummer!

eicos said:
Thanks, @Gizmoe, but I've already been down that road. I think my EMMC is fried. When I get the adb shell going and check /dev/block, I don't see any mmc devices - only ram and loop devices. And when I run cat /proc/emmc, all of the entries are mmcblk0. As with the others, when I try to relock the device, I get a CMD25 error.
I am open to suggestions but fear I will have to try to get a new device. Does anyone have any suggestions about how to do that? Should I go to Verizon or try HTC? And what should I say? This is really a bummer!
Click to expand...
Click to collapse
Did you try the repair process regardless with the right mount point?
These are the Verizon HTC one mounts
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yes @Gizmoe, the command fails with "could not stat /dev/block/mmcblk0p37 --- no such file or directory". Any other ideas? I appreciate your help.

Have you tried it with cache or system? Does fastboot oem rebootRUU give you an error too like the op?
---------- Post added at 09:37 PM ---------- Previous post was at 09:31 PM ----------
You could also hit up Mike1986 to see if he can help you out. He wrote the thread and does help people in irc. It's worth a shot.

I gave up and warrantied the phone and now it has 4.4.2 on it so no rooting until ther is a method that works and I'm not sure I'll try another custom rom any time soon.
@Gizmoe, thanks for the suggestion, that is an approach that I didn't try, I thought I went through them all.

Gizmoe said:
Have you tried it with cache or system? Does fastboot oem rebootRUU give you an error too like the op?
---------- Post added at 09:37 PM ---------- Previous post was at 09:31 PM ----------
You could also hit up Mike1986 to see if he can help you out. He wrote the thread and does help people in irc. It's worth a shot.
Click to expand...
Click to collapse
Thanks @Gizmoe, I had the same error with fastboot oem rebootRUU as the op. I am 99.999% sure the EMMC got fried somehow. Probably I hard booted the phone at a bad time during the installation or something - or maybe it was just ready to die. In any case I also have warrantied the phone. Replacement to arrive tomorrow. Here's hoping it doesn't have 4.4.2, though it probably will. @mike1986., do you have any light to shed on this topic?

Gizmoe said:
@wantasmartcookie @eicos
@jbeavis19
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html?m=1
Try this out.
Click to expand...
Click to collapse
I got my phone to a state where I could push a rom down to it using that fix. Thanks for the help! (I've created an entirely different thread detailing my new problem) http://forum.xda-developers.com/showthread.php?t=2657211

Sorry, but neex help with One X

Hello guys, I am on vacations at my cousin's apartment who lives on the other side of the world (Croatia). He has an HTC One X that he doesn't use because he says the battery doesnt last long. I have a few questions that I hope I can get helped with since I will stay here for only 2 more days. I bought an HTC One M7 a year ago as my first Android and learned on my own how to S-OFF, SuperCID and flash ARHD... so I am looking to do the same on his device, but don't have much time to research on my own.
1) His phone says One X UKR on the back (a sticker since he has never used it it seems). Is the hardware different to, say AT&T version? I remember that all HTC One M7 were the same so there was no problem SuperCIDing to 11111111 and flashing any firmware thereafter
2) What is the least demanding ROM I can install so that the battery lasts the longest? The simplest the better as my cousin is 52 years old and cant be bothered learning a difficult OS.
3) Are there any drivers for One X for Windows 8.1? I have a Surface Pro tablet, nothing else.
4) What are the HBTOOT requirements for S-OFF?
Thanks.

If it is an international one x then you can't achieve s-off without sending it to a specialist shop which are very rare.
You can unlock the bootloader at htcdev website and install any Rom you like without s-off but you will need to flash the boot.img from a pc using fastboot commands
If you boot into the bootloader by holding volume down & power it should tell you at the top which version you have:
endeavour u (international tegra3)
Evita (us snapdragon)
As for windows 8 drivers, I know they are available but not sure where to get them from mate, just search google

intel007 said:
If it is an international one x then you can't achieve s-off without sending it to a specialist shop which are very rare.
You can unlock the bootloader at htcdev website and install any Rom you like without s-off but you will need to flash the boot.img from a pc using fastboot commands
If you boot into the bootloader by holding volume down & power it should tell you at the top which version you have:
endeavour u (international tegra3)
Evita (us snapdragon)
As for windows 8 drivers, I know they are available but not sure where to get them from mate, just search google
Click to expand...
Click to collapse
Thank you,
C:\Android-adb>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.36.0000
(bootloader) version-baseband: 5.1204.162.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.401.27
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.924s
This is what I have... So I guess I cant get S-OFF then.
1) What custom ROM is the best battery lastingwise? Is there an ARHD for the One X? Sorry to bother so much, wish I had more time to read up on my own.
2) Not even sure if this phone is unlocked or not, is it hard to unlock it so that any SIM card is accepted? Thanks!

Ok, I've done some reading, and I found out ARHD exists for the One X. My cousin's phone is on 3.14 firmware and ARHD here http://forum.xda-developers.com/showthread.php?t=1562603 says it is on 4.18
How do I update to 4.18? Can I flash a firmware or is it OK if I update the phone from "Settings" before unlocking and rooting it?
I know that for the One M7, you need to update firmware first before installing the ROM.

If you are on the 3.14 official you do not necessarily need to update the firmware. You can flash that rom straight away

To SIM unlock first try a SIM from a different network carrier, if it asks for a code then you need an unlock code.
There are 2 options
1. Call the network that supplied the phone and see if they will give you the code at no cost to you.
2. Use an unlocking service on eBay, this is what I did because my provider T-Mobile UK (EE) wanted to charge me over £20, instead I got the code from eBay for £2.99, here's a link if your interested mate: http://pages.ebay.com/link/?nav=item.view&id=111262080291&alt=web
This is the seller I used and I got the code within 10 minutes and it worked perfectly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

-unlock the bootloader
-flash custom recovery
-flash the boot.img
-perform a full wipe
-Install the rom.zip
Done.....

Mr Hofs said:
-unlock the bootloader
-flash custom recovery
-flash the boot.img
-perform a full wipe
-Install the rom.zip
Done.....
Click to expand...
Click to collapse
Thank you, I know how to do all those things, but on ARHD page under the requirements it says:
---Proper HBOOT version for Jelly Bean based ROM - How To change Hboot
And it shows a link to a 22 minute video... is this required or can I just ignore it (I have HBOOT 1.36)
Thanks again!
EDIT: you say to flash boot.img then full wipe then install rom, but http://forum.xda-developers.com/showthread.php?t=2069904 says to flash rom first then flash boot img... is it the same?

Like i said ...

It doesn't matter if you flash the boot.img before or after mate, I always flash it first.

one m8 stuck in bootloader ( no recovery, no os and relocked )

hello everyone
i've got an international m8 stuck in bootloader: if i turn it on, it will start in bootloader mode; it doesn't start in recovery and OS is blank. i've tried to flash recovery or hboot but i couldn't because it is relocked and s-on .
moreover model id and serial number are currupted :
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.19.21331147A1
version-cpld: None
version-microp: None
version-main:
version-misc: UNKNOWN SHIP S-ON
serialno: ¢v×KÖÃ/eg)╗©õ¶¨
imei: __________________
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: ☻◄
cidnum: HTC__203
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5e4b24e4
hbootpreupdate: 11
gencheckpt: 0

Haven't seen this before. Did you try to do anything before this happened?

Try getting your bootloader unlocked and flashing a custom recovery. Or if you have a SD card, try placing a firmware inside to let the system install the firmware. I'm s-on so I know not much about s-off. Or you can always send it back to warranty stating that you have no idea what happen to your device

I had that happen to me when I relocked the boot loader your going to have to run the appropriate ruu on your pc with your phone plugged in and on the bootloader screen

redsocks95 said:
hello everyone
i've got an international m8 stuck in bootloader: if i turn it on, it will start in bootloader mode; it doesn't start in recovery and OS is blank. i've tried to flash recovery or hboot but i couldn't because it is relocked and s-on .
moreover model id and serial number are currupted :
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.19.21331147A1
version-cpld: None
version-microp: None
version-main:
version-misc: UNKNOWN SHIP S-ON
serialno: ¢v×KÖÃ/eg)╗©õ¶¨
imei: __________________
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: ☻◄
cidnum: HTC__203
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5e4b24e4
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Ok think i figured this out was in the same boat you need to :
1:Boot into your bootloader
2:click fastboot
3:goto computer download squabbis htc one toolkit 3.2.x
4:install drivers for htc if you havent already
5:click fastboot got to the flash section
6n your computer download newest custom recovery you want
7:locate file from flash section then select partition recovery should have your custom recovery back
8:install desired rom from sd card if no sd card can be viewed try mounting it if that doesnt work reboot into recovery and click fast boot go back to computer open cmd where from your abd folder is and type in "fastboot oem enableqxdm 0"
hope this helps please report back to let me know if it worked
CHEERS plz click thanks if this helps anyone else

i can't flash recovery because my bootloader is relocked ( if i try ., it'll say "FAILED (remote: signature verify fail)" )
i tried to unlock bootloader but htcdev give me an error ( Error Code: 150) :
<<We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 150.
Error Reason: Extract Token Information Fail>>

redsocks95 said:
i can't flash recovery because my bootloader is relocked ( if i try ., it'll say "FAILED (remote: signature verify fail)" )
i tried to unlock bootloader but htcdev give me an error ( Error Code: 150) :
<<We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 150.
Error Reason: Extract Token Information Fail>>
Click to expand...
Click to collapse
Try the token again. You have to copy and paste everything including the <<<<< >>>>> but none of the "bootloader" stuff on the side.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure you don't have any "spaces" selected in it too.
Should be a problem with the copy/paste of the code, the reason says it all.

BerndM14 said:
Try the token again. You have to copy and paste everything including the <<<<< >>>>> but none of the "bootloader" stuff on the side.
Make sure you don't have any "spaces" selected in it too.
Should be a problem with the copy/paste of the code, the reason says it all.
Click to expand...
Click to collapse
i've tried several of times butg nothing , every time i get error 150

redsocks95 said:
i've tried several of times butg nothing , every time i get error 150
Click to expand...
Click to collapse
I know this is an old topic but for those experiencing the same problem, you need to go through the token request process via HTCDev all over AGAIN. The old token that you used to unlock is not valid after you relock as it has a different value.
Once you get the new token you can copy it to the fastboot folder and then in command prompt use the command fastboot flash unlocktoken Unlock_code.bin to unlock.
Hope this will be useful to someone in a similar dilema.

Need help with My M8

hi
i installed leneage OS on my device few months back then used it few days then left it in my drawer , a few days back when i started my phone i saw a vertical colored lines on screen and i can barley see what came to my mind is that a software issue so what did i do is went to recovery did a full wipe (system as well) and that is my mistake , screen became worse in i cant see any thing except lines still im able to boot into bootloader , fastboot etc..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader)
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 6(s)
My Device status now is Unlocked TWRP recovery and No OS
thanks in advance

Cutrus said:
hi
i installed leneage OS on my device few months back then used it few days then left it in my drawer , a few days back when i started my phone i saw a vertical colored lines on screen and i can barley see what came to my mind is that a software issue so what did i do is went to recovery did a full wipe (system as well) and that is my mistake , screen became worse in i cant see any thing except lines still im able to boot into bootloader , fastboot etc..
My Device status now is Unlocked TWRP recovery and No OS
thanks in advance
Click to expand...
Click to collapse
Please remove your imei and serialno
Do those lines appear in twrp menu?
Have you tried flashing a different rom?

Saleen28 said:
Please remove your imei and serialno
Do those lines appear in twrp menu?
Have you tried flashing a different rom?
Click to expand...
Click to collapse
Yes they are , i reflashed the os at the beginning same results

Saleen28 said:
Please remove your imei and serialno
Do those lines appear in twrp menu?
Have you tried flashing a different rom?
Click to expand...
Click to collapse
uploaded a picture

Seems like hardware issue imo.
Your M8 is blue - have you changed the unibody or it was just a blue model?
Also - was your drawer a dry place? Maybe some moisture somehow got into it.

Saleen28 said:
Seems like hardware issue imo.
Your M8 is blue - have you changed the unibody or it was just a blue model?
Also - was your drawer a dry place? Maybe some moisture somehow got into it.
Click to expand...
Click to collapse
Yes blue , I've store it in his original box in a dry place

I'd flash a ruu as a last line of defense if it's a software thing.
If that doesn't help then it's a hardware problem, probably the screen. If you're lucky then reconnecting the screen ribbon might fix it, if not - you need a screen replacement.

Saleen28 said:
I'd flash a ruu as a last line of defense if it's a software thing.
If that doesn't help then it's a hardware problem, probably the screen. If you're lucky then reconnecting the screen ribbon might fix it, if not - you need a screen replacement.
Click to expand...
Click to collapse
Tried to flash a RUU halted at this message when i flash the RUU
fail43 main version check fail
Didn't figure out how to pass it

Cutrus said:
Tried to flash a RUU halted at this message when i flash the RUU
fail43 main version check fail
Didn't figure out how to pass it
Click to expand...
Click to collapse
This error tells that you're trying to flash a ruu that is lower than your current firmware. Try this one - https://androidfilehost.com/?fid=24369303960687057
Also a short guide I've found, just in case
ckpv5 said:
For S-On
fastboot oem lock (to relock bootloader)
fastboot reboot-bootloader (reboot to bootloader after relock)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
Click to expand...
Click to collapse

HTC M9 Stuck on bootloop

Hello,
I have a friend's HTC M) which is stuck in the black HTC logo loop, approx 1.5 second loop that goes on and on until it dies from battery depletion.
This happened after some heating up by the phone, so my search points to corrupt data on Nand memmory (or Nand itself died), don't know whter we can reverse it or not.
After some tries, I managed to get it in recovery mode, and wiped cache and data, both completed with errors. I attached some pic of it.
If from recovery menu, I choose reboot into bootloader, it reboots and gets stuck on white screen with HTC logo (not the black one I spoke before).
I have been reading the HTC M9 thread, but I don't know which nex step to take.
This is an unbranded M9, without any rom modifications.
Model OPJA1000,
Software status: Official
Locked
S-ON
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If anyone could point me in the right direction, I'll gladly try to go by myself.
Thank you in advance!

I have same problem
My software status is modify.
D:\HTC M9\L51>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT55CYJ00237
all:
finished. total time: 0.125s
i am stuck on bootloader mod doesn't go on download mod nor to recovery mod.
can't boot to Android as well,
All the other values for CID, MID and other stuff is blank when I do indivdual fastboot getvar command.
can I bring my M9 to life with any stock image flashing with Fastboot command.
If yes please let me know which stock image I use and how to flash?
Thanks

ketulharini said:
I have same problem
My software status is modify.
D:\HTC M9\L51>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT55CYJ00237
all:
finished. total time: 0.125s
i am stuck on bootloader mod doesn't go on download mod nor to recovery mod.
can't boot to Android as well,
All the other values for CID, MID and other stuff is blank when I do indivdual fastboot getvar command.
can I bring my M9 to life with any stock image flashing with Fastboot command.
If yes please let me know which stock image I use and how to flash?
Thanks
Click to expand...
Click to collapse
I still haven't made progrss, since I got no help and even searching I got no easy solution. One thing I did make was a somewhat easy way to access recovery by trial and error. I disassembled back cover and tied to boot to recovery. If it entered in the bootloop, I'll just unplug the battery and tried again and again. With some tries I can get to recovery. I'll try to install from sd card to see if I can fix it.

While I put into recovery or download mode it shows this screen.
My one doesn't go into bootloop just stuck on this screen.
Do you think it can go to download or recovery mode with your method.
Thanks

If you can't get to download mode then the phone is broken.

c_sarmento said:
Hello,
I have a friend's HTC M) which is stuck in the black HTC logo loop, approx 1.5 second loop that goes on and on until it dies from battery depletion.
This happened after some heating up by the phone, so my search points to corrupt data on Nand memmory (or Nand itself died), don't know whter we can reverse it or not.
After some tries, I managed to get it in recovery mode, and wiped cache and data, both completed with errors. I attached some pic of it.
If from recovery menu, I choose reboot into bootloader, it reboots and gets stuck on white screen with HTC logo (not the black one I spoke before).
I have been reading the HTC M9 thread, but I don't know which nex step to take.
This is an unbranded M9, without any rom modifications.
Model OPJA1000,
Software status: Official
Locked
S-ON
If anyone could point me in the right direction, I'll gladly try to go by myself.
Thank you in advance!
Click to expand...
Click to collapse
Suck in the same situation. Rooted for months no issues then started bootlooping. I can get to twrp but wont go further any ideas??

Had the same issue. Hold up volume button and power button until phone switches off. Remove sd card then power on.
Must be trying to boot from and old or corrupted file on sd