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 one M9 - s-on, cannot flash, mount issues, soft brick with odd behaviour

Hi Guys,
I have an interesting one here, which I have been battling for a couple of days!
My nephew some time ago decided to put some custom ROM’s on his M9. Recently he had some odd happenings relating to encryption (something about asking for passwords), he tried to recover it and bricked it slightly!
Twrp 3.0.2-0 is on the device, but I cannot flash anything to the recovery, even 3.0.1-0. I cannot lock/relock the bootloader and when I try to flash the Unlock_code.bin it hands in download mode and does not give me onscreen instructions. Twrp tells me it cannot mount any partitions with a crypto footer missing message. I have tired reformatting some partitions (cache and data) as well as writing zero’s to the start of the partition and they still cannot mount with an invalid argument message. It also boots straight to the bootloader (with a flash of the HTC logo screen) and I have dd’ed the boot partition off the device and it’s all zeros (not sure if some kind of protection is stopping this).
Together with this these issues, I need to hold volume up and volume down to get to the bootloader (without it flashing the htc logo), but documentation I have read says down and power. When I hold down the volume up, it boots to a white screen with HTC logo. When I hold down the volume down it boot loops the black HTC logo.
Download mode is version 3.35.401.12 and CID HTC__001.
Any help would be appreciated,
Thanks,

FlangeMonkey said:
Hi Guys,
I have an interesting one here, which I have been battling for a couple of days!
My nephew some time ago decided to put some custom ROM’s on his M9. Recently he had some odd happenings relating to encryption (something about asking for passwords), he tried to recover it and bricked it slightly!
Twrp 3.0.2-0 is on the device, but I cannot flash anything to the recovery, even 3.0.1-0. I cannot lock/relock the bootloader and when I try to flash the Unlock_code.bin it hands in download mode and does not give me onscreen instructions. Twrp tells me it cannot mount any partitions with a crypto footer missing message. I have tired reformatting some partitions (cache and data) as well as writing zero’s to the start of the partition and they still cannot mount with an invalid argument message. It also boots straight to the bootloader (with a flash of the HTC logo screen) and I have dd’ed the boot partition off the device and it’s all zeros (not sure if some kind of protection is stopping this).
Together with this these issues, I need to hold volume up and volume down to get to the bootloader (without it flashing the htc logo), but documentation I have read says down and power. When I hold down the volume up, it boots to a white screen with HTC logo. When I hold down the volume down it boot loops the black HTC logo.
Download mode is version 3.35.401.12 and CID HTC__001.
Any help would be appreciated,
Thanks,
Click to expand...
Click to collapse
Oofta. If there ever was a candidate for restoring to stock via RUU, this would be it. From the OS version you list, your SKU is 401. Head to the readme thread and follow the instructions there.

computerslayer said:
Oofta. If there ever was a candidate for restoring to stock via RUU, this would be it. From the OS version you list, your SKU is 401. Head to the readme thread and follow the instructions there.
Click to expand...
Click to collapse
Thank you for the reply, I have an RUU zip that doesn't flag any errors via SD card (not the same story via fastboot, as I get RU security errors). However when it reboots, it goes to the bootloader and not the expected rebootRUU. If I execute 'fastboot oem rebootRUU', it goes into a bootloop. I did some checking and although I could be wrong, it appears to need the boot strap to do RUU, which could be hosed.

FlangeMonkey said:
Thank you for the reply, I have an RUU zip that doesn't flag any errors via SD card (not the same story via fastboot, as I get RU security errors). However when it reboots, it goes to the bootloader and not the expected rebootRUU. If I execute 'fastboot oem rebootRUU', it goes into a bootloop. I did some checking and although I could be wrong, it appears to need the boot strap to do RUU, which could be hosed.
Click to expand...
Click to collapse
Have you tried the backup files in flippy's thread?
Beamed in by telepathy.

shivadow said:
Have you tried the backup files in flippy's thread?
Beamed in by telepathy.
Click to expand...
Click to collapse
Can you please point me to the thread your referring to?
edit: I think I have found what your refering to, I'm just looking at this (Stock_Backup_3.35.401.12.zip), I'll check it out and see if I can do anything with it.

So I tired the flippy "TWRP Backup Section II" and after the restore and selecting boot to system, it boots to the bootloader and it appears retain the original recovery, so it isn't restoring anything by the looks of it. I've also just found out that this phone is a M9u, if that makes any difference and the RUU that doesn't flag any errors is signed_2_4.

FlangeMonkey said:
So I tired the flippy "TWRP Backup Section II" and after the restore and selecting boot to system, it boots to the bootloader and it appears retain the original recovery, so it isn't restoring anything by the looks of it. I've also just found out that this phone is a M9u, if that makes any difference and the RUU that doesn't flag any errors is signed_2_4.
Click to expand...
Click to collapse
It makes a difference all right. Let's back up a step and get all of your phone's information straight. What is it's model and OS version? You can find out by running the command "fastboot getvar all" after installing the HTC adb drivers (via HTC Sync Manager) with your phone plugged into your computer.

