Develop Bugs

[Q] STUCK with HTC logo and 4 triangles in corners

Need some help daorderdillon...I have an HTC One M8
I wanted to flash to the UNROOTED Google Play Edition...so I rooted, TWRP'ed and did the S-OFF
and then tried to flash the ROM while in RUU mode...it gave me back a "41 error"...
so I tried to change the ModelID in the android.txt file...flashed, and then my HTC One M8 kept going into the HTC logo screen with 4 triangle error screen
When I do fastboot oem reboot, it gets me back into the device - but any normal restart after, and I'm back in the HTC logo error screen
I can't go into recovery mode either - using the POWER and UP / DOWN buttons or through the software...
Stuck, and I really don't know what to do
Thanks in advance!

wikwikwik said:
I've looked everyone and really need some help now
I've done the following steps to try and convert my Asia HTC One M8 to the Google Play Edition
Rooted the phone
Did the S-Off
The final flash using the ROM didn't work - so I tried changing the MODELID, and then the 4 warning triangles started to show up
I don't know what to do...so if you can help me with detailed steps to fix and get back to the stock ROM - that would be greatly appreciated
Thanks in advance
Click to expand...
Click to collapse
Do volume up and power when starts to reboot hold power volume down to get back to recovery

jaythenut said:
Do volume up and power when starts to reboot hold power volume down to get back to recovery
Click to expand...
Click to collapse
I tried that multiple times...but still gives me the HTC logo with the 4 triangles...
Don't know what else to do...
Thanks for your help...

Which network was the phone on?
The phone has a corrupt boot loader. You need to flash the correct firmware and then you will be able to boot into the boot loader.
Sent from my HTC One_M8 using Tapatalk

While you were trying to flash GPE Rom on RUU mode or you were flashing the RUU?

x017in said:
Which network was the phone on?
The phone has a corrupt boot loader. You need to flash the correct firmware and then you will be able to boot into the boot loader.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I'm on the 3 network in Hong Kong...the phone came unlocked when I bought it
Since I'm new to all this, can you help walk me through the steps on where to find the correct firmware and the process to get into the bootloader?
Thanks!

maxrdlf95 said:
While you were trying to flash GPE Rom on RUU mode or you were flashing the RUU?
Click to expand...
Click to collapse
I was trying to flash the GPE Rom while in RUU mode
Then I got the 41 modelid error...so I tried to change the modelid and flash the android-file.txt
That's when the phone became stuck
Thanks!

you can restart to bootloader mode?

maxrdlf95 said:
you can restart to bootloader mode?
Click to expand...
Click to collapse
No, that seems to be the problem...I can't get into bootloader
The only thing that seems to work temporarily is that I can do the fastboot oem boot...but I reboot, and back at the error screen

Need to Reflash firmware
What is your fastboot getvar all output?

SaHiLzZ said:
Need to Reflash firmware
What is your fastboot getvar all output?
Click to expand...
Click to collapse
Hi, this is what I get with getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 0P6B63000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

wikwikwik said:
Hi, this is what I get with getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 0P6B63000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Your CID/MID matches what is required in conversion. I will suggest to redownload the file, and restart the process
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip

SaHiLzZ said:
Your CID/MID matches what is required in conversion. I will suggest to redownload the file, and restart the process
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
Click to expand...
Click to collapse
Here's the error message I get when I try and reflash (after doing a new download):
target reported max download size of 1830711296 bytes
sending 'zip' (510598 KB)...
OKAY [ 16.173s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 16.672s
I always get the 41 model id check fail

wikwikwik said:
Here's the error message I get when I try and reflash (after doing a new download):
target reported max download size of 1830711296 bytes
sending 'zip' (510598 KB)...
OKAY [ 16.173s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 16.672s
I always get the 41 model id check fail
Click to expand...
Click to collapse
Try supercid.
I tried flashing a stock rom and i change my CID to match the rom but i got the same error. Change it to supercid and it worked
Sent from my HTC One_M8 using XDA Premium 4 mobile app

ring_GT said:
Try supercid.
I tried flashing a stock rom and i change my CID to match the rom but i got the same error. Change it to supercid and it worked
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, did that...and got this error message:
FAILED (remote: 24 parsing android-info fail)

Post your file config from the Android-info.txt please.
And what did you use to edit the MID there?
wikwikwik said:
Hi, did that...and got this error message:
FAILED (remote: 24 parsing android-info fail)
Click to expand...
Click to collapse

ring_GT said:
Post your file config from the Android-info.txt please.
And what did you use to edit the MID there?
Click to expand...
Click to collapse
modelid: 0P6B63000
cidnum: 11111111
mainver: 1.54.708.5
btype:1
aareport:1
hbootpreupdate:12

wikwikwik said:
modelid: 0P6B63000
cidnum: 11111111
mainver: 1.54.708.5
btype:1
aareport:1
hbootpreupdate:12
Click to expand...
Click to collapse
How did you edit the file? Notepad++?
Sent from my HTC One_M8 using XDA Premium 4 mobile app

ring_GT said:
How did you edit the file? Notepad++?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, it was just TEXTEDIT on Mac

Do you have a windows pc there?
Look at this thread... http://forum.xda-developers.com/showthread.php?t=2322820&page=19
"""""""""""""
"Thnx for reply but I just get it working.
My problem was the way of unzipping on MacOSX.
I now did it with 7Zip and NotePad++ on windows8 and it worked.
(No unzip, just editing the file in the zip)
"""""""""""
it is for htc one but he got the same error as you, and it was an issue with MAC OSX unzipping.
This all I can do. If still no go you will need an expert to help you.
wikwikwik said:
Yeah, it was just TEXTEDIT on Mac
Click to expand...
Click to collapse

[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

[Soft Bricked] need ruu for HTC M8

Hi all, first time in this forum and i hope someone would save me!
I have an HTC One M8
i'm **TAMPERED** **LOCKED** **SECURITY WARNING** and S-ON
so from hboot and fastboot i can't do anything (also enter in recovery mode)
via usb in hboot i can use fastboot command but not adb command (for that i have to turn on my device which restart in 30 secs so it's very hard)
i have to get it back to stock state but for doing that i need a RUU (fastboot flash is useless and as i sayed i can't do anything with adb in fastboot mode)
in order to do that i have downloaded from htc the mem_ul source to compile with AOSP but on the phone there aren't the proc/
config.gz file and i'm stucked here.
these are the fastboot getvar all instruction.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.1017
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.401.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********
(bootloader) imei: *********
(bootloader) imei2: *******
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.121s
Please help me you would be my hero!

ADB doesn't work in fastboot, only when booted into Android. You need to use the 4.16.401.10 RUU in General and flag it when connected in fastboot mode

EddyOS said:
ADB doesn't work in fastboot, only when booted into Android. You need to use the 4.16.401.10 RUU in General and flag it when connected in fastboot mode
Click to expand...
Click to collapse
His device is not M8 but HTC One mini 2.
ulisse2010 said:
Hi all, first time in this forum and i hope someone would save me!
Click to expand...
Click to collapse
Check this thread for your device type : http://forum.xda-developers.com/one-mini-2
and this for your RUU : http://forum.xda-developers.com/one-mini-2/general/htc-one-mini-2-european-signed-ruu-t3003069

Good spot!

thanks to all of you for the help in advance.
but i tried the ruu you suggested and it doesn't work. he said that i have to choice the correct one.
what it can be?

ulisse2010 said:
thanks to all of you for the help in advance.
but i tried the ruu you suggested and it doesn't work. he said that i have to choice the correct one.
what it can be?
Click to expand...
Click to collapse
That RUU says it requires s-off

Oh... i see
ok so it won't work if i modify like this? http://forum.xda-developers.com/showthread.php?t=2364349
it is about to inject another rom in a preexistent ruu...
have done it but and it starts but the progress bar stops on the first step and it reboot

ulisse2010 said:
thanks to all of you for the help in advance.
but i tried the ruu you suggested and it doesn't work. he said that i have to choice the correct one.
what it can be?
Click to expand...
Click to collapse
You have to use the one linked to by @ckpv5 as you have an M8 Mini - this is the 'proper' M8 forum...

i think it doesn't work because the file it's corrupted, another link maybe? i think also i'm getting trought this s****
Thx a lot all of you

How did you get this **TAMPERED** **LOCKED** **SECURITY WARNING**
Is it you unlocked it before then suddenly when it has reboot problem, it turns to **LOCKED** ?
How do you know the RUU zip is corrupted ? How actually you flash it, what commands ?

The OP will need the htc_fastboot version unless they do it via SD card...

i'm sorry it is **RELOCKED**
i'm pushing it by modifing another RUU (i put it inside by replacing the rom.zip and renaming it to rom.zip) and this RUU have the htc_fastboot.exe inside it so i'm trying now to push it via "cmd".
I think this op it's broken because i can't unzip it whitout error.

ulisse2010 said:
I think this op it's broken because i can't unzip it whitout error.
Click to expand...
Click to collapse
I have no idea what you are trying to do .... by pushing & modifying another RUU
But a signed RUU zip is encrypted, you can't unzip it, it's not that it's corrupted.

You flash it by connecting the phone in fastboot and then boot into RUU mode (fastboot oem rebootRUU) and then flash the RUU (htc_fastboot flash zip ruu.zip)

when i try to do fastboot oem rebootRUU the phone reboots but in normal mode not entering in bootloader or in RUU
it's possible to enter RUU mode with adb command?

ulisse2010 said:
when i try to do fastboot oem rebootRUU the phone reboots but in normal mode not entering in bootloader or in RUU
it's possible to enter RUU mode with adb command?
Click to expand...
Click to collapse
This is a symptom of a corrupted partition (more of a hardware problem) ...
I run out of idea to help you, further more your device is not M8.
Maybe someone else can help you ... good luck

please don't give up now i'm almost here:
i tried to flash it in ruu mode via htc_fastboot and the message is that:
sending 'zip'... (43267 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(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) total_image_number=7
(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
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
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 (SH4AAWR02353)...
< waiting for device >
sending 'zip'... (43267 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 74(s)
how i fix it?
i can't give the command two time because the device restart after this message.

I've moved this thread from the One M8 forum to the One Mini 2 forum. Hopefully you will get help here from people who have the same phone. Good luck!

Black screen after HTC startup logo please help! [bricked probably]

Hi everyone,
So my HTC one M8 was rooted with TWRP recovery. It was running Android 5.0 I think. I got an OTA update but I was not able to update it because of TWRP. I wanted the update so bad and I searched on Youtube to know how to update the software. I found a video and I followed these steps.
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
However, when I replaced the custom recovery with the stock recovery, I downloaded the OTA update and updated it. But after the update completed, the device never booted up. It shows the HTC logo then it goes black! (The screen is still on, but black!) Have I bricked the phone? How Can I fix it please!
PS. Here is the video I watched www.youtube.com/watch?v=PPPT5J8xG6w

Rezhwscene said:
Hi everyone,
So my HTC one M8 was rooted with TWRP recovery. It was running Android 5.0 I think. I got an OTA update but I was not able to update it because of TWRP. I wanted the update so bad and I searched on Youtube to know how to update the software. I found a video and I followed these steps.
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
However, when I replaced the custom recovery with the stock recovery, I downloaded the OTA update and updated it. But after the update completed, the device never booted up. It shows the HTC logo then it goes black! (The screen is still on, but black!) Have I bricked the phone? How Can I fix it please!
PS. Here is the video I watched www.youtube.com/watch?v=PPPT5J8xG6w
Click to expand...
Click to collapse
That video is nonsense. There is a blatant mistake at 6.44 and the knob doesn't see it. You need to go back to stock first, then take the OTA.

Einwod said:
That video is nonsense. There is a blatant mistake at 6.44 and the knob doesn't see it. You need to go back to stock first, then take the OTA.
Click to expand...
Click to collapse
Thanks for the reply! But please, how can I fix my device now? I don't have TWRP anymore! But I can access the Stock revovery. What should I do? :'(

Rezhwscene said:
Thanks for the reply! But please, how can I fix my device now? I don't have TWRP anymore! But I can access the Stock revovery. What should I do? :'(
Click to expand...
Click to collapse
Go into fastboot and open a command prompt. Type in fastboot getvar all and post the output here. Remove your serial and IMEI numbers before you post. Hopefully we can get you back to stock.

Einwod said:
Go into fastboot and open a command prompt. Type in fastboot getvar all and post the output here. Remove your serial and IMEI numbers before you post. Hopefully we can get you back to stock.
Click to expand...
Click to collapse
Okay, before I see your respond I did a stupid thing! I flashed TWRP and I wanted to flash stock ROM and I followed these instructions from this website
http://www.carbontesla.com/2015/01/htc-one-m8-4-16-401-10-stock-lollipop-ruu-0p6bimg/
But when I want to flash the rom its says "target reported max download size of 1826414592 bytes error: cannot load 'L50RUU.zip'"
Anyway, now my device is " Relocked" and when I type fastboot getvar I get this>>>>
{
"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"
}
What should I do?

Rezhwscene said:
Okay, before I see your respond I did a stupid thing! I flashed TWRP and I wanted to flash stock ROM and I followed these instructions from this website
http://www.carbontesla.com/2015/01/htc-one-m8-4-16-401-10-stock-lollipop-ruu-0p6bimg/
But when I want to flash the rom its says "target reported max download size of 1826414592 bytes error: cannot load 'L50RUU.zip'"
Anyway, now my device is " Relocked" and when I type fastboot getvar I get this>>>>
What should I do?
Click to expand...
Click to collapse
First unlock the bootloader again. TWRP you need and the command is: fastboot getvar all Check your messages also.

Einwod said:
First unlock the bootloader again. TWRP you need and the command is: fastboot getvar all Check your messages also.
Click to expand...
Click to collapse
Okay I'm a goddamn noob! How to unlock the bootloader again? this command " fastboot oem unlock" does not work!
AND here is the result!
(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.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__016
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.192s

Rezhwscene said:
Okay I'm a goddamn noob! How to unlock the bootloader again? this command " fastboot oem unlock" does not work!
AND here is the result!
(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.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__016
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.192s
Click to expand...
Click to collapse
Luckily you have a WWE device. Download this RUU and run it from Windows. Make sure you have HTC drivers installed. The easy way to do that is to install HTC Sync and then uninstall it. The HTC drivers will be left behind. That will take you to stock 4.16.401.10. You will then receive the update to 13.

Einwod said:
Luckily you have a WWE device. Download this RUU and run it from Windows. Make sure you have HTC drivers installed. The easy way to do that is to install HTC Sync and then uninstall it. The HTC drivers will be left behind. That will take you to stock 4.16.401.10. You will then receive the update to 13.
Click to expand...
Click to collapse
I owe you my life man! Thanks for responding quickly. Anyway, Should I unlock the bootloader then run the .exe file?

Rezhwscene said:
I owe you my life man! Thanks for responding quickly. Anyway, Should I unlock the bootloader then run the .exe file?
Click to expand...
Click to collapse
No, the bootloader needs to be relocked/locked for the RUU.exe to work. It should work from fastboot mode. If it doesn't, I'll be on again tomorrow.

Einwod said:
Luckily you have a WWE device. Download this RUU and run it from Windows. Make sure you have HTC drivers installed. The easy way to do that is to install HTC Sync and then uninstall it. The HTC drivers will be left behind. That will take you to stock 4.16.401.10. You will then receive the update to 13.
Click to expand...
Click to collapse
OH MY GOD IT WORKED! I seriously don't know how to thank you or how to repay you! Thank you a million! I don't have a credit card to donate because you deserve it! But I'll get one soon, Promise!!

Rezhwscene said:
OH MY GOD IT WORKED! I seriously don't know how to thank you or how to repay you! Thank you a million! I don't have a credit card to donate because you deserve it! But I'll get one soon, Promise!!
Click to expand...
Click to collapse
Glad everything all worked out. MM update should be out any day now. Enjoy.