Develop Bugs

Brick?

Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo

mtt_73 said:
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
Click to expand...
Click to collapse
im going to assume your phones is s-off?

Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Thank you.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Click to expand...
Click to collapse
You can't install custom recovery with a (re)locked bootloader.
With s-off, you shouldn't ever relock the bootloader, as its no longer a requirement to RUU once s-off. But that's neither here nor there at this point, just info for future reference.
Any response to: fastboot devices
Make sure the phone is in fastboot mode.
Try to run the GPE RUU with phone in fastboot mode, to get the phone back up and running at least. Assuming you are still on the GPE CID and MID.

How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Click to expand...
Click to collapse
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.

Hi guys,
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
1)flashing twrp via fastboot:
C:\adb>fastboot flash recovery C:\adb\openrecovery-twrp-2.8.5.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.438s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.500s
2) flashing stock recovery via fastboot( i dont know if i had the right one):
C:\adb>fastboot flash recovery C:\adb\recovery.img
target reported max download size of 1830727680 bytes
sending 'recovery' (14109 KB)...
OKAY [ 1.262s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.277s
3) 'booting' same stock recovery- what changed now are 3 android skaters for cca 0.2 sec when i try to enter recovery or start factory reset from bootloader, before it just went to fastboot usb mode.
C:\adb>fastboot boot recovery.img
creating boot image...
creating boot image - 14450688 bytes
downloading 'boot.img'...
OKAY [ 1.273s]
booting...
OKAY [ -0.000s]
finished. total time: 1.273s
Can please anyone help me? Thanks in advance
Here is data about the phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT.............8
(bootloader) imei: 35...........30
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

redpoint73 said:
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Click to expand...
Click to collapse
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Click to expand...
Click to collapse
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
mato123 said:
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
Click to expand...
Click to collapse
I would highly suggest not to post to another user's troubleshooting thread like this, as it doesn't look like the same problem at all (and in my experience rarely is, even when folks will post "I have the same issue"). You really should have just started your own thread, and would have been justified doing so IMO. Posting here just confuses matters for you, the OP and those trying to help.
But DON'T start another thread now (and add even more confusion). I'll ask the mods if they can move this post to its own thread.

ok, sorry

redpoint73 said:
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
Click to expand...
Click to collapse
Thanks for reply.
I went now in fastoob mode and tried to flash the RUU GPE again.
The error is:
macbooks-MacBook-Proownloads macbook$ ./fastboot-mac flash RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip
unknown partition 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
error: cannot determine image filename for 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
Just to clarify. I successfully when in GPE (with conversation). The problem was when going back to Sense. I do not know exactly what I did wrong.
My CID is 11111111
My MID is 0P6B10000
Really do not know how to proceed.
M

I unfortunately don't know jack about how to use fastboot and other actions on a Mac. I'm also not that familiar with running the RUU as a zip (I always do it on a PC with the RUU .exe).
But it looks like you just have the command syntax wrong. I think it should be:
fastboot oem rebootRUU
fastboot flash zip filename.zip
But it also look to me like nothing is actually "wrong" (aside from adb not working?). The phone not booting after relocking the bootloader is normal and intentional. You should just be able to run the desired Sense RUU, provided you have the right MID.

I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M

mtt_73 said:
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
Click to expand...
Click to collapse
hehe try watch this movie: https://www.youtube.com/watch?v=CCGj0rOuiR4
Most important is the firmware flash... so partition layout etc is changed to sense like after that you can flash sense roms etc. (for example viper rom as in video)

0kk0 said:
Most important is the firmware flash... so partition layout etc is changed to sense
Click to expand...
Click to collapse
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.

redpoint73 said:
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
Click to expand...
Click to collapse
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Sent from my HTC One_M8 using xda Forum

mtt_73 said:
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Click to expand...
Click to collapse
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.

redpoint73 said:
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
Click to expand...
Click to collapse
I did it. I am back to Sense now.
Any advice to remove tell HTC problem? I mean it says that I have a testing device. Is it because I am s-off? Should I go for s-on again? And how?
TY!

HTC m9 in bootloop after re-locking the bootloader

Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam

unlock with fastboot
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam

yotamh said:
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
Click to expand...
Click to collapse
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.

Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam

yotamh said:
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
Click to expand...
Click to collapse
It seems like you're talking about the android version not the firmware version since there is no 5.0.XXX.X firmware for the M9. For now it might be the best solution to wait until you're home.

yotamh said:
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
Click to expand...
Click to collapse
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!

LLegion said:
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
Click to expand...
Click to collapse
the problem is I can't unlock the bootloader. ADB devices doesn't work

Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?

yotamh said:
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
Click to expand...
Click to collapse
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in my google sheet (link can be found in my signature). Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.

Flippy498 said:
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in the google sheet in my signature. Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Click to expand...
Click to collapse
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??

yotamh said:
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
Click to expand...
Click to collapse
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.

