So.. where do I start..
After I rooted my phone with magisk and twrp -------------------->(I had a qualcomm crashdump crash when I tried to boot from the twrp .img and I found a way around it)
I tried installing some magisk modules.(first time installing a magisk module ever)
2-3 modules later I noticed that some modules should have an app installed after reboot but I didnt saw any new app despite of having no errors in the terminal while installing.
I tried:
--Installing newer beta magisk version (17.2)
--Reinstalling the module
--Complete factory reset with the unbrick tool (msmdownloadtool) and all over again.
--Installing bluspark recovery (and then all over again)
--Installing bluspark kenel (and then all over again)
--Changing data filesystem partition to F2FS (but OOS didnt like it and bootloop)
--Installing the .zip modules from twrp (didnt work) (probably cause of encryption but if I find a new module I want to install I dont want to factory reset every time)
--Installing xXx No limits magisk rom
And I am here to ask for help because I really do not know what to do.
Thank you :/
ps.I am new to this forum so do not take it for granted to know even some basic stuff
First do NOT use f2fs it's junk. Use Google for more information on that file system
So how do we root with offical Android 10 update? My last way i rooted doesnt seem to be working anymore? Any guides?
Magisk working on final android 10
oscar1823 said:
So how do we root with offical Android 10 update? My last way i rooted doesnt seem to be working anymore? Any guides?
Click to expand...
Click to collapse
Magisk is working on my pixel 3a with the current android 10.
First, I (fully) uninstalled magisk via magisk manager, then did an OTA to Android 10.
After that, I followed "The Boot Image Patching Installation method" on this guide:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Take care: use the latest canary-build of magisk, with the release one it didn't work.
Magisk refuses to install after upgrade to 10. Whether by patched image or by twrp, no magisk, no root.
alliance1975 said:
Magisk refuses to install after upgrade to 10. Whether by patched image or by twrp, no magisk, no root.
Click to expand...
Click to collapse
Odds are you are using the standard Magisk version and not the latest Canary version. TWRP doesn't work on Android 10, so you can't use it to install Magisk.
sic0048 said:
Odds are you are using the standard Magisk version and not the latest Canary version. TWRP doesn't work on Android 10, so you can't use it to install Magisk.
Click to expand...
Click to collapse
I almost brick my phone, I guest all we need to do now is wait till a compatible version of TWRP gets released.. the lastest does not read the Pixel 3a memory/data, thus Magisk Canary cannot be installed
omiCar said:
I almost brick my phone, I guest all we need to do now is wait till a compatible version of TWRP gets released.. the lastest does not read the Pixel 3a memory/data, thus Magisk Canary cannot be installed
Click to expand...
Click to collapse
I installed it while still Pie.
sic0048 said:
I installed it while still Pie.
Click to expand...
Click to collapse
That was my mistake, I didnt installed the canary versino while on Pie. I guest we all have to wait... thanks tho
I made the mistake of having Magisk set to beta instead of canary when I did the Magisk OTA update, but no issues with the regular boot image patching method.
Simply follow the guide linked above and you should be fine.
omiCar said:
That was my mistake, I didnt installed the canary versino while on Pie. I guest we all have to wait... thanks tho
Click to expand...
Click to collapse
Did you install the Canary Magisk Manager App? I would think you could install the Canary version that way even if you are on Android 10. The biggest unknown for me is if the fact that you have the Magisk stable version already installed would cause some issues. Normally I would recommend that you completely uninstall Magisk via the Magisk Uninstall zip and TWRP prior to moving to Canary, but obviously that isn't an option without TWRP.
Got it to work.
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
sic0048 said:
Did you install the Canary Magisk Manager App? I would think you could install the Canary version that way even if you are on Android 10. The biggest unknown for me is if the fact that you have the Magisk stable version already installed would cause some issues. Normally I would recommend that you completely uninstall Magisk via the Magisk Uninstall zip and TWRP prior to moving to Canary, but obviously that isn't an option without TWRP.
All you really need to do is flash Pie back on the phone and start the process over. I realize that seems like a long process, but it really isn't that hard. Just be sure to backup any important data off phone before you start because installing Pie should wipe the phone.
Click to expand...
Click to collapse
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
darkmeridian said:
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
Thanks for the response, I will download the Andriod 10 and flash it into my phone, hopefully it will work
darkmeridian said:
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
I agree that normally that would work.
However, simply replacing the boot.img file doesn't completely uninstall Magisk. That is why there is a Magisk Uninstaller zip that can be used with TWRP. It normally isn't needed, but it is a great way to completely wipe Magisk if you are having issues. Obviously that isn't an option on Android 10 currently because TWRP doesn't work yet.
Hopefully he doesn't have any issues moving from stable to Canary Magisk versions. But if he does, he will likely have to flash a full factory image to completely wipe the phone and reinstall everything without traces of Magisk
flow5673 said:
Magisk is working on my pixel 3a with the current android 10.
First, I (fully) uninstalled magisk via magisk manager, then did an OTA to Android 10.
After that, I followed "The Boot Image Patching Installation method" on this guide:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Take care: use the latest canary-build of magisk, with the release one it didn't work.
Click to expand...
Click to collapse
This worked for me. Thanks
darkmeridian said:
1. Sideloaded the Android 10 OTA through adb.
2. Download the factory image and extract the boot.img
3. Move boot.img to your phone.
4. Download the Canary Magisk Manager (NOT DEBUG).
5. Use Canary Magisk Manager to download Magisk Canary (19.4) (NOT DEBUG).
6. Use Canary Magisk Manager to install Magisk Canary, select file and patch option. Select the boot.img file.
7. Transfer the magisk_boot.img to your computer.
8. Reboot to fastboot.
9. "fastboot flash boot magisk_boot.img"
10. If it works, then it works.
11. If it doesn't work, it will probably hang at fastboot.
12. If that is the case "fastboot set_active other" "fastboot reboot"
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
He can just flash the Android 10 OTA, which will overwrite the boot.img and thereby remove Magisk. Then he can go ahead and use fastboot to install Magisk Canary.
Click to expand...
Click to collapse
Can you elaborate on this? like is there a video, or more detailed tutorial on how to accomplish this?
If you experience manager telling you that Magisk isn't installed after installing it through fastboot, uninstall manager and reinstall it. Deleting app data won't do the trick. Strange bug but I encountered that in the Q beta
Anyone else having issues with the canary build? I hard reboot and it shows magisk not installed, then I reboot again and its installed again?
Also Android Q is hella laggy for me?
Currently doing a full fresh image install
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
alliance1975 said:
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
Click to expand...
Click to collapse
Can't recommend uninstalling system apps anyway. Hasn't worked for me under Pie either. Rebooting always brought the app back and in the case of Digital Wellbeing, I uninstalled it through Root Uninstaller and encountered a bootloop.
Velcorn said:
Can't recommend uninstalling system apps anyway. Hasn't worked for me under Pie either. Rebooting always brought the app back and in the case of Digital Wellbeing, I uninstalled it through Root Uninstaller and encountered a bootloop.
Click to expand...
Click to collapse
For now I disabled the unused apps. Similar behavior also in pie. One update app remover wouldn't work but titanium would, the next update the reverse would happen. I think the apps need updating so as to work with Android 10.
omiCar said:
Can you elaborate on this? like is there a video, or more detailed tutorial on how to accomplish this?
Click to expand...
Click to collapse
I don't have a video but you can look up the individual steps. You want to do the OTA through ADB sideloading. Then patch the stock boot.img with Magisk Canary, which was linked to above, and then flash with fastboot.
alliance1975 said:
Magisk installed ok but it won't allow root operations. In particular neither app uninstaller (root) nor titanium backup is capable or removing system apps. Magisk includes them superuser list but the apps don't perform. Safety net both true and advanced settings has preserve avb 2.0 unchecked. App remover always fails and titanium won't show app list. Canary Magisk installed but it's as though there is no root.
MM is version 7.3.3
M is version 19.4
Click to expand...
Click to collapse
Uninstall and reinstall Canary Magisk Manager (NOT DEBUG). I had both force encryption and preserve avb CHECKED. Then patch boot.img and flash using fastboot.
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
MichRT said:
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
Click to expand...
Click to collapse
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
You have to use last magisk (above 19.4 if my memories are right).
HpNoTiQ said:
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Click to expand...
Click to collapse
This looks like it might work, so thank you! I found a similar, though different solution (below)
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
I ran into the issue that while boot-looping with a magisk patched boot img, I wasn't able to run the command, adb wasn't finding the phone. I tried again after booting TWRP and it basically threw an 'error - command not found'.
HpNoTiQ said:
You have to use last magisk (above 19.4 if my memories are right).
Click to expand...
Click to collapse
I think you are right, in beta/canary channel
@Tulsadiver gave me a hand with this, see here: https://forum.xda-developers.com/showpost.php?p=80398385&postcount=35997
Thank you guys!
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
You could use DFE (If you want unencrypted data) or use magisk module for recovery. to remove unwanted magisk modules
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
There is magisk module which check on start of the phone if any module makes a bootlop and disable it. Magisk Bootloop saver on github
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
Power phone off completely. Power on and when MIUI logo shows on screen hold volume down button until phone boots, this will disable all magisk modules you have installed. It's called magisk safe mode. You can now enter magisk app and enable modules one by one until you find the culprit.
Sidenote: I upgraded from xiaomi.eu 12.0.6 to 13.0.3 using fastboot. TWRP was unable to decrypt when I booted to recovery to install magisk after update. I rebooted back to MIUI and disabled pin and fingerprint. Rebooted back to TWRP and was able to access data and install magisk from the downloads folder. So try disabling screen lock and see if TWRP is working then.
Well orangefox has magisk manager built in, so modules can be removed with a swipe
you can navigate to data/adb/modules folder in twrp file manager without decryption needed and delete module folder.
worked for me on android 12.
I got stuck at Xiaomi logo after installing some module. The storage is encrypted on Android 12, decryption in recovery is not possible at the moment. So using OrangeFox or deleting /data/... is not possible.
The only solution that worked for me was accessing the safe mode and running this command from adb shell.
magisk --remove-modules
As in the subject, I have a problem with the magisk on the Mi 10 Lite 5G.
I downloaded room miui_MONETGlobal_V13.0.2.0.SJIMIXM_f2b661bdf6_12.0
Due to the fact that on android 12 there is no TWRP working yet, I uploaded magisk 24.3, patched the boot.img file and uploaded via FASTBOOT, everything is loaded, I have root access but the application does not work as it should. When he wants to hide an application under the name of settings installed he gets the message: "Restore application magisk, this application cannot run as root has been lost. Please restore it to its original state." and here I have install at the bottom. after installing the application from scratch, I get another message "Your device requires additional configuration for the magisk to work properly" I click ok and I have the message "configuration failed."
I tried multiple times to patch boot.img and upload it via Fastboot but I have the same problem every time.
Anyone know the solution to this problem ???
I'm still on MIUI 12/A10, I haven't tried this out.
But - since the flash-script is just a fastboot script, you can do it a bit backwards.
Install any pre-A12-rom, after that, boot in to TWRP. Flash boot.img from the A12-rom. Then flash magisk.
Now you edit the fastboot.bat or fastboot.sh-script. Remove the line with fastboot flash boot images\boot.img. Boot in to the bootloader. Then run the script.
You should now have a fully working A12-rom with magisk.