Database Users

Cant't flash recovery

I'm trying to flash my new Mate 8 with TWRP but I can't.
I've unlocked bootloader, flash twrp recovery with fastboot. Everything seems to be fine:
Code:
$ fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (31356 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 0.508s]
finished. total time: 1.185s
But for every time I've tried Huawei eRecovery runs instead of TWRP.

After you flash the twrp recovery, turn off the phone then boot into recovery by holding both volume up and power. This might prevent mate 8 to rewrite the stock recovery. If this works the next time you boot into recovery it will be twrp.

make sure also the phone is not plugged to your computer so you can enter twrp

Both your ways didn't work for me. After restart there is still Huaweii recovery. I've managed only to run TWRP. After flashing with
Code:
fastboot flash recovery twrp.img
I didn't restart by
Code:
fastboot reboot
but unplug from computer, and power off by holding power button. After restart I boot phone into recovery by holding both volume up and power. TWRP runs and wants a password from me. I've tried password which I use to unlock phone, but that doesn't work. After restart there is still stock recovery.

Flash new twrp image after u install via twrp nougat and do not restart , reboot to twrp first ! Hpebthat helps

schizo85 said:
I'm trying to flash my new Mate 8 with TWRP but I can't.
I've unlocked bootloader, flash twrp recovery with fastboot. Everything seems to be fine:
Code:
$ fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (31356 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 0.508s]
finished. total time: 1.185s
But for every time I've tried Huawei eRecovery runs instead of TWRP.
Click to expand...
Click to collapse
1-
Download TWRP Recovery 3.0.2-0
http://sillanwali.com/downloads/twrp-3.0.2-0-next.img
2-
adb devices
adb reboot bootloader
fastboot flash recovery (PATH-TO)\twrp-3.0.2-0-next.img
3-
Reboot your phone to TWRP then choose Wipe > format > type Yes
4-
Back again, then wipe (data, dalvik, cache, system)
Don't reboot
6-
Install supersu_v2.79_sr2.zip
7-
Rooted

sillanwali said:
1-
Download TWRP Recovery 3.0.2-0
http://sillanwali.com/downloads/twrp-3.0.2-0-next.img
2-
adb devices
adb reboot bootloader
fastboot flash recovery (PATH-TO)\twrp-3.0.2-0-next.img
3-
Reboot your phone to TWRP then choose Wipe > format > type Yes
4-
Back again, then wipe (data, dalvik, cache, system)
Don't reboot
6-
Install supersu_v2.79_sr2.zip
7-
Rooted
Click to expand...
Click to collapse
please help me i hase emui 4..1
and i install twrp 4.1 and when i install nougat i install
supersu_v2.79_sr2 then
update_2 but when istall update it stop on writinh ratio i shut dun the phone but no login to twrp or to stock recovery
help me plaese

Cannot Boot TWRP Recovery After Unlocking Bootloader and Successful Flashing Recovery

