Database Info

How to install Android pie with unlocked bootloader?

How would i install Android p/9/pie on my pixel since the bootloader is unlocked and rooted? Is there a guide i can follow? Would i use the factory image or the OTA file? Any help would be appreciated. Thank you in advance.

subvapor said:
How would i install Android p/9/pie on my pixel since the bootloader is unlocked and rooted? Is there a guide i can follow? Would i use the factory image or the OTA file? Any help would be appreciated. Thank you in advance.
Click to expand...
Click to collapse
Flash like every other factory image and all should be good.

phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
Is it do able without a computer my laptop quit on me? If its not I'll have to wait till I'm around my moms house to do it. Ive only ever flash custom roms before so im not sure if it can be done with TWRP. Thanks for the help.

You need to use the fastboot tools, so you need your PC.

phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
phaino00 said:
You need to use the fastboot tools, so you need your PC.
Click to expand...
Click to collapse
Okay thanks for the help.

Whats the difference between the files?
9.0.0 (PPR1.180610.009, Aug 2018)
9.0.0 (PPR1.180610.010, Aug 2018, Telus)

The Telus one is for people who have Telus for cell service. If you don't have Telus use the 009 if you have telus use 010. Google tends to do this from time to time.

phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
Does this apply if you have custom recovery (TWRP) and modified boot.img (Magisk)?

I fastboot flashed the 9.0 files on top of the July 8.1 version without a data wipe. I had to reinstall TWRP and Magisk using the same install procedure I used on 8.1. Even though root was successfully working on Magisk 16 I had to install beta version 16.7 for the SafetyNet check to work properly.
Sent from my SHT-AL09 using Tapatalk

Butch1326 said:
I fastboot flashed the 9.0 files on top of the July 8.1 version without a data wipe. I had to reinstall TWRP and Magisk using the same install procedure I used on 8.1. Even though root was successfully working on Magisk 16 I had to install beta version 16.7 for the SafetyNet check to work properly.
Click to expand...
Click to collapse
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.

SkinnyT said:
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
Click to expand...
Click to collapse
Not the exact same problem as yours, but I found that I wasn't able to boot into the OS after flashing Magisk 16.7. It would get to the animated "G" loading screen, but then reboot automatically and go into TWRP. Currently reflashing the stock (without wipe) and trying again.

Try installing the Magisk Uninstaller, then rebooting into system. If that doesn't work, you can use fastboot to install the boot.img file taken from the full factory image. If you already have it ready to go, it's faster than a full reinstall of the OS.

SkinnyT said:
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
Click to expand...
Click to collapse
For me it did not take long for the Pixel to start after boot. Maybe a minute or two. It did take 5-10 minutes to run the Pie update.
Maybe it was because I originally installed Magisk 16 before going to version 16.7.
I agree with post-mortem's suggestion. It will be easier for you to reinstall Magisk before reinstalling the OS.

I've been starting out by flashing the factory image with adb. Then once it boots I can fastboot the twrp.img and get twrp into the recovery slot with no issues. I didn't get a chance today, but tomorrow I'll try with Magisk again.

post-mortem said:
Try installing the Magisk Uninstaller, then rebooting into system. If that doesn't work, you can use fastboot to install the boot.img file taken from the full factory image. If you already have it ready to go, it's faster than a full reinstall of the OS.
Click to expand...
Click to collapse
I did end up doing that, though I don't know if this itself solved my problem. I'll explain more below
daver68 said:
Not the exact same problem as yours, but I found that I wasn't able to boot into the OS after flashing Magisk 16.7. It would get to the animated "G" loading screen, but then reboot automatically and go into TWRP. Currently reflashing the stock (without wipe) and trying again.
Click to expand...
Click to collapse
I ended up fixing my problem. After posting this, I repeated my exact steps a few more times to make sure I wasn't doing something wrong.
1. boot into bootloader
2. fastboot factory image (without -w)
3. boot into stock Pie
4. fastboot boot twrp 3.2.2.0 image
5. install twrp 3.2.2.0 zip
6. reboot into recovery
7. flash Magisk 16.7
8. reboot into Pie
These steps didn't work, and I would always get into a bootloop that takes me straight to recovery
What I ended up doing that fixed my problem was the following
1. boot into bootloader
2. fastboot factory image (without -w)
3. boot into stock Pie
4. fastboot boot twrp 3.2.2.0 image
5. install twrp 3.2.2.0 zip
6. reboot into recovery
7. flash Magisk uninstaller
8. reboot recovery
9. flash Magisk 16.6
10. set boot partition to B
11. reboot into rooted Pie
Specifically, I used the Magisk Uninstaller, used an "older" version of Magisk (16.6, not the later 16.7), and I also changed my boot partition from A to B after flashing Magisk. This worked for me, and until I know specifically why, I'm going to just re-use this procedure on the next factory image update.
Hopefully this can help someone else having the same problem!

