Related
I've checked the forum beforehand to see if there's a way to root, and yeh, there is, but a lot of them say "XT1944-2 and XT1944-4 only" but mine is XT1944-3 and honestly I'm afraid i'll ruin my phone, I've been rooting my phones since 2014ish but this has to be the most complicated phone I'd ever have to deal with, I love it the way it is but I just miss root and xposed a lot, please
andienchancer said:
I've checked the forum beforehand to see if there's a way to root, and yeh, there is, but a lot of them say "XT1944-2 and XT1944-4 only" but mine is XT1944-3 and honestly I'm afraid i'll ruin my phone, I've been rooting my phones since 2014ish but this has to be the most complicated phone I'd ever have to deal with, I love it the way it is but I just miss root and xposed a lot, please
Click to expand...
Click to collapse
Try this -- even in the event it doesn't work, it is virtually completely safe and runs no risk of bricking your device. First, of course, you will need to unlock your device's bootloader. If you haven't already done so, let me know and I can provide you some guidance. Visit this link for instructions and support on unlocking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Next, download a recent firmware package for your device. You can find one at http://mirrors.lolinet.com. Extract the boot.img file from the package and save it to your device. On your device, download the Magisk Manager application. Select install, then select the "Patch Boot Image" option, and navigate to the saved boot.img file. Once Magisk patches your boot image, save the patched image to your PC or laptop in your adb/fastboot directory (assuming you have adb/fastboot set up on your PC. If not, see my link at the end of this post to download it. Also, if you haven't done so, install the latest Motorola Device Manager on your PC from Motorola's official website. It will ensure that current USB device drivers are installed on your PC/laptop. Visit this link to download the latest version: https://support.motorola.com/us/en/solution/MS88481 ). Now boot your device into fastboot mode, connect your device to your PC, open a command window in your adb/fastboot path, and execute this command:
fastboot devices
If you are properly connected, an alphanumeric string will be returned via the command window, which is your device serial number. Now execute these fastboot commands:
fastboot flash boot patched_boot.img
fastboot reboot
** NOTE: It is completely normal for your device to boot loop a couple of times during the initial boot sequence. This shouldn't occur during the second and subsequent boots.
Upon reboot, open the Magisk Manager app again and you should have systemless root installed. If, however, anything goes south and you get stuck in a boot loop, you can always save face by flashing the stock boot image from the firmware package by:
fastboot flash boot boot.img
fastboot reboot
This exact method has been confirmed to achieve systemless root on a number of the Moto E5, E5 Plus & E5 Play variants, without the need for installing TWRP custom recovery. In essence, if your device has an unlockable bootloader, this should work.
Minimal ADB & Fastboot v1.4.3: https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk
It gives me bootloop, can I do it flashing twrp and the zip file?
reserved
Moto E5 XT1944-3 Nora solution
andienchancer said:
It gives me bootloop, can I do it flashing twrp and the zip file?
Click to expand...
Click to collapse
i can find solution in this post, just install twrp until, password encryption dont show.
LenovoTech said:
Try this -- even in the event it doesn't work, it is virtually completely safe and runs no risk of bricking your device. First, of course, you will need to unlock your device's bootloader. If you haven't already done so, let me know and I can provide you some guidance. Visit this link for instructions and support on unlocking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Next, download a recent firmware package for your device. You can find one at http://mirrors.lolinet.com. Extract the boot.img file from the package and save it to your device. On your device, download the Magisk Manager application. Select install, then select the "Patch Boot Image" option, and navigate to the saved boot.img file. Once Magisk patches your boot image, save the patched image to your PC or laptop in your adb/fastboot directory (assuming you have adb/fastboot set up on your PC. If not, see my link at the end of this post to download it. Also, if you haven't done so, install the latest Motorola Device Manager on your PC from Motorola's official website. It will ensure that current USB device drivers are installed on your PC/laptop. Visit this link to download the latest version: https://support.motorola.com/us/en/solution/MS88481 ). Now boot your device into fastboot mode, connect your device to your PC, open a command window in your adb/fastboot path, and execute this command:
fastboot devices
If you are properly connected, an alphanumeric string will be returned via the command window, which is your device serial number. Now execute these fastboot commands:
fastboot flash boot patched_boot.img
fastboot reboot
** NOTE: It is completely normal for your device to boot loop a couple of times during the initial boot sequence. This shouldn't occur during the second and subsequent boots.
Upon reboot, open the Magisk Manager app again and you should have systemless root installed. If, however, anything goes south and you get stuck in a boot loop, you can always save face by flashing the stock boot image from the firmware package by:
fastboot flash boot boot.img
fastboot reboot
This exact method has been confirmed to achieve systemless root on a number of the Moto E5, E5 Plus & E5 Play variants, without the need for installing TWRP custom recovery. In essence, if your device has an unlockable bootloader, this should work.
Minimal ADB & Fastboot v1.4.3: https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk
Click to expand...
Click to collapse
LenovoTech said:
Try this -- even in the event it doesn't work, it is virtually completely safe and runs no risk of bricking your device. First, of course, you will need to unlock your device's bootloader. If you haven't already done so, let me know and I can provide you some guidance. Visit this link for instructions and support on unlocking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Next, download a recent firmware package for your device. You can find one at http://mirrors.lolinet.com. Extract the boot.img file from the package and save it to your device. On your device, download the Magisk Manager application. Select install, then select the "Patch Boot Image" option, and navigate to the saved boot.img file. Once Magisk patches your boot image, save the patched image to your PC or laptop in your adb/fastboot directory (assuming you have adb/fastboot set up on your PC. If not, see my link at the end of this post to download it. Also, if you haven't done so, install the latest Motorola Device Manager on your PC from Motorola's official website. It will ensure that current USB device drivers are installed on your PC/laptop. Visit this link to download the latest version: https://support.motorola.com/us/en/solution/MS88481 ). Now boot your device into fastboot mode, connect your device to your PC, open a command window in your adb/fastboot path, and execute this command:
fastboot devices
If you are properly connected, an alphanumeric string will be returned via the command window, which is your device serial number. Now execute these fastboot commands:
fastboot flash boot patched_boot.img
fastboot reboot
** NOTE: It is completely normal for your device to boot loop a couple of times during the initial boot sequence. This shouldn't occur during the second and subsequent boots.
Upon reboot, open the Magisk Manager app again and you should have systemless root installed. If, however, anything goes south and you get stuck in a boot loop, you can always save face by flashing the stock boot image from the firmware package by:
fastboot flash boot boot.img
fastboot reboot
This exact method has been confirmed to achieve systemless root on a number of the Moto E5, E5 Plus & E5 Play variants, without the need for installing TWRP custom recovery. In essence, if your device has an unlockable bootloader, this should work.
Minimal ADB & Fastboot v1.4.3: https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk
Click to expand...
Click to collapse
I can confirm that the procedure works for Moto E5 Play XT1920-18.
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
Code:
- Device platform: arm64-v8a
- Existing zip found
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
maretodoric said:
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
Click to expand...
Click to collapse
I'm also getting same error how did you managed to find the solution...
maretodoric said:
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager.
[...]
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Click to expand...
Click to collapse
Similar problem here, but with Magisk 19.3.
Could you pass a link to patched boot image,you used? Can´t find it...
Thanks
I didn't download boot.img, it's best that you extract it yourself by using ADB.
Download adb software, there should be some tutorial here on forums how to find and get it (possibly https://forum.xda-developers.com/mi-a1/how-to/computer-setup-rooting-gcam-setup-t3731526) , but Windows 10 SHOULD natively have it (at least i did, i didn't have to install anything, already had ADB).
Now here comes the tricky part. I didn't remember this and i didn't write it down. When this happens again to me, i will be in huge .......
I'm sorry i can't help you, but try to google for info on how to extract boot.img from current installation using fastboot or adb.. not sure which, possibly fastboot.
Then you will have clean untouched boot.img from official repo. No need to wait for it to appear on xiaomi site.
If i find a tutorial, i will post it here. Please do the same if you find it before me.
GOT IT!!!
- Follow the previous tutorial if you do not have adb and fastboot, so you can install them. There should be plenty of tutorials how to install both of them
- After you installed it, download this version of TWRP https://dl.twrp.me/tissot/twrp-3.3.0-2-tissot.img.html to your desktop
- Connect your phone to your PC via USB cable
- Open command prompt (in Windows, hit CTRL+R then type in cmd)
- Change directory to desktop, for example type cd C:\Users\<username>\Desktop - replace "<username>" with your username ofcourse.
- Type adb reboot bootloader - it will boot to fastboot mode
- Once the phone is in fastboot mode, type fastboot boot twrp-3.3.0-2-tissot.img (keep cmd prompt open)
- It will boot into recovery, click on "Backup"
- Select "Boot"
- Click on Select Storage and there choose Internal Storage, click on OK
- Then on the bottom part of the screen, just swipe to right to extract boot.img (It should literally say "Swipe to Backup"). Pay attention to messages, it will display the directory where it will place the boot.img, but it will not be strictly named boot.img
- In my case, it's in Internal Storage/TWRP/BACKUPS/00bf23cc0904/2019-06-20-14-25-3_PKQ1/boot.emmc.win
You can either rename it to boot.img or just leave that name. But either way, open new magisk manager, select "Install" next to Magisk (not magisk manager), click on "Select and Patch a file", point to your new boot.img or boot.emmc.win.
Magisk will patch that image and show you the new location. Just download that file to your PC, on desktop, cmd again "adb reboot bootloader", and when it gets to fastboot mode, type "fastboot flash boot magisk_patched.img".
You should be good to go!
Usage:
Code:
fastboot boot 10.3.0_HD01AA_magisk_patched.img
Then install Magisk Manager apk from here
Connect phone to wifi and open Magisk Manager app (this may requires a reboot, re-do fastboot boot magisk patched image again) touch in "INSTALL" text button (near "Magisk is not installed" message)
Phone will reboot, thats it.
10.3.0_HD01AA_magisk_patched.img
10.3.0_HD01AA_stock_boot.img
mekato said:
Usage:
Then install Magisk Manager apk from here
Connect phone to wifi and open Magisk Manager app (this may requires a reboot, re-do fastboot boot magisk patched image again) touch in "INSTALL" text button (near "Magisk is not installed" message)
Phone will reboot, thats it.
10.3.0_HD01AA_magisk_patched.img
10.3.0_HD01AA_stock_boot.img
Click to expand...
Click to collapse
Or just install magisk manager first.
Enable advanced reboot in developer options
Make sure you have adb fastboot tools installed and have patched image in that folder
Reboot to bootloader
Open cmd line to fastboot adb files
use the command "fastboot flash boot magisk patched.img"
Use command "fastboot reboot"
Done
How do i remove magisk root and use stock boot.img ? Every time i flash '10.3.0_HD01AA_stock_boot.img' it and try to lock bootloader it gives me error and says phone is not reliable and broke etc.
I want to remove annoying bootloader is unlocked screen at startup but i cant i want to go back stock and locked bootloader but still cant
Fixed: Problem solved. Download Oxygen Updater from Play store and enable advanced settings and download latest firmware for your device and update restart done.
please sir, where can i get patched boot image for 1.0.07?
ums1405 said:
please sir, where can i get patched boot image for 1.0.07?
Click to expand...
Click to collapse
Waiting for it as well...
there is Patched for 10.3.6 HD01AA
Well, a lot of people wanting to root global miui 11.0.7 and not being able to... So I did it on my Global redmi 7a - MIUI 11.0.7 Global.
Simple though. Apart from whats being said, u can update Magisk to v20.+ after flashing
the 19 version, through the app Magisk Manager automatically installed after flashing.
Prerequisites & Downloads:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- ADB and Fastboot -> I did on windows version, maybe can be done on linux...
- patched boot.img for miui 11.0.7 global
- vbmeta.img
- Magisk v19.3 zip -> place it on the root of your external sdcard
This is basically copied from cg730620's post [Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie] and Avedroid's vid
1 - Unlock bootloader and flash stock miui 11.0.7 recovery rom, using miflash 2017
CAREFUL! On the lower right corner check the first option, "clean all", or you may end up with a locked bootloader.
-> exactly the same from the quoted post from now on, what differs is the files and we are only flashing magisk v19.3
"2. Install Minimal ADB and Fastboot
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in Program Files (x86)/Minimal ADB and Fastboot/ folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
Code:
fastboot flash boot boot.img
Code:
Code:
fastboot flash vbmeta vbmeta.img
Code:
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
Reboot to system, open Magisk, update and there u go.
Same steps of the beginning of Avedroid's video, only with modified boot.img and Magisk Version
https://www.youtube.com/watch?v=NSs08O6uGVI&t=324s
After 16:30 of the video he flashes a custom gsi rom which is not of the interest of this thread, just flash magisk.
Thanks to all who made it possible, especially Avedroid and cg730620
Post questions and answers here, please, NOT in PM.
Good luck!
Thank's it's work fine on custom gsi too, i just flash patch boot, vbmeta, finally install magisk success
I did everything right, however, when it came to installing Magisk, the following error occurred: "Updater process ended with ERROR: 1".
So I redid the whole process, but before installing Magisk I did the following: I went to Mount, I deselected the System partition and after that the installation proceeded normally.
Well, I don’t know if this is the best way to fix this problem, I don’t understand much of these things, but it ended up working for me.
Thanks for the post
I will do some tests to see if everything is working.
Can I just do this on MIUI 11.0.5 Global?
Omborkar said:
Can I just do this on MIUI 11.0.5 Global?
Click to expand...
Click to collapse
Download patched boot.img for ur rom instead of 11.0.7 boot.img I uploaded. Or patch it yourself.
I have a problem. Everytime I do the wipe it says only: "Failed to mount "vendor"(invalid argument)"
What to do?
Google play not certified... after flashing and installed magisk... Got solution??? Thanks
I've rooted my MoKee OS Android 10 rom. Can somebody help me change the system font? The font changer module in Magisk is not appearing in the search bar.
vincecabalan said:
I've rooted my MoKee OS Android 10 rom. Can somebody help me change the system font? The font changer module in Magisk is not appearing in the search bar.
Click to expand...
Click to collapse
I Tried To Root Mokee But Failed. Can You Please Tell Me How You Root Mokee
Hello, what files do I need to rename to boot.img and recovery.img? I'm lost
3. Rename the patched boot file to boot.img
4. Rename the custom recovery to recovery.img
RsAbubokor4 said:
I Tried To Root Mokee But Failed. Can You Please Tell Me How You Root Mokee
Click to expand...
Click to collapse
Extract boot.img of installer mokee.zip Patch boot image https://patcher.yaalex.xyz/ select include magisk Expect to do uploud after downloading rename boot.img sdcard Go twrp flash boot install magisk manager apk
Credit to @idcamper
vincecabalan said:
Extract boot.img of installer mokee.zip Patch boot image https://patcher.yaalex.xyz/ select include magisk Expect to do uploud after downloading rename boot.img sdcard Go twrp flash boot install magisk manager apk
Credit to @idcamper
Click to expand...
Click to collapse
I did according to this advice, uploaded boot.img to this site. Magisk works, but Wifi won't work . When I uploaded boot.img, Wifi works, then it shows that Magisk is not installed, but it was installed.
speed_cars said:
I did according to this advice, uploaded boot.img to this site. Magisk works, but Wifi won't work . When I uploaded boot.img, Wifi works, then it shows that Magisk is not installed, but it was installed.
Click to expand...
Click to collapse
try this process after flash zip of the last magisk from reset factory
Can i do this on miui 11.0.3.0 indian rom based on Android 10. If yes then i need recovery.img pls help.
4. Rename custom recovery file to recovery.img
- where i can download this?, or this is the outcome of step 1?
Everything works fine, exept password. When i set new password, let's say it is 1234, i set the password in the setting, then i press the power button for lock screen, i put the password in as usual, but it just says try again over and over, im pretty sure that it is not my fault. Thanks for reply.
Anyone have patched boot 11.0.4?
jurubebaamarga said:
Well, a lot of people wanting to root global miui 11.0.7 and not being able to... So I did it on my Global redmi 7a - MIUI 11.0.7 Global.
Simple though. Apart from whats being said, u can update Magisk to v20.+ after flashing
the 19 version, through the app Magisk Manager automatically installed after flashing.
Prerequisites & Downloads:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- ADB and Fastboot -> I did on windows version, maybe can be done on linux...
- patched boot.img for miui 11.0.7 global
- vbmeta.img
- Magisk v19.3 zip -> place it on the root of your external sdcard
This is basically copied from cg730620's post [Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie] and Avedroid's vid
1 - Unlock bootloader and flash stock miui 11.0.7 recovery rom, using miflash 2017
CAREFUL! On the lower right corner check the first option, "clean all", or you may end up with a locked bootloader.
-> exactly the same from the quoted post from now on, what differs is the files and we are only flashing magisk v19.3
"2. Install Minimal ADB and Fastboot
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in Program Files (x86)/Minimal ADB and Fastboot/ folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
Code:
fastboot flash boot boot.img
Code:
Code:
fastboot flash vbmeta vbmeta.img
Code:
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
Reboot to system, open Magisk, update and there u go.
Same steps of the beginning of Avedroid's video, only with modified boot.img and Magisk Version
After 16:30 of the video he flashes a custom gsi rom which is not of the interest of this thread, just flash magisk.
Thanks to all who made it possible, especially Avedroid and cg730620
Post questions and answers here, please, NOT in PM.
Good luck!
Click to expand...
Click to collapse
I wish to obtain root / access to magisk,
Wanting to know if I can do this without losing data (having to delete system data)
Thank you
Hello.
So I was trying to root my Redmi 7A - v10.2.1 with TWRP 3.3.1 but now I am stuck in a bootloop.
What I did:
1. Flash boot.img
2. Flash recovery.img
3. Flash vbmeta.img
4. reboot
Phone rebooted to system and TWRP was installed.
Then I booted to TWRP to install Magisk-v23.0.zip,
I went to Advanced Wipe, then wiped 'Dalvik / ART cache', 'System', 'Data', 'Cache'.
When I rebooted, it went into a bootloop, when I go to TWRP it says 'No OS INSTALLED".
What did I do wrong? And how to recover?
Thanks.
Cinox said:
I did everything right, however, when it came to installing Magisk, the following error occurred: "Updater process ended with ERROR: 1".
So I redid the whole process, but before installing Magisk I did the following: I went to Mount, I deselected the System partition and after that the installation proceeded normally.
Well, I don’t know if this is the best way to fix this problem, I don’t understand much of these things, but it ended up working for me.
Thanks for the post
I will do some tests to see if everything is working.
Click to expand...
Click to collapse
Im also getting the same error,, but what do you mean by "deselected the System partition". I see "system_root" in Mount but not "System"
H there,
TWRP and Magisk are not wot working as aspected.
First I tried to flash TWRP by
Code:
fastboot flash recovery recovery.img
but received
Code:
(bootloader) Invalid partition name recovery
So I had to just boot it
Code:
fastboot boot recovery.img
After that I "installed recory image" in TWRP itself. But when I try to boot into recovery it get stuck. So i had to do
Code:
fastboot boot recovery.img
again.
Any ideas what i did wrong or how to solve this?
Then I installed Magisk. To do that I had to drop an boot.img file, let the Magisk-App creates an pahteched version of it and than, back in bootloader
Code:
fastboot boot magisk_patched...img
Now i have root access. But when rebooting regularly the Magisk-App has no root and so all the other apps also not. So i had to boot that img again.
That CAN'T be the right way.
Thx in advance!
It's probably because you have A/B partitions on your device. To flash it successfully you'll need TWRP 3.5.0+. You can learn more about why is it so different from this XDA article.
You can check if your device supports A/B partitions through this app.
Follow this guide on how to flash it on A/B partitions, you can get TWRP from here (Beckham) or here (Addison).
Goodluck.