Develop Bugs

Phone Stuck

All of a sudden my phone hang up.
I booted into the stock recovery - factory reseted and everything and then this happened:
The optimizing started like when I made a wipe and data reset through recovery. xxx out of 164
but as soon as it finished I got the same problem as before:
"Android is starting.. starting apps"
and there it gets stuck
So I unlocked the phone, installed custom recovery and ROM, tried 3 different ones but still get the same issue. What might be the problem?! what can I do... I really dont know what else to do... :/

Do fastboot getvar all, and post the results (delete IMEI and serial number).
What ROMs did you try (and what version numbers)?

redpoint73 said:
Do fastboot getvar all, and post the results (delete IMEI and serial number).
What ROMs did you try (and what version numbers)?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT444******
(bootloader) imei: 358718**********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.018s
I tried the
Venom Viper (which is my favorite on the HTCs)
Android Revolution HD
Maximus HD
all the latest versions!
TWRP have the latest v3 installed too!

Did you wipe data, cache and Dalvik (this is the "default" wipe option in TWRP) before flashing the ROMs?
If so, I can't see anything that is obviously wrong. You might consider running the 6.12.1540 RUU to start from a completely "clean" baseline image, and see if the problem persists. Be aware, RUU will wipe the phone.

redpoint73 said:
Did you wipe data, cache and Dalvik (this is the "default" wipe option in TWRP) before flashing the ROMs?
If so, I can't see anything that is obviously wrong. You might consider running the 6.12.1540 RUU to start from a completely "clean" baseline image, and see if the problem persists. Be aware, RUU will wipe the phone.
Click to expand...
Click to collapse
I have done that 100 times... this crap doesnt boot at all... flashed the stock RUU multiple times! and of course multiple times clean the cache and internal data etc etc... it just wont start... :/
the only thing I didnt do is unlocking the CID... but I dont think this is that important?!

greek_lover_69 said:
I have done that 100 times... this crap doesnt boot at all... flashed the stock RUU multiple times! and of course multiple times clean the cache and internal data etc etc... it just wont start... :/
Click to expand...
Click to collapse
The response makes it sound like you are mad for me asking?
We can't know what you did, if you don't tell us. We aren't mind readers. And what may seem like an obvious thing to you, is a common mistake by many others.
Additionally, the simple answer is often (while not always) the correct one.
greek_lover_69 said:
the only thing I didnt do is unlocking the CID... but I dont think this is that important?!
Click to expand...
Click to collapse
You mean changing the CID? No, I don't see why that would make a difference.
If you've successfully installed the RUU, and the issue persists, I tend to believe this is a random hardware failure (such as emmc going bad). This theory would also explain why this happened "all of a sudden".

redpoint73 said:
The response makes it sound like you are mad for me asking?
We can't know what you did, if you don't tell us. We aren't mind readers. And what may seem like an obvious thing to you, is a common mistake by many others.
Additionally, the simple answer is often (while not always) the correct one.
You mean changing the CID? No, I don't see why that would make a difference.
If you've successfully installed the RUU, and the issue persists, I tend to believe this is a random hardware failure (such as emmc going bad). This theory would also explain why this happened "all of a sudden".
Click to expand...
Click to collapse
no no sorry.. why should I be mad at you.. you are just trying to help... I^m mad at my PHONE!
i^m guessing hardware failure too... can explain it else..
thanks! will have to sent it back.
I bought it from china.. maybe it had a problem and was fixed or something..

greek_lover_69 said:
no no sorry.. why should I be mad at you.. you are just trying to help... I^m mad at my PHONE!
Click to expand...
Click to collapse
No worries. I thought that might be the case (frustrated at the phone) which is why I posed it as a question. You'd be surprised at what folks here can sometimes take as an insult.
In any case, good luck and sorry we couldn't do more to help.

Soft bricked with S-On

I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.

R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.

