Related
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
Hi guys,
I need a proper guide how to install/flash magisk on RR Oreo.
Try to flash it through TWRP and no go. Seems likely i need to flash stock image or probably stock recovery.
Thanks.
same here
For me it's working on any Oreo, just flash in twrp.
If you don't see magisk app after reboot just do another reboot and it'll be there.
Sent from my HTC One using XDA Labs
Hi,
i have an general Question in which sequence the root might been installed? On my OP2 should be working Lineage so does the root installed after flashing custom rom und gapps or before? Lineage overwrite an existing root if i didnt flash in a correct sequence.
Or is it possible that Magisk 18.1 are incompatible with Lineage 15.1?
If someone can answer this question it will makes the flashing procedere for my first time safer.
Best regards
sense92 said:
Hi,
i have an general Question in which sequence the root might been installed? On my OP2 should be working Lineage so does the root installed after flashing custom rom und gapps or before? Lineage overwrite an existing root if i didnt flash in a correct sequence.
Or is it possible that Magisk 18.1 are incompatible with Lineage 15.1?
If someone can answer this question it will makes the flashing procedere for my first time safer.
Best regards
Click to expand...
Click to collapse
flash lineage+gapps, reboot and do the initial setup, reboot in twrp and flash magisk, reboot and install magisk manager manually(lately it's not installed automatically for some reason and root doesn't work without the app).
Hi All,
I have been running Lineage OS since it became available for OnePlus 5 with the Safety Net successfully being passed using Magisk and using firmware and modems from jamal2367.
That was up until Lineage required an updated firmware/modem to 5.1.4 and I found jamal2367 has stopped doing the firmware and modem for the OnePlus 5. I installed the firmware from shadowstep the new firmware provider and now I fail the safety net checks.
I have tired the following:
Flashing multiple weekly releases of Lineage OS
Flashing new version of TWRP
Flashing new version of TWRP blu_spark
Flashing new version of TWRP codeworkx
Flashing the ElementalX-OP5-3.10.zip
Flashing Boeffla-Kernel-2.0
Flashing blu_spark_r132
Flashing OSS 5.1.4
Flashing OSS 5.1.5
all with Magisk 17.1 installed
All with full wipes including the sdcard
The only thing that worked was installing OSS 5.1.5 with and relocking the bootloader.
Does anybody know what I have missed and how I can get the Safety Net to pass the ctsProfile.
Thanks in advance.
alrighte_then said:
Does anybody know what I have missed and how I can get the Safety Net to pass the ctsProfile.
Thanks in advance.
Click to expand...
Click to collapse
Relocking the Bootloader will of course work but you didn't need to do that.
What you missed:
That version of Magisk is clearly not working well with your setup and not hiding your Bootloader state properly. (Providing you set it up correctly).
Had you done all those steps without Magisk it would have passed. The custom Kernels alone would have gotten you a Pass due to them ignoring the Verified Boot state.
So, LOS+Kernel = Pass. If you need Magisk, try to find a version that is working properly with your setup. With Magisk working properly the custom Kernel is then optional.
Also, TWRP has nothing to do with it. Just use the latest Codeworkx.
Hi Dirk,
Thanks for your response, I have just tied to install it in the order you suggested
I install TWRP (twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img)
I wiped everything including sdcard
I installed Element Kernel (ElementalX-OP5-3.10.zip)
I installed Lineage OS (lineage-15.1-20180903-nightly-cheeseburger-signed.zip)
I installed Gapps (MindTheGapps-8.1.0-arm64-20180808_153856.zip)
I installed a safety net tester called safetyNet 'attest'
When I run the safetynet test I am still getting CTS profile match: false.
Any ideas what I can do next to make this work?
Thanks for any help
alrighte_then said:
Hi Dirk,
Thanks for your response, I have just tied to install it in the order you suggested
I install TWRP (twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img)
I wiped everything including sdcard
I installed Element Kernel (ElementalX-OP5-3.10.zip)
I installed Lineage OS (lineage-15.1-20180903-nightly-cheeseburger-signed.zip)
I installed Gapps (MindTheGapps-8.1.0-arm64-20180808_153856.zip)
I installed a safety net tester called safetyNet 'attest'
When I run the safetynet test I am still getting CTS profile match: false.
Any ideas what I can do next to make this work?
Thanks for any help
Click to expand...
Click to collapse
You flashed the Kernel before the ROM, so you overwrote that Kernel with the LOS one. Flash LOS then the custom Kernel.
On Magisk.. i've seen many people complain that they can't get the latest version to pass Safetynet. Again, it could just be people not configuring it correctly, or it might be better to try the previous version. Just to make sure you should tell us what you do to set it up.
You need to Hide Play Store, Banking Apps etc, and Magisk Manager too i believe. If you install Magisk and set it up when your current state is 'Uncertified', you will need to clear Data/Cache on Play Store for it to change to 'Certified'.
Also, don't rely on 'Safetynet Checker' apps. If the Play Store settings say 'Certified' try an app like Google Pay. It should work fine.
If you get cts profile mismatch. Download CTS props config from magisk modules and you will pass
Download magisk 17.1
Hi All,
Just to give you an update one where I got to with this.....
You where right the newer builds of Lineage OS do not pass safety net but the older ones do.
So after much playing around I and many flashes and wipes I found it impossible to boot a Lineage with a custom kernel, I believe this is probably down to the forced encryption.
The thing that worked for me in the end was installing "MagiskHide Props Config" and changing the figure print, I am it is very similar to the module Jamie suggested.
So I now have Lineage OS working fully with root, magisk and passing SafetyNet
Thanks everyone for you help.
The thing that worked for me in the end was installing "MagiskHide Props Config" and changing the figure print, I am it is very similar to the module Jamie suggested.
So I now have Lineage OS working fully with root, magisk and passing SafetyNet
Thanks everyone for you help.[/QUOTE]
Hello; can you explain to me in detail, step by step, how to do it? Thanks in advance.
" changing the figure print"
Guys,
Anyone successful so far in setting up Magisk 17.1 on stock B35 A2017U + TWRP 3.2.1.0?
I tried following ways but everytime I flash the Magisk 17.1 using TWRP, it boot loops to recovery mode. I tried clearing Dalvik + cache everytime but in vain.
1. Install Magisk 5.9.1 -> uncheck encryption, uncheck "restore dm-verify" -> Boot into TWRP and flash Magisk 17.1 -> Clear Dalvik+Cache and Restart -> Recovery Bootloop.
2. Flash Super SU, Install Magisk 5.9.1 -> uncheck encryption, uncheck "restore dm-verify" -> Boot into TWRP and flash Magisk 17.1 -> Clear Dalvik+Cache and Restart -> Recovery Bootloop
I cannot use Super SU, blanket root due to bank & workplace apps security restrictions.
Any help/guidance will be is appreciated.
Cheers
Any reason you need 17.1? If there's no pressing need go with something like 16.4. Seems to work better for some folks.
marcdw said:
Any reason you need 17.1? If there's no pressing need go with something like 16.4. Seems to work better for some folks.
Click to expand...
Click to collapse
Thanks.
Thinking of trying with v16.7 first. If that works then great.
mandrax.prime said:
Thanks.
Thinking of trying with v16.7 first. If that works then great.
Click to expand...
Click to collapse
it does. i'm staying on 16.7
It would be nice to always have a working version of Magisk as Google updates their Safety Net. We have to update as they update.
I ran into problems today with Magisk 18.1 on the latest official LineageOS 15.1, nothing I did was able to get magisk to work (no icon, no error messages).
Has anyone else tried?
Magisk should work fine on LOS, I use it (Magisk) when I have to (i.e. when there is a particular use for it, like converting a systemless mod to a system-installed mod).
On B35, no go, phone will bootloop. Magisk should work fine on stock ROMs up to B15 N, maybe also with the B25 and B32 OTAs too. I'm not a ZTE stock ROM fan, I dont spend alot of time rooting stock, but from the few tests I did,those were my results.
If you have an exFAT SD card, installing Magisk on stock ROM may make your SD falsely show up as corrupt, only solution is to use the inferior/antiquated FAT32 filesystem.
Maybe one day I'll write my own open source root solution, just to show the Android community that Magisk isnt the only game in town for rooting modern ROMs on modern devices. I dont need to hide from SafetyNet, I dont need stupid systemless mods, I just need root that work reliably. I know this will fall on deaf ears, but Magisk is more trouble than it's worth, I'd recommend staying unrooted instead of using it. @topjohnwu is a genius and means well, I'm sure, but in the real world Magisk just isnt reliable enough.
I tried Magisk 17.3, 18.0, and 18.1 on Axon 7 B19 and B35- bootloop on every try
G935FD
So I’m getting this in my Samsung S7 edge exynos with latest stock rom 8.0
¤Magisk 18.1 and magisk manager 7.1.1¤
Format /data,
restore stock boot.img to install magisk zip
install remove encryption,
install Magisk 18.1,
Reboot system.
After reboot to twrp, /data is again encrypted.
(But the data remains unencrypted when rooted with SuperSu)
☆Please tell me how do I keep my data in twrp unencrypted while keeping magisk installed☆
《Any help is greatly appreciated》
You can flash the modded twrp with encryption support so you don't need to remove encryption of your device.
the latest one I'm using is the one on my signature.
If you wan't to keep device unecryped anyways use this video for as a guide, this is the first guide I used before using xda forums: https://www.youtube.com/watch?v=JwLja68KmKM