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.
Related
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.
In this guide i will go over how to flash stock android 10 if you are unlocked after flashing installing magisk and disabling force encryption :-
THIS GUIDE HAS BEEN TWEAKED AND UPDATED FOR PIXEL EXPERIENCE TOO
HTML:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
THIS GUIDE IS ONLY FOR THOSE WHO HAVE UNLOCKED THEIR BOOTLOADER
Moving from Custom ROM to Stock 10 :- OR Flashing PE 10
First downlaod Stock 10 CLICK HERE OR Pe 10
Reboot to twrp
Wipe everything expect internal storage
Flash ROM Zip
>Now if You Want to be Encrypted you can skip to Formatting Data Step This is for whom you don't want to format and want to be decrypted
>Change Slot and Reboot To Bootloader
>Boot To Official TWRP Image
>Now Flash FBE Disabler (Normally Or Via ADB Sideload ) and Reboot
Now You have to Format Your Data (IMPORTANT IF YOU CHOOSE TO BEING ENCRYPTED)
Change Slot
Now Reboot
IMPORTANT DON'T TRY TO FLASH TWRP INSTALLER JUST AFTER FLAHING THE STOCK ROM OR ELSE YOU WILL NOT BE ABLE TO BOOT ROM IN PE YOU CAN FLASH TWRP INSTALLER BUT IT TWRP WON'T BOOT AS OUR TWRP ISN'T YET READY FOR FBE
IF YOU ARE ALREADY ON STOCK(ENCRYPTED) AND WANT TO INSTALL MAGISK OR WANT TO DECRYPT SO CAN USE TWRP AGAIN
Once you have installed Stock 10 via TWRP in a rush and later you find out nothing is working there no TWRP no magisk and thus you can't move to custom ROM now , well check this out now
STEPS TO ONLY INSTALL MAGISK WITHOUT ANY DECRYPTION
Downlaod pathced boot image from link CLICK HERE
Reboot to Fastboot
Now type this code
HTML:
fastboot flash boot magisk_patched.img
After Success message reboot normally
Now Install Magisk Manager (apk)
YOU ARE ROOTED !
STEPS TO INSTALL MAGISK REMOVE DECRYPTION AND USE TWRP (For Stock and Pixel Experience Both)
IN ORDER TO SWITCH TO OTHER CUSTOM ROMs WHICH AREN'T FORCE-ENCRYPTED YOU HAVE TO DECRYPT FIRST !
IF YOU ARE ALREADY MOVING TO A ENCRYPTED ROM THEN YOU DON'T HAVE TO DECRYPT .
Reboot to Fastboot
Now type this code
HTML:
fastboot -w
This will earse all your data and decrypt
Now wait don't reboot
Now downlaod TWRP image and place it in you platform folder
Now boot to TWRP using this code
HTML:
fastboot boot twrp.img
As soon as you are in twrp flash force encrypt disabler
After Flashing Disabler Flash Magisk and reboot
NOW YOU ARE ON STOCK WITH NO ENCRYPTION AND MAGISK INSTALLED!
IF JUST IN CASE YOU WANT TO MOVE TO CUSTOM ROMs JUST AFTER FORMAT DATA AND BOOTING TWRP STEP FLASH YOUR DESIRED ROM
RECOMMENDED TWRP :- XDA HERE
THANKS Zacktg5 for Zip
HIT THANKS:cyclops:
I followed "STEPS TO ONLY INSTALL MAGISK WITHOUT ANY DECRYPTION" and got a bootloop
Thank you man!
Coming from a custom ROM (PE 10), is it possible to flash the stock 10 using fastboot, or this will cause issues?
can't install miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip
Step 1/2
Error applying update: 7 (ErrorCode :: kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Error installing zip file /sdcard/miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
Zedsdeadbaby said:
I followed "STEPS TO ONLY INSTALL MAGISK WITHOUT ANY DECRYPTION" and got a bootloop
Click to expand...
Click to collapse
you can install miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip ?
why I got error ?
link to Universal DM-Verity, ForceEncrypt, Disk Quota Disablers in case someone asks: http://zackptg5.com/android.php#disverfe
XDA: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Great
Antusuprik said:
can't install miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip
Step 1/2
Error applying update: 7 (ErrorCode :: kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Error installing zip file /sdcard/miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
you can install miui_JASMINEGlobal_V11.0.4.0.QDIMIXM_545aa0d958_10.0.zip ?
why I got error ?
Click to expand...
Click to collapse
use some other twrp
I have flashed Android 10 ZIP in TWRP in slot A. After that i changed to slot B and restart to TWRP. In slot B i flashed Encryption Disabler zip and Magisk zip in order.
Same product, less steps
blackman01 said:
Downlaod pathced boot image from link CLICK HERE
HIT THANKS:cyclops:
Click to expand...
Click to collapse
Is this a December patched boot IMG?
d3rt0xx said:
I have flashed Android 10 ZIP in TWRP in slot A. After that i changed to slot B and restart to TWRP. In slot B i flashed Encryption Disabler zip and Magisk zip in order.
Same product, less steps
Click to expand...
Click to collapse
Just the Android 10 ZIP or with the twrp zip? Didn't you lose twrp if you didn't flash the twrp zip?
Thufailb said:
Just the Android 10 ZIP or with the twrp zip? Didn't you lose twrp if you didn't flash the twrp zip?
Click to expand...
Click to collapse
Without TRWP installer. I reboot to bootloader after every single step and boot TWRP.img manually with fastboot boot TWRP.img
So stock recovery is preset
Step by step:
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img"
- Delete all partitions and be sure active boot slot is "A"
- Reboot to Bootloader, NOT Recovery
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img" again
- Install Android 10 zip
- Change active boot slot to "B"
- Reboot to Bootloader, NOT Recovery again
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img" again
- Flash Encryption Disabler zip
- Flash Magisk zip in order
- Reboot! Profit!
Fresh Android 10, decrypted and rooted with stock recovery :good:
Which recovery did you use tho?
Also does that recovery boot from stock android 9???
Please help,asap.
Guys, I have mi a2 on official pie and arb4. How to update?
Rupamxx said:
Which recovery did you use tho?
Also does that recovery boot from stock android 9???
Please help,asap.
Click to expand...
Click to collapse
Recent twrp.
Twrp boots from every version
d3rt0xx said:
Without TRWP installer. I reboot to bootloader after every single step and boot TWRP.img manually with fastboot boot TWRP.img
So stock recovery is preset
Step by step:
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img"
- Delete all partitions and be sure active boot slot is "A"
- Reboot to Bootloader, NOT Recovery
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img" again
- Install Android 10 zip
- Change active boot slot to "B"
- Reboot to Bootloader, NOT Recovery again
- Boot twrp.img in fastboot from PC "fastboot boot twrp.img" again
- Flash Encryption Disabler zip
- Flash Magisk zip in order
- Reboot! Profit!
Fresh Android 10, decrypted and rooted with stock recovery :good:
Click to expand...
Click to collapse
Hi, very helpful guide.
But how do you get OTA update when there's a new one? Can you provide the steps to get OTA and then get back to root. Thanks in advance.
disaster_peace said:
Hi, very helpful guide.
But how do you get OTA update when there's a new one? Can you provide the steps to get OTA and then get back to root. Thanks in advance.
Click to expand...
Click to collapse
Easy!
Just install normally via updater.
But before you restart your phone, install TWRP Retention Script via Magisk Manager to change active boot slot
can i skip installing magisk in this guide to get my banking apps working??
Sivakumar$ said:
can i skip installing magisk in this guide to get my banking apps working??
Click to expand...
Click to collapse
Yes, if you only install official OTA, banking apps work. Why not? Its official and unrooted
But decryption Script will useless without root i think
Im on derp fest Q rom now i want to go to stock 10 i cannot find any latest fastboot file and there is some issues with the mi flash tool as some users were reporting getting dev error
I'm tried using two versions of TWRP(3.2.3-0 and 3.3.1-0) and got two different errors:
• No digest file found (3.2.3-0)
• Error 7 (3.3.1-0)
What should I do? I don't have any ROM's installed
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
How do I get Magisk 21.0 to install through Magisk Manager?
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
CraigHardy said:
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
Click to expand...
Click to collapse
This is what I am getting after following your directions to a T!
I also flashed to both partitions. Please see attachments. I sent 2 screenshots.
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
CraigHardy said:
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
Click to expand...
Click to collapse
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Doesn't work. Download the patched image, put it on the phone, use magisk canary manager to patch it again, transfer it off your phone, then boot into Fastboot and flash it.
It has to be patched in the phone it will be installed to otherwise it will not work.
akinkoff85 said:
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Click to expand...
Click to collapse
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Here is the exact size.
Problem uploading image
I am a little confused now... I uninstalled root for a few days and now have the second release of android 11... I am in fastboot mode doing fastboot flash boot... then the file name and all it says is waiting for device?? Any help??
dladz said:
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Click to expand...
Click to collapse
Indeed, using the beta version worked for me! Thanks for the tip!
imval said:
Indeed, using the beta version worked for me! Thanks for the tip!
Click to expand...
Click to collapse
No worries man, glad you're sorted
CraigHardy said:
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
Click to expand...
Click to collapse
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
rodken said:
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
akinkoff85 said:
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Click to expand...
Click to collapse
Watch this video it helped me out allot
dladz said:
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
Click to expand...
Click to collapse
I did not know that one can just boot a magisk_patched.img instead of flashing.
rodken said:
I did not know that one can just boot a magisk_patched.img instead of flashing.
Click to expand...
Click to collapse
It's preferable.
There are some things to note.
1st. You are only booting it, meaning if you reboot; you will start using the installed / flashed image and the booted image will be lost.
2nd. For the above reason. If you want to make root permanent you have to open magisk after opening and then click install - install directly.
As magisk will already have root access, it will be able to accomplish patching, if you tried this whilst unrooted it would fail, or not be an option.
3rd. By booting you avoid the potential bootloop problems you can and almost will have at some point if you always flash, bad images are pretty rife for a number of reasons.
I've got a large guide for rooting in the guides section which covers all the bases and their shortcomings /benefits.
This works both ways on Sailfish & Marlin
TWRP 3.5.1_9-0 as Recovery Ramdisk can now co-exist with Magisk! Yey!
The twrp-installer-3.5.1_9-0-marlin.zip is still unable to boot back to recovery after flashing. But as long as you flash twrp-3.5.1_9-0-marlin.img as Recovery Ramdisk, then you're okay.
Note: Download first twrp-3.5.1_9-0-marlin.img from twrp.me and save it to your preferred download location.
You need to boot TWRP from bootloader by typing "fastboot boot twrp.img". After TWRP loads up, go to "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk".
After that reboot back to recovery then flash Magisk-v22.0.apk & viola!
edwaine said:
This works both ways on Sailfish & Marlin
TWRP 3.5.1_9-0 as Recovery Ramdisk can now co-exist with Magisk! Yey!
The twrp-installer-3.5.1_9-0-marlin.zip is still unable to boot back to recovery after flashing. But as long as you flash twrp-3.5.1_9-0-marlin.img as Recovery Ramdisk, then you're okay.
Note: Download first twrp-3.5.1_9-0-marlin.img from twrp.me and save it to your preferred download location.
You need to boot TWRP from bootloader by typing "fastboot boot twrp.img". After TWRP loads up, go to "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk".
After that reboot back to recovery then flash Magisk-v22.0.apk & viola!
Click to expand...
Click to collapse
The title says Android 11; will this work with Android 10? I tried on LineageOS 17.1 (Android 10) and TWRP said the image was too large but I already had Magisk 22 installed.
Perhaps: 1) Install LineageOS 17.1 weekly update with Options/Update/Updater
2) Boot into Lineage recovery to change slots
3) Reboot into bootloader
4) fastboot boot twrp-3.5.1_9-0-marlin.img
5) As OP said, "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk"
6) Reboot into recovery (may not be needed?)
7) Flash Magisk-v22.0.apk (renamed to Magisk-v22.0.zip)
8) Reboot system & violin!
I've been trying to get TWRP and Magisk installed without having to use another computer to go into fastboot and flash the image. There may be a way to use the Magisk TWRP A/B retention script. This at least tells me why using TWRP 3.5.2_9-0-marlin.img to install the TWRP zip file would never reboot into recovery. Thanks.
lichan said:
The title says Android 11; will this work with Android 10? I tried on LineageOS 17.1 (Android 10) and TWRP said the image was too large but I already had Magisk 22 installed.
Perhaps: 1) Install LineageOS 17.1 weekly update with Options/Update/Updater
2) Boot into Lineage recovery to change slots
3) Reboot into bootloader
4) fastboot boot twrp-3.5.1_9-0-marlin.img
5) As OP said, "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk"
6) Reboot into recovery (may not be needed?)
7) Flash Magisk-v22.0.apk (renamed to Magisk-v22.0.zip)
8) Reboot system & violin!
I've been trying to get TWRP and Magisk installed without having to use another computer to go into fastboot and flash the image. There may be a way to use the Magisk TWRP A/B retention script. This at least tells me why using TWRP 3.5.2_9-0-marlin.img to install the TWRP zip file would never reboot into recovery. Thanks.
Click to expand...
Click to collapse
Youre free to try the steps. I only confirmed it on Android 11 because I'm already using Pixel Experience 11 Plus. You really need to repartition before TWRP can fit to your Phone.
edwaine said:
Youre free to try the steps. I only confirmed it on Android 11 because I'm already using Pixel Experience 11 Plus. You really need to repartition before TWRP can fit to your Phone.
Click to expand...
Click to collapse
Thanks, I'll check into the repartitioning.
edwaine said:
Youre free to try the steps. I only confirmed it on Android 11 because I'm already using Pixel Experience 11 Plus. You really need to repartition before TWRP can fit to your Phone.
Click to expand...
Click to collapse
What's the difference between PE and stock pixel rom? aren't they the same?
X4c3 said:
What's the difference between PE and stock pixel rom? aren't they the same?
Click to expand...
Click to collapse
Same. But with added features on Pixel Experience 11 Plus
edwaine said:
Same. But with added features on Pixel Experience 11 Plus
Click to expand...
Click to collapse
You own Cherry Mobile G1(seed/crackling), are you from Philippines? where did you buy your Pixel XL with unlocked boot loader?
edwaine said:
This works both ways on Sailfish & Marlin
TWRP 3.5.1_9-0 as Recovery Ramdisk can now co-exist with Magisk! Yey!
The twrp-installer-3.5.1_9-0-marlin.zip is still unable to boot back to recovery after flashing. But as long as you flash twrp-3.5.1_9-0-marlin.img as Recovery Ramdisk, then you're okay.
Note: Download first twrp-3.5.1_9-0-marlin.img from twrp.me and save it to your preferred download location.
You need to boot TWRP from bootloader by typing "fastboot boot twrp.img". After TWRP loads up, go to "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk".
After that reboot back to recovery then flash Magisk-v22.0.apk & viola!
Click to expand...
Click to collapse
I can confirm that this works on the Pixel 2 XL (taimen). I just tested it with twrp-3.5.2_9-0-taimen.img and Magisk-v23.0 with Havoc-OS v4.6 (Android 11).
No go for me. Not sure why my pixel xl gen 1 refusing to boot to any twrp when flashed but 3.3.0.0. I can command line boot fastboot to the latest fine though.
Hello!
I want to root a degoogleifyed Pixel 3a on LineageOS 17.1 using Magisk, but I'm not sure to understand which boot.img use for this.
For an other phone, I found the boot.img in the last nightly build on lineageosroms.com. The sargo one don't seem to contain it.
I've already read some how to (like this one), but I would like to have confirmation that it apply to LineageOS. Could some confirm that I should:
1. download the boot.img directly from Google
2. patch it with Magisk
3. reboot into fastboot mode
4. flash the phone with command:
fastboot flash boot /path/to/magisk_patched.img
Sorry in advance if the answer seems obvious. My English is not very good and I start with these manipulations, so I'm a little afraid of miss something.
_yoxd said:
Hello!
I want to root a degoogleifyed Pixel 3a on LineageOS 17.1 using Magisk, but I'm not sure to understand which boot.img use for this.
For an other phone, I found the boot.img in the last nightly build on lineageosroms.com. The sargo one don't seem to contain it.
I've already read some how to (like this one), but I would like to have confirmation that it apply to LineageOS. Could some confirm that I should:
1. download the boot.img directly from Google
2. patch it with Magisk
3. reboot into fastboot mode
4. flash the phone with command:
fastboot flash boot /path/to/magisk_patched.img
Sorry in advance if the answer seems obvious. My English is not very good and I start with these manipulations, so I'm a little afraid of miss something.
Click to expand...
Click to collapse
The boot.img is in the firmware but must be extracted to get to it. Since it is different than stock, you should use it, if needed. I can get it for you later. This wasn't zipped, just renamed by afding .zip to the end so it would upload.
Thank you Tulsadiver! Your answer helped me to understand what to do.
In case it could help someone else, that's what I did:
1. download the last nightly build on https://download.lineageos.org/sargo
2. unzip it
3. dump the boot.img from the payload.bin using this guide (if you use Linux)
4. patch the boot.img with Magisk
5. reboot the phone into fastboot mode:
adb reboot fastboot
6. flash the phone with commands:
fastboot flash boot magisk_patched.img
fastboot flash boot_b magisk_patched.img
The phone is now rooted!
I installed Lineage and rooted it last night. I followed the instructions and patched the stock boot.img from Google. Boy was that mistake! My digitizer stopped working. I then patched the Lineage RECOVERY image from the Lineage website. Now my phone is rooted perfectly!
ackliph said:
I installed Lineage and rooted it last night. I followed the instructions and patched the stock boot.img from Google. Boy was that mistake! My digitizer stopped working. I then patched the Lineage RECOVERY image from the Lineage website. Now my phone is rooted perfectly!
Click to expand...
Click to collapse
Roger that. Download the Lineage recovery image that's dated same as the Lineage rom build you are using and patch it using magisk manager and flash to boot partition. sudo fastboot flash boot lineage-18.1-2021xxxx.recovery.img --slot all (enter) You should be good then. Both boot and recovery sort of reside in the same place (boot) as there is no longer a recovery partition on A/B partition devices and everything nowadays that's Android is A/B partition. Works for me on my Pixels.