Database Users

Error Flashing TWRP on unlocked XT1640

Greetings everyone, I just got a new XT1640. I installed on it the ATHENE_NPJS25.93-14-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ROM from here. Went to motorola's site and unlocked the phone. But I still can't flash TWRP.
this is what happens:
Code:
fastboot flash boot twrp-3.0.2-0-athene.img
target reported max download size of 536870912 bytes
sending 'boot' (12496 KB)...
OKAY [ 0.435s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.186s]
finished. total time: 0.621s
I tried versions 3.1.1, 3.1.0 and 3.0.2 , all from the twrp site. Any ideas?

@yohanleafheart
Why do you want to brick your device ?
Check the command that you are entering, "BOOT" ???? That's "RECOVERY"
write command: fastboot flash recovery xyz.img
(Refer any Recovery or flashing thread)
EDIT:
When you used "fastboot flash boot twrp.img"
you got OKAY at last,
That means you flashed Recovery into Boot/kernel !!
If you face any kernel related problem on startup, then you will need to get original Boot.img and flash it...

Haha hey bro be careful while using commands .. u gonna poision your phone

In addition to ____Mdd's reply about TWRP being flashed to your boot (i.e. kernel!) partition, which isn't good...
The 'Image not signed or corrupt' error is normal because TWRP isn't cryptographically signed, so the bootloader reports as so. Normally, if you see [OKAY], the flash has succeeded (though in your case it's succeeded flashing to the wrong partition...) and you'd boot to recovery to ensure TWRP is not overwritten by the stock recovery (after which you can boot as normal).
If you need a stock kernel, you can pull the boot.img from the stock ROM you have and flash that to the boot partition or find the stock kernels here https://forum.xda-developers.com/showpost.php?p=72378739&postcount=262
Hopefully your device is working!

Gaaaaaaaaah didn't realize I was flashing to the wrong partition. Zomfg.
It didn't brick, i reverted to the stock before booting and relock the bootloader. I don't want the stock, I want to flash loa (did this on my s5 normally)
The problem is that even using the right command, it says that it is not signed, and wglhen I reboot in Dev mode it still won't boot on TWRP. It goes back to fastboot.
Any ideas?

TWRP not replacing CyanogenMod recovery

Hi all,
I understand there is loads of this stuff online but found nothing related to Z1, please bear with me. So, after successfully installing TWRP my Z1 is always loading the cm recovery.
I'm with CM 12.1 yog4pap25i, update CM recovery is off.
After flashing TWRP is there specific actions I need to do? I've always rebooted into recovery with fastboot or the advanced reboot in the phone, but I'm always having CM recovery installed.
Thanks for your help

badyards said:
Hi all,
I understand there is loads of this stuff online but found nothing related to Z1, please bear with me. So, after successfully installing TWRP my Z1 is always loading the cm recovery.
I'm with CM 12.1 yog4pap25i, update CM recovery is off.
After flashing TWRP is there specific actions I need to do? I've always rebooted into recovery with fastboot or the advanced reboot in the phone, but I'm always having CM recovery installed.
Thanks for your help
Click to expand...
Click to collapse
You unlocked bootloader and checked oem unlock im sure.
But which command did you use to flash the twrp?
Output should be like this:
C:\Users\anwender\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x2b4c flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (8686 KB)...
OKAY
Please post your output

Hi @strongst, I'm on mobile now but yes, the response is ok. Also I've checked what you suggested. The problem is I think I did everything well, but somehow I'm not rebooting correctly

after that command type fastboot boot twrp.img (twrp is the name of recovery img) and it will booted into recovery

badyards said:
Hi @strongst, I'm on mobile now but yes, the response is ok. Also I've checked what you suggested. The problem is I think I did everything well, but somehow I'm not rebooting correctly
Click to expand...
Click to collapse
I would say, after installing twrp, directly type fastboot reboot recovery and boot to recovery immediately.
Booting into system will replace the stock recovery
Sent from my Lenovo Zuk Z1 using XDA Labs

