Database Develop

[MAGISK] [BOOT] Pre rooted Boot.img for Oneplus 6T Android 10 Open Beta 1

Hi Guys
UPDATE 2: (2/11/2019) Boot img now patched to Magisk V20.1 and added Google Drive as a mirror
UPDATE: It has come to my attention that some users are having issues with this version, please note this is still in beta and root isn't fully supported yet, also please make sure your running the latest magisk manager (version 7.3.5 at the time of this update) BEFORE flashing the patched boot IMG, those currently having issues, try flashing the stock IMG provided and installing the latest magisk manager then flashing the patched IMG
here is a working magisk patched boot img for you guys wanting root on your new android 10 open beta 1 software.
PLEASE BE AWARE THIS DOESNT COME WITH TWRP, THIS MAY ALSO BREAK THE ORIGINAL STOCK RECOVERY, BY FLASHING THIS BOOT IMG, YOU TAKE FULL RESPONSIBILITY FOR YOUR DEVICE AND NEITHER I OR XDA WILL BE HELD RESPONSIBLE
this DOESNT contain TWRP but is just rooted with magisk v20.0
simply flash the provided file in fastboot with the following command
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
Please note this will ONLY work with the OnePlus 6T
i have also provided the stock android 10 boot img in case anything goes wrong
DOWNLOADS::
[CURRENT VERSION - Magisk V20.1]
Mega -> https://mega.nz/#!YI5BkICC!66fiUUdmg1EgGcTNExHZ52IoliVY4HBMBdwxErpI-co
Google Drive -> https://drive.google.com/file/d/1xyRPzsKh1kQXK0_RpdnesuR85vc6FvRf/view?usp=sharing
[OLD Versions]
[Magisk V20.0]
https://mega.nz/#!cQRFwA7b!R1yLz1ozFUTEOLXv-OREK-oF5YeUGN1PrWvSSh22vHw
Stock Boot img
https://mega.nz/#!1BAnRCoK!nu6UVAnR2yHnbaf54FEhc7U_3oEyP1q2BFMU0LK7XC4
Credits:
@oneplus for the phone and stock boot image
@topjohnwu for magisk and his boot image patcher

Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.

Do i need a computer for this ?

techlogik said:
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Click to expand...
Click to collapse
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img

charlie95113 said:
Do i need a computer for this ?
Click to expand...
Click to collapse
yes because fastboot command is needed, henced done using pc.

mywebslave said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I also used the payload extractor and took the stock boot.img and patched it with Magisk myself. Same issue. So obviously Magisk just doesn't suppor this phone yet and Devs need to work on it.
Thx

techlogik said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I tried patching the stock boot.img myself as well, it ends up being the exact same size as the TS for this method...same problem.
Thx
Click to expand...
Click to collapse
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.

mywebslave said:
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
Click to expand...
Click to collapse
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks

techlogik said:
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
Click to expand...
Click to collapse
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.

mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
So should we be using this instead?
Sent from my ONEPLUS A6013 using Tapatalk

mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine

zhenliang1102 said:
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
Click to expand...
Click to collapse
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot

when i flash the magisk_patched.img and my cellphone reboot my cellphone does not recognize my simcard and have no network, am back on the stock boot.img

cultofluna said:
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
Click to expand...
Click to collapse
I doubt this would work because the patched image is only 26mb while the stock boot image is 64mb. Someone mentioned this in the OB thread

Black screen after the update
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.

Hy, do you have proximity sensor problem after update?! Thanks...is anything i can do?

jack5225 said:
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Click to expand...
Click to collapse
Same happened to me
Phone boots to a Black screen
adb reboot bootloader -> works
fastboot flash boot boot.img -> works
Only Patched boot.img -> boots to black screen
Sent from my ONEPLUS A6010 using Tapatalk

Same for me. Softbrick and phone doesn't boot. It also encrypted my whole /data with diferent password i think and I had to wipe whole /data partition. System boots after wiping data storage but as soon as I install magisk it doesn't want to boot again. I guess I will wait for final image and TWRP support.

i couldnt flash it manually (via cmd), but all in one tool managed it well.
worked fine and quick,thank you

Crazy that some phones it is working and others it doesn't. Nothing we are doing wrong, OP has work to do still. I can imagine this official update to Q is going to cause a support fiasco...if you want to root that is. ROFL. All works fine with stock though upgrade. Understand it is Beta, but they claim a November official release
We are going to need some Dev help. Or going to need to sell this phone and upgrade to the 7t or Pro..haha

TWRP rooted boot image for OOS11 Beta 2. (OB2)

Pre rooted boot image with TWRP included for OOS11 Beta 2, OB2. This is not for the beta 1 hotfix. Flash in fastboot if not rooted, and through a kernel manager if you are already on beta 2 and rooted but don't have TWRP because flashing kept putting you in crash dump mode. Remove lock screen as a precaution before flash. No need to wipe anything.

