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

Nokia 4.2 Bricked, but can still enter FastBoot

Hello everyone :laugh:!
Tried rooting the Nokia 4.2, did not know which img to use exactly so I tried one from some other shady site and messed up. Luckily, the recovery partition was still working. After trying to boot lots of images, I got tired and accidentally even flashed a Nokia 6.2 TWRP image to my recovery partition. Then I completely messed up. The phone only gets into fastboot now. May I please ask some help of you? I've been trying for days to fix things. I just wanted to root the original firmware. Now when I try to flash TWRP, it even says that the 'recovery' partition has no partition table! I can still write to boot_a and boot_b though. The phone originally had the October patch level, but before bricking it I upgraded it to the December level.
Kind regards,
Alexander47u

Search on google and try do download and flash the stock firmware (unrooted)

Phone does not get detected by QFIL
thegamingcat13 said:
Search on google and try do download and flash the stock firmware (unrooted)
Click to expand...
Click to collapse
I have tried this using QFIL, however the phone is not detected. The phone also goes into fastboot as soon as the cable is plugged in, even when the phone is off.
Have also installed appropiate drivers for QFIL, but no luck.

Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot

Works, Thank you!
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Thank you! This worked flawlessly.

#metoo
Haha, I have done the EXACT same thing as you. Now I can only enter fastboot mode and when I try to flash anything I have downloaded I get an error about missing partitions. I have looked everywhere for details on the partition sizes, mount points and so on but nobody has uploaded the information. In the end I went and purchased a second device in order to dump the entire stock ROM in order to fix the first phone. I've got the second phone running in ADB-mode but I can only backup to an .ab file so now I am back at square one. All of the guides I can find on how to dump the ROM involves flashing TWRP recovery but THERE IS NONE FOR THE 4.2 :crying: And after researching Android forensics I have found a guide to dumping the ROM but it needs root access in the phone shell. All I wanted was root (and LineageOS). Does anyone feel like patching the stock ROM and making a zip-file containing the img-files from all of the partitions?

Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.

alexander47u said:
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
Click to expand...
Click to collapse
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!

You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.

alexander47u said:
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
Click to expand...
Click to collapse
I was able to succesfully patch boot.img with magisk, then I copied the patched boot image to my computer with linux. Fastboot flash boot boot.img worked but upon reboot I got an error message saying "corrupt data" and offered to do a factory reset. Any chance you can upload your patched boot image so I can use yours?

Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129

Posted

alexander47u said:
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Click to expand...
Click to collapse
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?

Oslokalle said:
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Click to expand...
Click to collapse
Up to March. I used the stock rom that is floating around on the internet. Not sure if I am allowed to post stock roms.
I was able to update to April using Magisk but not any further than that.

thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Tried this using a user_update.zip file from www[.]getdroidtips[.]com/stock-rom-nokia-4-2-firmware/. My phone boots again, but Wi-Fi doesn't work. My model # is TA-1133. What should I do?
Edit: tried to install the latest security OTA from t[.]me/nokiarepoen/379, V2.29C, but I get
Code:
E:Package is for source build 00WW_2_29B but expected 00WW_1_17I
. Is there a base user_update for build 00WW_2_29B floating around?

Oslokalle said:
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
Click to expand...
Click to collapse
Kindly provide me that zip too.

Need help with TWRP patching - V409N