flashed twrp and its gone

Guys i faced a wierd problem . I flashed twrp image and then twrp zip and then magisk ..i rebooted and when i tried to boot in recovery . The recovery was gone but magisk is still . What should i doo nowwww ?

What you do now is you
fastboot boot blu_sparktwrp.img
And then in twrp you flash blu_sparktwrp.zip
Reboot to twrp
Flash magisk 17.2.Zip
Done..rebot.

whizeguy said:
What you do now is you
fastboot boot blu_sparktwrp.img
And then in twrp you flash blu_sparktwrp.zip
Reboot to twrp
Flash magisk 17.2.Zip
Done..rebot.
Click to expand...
Click to collapse
It didnt work ....it goes away after a reboot

sanu26661 said:
It didnt work ....it goes away after a reboot
Click to expand...
Click to collapse
It must work. You're basically flashing TWRP temporarily, so when you are in TWRP for the first time, you have to flash the zip file so that it stays installed. Try that again, maybe you did something wrong, but it has to work, you just need the .img that you flash with your PC, and the .zip that you flash using TWRP when you boot into it the first time.

Kluxe Nobody said:
It must work. You're basically flashing TWRP temporarily, so when you are in TWRP for the first time, you have to flash the zip file so that it stays installed. Try that again, maybe you did something wrong, but it has to work, you just need the .img that you flash with your PC, and the .zip that you flash using TWRP when you boot into it the first time.
Click to expand...
Click to collapse
I booted img first then installed zip but when i reboot to recovery thers only stock recovery present ...did like 10 times results are same

the blu_spark twrp? v2?

If twrp isn't sticking, from my experience is to lock bootloader, flash stock OS and start from scratch.....
Do not flash stock with unlocked bootloader

I need Help with Rooting OP6 stable not beta 9.0.2, bootloader is unlocked

So, i have used my whole saturday on unlocking the booloader which was the easiest and quickest and then trying to root, but that has failed every time. I first flashed the stock firmware zip 9.0.2 then I go back I dont reboot and flash the twrp and magisk zip and then it wont boot up,
when I try rebooting after flashing the firmware back to the system it sends me to the firmware,
when I try flashing a new firmware and then boot into fastboot then twrp and flash magisk it wont boot up,
and when I do the same only with twrp it wont neither.
I have tried sevel magisk versions, 17.1,17.2,17.3 none of them worked
as for the twrp blu spark or the one from the twrp website, i was always able to boot into twrp but not really to flash it as that would end in a twrp loop
can PLEASE anyone, someone, with a good heart and patience help me ? im really loosing my ****s over this
:fingers-crossed::fingers-crossed:

Try booting into blu_spark twrp
Installing blu_spark twrp
Rebooting to blu_spark twrp
Install magisk 17.3 or 17.1 (I am using 17.3 because it it beta but less stable.)

Faaris Ansari said:
Try booting into blu_spark twrp
Installing blu_spark twrp
Rebooting to blu_spark twrp
Install magisk 17.3 or 17.1 (I am using 17.3 because it it beta but less stable.)
Click to expand...
Click to collapse
can you provide me with the files ? plus
does it make a difference if I take these twrps compared to the one im using from their website ? because I dont see how this can be the fault ?

galaxyss8 said:
can you provide me with the files ? plus
does it make a difference if I take these twrps compared to the one im using from their website ? because I dont see how this can be the fault ?
Click to expand...
Click to collapse
The normal twrp is known to be buggy on the OnePlus 6 since there was encryption and stuff. Here is the blu_spark twrp IMG to boot:
https://forum.xda-developers.com/devdb/project/dl/?id=30485
And here you need to flash the blu_spark twrp: https://forum.xda-developers.com/devdb/project/dl/?id=30484
Flash that then reboot into recovery again
Then flash magisk
If this doesn't work for you I think there is another way.

Faaris Ansari said:
The normal twrp is known to be buggy on the OnePlus 6 since there was encryption and stuff. Here is the blu_spark twrp IMG to boot:
https://forum.xda-developers.com/devdb/project/dl/?id=30485
And here you need to flash the blu_spark twrp: https://forum.xda-developers.com/devdb/project/dl/?id=30484
Flash that then reboot into recovery again
Then flash magisk
If this doesn't work for you I think there is another way.
Click to expand...
Click to collapse
ive done that now and im waiting again in the; the boot loader is unlocked and software integrety.. winodw
im waiting now for some minutes, i flashed the blu spark zip pressed back went to reboot pressed on reboot to recovery and flashed magisk and then reboot to system, thats where i am now

