Develop Bugs

How to i get my HTC one M8 off bootloader screen

This is what my phone is showing:
***LOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
0S-4.24.709.3
eMMC-boot 2048MB
Aug 5 2015, 00:17:06.0
Hello, im having problems with my HTC M8 phone. It used to work perfectly untill one day it got blocket and wasnt reaponding. So i pressed the power button until it turned off. When i tries to power on ot didnt start any more. It only shows the bootloader screen. I did the reboot, fast reboot etc and it stills doesn`t start up. It will not go into recovery, & will not factory reset. Every time i try those options it goes back to bootloader.
I`m really worried and i send the phone to many services but none of them could fix it. Please help me repair the problem or at least tell me that there is no hope for the phone to start working again.

Don't you have any HTC authorized service centre around your area ?
Only HTC may be able to fix your problem as I guess your device is fully stock.
(Also check whether you have corrupted sdcard inserted to device, take it out and see whether it boots)

I sent it to different services none could fix it. But It should have for certain an HTC authorized service centre here ... (ps: there is no sdcard inserted at all.) Thanks
ckpv5 said:
Don't you have any HTC authorized service centre around your area ?
Only HTC may be able to fix your problem as I guess your device is fully stock.
(Also check whether you have corrupted sdcard inserted to device, take it out and see whether it boots)
Click to expand...
Click to collapse

I'll get you a htc signed firmware when I'm home later.
You can try to flash the firmware to see whether it will fix that bootloader missing info or not.
But base on previous experience, you may need to get the motherboard replaced.
And only HTC authorized service centre can do that.

I notice that the latest signed firmware has no radio & adsp. Not sure whether it work or not to fix your bootloader problem.
Anyway give it a try ... link & how-to, check your PM

First of all thanks for trying to help me.
Relating my problem i did what you have written to me and when i enter this command:
C:\Users\user>fastboot oem rebootRUU i get the message below:
C:\Users\user>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.183s]
finished. total time: 10.188s
As a result for the device not entering the RUU mode the firmware.zip cannot be flashed(as below)
C:\Users\user>fastboot flash zip firmware.zip
error: cannot load 'firmware.zip'
From what i see there is no hope for my phone :crying::crying::crying::crying:
ckpv5 said:
I notice that the latest signed firmware has no radio & adsp. Not sure whether it work or not to fix your bootloader problem.
Anyway give it a try ... link & how-to, check your PM
Click to expand...
Click to collapse

Nothing much that I can offer to help.
It's clearly a hardware issue. Send it only to Htc service centre.
Some country have 2 years warranty for M8, check yours.

HELP - Can't relock bootloader

Originally unlocked bootloader through HTC-DEV
CID: 11111111
Hboot 3.19.0.0000
Radio-1.2121331147A1.19_2G
M8_UL_CA PVT SHIP S-OFF
I'm trying to relock the bootloader so I can RUU, however keep getting the following error when running "fastboot oem lock"
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))
finished. total time: 1.230s
After the above message, the phone goes from unlocked -> relocked. However I believe the phone is still actually unlocked because I'm getting Error: 155 when I try to run an RUU. I also can see the red text on the charging screen indicating the phone is unlocked.
I have also used this method http://forum.xda-developers.com/showthread.php?t=2708571 to try unlock/relock, and also tried to relock and use HTC-DEV to lock but no matter what, I'm still getting Error 155.
Also, none of the user data is being wiped when I use fastboot flash unlocktoken Unlock_code.bin

blazerxzero said:
Originally unlocked bootloader through HTC-DEV
CID: 11111111
Hboot 3.19.0.0000
Radio-1.2121331147A1.19_2G
M8_UL_CA PVT SHIP S-OFF
1. I'm trying to relock the bootloader so I can RUU, however keep getting the following error when running "fastboot oem lock"
2. After the above message, the phone goes from unlocked -> relocked. However I believe the phone is still actually unlocked because I'm getting Error: 155 when I try to run an RUU. I also can see the red text on the charging screen indicating the phone is unlocked.
Click to expand...
Click to collapse
1. You don't need to relock bootloader to run RUU on S-Off device.
2. Are you trying to run Marshmallow RUU ? You'll get error 155 if the current firmware is lower than Marshmallow. You need to flash its Marshmallow firmware first then run RUU.

Thanks for the reply, I tried your method of matching the RUU with the firmware version and got a different error.
Error couldn't allocate space, even though the RUU image was smaller than the available storage.
The solution which resolved the problem was to rename the correct RUU version zip load onto SD card and flash using the bootloader auto-detection method.

Problems with Phone /dev/block/bootdevice/by-name/frp

