[GUIDE] Install Magisk on stock ROM - ZTE Axon 10 Pro Guides, News, & Discussion

My phone is A2020G, so the ROM version of the following instructions is for G only, but you can still try on A2020U (just notice the Android version).
I once flashed Magisk through TWRP on stock Pie ROM but caused freeze at the boot screen, even the same while patching the boot image. However, now I found that if you are at stock Q and R version, you can now successfully install Magisk by patching boot images.
The only problem is that there is no TWRP for the two versions of stock ROM (since the recovery was made into boot image), so be careful while installing modules.
My method is to use Axon 10 EDL Tool. Fastboot mode is unavailable for stock Pie and Q Bootloader, while R can but this fastboot cannot flash images. So we need to use the patched bootloader of EDL Tool to access the fastboot and flash the patched boot images, then recover to the original bootloader so it can boot the system (The patched bootloader of EDL Tool can only boot stock Pie ROM).
Before proceeding:
Make sure you have updated to at least stock Q version and unlocked bootloader.
If you have not unlocked at Q or R, you can still proceed unlocking. The program will auto backup your current bootloader, however the patched bootloader cannot boot stock Q and R. So following these instructions:
1.Turn on the Developer Options and turn on OEM unlocking, remove your Google Account and lock screen passwords cause it will ask you to login after wiping because of FRP.
2.Boot into EDL Mode (If the phone is off, hold on pressing Vol+ and Vol- and then connect the cable; If the phone is on, connect the cable, then hold on pressing two Volume buttons and then press the power button for about 10 sec and the phone will automatically reboot)
3.Execute the EDL Tool with administrator rights.
4.Choose Unlock-Unlock bootloader
5.Follow the instructions, when the program has flashed (not backup) patched bootloader (Display "DONE", ask you to press any key), hit enter, and your phone will reboot immediately. When your phone vibrates, press both of the Vol+ and Vol- button immediately to boot into fastboot. (If you press in advance you will boot into EDL mode)
6.Open Command Prompt, use the fastboot.exe of the EDL Tool to proceed this command line:
Code:
fastboot flashing unlock
or just drag the program into CMD, like this:
Code:
D:\Axon10Pro_EDL_Tool\tools\fastboot.exe flashing unlock
7.Your phone will display the unlock warning, use volume button to select Yes and press power button to confirm.
8.After pressing power button (keep the cable connecting), press the two volume button immediately to boot into EDL mode, open the EDL Tool again and Restore bootloader from backup.
9.While restoring completed, reboot and hold on pressing Vol+ button to boot into recovery, the phone will automatically erase data and unlocking is done.
After unlocked:
1.Use djkuz's Axon 10 EDL Tool
2.Backup your boot image.
3.Copy your boot image to your phone and install Magisk Application.
4.Patch the two boot images (a/b), and remember the filename of the patched a and b boot.
5.Copy the patched boot images to your computer.
6.Use the EDL Tool to proceed unlocking, follow step 5 above to boot into fastboot.
7.Use the fastboot.exe of EDL Tool to flash patched boot images:
Code:
fastboot flash boot_a pta.img
fastboot flash boot_b ptb.img
(pta, ptb is the filename of your patched boot image)
8.Use volume button to select the green "START" and hit power button to reboot.
9.Follow step 8 above to recover bootloader, and you are done.
Problems:
Cannot use the default "Files" application to install local modules in stock R ROM cause it will possibly crash, so you have to install a third-party file manager application (like Root Explorer) to select modules. (When it open "Files" app, click the menu icon of the left side and select your installed file manager, then select modules to install)
Notes:
I can't find a way of checking which slot(A/B) of the phone has been on without using recovery, so I have to patch the two bootloaders. If you know, then you can patch and flash only that one.
I don't know if you can update to stock Q while unlocked at Pie when I saw this thread, but you can still upgrade to stock R while unlocked and installed Magisk at Q (V2.8). Just remember not to reboot immediately after you installed the upgrade, use the Magisk Application to install to another slot and then reboot.
Hope you enjoy~
Thanks to djkuz for developing the EDL Tool