Hi, I'm having issues with booting recovery.
I've successfully rooted my phone before, but because of an OTA update, had to revert back to the flashing of recovery (TWRP), booting recovery, then flashing Magisk steps.
So, I have my recovery.img file which I renamed to "twrp.img" (no double twrp.img.img file extensions). It looks like I'm able to flash it successfully, giving something that looks like this when I run "fastboot flash recovery twrp.img" (in the directory where the recovery image is located):
target reported max download size of 536870912 bytes
sending 'recovery' (24496 KB)...
OKAY [ 0.530s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.691s
Click to expand...
Click to collapse
​
However, after I try the "fastboot boot recovery twrp.img" command, it gives me:
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
​
When I try to restart into recovery, it just boots into stock recovery, and not TWRP.
Any help would be super useful, I'm really not able to figure this out. I've done a lot of research, even going through disabling/uninstalling the Kedacom USB drivers and turning airplane mode on and installing adb/fastboot drivers from XDA.
Thanks!

Why are you flashing two recovery images? Maybe I'm missing something but I'm not understanding what it is that you are doing.
Your problems could also be related to whatever version of TWRP you are flashing on whatever OS you are running. Maybe there is a compatibility issue between the two but without more specific information it's pretty much impossible to say.

I'm just flashing one recovery.img file (TWRP), which doesn't display any errors in the flashing in command line. But when I try to boot it in command line, it gives me the above error that the recovery doesn't exist. When I try to boot it by advanced restart -> recovery, it just takes me to the stock recovery.
I'm on Oxygen 4.5.14. Let me know if there's anything else I can provide.

Rename your Recovery file to twrp.img
Seems like you forgot to do that according to your command
k0byf1ch said:
Hi, I'm having issues with booting recovery.
I've successfully rooted my phone before, but because of an OTA update, had to revert back to the flashing of recovery (TWRP), booting recovery, then flashing Magisk steps.
So, I have my recovery.img file which I renamed to "twrp.img" (no double twrp.img.img file extensions). It looks like I'm able to flash it successfully, giving something that looks like this when I run "fastboot flash recovery twrp.img" (in the directory where the recovery image is located):
​
However, after I try the "fastboot boot recovery twrp.img" command, it gives me:
​
When I try to restart into recovery, it just boots into stock recovery, and not TWRP.
Any help would be super useful, I'm really not able to figure this out. I've done a lot of research, even going through disabling/uninstalling the Kedacom USB drivers and turning airplane mode on and installing adb/fastboot drivers from XDA.
Thanks!
Click to expand...
Click to collapse
Edit:Sorry I kind of Missed that its already Done
Please Ignore My Upper Message
Possible another Solution:
Download Another Recovery File and Do the Same again

I've renamed the file since, and it still has been a problem.
Both recovery.img and twrp.img and the original name of the file "twrp-3.1.1-cheeseburger-84-20170820-194433-CEST.img" wouldn't take.

The file name is irrelevant. But it seems like your command to boot into recovery is the problem: fastboot boot only takes one argument (the file to boot into) whereas the fastboot flash command takes two arguments (partition and file to flash).
fastboot flash recovery twrp.img
fastboot boot twrp.img

Okay, I'll give that a shot but I'm still booting into the stock recovery when I advance restart into recovery.

can only get into fastboot or TWRP

I am trying to flash Lineage OS, and from TWRP it appears to flash but now this Storm Kipper will not boot into Lineage.
From TWRP if I select power off it goes straight into Fastboot.
From Fastboot:-
Start: reboots and goes straight into fastboot
Restart bootloader: reboots and goes straight into fastboot
Power off: reboots and goes straight into fastboot
Recovery mode: goes to Team Win Recovery Project 3.1.0-0
I have a number of lineage-14.1-2017xxyy-nightly-kipper-signed.zip on a microSD card, and I have checked the SHA256 hashes and they match the ones on the website
Another oddity is that if I try and flash open_gapps it says wrong architecture, I have tried arm and arm64 and it makes no difference.
I have tried using the repair feature on System, Data and Cache and it seems to complete without issues but lineage still won't boot.
Can anyone advise? thanks

also I just tried the ADB sideload feature in TWRP (just to rule out the microSD card)
it appeared to work with a progress bar and at the end said "script succeeded", but when you select reboot it says "No OS installed! Are you sure you wish to reboot?"

ok people.
If I extract the boot.img from the LineageOS zip file and flash that using fastboot is that likely to make things better or worse?

Did you have success? I have the same problem...

Possible solution found!
dieselnutjob said:
ok people.
If I extract the boot.img from the LineageOS zip file and flash that using fastboot is that likely to make things better or worse?
Click to expand...
Click to collapse
I got my wf storm up and running again!
Look here -> reddit-forum for LineageOS

android_paul said:
I got my wf storm up and running again!
Look here -> reddit-forum for LineageOS
Click to expand...
Click to collapse
Thank you for this. I now also have Lineage 14.1 working.
The back button still doesn't illuminate though. I'm not sure if it's a bug or a hardware fault.
Anyway, as per the reddit post.
Download cm-13.1.5-ZNH2KAS7EC-kipper (fastboot).zip
unpack the zip file into a new folder
follow these instructions (I am using Linux)
Code:
cd ~/cm-13.1.5-ZNH2KAS7EC-kipper-fastboot/
fastboot flash aboot emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
This got it back to a working CM13.1
From here I went to bootloader mode and had a play with CM Recovery but didn't get on with it.
So I flashed on TWRP+3.1.0-0.img again.
This time it wouldn't pick up the microSD card, but adb sideload worked and that is how I installed lineage, su and gapps.
Thanks again.

Now that Lineage 14.1 is on TWRP can now see the microSD card.

dieselnutjob said:
...
The back button still doesn't illuminate though. I'm not sure if it's a bug or a hardware fault.
Click to expand...
Click to collapse
My led of the back button is off too. I'm afraid, it's a hardware issue. If my phone gets cold (using as a navigation tool on bike in winter....), the led begins to shine - until it's warm again. So this looks like an electrical (dis)connection problem.
There are bigger problems to imagine.

Can't flash twrp to Wileyfox Storm!
I can't install twrp of my Wileyfox Storm (I've tried several times)!
* I've unlocked the bootloader.
* I change to the directory where the twrp image is stored.
* I do <adb reboot bootloader>
* I do <fastboot flash recovery ./twrp-3.2.1-0-kipper-20180110.img>
I then get the message:
target reported max download size of 268435456 bytes
sending 'recovery' (26676 KB)...
OKAY [ 0.923s]
writing 'recovery'...
OKAY [ 0.339s]
finished. total time: 1.262s
* I then do <fastboot reboot>
The phone then reboots OK, but if I try to reboot to recovery I just get the 'vanilla' boot menu.
I'd be grateful for any help, please.
Jim

