Develop Bugs

[Q] I have tried everything! Recovery will not load!

Hello, I have a verizon htc one m7. I am rooted and s-off.
1: getvar info
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
2: In the the bootloader screen if I choose recovery the phone tries to load twrp screen goes to entering recovery goes black then the entering recovery screen comes back up and stays until I power down:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3: I have tried fastboot, flashify, rom toolbox pro and linux to flash twrp images. every one of them does so without error, yet I can not get into twrp. The md5 on every file I have tried to flash checked out ok.
4: I installed the ruu from dottat kitkat 4.4.2 and 4.4.3 and installed the ruu version of twrp 2.7.0.8 and 2.7.1.12 and still recovery does not load. This is after installing an ruu and wipes the phone completely.
5:I have tried everything that has been suggested including running the commands from a linux terminal.
If anybody knows how to fix this please help!

vaping redhead said:
Hello, I have a verizon htc one m7. I am rooted and s-off.
1: getvar info
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
2: In the the bootloader screen if I choose recovery the phone tries to load twrp screen goes to entering recovery goes black then the entering recovery screen comes back up and stays until I power down:
3: I have tried fastboot, flashify, rom toolbox pro and linux to flash twrp images. every one of them does so without error, yet I can not get into twrp. The md5 on every file I have tried to flash checked out ok.
4: I installed the ruu from dottat kitkat 4.4.2 and 4.4.3 and installed the ruu version of twrp 2.7.0.8 and 2.7.1.12 and still recovery does not load. This is after installing an ruu and wipes the phone completely.
5:I have tried everything that has been suggested including running the commands from a linux terminal.
If anybody knows how to fix this please help!
Click to expand...
Click to collapse
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?

jpradley said:
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
Click to expand...
Click to collapse
they are in zip format and can be downloaded from dottat thread in the developer section. you use the command fasboot flash zip "filename"
http://forum.xda-developers.com/verizon-htc-one/development/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643
http://forum.xda-developers.com/showthread.php?t=2765784

vaping redhead said:
they are in zip format and can be downloaded from dottat thread in the developer section. you use the command fasboot flash zip "filename"]
Click to expand...
Click to collapse
OK, thanks.
But what's wrong with the file format that most everyone uses for a recovery installation, which isn't a *zip file, but a *img file?

jpradley said:
OK, thanks.
But what's wrong with the file format that most everyone uses for a recovery installation, which isn't a *zip file, but a *img file?
Click to expand...
Click to collapse
It is my understanding that img files can be flashed directly from fastboot or flashify etc. the zip file contains the image file and also a txt file and can only be flashed while your phone is in ruu mode "fastboot oem rebootRUU"
since there is 2 files that it why it is zipped. the txt file contained in there is the istructions that tell the rom update utility how to flash the enclosed recovery image file.

jpradley said:
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
Click to expand...
Click to collapse
Fastboot erase cache
Then flash your recovery again and see what you have.

dottat said:
Fastboot erase cache
Then flash your recovery again and see what you have.
Click to expand...
Click to collapse
I have tried that command, it does not solve recovery not loading. Trust me I have tried every suggestion I can find on the internet and nothing solves this. I am hoping someone out there has knowledge of exaclty how the recovery partition works because at this point it would appear that the recovery partition on my phone is either not being written to or is corrupted.

vaping redhead said:
I have tried that command, it does not solve recovery not loading. Trust me I have tried every suggestion I can find on the internet and nothing solves this. I am hoping someone out there has knowledge of exaclty how the recovery partition works because at this point it would appear that the recovery partition on my phone is either not being written to or is corrupted.
Click to expand...
Click to collapse
When you flash the ruu mode twrp put a -w on the end of the command.

dottat said:
When you flash the ruu mode twrp put a -w on the end of the command.
Click to expand...
Click to collapse
I will try. Here are the results
c:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
c:\adb>fastboot flash zip M7_RUU_TWRP.zip -w
target reported max download size of 1514139648 bytes
sending 'zip' (9360 KB)...
OKAY [ 1.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.179s]
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 4.250s
Revovery still does not load.