willwongprd said:
My phone is A2020G, so the ROM version of the following instructions is for G only, but you can still try on A2020U (just notice the Android version).
I once flashed Magisk through TWRP on stock Pie ROM but caused freeze at the boot screen, even the same while patching the boot image. However, now I found that if you are at stock Q and R version, you can now successfully install Magisk by patching boot images.
The only problem is that there is no TWRP for the two versions of stock ROM (since the recovery was made into boot image), so be careful while installing modules.
My method is to use Axon 10 EDL Tool. Fastboot mode is unavailable for stock Pie and Q Bootloader, while R can but this fastboot cannot flash images. So we need to use the patched bootloader of EDL Tool to access the fastboot and flash the patched boot images, then recover to the original bootloader so it can boot the system (The patched bootloader of EDL Tool can only boot stock Pie ROM).
Before proceeding:
Make sure you have updated to at least stock Q version and unlocked bootloader.
If you have not unlocked at Q or R, you can still proceed unlocking. The program will auto backup your current bootloader, however the patched bootloader cannot boot stock Q and R. So following these instructions:
1.Turn on the Developer Options and turn on OEM unlocking, remove your Google Account and lock screen passwords cause it will ask you to login after wiping because of FRP.
2.Boot into EDL Mode (If the phone is off, hold on pressing Vol+ and Vol- and then connect the cable; If the phone is on, connect the cable, then hold on pressing two Volume buttons and then press the power button for about 10 sec and the phone will automatically reboot)
3.Execute the EDL Tool with administrator rights.
4.Choose Unlock-Unlock bootloader
5.Follow the instructions, when the program has flashed (not backup) patched bootloader (Display "DONE", ask you to press any key), hit enter, and your phone will reboot immediately. When your phone vibrates, press both of the Vol+ and Vol- button immediately to boot into fastboot. (If you press in advance you will boot into EDL mode)
6.Open Command Prompt, use the fastboot.exe of the EDL Tool to proceed this command line:
Code:
fastboot flashing unlock
or just drag the program into CMD, like this:
Code:
D:\Axon10Pro_EDL_Tool\tools\fastboot.exe flashing unlock
7.Your phone will display the unlock warning, use volume button to select Yes and press power button to confirm.
8.After pressing power button (keep the cable connecting), press the two volume button immediately to boot into EDL mode, open the EDL Tool again and Restore bootloader from backup.
9.While restoring completed, reboot and hold on pressing Vol+ button to boot into recovery, the phone will automatically erase data and unlocking is done.
After unlocked:
1.Use djkuz's Axon 10 EDL Tool
2.Backup your boot image.
3.Copy your boot image to your phone and install Magisk Application.
4.Patch the two boot images (a/b), and remember the filename of the patched a and b boot.
5.Copy the patched boot images to your computer.
6.Use the EDL Tool to proceed unlocking, follow step 5 above to boot into fastboot.
7.Use the fastboot.exe of EDL Tool to flash patched boot images:
Code:
fastboot flash boot_a pta.img
fastboot flash boot_b ptb.img
(pta, ptb is the filename of your patched boot image)
8.Use volume button to select the green "START" and hit power button to reboot.
9.Follow step 8 above to recover bootloader, and you are done.
Problems:
Cannot use the default "Files" application to install local modules in stock R ROM cause it will possibly crash, so you have to install a third-party file manager application (like Root Explorer) to select modules. (When it open "Files" app, click the menu icon of the left side and select your installed file manager, then select modules to install)
Notes:
I can't find a way of checking which slot(A/B) of the phone has been on without using recovery, so I have to patch the two bootloaders. If you know, then you can patch and flash only that one.
I don't know if you can update to stock Q while unlocked at Pie when I saw this thread, but you can still upgrade to stock R while unlocked and installed Magisk at Q (V2.8). Just remember not to reboot immediately after you installed the upgrade, use the Magisk Application to install to another slot and then reboot.
Hope you enjoy~
Thanks to djkuz for developing the EDL Tool
Click to expand...
Click to collapse
Thanks for the guide, My phone is A2020G and bootloader is unlocked. Is there an easy way to boot into fastboot mode easily? I do not want to unlock again, because the data in the phone is reset after bootloader unlocking process.