Hello everyone.
My phone is currently on V409N30f_00_LGU_KR_OP_0126.kdz, i was successful in unlocking it via 9008 method, and just a moment ago i was also successful in patching it with magisk (thanks to great guide here: https://forum.xda-developers.com/t/root-eu-lmv405ebw-magisk.3912959/ ). I had some problems, mainly i didn't know that you actually need proper abl_a/abl_b to boot the OS (i thought it's not a part of boot process, unless you push some buttons, but that doesn't seem to be the case). My final problem is that i can't seem to be able to get a proper permanent fastboot installed, and by proxy i can't get TWRP as well. Therefore i have couple of questions here:
1. How to get proper fastboot on an encrypted phone with android Q? Do i have to get rid of the encryption? How?
2. From what I understand, the boot partition needs to be patched to include TWRP, similar to how magisk was prepared - is there guide how to do that?
3. Why the phone fails to boot if i try to sideload/fastboot to TWRP image provided on this forum?
Thanks in advance for all your support

Scorcerer said:
Hello everyone.
My phone is currently on V409N30f_00_LGU_KR_OP_0126.kdz, i was successful in unlocking it via 9008 method, and just a moment ago i was also successful in patching it with magisk (thanks to great guide here: https://forum.xda-developers.com/t/root-eu-lmv405ebw-magisk.3912959/ ). I had some problems, mainly i didn't know that you actually need proper abl_a/abl_b to boot the OS (i thought it's not a part of boot process, unless you push some buttons, but that doesn't seem to be the case). My final problem is that i can't seem to be able to get a proper permanent fastboot installed, and by proxy i can't get TWRP as well. Therefore i have couple of questions here:
1. How to get proper fastboot on an encrypted phone with android Q? Do i have to get rid of the encryption? How?
2. From what I understand, the boot partition needs to be patched to include TWRP, similar to how magisk was prepared - is there guide how to do that?
3. Why the phone fails to boot if i try to sideload/fastboot to TWRP image provided on this forum?
Thanks in advance for all your support
Click to expand...
Click to collapse
Follow this link for the 30f boot_a with twrp injected.
Let me try to clarify a bit; The engineering v35 abl is Oreo. So if you have it installed, the phone won't boot, unless your OS is Oreo (which it isn't).
So the purpose of having that abl isn't to boot the phone, it's only to be used for things like 'fastboot oem unlock' or 'fastboot flash abl_a abl_original_a.img'
it's not to boot the phone. And yes, absolutely it's a part of the boot process abl stands for 'android boot loader'.
So to make use of that v35 eng abl (after you've unlocked the boot loader), would be to flash it to the inactive slot on the phone (most people that would be abl_b). That way, you can use twrp to switch slots, use fastboot, then switch back to the active slot.
To use that proved boot_twrp_a.img, you need to 1st, save your original boot partition, just in case. Then flash it (using qfil) to boot_a (assuming that's your active slot). Then, don't boot the device, go directly to recovery. Once in twrp, format data. Then reboot recovery. Then flash magisk and dm_verity.
then u should be all set.
cheers

AsItLies said:
Follow this link for the 30f boot_a with twrp injected.
Let me try to clarify a bit; The engineering v35 abl is Oreo. So if you have it installed, the phone won't boot, unless your OS is Oreo (which it isn't).
So the purpose of having that abl isn't to boot the phone, it's only to be used for things like 'fastboot oem unlock' or 'fastboot flash abl_a abl_original_a.img'
it's not to boot the phone. And yes, absolutely it's a part of the boot process abl stands for 'android boot loader'.
So to make use of that v35 eng abl (after you've unlocked the boot loader), would be to flash it to the inactive slot on the phone (most people that would be abl_b). That way, you can use twrp to switch slots, use fastboot, then switch back to the active slot.
To use that proved boot_twrp_a.img, you need to 1st, save your original boot partition, just in case. Then flash it (using qfil) to boot_a (assuming that's your active slot). Then, don't boot the device, go directly to recovery. Once in twrp, format data. Then reboot recovery. Then flash magisk and dm_verity.
then u should be all set.
cheers
Click to expand...
Click to collapse
Thanks for the TWRP image, i'm gonna flash it after weekend, when i'll have acces to the phone and will report back
One more question here though, are fastboot flashable files also flashable via qfil ?

Scorcerer said:
Thanks for the TWRP image, i'm gonna flash it after weekend, when i'll have acces to the phone and will report back
One more question here though, are fastboot flashable files also flashable via qfil ?
Click to expand...
Click to collapse
Yes, absolutely. With qfil you can pretty much flash anything to any partition. That's why it's wise to be very very cautious, you could flash the wrong image to a partition, it won't stop you, and it could be too big of an image for that partition but qfil will keep writing it and write over the neighboring partition(s)!

Alright,
I went in and flashed v35 eng abl via qfill into abl_a. That gave me fasboot, which i used to do:
fastboot flash boot_b boot-twrp-30f_a.img (the twrp image i've got from you)
and
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
Then, i switched over to b slot, and rebooted straight to recovery.
In TWRP, i wiped data with formatting it, rebooted to recovery again (didn't got asked for password, i think that's a good thing), then installed magisk.zip via sideload (didn't have it on sd card) and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip afterwards.
I still have 2 problems though:
1. I can't mount vendor - in the log i'm getting "Failed to mount /vendor" (unknown error 150)
2. If i try to boot to system it loops over, i have to wait till it switches over to a slot, which gives me fastboot back, which i'm using to boot to recovery on slot B.
Should i just YOLO it and try to install Lineage directly from here (as i have TWRP)? That's my end goal...
EDIT:
I just noticed by DDing off the vendor_a it's reeeeeally different form vendor_b, and i'm considering copying stuff over, especially since i already did KDZ couple of times, so i'm not afraid of starting over.
EDIT: this let me mount /vendor finally, but boot to OS still loops.

Scorcerer said:
Alright,
I went in and flashed v35 eng abl via qfill into abl_a. That gave me fasboot, which i used to do:
fastboot flash boot_b boot-twrp-30f_a.img (the twrp image i've got from you)
and
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
Then, i switched over to b slot, and rebooted straight to recovery.
In TWRP, i wiped data with formatting it, rebooted to recovery again (didn't got asked for password, i think that's a good thing), then installed magisk.zip via sideload (didn't have it on sd card) and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip afterwards.
I still have 2 problems though:
1. I can't mount vendor - in the log i'm getting "Failed to mount /vendor" (unknown error 150)
2. If i try to boot to system it loops over, i have to wait till it switches over to a slot, which gives me fastboot back, which i'm using to boot to recovery on slot B.
Should i just YOLO it and try to install Lineage directly from here (as i have TWRP)? That's my end goal...
EDIT:
I just noticed by DDing off the vendor_a it's reeeeeally different form vendor_b, and i'm considering copying stuff over, especially since i already did KDZ couple of times, so i'm not afraid of starting over.
EDIT: this let me mount /vendor finally, but boot to OS still loops.
Click to expand...
Click to collapse
First thing I see is that you flashed, assuming what you typed above is exactly what you did, vbmeta wrong.
it should be fastboot --disa... --disa... flash vbmeta_b vbmeta_blank.img
The 1st parameter, after 'flash' should be the partition you want to flash to. Then, after that, the image you want to flash to it.
2nd, just ignore the 'can't mount vendor' in the output of when you zip install magisk or dm_verity, it's irrelevant.
So why is it bootlooping when trying to get to system? Possibly the incorrect vbmeta command? Or maybe you didn't format data? (for format, you have to type in 'yes'). Possibly it's not the right image for the os? It is, beyond doubt, 30f that you flashed?
cheers

AsItLies said:
First thing I see is that you flashed, assuming what you typed above is exactly what you did, vbmeta wrong.
it should be fastboot --disa... --disa... flash vbmeta_b vbmeta_blank.img
The 1st parameter, after 'flash' should be the partition you want to flash to. Then, after that, the image you want to flash to it.
Click to expand...
Click to collapse
But that's what i did - i didn't change the command in my command and i copy-pasted it straight from command line and it says vbmeta_b everywhere...
AsItLies said:
2nd, just ignore the 'can't mount vendor' in the output of when you zip install magisk or dm_verity, it's irrelevant.
So why is it bootlooping when trying to get to system? Possibly the incorrect vbmeta command? Or maybe you didn't format data? (for format, you have to type in 'yes'). Possibly it's not the right image for the os? It is, beyond doubt, 30f that you flashed?
cheers
Click to expand...
Click to collapse
Yup, i didn't change name of the boot image you provided so i won't make any mistake here. Also, i noticed that after i restored from KDZ it forced me to grant access to internet and downloaded some kind of patches - can it be that those affected the booting sequence somehow and i should just take clean dump of abl_b for example so that it can be patched properly?
Oh, just now it occured to me, i can basically take two dumps, one after kdz restore and the other after booting it, then compare them with md5 and i'll know if it actually does something to them...
EDIT: one more question, is KDZ restoring both slots properly? or only the currently active one?

Scorcerer said:
But that's what i did - i didn't change the command in my command and i copy-pasted it straight from command line and it says vbmeta_b everywhere...
Yup, i didn't change name of the boot image you provided so i won't make any mistake here. Also, i noticed that after i restored from KDZ it forced me to grant access to internet and downloaded some kind of patches - can it be that those affected the booting sequence somehow and i should just take clean dump of abl_b for example so that it can be patched properly?
Oh, just now it occured to me, i can basically take two dumps, one after kdz restore and the other after booting it, then compare them with md5 and i'll know if it actually does something to them...
EDIT: one more question, is KDZ restoring both slots properly? or only the currently active one?
Click to expand...
Click to collapse
hmmmm, confusing. So u speak of clean dump abl_b so it can be patched... but we never patch abl (a or b).
and no, the 'downloaded some kind of patches' are just updates to their specific apps, it's not making any change to 'system'.
when using lgup, you should first use Part D/L and choose all partitions (you can clearly see it's doing both a & b by the list). Also, if doing a 'refurbish', it should be updating both slots. Only 'upgrade' would do one side and then switch to that side.
cheers

Okay, so, step-by step, i'll try it once again and will also be taking notes meanwhile
First, i restored from KDZ by refurbishing V409N30f_00_LGU_KR_OP_0126.kdz to be exact.
Just now i flashed eng35 into abl_a which got me into fastboot no problem - the fastboot screens says SECURE BOOT is "yes" and DEVICE STATE "unlocked" which seems okay i guess...
Flashing the TWRP image you provided with
fastboot flash boot_b boot-twrp-30f_a.img
I intend to leave abl_a with fastboot for the future and so i plan to boot from b side
Now the vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
went in just fine.
Reboothing to recovery - set the b slot to be active:
fastboot set_active b
rebooting form the phone buttons directly into recovery...Got TWRP 3.3.1-0 - asks for password, i have to cancel it obviously. Swiping to allow modifications and going directly to Wipe->Format Data->yes - works and done, but complains about /vendor and /data/media/TWRP/.twrps.
Going back a bit and rebooting TWRP to recovery again - This time it doesn't ask me for password so i think i got rid of the encryption.
Flashing Magisk-v22-0.zip from their webpage, i'm clicking on add more zips and adding Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip as well, clicking on reboot system aaaaand bootloop

Okay good, making progress for sure.when I get back to my computer I'll post a link to the magisk and DM verity I use that I know will work. Not positive that those are the problem, but everything else seems to be exactly what you should be doing.

Scorcerer said:
Okay, so, step-by step, i'll try it once again and will also be taking notes meanwhile
First, i restored from KDZ by refurbishing V409N30f_00_LGU_KR_OP_0126.kdz to be exact.
Just now i flashed eng35 into abl_a which got me into fastboot no problem - the fastboot screens says SECURE BOOT is "yes" and DEVICE STATE "unlocked" which seems okay i guess...
Flashing the TWRP image you provided with
fastboot flash boot_b boot-twrp-30f_a.img
I intend to leave abl_a with fastboot for the future and so i plan to boot from b side
Now the vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
went in just fine.
Reboothing to recovery - set the b slot to be active:
fastboot set_active b
rebooting form the phone buttons directly into recovery...Got TWRP 3.3.1-0 - asks for password, i have to cancel it obviously. Swiping to allow modifications and going directly to Wipe->Format Data->yes - works and done, but complains about /vendor and /data/media/TWRP/.twrps.
Going back a bit and rebooting TWRP to recovery again - This time it doesn't ask me for password so i think i got rid of the encryption.
Flashing Magisk-v22-0.zip from their webpage, i'm clicking on add more zips and adding Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip as well, clicking on reboot system aaaaand bootloop
Click to expand...
Click to collapse
check this folder for the version of Magiisk I know works. Don't remember why, but have read the latest version of Magisk is a problem somehow. Pretty sure if you follow the steps as u did above, with this magisk, it will work.
cheers

Hiho, thanks for sticking with me.
I did everything the same except for using the Magisk you provided, and when i finally got to it, it bootlooped all the same
I tried to flash stuff in different order and stuff, but accomplished nothing.
And then I remembered i read somewhere that the OTA only does update one slot at a time, so i thought maybe Refurbish behaves the same and flashes the other slot (in my case it'd be A since i'm trying TWRP and stuff on B)
I started comparing partitions, and almost all of them were the same, except:
515cddf67500d0be189f6fc386bad7c7 /dev/block/by-name/OP_a
7fe5ca2a051d6dbb9ef191fbee0af98c /dev/block/by-name/OP_b
a4b4bbed1d0a0aa668d76558a9d10fb4 /dev/block/by-name/abl_a
4c47ecd7254de2dd84f88dbc3e31ccc2 /dev/block/by-name/abl_b
65c4413067309174d839b98b3c7eff0e /dev/block/by-name/laf_a
e7e47f8e1e05f21cf06c638bf537be67 /dev/block/by-name/laf_b
c62e2c813eeaba8682bb7dd5e26ffa8b /dev/block/by-name/oem_a
65b0e730e47fd0017c11852917ef1d2b /dev/block/by-name/oem_b
dd90de59c1b08c949326d1625a8e4d55 /dev/block/by-name/system_a
d192b99fd2cc8a48dd3f106d9f0f8233 /dev/block/by-name/system_b
Obviously abl_a is different since i installed v35 eng to it, but the rest should be the same, right?
Since they're not, can i just dd from a to be and be done with it? A slot always booted fine, but since I'm installing eng into it I never tried to do twrp and stuff there...

Aaaand it works
So the trick was just to make sure that the proper OS is actually here, and then, well, everything works like a charm i guess I used newer magisk, and so far everything looks okay
Now i'm gonna put in Lineage, but this should be easy
This also means that Refubish doesn't flash everything as we thought it's supposed to be

Scorcerer said:
Aaaand it works
So the trick was just to make sure that the proper OS is actually here, and then, well, everything works like a charm i guess I used newer magisk, and so far everything looks okay
Now i'm gonna put in Lineage, but this should be easy
This also means that Refubish doesn't flash everything as we thought it's supposed to be
Click to expand...
Click to collapse
yeah the only one I trust to flash everything would be part D/L. When doing it, you select ea individual partition, and they are all listed, both a and b slots.
The purpose of the 'dual' slots (and no recovery partition any longer) is to update 1 slot at a time, while the other slot is the older OS version. That's the way OTA's are suppose to happen. But if you use LGUP and do a Part D/L, then both sides have the same OS.
it's confusing. Good u got it working!
cheers

Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.

sptw said:
Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.
Click to expand...
Click to collapse
If you want to stay on Pie, your situation is easier, you can just follow the guide to unlock and then use fastboot to boot twrp, use 'ramdisk inject' to inject the twrp image. Reboot to recovery, format data, reboot recovery again, flash magisk and dm_verity.
cheers

sptw said:
Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.
Click to expand...
Click to collapse
Didn't realize it was available, but follow for the 20n boot+magisk boot image. This Link
I'd suggest using qfil to (first backup your original boot partition) to flash this to your active boot partition. Then exit edl mode and use the key combo to go directly to recovery (now twrp). Format data, then reboot recovery, then flash magisk and dm_verity. All set!
cheers

Hi AsltLies,
Thanks for both of informations. Let me try to explain a bit more. I am able to root the device with magisk. I made a boot_a patched using magisk apk and inject diretly into boot_a using qfill. It works like a charm. No problem at all.
The problem is that there are something wrong with viper4android using magisk. I want the older 2.3.4 driver and it has a kind of problem using convolver and system inject. User app method does not work.
I own a LG V20 with viper4android on it, and i can confirm that there are something wrong with viper on LG V40. My LG V20 is not a Bang & Olufsen and not even Merodian tune. Maybe the problem lies on this meridian audio tuned on LG V40. Chances are great about that. Devices sound differents and i have to accept this. But...
I would like to try the method that i used to root the LGV20 : Supersu and not magisk. I dont care about safety net. I dont use it. And a second problem with magisk : two apk refuse to open with magisk root method. I know they work with rooted devices but using rootcloack on xposed and xposed is very hard to get to work on magisk ( very limited )
So, i would like to use SuperSu method and not magisk to inject the old 2.3.4 viper4android directly on TWRP. I know how i can do it to works using the original drive and apk from the original devs. ( I dont like the new version 2.7 )
So, sorry for the long explanation, but do you know how i can install TWRP without to use magisk? ( That [TWRP] LG V40 / Judypn does not work. I only get bootloop ).
Thanks again.
In time: Maybe i'm doing something wrong to install TWRP. Do i need to instal it in both slots ( a and b? Do i need to access TWRP using the slot that is not active and make the zips install from there and not from the active slot? It's a kind of confusion for me. I already read a lot about it, but i'm still in doubt how it really works. I'm not interested to use another ROM, just stock.

sptw said:
Hi AsltLies,
Thanks for both of informations. Let me try to explain a bit more. I am able to root the device with magisk. I made a boot_a patched using magisk apk and inject diretly into boot_a using qfill. It works like a charm. No problem at all.
The problem is that there are something wrong with viper4android using magisk. I want the older 2.3.4 driver and it has a kind of problem using convolver and system inject. User app method does not work.
I own a LG V20 with viper4android on it, and i can confirm that there are something wrong with viper on LG V40. My LG V20 is not a Bang & Olufsen and not even Merodian tune. Maybe the problem lies on this meridian audio tuned on LG V40. Chances are great about that. Devices sound differents and i have to accept this. But...
I would like to try the method that i used to root the LGV20 : Supersu and not magisk. I dont care about safety net. I dont use it. And a second problem with magisk : two apk refuse to open with magisk root method. I know they work with rooted devices but using rootcloack on xposed and xposed is very hard to get to work on magisk ( very limited )
So, i would like to use SuperSu method and not magisk to inject the old 2.3.4 viper4android directly on TWRP. I know how i can do it to works using the original drive and apk from the original devs. ( I dont like the new version 2.7 )
So, sorry for the long explanation, but do you know how i can install TWRP without to use magisk? ( That [TWRP] LG V40 / Judypn does not work. I only get bootloop ).
Thanks again.
In time: Maybe i'm doing something wrong to install TWRP. Do i need to instal it in both slots ( a and b? Do i need to access TWRP using the slot that is not active and make the zips install from there and not from the active slot? It's a kind of confusion for me. I already read a lot about it, but i'm still in doubt how it really works. I'm not interested to use another ROM, just stock.
Click to expand...
Click to collapse
Well... i got to install TWRP in slot a. No more encrypt data. Install Selinux ( SuperSu ) too. Reboot to recovery and no more ask for password, so it works. Data continue to be there. TWRP see the Selinux root, but it always return to TWRP. It does not matter reboot to system, recovery and power off, it always return to TWRP. So, i go to the EDL mode, install v35eng on abl_a, install ablpiestock again to abl_a and...TWRP again...I cant boot.

sptw said:
Well... i got to install TWRP in slot a. No more encrypt data. Install Selinux ( SuperSu ) too. Reboot to recovery and no more ask for password, so it works. Data continue to be there. TWRP see the Selinux root, but it always return to TWRP. It does not matter reboot to system, recovery and power off, it always return to TWRP. So, i go to the EDL mode, install v35eng on abl_a, install ablpiestock again to abl_a and...TWRP again...I cant boot.
Click to expand...
Click to collapse
Hmmm, not sure yet what's going on but I updated the link above in prev post, it now points to a gdrive folder called 20n.
There's a new boot image in it that has just twrp injected, no magisk. Try that and see if it doesn't help. Be sure though of which is your active slot. The way a treble enabled device does ota updates is it will update the inactive slot, with the new version, switch slots, and then boots the new version. What that means is the OLD version is now the inactive slot.
So if u are on 20n, be sure to flash the new image to that slot, not the old one. If need be, use twrp or fastboot (getvar all) will tell you which slot is active.
cheers

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?

Question [Solved] Unable to install EU ROM :/

Hi everyone, and a happy new year
I need some light please, i don't understand what i'm doing wrong :/
To follow this post, i can't install EU ROM anymore (via TWRP) and i don't know why...
1) i flash the EEA Global via MiFlashTool, all ok
2) i make sure to unlock bootloader, all ok
3) i flash TWRP (official 3.6), all ok
Finally i want to flash 12.5.20.0, or 12.5.17.0 of EU ROM via TWRP/install, the process end up nicelly, no error so reboot, now everytime /data is lost, so it only boot on twrp and nothing is here anymore, need to go back at 1)
That is so frustrating :/
Can anyone enlight me please ?

did you format data after flashing 12.5.20.0

marcel112 said:
did you format data after flashing 12.5.20.0
Click to expand...
Click to collapse
nope, i need to ?
(if i format data, then i'll need to reflash the rom, right ?)

Only fastboot Version available right now bro. Already using it.

If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only

marcel112 said:
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
Click to expand...
Click to collapse
Thanks both of you !
Ok, but when i see files like 12.5.20.0 with a twrp flashing procedure labelled Mi11 Ultra, that let me think i can do it that way, it's misleading, at least :/
So, i flashed the latest 12.6 xiaomi eu rom and it worked
New problem, i then try to use twrp to flash magisk, i do fastboot boot twrp.img and then, /data lost again, so impossible to flash magisk :/
I tried both 3.6 official and 3.5.1 unofficial
p.s.: never set security pin/pass or whatever atm, so it's not a problem with the password

why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line

marcel112 said:
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
Click to expand...
Click to collapse
Oh my god, i totally forgot this method
Thank you very much, seems to work !
Solved