galaxyss8 said:
ive done that now and im waiting again in the; the boot loader is unlocked and software integrety.. winodw
im waiting now for some minutes, i flashed the blu spark zip pressed back went to reboot pressed on reboot to recovery and flashed magisk and then reboot to system, thats where i am now
Click to expand...
Click to collapse
You might be on the wrong slot. DO you even have a system to boot to? Not sure why you even tyred flashing the 9.0.2 ROM. If I was you I would start over. Use the fastboot ROM to get a clean wiped system booting. After that
fastboot boot bluespark twrp v86. Img
Flash bluespark twrp v86. Zip
Reboot revovery
Flash magisk 17.1

yldlj said:
You might be on the wrong slot. DO you even have a system to boot to? Not sure why you even tyred flashing the 9.0.2 ROM. If I was you I would start over. Use the fastboot ROM to get a clean wiped system booting. After that
fastboot boot bluespark twrp v86. Img
Flash bluespark twrp v86. Zip
Reboot revovery
Flash magisk 17.1
Click to expand...
Click to collapse
I flashed the rom because my phone didn't boot up anymore after either flashing TWRP or magisk.
Why should I use the fastboot room, what is the benefit if I use it.
Is the reboot to recovery necessary ? I feel like that part is actually not working properly ?

galaxyss8 said:
I flashed the rom because my phone didn't boot up anymore after either flashing TWRP or magisk.
Why should I use the fastboot room, what is the benefit if I use it.
Is the reboot to recovery necessary ? I feel like that part is actually not working properly ?
Click to expand...
Click to collapse
Yes the reboot to recovery is the most nessesary part of it as it will change slots.
You can try boot to recovery
Flash oos full rom
Flash bluespark twrp. Zip
Reboot recovery
Flash full ROM again
Flash bluespark twrp. Zip again.
Reboot recovery
Flash magisk.

yldlj said:
Yes the reboot to recovery is the most nessesary part of it as it will change slots.
You can try boot to recovery
Flash oos full rom
Flash bluespark twrp. Zip
Reboot recovery
Flash full ROM again
Flash bluespark twrp. Zip again.
Reboot recovery
Flash magisk.
Click to expand...
Click to collapse
Can you explain how to properly boot back into recovery?
Previously I either just went on the back button and flashed the other Zip's or I went back to the reboot overview and pressed recovery there but that also did not seem to work properly I think.

galaxyss8 said:
Can you explain how to properly boot back into recovery?
Previously I either just went on the back button and flashed the other Zip's or I went back to the reboot overview and pressed recovery there but that also did not seem to work properly I think.
Click to expand...
Click to collapse
Just press back button in Recovery/ reboot / choose recovery.

TWRP gone after Magisk update

Hey everyone,
My TWRP has been erased from the phone and all I did was update magisk to the latest version (v 20). I'm on Android Pie, why did that happen? I can boot the phone and everything looks fine, it's just that TWRP is gone.
Should I just install it again ? Will I lose data if I install latest TWRP ?
THanks

Hmm.. i dont know what's happened to yours.. but i also updated my magisk to v20. And all.is well.. when i checked thru it a while ago... I can still boot to twrp..
Are you using the v70 twrp?? Try flashing it again via magisk.. be sure to flash magisk.again after that.. ??

santiagoruel13 said:
Hmm.. i dont know what's happened to yours.. but i also updated my magisk to v20. And all.is well.. when i checked thru it a while ago... I can still boot to twrp..
Are you using the v70 twrp?? Try flashing it again via magisk.. be sure to flash magisk.again after that..
Click to expand...
Click to collapse
No, I was using an old version of TWRP, don't remember what it was exactly, but it wasn't the latest one for sure.
What would be the correct steps to flash TWRP and Magisk so my phone boots up and I don't lose data?

Boot to twrp using fastboot then install twrp and magisk then proceed to reboot to system

Phantom Thief said:
Boot to twrp using fastboot then install twrp and magisk then proceed to reboot to system
Click to expand...
Click to collapse
same here. can't permanetly install twrp as recovery

Same here... I tried to install TWRP again and, at a certain point, phone couldn't even boot. I had to fastboot boot img, flash installer and then magisk 19.3. Now it all works
I was already on 3.3.1-70 ofc

Jack_Sparrow_ said:
Same here... I tried to install TWRP again and, at a certain point, phone couldn't even boot. I had to fastboot boot img, flash installer and then magisk 19.3. Now it all works
I was already on 3.3.1-70 ofc
Click to expand...
Click to collapse
which twrp version u use?

lee0525 said:
which twrp version u use?
Click to expand...
Click to collapse
Not the bluspark, the other one

I got the same issue, twrp is gone after update magisk to v20
what is the right way to install twrp from magisk v20?
I downloaded twrp .70
tnx