Sharma_Ji said:
I would say, after installing twrp, directly type fastboot reboot recovery and boot to recovery immediately.
Booting into system will replace the stock recovery
Sent from my Lenovo Zuk Z1 using XDA Labs
Click to expand...
Click to collapse
Hi, this is the message received after flashing:
PS C:\platform-tools> fastboot -i 0x2b4c flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (9578 KB)...
OKAY [ 0.340s]
writing 'recovery'...
OKAY [ 0.138s]
finished. total time: 0.594s
then I digit this
PS C:\platform-tools> fastboot reboot recovery
< waiting for device >
if i switch off it is booting automaticaly into CM12. If I exit the shell and try power + volume down it opens a plain recovery, neither the CM revocery nor the twrp. Any idea of what I'm doing wrong?
edit: also tried this
PS C:\platform-tools> adb devices
List of devices attached
cb02ec72 device
PS C:\platform-tools> adb reboot bootloader
PS C:\platform-tools> fastboot -i 0x2b4c flash recovery recovery.img
target reported max download size of 1610612736 bytes
sending 'recovery' (9578 KB)...
OKAY [ 0.330s]
writing 'recovery'...
OKAY [ 0.134s]
finished. total time: 0.467s
PS C:\platform-tools> fastboot boot recovery.img
< waiting for device >
looks like the fastboot is gone after flashing

hi everyone, sorry for the newbie question above. Eventually I've managed to install TWRP, I just missed the right key combination to reboot.
Thanks

Can't boot in twrp

Hi, i'm trying to root my redmi note 7 so first i need to boot in twrp in order to root my phone.
My problem is that i can't enter twrp:
I've unlocked bootloader and installed adb + enabled usb debugging. Then, i enter fastboot (adb reboot bootloader), i flash the recovery with twrp img, which works fine
C:\Users\Ailiganon\Desktop\redmi note 7 root tool\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.410s]
Writing 'recovery' OKAY [ 0.452s]
Finished. Total time: 1.928s
But then, when i want to enter twrp using VolumeUp+Power button, it simply boots the phone normally !!!
I've also tried using this command when in fastboot: fastboot boot twrp.img but it does nothing although in CMD, it shows the command worked fine:
C:\Users\Ailiganon\Desktop\redmi note 7 root tool\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (65536 KB) OKAY [ 1.392s]
Booting OKAY [ 0.133s]
Finished. Total time: 1.584s
I can access recovery mode when i turn off my phone and simply use VolumeUp+Power button (not from fastboot) but since Xiaomi overwrites the recovery mode everytime it reboots, it just enters the regular redmi recovery menu and not twrp. Idk what to do else
I've used the twrp img from this video: www youtube com watch?v=r3R9kiBIx34 (i can't post url >.<) and i've tried another one on another website, but i think it was the same one since they had the same size.
Hope someone can help me ty

Orangenfox unpack, flash in Fastboot mode, don't restart, hold the recovery buttons and then flash the Orangenfox.zip in recovery mode

joke19 said:
Orangenfox unpack, flash in Fastboot mode, don't restart, hold the recovery buttons and then flash the Orangenfox.zip in recovery mode
Click to expand...
Click to collapse
I've unpacked orangefox, flash recovery.img in fastboot mode, and then i held the recovery buttons, but yet again, it just boots the phone and it's even worse cause it prompts me a password to access android that i dont fkin know. So i've had to reset the phone using "fastboot format userdata" command. I did it twice cause the first time i had a schema to unlock the phone so i've put a password instead but the second time it prompted me the password, i've put the password i've chosen to unlock the phone but it said "wrong password". So i don't know what password they ask, and i dont know why it appears only after flashing orange fox....
I've also tried with the command "fastboot boot recovery.img" with the same result as earlier
C:\Users\Ailiganon\Desktop\redmi note 7 root tool\platform-tools>fastboot flash recovery recovery.img
Sending 'recovery' (30488 KB) OKAY [ 0.659s]
Writing 'recovery' OKAY [ 0.216s]
Finished. Total time: 0.917s

What orangenfox said by cancel and format data?

[SOLVED]Stuck in Fastboot