Flippy498 said:
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Click to expand...
Click to collapse
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?

some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s

yotamh said:
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
Click to expand...
Click to collapse
yotamh said:
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
Click to expand...
Click to collapse
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.

Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Click to expand...
Click to collapse
Hi thanks for the top about the IMEI I've changed it.
and sorry, I didn't understood the the original comment and got in to the a wrong line in the comment. I'll try again with the correct file (2gb will take some to download). Again, thank you for your answer and patient. It's nice to see people try to help. :good:

THANK YOU so much! everything is working and even updated! thanks!

it seems i have a strange issue after all.
my phone doesn't detect my htc headphones. It recognize other headphone and the HTC headphones works with other devices.
it looks like a software issue.

Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. [REMOVED BECAUSE I'M A NEWBIE]I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature[/URL].
Click to expand...
Click to collapse
Hi I know this is probably old but I was in this exact same predicament and I had "tried everything" and your instructions brought my phone back to life!! I am so grateful after almost a week of adb commands and zip files that got me nowhere! THANK YOU SO MUCH!!!:good:

htc m9

Hallo good people. I am very new here. Irecently obtained an m9u from a friend. Apps keep stopping unexpectedly and accessing google servers seems to be a problem too. I took it to a technician but he couldnt help as the Australian software he installed is even worse. I decided ti flash on my own but i am getting an error 'invalid sparse file format at header magi'
Followed by something like 'couldnt read header len' Anyone who can help? Thanks

Have you gone through the readme thread?

I have only searched for related threads but wasn't lucky to find a solution to my problem

Boot in download and do "fastboot getvar all" and post here the result(remove your imei,sn...)

lucyr03 said:
Boot in download and do "fastboot getvar all" and post here the result(remove your imei,sn...)
Click to expand...
Click to collapse
D:\fastboot-win>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.38.841.6
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_96.01.51207G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
all:
finished. total time: 0.011s

Because of SuperCID I assume you have S-OFF too.
I recommend you to install the international ruu, but first change supercid(11111111) to a normal cid(HTC__032 for international).
Then you need to flash a nougat(4.xx.xxx.xx) firmware because you can't flash nougat ruu on marshmallow firmware(3.xx.xxx.xx).
After that you can flash the nougat ruu.
Links:
Nougat firmware: https://androidfilehost.com/?fid=817550096634760161
Nougat RUU: https://androidfilehost.com/?fid=961840155545567615

lucyr03 said:
Because of SuperCID I assume you have S-OFF too.
I recommend you to install the international ruu, but first change supercid(11111111) to a normal cid(HTC__032 for international).
Then you need to flash a nougat(4.xx.xxx.xx) firmware because you can't flash nougat ruu on marshmallow firmware(3.xx.xxx.xx).
After that you can flash the nougat ruu.
Links:
Nougat firmware: https://androidfilehost.com/?fid=817550096634760161
Nougat RUU: https://androidfilehost.com/?fid=961840155545567615
Click to expand...
Click to collapse
Thanks alot for the assistance. My phone is S-OFF but i will have to follow the procedures a step at a time because i am not good at tech. I hope things will work out fine.

mikkei said:
Thanks alot for the assistance. My phone is S-OFF but i will have to follow the procedures a step at a time because i am not good at tech. I hope things will work out fine.
Click to expand...
Click to collapse
You could find all informations you need in ReadMe thread.

lucyr03 said:
You could find all informations you need in ReadMe thread.
Click to expand...
Click to collapse
Thanks again. I will go through the thread, your guidance is highly appreciated

still unable to flash the RUU. Did relock the bootloader not sure whether it could be the cause
D:\adb>fastboot flash zip software.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2164446778 is not a multiple of
the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2164446778 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2164446778 is not a multiple of
the block size 4096
OKAY [ 1.058s]
writing 'zip'...
(bootloader) HOSD CL#869604
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_D
(bootloader) R2MQ3
(bootloader) ERR preload central directory info failed (EOCD).
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.110s

mikkei said:
still unable to flash the RUU. Did relock the bootloader not sure whether it could be the cause
D:\adb>fastboot flash zip software.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2164446778 is not a multiple of
the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2164446778 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2164446778 is not a multiple of
the block size 4096
OKAY [ 1.058s]
writing 'zip'...
(bootloader) HOSD CL#869604
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_D
(bootloader) R2MQ3
(bootloader) ERR preload central directory info failed (EOCD).
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.110s
Click to expand...
Click to collapse
You don't need to relock your bootloader when S-OFF.
With the fastboot method you need do do this command frist: fastboot oem rebootRUU
I recommend sdcard method anyway, the fastboot can fail if you don't have the correct htc_fastboot.exe

lucyr03 said:
You don't need to relock your bootloader when S-OFF.
With the fastboot method you need do do this command frist: fastboot oem rebootRUU
I recommend sdcard method anyway, the fastboot can fail if you don't have the correct htc_fastboot.exe
Click to expand...
Click to collapse
Thanks for your quick reply. I had done that command already. Guess the problem is that I don't have correct htc_fastboot. Have to try sd method now

lucyr03 said:
You don't need to relock your bootloader when S-OFF.
With the fastboot method you need do do this command frist: fastboot oem rebootRUU
Click to expand...
Click to collapse
That only applies to HTC devices that are older than the M9. On the M9 you don't need to relock at all for RUUs. And the download mode accepts RUUs via htc_fastboot, as well. It even gives you a more detailed output about the flashing process of the single files inside the RUU than the RUU mode.

Flippy498 said:
That only applies to HTC devices that are older than the M9. On the M9 you don't need to relock at all for RUUs. And the download mode accepts RUUs via htc_fastboot, as well. It even gives you a more detailed output about the flashing process of the single files inside the RUU than the RUU mode.
Click to expand...
Click to collapse
I encountered errors with custom RUUs(not signed) in download mode, that's the cause I told him to flash from RUU mode.
EDIT: Off-topic: I saw in your signature that you are using ViperOneM9 rom, what kernel are you using and how's battery life, if you have some time could you PM me please? I have few questions

Flippy498 said:
That only applies to HTC devices that are older than the M9. On the M9 you don't need to relock at all for RUUs. And the download mode accepts RUUs via htc_fastboot, as well. It even gives you a more detailed output about the flashing process of the single files inside the RUU than the RUU mode.
Click to expand...
Click to collapse
Thanks for the clarification. If you can please give me a link to the correct htc_fastboot.

They're linked in one of the first posts of the ReadMe thread.

Flippy498 said:
They're linked in one of the first posts of the ReadMe thread.
Click to expand...
Click to collapse
Okay. Thanks

Thanks all for your help I was finally able to flash my phone, unfortunately apps are still stopping unexpectedly so i suspect it could be a hardware issue. Right now the digitizer doesn't work, volume buttons don't work too neither can i use a mouse so I have to wait for the device to run out of power. I think its time to buy a new phone I can't keep bothering people here. All the best team developers!

mikkei said:
Thanks all for your help I was finally able to flash my phone, unfortunately apps are still stopping unexpectedly so i suspect it could be a hardware issue. Right now the digitizer doesn't work, volume buttons don't work too neither can i use a mouse so I have to wait for the device to run out of power. I think its time to buy a new phone I can't keep bothering people here. All the best team developers!
Click to expand...
Click to collapse
Hmm, that's strange, can you flash a twrp and see if the digitizer is working?
Sent from my HTC One M9 using Tapatalk

lucyr03 said:
Hmm, that's strange, can you flash a twrp and see if the digitizer is working?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
It actually worked for some time after flashing the RUU but later everything started misbehahing just like before. The problem is that i can not power off so no way to boot download mode. ADB does not recognise my device since i cannot unlock it.

Recovery/System Bootloop - Fastboot Doesn't Flash

I am suffering from a bootloop in my phone, lineage suddenly decided to crash trebuchet, and phone turned off. Bootloader works, download mode works, recovery absolutely DOES NOT, It gives me the black HTC logo and turns off and on when I put the "fastboot oem lock" option, and just redirects back to the bootloop when I don't. I can use fastboot to flash files to it, I flashed TWRP old and new, but nonetheless, it bootloops when picking recovery once more. I have S-ON, with the bootloader unlocked. I'd love to buy the sunny license and turn S-OFF, but have no way of accessing my OS anymore.
Here are my details.
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
Here is my recovery flashing log
target reported max download size of 800000000 bytes
sending 'recovery' (20084 KB)...
OKAY [ 2.097s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.838s]
finished. total time: 3.939s
I've tried flashing a signed stock ROM, but I know I need to re-lock the bootloader, the "fastboot oem lock" option doesn't work too well either, it just resets without actually locking anything. It can't hold a flash it seems.
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp (bootloader) [KillSwitch] Last Byte is 0X01, enable unlock (bootloader) RELOCK device
I've tried the "0PJAIMG.zip" method in download mode, but it just gives me these errors as well.
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
If my phone gets a file that matches up, it freezes for a bit, THEN goes back to another bootloop. It's frustrating.
9 RU_SECURITY_FAIL is also another error I get when trying to flash the .zip by fastboot, they're so annoying.
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
OKAY [ 1.028s]
writing 'zip' 1/1...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.053s
Then after that, I tried flashing "0PJAIMG_HIMA_WHL_L50_SENSE70_SPCS_Sprint_WWE_1.32.651.17_Radio_1.10.C1144022_50312.5_NV_SPCS_0.23_003_release_425355_signed_RYDAH805.zip" via download mode with the SD card, and it gave me a FAIL19 RU_MAIN_VER_FAIL error that I don't understand that well, but I did find a reddit thread on it. I may have messed up my partitions.
https://www.reddit.com/r/AndroidQuestions/comments/69i53h/help_with_htc_m9_fail19_ru_main_ver_fail/
HOSD is also yet another method that ends up in failure
sending 'hosd' (38148 KB)... OKAY
writing 'hosd'... (bootloader) HOSD CL#695981
FAIL35 RU_PARTITION_NOT_SUPPORT hosd
FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT hosd)
Execution time is 4(s)
Here are a list of things that DIDN'T work
-Firmware Flashing
-Boot/TWRP Flashing
-fastboot oem unlock
-the "Power then Volume up" trick, it just redirects me to a white HTC splash screeen
-Recovery from bootloader option
-signed .img files
https://androidforums.com/threads/htc-one-m8-brick-stuck-on-boot.927336/
After finding the thread above, I'm starting to think it might be a hardware error, it now gives me a "Failed to boot to recovery mode" error,. The eMMc may be messed up, ughhhhhhhh
Any way to recover my files, at least? If anyone here has any clues on getting my phone to working condition, I'd appreciate it a ton, hell, I might even pay you for helping me, better than losing all my data!
Will add as much info as possible and update my current status if asked.