Just like any other image I tried, this gets me into a boot loop on the spinning circle. I can get into twrp, but the magisk root seems to be breaking something. Any ideas?

romanuks said:
Just like any other image I tried, this gets me into a boot loop on the spinning circle. I can get into twrp, but the magisk root seems to be breaking something. Any ideas?
Click to expand...
Click to collapse
What device are you using ( 6 or 6T ) ? Or whats the code name for your device??

SOK seila said:
What device are you using ( 6 or 6T ) ? Or whats the code name for your device??
Click to expand...
Click to collapse
OP6T europe

i use command "fastboot boot fajita-ob2-oos11-twrp-rooted.img" but in boot to system

lockmunk said:
i use command "fastboot boot fajita-ob2-oos11-twrp-rooted.img" but in boot to system
Click to expand...
Click to collapse
you should probably write fastboot flash boot ...

romanuks said:
you should probably write fastboot flash boot ...
Click to expand...
Click to collapse
"fastboot boot" and "fastboot flash" are do the same thing (to flash). If you use "fastboot flash" you have to manually reboot the phone to system or twrp, it is auto reboot after finished flash (based on image if flash TWRP it will boot to TWRP) if you use "fastboot boot".

Sooooo, any ideas on what I could do?

romanuks said:
Sooooo, any ideas on what I could do?
Click to expand...
Click to collapse
So you are using op6T-EU. I don't know if eu image different from groble image or not but you can try to patch boot image yourself.

Well, I already tried that too, so really not a clue as to why it wouldnt work... Probably should just downgrade, backup and get lineage or so

OOS stable boot image and patched magisk boot image both for 11.1.1.1.

Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.

I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.​

235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D

sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot

235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well

sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process

sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)

previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later

abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.​
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.

I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!

F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.

I got boot loop after updating to 11.1.2.2
Any new boot img?

izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go

rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.

The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!

rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?

raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes

rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you

Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.​​I uninstalled magisk by mistake and could regain root, quick and painless​

Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?

Development [RECOVERY][UNOFFICIAL] TWRP for barbet

Download:
twrp-3.6.0_11-0-barbet.img
This is my unofficial built, fully working with A12 with some remarks:
- internal storage decryption works but you have to set Screen lock to None or Swipe in Android Settings -> Security. If Pattern, Pin or Password are set storage decryption and MTP will not work until TeamWin fixes the code for A12.
- nandroid backup/restore works but you might need to reboot Android a couple of times after restore until dalvic-cache fully rebuilds. Until then you will see black home screen background instead of your wallpaper... Just keep restarting until everything is back to normal.
- DON'T MESS(WIPE) WITH METADATA in TWRP Advanced Wipe!!! If you do you can't boot Android until formatting data = factory reset.
DO NOT FLASH THIS TWRP IMAGE IN FASTBOOT!!!
Install TWRP form within itself after boot with fastboot.
Not tested on A11 so might have some bugs...
recovery.log and logcat are helpful.
To boot it connect USB and run these commands:
Code:
adb reboot bootloader
fastboot boot twrp-3.6.0_11-0-barbet.img
While in recovery you can install it permanently on the boot partitions by going to Advanced and pressing Flash current TWRP. Root will be lost so after that you have to reboot to bootloader again, fastboot boot your magisk patched boot.img, direct patch boot with magisk to get root back and reboot. Done. You have root and TWRP on device. To get to TWRP:
Code:
adb reboot recovery
Big thanks to @bigbiff, @Captain_Throwback and the entire TeamWin for their work!
Source code:
device tree - my GitHub
recovery - TeamWin GitHub

You have no idea how excited I am this was posted.. Everyday I check github and Google for something! Thank you so much for this!

Touch does not seem to be working in your build.
Mozilla Community Pastebin/qhsgAEtd (Plain Text)
USB mouse works for now.
Connection to a computer works only until unplugged.
MTP doesn't work even if not encrypted. Stalls during copy. No error.

eriklion said:
Touch does not seem to be working in your build.
Mozilla Community Pastebin/qhsgAEtd (Plain Text)
Click to expand...
Click to collapse
Thanks for the log.
What ROM are you running? Lineage? Looks like the kernel is the problem:
Code:
Linux version 4.19.110-dirty ([email protected]) (Android (6443078 based on r383902)
clang version 11.0.1 (https://android.googlesource.com/toolchain/llvm-project
b397f81060ce6d701042b782172ed13bee898b79)) #1 SMP PREEMPT Wed Feb 24 18:49:40 EST 2021
and the touchscreen drivers doesn't load:
Code:
modprobe: LoadWithAliases was unable to load ftm5.ko
modprobe: LoadWithAliases was unable to load sec_touch
Sorry, can't do anything about it... Use recovery with fastboot boot.
Connection to a computer works only until unplugged.
Click to expand...
Click to collapse
Confirmed, will look at it... As a workaround go to Mount and toggle disable/enable MTP and it'll work again.
MTP doesn't work even if not encrypted. Stalls during copy. No error.
Click to expand...
Click to collapse
Must be the kernel again... Works fine here.

