This is an ATT version phone I rooted this phone a couple of days ago with TWRP. However, I had to use adb to enter fastboot as it would not go to fastboot using power/volume keys. Actually, it never shows a fastboot screen, even in adb, so it may have been going into fastboot all along and I just could not see it.
So, instead of leaving well enough alone, I RUU'ed (newest ATT version from HTC site) it to try to get fastboot to work normally (it still works, I just can't see it on screen). Now, I can't get rooted again. FWIW, I did make a backup with TWRP before RUU'ed. Regardless, there is nothing on this phone I need to keep, I just want to root it before I start using it.
Any help is greatly appreciated...
Here is my unlock sequence. Note what happens if I try to flash TWRP immediately after unlock. I have to CTRL C and Reboot phone.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash unlockt
oken unlock_code.bin
target reported max download size of 1826414592 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.110s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.012s]
finished. total time: 0.125s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
Now when I try to flash TWRP, I get :
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recover' (20022 KB)...
OKAY [ 1.884s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.611s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
HT445####### fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.013s
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Mr Hofs said:
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Click to expand...
Click to collapse
Same Results:
C:\s>fastboot flash recovery twrpm8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.438s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.976s
C:\s>
C:\s>fastboot flash recovery twrp30m8
error: cannot load 'twrp30m8'
C:\s>fastboot flash recovery twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.889s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.616s
C:\s>
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Mr Hofs said:
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Click to expand...
Click to collapse
Already tried that, but tried again. First below is my result before I downloaded new twrp and the second one is my result after I re-downloaded image
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.896s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.899s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>
Try the HTC_fastboot adb package. It's posted several times here on xda.
Mr Hofs said:
Try the HTC_fastboot adb package. It's posted several times here on xda.
Click to expand...
Click to collapse
Still no luck, same error (see below). This worked flawless before I flashed the latest ATT RUU.
Is it possible phone is still not unlocked or would I be getting that far if it was still locked?
Question. This phone is AT&T (more details in getvar above) but at the end of the contract, AT&T sent me code to unlock the SIM. Now, the SIM I am using is on a T-Mobile MVNO (TING). Since they SIM unlocked the phone, would I be able to and would there be any advantage/risk to trying to flash the Stock RUU for HTC unlocked/developer. It is a higher software version than the ATT version I flashed (twice).
C:\FB>htc_fastboot flash recovery twrp.img
sending 'recovery' (20022 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 3(s)
Any other ideas? I can't see bootloader screen, but it appears I can access and do all bootloader functions in adb.
I would really like to be able to eliminate locked bootloader as the issue, is there anything else I can flash or try that might let me know if bootloader is still locked. I can get results from getvar and fastboot devices.
I also have an image of the phone saved from TWRP before I flashed the RUU, but seems no way to get that image back. I am not opposed to purchasing S-off if that will for sure help me.
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
joikep said:
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
Click to expand...
Click to collapse
Already tried two previous versions
rockfordpi said:
Already tried two previous versions
Click to expand...
Click to collapse
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
rockfordpi said:
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
Click to expand...
Click to collapse
OK, we can close this one out. I did want to post my solution, just in case anyone else had a similar error.
Long Story a little bit shorter, on my HTC one M8, the error:
sending 'recovery' (11976 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Was due to a locked bootloader. Because, for some reason I can't see the bootloader on my phone, I could not see the lock status, so I was having to do EVERYTHING via ADB. The problem was, when unlocking the bootloader there is screen on the phone that asks you to confirm yes or no if you want to unlock it. I could not see that screen and the instructions I was reading left that out (It was a good assumption that if one was trying to unlock one would know to say YES. LOL). So, I was missing that step. When I found that step, even though I could not see it on screen, I just blindly pushed volume down and then power to select. At that point it unlocked and allowed me to flash twrp 3.0.
Still do not know WHY I can't see the bootloader screen. I wonder if for some reason the colors are off in my bootloader screen and all the words are the same color as the background or it is trying to redirect that output somewhere else.
but at this point I am going to live with it as trying to fix it is what got me in here in the first place.
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Someone have an idea to help me ?
Many thanks
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
Click to expand...
Click to collapse
The top post is in regards to getting signature verify fail message when flashing custom recovery. So I don't see how it's the "same problem".
Be careful about saying "same problem" without giving any specific information about your actual problem, or device details. From my experience, I've seen many dozens of times where folks say they have the "same problem" and when prompted for more info, we find there are many many differences.
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
Click to expand...
Click to collapse
Did the RUU flash successfully, or were there any error messages?
Also, please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the phone.
foosee said:
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Click to expand...
Click to collapse
This is normal and expected. You can't use adb when in bootloader. And you can't use fastboot and adb simultaneously. Meaning, when one works, the other will not work, by definition.
Fastboot = only works in bootloader fastboot mode
adb = only works within OS, or alternately will work in custom recovery TWRP
If you issue the command fastboot devices, you should find that it works.
It is also not clear what you are trying to use adb to do (what commands?).
I've got a Moto G4 Play and with LineageOS I can't make any calls. So I wanted to downgrade the firmware to the stock-firmware which I downloaded here: bit.ly/2lvXpgC. There are instructions how to downgrade the firmware here: bit.ly/2kPAuNS.
The first command - "fastboot oem fb_mode_set" - is accepted.
But the second command - "fastboot flash partition gpt.bin" - produces the following:
"target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.442s"
Can anyone tell me what I'm doing wrong here?
[EDIT]:
I simply run the other commands and ignored those that failed. Now my Phone boots into the bootloader and if I press start, I get into an endless boot-loop. If I start the TWRP recovery-image with "fastboot boot twrpxyz.img", the device restarts and stops in the bootloader, i.e. the recovery-mode isn't started.
Can anyone help me from here?
[EDIT2]:
I've got the problem: I tried to boot the bootloader without a battery in the phone and just the USB-cable attached. So I suspected this was also the problem when flashing the stock-image and I run through tge commands to install it. I simply ignored that "fastboot flash partition gpt.bin" didn't work (according to someone who had the same problem here in this boadd) and every other command was successful. The phone booted the stock firmware and everything is fine now.
Thanks you so much
Work fine for me, only i found the solution here, seriously, thanks!!
GOD BLESS YOU
The bootloader are unlocked. But, when I decide to rollback, I started the flash process using "fastboot oem lock begin"; then, every try of flash give me this kind of error, showed bellow.
So, for example, I got this when I tried to flash stock over a lineage rom:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.014s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.184s
What should I do? I have tried to flash bootloader.img and use "fastboot oem fb_mode_set", but stay in the same situation.
Obviously, I'm using the exactly stock versions to my device.
Thank you guys! :laugh:
motafoca55 said:
The bootloader are unlocked. But, when I decide to rollback, I started the flash process using "fastboot oem lock begin"; then, every try of flash give me this kind of error, showed bellow.
So, for example, I got this when I tried to flash stock over a lineage rom:
What should I do? I have tried to flash bootloader.img and use "fastboot oem fb_mode_set", but stay in the same situation.
Obviously, I'm using the exactly stock versions to my device.
Thank you guys! :laugh:
Click to expand...
Click to collapse
All I can say is you should have pulled ur stock ROM
With the help of @Nirbhay2 I managed to block my bootloader, however what I wanted to share here is that to block the bootloader of the Brazilian variant it is necessary the last ROM with january security patch POTTER_NPNS25.137-92-4. Here you will find the guide to block your Brazilian device.
Have minimal ADB
Have Motorola drivers installed on your PC
Have the january patch ROM stock: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Extract the ROM to any folder and paste the minimal ADB along with the extracted ROM.
Open a command prompt in the folder and with the device in fastboot mode make a flash of the entire ROM stock on your device, to facilitate copying all the commands at once and paste at the command prompt and it will install automatic to your ROM , then do the same with the commands to re-block the bootloader and at the end of this process your device will be started with bootloader locked.
Commands to re-lock bootloader, do this after the full ROM flash
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Command link for flash ROM stock
https://pastebin.com/ZWTaWuyr
We thank @Nirbhay2 for this great guide.
I have a problem relocking bootloader:
...
[email protected] at 12:34:24 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.870s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.465s]
finished. total time: 1.335s
...
[email protected] at 12:36:36 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.002s]
finished. total time: 0.002s
So, bootloader remains unlocked.
Moreover:
[email protected] at 12:36:38 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash bootloader bootloader.img(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.551s
How can I flash original bootloader, boot and lock bootloader?
pss34 said:
I have a problem relocking bootloader:
...
[email protected] at 12:34:24 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.870s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.465s]
finished. total time: 1.335s
...
[email protected] at 12:36:36 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.002s]
finished. total time: 0.002s
So, bootloader remains unlocked.
Moreover:
[email protected] at 12:36:38 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash bootloader bootloader.img(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.551s
How can I flash original bootloader, boot and lock bootloader?
Click to expand...
Click to collapse
friend, you need to use this ROM that I made available on the link, if you have a moto G5 plus brazilian you can get the lock, but use this link ROM.
Enviado de meu XT1683 usando Tapatalk
I tried the same thing.
I had TWRP and SuperSu on my phone a few days back. But weirdly, I lost network connectivity and after a botched attempt at installing V4A, the audio died as well. Even the camera and the flash had stopped working. More weirdly, the Root Checker app I had now showed me that root access was not properly installed.
SInce my phone was on the November patch (25-137-92), I found the stock ROM of it online and flashed it with the Moto G5 Plus ToolKit.
Now all the issues I've had are fixed. Everything works perfectly. TWRP has been removed along with SuperSu.
But the bootloader still shows me that software status is modified. The warning on boot-up which tells that the device has been unlocked is still there.
I don't know if it's related but I've got WiFi speed issues now, apps won't download quickly or is it my damn internet?
The bootloader IS locked, though. That I can say confidently because the bootloader unlock option in developer options is now not selected.
Moto G(5) Plus XT1686 4/32 GB Indian Version
I have searched and searched but cannot find anywhere that tells me what these messages mean in fastboot.
Example:
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Please help.
Thank you.
Did you do something before this happened?
LOL, yes, I completely fecked it up.
I have got the recovery back now, but when I try to flash a stock image,
1. Obviously will not flash the bootloader cos it is now unlocked. So I deleted the bits in the bat file that try to flash the bootloader so that the rest can complete.
2. Now will only get to various Systemchunks and then hangs, having installed previous system chunks ok.
Seems to get to here and then hangs.
Executing ".\Windows\fastboot.exe -s SERIALNUMBER flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
I though about erasing system, butbut the I now get this message bootloader message.
fastboot erase system
(bootloader) has-slot:system: not found
Erasing 'system' OKAY [ 0.025s]
Finished. Total time: 0.062s
So, I had to go to Qualcomm fix, and I have lineage 16 on it now, but I have lost my IMEI's
Thanks for reading.
myjess said:
LOL, yes, I completely fecked it up.
I have got the recovery back now, but when I try to flash a stock image,
1. Obviously will not flash the bootloader cos it is now unlocked. So I deleted the bits in the bat file that try to flash the bootloader so that the rest can complete.
2. Now will only get to various Systemchunks and then hangs, having installed previous system chunks ok.
Seems to get to here and then hangs.
Executing ".\Windows\fastboot.exe -s SERIALNUMBER flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
I though about erasing system, butbut the I now get this message bootloader message.
fastboot erase system
(bootloader) has-slot:system: not found
Erasing 'system' OKAY [ 0.025s]
Finished. Total time: 0.062s
So, I had to go to Qualcomm fix, and I have lineage 16 on it now, but I have lost my IMEI's
Thanks for reading.
Click to expand...
Click to collapse
probably u just delete system image file
Is ok, got it all working again.
Thanks.