erturkmen said:
Thanks for the guide, My phone is A2020G and bootloader is unlocked. Is there an easy way to boot into fastboot mode easily? I do not want to unlock again, because the data in the phone is reset after bootloader unlocking process.
Click to expand...
Click to collapse
There is no way other than using the EDL Tool because ZTE didn't make fastboot accessible while it is on stock Bootloader. However it's safe to flash the modified bootloader using EDL Tool's unlock option because the original bootloader will be backuped. Since you have already unlocked, the fastboot application won't unlock it again, neither will it erase your data. But the modified bootloader can't boot stock system above Android 9 normally, so use it only when you want to flash a image.

I managed to apply Magisk on both Android 10 and 11.
Method. Backup boot.img from Android 10 / 11. Use Magisk app to patch the boot.img and flash it via EDL.
Here is my Android 11 + Magisk boot.img - Backup your own first before you flash this one and do it on your own risk. When I find time, I will create full EDL files with Android 10 and 11 featuring Magisk.

Sorry, but I have same questions here:
Hi, I had already tried to root my device according to the instructions from flymetothemoon, which unfortunately I haven't been able to do so far.
I already unlocked my bootloader under version 1.8, i.e. Android 9. Another unlock is no longer possible. I get the error message from fastboot:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed.
The EDL tool still created the backups of the boot images. I wanted to copy this images into the system, but unfortunately the device got stuck in a bootloop after the restart.
I found a way to patch the boot images on the PC with Magisk. I used the latest version of Magisk for this. I was also able to flash the patched boot images via fastboot and then restore the backed up boot images in the EDL.
After the restart, however, the device goes back into the bootloop.
To be honest, the last step is not entirely clear to me. The patched images are flashed and then I restore the original boot images. Am I misunderstanding something?

And I got my A10Pro to charge again, so this is fantastic news! Miss root more than anything else out there.

Related

Need Help. ADB, Recovery and Fastboot/Download Mode don't work

