Database Users

Stuck on installing TWRP

Hello and thanks in advance to everyone,
I am trying to root my moto g4 but I am stuck on installing a recovery. I did unlock the bootloader and when I turn on the phone i am greeted with"this device is unlocked and can't be trusted"
Yet when i try to flash the recovery it states that it failed to install since the package is unsigned:
C:\Users\Jelle\Desktop\Nieuwe map>mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12496 KB)...
OKAY [ 0.405s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.344s]
finished. total time: 0.748s
Re-entering my unlock code also does not work as it gives me this message:
C:\Users\Jelle\Desktop\Nieuwe map>fastboot oem unlock NYRTWS*************
...
(bootloader) invalid boot state
OKAY [ -0.000s]
finished. total time: -0.000s
Does someone have any idea on what the issue is, am I missing something?
Thank you in advance!

Twrp is for motog4 plus aka athene. Make sure your device is the same.
Just reboot to recovery after you flash twrp using fast boot. Do not reboot your device to your home screen as your recovery partition will be rewritten with the stock recovery.
Do not worry about the message. It doesn't say that flashing failed. It only gives you a warning that it's not signed. That message is displayed even if you flash the stock recovery using fast boot.
Sent from my Moto G (4) using Tapatalk

Silesh.Nair said:
Twrp is for motog4 plus aka athene. Make sure your device is the same.
Just reboot to recovery after you flash twrp using fast boot. Do not reboot your device to your home screen as your recovery partition will be rewritten with the stock recovery.
Do not worry about the message. It doesn't say that flashing failed. It only gives you a warning that it's not signed. That message is displayed even if you flash the stock recovery using fast boot.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
that totally worked! thank you very much

same problem mentioned above but after recovery mode my devicxe says no command.
help mw plzzz

sauravchandela95 said:
same problem mentioned above but after recovery mode my devicxe says no command.
help mw plzzz
Click to expand...
Click to collapse
If you're getting a screen with 'no command', that's the stock recovery on your device.
Are you rebooting to the recovery straight after flashing TWRP? Do you have an unlocked bootloader and what version of TWRP are you flashing? What commands are you using to flash?
You may wish to try booting with TWRP first:
1)On a device with an unlocked bootloader, boot to the bootloader screen.
2)Connect your device to your computer via a high quality USB data cable or the original USB cable.
3)Ensure your TWRP image is copied to your ADB folder.
4)Open an ADB terminal. Verify your device is communicating with your computer by typing 'fastboot devices' without quotes. Press Enter. You should get a serial number response.
5)If so, then type 'fastboot boot twrp.img' without quotes. Replace twrp.img with the actual full file name of your TWRP image in your ADB folder including the file extension. For example, if your TWRP image file name is shreps_twrp_3_1_1.img, the full command would be fastboot boot shreps_twrp_3_1_1.img You can type the first few letters of the file name and press Tab on your keyboard to automatically complete the file name if you so wish.
6)Press Enter, and your device should download TWRP and boot to TWRP.

Root, Downgrade and install TWRP

For the last week I have been trying to root and install TWRP on my Huawei p8 Lite ALE21. Sofar every attempt has failed.
Steps taken:
Get Bootloader Code
Unlock bootloader with "fastboot oem unlock"
Flash TWRP with "fastboot flash recovery recovery.img"
Result:
When booting into recovery the default "Huawei eRecovery" opens, not TWRP
No app can detect root
Additional info:
TWRP form here: http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
Trying to debug the problem, I entered
Code:
fastboot getvar all
this returned
Code:
getvar:all FAILED (remote: Command not allowed)
Additional I have tried to downgrade to android 5.0 again, but after copying the Firmware to the "dload" folder and holding the Volume-Up and Down and Power buttons, the phone wouldn't do anything but show the huawei logo and turn off.
Any help would be very appreciated!
Thank you in advance,
Oisin

Oisins said:
For the last week I have been trying to root and install TWRP on my Huawei p8 Lite ALE21. Sofar every attempt has failed.
Steps taken:
Get Bootloader Code
Unlock bootloader with "fastboot oem unlock"
Flash TWRP with "fastboot flash recovery recovery.img"
Result:
When booting into recovery the default "Huawei eRecovery" opens, not TWRP
No app can detect root
Additional info:
TWRP form here: http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
Trying to debug the problem, I entered
Code:
fastboot getvar all
this returned
Code:
getvar:all FAILED (remote: Command not allowed)
Additional I have tried to downgrade to android 5.0 again, but after copying the Firmware to the "dload" folder and holding the Volume-Up and Down and Power buttons, the phone wouldn't do anything but show the huawei logo and turn off.
Any help would be very appreciated!
Thank you in advance,
Oisin
Click to expand...
Click to collapse
In order to boot in twrp recovery you should first remove your usb cable,once is done,press and hold volume up and power button,once you see huawei logo,release power button but keep press on volume up,about firmware witch build number do you have on your phone,share more info if you want a quick help