I was on MIUI Global 12.0.2 Stable. I tried to flash Pig's latest Lineage (2020.07.21) from TWRP. The flash failed with an "Error 7". When I tried to reboot, the device went to "fastboot" mode.
After that, every attempt of a reboot ended in fastboot mode. So I tried to flash TWRP.img. Flashing went OK. But "fastboot boot twrp.img" gave the error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". The result was same with "fastboot oem reboot-recovery" command.
So I was stuck in fastboot mode with the risk of battery depletion. Below is the commands I ran to flash the TWRP.
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.016s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 2.179s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.016s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.046s
C:\adb>
Click to expand...
Click to collapse
SOLUTION: One needs to flash the fastboot ROM in MiFlash.
My situation had an extra issue as there were no fastboot ROM for MIUI Global 12.0.2. So, I downloaded MIUI 11.0.5 Global Fastboot ROM and flashed it. One needs to keep in mind about the "Anti-Rollback Protection" (https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/) and take necessary steps to avoid an anti-rollback brick.
If anti-rollback compatible ROM not available, then just delete first lines in all .bat files (.bat for Windows; .sh for Linux) up to the first line that starts with "fastboot %* getvar product..." of the available fastboot ROM. Those lines are the anti-rollback check. After than you can flash it via MiFlash.

Stillness said:
So I try to flash TWRP.img. Flashing goes OK. But "fastboot boot twrp.img" gives this error "FAILED (remote: Failed to load/authenticate boot image: Load Error)"
Click to expand...
Click to collapse
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery

zgfg said:
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
Click to expand...
Click to collapse
Thanks for the reply. I tried that command too, but ended with the same error.
Now, downloading the 11.0.5 Global Fastboot ROM since no 12.0.2 Fastboot available. My plan is to just delete first lines in .bat files of the ROM to avoid 'rollback protection' and flash via MiFlash before the battery goes zero. According to google, it seems flashing the full Fastboot ROM is the only solution

SOLVED
Solved. Edited the OP.

zgfg said:
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
Click to expand...
Click to collapse
Wow, thank you so much for pointing this out!
I just had a close to two hour journey through all emotions after trying to restart my phone and suddenly ending up in a seemingly inescapable fastboot hell...
I've tried booting different recoveries, all failing with
Code:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
and was already at the point of giving up getting my system back, just trying to save my data if possible. Flashing seemed to work, but
Code:
fastboot reboot recovery
just threw me back into fastboot, which I assumed to be due to the phone rejecting the flashed recoveries just as it was rejecting them when I tried to boot them directly.
When I saw this comment I wondered whether Xiaomi implemented rebooting directly to the recovery differently (as it turns out, it doesn't seem to be standardized) and
Code:
fastboot oem reboot-recovery
worked perfectly! After reflashing my ROM from TWRP I was booted back up into my system with everything intact, as if nothing has happened.

Fastboot can't flash twrp

Hello, I tried to upgrade to official LOS, so I upgraded firmware using twrp and then I installed new LOS 18.1, however I didn't make any partition clean, so I stuck with bootloop can't boot into lineage os.
I can't boot into TWRP too, it seems to freeze on TWRP splash screen.
I tried to flash another recovery using fastboot. I boot successfully into fastboot, however when I enter flash command from my PC it freezes, when I ran fastboot flash with verbose, I got:
Code:
fastboot: verbose: target didn't report max-download-size
Have you idea what should I do?
I'd mention that before my TWRP sideload worked only after `adb reboot sideload` and I couldn't sideload package using TWRP gui "adb sideload".
Update: I tried connect to different usb port and I got:
Code:
$ sudo ./platform-tools_r29.0.1-linux/platform-tools/fastboot flash recovery --verbose asus/lineage-18.1-20210518-recovery-X00TD.img
fastboot: verbose: target reported max download size of 536870912 bytes
Sending 'recovery' (21157 KB)
and then phone freezed (I still have twrp splash screen)
Update 2: I discovered, I can run `adb shell` command in the twrp splash screen (however I can't i.e. run wipe command)
Finally erase cache and userdata worked but I still have bootloop. TWRP GUI works however I have problem with Mount
Now I can flash TWRP or lineage os recovery, I tried TWRP Kud however still error on wipe same AS in attarched screen.