I am using Asus Zenfone Max Z010D (ZC550KL).
I have TWRP-3.2.0-Z010D-20171205 on my phone, currently using stock rom Version WW 8916-13.8.26.92.
When flashing Magisk 14 thru twrp and reboot, Magisk is detected in the system and is installed correctly.
But Collective Dolby (https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342)
and Viper (https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058) is not working and not installing thru TWRP with error saying that Magisk v15+ is needed.
When flashing magisk 15.2, it is done successfully but upon reboot and checking in magisk manager it is stated that Magisk is not installed.
So I want to be able to use magisk 15 and up so i can use dolby and viper by sir ahrion.
I hope you can help me guys.
Thanks in advance.
griffynix said:
I am using Asus Zenfone Max Z010D (ZC550KL).
I have TWRP-3.2.0-Z010D-20171205 on my phone, currently using stock rom Version WW 8916-13.8.26.92.
When flashing Magisk 14 thru twrp and reboot, Magisk is detected in the system and is installed correctly.
But Collective Dolby (https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342)
and Viper (https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058) is not working and not installing thru TWRP with error saying that Magisk v15+ is needed.
When flashing magisk 15.2, it is done successfully but upon reboot and checking in magisk manager it is stated that Magisk is not installed.
So I want to be able to use magisk 15 and up so i can use dolby and viper by sir ahrion.
I hope you can help me guys.
Thanks in advance.
Click to expand...
Click to collapse
Same here when installing magisk 15.2 but magisk manager for me is stuck at the splash screen, only magisk 14.x works.
Zenfone 2 ZE551ML / Stock 6.0.1
guys, i got error on installing magisk manager apk. its say "app not installed". how to solved it? thank you
i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally
Glad it worked . Are u able to install magisk again ?
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide
I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?
Same problem here with magisk I guess it is a compatibly issue with MIUI 11
Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.
I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone
XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.
I forgot to add on the title -- my phone is the EU variant with Snapdragon 5G. (G781B)
Hello, did anyone get Edxposed for the phone?
I've succesfully rooted but edxposed seems to be always causing some kind of bootloop.
I haven't need to use edxposed as I was refusing to upgrade from my old oneplus 3, so I'm a complete noob here at this point,
However, it does seem like there seems to be issue on this area anyway.
If anyone succeeded, please share what you did.
Thanks!
everlasting207 said:
I forgot to add on the title -- my phone is the EU variant with Snapdragon 5G. (G781B)
Hello, did anyone get Edxposed for the phone?
I've succesfully rooted but edxposed seems to be always causing some kind of bootloop.
However, it does seem like there seems to be issue on this area anyway.
If anyone succeeded, please share what you did.
Click to expand...
Click to collapse
Morning
I have just purchased the same phone, but I didn't get as far as you, so in the hope we can help each other here is a summary of what I did and how far I got -
I upgraded stock ROM all the way upto Android 11
Then enabled dev. options, and clicked on OEM unlock and then rebooted following the new unlock bootloader option on the download screen.
Then rebooted into download mode and flashed vbmeta_disabled.tar via ODIN (this then factor reset the phone).
Then had to re-flash stock android (via ODIN), as OEM unlock disappeared from dev. options.
Then back into download model to flash twrp 3.5.1 via ODIN.
Then after to trial and error and help from @afaneh92 I figured how to get into twrp recovery (and how to stop the phone from restoring stock recovery).
I then extracted & patched boot.img in Magisk (see instructions)
Then I booted back into download mode and 'tried to flash to new magisk patched boot.img via ODIN, but it failed with Can't open the specified file (line: 2006)
I then installed magisk manager 8.05, then tried flashing Magisk 21.2 via twrp and it failed with (Android Rescue party trigger).
So I then re-flashed multi-disabler.zip via TWRP and without rebooting formated data, then power off and boot back into recovery. I then flashed magisk 21.2 no problem.
Back into Android I loaded up magisk to confirm I was rooted and to get Riru & EdXxposed installed.
I installed EdXposed manager via its APK.
I then went back into Magisk manager and found and installed Riru 23.3 (this as i understand it replaced Riru - core).
I then found the latest stable version of EdXposed YAHFA 0.4.6.4 (4563) and this refused to install via magisk manager, with error ( ' Riru - core ' is not installed, Unsupported v22+ is installed, user 21.3 instead ) . So Clearly the above ver. of EdXposed isnt compatible with the latest version of Riru.
I then installed the alpha version of EdXposed 0.5.1.4 (4655) and this installed, but when I went into EdXposed manager it said it was installed but not active
So I have my shiny new SM-G781B, w/custom recovery & rooted, but no Xposed framework. I need Xposed for Xprivacy_lua so not having this running isnt an option. So I am going to try Riru - core 21.3/EdXposed_ 0.4.6.4 and if that fails then going all the way back to Android 10 and starting from the top.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What versions of Android, Twrp, Magisk, EdXposed, Riru - have you got installed? Also regarding your EdXposed bootloop - if you read the supports docs, its does say that YAHFA can cause soft loop, and to try Sandhook. But on my old S7, Sandhook caused a boot-loops so I went to and am using YAHFA with no issues - so as always your mileage will always vary.
I have a car Android device in which I am able to install magisk extracting boot.img and then patching it. I was having some problems and have reset, and now I am having some issues:
I flashed latest magisk and got bootloop, so I managed to install 20.2 version and it gives superuser access, but I can't install no modules (it seems to install them but they are not there after a reboot).
I think before the reset I had 20.4 installed, but I don't know how to update my version to 20.4, it always offers me latest version, which ends in bootloop. I don't have access to any custom recovery, so I think the only way to make it work is to update through a custom channel pointed to 20.4, but can't figure out how to set it.
Any help would be appreciated.
Ok, I realized a simpler way to do it: I downloaded 20.4 zip and flashed it through magisk. Now it works perfectly, but when I use Viper4android together with sygic, sygic crashes.
I'm trying to install Magisk 24.3 on my Redmi Note 10S to hide magisk from Apex Legends, but every time I try direct install update from the magisk app, the phone reboots to magisk 23.0 again, everytime (Although I made sure the install logs show that 24.3 installs correctly). It's stuck on 23.0 and I tried reinstalling magisk several times but it doesn't fix it. I'm running on a custom ROM (LiteE) with Genom kernel (4.14.263 rosemary). How do I fix it and install 24?
install it via twrp