HTC 10 - Bricked - HTC 10 Questions & Answers

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

Related

Brick?

Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
mtt_73 said:
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
Click to expand...
Click to collapse
im going to assume your phones is s-off?
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Thank you.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Click to expand...
Click to collapse
You can't install custom recovery with a (re)locked bootloader.
With s-off, you shouldn't ever relock the bootloader, as its no longer a requirement to RUU once s-off. But that's neither here nor there at this point, just info for future reference.
Any response to: fastboot devices
Make sure the phone is in fastboot mode.
Try to run the GPE RUU with phone in fastboot mode, to get the phone back up and running at least. Assuming you are still on the GPE CID and MID.
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Click to expand...
Click to collapse
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Hi guys,
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
1)flashing twrp via fastboot:
C:\adb>fastboot flash recovery C:\adb\openrecovery-twrp-2.8.5.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.438s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.500s
2) flashing stock recovery via fastboot( i dont know if i had the right one):
C:\adb>fastboot flash recovery C:\adb\recovery.img
target reported max download size of 1830727680 bytes
sending 'recovery' (14109 KB)...
OKAY [ 1.262s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.277s
3) 'booting' same stock recovery- what changed now are 3 android skaters for cca 0.2 sec when i try to enter recovery or start factory reset from bootloader, before it just went to fastboot usb mode.
C:\adb>fastboot boot recovery.img
creating boot image...
creating boot image - 14450688 bytes
downloading 'boot.img'...
OKAY [ 1.273s]
booting...
OKAY [ -0.000s]
finished. total time: 1.273s
Can please anyone help me? Thanks in advance
Here is data about the phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT.............8
(bootloader) imei: 35...........30
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
redpoint73 said:
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Click to expand...
Click to collapse
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Click to expand...
Click to collapse
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
mato123 said:
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
Click to expand...
Click to collapse
I would highly suggest not to post to another user's troubleshooting thread like this, as it doesn't look like the same problem at all (and in my experience rarely is, even when folks will post "I have the same issue"). You really should have just started your own thread, and would have been justified doing so IMO. Posting here just confuses matters for you, the OP and those trying to help.
But DON'T start another thread now (and add even more confusion). I'll ask the mods if they can move this post to its own thread.
ok, sorry
redpoint73 said:
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
Click to expand...
Click to collapse
Thanks for reply.
I went now in fastoob mode and tried to flash the RUU GPE again.
The error is:
macbooks-MacBook-Proownloads macbook$ ./fastboot-mac flash RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip
unknown partition 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
error: cannot determine image filename for 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
Just to clarify. I successfully when in GPE (with conversation). The problem was when going back to Sense. I do not know exactly what I did wrong.
My CID is 11111111
My MID is 0P6B10000
Really do not know how to proceed.
M
I unfortunately don't know jack about how to use fastboot and other actions on a Mac. I'm also not that familiar with running the RUU as a zip (I always do it on a PC with the RUU .exe).
But it looks like you just have the command syntax wrong. I think it should be:
fastboot oem rebootRUU
fastboot flash zip filename.zip
But it also look to me like nothing is actually "wrong" (aside from adb not working?). The phone not booting after relocking the bootloader is normal and intentional. You should just be able to run the desired Sense RUU, provided you have the right MID.
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
mtt_73 said:
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
Click to expand...
Click to collapse
hehe try watch this movie: https://www.youtube.com/watch?v=CCGj0rOuiR4
Most important is the firmware flash... so partition layout etc is changed to sense like after that you can flash sense roms etc. (for example viper rom as in video)
0kk0 said:
Most important is the firmware flash... so partition layout etc is changed to sense
Click to expand...
Click to collapse
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
redpoint73 said:
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
Click to expand...
Click to collapse
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Sent from my HTC One_M8 using xda Forum
mtt_73 said:
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Click to expand...
Click to collapse
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
redpoint73 said:
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
Click to expand...
Click to collapse
I did it. I am back to Sense now.
Any advice to remove tell HTC problem? I mean it says that I have a testing device. Is it because I am s-off? Should I go for s-on again? And how?
TY!

