Database Users

Moto g4 XT1625 install TWRP 3.0.2 fail, Image not signed or corrupt.

Moto g4 XT1625 install TWRP 3.0.2 fail, Image not signed or corrupt.
unlock boot loader ok,
Install TWRP 3.0.2 from official (twrp-3.0.2-0-athene.img 12.2M 2016-06-08 17:50:53 EDT) fail with these message:
(bootloader) Image not signed or corrupt
I tried again, not work. After that, reboot, try to enter recovery mode, only get "no command" message with a dead Android robot on the screen.
I wanna root this device, but can't install TWRP at all.
Please give some help.

1) Did you type in the right command?
fastboot flash recovery twrp.img
2) Did you download twrp from the official page? Did you try re-downloading the twrp file to make sure its not corrupted? Below is the link for twrp 3.0.2, directly from the official page of twrp.
https://dl.twrp.me/athene/
Please update me how it goes.

I had the same issue. Always got that message, but I reflashed it a few times until it eventually worked.

xtermmin said:
I had the same issue. Always got that message, but I reflashed it a few times until it eventually worked.
Click to expand...
Click to collapse
Glad to hear it worked

First of all, thanks for all the reply.
I will leave more detail and keep trying.
turn on usb debugging. --> ok
adb reboot bootloader --> ok
fastboot devices --> ok show devices
fastboot flash recovery recovery.img --> enter everything right but only got fail & pain T_T
// The message:
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12496 KB)...
OKAY
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY
// end
Here, it said sending 'recovery' (12496 KB)...
which means, I guess it get that img file, but still fail.
By the way, some other user got the same problem and message.
I tried on XT1625 Moto g4, again and again, fail. close unnecessary program.
If I can unlock bootloader, hardly believe things could go south like this.
Maybe the key problem is
1 (bootloader) has-slot:recovery: not found
something must wrong, but where?
2 (bootloader) Image not signed or corrupt
XT1625 Moto g4, Moto g4 plus need different TWRP? But there's only one from TWRP official website.
I tried everything I can do, download again compare with md5 before I post.
I can't find way out.
Anyway, thanks alot.

updated, I'm not sure, but as you said, I tried again, suddenly, I could enter TWRP, I will try whether it work or not.
Another question is, after unlock bootloader, install TWRP, root. Can I update system or patch with OTA?
Thank you for reply and help.

funplay said:
updated, I'm not sure, but as you said, I tried again, suddenly, I could enter TWRP, I will try whether it work or not.
Another question is, after unlock bootloader, install TWRP, root. Can I update system or patch with OTA?
Thank you for reply and help.
Click to expand...
Click to collapse
Custom recovery and root break OTA. You might still get the notification that an OTA is available, but it won't be able to apply.

it never worked for me.
But the next command works:
fastboot boot twrp.img
funplay said:
updated, I'm not sure, but as you said, I tried again, suddenly, I could enter TWRP, I will try whether it work or not.
Another question is, after unlock bootloader, install TWRP, root. Can I update system or patch with OTA?
Thank you for reply and help.
Click to expand...
Click to collapse

I was having the same problem. I tried the RootJunkyremove amazon bloat script, and I was having all sorts of problems, Even getting into a boot loop for a while.
I was running without a recovery until I ran Rootjunky's root script, which seems to have fixed most things.

Screwed up phone while rolling back Android 7 - help?

So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?

First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.

Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.

Why is everything so difficult on this device?

I constantly encounter roadblocks on this phone. Have not had issues with my OP3, Le Max 2, older Note 4 and Nexus 6 . If ZTE is pro this community, why are things not straightforward? On the OP3, simple lock and unlock commands and flash away. Got to do this and do that, 1001 different ideas from people. Right now, my BL is unlocked and I am trying to reinstall TWRP after upgrading to Nougat. This is the message I get when running my adb command to flash recovery:
I have an unlocked BL and recently upgraded to Nougat, but when I try to reinstall TWRP via fastboot flash method, it fails. I have tried two different versions of TWRP 3.0.3-1 & 3.0.4-1. This is the message I get.
PS C:\adb> fastboot flash recovery twrp-3.0.4-1-a7.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.332s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.363s
Any ideas?

Check here and you'll find the answer...
https://forum.xda-developers.com/axon-7/help/fastboot-recognizing-phone-bootloader-t3492201
you need to revert back the drivers to get fastboot working.

