Develop Bugs

[PROJECT][ROOT][RN8P] rooting without TWRP / rooting with magisk+boot.img patched

device : chinese RN8P
rom : chinese swapped to global
hi,
tried to find another method to root the RN8P, chinese version with global rom
followed this guide to patch boot.img, extracted from global rom package 10.4.1.0 global
https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/
in the end, we should theorically root after flash patched.img in fastboot mode, and install magisk after that with magisk manager
for now patched boot.img by magisk manager with magisk20.zip make a patched img 10mb...the original file makes 60mb
any ideas from experts?
thanx
https://drive.google.com/open?id=1f3DzBwZ_xfwy6ES6YElQQJy6ZVe4CS3P

harmakhis said:
device : chinese RN8P
rom : chinese swapped to global
hi,
tried to find another method to root the RN8P, chinese version with global rom
followed this guide to patch boot.img, extracted from global rom package 10.4.1.0 global
https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/
in the end, we should theorically root after flash patched.img in fastboot mode, and install magisk after that with magisk manager
for now patched boot.img by magisk manager with magisk20.zip make a patched img 10mb...the original file makes 60mb
any ideas from experts?
thanx
https://drive.google.com/open?id=1f3DzBwZ_xfwy6ES6YElQQJy6ZVe4CS3P
Click to expand...
Click to collapse
make a backup of the patched boot.img with twrp. it will be like boot.emmc.win
rename .win by .img

i dont have twrp and you say to me to backup with twrp

You can try magisk in recovery

You can extract boot without installing twrp
Get twrp working on the phone and use command
Fastboot boot " twrp.img "
This will redirect you to twrp and you can use it without replacing the recovery of the phone and when you restart the device you will be using your phone normally
I tried to do the same thing
Fastboot boot patched_boot.img to test the img from magisk but the phone boot loop
Maybe i will try to backup boot using twrp and patch it with magisk

i dont know what they do with those phones but they were not such a pain in the ass to mod in the past

Question [SOLVED] How to root Android 12 version? (see thread, use Alpha Magisk!)

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...

Initial Installation of Magisk v24 - patch boot.img

Hey guys, has someone ever installed Magisk v24 by using this Guide:
I have shortened it in the way that I think it's right, NOT TESTED YET
Can anyone with the knowledge about this "proof read it"?
############################################
Get a copy of the boot.img.
You should be able to extract the file you need from official firmware packages or your custom ROM zip.
Next, we need to know whether your device has a separate vbmeta partition.
If your official firmware package contains vbmeta.img, then yes, your device has a separate vbmeta partition
You can also check by connecting your device to a PC and run the command:
adb shell ls -l /dev/block/by-name
If you find vbmeta, vbmeta_a, or vbmeta_b, then yes, your device has a separate vbmeta partition
Otherwise, your device does not have a separate vbmeta partition.
Quick recap, at this point, you should have known and prepared:
Whether your device has boot ramdisk
Whether your device has a separate vbmeta partition
A boot.img or recovery.img based on (1)
Let’s continue to Patching Images.
Patching Images​
Copy the boot image to your device
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the boot image
Start the installation, and copy the patched image to your PC using ADB:
Code:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Flash the patched boot image to your device.
For most devices, reboot into fastboot mode and flash with command:
Flash the patched boot image to your device.
For most devices, reboot into fastboot mode and flash with command:
Code:
fastboot flash boot /path/to/magisk_patched.img
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Reboot and voila!
Uninstallation​The easiest way to uninstall Magisk is directly through the Magisk app. If you insist on using custom recoveries, rename the Magisk APK to uninstall.zip and flash it like any other ordinary flashable zip.
Best, dj

derjango said:
Hey ...
Click to expand...
Click to collapse
Why people look for troubles ?
That guide is for people who don't have custom recovery
it's a long process and some people will make mistakes
renaming to zip and flash in recovery is the easiest way
also with patching img way you will not have a magisk folder in data/adb and magisk will tell you that the install is not complete and probably will need couple of reboots to work ...

