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.
Related
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:
To be clear im trying to bring back the old "boot loader is unlocked and software integrity cannot be guaranteed" boot message from the red one that says "Your device is corrupt. It can’t be trusted and may not work properly." Now I no this topic has already been on the forums but I read them, and made several attempts to fix the issue but was unsuccessful. every time I end up losing my all my **** and as soon as i upgrade to the latest pie ota it goes right back to the red boot message. One time I even hard bricked my phone and had to use the msmdownloadtool to get me back to hydrogen os and still the same thing happend when I upgraded to pie. Can anyone point me in the right direction on how to fix this problem.
p.s. I know its not a "problem" really but its one of those things that’s been pestering me for over a month. thanks for your concern.
Did you use in-built updater or flashed pie via twrp?
If you flashed by twrp, you may need to flash twice for both a and b bootslots.
You may try to lock bootloader, use msm again then update pie.
After that try to unlock it may fix
Linux_fart_18.3 said:
To be clear im trying to bring back the old "boot loader is unlocked and software integrity cannot be guaranteed" boot message from the red one that says "Your device is corrupt. It can’t be trusted and may not work properly." Now I no this topic has already been on the forums but I read them, and made several attempts to fix the issue but was unsuccessful. every time I end up losing my all my **** and as soon as i upgrade to the latest pie ota it goes right back to the red boot message. One time I even hard bricked my phone and had to use the msmdownloadtool to get me back to hydrogen os and still the same thing happend when I upgraded to pie. Can anyone point me in the right direction on how to fix this problem.
p.s. I know its not a "problem" really but its one of those things that’s been pestering me for over a month. thanks for your concern.
Click to expand...
Click to collapse
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
abasba said:
Did you use in-built updater or flashed pie via twrp?
If you flashed by twrp, you may need to flash twice for both a and b bootslots.
You may try to lock bootloader, use msm again then update pie.
After that try to unlock it may fix
Click to expand...
Click to collapse
unfortunate for me ive tried all the above except locking bootloader before msm which i have also tried both separtatly but not in that order.
ab123pro said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
ill give it a try thanks also do you know the command to switch partitions when in fastboot? im stuck on a partion and stuck only rebooting to fastboot cant flash twrp img or boot img id really appreciate it any know the command
Linux_fart_18.3 said:
ill give it a try thanks also do you know the command to switch partitions when in fastboot? im stuck on a partion and stuck only rebooting to fastboot cant flash twrp img or boot img id really appreciate it any know the command
Click to expand...
Click to collapse
Run "fastboot boot twrp-3.3.1-3-enchilada.img" in command line https://androidfilehost.com/?fid=6006931924117908950
then from within twrp flash twrp installer - https://androidfilehost.com/?fid=6006931924117908949
and magisk if you want root
ab123pro said:
Run "fastboot boot twrp-3.3.1-3-enchilada.img" in command line https://androidfilehost.com/?fid=6006931924117908950
then from within twrp flash twrp installer - https://androidfilehost.com/?fid=6006931924117908949
and magisk if you want root
Click to expand...
Click to collapse
sudo fastboot boot ./twrp-3.2.3-x_blu_spark_v9.91_op6.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.924s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.939s
every time. thats why im in need of a command to get me back to the (b) partition and also
fastboot –set-active=_b just get me "waiting for device" and nothing more.
Linux_fart_18.3 said:
sudo fastboot boot ./twrp-3.2.3-x_blu_spark_v9.91_op6.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.924s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.939s
every time. thats why im in need of a command to get me back to the (b) partition and also
fastboot –set-active=_b just get me "waiting for device" and nothing more.
Click to expand...
Click to collapse
looks like your boot partition got corrupted some how im not sure tho
maybe try to flash one of those fastboot roms - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
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.
Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
gardeimasei said:
Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
Click to expand...
Click to collapse
Flash factory image with fastboot.
wangdaning said:
Flash factory image with fastboot.
Click to expand...
Click to collapse
Where can I get the factory image? And how do I use fastboot to flash the device? Like so?:
Code:
fastboot boot <image name>.img
I am able to fastboot boot into the blueline TWRP image. Selecting the "Fix bootloop" didn't work however
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
gardeimasei said:
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
Click to expand...
Click to collapse
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Also, the boot partition is not the bootloader partition. Just run the flash-all script that google provides with the factory image download.
dcarvil said:
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Click to expand...
Click to collapse
I was using Android 9. I tried running the flash-all script (i.e., follow the official instructions) but the fastboot commands would hang. Maybe I just didn't wait for long enough.
I wiped system,data,cache using TWRP following some online guide and now I can't boot into recovery mode. I can get into the bootloader menu though. When I try to boot into TWRP using:
Code:
fastboot boot twrp-3.3.0-0-blueline.img
I get the following error on the PC: Booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
When I try to enter recovery mode the screen turns black indefinitely.
I still have the TWRP .win files from my backup on my PC. Is there a way out of this?
EDIT:
Weirdly, after trying the flash-all.sh script again it worked basically instantly. Possibly it took so long the first time i ran it because it was wiping data (which i then did manually).
Was able to get the factory image on there. Thanks a lot!
Oneplus 6. Working just fine. OOS 10.3.2
So, I... got a new second phone for, well just because.
Same model etc. Both unlocked rooted and TWRP installed.
Was careless in a restore on phone 2. Now when trying to boot to TWRP, I'm stuck in bootlaoder.
If I run TWRP to resintall or load another restore it fails with the following error.
PS C:\x\OP6> fastboot boot twrp-3.3.1-12.img
downloading 'boot.img'...
OKAY [ 0.710s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
TWRP.img works! Have used on phone 1 and phone 2. today.
I need to boot to TWRP, get new OS installed (OOS current 10.3.2) and then... well, onward and upward.
side note - OP Switch sucks.
Help please.
Bellooch said:
Oneplus 6. Working just fine. OOS 10.3.2
So, I... got a new second phone for, well just because.
Same model etc. Both unlocked rooted and TWRP installed.
Was careless in a restore on phone 2. Now when trying to boot to TWRP, I'm stuck in bootlaoder.
If I run TWRP to resintall or load another restore it fails with the following error.
PS C:\x\OP6> fastboot boot twrp-3.3.1-12.img
downloading 'boot.img'...
OKAY [ 0.710s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
TWRP.img works! Have used on phone 1 and phone 2. today.
I need to boot to TWRP, get new OS installed (OOS current 10.3.2) and then... well, onward and upward.
side note - OP Switch sucks.
Help please.
Click to expand...
Click to collapse
Go here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815. Use 3.3.1-18