DrakenFX said:
Check here and you'll find the answer...
https://forum.xda-developers.com/axon-7/help/fastboot-recognizing-phone-bootloader-t3492201
you need to revert back the drivers to get fastboot working.
Click to expand...
Click to collapse
It is possible rigth now, for a A2017U full stock in NOUGAT (no unlock, no root) to flash TWRP and jump to LineajeOS 14.1 ?
Thanks

Happened to me. Didn't figure it out on there. You have to re unlock the bootloader to get it to work as it currently shows unlocked but is in fact partially locked. I used the bl unlock kit available and ew unlocked the bootloader then jumped to lineage os. You must get to a point in the zip where it says to fastboot oem unlock and instead type fastboot oem lock. Then start the zip guide from the very beginning again

It's not that difficult, it's just different from hacking a Samsung/HTC device. Just be patient and read. We've all had those same problems and there are workarounds to those problems. But the problem you're running into is you don't have the proper fastboot installed that allows fastboot commands.

https://forum.xda-developers.com/ax...on-7-root-bootloader-unlokced-t3441204/page92
Scroll close to the end, bornlivedie mentions that he did on B15 "Nouget"
Altomugriento said:
It is possible rigth now, for a A2017U full stock in NOUGAT (no unlock, no root) to flash TWRP and jump to LineajeOS 14.1 ?
Thanks
Click to expand...
Click to collapse

My mate 9 has become a hard brick and I want to help for recovery.

My mate 9 has become a hard brick and I want to help for recovery.
I am Japanese and I am not good at English.
I apologize for being a difficult to read sentence
I purchased MATE 9(MHA-AL00 6GB/128GB).
However, the firmware was MHA-L29C636B183 from the beginning.
I tried updating to Android 8 but I failed.
Currently, it is in the following state.
1. When turn on the power,Huawei logo is not displayed
2. The screen is black and does not react even if the power button is pressed for a long time.
3. use Vol-Up + Power , Vol-Down + Power,3 Button does not respond.
4. However, when I run fastboot devices, The following is returned.
=====
C:\>fastboot devices
N8K021xxxxxxxxxx fastboot
=====
5. fastboot reboot-bootloader respond. but there is no change in the display.
=====
C:\>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.025s
=====
When Oreo update failed and turned on,
"ERROR 10 Boot.img" displayed on the screen where the droid doll is displayed,
and it can not start up.
I tried to recover with the following procedure No.1-4, but it got even worse.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Currently, fastboot may be usable. I installed TWRP but I can not use it.
eRecovery also does not work.
I am thinking that I can recover using FASTBOOT FLASH XXXX.IMG.
But I do not know which partition and how to update.
Please tell me about how to recover and related sites.
Thank you

have you tried turning it off and on?

;74563891 said:
My mate 9 has become a hard brick and I want to help for recovery.
I am Japanese and I am not good at English.
I apologize for being a difficult to read sentence
I purchased MATE 9(MHA-AL00 6GB/128GB).
However, the firmware was MHA-L29C636B183 from the beginning.
I tried updating to Android 8 but I failed.
Currently, it is in the following state.
1. When turn on the power,Huawei logo is not displayed
2. The screen is black and does not react even if the power button is pressed for a long time.
3. use Vol-Up + Power , Vol-Down + Power,3 Button does not respond.
4. However, when I run fastboot devices, The following is returned.
=====
C:\>fastboot devices
N8K021xxxxxxxxxx fastboot
=====
5. fastboot reboot-bootloader respond. but there is no change in the display.
=====
C:\>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.025s
=====
When Oreo update failed and turned on,
"ERROR 10 Boot.img" displayed on the screen where the droid doll is displayed,
and it can not start up.
I tried to recover with the following procedure No.1-4, but it got even worse.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Currently, fastboot may be usable. I installed TWRP but I can not use it.
eRecovery also does not work.
I am thinking that I can recover using FASTBOOT FLASH XXXX.IMG.
But I do not know which partition and how to update.
Please tell me about how to recover and related sites.
Thank you
Click to expand...
Click to collapse
Is Erecovery working?

what command that you use to flash twrp ??

le grande magnetto said:
have you tried turning it off and on?
Click to expand...
Click to collapse
wmfreak said:
Is Erecovery working?
Click to expand...
Click to collapse
Thank you for your reply.
I turned off the power, but it looks like the power is turned on automatically.
There is no screen display, but confirmed with fastboot devices.
I can not enter eRecovery screen.

superseventh said:
what command that you use to flash twrp ??
Click to expand...
Click to collapse
fastboot flash recovery TWRP8_3.0.3.img

