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
Related
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.
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!
UninstallationThe 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 ?
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...
Hello! As written in the title, i updated my already rooted poco f3 to the latest miui 14.0.7 (european rom) and then proceded to flash magisk. I followed everything to a T (extract boot from payload, patch in magisk, check partitions) and flashed it in fastboot. The terminal said "flashed to boot_a succesfully" so i rebooted. After unlocking the phone though, just a few seconds later it starts reooting on its own and prompts me to the miui recovery. I tried flashing the patched boot image both to boot_a and boot_b after this error, but it keeps happening.
Any help? i just don't want to lose my data.
EDIT: Thankfully i made it. The error was caused by a magisk module, so in the adb shell just run magisk --remove-modules and the error should be solved. Info from https://topjohnwu.github.io/Magisk/...debugging,and automatically reboot the device.
Would it work again if i flashed the stock boot image?
Pillow fan said:
Would it work again if i flashed the stock boot image?
Click to expand...
Click to collapse
Yes, or you can reflash the ROM.zip (without data-format of course)
OrangeFox Recovery has a Magisk Module Manager built-in and lets you disable/remove individual Modules.
Otherwise, you can simply put an empty file called "disable" or "remove", into /data/adb/modules/your_module_here/
On the next boot, Magisk will take action accordingly.
Also, maybe this is easier for you, but you can simply use a TWRP / OrangeFox Backup of the boot-partition, to patch Magisk.
Then you can rename the Magisk-patched Boot.img back into "boot.emmc.win", put it into Backup folder and replace with original Boot backup file, and restore with TWRP/OF.
Doesn't require a PC.
Hi,
When my phone automatically updated to MIUI 14, a error message appeared and then, my root was lost...
Il tryed several times to get it back patching boot.img from Magisk.. (canary version included), but when I install patched.img my phone does not start and i have to get back to boot.img
Any ideas?
Rename magisk from apk to zip, and then flash the magisk zip from recovery
Saezrfff said:
Hi,
When my phone automatically updated to MIUI 14, a error message appeared and then, my root was lost...
Il tryed several times to get it back patching boot.img from Magisk.. (canary version included), but when I install patched.img my phone does not start and i have to get back to boot.img
Any ideas?
Click to expand...
Click to collapse
Hi,
Boot your F3 into fastboot mode and connect to a PC,
Download "Temporary Recovery" and unzip, run the "RUN ME Temporary TWRP A13-Orange Fox Recovery.bat" file and choose TWRP.
Once rebooted select: Advanced from within TWRP and tap "Flash current TWRP", copy over the included Magisk files into the internal memory (I use a OTG adaptor and USB Stick), install Magisk V26.1.apk, when in recovery you can install Magisk as a .apk format.
Included are the files i use when switching between roms, included are the latest, Magisk V26.1 and Magisk Delta, it also includes the latest versions of TRWP/OrangeFox recovery and other goodies,
I hope it helps
It's possible that the MIUI 14 update may have caused compatibility issues with your previous root method. You could try using a different root method or a different version of Magisk. Additionally, make sure you are following the correct steps for patching the boot.img file and installing it. If the issue persists, you may need to wait for an updated version of Magisk or seek assistance from the Magisk community.
you can try patching Boot.img instead of flashing Magisk.zip
you can do a OrangeFox/TWRP Backup of Boot-partition and patch the resulting "boot.emmc.win" file in Magisk App, because it's actually just a normal partition-image.
then flash the magisk-patched image file.
no pc required. just a custom recovery.
you can try the new Magisk v26.1, or Magisk Alpha (not affiliated with official Magisk).
i use Magisk v26.1 Official but I'm on AOSP