xunholyx said:
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.
Click to expand...
Click to collapse
I tried that, but it doesn't flash the ROM. Instead it starts flashing and then restarts back into TWRP midway. I tried flashing superuser the same way but to no avail.

You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.

R3dact said:
I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On
Click to expand...
Click to collapse
Are you sure it was ever s-off? S-off isn't need to flash ROMs, root, or a great many other things.
The only way you could have gotten s-off is with the sunshine app ($25); unless you did s-off with firewater before that method was disabled in Dec 2014.
R3dact said:
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Click to expand...
Click to collapse
There is rarely ever a reason to go into the Advanced section. But if you do, its called "Advanced" for a reason. You shouldn't be wiping any partitions on this device without understanding what it means, and what the results will be.
R3dact said:
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part)
Click to expand...
Click to collapse
If you haven't installed a new TWRP version in a year, there is no way its the "latest".
There is also no reason to guess at this. It says the TWRP version number right on the main screen of TWRP. You're always better of giving the specific number, instead of just saying latest. Folks on here often post they have the "latest" TWRP. But once prompted for the actual version number, I often find its something very old, often 2 years old!

R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Can you plz post fastboot getvar all here without the imei or serial#. We may be able to find you an RUU that may be able to recover your device.
Sent from my Nook HD using XDA Labs

ckpv5 said:
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
Click to expand...
Click to collapse
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================

smub said:
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================
Click to expand...
Click to collapse
Jesus. 1.54.651.8 OS? That phone has never been updated since forever.
Go to this thread for instructions and links to update your device.
You want the ones that aren't "Harman"
EDIT: You are S-Off, so keep that in mind (security: off from your getvar)
Feel free to send me a PM if you need further instructions.

Htc one m8 not booting into Os

i had installed (TWRP by chr0247 v2.8.0.3). then i installed new Os. but it always boots into bootloader. when i click mount button on recovery mode, the system partition is unticked. Is this a reason for my problem? i tried marking it(mounting) and rebooted my devices but still same problem. again it boots to bootloader, system is shown unmounted on mount option on opening recovery. my device is bricked and i am stuck since very long time. Plz any help would be greatly appreciated. bootloader is unlocked !

