Database Info

Root android pie 9.0

So i just updated my device to official 9.0 Android Pie, and then I was trying to root my device but while I was in the fastboot screen and tried to boot into Twrp via platform-tools to flash the twrp zip file but when I typed in "fastboot boot twrp.img" (I shorten the twrp name) I got crashdump mode screen can anyone help me with my problem please, Thank you
Edit: this actually works with me
nightfury04 said:
go ahead and try to boot into this img file with fastboot https://forum.xda-developers.com/devdb/project/dl/?id=30421.... It will work for sure.
Then flash this zip file https://forum.xda-developers.com/devdb/project/dl/?id=30420
Click to expand...
Click to collapse
Do what he said:
1)Boot with twrp blu_spark.img via Bootloader.
2)If you want to use blu_spark twrp file then you flash blu_spark.img via recovery mode
For me:
I did a bit different from nightfury04, I did boot into the blu_spark twrp but I flash the Official twrp from Teamwin and it worked fine for me.
To root:
After flashed the recovery TWRP image I flashed Magisk 7.12, worked like a charm.

HerySean said:
So i just updated my device to official 9.0 Android Pie, and then I was trying to root my device but while I was in the fastboot screen and tried to boot into Twrp via platform-tools to flash the twrp zip file but when I typed in "fastboot boot twrp.img" (I shorten the twrp name) I got crashdump mode screen can anyone help me with my problem please, Thank you
Click to expand...
Click to collapse
Mee too

HerySean said:
So i just updated my device to official 9.0 Android Pie, and then I was trying to root my device but while I was in the fastboot screen and tried to boot into Twrp via platform-tools to flash the twrp zip file but when I typed in "fastboot boot twrp.img" (I shorten the twrp name) I got crashdump mode screen can anyone help me with my problem please, Thank you
Click to expand...
Click to collapse
which version of TWRP did you use??

HerySean said:
So i just updated my device to official 9.0 Android Pie, and then I was trying to root my device but while I was in the fastboot screen and tried to boot into Twrp via platform-tools to flash the twrp zip file but when I typed in "fastboot boot twrp.img" (I shorten the twrp name) I got crashdump mode screen can anyone help me with my problem please, Thank you
Click to expand...
Click to collapse
Same here
---------- Post added at 08:17 PM ---------- Previous post was at 08:17 PM ----------
nightfury04 said:
which version of TWRP did you use??
Click to expand...
Click to collapse
3.2.3.0

Mighty_Pig said:
Same here
---------- Post added at 08:17 PM ---------- Previous post was at 08:17 PM ----------
3.2.3.0
Click to expand...
Click to collapse
I have read that no TWRP is compatible with android 9 for OP6 till now, except the bluespark one.
Can you still access fastboot mode on ur OP6??

nightfury04 said:
I have read that no TWRP is compatible with android 9 for OP6 till now, except the bluespark one.
Can you still access fastboot mode on ur OP6??
Click to expand...
Click to collapse
Yes I can acces is, but when I try to flash the image it crashes.

I used bluspark worked like a charm

Mighty_Pig said:
Yes I can acces is, but when I try to flash the image it crashes.
Click to expand...
Click to collapse
Ok I get that, let me search if there is a patched blue spark img file so that you could boot into via fastboot and flash permanent blue spark twrp zip file from there.
---------- Post added 22nd September 2018 at 12:00 AM ---------- Previous post was 21st September 2018 at 11:58 PM ----------
whizeguy said:
I used bluspark worked like a charm
Click to expand...
Click to collapse
You might have flashed bluespark TWRP from stable version of TWRP right? @mighty's problem is that he isn't having any TWRP to flash bluespark from.

This is how you should do it...
Fastboot the img file
Let it boot to twrp
Flash twrp ZIP.... People are doing this wrong, they try to flash the img, it will cause errors.
Worked 100% for me.. Didn't have any twrp at all before, was on latest beta,
Fastboot img
Boot twrp
Flash twrp zip
Reboot to twrp
Flash rom
Flash twrp
Reboot to twrp
Flash magisk 17.2
Boot system

