EDIT: Unfortunatelly this is not working any more due to recent SafetyNet updates
Hello everyone. This is first guide i'm trying to write here so don't be to harsh for me also sorry for my english, it's not my native language.
After almost 3 days of messing with various roms and kernels i finally managed to successfully installl Magisk V6 on my Z3 D6633 (yes, Pokemon Go 0.37 works too ) .
First of all you need unlocked bootloader. Without it you won't be able to flash custom kernel. Also, if your kernel is still locked, and you want to unlock it remember that doing so will wipe all data from your device, so backup everything that is important to you prior to following this guide.
This is the setup that works for me:
SLiMM 3.1 rom by Wajk:
http://forum.xda-developers.com/z3/development/rom-slimm-t3359907
Advanced stock/beta kernel Marshmallow 6.0.1 - 06/aug/2016 by Gustavo RD78:
http://forum.xda-developers.com/z3/development/kernel-advanced-stock-kernel-t3345880
Magisk v6 - The Universal Systemless Interface by topjohnwu:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Here are the steps:
1. flash rom with 6633 patch, reboot
2. full unroot and clean in SuperSU, reboot
3. flash kernel, reboot
4. flash Magisk V6 and PHH root, reboot
5. install PHH root from play store and Magisk Manager
I used SafetyNet Helper to verify if SafetyNet is working several times during all those steps:
after 1 - not working,
after 2 - working,
after 3 - working,
after 4 - not working,
after 5 - not working,
after disabling root in Magisk Manager - working.
Hope it helps someone
Hi,
For this tutorial I still need the unlocked bootloader?
Regards!
ask the following I
is a LB or UB requirement ?
If the Rom matter as long as the kernel is flashed ?
If the whole with D6603 ?
Thanks for your tutorial
adripred said:
Hi,
For this tutorial I still need the unlocked bootloader?
Regards!
Click to expand...
Click to collapse
smellz said:
ask the following I
is a LB or UB requirement ?
If the Rom matter as long as the kernel is flashed ?
If the whole with D6603 ?
Thanks for your tutorial
Click to expand...
Click to collapse
I haven't try with locked bootloader, because I unlocked mine a while ago, but in the kernel thread there is info that unlocked bootloader is required. It might be possible to do it with other roms, as long as they work with Advanced Stock Kernel from the link in first post. D6603 should work too, only difference is that you don't need dual sim patch for SLiMM 3.1 rom
I must have had a similar problem to you originally, I had a working D6603 with a Rooted Marshmellow 6 Rom.
Then, performed the following Steps;
1. Unroot (Inside the SuperSU App)
2. Booted into TWRP and flashed Magisk - v6
3. Then Flashed phh 's systemless superuser
I rebooted the phone and now it is not working. Does not Boot, Black Screen.
The Led will flash red quickly and I am not able to boot into TWRP.
I can see the Phone is Recognised by the Computer (S1 /SOMC Flash Device in Device Manager.)
Could someone please post step by step instructions to restore a to Marshmellow Rom (Any)?
Will I have to download an Image and a Flashtool?
same problem here. I manage to boot to twrp by flashing back the recovery image using fastboot.
Z3- said:
I must have had a similar problem to you originally, I had a working D6603 with a Rooted Marshmellow 6 Rom.
Then, performed the following Steps;
1. Unroot (Inside the SuperSU App)
2. Booted into TWRP and flashed Magisk - v6
3. Then Flashed phh 's systemless superuser
I rebooted the phone and now it is not working. Does not Boot, Black Screen.
The Led will flash red quickly and I am not able to boot into TWRP.
I can see the Phone is Recognised by the Computer (S1 /SOMC Flash Device in Device Manager.)
Could someone please post step by step instructions to restore a to Marshmellow Rom (Any)?
Will I have to download an Image and a Flashtool?
Click to expand...
Click to collapse
Resolved using Emma. I installed the S1 SOMC Flash Device Drivers and I was able to download lollypop.
I will attempt now to reinstall recovery, new rom, and Magisk
Guide helped alot thanks!
Important part was to uninstall SuperSU. Before that ROM appeared to reject the kernel or vice versa, but now it boots on Fragment ROM and unmount seems to work!
Better be worth unlocking the BL
Z3- said:
I must have had a similar problem to you originally, I had a working D6603 with a Rooted Marshmellow 6 Rom.
Then, performed the following Steps;
1. Unroot (Inside the SuperSU App)
2. Booted into TWRP and flashed Magisk - v6
3. Then Flashed phh 's systemless superuser
I rebooted the phone and now it is not working. Does not Boot, Black Screen.
The Led will flash red quickly and I am not able to boot into TWRP.
I can see the Phone is Recognised by the Computer (S1 /SOMC Flash Device in Device Manager.)
Could someone please post step by step instructions to restore a to Marshmellow Rom (Any)?
Will I have to download an Image and a Flashtool?
Click to expand...
Click to collapse
Just flash stock kernel with flashtool.
This Process worked for Me - D6603
1. flash SLIM Rom 6603 and reboot
2. Disable SuperSu, Unroot SuperSu, Boot to Recovery and Wipe Davilk, Reboot
3. Reboot to Recovery, Flash Advanced Kernel, Reboot
4. Flash Magisk V6 and PHH root, Reboot
5. install PHH Super from play store and Magisk Manager
Thanks for the tuto.
Of course you need to have Unlocked Bootloader, this is the principle of flashing a custom kernel. And systemless root like magisk needs custom kernel. With LB you will not boost after flashing a custom kernel.
kotlin said:
Hello everyone. This is first guide i'm trying to write here so don't be to harsh for me also sorry for my english, it's not my native language.
After almost 3 days of messing with various roms and kernels i finally managed to successfully installl Magisk V6 on my Z3 D6633 (yes, Pokemon Go 0.37 works too ) .
This is the setup that works for me:
SLiMM 3.1 rom by Wajk:
http://forum.xda-developers.com/z3/development/rom-slimm-t3359907
Advanced stock/beta kernel Marshmallow 6.0.1 - 06/aug/2016 by Gustavo RD78:
http://forum.xda-developers.com/z3/development/kernel-advanced-stock-kernel-t3345880
Magisk v6 - The Universal Systemless Interface by topjohnwu:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Here are the steps:
1. flash rom with 6633 patch, reboot
2. full unroot and clean in SuperSU, reboot
3. flash kernel, reboot
4. flash Magisk V6 and PHH root, reboot
5. install PHH root from play store and Magisk Manager
I used SafetyNet Helper to verify if SafetyNet is working several times during all those steps:
after 1 - not working,
after 2 - working,
after 3 - working,
after 4 - not working,
after 5 - not working,
after disabling root in Magisk Manager - working.
Hope it helps someone
Click to expand...
Click to collapse
thanks for sharing this... and did you try to install Systemless Xposed? is it working on your Z3?
It didnt work for me... the Magisk manager cannot toggle Root...it just greyed out...
kotlin said:
Hello everyone. This is first guide i'm trying to write here so don't be to harsh for me also sorry for my english, it's not my native language.
After almost 3 days of messing with various roms and kernels i finally managed to successfully installl Magisk V6 on my Z3 D6633 (yes, Pokemon Go 0.37 works too ) .
This is the setup that works for me:
SLiMM 3.1 rom by Wajk:
http://forum.xda-developers.com/z3/development/rom-slimm-t3359907
Advanced stock/beta kernel Marshmallow 6.0.1 - 06/aug/2016 by Gustavo RD78:
http://forum.xda-developers.com/z3/development/kernel-advanced-stock-kernel-t3345880
Magisk v6 - The Universal Systemless Interface by topjohnwu:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Here are the steps:
1. flash rom with 6633 patch, reboot
2. full unroot and clean in SuperSU, reboot
3. flash kernel, reboot
4. flash Magisk V6 and PHH root, reboot
5. install PHH root from play store and Magisk Manager
I used SafetyNet Helper to verify if SafetyNet is working several times during all those steps:
after 1 - not working,
after 2 - working,
after 3 - working,
after 4 - not working,
after 5 - not working,
after disabling root in Magisk Manager - working.
Hope it helps someone
Click to expand...
Click to collapse
thnx for this workaround. if you follow it to the letter, you should be fine, else it won't work, and you still get "cts profile match: false"
( it cost me 2 attempts because i flashed the kernel directly)
finally there is someone who desire to create specific systemless method with magisk for xperia device line
unfortunately I've tried earlier than this thread exist so I have to clearance to noob xperia user, here's my post
ryandxter said:
well well I'm here just to give specific classification / explanation about what is this projects do
I'm here to say that this method is about modifying boot partition to make systemless works (correct me if I'm wrong), since my device was Xperia Z3 then this require "unlocked bootloader" for any Xperia device in case to use custom boot.img script from this projects... please please OP underline this before another people from Xperia users with locked bootloader flash this projects, thanks
I'm already tried on myself almost hardbricking my phone and this isn't funny
Click to expand...
Click to collapse
that's mean xperia device line (no exception) need to be Unlocked Bootloader before flashing magisk otherwise the'll soft brick
hi mr @kotlin can you add this to OP for specific clarification?
that's mean xperia device line (no exception) need to be Unlocked Bootloader before flashing magisk otherwise the'll soft brick
hi mr @kotlin can you add this to OP for specific clarification?
Click to expand...
Click to collapse
and don't forget that unlocking the bootloader is easy, but your phone will be wiped clean.
( i forgot about that....)
Z3- said:
This Process worked for Me - D6603
1. flash SLIM Rom 6603 and reboot
2. Disable SuperSu, Unroot SuperSu, Boot to Recovery and Wipe Davilk, Reboot
3. Reboot to Recovery, Flash Advanced Kernel, Reboot
4. Flash Magisk V6 and PHH root, Reboot
5. install PHH Super from play store and Magisk Manager
Click to expand...
Click to collapse
This worked for me!
ataraxist said:
thanks for sharing this... and did you try to install Systemless Xposed? is it working on your Z3?
It didnt work for me... the Magisk manager cannot toggle Root...it just greyed out...
Click to expand...
Click to collapse
Yes I installed Systemless Xposed from magisk thread, it works like a charm, hadn't any problems Did you followed all the steps? It's order is very important. You have unlocked bl? I just put info in op that it is necessary. For me toggle root was greyed out when i didn't properly flashed magisk to kernel, or after restoring kernel. Try to make backup and follow the steps again.
ryandxter said:
finally there is someone who desire to create specific systemless method with magisk for xperia device line
unfortunately I've tried earlier than this thread exist so I have to clearance to noob xperia user, here's my post
that's mean xperia device line (no exception) need to be Unlocked Bootloader before flashing magisk otherwise the'll soft brick
hi mr @kotlin can you add this to OP for specific clarification?
Click to expand...
Click to collapse
Thanks, just did that
kotlin said:
Yes I installed Systemless Xposed from magisk thread, it works like a charm, hadn't any problems Did you followed all the steps? It's order is very important. You have unlocked bl? I just put info in op that it is necessary. For me toggle root was greyed out when i didn't properly flashed magisk to kernel, or after restoring kernel. Try to make backup and follow the steps again.
Thanks, just did that
Click to expand...
Click to collapse
I'm coming from Xperia Z... not z3
can't be sure if the problem is coming from different advance stock kernel...
Thanks for sharing the steps...I will try again when I have time...
I finally got it working after several attempts. Everyting went well with unlocking the bootloader and installing the rom.
In magisk manager i got Selinux toggle working for me. I just cant use the root toggle. The toggle is on, and if i want to disable it it says: magisk manager is granted superuser acces. Then it turns the toggle back on. Should i not grant SU acces to the magisk manager or is there another problem?
I've had this working a while and even used Android Pay for the first time. However Viper4Android doesn't seem to be working well and sounds are too quiet do any existing mods still work or would they break SafetyNet?
Related
Hi,
Wondering if anyone has succeeded in using Android Pay on their Mi Note 2?
I have the bootloader unlocked on mine and while I've had a play with Magisk and such, unsurprisingly since the bootloader is unlocked I'm not getting anywhere.
I'm aware there are kernel hacks that can return support to unlocked devices but I'm having a hard time telling if I'd require the full kernel source in order to implement them or if there are any other ways around this or if it is simply to MIUI being an unsupported ROM. I have heard that running stock MIUI with a an originally locked bootloader still fails SafetyNet and is incompatible. With the difficulties Xiaomi place on unlocking/relocking the bootloader etc
I was hoping someone who is still running stock would be able to verify it works on a stock device
If you could also post a screenshot of the ROM you're using that would be great. With so many devices shipping with vendor ROMs rather than the official it only complicates things further.
I'm happy to keep trying and post a tutorial for others if I can get it working but frankly at this stage if the issue is MIUI itself rather than the state of the bootlock then I'd rather not waste any more hours on this.
Cheers,
StoneTrap
Can confirm Android Pay works - I am using a rom provided by Hong Kong Goldway. I haven't rooted yet but I will see if it works afterwards.
thedeejay said:
Can confirm Android Pay works - I am using MIUI Global Stable 8.0.9.0.0. I haven't rooted yet but I will see if it works afterwards.
Click to expand...
Click to collapse
That's great to know.
I'm guessing your bootloader is still locked if you're unrooted. I'm fairly sure that's the only thing left tripping safetynet. AFAIK there's no bypass until we can build our own kernel but I'd love for someone to porve me wrong.
Did you try to lock bootloader again?
I think the Magisk trick is for hiding root, not unlocked bootloader.
terstor said:
Did you try to lock bootloader again?
I think the Magisk trick is for hiding root, not unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the reply.
Like I said, I realise the issue is the unlocked bootloader. I know what Magisk is for
What I was asking is if a full kernel source is needed to build a hacked kernel that supports an unlocked bootloader meeting SafetyNet or if there are is any way of patching or rebuilding a pre-existing one?
There are already compatibility issues with some MIUI versions and Android Pay even with a locked bootloader. Rather than testing every rom myself I was wondering if anyone here had any experience with it working on a certain rom.
I know that you know
I'm just curious if android pay will work again if you lock bootloader again for example using 'fastboot oem lock'.
If someone is unlocking bootloader to install custom recovery only, it would be good idea to unlock -> install recovery -> lock -> install android Pay.
But does anyone know if this will work? Is this fastboot "lock" differs from the original "lock"?
terstor said:
I know that you know
I'm just curious if android pay will work again if you lock bootloader again for example using 'fastboot oem lock'.
If someone is unlocking bootloader to install custom recovery only, it would be good idea to unlock -> install recovery -> lock -> install android Pay.
But does anyone know if this will work? Is this fastboot "lock" differs from the original "lock"?
Click to expand...
Click to collapse
Ah sorry it's hard to tell sometimes when people are making posts just to hit that first 5 posts for access. If there was a signed recovery file, Magisk would be perfect for all sorts of hi-jinx (Like for example on the ZTE Axon 7)
Unfortunately because of the way xiaomi controls unlocking the bootloader there is no way to have a custom recovery and a locked bootloader. The recovery would have to be signed by xiaomi in order to boot it.
Signing system components isn't something I know much about, all we seem to have access to is the firehose in the fastboot images but even then with the way xiaomi have locked down fastboot it seems to require some kind of authorisation first.
I was able to flash the custom recovery with a locked bootloader by modifying a fastboot image before flashing and reclocking. This just forces the phone into EDL mode when trying to boot into recovery. The system itself continues to work and will quickly overwrite the unsigned recovery with the MIUI one if an attempt to boot into recovery doesn't happen.
The locks are all the same, this can be checked with
Code:
fastboot oem device-status
on locked and unlocked phones.
Ok, so if I understood correctly, custom recovery will stop working when i will lock the bootloader.
Sorry for the little offtop, but i have another question connected with this issue. And i can't verify it by myself because i'm still waiting for unlock approval. What will happen in this scenerio:
stock rom *stable* (not dev) -> unlock bootloader -> install custom recovery -> flash eg. SuperSu.zip (to get root) via recovery -> instal magisk/xposed -> lock bootloader.
3 questions:
1. Will root 'survive' after locking or not?
2. Will xposed/magisk survive and works correctly or not?
3. OTA updates will be available or not?
I can confirm locking the boot loader and flashing original firmware global works with Android pay
Sent from my Mi Note 2 using Tapatalk
I am able to get Xiaomi Mi Note 2 and Android Pay working WITH Magisk and unlocked bootloader.
1. Install Magisk
2. Install this patch
There are some issues with files unmounting correctly. I had to manually stop and start magisk hide to get this working.
But right now, I have Android Pay confirmed working, with an unlocked phone.
thedeejay said:
I am able to get Xiaomi Mi Note 2 and Android Pay working WITH Magisk and unlocked bootloader.
1. Install Magisk
2. Install this patch
There are some issues with files unmounting correctly. I had to manually stop and start magisk hide to get this working.
But right now, I have Android Pay confirmed working, with an unlocked phone.
Click to expand...
Click to collapse
Sorry, I have one more question. Which root did you use? (SuperSU, MagiskSU, or ?)
Felixweaster said:
Sorry, I have one more question. Which root did you use? (SuperSU, MagiskSU, or ?)
Click to expand...
Click to collapse
MagiskSU
thedeejay said:
MagiskSU
Click to expand...
Click to collapse
Sorry, which ROM do you install in phone?
I installed the modified MIUI 8 China Developer ROM 7.5.6 without root in my phone.
After flash Magisk V.12 in twrp 3.0.2.0, the Magisk do nothing in my phone.
Felixweaster said:
Sorry, which ROM do you install in phone?
I installed the modified MIUI 8 China Developer ROM 7.5.6 without root in my phone.
After flash Magisk V.12 in twrp 3.0.2.0, the Magisk do nothing in my phone.
Click to expand...
Click to collapse
I am using MIUI Global Stable 8.2.5. However, with the patch (which I think you haven't installed), it shouldn't matter which ROM you are using - China or Global, Stable or Dev. What the patch does is mainly changes the build.prop to a recognised device version and a few other things on the back end to hide being unlocked.
thedeejay said:
I am using MIUI Global Stable 8.2.5. However, with the patch (which I think you haven't installed), it shouldn't matter which ROM you are using - China or Global, Stable or Dev. What the patch does is mainly changes the build.prop to a recognised device version and a few other things on the back end to hide being unlocked.
Click to expand...
Click to collapse
My problem is nothing working after flash Magisk only or with patch!! Q___Q!
I will test and discuss with other people and developer on Sunday with new ROM.
Thank you very much.
Felixweaster said:
My problem is nothing working after flash Magisk only or with patch!! Q___Q!
I will test and discuss with other people and developer on Sunday with new ROM.
Thank you very much.
Click to expand...
Click to collapse
Can you send a copy of your Magisk log? Go to Magisk -> Log and click on Magisk.
I have a feeling that the issue may be that Magisk might not be unmounting correctly. There is quite a bit of a discussion on this (as well as even MORE patches to get this to work)
(and to make sure, you also don't have xposed?)
thedeejay said:
Can you send a copy of your Magisk log? Go to Magisk -> Log and click on Magisk.
I have a feeling that the issue may be that Magisk might not be unmounting correctly. There is quite a bit of a discussion on this (as well as even MORE patches to get this to work)
(and to make sure, you also don't have xposed?)
Click to expand...
Click to collapse
You can find the log as attached.
I did NOT have xposed.
Felixweaster said:
You can find the log as attached.
I did NOT have xposed.
Click to expand...
Click to collapse
It is mounting xposed so you still have traces of it left. Go through these steps:
flash this file in TWRP: - Xposed Uninstaller
Reboot. Check if Magisk is working. If it is not, reboot back into TWRP and flash Magisk v12.0 again: Latest Magisk
Reboot. Do a few keypresses before going back into TWRP. Flash This patch here: Xiaomi safetynet fix v1.3
Reboot back into system, and check if SafetyNet is working (can be done in Magisk Manager). If it isn't, reboot into TWRP once again and flash THIS one here: Magisk v12.0 fix
(So total of 4 files that need to be flashed and cycled through).
Also make sure that you DO NOT clear cache/dalvik cache at any stage!
Give that a shot and let me know how it goes.
thedeejay said:
It is mounting xposed so you still have traces of it left. Go through these steps:
flash this file in TWRP: - Xposed Uninstaller
Reboot. Check if Magisk is working. If it is not, reboot back into TWRP and flash Magisk v12.0 again: Latest Magisk
Reboot. Do a few keypresses before going back into TWRP. Flash This patch here: Xiaomi safetynet fix v1.3
Reboot back into system, and check if SafetyNet is working (can be done in Magisk Manager). If it isn't, reboot into TWRP once again and flash THIS one here: Magisk v12.0 fix
(So total of 4 files that need to be flashed and cycled through).
Also make sure that you DO NOT clear cache/dalvik cache at any stage!
Give that a shot and let me know how it goes.
Click to expand...
Click to collapse
After flash Xposed Uninstaller & reboot => magisk nothing working
After flash Magisk v12.0 => magisk nothing working
After flash Magisk v12.0 again & Xiaomi safetynet fix v1.3 => magisk nothing working
After flash Magisk v12.0 again & Xiaomi safetynet fix v1.3 again & Magisk v12.0 fix => magisk nothing working
After flash Xiaomi official root
I get the same error log as attached.
I also attach the recovery log in attachment.
When I check the recovery log, there are something strange as below.
============
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
grep: init.rc: No such file or directory
sed: init.rc: No such file or directory
sed: init.rc: No such file or directory
Cannot open init.rc
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Cannot find the file entry [sepolicy]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Can't open 'sepolicy': No such file or directory
Could not load policy
Cannot open sepolicy
......
......
- Flashing new boot image
I:Set overlay: ''
5745+0 records in
5745+0 records out
23531520 bytes (22.4MB) copied, 0.291553 seconds, 77.0MB/s
- Unmounting partitions
losetup: /dev/block/loop0: No such device or address
umount: can't unmount /system: Device or resource busy
- Done
I:Updater process ended with RC=0
I:Legacy property environment disabled.
I:Install took 30 second(s).
I:Install zip Success,and install cofface-no-verity by cofface.
================
1. After flash the TWRP Unofficial TWRP 3.1.0-0 Mi Note 2 (scorpio)
2. Mount the /system read-write (I'm NOT sure do it cause something wrong?)
3. flash Magisk v12.0 => magisk working, saftnet false
4. Xiaomi safetynet fix v1.3 => magisk working, saftnet false
5. flash Magisk v12.0 fix => magisk working, saftnet true (before check saftnet, I found Magisk Hide in Magisk Manager and I also selected the safetynet attest app.)
Three more question
1. When you flash Magisk, is the /system read-only ?
2. Where do you have Magisk v12.0 fix ??
3. Why do you ask to flash Xiaomi safetynet fix v1.3 not Xiaomi safetynet fix v1.6 ?
thedeejay!! Thank you very much!!
: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
This is a guide for people who want a rooted MIUI. It will keep stock recovery and system partitions untouched to allow MIUI OTAs to install without problems. It will also pass Google's safety net test so bank apps keep working. The best of both worlds really
Requirements:
- Unlocked bootloader
- Windows PC
- fastboot (present in the miunlock app folder)
- Latest TWRP (download here)
- Latest Magisk (download here)
Steps:
- Install latest Magisk app
- Put latest Magisk zip on your device storage (SD)
- Shut down device
- put latest twrp.img in miunlock folder
- Connect phone to PC
- Press volume down and power button to boot to fastboot mode
- Open "Command Prompt" on your PC
- Type: (without quotes)
----- "cd C:\Users\[your name]\Desktop\miflash_unlock-en-2.3.803.10" . (or wherever the folder is)
----- "fastboot devices"
----- "fastboot boot twrp.img"
- In a few seconds, TWRP will boot on your phone. DO NOT swipe to make changes to system.
- In TWRP, flash the Magisk zip
Enjoy root
Disclaimer: I will not be help responsible for any damage or loss caused by following those steps.
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g
kn1g said:
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g
Click to expand...
Click to collapse
Same as my question. Let say system partition won't touch by root, but twrp is installed over the Mi stock recovery. Will it install Eta?
This guide DOES NOT flash TWRP. Stock recovery remains so OTA updates work.
The only thing that is touched by this guide is the "Boot" partition to install magisk. You can restore stock "Boot" using magisk manager's uninstall option at any moment and be 100% stock again.
Ok, but is Xposed etc. possible?
kn1g said:
Ok, but is Xposed etc. possible?
Click to expand...
Click to collapse
I haven’t tried but should work.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
It is really works! Thank you!
gonna check this cause i wanna root the phone but keep enjoying updates
I just rooted my Note 4 Qualcomm by this method, so far so good. Really easy and dummy-proof tutorial
I bump this because it worked. Quite easy, clean and fast. Thanx!
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?
masri.razak said:
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?
Click to expand...
Click to collapse
Wrong...u need to boot twrp not to install. Read the OP for steps.
Dadovvv said:
Wrong...u need to boot twrp not to install. Read the OP for steps.
Click to expand...
Click to collapse
Well... That's I mean, boot TWRP using adb
After have TWRP, how can i get update via OTA?
it successfully worked for Redmi Note 4 global beta/stable MIUI9.2
even installed camera api 2 using magisk module
Just a quick question. I've TWRP right now with SuperSU. So I'll remove SuperSU, flash Magisk in TWRP. All good till now, but I'd want the stock recovery, a flash-able zip maybe. How can I get it? From where?
**[EDIT]**
Okay. One can get it from fastboot ROMs available at MIUI website (here), extract the pack and get recovery.img.
Installed successfully on miui 9.2.1.0 stable
Now when a new update for magisk is released, how should i update it??
I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
I'd like to keep the phone untouched but I need to change emojis and with Xposed I can use Youtube in background.
Giacomo_ITA said:
I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
Click to expand...
Click to collapse
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)
Baxeisindi said:
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)
Click to expand...
Click to collapse
Do you mean this?
When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
Click to expand...
Click to collapse
Giacomo_ITA said:
Do you mean this?
Click to expand...
Click to collapse
Yes, I hope it works, anyway at the next update I will reroot it in a few minutes.
I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
hi ppl
it was rooted before. used twrp and some custom roms. but later it unrooted somehow.
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
io root made it stuck on bootloader animation so I flashed a backup.
how to root it?
thx in advance
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
Click to expand...
Click to collapse
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
zemix said:
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
Click to expand...
Click to collapse
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
so any advice anout that problem?
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Screenshot https://i.imgur.com/6IcIvJx.jpg
slabongrade said:
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
Click to expand...
Click to collapse
flash magisk.zip and install magisk.apk to root android 9
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
I used supersu and it turned out to be "certification verify" problem. OS not running because of this problem but says rooted. so I can still reach twrp but it really become annoying. this is my old phone and will use as 2nd in my Thailand trip soon.
what to do now? can I use unrooted with a sim card? with no problem?
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
zemix said:
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
Click to expand...
Click to collapse
Oh Finally!
dowloaded aosp 8.1 and all done. I was trying to use android 9 to be updated. But, pie becoming to be a "creampie" to me so I listened your word. and did it
just opened recovery mode and deleted all the zips. and copied new ones and flashed in order
1) aosp extended 8.1
2) open gapps nano for 8
3) magisk beta (yes this time I tried beta ver and it worked!)
after settings etc. checked with root checker and it was ok. so magisk.apk is not necessary now
thx again bro