vaping redhead said:
I will try. Here are the results
c:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
c:\adb>fastboot flash zip M7_RUU_TWRP.zip -w
target reported max download size of 1514139648 bytes
sending 'zip' (9360 KB)...
OKAY [ 1.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.179s]
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 4.250s
Revovery still does not load.
Click to expand...
Click to collapse
Failed (remote not allowed)
Is a sure sign that something isn't set up right for flashing to the device.
It will never work if that is the result in terminal.
Are you using Usb 2.0 and the original data cable that is meant for the device?
I think you probably never successfully flashed any recovery.
I would advise trying a cable meant for this device.

santod040 said:
Failed (remote not allowed)
Is a sure sign that something isn't set up right for flashing to the device.
It will never work if that is the result in terminal.
Are you using Usb 2.0 and the original data cable that is meant for the device?
I think you probably never successfully flashed any recovery.
I would advise trying a cable meant for this device.
Click to expand...
Click to collapse
I am using the htc cable that came with the phone. I will double check that I am using USB 2.0 and try a different cable.
I also noticed wihen flashing with rom toolbox pro is says successful yet also says #error: cannot locate recovery partition
Is it possible my recovery partitiion is not there?

I just tried several cables including the the one from htc. I also made sure I was using a usb 2.0 port. I still get the failed(remote not allowed)
Thank you for the help btw.

Hi, I think I have figured this one out. I changed my phone from blue to red. Verizon only offers silver or blue. Anyway I thought I might have damaged my motherboard, So I bought a silver verizon htc one off ebay with a cracked screen. (easy fix). So I swapped the hardware from the silver to my red and with a new board in the red shell twrp does not load. However my old board wich twrp would not load on is now in the silver shell and twrp now loads. Bottom line the red shell is the problem.

vaping redhead said:
Hi, I think I have figured this one out. I changed my phone from blue to red. Verizon only offers silver or blue. Anyway I thought I might have damaged my motherboard, So I bought a silver verizon htc one off ebay with a cracked screen. (easy fix). So I swapped the hardware from the silver to my red and with a new board in the red shell twrp does not load. However my old board wich twrp would not load on is now in the silver shell and twrp now loads. Bottom line the red shell is the problem.
Click to expand...
Click to collapse
Update. The red shell is 100% to blame for recovery software not loading. I did some more tinkering with two m7 motherboards and in a stock verizon silver shell twrp loads. Both board when in the red shell, twrp does not load.
If anyone out there was thinking of converting their blue or silver verizon m7 to a different color. Be warned that your recovery software will probably not load once you transfer the hardware over to the new shell.
I guess if I want a red htc one that twrp works on, I have to get a m8

vaping redhead said:
Update. The red shell is 100% to blame for recovery software not loading. I did some more tinkering with two m7 motherboards and in a stock verizon silver shell twrp loads. Both board when in the red shell, twrp does not load.
If anyone out there was thinking of converting their blue or silver verizon m7 to a different color. Be warned that your recovery software will probably not load once you transfer the hardware over to the new shell.
I guess if I want a red htc one that twrp works on, I have to get a m8
Click to expand...
Click to collapse
Or just.... Paint it with a good quality modeling paint (like you buy for model cars, boats, etc). It is durable and lasts if you know how to coat it correctly.
Sent from my HTC6500LVWBLU using XDA Free mobile app

Doesn't seem to me that you solved the initial problem, just found a work around for it. I have the same problem with my phone not accepting the stock recovery for what ever reason. It will, however, accept the TWRP recovery, but this doesn't do me any good wrt warranty returns. before I S-On and Lock it, I need to have the stock recovery installed.

gryghst72 said:
Doesn't seem to me that you solved the initial problem, just found a work around for it. I have the same problem with my phone not accepting the stock recovery for what ever reason. It will, however, accept the TWRP recovery, but this doesn't do me any good wrt warranty returns. before I S-On and Lock it, I need to have the stock recovery installed.
Click to expand...
Click to collapse
Have you tried ruu? That should flash the stock recovery and everything else stock. Need to ruu when you s-on to ensure everything is okay before turning secure flag on.
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uzephi said:
Have you tried ruu? That should flash the stock recovery and everything else stock. Need to ruu when you s-on to ensure everything is okay before turning secure flag on.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
I have RUU'd the following and in different orders:
5.28.605.2_NoBoot-IMG_firmware.zip
VZW.M7.5.28.605.2.PN0731IMG.zip
as well as "fastboot flash recovery 5.28.605.2_Stock_recovery.img"
all with a scattering of "fastboot erase cache".
The flash says it is successful, but when I boot to recovery, the screen graphics are garbage and when not garbage, it's the ! droid after the usual 15-20 sec blank screen. When I flash TWRP either via flash recovery or RUU that takes and works just fine. But this obviously isn't a "back to stock" set up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3899mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.164s
Thoughts?

