Database Users

[Guide][Root] Magisk without TWRP on Android P

Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode
REQUIREMENTS -
1 - Setup adb and fastboot on your PC.
2- Stock boot image (boot.img) of your device (extract file from factory image android P)
3 - Last Magisk Manager (v 5.8.3)
4 - Active Internet connection
5 - Active mind and patience.
6 - Devices must is unlock bl.
This Boot-Image is for boot android P PPR1.180610.009:
https://drive.google.com/open?id=166pE9aMk-jqns3JM74enFhsaDY6-c3yJ
Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
==================================================
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta
7- Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
CREDITS
@topjohnwu (Magisk)

Sadly goes into a bootloop for me - no idea why though

This worked for me. I had magisk installed and took the pie update. No more root. D/l the factory image and extracted the boot image to the files folder...pissmeoff they changed the name of the icon... and magisk patched the image and saved it in its folder. Found the file, moved it to the laptop then flashed it.

reawo said:
Sadly goes into a bootloop for me - no idea why though
Click to expand...
Click to collapse
I think you made a mistake.

I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide

reawo said:
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
Click to expand...
Click to collapse
I think you use my file(boot.img) for patch_boot.img from magisk manager.
I think you must check your build number devices.
You must use file boot.img from your factory image for root.
9.0.0 (PPR1.180610.009, Aug 2018) >This is version for my devices
9.0.0 (PPR1.180610.011, Aug 2018, Telstra) >?

hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?

reawo said:
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
Click to expand...
Click to collapse
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin

newyesor said:
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
Click to expand...
Click to collapse
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?

I receive also a bootloop and I didnt make any mistake. I also used this method pre Pie, I read that alot of users have problems with rooting Pie atm, even with TWRP

reawo said:
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
Click to expand...
Click to collapse
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.

newyesor said:
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
Click to expand...
Click to collapse
I downloaded all the latest adb and fastboot. Never touched kernel or did custom recovery, always used the magisk method since i am on a pixel device. i also got the issue that my pc doesnt recognize my pixel from time to time, you think i should do a complete wipe?

I don't sure.
You are use platfrom-tool from sdk lastversion?(for flash via fastboot mode)

@reawo
I think you should flash factory image new again and factory reset your devices.
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta ,and close this app.****
7- Open app again and Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching (This process is not failed)***
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk

Will work on the verizon variant (bootloader locked)?

sabi95190 said:
Will work on the verizon variant (bootloader locked)?
Click to expand...
Click to collapse
Nope. If it were that easy for bootloader locked Verizon phones, it would have been done months ago.

What happens if you lock the bootloader after all of this?

DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
You'll wipe the phone, lose root, and be stock.

DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.

TonikJDK said:
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
Click to expand...
Click to collapse
"Borderline"???? More like certifiably insane! ?

Nokia 6 Rooting?

Hi!
I need some help rooting my Nokia 6 Mobile phone
The model number is TA- 1033
I have tried all kinds of different sources as a guide, but all failed for me.
I tried several one-click root tools as well. (Kingroot, Kingo Root)
I have tried to unlock the bootloader with Fastboot and ADB for the TWRP recovery flash
I have got developer options and also enabled USB Debugging and OEM unlocking ut the procedure still fail all the time.
I've tied to flash the TWRP without unlocking the bootloader but that ailed as well.
My device is not bricked yet.
Thank you for your help

