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! ?

How to root L29C432B584, if not how to downgrade back to B581? Please HELP!

Hello. I had B584 rooted and tried to update to B584 via huRupdater. The phone didn´t ipdate but the phone had lost the root, then I updated it to B584 via OTA. Now I see that there is not a root for B584.
Someone can help me with this problem or how I can downgrade to B581.
Thank you.

Download L29C432B584's update.zip.
Extract zip with zip tool.
Extract ramdisk.img from Update.app file with huawei update extractor tool.
Patch L29C432B584's ramdisk.img with magiskmanager.
Boot in bootloader mode.
Flash via fastboot the patched L29C432B584's ramdisk.img to device's ramdisk partition.
Boot in normal mode, configure magisk manager and you're rooted !

oslo83 said:
Download L29C432B584's update.zip.
Extract zip with zip tool.
Extract ramdisk.img from Update.app file with huawei update extractor tool.
Patch L29C432B584's ramdisk.img with magiskmanager.
Boot in bootloader mode.
Flash via fastboot the patched L29C432B584's ramdisk.img to device's ramdisk partition.
Boot in normal mode, configure magisk manager and you're rooted !
Click to expand...
Click to collapse
Is the only way? Very complicated. I´ll try but...

oslo83 said:
Download L29C432B584's update.zip.
Extract zip with zip tool.
Extract ramdisk.img from Update.app file with huawei update extractor tool.
Patch L29C432B584's ramdisk.img with magiskmanager.
Boot in bootloader mode.
Flash via fastboot the patched L29C432B584's ramdisk.img to device's ramdisk partition.
Boot in normal mode, configure magisk manager and you're rooted !
Click to expand...
Click to collapse
It was method 1.
Here is method 2, fat more easy:
Boot in TWRP recovery mode.
Install latest magisk.zip via TWRP.
Boot in normal mode, configure magisk manager and you're rooted !

It´s imposible.

oslo83 said:
It was method 1.
Here is method 2, fat more easy:
Boot in TWRP recovery mode.
Install latest magisk.zip via TWRP.
Boot in normal mode, configure magisk manager and you're rooted !
Click to expand...
Click to collapse
Two days later I maid it. It was awful but I made it.

natispain said:
Two days later I maid it. It was awful but I made it.
Click to expand...
Click to collapse
Congratulations !
Which method did you used ?
-Be warned that magisk 17.3 was pulled off just after today release because causing problems or not working, so just use 17.2 for now.

hi all, I have a problem ..
i get everytime with TWRP the message : Process Updater error 1 , Failed to install zip @natispain which TWRP image are you using ?

natispain said:
... or how I can downgrade to B581.
Thank you.
Click to expand...
Click to collapse
see here -> https://forum.xda-developers.com/mate-8/help/mate-8-nxt-l29c432-584-return-to-582-how-t3857999

Failing to write twrp? Picture Links Included Please Help

Hi got a p smart phone got all the files correct twrp everything needed i can find the fastboot device but it says this on fastboot flash recovery.img or using the correct flash tool
Failing write IMG
http://i65.tinypic.com/r0vaiw.jpg
Guide I Used
http://i63.tinypic.com/2psexvs.jpg
When I use the root guide I cannot get a install of magisk files only the magisk manager I have downloaded the latest magisk?
Can someone layman term all this please

It seems to me thst your bootloader needs to be unlocked.. Did u check that?

Message of dm-verity on TWRP Recovery website

I'm using android Pie(stock rom) on mi a1. I want to flash Lineageos for microG. On TWRP Recovery website, it says this device(mi a1-tissot) uses dm-verity and in order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in fastboot.
I'm completely new in the realm of flashing custom roms. And no website and youtube video talks about dm-verity in a clear manner:crying:. So what steps exactly should I follow to install Lineageos for microG?
Also, my phone(data) is encrypted. And I can't find a way to decrypt it. Will it affect flashing TWRP Recovery or Lineageos?

wHY did not anybody answer guys?