Under fastboot:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:*redacted*
Under Download Mode:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: *redacted*
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
On the back of the phone it reads: 0PJA100... FCC... M9u

FlangeMonkey said:
(bootloader) product: htc_himauhl
(bootloader) version-main: 3.35.401.12
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
Click to expand...
Click to collapse
These are the pieces that I find most helpful. From everything provided, I can't see why the M9u shouldn't be able to accept the RUU under normal circumstances.
I notice that in the instructions for the SD card method there is this note in step 6:
"Depending on your current firmware version it may reboot to Android or the Bootloader instead of rebooting to Download Mode. If this happens you just need to manually boot it to Download Mode."
Have you given that a shot? That may solve the problem.

computerslayer said:
These are the pieces that I find most helpful. From everything provided, I can't see why the M9u shouldn't be able to accept the RUU under normal circumstances.
I notice that in the instructions for the SD card method there is this note in step 6:
"Depending on your current firmware version it may reboot to Android or the Bootloader instead of rebooting to Download Mode. If this happens you just need to manually boot it to Download Mode."
Have you given that a shot? That may solve the problem.
Click to expand...
Click to collapse
Yea I did try that as well as a slew of different modes and options, which none of seem to work. I just performed it again for good messure and it bootloops on rebootRUU. I've also found an old backup from the phone itself that was performed back in October with twrp and that has no effect.
I have performed backups using TWRP after restores and examined the images but they are all zeroed! Additionally I do recall seeing write speeds in DD at the 50mb mark, which is way to fast in my opinion and using twrp restore is quick.
It’s very much like nothing is being written, but I have no idea why or if it’s possible to fix.
Could it be possible that something is physically broken, which is preventing writes?

FlangeMonkey said:
Yea I did try that as well as a slew of different modes and options, which none of seem to work. I just performed it again for good messure and it bootloops on rebootRUU. I've also found an old backup from the phone itself that was performed back in October with twrp and that has no effect.
I have performed backups using TWRP after restores and examined the images but they are all zeroed! Additionally I do recall seeing write speeds in DD at the 50mb mark, which is way to fast in my opinion and using twrp restore is quick.
It’s very much like nothing is being written, but I have no idea why or if it’s possible to fix.
Could it be possible that something is physically broken, which is preventing writes?
Click to expand...
Click to collapse
Bummer - it would have been nice if it had been a simple fix there.
It's entirely possible that something is physically broken, but that would probably involve some sort of corrupt memory chip or something. I don't know how you would confirm that though, at least without a professional tearing the phone apart.
From posts I've read elsewhere, it may be possible to flash individual partitions, but that's beyond me. Apart from exploring that option, I'm afraid I'm at a loss.

computerslayer said:
Bummer - it would have been nice if it had been a simple fix there.
It's entirely possible that something is physically broken, but that would probably involve some sort of corrupt memory chip or something. I don't know how you would confirm that though, at least without a professional tearing the phone apart.
From posts I've read elsewhere, it may be possible to flash individual partitions, but that's beyond me. Apart from exploring that option, I'm afraid I'm at a loss.
Click to expand...
Click to collapse
I appreciate your efforts. I have tried flashing partitions via DD and fastboot, but its the same result. Unless anyone can tell me another means to try?
On another note, is it possible to s-OFF in this state (paid or otherwise)?

FlangeMonkey said:
I appreciate your efforts. I have tried flashing partitions via DD and fastboot, but its the same result. Unless anyone can tell me another means to try?
On another note, is it possible to s-OFF in this state (paid or otherwise)?
Click to expand...
Click to collapse
Maybe with a Java Clip. The common method (Sunshine) requires a working ROM

Can't get past loading screen after factory reset

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

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

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

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

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

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

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

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

C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499185667
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 631e3609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
htc_fastboot finished. total time: 0.120s

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

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

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

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

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

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

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

bricked htc one m8s