To be honest, my trouble is, that the Magisk App does not work properly and I'm searching the reason for that.
It says:
Magsik:
Installed: N/A
Zygisk: No
Ramdisk: No
In the bottomline Superuser is inactive as well as Modules.
How can I fix this?
I've installed Magisk.zip via TWRP, Root Checker tells me that Root is not installed properly
Best, dj
/edit
got it, I had to install it after booting into rom, not directly after flash ROM

derjango said:
In the bottomline Superuser is inactive as well as Modules.
/edit
got it, I had to install it after booting into rom, not directly after flash ROM
Click to expand...
Click to collapse
Hey brother, I've been searching high and low for this problem and got excited seeing your post.
Care to elaborate on how you managed to solve the inactive SU & Modules sections problem?

loopypalm said:
Why people look for troubles ?
That guide is for people who don't have custom recovery
it's a long process and some people will make mistakes
renaming to zip and flash in recovery is the easiest way
also with patching img way you will not have a magisk folder in data/adb and magisk will tell you that the install is not complete and probably will need couple of reboots to work ...
Click to expand...
Click to collapse
I tried doing that with lineage but it stopped internet working

Nebster7 said:
I tried doing that with lineage but it stopped internet working
Click to expand...
Click to collapse
i used .ZIP method on over than 200 rom (including lineage builds) and never had such problem
maybe in new magisk builds ? or miui based rom ?

Done it now using boot_a and boot_b method https://www.getdroidtips.com/how-to-root-poco-x4-pro-5g/

Nebster7 said:
Done it now using boot_a and boot_b method https://www.getdroidtips.com/how-to-root-poco-x4-pro-5g/
Click to expand...
Click to collapse
so you look on how to root "Poco X4 Pro 5G" on "redmi note 8" forums ?

Question cant flash anything after flashing custom rom.. please help ASAP

tried many custom roms with recoveries but after flashing rom cant install magisk because of this !! help needed !!

You need after install customrom instal in system Magisk apk
After in app magisk patch boot.img from your customrom. This file patched in Download folder. Transfer to your PC and this file patchedboot.img flash in Fastbooy mode command with adb
Fastboot flash boot patchedfile.img
After patch magisk work
Patch here

Works for me with PixelOs or PixelExperience

boneszbo said:
You need after install customrom instal in system Magisk apk
After in app magisk patch boot.img from your customrom. This file patched in Download folder. Transfer to your PC and this file patchedboot.img flash in Fastbooy mode command with adb
Fastboot flash boot patchedfile.img
After patch magisk work
Patch here
View attachment 5769251
View attachment 5769253
Click to expand...
Click to collapse
ur 3rd photo does not showed up !

boneszbo said:
You need after install customrom instal in system Magisk apk
After in app magisk patch boot.img from your customrom. This file patched in Download folder. Transfer to your PC and this file patchedboot.img flash in Fastbooy mode command with adb
Fastboot flash boot patchedfile.img
After patch magisk work
Patch here
View attachment 5769251
View attachment 5769253
Click to expand...
Click to collapse
what patched file ??? u mean from magisk zip img file ?

1. Install Customrom like PixelOS before u install u flash via fastboot file boot.img
After install Customrom u must the same file from your Rom patch Via Magisk so u must install Magisk.apk in Android
In Android Magisk App u must click Install and patch file from ur Rom Boot.img
New file save in Download Patched_boot.img
This file transfer to your computer
Go phone to fastboot mode and flash with command new file patched
Fastboot flash boot patched_boot.img
After flash boot recovery u have install Magisk correctly
Examples:
How to Root Pixel Experience ROM via Magisk [Video]
In this comprehensive tutorial, we will show you the steps to root your Pixel Experience ROM via Magisk patched boot.img file
www.droidwin.com
U only need download recovery boot from ur CustomRom u dont need extract payload.bin

U must patch this file via Magisk application in PixelOs for examples

So first go to
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Download magisk.apk and install
In Magisk App patch boot file img after flash it with PC
Done u goot Magisk installed with root