Stop before you break it.
Find the official stock signed firmware ruu in .zip format that matches your current firmware. Ie 3.41.651.x (x can be any number but the other 3 octets MUST MATCH). Rename it to 0PJAIMG.ZIP and copy to the external sdcard.
DO NOT relock/lock the bootloader and DO NOT s-on.
Boot to download mode (Black screen red writing) and at the bottom, in yellow text, you should see "press vol up to flash"..

shivadow said:
Stop before you break it.
DO NOT relock/lock the bootloader and DO NOT s-on.
Boot to download mode (Black screen red writing) and at the bottom, in yellow text, you should see "press vol up to flash"..
Click to expand...
Click to collapse
That's unfortunately the issue, I AM S-On, never turned it off, which has pretty much sealed this poor phones fate I assume. If not, I'm betting I would have already flashed a no wipe .zip successfully. It's a shame, since this could have been prevented if I knew this phone was prevalent to system corruption, now the only thing I can depend on is obtaining a compatible recovery, since mine isn't working, download/fastboot is the only thing I have now.
It also seems I cannot find the "RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.4.zip" over the web, would an .exe work if I rename the extension as .zip?

S-on or s-off doesn't matter. What i meant is if you go s-off there is no need to ever s-on again. Same for bootloader. If it's unlocked then you don't ever need to lock/relock it.
Exe or zip but sometimes exe fails. Exe must be run on a pc and have the phone connected via USB. Zip must be run from external sdcard. It MUST be that version regardless.
Your only way without buggering it further is to flash the stock firmware. It will replace the recovery etc itself and will be safer than messing around with it, if it flashes OK.