nijel8 said:
Thanks for the log.
What ROM are you running? Lineage? Looks like the kernel is the problem:
Code:
Linux version 4.19.110-dirty ([email protected]) (Android (6443078 based on r383902)
clang version 11.0.1 (https://android.googlesource.com/toolchain/llvm-project
b397f81060ce6d701042b782172ed13bee898b79)) #1 SMP PREEMPT Wed Feb 24 18:49:40 EST 2021
Click to expand...
Click to collapse
I hadn't even flashed Lineage yet.

eriklion said:
I hadn't even flashed Lineage yet.
Click to expand...
Click to collapse
Is the recovery flashed or fastbooted? Also you did not answer what android you have.
Log shows recovery is flashed and trying to load touchscreen drivers from vendor partition. If it is fastbooted then something else is wrong, device reports normal reboot to recovery, not boot from bootloader and touchscreen drivers are messed up.
I will need recovery.log too.

nijel8 said:
Is the recovery flashed or fastbooted? Also you did not answer what android you have.
Log shows recovery is flashed and trying to load touchscreen drivers from vendor partition. If it is fastbooted then something else is wrong, device reports normal reboot to recovery, not boot from bootloader and touchscreen drivers are messed up.
I will need recovery.log too.
Click to expand...
Click to collapse
That was just your TWRP flashed to boot via fastboot, then reboot-bootloader then select recovery. that was with latest A11 build freshly flashed.

I also couldn't get the touchscreen to work. I flashed using:
Code:
adb reboot bootloader
fastboot flash boot_b twrp-3.6.0_11-0-barbet.img
fastboot flash boot_a twrp-3.6.0_11-0-barbet.img
I was softlocked to the Recovery partition until I flashed back..

InfoSecREDD said:
I also couldn't get the touchscreen to work. I flashed using:
Code:
adb reboot bootloader
fastboot flash boot_b twrp-3.6.0_11-0-barbet.img
fastboot flash boot_a twrp-3.6.0_11-0-barbet.img
I was softlocked to the Recovery partition until I flashed back.
Click to expand...
Click to collapse
fastboot boot ≠ fastboot flash boot
Am I missing something here?
Boot TWRP and then flash TWRP through it's advanced settings.

kingofnice said:
fastboot boot ≠ fastboot flash boot
Am I missing something here?
Boot TWRP and then flash TWRP through it's advanced settings.
Click to expand...
Click to collapse
Yep, you're on track.
fastboot flash boot overwrites the /boot partition, including the kernel, so all you'd be able to boot to would be TWRP. To fix this, download the factory image and reflash the stock boot image.
fastboot boot twrp.img forces a "live" boot of TWRP via USB; to install it, you'd have to patch the boot image through TWRP settings.

V0latyle said:
Yep, you're on track.
fastboot flash boot overwrites the /boot partition, including the kernel, so all you'd be able to boot to would be TWRP. To fix this, download the factory image and reflash the stock boot image.
fastboot boot twrp.img forces a "live" boot of TWRP via USB; to install it, you'd have to patch the boot image through TWRP settings.
Click to expand...
Click to collapse
It wouldn't be the likely culprit of the touchscreen issues being brought up, would it?

V0latyle said:
Yep, you're on track.
fastboot flash boot overwrites the /boot partition, including the kernel, so all you'd be able to boot to would be TWRP. To fix this, download the factory image and reflash the stock boot image.
fastboot boot twrp.img forces a "live" boot of TWRP via USB; to install it, you'd have to patch the boot image through TWRP settings.
Click to expand...
Click to collapse
Yeah forgot and ran the install script I usually use to install my boot.img.. But Idk about it stopping touchscreen inputs tho.

Updated... Please redownload from OP
- fixed touchscreen not working on A11 ROMs(not tested but should work), please report...
- fixed MTP on reconnecting
Do not flash twrp-3.6.0_11-0-barbet.img!!! Install it form its Advanced meny ones booted with fastboot...

kingofnice said:
It wouldn't be the likely culprit of the touchscreen issues being brought up, would it?
Click to expand...
Click to collapse
InfoSecREDD said:
Yeah forgot and ran the install script I usually use to install my boot.img.. But Idk about it stopping touchscreen inputs tho.
Click to expand...
Click to collapse
Touchscreen wasn't working b/c A11 bootloader reports different bootreason value(guessing...) than A12(on what I test) and the script that loads the appropriate touchscreen drivers for the booted kernel got confused...
Fixed it... Now script reads booted kernel cmdline which has special twrp fastboot portion and should never load wrong drivers.