Remember to use boot file from your customrom not other... If u use PixelOs u need boot recovery from PixelOs etc. !!

boneszbo said:
1. Install Customrom like PixelOS before u install u flash via fastboot file boot.img
After install Customrom u must the same file from your Rom patch Via Magisk so u must install Magisk.apk in Android
In Android Magisk App u must click Install and patch file from ur Rom Boot.img
New file save in Download Patched_boot.img
This file transfer to your computer
Go phone to fastboot mode and flash with command new file patched
Fastboot flash boot patched_boot.img
After flash boot recovery u have install Magisk correctly
Examples:
How to Root Pixel Experience ROM via Magisk [Video]
In this comprehensive tutorial, we will show you the steps to root your Pixel Experience ROM via Magisk patched boot.img file
www.droidwin.com
U only need download recovery boot from ur CustomRom u dont need extract payload.bin
Click to expand...
Click to collapse
there is no recovery boot so i think i need to extract playload.bin

Try PixelOs good Rom everythings work. Photos google unlimited srorage...
And u got recovery boot img file

boneszbo said:
Remember to use boot file from your customrom not other... If u use PixelOs u need boot recovery from PixelOs etc. !!
Click to expand...
Click to collapse
i am using awoken os !!
https://sourceforge.net/projects/pr...iton-lisa-official-1240-20221018.zip/download
i extracted the rom but there is no img file

boneszbo said:
Try PixelOs good Rom everythings work. Photos google unlimited srorage...
And u got recovery boot img file
Click to expand...
Click to collapse
ok flashing pixel os again then !!!

U have here boot awaken os

U need patch thia boot.img file via Phone Magisk and flash via fastboot.
Done

boneszbo said:
Try PixelOs good Rom everythings work. Photos google unlimited srorage...
And u got recovery boot img file
Click to expand...
Click to collapse
dude I was so tired that I could not understand what u said but it was so simple !!!! thanks for the help !!!! thank you so much !!!

boneszbo said:
U need patch thia boot.img file via Phone Magisk and flash via fastboot.
Done
Click to expand...
Click to collapse
yes it was simple but those links and tutorials confused me !!! again thanks for the big help

Welcome back...

[OOS13] IN2023_11_F.15 Patched boot.img

Hello everyone,
I wasn't able to find it here and I didn't want to wait I am sharing here the Patched boot.img for the last OOS13 update. (F.15)
I want to thank user @Neil_Armstrong_ for his post and, please forgive me and my laziness, I am copying here his perfect instructions
You can find attached the patched boot image for the first stable OOS 13 firmware (IN2023 = 8 Pro European/Global version)
Steps :
Unlock the phone bootloader
Install ADB and Fastboot on your computer
Download the patched boot.img below
Reboot your phone to fastboot mode and link it to your computer
Open a terminal prompt in the directory where the boot.img is located
type in the cmd
fastboot flash boot IN2023_11_F15-Patched.img
Click to expand...
Click to collapse
and press enter
Reboot the phone
Open the magisk app, hit Install then use the recommended method
Reboot and you're rooted
Google drive

Hi, I'm looking for the patched boot.img for IN2025_F15
Is there a thread how to extract and patch (complete) ? Thanks

@karib97 you can find a good guide here
[GUIDE]How to extract img(boot.img, etc...) from payload.bin using payload-dumper-go.
For 10R only: I have uploaded a few of the extracted boot.img, before extracting if you want you can look for the required boot.img here: https://www.mediafire.com/folder/kyn2p5mhde7nn/boot.img 1. Download and extract payload-dumper-go. 2...
forum.xda-developers.com
First remember to download on your pc the update of your phone and the payload dumper. It seems difficult but it is not!

i am currently on OS 11.0.11.11.IN11.AA. Is it safe to update to this F.15 version as you described?

epicurean said:
i am currently on OS 11.0.11.11.IN11.AA. Is it safe to update to this F.15 version as you described?
Click to expand...
Click to collapse
No, you have to update to OS 13 (without incremental) and root it. This is the latestest version for IN on OS 13 for incremental only.