HTC M8s Stuck between Bootloader and Stock Recovery - One (M8) Q&A, Help & Troubleshooting

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

Related

M8 Bricked while updating to Marshmallow.

Hi,
The other day i've tried to update my M8 to marshmallow via OTA and my device get bricked . . .
It is stucked on Android Recovery, and have tried everything. Ruu's, factory reset . . . everything. Ruu always gives me back error 155.
Don't know what else to do. It is new, but I think the people that sold it to me have changed things like CID and it have S-OFF.
I'll post the "fastboot getvar all" command results:
E:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei: ---------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Can someone help me? :crying: Thanks!
I am having the same problem!! I installed the official update via the system update, installed then at the end it told me there is a problem with the OTA thing and that is it. Since then my device is bricked and I'm in between the recovery menu and the bootloader.
I don't wanna root my device and didn't try it. This sucks. I wish I can rollback this mess to Lollipop.
Moe88Saber said:
I am having the same problem!! I installed the official update via the system update, installed then at the end it told me there is a problem with the OTA thing and that is it. Since then my device is bricked and I'm in between the recovery menu and the bootloader.
I don't wanna root my device and didn't try it. This sucks. I wish I can rollback this mess to Lollipop.
Click to expand...
Click to collapse
I had a similar issue, bricked my HTC ONE M8 by updating through OTA.
But I got it fixed by flashing RUU through htc_fastboot.exe, it took a while but was effective.
In your case, if you need to find your right CID, first get your mid number and check if you can find a right CID to your MID, then write it through fastboot. Hope it can help you.
If you will need a detailed how to, let me know
azbtaurus said:
I had a similar issue, bricked my HTC ONE M8 by updating through OTA.
But I got it fixed by flashing RUU through htc_fastboot.exe, it took a while but was effective.
In your case, if you need to find your right CID, first get your mid number and check if you can find a right CID to your MID, then write it through fastboot. Hope it can help you.
If you will need a detailed how to, let me know
Click to expand...
Click to collapse
My CID is 11111111, it says so in the bootloader. Can you provide links on where to get the RUU and the flashing app? Thanks
The bootloader says LOCKED yet my device is the international variant. Is it related or does it mean that my bootloader is locked?
ramajo17 said:
Hi,
The other day i've tried to update my M8 to marshmallow via OTA and my device get bricked . . .
It is stucked on Android Recovery, and have tried everything. Ruu's, factory reset . . . everything. Ruu always gives me back error 155.
Don't know what else to do. It is new, but I think the people that sold it to me have changed things like CID and it have S-OFF.
I'll post the "fastboot getvar all" command results:
E:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44WWM07312
(bootloader) imei: ---------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Can someone help me? :crying: Thanks!
Click to expand...
Click to collapse
Hey, I've made a simple research and found that your serial number belongs to HTC ONE M8 Taiwan version, so first you need to change your MID to 0P6B150 (optional but strongly advised for applaying offical updates) and then the CID to CHT__601 (Taiwan).
Only after this you need to find the right RUU and flash it, or use RUU.zip and flash it through htc_fastboot.exe
Hope it will be helpfull
---------- Post added at 09:52 AM ---------- Previous post was at 09:48 AM ----------
Moe88Saber said:
My CID is 11111111, it says so in the bootloader. Can you provide links on where to get the RUU and the flashing app? Thanks
The bootloader says LOCKED yet my device is the international variant. Is it related or does it mean that my bootloader is locked?
Click to expand...
Click to collapse
Send me your detailed phone information as it was shown in the first post of the thread so I can tell you how to change you CID and other identification numbers that in the end will let you apply the update
Having the original CID is very important, cuz your bootloader was relocked? otherwise they could've not changed you CID/
Check your serial information go to HTC Warranty Check - Lookup
this tell you right region information of your phone so you can easily find right CID and MID numbers of your phone
azbtaurus said:
Send me your detailed phone information
Click to expand...
Click to collapse
Can you walk me through it? When I connect my device to my laptop, it shows nothing. the HTC sync app fails to detect my phone as well.
But my bootloader detects it. It goes from FASTBOOT to FASTBOOT USB
azbtaurus said:
Hey, I've made a simple research and found that your serial number belongs to HTC ONE M8 Taiwan version, so first you need to change your MID to 0P6B150 (optional but strongly advised for applaying offical updates) and then the CID to CHT__601 (Taiwan).
Click to expand...
Click to collapse
That is wrong .. you need to see the CID/MID not the serial no.
He can flash the 6.12.401.4 RUU zip
---------- Post added at 01:40 PM ---------- Previous post was at 01:35 PM ----------
ramajo17 said:
Hi,
The other day i've tried to update my M8 to marshmallow via OTA and my device get bricked . . .
It is stucked on Android Recovery, and have tried everything. Ruu's, factory reset . . . everything. Ruu always gives me back error 155.
Don't know what else to do. It is new, but I think the people that sold it to me have changed things like CID and it have S-OFF.
I'll post the "fastboot getvar all" command results:
E:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei: ---------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Can someone help me? :crying: Thanks!
Click to expand...
Click to collapse
1. - remove the serial no. in your above post.
2. - Is the bootloader LOCKED or RELOCKED ? If it is UNLOCKED, relock it with command fastboot oem lock
3. - follow this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4 for the driver part
and this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6 for the RUU part
Moe88Saber said:
Can you walk me through it? When I connect my device to my laptop, it shows nothing. the HTC sync app fails to detect my phone as well.
But my bootloader detects it. It goes from FASTBOOT to FASTBOOT USB
Click to expand...
Click to collapse
1 - see the links in the end of #7 post? Go there and first get the drivers and adb-fastboot tools
once you get try command fastboot getvar all this will show you the detailed information of your device
2 - once done get HTC ONE M8 all in one tool kit, it would be easier for you to use instead typing commands all the time
3 - unlock your bootloader by following the instructions on the program listed above
4 - search for right CID number of your phone and write it by using command fastboot oem writecid (YOUR CID)
5 - relock bootloader
6 - flash the right RUU (check if it is right for your original new CID)
Keep in mind that I've done this on my own devices, and I don't take any responsibility in case if you get your device bricked
ckpv5 said:
That is wrong .. you need to see the CID/MID not the serial no.
He can flash the 6.12.401.4 RUU zip
---------- Post added at 01:40 PM ---------- Previous post was at 01:35 PM ----------
1. - remove the serial no. in your above post.
2. - Is the bootloader LOCKED or RELOCKED ? If it is UNLOCKED, relock it with command fastboot oem lock
3. - follow this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4 for the driver part
and this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6 for the RUU part
Click to expand...
Click to collapse
I'm not the OP but I am experiencing the same issue. anyway...my bootloader is locked and it is connected to the ADB, getvar shows me some stats. I'm now downloading the RUU and will flash it afterwards. Thanks for your help.
Moe88Saber said:
I'm not the OP but I am experiencing the same issue. anyway...my bootloader is locked and it is connected to the ADB, getvar shows me some stats. I'm now downloading the RUU and will flash it afterwards. Thanks for your help.
Click to expand...
Click to collapse
You cannot simply flash the RUU .. the first question is .. is the RUU the right one for your device ?
You have SUperCID as you mentioned above .. what about the MID ?
Is it 0P6B10000 ? If yes .. then go ahead
ckpv5 said:
You cannot simply flash the RUU .. the first question is .. is the RUU the right one for your device ?
You have SUperCID as you mentioned above .. what about the MID ?
Is it 0P6B10000 ? If yes .. then go ahead
Click to expand...
Click to collapse
Sir, If you mean the modelid, then yes, it is 0P6B10000 and cidnum is 11111111
Should I go ahead?
Moe88Saber said:
Sir, If you mean the modelid, then yes, it is 0P6B10000 and cidnum is 11111111
Should I go ahead?
Click to expand...
Click to collapse
Yes.. sure
ckpv5 said:
That is wrong .. you need to see the CID/MID not the serial no.
He can flash the 6.12.401.4 RUU zip
---------- Post added at 01:40 PM ---------- Previous post was at 01:35 PM ----------
1. - remove the serial no. in your above post.
2. - Is the bootloader LOCKED or RELOCKED ? If it is UNLOCKED, relock it with command fastboot oem lock
3. - follow this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4 for the driver part
and this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6 for the RUU part
Click to expand...
Click to collapse
Ok I'm downloading the RUU. I've tried to apply this RUU from computer but not worked, I hope it works with fastboot!
I'll tell you once is done, thanks!
Update info:
It gets stuck in "sending 'zip'... <53965 KB>
I've waited 20 minutes and nothing happens.
ckpv5 said:
yes.. Sure
Click to expand...
Click to collapse
yes!!! It lives! You are one magnificent human being! I am forever in your debt!:d:d
thank you thank you thank you
ramajo17 said:
Ok I'm downloading the RUU. I've tried to apply this RUU from computer but not worked, I hope it works with fastboot!
I'll tell you once is done, thanks!
Update info:
It gets stuck in "sending 'zip'... <53965 KB>
I've waited 20 minutes and nothing happens.
Click to expand...
Click to collapse
Have you install the fastboot/adb that linked above ?
Have you updated the HTC USB drivers, also linked above ?
Try with a Windows PC USB2.0
ckpv5 said:
Have you install the fastboot/adb that linked above ?
Have you updated the HTC USB drivers, also linked above ?
Try with a Windows PC USB2.0
Click to expand...
Click to collapse
Yes both things. I'll try to download the RUU again because when I try to unzip it on my PC it says that the file is corrupted.
Can be that the problem?
ramajo17 said:
Yes both things. I'll try to download the RUU again because when I try to unzip it on my PC it says that the file is corrupted.
Can be that the problem?
Click to expand...
Click to collapse
You can't extract/unzip an encrypted HTC RUU zip.
You never reply to my first question .. is your bootloader LOCKED, RELOCKED or UNLOCKED ?
If it is UNLOCKED .. I can suggest another method .. restore a TWRP backup.
If you have installed both adb/fastboot and latest HTC USB driver (and uninstall HTC Sync Manager) I don't see a reason why it cannot work for you when it worked for the other guy (post #14)
Do you have a microSD card ? You can do it different way.
ckpv5 said:
You can't extract/unzip an encrypted HTC RUU zip.
You never reply to my first question .. is your bootloader LOCKED, RELOCKED or UNLOCKED ?
If it is UNLOCKED .. I can suggest another method .. restore a TWRP backup.
If you have installed both adb/fastboot and latest HTC USB driver (and uninstall HTC Sync Manager) I don't see a reason why it cannot work for you when it worked for the other guy (post #14)
Do you have a microSD card ? You can do it different way.
Click to expand...
Click to collapse
Sorry, it is RELOCKED.
I'll try to do all from 0 again. If it does not work we can UNLOCK it and try the TWRP method you say?
Yes I do have an SD card in my phone, but my PC doesn't detect it and have no SD adapter. I've heard that there's some fastboot command "push" or something like that to put the RUU on it but don't know how it works.
Thanks for your time, I'm desperate. . .
You need to unlock bootloader to go with TWRP method.
Just try again ... with a Windows PC with USB2.0 (many people report USB3.0 is a hit and miss)
Make sure the HTC Sync manager is uninstalled after you install the driver.
ckpv5 said:
You need to unlock bootloader to go with TWRP method.
Just try again ... with a Windows PC with USB2.0 (many people report USB3.0 is a hit and miss)
Make sure the HTC Sync manager is uninstalled after you install the driver.
Click to expand...
Click to collapse
Can't believe it was de USB . . . Now is doing things, let's see
Update:
IT IS ALIVE!! The problem was de USB . . I was using the official one but didn't work.
Really big thanks!!