I got an HTC One (M9) from a friend that no longer uses it and when you boot up it does ask for the last email registered to this device. It will not allow me to do anything in RUU mode or command line without repeating the same message over and over.
Code:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>adb
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
C:\Users\rbgCO\Desktop>fastboot flash firmware.zip
unknown partition 'firmware.zip'
error: cannot determine image filename for 'firmware.zip'
C:\Users\rbgCO\Desktop>fastboot flash zip firmware.zip
target reported max download size of 800000000 bytes
sending 'zip' (33033 KB)...
OKAY [ 2.726s]
writing 'zip'...
(bootloader) HOSD CL#669662
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8 RU_SIGNATURE_FAIL )
finished. total time: 5.717s
C:\Users\rbgCO\Desktop>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.016s]
finished. total time: 0.016s[CODE]
[/CODE]
Now doing some research I see the spot that was not checked was by pressing the build number 6 times and it is a checkbox allowing you to enter the mode to flash different roms or even to flash this back to stock but I do not know how I could change that.
If changing that checksum is not possible, is there a way I could contact google or HTC to see which email is associated with the lock so that I can bring it back to the guy I bought it from and have him enter that email and password allowing me to change that checkbox then reset the phone again?
Any help would be greatly appreciated.

Any help would be appreciated!

rbgCODE said:
Any help would be appreciated!
Click to expand...
Click to collapse
Does it have a recovery?

my htc m9 verizon
show unlocked s-off what do i do next should i just flash or still need to do something else. please am new to rooting and all

HTC M8 eye with official rom stuck in fastboot