bought a oneplus 2 with 3.6.1 OOS and cant flash twrp to recovery part

newbie to a oneplus 2. I acquired this phone locked and with OOS 3.61. been doing some searches but apparantly not enough and not getting very far.
Actions performed so far
set oem unlocking in dev-options to enabled.
rebooted to fastboot
"fastboot oem unlock" was succesful and rebooted and completed setup
rebooted to fastboot
from fastboot installed twrp "fastboot flash recovery recovery.img" (recovery.img being twrp-3.2.1-0-oneplus2.img)
results:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22180 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 1.310s]
finished. total time: 1.934s
:end results
then boot directely to twrp with "fastboot boot recovery.img"
performed nandroid backup.
rebooted device and tried booting to recovery but still has oem recovery.
any ideas? would like twrp native not via fastboot only.
thanks in advance.
Update solved:
booted twrp from .img file and installed su.zip and installed twrp.apk and used the app to install twrp. works now. not sure why it was saying it was working from from fastboot and writing but hope this helps someone else.

TWRP 3.2.1 doesn't work properly yet on the OnePlus 2 for some reason. I can assume that you wanted root so I can give you 2 options:
1) If you want to stay on stock OxygenOS 3.6.1 or a custom rom Nougat or lower, then flash TWRP 3.1.1
2) If you want to have an Oreo rom, then you have to get your hands on the unofficial TWRP from anupritaisno1. The download link for that on his forum doesn't work so if you want, I can link my Google Drive.

This is my first time trying to root my android and I am having the same problem with my oneplus 2 3.6.1 OOS. I have successfully unlocked oem but can't seem to flash twrp.
I have downloaded twrp 3.2.1 on my desktop and renamed it to "recovery".
I used the same command "fastboot flash recovery recovery.img" but it just says "error: cannot open 'recovery.img' "
Can you please tell me how you managed to install twrp and root your android?

you need to downgrade the OOS to ver 3.002 or 3.1, then you re-unlock the bootloader then flash twrp recovery.
Finally flash your phone with root of your liking.

rp201 said:
newbie to a oneplus 2. I acquired this phone locked and with OOS 3.61. been doing some searches but apparantly not enough and not getting very far.
Actions performed so far
set oem unlocking in dev-options to enabled.
rebooted to fastboot
"fastboot oem unlock" was succesful and rebooted and completed setup
rebooted to fastboot
from fastboot installed twrp "fastboot flash recovery recovery.img" (recovery.img being twrp-3.2.1-0-oneplus2.img)
results:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22180 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 1.310s]
finished. total time: 1.934s
:end results
then boot directely to twrp with "fastboot boot recovery.img"
performed nandroid backup.
rebooted device and tried booting to recovery but still has oem recovery.
any ideas? would like twrp native not via fastboot only.
thanks in advance.
Update solved:
booted twrp from .img file and installed su.zip and installed twrp.apk and used the app to install twrp. works now. not sure why it was saying it was working from from fastboot and writing but hope this helps someone else.
Click to expand...
Click to collapse
dear,
do you mind sharing the twrp.img you used?
Thank you

[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.