If you use the blu_spark twrp and use the latest magisk 17.1 you are good to go.
I am passing safety net and have working root

I don't get how you guys do it. For me it just ends up in bootloop

Mighty_Pig said:
Yes I can acces is, but when I try to flash the image it crashes.
Click to expand...
Click to collapse
go ahead and try to boot into this img file with fastboot https://forum.xda-developers.com/devdb/project/dl/?id=30421.... It will work for sure.
Then flash this zip file https://forum.xda-developers.com/devdb/project/dl/?id=30420

Anyone got a link to bluespark twrp? I can only find the kernel
Edit 1: already given

Delete

Here is what works for me on my OnePlus 6 Android 9 Pie
1. Download TWRP from @nightfury04 at Post 12
Flash it just as flashing the official TWRP for OnePlus 6
2. Magisk 17.2 Latest Beta with Latest Magisk Manager
Note: When I first used Magisk 17.1 stable, WiFi and SIM cards did not work.

I'm running the latest Blu spark twrp and tried to flash magisk 17.1 several times, but it just ends up in a bootloop everytime.
any ideas what might cause this?

=dave= said:
I'm running the latest Blu spark twrp and tried to flash magisk 17.1 several times, but it just ends up in a bootloop everytime.
any ideas what might cause this?
Click to expand...
Click to collapse
Try 17.2 beta
I have problems with 17.1, too like no wifi, sim card not detected and takes a long time to boot.

=dave= said:
I'm running the latest Blu spark twrp and tried to flash magisk 17.1 several times, but it just ends up in a bootloop everytime.
any ideas what might cause this?
Click to expand...
Click to collapse
Use latest Uninstaller first., then flash 17.2

whizeguy said:
Use latest Uninstaller first., then flash 17.2
Click to expand...
Click to collapse
thanks, that worked

is the unlocked boot message still present in this method?

Rooting for March Update?

Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.

lgstylus2root said:
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
Click to expand...
Click to collapse
I personally feel installing twrp offians twrp and flashing magisk is easyer

rob420p said:
I personally feel installing twrp offians twrp and flashing magisk is easyer
Click to expand...
Click to collapse
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.

lgstylus2root said:
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
Click to expand...
Click to collapse
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.

rob420p said:
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
Click to expand...
Click to collapse
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)

lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Go to the pa ROM page and use that twrp that's offians twrp.the best guild ive seen n is type in customdriod mi a2 lite twrp and that page is the best in my opinion to follow I'll see if I can get a link for the page in a minute

Won't let me simend the link

rob420p,
Please provide links.

rob420p said:
Won't let me simend the link
Click to expand...
Click to collapse
Would you be capable of private messaging me the link?

I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.

lgstylus2root said:
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
Click to expand...
Click to collapse
I have followed this guide but it would always result in the installed version of TWRP not installing correctly, and the system mentioning "The System has been destroyed, Press power button to shut down"
How can i resolve this?

I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY

marstonpear said:
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
Click to expand...
Click to collapse
I figured out how to do it either way, thank you for your efforts however!

lgstylus2root said:
I figured out how to do it either way, thank you for your efforts however!
Click to expand...
Click to collapse
You can add the links to the main thread so that people can see :good:

Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks

max-damage said:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
Click to expand...
Click to collapse
Search before asking : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952

I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.

max-damage said:
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
Click to expand...
Click to collapse
I'm stuck with the same problem.
Booting with patched_boot.img (made on my own or downloaded from this forum) make the phone not starting, blocked on white screen.
Have you already solved?

lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....

Winchester316 said:
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Click to expand...
Click to collapse
I believe we can I have heard reports offains 3.3.3. Twrp can do it I haven't tryed yet.but I did have twrp with root running on the march update but I'm on pa now

