Can't Flash TWRP "Signature Verify Fail" - One (M8) Q&A, Help & Troubleshooting

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?).

Related

Complications during CM install. Can't find HTC__Y13 firmware; CWM recovery bootloops

I've been trying to install CyanogenMod for my endeavoru by the instructions in their wiki. These are the steps I took in the very beginning:
Unlock via HTC Dev
Flashed CWM
Entered CWM
Ran the CWM backup function
Wipe data/factory reset
Transferred over the .zip file
Attempted to flash from sdcard
The installation aborted because I apparently have an insufficient version of HBOOT (1.12.0000). The page on endeavoru itself had a note on this, but the install page doesn't, so like a fool I thought there would be instructions relating to that when it became relevant. Thinking what to do, I figured maybe upgrading HBOOT is the same as flashing boot.img (which IS mentioned in the install guide), so I did that as well, but the HBOOT version stayed the same.
I was uncomfortable with not feeling in control of events, so I thought I'd get back to the stock OS as a way to reassure myself and make an external (nandroid?) backup. I thought using CWM's backup/restore function would make that possible, but when I did a restore and rebooted it just went into a bootloop. (There was a FAQ item on this, but it assumed I had a zip file to get the boot.img out of, which I don't -- this was a recovery).
Easier than finding a stock rom would seem to be just to upgrade HBOOT. I found this guide on the topic, but the link to firmware doesn't work. I've found others using Search, but they don't work either. (I have HTC__Y13.) One site that has files is here, but I'm being cautious because the phone isn't cheap and I'm trying hard not to brick it. First, the site is in German (I speak a little, but I can't bee 100% sure what these things are saying); second, the link didn't come from xda-developers, so I'm wary of trusting it out of hand.
Would you suggest going on a search for another ROM (2.17.401.2), or flashing HBOOT (with a file from the German site or from somewhere else), or some other thing? The main thing I'm concerned about for the moment is having a functional phone in the next few days.
Also, can I generally expect the battery to not run out while plugged in by USB?
Thanks in advance.
Grab the firmware.zip from the german site, it seems good.
You can get the boot.img for your nandroid backup by selecting mounts and storage > mount usb storage > /sdcard/clockworkmod/backup/
Your device will charge, provided that you are booted in recovery and the version is 5.8.4.0.
Sent from my One X using xda premium
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
hallydamaster said:
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
Click to expand...
Click to collapse
To flash the hboot you don't need to flash back the stock recovery first ...... Just relock, flash the firmware, unlock, flash a custom recovery again and install a new rom
Thanks. It looks like I got the lock and flash done fine, but it hangs on unlock:
Code:
[~/endeavory] fastboot oem lock
...
OKAY [ 0.000s]
finished. total time: 0.001s
[~/endeavory] fastboot oem rebootRUU [13:14]
...
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) [MSG] OKAY
OKAY [ 0.190s]finished. total time: 0.190s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
sending 'zip' (12876 KB)...
OKAY [ 1.757s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.116s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
< waiting for device >
sending 'zip' (12876 KB)...
OKAY [ 1.661s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) Format partition LNX done
(bootloader) [RUU]WP,boot,100
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) Format partition SOS done
(bootloader) [RUU]WP,recovery,100
(bootloader) ERASE backup cid
OKAY [ 3.176s]
finished. total time: 4.837s
[~/endeavory] fastboot flash unlocktoken
Unlock_code.bin [13:16]
sending 'unlocktoken' (0 KB)...
OKAY [ 0.021s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
What I'm seeing right now is a black screen with a htc logo and a full green status bar. It's been this way for a while.
What should I do? Is it safe to terminate the unlock command?
Yeah press ctrl+c and reboot phone.
Sent from my One X using xda premium
All right, I'm happily using HBOOT 1.39 now with a CyanogenMod nightly running, and ready to explore this supermarket of excitement and possibility.
I terminated the process and rebooted, which worked fine, and flashed boot.img and CWM and then CM from recovery.
Thanks again to all of you.

Which firmware and official ROM to update my AT&T M8 to? (stuck on Android 4.4.2)

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I want to get the latest android available for my HTC M8 (AT&T). I'm currently on Android 4.4.2. I have an mdnsd battery drain bug, and the bluetooth has a bug that causes it to break whenever I get around too many bluetooth devices.
I've tried flashing to TWRP, flashing back to the factory recovery, multiple RUU files, and a SkyDragon ROM. All either don't update or cause a boot loop, and I end up doing a nandroid restore to my old ROM.
I get the impression that I need the correct version of the boot loader, which is included in the right firmware.zip file. I've tried to find the right file, but when I go to the mike1986 page to download the firmware, I'm not sure which version to try. What is the latest official firmware that will work for my phone, and what is the latest official version of Android I can update to?
Any help is greatly appreciated!
Read this - https://forum.xda-developers.com/showthread.php?t=2751432
and this - https://forum.xda-developers.com/att-htc-one-m8/general/marshmellow-update-t3379303
everything that you need is there.
The latest version is Marshmallow 6.20.502.5
ckpv5 said:
Read this - https://forum.xda-developers.com/showthread.php?t=2751432
and this - https://forum.xda-developers.com/att-htc-one-m8/general/marshmellow-update-t3379303
everything that you need is there.
The latest version is Marshmallow 6.20.502.5
Click to expand...
Click to collapse
Thanks! I notice that the firmware isn't flashing, either hanging indefinitely or giving an error message:
C:\adb>fastboot flash zip fw_6.20.502.5.zip
target reported max download size of 1772113920 bytes
sending 'zip' (57092 KB)...
OKAY [ 2.585s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.924s
Do I have to have S-off? I was trying to get around paying $25 for the software.
kentuckythrash said:
Thanks! I notice that the firmware isn't flashing, either hanging indefinitely or giving an error message:
C:\adb>fastboot flash zip fw_6.20.502.5.zip
target reported max download size of 1772113920 bytes
sending 'zip' (57092 KB)...
OKAY [ 2.585s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.924s
Do I have to have S-off? I was trying to get around paying $25 for the software.
Click to expand...
Click to collapse
repeat the flashing command immediately after you see this error
no need for s-off to flash signed firmware only relocked/locked bootloader
ahmed.ismael said:
repeat the flashing command immediately after you see this error
no need for s-off to flash signed firmware only relocked/locked bootloader
Click to expand...
Click to collapse
Thanks! I ended up getting the " FAILED (remote: 90 hboot pre-update! please flush image again immediately)" multiple times, apparently going 7/8s of the way through. I ended up trying the RUU, and it got much further and right now has been on "Updating...(1/1) Sending...." for about 20 minutes. The same window has "Remember, the operation will take about 10 minutes." Should I keep waiting or try the RUU again? I don't know if it's hung or not, and there's no real progress meter.
kentuckythrash said:
Thanks! I ended up getting the " FAILED (remote: 90 hboot pre-update! please flush image again immediately)" multiple times, apparently going 7/8s of the way through. I ended up trying the RUU, and it got much further and right now has been on "Updating...(1/1) Sending...." for about 20 minutes. The same window has "Remember, the operation will take about 10 minutes." Should I keep waiting or try the RUU again? I don't know if it's hung or not, and there's no real progress meter.
Click to expand...
Click to collapse
actually in my first respond i was mistaken about the error 99
i was talking about error 90 sorry about that
now wait for the RUU to complete the process or return with an error
if something changed please post it here
ahmed.ismael said:
actually in my first respond i was mistaken about the error 99
i was talking about error 90 sorry about that
now wait for the RUU to complete the process or return with an error
if something changed please post it here
Click to expand...
Click to collapse
It's been an hour and no change... should I let it continue? Seems like it should have finished by now.
kentuckythrash said:
It's been an hour and no change... should I let it continue? Seems like it should have finished by now.
Click to expand...
Click to collapse
what is the current status for the phone ?
If the flashing didn't start then try to flash the firmware again
Another question : did you relocked the bootloader ?
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
what is the current status for the phone ?
If the flashing didn't start then try to flash the firmware again
Another question : did you relocked the bootloader ?
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
The phone screen has the htc gradient logo. The bootloader is relocked.
I've attached an image of the ROM update window.
kentuckythrash said:
The phone screen has the htc gradient logo. The bootloader is relocked.
I've attached an image of the ROM update window.
Click to expand...
Click to collapse
Ok open cmd window and type
fastboot reboot-bootloader
Then flash the firmware
From where you got the firmware ?
and try with another USB 2 port don't use USB 3 type
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Ok open cmd window and type
fastboot reboot-bootloader
Then flash the firmware
From where you got the firmware ?
and try with another USB 2 port don't use USB 3 type
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
I got the firmware from:
https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU
I tried the 'fastboot reboot-bootloader' command and see:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
and it won't go past that point.
kentuckythrash said:
I got the firmware from:
https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU
I tried the 'fastboot reboot-bootloader' command and see:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
and it won't go past that point.
Click to expand...
Click to collapse
Close the RUU setup wizard if it still didn't flash anything or hanging on the same screen
And restart your pc then try to flash the firmware again on the device ( as it's on RUU mode )
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Close the RUU setup wizard if it still didn't flash anything or hanging on the same screen
And restart your pc then try to flash the firmware again on the device ( as it's on RUU mode )
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Thanks for your prompt responses! I managed to successfully update the firmware, seeing a completed message in the command prompt, and green bar on the HTC screen. However, now I'm still stuck on "
Updating...(1/1) Sending.......
Updating the ROM image on your Android phone...
"
I've rebooted my workstation and the phone multiple times. Not sure where to go from here.
kentuckythrash said:
Thanks for your prompt responses! I managed to successfully update the firmware, seeing a completed message in the command prompt, and green bar on the HTC screen. However, now I'm still stuck on "
Updating...(1/1) Sending.......
Updating the ROM image on your Android phone...
"
I've rebooted my workstation and the phone multiple times. Not sure where to go from here.
Click to expand...
Click to collapse
another solution you can extract the rom.zip from the RUU.exe
By start it and goto %temp% folder and you will find rom.zip
Here what you need to do
press ctrl+r and type %temp% it will open a folder,delete everything in this folder
start the RUU.exe again,once it starting and hang goto %temp% folder again you will find a folder and the rom.zip inside it copy it and flash using fastboot or
rename it to 0P6BIMG.zip and put it in your sd card ( formatted as fat32 ) then reboot into bootloader the update process should start automatically
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
another solution you can extract the rom.zip from the RUU.exe
By start it and goto %temp% folder and you will find rom.zip
Here what you need to do
press ctrl+r and type %temp% it will open a folder,delete everything in this folder
start the RUU.exe again,once it starting and hang goto %temp% folder again you will find a folder and the rom.zip inside it copy it and flash using fastboot or
rename it to 0P6BIMG.zip and put it in your sd card ( formatted as fat32 ) then reboot into bootloader the update process should start automatically
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
OK. There were 2 .zip files, rom_01.zip and rom_02.zip. Here's what happened when I tried to flash each:
--------------------------------------------------------------------------------
C:\adb>fastboot flash zip rom_01.zip
target reported max download size of 1826418688 bytes
sending 'zip' (493 KB)...
OKAY [ 0.218s]
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) total_image_number=1
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(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
OKAY [ 2.260s]
finished. total time: 2.480s
C:\adb>fastboot flash zip rom_02.zip
target reported max download size of 1825775616 bytes
sending 'zip' (1584998 KB)...
OKAY [ 48.647s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 106.973s
C:\adb>
--------------------------------------------------------------------------------
So I guess the problem is the FAILED "remote:12 signature verify fail"
kentuckythrash said:
OK. There were 2 .zip files, rom_01.zip and rom_02.zip. Here's what happened when I tried to flash each:
--------------------------------------------------------------------------------
C:\adb>fastboot flash zip rom_01.zip
target reported max download size of 1826418688 bytes
sending 'zip' (493 KB)...
OKAY [ 0.218s]
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) total_image_number=1
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(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
OKAY [ 2.260s]
finished. total time: 2.480s
C:\adb>fastboot flash zip rom_02.zip
target reported max download size of 1825775616 bytes
sending 'zip' (1584998 KB)...
OKAY [ 48.647s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 106.973s
C:\adb>
--------------------------------------------------------------------------------
So I guess the problem is the FAILED "remote:12 signature verify fail"
Click to expand...
Click to collapse
rom_02 rename it to 0P6BIMG.zip and put it in your sd card and reboot to bootloader,have you tried to do that ?
rom_01 is hboot as shown in the output
rom_02 supposed to be the RUU
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
rom_02 rename it to 0P6BIMG.zip and put it in your sd card and reboot to bootloader,have you tried to do that ?
rom_01 is hboot as shown in the output
rom_02 supposed to be the RUU
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
That worked! Thank you very much for your help. These M8s are really hard to update!
kentuckythrash said:
That worked! Thank you very much for your help. These M8s are really hard to update!
Click to expand...
Click to collapse
Not hard but tricky
Glad i helped
Sent from my HTC M8 using XDA Labs

Confused on the upgrade process

Hey everyone,
Its been a long time since I updated my phone.
Here's my configuration:
HTC One M8
Android Version: 4.4.4
HTC Sense version: 6.0
Unlocked, M8_UL, S-On
HBOOT: 3.16.0.0000
Radio: 1.15.2133156.UA13G
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Now I tried to turn to convert to S-OFF using Sunshine but it comes up with this: Debug Kernel/Ramdisk - Your device has a debuggable ramdisk. You need to flash a non-debuggable boot.img
I want to go back to the hassle free official Android version provided by HTC. I have tried to look for a up to date guide, however the download links are dead.
Can someone point me in the right step? It'll be much appreciated.
Thank you
why do you need to s-off the device ??
AFAIK it will work on stock roms only ( rooted is fine )
you have an outdated version of android
to be completely stock and have the latest android version available for this device officially
do what this post said (( all of it ))
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
ahmed.ismael said:
why do you need to s-off the device ??
AFAIK it will work on stock roms only ( rooted is fine )
you have an outdated version of android
to be completely stock and have the latest android version available for this device officially
do what this post said (( all of it ))
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Thank you Ahmed I will follow that post and will let you know it goes.
ahmed.ismael said:
why do you need to s-off the device ??
AFAIK it will work on stock roms only ( rooted is fine )
you have an outdated version of android
to be completely stock and have the latest android version available for this device officially
do what this post said (( all of it ))
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
So I reached the following step:
htc_fastboot flash zip RUU.zip (to install RUU)
And heres what happened.
C:\Users\User\Desktop\HTC One M8\RUU>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.015s
C:\Users\User\Desktop\HTC One M8\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.013s]
finished. total time: 0.015s
C:\Users\User\Desktop\HTC One M8\RUU>htc_fastboot flash zip RUU.zip
sending 'zip'... (53965 KB) OKAY
sending time = 2.927 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 4(s)
SamungGalaxyS2 said:
So I reached the following step:
htc_fastboot flash zip RUU.zip (to install RUU)
And heres what happened.
C:\Users\User\Desktop\HTC One M8\RUU>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.015s
C:\Users\User\Desktop\HTC One M8\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.013s]
finished. total time: 0.015s
C:\Users\User\Desktop\HTC One M8\RUU>htc_fastboot flash zip RUU.zip
sending 'zip'... (53965 KB) OKAY
sending time = 2.927 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 4(s)
Click to expand...
Click to collapse
did you relocked the bootloader ??
if yes try another method to flash and check the md5 for the RUU.zip
this is the easiest method to flash a signed RUU.zip https://forum.xda-developers.com/showpost.php?p=67307303&postcount=1748
ahmed.ismael said:
did you relocked the bootloader ??
if yes try another method to flash and check the md5 for the RUU.zip
this is the easiest method to flash a signed RUU.zip https://forum.xda-developers.com/showpost.php?p=67307303&postcount=1748
Click to expand...
Click to collapse
The bootloader is currently unlocked (it says ** UNLOCKED ** in purple).
I just tried to open the ZIP file, in Windows, and it says cannot be opened, so I do think it was corrupt somehow. I am going to download it again and see if it does it again.
If it doesn't work again, I will try your other method.
Thank you buddy.
SamungGalaxyS2 said:
The bootloader is currently unlocked (it says ** UNLOCKED ** in purple).
I just tried to open the ZIP file, in Windows, and it says cannot be opened, so I do think it was corrupt somehow. I am going to download it again and see if it does it again.
If it doesn't work again, I will try your other method.
Thank you buddy.
Click to expand...
Click to collapse
no you can't open the .zip it's signed with htc keys and you can't open it by normal apps
now relock the bootloader as the guide said in the linked post above
it should be relocked to flash a signed RUU.zip on s-on device
no need to download again
ahmed.ismael said:
no you can't open the .zip it's signed with htc keys and you can't open it by normal apps
now relock the bootloader as the guide said in the linked post above
it should be relocked to flash a signed RUU.zip on s-on device
no need to download again
Click to expand...
Click to collapse
You are a star. Thank you so much mate. Just rebooting right now, with the "Android is starting"
SamungGalaxyS2 said:
You are a star. Thank you so much mate. Just rebooting right now, with the "Android is starting"
Click to expand...
Click to collapse
Glad i helped
Enjoy
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Glad i helped
Enjoy
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
WORKS

Phone may be done for please help

so I downloaded a rom the new xperience rom for moto z play and I used it and liked it but wanted to use a different rom well their recovery replaced my twrp so I went to settings and factory reset and now I cant get out of fastboot mode everytime I try it says "start up failed your device didn't start up successfully use the storage repair assistant on computer to repair your device" I think it completely wiped everything my whole sysem I cant even get into twrp so I'm trying to flash twrp and use the back up I have saved on my computer but I get this
C:\Program Files (x86)\Minimal ADB and Fastboot>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' (23420 KB)...
OKAY [ 0.506s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.530s
PLEASE HELP!!!!!!!!!!!
Addison xt1635-02
This is gonna sound stupid. But after you fastboot TWRP, did you try starting ur phone into bootloader, and going to recovery? I thought TWRP wouldn't install at first but it was there all along when I used the English version.

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.

Categories

Resources