"No app can detect root"
TWRP isn't root
"fastboot flash recovery recovery.img"
Any error?
"....(remote: Command not allowed)"
i think you have to unlock bootloader

Thank you for you quick response!
Running "fastboot flash recovery recovery.img" returns
Code:
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.880s]
writing 'recovery'...
OKAY [ 2.084s]
finished. total time: 2.967s
I checked if the bootloader is unlocked with "fastboot oem get-bootinfo"
Code:
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
I also tried booting into recovery without the cable plugged it, but it still just booted into "eRocovery"
More info
Product: ALE-L21
Serial: W3D4C16916992523
Build: ALE-L21C432BB574

just try this:
1) (re) boot normally
2) attach to pc with usb cable
3) reboot into recovery using adb command: adb reboot recovery

ItalianWolf said:
just try this:
1) (re) boot normally
2) attach to pc with usb cable
3) reboot into recovery using adb command: adb reboot recovery
Click to expand...
Click to collapse
The phone reboots, shows the HUAWEI logo and then turn off again.

Sorry, i didn't read the post linked.
You need twrp 3.0.2 for B5xx, i was thinking you had the right one (2.8.7 works on kk and maybe lollipop), so here you are: http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320

ItalianWolf said:
Sorry, i didn't read the post linked.
You need twrp 3.0.2 for B5xx, i was thinking you had the right one (2.8.7 works on kk and maybe lollipop), so here you are: http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320
Click to expand...
Click to collapse
It worked! Thank you very very much! I spend sooo much time on this... wow thanks!

Help me please i can't flash twrp oneplus 5 FAILED

oneplus 5 FAILED remote: Requested download size is more than max allowed
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
my oneplus 5 version oxygenos 4.5.5 latest

abuawaahed said:
oneplus 5 FAILED remote: Requested download size is more than max allowed
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
Click to expand...
Click to collapse
Try 'boot recovery.img' then flash it via twrp

Krsambhav16 said:
Try 'boot recovery.img' then flash it via twrp
Click to expand...
Click to collapse
how to try boot recovery
please explain

abuawaahed said:
how to try boot recovery
please explain
Click to expand...
Click to collapse
I'm sorry but you seem to be doing something without researching or understanding what it is. If you don't know what you're doing please don't do it.

abuawaahed said:
oneplus 5 FAILED remote: Requested download size is more than max allowed
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
my oneplus 5 version oxygenos 4.5.5 latest
Click to expand...
Click to collapse
i got the same error while using cmd from windows 10, but i was able to successfully install the recovery using git bash.
https://git-scm.com/download/win

pankajsammal said:
i got the same error while using cmd from windows 10, but i was able to successfully install the recovery using git bash.
https://git-scm.com/download/win
Click to expand...
Click to collapse
git bash for what

@abuawaahed
Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery xxxx.img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..
Also it's better to ask in Question and answer thread...

abuawaahed said:
git bash for what
Click to expand...
Click to collapse
Used gitbash terminal to use the fastboot command to flash recovery.

mukesh22584 said:
@abuawaahed
Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery xxxx.img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..
Also it's better to ask in Question and answer thread...
Click to expand...
Click to collapse
thanks but also not working
fastboot erase recovery
failed (remote :unknown command )
fastboot erase cache
failed (remote :unknown command )

