Database Info

Rooting for March Update?

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

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

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

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

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

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

Won't let me simend the link

rob420p,
Please provide links.

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

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

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

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

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

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

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

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

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

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

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

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

Root on Android 10 Stable

I need help. I was rooted with TWRP on Android Pie. I can't figure out how to flash or boot TWRP on Android 10 stable. Can someone please advise on the procedure to get TWRP and root with Magisk. Thank you!

Android 10 very friendly with root
There is an unofficial twrp for Android Q . Download it and temporarily Mount that image and install root.zip. after completing the installation of magiks . Install offical twrp zip to your phone. Done! Now your phone turns on with root.

As the previous response mentioned, unofficial TWRP version -70 just came out yesterday, fixing the "fastboot boot" command. You can now root Android 10 the same as you (probably) did with Pie: fastboot boot twrp.img, then flash twrp installer, and flash Magisk.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322

redpoint73 said:
As the previous response mentioned, unofficial TWRP version -70 just came out yesterday, fixing the "fastboot boot" command. You can now root Android 10 the same as you (probably) did with Pie: fastboot boot twrp.img, then flash twrp installer, and flash Magisk.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
I was able to boot into TWRP... What is the command to flash the Installer file?

akinkoff85 said:
I was able to boot into TWRP... What is the command to flash the Installer file?
Click to expand...
Click to collapse
?????
After you boot to TWRP, you enter your password to decrypt.
You then select the button that says install and navigate to the TWRP_install.zip file.
You will then select additional zip files, one of those being the Magisk.zip.
If you don't install Magisk after TWRP, you will get a bootloop/softbrick.
TWRP requires Magisk.

tech_head said:
?????
After you boot to TWRP, you enter your password to decrypt.
You then select the button that says install and navigate to the TWRP_install.zip file.
You will then select additional zip files, one of those being the Magisk.zip.
If you don't install Magisk after TWRP, you will get a bootloop/softbrick.
TWRP requires Magisk.
Click to expand...
Click to collapse
I installed twrp only and it booted up fine

All done I figured it out and got Root

Maybe it's changed recently, but Magisk was a requirement.
But if you have TWRP why not root?

redpoint73 said:
As the previous response mentioned, unofficial TWRP version -70 just came out yesterday, fixing the "fastboot boot" command. You can now root Android 10 the same as you (probably) did with Pie: fastboot boot twrp.img, then flash twrp installer, and flash Magisk.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Thank you. I was struggling for a few days on Android 10 stable, wondering why I couldn't flash root, but eventually found that fastboot boot command wasnt working on 10. So I waited a few days in hopes there would be a way. So just wanted to thank you for this post. Going to try soon. Appreciate it.
---------- Post added at 03:47 AM ---------- Previous post was at 03:46 AM ----------
tech_head said:
Maybe it's changed recently, but Magisk was a requirement.
But if you have TWRP why not root?
Click to expand...
Click to collapse
Good point.

wiswis said:
I installed twrp only and it booted up fine
Click to expand...
Click to collapse
In seems to vary for folks (exact variables not clear), but in many circumstances, flashing TWRP without Magisk will result in no longer booting to OS.

Flashed another rom with twrp and no magisk and it booted up fine. I formatted my phone before the install, maybe that has to do with it

i had magisk running nicely since i installed debloater module ,,,after that my phone gone to bootloop.......now when i uninstall magisk then it turns on normally but if i install magisk then it bootloops again ...any fix for this ?

Oneplus 6 - twrp boot not working

Hello,
I have bricked and unbricked my op6 with msm download tool.
Now i tried to install lineage and followed the instructions.
I tried following:
- with twrp standard
- with blu
- with twrp in Boot_a and b
In all cases the reboot lead to a dark screen.
Any idea?
BR Martin

You will have to msm flash

anupsnair said:
You will have to msm flash
Click to expand...
Click to collapse
That is what i did - twice already... Still no Boot into twrp...

martinforum said:
Hello,
I have bricked and unbricked my op6 with msm download tool.
Now i tried to install lineage and followed the instructions.
I tried following:
- with twrp standard
- with blu
- with twrp in Boot_a and b
In all cases the reboot lead to a dark screen.
Any idea?
BR Martin
Click to expand...
Click to collapse
From what firmware are you from?

Hitman478™ said:
From what firmware are you from?
Click to expand...
Click to collapse
MSM included OOS 5.1.5
Update required to which version to make twrp bootable?

