Im unable to root moto g5s plus, TWRP is not also working get error.
You include no useful information so not much folks can do to help out.
Which model/variant?
Are you unlocked?
What TWRP version?
What's the error?
How did you try to install it?
Include answers to those and more if you want assistance.
Moto G5S Plus XT1806, Resurrection Remix ROM, AL-ice Kernel, MultiROM, Tapatalk 4.9.5
Which model/variant?
moto g5s plus Model XT1804
Are you unlocked?
unlock
What TWRP version?
twrp-3.1.1-sanders.img
What's the error?
"(bootloader) Image not signed or corrupt"
How did you try to install it?
" adb through
Steps to flash TWRP Recovery.
Download and copy recovery image to ADB driver folder.
Open command promt on ADB folder.
Run this command
Code:
fastboot flash recovery twrp-3.1.1-sanders.img
Now run this command
Code:
fastboot reboot recovery
Now you will be booted in TWRP recovery."
PrafulP143 said:
Which model/variant?
moto g5s plus Model XT1804
Are you unlocked?
unlock
What TWRP version?
twrp-3.1.1-sanders.img
What's the error?
"(bootloader) Image not signed or corrupt"
How did you try to install it?
" adb through
Steps to flash TWRP Recovery.
Download and copy recovery image to ADB driver folder.
Open command promt on ADB folder.
Run this command
Code:
fastboot flash recovery twrp-3.1.1-sanders.img
Now run this command
Code:
fastboot reboot recovery
Now you will be booted in TWRP recovery."
Click to expand...
Click to collapse
There's another thread with newer twrp. Use that. Disregard image not signed.
Related
Hi, can anyone clarify this instruction, I have just finished unlocking bootloader and about to install custom recovery:
Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
shadow071506 said:
Hi, can anyone clarify this instruction, I have just finished unlocking bootloader and about to install custom recovery:
Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
Click to expand...
Click to collapse
The statement means you have to flash(install) the custom recovery by using a command like:
Code:
fastboot flash recovery recovery.img
Or by using a toolkit, however you can't just boot the recovery with a command like this:
Code:
fastboot boot recovery.img
crushalot said:
The statement means you have to flash(install) the custom recovery by using a command like:
Code:
fastboot flash recovery recovery.img
Or by using a toolkit, however you can't just boot the recovery with a command like this:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
thanks ..that really helped
Hi
Is stock ROM for Moto G5s Plus available to download? I need to reflash my phone with stock ROM and unable to find it yet.
Thanks
Full firmware is available!
Here you go...
https://drive.google.com/uc?id=0B9VEaFoqTCkLX2JUd0lVdzZLUUk&export=download
Please tell me if it relocks your bootloader.
Thanks Raj.S. Just to confirm, this is for Indian variant of Moto G5s Plus, right?
Update: Tried to flash this using TWRP but got error: Invalid zip file format!
Tried fastboot update method and that also results into error: no android-info.txt file found.
Please help.
Ok, was able to install the ROM with fastboot. However, it doesn't relock bootloader.
There's a few additional steps required to relock the bootloader.
If you run "fastboot OEM lock" then it will tell you more.
Essentially you need to execute this command twice, then flash the OEM data (boot and system), and then execute the "fastboot OEM lock" command once more.
That should lock things back up again.
@Raminder_Singh
How did you overcome the no android-info.txt file found error?
I am unable to flash the ROM via fastboot.
i was following this guide https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182 and i did everything up until "fastboot flash recovery twrp_james.img
fastboot reboot recovery" and it says the image isnt signed or corrupted any help would be nice thanks.
skyrimman33 said:
i was following this guide https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182 and i did everything up until "fastboot flash recovery twrp_james.img
fastboot reboot recovery" and it says the image isnt signed or corrupted any help would be nice thanks.
Click to expand...
Click to collapse
Have you successfully unlocked bootloader?..I get same error messages when flashing on e5 play with unlockable bootloader..Motorola will not add the Verizon James variant to oem unlock list..but a locked bootloader will give you that error message..
I´m trying to install a custom ROM to get android 9 on my g6 h872. When trying to flash recovery.img to install TWRP, i get the error:
writing 'recovery'...
FAILED (remote: unknown command)
I tried with the "fastboot boot recovery.img" command but it won´t work either. Help would be much appreciated.
Are using adb command?
If yes it's not working
You can do it easy by
1- get temp root using su98.apk
2- use flashify to flash orange fox or other recovery img
3- reboot to recovery by using adb command "adb reboot recovery"
Dev4up said:
Are using adb command?
If yes it's not working
You can do it easy by
1- get temp root using su98.apk
2- use flashify to flash orange fox or other recovery img
3- reboot to recovery by using adb command "adb reboot recovery"
Click to expand...
Click to collapse
You can also do this :
4- install latest magisk
5- install any app for reboot to recovery from play store.
6- enjoy
This method work just in Oreo or nougat rom .
Use this tutorial https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 tmo h872 fastboot flashing isn't working on this device
I'm running on realme 8i with RMX3151_11_C.19, locked bootloader
(sorry for my english)
If I run adb reboot fastboot it boots in recovery, but I can still run fastboot devices. With adb reboot recovery it boots in recovery, but it's not recognized infastboot. Unfortunatly, fastboot oem unlock returns
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Does anyone know why is it like that and if I unlock the bootloader will I be able to flash custom recovery like on a normal phone?
Treeager said:
I'm running on realme 8i with RMX3151_11_C.19, locked bootloader
(sorry for my english)
If I run adb reboot fastboot it boots in recovery, but I can still run fastboot devices. With adb reboot recovery it boots in recovery, but it's not recognized infastboot. Unfortunatly, fastboot oem unlock returns
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Does anyone know why is it like that
Click to expand...
Click to collapse
adb reboot bootloader
mvikrant97 said:
adb reboot bootloader
Click to expand...
Click to collapse
This only reboots the phone
Treeager said:
I'm running on realme 8i with RMX3151_11_C.19, locked bootloader
(sorry for my english)
If I run adb reboot fastboot it boots in recovery, but I can still run fastboot devices. With adb reboot recovery it boots in recovery, but it's not recognized infastboot. Unfortunatly, fastboot oem unlock returns
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Does anyone know why is it like that and if I unlock the bootloader will I be able to flash custom recovery like on a normal phone?
Click to expand...
Click to collapse
The fastest way to unlock your phone's bootloader is using mtk client.
You will find plenty of tutorials on youtube as well as XDA on how to use mtk client.
Please comment down here if you need any help.
UPDATE: So I unlocked the bootloader with mtk, and with this weird fastboot I can flash recoveries. But if I do "adb reboot fastboot", I can execute fastboot commands, but the recovery becomes the stock recovery wich is a little strange to me... Anyway, how to decrypt the storage in twrp? And also I am trying to install Pixel OS from here. I installed the pixel recovery too.