Anyone please let me know the OOS 10 and TWRP/Magisk Situation...

I am currently on OOS 10 OB2/31 and can't seem to find a way to install TWRP and Magisk. Found ways to install TWRP and Magisk via patched boot images on OOS 10 stable but not for OB2/31.... anyone know why it's not as simple as flashing TWRP via fastboot?

I also have a problem
'OOS10beta31' Root

XcutionerX said:
[...] anyone know why it's not as simple as flashing TWRP via fastboot?
Click to expand...
Click to collapse
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.

adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
Thank you for your help, gonna try following those. Hopefully I don't f up and have to do a msm restore. But why would they disable that command?... Just to make everything complicated? Guess I will not stick to Oneplus next year.

XcutionerX said:
But why would they disable that command?
Click to expand...
Click to collapse
Security? Deprecated or soon-to-be-deprecated command? Dunno really, lol.
XcutionerX said:
... Just to make everything complicated?
Click to expand...
Click to collapse
To be fair, the only difference between this method and the old method is just one word and manually rebooting to recovery. You still have to flash the twrp.zip after flashing from bootloader file to install TWRP, so it's not too radically different.

this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332

adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
I have successfully installed TWRP and Magisk with the help of those links. Thank you again for your help.

quizzina said:
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
Click to expand...
Click to collapse
Thank your for the in-depth explanation.

Just download oxygen updater and install 10.0.1 and be done with it

[Guide] TWRP+MAGISK ROOT Installed on OOS 10.3.5