HTC m9 in bootloop after re-locking the bootloader

Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
unlock with fastboot
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
yotamh said:
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
Click to expand...
Click to collapse
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
yotamh said:
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
Click to expand...
Click to collapse
It seems like you're talking about the android version not the firmware version since there is no 5.0.XXX.X firmware for the M9. For now it might be the best solution to wait until you're home.
yotamh said:
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
Click to expand...
Click to collapse
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
LLegion said:
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
Click to expand...
Click to collapse
the problem is I can't unlock the bootloader. ADB devices doesn't work
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
yotamh said:
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
Click to expand...
Click to collapse
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in my google sheet (link can be found in my signature). Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Flippy498 said:
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in the google sheet in my signature. Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Click to expand...
Click to collapse
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
yotamh said:
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
Click to expand...
Click to collapse
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Flippy498 said:
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Click to expand...
Click to collapse
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
yotamh said:
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
Click to expand...
Click to collapse
yotamh said:
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
Click to expand...
Click to collapse
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Click to expand...
Click to collapse
Hi thanks for the top about the IMEI I've changed it.
and sorry, I didn't understood the the original comment and got in to the a wrong line in the comment. I'll try again with the correct file (2gb will take some to download). Again, thank you for your answer and patient. It's nice to see people try to help. :good:
THANK YOU so much! everything is working and even updated! thanks!
it seems i have a strange issue after all.
my phone doesn't detect my htc headphones. It recognize other headphone and the HTC headphones works with other devices.
it looks like a software issue.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. [REMOVED BECAUSE I'M A NEWBIE]I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature[/URL].
Click to expand...
Click to collapse
Hi I know this is probably old but I was in this exact same predicament and I had "tried everything" and your instructions brought my phone back to life!! I am so grateful after almost a week of adb commands and zip files that got me nowhere! THANK YOU SO MUCH!!!:good:

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.

My phone is probably bricked... possible suggestions?

So I was trying to get the Viper 4.3.1 to work. I installed newest twrp, flashed my rom but the home button doesn't work.
So I thought it was because I have the wrong firmware. I installed a new one, but everything starts going down.
Download mode now says failed to boot to download mode, just boots to bootloader when I choose to boot to recovery. Nothing is working.
I tried to download the RUU online, but even when i phone is fully charged, it says it is lower than 30%.
I tried to flash the newest recovery again, but boots me back to bootloader.
Try to simply reboot, boots me back to bootloader.
So any help would be appreciated. Thanks.
what i get after entering "fastboot 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
all:
finished. total time: 0.366s
Update:
Now I can't even turn it off. When I plug it into a power supply, it automatically turns to bootloader.
So basically I am stuck at bootloaer mode.
Seems to be a lot of firmware-related bricking going on. If you flash the wrong firmware in the wrong way kiss your phone goodbye.
.
Ryanchan97 said:
So I was trying to get the Viper 4.3.1 to work. I installed newest twrp, flashed my rom but the home button doesn't work.
So I thought it was because I have the wrong firmware. I installed a new one, but everything starts going down.
Download mode now says failed to boot to download mode, just boots to bootloader when I choose to boot to recovery. Nothing is working.
I tried to download the RUU online, but even when i phone is fully charged, it says it is lower than 30%.
I tried to flash the newest recovery again, but boots me back to bootloader.
Try to simply reboot, boots me back to bootloader.
So any help would be appreciated. Thanks.
what i get after entering "fastboot 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:FA68BBN00327
all:
finished. total time: 0.366s
Update:
Now I can't even turn it off. When I plug it into a power supply, it automatically turns to bootloader.
So basically I am stuck at bootloaer mode.
Click to expand...
Click to collapse
Did you try fastboot reboot? Nevermind. If you are in bootloader mode, leave it there. Get the ruu.exe file for your original phone. Nuke everything by running the ruu.exe on your computer. Original rom with the correct firmware will be installed. You will start over from scratch but at least you will have your phone back.
comstockload said:
Did you try fastboot reboot? Nevermind. If you are in bootloader mode, leave it there. Get the ruu.exe file for your original phone. Nuke everything by running the ruu.exe on your computer. Original rom with the correct firmware will be installed. You will start over from scratch but at least you will have your phone back.
Click to expand...
Click to collapse
Thanks for the suggestion. I am trying it right now, but it says my battery is lower than 30% so it doesnt let me run. I dont know how much battery it has but now i just have to let it charge for maybe an hour or so and see if it lets me do it.
This is probably the last and only solution to this.
Method of installing RUU? I always use and suggest SD-CARD. just curious. Sorry to read this.
andybones said:
Method of installing RUU? I always use and suggest SD-CARD. just curious. Sorry to read this.
Click to expand...
Click to collapse
I tried both through SD and through RUU.exe. Both don't work. So now I really don't have a clue on what to do....
Ryanchan97 said:
I tried both through SD and through RUU.exe. Both don't work. So now I really don't have a clue on what to do....
Click to expand...
Click to collapse
You may find help from someone much smarter than myself with this such as the sunshine team of Dottat. No idea if they can or will hell but the worst they can say is no. Just tossing out ideas.
Even if bricked, I'd hide your serial number. It's in post 1 & 3
Ryanchan97 said:
So I was trying to get the Viper 4.3.1 to work. I installed newest twrp, flashed my rom but the home button doesn't work.
So I thought it was because I have the wrong firmware. I installed a new one, but everything starts going down.
Download mode now says failed to boot to download mode, just boots to bootloader when I choose to boot to recovery. Nothing is working.
I tried to download the RUU online, but even when i phone is fully charged, it says it is lower than 30%.
I tried to flash the newest recovery again, but boots me back to bootloader.
Try to simply reboot, boots me back to bootloader.
So any help would be appreciated. Thanks.
what i get after entering "fastboot 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
all:
finished. total time: 0.366s
Update:
Now I can't even turn it off. When I plug it into a power supply, it automatically turns to bootloader.
So basically I am stuck at bootloaer mode.
Click to expand...
Click to collapse
I can fix this....Wanna do a TeamViewer session at some point?
Sent from my HTC6545LVW using Tapatalk
Sorry i am not too familiar with tech. How doed Team View work?
dottat said:
I can fix this....Wanna do a TeamViewer session at some point?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Is it okay if you give me a breif instruction on how to do it? I dont usually have time during the day sorry. But thank you for the offer!
Ryanchan97 said:
Is it okay if you give me a breif instruction on how to do it? I dont usually have time during the day sorry. But thank you for the offer!
Click to expand...
Click to collapse
Your issue is mismatched firmware. Extract the lastest ruu and flash each IMG by name manually in bootloader. When done you should have your phone back. If you still have an issue tonight lemme know. This same symptom goes back to the HTC m9 days.
dottat said:
Your issue is mismatched firmware. Extract the lastest ruu and flash each IMG by name manually in bootloader. When done you should have your phone back. If you still have an issue tonight lemme know. This same symptom goes back to the HTC m9 days.
Click to expand...
Click to collapse
So will the command be "fastboot flash recovery filename"?
Or is there a specific one for img files?
Ryanchan97 said:
So will the command be "fastboot flash recovery filename"?
Or is there a specific one for img files?
Click to expand...
Click to collapse
the phone can be turned off from pretty much anywhere by holding down vol- and power. the touch lights will flash about 15 times and the shut off.
secondly, I havnt seen any mention or ask if you are s-off or not. of you are s-on, it is virtually impossible to permanently brick. because from bootloader/download a recovery can be flashed and from there, custom ROM etc.
unless you've altered your cid or mid, it is usually not possible to flash just any old RUU.
Ryanchan97 said:
So will the command be "fastboot flash recovery filename"?
Or is there a specific one for img files?
Click to expand...
Click to collapse
Use the default name of the image. If radio use radio.
Sent from my HTC6545LVW using Tapatalk
dottat said:
Use the default name of the image. If radio use radio.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
So I tried to do that just now. But the phone doesn't even turn on now. Like I clicked reboot but now it is just a black screen with nothing. I tried volume down + power button but doesn't seem to work. Doesnt even seem to be charging also. I am going to let to charge for the night and see if it works.
silegeek said:
the phone can be turned off from pretty much anywhere by holding down vol- and power. the touch lights will flash about 15 times and the shut off.
secondly, I havnt seen any mention or ask if you are s-off or not. of you are s-on, it is virtually impossible to permanently brick. because from bootloader/download a recovery can be flashed and from there, custom ROM etc.
unless you've altered your cid or mid, it is usually not possible to flash just any old RUU.
Click to expand...
Click to collapse
Sorry I forgot to mention. It is s-off. And i also changed the CID to 11111111. But if i do getvar all, it doesnt show what cid i have. I am assuming this has something to do with the broken firmware also. Any suggestions? Thanks!
Ryanchan97 said:
Sorry I forgot to mention. It is s-off. And i also changed the CID to 11111111. But if i do getvar all, it doesnt show what cid i have. I am assuming this has something to do with the broken firmware also. Any suggestions? Thanks!
Click to expand...
Click to collapse
if you tried "fastboot getvar cid" and its blank then I would say yes something might be wrong. in my experience "getvar all" doesn't always show all the information. and when I was super cid, it came up blank. but "getvar cid" usually worked. but since being HTC__001 (WWE) it's always shown up regardless of method.
you can usually flash an appropriate RUU by altering either your cid or mid. for instance I was able to successfully install the US Nougat RUU by changing my cid to BS_US001 and my mid to 2PS650000. Afterwards I changed back to HTC__001 and 2PS620000
i would not recommend flashing 2PSIMG.zip from the SD card unless you are totally sure it is suitable for your phone, and even then, check again. if it gives you warnings, pay attention to what they are.
have you tried flashing the RUU manually? by using a 2PS6img.zip file? it will run in recovery on your phone automatically when you have it on there. I had trouble flashing RUUs before on my 10, had to relock the bootloader and manually install a stock img.
kazuki1 said:
have you tried flashing the RUU manually? by using a 2PS6img.zip file? it will run in recovery on your phone automatically when you have it on there. I had trouble flashing RUUs before on my 10, had to relock the bootloader and manually install a stock img.
Click to expand...
Click to collapse
All sorts of wrong advice there. No need to relock on this device. Also, the ruu will not run in recovery.
Sent from my HTC6545LVW using Tapatalk
dottat said:
All sorts of wrong advice there. No need to relock on this device. Also, the ruu will not run in recovery.
Click to expand...
Click to collapse
Meant download mode not recovery sorry. And I actually had to relock my device, but tysm.

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

Categories

Resources