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.

Reboot to recovery first after flashing twrp. Then reboot from twrp recovery.
Don't worry about the message. It's just a warning.
Sent from my Moto G (4) using Tapatalk

funplay said:
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.
Click to expand...
Click to collapse
do exactly what i give-
1.Put your device in bootloader mode(make sure the usb debugging is on)
2.Open adb (make sure adb and twrp are in the same folder)by shift+right click,then open command window here(do this where adb is installed).
3.Type: fastboot flash recovery [name of twrp image].img
4.Then in the bootloader menu toggle to restart bootloader .(Not restart because the recovery will get replaced by stock recovrey)
5.Open recovery.twrp should be installed
If you have any problem send the printscreen of cmd.

Step 4 : Choose Reboot to recovery mode using volume keys. Press power button to select.
Sent from my Moto G (4) using Tapatalk

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:
fastboot flash recovery twrp.img
(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
Nupe.

Unable to flash TWRP on Moto G4 Plus

I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks

unknown_geek said:
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
Click to expand...
Click to collapse
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.

1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A

echo92 said:
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
Click to expand...
Click to collapse
Hi @echo92,
Thanks for pointing out what I was doing wrong. I now realize that the TWRP recovery was being overwritten by stock recovery and I didn't know adb commands don't work while still in bootloader mode.
I did boot into recovery mode from the bootloader (using the volume buttons from the phone) and it worked.
And the ID: bad key is also gone and now it shows ID: N/A.
Thanks again for your help!
Regards

____Mdd said:
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
Click to expand...
Click to collapse
Hi @____Mdd,
I rebooted into recovery right after flashing TWRP and it worked fine. Now, I'm able to boot into TWRP recovery.
Thanks for your response.
Regards.

Im Facing this issue while flashing TWRP
C:\adb>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (12644 KB) OKAY [ 0.422s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse

vaibhavhr2010 said:
Im Facing this issue while flashing TWRP
Click to expand...
Click to collapse
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?

echo92 said:
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
Click to expand...
Click to collapse
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3

vaibhavhr2010 said:
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
Click to expand...
Click to collapse
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?

echo92 said:
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
Click to expand...
Click to collapse
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.

vaibhavhr2010 said:
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
Click to expand...
Click to collapse
That TWRP won't work, if it's for Titan. The codename for Moto G4/plus is athene, only TWRP images specifying athene in their name will work.
https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 or https://eu.dl.twrp.me/athene/ give these a try instead

PSA: 'fastboot boot'ing a bad image can confuse the A/B bootloader (fix inside)

Yesterday, I was messing about trying to fastboot boot other MSM8998 TWRP boot.imgs, with the hopes that the device-trees on some of them would be close enough to get far enough in boot to bring up the USB port (even if they didn't mount anything or bring up the screen). As it turns out, none of them did (and, in fact, they all blanked the screen and went back to having the USB interface enumerate as fastboot -- how could that be? does anyone understand what could cause fastboot to reject a kernel before even trying to boot it?), but when I was done for the day, I had another disturbing event: when I tried to boot the device normally, it would simply sit there at the fastboot screen, and in fact, when I tried to boot into recovery, it would still just kick me back to fastboot.
This was very scary -- without factory images to reflash it with, I thought I had bricked my device! I did a fastboot getvar all, and saw:
Code:
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:3
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
So apparently just fastboot booting something that fails to boot can cause fastboot to declare that the live system image is no good.
If this happens to you, the answer to this is to make sure that you have the latest platform-tools (I had a properly oldschool version of fastboot that I've been kicking along on my Mac from the unrevoked era...) -- get them from Google -- and you can un-confuse the bootloader even without flashing a new image by doing a fastboot set_active a.
Then your phone will boot again. Phew!

So useful, thanx man!

Thank you, this is good to know.

Can anyone share system dump pls?

No need for system dump, the factory images are up: https://developers.google.com/android/images

joshua_ said:
Yesterday, I was messing about trying to fastboot boot other MSM8998 TWRP boot.imgs, with the hopes that the device-trees on some of them would be close enough to get far enough in boot to bring up the USB port (even if they didn't mount anything or bring up the screen). As it turns out, none of them did (and, in fact, they all blanked the screen and went back to having the USB interface enumerate as fastboot -- how could that be? does anyone understand what could cause fastboot to reject a kernel before even trying to boot it?), but when I was done for the day, I had another disturbing event: when I tried to boot the device normally, it would simply sit there at the fastboot screen, and in fact, when I tried to boot into recovery, it would still just kick me back to fastboot.
This was very scary -- without factory images to reflash it with, I thought I had bricked my device! I did a fastboot getvar all, and saw:
So apparently just fastboot booting something that fails to boot can cause fastboot to declare that the live system image is no good.
If this happens to you, the answer to this is to make sure that you have the latest platform-tools (I had a properly oldschool version of fastboot that I've been kicking along on my Mac from the unrevoked era...) -- get them from Google -- and you can un-confuse the bootloader even without flashing a new image by doing a fastboot set_active a.
Then your phone will boot again. Phew!
Click to expand...
Click to collapse
With that said you should still probably reflash partition_b because it might interfere with future updates which I assume you know how they work. Images like @hazzamon said are finally available.
Sent from my marlin using XDA Labs

Doesn't pixel 1 have a TWRP version which can see both slots and boot to either? Did you try to install or just fastboot to .img file? Did you unlock the bootloader? If you bought it from Google, I would think the bootloader should be pretty easy to unlock, there is the option to allow it in the dev settings.

I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Any Help would be greatly appreciated!
Thanks!

I was looking through the bootloader screen and apparently there is a download mode, perhaps you could sideload an OTA

RagedElimanator said:
With that said you should still probably reflash partition_b because it might interfere with future updates which I assume you know how they work. Images like @hazzamon said are finally available.
Click to expand...
Click to collapse
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
pvillegeek said:
I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Click to expand...
Click to collapse
Have you tried with a modern fastboot?
What does 'fastboot getvar all' tell you?
You need to set_active, like I mentioned.
pixel-painter said:
I was looking through the bootloader screen and apparently there is a download mode, perhaps you could sideload an OTA
Click to expand...
Click to collapse
The download mode is a no-op on production Walleye, I think
pixel-painter said:
Doesn't pixel 1 have a TWRP version which can see both slots and boot to either? Did you try to install or just fastboot to .img file? Did you unlock the bootloader? If you bought it from Google, I would think the bootloader should be pretty easy to unlock, there is the option to allow it in the dev settings.
Click to expand...
Click to collapse
I took the steps I mentioned in the OP You can't fastboot boot, fastboot set_active, or fastboot flash something without unlocking the bootloader.

joshua_ said:
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
Have you tried with a modern fastboot?
What does 'fastboot getvar all' tell you?
You need to set_active, like I mentioned.
The download mode is a no-op on production Walleye, I think
I took the steps I mentioned in the OP You can't fastboot boot, fastboot set_active, or fastboot flash something without unlocking the bootloader.
Click to expand...
Click to collapse
Which is why I asked if the bootloader was unlocked

joshua_ said:
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
Click to expand...
Click to collapse
I wonder if that means that flashing the factory image replaces the opposite slot with those prebuilt odex files then. On the original Pixel and Pixel XL it just flashed the opposite slot with an empty image.

joshua_ said:
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
Have you tried with a modern fastboot?
What does 'fastboot getvar all' tell you?
You need to set_active, like I mentioned.
The download mode is a no-op on production Walleye, I think
I took the steps I mentioned in the OP You can't fastboot boot, fastboot set_active, or fastboot flash something without unlocking the bootloader.
Click to expand...
Click to collapse
Well if you want to use slot_b then you might as well flash the image over that the slot_a pretty much takes place of what slot_b was in the beginning, but yeah you are right though about having slot_b at preconfigured state yet that's if you are on slot_a.

I think I might be in real trouble. I can't boot anything at all, just like others in this thread. I can't even boot TWRP, and I get this error:
PS C:\Users\hanna\Desktop\platform-tools> fastboot boot twrp-3.1.1-beta1-walleye.img
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.734s
Click to expand...
Click to collapse
I've tried setting the active slot to a, and back to b. I've tried multiple times to flash the stock image files from Google. They appear to flash normally, but I still can't boot.
All of this started after I accidentally tried to boot the recovery image from the pixel 2 xl. Something got seriously messed up, and I can't figure out how to repair it.
Does anyone know what else I can try?

mtpease said:
I think I might be in real trouble. I can't boot anything at all, just like others in this thread. I can't even boot TWRP, and I get this error:
I've tried setting the active slot to a, and back to b. I've tried multiple times to flash the stock image files from Google. They appear to flash normally, but I still can't boot.
All of this started after I accidentally tried to boot the recovery image from the pixel 2 xl. Something got seriously messed up, and I can't figure out how to repair it.
Does anyone know what else I can try?
Click to expand...
Click to collapse
Use cmd instead of powershell. I've had issues relating to fastboot/adb with PS in the past
Sent from my Pixel 2 using Tapatalk

mtpease said:
I think I might be in real trouble. I can't boot anything at all, just like others in this thread. I can't even boot TWRP, and I get this error:
I've tried setting the active slot to a, and back to b. I've tried multiple times to flash the stock image files from Google. They appear to flash normally, but I still can't boot.
All of this started after I accidentally tried to boot the recovery image from the pixel 2 xl. Something got seriously messed up, and I can't figure out how to repair it.
Does anyone know what else I can try?
Click to expand...
Click to collapse
I was in the same boat. Would only boot to bootloader after typical manual flash-all of the system image (no recovery, no nothing, just bootloader).
Here's what I did (Windows 10):
1) Update fastboot/adb
2) Download and extract latest 8.0 image (ends in 25)
3) Open CMD (not powershell)
4) fastboot set_active other
5) Manually flash bootloader (failed for me), radio (went ok), update .zip (some errors), reboot bootloader between each:
fastboot flash bootloader <location>
fastboot flash radio <location>
fastboot update <location of image-walleye-opd1.170816.025.zip>
6) fastboot set_active other then repeat bootloader, radio, update.zip manual flashes
Though I read this about the og Pixels... Basically just manually flash images to both slots when all else fails.