gryghst72 said:
I have RUU'd the following and in different orders:
5.28.605.2_NoBoot-IMG_firmware.zip
VZW.M7.5.28.605.2.PN0731IMG.zip
as well as "fastboot flash recovery 5.28.605.2_Stock_recovery.img"
all with a scattering of "fastboot erase cache".
The flash says it is successful, but when I boot to recovery, the screen graphics are garbage and when not garbage, it's the ! droid after the usual 15-20 sec blank screen. When I flash TWRP either via flash recovery or RUU that takes and works just fine. But this obviously isn't a "back to stock" set up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3899mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.164s
Thoughts?
Click to expand...
Click to collapse
Have you tried the 2.x.y.z signed ruu in santod's stock Rom/firmware thread? Unsigned ruus are good, but sometimes a signed, official ruu gets the job done that unofficial ones can't.
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uzephi said:
Have you tried the 2.x.y.z signed ruu in santod's stock Rom/firmware thread? Unsigned ruus are good, but sometimes a signed, official ruu gets the job done that unofficial ones can't.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Is the signed one located here? I have not only because I have not read that one can go backwards, especially that far back. Can this be done successfully? What are the risks? Does the signed RUU contain all he necessary files to restart after the flash, are there any supporting flashes necessary (HBOOT, Recovery, Radios, etc.) Is this a viable solution or a shot in the dark which could brick the device?
Thanks for the on-going troubleshooting. I'm not trying to be a pain, just being careful since I am unfamiliar with the bootload/security features build into the system.
---------- Post added at 03:33 PM ---------- Previous post was at 02:58 PM ----------
I tried to RUU flash the 1.10.605.10 version .. here was my result:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Android>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 44.569s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 51.044s
C:\Android>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 44.632s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 51.075s
C:\Android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.031s
Well, that didn't do anything, good or bad. Just didn't take and phone operates just fine as a phone, but still no recovery image, stock or otherwise.
Downloading 2.x.y.z signed version now. Will report the results after flash attempt.
Same results:
C:\Android>adb reboot-bootloader
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Android>fastboot flash zip RUU_2_10_605_1.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1232586 KB)...
OKAY [ 41.931s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 48.420s

[SOLVED]Can't unlock relocked bootloader after 4.16.401.10 update (OS Not working)

Hello all,
I'm having a bit of a time rectifying this problem, and my usual Google/XDA searches haven't unfortunately bore any fruit.
The problem in a nutshell:
I unlocked my phone via HTC Dev, it was S-Off, and bootloader was unlocked.
I was using Viper Rom, last one before their 4.0/4.1 Lollipop release - no prroblems.
I was using an older 3.X firmware (I forget which - probably inconsequential in any case).
I wiped my phone in preparation for installing the 4.1 Rom with TWRP.
I installed the new Rom via TWRP, I wiped again with the Rom's wiper.
I rebooted my phone after a successful wipe.
I booted into the rom, but a whole bunch of processes failed (com.android ones), however I was able to, at this point, get into my wifi and set up my accounts etc.
After this, I had a black screen, though my notification bar etc. were there.
I thought it might be a firmware issue, and so I used fastboot RUU to install the firmware version 4.16.401.10. Everything was fine, and it has flashed successfully.
Unfortunately, the bootloader is now once again locked (relocked, to be exact), and I can't boot back into the Rom OS to run adb commands to unlock it once again.
Fastboot commands such as flash unlocktoken are met with fails.
I have no idea how to proceed from this point forwards.
So, I'd appreciate any and all help at this point to get me back up and running again! Maybe I'll learn something along the way too
Thanks in advance!
edit: Ah yes, here is my getvar information:
(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: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(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

Can you post the error you get when trying to unlock the phone?
You don't actually need to be unlocked to flash a custom recovery, you just flash a ZIP via RUU mode (it's what I do on the rare occasion I want to root my phone to try something)

Sure, which error are you talking about?
When trying to use my unlock token, I get the following:
target reported max download size of 1826152448 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.135s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
Click to expand...
Click to collapse
I thought there was a fastboot oem unlock, but as it turns out, there isn't.
When trying to flash TWRP 2.8.5.0 (mine is an international UK/EU version, not sprint or verizon or tmobile, carrier SIM unlocked) - I get:
target reported max download size of 1826152448 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.683s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.689s
Click to expand...
Click to collapse
Do you require any additional information?
Thank you for the quick response to my plight!
Edit: Oh, do I have to be in RUU mode to install TWRP? If so, that might be my noobish mistake!
Edit2: nope, RUU mode won't let me do it either
target reported max download size of 1826418688 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.698s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.704s
Click to expand...
Click to collapse

For example, you could flash this ZIP file in RUU mode for the latest TWRP and keep the bootloader locked:
https://www.hightail.com/download/UlRTcXlpOC9iV3hMWE1UQw
You shouldn't have to be in RUU mode, I just made this ZIP to flash TWRP with a locked bootloader

Thank you for this, however I'm getting the same error.
Am I doing this correctly?
(Using Ubuntu)
Terminal command: sudo fastboot oem rebootRUU
Wait for silver HTC logo on phone screen.
(After unzipping the recovery.img file) sudo fastboot flash recovery recovery.img
Same error as above -
target reported max download size of 1826418688 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.735s]
writing 'recovery'...
FAILED (remote: not allowed)
Click to expand...
Click to collapse

fastboot flash recovery recovery.img <--- wrong
fastboot flash zip recoveryRUU.zip <--- this one

I love you man! Thank you so much!
Worked, TWRP reinstalled, happy days!
For my own knowledge, why did using 'flash recovery' not work? And why did using RUU and flashing the zip work?
Thank you

Because you can't flash partitions in RUU mode, only ZIP files
Individual partitions are flashed in fastboot but you need the bootloader unlocked to do that

Nicely put, thank you. I'll remember all this for future.
Thanks again both!

What you can do now, though, is lock/unlock the bootloader from TWRP...
1. Boot into TWRP
2. Connect phone to your PC (make sure drivers are installed and that your device is recognised when you type adb devices)
3. Get into the shell by typing adb shell
4. Type the following command to unlock the bootloader (probably best to copy/paste this):
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5. Exit shell by typing exit
6. Reboot phone to the bootloader and check you're now 'unlocked'
Parts taken from this thread by @scotty1223 - http://forum.xda-developers.com/showthread.php?t=2708571

EddyOS said:
Can you post the error you get when trying to unlock the phone?
You don't actually need to be unlocked to flash a custom recovery, you just flash a ZIP via RUU mode (it's what I do on the rare occasion I want to root my phone to try something)
Click to expand...
Click to collapse
EddyOS said:
What you can do now, though, is lock/unlock the bootloader from TWRP...
1. Boot into TWRP
2. Connect phone to your PC (make sure drivers are installed and that your device is recognised when you type adb devices)
3. Get into the shell by typing adb shell
4. Type the following command to unlock the bootloader (probably best to copy/paste this):
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5. Exit shell by typing exit
6. Reboot phone to the bootloader and check you're now 'unlocked'
Parts taken from this thread by @scotty1223 - http://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Hey, thank you! Sorry, I didn't look back on my topic once I'd managed to solve it. Cheers for the instructions!

