Develop Bugs

Possible dead phone

reposted from wrong forum
What happened: Rooted and installed Cyanogenmod 11 snapshot. Ran for a week just fine though I ****ed up the boot animation trying to change it, in case that matters. After a week, I open my phone that had been on and none of the apps worked or gave any response and then they disappeared and reappeared. Rebooted phone and it kept stopping at my blank boot animation, a blank illuminated screen after the HTC splash screen.
In TWRP, I am unable to format, wipe or do anything that I can think of to /data. Every time: "Unable to mount E:/data" Not totally sure what that means but it sounds quite important. Definitely not sure why. A possible hard drive failure? Any tips or advice?
Related, if my phone is dead: I am having difficulty switching phones through Verizon to my old flip phone. It seems they are waiting for the SIM card on my m7 to turn off, however that doesn't seem like it's happening with my dead phone. They said it would take up to 24 hours, it's been three days. I guess I'll need to take it in to the Verizon store, who might not give any help once they see I voided the warranty. Is there any way to "turn off the SIM card" and get my flip phone to work, even if the m7 is dead?
Thanks in advance
Unsure if this helps vv
"fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [removed]
(bootloader) imei: [removed]
(bootloader) meid: [removed]
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3783mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
TWRP version 2.7.0.8

Try to ruu your phone. Be sure to back everything up
Sent from my HTC6500LVW using XDA Free mobile app

no_trace said:
reposted from wrong forum
What happened: Rooted and installed Cyanogenmod 11 snapshot. Ran for a week just fine though I ****ed up the boot animation trying to change it, in case that matters. After a week, I open my phone that had been on and none of the apps worked or gave any response and then they disappeared and reappeared. Rebooted phone and it kept stopping at my blank boot animation, a blank illuminated screen after the HTC splash screen.
In TWRP, I am unable to format, wipe or do anything that I can think of to /data. Every time: "Unable to mount E:/data" Not totally sure what that means but it sounds quite important. Definitely not sure why. A possible hard drive failure? Any tips or advice?
Related, if my phone is dead: I am having difficulty switching phones through Verizon to my old flip phone. It seems they are waiting for the SIM card on my m7 to turn off, however that doesn't seem like it's happening with my dead phone. They said it would take up to 24 hours, it's been three days. I guess I'll need to take it in to the Verizon store, who might not give any help once they see I voided the warranty. Is there any way to "turn off the SIM card" and get my flip phone to work, even if the m7 is dead?
Thanks in advance
Unsure if this helps vv
"fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [removed]
(bootloader) imei: [removed]
(bootloader) meid: [removed]
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3783mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
TWRP version 2.7.0.8
Click to expand...
Click to collapse
You are s-off, so just pick an RUU, put it into RUU mode and flash it. I doubt it is dead.

Can't relock my phone to apply the RUU?
C:\Windows\system32>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (No such file or directory))
finished. total time: 1.218s

no_trace said:
Can't relock my phone to apply the RUU?
C:\Windows\system32>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (No such file or directory))
finished. total time: 1.218s
Click to expand...
Click to collapse
you didn't need to relock for ruu