Hi all,
@THE company I work we found a htc one m8s that when I booted it went straight to bootloader menu.
I want to get it working again so I started reading here on the forums, download some stuff from ruu.lalleman.net that I found in one of the other treads. In the end i'm still stuck and i'm hoping to get some advice through this channel.
Here is my current status
when the devices is connected to the PC it boots ALWAYS straight to bootloader with the following info
software status : Modified
unlocked
m8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.000
[email protected]
OS-1.16.401.10
eMMC-boot 2048MB
aug 13 2015
Fastboot USB with the normal stuff
when I try to load a RUU through the exe I reboot the device and then keeps waiting with in the end a disconnect (saying I need to connect my device) the device itself is already back in bootloader window.
when I try to use htc_fastboot to flash a recovery it gives me
fastboot flash recovery recovery.img
sending 'recovery' (6002 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 1(s)
but then on reboot it's straight back to bootloader menu no recovery
when I try to lock the device I get
fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: 15
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
(bootloader) [INFO] Rebooting device arbiter!!I PMIC arbitery-
FAILED (unknown status code)
Execution time is 1(s)
I did get it unlocked (as it was locked before but relocking is not working)
Also fastboot devices shows me the devices but adb devices shows nothing (tried both htc drives and general android ones)
These are my var all info
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__031
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1d456ef7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
Execution time is 28(ms)
Hoping on any help from here
Greetings
Tom

Little update:
I kept on trying different versions from recovery / boot / ruu's in the hope that one works but nothing so far.
In another topic somewhere I did found that as long as my device is unlocked it will not work to use RUU, so locking the device again will be my first step.
I did notice that when I ended my adventure yesterday evening I wasn't able to turn the phone off, I always rebooted (in like a millisecond) back to bootloader as long as it was connected to the pc. I had to remove the usb connection and then try couple of times with volume-up / power to turn it off.
I did do the 2 minutes bright licht / volume up + down + power button trick to reset the battery but that didn't change anything.
also as a last minute addition
when I do the fastboot -> image CRC i'm getting a 0X0 on sbl2 - sbl3 - boot and recovery so it seems that what ever I do with htc_fastboot flash is not sticking.
Going to look into trying to get it locked again now first in combination with trying to find out why I can't write to the damn phone (adb isn't working ether so maybe driver problem also ?)
The adventure continues
Tom

adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?

ckpv5 said:
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
Click to expand...
Click to collapse
That is indeed the RUU i tried, i got it based on the fastboot var all i did.
Still trying to get my Phone locked again as that is holding back the ruu upgrade now from what i see.

Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.

ckpv5 said:
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
Click to expand...
Click to collapse
Yhea i did it with the htc_fastboot version.

another update,
After some more trial and error while aiming for the locking of my phone i'm still stuck.
Both my boot and my recovery are empty it seems (the 0x0 from the image crc) and all the others still have 0xA.....B or what ever value in them
All the writing I do like
C:\tel>htc_fastboot.exe flash recovery recovery_signed.img
sending 'recovery' (30080 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
seems to be working but that doesn't change the crc value's nether does it allow me to use the recovery from the hboot menu.
also when I type stuff like htc_fastboot oem rebootRUU it brings me straight back to the bootloader menu, no black screen to do htc_fastboot flash zip rom.zip.
What I didn't try yet is using a SD-card and see if that fixes it (I could put that card in my other phone, write stuff to it and use it in the M8s.
Anybody got any expereance for using a sdcard to flash the device back to stock.
@ this moment I will be kind of happy with anything that advances me a step
Tom

I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.

kruc Ire said:
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
Click to expand...
Click to collapse
How do you mean give up ?
is there no way arround based on your opinion from what i posted above ?
I Always hoped it was my lack of knowledge that was holding me back in fixing it ...

Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.

kruc Ire said:
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
Click to expand...
Click to collapse
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom

TomBrunson said:
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
Click to expand...
Click to collapse
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough

I made that video but if the F'N censors won't let me put up the lyrics of a song they HATE in their pinheads then I won't be posting their garbage they WOULD view.
I'll keep putting up large videos though just to chew up this sh!tty world's resources. If it's a world of creeps it's
Music videos mostly. Ooh how they HATE my beautiful music...and I can hear the little b##ch there in her fuzzy chair. Like she spoke directly into my head. And if it hadn't taken me so long to make a thumbnail she wouldn't have been able to install her trick. Literally FFFF youtube.

kruc Ire said:
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
Click to expand...
Click to collapse
Is there a different command to Relock as to Lock ?
I couldn't find anything else then htc_fastboot oem lock
Tom

Ok i'm over it. I attached a different (worse) song and reuploaded it. No censorship now.
HTC M8s firmware flash in photos:
Please note I only started making a video because I noticed that time bar on upper right about 15 minutes into the (uninterrupted) flash. So that took a long time and I was concerned about the messed up and overprinted text and made photos during every new screen between the third or fourth at the start (when I caught up with my camera) up till the time of video starting.
So yeah what I am trying to say is it seemed to take very long, with many seemingly false starts and failures. Only by waiting did it finally achieve correctness.

thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick

TomBrunson said:
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
Click to expand...
Click to collapse
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.

kruc Ire said:
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
Click to expand...
Click to collapse
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom

You have never gotten it to lock? I thought you said you couldn't get the zip to work?
---------- Post added at 06:53 PM ---------- Previous post was at 06:38 PM ----------
TomBrunson said:
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
Click to expand...
Click to collapse
What output does your cmd window give u? Can you show a screenshot of what your command is and the output.

I see. You are trying to put a lollipop. Still first ya gotta lock it does anyone remember the rules for firmware flash? Is it going to screw up the phone to flash the MM 60 sense 70 ? Dude are you in Europe? The 60 70 I flashed from my microSd was a EUROPE.

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