shivadow said:
S-on or s-off doesn't matter. What i meant is if you go s-off there is no need to ever s-on again. Same for bootloader. If it's unlocked then you don't ever need to lock/relock it.
.
Click to expand...
Click to collapse
Then I'm assuming the correct fw "0PJAIMG.zip" would flash successfully even with an unlocked bootloader?

RebeccaSugar said:
Then I'm assuming the correct fw "0PJAIMG.zip" would flash successfully even with an unlocked bootloader?
Click to expand...
Click to collapse
Correct.
If you prefer the *.zip over the *.exe then take a look at the "further reading" section of the ReadMe thread. There's a link to a decryption tool. Download the correct version for your computer. If you use windows, you can drag and drop the *.exe onto the decryption tool and it will extract the *.zip for you. On Linux and Mac you'll probably need to use some commands.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Correct.
If you prefer the *.zip over the *.exe then take a look at the "further reading" section of the ReadMe thread. There's a link to a decryption tool. Download the correct version for your computer. If you use windows, you can drag and drop the *.exe onto the decryption tool and it will extract the *.zip for you. On Linux and Mac you'll probably need to use some commands.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Done, though, after doing the "0PJAIMG.zip" method once more, it interrupts the flash with a very fast error(?) message highlighted in white then quickly reverts to bootlooping the recovery splash screen (Black Background with Silver HTC Logo)
I decided to flash the boot.img and system.img
target reported max download size of 800000000 bytes
sending 'recovery' (20084 KB)...
OKAY [ 2.097s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.838s]
finished. total time: 3.939s
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: 990005027515833
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
C:\Users\Infinity>Documents\Pack\fastboot.exe flash system C:\Users\Infinity\Documents\James\HTC\OUT_0PJA_3.41.651.21\system\system.img
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.232s]
sending sparse 'system' 1/6 (743090 KB)...
OKAY [ 40.331s]
writing 'system' 1/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 28.653s]
sending sparse 'system' 2/6 (725823 KB)...
OKAY [ 39.600s]
writing 'system' 2/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 27.937s]
sending sparse 'system' 3/6 (776453 KB)...
OKAY [ 42.390s]
writing 'system' 3/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 30.090s]
sending sparse 'system' 4/6 (764994 KB)...
OKAY [ 41.446s]
writing 'system' 4/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 30.371s]
sending sparse 'system' 5/6 (775925 KB)...
OKAY [ 42.348s]
writing 'system' 5/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 29.562s]
sending sparse 'system' 6/6 (546809 KB)...
OKAY [ 31.210s]
writing 'system' 6/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 21.738s]
finished. total time: 405.943s
They were successful, apparently, but I've seen no changes. When booting, it just hangs on the white splash screen with the green htc logo and the "This build is for development, etc" warning.
If only I had a way to boot a working recovery, the more I do this, the more it seems like it is without a shadow of a doubt, a hardware problem.
Here are some logs, the fw seems to match up with my phone just fine, nonetheles...
View attachment RUU_Decrypt_LOG-0PJA20000_3.41.651.21_2018-04-01_025319.txt
View attachment android-info.txt
View attachment android-info2.txt
View attachment backup_android-info.txt