My attempts to root were successful only on Nougat (Not Oreo, because of bootloader)
Make a backup of all your important files in your phone.
Download OST and with it install this stock rom (https://mega.nz/#!5ccRnb4b!VsgiKQ4CjxFyjbjcxR0esjeKmHZsUTnEz0FA_FMZQbM)
(To install it, you need the phone in bootloader mode.)
If it displays an error the first time, try again until the installation is fully successful.
Once the phone is turned on, the first thing you need to do is turn off automatic software updates. Know that if you want root, you should forget about OTA updates.
Once all written above is done remains to unlock the bootloader and installing TWRP.
For that..
Enter in bootloader mode.
Use Fastboot from your PC and enter this command to allow the partitions to be changed on your phone.
(To get MD5 of your serial number, use this website: http://www.miraclesalad.com/webtools/md5.php)
fastboot oem dm-verity [MD5_of_your_device_serial_number]
(Example: fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e)
After that download this bootloader(http://pc.cd/xUFrtalK) and flash it:
fastboot flash aboot D1C-emmc_appsboot.mbn
(Make sure that downloaded bootloader is located in adb/fastboot folder)[Or you can type full file path of bootloader(Example: "C:\Users\Martin\Downloads\D1C-emmc_appsboot.mbn")]
(This to flash an unlocked bootloader.)
fastboot reboot-bootloader
(This is to reboot for using new unlocked bootloader.)
fastboot oem dm-verity [MD5_of_your_device_serial_number]
(Again to allow installing partitions.)
Download recovery from here: https://mega.nz/#F!K1k0gC5C!xpw3-AQvSQJ5p6VWX19gpA)
Flash it with this command:
fastboot flash recovery nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img
(Make sure that downloaded recovery is located in adb/fastboot folder)[Or you can type full file path of twrp recovery(Example: "C:\Users\Martin\Downloads\nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img")]
After that reboot to twrp recovery and flash Magisk ROOT.
All is done.
Magisk is built in recovery. You don't need to download it from internet. Flash magisk which is in recovery.
Warning: After opening magisk manager you can update app but you can't update magisk version (core). Because latest version cause bootloop on ours devices. Use 16.1 version which is in recovery build it.
I hope everything will be fine. Good luck!

Hi! I have some issues.
marto2013 said:
My attempts to root were successful only on Nougat (Not Oreo, because of bootloader)
Make a backup of all your important files in your phone.
Download OST and with it install this stock rom
Click to expand...
Click to collapse
Okay
So when I tried to flash the rom you gave me it failed with a download error. I tried to use OST LA 6.0.4 and 6.1.2 but both failed.
Clicking on the "Edit phone information" didn't work either. Can you help me in this situation? I have tried to reinstall OST LA several times, but it didn't resolve the problem.

VargaTibor1 said:
Okay
So when I tried to flash the rom you gave me it failed with a download error. I tried to use OST LA 6.0.4 and 6.1.2 but both failed.
Clicking on the "Edit phone information" didn't work either. Can you help me in this situation? I have tried to reinstall OST LA several times, but it didn't resolve the problem.
Click to expand...
Click to collapse
On which patch level are you?

ZeroPointMax said:
On which patch level are you?
Click to expand...
Click to collapse
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08

VargaTibor1 said:
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
Click to expand...
Click to collapse
That means you cannot use OST LA or oem-veracity. Nokia changed the algorithm with August patch. You can basically not root your phone anymore using this method.

ZeroPointMax said:
That means you cannot use OST LA or oem-veracity. Nokia changed the algorithm with August patch. You can basically not root your phone anymore using this method.
Click to expand...
Click to collapse
He can downgrade his bootloader using older OTA update.
=====
VargaTibor1 said:
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
Click to expand...
Click to collapse
Make backup on anything! You will not have access to anything until you install the rom I gave you in the first post.
Go to recovery and flash this ota update.
https://my.pcloud.com/publink/show?code=XZYg1T7ZzpJwx2DdRo4wbpTUEXABAfnS9PgX
After all go to recovery again.
If it says that the Android version is 7.1, then everything is ready.
If it does not get the first time, flash ota again.
When I did it, I think I flash two times ota update.
If it's okay, try the Instructions from the first post again.

marto2013 said:
He can downgrade his bootloader using older OTA update.
=====
Make backup on anything! You will not have access to anything until you install the rom I gave you in the first post.
Go to recovery and flash this ota update.
https://my.pcloud.com/publink/show?code=XZYg1T7ZzpJwx2DdRo4wbpTUEXABAfnS9PgX
After all go to recovery again.
If it says that the Android version is 7.1, then everything is ready.
If it does not get the first time, flash ota again.
When I did it, I think I flash two times ota update.
If it's okay, try the Instructions from the first post again.
Click to expand...
Click to collapse
I thought this wouldn't work too

Original (and patched too) boot.img from Mi A1 Android 9 10.0.12.0 (August Patch)

I am searching for it
Thanks
Paolo

You can download the patched boot image from here https://phonebatao.com/phone/xiaomi-mi-a1-price-in-india#downloads

Help!
The file put by the gizmofreak friend I tried to install by means of magisk but in doing so it says done and nothing happens, I have to install by means of pc and adb or how is the process for this boot file

I need 10.0.11 boot patched or original!

GizmoFreak said:
You can download the patched boot image from here https://phonebatao.com/phone/xiaomi-mi-a1-price-in-india#downloads
Click to expand...
Click to collapse
Hi, Can you please upload patched image for the September 2019 update?
Thanks

goto this thread you can find august patched boot img with permanent twrp installed just flash and enjoy
https://forum.xda-developers.com/mi-a1/how-to/install-twrp-recovery-pc-rooted-mi-a1-t3958662

[help] Magisk, Mi A1 and october 2019 security patch.

Hi, I'm a long time magisk user, yesterday update my mi a1 to latest stock update (October patch) I'm following the steps used before: Update from twrp Reboot with twrp and backup boot Reboot the phone, from magisk manager install, select img and patch. Reboot Boot from patche boot.img
And then this time get a bootloop.
See the files original boot.emmc.win has 61mb Magisk_patched.img this time has 16mb The previous version of boot_patched.img has always @60mb
Any idea?
Thanks.

The same thing happened to me, but luckily the other slot was functional.
Reboot in Fastboot mode (holding down the VOL- button while powering on) and switch slots (check which one is active with fastboot getvar all and then fastboot set-active=a or b using fastboot tool connected to a PC) and mine booted with no problems, updated and with Magisk 20 still active and running.
Then I did the logic next step of dumping my working system, boot and modem images and flashed them to the corrupted slot - now both work flawlessly.

I had the may update stock rom with magisk. As soon as I updated to magisk 20, I got the "System destroyed error". Luckily I was able to apply stock image again and started from scratch

(closed)Fastboot bootloop

Hi gyes, I have redmi k20, when I flash magisk patched recovery image then device stuck at fastboot, so I flash original recovery image for device , then it start in normal mode, so device can't rooted, so pls any one guide me to root device with magisk.
Thanks...

wakram001 said:
Hi gyes, I have redmi k20, when I flash magisk patched recovery image then device stuck at fastboot, so I flash original recovery image for device , then it start in normal mode, so device can't rooted, so pls any one guide me to root device with magisk.
Thanks...
Click to expand...
Click to collapse
You have to patch boot.img and flash the patched img to Boot
Btw, there were two guides in the Guides section about the same (stating exactly the same: extract boot ing, patch and flash).
Guides (in the Redmi K20/Mi 9T section) are old and maybe from the times of A9 MIUI 10 - but the same method still works for A11 / MIUI 12.x
Hence, you can have in parallel both Magisk (in Boot partition) and TWRP (in Recovery partition)
boot.img must be extracted from exactly the same firmware package (recovery/zip or fastboot/tgz) that you have installed to your phone.
Or you can patch boot.emmc.win TWRP backup file of your Boot partition (instead of exteacted boot.img file)
You can flash from Fastboot of from TWRP
If using TWRP, use the latest official twrp-3.5.2_9-0-davinci

My device has no ramdisk.
I have already tried with boot image but magisk patched boot image not flash, it show error.
Thanks for reply...

zgfg said:
You have to patch boot.img and flash the patched img to Boot
Btw, there were two guides in the Guides section about the same (stating exactly the same: extract boot ing, patch and flash).
Guides (in the Redmi K20/Mi 9T section) are old and maybe from the times of A9 MIUI 10 - but the same method still works for A11 / MIUI 12.x
Hence, you can have in parallel both Magisk (in Boot partition) and TWRP (in Recovery partition)
boot.img must be extracted from exactly the same firmware package (recovery/zip or fastboot/tgz) that you have installed to your phone.
Or you can patch boot.emmc.win TWRP backup file of your Boot partition (instead of exteacted boot.img file)
You can flash from Fastboot of from TWRP
If using TWRP, use the latest official twrp-3.5.2_9-0-davinci
Click to expand...
Click to collapse
My device has no ramdisk, A 10 miui 12.
I have already tried with boot image but magisk patched boot image not flash, it show error.
Thanks for reply...

wakram001 said:
My device has no ramdisk, A 10 miui 12.
I have already tried with boot image but magisk patched boot image not flash, it show error.
Thanks for reply...
Click to expand...
Click to collapse
Don't pay attention to what Magisk says (No Ramdisk).
Brw, there is some (albeit small prints) note about 'No Ramdisk' devices in the Magisk guide on the official Magisk Github - saying that on some (not sure does it mention Xoaomi) boot.img must be patched
I use this method since A9/MIUI 10 till now on A11/MIUI 12.6 and never had problems - see also my screenshot (Magisk installed, saying No Ramdisk but I installed Magisk by patching boot img)
Also, if it won't work, just flash the original boot.img

wakram001 said:
My device has no ramdisk, A 10 miui 12.
I have already tried with boot image but magisk patched boot image not flash, it show error.
Thanks for reply...
Click to expand...
Click to collapse
What error?
Command for Fastboot flashing must be:
fastboot flash boot <patched-boot-img>
Try again and post the error screenshot
When patching, you must not tick Recovery option (since you are not patching Recovery)
You can read also discussion about patching boot img
(where the same has been asked and answered many times) for Xiaomi phones in the General Magisk Support thread on XDA
Edit:
You can also only temporarily (one time) boot to the patched boot img by:
fastboot boot <patched boot img>
(Observe that flash command is omitted)
Then if ok, flash it permanently
Btw, always make sure that Fastboot is properly connected:
fastboot devices

Btw, another similar thread - Mi 9T Pro (doesn't matter), MIUI 12, disbelief about patching boot.img (and possible bootloop with the solution, in case of previously installed Magisk modules):
Does patched boot.img Magisk work on MIUI V12.5.1.0? (Edit: Yes it does!)
Just curious if anyone has any insight as to whether I can use the Magisk app to patch the newest boot.img (12.5.1.0 global / Android 11 / mi9t pro) and whether it will go smoothly if I install it via fastboot flash boot patchedmagiskhere.img? I...
forum.xda-developers.com

Magisk patched boot image is working properly. Now I have rooted device.
Thanks.