HeadKandy said:
Hey, thank you! Sorry, I didn't look back on my topic once I'd managed to solve it. Cheers for the instructions!
Click to expand...
Click to collapse
This is new information for me... And I'm stuck too wanting to root..but don't want to use the htcdev token and want to install TWRP.
Q#1: Do I put the recoveryRUU.zip in the platform-tools directory?
Q#2: What is RUU mode? I've done plenty of things in fastboot (flashed recoveries before...I guess I didn't realize I was flashing a partition)... So the whole RUU thing is confusing me. Aren't you just rebooting into fastboot and flashing that zip?
I see the correct commands above, but I just want to confirm what I'm doing exactly.
Thank you very much in advance!

syntropic said:
This is new information for me... And I'm stuck too wanting to root..but don't want to use the htcdev token and want to install TWRP.
Q#1: Do I put the recoveryRUU.zip in the platform-tools directory?
Q#2: What is RUU mode? I've done plenty of things in fastboot (flashed recoveries before...I guess I didn't realize I was flashing a partition)... So the whole RUU thing is confusing me. Aren't you just rebooting into fastboot and flashing that zip?
I see the correct commands above, but I just want to confirm what I'm doing exactly.
Thank you very much in advance!
Click to expand...
Click to collapse
1. Yes
2. It's the mode used to flash the RUU - fastboot oem rebootRUU