Why would you think you need to lock it? Luckily you are s-off, so unlocking is easy. But for god's sake don't put it to s-on. And you can go ahead and unlock it too.
---------- Post added at 09:45 PM ---------- Previous post was at 09:42 PM ----------
no_trace said:
Can't relock my phone to apply the RUU?
C:\Windows\system32>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (No such file or directory))
finished. total time: 1.218s
Click to expand...
Click to collapse
Here is how to fix it
Download an RUU file, this is an older one but it is signed and you can take otas afterwards to update to newest firmware etc
http://bit.ly/vzwone10
then put the file in your fastboot / adb directory, and rename it to Rom.zip
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip Rom.zip (rename file to Rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip Rom.zip
Then when it finishes, type "fastboot reboot"

ccarr313 said:
Why would you think you need to lock it? Luckily you are s-off, so unlocking is easy. But for god's sake don't put it to s-on. And you can go ahead and unlock it too.
---------- Post added at 09:45 PM ---------- Previous post was at 09:42 PM ----------
Here is how to fix it
Download an RUU file, this is an older one but it is signed and you can take otas afterwards to update to newest firmware etc
http://bit.ly/vzwone10
then put the file in your fastboot / adb directory, and rename it to Rom.zip
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip Rom.zip (rename file to Rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip Rom.zip
Then when it finishes, type "fastboot reboot"
Click to expand...
Click to collapse
Hello and thanks.
1)locking the bootloader failed, thankfully... got bad advice from a 4 year old post that I didn't realize...
2) "fastboot oem rebootRUU" has not been sending the phone into RUU mode with the silver HTC logo. It reboots and gives a blank illuminated screen after the HTC splash which is what happens when I try to boot the phone normally. I don't know why. Flashing doesn't seem to take here, got a couple <waiting for device> messages

no_trace said:
Hello and thanks.
1)locking the bootloader failed, thankfully... got bad advice from a 4 year old post that I didn't realize...
2) "fastboot oem rebootRUU" has not been sending the phone into RUU mode with the silver HTC logo. It reboots and gives a blank illuminated screen after the HTC splash which is what happens when I try to boot the phone normally. I don't know why. Flashing doesn't seem to take here, got a couple <waiting for device> messages
Click to expand...
Click to collapse
make sure you are in fastboot usb from bootloader menu. mine would say waiting for device, then i had to power it off then go into fastboot mode when powering off while holding volume down

no_trace said:
Hello and thanks.
1)locking the bootloader failed, thankfully... got bad advice from a 4 year old post that I didn't realize...
2) "fastboot oem rebootRUU" has not been sending the phone into RUU mode with the silver HTC logo. It reboots and gives a blank illuminated screen after the HTC splash which is what happens when I try to boot the phone normally. I don't know why. Flashing doesn't seem to take here, got a couple <waiting for device> messages
Click to expand...
Click to collapse
What?
Does anyone have any kind of advice? I wil GLADLY post any more information if it helps. THANKS

Help restoring stock for Three UK network?

Hello everyone, i was using DEV edition of Loli but today for some reason ive lost signal, the network shows unavailable, tried using SIM on iPhone that i had around working fine. Tried restoring to factory still same problem. So now want to send this back to Three or HTC for warranty but want to restore to Three UK factory firmware. Any tips?
my device Unlocked and S-Off

I'm getting FAILED (remote: 32 header error) when flashing from oem RUU screen

What is your current CID?

Deadeye* said:
I'm getting FAILED (remote: 32 header error) when flashing from oem RUU screen
Click to expand...
Click to collapse
If you're trying to flash the RUU ZIP you HAVE to use htc_fastboot.exe as the Google fastboot file can't flash the ZIP. You can get it here (I pulled it from the latest EU RUU)

at the moment i'm flashing from SD card, that finds that file automatically. my CID is 111111
When my network reception disappeared i was listening to spottily din't do anything to the phone and din't install anything that required Root for 3-4 weeks, not sure what happened

So tried that method still no luck, hopefuly they will take it in warranty

Post your fastboot getvar all (minus serial no. & imei no.)
I believe you need x.xx.771.x ROM and firmware version because your device is H3G, and I have all versions x.xx.771.x backups

I'm trying to relock my bootloader using this guide on my mac http://www.pocketables.com/2014/07/nondestructively-lockrelockunlock-s-htc-one-m7m8-bootloader.html
but when i do su i'm getting this error message:
/system/bin/sh: su: not found
127|[email protected]_m8:/ $
It same happens on windows

Getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_ul
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Deadeye* said:
I'm trying to relock my bootloader using this guide on my mac http://www.pocketables.com/2014/07/nondestructively-lockrelockunlock-s-htc-one-m7m8-bootloader.html
but when i do su i'm getting this error message:
/system/bin/sh: su: not found
127|[email protected]_m8:/ $
It same happens on windows
Click to expand...
Click to collapse
You need SuperSU installed to run that lock command
If you still have TWRP installed (not sure about other custom recovery), you can boot to recovery then run that command while in recovery (this way you don't need SuperSU installed)
just run adb shell
then that echo part
(only two commands)
Deadeye* said:
Getvar:
(bootloader) version-main: 4.16.401.10
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
With this EU WWE details, I don't know whether Three UK will accept your device under warranty ... someone else need to advise you as I'm not familiar with that region.
In my region ... if I have other Asia ROM even with LOCKED & S-ON status, they still cannot accept because the IMEI is registered under ASIA WWE which is x.xx.707.x

I'm in recovery now, but trying and getting this: error: device not found
Just to double check in bootloader i just select Recovery? or wait does it have to be Unofficial Recovery or HTC one?

This phone is going in HTC not Three so dont think that should cause any problems?

Sorted thanks, my device was showing Relocked so had to unlock it again. but now it shows Locket, now just need to get SD card and reinstall system, and send it to HTC only thing i have is S-Off so hope HTC wont be picky about this, because when i spoke to Support staff he did mention that unlocked bootloader will void warranty so not sure how to take on this

[Q] Unroot HTC One M8 Dual SIM

Hi, I have an HTC One M8 Dual SIM which I managed to root and s-off. I need to get this back to stock but am having some problems.
At the moment my phone is as follows:
Software Status: Official
***LOCKED***
M8_DUGL PVT SHIP S-OFF
CID-HTC__032
HBOOT-3.19.0.0000
OS-3.33.401.6
I have TWRP v2.8.4.0 installed as well
I have looked at the following thread http://forum.xda-developers.com/showthread.php?t=2735235 and managed to get the phone back to Software Status: Official and ***LOCKED*** I think but not managed to get S-ON or unrooted.
I have found firmware 3.33.401.6 for the M8 but not managed to find the actual stock OS.
Can someone point me in the right direction of what I need to do now?
This is the first time I have tried to unroot a device so sorry for anything I am missing from this post.
Thanks.

1. Do NOT S-ON unless the phone is 100% stock (and even then I wouldn't bother)
2. Flash the RUU in here - https://drive.google.com/file/d/0B17smFr95pleb3dJVDZVZTFfUEU/

EddyOS said:
1. Do NOT S-ON unless the phone is 100% stock (and even then I wouldn't bother)
2. Flash the RUU in here - https://drive.google.com/file/d/0B17smFr95pleb3dJVDZVZTFfUEU/
Click to expand...
Click to collapse
Thanks. I have downloaded and run and get the error "ERROR [130]: MODEL ID ERROR"
I followed the previous guide and think I may have used the wrong recovery image as the guide doesn't mention Dual SIM. So, I have downloaded recovery_1.54.401.10.img from here http://forum.xda-developers.com/showthread.php?t=2701376 and tried "fastboot flash recovery recovery_1.54.401.10.img" but get the following error:
sending 'recovery' (15236 KB)... OKAY
writing 'recovery'... FAILnot allowed
FAILED (remote: not allowed)
Execution time is 1(s)
Not sure if the recovery image is the problem or not however.
Any suggestions?
Thanks.

If you've relocked the bootloader it won't work. If you're getting the Model ID error it means you've changed your MID at some point. Can you connect your phone in fastboot and post the results of fastboot getvar all (leave out your IMEI and S/N)

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.30306251.27G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__032
(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: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 27(ms)
Thanks.

Back to being unlocked now by following htconeroot com again. After this, I have now been able to run the command "fastboot flash recovery recovery_1.54.401.10.img" to remove TWRP.
I have tried running the RUU EXE again but get the same issue. Is there anything you can suggest to get this fixed?
Thanks for the help.

Well, you've go the right Model ID, so do this...before we start make sure the RUU I linked to is named ruu.zip (not ruu.zip.zip!) and that you have htc_fastboot in the same location (if you don't have htc_fastboot you can get it here - https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/). Also make sure you've relocked the bootloader using fastboot oem lock
1. Connect phone in fastboot mode
2. Run fastboot oem rebootRUU to get into RUU mode
3. Open a command window in the location where the RUU and htc_fastboot are
4. Type htc_fastboot flash zip ruu.zip
5. Wait for it to finish
If you get any errors please post them up

With "fastboot oem lock" I received the following, however after a reboot of the phone it is showing as *** RELOCKED ***:
Code:
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
Execution time is 1(s)
"fastboot oem rebootRUU" worked fine:
Code:
... (bootloader) Start Verify: 0
OKAY
Execution time is 21(ms)
"fastboot flash zip ruu.zip" failed:
Code:
sending 'zip'... (46605 KB) OKAY
sending time = 2.308 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 2(s)

Hmmmm, I'm not sure. Never had an issue doing it before but never used the Dual-SIM model. Can't see it being any different, though

I appreciate the help.
Do you have a link to stock recovery for the Dual SIM M8 as not sure that is 100% at the moment - when I press on RECOVERY it just goes back to the FASTBOOT menu.
Thanks.

I don't, no. I've been trying to see if anyone has the OTA cause you can pull it from that but the RUU is encrypted so can't be pulled without decrypting the RUU (which I don't know how to do)

[M8s] How can i restore to 100% stock?

Hey folks,
i wrongly made a thread in the M8-forum, because i thought this smartphone was a M8, but it's a M8s.
Anyway, a friend of mine sent me his smartphone to repair but i'm sitting in a corner right now.
I never had a HTC before, not in my hands, not received by any other person - first try so far.
Here's the situation:
The battery from the smartphone was empty over a night.
Next day, when he want to start - it doesn't start and runs into bootloader.
He tried some things i think, but isn't really familiar with that.
Bootloader saying:
*** Software status: Modified ***
*** UNLOCKED ***
M8QL_UL PVT SHIP S-ON
Click to expand...
Click to collapse
I searched the web and found the original RUU (RUU[email protected]50408_15.00_016_F_release_450409_combined_signed.zip) which i already downloaded. Beside, i already unlocked the Bootloader via "Unlock_code.bin".
Some useful infromations:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.0.[email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **************
(bootloader) imei: **************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__102
(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: 1d456ef7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Click to expand...
Click to collapse
I don't really know how to restore this smartphone to 100% stock. Most of all Howtos describe M8 and that's not working at all.
Is someone familiar with that on M8s?
Can someone support me with this?

Okay, copied several zip-files to internal Samsung microSDXC EVO 64GB (exFAT) card, while renaming always to 0PKVIMG.zip but this phone won't eat any of these:
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.10_Radio_1.0.U20410.1@050408_15.00_016_F_release_450409_combined_signed.zip
Checking...
Wrong zipped image !
Device halted due to Large Image update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
RUU_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.10_Radio_1.0.U20410.1@050408_15.00_016_F_release_450409_combined_signed.zip
Checking...
Wrong zipped image !
Device halted due to Large Image update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
extracted rom.zip from RUU_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.10_Radio_1.0.U20410.1@050408_15.00_016_F_release_450409_combined_signed.zip
Checking...
Wrong zipped image !
Device halted due to Large Image update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1_Radio_1.0.U20410.1@50408_15.00_016_F_release_436156_signed.zip
Parsing...
Device halted due to Large Image update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1@60201_20.05_018_F_release_479349_combined_signed.zip
Checking...
Wrong zipped image !
Device halted due to Large Image update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
MD5Sums are always identical to the provided ones.
All zip-files comes from ruu.lalleman.net.
Read something about, the bootloader must be LOCKED/RELOCKED, but when i try, i get the following:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdif debug: 15
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
The phone reboots after that, but still says UNLOCKED.
Seem something is dead on that phone?
It always starts at bootloader.
Any hints!?

I don't have M8s only M8 but the basic is still the same.
You need a locked or relocked bootloader to proceed.
The RUU zip won't work on unlocked bootloader. The different that I noted is you need to use htc_fastboot mostly for M8s, M8 can run mostly on generic fastboot.
Try again .. use the htc_fastboot that you can find in this thread -
http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
htc_fastboot oem lock
htc_fastboot reboot-bootloader

I tried @ckpv5, doesn't work either.

Try what I suggested here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/help-request-t3439356
If it work, take it as temp fix. Need to find whether backup for 1.16.401.10 is available or not.
It's very late over here, I'll see anything I can find to help you tomorrow.

Thanks @ckpv5 !
Already tried flashing recoveries and all of them succeeded with:
sending 'recovery' (31014 KB)... OKAY
writing ''recovery'... OKAY
Execution time is 8(s)
Click to expand...
Click to collapse
After rebooting into bootloader and selecting RECOVERY, the phone reboot immediately to bootloader again.
For just a thousand of second i can see a white screen, with green htc and black android - logo.
Tried with:
twrp-recovery-2.8.6.0-m8s-qlul.img
twrp-2.8.7.0-m8s-qlul.img
twrp-3.0.2-0-m8.img
Always the same.

Oh ... that's bad. Without relocking bootloader you can't install RUU
and without TWRP installed you can restore a backup
I don't know whether these indicate some hardware problem.

Seems so.
Reading hundreds of tutorials and threads but all of them are different.
That's sad...
Anyway, thanks for your effort!

Hey guys,
i have also a problem with getting back to 100% stock.
I have restored my first backup with twrp and have the original rom. I can download the update for marshmallow.
When i want to install it the phone is restarting into bootloader with the following error message.
I think there is a problem with the recovery. I already tried the Vodafone UK & DE_CH recovery version.
The device is relocked. Somebody has an idea what i can do?
edit: sorry it should be the thumbnail
Greetings
realclone

realclone1000 said:
Somebody has an idea what i can do?
Greetings
realclone
Click to expand...
Click to collapse
The screenshot is too small to read what the error is.
If it is recovery error, you can adb pull the OTA and use the recovery that come from OTA to proceed.
As I said, the screenshot is too small, unable to read where the OTA is located on your device.

Short Update:
I tried again to run the RUU_M8_QL_UL_L50_SENSE60_Vodafone_UK_1.11.161.1_Radio_1.0.U20410.1G50408_15.00_016_F_release_430447_signed via ARUWizard.exe and now it worked.
So it was a downgrade, but after 2 Software updates i finally installed the Marshmallow update.
In my Opinion it's faster and the battery stays longer.
Now Nougat can come

HTC m8 phone keeps booting into fastboot mode

hello,
after root my phone
every time i try to put it in recovery mode it goes back to fastboot mode ..
even if i tried to flash a recovery on it , it would boot to fastboot mode
even when trying to install a official htc software update it just boots into fastboot ..
now i want to get it back to stock..
please help me !!

Need more info.
What version SuperSU? What version TWRP?
What "official update" file did you use? Was it an OTA or an RUU (list the exact file name)?
Also, do fastoboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
Need more info.
What version SuperSU? What version TWRP?
What "official update" file did you use? Was it an OTA or an RUU (list the exact file name)?
Also, do fastoboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
HI
Pls refer Bellow details
C:\miniadb_v1031>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.213311771.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.82.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mels_tuhl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B81000
(bootloader) cidnum: HTC__J15
(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: 8d01ca6e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s

In addition to the fastboot output, I asked 4 questions, none of which you answered.
You have the M8 eye, not the "standard" M8. Far as I can tell (not many folks on xda have the "eye") you need a special version of TWRP for this version. You can try the right version TWRP, and flash SUperSU again, see if that helps. No idea if this version TWRP will work on not (can't personally vouch for it): https://forum.xda-developers.com/htc-one-m8/general/m8-eye-recovery-root-t3159648
Depending on what you did to the phone by flashing the wrong TWRP, it's hard to tell what the proper way to proceed.

redpoint73 said:
In addition to the fastboot output, I asked 4 questions, none of which you answered.
You have the M8 eye, not the "standard" M8. Far as I can tell (not many folks on xda have the "eye") you need a special version of TWRP for this version. You can try the right version TWRP, and flash SUperSU again, see if that helps. No idea if this version TWRP will work on not (can't personally vouch for it): https://forum.xda-developers.com/htc-one-m8/general/m8-eye-recovery-root-t3159648
Depending on what you did to the phone by flashing the wrong TWRP, it's hard to tell what the proper way to proceed.
Click to expand...
Click to collapse
Hi
It's work
Thanks for your support

redpoint73 said:
In addition to the fastboot output, I asked 4 questions, none of which you answered.
You have the M8 eye, not the "standard" M8. Far as I can tell (not many folks on xda have the "eye") you need a special version of TWRP for this version. You can try the right version TWRP, and flash SUperSU again, see if that helps. No idea if this version TWRP will work on not (can't personally vouch for it): https://forum.xda-developers.com/htc-one-m8/general/m8-eye-recovery-root-t3159648
Depending on what you did to the phone by flashing the wrong TWRP, it's hard to tell what the proper way to proceed.
Click to expand...
Click to collapse
hi
can i have stock recovery download link in that phone pls

I have a similar issue, but with a standard M8
£10 off ebay, so not expecting ,much (also means no known history) . 1 week old noob reading here and flashing phones
1) only boots to fastboot, and even does this when you leave it powered off, but charging.
2) select hboot, then to recovery, recovery doesn't run, just resets back to fastboot eventually, after screen goes white not black.
3) can partially speak to phone in fastbook and get versions ok (included below)
Getver all as below:
C:\Program Files (x86)\Minimal ADB and Fastboot>
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA615WM01404
(bootloader) imei: 357336060194484
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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.114s
4) never been able to boot to full o/s so not in developer mode, so cant get response in adb (and dont know how to use this anyway)
5) tried RUU.exe - fails with usb error after it tries to restart bootloader
6) tried ruu.zip from memory card - fails with partition update fail
7) tried fastboot recovery image 6.12.401.4 and it fails to write - error is 'remote:signature verify fail'
8) random google lead me to fastboot oem reboot RUU which does this:
E:\android tools>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.052s]
finished. total time: 10.053s
9) htcdev unlock bootloader didnt work initially but has done now - is this a path i should try?
aim is to get a standard phone working again
Thanks
G