pankajsammal said:
Used gitbash terminal to use the fastboot command to flash recovery.
Click to expand...
Click to collapse
$ fastboot flash recovery twrp-3.1.1-0-oneplus5.img
sending 'recovery' (24404 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.001s
also failed

Have you unlocked bootloader.....
If yes change USB port/cable may help you...
Also check that you've enabled usb debugging in developer option....

And which version you are using adb&fastboot setup and drivers? Try different versions Adb setup 1.4.3 example.

mukesh22584 said:
Have you unlocked bootloader.....
If yes change USB port/cable may help you...
Also check that you've enabled usb debugging in developer option....
Click to expand...
Click to collapse
yes unlocked bootloader done
oem enable
usb debugging on

Download the latest Platform Tools package directly from Google and try with these: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Also indeed make sure that you have "checked" if you have properly unlocked your bootloader (follow the directions here

Gonik said:
Download the latest Platform Tools package directly from Google and try with these: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Also indeed make sure that you have "checked" if you have properly unlocked your bootloader (follow the directions here
Click to expand...
Click to collapse
not working
i think because of oxygenos 4.5.5

abuawaahed said:
not working
i think because of oxygenos 4.5.5
Click to expand...
Click to collapse
No it's not. It's something that you are doing wrong or your fastboot executable is too old or something. Works fine in OOS 4.5

just update to latest fastboot/adb package and flashing should be fine.

inffy said:
No it's not. It's something that you are doing wrong or your fastboot executable is too old or something. Works fine in OOS 4.5
Click to expand...
Click to collapse
see image unlock bootloader is ok

acmerw said:
just update to latest fastboot/adb package and flashing should be fine.
Click to expand...
Click to collapse
adb-setup-1.4.3 installed

I had the exact same issue, my main rig is on the latest update of windows so the adb minimal drivers couldn't install properly (windows problem)
so tried to do this on my laptop (not on the latest update) and was able to install the drivers.
Now when it came to flashing the recovery - I kept getting the same error as you.
To fix this I tried a different USB port (2.0) and it worked.
Give it a try, should work now.

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

my h872 is brick,even though the download mode and system,anyone could help me?

my h872 is brick,even though the download mode and system,now i can only boot into the fastboot,how can i get my phone work?
i have tried fastboot flash command to flash boot or recovery ,etc,it always show:
sending 'bootloader'
ok,
target reported max download size of 536870912 bytes
sending 'laf' (29916 KB)...
OKAY [ 1.029s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 1.050s
might my drives is not proper? i have change the usb point or another device,it always is this...

小阿瑟 said:
my h872 is brick,even though the download mode and system,now i can only boot into the fastboot,how can i get my phone work?
i have tried fastboot flash command to flash boot or recovery ,etc,it always show:
sending 'bootloader'
ok,
target reported max download size of 536870912 bytes
sending 'laf' (29916 KB)...
OKAY [ 1.029s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 1.050s
might my drives is not proper? i have change the usb point or another device,it always is this...
Click to expand...
Click to collapse
How'd you get here? (Your phone bricked)

christopherrrg said:
How'd you get here? (Your phone bricked)
Click to expand...
Click to collapse
i use the twrp flash a wrong recover or maybe wrong root？mostly it is ，

小阿瑟 said:
i use the twrp flash a wrong recover or maybe wrong root？mostly it is ，
Click to expand...
Click to collapse
I just asked because the logs show that your LAF partition isn't flashing and from what I've been reading so far about the LAF partition is that it is a very fragile thing.
Have you tried a factory kdz with LGUP?

christopherrrg said:
I just asked because the logs show that your LAF partition isn't flashing and from what I've been reading so far about the LAF partition is that it is a very fragile thing.
Have you tried a factory kdz with LGUP?
Click to expand...
Click to collapse
what a amazing ! i got another‘s help,now i can boot into the twrp,
but after i install the AospExtended, it just play the aex booting video,how many times i erase all date include system and date,cache,etc.
now ,iwant to konw how to get it into a system

Find stock.kdz to flash using LGUP, reflash TWRP using fast boot commands. Should boot correctly after stock .kdz is applied. Once confirmed your phone works correctly.. Boot into TWRP factory reset, and wipe partition, then attempt to flash your choice of custom ROM.

小阿瑟 said:
what a amazing ! i got another‘s help,now i can boot into the twrp,
but after i install the AospExtended, it just play the aex booting video,how many times i erase all date include system and date,cache,etc.
now ,iwant to konw how to get it into a system
Click to expand...
Click to collapse
Hi mate,
I got into the same problem as u did, i hope you solved your problem by now. Will share to me how you solve it?
Did u flash twrp via fastboot? If u do, can you share to me the command u used?
Thanks alot for your help.

spaceantz said:
Hi mate,
I got into the same problem as u did, i hope you solved your problem by now. Will share to me how you solve it?
Did u flash twrp via fastboot? If u do, can you share to me the command u used?
Thanks alot for your help.
Click to expand...
Click to collapse
Download mode via holding VOL+ and plug in GOOD USB-C cable into Windows 10 laptop/desktop with LG USB drivers, Uppercut, LGUP installed. Then KDZ 10E image to bring back to stock Nougat (losing all root, data, and it'll force encryption): http://firmware-up.com/system/files/basicpr/8d0e1fc8/H87210e_00_0322.kdz

LG G6 H872 stucked in Download mode with 5 dots
My phone LG G6 H872 got stucked in download mode with 5 dots in the process of getting it rooted, pls anyone with information on how to get it out of this should pls help. you can mail me direct on [email protected]