Here are the steps to install TWRP and maybe a custom ROM:
1.Make sure to have USB Debugging activated
2.Put the Mi A1 in Fastboot Mode(Volume Down+Power)
3.Connect your phone to your PC
4.Make sure to have downloaded platform-tools
5.Download the .img TWRP file and copy it in the platform-tools folder
6.Hold Shift and right Click in the platform-tools folder,and click onpen a PowerShell window here
7.Type fastboot devices or .\fastboot devices(for me the second worked)
8.Now write fastboot boot twrp.xx.xx.xx.img(here Goes the name of your .img TWRP file)
9.After 15 seconds,you will probably see a warning that asks You to swipe to allow modifications.Don't swipe.Press on:Keep read only.
10.From this point,You can install every custom ROM,You can install Magisk.
Hope this helped You out!

TheAlmigthyOne said:
Here are the steps to install TWRP and maybe a custom ROM:
1.Make sure to have USB Debugging activated
2.Put the Mi A1 in Fastboot Mode(Volume Down+Power)
3.Connect your phone to your PC
4.Make sure to have downloaded platform-tools
5.Download the .img TWRP file and copy it in the platform-tools folder
6.Hold Shift and right Click in the platform-tools folder,and click onpen a PowerShell window here
7.Type fastboot devices or .\fastboot devices(for me the second worked)
8.Now write fastboot boot twrp.xx.xx.xx.img(here Goes the name of your .img TWRP file)
9.After 15 seconds,you will probably see a warning that asks You to swipe to allow modifications.Don't swipe.Press on:Keep read only.
10.From this point,You can install every custom ROM,You can install Magisk.
Hope this helped You out!
Click to expand...
Click to collapse
I found this thread by doing something wrong that you mentioned. I didn't swipe to allow modifications and now the TWRP can't flash anything. Tried every remedy I can find but nothing. It can wipe system though, but not restore it so now I'm stuck in bootloops. Damn, idk what to do.

Dear Zentom,for me,that method worked.But,I can help you get out of that situation
1.Make sure to have your bootloader unlocked
2.Download the stock ROM for Mi A1
3.Boot into Fastboot Mode
4.Extract the stock ROM archive
5.Copy all the extracted files into the platform-tools folder
6.Find a .bat file names "flash-all"
7.Open it
8.After 15 minutes or so,your phone will boot.
Hope I helped you!

TheAlmigthyOne said:
Dear Zentom,for me,that method worked.But,I can help you get out of that situation
1.Make sure to have your bootloader unlocked
2.Download the stock ROM for Mi A1
3.Boot into Fastboot Mode
4.Extract the stock ROM archive
5.Copy all the extracted files into the platform-tools folder
6.Find a .bat file names "flash-all"
7.Open it
8.After 15 minutes or so,your phone will boot.
Hope I helped you!
Click to expand...
Click to collapse
Thanks, but I flashed the stock rom from twrp anyway. Though I had to flash the October 2019 ROM. Do you know anywhere where one can get an updated one?

If You want the latest stock ROM,this is:https://drive.google.com/file/d/1yVWv4hiTSk-3zai-4u2c2OcLpRdFL_J6/view

Is it possible to root OOS 10.0.1?

lately I did a clean install of OOS 10.0.1 on my International 6t. Installed OOS and magisk from TWRP.
After booting there was a Magisk Manager in applications claiming that Magisk itself was not installed. I tried to install Magisk from Manager, but failed. Then I reboot the phone into the recovery and TWRP was gone!! There was only a stock recovery. Well, I tried to run TWRP from computer with 'fastboot boot .\twrp-3.3.1-28-fajita-Q-mauronofrio.img'. Error - "remote: unknown command".
I searched forum and found a thread fastboot boot twrp.img FAILED (remote: unknown command). @dbarrett480 wrote: 'Twrp can't flash anything to system in A10 right now, so unless that is fixed there is no point at this moment anyway. A10 uses a virtualized system partition which doesn't allow R/W access to system....'. Does it mean that rooting is not possible with stock OOS and only possible solution is to use custom ROM?

It is. Look for the patched boot.img and flash that through fastboot. Make sure to install magisk manager first.