ok got my unlock token, seemed to flash it, but no status change/reaction on phone and rebooting still shows locked
E:\android tools>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.125s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ -0.000s]
finished. total time: 0.125s
G

My responses to some of your points below, in red font:
gda_scooby said:
(bootloader) version-main: 6.12.401.4
4) never been able to boot to full o/s so not in developer mode, so cant get response in adb (and dont know how to use this anyway) That is correct, you will not be able to use adb unless you can boot to OS or alternately TWRP custom recovery. So you are basically limited to fastboot in the current condition.
5) tried RUU.exe - fails with usb error after it tries to restart bootloader There isn't a valid exe format RUU for your version number (6.12.401.4) so you are probably using the wrong RUU. What is the version number or file name for the RUU.exe?
6) tried ruu.zip from memory card - fails with partition update fail Exactly what partition(s) is it failing to update? What is the version RUU you are using? The only valid one for your version would be the RUU.zip from here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
7) tried fastboot recovery image 6.12.401.4 and it fails to write - error is 'remote:signature verify fail' You can't flash an unsigned recovery image, unless the bootloader is unlocked. It also seems you are trying to flash stock recovery, and I don't see how that is going to help your current condition.
Click to expand...
Click to collapse
I think your best bet right now, is to try the correct RUU.zip which I linked above.