Develop Bugs

Htc m9 soft bricked

Hi everyone i hope I put this in the right area I'm new to forums and if not I'm sorry and could the admin please put me in the right place so I known for next time we'll here's my problem I have an AT&T m9 bootloader locked rooted and s-off with twrp recovery 2.8.6.0 well I tryed flashing the viperone rom on it with the bootloader locked I assumed sence i rooted it the bootloader was unlocked well it was not and so its now soft bricked it I can still get in to recovery but it hangs on the logo screen if I try to boot it up and I've tryed the ruu for it that another post told me to use but every time I try I get error code 150 unknown error and when I go to download mode it says at the bottom file /mnt/media_rw/ext_sd/opjaimg.zip file not found and the memory card I have is 64 gigs if that makes a difference if any one can help me that would be much appreciated and thanks for any help anyone can give
me

Unlock the bootloader via htcdev and flash viperone via twrp

htc m9
degerli43 said:
Unlock the bootloader via htcdev and flash viperone via twrp
Click to expand...
Click to collapse
hi iv tried what you said but i dont get that long list like im suppose to iget this
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.012s]
finished. total time: 0.014s
C:\Program Files (x86)\Minimal ADB and Fastboot>
and when im in the bootloader i dont have a fastboot option do i not have fastboot poperly installed mabe

OEM unlocking should be ticked in Settings>developer options

side_flip15 said:
OEM unlocking should be ticked in Settings>developer options
Click to expand...
Click to collapse
It should all ready be off because the guy I paid to get the frp off checked oem unlocking to be able to get the s-off and I can't get to settings anyway cause it's soft bricked

Well based on the fastboot command output it seems like its not.
Please run fastboot getvar all and post the output here. remove the SN and IMEI

side_flip15 said:
Well based on the fastboot command output it seems like its not.
Please run fastboot getvar all and post the output here. remove the SN and IMEI
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Owner>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: 11111111
all:
finished. total time: 0.046s
i all so made sure fastboot was properly installed

Looks like you have a dev edition.
Two options for you...
1. Since you are s-off already you can try to unlock bootloader without htcdev. check this link for instructions. After unlock you can flash latest TWRP here. You're still in LP firmware so latest Viper ROm will not work for you. You will need to flash MM dev edition firmware, dl here.. After flashing you can install the latest Viper Rom via TWRP.
2. You can find the MM RUU or ROm.zip here. Run RUU or flash Rom.zip. This will already upgrade your M9 to MM.
good luck!

side_flip15 said:
Looks like you have a dev edition.
Two options for you...
1. Since you are s-off already you can try to unlock bootloader without htcdev. check this link for instructions. After unlock you can flash latest TWRP here. You're still in LP firmware so latest Viper ROm will not work for you. You will need to flash MM dev edition firmware, dl here.. After flashing you can install the latest Viper Rom via TWRP.
2. You can find the MM RUU or ROm.zip here. Run RUU or flash Rom.zip. This will already upgrade your M9 to MM.
good luck!
Click to expand...
Click to collapse
Now it's saying that adb server is out of dare then says killing all I did was Uninstall adb and reinstall it yesterday

Please help my htc 10 is dead

