hi @ante0
after a week of using oreo,i've downgraded to C185B187.
oreo has some issues like draining battery,weird "undetected root" error after installing busybox in /system/xbin (u have to make a new folder in system first,then install busybox) and over heating even when the phone is in charge and fully charged already...
now i need those root files that u gave me before for b182 !:laugh:
Need a boot image (and can u explain what this image does? )
(also how to make one )
and SuperSU-v2.82-SR5
SuperSU 2.82 SR5 if you decrypt: https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
SuperSU 2.82 SR5 if you stay encrypted: https://mega.nz/#!ZTBQXZra!JHUocH9oMEApULxfLYm9VO5UPhjHNMGLymkXDY_ihhI
Boot MHA-L29C185B187: https://mega.nz/#!IL4gxCaL!_O0B1rm-eys5Ta8CnD5BfXsyLTGM3RXdtZ09v7kWUk4
Or you could just make a backup of your current boot image using TWRP.
If you want to do it yourself in the future:
Download your current firmware from http://pro-teammt.ru/firmware-database/
Extract update.app from downloaded update.zip, download Huawei Update Extractor (https://forum.xda-developers.com/showthread.php?t=2433454)
Open update.app in Huawei Update Extractor, rightclick on what you want to extract and select "Extract Selected".
This image can only be flashed using fastboot (at least when I extract it). You can unpack and repack using Android Image Kitchen to make a TWRP flashable image.
What boot is... It's the ramdisk and kernel.
Read more here: https://www.linux.com/learn/kernel-newbie-corner-initrd-and-initramfs-whats
Basically it tells your phone how to boot xD
ante0 said:
SuperSU 2.82 SR5 if you decrypt: https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
SuperSU 2.82 SR5 if you stay encrypted: https://mega.nz/#!ZTBQXZra!JHUocH9oMEApULxfLYm9VO5UPhjHNMGLymkXDY_ihhI
Boot MHA-L29C185B187: https://mega.nz/#!IL4gxCaL!_O0B1rm-eys5Ta8CnD5BfXsyLTGM3RXdtZ09v7kWUk4
Or you could just make a backup of your current boot image using TWRP.
If you want to do it yourself in the future:
Download your current firmware from http://pro-teammt.ru/firmware-database/
Extract update.app from downloaded update.zip, download Huawei Update Extractor (https://forum.xda-developers.com/showthread.php?t=2433454)
Open update.app in Huawei Update Extractor, rightclick on what you want to extract and select "Extract Selected".
This image can only be flashed using fastboot (at least when I extract it). You can unpack and repack using Android Image Kitchen to make a TWRP flashable image.
What boot is... It's the ramdisk and kernel.
Read more here: https://www.linux.com/learn/kernel-newbie-corner-initrd-and-initramfs-whats
Basically it tells your phone how to boot xD
Click to expand...
Click to collapse
so u did not modify this boot image,am i right ?
i thought u modify this boot images to make the SuperSu works -.-
and did u modify SuperSu package ?
ezraiil1 said:
so u did not modify this boot image,am i right ?
i thought u modify this boot images to make the SuperSu works -.-
and did u modify SuperSu package ?
Click to expand...
Click to collapse
It's just stock boot. SuperSU works fine with it when you're on B182+.
It's only useful if you want to flash back stock boot, to maybe switch to Magisk or if SuperSU doesn't want to update.
I did modify the SuperSU "for_encrypted", I just changed "KEEPENCRYPTED=false" to "true". It just tells the installer to not remove the encryption tag so it stays encrypted.
Edit: one reason to modify boot is to "pre-root", but it's not needed for Mate 9. Another is to remove encryption or verity manually.
If you install twrp recovery then it is very easy to install magisk manager.
just go on your twrp recovery mode
Select advanced and select install root.
Reboot your Phone .
See magisk manager install successfully.
Any help about mi cc9 magisk manager just coment here. I will be ready for replay just like you want.
.
Or Download this file and install through twrp recovery.
Latest stable magisk manager zip [flash file]
https://drive.google.com/file/d/1j6EWKPt1ZNzW7QgtILkgW5xphCzzcKNH/view?usp=drivesdk
Magisk manager apk
https://drive.google.com/file/d/1Hzvi5f2bZcUPyzWx-ETfqZanQjLCJHGq/view?usp=drivesdk
Lijlp0/02plppp000p7 lu6pppp?0lpl
Ul u?????//6000
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
eidrag said:
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
Click to expand...
Click to collapse
I need unlock BL to flash the modded boot.img?
RazrBR said:
I need unlock BL to flash the modded boot.img?
Click to expand...
Click to collapse
Yes, first unlock BL to be able to enter fastboot mode. Apply to unlock bootloader with Mi account, please follow guide on how to unlock the bootloader.
eidrag said:
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
Click to expand...
Click to collapse
Hi. Did you do these passages also on MIUI 12? Because I installed Magisk app, but it showed Ramdisk: no, and now I don't know if I should install it in recovery partition or not
there's twrp and orangefox that can be used for cc9 meitu/vela. Unlock bootloader, enable adb, flash custom recovery by fastboot. After that use custom recovery to install magisk. I'm sorry I don't use cc9 anymore since last weekend because miui12 notification and permission is too aggressive, have to restart app everytime so that can get contact info.
Alternative Option For Applying December (or any other OTA updates) without using ADB or Fastboot.
Pros:
+ No need for fastboot or ADB
+ Can be done without a PC
+ OTA is applied from within Android, using Android's normal update process
+ Retains root
+ Retains any installed Magisk Modules
Cons:
- Until Magisk is updated, requires that you fake a backup by compressing a stock boot image and renaming the resulting file.
- Only works on phones with duel partitions
- Slightly harder to do without a PC
The Pixel 4/4XL has duel partitions. This allows for an alternative option for installing OTA updates without losing root (Magisk) or wiping data. The process is outlined in the Magisk guide here: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The problem with following that guide is that since there is no TWRP for Pixel 4 / Android 10, most of us patched Magisk into a stock boot image manually, leaving us without an automatically created backup. Then, when you attempt to uninstall Magisk and restore the backup boot image, you get a message stating "No backup image found". However, it is easy to copy a stock boot image to your phone and have Magisk treat it as a backup. Magisk can then uninstall itself, you apply the OTA without restarting, reinstall Magisk by patching OTA image in the inactive partition, then reboot. After reboot you will be running the OTA version with Magisk patched in.
The process is a little easier if you have a PC, but it can be done completely on the phone itself, without any other hardware.
Here is a full process:
Requirements:
A rooted Pixel with Magisk Manager installed
A file explorer app that has a root broswer (I use Total Commander)
A text editor that can open arbriatry files (I used Quick Edit)
A tool to zip files (I used 7-Zip on a Windows PC, then transfered the file via USB, but you can do this completely without a computer)
The unpatched boot.img file that corresponds to your current build. (Get it from https://developers.google.com/android/images#coral
Create a backup image that Magisk can auto-restore
On your Android phone, open the following file: /sbin/.magisk/config
Copy the SHA1 hash (you want to copy everything after the = sign)
Download the factory image that corresponds to your current build. Extract the zip, then from the zip extract the boot.img file (Yes, there is a zip within a zip). This is easier to do on a computer, but can be done directly on the phone.
Create a new .gz archive that contains the boot.img file and nothing else. On Windows, I used 7zip for this, selecting gzip as the method, and using all of the defaults.
Rename the .gz achive to the following: 'stock_boot_<hash>.img.gz' where <hash> is the SHA1 hash that you coped from the Magisk config file.
Copy the .gz file to your phone and place it in the /data directory. The full path on your phone should be /data/stock_boot_<hash>.img.gz.
You can now follow the rest of the guide from https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md, but an abbreviated version is included
Uninstall Magisk and Apply the OTA
Launch Magisk Manager on your phone
Select "Uninstall", then choose "Restore Images". Magisk will be uninstalled and you will be back to running stock boot.
Go to Settings --> Systems --> Advanced --> System Update, then check for and apply updates. You will need to select "resume" to force the update to happen immediately. DO NOT RESTART THE PHONE. The December update can take a while. I was on the "optimizing apps" message for a good 20 - 30 minutes.
After the udpate has been installed, the screen will have the option to restart. Don't select it.
Install Magisk to the updated boot and restart
Start Magisk Manager
Select Install (we are installing Magisk, not Magisk Manager)
When prompted, choose to install to an inactive partition
Read the warning and confirm. The OTA boot image will be patched with Magisk.
Restart your phone.
You should now have the OTA update (verified by checking Settings --> About Phone --> Build number)
You should also have a new stock_boot_<hash>.img.gz file in your /data directory. Next time there is an OTA update, you can skip the first part of this and go straight to uninstalling Magisk and applying the OTA.
Thanks to reyqn and Nephiel for commenting on https://github.com/topjohnwu/Magisk/issues/1870.
Hi. What do you mean " Copy the SHA1 hash " because in /sbin/magisk/config. i don't see any file name SHA1 hash?
Sent from my Pixel 4 XL using Tapatalk
GrimEcho said:
...when you attempt to uninstall Magisk and restore the backup boot image, you get a message stating "No backup image found"...
...Create a backup image that Magisk can auto-restore
On your Android phone, open the following file: /sbin/.magisk/config
Copy the SHA1 hash (you want to copy everything after the = sign)
Download the factory image that corresponds to your current build. Extract the zip, then from the zip extract the boot.img file (Yes, there is a zip within a zip). This is easier to do on a computer, but can be done directly on the phone.
Create a new .gz archive that contains the boot.img file and nothing else. On Windows, I used 7zip for this, selecting gzip as the method, and using all of the defaults.
Rename the .gz achive to the following: 'stock_boot_<hash>.img.gz' where <hash> is the SHA1 hash that you coped from the Magisk config file.
Copy the .gz file to your phone and place it in the /data directory. The full path on your phone should be /data/stock_boot_<hash>.img.gz....
Click to expand...
Click to collapse
I think they fixed Magisk/Magisk Manager: Opened Magisk Manager ==> Tapped Uninstall ==> Tapped Restore images
Not getting this message: "No backup image found"
Appreciate the instructions to "Create a backup image that Magisk can auto-restore.":good:
---------- Post added at 11:44 AM ---------- Previous post was at 11:10 AM ----------
DinarQ8 said:
Hi. What do you mean " Copy the SHA1 hash " because in /sbin/magisk/config. i don't see any file name SHA1 hash?
Click to expand...
Click to collapse
Everything after SHA1= in sbin/.magisk/config (file) is the 'hash'.
Thanks for this guild.... I just wondering if we could use EX kernel Manager (or anything similar) to flash the stock boot.img (so everything returned to stock), then apply OTA, then use Magisk Manager to patch the inactive slot...
Although this requires another app, but we don't need to create backup specific for MM... Just a stock boot.img is needed...
Haven't tried this yet... Will try on Jan update.....
For some reason if the config file says recoverymode=true then magisk will still not find the backup image. If you change it to recoverymode=false then you can continue on with the rest of the steps. I wonder why?
StoicSage said:
For some reason if the config file says recoverymode=true then magisk will still not find the backup image. If you change it to recoverymode=false then you can continue on with the rest of the steps. I wonder why?
Click to expand...
Click to collapse
Or you can Open Magisk Manager, Tap Advanced Settings and uncheck Recovery Mode.
DinarQ8 said:
Hi. What do you mean " Copy the SHA1 hash " because in /sbin/.magisk/config. i don't see any file name SHA1 hash?
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
/sbin/.magisk/config is the name of the file. There is no extension to it, but it is a text file.
Open the file in an editor and the last line should have the SHA1 hash.
Homeboy76 said:
I think they fixed Magisk/Magisk Manager: Opened Magisk Manager ==> Tapped Uninstall ==> Tapped Restore images
Not getting this message: "No backup image found"
Appreciate the instructions to "Create a backup image that Magisk can auto-restore.":good:
---------- Post added at 11:44 AM ---------- Previous post was at 11:10 AM ----------
Everything after SHA1= in sbin/.magisk/config is the 'hash'.
Click to expand...
Click to collapse
I think it depends on what method you used to originally root the Pixel 4. If you copied over a .boot.img file to the phone, then used Magisk Manager to patch the file while you didn't have root then Magisk won't make a backup, since it doesn't have access to copy the backup /data. But if you have root when you use Magisk Manager to create a patch (via TWRP, or because root is still enabled from an in memory magisk), then it can copy the file.
lssong99 said:
Thanks for this guild.... I just wondering if we could use EX kernel Manager (or anything similar) to flash the stock boot.img (so everything returned to stock), then apply OTA, then use Magisk Manager to patch the inactive slot...
Although this requires another app, but we don't need to create backup specific for MM... Just a stock boot.img is needed...
Haven't tried this yet... Will try on Jan update.....
Click to expand...
Click to collapse
I think this would work as long as you can flash stock using Ex Kernal Manager while Magisk is still installed, and don't have to reboot. Magisk needs root access to be able to patch the OTA in the inactive slot, so if you flashed stock, then restarted, Magisk Manager couldn't access the inactive slot any longer (I think). I haven't used EX Kernal Manager though, so I'm not positive.
GrimEcho said:
I think this would work as long as you can flash stock using Ex Kernal Manager while Magisk is still installed, and don't have to reboot. Magisk needs root access to be able to patch the OTA in the inactive slot, so if you flashed stock, then restarted, Magisk Manager couldn't access the inactive slot any longer (I think). I haven't used EX Kernal Manager though, so I'm not positive.
Click to expand...
Click to collapse
O think you are absolutely right! The key is "do not reboot after flash the stock boot.img" so MM can still do the magic on patch the inactive partition. Your original idea does open a good avenue on OTA without PC.. which saves a lot of troubles......
GrimEcho said:
I think it depends on what method you used to originally root the Pixel 4. If you copied over a .boot.img file to the phone, then used Magisk Manager to patch the file while you didn't have root then Magisk won't make a backup, since it doesn't have access to copy the backup /data. But if you have root when you use Magisk Manager to create a patch (via TWRP, or because root is still enabled from an in memory magisk), then it can copy the file.
Click to expand...
Click to collapse
I did this while on the November 2019 Factory Image:
- opened MM, tapped uninstall, tapped restore images (root gone)
- downloaded December 2019 Factory Image
- extracted the boot.img
- opened MM, tapped install, tapped install, tapped patch a file, selected the December boot.img
- After, it finished patching the boot.img, there was a backup file in /data folder.
I could be wrong but I think the key to ensuring a back up file is made it to turning off Recovery Mode prior to patching the boot.img: Open MM, tap Advanced Settings, and uncheck Recovery Mode.
Amazing this worked! Thanks so much.
Just to note: I had to use QuickEdit to set the RECOVERYMODE=false unchecking the box in Magisk didn't seem to work for me.
One question, I'm now on "Security patch level: November 5, 2019". I'm pretty sure my stock boot.img was from October some time. To get the December update, should I download the latest factory image and redo the process? Therefore, everytime we want to do an OTA, we must download the latest factory image and extract the boot.img?
foaf said:
Amazing this worked! Thanks so much.
Just to note: I had to use QuickEdit to set the RECOVERYMODE=false unchecking the box in Magisk didn't seem to work for me.
One question, I'm now on "Security patch level: November 5, 2019". I'm pretty sure my stock boot.img was from October some time. To get the December update, should I download the latest factory image and redo the process? Therefore, everytime we want to do an OTA, we must download the latest factory image and extract the boot.img?
Click to expand...
Click to collapse
Short answer is yes to the factory image and extracting the boot.img every month before taking the ota. Just make sure the OTA and factory image build numbers match :good:
**UPDATE** - flashing the boot.img from the October Factory Image seems to have fixed the touch screen issue. So, now I gotta figure out why the OTA keeps failing...
I have question, I attempted this method but the update would not install... I kept getting an installation error. So, I just reinstalled Magisk from the Magisk Manager. However, when I rebooted the touch screen no longer works... So I can't unlock my phone.
What is the easiest way to fix this? I was on the original factory image (October) and I bought the phone directly from Google (non-carrier version).
I've attempted to just flash-all using the Dec factory image from fastboot (using key-combo to get into fastboot) but I get the flash in fastbootd error. I'm assuming flash-all from the correct October factory image will fix me up, but I honestly can't remember exactly which October factory image came with the device. Any help would be greatly appreciated.
ihuntinde said:
**UPDATE** - flashing the boot.img from the October Factory Image seems to have fixed the touch screen issue. So, now I gotta figure out why the OTA keeps failing...
I have question, I attempted this method but the update would not install... I kept getting an installation error. So, I just reinstalled Magisk from the Magisk Manager. However, when I rebooted the touch screen no longer works... So I can't unlock my phone.
What is the easiest way to fix this? I was on the original factory image (October) and I bought the phone directly from Google (non-carrier version).
I've attempted to just flash-all using the Dec factory image from fastboot (using key-combo to get into fastboot) but I get the flash in fastbootd error. I'm assuming flash-all from the correct October factory image will fix me up, but I honestly can't remember exactly which October factory image came with the device. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Can't you flash the December image but do it manually? Pain in the ass but should get it done.
p70shooter said:
Can't you flash the December image but do it manually? Pain in the ass but should get it done.
Click to expand...
Click to collapse
I tried to flash-all the December image but it kept failing with flash with fastbootd. Even though I have the most up to date platform-tools.
I believe I know what I did though... I didn't read the instructions clearly and i used the december boot image when i uninstalled magisk.... I'm attempting it again doing the instructions exactly as it states... fingers crossed...
foaf said:
Amazing this worked! Thanks so much.
Just to note: I had to use QuickEdit to set the RECOVERYMODE=false unchecking the box in Magisk didn't seem to work for me.
One question, I'm now on "Security patch level: November 5, 2019". I'm pretty sure my stock boot.img was from October some time. To get the December update, should I download the latest factory image and redo the process? Therefore, everytime we want to do an OTA, we must download the latest factory image and extract the boot.img?
Click to expand...
Click to collapse
If you are willing to wait for the OTA updates then you don't need to keep doing the download/extract/zip process. After the first OTA update, when you use Magisk to root patch the inactive partition with the installed OTA, Magisk will create a new backup. So next time there is an OTA, you can just uninstall Magisk and restore. It should now find the backup.
ihuntinde said:
I tried to flash-all the December image but it kept failing with flash with fastbootd. Even though I have the most up to date platform-tools.
I believe I know what I did though... I didn't read the instructions clearly and i used the december boot image when i uninstalled magisk.... I'm attempting it again doing the instructions exactly as it states... fingers crossed...
Click to expand...
Click to collapse
Yep, it sounds like that is the issue. It can be easy to mix up. You need to fake a restore of the boot image for the version your phone is currently on (pre-OTA). But after you apply the OTA and install Magisk to the inactive partition, Magisk will create a new backup of a new unpatched boot image with the OTA applied, so each update will roll forward.
@GrimEcho
man, thx you so much. I've just updated from dec to jan ota build, without any issues! xD
This worked beautifully. Unfortunately it only moved me up to December. Will be great if I don't have to remake the boot.img file to go to January.
Recovery mode being on in magisk caused this to fail. I had to edit the config file as mentioned by another, kill magisk then it worked at next launch. Toggling it off within magisk left the flag active in the config file.
Appreciate the writeup.
Anyone have vendor_boot, dtbo and boot.img from 11.2.9.9 le25aa ?. Install a custom kernel and I need to go back to stock
Just use oxygen updtaer to download full zip and do a local install. Flash magisk to alternate partition and reboot.
gorilla p said:
Just use oxygen updtaer to download full zip and do a local install. Flash magisk to alternate partition and reboot.
Click to expand...
Click to collapse
Install the Arter kernel. And now I get an error when I want to update that way. So I need to go back to stock rom.
Do you know any way to do that?
Partigiano0105 said:
Install the Arter kernel. And now I get an error when I want to update that way. So I need to go back to stock rom.
Do you know any way to do that?
Click to expand...
Click to collapse
Shouldn't be flashing a kernel without proper backups first. You need stock untouched boot.img and vendor_boot
mattie_49 said:
Shouldn't be flashing a kernel without proper backups first. You need stock untouched boot.img and vendor_boot
Click to expand...
Click to collapse
how can I do that?
You can download the zip file containing th full update of your version in a thread here, them using the payload dumper tool you extract all img files inside
I don't know how to edit so more details about this process:
1. Go to sticked thread Repo of oos builds
2. Download the zip file of the firmware you are using
3. Download the payload dumper here: https://androidfilehost.com/?fid=818070582850510260
4. Once extracted extract the payload.bin from firmware zip into payload_input directory
5. Launch payload_dumper.exe
6. Process take few minutes depending on your computer, result img files are stored in payload_output directory
7. Have fun with your img file
Alguém sabe como fazer root no oneplus 9 Android 13.1?
First of all, please write in English. This is an English-only forum.
You can root the latest 13.1 firmware the same way you root others. I assume you already have the bootloader unlocked, proper drivers installed on your PC, and basic know-how of fastboot/adb commands. Here is the process:
You need to get the boot.img of your current firmware. You can extract it through MSM Tool's Read Back feature. In case you don't know about MSM, I have attached the boot.img for latest OOS13.1 firmware LE2115_13.1.0.500(EX01). Download and extract zip file and you will have boot.img. Copy this boot.img to your phone. Next you need to download/install Magisk v26.1 on your phone. Open the app, click Install and select that boot.img. Magisk will patch that boot.img and create a new patched_boot.img in your phone's Download folder. Copy that patched_boot.img to your PC. Reboot your phone to bootloader mode. Run this command to temporarily boot the patched_boot.img:
fastboot boot <your_patched_boot.img>
Note that this command is to boot it temporarily. It DOES NOT flash it. Ok, so once your phone boots up, open Magisk app again, click Install and select Direct Install. Now Magisk will root your current firmware permanently.
By this method of temporary booting and then rooting with Magisk's Direct Install method, Magisk will backup your original boot.img. So whenever there is a new software update, you can go to Magisk, select Uninstall, choose Restore Images, and Magisk will revert your original stock boot.img from it's backup. Then you can proceed with system update. Otherwise, without restoring original boot.img, the system update will fail because of patched_boot.img.
Here is the zip attachment. Make sure to extract it.
Thank you friend
shadabkiani said:
First of all, please write in English. This is an English-only forum.
You can root the latest 13.1 firmware the same way you root others. I assume you already have the bootloader unlocked, proper drivers installed on your PC, and basic know-how of fastboot/adb commands. Here is the process:
You need to get the boot.img of your current firmware. You can extract it through MSM Tool's Read Back feature. In case you don't know about MSM, I have attached the boot.img for latest OOS13.1 firmware LE2115_13.1.0.500(EX01). Download and extract zip file and you will have boot.img. Copy this boot.img to your phone. Next you need to download/install Magisk v26.1 on your phone. Open the app, click Install and select that boot.img. Magisk will patch that boot.img and create a new patched_boot.img in your phone's Download folder. Copy that patched_boot.img to your PC. Reboot your phone to bootloader mode. Run this command to temporarily boot the patched_boot.img:
fastboot boot <your_patched_boot.img>
Note that this command is to boot it temporarily. It DOES NOT flash it. Ok, so once your phone boots up, open Magisk app again, click Install and select Direct Install. Now Magisk will root your current firmware permanently.
By this method of temporary booting and then rooting with Magisk's Direct Install method, Magisk will backup your original boot.img. So whenever there is a new software update, you can go to Magisk, select Uninstall, choose Restore Images, and Magisk will revert your original stock boot.img from it's backup. Then you can proceed with system update. Otherwise, without restoring original boot.img, the system update will fail because of patched_boot.img.
Click to expand...
Click to collapse
Thank you for the specifics. I haven't decided whether or not I will modify my OnePlus 9 but I will keep this in mind.
Get token.
Flash token.
Enable unlock bl in dev options.
Install Magisk inside Andoid.
Congrats you did it.
Is there a boot img for LE2115_13.1.0.101(CN01)?
oneplus 9 LE2115_13.1. colorOS
ahumzert said:
Is there a boot img for LE2115_13.1.0.101(CN01)?
Click to expand...
Click to collapse
You can use MSM Tool to extract the Boot.img file, this is how most of use get our hands on the image files. I have provided a guide below on how to do this.
MSM Download Tool Read Back Mode: Create OnePlus Backup!
In this guide, we will show you the steps to take a backup of all the partitions on your OnePlus device via MSM Download Tool Read Back Mode.
droidwin.com