Related
So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Sorry, no idea, i found the provided link via google,
testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?
https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know
pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super
Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.
10.5.10.IN11BA (European version):
I dumped the boot.img with payload dumper from the "OnePlus8ProOxygen_15.E.19_OTA_019_all_2007021957_d0064.zip" file and patched it with magisk
Note: This is for the European variant of version 10.5.10(.IN11BA)
Download links:
boot.img: https://drive.google.com/file/d/1q9BP31PO6tELbTR-4bWD8pP19_g_VSU0/view?usp=sharing
patched boot.img: https://drive.google.com/file/d/1peDOwsvoUVIoEkp8WZ3jGoRvyqd46MOo/view?usp=sharing
You can use these files to root your OP8Pro with the following guide: https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-how-to-root-oneplus-8-pro-twrp-t4083981
10.5.10.IN11AA (global version):
I dumped the boot.img with payload dumper from the "OnePlus8ProOxygen_15.O.19_OTA_019_all_2005301411_63c531a1a94a4fc1.zip" file, you'll have to patch it yourself with magisk
Here is the boot.img file for 10.5.10.IN11AA : https://gofile.io/d/yavZRg
You can patch it using the following steps (source: Magisk github)
Copy the boot.img file to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. (If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img)
Flash the patched boot image to your device with adb:
Code:
fastboot flash boot /path/to/magisk_patched.img
reboot
Please give me feedback if it worked or not
Hello, Thanks for this work. Just a beginner's question, I suppose you must already have an unlocked bootloader to use your files.
vigneras said:
Hello, Thanks for this work. Just a beginner's question, I suppose you must already have an unlocked bootloader to use your files.
Click to expand...
Click to collapse
Yes of course.
Is this patched with magisk 20.4,not magisk canary? And fingerprint sensor works after that?
Thanks, I would come back after unlocking the bootloader
janitor9 said:
Yes of course.
Is this patched with magisk 20.4,not magisk canary? And fingerprint sensor works after that?
Click to expand...
Click to collapse
Yes indeed, patched with 20.4 and fingerprint works fine. I recommend backing up the persist.img just to be sure
Hey brother, any chance of patching 10.5.10AA? Thank you in advance. Cheers
Sent from my IN2025 using Tapatalk
rawhide85 said:
Hey brother, any chance of patching 10.5.10AA? Thank you in advance. Cheers
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
Here is the boot.img file for 10.5.10.IN11AA : https://gofile.io/d/yavZRg
You can patch it using the following steps (source: Magisk github)
Copy the boot.img file to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. (If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img)
Flash the patched boot image to your device with adb:
Code:
fastboot flash boot /path/to/magisk_patched.img
reboot
Unable to boot from patched image. Unable to boot from normal boot patched with magisk ... as a hole - no root with 10.5.10BA
Can someone suggest solution?
Lucifer4o said:
Unable to boot from patched image. Unable to boot from normal boot patched with magisk ... as a hole - no root with 10.5.10BA
Can someone suggest solution?
Click to expand...
Click to collapse
Boot the twrp and flash magisk
cultofluna said:
Boot the twrp and flash magisk
Click to expand...
Click to collapse
Same result - boot loop.
Does anyone have the stock boot.img for the Global version of 10.5.10? For the IN2017 OnePlus 8. IN21AA.
10.5.11 EU Patched pls ??
alxioa said:
10.5.11 EU Patched pls ??
Click to expand...
Click to collapse
Found it here:
https://forum.xda-developers.com/showpost.php?p=83137417&postcount=424
Flying Fox said:
Found it here:
https://forum.xda-developers.com/showpost.php?p=83137417&postcount=424
Click to expand...
Click to collapse
Thanks my friend
hi, sadly the payload unzip doesn't work on my computer. I am urgently looking for the boot.img for 10.5.10.IN21BA. Can anyone help me? i can't find it on the net.
Hi all,
Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself
Please read the process before committing to proceeding, so you know what's required and what you should and shouldn't use!
Stock and patched images are UK/ EU but the guides are universal and could be used on multiple devices.
NOTE:
For these guides the versions used are:
Stable, Canary or BETA depending on firmware, simply change the channel in Magisk settings then select install / update:
11.0.1.1
Magisk Manager - Magisk (Canary) version: 1469b82a (21101)
11.0.2.2
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
11.0.3.3
Boot img patched using Magisk beta 21.4 (21400)
11.0.4.4 (DO NOT UPDATE TO 22.0 YOU WILL BOOTLOOP!
Boot Img patched using Magisk beta
21.4 (21400)
11.0.5.5
Boot img patched using Magisk Stable 22.0 (22000) (18)
11.0.6.6
Boot img patched using Magisk Stable 22.1 (22100)
11.0.7.7
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.8.8
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.9.9
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.10.10
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.11.11
Boot.img patched using Magisk 24
https://forum.xda-developers.com/attachments/11-0-11-11-europe-patched-24303-zip.5566283/
Thanks @tfae
12 11.C.15 EU. Thanks @tfae
1st
Extracting a boot.img using Payload dumper
Pre-requisites
A device with a working version of magisk manager installed, simply change the channel to the version outlined in the list above relevant to your firmware then select install / update:
A Windows 10 computer / laptop
A full update downloaded firmware zip for your model (recommend oxygen updater)
Payload dumper program for Windows.
Process
On your computer
1. Download and copy the PAYLOAD DUMPER folder to your desktop, there will be one folder with 2 files and 2 folders inside.
Download from here: https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
2. Download the firmware of your choice and open it using Winrar or a similar zip program, extract the file called payload.bin to the folder within the payload folder called payload_input.
3. Run the program payload_dumper.exe, a Command prompt will open to show extraction progress (this will extract a bunch of files to the payload_output folder) allow it to completely finish (the CMD window will close automatically)
4. One of the files will be called boot.img, this is the file we'll be patching, copy this to your phone, root of storage which is called /sdcard.
On your phone
5. Open up Magisk and click Install / Update, if you don't see update then change channel, so this by changing the channel in magisk settings, it'll then show the install/ update buttons.
6. Select "Select and Patch a file" it'll open up a file browser, navigate to the boot.img you copied earlier and select it, allow it to complete (this will output a file called "magisk_patched" (which will be in the Downloads folder)
You now have a patched boot.img ready to flash to either slot with fastboot or boot via fastboot, would recommend booting as this is risk free, if it's a bad image for whatever reason and you choose to flash then your phone may bootloop.
NOTE** Some people have noticed that an already patched boot.img when flashed can fail and cause a boot loop when flashed,so if you have downloaded a magisk_patched img from somewhere else then you WILL need to re-patch it on your own device preferably using the afore mentioned magisk manager based on what firmware it's from.
If you intend to follow the guide below with your own patched img then you shouldn't need to patch twice but it won't hurt if you do.
2nd
Upgrading from rooted Android 10 to rooted Android 11
Pre-requisites
A rooted device running Android 10
Canary magisk manager or beta version that works:
Windows 10 computer / laptop
Process
On your phone
1. Disable all Magisk mods
2. Download the Android 11 firmware using Oxygen updater DO NOT INSTALL AUTOMATICALLY, WE NEED TO INSTALL MANUALLY!!!
3. Once downloaded; open settings / system / system updates
4. Click the settings cog and click 'install from local storage'
5. Locate the firmware you downloaded, it's in the root of storage.
6. Click install and allow it to finish, DO NOT CLICK THE REBOOT BUTTON YET!
7. Open Magisk. manager and click "Install / Update"
8. Click "Install to Inactive slot (After OTA) (Once complete, click reboot)
As this is a new base the first boot may take a little longer.
Your phone will now boot with Android 11.0.0 and will have retained root, all your apps will remain as you left them.
Be careful what mods you re-enable as they may not be 11 compatible.
3rd
Update from 11 stable to 11+ stable whilst retaining root
Guide
1. Download the relevant firmware for your device via oxygen updater
2. Open Magisk and remove all the modules you have installed, then reboot
**NOTE- At this point I tend to copy out the whole firmware to my computer, incase I need it in the future, the boot img and patched boot img are at the foot of this guide, I'll always upload the latest firmware as soon as it comes out for the UK/EU model
3. Open up settings / system / system updates , click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage.
4. Click install and allow it to go through the process
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS "INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES"
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select "Install to Inactive slot (After OTA)" then select "LET'S GO" once complete click reboot.
7. Once your phones booted back up your system / files should all remain as they were and you should have root access.
You can now install all your modules again so long as they're compatible with the firmware you've just updated to.
4th
Rooting using fastboot commands
Method 1
Booting the patched image
1. Obtain a patched boot image for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - The above suggested downloads are for the EU / UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager to avoid a bootloop, if you still get a bootloop it's best to obtain one yourself using the guide at the top of this post.
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
You should now boot and remain rooted.
Method 2
Flashing to both slots
1. Obtain a patched boot img for your device variant or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, if you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
Command: adb reboot bootloader
3. Open a command prompt on your computer and navigate to your ADB/fastboot folder.
4. Type the following.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter
6. Your phone should now boot, open magisk and verify you're rooted.
Troubleshooting
If flashing succeeds but you don't have root and you've followed all the instructions, you may have some magisk modules still active, try performing the following.
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation enter this command via ADB.
adb wait-for-device shell magisk --remove-modules
3. Allow to boot, modules will be removed and root should then be active.
Thanks @nycdiplomat for this tip.
If there is no magisk install / update buttons.
1. Make sure you have granted permission to magisk in settings / apps / magisk / permissions
2. Make sure that the update channel is on canary, then force close magisk and then re-open
3. If it still doesn't work then update magisk using canary
4. Last method to check would be to change to the beta channel in magisk settings, then install it.
Or change the update channel, install the version on offer, then change back to canary, install and you should be good to go.
Window's version
Windows 7 will not work with fastboot, please use Windows 10
USB
Use USB 2.0 not 3.0 or 3.1
ADB
These are the files i use for ADB (1st in the below list) tested these on fresh installs of windows on several windows machines, all win 10
Place them into the root of C so it reads C:\ADB much easier to navigate to that way.
Files:
ADB Files for Windows 10:
7.69 MB folder on MEGA
5 files
mega.nz
Payload dumper program for Windows-
https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
Full OTA - Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 FIRMWARE -
https://mega.nz/file/TZl2WIBR#wSP3_bkoWl1FZZX7zfhobo3cYIAhWvDQ9f0ot3_qNFo
Oxygen OS 11.0.0 EU 11.IN11BA - IN2023 Patched boot.img -
https://mega.nz/folder/TE8yWbIL#a6woc43pCpTX_URX5dWr1A
Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 Stock boot.img -
https://mega.nz/folder/6d1mVYgJ#tE90TcwqTLp71SgZX9Xxhg
Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 Patched boot.img -
https://mega.nz/folder/CINjAQCZ#Sns
sRugbc0sELF0ajSAEXg
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
Oxygen OS 11.0.2.2 - EU IN11BA -IN2023 Stock boot.img -
https://mega.nz/folder/PFsmFDKY#01sGzxzVpiAELjcT0LuZmQ
Oxygen OS 11.0.2.2 - EU IN11BA -IN2023 Patched boot.img -
https://mega.nz/folder/vJs0FRBD#SisIJ5FrmkJ3ej1RB6Yz3Q
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
Oxygen OS 11.0.3.3 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.3.3 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.4.4 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.4.4 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.5.5 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.5.5 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.6.6 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.6.6 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.7.7 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.7.7 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.8.8 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.8.8 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.10.10 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.10.10 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.11.11 EU IN11BA - IN2023
Stock boot.img
16.98 MB file on MEGA
mega.nz
Oxygen OS 11.0.11.11 EU IN11BA - IN2023
Patched boot.img
https://forum.xda-developers.com/attachments/11-0-11-11-europe-patched-24303-zip.5566283/
Android 12 11.C.15 - Stock and patched images from. @tfae
File on MEGA
mega.nz
Hi bro thank you so much for this. I don't understand what to do next now. My phone is already updated to 11 and I want to root it and install masigk etc how do I do that? Its already on version 11 I installed normal version 11 stock rom.
So I was on version 10 before and it was rooted and I had magisk I updated and lost root access and magisk. So now I'm on version 11. I have downloaded your patched boot image but what do I do next could you please hell me?
dblane82222 said:
Hi bro thank you so much for this. I don't understand what to do next now. My phone is already updated to 11 and I want to root it and install masigk etc how do I do that? Its already on version 11 I installed normal version 11 stock rom.
So I was on version 10 before and it was rooted and I had magisk I updated and lost root access and magisk. So now I'm on version 11. I have downloaded your patched boot image but what do I do next could you please hell me?
Click to expand...
Click to collapse
Ah so you're on 11 stock? Have you unlocked the bootloader?
I have a guide based on android 10 here for unlocking the bootloader, lot of similarities.
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
Please don't dive in without reading first.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section.
Please let me know before you start.
PS: thanks for not quoting the entire post
Bootloader is already unlocked.
Yes I'm on stock 11.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section. (Where is this section?)
I'm about to start the process now.
dblane82222 said:
Bootloader is already unlocked.
Yes I'm on stock 11.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section. (Where is this section?)
I'm about to start the process now.
Click to expand...
Click to collapse
Yep that should be fine. I think you can also do this from magisk under direct install but I've not tried before and I think it's possible that this may require twrp. So yea go with the root guide.
Should be ok.
Could you give me the link to the Rooting section you have referred too so I know what to do please?
And magisk won't install for me won't let me. So I can't do that. I even tried installing twrp but it won't work.
dblane82222 said:
Could you give me the link to the Rooting section you have referred too so I know what to do please?
And magisk won't install for me won't let me. So I can't do that. I even tried installing twrp but it won't work.
Click to expand...
Click to collapse
No don't install twrp it doesn't work..
Rooting should be a case of installing the magisk_patched IMG to the active slot, you can do both..
The root process is at the bottom of the link i sent you mate.
This is the section on root.
You'll need the magisk_patched file from the OP
Rooting
1. On your computer
Get the magisk_patched file
2. Copy "magisk_patched.img" to C:\Android
3. Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
4. Type the following into the window
adb reboot fastboot
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
On your computer
5. Type the following into the window
fastboot flash boot_a magisk_patched.img
press enter
then
fastboot flash boot_b magisk_patched.img
press enter
NOTE* THIS WILL FLASH THE PATCHED BOOT IMG TO BOTH SLOTS, THIS IS WHAT I DID, I HAVEN'T EXPLORED IF ONE SLOT IS ADEQUATE OR NOT, IT MAY BE POSSIBLE TO ONLY FLASH THE BOOT.IMG TO ONE SLOT BUT AS I HAVEN'T I CAN'T ADVISE.
6.. Once complete, type in the following command
fastboot reboot
press enter, your device will reboot
7. On your phone open up "Magisk Manager" you should now have two green ticks signifying that you now have root access.
So long as you have magisk manager installed that's all you need to do besides that guide
Let me know how u get on
dladz said:
Let me know how u get on
Click to expand...
Click to collapse
so every time i do this on my cmd it says unknown partition 'magisk_patched.img'
error cant determine image file name for 'magisk_patched.img'
sorry if i seems stupid.
---------- Post added at 09:44 PM ---------- Previous post was at 09:34 PM ----------
dladz said:
Let me know how u get on
Click to expand...
Click to collapse
okay so its worked now. i managed to flash it but once i restarted the phone its stuck in a loop keeps going to bootloader menu what do i do now?
---------- Post added at 09:57 PM ---------- Previous post was at 09:44 PM ----------
okay so now its gone to crashdump mode?
dblane82222 said:
so every time i do this on my cmd it says unknown partition 'magisk_patched.img'
error cant determine image file name for 'magisk_patched.img'
sorry if i seems stupid.
---------- Post added at 09:44 PM ---------- Previous post was at 09:34 PM ----------
okay so its worked now. i managed to flash it but once i restarted the phone its stuck in a loop keeps going to bootloader menu what do i do now?
---------- Post added at 09:57 PM ---------- Previous post was at 09:44 PM ----------
okay so now its gone to crashdump mode?
Click to expand...
Click to collapse
? What did you flash?
dladz said:
? What did you flash?
Click to expand...
Click to collapse
the file you gave .. the bootimage please help me because im screwed now i dont have a working phone...
so basicaly before i installed what u gave me and it was just stuck on the bootloader screen it wouldnt go off it. at all
so i installed twrp and then it jut crashed mode... please please help me?
So you needed the magisk_patched from the beginning of this thread (the OP)
Then boot to fastboot mode and flash to both slots using ADB / fastboot from Windows..
Then fastboot reboot.
That's literally it mate..that's all I did.
If you're in crashdump mode then i have no idea what you flashed or how you flashed it..shouldn't have done that.
You're on the EU/UK model right?
No reason why it wouldn't have worked.
dblane82222 said:
the file you gave .. the bootimage please help me because im screwed now i dont have a working phone...
so basicaly before i installed what u gave me and it was just stuck on the bootloader screen it wouldnt go off it. at all
so i installed twrp and then it jut crashed mode... please please help me?
Click to expand...
Click to collapse
Ok so do not install twrp it does not work on 11.
Calm down a moment you haven't broken anything so don't worry..
Tell me what screen you're on please. Also can you boot to fastboot mode? Or even bootloader?
Worse case scenario you will have EDL mode and the MSM tool which can get you back up and running..
Do not attempt to install twrp as it will not work and will cause more harm than good.
If you add steps besides what you're meant to do I can't help you pal.
dladz said:
Ok so do not install twrp it does not work on 11.
Calm down a moment you haven't broken anything so don't worry..
Tell me what screen you're on please. Also can you boot to fastboot mode? Or even bootloader?
Worse case scenario you will have EDL mode and the MSM tool which can get you back up and running..
Do not attempt to install twrp as it will not work and will cause more harm than good.
Click to expand...
Click to collapse
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
dblane82222 said:
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
Click to expand...
Click to collapse
do you have anything that i can speal to u on thats more instant such as whts app or discord or icq or anything ??
dblane82222 said:
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
do you have anything that i can speal to u on thats more instant such as whts app or discord or icq or anything ??
Click to expand...
Click to collapse
I'm actually in bed at the moment pal.
Here's the MSM thread
https://forum.xda-developers.com/on...-tool-to-restore-device-t4084953/post82327013
I think it may have been trying to install twrp.
Before you go down the MSM route.
Try to power off the device without the cable connected..press and hold power and vol down..until the phone turns on.
Should go to bootloader.
If not try it the above with the cable connected to your phone and computer.
If you still can't get in then yes it's MSM time..
Personally have never used it but it's an active thread so always people in there and 10000% someone will have been in the same boat as you.
Not sure what happened with your situation tbh..I tested all the files again myself and they're all legit. I used them before I spoke with you and again just now.
Please though, try not to worry, you'd have to do something mental to break a OnePlus.
You'll be fine.
Let me know how your get on and I'll answer when I can..quite tired at moment.
yeah tried all of that still nothing. going to try the msm solution see what that does its downloading as we speak. but even before the twrp i done what u said and it was stuck on bootloader any idea why that would be ? i can understand it happened becuase i installed twrp and that casued the phone ot enter edl mode. but prior to it it was stuck on bootloader. following just the steps u had said ? once i have got he phone back up and running should i try your mehtod again and see what happens again ?
no problem really apprecite all the help you have given me thank so much.
dblane82222 said:
yeah tried all of that still nothing. going to try the msm solution see what that does its downloading as we speak. but even before the twrp i done what u said and it was stuck on bootloader any idea why that would be ? i can understand it happened becuase i installed twrp and that casued the phone ot enter edl mode. but prior to it it was stuck on bootloader. following just the steps u had said ? once i have got he phone back up and running should i try your mehtod again and see what happens again ?
no problem really apprecite all the help you have given me thank so much.
Click to expand...
Click to collapse
Nah no worries man, just trying to work out what happened..
Once you're back up, maybe ask another thread just to confirm as I'm second guessing myself now..
Don't want you to end up like this again..
See what the chap says in the MSM thread too, his telegram username is in his profile.
To confirm you do have a UK phone right? IN2023 BA
Could have just been the flash didn't go through. You did do a flash and not boot right? To get out of that. Could have just flashed the stock boot.img and that would have saved you
I need a boot.img necessarily from 12.5.6.0.RKHEUXM GLOBAL.
Nowhere is this version of ROM in FastBoot format to download.
I need extract boot.img to magisk root.
I have an installed version of 12.5.6.0.
But I mistake I flash boot.img from version 12.5.3.0. , and now I have a broken system, it's not sound,wi-fi, etc.
Thanks very much
Hi. I used the boot.img from the 12.5.6 "Stable Beta" released a few weeks ago. I read somehere, here, that it is the same built as the one released over OTA a couple of days ago. And so far it's working fine. I have wifi and sound.
It is a recovery file, but you can unzip it and then use a payload dumper tool to extract the boot.img.
The recovery: https://xiaomifirmwareupdater.com/miui/alioth/stable beta/V12.5.6.0.RKHEUXM/
And this tool on my Mac: https://github.com/ssut/payload-dumper-go/releases/tag/1.0.0
kurtschmeichel said:
Hi. I used the boot.img from the 12.5.6 "Stable Beta" released a few weeks ago. I read somehere, here, that it is the same built as the one released over OTA a couple of days ago. And so far it's working fine. I have wifi and sound.
It is a recovery file, but you can unzip it and then use a payload dumper tool to extract the boot.img.
The recovery: https://xiaomifirmwareupdater.com/miui/alioth/stable beta/V12.5.6.0.RKHEUXM/
And this tool on my Mac: https://github.com/ssut/payload-dumper-go/releases/tag/1.0.0
Click to expand...
Click to collapse
If I may go off-topic for a question, recovery files are to be flashed in recovery? fastboot files in fastboot mode? hope you can help enlighten me.
I dont need recovery type rom , there is not after unzip the boot. img.
I need fastboot type rom, there is boot. img after unzip.
Thanks
I must flash boot.img over magisk, not twrp!
Please read my previous post again.
You can get a boot.img from the recovery file!
kurtschmeichel said:
Please read my previous post again.
You can get a boot.img from the recovery file!
Click to expand...
Click to collapse
Thanks very much I'll try it.
So far I have tried to extract boot.img from China V12.5.6.0.RKHCNXM Fastboot TYPE, I flashed it via magisk and everything works fine.
If everything works OK, then it's fine
When the official 12.5.6.0.RKHEUXM is published, you can still patch and flash its boot.img again, in order to be sure you have the right one. I will do it.
Or just wait for the Android 12 update.
kurtschmeichel said:
If everything works OK, then it's fine
When the official 12.5.6.0.RKHEUXM is published, you can still patch and flash its boot.img again, in order to be sure you have the right one. I will do it.
Or just wait for the Android 12 update.
Click to expand...
Click to collapse
;-)
To complete this thread, here is how I extracted the boot.img from the recovery file:
- Download the recovery file from here: https://xiaomifirmwareupdater.com/miui/alioth/stable beta/V12.5.6.0.RKHEUXM/
- Unzip it, you will find a payload.bin file inside.
- Download this command line tool for your platform, I used it on my Mac: https://github.com/ssut/payload-dumper-go/releases
- Unpack it and put the binary inside the folder of the unpacked recovery, next to the payload.bin file
- Run the command : ./payload-dumper-go payload.bin
- Let it do its thing and you will find a series of .img files, one will be boot.img
Credits: https://forum.xda-developers.com/t/tool-a-quick-android-ota-payload-dumper.4173271/
So I' can't root my phone anymore after upgrading.
First I tried my usual method that I used on my Pixel 3a XL running the latest Android 12 image.
- Extracted the boot.img from the OTA pack using "Payload-dumper-go".
- Copied up the boot.img to phone.
- Install Magisk Canary on the phone.
- Rooted the boot.img, copied it to PC.
- Booted it from fastboot.
- Tried direct install.
Crashdump mode. So clearly, no go.
Some helpful person (Mr. Intoxicated.mad from the Telegram group) posted some instructions.
1) Have Magisk Manager installed
2) Download rooting files and extract on PC
3) Copy boot.img and vendor_boot.img to Download folder
4) Open Magisk Manager and click top Install and patch boot.img. When done, go back and repeat the process for vendor_boot.img
5) Move both patched images to adb directory on your pc along with vbmeta.img
6) Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
Unfortunately, this did not work either.
It flashes, the phone boots, but Magisk Manager shows up like there is no actual root.
Tried the same steps with flash boot_a and flash boot_b and also flash boot (so just everything), but no change.
So I've tried:
- Magisk Canary direct install: Root works, but Direct Install -> CrashDump soft brick
- Magisk stable (23.0) with flash -> No root
- Magisk stable (23.0) with boot via fastboot -> No root, not even temporary
I'd appreciate any tips, guides!
Maybe Canary + root both vendor_boot and boot images? I haven't tried that one yet...
Did you try https://t.me/s/magiskalpha ? It's all about OOS12 or AOSP (custom) A12 ?
felek73 said:
Did you try https://t.me/s/magiskalpha ? It's all about OOS12 or AOSP (custom) A12 ?
Click to expand...
Click to collapse
Oh this is a custom Magisk build? I'll try that, thank you!
Will report back if it worked.
I've still got to do some work calls (without call recording that'll be FUN!) and then I'll attempt this.
You can also try this solution (https://forum.xda-developers.com/t/...xyysds-root-toolbox-coloros-oxygenos.4341167/) for Open Beta 3. I am curious if it works for you.
Which region is your OP9?
felek73 said:
Did you try https://t.me/s/magiskalpha ? It's all about OOS12 or AOSP (custom) A12 ?
Click to expand...
Click to collapse
This worked great! I just grabbed the latest APK I could find from the channel, installed it via Direct Install and voila'!
Basic steps:
- Extract the ZIP, use payload-dumper-go to get boot.img
- Copy up boot.img to phone
- Install this Alpha Magisk version, open boot.img from Magisk Manager
- Copy new patched image from Downloads folder to your PC
- Use Fastboot to boot this patched image, you have root at this point (but only temporary)
- Go into Magisk Manager and go for Direct Install
h8Aramex said:
This worked great! I just grabbed the latest APK I could find from the channel, installed it via Direct Install and voila'!
Basic steps:
- Extract the ZIP, use payload-dumper-go to get boot.img
- Copy up boot.img to phone
- Install this Alpha Magisk version, open boot.img from Magisk Manager
- Copy new patched image from Downloads folder to your PC
- Use Fastboot to boot this patched image, you have root at this point (but only temporary)
- Go into Magisk Manager and go for Direct Install
Click to expand...
Click to collapse
What region is your phone?
l_mike said:
You can also try this solution (https://forum.xda-developers.com/t/...xyysds-root-toolbox-coloros-oxygenos.4341167/) for Open Beta 3. I am curious if it works for you.
Which region is your OP9?
Click to expand...
Click to collapse
I haven't tried that one yet. I saw it yesterday but today it just would not pop up today while I was looking for it.
My phone is EU (Europe) - 12GB/256GB OnePlus 9 Pro LE2123 , ordered directly from the OnePlus online store.
Could you extract your boot.img? I am also with eu, maybe i would had less steps to make
Also, does the call recording work on a12?
h8Aramex said:
This worked great! I just grabbed the latest APK I could find from the channel, installed it via Direct Install and voila'!
Basic steps:
- Extract the ZIP, use payload-dumper-go to get boot.img
- Copy up boot.img to phone
- Install this Alpha Magisk version, open boot.img from Magisk Manager
- Copy new patched image from Downloads folder to your PC
- Use Fastboot to boot this patched image, you have root at this point (but only temporary)
- Go into Magisk Manager and go for Direct Install
Click to expand...
Click to collapse
So just do normal steps but use alpha magisk instead of stable? Can I use latest canary?
Moe2003 said:
So just do normal steps but use alpha magisk instead of stable? Can I use latest canary?
Click to expand...
Click to collapse
Apparently not, see OP.
terlynn4 said:
Apparently not, see OP.
Click to expand...
Click to collapse
He linked the telegram channel for canary magisk and said he grabbed the latest that he could find there, soooo
Moe2003 said:
He linked the telegram channel for canary magisk and said he grabbed the latest that he could find there, soooo
Click to expand...
Click to collapse
The telegram channel is for alpha, not canary. The whole OP is about how canary didn't work.
I just installed alpha myself, and against my better judgment I'm about to attempt the upgrade from OB3 to stable.
terlynn4 said:
The telegram channel is for alpha, not canary. The whole OP is about how canary didn't work.
I just installed alpha myself, and against my better judgment I'm about to attempt the upgrade from OB3 to stable.
Click to expand...
Click to collapse
Ok I'm stupid I thought canary and alpha were the same haha
l_mike said:
Also, does the call recording work on a12?
Click to expand...
Click to collapse
With Skvalex Call Recording + Root, yes it does. I never used the OnePlus call recorder thing because I saw it tells the other half that they are being recorded or something. Which just makes the entire conversation hostile, awkward. People know that I record them and they love that they can just dictate all their orders and crap.
h8Aramex said:
So I' can't root my phone anymore after upgrading.
First I tried my usual method that I used on my Pixel 3a XL running the latest Android 12 image.
- Extracted the boot.img from the OTA pack using "Payload-dumper-go".
- Copied up the boot.img to phone.
- Install Magisk Canary on the phone.
- Rooted the boot.img, copied it to PC.
- Booted it from fastboot.
- Tried direct install.
Crashdump mode. So clearly, no go.
Some helpful person (Mr. Intoxicated.mad from the Telegram group) posted some instructions.
1) Have Magisk Manager installed
2) Download rooting files and extract on PC
3) Copy boot.img and vendor_boot.img to Download folder
4) Open Magisk Manager and click top Install and patch boot.img. When done, go back and repeat the process for vendor_boot.img
5) Move both patched images to adb directory on your pc along with vbmeta.img
6) Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
Unfortunately, this did not work either.
It flashes, the phone boots, but Magisk Manager shows up like there is no actual root.
Tried the same steps with flash boot_a and flash boot_b and also flash boot (so just everything), but no change.
So I've tried:
- Magisk Canary direct install: Root works, but Direct Install -> CrashDump soft brick
- Magisk stable (23.0) with flash -> No root
- Magisk stable (23.0) with boot via fastboot -> No root, not even temporary
I'd appreciate any tips, guides!
Maybe Canary + root both vendor_boot and boot images? I haven't tried that one yet...
Click to expand...
Click to collapse
I have always rooted my phones, right now i am rooted on OOS 11 for OnePlus 9 Pro, should I follow the tutorial provided at [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] ? Not sure if it is updated for OOS 12 or not yet.
l_mike said:
Could you extract your boot.img? I am also with eu, maybe i would had less steps to make
Click to expand...
Click to collapse
It's 40MB unfortunately so I don't think XDA would let me attach it.
Also try to source most steps, files from "trusted places". Don't run these "packs" you can find in Google and whatnot. Not that I personally would ever try to harm any of our fellow XDA members, but you get the idea. The internet and people can be nasty.
You can do "payload-dumper-go.exe -p boot payloadfile" and then it only extracts the payload.
Also one thing people!
For me, something installed a C:\Android\ folder with Fastboot and ADB.
ALWAYS MAKE SURE TO USE LATEST, OFFICIAL FASTBOOT AND ADB!!!!!
I know. Lot of exclamation marks and bold font.
But I've spent SO MUCH time because of this.
Even though I've had the "platform-tools" folder added to my PATH, this other thing appeared higher in the list for Windows.
So.
1) Open CMD.
2) Type "where fastboot"
Then you can make sure if you are using the one you want.
Where to get a "good fastboot"?
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Extract it, and you can add it to Path.
How to add to Path? In Win10/11, type "Path" in Start. And "Edit system environment variables" comes up.
Then click "Environment Variables" on the bottom of the newly opened System Properties window.
Double click "Path" , "New" and then just paste in the path. Like: C:\junk\platform-tools-123\
You don't have to mess with all this though. But ALWAYS make sure you are running the adb/fastboot you want!
tazoman said:
I have always rooted my phones, right now i am rooted on OOS 11 for OnePlus 9 Pro, should I follow the tutorial provided at [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] ? Not sure if it is updated for OOS 12 or not yet.
Click to expand...
Click to collapse
Thank you! Unfortunately, this does not work; but there is a solution in the thread. I've just changed the topic to say [SOLVED], I forgot about it, sorry.
h8Aramex said:
Thank you! Unfortunately, this does not work; but there is a solution in the thread. I've just changed the topic to say [SOLVED], I forgot about it, sorry.
Click to expand...
Click to collapse
Later on how would we switch to canary or beta if it works again, and did u clean flash oos 12 or just update? Any bugs?
Moe2003 said:
Later on how would we switch to canary or beta if it works again, and did u clean flash oos 12 or just update? Any bugs?
Click to expand...
Click to collapse
Well, root definitely works (tried with Call Recorder).
You can simply uninstall the Magisk Manager, grab whichever you want (stable, canary) and then patch the latest boot.img. Just like now. Nothing tricky honestly. Once you update to a new system version, your boot.img will return to stock/unrooted anyway.
Though, Canary is like... super-alpha. It's supposed to be bleeding-edge, the freshest. So it's weird Canary failed, while Alpha works fine.
I updated via OTA. I don't think OnePlus provides flashable ZIPs at all. To do a Pixel like, full fastboot "-w" wipe update. You could upgrade and then wipe. But other than that...