After days of trial and error, I can conclude that B25 has serious issues with Magisk - Magisk Manager will fc on every root permission prompt, the Magisk app is also not usable. I've raised this issue here as it seems it is producing a code 14 error on opening the database. This problem seems to be B25 or Axon exclusive.
Since B25 stripped bootloader and caused the Magisk to crash, I see no reason to use it and to get Safetynet to work, rolling back to B19 is the next best move.
I will describe my process (which involves a wipe) and successfully get Magisk 13.2 to work and Safetynet all passed without extra modules.
1) Download the B19 EDL (B19-NOUGAT_FULL) and have MiFlash ready
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
2) Flash B19 EDL by using
Code:
adb reboot edl
3) Boot to stock recovery by pressing Vol Up+Power, choose a wipe/reset
4) Boot to Bootloader, install TWRP
Code:
fastboot flash recovery twrp-3.1.1-0-ailsa_ii.img
5) Boot to TWRP and sideload Magisk 13.2
Code:
adb sideload "magisk v13.2.zip"
6) Boot to system
7) Enable USB Debugging and run
Code:
adb reboot disemmcwp
Magisk should be working and it should pass the SafetyNet check. You now have a clean phone to play with and stay away from B25.
Related
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Master Luca said:
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Click to expand...
Click to collapse
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
bilausdaniel said:
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
Click to expand...
Click to collapse
Still in boot loop ( I let it boot for 18 min )
Did you tried to disable xposed on booting?
There is key combination when system boots up, to disable xposed, and so all modules.
Go into recovery, and boot up again from there (normal boot), and when logo appears click at least 3 times power button, and xposed will understand it need to disable itself.
That should work.
And if you have some data in phone, you can make app backup from recovery and if you have files you can connect to PC and copy those files on PC.
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
brasscupcakes said:
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
Click to expand...
Click to collapse
go in twrp and to android/adb/modules.. module there reboot phone
bilausdaniel said:
go in twrp and to android/adb/modules.. module there reboot phone
Click to expand...
Click to collapse
delete that module in there
Hi all,
I have read about how to install Twrp, with method described for flashing roms, but i need twrp only for flashing mods eventually and nothing more, and i need to receive ota.
Which is the simpliest and secure way?
Boot.img method or fastboot slot a/b?
Hope i was clear enough and thanks all in advance.
In theory, you could:
- fastboot flash boot twrp.img (do NOT allow system modifications)
- fastboot continue or fastboot reboot (it is being mentioned that continue command is to be used on A3, though not sure why)
- do the magic in twrp
- fastboot flash boot stock_boot.img
- fastboot continue or fastboot reboot
- use the phone and install OTA when it arrives
However, I can't imagine what kind of mods do you want to install in TWRP. Any system modification will prevent OTA installation (even mounting system partition as R/W) and also can prevent booting up the phone (dm-verity). Most mods these days are systemless via Magisk. TWRP on Mi A3 is useful mainly for making (and possibly restoring) backups, installing custom ROMs and troubleshooting. For everything else you have Magisk.
_mysiak_ said:
In theory, you could:
- fastboot flash boot twrp.img (do NOT allow system modifications)
- fastboot continue or fastboot reboot (it is being mentioned that continue command is to be used on A3, though not sure why)
- do the magic in twrp
- fastboot flash boot stock_boot.img
- fastboot continue or fastboot reboot
- use the phone and install OTA when it arrives
However, I can't imagine what kind of mods do you want to install in TWRP. Any system modification will prevent OTA installation (even mounting system partition as R/W) and also can prevent booting up the phone (dm-verity). Most mods these days are systemless via Magisk. TWRP on Mi A3 is useful mainly for making (and possibly restoring) backups, installing custom ROMs and troubleshooting. For everything else you have Magisk.
Click to expand...
Click to collapse
Thanks for reply, really appreciated. Twrp grant you to mount system (for example with fonts) and then umount without issue with ota if you restore boot image, in theory.
Thanks again, maybe i use magisk but i use banks app and i don't want root
HTCDevil said:
Thanks for reply, really appreciated. Twrp grant you to mount system (for example with fonts) and then umount without issue with ota if you restore boot image, in theory.
Thanks again, maybe i use magisk but i use banks app and i don't want root
Click to expand...
Click to collapse
Nope, won't work. OTA update engine checks system partition metadata hash, if it doesn't match, it won't continue with the installation. Just mounting system partion as R/W will change its metadata. With banking apps you'll have more luck with Magisk than without for a simple reason, unlocked bootloader will fail the Safetynet test. Magisk can hide bootloader status, root and itself. Only a very few apps can detect Magisk (mostly with controversial "undocumented" methods).
Btw. fonts replacement is a perfect task for Magisk, there are already modules ready for this.
_mysiak_ said:
Nope, won't work. OTA update engine checks system partition metadata hash, if it doesn't match, it won't continue with the installation. Just mounting system partion as R/W will change its metadata. With banking apps you'll have more luck with Magisk than without for a simple reason, unlocked bootloader will fail the Safetynet test. Magisk can hide bootloader status, root and itself. Only a very few apps can detect Magisk (mostly with controversial "undocumented" methods).
Btw. fonts replacement is a perfect task for Magisk, there are already modules ready for this.
Click to expand...
Click to collapse
Thank you again, you are right, probably magisk is more secure than if you haven't it once bootloader is unlocked
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Yajirobai said:
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Click to expand...
Click to collapse
Your bootloader needs to be unlocked and USB debugging enabled first of course. TWRP Recovery should be installed.
To do this, you need the adb and fastboot binaries installed on a PC/Laptop. I use Ubuntu and installing these is trivial via apt package manager:
Debian based:
Code:
sudo apt install adb fastboot
RedHat based:
Code:
yum install adb fastboot
If you use Windows, the install and use of these binaries is a little different. I don't use Windows so you'll have to do a quick search to find out how to install and use these binaries. The commands listed below will work no matter what OS you use.
Connect your phone to your PC/Laptop via it's USB cable and reboot it to TWRP Recovery:
Power off the phone, then power on while holding the volume up button until you see the TWRP logo. Log into TWRP to decrypt.
Next, you need to pull the current boot.img from your ROM to patch it for root access:
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
There should be a boot.img on your phone's internal storage, copy it to your PC/Laptop. From TWRP, reboot your phone to fastboot.
Now, we'll use this most excellent, free resource to patch the boot.img file which will give root access:
https://patcher.yaalex.xyz/
Check the 'Include Magisk' checkbox on the website before submitting image.
Important: After you upload your boot.img file to the website, be patient. This could take 10 minutes or more to complete, just wait until you get a prompt to download the patched image. You will be provided a patched_boot.img file from the website once it is finished.
Finally, all you need to do is flash the patched_boot.img to your phone:
Code:
fastboot flash boot patched_boot.img
Boot your phone to the ROM:
Code:
fastboot reboot
Install Magisk Manager if you haven't already, and enable Magisk Hide in the settings. Magisk Manager should report root access is available and SafetyNet test should pass.
I typed all this up from memory so if you run into trouble or are confused by any step, let me know and I will gladly clarify/fix the steps.
I hope this helps others achieve root on this phone. Let me know how it goes and happy de-bloating!
Rollback instructions:
If your phone fails to boot don't panic. You can restore your original boot.img if needed to regain access. Reboot your phone to fastboot:
Boot phone while holding the down volume button until you see the fastboot logo.
Next, flash the original boot.img to the boot partition:
Code:
fastboot flash boot boot.img
Now just reboot to ROM and all should be restored:
Code:
fastboot reboot
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Iirc redmi 8a is an ab device, and yes this device is as customisable as any other Qualcomm. What gsi image are you flashing?
Actually he is not way off ..... i am NOT able to find a Custom Non MIUI ROM with full VoLTE support. VoLTE fix for GSI's ( if at all it worked ! ) does not work for Havoc. twrp root is all good. I want a NON MIUI ROM that can regional variants ( Europe and Asia ) and supports VoLTE
Waking up with a sleepy head I wanted to swipe the new version notification away, but didnt swipe well enough and it actually upgraded. I need to downgrade to v23 again but for whatever reason, its not working. Here's what I tried:
1. Reboot to fastboot and do fastboot boot magisk_patched.img (boot img with magisk 23 I use after OTA's). This boots but its not rooted. Magisk mgr is 24 though.
2. Rebooted to system, uninstalled Installed magisk manager 24, rebooted and retried the above. Installed Magisk mgr 23. No root.
I then unpacked the latest full oos 11 for my phone with payload_dumper, copied the boot.img to my phone and patched it using magisk manager 23. Copied it back to the PC.
retried step 1. No root.
Rebooted to fastboot again, checked current slot, its A.
fastboot flash boot magisk_patched.img (the new one I patched in the step above).
Rebooted, no root.
What am I supposed to do to get Magisk 23 back on my phone?
The reason is I'm dependent on riru/lsposed for a couple of xposed modules. If I disable zygisk in magisk 24 I won't have root hide, if I enable that, riru/lsposed isn't working.
Thanks for the help!
Yeah I had a similar issue on A12 rom, Magisk 24 just doesn't allow me to pass safety net due to Google play services in Magisk 24 deny list unselects after a reboot, so downgrading to 23 which just works after using hide list.
I had to disable and remove any modules, unhide Magisk 24 then restart.
Use Magisk 24 uninstall in the app and restart.
Install Magisk 23 and Install to boot image file to payload Boot.img, restart to Fastboot and flash as you did.
Then again in Magisk install select Direct Install then restart.
Reapply Magiskhide to apps google pay/services etc restart and check root.
I still have an issue with Magisk hiding the app installs the proxy app but it doesn't open so isn't working, so still working on this. Root is working tho with the above.
Thanks, I still cant get it to work though.
I can patch the boot.img, but when I try to boot it I don't get root.
When I flash and boot it, there still is no root available.
Possibly i had the same issue, no root after flashing the 23-modified boot image. I solved it by, upgrading the app to 24.3, patch the boot image, reboot to fastboot, flash it, reboot it so i was back at Magisk 24.3 Then i did a full uninstall of Magisk, via the app. Then installed app v23. Patched the boot image etc as per https://topjohnwu.github.io/Magisk/install.html#patching-images
Key here was, i think the full removal of Magisk 24 before downgrading.
Works!
But you have to solve some basic problems:
Unlock bootloader. Solved here: https://github.com/mashed-potatoes/PotatoNV
You have to patch the recovery_ramdisk original partition. Patch with The Magisk https://github.com/topjohnwu/Magisk
Take the recovery_ramdisk partition from the latest full upgrade file VTR-L29 9.1.0.297(C432E5R1P9), VTR-L29C432B185
Download the lineage .img file https://sourceforge.net/projects/andyyan-gsi/files/. You will need the -arm64_bgN.img.xz version
Reboot the phone to fastboot mode and execute command: fastboot flash system xxxxx-arm64_bgN.img
fastboot reboot
After reboot the phone go to the erecovery (Volume up to 3 secondes) and do wipe data / factory reset
Boot phone in to clean Lineage system and do the first Lineage configuration
Reboot phone to fastboot mode
Flash the Magisk patched recovery_ramdisk partition: fastboot flash recovery_ramdisk magisk_patched_recovery_ramdisk.img
Now you have a full working Huawei P10 with Lineage 18.1, 19.1 or 20.x system, but every time you will have to boot the phone with "Magisk boot cheat" means Volume Up + Power button. When appears the Huawei logo release all buttons. https://topjohnwu.github.io/Magisk/install.html
Not necessary - permanent boot to recovery cheat. When the phone boot and the yellow text on black wallpaper appers, use the first option and go to eRecovery (Volume Up for 3 seconds). In eRecovery select Wipe data / Factory reset, confirm and reboot the phone. The phone will reboot to recovery and will boot in to the Magisk root boot system (the wipe will not be called).
Go back to point 11 state. The RAM card have not to contain a /dload directory!!!!! Power off the phone. Press Volume Up + Volume Down + Power and release all buttons, when Huawei logo appears. Now you will see aclean EMUI screen which will respond - OS Upgrade not successfull. Go to reboot and the permanent Recovery reboot byte will be cleaned.
here's a great alternative for magisk
KernelSU
all thx to coconut for bringing kernelsu on vtr & also maimai for his pangu kernel
GitHub - Coconutat/android_kernel_huawei_vtr_emui9_KernelSU: Modify based Pangu Kernel(EMUI 9 Custom Kernel) for support KernelSU
Modify based Pangu Kernel(EMUI 9 Custom Kernel) for support KernelSU - GitHub - Coconutat/android_kernel_huawei_vtr_emui9_KernelSU: Modify based Pangu Kernel(EMUI 9 Custom Kernel) for support KernelSU
github.com
that's for EMUI "9.0"
works great, i did test some magisk module such as uka tool and it works without any issues.
for zygisk on kernelsu:
GitHub - Dr-TSNG/ZygiskOnKernelSU: Run Zygisk on KernelSU
Run Zygisk on KernelSU. Contribute to Dr-TSNG/ZygiskOnKernelSU development by creating an account on GitHub.
github.com