;74565458 said:
fastboot flash recovery TWRP8_3.0.3.img
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
this link will guide you how to HWOTA to update ROM when you already have Oreo update.zip, update_data_public.zip, and update_all_hw.zip put these 3 files in to update folder
if this HWOTA that you download not work try this https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
it is HWOTA8 to update to Oreo
if twrp won't work try this https://forum.xda-developers.com/mate-9/development/preliminary-twrp-3-1-1-0-mate-9-emui-8-t3687622

superseventh said:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
this link will guide you how to HWOTA to update ROM when you already have Oreo update.zip, update_data_public.zip, and update_all_hw.zip put these 3 files in to update folder
if this HWOTA that you download not work try this https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
it is HWOTA8 to update to Oreo
if twrp won't work try this https://forum.xda-developers.com/mate-9/development/preliminary-twrp-3-1-1-0-mate-9-emui-8-t3687622
Click to expand...
Click to collapse
Thank you for showing me three ways. Since I am going to work from now I will try after going home.
After that, as a result of investigation, I found out that the FRP is locked.
C:\>fastboot oem lock-state info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.008s]
finished. total time: 0.012s
I am looking for a way to unlock this using FASTBOOT.
If I erase a partition somewhere, will it be unlockd ?

;74570405 said:
Thank you for showing me three ways. Since I am going to work from now I will try after going home.
After that, as a result of investigation, I found out that the FRP is locked.
C:\>fastboot oem lock-state info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.008s]
finished. total time: 0.012s
I am looking for a way to unlock this using FASTBOOT.
If I erase a partition somewhere, will it be unlockd ?
Click to expand...
Click to collapse
when you rebrand and install ROM with dload and then sign in to Google account the FRP Locked will be dissappear
this following method be the same that you use it before
now try this
1- Unlock bootloader
2- install twrp,
3-do oeminfo backup in twrp,you should have a folder name twrp, inside this folder there is many subfolders.
In last folder there is 2-3 files,those files should be replaced with Oeminfo Al00 : https://www.mediafire.com/download/37n3jqv23j6erq5
Once replaced, put this folder on ur sd card and boot to twrp recovery than restore it.
4- download C00 offline firmware from third post here https://forum.xda-developers.com/ma...o-bootloop-t3534594/post70937310#post70937310 , Download B115 then extract the rar and copy dload folder to external sd card,turn off ur phone than press 3 buttons combination,power volume up and down till the update start.
5- when finished unlock bootloader again
6-install twrp again
7- flash hw_data for C00 in twrp http://update.hicloud.com:8180/TDS/.../v65567/f2/full/all/cn/update_full_all_cn.zip it will give an error, don't worry.
8-flash c00 offline firmware again to have locked bootloader and get rid of the warning message lol
9 factory rest from settings.
10-use system update to get the latest firmware, sometimes you need sim card inserted,and using the download latest package option.
11 done.

Currently, only FASTBOOT can be used,
FRP is preventing the overwriting of the partition,
so I can not try the suggested method.
I studied variously, but I can not find a good solution.
I am planning to use DC-Phoenix (paid service) in a few days.
It seems to be able to update ROM from FASTBOOT even when FRP is locked.

I tried DC-Phoenix, but as a result it failed. The FAST BOOT which I was able to use until now can not be used and the power can not be turned on.
I am disappointed that the method of recovery is gone.
Thank you for your support.

Bricked
GreenOcean said:
I tried DC-Phoenix, but as a result it failed. The FAST BOOT which I was able to use until now can not be used and the power can not be turned on.
I am disappointed that the method of recovery is gone.
Thank you for your support.
Click to expand...
Click to collapse
Well, with fastboot, adb, bootloader mode, and eRecovery gone there is not really a lot you can do short of returning the device to Huawei (hopefully you still have warranty) for a replacement. Just tell them your phone died.

messed up unlock.

Followed a tutorial on how to install lineage-14.1-20180817-UNOFFICIAL-cedric, but somehow missed a step or messed up.
I unlocked the bootloader, not exactly but in general: flashed the boot.img and rebooted, phone started and was able to use android.
But some strange problems occurred, like somehow my PIN was not recognized and device failed to factory reset.
Locked the bootloader again because of the warning (here's my mistake I guess) and now am unable to flash or revert to stock.
I am able to boot into android, did enable USB debug and bootloader unlock.
But everytime I boot I get the warning a different kernel has been installed (instead of wrong key before) and permission is always denied remotely.
C:\ad>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) OKAY [ 0.068s]
Writing 'logo' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 0.077s
This happens with everything, permission denied.
If I try to unlock it again via fastboot commandline (Windows) I get:
"(bootloader) invalid boot state"
Starting the phone in fastboot, the status is "flashing_locked".
What can I do now?
I am a noob, therefor the tutorial...
Thanks