martinforum said:
MSM included OOS 5.1.5
Update required to which version to make twrp bootable?
Click to expand...
Click to collapse
Thank you. Yes this was the reason why! I can boot in twrp again.
There are different howto's out there. What is the right order to install following packages - do I have to reboot after each package?
Twrp
Lineage rom
Openapps Pico
Su

I did not fully understand the problem but i can see one thing: oos 5.1.5 as a base firmware for lineage is not correct because oreo firmware is not supported, so in order
if you want only TWRP
Update to the latest firmware (oos 10)
follow this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-installing-bluspark-twrp-magisk-t3997765
If you want lineage 16/17
Update to the latest open beta pie (28)
reboot to fastboot
download TWRP img and zip (9.101)
open windows prompt and type "fastboot boot twrp.img" (make sure to insert the correct name file instead of twrp.img and check if is .img and not the .zip)
device will automatic reboots in TWRP
now from here flash the TWRP .zip file and reboot to recovery to make sure it's there
now you can update recovery to 9.107 if you want (and it's highly reccomended) by flashing the proper 9.107 .zip
don't forget to use blue_spark TWRP
Now everytime you flash a rom you need to flash TWRP after that otherwise it will not stay there
hope it's all clear and that i've not forgot anything

Hitman478™ said:
I did not fully understand the problem but i can see one thing: oos 5.1.5 as a base firmware for lineage is not correct because oreo firmware is not supported, so in order
if you want only TWRP
Update to the latest firmware (oos 10)
follow this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-installing-bluspark-twrp-magisk-t3997765
If you want lineage 16/17
Update to the latest open beta pie (28)
reboot to fastboot
download TWRP img and zip (9.101)
open windows prompt and type "fastboot boot twrp.img" (make sure to insert the correct name file instead of twrp.img and check if is .img and not the .zip)
device will automatic reboots in TWRP
now from here flash the TWRP .zip file and reboot to recovery to make sure it's there
now you can update recovery to 9.107 if you want (and it's highly reccomended) by flashing the proper 9.107 .zip
don't forget to use blue_spark TWRP
Now everytime you flash a rom you need to flash TWRP after that otherwise it will not stay there
hope it's all clear and that i've not forgot anything
Click to expand...
Click to collapse
Thank you. Blue_spark twrp is working.
Now i have installed lineage and without reboot oppengapps pico but I do get an error message.
To ensure twrp, i reinstalled as you said bstwrp. But the reboot brings me back to a black screen.
Any tips for the right order to install and reboot?

[Guide] TWRP+MAGISK ROOT Installed on OOS 10.3.5

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Why is flashing Patched boot img causing bootloop?

I have a OnePlus 7 Pro on Android 11, OOS 11.0.0.2. The bootloader is unlocked. The devices runs absolutely fine unrooted. I have been wanting to root for quite some time. I patched the boot.img file of the ROM using latest Magisk Canary (app-debug.apk) from the GitHub repository. When I flash the .img through ADB, it is flashed successfully.
But when I reboot the phone, the phone is stuck on OnePlus' 'Two circling dots animation' (bootloop) and never starts. These are the commands that I enter one-by-one in CMD prompt on my laptop:
adb devices
adb reboot bootloader
fastboot flash boot "D:\Downloads\boot_patched.img"
fastboot reboot
Click to expand...
Click to collapse
So, to get out of this issue, I flash the stock boot image using similar commands. Then the phone boots successfully, but, of course, it is unrooted.
I even tried these commands, still no luck.
fastboot flash boot_a "D:\Downloads\boot_patched.img"
fastboot flash boot_b "D:\Downloads\boot_patched.img"
Click to expand...
Click to collapse
I also tried patching using the stable Magisk release (Magisk v23.0), still nothing.
What am I doing wrong?

iamMG said:
I have a OnePlus 7 Pro on Android 11, OOS 11.0.0.2. The bootloader is unlocked. The devices runs absolutely fine unrooted. I have been wanting to root for quite some time. I patched the boot.img file of the ROM using latest Magisk Canary (app-debug.apk) from the GitHub repository. When I flash the .img through ADB, it is flashed successfully.
But when I reboot the phone, the phone is stuck on OnePlus' 'Two circling dots animation' (bootloop) and never starts. These are the commands that I enter one-by-one in CMD prompt on my laptop:
So, to get out of this issue, I flash the stock boot image using similar commands. Then the phone boots successfully, but, of course, it is unrooted.
I even tried these commands, still no luck.
I also tried patching using the stable Magisk release (Magisk v23.0), still nothing.
What am I doing wrong?
Click to expand...
Click to collapse
I had an issue before, with the Canary APK. Try installing the v23 app and repatch your boot IMG with it. Worth a shot.

I tried, again, with v23. Same bootloop occuring.

Do you perhaps have the magisk app installed, I know of modules causing these sort of bootloop issues.

@soka said:
Do you perhaps have the magisk app installed, I know of modules causing these sort of bootloop issues.
Click to expand...
Click to collapse
Yes, the Magisk app is installed, but I don't have any modules installed. I don't even have root, how will I install a module?

iamMG said:
Yes, the Magisk app is installed, but I don't have any modules installed. I don't even have root, how will I install a module?
Click to expand...
Click to collapse
True, sorry just trying to help you narrow it down.

@soka said:
True, sorry just trying to help you narrow it down.
Click to expand...
Click to collapse
No problem. I just need to know how to fix the issue. Else, I would have to flash OOS 10.

iamMG said:
No problem. I just need to know how to fix the issue. Else, I would have to flash OOS 10.
Click to expand...
Click to collapse
This OnePlus 8T thread https://forum.xda-developers.com/t/...in-eu-us-kb2000-kb2001-kb2003-kb2005.4178675/ says to boot, not flash, the patched boot image. In other words, use fastboot boot "D:\Downloads\boot_patched.img" and then do a direct install in Magisk.
That's the process I used and it worked perfectly.
Note: my phone is an 8T.

BillGoss said:
This OnePlus 8T thread https://forum.xda-developers.com/t/...in-eu-us-kb2000-kb2001-kb2003-kb2005.4178675/ says to boot, not flash, the patched boot image. In other words, use fastboot boot "D:\Downloads\boot_patched.img" and then do a direct install in Magisk.
That's the process I used and it worked perfectly.
Note: my phone is an 8T.
Click to expand...
Click to collapse
Thanks, I will try this method and report back.
Btw, after you booted using this method, for how much time did the boot animation showed up (the two circling white dots around bigger red dot)?
Edit: I tried this method. No luck. The boot animation goes on 5-10 minutes, at which point I reboot into bootloader and flash the stock boot image.

Anyway, I ended up downgrading to OxygenOS 10.3.8.

Starting to give up as well... Never had any issues before (on Android 10) to flash root on O7Pro, but ever since Android 11, I keep having "boot loop" issues. Aka, the boot logo keeps loading and never boots into the OS. Only works again if I re-patch the original boot.img file.
This is starting to get.. VERY, VERY annoying. Why isn't there any proper method of getting this to work?

Not sure which boot.img you using.
But I face similar problem a week ago, and i fix that by using another .img then all fine.
I download from:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com

i'm running oxygen os 11.0.2.1 with root access. i'm running with the latest version of magisk, v.23.0. i haven't had any problems with android 11 and root. my suggestion is to make sure that you're patching the correct boot image. when an update is available, i download the full update, copy the zip to a computer, and then use payload dumper to extract the boot image. that's the boot image i use for patching.

hkdoublecat said:
Not sure which boot.img you using.
But I face similar problem a week ago, and i fix that by using another .img then all fine.
I download from:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Click to expand...
Click to collapse
I am too afraid to upgrade to OOS 11, only to find out root doesn't work for me. The restore function of this unofficial TWRP version is buggy so can't really depend on it to restore OOS 10.3.8. So, I have decided to stay on the latter until Team Recovery releases a proper update for Android 11.

altwu said:
i'm running oxygen os 11.0.2.1 with root access. i'm running with the latest version of magisk, v.23.0. i haven't had any problems with android 11 and root. my suggestion is to make sure that you're patching the correct boot image. when an update is available, i download the full update, copy the zip to a computer, and then use payload dumper to extract the boot image. that's the boot image i use for patching.
Click to expand...
Click to collapse
Hi i am just wondering if you can upload the patch image and the original boot image of 11.0.2.1GM21AA thanks in advance.

Mangtas_666 said:
Hi i am just wondering if you can upload the patch image and the original boot image of 11.0.2.1GM21AA thanks in advance.
Click to expand...
Click to collapse
attached are the original and magisk patch boot images from my phone running 11.0.2.1 GM21AA.
boot_11021.img is the original boot image that i extracted with payload dumper.
magisk_patched-23000_fQNMs.img is the magisk patched boot image. it was patched with magisk v23.0.

altwu said:
attached are the original and magisk patch boot images from my phone running 11.0.2.1 GM21AA.
boot_11021.img is the original boot image that i extracted with payload dumper.
magisk_patched-23000_fQNMs.img is the magisk patched boot image. it was patched with magisk v23.0.
Click to expand...
Click to collapse
i tried attaching the images to the post but they're not showing up. i tried editing the post to attach the images, but they're still not showing up. sorry.