joetheshmo said:
Use cmd instead of powershell. I've had issues relating to fastboot/adb with PS in the past
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I'm trying this now, but I can't get my phone to boot. It just goes back to the bootloader (which is unlocked). I'm getting the same "FAILED (remote: Failed to load/authenticate boot image: Load Error)" error. My adb/fastboot is at the latest version. Trying to flash the 8.1 factory image.

joshua_ said:
Yesterday, I was messing about trying to fastboot boot other MSM8998 TWRP boot.imgs, with the hopes that the device-trees on some of them would be close enough to get far enough in boot to bring up the USB port (even if they didn't mount anything or bring up the screen). As it turns out, none of them did (and, in fact, they all blanked the screen and went back to having the USB interface enumerate as fastboot -- how could that be? does anyone understand what could cause fastboot to reject a kernel before even trying to boot it?), but when I was done for the day, I had another disturbing event: when I tried to boot the device normally, it would simply sit there at the fastboot screen, and in fact, when I tried to boot into recovery, it would still just kick me back to fastboot.
This was very scary -- without factory images to reflash it with, I thought I had bricked my device! I did a fastboot getvar all, and saw:
Code:
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:3
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
So apparently just fastboot booting something that fails to boot can cause fastboot to declare that the live system image is no good.
If this happens to you, the answer to this is to make sure that you have the latest platform-tools (I had a properly oldschool version of fastboot that I've been kicking along on my Mac from the unrevoked era...) -- get them from Google -- and you can un-confuse the bootloader even without flashing a new image by doing a fastboot set_active a.
Then your phone will boot again. Phew!
Click to expand...
Click to collapse
What if both partitions show as not successful?
Code:
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:5
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no

Sorry to resurect this from the dead, but I was in the same boat and there doesn't seem to be an answer here, So I'll tell you what I did.
1. I booted into linux
2. Made sure my android platform tools were up to date
3. from the bootload I went to recovery(which would not open, ended up with phone with black screen)
4. from that black screen I could use Duece's tool and that fix the phone to where it will at least boot properly.
In hope this helps

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?

Moto G7 Soft brick

I was asked yesterday to install LineageOS on someone's phone. It's been a few years, and I screwed some stuff up and now I need help. I'll go through what I did first and then I'll go through my current problems.
Enabled USB debugging and OEM unlock in the phone's settings.
Used ADB to reboot ot bootloader (adb reboot bootloader)
Verified the device's existence with adb.
Used Motorola's website to unlock the phone's bootloader. Process went fine.
Restarted the phone. Got the message that the bootloader was unlocked.
Went back to developer settings to re-enable USB debugging.
Rebooted to fastboot.
Typed in "fastboot flash boot twrp.img" (the file name was longer, but I'll abbreviate for the sake of brevity).
Wiped data.
Formatted data
Now, this is where the problems started. With the data formatted, I couldn't sideload anything, mounting didn't work, and the TWRP file manager showed literally nothing on the phone. No file system or anything, it looked like. This was done on a Linux computer (which also turned two of my MicroSD cards into read only. Thanks Fedora.
Anyway, I figured I should go back to fastboot to fix things. This was probably a mistake, because now I can't do anything. I can't flash TWRP, I can't boot into it, nothing. For example, when I type in
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
I get this:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (27096 KB) OKAY [ 0.802s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I Googled around. Some people said I might need to flash partitions from gpt.bin, but that didn't work either. Every time, I get "invalid partition name xxx."
What can I do?
Thanks you in advance.