I noticed that you used fastboot. Be aware that flashing RUUs isn't possible with the generic fastboot files. You'll need htc_fastboot. A download link can be found in the RUU section of the ReadMe thread.
Are you sure that the SD card isn't broken? (Never use old cards for flashing RUUs. They can corrupt the files.) Did you try another one? Normally the extracted *.zip should flash just fine via an SD card.
I'd try a different SD card and flashing the RUU via htc_fastboot. (Flashing only the system and the boot.img might not be sufficient.) If both methods fail then the phone's hardware is most probably damaged and there's nothing you could do.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
I noticed that you used fastboot. Be aware that flashing RUUs isn't possible with the generic fastboot files. You'll need htc_fastboot. A download link can be found in the RUU section of the ReadMe thread.
Are you sure that the SD card isn't broken? (Never use old cards for flashing RUUs. They can corrupt the files.) Did you try another one? Normally the extracted *.zip should flash just fine via an SD card.
I'd try a different SD card and flashing the RUU via htc_fastboot. (Flashing only the system and the boot.img might not be sufficient.) If both methods fail then the phone's hardware is most probably damaged and there's nothing you could do.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I used a different SD card, formatted it to fat32 then exFAT, and nothing happened, it just gave me another error and rebooted. Though, after the reboot I manually booted the download mode and the same happened. Except this time, it gave me a list of all the .img files at 0% inside the "0PJAIMG.zip" before abruptly shutting off.
I took your advice on using the manual htc_fastboot to flash the "0PJAIMG.zip", even with the powershell, and it still fails.
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.41.651.21
found large-zip header, file count: 8
processing file 1/8...
sending 'zip' (88845 KB)...
OKAY [ 5.992s]
writing 'zip'...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 7.195s
htc_fastboot finished. total time: 8.782s
I did a bit of spelunking and came across this users post, that had the same issue as I.
repl1ca said:
Ok...so hopefully I didn't foobar something. I went to go back to stock since I'm returning my phone soon (1 year lease), so I relocked my bootloader before trying to flash the RUU (I'm S-ON by the way). Relock went fine, but the phone immediately returned to the bootloader with a "*** Security Warning***" message and now the phone won't boot into the ROM or recovery. I tried booting into download mode and flashing the RUU zip, but I am getting the following message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip d:\downloads\0PJAIMG.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of the block size 4096
OKAY [ 1.015s]
writing 'zip'...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.017s
I also tried running the RUU exe in download mode, but that didn't work either.
Hopefully I am doing something wrong and didn't mess the phone up! I will be forever in debt to whoever can help me.
P.S. - I also tried unlocking the bootloader again but that is failing as well!! (Even though it says successful...)
_____________________________________________________________________________
EDIT: Ok, so I gave my Windows account full access to the platform-tools folder (which includes fastboot and the unlock token) and tried unlocking again, and it worked?! ROM is booting now, but how do I avoid having this happen again and return to stock? TIA
Click to expand...
Click to collapse
What did he mean by "Full Access to the platform-tools folder"? That may be my meal ticket to getting my phone working or nothing else.

You have to go into Windows Explorer on your computer and find the platform-tools folder. Once you find it, right click on it and go to Properties, then the Security tab. On that tab, add your Windows username in there and make sure the Full Access box is checked. Hit Apply, then OK.
My post is really old, so I'm having a hard time remembering what the actual issue was [emoji23]
Sent from my SM-G965U using Tapatalk

Security fail means the ruu is corrupt. Remote:9 I think is unsigned ruu. You need to be flashing a signed ruu.zip.

shivadow said:
Security fail means the ruu is corrupt. Remote:9 I think is unsigned ruu. You need to be flashing a signed ruu.zip.
Click to expand...
Click to collapse
That's what bothers me the most, the ruu I have IS signed, you sure I don't need S-OFF, or to lock the bootloader?

Security or bootloader make no odds. If you had s-off life would probably be easier..
Exactly which file are you flashing? Have you checked the md5 hash?

shivadow said:
Security or bootloader make no odds. If you had s-off life would probably be easier..
Exactly which file are you flashing? Have you checked the md5 hash?
Click to expand...
Click to collapse
I'll probably buy the XTC 2 Clip chip thing needed to manually turn S-OFF, I don't care about paying a little extra, as long as I can recover all my files in the phone.
I am flashing a "3.41.651.21" .zip from extracted from "RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.21.exe"
The MD5 hash for it is "f41f1b941eb3f9f9ecaebcbf235e87af"
Which looking up the hash reveals to be the version for my exact same hardware, kernel and software version
https://androidfilehost.com/?fid=312978532265363975
I'm more than confident S-OFF is the only way to fix it. Unless there are cases of android bricking, even with a working fastboot. Something, a type of security, is preventing files from being read/flashed, unless It's an eMMc error. Two verdicts now.

You most probably won't be able to recover any files at this point. Flashing a RUU will delete everything that's stored on your phone. Even S-OFF won't change that. S-OFF will only enable downgrading with older RUUs. Converting the phone isn't recommended unless you're willing to risk getting a paperweight since it's a CDMA device.
I haven't seen error 9 before I read about it in this thread. Since you already tried different methods and the md5 checksum of your manually extracted RUU seems to match the one of the AFH RUU, chances are high that the phone's hardware is broken.
Sorry for the bad news.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
You most probably won't be able to recover any files at this point. Flashing a RUU will delete everything that's stored on your phone. Even S-OFF won't change that. S-OFF will only enable downgrading with older RUUs. Converting the phone isn't recommended unless you're willing to risk getting a paperweight since it's a CDMA device.
Click to expand...
Click to collapse
At this point, it's already a paperweight, what's an extra $100 invested on the XTC 2 Clip going to do? Haha! If I can't recover the files, I'll just make an attempt at salvaging this phone and giving it away to someone else.
Flippy498 said:
I haven't seen error 9 before I read about it in this thread. Since you already tried different methods and the md5 checksum of your manually extracted RUU seems to match the one of the AFH RUU, chances are high that the phone's hardware is broken..
Click to expand...
Click to collapse
That IS a fear, especially about hearing about the "horrors" of the Hynix eMMc from people in the the thread I linked in the OP, and others in gsmhosting, this device might have just been another victim of faulty circuitry, which actually has me steamed.
http://forum.gsmhosting.com/vbb/f961/htc-one-m9-bootloop-2214236/#3
This is going to be my brave (read: foolish) attempt.

The biggest problem of the M9 is the Snapdragon 810 processor. Although later firmware revisions fixed the overheating (more or less) the heat damages that emerged from to the usage of older firmware versions aren't fixable.
Most phones that got sold with this processor suffer from similar issues, sooner or later. If you check the xda forums from other 2015 flagship devices with the SD810 you'll see that they all have some kind of sudden bootloop death problem.
And as said before, getting S-OFF won't change your situation. If you really want to try a method that has a slightly chance of being successful you should search for a jtag device like e.g. a riff-box. The thing is I personally don't have any experiences with jtagging. I only know that it can still help in situations in which there already seems to be no hope, anymore. Check sneakyghost's firmware thread in the development section. If I remember correctly, post #5 contains info or at least a link with further info about the topic. Be aware that these devices can be quite expensive.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
The biggest problem of the M9 is the Snapdragon 810 processor. Although later firmware revisions fixed the overheating (more or less) the heat damages that emerged from to the usage of older firmware versions aren't fixable.
Most phones that got sold with this processor suffer from similar issues, sooner or later. If you check the xda forums from other 2015 flagship devices with the SD810 you'll see that they all have some kind of sudden bootloop death problem.
Click to expand...
Click to collapse
I've heard things like that before! It shorts out the board or something above those lines, if heating is an issue, then it certainly did that to mine, which may be the fault of the missing recovery and bootloop, along with one crash I remember! Yes, I remembered I had one crash, the screen had all sorts of garbled colorful static on it and the phone made a beeping noise, why didn't I remember that!? I'm an idiot. That should have been a clear warning to back up everything, I should have reminded myself of the issues with the 810 Processor. Whether the crash months earlier had anything to do with what might have either been a sign of decay, or just a coincidence is beyond me, but knowing my current position with this phone, I'll go with the former.
Flippy498 said:
And as said before, getting S-OFF won't change your situation. If you really want to try a method that has a slightly chance of being successful you should search for a jtag device like e.g. a riff-box. The thing is I personally don't have any experiences with jtagging. I only know that it can still help in situations in which there already seems to be no hope, anymore. Check sneakyghost's firmware thread in the development section. If I remember correctly, post #5 contains info or at least a link with further info about the topic. Be aware that these devices can be quite expensive.
Click to expand...
Click to collapse
Lucky for you (and me) I do! I've successfully soldered about 5 things in the past, so this phone should be familiar territory! I just cancelled the XTC 2 Clip order, and instead ordered myself a Riff Box, I saw that it supports my HTC 9, and I thank you for telling me this! I work much better under hardware than software (Thanks ADHD), I'll check out. I immensely appreciate your help, and you taking time out of your day to give me sources, it truly, honestly means a lot. The device is around $120, not horribly expensive, my wallet can take it, I'll update you on my progress later in the thread! Thanks again!
Woah, apparently I don't NEED to solder? Well, this just makes it easier I'd say! BUT, I don't trust myself enough to risk destroying the sensitive data inside my device, so I will e-mail Tecardo and offer him a price for helping me instead. Can't trust myself enough not to screw up!

Oh, only 120 bucks? Don't ask me why but I had a higher price in mind. Either my mind betrayed me or the riff box got cheaper...
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Oh, only 120 bucks? Don't ask me why but I had a higher price in mind. Either my mind betrayed me or the riff box got cheaper...
Click to expand...
Click to collapse
Well, in your defense, there ARE bundles that are priced ridiculously high (In the $500's for some damned reason) even though you can get the same bundles separately, for less than half of what they ask.

HTC 10 - Bricked

So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still disabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?

PirateNL said:
So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still enabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?
Click to expand...
Click to collapse
im in the same situation ,i'm currently looking at data recovery option from gillware since apparently they literally go the extra mile physically to extract data. but im hoping there is options for me to unbrick it before deciding on that option

venom55521 said:
im in the same situation ,i'm currently looking at data recovery option from gillware since apparently they literally go the extra mile physically to extract data. but im hoping there is options for me to unbrick it before deciding on that option
Click to expand...
Click to collapse
Well at least the data on the device is not worth much to my friend. Let me know if you find were able to unbrick it

PirateNL said:
So I'm trying to restore a HTC 10 of a friend of mine which is in a boot loop.
I can enter bootloader mode (white background with four options), but I cannot enter download mode.
Bootlocker is locked and S-ON, i also think USB debugging is still disabled.
I want to try to follow these steps: https://forum.xda-developers.com/showpost.php?p=72992391&postcount=26
However, ADB does not even seem to detect the device in bootloader mode even though Windows recognizes it as being a HTC device.
I'm at the stage of just throwing the device away, as I think it is bricked. Anyone has any ideas left?
Click to expand...
Click to collapse
ADB won't detect it if USB debugging is turned off.
Can you boot to RUU mode? If so you could restore it perhaps that way. If you are booted to that you can run an RUU.exe
The command is:
fastboot oem rebootRUU

xunholyx said:
ADB won't detect it if USB debugging is turned off.
Can you boot to RUU mode? If so you could restore it perhaps that way. If you are booted to that you can run an RUU.exe
The command is:
fastboot oem rebootRUU
Click to expand...
Click to collapse
Thanks for your reply. I'm not sure on how I can execute that command without ADB/USB debugging being enabled? Any advice there?

PirateNL said:
Thanks for your reply. I'm not sure on how I can execute that command without ADB/USB debugging being enabled? Any advice there?
Click to expand...
Click to collapse
You don't have to have USB debugging on to use fastboot commands, only ADB commands. For many fastboot commands, you need an unlocked bootloader. For this one you don't. Or at least you didn't on the M8 before HTC introduced download mode. I'm pretty sure it will still work.

xunholyx said:
You don't have to have USB debugging on to use fastboot commands, only ADB commands. For many fastboot commands, you need an unlocked bootloader. For this one you don't. Or at least you didn't on the M8 before HTC introduced download mode. I'm pretty sure it will still work.
Click to expand...
Click to collapse
So I only had time to test this today. And you were right i was able to trigger this command:
fastboot oem rebootRUU
The phone then rebooted showed the grey HTC boot screen and soon after it started the boot loop sequence again. What am I suppose to do now? Is there anything I can flash in this RUU mode? Thanks again for your help.

PirateNL said:
So I only had time to test this today. And you were right i was able to trigger this command:
fastboot oem rebootRUU
The phone then rebooted showed the grey HTC boot screen and soon after it started the boot loop sequence again. What am I suppose to do now? Is there anything I can flash in this RUU mode? Thanks again for your help.
Click to expand...
Click to collapse
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.

xunholyx said:
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.
Click to expand...
Click to collapse
Unfortunately I do not see the red security warning, it just a grey HTC logo for a few seconds, then it reboots and then shows a white HTC logo + "powered by android" and then its stuck in the boot loop again.
The phone is an EU-model, this is the output you requested:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA69KBN01219
all:
finished. total time: 0.360s
The version-main variable does not seem to be there

xunholyx said:
You can flash an RUU in RUU mode. An RUU is HTC's "ROM Update Utility". It's a full system image. You would need to know his model type, like Sprint, AT&T, US Unlocked, etc Then you could download the appropriate RUU for it.
Does it boot to RUU mode with the red security warning at the bottom? If so, enter fastboot getvar all, and you can find the firmware version the phone is on now. It's listed under "version-main". Get the RUU with the same version number as that, and flash it in RUU mode.
If you can get the firmware version and you post it here, I can direct you to the proper RUU to download.
Click to expand...
Click to collapse
Hey man, if you have some time today. Could you please look at the output I sent? Im not sure what to do next.
Thanks in advance

PirateNL said:
Hey man, if you have some time today. Could you please look at the output I sent? Im not sure what to do next.
Thanks in advance
Click to expand...
Click to collapse
The readout doesn't really say anything. With the HTC 10, and starting with the M9 I believe (I never owned one), you can only get a proper getvar from download mode or RUU mode. You can't get one from bootloader anymore like you used to be able to.
You said it was a EU model, so I would suspect it's WWE. The RUUs for that are available, but you can't flash it in bootloader, only download or RUU mode.

exactly the same problem here
PirateNL said:
Unfortunately I do not see the red security warning, it just a grey HTC logo for a few seconds, then it reboots and then shows a white HTC logo + "powered by android" and then its stuck in the boot loop again.
The phone is an EU-model, this is the output you requested:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA69KBN01219
all:
finished. total time: 0.360s
The version-main variable does not seem to be there
Click to expand...
Click to collapse
I have exactly the same problem with my HTC10, i don't have access to download mode, recovey, system, i even tried to boot to an image of twrp and i can't.
Code:
D:\Android\platform-tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA661BN06728
all:
Finished. Total time: 0.393s
Click to expand...
Click to collapse
Click to expand...
Click to collapse

xunholyx said:
The readout doesn't really say anything. With the HTC 10, and starting with the M9 I believe (I never owned one), you can only get a proper getvar from download mode or RUU mode. You can't get one from bootloader anymore like you used to be able to.
You said it was a EU model, so I would suspect it's WWE. The RUUs for that are available, but you can't flash it in bootloader, only download or RUU mode.
Click to expand...
Click to collapse
OK that makes sense. But as you know I cannot get into RUU nor download mode. I guess it really is bricked then. Oh well thanks for your time and help.

PirateNL said:
OK that makes sense. But as you know I cannot get into RUU nor download mode. I guess it really is bricked then. Oh well thanks for your time and help.
Click to expand...
Click to collapse
It might not be. A friend reminded me of a method in a conversation about something else. I'm at work right now, but I'll reply again later on when I'm home

Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.

no luck
xunholyx said:
Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.
Click to expand...
Click to collapse
D:\Android\platform-tools>fastboot flash radio radio.img
Sending 'radio' (54629 KB) OKAY [ 1.341s]
Writing 'radio' FAILED (remote: 'cannot flash
this partition in s-on state')
fastboot: error: Command failed
it says that because it is in S-On state, any ideia ohow can i change the S state?
thank you mate

xunholyx said:
Here's how you may be able to fix it. If you flash all of the parts of the firmware.zip included in the RUU, you essentially are flashing the RUU (mostly, but not exactly).
You can flash the individual parts in bootloader.
Here is a link to the instructions
Here is a link to the firmware you will need.
And as I've already stated, I assume he has WWE firmware. This firmware is not carrier branded. You said he had the European model so I'm going with that.
You can already boot to bootloader, so obviously you can skip that part of the instructions.
Good luck! Hopefully you can bring it back to life.
Click to expand...
Click to collapse
Tried to revive it today. Unfortunately getting the same error as our friend in the post above me:
Code:
C:\adb>fastboot flash radio radio.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (54629 KB)...
OKAY [ 1.366s]
writing 'radio'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.456s
So to summarize:
- Not able to boot into download/recovery/RUU mode
- Cannot flash images using fastboot due to S-ON
I guess that's it, RIP HTC 10.

PirateNL said:
Tried to revive it today. Unfortunately getting the same error as our friend in the post above me:
Code:
C:\adb>fastboot flash radio radio.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (54629 KB)...
OKAY [ 1.366s]
writing 'radio'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.456s
So to summarize:
- Not able to boot into download/recovery/RUU mode
- Cannot flash images using fastboot due to S-ON
I guess that's it, RIP HTC 10.
Click to expand...
Click to collapse
costum rom was installed on my phone I deleted everything with trwp normally I should have installed a new rom file but I didn't now the htc logo is stuck, there is twrp unlocked but I can't access it the boot loader does not open, because there is no rom, it does not open normally, there is only htc logo and red warning, maybe I can open the security mode or something else I am very tired