EddyOS said:
1. Yes
2. It's the mode used to flash the RUU - fastboot oem rebootRUU
Click to expand...
Click to collapse
Ok... I guess when I hear RUU I think of the .exe run in Windows to update or restore to factory. Didn't know there was a "mode".
But thanks! I'll put your zip in platform-tools, and then run the above commands.
How is the zip created? Is that something I can do fairly easily?

No. It's extracted from the EXE version of the RUU and in encrypted by HTC (unless you have the right tools to hack it)

EddyOS said:
No. It's extracted from the EXE version of the RUU and in encrypted by HTC (unless you have the right tools to hack it)
Click to expand...
Click to collapse
What tools do I need? Like a disassembler or Ollydbg?
[deleted earlier self-solved error]
---------- Post added at 01:28 PM ---------- Previous post was at 01:02 PM ----------
This is quite frustrating.... I am not sure why I am finding so many obstacles to what looked like an effortless way to flash a custom recovery...
I ran the fastboot flash zip recoveryRUU.zip
and received the following response from adb.
target reported max download size of 1826418688 bytes
sending 'zip' (12223 KB)...
OKAY [ 1.440s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 3.869s
Any idea what "41 model id check fail" could mean?? It doesn't sound good.
I researched this and it looks like it has something to do with the a version mismatch or something. Not sure.
I ran getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.531.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: ********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 06f11f5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
and noticed that my bootloader and HeadKandy's bootloader are different... could that be the problem?
Above you said you created the recoveryRUU.zip from an HTC RUU. So could the variant of the RUU you used to create that zip be the issue??
I appreciate any help as I would love to root this without having to use HTCDEV token to unlock the bootloader.
This is a very interesting and cool way to get around having to unlock the boot loader with a HTC token, but flashing a zip containing the custom recovery requires that I create that zip...which I have no idea how to do.
Is there any source for any custom recovery that's in a flashable zip format already?? If so, I could use that, then root it/unlock bootloader and then install TWRP.

syntropic said:
What tools do I need? Like a disassembler or Ollydbg?
[deleted earlier self-solved error]
---------- Post added at 01:28 PM ---------- Previous post was at 01:02 PM ----------
This is quite frustrating.... I am not sure why I am finding so many obstacles to what looked like an effortless way to flash a custom recovery...
I ran the fastboot flash zip recoveryRUU.zip
and received the following response from adb.
target reported max download size of 1826418688 bytes
sending 'zip' (12223 KB)...
OKAY [ 1.440s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 3.869s
Any idea what "41 model id check fail" could mean?? It doesn't sound good.
I researched this and it looks like it has something to do with the a version mismatch or something. Not sure.
I ran getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.531.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: ********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 06f11f5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Sorry, I thought you were the OPand noticed that my bootloader and HeadKandy's bootloader are different... could that be the problem?
Above you said you created the recoveryRUU.zip from an HTC RUU. So could the variant of the RUU you used to create that zip be the issue??
I appreciate any help as I would love to root this without having to use HTCDEV token to unlock the bootloader.
This is a very interesting and cool way to get around having to unlock the boot loader with a HTC token, but flashing a zip containing the custom recovery requires that I create that zip...which I have no idea how to do.
Is there any source for any custom recovery that's in a flashable zip format already?? If so, I could use that, then root it/unlock bootloader and then install TWRP.
Click to expand...
Click to collapse
Sorry, I thought you were the OP! That RUU won't work at all as you have to be on x.xx.401.x to flash it (it's the EU RUU, yours looks like T-Mobile)

syntropic said:
This is quite frustrating.... I am not sure why I am finding so many obstacles to what looked like an effortless way to flash a custom recovery...
Click to expand...
Click to collapse
I don't find this surprising at all. You are trying to flash a custom recovery with a locked bootloader. And one of the whole points (arguably the main point) of the locked bootloader is to prevent installing custom recovery.
A locked bootloader means you can only flash something that is properly signed, meaning it also has to pass the CID, MID checks. Since the zip you are trying to flash is not for your CID, you will get a fail.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Unlocking bootloader a second time did it!
Hi there,
yesterday a friend of mine came around and told me he tried to update from AHRD 3.28.401.9 to 4.16.401.10.
He told me he followed the guides but he end up in a working ARHD Lollipop - but without the ability
to flash anything via fastboot ('ERROR' remote:not allowed) while having bootloader 'RELOCKED'.
He also tried to update to the lastest firmware - FUU as well - but without success.
I tried alot to fix it - but also without success.
The last option and idea I had was to unlock the bootloader at HTCDEVs a second time.
I did it like described in the public tuts around here at XDA.
AND IT WORKED !
This might not work in every case - but it is an option since your bootloader is already unlocked and because this might be you last option
As usual -> I am not responsible for bricked devices ... etc, if you try this!
Regards,
brush2
Here is the final result of fastboot getvar all (bootloader is now 'UNLOCKED'):
Code:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main: 4.16.401.10
version-misc: PVT SHIP S-OFF
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__001 (HTC_102 originally)
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0

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

[Q] Stuck in Tampered with BL Locked and S-On [SOLVED]

Hello Android geeks! I am a novice Android user and have got myself a big problem!
I had a rooted phone with a custom recovery and a custom rom. Trying to return it to stock conditions (to sell), I did the following:
- Flashed the stock rom using the following RUU: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
- Relocked the BL
- Used the revone tool to change "relock" to "lock" and then to S-On
Now I am stuck at the screen that says Tampered and Locked with S-on. I try rebooting the phone or going to recovery, and I end up here again! I have researching it from this morning and tried several things without any luck! Here are some more details:
HBOOT-1.61.0000
RADIO-1.13.41.1209
Your help is really really appreciated!

SalmanMa said:
Hello Android geeks! I am a novice Android user and have got myself a big problem!
I had a rooted phone with a custom recovery and a custom rom. Trying to return it to stock conditions (to sell), I did the following:
- Flashed the stock rom using the following RUU: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
- Relocked the BL
- Used the revone tool to change "relock" to "lock" and then to S-On
Now I am stuck at the screen that says Tampered and Locked with S-on. I try rebooting the phone or going to recovery, and I end up here again! I have researching it from this morning and tried several things without any luck! Here are some more details:
HBOOT-1.61.0000
RADIO-1.13.41.1209
Your help is really really appreciated!
Click to expand...
Click to collapse
That's not an ruu
Show me the output of fastboot getvar all
Edit out the serial number and imei

dottat said:
That's not an ruu
Show me the output of fastboot getvar all
Edit out the serial number and imei
Click to expand...
Click to collapse
Thanks a lot for responding! Here it is:
Code:
c:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.13.41.1209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.22.605.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) meid: XXXX
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3750mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s