thugscorpion said:
Followed a tutorial on how to install lineage-14.1-20180817-UNOFFICIAL-cedric, but somehow missed a step or messed up.
I unlocked the bootloader, not exactly but in general: flashed the boot.img and rebooted, phone started and was able to use android.
But some strange problems occurred, like somehow my PIN was not recognized and device failed to factory reset.
Locked the bootloader again because of the warning (here's my mistake I guess) and now am unable to flash or revert to stock.
I am able to boot into android, did enable USB debug and bootloader unlock.
But everytime I boot I get the warning a different kernel has been installed (instead of wrong key before) and permission is always denied remotely.
C:\ad>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) OKAY [ 0.068s]
Writing 'logo' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 0.077s
This happens with everything, permission denied.
If I try to unlock it again via fastboot commandline (Windows) I get:
"(bootloader) invalid boot state"
Starting the phone in fastboot, the status is "flashing_locked".
What can I do now?
I am a noob, therefor the tutorial...
Thanks
Click to expand...
Click to collapse
First, this thread is for g5 plus not for g5, so post in that thread.
Solution:- which firmware you are trying is it for g5 or g5+, if you flash wrong firmware then this happen, try downloading your firmware and then flash it.now you are on stock. If you don't know how to Flash, you can prefer XDA threads or use Lenovo Moto smart assistant app (pc) that will flash the firmware for you.
If you want to go on custom ROM then, first go to stock rom as it will restore your boot.img and custom ROM can work. If you directly want to go to custom rom (skiping above procedure) then flash boot.img from ADB or twrp and install custom ROM.
Here is the thread to Flash stock ROM:-
https://forum.xda-developers.com/g5...-flash-stock-romfactory-t3691396/post74221633
Link for Lenovo Moto smart assistant app:-
https://support.lenovo.com/in/en/downloads/ds101291
And if you are using XDA threads it has old firmware which can brick you Device you can get your firmware from here and chose which firmware channel you belong:-
https://mirrors.lolinet.com/firmware/moto/potter/official/
At last to not take risk remove bootloader and gpt commands from ADB.

It is a G5 Plus and I get permission denied with adb or fastboot.
In android I van go go developers option and OEM unlock is ON, if I go fastboot, flashing is locked.

thugscorpion said:
It is a G5 Plus
Click to expand...
Click to collapse
Well LOS14....-cedric is the G5 variant. You didn't flash the wrong firmware did you?

Apperently I did...
Is there a way to fix it?
the Lenovo recovery tool mentioned above doesn't do anything with the "flash" option.
Put the phone in fastboot mode and it is not recognized by the Lenovo application.
Can still manual send fastboot and adb via the Windows command line but still "locked" and "pemrission denied".

the command fastboot flashing unlock did the trick for now.
But, I want to revert to stock, what is the correct way?
Can someone point me to a good how to or tutorial with recent files?
EDIT: I see LineageOS officially is not supporting the G5 plus, but there is a unofficial version in the G5 plus forums.
I'm still thinking of customizing because of all the bloatware and sluggish performance.

reïnstalled TWRP, put Pixel Experience on an SD card, booted TWRP recovery, did several attempts to clean all data / cache etc. but got several errors, retried, rebooted, chose all options and installed Pixel.
First try phone did not boot, froze on Pixel boot, again wiped everything, again installed Pixel and now it boots.
good lesson.
Phone is not entirely recognized the correct way, google security speaks of a Moto X (4) and the phone itself mentions the exact model number instead of Moto G5 Plus.

thugscorpion said:
reïnstalled TWRP, put Pixel Experience on an SD card, booted TWRP recovery, did several attempts to clean all data / cache etc. but got several errors, retried, rebooted, chose all options and installed Pixel.
First try phone did not boot, froze on Pixel boot, again wiped everything, again installed Pixel and now it boots.
good lesson.
Phone is not entirely recognized the correct way, google security speaks of a Moto X (4) and the phone itself mentions the exact model number instead of Moto G5 Plus.
Click to expand...
Click to collapse
Yeah security does show as Moto X4. That's normal.

One final question: On reboot I always end up in the fastboot menu without holding power and volume down, I also always get the unlock warning.
Is this a sign the bootloader is still not okay?
And is there an easy way to fix it?