Waiting for a stable version but good job! Well appreciated.

My pin worked on Android 11 when loading the twrp image, I was able to install the recovery and do the Direct install with magisk after loading my master_boot.img (magisk patched img from stock barbet).
I haven't done much else yet. But this looks good so far!

Hell ya! Installed while running Lineage and Magisk rooted! Thanks for this!

lowridincrew said:
Waiting for a stable version but good job! Well appreciated.
Click to expand...
Click to collapse
Apart from A12 pin/password/pattern decryption which will take considerable time, this is stable version... or you mean official...

Updated... Please redownload from OP
- fixed vibration haptics
- synced with latest TeamWin code
Do not flash twrp-3.6.0_11-0-barbet.img!!! Install it form its Advanced menu ones booted with fastboot...

This is awesome!
One question.
If it's for A12, why is it labled twrp-3.6.0_11-0-barbet.img?
I thought _11 indicated android version?
Shouldn't be twrp-3.6.0_12-0-barbet.img?

Question root failed and bootloop

I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Hey,
If you've only booted the image, then you only need to reboot and the image is lost, the only way that it would be permanent is if it was flashed: fastboot flash not: fastboot boot.
Usually what happens is when you obtain a firmware to install or in your case change region, and you wish to root this firmware you would extract payload.bin then use fastboot enhance to extract the boot.img
Then copy to your phone and patch it with the latest stable Magisk (in this case 24.3)
So again, if you've only booted the image then just reboot your phone and it'll turn on using the actual flashed boot.img from the firmware, not the one you booted.
If that doesn't work then you must have flashed it. In which case you can either re-flash your original boot.img or boot then direct install a correctly patched image for the correct firmware (after a success boot) via Magisk.

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Here's a good "how to" to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/

Canuck Knarf said:
Here's a good how to to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Click to expand...
Click to collapse
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse

dladz said:
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
Click to expand...
Click to collapse
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk

Canuck Knarf said:
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Click to expand...
Click to collapse
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
If what he's advised is true then he's successfully changed OS/region and now wants to root, the only thing he's done thus far is to boot a boot image. I think he's flashed it as booting is not permanent, to suggest to go ahead and attempt to obtain a color OS boot image or vendor image is absolutely ridiculous.
He's on an EU firmware. So he requires an EU boot image.

He's in boot loop cause he is booting to A slot...

Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode

dladz said:
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
Click to expand...
Click to collapse
oxygen OS using the firmware EU 11_A.12.... He still needs boot img ...vender_boot form the firmware EU 11_A.12 . to root

leofung_wai said:
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
Click to expand...
Click to collapse
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance

He already had boot?? What are you talking about???
He had a functional OS, in order to root you only need ONE image.
The boot image which comes from OOS. The link you sent is for Color OS?? Make sense now ??
He just needs to patch it correctly and boot it then direct install.
Im going over this again with someone who's incapable of understanding the basics.

Canuck Knarf said:
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
Click to expand...
Click to collapse
You do realise that booting an image does not need to be directed don't you?
Only by flashing should you direct the image to a particular slot.
By flashing you are permanently flashing an image.
I don't think you understand this so I'll make it simple for you.
You want to root your phone. You have an image you've just patched, from boot.img to magisk_patched.img
Firstly you would want to send this via fastboot, you do not need fastboot enhance for this.
The preferred way to do this is to fastboot boot magisk_patched.img
Why is this preferred??
Because if it fails as it may. Then you are not stuck in a boot loop, you just reboot and you're back in the OS.
The 2nd method is flashing.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter.
Now although this can work it is not the preferred method because you aren't just booting the image you are flashing it, this means that if it fails you cannot just reboot and get back to the OS you have to either obtain a new boot image and patch it although you cannot do this yourself as your phone no longer boots or you obtain an already patched boot image, again the last one I wouldn't recommend..

Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
Ok so if you've got into the system..
You need to follow the instructions I have in my guide in order to get root...
You can use the boot image I have there.

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
It is always better to patch boot.img of your own version (you can dump it from payload dumper etc.) and then only fastboot boot patched_image.img and then directly install it via Magisk.

Boot this image.
192 MB folder on MEGA
mega.nz

Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally

Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done

leofung_wai said:
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Click to expand...
Click to collapse
If you've patched your own image and booted it then click Magisk then install. Then direct install and you're done..

dladz said:
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
Click to expand...
Click to collapse
thanks i success root by your image now
but i had a question, i messed up the slot B and now can only boot through slot A Will it affect anything