Ok guys, I decided to write this up because the current state of finding good info on this is quite messy. I'm going to keep it short and to the point.
I'm not here to explain what TWRP or Magisk Root are. You can find that somewhere else.
Goal:
Install TWRP and Magisk Root on OOS 10.3.5, without losing data.
(This same method worked on earlier versions of OOS 10, and may also work on later versions.)
Requirements:
OnePlus 6 Unrooted and Unmodified Recovery
Computer/Laptop
Magisk (ZIP)
TWRP Blu_Spark (ZIP)
TWRP Q by Mauronofrio (IMG)
Important Notes:
If you have installed or upgraded to OOS 10.3.5, then your device should be returned to stock (unrooted and unmodified recovery), and you're ready to begin. Otherwise, I suggest you simply reinstall the system again (full system links here) and then you'll be ready.
To send commands from your computer to your phone, you will need Android ADB debug software and possibly OnePlus drivers.
OnePlus Drivers Installation Instructions
Download Links:
Magisk 20.4 ZIP
Magisk Uninstaller 20.4 ZIP
TWRP Blu_Spark 3.4.0-x v9.116 ZIP
TWRP Q by Mauronofrio 3.3.1-18 IMG
Begin
Step 1:
Disable all lock patterns and security on your phone.
Step 2:
Back up anything important on your phone. You accept responsibility for any lost data.
Step 3:
Copy/Save the ZIP files (Magisk + Magisk Uninstaller + TWRP Blu_Spark) to the storage in your phone. The IMG file (TWRP Q by Mauronofrio) should be saved on your Computer
Step 4:
Boot your phone to fastboot mode.
(Power off. Then press Power on + Volume Up)
Step 5:
Connect phone to computer with USB. (Don't use a crap/cheap USB cable or the connection may fail.)
Step 6:
On your Computer, Open the command line, and Run the command to fastboot the TWRP Q by Mauronofrio
fastboot boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img
Step 7:
Your phone should boot into TWRP (this is a temporary boot and nothing yet has been modified on your device).
Step 8:
Use the TWRP menu to Install both ZIP files. Starting with TWRP Blu_Spark, then Magisk.
BEWARE, DO NOT REBOOT BETWEEN INSTALLS! READ CAREFULLY. TWRP MAY TRY TO REBOOT. INSTALL BOTH ZIP FILES BACK TO BACK WITHOUT REBOOT.
Step 9:
Reboot. Complete. Congratulations.

If someone could provide me a link to ADB, then I will gladly include it in the post. Thank you

BEWARE, DO NOT REBOOT BETWEEN INSTALLS! READ CAREFULLY. TWRP MAY TRY TO REBOOT. INSTALL BOTH ZIP FILES BACK TO BACK WITHOUT REBOOT.
With reboot works too. Install twrp then reboot system, then reboot recovery from system, and install magisk. Works. I tried several times.

Shyciii said:
With reboot works too. Install twrp then reboot system, then reboot recovery from system, and install magisk. Works. I tried several times.
Click to expand...
Click to collapse
I have had bad problems on an earlier version, where Blu_Spark would Not properly install Magisk, and ruined my Recovery. Let me ask, on reboot, Did you boot into TWRP Q Mauron or TWRP Blu_Spark to install Magisk?

Sepero said:
I have had bad problems on an earlier version, where Blu_Spark would Not properly install Magisk, and ruined my Recovery. Let me ask, on reboot, Did you boot into TWRP Q Mauron or TWRP Blu_Spark to install Magisk?
Click to expand...
Click to collapse
I always use Mauron-like TWRP, and never had a problem.

Shyciii said:
I always use Mauron-like TWRP, and never had a problem.
Click to expand...
Click to collapse
Well then, I should consider you luckier than me, as I've had lots of data lost due to the issues with TWRP and Magisk. According to Mauronofrio,
"after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now."
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
If TWRP by Mauronofrio is now working with the latest Magisk, then he it appears he has not publicly stated so. Did you install Magisk 20.4?

Sepero said:
Well then, I should consider you luckier than me, as I've had lots of data lost due to the issues with TWRP and Magisk. According to Mauronofrio,
"after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now."
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
If TWRP by Mauronofrio is now working with the latest Magisk, then he it appears he has not publicly stated so. Did you install Magisk 20.4?
Click to expand...
Click to collapse
Of coz. I always use the latest Magisk, so now 20.4

I've never rooted my device can i go from stock to root or.do i need to oem unlock? Tnq.

Hi, I need help.
On step 8 I can not find files I copied on step 4. How I should copy those files to find it when I need to install them in step 8?
Thank you

I got following message returned:
FAILED (remote: boot is not allowed in Lock State)
Do I have to unlock bootloader before? This would wipe all data ...

followed the second half of the guide being an idiot and just keep all security as is. workt like a charm actually.. Thanks:highfive:

We don't need to unlock the bootloader before doing this???
fastboot OEM unlock????

techstuff_18 said:
We don't need to unlock the bootloader before doing this???
fastboot OEM unlock????
Click to expand...
Click to collapse
No, first unlock bootloader because you can't run twrp in fastbot. I did this, mean installed magisk on latest oxygen.

erdock said:
I got following message returned:
FAILED (remote: boot is not allowed in Lock State)
Do I have to unlock bootloader before? This would wipe all data ...
Click to expand...
Click to collapse
i unlocked it then all worked. and yes all data wiped

Guide for installing TWRP on OOS 11 Open Beta(Upto closed release 11)

Backup first, that's a must as always.
If coming from OOS 10 base -
1. Flash OOS 11 OB1/hotfix, after its completion do not reboot
2. Install official/unofficial twrp recovery image to ramdisk from advance menu in TWRP
3. Reboot to recovery
4.a. install magisk(optional) and reboot
4.b. repeat 1 and 2, reboot again then, 4.a.
If already on OOS 11 OB1/hotfix-
1. Flash the attached boot.img from bootloader
2. Reboot to recovery from bootloader itself(booting to system at this point will result in bootloop)
3. Follow the process as mentioned for OOS 10
Thx to Soft_M for boot image
NOTE: Above method is not compatible with OB2
OB2,OB3, closed release users directly flash official latest TWRP zip
NOTE: Installing TWRP on OB3 with any given method will cause safety net to fail

man thanks, that saved me from a bootloop from magisk...

Does this work with the HOTFIX build for OB1?

sw1tchback said:
Does this work with the HOTFIX build for OB1?
Click to expand...
Click to collapse
Yes it does, actually I tested this method on hotfix

Whats your widevine status on OOS11? Mine is l3 on unlocked bootloader.

parthrathore said:
Whats your widevine status on OOS11? Mine is l3 on unlocked bootloader.
Click to expand...
Click to collapse
For unlocked bootloader, l3 always

So you have tested official TWRP 3.5.2-9.0 on OOS Open Beta 2 and it works fine? Interesting

CrysisLTU said:
So you have tested official TWRP 3.5.2-9.0 on OOS Open Beta 2 and it works fine? Interesting
Click to expand...
Click to collapse
I confirm

I flashed oos beta2 and try to boot into twrp image through bootloader.but got to crushdump screen

What do I need to do on Beta 2 to get magisk and twrp installed? Currently none of them installed, magisk patched boot.img causes loop

romanuks said:
What do I need to do on Beta 2 to get magisk and twrp installed? Currently none of them installed, magisk patched boot.img causes loop
Click to expand...
Click to collapse
you can follow these steps:
1. install magisk app
2. boot patched boot img with magisk from another thread https://forum.xda-developers.com/t/...beta-1-for-oneplus-6-6t.4304161/post-85408313 through bootloader
3. patch boot image via magisk(if magisk ask you to allow reboot when you first time open it,don't allow it).
4. reboot your phone.you are good to go.

megaslx said:
you can follow these steps:
1. install magisk app
2. boot patched boot img with magisk from another thread https://forum.xda-developers.com/t/...beta-1-for-oneplus-6-6t.4304161/post-85408313 through bootloader
3. patch boot image via magisk(if magisk ask you to allow reboot when you first time open it,don't allow it).
4. reboot your phone.you are good to go.
Click to expand...
Click to collapse
Patching magisk from bootloader leads me to a bootloop though

megaslx said:
you can follow these steps:
1. install magisk app
2. boot patched boot img with magisk from another thread https://forum.xda-developers.com/t/...beta-1-for-oneplus-6-6t.4304161/post-85408313 through bootloader
3. patch boot image via magisk(if magisk ask you to allow reboot when you first time open it,don't allow it).
4. reboot your phone.you are good to go.
Click to expand...
Click to collapse
flash the above attached image and reboot to recovery directly, then follow the given procedure

voske15 said:
flash the above attached image and reboot to recovery directly, then follow the given procedure
Click to expand...
Click to collapse
so,on ob2 and 3, the pure twrp img will boot into crush dump,but patched boot partition won't?

megaslx said:
so,on ob2 and 3, the pure twrp img will boot into crush dump,but patched boot partition won't?
Click to expand...
Click to collapse
After testing it out, seems that is the case

edit: deleted

I had OB3 than I tried to "fastboot boot" latest TWRP to use PixelExperience. I got the QUALCOM message.
So I did the stupid thing to "fastboot flash boot" the latest TWRP. Now I'm bricked.
I will try to flash this one and see what happens. I was trying @mauronofrio unbrick guide, but it goes only until 10.3.8.

Julianocas said:
I had OB3 than I tried to "fastboot boot" latest TWRP to use PixelExperience. I got the QUALCOM message.
So I did the stupid thing to "fastboot flash boot" the latest TWRP. Now I'm bricked.
I will try to flash this one and see what happens. I was trying @mauronofrio unbrick guide, but it goes only until 10.3.8.
Click to expand...
Click to collapse
It worked. I've manage to get into TWRP and flash the stock O11. Thanks.

any actual guide to get twrp working on B3?

TheUndertaker21 said:
any actual guide to get twrp working on B3?
Click to expand...
Click to collapse
Just use FKM to flash a twrp and magisk. it should freakinglish work.