I tried flashing magisk v15 on miui global beta mm, but when I boot to system I couldn't find magisk installed . I also tried installing apk but it said magisk not installed. Magisk v14 works on this ROM( Magisk v15 works on my nos 8.1)
tom jp said:
I tried flashing magisk v15 on miui global beta mm, but when I boot to system I couldn't find magisk installed . I also tried installing apk but it said magisk not installed. Magisk v14 works on this ROM( Magisk v15 works on my nos 8.1)
Click to expand...
Click to collapse
Mine is working fine, magisk 15. Miui 9 latest dev beta.
rajbain said:
Mine is working fine, magisk 15. Miui 9 latest dev beta.
Click to expand...
Click to collapse
Which build, I tried it on 8th Dec build
I've also tried magisk v15 on my miui8 kenjo. its showing that magisk not installed. but v14 is working.
I have the same. Redmi 4A and Redmi 4Pro. Rom Xiaomi.eu 7.12.28. Magisk 14.0 works correctly. However, 15.0 and 15.1 can not be installed. Installation via twrp also does not change anything.
Same problem with redmi 4 pro miui 9.2 stable (xiaomi.eu)
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.lang.OutOfMemoryError: Failed to allocate a 134209548 byte allocation with 16777216 free bytes and 113MB until OOM
at java.io.ByteArrayOutputStream.expand(ByteArrayOutputStream.java:91)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:201)
at com.topjohnwu.crypto.ByteArrayStream.readFrom(Unknown Source)
at com.topjohnwu.crypto.ByteArrayStream.readFrom(Unknown Source)
at com.topjohnwu.crypto.SignBoot.verifySignature(Unknown Source)
at com.topjohnwu.magisk.asyncs.InstallMagisk.doInBackground(Unknown Source)
at com.topjohnwu.magisk.asyncs.InstallMagisk.doInBackground(Unknown Source)
at android.os.AsyncTask$2.call(AsyncTask.java)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
... 3 more
i'm also facing the same problem. in my case even v14 isn't working.
send me your zip link
ktanay said:
i'm also facing the same problem. in my case even v14 isn't working.
send me your zip link
Click to expand...
Click to collapse
Hi, I used the official version, you can download it from the official XDA thread
I also have it up and running... I updated from v14 to v15, then v15.1 and i reboot to flash v15.2 now.
Rom: Official Global Developer
Version: 7.12.28 (latest when i write this post)
GreatApo said:
I also have it up and running... I updated from v14 to v15, then v15.1 and i reboot to flash v15.2 now.
Rom: Official Global Developer
Version: 7.12.28 (latest when i write this post)
View attachment 4377599 View attachment 4377600
Click to expand...
Click to collapse
What version of TWRP are you running?, did you update from 14, 15, and 15.1 at once or reboot after each update, I also noticed you have force preserve force encryption checked,
otyg said:
What version of TWRP are you running?, did you update from 14, 15, and 15.1 at once or reboot after each update, I also noticed you have force preserve force encryption checked,
Click to expand...
Click to collapse
I am running the ZCX TWRP (i think it's v3.0.2, available here in xda). I had installed v14.x and I was constantly updating when the new versions became available. I am now on 15.2 (so not all at once). I don't remember pressing the force encryption button, maybe it was checked for me...
GreatApo said:
I am running the ZCX TWRP (i think it's v3.0.2, available here in xda). I had installed v14.x and I was constantly updating when the new versions became available. I am now on 15.2 (so not all at once). I don't remember pressing the force encryption button, maybe it was checked for me...
Click to expand...
Click to collapse
Strange since I could not update to 15.2 no matter what I tried (only 14.0 would work), I was also using ZCX TWRP, I recently updated to redwolf twrp and now Magisk 15.2 went in fine, but I think it does have something to do with "force encryption" since RedWolf TWRP has a option "disable force encryption" and "disable dm-verity" , I don't think the first option was in ZCX twrp, so maybe when that got checked in your magisk manager it fixed it the same way the newer twrp does.
for people having issues here are the steps that worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-install-magisk-15-2-kenzo-t3729329
otyg said:
Strange since I could not update to 15.2 no matter what I tried (only 14.0 would work), I was also using ZCX TWRP, I recently updated to redwolf twrp and now Magisk 15.2 went in fine, but I think it does have something to do with "force encryption" since RedWolf TWRP has a option "disable force encryption" and "disable dm-verity" , I don't think the first option was in ZCX twrp, so maybe when that got checked in your magisk manager it fixed it the same way the newer twrp does.
for people having issues here are the steps that worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-install-magisk-15-2-kenzo-t3729329
Click to expand...
Click to collapse
Awesome! Here is your "thanks" for helping others
otyg said:
for people having issues here are the steps that worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-install-magisk-15-2-kenzo-t3729329
Click to expand...
Click to collapse
I'm having trouble with the part about flashing the Magisk Uninstaller file, since my device (Redmi Note 2) is encrypted, I can't seem to make it work from the TWRP, in the same way wiping the Dalvik/Cache doesn't work.
So I'm stuck on Magisk 14 and even the direct update from the Magisk app puts my device in a bootloop (resolved only by installing the latest rom from the TWRP), maybe because I can't uninstall Magisk properly.
Should I try to flash the uninstall package from the adb?
EDIT: I finally managed to solve it by
1: Uninstalling Magisk from the Magisk manager app itself rather than flashing the uninstaller zip
2: Rebooted into the TWRP recovery where I first followed the instructions here under "Keeping dm-verity and forced encryption
": https://forum.xda-developers.com/showpost.php?p=73145975&postcount=2
3: and I then installed the latest Magisk 15.3
booted into system and no bootloop this time, successfully switched from Magisk 14 to 15
Related
Hi all,
My system was working fine with Magisk v12, I saw there was a big new update, I was interested and updated.
But using the latest Magisk Manager, it says root is not detected.
It's not a big problem, I will restore back to v12 for now, but did anyone else get it working?
Thanks
Asus zenfone 2 flash update manual Magisk 13.1 crash recovery recovery then AD
Same here with Xperia XZ. With v13.1 Root is not detected. v12 is working fine.
Have tried to reinstall it by completely removing and flashing from TWRP, but still no luck.
13.1 and 13.2 working on 7.1 with repacked stock kernel with drmfix fix. It will also work with newest genesis kernel
I upgraded Magisk 12 to 13 beta, then 13.1 and 13.2 without problems.
Even SafetyNet Check passes.
I'm using genesis-nodrm kernel.
Hmm... I was on back on v12, everything fine, I see the 2 above posts saying it is working.
So I flashed 13.2 in TWRP, installed the latest manager app, but still 'magisk not installed', 'not rooted'.
2 say it works with genesis, 1 of them say also with stock...
For me with stock, it's not working.
qvmuhuuxz said:
Hmm... I was on back on v12, everything fine, I see the 2 above posts saying it is working.
So I flashed 13.2 in TWRP, installed the latest manager app, but still 'magisk not installed', 'not rooted'.
2 say it works with genesis, 1 of them say also with stock...
For me with stock, it's not working.
Click to expand...
Click to collapse
Did you try to flash a clean boot.img first so magisk 12 is completely uninstalled instead of flashing back and forth over the same boot.img. Pretty sure I read people on different devices sometimes had to do this, or use the magisk uninstaller. Flashing the clran boot.img first is ofc preferred.
realtuxen said:
Did you try to flash a clean boot.img first so magisk 12 is completely uninstalled instead of flashing back and forth over the same boot.img. Pretty sure I read people on different devices sometimes had to do this, or use the magisk uninstaller. Flashing the clran boot.img first is ofc preferred.
Click to expand...
Click to collapse
Ok I'll try that.
I believe I flashed v13.2 straight over v12.
But when downgrading back to 12, I did flash the uninstaller first.
I'll try uninstalling and then updating
- Still no luck, it didn't work.
I tried updating Magisk 12 -> 13.1 thru the manager, and it would download the zip then do nothing. I found the zip in the Magisk directory, and installed it like it was a module, thru the manager, and it appeared to work. I got the new Magisk Manager (5.0.4) and it says I'm on Magisk 13.1 but that Magisk is not installed, and there is no root.
Following the installation instructions, I rebooted a few times, no change. So I flashed Magisk uninstaller, cleared cache/davlik, and rebooted. Uninstalled Magsick Manager. Rebooted. Booted to TWRP and flashed Magisk-13.1.zip. Rebooted twice. Same issues; Manager 5.0.4 says I'm on Magisk 13.1 but that it's not installed, no root.
Finally I had to flash Magisk uninstall, reboot, uninstall magisk manager. Reboot TWRP, flash magisk-12 installer, reboot, sideload magisk manager v4.3.3, just to get Magisk 12 back.
voilsb said:
Finally I had to flash Magisk uninstall, reboot, uninstall magisk manager. Reboot TWRP, flash magisk-12 installer, reboot, sideload magisk manager v4.3.3, just to get Magisk 12 back.
Click to expand...
Click to collapse
I didn't have to reboot after flashing magisk uninstaller, I just flashed v12 straight after.
And I just uninstalled the new magisk manager then the old one right away, I think?
Magisk manager 13.1 not working for me either tried installing thru app but it does not work
might be related to this https://github.com/topjohnwu/Magisk/issues/265
Also it might be related to this - https://github.com/topjohnwu/Magisk/issues/166#issuecomment-298765812
"Use rootkernel tool from tobias.waldvogel to fix drm instead of PoC TA fix. It seems to be incompatible to Magisk while rootkernel tool patched images work"
I swapped over to Genesis kernel (1.05, the current latest) to try and see if it would help my device pass safety net, since for some reason it is not passing anymore (I tried lots to fix it, flashing etc)
As I posted directly above, it looks like Magisk v13 doesn't like ta_poc, so I used the drmfix version, and Magisk v13.3 works great, and once again my device passes safety net
Did anyone notice that doing a "fastboot boot boot-patched.img" for installing magisk sometimes hangs during boot or a stock recovery error msg "Could not load Android system. Your data could be corrupt....."
I need a few tries before it boots properly. And then installing the systemless expose module gives a similar error.
edit- It doesn't seem to be happening anymore. I tried reproduce the problem but couldn't get it to hang after many tries.
Others have reported seeing this issue as well.
Use TWRP for Magisk installation + check here https://forum.xda-developers.com/mi-a1/help/rooted-device-freezes-booting-secure-t3819483
_mysiak_ said:
Use TWRP for Magisk installation + check here https://forum.xda-developers.com/mi-a1/help/rooted-device-freezes-booting-secure-t3819483
Click to expand...
Click to collapse
Will installing magisk via TWRP break OTA? I'm assuming you boot(not flash TWRP earlier) into TWRP and flash the Magisk framework zip.
From the thread, it sounds like Magisk 16.7 beta has problems with common apps.
barrack1 said:
Will installing magisk via TWRP break OTA? I'm assuming you boot(not flash TWRP earlier) into TWRP and flash the Magisk framework zip.
From the thread, it sounds like Magisk 16.7 beta has problems with common apps.
Click to expand...
Click to collapse
If you boot TWRP to flash magisk it won't break OTA.
I installed 16.7 yesterday and no problem so far with any app.
pantezuma said:
If you boot TWRP to flash magisk it won't break OTA.
I installed 16.7 yesterday and no problem so far with any app.
Click to expand...
Click to collapse
Do you know why flashing magisk after booting into TWRP won't cause problems VS booting into patched boot.img and installing Magisk via "direct install"?? It didn't cause any big booting issue pre 8.1 for me until the last update.
barrack1 said:
Do you know why flashing magisk after booting into TWRP won't cause problems VS booting into patched boot.img and installing Magisk via "direct install"?? It didn't cause any big booting issue pre 8.1 for me until the last update.
Click to expand...
Click to collapse
I think you booted an image patched with 16.0 and not 16.7 (you can try to get an image patched with 16.7 beta just to verify).
As said before, it seems 16.0 has some issues regarding booting and secure boot solved in 16.7.
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
I'll try right away.
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thank you bro, I followed same steps however, I got a bootloop ;(
MaZeNsMz said:
Thank you bro, I followed same steps however, I got a bootloop ;(
Click to expand...
Click to collapse
I can't say what else would help sorry, those are the exact steps I followed and they worked.
Perhaps you could post in the Magisk part of the forums with some info about your device and see if someone could help.
MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
This is a magisk issue and shouldn't be posted here
Sent from my LG-H910 using XDA Labs
I had the same problem till I went to twrp recovery and flashed the zip that magisk downloaded and it works great. Only problem left on the side is trying to get Xposed to work again through the new magisk on H918 Super Rom, it's not working ATM but I think it's fixable somehow I guess. Magisk is effecting all phones, not just V20 btw.
Check out the video about the API and safetynet by the YouTuber HighOnAndroid. That video let's u know what's up with magisk the day before new magisk update came.
Is it possible that someone backup and share with me boot partition, and from my side I recover it ?!
I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?
I was able to directly install Magisk 17.1 from Magisk itself without issues.
SebTech33 said:
I'm running:
ROM: RR-0-v6.1.0-h990-Unofficial
Kernel: Gamma Kernel v26.0.0
Magisk: v17.1
Magisk Manager: v5.9.1
I'm not on stock, but i had no error or problems installing it.
Are you on stock or?
Click to expand...
Click to collapse
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0
KawaiiNek0 said:
I was able to directly install Magisk 17.1 from Magisk itself without issues.
Click to expand...
Click to collapse
Very locky,
I did the same here by I end up with a nice boot loop
MaZeNsMz said:
Rom: Stock,
Kernel: neocore-reboot-v2.5
Magisk: V16.0
Click to expand...
Click to collapse
Have you tried another kernel?
Anyone could test sixaxis compatibility checker?
(free on store)
Only on h990ds. 910 and other never were affected by this problem with previous magisk.
Dont know if v17 solved this problem.
Thanks
SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
I'll try today, do you recommend any kernel?
SebTech33 said:
Have you tried another kernel?
Click to expand...
Click to collapse
Tried D.O.T.S and failed, bootloop
I am thinking if someone can backup the boot and share it with us. So we can recover it
Regards..
Has anyone found a way to make 17.1 work on the H990DS? It took me several flashes to get it to boot but after a couple restarts it started bootlooping again so I had to downgrade to 16 and 16 works just fine
Just stay on v16 until they can work the bugs out with v17 -- you aren't gaining anything by going to v17.
-- Brian
iDefalt said:
Download 17.1 zip
Download latest Magisk Manager apk
Download Magisk uninstaller zip
Install Magisk Manager latest apk
Reboot to recovery
Flash uninstaller zip
Reboot to recovery again
Flash Magisk zip
Wipe caches
Reboot to system.
Click to expand...
Click to collapse
Thanks, that did the trick for me on lg h910r
MaZeNsMz said:
Hi there,
In short, I couldn't manage to install new Magisk v17 and v17.1 on my LG V20 H990DS due to the bootloop issue.
Anyone managed to do that ?!
The details:
- I tried to install Magisk V17 through Magisk app, but failed.
- I installed it through TWRP but failed (Bootloop),
- I uninstall it, phone returned to normal
- I tried to install Magisk V17.1 through Magisk app, but failed (Bootloop).
- I installed it through TWRP but failed (Bootloop).
- I uninstall it, phone returned to normal
- I installed Magisk V16.0 and now functioning normal.
Click to expand...
Click to collapse
Note 26.10.2018 :
I upgraded to Oreo V8.0 from here and everything is fine now
I currently run OOS 5.1.2 (xXx No limits), with magisk 17.1 and blu_spark 3.1.2 (non treble) twrp. I want to update to Open Beta 18, so today i tried by updating the twrp to twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t (successfully). I then removed magisk by the uninstaller and tried to boot into system (still haven't flashed the beta), and it wouldn't load. I then returned to the updated recovery to flash the full zip of the beta but had a zip verification error. I disabled zip verification then got error 7 in the twrp. For now i have reverted to a NAND recovery i had made before updating the twrp, but i would still like to update to Open Beta 18. What did i miss, and how can i make it work? please keep in mind that i would prefer a dirty flash over a clean flash if possible.
Thanks
yohouse2 said:
I currently run OOS 5.1.2 (xXx No limits), with magisk 17.1 and blu_spark 3.1.2 (non treble) twrp. I want to update to Open Beta 18, so today i tried by updating the twrp to twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t (successfully). I then removed magisk by the uninstaller and tried to boot into system (still haven't flashed the beta), and it wouldn't load. I then returned to the updated recovery to flash the full zip of the beta but had a zip verification error. I disabled zip verification then got error 7 in the twrp. For now i have reverted to a NAND recovery i had made before updating the twrp, but i would still like to update to Open Beta 18. What did i miss, and how can i make it work? please keep in mind that i would prefer a dirty flash over a clean flash if possible.
Thanks
Click to expand...
Click to collapse
It's been discussed 100 times on the xXx thread that it's not recommended to switch between stable and beta the dirty way cause you're facing issues. Like you.
It's also not recommended by oneplus in the official threads cause of issues.
A clean installation(look at the beta thread) saves you hours on troubleshooting/headaches in the future.
And latest stable build has advanced reboot menu instead of beta
Hi All, I was on 9.0.14 and now I installed the latest OOS 9.0.16 through TWRP. All went well except i flashed magisk root.
I flashed the latest magisk 19.3 and 19.1 and all got me stuck on oneplus loading screen the red circle and white circle turning infinitely.
Then i tried magisk 18.1, everything loaded fine but magisk seems to be causing errors and not rooted. as i tried to grant nova launcher root, the app freezed and got stuck and force closed.
Also other apps that requires root are not able to request root.
any help would be appreciated.
Thanks!
What update file did you use? Full?
Did you wipe cache/dalvik?
Did you reapply twrp, then magisk?
At least that's what I did and it worked (and still does).
What twrp version?
OOs 9.016 + Magisk 19.3 (+ xXx 7.7 + Omega Kernel) working here for 2 weeks without any problems.
My suggestion would be to reboot in recovery (TWRP), reflash full OOs.zip, flash TWRP.zip, reboot in recovery (TWRP), repeat all this once more then flash Magisk 19.3 Zip and reboot system.
Shady282 said:
Hi All, I was on 9.0.14 and now I installed the latest OOS 9.0.16 through TWRP. All went well except i flashed magisk root.
I flashed the latest magisk 19.3 and 19.1 and all got me stuck on oneplus loading screen the red circle and white circle turning infinitely.
Then i tried magisk 18.1, everything loaded fine but magisk seems to be causing errors and not rooted. as i tried to grant nova launcher root, the app freezed and got stuck and force closed.
Also other apps that requires root are not able to request root.
any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Use magisk uninstaller in twrp. Then flash magisk 19.4 canary.
elchmartin said:
What update file did you use? Full?
Did you wipe cache/dalvik?
Did you reapply twrp, then magisk?
At least that's what I did and it worked (and still does).
What twrp version?
Click to expand...
Click to collapse
yes i always follow these steps, 3.2.3 twrp
MoHed said:
OOs 9.016 + Magisk 19.3 (+ xXx 7.7 + Omega Kernel) working here for 2 weeks without any problems.
My suggestion would be to reboot in recovery (TWRP), reflash full OOs.zip, flash TWRP.zip, reboot in recovery (TWRP), repeat all this once more then flash Magisk 19.3 Zip and reboot system.
Click to expand...
Click to collapse
I did as you suggested and had the same issue stuck at oneplus circles. I then tried to flash 18.1 it made me boot back into the system but root not working just magisk manager with just 2 options, in the menu side, settings magisk and settings.
Then I would try to start from scratch.
Means wipe everything, flash full OOS and then magisk.
@Shady282
Have you got it fixed? I am in the same situation and its frustrating that I am still unable to get root.
Tried flash magisk 19.4 canary no success. Still stuck in bootloop.
elchmartin said:
What update file did you use? Full?
Did you wipe cache/dalvik?
Did you reapply twrp, then magisk?
At least that's what I did and it worked (and still does).
What twrp version?
Click to expand...
Click to collapse
What twrp version are you using and could you please outline how you updated OOS 9.0.16 so i can follow the same path.
a4abbas said:
What twrp version are you using and could you please outline how you updated OOS 9.0.16 so i can follow the same path.
Click to expand...
Click to collapse
Hmm sorry, do 't remember.
I guess it was the latest Twrp at that time, I switched to op7 non-root for a while now...
the 6t was derooted and given to my s.o.
Shady282 said:
Hi All, I was on 9.0.14 and now I installed the latest OOS 9.0.16 through TWRP. All went well except i flashed magisk root.
I flashed the latest magisk 19.3 and 19.1 and all got me stuck on oneplus loading screen the red circle and white circle turning infinitely.
Then i tried magisk 18.1, everything loaded fine but magisk seems to be causing errors and not rooted. as i tried to grant nova launcher root, the app freezed and got stuck and force closed.
Also other apps that requires root are not able to request root.
any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Have you found any solutions to it yet? Please advice