Hey xda community,
last night i run into a tricky situation.
First, I explain what I did
I bought me the P9 EVA-L09 via Telekom Germany.
cause i don't want the Telekom **** on my device i decide to TWRP, Root, and flash P9 stock Rom on it.
Unlocking and install TWRP with the SRK Tool works fine. Install the Root was a bit more tricky, because windows lost the correct ADB connection when i go into TWRP Sideload Mode. Because that does not work, i decide to flash the P9 Stock ROM without Root to come forward.
While flashing, (i don''t now anymore which method i choose to flash) an error appers, and the flash process canceled.
The Device don't boot anymore. After a loot of googeling and testing, i've found out that the problem was the encryption of the /Data Partition.
TWRP was unable to mount it, same for the /cust and one more.
After reading about other Methods to get the Phone work again i try this Method i've found on xda.
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
Unfortunately the "press all buttons on the phone" Method don't work.
I also tried out the Huawei Update Extractor to flash single image files to the partitons of the phone. I used the dload file form the previous Method
http://forum.xda-developers.com/showthread.php?t=2433454
http://www.modaco.com/forums/topic/372688-re-partition-stock-partition-tool/ (using the answer on the bottom)
Download from xda huawei update extractor and extract img files from the update.
Turn off the phone, then press vol- and power key, you are in fastboot mode.
Then, flash img files from extracted rom with:
Fastboot flash system SYSTEM.IMG
fastboot flash boot BOOT.IMG
And do the same with the others...
When you finish, fastboot reboot
Click to expand...
Click to collapse
But that don't work. fastboot already replies with "Remote Command not allowed"
i changed the Method a bit. I've put the BOOT.IMG and RECOVERY.IMG an an SD card and flash it via the Install IMG Funktion of TWRP.
That workes very well and expect the /data partition every partition was mountable again.
Then i used the "Fastboot flash system SYSTEM.IMG" again, and tada it works without errors.
The device is booting again to Android, but it reports that the /Data Partition Decryption failed and i have to enter the Recovery Mode and do a factory reset to unlock the partition. If i reboot for get rid of this error the phone does not boot into the Recovery, it boot to the eRecovery which is useless for that because it only provide the eRecovery function instead of also a normal factory reset (how dump is this )
Now the state is, phone boots normal, reports the /Data is not decryptable, reboot to eRecovery, shutdown or reboot. It does really nothing else.
I can't get into the Fastboot/Download Mode, it ignores the Key Combination Volume down + Power. If i press this it starts normal.
I also can't get into the recovery / TWRP Mode, it ignores the Key Combination Volume Up + Power. If i press this is starts normal.
I've also noticed that the Phone is not conecting to the ADB on my computer, only the virtual CDROM from wich the HiSuite is installable connects.
I've also noticed that the eRecovery is not able to starts WIFI on the phone. It errors with "Starting WIFI failed!"
I also tryed out another time the dload function. This changed nothing. Phone boots still normal and run into the Decryption problem.
And i tried out to boot into fastboot or recovery after a cold reset, battery empty
Now it's on you. Has anybody an idea how i can solve one of the above problems. I think when one is solved the others will disappear via flashing new TWRP or so
Try connecting your phone to usb and then holding power+volume down until it boots to fastboot mode.
Huawei phone won't boot into recovery if system and twrp don't match but it should boot to fastboot allways.
What is the last rom you had on your phone while it was working?
Ogameplayer said:
Hey xda community,
last night i run into a tricky situation.
First, I explain what I did
I bought me the P9 EVA-L09 via Telekom Germany.
cause i don't want the Telekom **** on my device i decide to TWRP, Root, and flash P9 stock Rom on it.
Unlocking and install TWRP with the SRK Tool works fine. Install the Root was a bit more tricky, because windows lost the correct ADB connection when i go into TWRP Sideload Mode. Because that does not work, i decide to flash the P9 Stock ROM without Root to come forward.
While flashing, (i don''t now anymore which method i choose to flash) an error appers, and the flash process canceled.
The Device don't boot anymore. After a loot of googeling and testing, i've found out that the problem was the encryption of the /Data Partition.
TWRP was unable to mount it, same for the /cust and one more.
After reading about other Methods to get the Phone work again i try this Method i've found on xda.
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
Unfortunately the "press all buttons on the phone" Method don't work.
I also tried out the Huawei Update Extractor to flash single image files to the partitons of the phone. I used the dload file form the previous Method
http://forum.xda-developers.com/showthread.php?t=2433454
http://www.modaco.com/forums/topic/372688-re-partition-stock-partition-tool/ (using the answer on the bottom)
Download from xda huawei update extractor and extract img files from the update.
Turn off the phone, then press vol- and power key, you are in fastboot mode.
Then, flash img files from extracted rom with:
Fastboot flash system SYSTEM.IMG
fastboot flash boot BOOT.IMG
And do the same with the others...
When you finish, fastboot reboot
But that don't work. fastboot already replies with "Remote Command not allowed"
i changed the Method a bit. I've put the BOOT.IMG and RECOVERY.IMG an an SD card and flash it via the Install IMG Funktion of TWRP.
That workes very well and expect the /data partition every partition was mountable again.
Then i used the "Fastboot flash system SYSTEM.IMG" again, and tada it works without errors.
The device is booting again to Android, but it reports that the /Data Partition Decryption failed and i have to enter the Recovery Mode and do a factory reset to unlock the partition. If i reboot for get rid of this error the phone does not boot into the Recovery, it boot to the eRecovery which is useless for that because it only provide the eRecovery function instead of also a normal factory reset (how dump is this )
Now the state is, phone boots normal, reports the /Data is not decryptable, reboot to eRecovery, shutdown or reboot. It does really nothing else.
I can't get into the Fastboot/Download Mode, it ignores the Key Combination Volume down + Power. If i press this it starts normal.
I also can't get into the recovery / TWRP Mode, it ignores the Key Combination Volume Up + Power. If i press this is starts normal.
I've also noticed that the Phone is not conecting to the ADB on my computer, only the virtual CDROM from wich the HiSuite is installable connects.
I've also noticed that the eRecovery is not able to starts WIFI on the phone. It errors with "Starting WIFI failed!"
I also tryed out another time the dload function. This changed nothing. Phone boots still normal and run into the Decryption problem.
And i tried out to boot into fastboot or recovery after a cold reset, battery empty
Now it's on you. Has anybody an idea how i can solve one of the above problems. I think when one is solved the others will disappear via flashing new TWRP or so
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/p9/how-to/tools-huawei-p9-firmware-updater-t3432457/page1
Sent from my HUAWEI VIE-L29 using XDA Labs
I see two possibilites for this behavior:
1) The phone only pretents to reboot but makes a kind of warm start (never running the code to branch to recovery/boot) -> if the phone seems powered off and you attach usb cable, do you see standard battery laoding animation (that's what it should be) or black screen / boot logo?
2) You flashed a wrong boot.img and/or recovery.img or flashing got screwed up
If you have wrong images, fastboot should still work as edint3000 said.
For the unlikely case (1) with non removable battery you have to wait until battery is drained before you can boot into fastboot after connecting USB cable. Edit: oops just saw you did that.
I had another phone that at some point decided to go only in fastboot with volume down and no power button, when powered up with USB power. But I had never such an issue with a Huawei phone. However, playing around a bit costs nothing (but time).
I see no reason why fast boot should not work. How did you find out, that everything is fine after flahing with TWRP and before flashing system with fastboot?
Did you do anything else than flashing the system.img with fastboot?
Chilli
Same problem here...Phone not boot/not enter fastboot mode/not enter recovery mode...just stuck "your device booting now" screen...any solution?
Hello Mossyhand
you should search for the recovery Method with an "dload" ROM. This are kind of special Roms wich are able to "selfflash" onto the phone.
You have to put the right file onto your SD Card and then you have to press some keys when i remember right.
Sadly i've forgot, when i solved my problem, to reply how i did that exactly ._.
But if you do search in the dload method you will figure a way out i guess
If you don't find an right file, i can upload you my file, i have it still on my computer
had the same problem
go into the erecovery, it will tell you the data partition has been damaged. u can wipe it from there. go into trwp again, install rom and stuff. voila, works
cheers