BesoC said:
Well, I tried to run TWRP from computer with 'fastboot boot .\twrp-3.3.1-28-fajita-Q-mauronofrio.img'. Error - "remote: unknown command".
I searched forum and found a thread fastboot boot twrp.img FAILED (remote: unknown command). @dbarrett480 wrote: 'Twrp can't flash anything to system in A10 right now, so unless that is fixed there is no point at this moment anyway. A10 uses a virtualized system partition which doesn't allow R/W access to system....'. Does it mean that rooting is not possible with stock OOS and only possible solution is to use custom ROM?
Click to expand...
Click to collapse
The information you found is outdated. I'm surprised you didn't properly read through the official TWRP thread here, more specifically this post clarifies the error in your use of fastboot (or better said: the use of fastboot according to the mistakes made by OnePlus). Which is also mentioned several times in the page you linked to.
As a senior member, please don't create new threads inquiring information you could easily find. Even though the methods to obtain it have been challenging for a short while, being able to achieve root has never been interrupted for this device. Even without being able to modify system files. Systemless rules!
Wrapped with delicious Fajita [emoji896]

bokkoman said:
It is. Look for the patched boot.img and flash that through fastboot. Make sure to install magisk manager first.
Click to expand...
Click to collapse
So, should do following:
Install Magisk Manager
Flash patched boot.img through fastboot
Install TWRP
Install Magisk
Is it correct?

The patched boot.img already contains magisk.
But you don't need twrp to be rooted, unless you really want to use it for something else... But i don't use it anymore. So I'm fully stock, except that I'm unlocked and rooted.
So it should be:
1. Install magisk manager.
2. Flash boot.img
3. Enjoy. But check magisk manager if it was successful.

bokkoman said:
The patched boot.img already contains magisk.
But you don't need twrp to be rooted, unless you really want to use it for something else... But i don't use it anymore. So I'm fully stock, except that I'm unlocked and rooted.
So it should be:
1. Install magisk manager.
2. Flash boot.img
3. Enjoy. But check magisk manager if it was successful.
Click to expand...
Click to collapse
Regarding all that was said here, is rooting possible by following these steps?
Reboot
Fastboot TWRP img
Use volume up to recovery and power button to boot to recovery
Flash 10.0.1 stock boot img from TWRP
Flash TWRP zip
Reboot to recovery
Flash Magisk 20.1
Flash kernel if want
Reboot system
Click to expand...
Click to collapse

BesoC said:
Regarding all that was said here, is rooting possible by following these steps?
Click to expand...
Click to collapse
Yes, this tutorial with the twrp should work ...

BesoC said:
Regarding all that was said here, is rooting possible by following these steps?
Click to expand...
Click to collapse
That's only if you need TWRP.
But for what I've been reading, you don't need TWRP and then i suggest to not install it.
Just flash everything stock and keep it that way. Only thing to flash is the patched boot.img with root in it.
You can always update Android from the settings and patch/install boot with magisk manager on inactive slot. This will keep your device rooted without the need of TWRP.

Here what I found:
https://forum.xda-developers.com/showpost.php?p=81111389&postcount=145
Today I installed the new update, 10.0.1 for OP 6T and then I discovered that there is no magisk patched boot.img yet. I extracted it with payload dumper, patched with the installed magisk and flashed successfully.
I uploaded it to my drive for others. https://drive.google.com/open?id=1kb...VgWNaWgLN6j17b
The commands for flashing are:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Maybe someone can add it to the first post.
original 10.0.1 boot.img https://drive.google.com/open?id=1HP...Du8zCOFMXInjXq
Click to expand...
Click to collapse

I used this method to root 10.0.01
https://forum.xda-developers.com/oneplus-6t/how-to/ultimateguide-t4004367
I went from rooted 9.0.17 to 10 to 10.0.01
Never had an issue and everything works fine for me.

Today I installed the new update, 10.0.1 for OP 6T and then I discovered that there is no magisk patched boot.img yet. I extracted it with payload dumper, patched with the installed magisk and flashed successfully.
I uploaded it to my drive for others. https://drive.google.com/open?id=1kb...VgWNaWgLN6j17b
The commands for flashing are:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Maybe someone can add it to the first post.
original 10.0.1 boot.img https://drive.google.com/open?id=1HP...Du8zCOFMXInjXq
Click to expand...
Click to collapse
My phone get stuck on the boot animation by following this guide. I have not factory reset my phone.

DrXperience said:
My phone get stuck on the boot animation by following this guide. I have not factory reset my phone.
Click to expand...
Click to collapse
I still don't get why people don't use the good old way:
fastboot flash boot twrp.img (latest version)
If you just need root use twrp to flash Magisk zip
If you need twrp flash twrp installer also
Reboot
All the mess before was because we didn't have a working TWRP! Now that we have it don't need to use patched boot img made by others.