Hi there,
A quick question - has someone here recently updated to Magisk 13.3 / Magisk Manager 5?
I am currently on Magisk 12.0 / Manager 4.3.3 (Resurrection Remix) and would like to update as Safety Check is failing after the Playstore update.
However according to this thread
https://forum.xda-developers.com/showpost.php?p=73142437&postcount=17290
there is a problem with the Axon 7 and the latest Magisk...
So which version is everyone one using and how did you get there (update Magisk first/Manager first...)?
(Magisk Manager is prompting me to update to 13.1 at the moment - not sure that's wise then?)
I updated to magisk 13.3 using magisk manager. Everything went smoothly and safety net passes even with a few modules installed. I was using A2017G on stock B05
Grogros4 said:
I updated to magisk 13.3 using magisk manager. Everything went smoothly and safety net passes even with a few modules installed. I was using A2017G on stock B05
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - when you updated to Magisk 13, did you already use Manager version 5 or are/were you still on version 4 and updated afterwards?
I am not sure.... I think I was running magisk 13 beta so I guess I was using magisk manager 5
I'm using magisk 13.3 with manager 5.1.1 on a stock chinese rom. I already fixed my issues regarding our unit which crashes the manager after giving su permissions.
After installing magisk in twrp and booting into system, open terminal manager and type these codes.
Code:
su
cd /data/data/com.topjohnwu.magisk/
mkdir /sdcard/Android/data/com.topjohnwu.magisk
cp -R ./databases /sdcard/Android/data/com.topjohnwu.magisk/
mv databases .databases_old
ln -s /sdcard/Android/data/com.topjohnwu.magisk/databases databases
chcon -h "u:object_r:app_data_file:s0:c512,c768" "/data/data/com.topjohnwu.magisk/databases"
Credits to @zorgzd for his fix.
Thanks a lot both of you -
I'll try the fix once I updated, that's really helpful. (Still wondering if I should try to update to Magisk 13 from Manager 4 and then install the Manager 5 apk after reboot...).
Whoooo? said:
Thanks a lot both of you -
I'll try the fix once I updated, that's really helpful. (Still wondering if I should try to update to Magisk 13 from Manager 4 and then install the Manager 5 apk after reboot...).
Click to expand...
Click to collapse
I would suggest to remove your old magisk using the latest uninstaller flashed in twrp. That will also install manager v4.
Then restore your boot.img backup if you have any.
And lastly, flash the latest version, 13.3 as of writing. It contains the latest manager also included in the zip.
Related
hello who got safty net failed in magisk here is solution
first clean flash rr i mean only wipe system partition
use rr bulid 16 march
reboot and check supersu and busybox install if yes then full unroot supersu and uninstall buybox using buybox app
and disable usb debugging
and then reboot to recover and install magisk 11.5
reboot
now install magisk a manger (if you not loss root then reboot then reboot one or 2 time if will get it)
magisk manager setting-check magisk hide and adblock host
and uncheck busybox see pic in attachment for reference
now reboot now you will able to bypass satynet as well as no loss of root and busybox will work even it disbale in magisk manager
remember do not modified any system partition
and don't install any sound mod
use magisk version dobly and viber4android
magisk version of unified adblocked
magisk verson of youtube adblock patched apk
and yes one more thing i forget
plz check two file su and busybox in system/bin and system/xbin if you found these plz delete then using twrp filemanager(remember to mount system) and use stock kernal
i tested this methode on rr
u can try in other rom as well as stock miui rom but before if you used xposed then install it first and use magisk version of xposed for miui or stock
hit thanks button if i help
:highfive:HELLO GUYS
So Here u can Find How To Bypass Safetnet In Your Phone While Being Rooted.
As you all know safetynet is implemented by Google itself to check Security of your Device & also by Some games or apps Eg. Pokeman Go,Android pay,Snapchat etc. So If Your Phone Is Rooted SafetyNet Test Will Fail.
With failed Safetynet Test You Can't Run These Apps in Your Mobile.
Check your Safetynet Status By This App:- https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
So If your Test Failed And you can't able to run Games or Some Apps Try This method
1. Fully Unroot Your Phone In SuperSu app Go to Settings tab on the top right corner, and then click Full Unroot. Confirm with 'Continue'. 3. Once this operation is done, which takes a few minutes, you can reboot your Android & Then Flash This Unroot Script In Custom Recovery
https://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
2. Download Magisk 12.0 http://tiny.cc/latestmagisk and Flash it in Custom Recovery & Reboot **Make sure in custom recovery if a Line Appears "Boot img already patched" That means You'r Not Fully Unrooted in this case you have to flash your Stock System.img or Stock rom**
3. Now Install Magisk Manager From Play Store https://play.google.com/store/apps/details?id=com.topjohnwu.magisk
4 In Magisk manager Go To Settings Click on Enable BusyBox & Magisk Hide
5. Thats it. Now Run Safetynet test in Magisk Manager It will pass.
6.Enjoy your Games or Apps
UPDATE :- With Android Security Patch 01/04/2016 On Marshmallow Flashed SuperSu 2.79 Flashed Suhide 0.55 Flashed Magisk 12.0 Flashed Xposed 87.0 Systemless PASSING SAFETY NET Without Disabling root
Credits :-
@topjohnwu For Magisk 12.0 & Magisk Manager App
@halifax For Unroot Su Script
Hey, I have a problem:
I used this script on my Galaxy Nexus but now I decided to use SuperSU again because Magsik didn't work for me. I have just one problem: After using this script I can't install SuperSU anymore. The installation works as usual without problems but if I open the SU app it sais I need a Su file flashed. Could you please help me to fix thid problem?
Thanks in advance,
greetings Nils
yo_honey said:
:highfive:HELLO GUYS
So Here u can Find How To Bypass Safetnet In Your Phone While Being Rooted.
.....
1. Fully Unroot Your Phone In SuperSu app Go to Settings tab on the top right corner, and then click Full Unroot. Confirm with 'Continue'. 3. Once this operation is done, which takes a few minutes, you can reboot your Android & Then Flash This Unroot Script In Custom Recovery
https://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
2. Download Magisk 12.0 http://tiny.cc/latestmagisk and Flash it in Custom Recovery & Reboot **Make sure in custom recovery if a Line Appears "Boot img already patched" That means You'r Not Fully Unrooted in this case you have to flash your Stock System.img or Stock rom**
3. Now Install Magisk Manager From Play Store https://play.google.com/store/apps/details?id=com.topjohnwu.magisk
4 In Magisk manager Go To Settings Click on Enable BusyBox & Magisk Hide
5. Thats it. Now Run Safetynet test in Magisk Manager It will pass.
6.Enjoy your Games or Apps
UPDATE :- With Android Security Patch 01/04/2016 On Marshmallow Flashed SuperSu 2.79 Flashed Suhide 0.55 Flashed Magisk 12.0 Flashed Xposed 87.0 Systemless PASSING SAFETY NET Without Disabling root
Credits :-
@topjohnwu For Magisk 12.0 & Magisk Manager App
@halifax For Unroot Su Script
Click to expand...
Click to collapse
Thanks my friend, u save my day, Samsung S6 Edge +.
Flash Latest SuperSu Zip in custom recovery
MrFlashGame said:
Hey, I have a problem:
I used this script on my Galaxy Nexus but now I decided to use SuperSU again because Magsik didn't work for me. I have just one problem: After using this script I can't install SuperSU anymore. The installation works as usual without problems but if I open the SU app it sais I need a Su file flashed. Could you please help me to fix thid problem?
Thanks in advance,
greetings Nils
Click to expand...
Click to collapse
Download Latest Stable version of SuperSu zip And Flash it Using Custom Recovery. This may solve your problem.
Hello, anyone have boot img for htc 820 dual sim?
Thank you
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
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
History:
After I change the kernel I lost the root! Then I tried to update the Magisk to version 18 and the Magisk Manager to a most recent version that I don't remember its version.... But my phone continued without root.
Trying to solve this again I install Magisk 16.3 and Magisk Manager 5.6.4 downloading and installing the files available in this link: https://www.stechguide.com/download-magisk-v16-3/
Without success too!
-
So, darlings.
I'm asking for a tutorial to uninstall all the Magisk things of my phone (if you experts think it is necessary) and I'm asking for a tutorial to root again my phone with Magisk.
And I'm also asking to know the latest STABLE version of Magisk and of Magisk Manager COMPATIBLE with my phone and that will work well!
I have a Galaxy Note 3 (SM-N9005) with [ROM][C9 Pro Port][N900X] AspireTeam C9 Pro v5.0 [18.5.18][Aroma/Smooth/Modded] installed.
Thank you so much!!!
LeandritoG said:
History:
After I change the kernel I lost the root! Then I tried to update the Magisk to version 18 and the Magisk Manager to a most recent version that I don't remember its version.... But my phone continued without root.
Trying to solve this again I install Magisk 16.3 and Magisk Manager 5.6.4 downloading and installing the files available in this link: https://www.stechguide.com/download-magisk-v16-3/
Without success too!
So, darlings.
I'm asking for a tutorial to uninstall all the Magisk things of my phone (if you experts think it is necessary) and I'm asking for a tutorial to root again my phone with Magisk.
And I'm also asking to know the latest STABLE version of Magisk and of Magisk Manager COMPATIBLE with my phone and that will work well!
I have a Galaxy Note 3 (SM-N9005) with [ROM][C9 Pro Port][N900X] AspireTeam C9 Pro v5.0 [18.5.18][Aroma/Smooth/Modded] installed.
Thank you so much!!!
Click to expand...
Click to collapse
First, Magisk is one of the most documented tools on xda, has its own official forum and especialy its official releases on GitHub (where all versions are available). It's useless to get it elsewhere.
Second, Magisk will only do his magic on an already flashed kernel. If you flash kernel after Magisk, you won't get root.
Third, Magisk flashable zip contains the corresponding Manager and will inject it systematically.
Finaly, you need TWRP for a successful flash of Magisk. With other custom recoveries, errors like "can't find the boot image" can happens.
Now, for a complete removal of Magisk from the system, you only have to flash the latest official uninstaller.
After reboot, go to recovery, flash your prefered kernel then flash Magisk. The latest stable version is v18 and will work well on your rom.
...