mikek753 said:
I got the same issue, twrp is gone after update magisk to v20
what is the right way to install twrp from magisk v20?
I downloaded twrp .70
tnx
Click to expand...
Click to collapse
looks like there is an issue with the latest magisk update. We'll have to wait for an update to the magisk or twrp so TWRP can stick

To fix it i booted into twrp then installed the last rom i was using (pie) then flashed twrp.zip, rebooted into recovery then installed magisk 19.4. you'll have to re-install your modules and re enable your apps that used root.

so since I'm using PIE 9.5.13. Just install the full zip of 9.5.13 through local storage > And then flash twrp and then magisk through twrp? Will there be data loss?

I got twrp back, in magisk by install twrp.
magic download I run flash the twrp and recovery is back
there was no any data loss in my case

For those have the same issue, here is the solution without flashing a new ROM.
https://github.com/topjohnwu/Magisk/issues/1920
from bootloader mode execute
fastboot flash boot boot.img (the stock boot.img)
boot twrp image (I used .70 unified)
fastboot boot twrp.img
flash twrp-installer.zip
flash magisk.zip (I flashed 19.4)
Enjoyyyyy
PS: you can get your corresponding stock boot.img from
https://www.oneplus7tips.com/category/oneplus-7-pro/kernels/

lee0525 said:
For those have the same issue, here is the solution without flashing a new ROM.
https://github.com/topjohnwu/Magisk/issues/1920
from bootloader mode execute
fastboot flash boot boot.img (the stock boot.img)
boot twrp image (I used .70 unified)
fastboot boot twrp.img
flash twrp-installer.zip
flash magisk.zip (I flashed 19.4)
Enjoyyyyy
PS: you can get your corresponding stock boot.img from
https://www.oneplus7tips.com/category/oneplus-7-pro/kernels/
Click to expand...
Click to collapse
Thank you.....
New to the OP7 Pro and this post saved me... I got my device last week and Magisk v20 was current and removed TWRP.... There is a Magisk 21 update is that safe or just say right here?

Issues getting root back after Android 11 Update OP6

Hey, after installing android 11 on my Oneplus 6 I have servere issues on getting root back.
Both methods I used result in a stuck boot.
Method 1: fastboot boot twrp, then install magisk.zip (tried with both 21.4 (last with a zip) and the renamed 23.0 (from apk to zip)
Method 2: Extracted boot.img from my OTA update, then patched with magisk 23.0.
Flashed the new boot.img -with fastboot -with twrp both result in a stuck boot.
Suprisingly flashing the extracted boot.img from the OTA boots fine, but that image is without magisk
Update: I have extracted the boot.img directly from the phone, patched it and it still doesn't work

I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it

Thratchen said:
I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it
Click to expand...
Click to collapse
twrp actually works, but after flashing magisk or flashing a magisk boot.img it breaks. I have a working version here
Ping me if you get magisk working

I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help

To remember!

Thratchen said:
I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help
Click to expand...
Click to collapse
Which installation method of magisk did you use?
How long did you wait after first boot?

I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you

Thratchen said:
I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you
Click to expand...
Click to collapse
Thanks for the reply, as a last question: Which magisk version did you use (could you link i?t). I assume you took the magisk v23 apk and renamed it to .zip? or what did you do?

Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk

Thratchen said:
Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Click to expand...
Click to collapse
Hmm, I perfectly copied your instructions and still get a bootloop. Even reflashed 11.1.1.1 again. Might be time for a reset

Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.

vkass said:
Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.
Click to expand...
Click to collapse
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)

is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp latest zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !

tacohell said:
is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp lat est zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !
Click to expand...
Click to collapse
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)

UraniumDonut said:
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)
Click to expand...
Click to collapse
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.

vkass said:
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.
Click to expand...
Click to collapse
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!

UraniumDonut said:
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)
Click to expand...
Click to collapse
Thhank @UraniumDonut - that worked - I have never before used that method and honestly didn't even know about it. I use the official documented twrp way which is to first fastboot in to twrp and then install the zip file which has to be located on the phone file system. This method seems a lot easier!
As to magisk, I usually flash that from twrp using the zip file method and never have had any issues. But with all the issues surrounding oos 11 I am playing it safe as I don't want to get in to a boot loop. Will do some more research before I try something. But thanks to you I have made 1 step forward progress!

UraniumDonut said:
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!
Click to expand...
Click to collapse
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.

vkass said:
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.
Click to expand...
Click to collapse
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing

Just for reference here
UraniumDonut said:
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing
Click to expand...
Click to collapse
I posted detailed steps if you want to give this a try @UraniumDonut: https://forum.xda-developers.com/t/how-to-root-op6-11-1-1-1.4344269/#post-85765879