SalmanMa said:
Thanks a lot for responding! Here it is:
Code:
c:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.13.41.1209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.22.605.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) meid: XXXX
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3750mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s
Click to expand...
Click to collapse
Install HTC sync. Boot phone to fastboot mode. Connect to PC. Wait for phone to be read and click repair in the sync app. This will repair ruu your phone. Tampered will be gone and phone will be 100% stock.

dottat said:
Install HTC sync. Boot phone to fastboot mode. Connect to PC. Wait for phone to be read and click repair in the sync app. This will repair ruu your phone. Tampered will be gone and phone will be 100% stock.
Click to expand...
Click to collapse
HTC Sync does not detect the phone!

SalmanMa said:
HTC Sync does not detect the phone!
Click to expand...
Click to collapse
Check device manager. Likely you need to force update the driver that's installed for your phone to the latest which should be in c:/program files / HTC/ drivers
Sent from my HTC6535LVW using Tapatalk

dottat said:
Check device manager. Likely you need to force update the driver that's installed for your phone to the latest which should be in c:/program files / HTC/ drivers
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
The drivers were the latest. I reinstalled the Sync Manager with the drivers, and still no luck. Please see the screen shots below. It shows "no phone connected" in the lower left, but shows a phone without any information on the right (it disappears when I disconnect the phone). When I go to repair, I see the screen on the bottom and cannot do anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