How to install rom, Can only access fastboot atm

Hey,
Guide was unclear and I deleted my rom. Ive accessed bootloader by update miui app. Now I can't access boatloader and phone is stuck at booting. I can only access fastboot. Do you know what can I do? Please help.
1. I got it back at fresh miui 8. When I try to install lineage os from device memory. It shows error
2. some tutorials say shift+right click shows cmd when fastboot and recovery in same directory. mine shows powershell window that doesn't work
Please link me valid guide or help
dixon118_pl said:
Hey,
Guide was unclear and I deleted my rom. Ive accessed bootloader by update miui app. Now I can't access boatloader and phone is stuck at booting. I can only access fastboot. Do you know what can I do? Please help.
1. I got it back at fresh miui 8. When I try to install lineage os from device memory. It shows error
2. some tutorials say shift+right click shows cmd when fastboot and recovery in same directory. mine shows powershell window that doesn't work
Please link me valid guide or help
Click to expand...
Click to collapse
I assume that twrp is not installed yet on your device and you've a unlocked bootloader. If that's the case go fastboot mode by turning your phone off and then pressing the power+volume down together. Then from your computer flash the latest twrp image ("fastboot flash recovery filename.img"). Then boot to recovery by pressing volume up+ power button and from the recovery flash lineage os. And don't forget to flash the required firmware before flashing lineage os.
sravans578 said:
I assume that twrp is not installed yet on your device and you've a unlocked bootloader. If that's the case go fastboot mode by turning your phone off and then pressing the power+volume down together. Then from your computer flash the latest twrp image ("fastboot flash recovery filename.img"). Then boot to recovery by pressing volume up+ power button and from the recovery flash lineage os. And don't forget to flash the required firmware before flashing lineage os.
Click to expand...
Click to collapse
I got it, using lineage os atm. Ty

