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:
Related
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.
I just flashed the OOS Android 10 beta ROM via the system upgrade tool (didn't work via TWRP) so now I'm unrooted. ROM works fine, but I'm having trouble re-rooting. I'm trying to boot the TWRP img via fastboot and keep getting the same error:
Code:
c:\adb>fastboot boot twrp.img
Sending 'boot.img' (28980 KB) OKAY [ 0.640s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm unable to boot into TWRP and tried different versions of the img file, all which give me the same error. How can I fix this?
vorsprungtechnik said:
I just flashed the OOS Android 10 beta ROM via the system upgrade tool (didn't work via TWRP) so now I'm unrooted. ROM works fine, but I'm having trouble re-rooting. I'm trying to boot the TWRP img via fastboot and keep getting the same error:
Code:
c:\adb>fastboot boot twrp.img
Sending 'boot.img' (28980 KB) OKAY [ 0.640s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm unable to boot into TWRP and tried different versions of the img file, all which give me the same error. How can I fix this?
Click to expand...
Click to collapse
Doesn't work yet, don't think it will for a while because fastboot has changed apparently.
The guy who makes the OP7 port has it baked in, but it's not encrypted
brashmadcap said:
Doesn't work yet, don't think it will for a while because fastboot has changed apparently.
The guy who makes the OP7 port has it baked in, but it's not encrypted
Click to expand...
Click to collapse
Ok thanks. So there's no way to possibly root the new ROM at the moment?
Flash patched boot.img via fastboot. Just becarful with magisk modules at the moment.
Bradl79 said:
Flash patched boot.img via fastboot. Just becarful with magisk modules at the moment.
Click to expand...
Click to collapse
Can you elaborate on this? The part about being careful with modules? I got magisk working, and I'm using 2 modules, YT Vanced and Google Dialer framework.
When should I be careful? When there is a new update for the A10 beta? Or just on how many modules you install, or which ones?
Thanks
Meaning if u go into a bootloop u r pretty much screwed without a twrp, there is no way to remove the module.
Deleted, wrong post
ArkAngel06 said:
Can you elaborate on this? The part about being careful with modules? I got magisk working, and I'm using 2 modules, YT Vanced and Google Dialer framework.
When should I be careful? When there is a new update for the A10 beta? Or just on how many modules you install, or which ones?
Thanks
Click to expand...
Click to collapse
Just be smart. Use stuff that doesn't fundementally alter things (framework mods, etc.). FDE is updated, Vanced works, stuff like call recorder, fonts etc. should be fine. I'd avoid audio mods (directories might have changed idk) and things like auto brightness fix (framework mods).
---------- Post added at 02:22 AM ---------- Previous post was at 02:20 AM ----------
vorsprungtechnik said:
Ok thanks. So there's no way to possibly root the new ROM at the moment?
Click to expand...
Click to collapse
Updating from rooted OOS Pie, flash magisk through manager to inactive slot before reboot after OTA finished. Worked for me.
Of course I don't have any recovery at all so we will see how that goes three days from now when I install something crazy
vorsprungtechnik said:
I just flashed the OOS Android 10 beta ROM via the system upgrade tool (didn't work via TWRP) so now I'm unrooted. ROM works fine, but I'm having trouble re-rooting. I'm trying to boot the TWRP img via fastboot and keep getting the same error:
Code:
c:\adb>fastboot boot twrp.img
Sending 'boot.img' (28980 KB) OKAY [ 0.640s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm unable to boot into TWRP and tried different versions of the img file, all which give me the same error. How can I fix this?
Click to expand...
Click to collapse
I fixed this on the op6 by doing this:
Note: On Windows systems, thanks to a bug in fastboot, you must first swap to slot a with fastboot set_active a, then specify slot a when flashing images, e.g. fastboot flash boot_a <recovery_filename>.img
(from lineageos install site)
however after this was a success i'm now stuck on the 1+ fastboot splash screen and it never actually goes to recovery. Hopefully you've figured it out by now but I came across your post a few times while I was looking for the solution myself
So, i bumped into this the other day, what i did was, flash the full Android 10 fastboot rom using the op6 aio tool, then, using fastboot I flashed twrp the one from mauronofrio, then from twrp without wiping anything, I flashed the stock boot.img, then the twrp installer again from mauronofrio and voila, twrp working, I also flashed magisk after the first boot, this is all in the fool proof guide in the guides subforum
any update on this? just updated to OOS 10.3.2 and cant boot into twrp anymore. All I want is to have twrp...any way to roll back to android 9?
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.
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
Hi, up until recently I had crDroid on my phone, after not touching for a while and the rom being a bit corrupt, I decided to rollback to OOS.
To do this, I used some files I had of the OOS version that was on the phone before crDroid, went into fastbootd mode through the custom recovery of the crDroid ROM and became flashing images, it's a bit janky but I only wanted to get OOS working and booting to install a fresh OTA version of OOS through the settings. I ended up using the Oxygen updater app (or something like that, got it off the playstore) to have the OOS file to copy it to my PC where I would dump the payload into a folder to get the boot image and patch it with magisk.
Everything worked perfectly, I had root, OOS was running with no apparent big problems, but I wanted to try and flash TWRP, that's when crap hit the fan.
I was a bit worried about the process because I know TWRP can behave unpredictably but after I saw some posts of users who have android 12 OOS and TWRP I decided to try.
I downloaded the TWRP image from the official website on Oneplus 7 pro, chose the version for stock rom, Europe (I am from Israel, pretty sure I need EU image), opened up fastboot, typed:
Code:
fastboot boot <image file location>
, it was sending, the phone began booting, and nothing, it didnt boot up, stuck on the loading LOGO of Oneplus, so I tried a different version.
I tried the American version, still didnt work, and then tried the custom ROM > Europe version, and the phone booted to twrp, I wanted to check everything was alright, so I rebooted from the custom recovery to system, it reboot to recovery. I wasnt so surprised, had a few issues with TWRP in the past, so I went into TWRP and did the "flash current TWRP image" thing, and the phone still wouldnt boot to system, only the custom recovery. At that point, I gave up on a custom recovery, and tried to flash the boot image again, as from what I remember usually this fixes the custom recovery problems, got a bootloop, tried flashing the Magisk patched boot image, got a bootloop, tried flashing all the images I could (not critical partitions), of the OOS I had installed on the phone and still got a bootloop.
thought that maybe I need to flash everything, flashed all the images I could of crDroid to get to its custom recovery and enter fastbootd, flashed all of the OOS images except "reserve.img" which gave me:
"fastboot flash reserve '/run/media/android/2E5CD91E5CD8E21F/Utilities/notroot/payload_dumper-win64/payload_output/reserve.img'
Invalid sparse file format at header magic
Sending sparse 'reserve' 1/11 (262124 KB) OKAY [ 8.115s]
Writing 'reserve' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed"
and Im still in a bootloop, never had a problem like this before, and I would love some help.
PS: Sorry for the long story, thought it would be essential for a real pro who would like to help me understand my poor phones situation.
Also, English isn't my first language so forgive me for a painful read.
Thanks in advance for any help.
Forgot to add, while trying to get to fastbootd, I read on the forum that you can do that with running in fastboot the following command:
fastboot reboot fastboot
after doing it the phone bootlooped again, and I got this message:
Code:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Hello,
I think you need to use the MSMDownloadTool to entirely reset your phone and restart from a fresh phone.
You will find informations here : https://forum.xda-developers.com/t/...a-gm21ba-collection-of-unbrick-tools.3956595/
Shalom and Happy Rosh Chodesh. Hebrew is not my first language, I believe you are better at inglet than I am at ivrit.
I agree with the above post, probably your only way out now. I think it started with your usage of the custom crDroid features as I am always wary of those 'custom' features on such a finicky device (as you found) as this. Compounded when trying to flash TWRP. So many have luck, but . . . . I have flashed more phones than I can count and for me the One Plus 7 Pro just does not like not being stock.