I Tried to flash but always getting error partition failed. Stucked in boot loop. no recovery. only i can get fastboot. below is my getvar.
(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:FA64xxxxxxx
all:
finished. total time: 0.381s
htc_fastboot finished. total time: 0.738s
Press any key to continue . . .

What's your CID and latest ROM version? And what did you try to flash?

Dont know anything here... I dont know what was the ROM version at the time of root... now no information available... what can I do ...

When I try to flash anything via fastboot it says partion not exist
RUU also not working says battery is less than 30% but actually battery is full...

Does charging led turns green..
@Sneakyghost could help

cutecool said:
Does charging led turns green..
@Sneakyghost could help
Click to expand...
Click to collapse
no it doesnt... the battery icon comes up and then boot loop starts again...

Since you're in Qatar, you're probably on the 401 software. Did you get a software update in the last 2-3 weeks?
If not, download this: https://www.androidfilehost.com/?fid=24686681827312455
Relock your bootloader (fastboot oem lock), and flash this RUU (fastboot flash zip "name of zip").
If you got the recent update, then you're likely on 1.95, and you'll have to wait until there's an RUU, or take it to a service center.
This is as much help as I can give. Good luck.

I wouldn't lock the bootloader until you know your device fully boots.

Stephen said:
I wouldn't lock the bootloader until you know your device fully boots.
Click to expand...
Click to collapse
The 401 RUU zip won't flash on unlocked. This has been documented and I have gone through it myself. Do you have any alternate suggestions?
Why wouldn't you lock without a working system? My understanding is that unlocking via HTCdev would still be possible.

I tried dear but its not locking bootloader
here is the message
C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.257s
C:\Android\com>htc_fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.249s
C:\Android\com>

abidpioneer said:
I Tried to flash but always getting error partition failed. Stucked in boot loop. no recovery. only i can get fastboot. below is my getvar.
(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:FA64xxxxxxx
all:
finished. total time: 0.381s
htc_fastboot finished. total time: 0.738s
Press any key to continue . . .
Click to expand...
Click to collapse
You need to be in download mode then use the getvar all command. All fastboot commands are done in downlaod mode. How are you trying to flash RUU?

I am unable to use download mode..it says download mode failed in red

abidpioneer said:
I am unable to use download mode..it says download mode failed in red
Click to expand...
Click to collapse
You'll need a service center.

Yes. Service center. I don't think it's a brick since there's still a boot process but at this time I also wouldn't know how to force it to flash stuff, since it seems at least one vital partition is broken. So, call it a semi-brick with currently no way out...
Sorry that I can't offer any help here...

abidpioneer said:
I tried dear but its not locking bootloader
here is the message
C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.257s
C:\Android\com>htc_fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.249s
C:\Android\com>
Click to expand...
Click to collapse
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Sent from my HTC6545LVW using Tapatalk

I will check dear..thanks

dottat said:
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Click to expand...
Click to collapse
What is hosd.. ? Never heard about it...

I tried but its not working... i went to htc service centre they refused to do the job saying its modified they cannot do the job.. WTH is this at htc service centre...

abidpioneer said:
I tried but its not working... i went to htc service centre they refused to do the job saying its modified they cannot do the job.. WTH is this at htc service centre...
Click to expand...
Click to collapse
What happened? Did it flash successfully? Any errors?
Sent from my HTC6545LVW using Tapatalk

dottat said:
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Interesting facts there, mate. Thought you retired. Obviously I'm much more retired than you, considering I never knew HOSD is directly flashable like aboot...
Good to see you around!
(Besides, is it a true story that you retired? People were telling me that...)

Modify OTA zip to gain root access

Hello
My device is running on Marshmellow [arm64-v8a] with locked bootloader [i cant able to unlock due to getting unknown command error]
so today i found that OTA which can able to upgrade my marshmellow to android N
so i think if i somehow inject superuser apk in OTA/system/priv-app and then i update my phone using that modified OTA, will it work to gain full root access?
or should i something try another method to inject super user in ota.zip?
so how to do?
Thank you

tcpcd said:
Hello
My device is running on Marshmellow [arm64-v8a] with locked bootloader [i cant able to unlock due to getting unknown command error]
so today i found that OTA which can able to upgrade my marshmellow to android N
so i think if i somehow inject superuser apk in OTA/system/priv-app and then i update my phone using that modified OTA, will it work to gain full root access?
or should i something try another method to inject super user in ota.zip?
so how to do?
Thank you
Click to expand...
Click to collapse
Mostly likely not, bootloader is locked meaning you can only run verified images.
Let's see why you can't unlock the bootloader instead.
What steps have you done, etc.

Matt07211 said:
Mostly likely not, bootloader is locked meaning you can only run verified images.
Let's see why you can't unlock the bootloader instead.
What steps have you done, etc.
Click to expand...
Click to collapse
FIrst i enable usb debugging and oem unlocker in developer setting
then i enter 'adb reboot bootloader' to boot into bootloader
after i entered 'fastboot oem unlock' so i got an error that 'unknown command'
so i guess my device manufacture somehow changed unlocking code.
after googling i found that oem unlock code saved in aboot.img file [https://www.reddit.com/r/Android/comments/54wz8j/how_to_discover_hidden_fastboot_commands/]
therefore i try to grab aboot from /dev/block using dirtycow, but BIG FAILURE
so i thought maybe in OTA Chinese company always hide their backdoor. so what if i inject superuser in my OTA.zip.
EDIT:
File content in OTA.zip
Code:
+media
+app
+etc
+fake-libs
+fake-libs64
+fonts
+framework
+lib
+lib64
+bin
+nv
+presetapp
+priv-app
+tts
+usr
+vendor
+xbin
Description about my OTA [1.7gb]
- It can upgrade Marshmellow to Android N, by open recovery mode and choose OTA.zip file from mmc.
- It contain lots of system apk and device mfg apk.

tcpcd said:
FIrst i enable usb debugging and oem unlocker in developer setting
then i enter 'adb reboot bootloader' to boot into bootloader
after i entered 'fastboot oem unlock' so i got an error that 'unknown command'
so i guess my device manufacture somehow changed unlocking code.
after googling i found that oem unlock code saved in aboot.img file [https://www.reddit.com/r/Android/comments/54wz8j/how_to_discover_hidden_fastboot_commands/]
therefore i try to grab aboot from /dev/block using dirtycow, but BIG FAILURE
so i thought maybe in OTA Chinese company always hide their backdoor. so what if i inject superuser in my OTA.zip.
EDIT:
File content in OTA.zip
Description about my OTA [1.7gb]
- It can upgrade Marshmellow to Android N, by open recovery mode and choose OTA.zip file from mmc.
- It contain lots of system apk and device mfg apk.
Click to expand...
Click to collapse
What's your device model?
Have you tried searching for <device model> root?
No copy of aboot.img or bootloader etc name I'm a full firmware image?
Is your device the kinda of device where you need to request a unlock code from manufacturers website (I think it's Sony who does that, not sure who else).
Can you give me any more info to work with?

Matt07211 said:
What's your device model?
Have you tried searching for <device model> root?
No copy of aboot.img or bootloader etc name I'm a full firmware image?
Is your device the kinda of device where you need to request a unlock code from manufacturers website (I think it's Sony who does that, not sure who else).
Can you give me any more info to work with?
Click to expand...
Click to collapse
Model is Coolpad Note5
yes i searched everywhere to find root solution, even in official forum, but no success.
no my device dont need unlock code.
im sending you OTA.zip extracted link so you can see whats inside.

tcpcd said:
Model is Coolpad Note5
yes i searched everywhere to find root solution, even in official forum, but no success.
no my device dont need unlock code.
im sending you OTA.zip extracted link so you can see whats inside.
Click to expand...
Click to collapse
I'm wondering, is your device MediaTek based?

Matt07211 said:
I'm wondering, is your device MediaTek based?
Click to expand...
Click to collapse
no its qualcomm/snapdragon based

tcpcd said:
no its qualcomm/snapdragon based
Click to expand...
Click to collapse
Can you be specific?
What fastboot commands work and don't?

Matt07211 said:
Can you be specific?
What fastboot commands work and don't?
Click to expand...
Click to collapse
Code:
fastboot getvar all
^^work only this one
Code:
fastboot reboot
^^this is not woking even. just got output "reboot..." but fone actually not rebooting.
i tried fastboot oem unlock,unlock-go,flashing unlock << all Failed

tcpcd said:
^^work only this one
^^this is not woking even. just got output "reboot..." but fone actually not rebooting.
i tried fastboot oem unlock,unlock-go,flashing unlock << all Failed
Click to expand...
Click to collapse
Not even
Code:
fastboot boot boot.img
?
I've sadly never had a device with fastboot, so it ain't my area of expertise

Matt07211 said:
Not even
Code:
fastboot boot boot.img
?
I've sadly never had a device with fastboot, so it ain't my area of expertise
Click to expand...
Click to collapse
i think that command is working, but i didnt checked
i only checked oem commands with fastboot

tcpcd said:
Not even
i think that command is working, but i didnt checked
i only checked oem commands with fastboot
Click to expand...
Click to collapse
If you can boot custom boot.img then you can root it.
I personally rooted the xCover3 by modifying the boot.img

Matt07211 said:
If you can boot custom boot.img then you can root it.
I personally rooted the xCover3 by modifying the boot.img
Click to expand...
Click to collapse
no i cant boot custom images

tcpcd said:
no i cant boot custom images
Click to expand...
Click to collapse
Okay. Can you detail, EVERY method you've tried (any apps, fastboot commands Cave's (E.g. Dirty Cow) etc.) So we can get a clear overview and saves us both time as we are not going over the same stuff

Matt07211 said:
Okay. Can you detail, EVERY method you've tried (any apps, fastboot commands Cave's (E.g. Dirty Cow) etc.) So we can get a clear overview and saves us both time as we are not going over the same stuff
Click to expand...
Click to collapse
OKay
I tried Kingroot, kingoroot << Failed
Using dirtycow << Got success :cyclops: for temp root
Used farm-root to pull boot.img << termination after long wait
VIKIROOT << Working but not spawn shell
I only check fastboot oem commands but << failure
Code:
fastbooot oem unlock
fastbooot oem unlock-go
fastbooot oem unlock_go
fastbooot oem flashing unlock
fastbooot flashing unlock
fastbooot oemunlock
Output: FAILED (remote: unknown command)
Big 0
But one command work:
Code:
[stark]:~|$ fastboot getvar all
(bootloader) yl_udiskname:userdata
(bootloader) version:REFRESH_emmccid_new
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4199000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5a7bfbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x140000000
(bootloader) serialno:366da886
(bootloader) kernel:lk
(bootloader) product:MSM8952
all:
finished. total time: 0.022s

So I believe using dirtycow will probably be your chance at getting root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
Unless you figure out the correct fastboot commands

Matt07211 said:
So I believe using dirtycow will probably be your chance at getting root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
Unless you figure out the correct fastboot commands
Click to expand...
Click to collapse
Well dirtycow is only option for temp root

would this work on specific firmware, for example a combination firmware (factory binary on samsung) then install a custom recovery from there...?

tcpcd said:
Well dirtycow is only option for temp root
Click to expand...
Click to collapse
Well it's better then nothing, you can work Frkm there if roots such a bug deal for you

I think DC Unlocker Tool Maybe Work.

Bootloop + can't enter Download or Recovery mode

Hey,
my problem is that, after a reboot, my phone went into a bootloop.
I tried to enter the Recovery or the Download mode but it does not working.
After an automatic restart there is the bootloop again.
I can enter the Bootloader.
Official Software status
Unlocked
S-OFF
an interesting thing is that when i try to read my cid or mid with
fastboot getvar cid/mid
there is nothing to read out. It's empty.
Code:
c:\android>fastboot getvar cid
cid:
finished. total time: 0.036s
c:\android>fastboot getvar mid
mid:
finished. total time: 0.003s

domme0852 said:
Hey,
my problem is that, after a reboot, my phone went into a bootloop.
I tried to enter the Recovery or the Download mode but it does not working.
After an automatic restart there is the bootloop again.
I can enter the Bootloader.
Official Software status
Unlocked
S-OFF
an interesting thing is that when i try to read my cid or mid with
fastboot getvar cid/mid
there is nothing to read out. It's empty.
Click to expand...
Click to collapse
What is the output with fastboot getvar all?

Code:
(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: 0x61b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:xxxxxxxxxxxx
all:
finished. total time: 0.380s

Since you have access to the bootloader did you try entering recovery from the bootloader itself?...or try using: fastboot reboot recovery, or adb reboot recovery?

I basically have the same problem as you... except my phone is still bootloader locked and s-on. Have you tried putting a 2PS6IMG.zip file (ruu) on the root of a FAT32 formatted microSD card and see if you can access download mode that way?

chrisz5z said:
Since you have access to the bootloader did you try entering recovery from the bootloader itself?...or try using: fastboot reboot recovery, or adb reboot recovery?
Click to expand...
Click to collapse
I tried both. Via bootloader and fastboot command but nothing worked.
adb reboot recovery also doesn't work. There is no devices in adb mode.
Code:
c:\android>adb devices
List of devices attached
c:\android>
mang0 said:
I basically have the same problem as you... except my phone is still bootloader locked and s-on. Have you tried putting a 2PS6IMG.zip file (ruu) on the root of a FAT32 formatted microSD card and see if you can access download mode that way?
Click to expand...
Click to collapse
The download mode is, as I see it, completely bricked. There is no way to enter it.
Without an SDcard it should at least boot into it. But the device is going back to the bootloop.
To answer your question... no I don't try it

domme0852 said:
I tried both. Via bootloader and fastboot command but nothing worked.
adb reboot recovery also doesn't work. There is no devices in adb mode.
Code:
c:\android>adb devices
List of devices attached
c:\android>
The download mode is, as I see it, completely bricked. There is no way to enter it.
Without an SDcard it should at least boot into it. But the device is going back to the bootloop.
To answer your question... no I don't try it
Click to expand...
Click to collapse
You wouldn't be able to see much information via fastboot getvar all unless you were in download mode, so it's not really that strange.
Sometimes you can "trick" (I don't know if that's the correct word) the system into entering download mode from the above method.
At least, from this post and this post, that is what I gathered.

mang0 said:
Sometimes you can "trick" (I don't know if that's the correct word) the system into entering download mode from the above method.
At least, from this post and this post, that is what I gathered.
Click to expand...
Click to collapse
I tried the Method but the Phone still don't want to boot into download mode. It starts the bootloop like before.
I also tried to do an Update via the RUU.exe but this doesn't work too. The program stops with the error low battery although the phone was the whole night on the charger in bootloader. (Don't know if it does not charge right in this state)

Help I have the same problem

Its a simple fix. Take your phone back to carrier or HTC

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