Database Info

Failed to load/authenticate boot image:

Need some help here as I am in a bit of a bind. Was on 5.1.11 and attempted to update to stable Pie. Used Blu_Spark TWRP v2 and upon rebooting got the error about device being corrupted. Continued booting but was stuck on boot animation. Rebooted to TWRP and attempted to restore nandroid. Upon restoring and reboot, boots immediately to TWRP. Attempt to change slots (which might have been an error on my part) and rebooted. Now stuck in fastboot! I attempt to flash TWRP.img via fastboot and get the following error:
Code:
PS D:\OnePlus 6\adb> fastboot boot twrp-3.2.1-0-enchilada_official.img
downloading 'boot.img'...
OKAY [ 0.628s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.650s
If I try and switch to slot _b, I get the following error:
Code:
PS D:\OnePlus 6\adb> fastboot --set-active=_b
C:\Android\fastboot.exe: unknown option -- set-active=_b
PS D:\OnePlus 6\adb>
At the moment, my phone is bricked, so any help is GREATLY appreciated.
Thanks!!!!

https://www.androidfilehost.com/?fid=746163614322268882
Tool
https://www.androidfilehost.com/?fid=889964283620777981
Qualcomm drivers
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Watch video on clicking 5T in thread
@azsl1326

I had the same, fixed it using this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Choose the Andriod PIE fastboot rom.
After that you can boot into PIE again, and if you want to go back to Oreo, use this Rollback procedure
https://www.theandroidsoul.com/rollback-oneplus-6-from-android-pie-to-android-oreo/
PS: You will lose ALL your data and Internal files

can I update my op6 after this...

Hi guys,
I'll tell you the story first, so you can see the whole picture and answer me based on it.
A few days ago I was trying to flash twrp and magisk on my op6 oos 9.0.3. I failed a lot and went into a lot of bootloops and crashdump and black screen but got out of these situations somehow. eventually, I found a way to root using patched magisk and it worked, but I didn't have twrp. So I uninstalled magisc from the app itself and rebooted, but that caused my op6 to get into a bootloop. Luckily I was able to get to the fastboot mode but after trying to flash different twrp imgs, and failing becasue I was just trying without any previous experience and that's stupid, I know. Anyway, fastboot started to give me this error "downloading 'boot.img'... OKAY [ 0.769s] booting... FAILED (remote: Failed to load/authenticate boot image: Load Error) finished. total time: 0.784s " so I used this command "fastboot --set-active=B" to switch to slot b and it worked, then I flashed twrp and magisk successfully because I learned a lot from those failures.
So, idk what happened to slot a, so when I recieve an update in the future for op6, can I update normally from updates in settings or do I have to do it manually or what? I really have no idea and I would like to have an expectation to what may happen.

olik2000 said:
Hi guys,
I'll tell you the story first, so you can see the whole picture and answer me based on it.
A few days ago I was trying to flash twrp and magisk on my op6 oos 9.0.3. I failed a lot and went into a lot of bootloops and crashdump and black screen but got out of these situations somehow. eventually, I found a way to root using patched magisk and it worked, but I didn't have twrp. So I uninstalled magisc from the app itself and rebooted, but that caused my op6 to get into a bootloop. Luckily I was able to get to the fastboot mode but after trying to flash different twrp imgs, and failing becasue I was just trying without any previous experience and that's stupid, I know. Anyway, fastboot started to give me this error "downloading 'boot.img'... OKAY [ 0.769s] booting... FAILED (remote: Failed to load/authenticate boot image: Load Error) finished. total time: 0.784s " so I used this command "fastboot --set-active=B" to switch to slot b and it worked, then I flashed twrp and magisk successfully because I learned a lot from those failures.
So, idk what happened to slot a, so when I recieve an update in the future for op6, can I update normally from updates in settings or do I have to do it manually or what? I really have no idea and I would like to have an expectation to what may happen.
Click to expand...
Click to collapse
As per my knowledge, since you already have your bootloader unlocked and have custom recovery, you might no lt be able to install updates directly. You will have to download them from oneplus' official website and then manually flash the updates. This has to be followed with the normal twrp recovery or unlocked bootloader.
I am not too sure about slot a and b, but I hope the procedure will be same. If you want to directly get updates, you will have to flash original recovery and OOS from oneplus' website.

Download and flash manually using twrp. Should be just fine.

happiy91 said:
As per my knowledge, since you already have your bootloader unlocked and have custom recovery, you might no lt be able to install updates directly. You will have to download them from oneplus' official website and then manually flash the updates. This has to be followed with the normal twrp recovery or unlocked bootloader.
I am not too sure about slot a and b, but I hope the procedure will be same. If you want to directly get updates, you will have to flash original recovery and OOS from oneplus' website.
Click to expand...
Click to collapse
That's really helpful, thanks :highfive:

Oneplus 7 Pro Nasty Brick - Custom ROM, no root, no TWRP - help?

Dear community. I screwed up.
I purchased my new OP7P and in all my excitement, logically, the first thing I went to do was to unlock the bootloader, install TWRP and root it, which I did successfully because I am pretty familiar with this on multiple phones. Long story short, here's what I did, and where my problem lies:
1. Went to install the Havoc Custom ROM by following their installation instructions, went ahead and booted to TWRP recovery
2. As instructed, wiped dalvik and /data
3. Flashed Havoc ROM and here is the part where I was supposed to flash TWRP installer
4. Forgot to reflash TWRP installer and rebooted to the now nonexisting recovery. - getting the dead android icon with the message "NO COMMAND"
5. After holding VOLUP + POWER managed to turn it off and then turn it on again with just POWER to be greeted with a message warning me that I am in a bootloop
and that I have two options; to try again or to "reset to factory settings", which I did, which booted me into the HavocOS.
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
I have tried this on both Linux & Windows, same deal. The TWRP website has mentioned that if this happens I need root, but how do I root my phone without TWRP or "fastboot boot", and how do I install TWRP on the OP7P without livebooting TWRP?
Any help at all is truly appreciated. Thanks guys.

Download the MSM tool here and restore your phone. I've never used it but it gets everyone out of a brick.

I've used this tool a few times and it has gotten me out of a jam, just be sure to download the correct version for your phone. AFA your fastboot error, I got that until I let the OTA update to 9.5.11, then it worked again. https://forum.xda-developers.com/oneplus-7-pro/development/tool-tool-one-driversunlocktwrpfactory-t3930862

x3lade said:
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
Click to expand...
Click to collapse
Try to fastboot boot the TWRP build -70 from here: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
It fixes the problem with "fastboot boot" not working on the official Android Q update. Not sure why that would apply to your case (custom ROM after already successfully installing TWRP). But it's very easy to try, and certainly can't hurt. And the error message you are getting is exactly the same as the official Android Q problem.

Flash TWRP via fastboot android 10

Hello guys, as we known that it is unable to use command in fastboot to boot into TWRP if we are on Android 10 (both OOS and Custom rom) at the moment, so here is the simple command allow us to do that if you want to roll back android 9 or any rom by TWRP
fastboot flash boot_a <twrp name.img>
fastboot flash boot_b <twrp name.img>
fastboot reboot
Your phone will automatically boot into TWRP, so you can flash another rom

Can anyone confirm this works?
I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it.
I would try again, but I'm on a critical work trip until the end of the month, so my phone's uptime is expected to be 100% until then.

worked for me while anything else didnt

LazerH said:
worked for me while anything else didnt
Click to expand...
Click to collapse
Does it wipe your data?

Didn't work for me. My boot image was patched already this is probably why.

ok, I tried this, but as reported above, now also stuck on this same: "I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it."
How do I resrore operation for my phone? (help?)

Well, I met this issue before, and ended up with using this method to successfully boot into twrp.
This issue seems to appear on OOS, when I using `fastboot boot xxx.img` on other ROM like omni, I'm able to boot into twrp, thanks!

can someone help me please. my phone is stuck in a fastboot bootloop. everything I try doesn't work.
fastboot boot TWRP.img NOTHING
tried your solution above and still nothing
Still stuck in fastboot this is what I get:
PS C:\Users\Les Brown\Desktop\OnePlus 6> fastboot boot twrp-3.3.1-17-enchilada-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.617s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.655s

@killathenoob Download DECRYPTED OOS 10.3.0 with this help if you don't really know what to do with this.
For others people (and you if you want to root or just install TWRP after fresh OOS10 Decrypted install) don't forget to OEM unlock before doing anything.
Download this
Copy "twrp-3.3.1-17-enchilada-installer-mauronofrio.zip" into internal storage of your OP6
Power it OFF
Power it ON in fastboot mode
Launch "Boot TWRP.bat"
Connect your OP6 to your PC and wait for TWRP to boot
Install twrp-3.3.1-17-enchilada-installer-mauronofrio.zip
Reboot to recovery and install magisk if you need to.
Source
Hope I helped a bit.

Stuck in fastboot after using fastboot rom

One plus 7 pro, European version
So i was running Lineage OS on my phone for some time now (latest base update i did was to ob1 as far as i am aware), when there was an update lately
I installed it as normal, but the phone would not get past the boot animation and kept restarting, so i went back to the other slot to see if that still worked, but it only had a laggy boot animation, which never booted
I then installed the previous version that i was running before the update back to the other slot, hoping it would solve the problem of not booting (that worked before already) but it still did not boot
I saw someone post they had 10.3 installed as base so i restored the ob1 installation with a fastboot rom i still had on my hard drive, but upon finishing the phone just went into crash dump mode showing
dm-verity device corrupted force dump
kernel_restart
I tried another install just to be sure, but same result
I then tried flashing twrp to the boot partition to at least get there, but the phone just went straight to fastboot upon doing that
Fastboot boot still seems broken and just shows
D:\Minimal ADB and Fastboot>fastboot boot tw.img
downloading 'boot.img'...
OKAY [ 1.228s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.346s
I searched around if there were other ways to install twrp from fastboot, and found this tool (https://forum.xda-developers.com/an...g/apk-img-dat-br-one-click-decompile-t3886057) that promises to unpack and repack the boot.img, so i hoped i could use that to manually add twrp to it, but it failed to unpack the file
Next thing i found was this MSM tool post (https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691) instructed to hold volume up and down for 5 seconds before connecting the phone to a pc, and the program actually picked it up, however the phone started itself after a few seconds and went back to crashdump mode
At this point i'm seriously out of ideas, does anyone else have other ideas that i missed?
Does anyone have a boot img with twrp?

keep trying the MSM tool. it WILL work.
if you can get into fastboot again, type in fastboot reboot edl in ADB

Luke JC said:
Fastboot boot still seems broken and just shows
D:\Minimal ADB and Fastboot>fastboot boot tw.img
downloading 'boot.img'...
OKAY [ 1.228s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.346s
Click to expand...
Click to collapse
This is indeed what typically shows for an error when fastboot boot isn't working. Probably due to using an older fastboot ROM. I'd try to use a newer fastboot ROM, or you can flash a patched boot image, which is how the phone was being rooted before fastboot boot was fixed:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345

If I recall correctly, you can't fastboot boot with android 10.