bhuwanpandey999 said:
i had installed (TWRP by chr0247 v2.8.0.3). then i installed new Os.
Click to expand...
Click to collapse
Where did you get that version TWRP? I don't recognize the user/source chr0247
Describe the source location, or obfuscate the link with some extra character (as I see you don't have enough posts to post a link).
Which ROM did you try to install?
That TWRP version is a bit old. I just have a feeling you have used wrong or old TWRP; or mismatched ROM vs. firmware, and the condition is probably recoverable.
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
Where did you get that version TWRP? I don't recognize the user/source chr0247
Describe the source location, or obfuscate the link with some extra character (as I see you don't have enough posts to post a link).
Which ROM did you try to install?
That TWRP version is a bit old. I just have a feeling you have used wrong or old TWRP; or mismatched ROM vs. firmware, and the condition is probably recoverable.
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
C:\Users\Karthik\AppData\Local\Android\Sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311691.15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.03.720.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA4A2Y900311
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: mels_tuhl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B90000
(bootloader) cidnum: HTC__038
(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: 4d1016cf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
help me out mate, please.

Pokémon_.rayquaza said:
help me out mate, please.
Click to expand...
Click to collapse
Help you out with what exactly? I assume you have the same/similar problem as the (old) thread title: not booting to OS. But it would be nice if you gave a description of how you got to this point, if you have TWRP (like the OP does) and unlocked bootloader or not. Getvar data is really useful, but usually not enough info by itself to describe the problem.
You have the M8eye. Not a lot of folks on this forum have that variant, and not a lot of resources for it. If you have unlocked bootloader and TWRP, you can try to restore one of the stock TWRP backups (has to be one for the "eye" specifically). Although the only one uploaded for your CID is 1.80.720.1. So I don't personally know if they higher version number backup will work or not.
---------- Post added at 01:51 PM ---------- Previous post was at 01:40 PM ----------
You can try the RUU posted on the following webpage (Post #10): http://forum.gsmdevelopers.com/showthread.php?t=34990&p=156198&viewfull=1#post156198
Can't personally vouch for this, and I don't normally like to link random websites outside xda. But one user at least appeared to have success with it.

It's the same one as the above guys

Pokémon_.rayquaza said:
It's the same one as the above guys
Click to expand...
Click to collapse
I asked for a detailed description of how you got to this point, plus if you have TWRP and unlocked bootloader. And you respond with a single sentence?
"I have the same problem" isn't an appropriate description of your issue, if you want proper help.
You have TWRP 2.8.0.3 and tried to install a ROM? Since that is what the "above guy" did. Unless your problem is exactly the same (and trust me, it never is!) you need to provide specific information.

Yeah, sorry. To be honest it's my cousin's phone and he gave it to me to fix. Yes, it has TWRP 2.8.0.3 and I don't think it has a ton installed in it, coz whenever I try to switch it on, it just shows HTC in the blank white screen and it's stuck like that until the battery dies. If I open it in recovery mode it takes me to some TWRP bootloader.

Pokémon_.rayquaza said:
Yeah, sorry. To be honest it's my cousin's phone and he gave it to me to fix.
Click to expand...
Click to collapse
Even so, I don't see why you can't ask your cousin what he did, tried to do, etc. It's in his interest if he wants the phone fixed, to give you the info.
Might be something as simple as flashing the right version SuperSU (botched root attempt).

HTC M8s Stuck between Bootloader and Stock Recovery

I wonder I anyone can point me in a right direction ?
After Factory Reset phone went into White HTC Screen and stopped. I'm only able to access Bootloader and Stock Recovery now. There is no OS.
OS.1.21.401.1
HTC___001
HBOOT 3.19.0.0000
S-ON
LOCKED
Software Status: Official
I tried to Unlock bootloader. I used Hasoon's tool. I confirmed YES to unload bootloader. But after restart Bootloader is still locked.
I tried to flash boot.img and recovery.img but all FAILS.
I can access the phone via ADB but anything flashing always fails. Tried sideload via ADB in Phone's recovery. But always Fails.
I can't access SD via Recovery, says E: mount fail. Tried to re-format the SD but no result
To me it seems like bootloader is corrupt and seems that without proper hardware I won't be able to do anything...
I spen many hours now and about to give up. Please let me know if I missed anything before I will, sadly, have to try professionals.
Many thanks to everyone.
Vash

panagath said:
Hello, thanks for the reply. What I see are the following:
LOCKED
HBOOT - 3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.61.4
Click to expand...
Click to collapse
Did you find solution/fix pls ?
I seem to have similar problem.
After Factory Reset phone went into White HTC Screen and stopped. I'm only able to access Bootloader and Stock Recovery now. There is no OS.
OS.1.21.401.1
HTC___001
HBOOT 3.19.0.0000
S-ON
LOCKED
Software Status: Official
I tried to Unlock bootloader. I used Hasoon's tool. I confirmed YES to unload bootloader. But after restart Bootloader is still locked.
I tried to flash boot.img and recovery.img but all FAILS.
I can access the phone via ADB but anything flashing always fails. Tried sideload via ADB in Phone's recovery. But always Fails.
I can't access SD via Recovery, says E: mount fail. Tried to re-format the SD but no result
To me it seems like bootloader is corrupt and seems that without proper hardware I won't be able to do anything...
I spent many hours now and about to give up. Please let me know if I missed anything before I will, sadly, have to try professionals.
Vash

vagon1 said:
Did you find solution/fix pls ?
I seem to have similar problem.
After Factory Reset phone went into White HTC Screen and stopped. I'm only able to access Bootloader and Stock Recovery now. There is no OS.
OS.1.21.401.1
HTC___001
HBOOT 3.19.0.0000
S-ON
LOCKED
Software Status: Official
I tried to Unlock bootloader. I used Hasoon's tool. I confirmed YES to unload bootloader. But after restart Bootloader is still locked.
I tried to flash boot.img and recovery.img but all FAILS.
I can access the phone via ADB but anything flashing always fails. Tried sideload via ADB in Phone's recovery. But always Fails.
I can't access SD via Recovery, says E: mount fail. Tried to re-format the SD but no result
To me it seems like bootloader is corrupt and seems that without proper hardware I won't be able to do anything...
I spent many hours now and about to give up. Please let me know if I missed anything before I will, sadly, have to try professionals.
Vash
Click to expand...
Click to collapse
Your device is not regular M8, it's htc M8s.
You can try to RUU - https://forum.xda-developers.com/showpost.php?p=70306458&postcount=2
Anything ask here not in M8 section - https://forum.xda-developers.com/htc-one-m8/one-m8s-general
---------- Post added at 05:24 PM ---------- Previous post was at 05:21 PM ----------
panagath said:
Hello, thanks for the reply. What I see are the following:
LOCKED
HBOOT - 3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.61.4
Click to expand...
Click to collapse
I can't remember whether there is RUU for your device. I'll check later tonight.
For the time being, try to install stock 6.12.61.4 firmware and see whether this helps or not.
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5

ckpv5 said:
Your device is not regular M8, it's htc M8s.
You can try to RUU - https://forum.xda-developers.com/showpost.php?p=70306458&postcount=2
Anything ask here not in M8 section - https://forum.xda-developers.com/htc-one-m8/one-m8s-general
---------- Post added at 05:24 PM ---------- Previous post was at 05:21 PM ----------
I can't remember whether there is RUU for your device. I'll check later tonight.
For the time being, try to install stock 6.12.61.4 firmware and see whether this helps or not.
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Click to expand...
Click to collapse
That's interesting ! I will give it a go this evening. Did not think it could be M8s. Thank you !
Vash
---------- Post added at 10:57 AM ---------- Previous post was at 10:56 AM ----------
panagath said:
Hey, thanks for the reply. I haven't managed to do anything neither did I spend a lot of time on this. I was waiting in case someone could help. Such a shame if the phone is bricked. I do not know if it is worth taking to professionals as its value as a used phone is quite low at the moment...
Click to expand...
Click to collapse
Yes you are right. The only way is to keep trying with these phones, until you succeed
---------- Post added at 11:30 AM ---------- Previous post was at 10:57 AM ----------
ckpv5 said:
Your device is not regular M8, it's htc M8s.
You can try to RUU - https://forum.xda-developers.com/showpost.php?p=70306458&postcount=2
Anything ask here not in M8 section - https://forum.xda-developers.com/htc-one-m8/one-m8s-general
---------- Post added at 05:24 PM ---------- Previous post was at 05:21 PM
Click to expand...
Click to collapse
How can you say that it is M8s and not M8 please ? I had a problem with another M8 before, seems it could be for the very same reason (could be M8s afterall)
Thank you
Vash

vagon1 said:
How can you say that it is M8s and not M8 please ? I had a problem with another M8 before, seems it could be for the very same reason (could be M8s afterall)
Thank you
Vash
Click to expand...
Click to collapse
Based on the OS no. that you wrote. Regular M8 doesn't have that version, only M8s does.
To really confirm, write here all the details that you see on bootloder because your current one is incomplete.
Better if you give result of fastboot getvar all (without serial & imei no.), this will be truly complete details.

update
ckpv5 said:
Based on the OS no. that you wrote. Regular M8 doesn't have that version, only M8s does.
To really confirm, write here all the details that you see on bootloder because your current one is incomplete.
Better if you give result of fastboot getvar all (without serial & imei no.), this will be truly complete details.
Click to expand...
Click to collapse
Hi Matey
Update. Downloaded the file, placed to SD card and rebooted to bootloader. Update started ok, but soon message popped up : Device halted due to Large Image update fail!
Device rebooted, but now it's blinking orange led but can't start it or anything. Will keep it on charger until tomorrow and see if I can start it again.
My Getvar bellow :
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.21.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT554YS01064
(bootloader) imei: 358031060751297
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__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: 7900fbfd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
The attachment below is from someone else, for illustration purposes only. As did not manage to take a photo of mine. But message looks exactly the same..

vagon1 said:
Hi Matey
Update. Downloaded the file, placed to SD card and rebooted to bootloader. Update started ok, but soon message popped up : Device halted due to Large Image update fail!
Device rebooted, but now it's blinking orange led but can't start it or anything. Will keep it on charger until tomorrow and see if I can start it again.
My Getvar bellow :
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.21.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT554YS01064
(bootloader) imei: 358031060751297
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__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: 7900fbfd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
The attachment below is from someone else, for illustration purposes only. As did not manage to take a photo of mine. But message looks exactly the same..
Click to expand...
Click to collapse
Seems I managed to brick my M8s. After failed updated and device restart it wont turn back on. Only orange LED is repeatedly flashing when plugged to the charger or PC. PC detects that something is connected by doesn't recognize it. Wont respond to any ADB commands. I also tried VOL UP/DOWN + POWER BUTTONS for 5minutes a number of times, but nothing.
I had similar problem with HTC One Mini 2, had to take phone apart and disconnect the battery for a few minutes. Phone started OK and worked fine after this. But really don't want to take this M8s apart to disconnect the battery. As it's not mine.
Don't know if to keep the phone on charger, or let it rather disconnected and discharge.. ??
Any help would be much appreciated.
Vash

vagon1 said:
My Getvar bellow :
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-main: 1.21.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__001
The attachment below is from someone else, for illustration purposes only. As did not manage to take a photo of mine. But message looks exactly the same..
Click to expand...
Click to collapse
First to answer your earlier question how to know whether your device is M8 or M8s.
As you can see in your getvar result, the product is m8ql_ul which belongs to M8s. M8 is m8_ul for GSM version.
Now your thread already been moved to M8s section. Hoefully someone familiar with M8s can assist here.
I can only assist on general term and idea.
With your getvar result, now we know you have a Lollipop. The RUU is for Marshmallow. To install a Marshmallow RUU (for the case of M8), you need first to install Marshmallow firmware then only can install Marshmallow RUU. That's explained the Large image failure. Unfortunately I don't know whether anyone post any firmware only for 2.10.401.1 so you can install the RUU after.
Getting this Large image failure doesn't brick a device. With S-On it's either the RUU is successfully installed or failed. And usually will only be successfully installed when the problem is firmware & software related. When a hardware problem like corrupted emmc, RUU won't be able to fix it.
As you used Hansoon toolkit earlier which is meant for M8 not M8s, not sure whether that have any effect on your device hardware.
Let's see whether anyone with M8s has any knowledge on how to fix your problem.

ckpv5 said:
First to answer your earlier question how to know whether your device is M8 or M8s.
As you can see in your getvar result, the product is m8ql_ul which belongs to M8s. M8 is m8_ul for GSM version.
Now your thread already been moved to M8s section. Hoefully someone familiar with M8s can assist here.
I can only assist on general term and idea.
With your getvar result, now we know you have a Lollipop. The RUU is for Marshmallow. To install a Marshmallow RUU (for the case of M8), you need first to install Marshmallow firmware then only can install Marshmallow RUU. That's explained the Large image failure. Unfortunately I don't know whether anyone post any firmware only for 2.10.401.1 so you can install the RUU after.
Getting this Large image failure doesn't brick a device. With S-On it's either the RUU is successfully installed or failed. And usually will only be successfully installed when the problem is firmware & software related. When a hardware problem like corrupted emmc, RUU won't be able to fix it.
As you used Hansoon toolkit earlier which is meant for M8 not M8s, not sure whether that have any effect on your device hardware.
Let's see whether anyone with M8s has any knowledge on how to fix your problem.
Click to expand...
Click to collapse
Thank you for the reply, yes there are some seriously valid points. I'm still hoping I'll be able to ressurect the phone. But before I had One Mini 2 with exactly same symptoms and had to take the phone apart, disconnect the battery and when put all back together phone worked again. But really want to avoid doing this... I'll give it a couple of days playing with buttons and charger and if phone doesn't start I will take it apart and do the battery trick.
Once working again will load a Lollipop on it and hopefully phone will work. If emmc is buggered then I think the phone is done...
Will keep everyone posted about results..
Again thank you very much
Vash

Bootloop problem; can't restore to TWRP backup with root.

A somewhat similar problem to this one: https://forum.xda-developers.com/ht...soft-brick-t3504692/post69758285#post69758285
I have a HTC one M8 (obviously).
It successfully has TWRP installed, and until today it had both SuperSU (2.78) and x-posed installed and working.
Earlier today, I was struggling with suspected power failure in the device (it said it had 20-30% power left but it shut off as if completely out of power).
As a result of this, once I started charging it, it could boot fine but had forgotten all my personalization options (what start screen icons, alarms, ringtone etc. and even android device-ID changed, according to titanium backup) though the installed apps were untouched.
So, after I reset the device ID back to the original with titanium backup, I shut it off, made a backup in TWRP, and tried to reload the previous backup with the correct personalization settings.
however, it seems unable to boot into any of the backups I have, not even the one I just made, except for the completely untouched backup that I original made before beginning on rooting.
every other one I try to boot into, it gets stuck on the "HTC powered by Android" splash screen, including the backup of a state that worked mere hours ago.
If anyone has an idea what could be going on I would appreciate the help.

What version TWRP?
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
What version TWRP?
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
TWRP is version 2.7.0.2 (upon investigation, this is a bit out of date. but does that matter seeing as the hardware doesn't change?).
getvar all resulted in:
Code:
(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:
(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: VODAPE17
(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
Since this, I've been working on it some more. I think something went wrong with the system or boot partitions, since restoring to factory default and then getting the latest backup of the data on did work. Since then I've been working on re-rooting the phone with majisk.
Though it isn't urgent anymore now that the phone is no longer effectively soft bricked, the fact that TWRP backups didn't work is very disturbing to me, so help getting that working is still appreciated. Hopefully it's just something simple/stupid, like an out of date TWRP.

wild_dog said:
TWRP is version 2.7.0.2 (upon investigation, this is a bit out of date. but does that matter seeing as the hardware doesn't change?).
Click to expand...
Click to collapse
TWRP version absolutely matters. Outdated TWRP is known to cause problems due to incompatibility with later firmware/software. It will probably also fail or cause other problems while trying to root, flash custom ROMs, etc.
Also, it's not just a bit out of that. TWRP 2.7 is something like 3 years old!
Latest TWRP is typically recommended. Currently, that is version 3.1.1. You can get it here: https://dl.twrp.me/m8/

redpoint73 said:
TWRP version absolutely matters. Outdated TWRP is known to cause problems due to incompatibility with later firmware/software. It will probably also fail or cause other problems while trying to root, flash custom ROMs, etc.
Also, it's not just a bit out of that. TWRP 2.7 is something like 3 years old!
Latest TWRP is typically recommended. Currently, that is version 3.1.1. You can get it here: https://dl.twrp.me/m8/
Click to expand...
Click to collapse
0_0 welp, lucky me then that it still was able to go back to the old stock backup... just flashed a new TWRP and am now running a new backup. looks like it also backups more, or at least has a finer controlled partitioning in what it does backup. i'll play around with that a bit, caus I now see that a data backup does not include storage, which is something I would want.