Having some trouble rooting now sure where is the problem

So I followed this guide, watch?v=eBAzsEw-QVsAnd, He used an auto flashing program, got to the step where you flash the recovery, it worked, the ADB was recognized and the writing of the recovery was successful.
But, when I tried booting into TWRP (by power + vol-up) I just get a black screen for a few secs and then the mi logo again.
Also, I manually installed TWRP 3.3.1 and still the same thing
Any suggestions?
Fullbit310 said:
So I followed this guide, watch?v=eBAzsEw-QVsAnd, He used an auto flashing program, got to the step where you flash the recovery, it worked, the ADB was recognized and the writing of the recovery was successful.
But, when I tried booting into TWRP (by power + vol-up) I just get a black screen for a few secs and then the mi logo again.
Also, I manually installed TWRP 3.3.1 and still the same thing
Any suggestions?
Click to expand...
Click to collapse
When you restore the phone try using the latest TWRP from here https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
Copy the TWRP image to the adb/fastboot folder and rename to TWRP.img.
No need to use any tools, just boot into fastboot connect to the PC then in command prompt navigate to the adb folder and use
Code:
fastboot flash recovery TWRP.img
After installing boot immediately into TWRP and flash what you need.
In fastboot still press and hold power and vol+ until it vibrates. Then let go of power and keep pressing vol+ until TWRP boots

Question Phone stuck in boot loop, unable to get to FastBoot

Hi,
Sequence of steps:
1. Extracted the boot.img from payload.bin and flashed it to the phone. At this point I was able to get into Fastboot
2. While in Fastboot I went into advanced and wiped the "System Settings", and that's when the trouble started - now the phone is stuck into a boot loop forever, I do however get the options to "Power Off" and "Restart"
3. But none of the options above in Step 2 is able to bring me back to Fastboot (and hence into fastbootd either)
Question: How can I get the phone into Fastboot Mode - have tried MSM Tool v4 as well, but that doesn't even recognize the phone
Edit - This seems to have been resolved now, think I had to press Vol Down + Power instead of Vol Up + Power
Was able to enter into Fastbootd as well, will try to proceed with unbricking the phone with a fresh mind tomorrow
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
VoltaGe86 said:
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
Click to expand...
Click to collapse
Thats right, "fastboot boot <file_name>" loads temporarily your custom recovery of choice. After rebooting your phone, the custome recovery is gone.
Otherwise, the command "fastboot flash <file_name> recovery" flashs permamently your custom recovery of choice to your device.
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Zekedw said:
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Click to expand...
Click to collapse
I have exactly the same issue, on a nord 2
How about vol+/vol-&power all together? When stuck that gives me some screen that allows start, recovery (the one where you can enter advanced settings I expect from your description) and bootloader booting.

Suddenly no root possible with Magisk

Hello, suddenly have a curious problem. I updated my Xiaomi MI9 via the updater (select update package) to 12.0.5.0 (EEA Stable so still Android 10, I had before, so no global or otherwise). Normally, I had installed the Magisk Apk, patched the corresponding boot.img, install via fastboot and root was successful.
When I do that now, I end up directly in fastboot mode after reboot. Then I tried the variants about TWRP install and also the Recovery.img patch, but no matter which variant always I land after the reboot directly in fastboot mode. I also tried the Magisk uninstaller via TWRP, but even there after the reboot the MI9 ends up directly in fastboot mode. Also tried several versions of Magisk, always the same.
If I reload the original boot.img via fastboot, the boot process works fine again, but of course without root.
What I also noticed, after the update to 12.0.5.0 is also in the Magisk app "ramdisk: no". I am firmly convinced, before that was on "yes".
Is there another possibility without completely format the phone?
If you don’t hold the volume up and power at the start, then the phone will start without root access because most of Chinese phone is rooted by recovery mode. It means you can't just power up by power button, must use key combo OR put usb-to-go (utg) stick in usb port then boot normally with power button

Categories

Resources