Out of options, phone fails to work.

Hey all, i have a bit of problem here.
To days ago my M8 started to randomly turn off , and now it`s happening more and more often , to point where it is impossible to use.
Before it started it got a bit hot, not to hot, regular htc hot.
Tried: Blues GPE,Lypota GPE (was on this one before things happened), Sky dragoon GPE
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
How does this sudden turn off happen:
It`s fine, when it`s plugged in and charging, sometimes not, tried to test GPE maybe one of them fails, it`s random. When i remove phone from power it works for a while if i don`t press any app, but again it`s like a lottery , sometimes it works for longer sometimes it just dies, and i get more or less stuck on system not booting.
Do anybody have any suggestions ?
boomboxie said:
Hey all, i have a bit of problem here.
To days ago my M8 started to randomly turn off , and now it`s happening more and more often , to point where it is impossible to use.
Before it started it got a bit hot, not to hot, regular htc hot.
Tried: Blues GPE,Lypota GPE (was on this one before things happened), Sky dragoon GPE
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
How does this sudden turn off happen:
It`s fine, when it`s plugged in and charging, sometimes not, tried to test GPE maybe one of them fails, it`s random. When i remove phone from power it works for a while if i don`t press any app, but again it`s like a lottery , sometimes it works for longer sometimes it just dies, and i get more or less stuck on system not booting.
Do anybody have any suggestions ?
Click to expand...
Click to collapse
UPDATE: Seems like it`s mostly happening when installing new apps, or recovering them. Tried to remove sdcard , did`t help.
boomboxie said:
H
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
Click to expand...
Click to collapse
When you say "FAIL" you mean these things actually don't happen successfully (fail to flash, etc.); or that the random power off persists?
Are you converted to GPE by RUU? Maybe try to RUU to full GPE "stock" and see if that helps.
You may be looking at a bad battery or some other hardware failure (emmc).
redpoint73 said:
When you say "FAIL" you mean these things actually don't happen successfully (fail to flash, etc.); or that the random power off persists?
Are you converted to GPE by RUU? Maybe try to RUU to full GPE "stock" and see if that helps.
You may be looking at a bad battery or some other hardware failure (emmc).
Click to expand...
Click to collapse
Depends some rom fail to flash some works. After flashing power off problem persists. As for now, i`m not able to turn on phone without power cord, but once it`s one, works fine unless i do anything (starting an app and so on)
At the beginning i used Hanson2000`s toolkit to root the phone, and after that installed GPE room.
Will try to convert to stock GPE with RUU and update on results.
boomboxie said:
Depends some rom fail to flash some works. After flashing power off problem persists. As for now, i`m not able to turn on phone without power cord, but once it`s one, works fine unless i do anything (starting an app and so on)
At the beginning i used Hanson2000`s toolkit to root the phone, and after that installed GPE room.
Click to expand...
Click to collapse
The toolkit hasn't been updated since April 2014! It contains woefully obsolete version of TWRP, and that is probably why some ROMs are failing to flash. Highly advise to update to current TWRP 3.0.
How long have you had the phone, how long on GPE ROMs? Is the firmware up to date?
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
boomboxie said:
Will try to convert to stock GPE with RUU and update on results.
Click to expand...
Click to collapse
You can only do this if you have s-off.
You may want to try to RUU back to your stock (probably Sense) version, and see if the random power offs persist.
To me it looks like a hardware fail, most likely a bad battery. OP says it works when plugged in but dies when not.
My guess ,if all else fail ,is to try a new battery
redpoint73 said:
The toolkit hasn't been updated since April 2014! It contains woefully obsolete version of TWRP, and that is probably why some ROMs are failing to flash. Highly advise to update to current TWRP 3.0.
How long have you had the phone, how long on GPE ROMs? Is the firmware up to date?
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
You can only do this if you have s-off.
You may want to try to RUU back to your stock (probably Sense) version, and see if the random power offs persist.
Click to expand...
Click to collapse
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
boomboxie said:
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
Click to expand...
Click to collapse
Be careful with your terminology there, to avoid confusion. From your previous post, you stated you just flashed a GPE ROM.
This isn't the same as "converting" to GPE with RUU, which puts you on GPE firmware, GPE partitioning, etc.
boomboxie said:
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
Click to expand...
Click to collapse
I don't know what that means, if you don't give details on what you did, and the specific results. But I'm assuming you know how to use command prompt to issue adb/fastboot commands, entered the command, and get no response (or device offline)?
If so, check that you are in bootloader-fastboot mode, have HTC drivers installed, or try different cable or USB port.
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
bombo_b said:
To me it looks like a hardware fail, most likely a bad battery. OP says it works when plugged in but dies when not.
My guess ,if all else fail ,is to try a new battery
Click to expand...
Click to collapse
I tend to agree that its a hardware problem. But its always a good idea to return to full stock by RUU, to eliminate the possibility its a software issue, before concluding its a hardware problem.
boomboxie said:
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
Click to expand...
Click to collapse
1) at first go to bootloader
2) connect device via usb cable into pc
3) confirm you are in fastboot mode
4) install drivers through htc sync manager
5) download the following zip
6) at first create a new folder in desktop. then copy zip into that folder & extract.
7) while press ''shift'' right clik on the new folder & select ''open command window here''
8) on the command prompt type fastboot getvar all
I managed to run command: here are the results.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(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: HTC__203
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Disregard this post.Sorry
boomboxie said:
I managed to run command: here are the results.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(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: HTC__203
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Click to expand...
Click to collapse
You are still with kitkat firmware. Your version is 3.28.401.9. Try to go to a stock. Confirm whether your problem is a hardware problem or not.
umesh.lk said:
You are still with kitkat firmware. Your version is 3.28.401.9. Try to go to a stock. Confirm whether your problem is a hardware problem or not.
Click to expand...
Click to collapse
What would be the best way to do that ?
boomboxie said:
What would be the best way to do that ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Restore stock ROM and stock recovery for 3.28.401.9, then OTA update up to current MM.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
boomboxie said:
I have newest TWRP installed.
Yes firmware is up to date.
Click to expand...
Click to collapse
As I've often found to be the case here, folks claim to be "up to date" without providing any specific details or version numbers, and it turns out they are very much not up to date.
redpoint73 said:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Restore stock ROM and stock recovery for 3.28.401.9, then OTA update up to current MM.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
As I've often found to be the case here, folks claim to be "up to date" without providing any specific details or version numbers, and it turns out they are very much not up to date.
Click to expand...
Click to collapse
Thanks, will update on outcome.
EDIT: I thought i was "up to date" i guess i wasn`t lol, my bad.
UPDATE:
Flashed stock rom, did all the updates, nothing has changed same issue persists: Turning off, seem like it`s 90% chance of battery failure.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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
all: Done!
finished. total time: 0.049s
https://www.youtube.com/watch?v=F2SetwqZzKE <- Filmed how it happens/
boomboxie said:
UPDATE:
Flashed stock rom, did all the updates, nothing has changed same issue persists: Turning off, seem like it`s 90% chance of battery failur
https://www.youtube.com/watch?v=F2SetwqZzKE <- Filmed how it happens/
Click to expand...
Click to collapse
At first did you calibration the battery? Is your device still Hot? It's amazing as you could install an ota in such a situation. Turn off Wi-Fi and then check. You're still 50% Battery problem, you have more works to do.
umesh.lk said:
At first did you calibration the battery? Is your device still Hot? It's amazing as you could install an ota in such a situation. Turn off Wi-Fi and then check. You're still 50% Battery problem, you have more works to do.
Click to expand...
Click to collapse
Did calibration of battery with Power+vol up/down method, went to safe mode problem still persists.
No problems with booting into boot-loader, dosn`t power off. once i try to access recovery powers off.
https://www.youtube.com/watch?v=5wgC8ST9lU4
boomboxie said:
Did calibration of battery with Power+vol up/down method, went to safe mode problem still persists.
No problems with booting into boot-loader, dosn`t power off. once i try to access recovery powers off.
https://www.youtube.com/watch?v=5wgC8ST9lU4
Click to expand...
Click to collapse
try to flash firmware through hboot. when it flash look whether sensor_hub.img flushing & flashing correctly happen. then reboot.
umesh.lk said:
try to flash firmware through hboot. when it flash look whether sensor_hub.img flushing & flashing correctly happen. then reboot.
Click to expand...
Click to collapse
By that you mean: Connecting phone to PC and flashing Newer recovery or OS ?

MY HTC M8 is not booting. What can I do?

I have S-ON M8 with custom recovery on it. I can get to the recovery but it is impossible to mount it as memory to upload any custom rom to flash it to work. My phone gets stuck on Android logo and does not go further. Is it possible for me to flash it using RUU and get it back to original, stock firmware?
palito1980 said:
I have S-ON M8 with custom recovery on it. I can get to the recovery but it is impossible to mount it as memory to upload any custom rom to flash it to work.
Click to expand...
Click to collapse
In TWRP, go to Wipe, and tap the button "Format data". It sounds like your internal storage is corrupt, and doing the format data option usually fixes this. Obviously, you will lose any data on the phone, but it sounds like we're well past that point already.
palito1980 said:
Is it possible for me to flash it using RUU and get it back to original, stock firmware?
Click to expand...
Click to collapse
Probably. But it depends on whether your M8 version has an RUU.
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Software status MODIFIED
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.25.21331147A1.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.771.2
eMMC-boot 2048MB
This is the info about my device.
I think I downloaded proper RUU but when I start installation on my Windows 10 machine it asks for Admin privliges and starts installation and disappears at the end. Nothing happens.
palito1980 said:
I think I downloaded proper RUU
Click to expand...
Click to collapse
It would be useful if you provided some specific reasoning/rationale on why you think its the right RUU, or any specific details (file name, link to where you got it from, etc.).
I've lost count of how many times folks "thought" they had the right RUU, but were wrong.
Also, I suggested in my last post that you try2 very specific things, which it seems you completely ignored. Don't know if there is a point in trying to help you, if you ignore the advice given.
I didn't ignore anything. Tried, didn't work. And mu RUU's name is RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
With different RUU the situation is the same. Drivers installed and still does not work.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
palito1980 said:
I didn't ignore anything. Tried, didn't work.
Click to expand...
Click to collapse
That's important information to provide. Otherwise, we can only assume you ignored the advice.
Plus, if it "didn't work" what does that mean? Were their error messages, or any other outputs?
You tried both things (format data, and getvar) and the both didn't work?
palito1980 said:
And mu RUU's name is RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
Click to expand...
Click to collapse
This is not even remotely the right RUU for your device. I don't know why you think its the right one. Its for the US Sprint version. In fact, if it had run (which wouldn't happen on an s-on device) it would have radio bricked your phone, due to the differences in the Sprint version.
---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------
palito1980 said:
With different RUU the situation is the same. Drivers installed and still does not work.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
Click to expand...
Click to collapse
This isn't the right RUU either. It seems you are just guessing. This one is for the US Developer's Edition.
I don't think your version has RUU.
But I also need to see the getvar output, to see if anything on the phone has been modified (to change the carrier version).
Unfortunately I am unabale to get anything from getvar. It get stuck on "waiting for device"
palito1980 said:
Unfortunately I am unabale to get anything from getvar. It get stuck on "waiting for device"
Click to expand...
Click to collapse
The phone is in bootloader, with fastboot mode selected (highlighted in red near the top - if its not, select fastboot in the menu selections on the bootloader screen, and confirm with power button).
Also, try another USB cable.
If its still not working, hanging on "waiting for devices" is usually a problem on the PC side. Uninstall and re-install HTC Sync, try another USB port, or another PC if possible. Win7 and USB 2.0 has the best chance of compatibility with this device.
---------- Post added at 09:22 AM ---------- Previous post was at 09:15 AM ----------
palito1980 said:
I can get to the recovery but it is impossible to mount it as memory to upload any custom rom to flash it to work.
Click to expand...
Click to collapse
To be clear, are you trying to mount when booted into TWRP?
Do you have an SD card, and a USB card reader? If so, just put the ROM on the SD card from your computer, then just put the SD in the phone, flash in TWRP.
That is all getvar sit out. This was done under Linux coz Windows just didn't want to work with the phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.771.2
(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: H3G__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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

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).

Hi guys anybody can help me ? My Htc one m8 has been bricked i can't flash stock ruu

Hi guys anybody can help me ? My Htc one m8 has been bricked i can't flash stock ruu please help me
this are my fastboot getvar all value :
(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.20.709.2
(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: 0P6B11000
(bootloader) cidnum: HTC__621
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
so my bootlader is locked with security warning and software status : modified
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
redpoint73 said:
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
Click to expand...
Click to collapse
When i flash RUU faced with "remote : 12 signautre verify fail" and this is a RUU that i flashed : HTC One M8 6.20.709.2 sense 8
redpoint73 said:
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
Click to expand...
Click to collapse
when i unplugged the phone from charger this problem occurred i didn't flash any RUU later and my phone is unrooted .
mamali0067 said:
when i unplugged the phone from charger this problem occurred .
Click to expand...
Click to collapse
I assume when you say "bricked" it means you can't boot to Android OS, but you can get to bootloader (otherwise, you wouldn't have been able to do fastboot getvar).
On the bootloader screen, does it say LOCKED or UNLOCKED near the top?
Also, I recommend you delete IMEI and serial number from your top post. These are personal info, and should not be posted online (and also, not needed to help or advise you).
---------- Post added at 09:09 AM ---------- Previous post was at 09:09 AM ----------
mamali0067 said:
When i flash RUU faced with "remote : 12 signautre verify fail" and this is a RUU that i flashed : HTC One M8 6.20.709.2 sense 8
Click to expand...
Click to collapse
To confirm, the file actually says "RUU" in the file name, and about 1.5 GB in size?
redpoint73 said:
I assume when you say "bricked" it means you can't boot to Android OS, but you can get to bootloader (otherwise, you wouldn't have been able to do fastboot getvar).
On the bootloader screen, does it say LOCKED or UNLOCKED near the top?
Also, I recommend you delete IMEI and serial number from your top post. These are personal info, and should not be posted online (and also, not needed to help or advise you).
---------- Post added at 09:09 AM ---------- Previous post was at 09:09 AM ----------
To confirm, the file actually says "RUU" in the file name, and about 1.5 GB in size?
Click to expand...
Click to collapse
yes of course it's about 1.6 GB and in my bootloader it say LOCKED
mamali0067 said:
yes of course it's about 1.6 GB and in my bootloader it say LOCKED
Click to expand...
Click to collapse
Is this a zip format RUU? If so, cut/paste the exact commands you used.
redpoint73 said:
Is this a zip format RUU? If so, cut/paste the exact commands you used.
Click to expand...
Click to collapse
yes the RUU is a zip file , but i flashed that RUU perefer in finding right RUU thread and faced with remote : 12 signature verify fail
mamali0067 said:
i flashed that RUU perefer in finding right RUU thread
Click to expand...
Click to collapse
I'm not going to jump around threads looking for the info. I already told you that twice. You should be trying to make it easier for folks to help you, not harder!
redpoint73 said:
I'm not going to jump around threads looking for the info. I already told you that twice. You should be trying to make it easier for folks to help you, not harder!
Click to expand...
Click to collapse
Okay dude , so help me here !
mamali0067 said:
Okay dude , so help me here !
Click to expand...
Click to collapse
You didn't provide the info I asked for: cut/paste the exact commands you used
redpoint73 said:
You didn't provide the info I asked for: cut/paste the exact commands you used
Click to expand...
Click to collapse
Yes , I have been cutted and pasted the command

Categories

Resources