SalmanMa said:
The drivers were the latest. I reinstalled the Sync Manager with the drivers, and still no luck. Please see the screen shots below. It shows "no phone connected" in the lower left, but shows a phone without any information on the right (it disappears when I disconnect the phone). When I go to repair, I see the screen on the bottom and cannot do anything.
Click to expand...
Click to collapse
Alright. So you will need to manually flash this ruu. Download and rename file to rom.zip
https://www.androidfilehost.com/?fid=24052804347761412
To be successful you will need to use the following version of fastboot. Your old sdk version will not work.
https://www.androidfilehost.com/?fid=95784891001612150
Unzip this folder and drag the ruu into the newly created folder. Hold shift and right click inside the newly created folder and hit "open cmd prompt here".
Run the following commands
HTC_fastboot oem rebootRUU
HTC_fastboot flash zip rom.zip
Allow cmd above to fully finish. Once complete issue the following cmd to reboot
HTC_fastboot reboot
Sent from my HTC6535LVW using Tapatalk

dottat said:
Alright. So you will need to manually flash this ruu. Download and rename file to rom.zip
To be successful you will need to use the following version of fastboot. Your old sdk version will not work.
Unzip this folder and drag the ruu into the newly created folder. Hold shift and right click inside the newly created folder and hit "open cmd prompt here".
Run the following commands
HTC_fastboot oem rebootRUU
HTC_fastboot flash zip rom.zip
Allow cmd above to fully finish. Once complete issue the following cmd to reboot
HTC_fastboot reboot
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
The good news is it is finally doing something. All I got with other RUUs was signature checking failed.
The bad news is after a quick restart (you can see it in the log), it has been stuck here for about 15 minutes now. I will leave it be to see if it gets anywhere. I will update the post then!
Code:
C:\HTC_fastboot_adb>HTC_fastboot flash zip rom.zip
sending 'zip'... (46522 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (FA37TS921762)...
< waiting for device >
sending 'zip'... (46522 KB)

SalmanMa said:
The good news is it is finally doing something. All I got with other RUUs was signature checking failed.
The bad news is after a quick restart (you can see it in the log), it has been stuck here for about 15 minutes now. I will leave it be to see if it gets anywhere. I will update the post then!
Code:
C:\HTC_fastboot_adb>HTC_fastboot flash zip rom.zip
sending 'zip'... (46522 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (FA37TS921762)...
< waiting for device >
sending 'zip'... (46522 KB)
Click to expand...
Click to collapse
Unplug phone and replug it.
Start that exact cmd over again.
Sent from my HTC6535LVW using Tapatalk

dottat said:
Unplug phone and replug it.
Start that exact cmd over again.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Thanks to you, my phone is back alive!! I think the problem was the HTC Sync intervening when the phone automatically rebooted. After I uninstalled the HTC Sync, it went through seamlessly, and after the final reboot, my phone was quickly up and running!
Now, out of curiosity, I want to know:
- What I did wrong in the first place that got me stuck there?
- Why all the RUUs I tried failed?
- And where you got this RUU from?
Thank you so much again!

SalmanMa said:
Thanks to you, my phone is back alive!! I think the problem was the HTC Sync intervening when the phone automatically rebooted. After I uninstalled the HTC Sync, it went through seamlessly, and after the final reboot, my phone was quickly up and running!
Now, out of curiosity, I want to know:
- What I did wrong in the first place that got me stuck there?
- Why all the RUUs I tried failed?
- And where you got this RUU from?
Thank you so much again!
Click to expand...
Click to collapse
Specifically to flash a signed ruu you just use HTC fastboot. Regular fastboot doesn't understand htc's [email protected] format that really has it split into about 7 different zip files. You probably noticed it sending system at least 5 times. That's because it's split up.
Sent from my HTC6535LVW using Tapatalk

SalmanMa said:
Thanks to you, my phone is back alive!! I think the problem was the HTC Sync intervening when the phone automatically rebooted. After I uninstalled the HTC Sync, it went through seamlessly, and after the final reboot, my phone was quickly up and running!
Now, out of curiosity, I want to know:
- What I did wrong in the first place that got me stuck there?
- Why all the RUUs I tried failed?
- And where you got this RUU from?
Thank you so much again!
Click to expand...
Click to collapse
Great to see you up and running .... :good:
Can you add 'SOLVED' to the thread title ....
Thx Josh

lj50036 said:
Great to see you up and running .... :good:
Can you add 'SOLVED' to the thread title ....
Thx Josh
Click to expand...
Click to collapse
Thank you for reminding me!

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.