Develop Bugs

Can't access custom recovery

My goal: Get CM 11 on my One X
What I've done so far: (using simplified filenames)
Unlocked bootloader via HTCdev
adb push cm11.zip /sdcard/
adb push gapp.zip /sdcard/
adb reboot bootloader
fastboot flash recovery clockwork.img
disconnect USB
selected "Recovery" from HBOOT menu.
Result: Stuck on white screen with HTC logo when accessing recovery.
(I can boot into stock ROM and use the phone, but not access custom recovery)
Might or might not be relevant:
I flashed boot.img from CDM11.zip first, that caused the device to hang at normal boot as well.
After quite a lot of googling, I found what I believe is the correct boot.img for my device, as it boots normally now (as long as I don't try to boot recovery)
If I flash (what I believe to be) stock recovery, I get the black screen with a red triangle on it.
Results from fastboot getvar all:
Code:
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 3.1204.171.33
version-cpld: None
version-microp: None
version-main: 2.18.401.2
serialno: FA2Cxxxxxxxx
imei: 3535670xxxxxx
product: enrc2b_u
platform: HBOOT-T30S
modelid: PM3511000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4101mV
devpower: 82
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
So, I think I've done enough searching to say that not many people have this exact problem.
Care to help me out by nudging me in the right direction?

Flash this recovery
https://www.dropbox.com/s/7zxfzbwewzq6hmq/twrp-recovery2.img
And also do the command after flashing :
Fastboot erase cache
Then try to enter it again.

Mr Hofs said:
Flash this recovery
https://www.dropbox.com/s/7zxfzbwewzq6hmq/twrp-recovery2.img
And also do the command after flashing :
Fastboot erase cache
Then try to enter it again.
Click to expand...
Click to collapse
Same result...
And I'm sorry that I didn't mention it earlier; I have tried a few different versions of CWM and TWRP all without success.
And now that I see the command, I also remember trying that one as well.
But for the record;
Code:
adb reboot bootloader
fastboot flash recovery OneX\twrp-recovery2.img
fastboot erase cache
disconnected USB
selected HBOOT
selected Recovery
Stuck on white screen with green HTC logo.

Rename the recovery name to just recovery.img and try
Fastboot flash recovery recovery.img
Fastboot erase cache
And make sure to use the original HTC usb cable and a 2.0 usb port (directly ....not via any hub or extension chord)

Mr Hofs said:
Rename the recovery name to just recovery.img and try
Fastboot flash recovery recovery.img
Fastboot erase cache
And make sure to use the original HTC usb cable and a 2.0 usb port (directly ....not via any hub or extension chord)
Click to expand...
Click to collapse
Still stuck on white screen with HTC logo when trying to access Recovery.

Ah CRAP !!!!!!! you have the HOX +......STOP flashing stuff from here immediately !!!!
Get the recoveries and roms from the hox+ section asap. That will help you

Mr Hofs said:
Ah CRAP !!!!!!! you have the HOX +......STOP flashing stuff from here immediately !!!!
Get the recoveries and roms from the hox+ section asap. That will help you
Click to expand...
Click to collapse
Holy crap! You're right!
When I look at the "About" section; it's a One X+ !
Good thing I didn't get the recovery in then, because then I'd be flashing ROMS in a minute!
THANKS for noticing!

Yeah just rechecked the posts, i firstly stopped reading at the hboot of 1.72 sorry ....should have seen it faster than this !

hit a roadblock while trying to revert my 816 to stock. please help.

Hi guys.
I rooted my 816 using CWM and SuperSU months ago. Now, there's an OTA update to Android 6.0 which will hopefully render the usefulness of root obsolete, as I mostly need it for link2sd (they also cite better RAM management as a new feature, which should get rid of the horrible lag on Lollipop).
I know I have to go back to full stock, and I read a simple guide somewhere, and I thought, why don't I give it a crack. So, it said I should just "fastboot oem lock" the phone and flash the correct .zip RUU. After much trouble with connectivity and driver issues between my computer (adb server is out of date. killing...; device offline; errors etc.) I FINALLY (after hours of troubleshooting) managed to go into fastboot via USB and lock the bootloader. Great. But, when I tried to flash the .zip, it just says waiting for device, indefinitely. Tried to go into recovery via the power buttons on the phone, but it shows an error and simply refuses to. As a sidenote, root still works, but the phone displays this in fastboot: Relocked, Security Warning.
Basically, I'm afraid to proceed because I think I'm on the wrong track, and could end up f'ing up my device altogether. I'm from Croatia so I downloaded the 5.0.1 EU version .zip from here: (can't post link, just search htcdev downloads, it's the first one).
I hate opening new threads because I'm sure someone has already had the problems I'm having, but I just can't keep searching the web for hours on end trying to find a solution. Forgive me for this guys, and please help a poor noob in need if you can.

Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.

nukaru said:
Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.
Click to expand...
Click to collapse
Oh great, you're from Germany, so you have an EU 816 too. It's an a5ul just like yours. I'll send the full info text as soon as i install SDK tools completely.
I noticed that in your guide you first flash the stock ROM, and only then lock the bootloader. In the guide I found it said to first lock the bootloader, and then flash the stock ROM. So right now, I have a locked bootloader and CWM recovery I can't get into. Is this going to be a problem?

No, you first flash the stock recovery, then relock bootloader. And if your flashed recovery works you flash the RUU.

running fastboot devices does literally nothing, just sends me to the next line.
running adb devices, on the other hand, lists my device.
great, so I messed up there. do you know how I can fix it?

Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.

nukaru said:
Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.
Click to expand...
Click to collapse
I managed to get the getvar command to work: here's the info
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.111011.20.0123
(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: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(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: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s

The files from my guide should work with your device.

so it doesn't matter that my bootloader is now locked? I can just follow your guide and it should work?

Have you flashed stock recovery BEFORE locking bootloader? You have to install stock recovery or the RUU won't flash. It's all in the guide.

No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?

edofot said:
No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?
Click to expand...
Click to collapse
Did you type this before flashing the RUU?
Code:
fastboot oem rebootRUU

Nope. I tried to flash the RUU with fastboot flash ... .zip but it just said: waiting for device; and nothing happened. So I'll try the rebootRUU command when I get home from classes.

You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.

nukaru said:
You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.
Click to expand...
Click to collapse
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?

edofot said:
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?
Click to expand...
Click to collapse
Use this HTC mini-SDK

Gibz97 said:
Use this HTC mini-SDK
Click to expand...
Click to collapse
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)

edofot said:
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)
Click to expand...
Click to collapse
First type this. It will reboot phone into a black screen with a silver HTC logo:
Code:
fastboot oem rebootRUU
then type:
Code:
fastboot erase cache
then type:
Code:
fastboot flash zip 0P9CIMG.zip

Sorry, I was looking for an sd-card adapter, I wasn't here.
Update: Moved the 09PCIMG.zip to the sd-card successfully this time and am flashing the img now from sd-card! Seems to be going well so far.

Success
Finally! Did it, works like a charm.
I'm still amazed by how fast the phone really is when it's stock.
Viele Dank, @nukaru, du wärst eine sehr grosse hilfe. Wenn du nach Kroatien kommst, melde mich an, du hast ein Bier und/oder Kaffe von mich (at least I tried, even without google translate)
Thank you too @Gibz97, really appreciate the effort.
If anyone reading this has the same questions I had, just follow nukaru's guide, it has all you need to know. If you have an A5_UL, it's gonna 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 One M8 stuck in fastboot screen since loading CWM Recovery Image

Hi, I attempted to root my phone for the first time following these instructions, which have the HTCDev.com unlocking bootloader instructions as part of them.
Output of "fastboot getvar all" is below
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0​
I did make a mistake, I loaded both the below images in the given order.
openrecovery-twrp-2.7.0.2-m8.img
philz_touch_6.26.6-m8.img
When I went into recovery I got philz touch and loaded the UPDATE-SuperSU-v2.37.zip that was instructed. However I am got stuck in permanent reboot.
I followed the instructions in this thread up until post #6, but I don't understand how to "reflash my custom recovery". I am currently on the fasboot screen after having successfully run "fastboot flash zip firmware-2.22.531.5.zip".
Is this removing the philz touch image? How is this done?
Or more what I'm after, how do I get to a rooted phone from here which is usable?
Thank you in advance for any help given!

The chosen SuperSu is way too old. I never used Philz Touch but even TWRP you loaded is way too old as well.
Flash the latest TWRP and the latest SuperSu or magisk and you're good to go.
And please remove your imei and serial no.

maultasche said:
The chosen SuperSu is way too old. I never used Philz Touch but even TWRP you loaded is way too old as well.
Flash the latest TWRP and the latest SuperSu or magisk and you're good to go.
And please remove your imei and serial no.
Click to expand...
Click to collapse
Many thanks!
Can I just clarify what flashing the latest TWRP and the latest SuperSU means? I'm running on windows, which fastboot instruction(s) in cmd do I need to run? (Sorry, I am very new to this.)

MonkeyBrains7532 said:
I followed the instructions in this thread up until post #6, but I don't understand how to "reflash my custom recovery". I am currently on the fasboot screen after having successfully run "fastboot flash zip firmware-2.22.531.5.zip".
Click to expand...
Click to collapse
Hold on, I missed this part. Why would you even flash this zip? I don't even know what that is. I'm not even sure this zip was intended for your phone. Flashing zips which are not for your device model could brick the phone.
The latest TWRP can be found here:
https://dl.twrp.me/m8/
Latest SuperSu:
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

maultasche said:
Hold on, I missed this part. Why would you even flash this zip? I don't even know what that is. I'm not even sure this zip was intended for your phone
Click to expand...
Click to collapse
I thought it was resetting firware... Is there a way to remove this? "flashboot flash zip <some_correct_firmware>"?
Check out the link to the other thread, as I did (niavely) follow the instructions given.

MonkeyBrains7532 said:
I thought it was resetting firware... Is there a way to remove this? "flashboot flash zip <some_correct_firmware>"?
Check out the link to the other thread, as I did (niavely) follow the instructions given.
Click to expand...
Click to collapse
I did. Your phone is an orange one, you flashed old firmware which was meant for a t-mobile phone. Flashing random zips which are not meant for your phone could brick the device.

maultasche said:
I did. Your phone is an orange one, you flashed old firmware which was meant for a t-mobile phone. Flashing random zips which are not meant for your phone could brick the device.
Click to expand...
Click to collapse
Right, okay... Assuming it's not beyond all hope, would flashing the correct firmware possibly resolve this?
If so, where would I need to go to get the latest correct firmware for my carrier?
I can see some options on the HTC website ROM downloads, but nothing for Orange. I thought I was T-Mobile as I got the phone from EE...

MonkeyBrains7532 said:
Right, okay... Assuming it's not beyond all hope, would flashing the correct firmware possibly resolve this?
If so, where would I need to go to get the latest correct firmware for my carrier?
I can see some options on the HTC website ROM downloads, but nothing for Orange. I thought I was T-Mobile as I got the phone from EE...
Click to expand...
Click to collapse
The site only posts RUU for US phones.
Is the phone really in a bootloop or just stuck at the boot screen?
There is hope for you. Since you want to root as well we'll go this way:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Download the TWRP backup from post #3. It's the first one there for your device. After you downloaded the backup, flash the latest TWRP which I linked earlier. Boot into TWRP and restore the backup. If the phone is not booting then follow instructions in post #5 to flash firmware.
But before you go and restore a backup try to flash firmware as mentioned in post #5. You need to relock bootloader though.

maultasche said:
The site only posts RUU for US phones.
Is the phone really in a bootloop or just stuck at the boot screen?
There is hope for you. Since you want to root as well we'll go this way:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Download the TWRP backup from post #3. It's the first one there for your device. After you downloaded the backup, flash the latest TWRP which I linked earlier. Boot into TWRP and restore the backup. If the phone is not booting then follow instructions in post #5 to flash firmware
Click to expand...
Click to collapse
It was originally just on the White with green "HTC" text boot screen. I'm now in fastboot.
So I have downloaded the following.
SuperSU-v2.82-201705271822.zip
twrp-3.1.1-0-m8.img
I also downloaded the below (on the mega-nz.com link).
hboot 3.19.0000 - 6.xx.xxx.x (Marshmallow)
CID ORANG001
MID 0P6B10000
6.12.61.4​
as well as the below from post #5
CID ORANG001
MID 0P6B10000
fw_6.12.61.4​
I attempted to flash the TWRP, but got "'flashboot' is not recognized as an internal or external command". I am still in the directory where I downloaded flashboot and this is a new error..
I then started on the instructions in post #5, all the way up to "fastboot flash zip fw_6.12.61.4.zip" but I get the same "...not recognized..." error. My phone is now on a screen similar to fastboot, but there is just the one option, "RUU". It was on a black screen with "HTC" in the middle a moment ago when I was trying to flash the zip.

@MonkeyBrains7532
What do you mean with flashboot? Or is this just a typo? There is no flashboot command. The basic idea is:
fastboot flash recovery NameOfRecovery.img
You can also only boot into TWRP with fastboot boot NameOfRecovery.img
If you want to try to flash only the firmware first you need to lock bootloader first. I'm not quite sure if you should be on stock recovery for that. You can flash that one as well with the mentioned command

maultasche said:
@MonkeyBrains7532
What do you mean with flashboot? Or is this just a typo? There is no flashboot command. The basic idea is:
fastboot flash recovery NameOfRecovery.img
You can also only boot into TWRP with fastboot boot NameOfRecovery.img
If you want to try to flash only the firmware first you need to lock bootloader first. I'm not quite sure if you should be on stock recovery for that. You can flash that one as well with the mentioned command
Click to expand...
Click to collapse
Oh lord that was a typo, okay starting the instructions again. Sorry for the dumb mistake.

MonkeyBrains7532 said:
Oh lord that was a typo, okay starting the instructions again. Sorry for the dumb mistake.
Click to expand...
Click to collapse
Don't worry. I've been through the same once

maultasche said:
Don't worry. I've been through the same once
Click to expand...
Click to collapse
Thanks
So I continued off where I left, firstly by putting the phone in flashboot mode then repeating step 4 on post #5.
However, when I ran "fastboot oem rebootRUU" in cmd it just sat on "<waiting for device>" until I killed the command.
Is this just a question of leave it alone for a little while?

MonkeyBrains7532 said:
Thanks
So I continued off where I left, firstly by putting the phone in flashboot mode then repeating step 4 on post #5.
However, when I ran "fastboot oem rebootRUU" in cmd it just sat on "<waiting for device>" until I killed the command.
Is this just a question of leave it alone for a little while?
Click to expand...
Click to collapse
Was USB debugging enabled on your phone? Seems like it wasn't. Does it say in hboot fastboot USB?

maultasche said:
Was USB debugging enabled on your phone? Seems like it wasn't. Does it say in hboot fastboot USB?
Click to expand...
Click to collapse
I thought I had when I first got into the dev options, I may well be misremembering. It just says hboot fastboot...

MonkeyBrains7532 said:
I thought I had when I first got into the dev options, I may well be misremembering. It just says hboot fastboot...
Click to expand...
Click to collapse
Well then it's not working. It either should say fastboot USB or fastboot AC. It's been a while as I've done that, so I'm not 100% sure what it should say. So you need to go the route with twrp backup instead. Can you at least flash or boot twrp?

maultasche said:
Well then it's not working. It either should say fastboot USB or fastboot AC. It's been a while as I've done that, so I'm not 100% sure what it should say. So you need to go the route with twrp backup instead. Can you at least flash or boot twrp?
Click to expand...
Click to collapse
I am getting "waiting for device" when I run either "fastboot boot twrp-3.1.1-0-m8.img" or "fastboot flash recovery twrp-3.1.1-0-m8.img".

MonkeyBrains7532 said:
I am getting "waiting for device" when I run either "fastboot boot twrp-3.1.1-0-m8.img" or "fastboot flash recovery twrp-3.1.1-0-m8.img".
Click to expand...
Click to collapse
Do you have philztouch still on your phone?

maultasche said:
Do you have philztouch still on your phone?
Click to expand...
Click to collapse
I should do. Next step, go to recovery?
Fyi, I scrolled down in Fastboot and the menu name changed to Fastboot USB. Tried booting and flashing again, but still waiting for device. I don't know if this new information changes anything.

MonkeyBrains7532 said:
I should do. Next step, go to recovery?
Fyi, I scrolled down in Fastboot and the menu name changed to Fastboot USB. Tried booting and flashing again, but still waiting for device. I don't know if this new information changes anything.
Click to expand...
Click to collapse
Yes, boot into Philz and try to find out if the recovery can flash .img files
Never used it so I don't know :/

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