Hey guys
Last night my phone(HTC m8 eye 5.07.401.1) slowed down badly, after a while it restarted automatically and fastboot screen showed up.
Things I've tried:
1-Restarting the phone after fully charging it for 1 billion times (worked once but the phone was frozen and restarted automatically again)
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
3-Trying to flash the official rom , didn't work
4-removing the SIM and SD card and restarting the phone, didn't work
by the way, usb debugging was not active last time the phone was working normally, Also the phone have not experienced any unusual activity like rooting or flashing custom roms or...
What can I do?
(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: 5.07.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA00000000000
(bootloader) imei: 3580000000000000
(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: 5c9466dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
------------------------------------------------------------------------------------------- fastboot results----------------------
C:\fastboot>fastboot devices
FA57LY901038 fastboot
C:\fastboot>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.041s]
finished. total time: 10.041s
C:\fastboot>fastboot flash zip update.zip
target reported max download size of 1826332672 bytes
sending 'zip' (1687274 KB)...
OKAY [ 57.179s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 118.969s
---------------------------------------------------------------------------------------

I don't have the "eye", only the "standard" M8, but I'll try to help as much as I can, as far as anything that I believe is common between the two M8 versions (unlocking bootloader, flash RUU, etc.).
bahmaniq said:
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
Click to expand...
Click to collapse
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
bahmaniq said:
3-Trying to flash the official rom , didn't work
Click to expand...
Click to collapse
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.

redpoint73 said:
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
Click to expand...
Click to collapse
Yes, *****LOCKED***** it says, I guess it is very serious on this one. Based on knowledge I gathered in these 2 days, I think it should show a black confirmation screen after I try to unlock it (using *.bin file), but it simply does not.
redpoint73 said:
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
Click to expand...
Click to collapse
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
redpoint73 said:
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.
Click to expand...
Click to collapse
So, that's it, I'm gonna play "One last goodbye" and let the history judge. 2 years of EMERGENCY CALLS ONLY, 2 years of zero antenna...
After a silent peaceful night
You took my heart away
oh I wish, I wish you could have stayed

bahmaniq said:
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Click to expand...
Click to collapse
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.

redpoint73 said:
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.
Click to expand...
Click to collapse
It has been a long time since the last time I was here but the problem is not solved. Sorry for the delay, and No the black screen with HTC logo does not appear.
Is there anything I can do to get rid of this fastboot screen? or the phone is useless

Cant flash recovery error target reported max download size of 536870912 by

I can't flash my recovery.
Bootloader is unlocked.
Phone is not rooted
This sucks becouse i bought this phone thinking i whould not have this ****ing problem again.
(also lost my old one for the millionth time)
PS C:\Users\Admin> fastboot flash recovery C:\ProgramData\chocolatey\lib\adb\tools\platform-tools\twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.473s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.502s
PS C:\Users\Admin>
Click to expand...
Click to collapse

Weird, that validation error is usually shown when bootloader isn't actually unlocked. Have you tried unlocking it again? Have you tried with mfastboot?

DrunkenPanda2000 said:
I can't flash my recovery.
Bootloader is unlocked.
Phone is not rooted
This sucks becouse i bought this phone thinking i whould not have this ****ing problem again.
(also lost my old one for the millionth time)
Click to expand...
Click to collapse
Either you are flashing the wrong recovery for the phone - or you renamed a zip file instead of extracting the img file first
Or
Put quotation marks around the file path eg "c:/file path" or navigate to where you have fastboot and the twrp image first so all you have to type is
fastboot flash recovery recovery.img
Also make sure adb debugging is enabled in dev options of phone settings
Also if the bootloader is unlocked you should get a bootloader unlocked warning when the device starts unless you have replaced the boot logo with a modified one
If you haven't replaced this & you don't get said warning your device doesn't have an unlocked bootloader

The console is definatly finding the file. this is not the issueadb debugging is enabled. altho i realised i have the insert pattern before startup enabled and i think that might be interfering.
I am not gettIng the bootloader unlocked warning.

I disabled the pattern on bootup.
I unlocked with oem unlock.
i tried to flash from directory
Same issue
Stil no unlocked warning
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.493s
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools>
Click to expand...
Click to collapse

DrunkenPanda2000 said:
I disabled the pattern on bootup.
I unlocked with oem unlock.
i tried to flash from directory
Same issue
Stil no unlocked warning
Click to expand...
Click to collapse
Just to check, have you requested and used the unlock key from the Motorola website? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

echo92 said:
Just to check, have you requested and used the unlock key from the Motorola website? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
I have requested one. haven't received it yet.
The website doesn't show if eligable if click that button.
Also they havent send me anything for an houer after requesting.

DrunkenPanda2000 said:
I have requested one. haven't received it yet.
The website doesn't show if eligable if click that button.
Also they havent send me anything for an houer after requesting.
Click to expand...
Click to collapse
Hopefully they'll send you an email with the code in soon. Sometimes the website is a little slow, but regardless it should say if your device is eligible for unlocking. Is your device a carrier bought device or a retail device or bought from Amazon Prime? They do say if your device is bought from Motorola, to wait at least 24 hours before requesting the code.
Check that the unlock string from your device is properly formatted for the website
Ok, so my device should be eligible, but when in enter my unlock string in your tool, I get an error message. What’s wrong?
Please make sure the string you enter in the tool is:
formatted to fit on one line only
has no spaces (you have to remove them manually)
has no carriage returns (these pesky \n)
is of the right length, e.g don’t forget to append the extra 000000… on the last line
USE THE SCRUB TOOL on the UNLOCK PAGE - ABOVE the INPUT BOX
As an example, this is what is returned with the fastboot command
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 99999999999999993332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
And this is what you should enter in the form; it’s a single line, no spaces but with all the trailing zeroes.
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2A 0C39F951A3E5#1F532800020000000000000000000000
Click to expand...
Click to collapse
credit to: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1
That code in the email should let you unlock the bootloader and let you flash TWRP, no other way to unlock your bootloader (officially). If you don't get the code after a few tries of the website/waiting for the email, you may have to post on the Motorola forums: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1

Ok so now i unlocked with the code and when i flash i get the following.µ
Model is cedric XT1676 16GB P5
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.469s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.510s]
finished. total time: 0.985s
Seems to be working now.

DrunkenPanda2000 said:
Ok so now i unlocked with the code and when i flash i get the following.µ
Model is cedric XT1676 16GB P5
PS C:\ProgramData\chocolatey\lib\adb\tools\platform-tools> fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14712 KB)...
OKAY [ 0.469s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.510s]
finished. total time: 0.985s
Click to expand...
Click to collapse
That looks normal - the 'Image not signed or corrupt' message is normal as TWRP has not been cryptographically signed. As you've unlocked your bootloader that message is informational to alert that you're flashing non-Motorola files to your device (which you are).
I'd reboot to recovery after flashing and perform the other steps required (which appear to include disabling dm-verity: https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737 )

When flashing super su i get the error message
-extracting ramdisc
---failure aborting

DrunkenPanda2000 said:
When flashing super su i get the error message
-extracting ramdisc
---failure aborting
Click to expand...
Click to collapse
Flash Magisk v16.0 instead of su zip. It will work.

shad.man92 said:
Flash Magisk v16.0 instead of su zip. It will work.
Click to expand...
Click to collapse
Thx for the advice i need to act before i post sometimes.
I've done this already now i'm facing issues with the magisk nethunter module. this will be discussed in their thread.

Can i close or remove this ?

DrunkenPanda2000 said:
Can i close or remove this ?
Click to expand...
Click to collapse
Yeah sure.

Boot loader unlock
Shooting Star Max said:
Weird, that validation error is usually shown when bootloader isn't actually unlocked. Have you tried unlocking it again? Have you tried with mfastboot?
Click to expand...
Click to collapse
I have tried a same,got a bootloader and tried with fastboot,but i got error 'need to enable OEM in android settings'
.Actualy my mobile stuck with logo,once moto logo appear its gets shutdown,
Looking for your reply.