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?
The Magisk Universal Systemless Interface by XDA Recognized Developer @topjohnwu has received an update that bumps it up to version 7. There are a bunch of notable changes that follow in the changelog:
Fully open source
Remove supolicy dependency, use my own sepolicy-injection
Run everything in its own selinux domain, should fix all selinux issues
Add Note 7 stock kernel hex patches
Add support to install Magisk in Manager
Add support for image merging for module flashing in Manager
Add root helpers for SuperSU auto module-ize and auto upgrading legacy phh superuser
New paths to toggle busybox, and support all root solutions
Remove root management API; both SuperSU and phh has their own superior solutions
Downloads:
1)Official MM OOS STOCK 3.1.3 - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
2)Official MM H2OS Stock 2.0 - http://download.h2os.com/oneplus_x/mp/OnePlusH2OS_14_OTA_001_all_201609270726_5aa42273def7431b.zip
3) Use this recovery to Flash Magisk (TWRP by Bluespark) - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4)Magisk Manager.apk - http://forum.xda-developers.com/attachment.php?attachmentid=3893660&d=1475527472
5)Latest Magisk Zip File - http://forum.xda-developers.com/attachment.php?attachmentid=3893659&d=1475527472
6)Systemless Superuser (use this Systemless superuser) - http://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
7)Magisk Uninstaller (if anything goes wrong) - http://forum.xda-developers.com/attachment.php?attachmentid=3893658&d=1475527472
Before Flashing:
1) If you are already on MM with stock recovery and no root,then wipe your data and cache,flash full MM rom pack, flash provided TWRP and follow the instruction below
2)If you are in MM with rooted system,do wipe data and cache,flash full rom pack, flash twrp and follow the instruction
MOST IMPORTANT:
BEFORE FLASHING MAGISK,YOU NEED TO HAVE UNMODIFIED SYSTEM
USE TWRP TO FLASH MAGISK
FLASHING INSTRUCTION:
1)Flash your rom pack
2)Flash magisk zip file
3)Flash systemless root
4)Flash systemless xposed
Ooh laa... Got unmodified system with root access
what is this used for?
meraj99 said:
what is this used for?
Click to expand...
Click to collapse
Systemless Benefits
OTA:
The system partition will not be modified or mount r/w, thus your Android devices are capable of applying OTA updates even if ur mobile s rooted
Safety Net:
Android Pay is confirmed working!
Note: This will not work on any custom ROM running Android 4.3 and below. This will work however from 4.4 KitKat all the way up to 7.0 Nougat (as of post date)
Second Note: This method works for Android Pay and Snapchat too, as well as any other app plagued by SafetyNet.
Tutorial is made for the international variant of the Galaxy S3 (aka the i9300) - swap files out as needed for other variants
1. Download any 4.4+ custom ROM of your choosing.
2. Download SuperSU systemless (latest version is recommended, SR1 from 15th September 2016 as of post date) from here.
3. Download suhide (latest version is recommended, 0.55 as of post date) from here.
4. Install your custom ROM via your favourite custom recovery (recommendation is twrp, from here)
5. Install SuperSU systemless.
6. In TWRP file manager, or a file manager of your choice, remove /system/bin/su and /system/xbin/su.
7. Install suhide
8. Reboot into ROM
9. Enjoy Pokémon GO
Third Note: you may flash over zips like GApps (you flash these like normal)
Final Note: If you wish to install Xposed, you must flash the one from the suhide thread and install Material Design Xposed Installer from here for Pokémon Go, Snapchat, Android Pay and other affected apps caused by SafetyNet
What apps or processes have to be added to the blacklist?
Sorry my english
So, I have a GT-I9300 for my son, who's into playing Pokemon.
Worked so far, with custom rom (Currently it is NamelessRom).
No exposed.
So, how to approach this, as with the 41.4 updete of the game, (or more likely, an update again to Safetynet), I can't get the game to work anymore.
Any suggestions for "the best" rom to use for this ?
I don't care about root on that phone, it doesn't have to be there.
Thanks
-------------------------------
Edit: Just flashed Back to n00t rom, without root, and that seems to be working at least. It's crap that it's Android 4.4.4, however at least it works for him with Pokemon.
/system/bin/su and /system/xbin/su
any rom without these files should work with Poke Go
pokemon go
Hello
I have GT-I9300, rom eleckra s5 lite aroma 4.4.2, root, super su and sushed from you page, but didint work for, me.
My step:
1. instal rom
2 super su
3.Root explorer...but in system/bin su didint exist i have sh but in system/bin/ext i have su y delet this and after this i deleat system/xbin/su
4. reebot in twrp instal sushed rebbot rom
5.instal Pokemon go, log in with cont club...and error this software is not compatible...
Help
turbolukex5 said:
/system/bin/su and /system/xbin/su
any rom without these files should work with Poke Go
Click to expand...
Click to collapse
jorgesibiu said:
Hello
I have GT-I9300, rom eleckra s5 lite aroma 4.4.2, root, super su and sushed from you page, but didint work for, me.
My step:
1. instal rom
2 super su
3.Root explorer...but in system/bin su didint exist i have sh but in system/bin/ext i have su y delet this and after this i deleat system/xbin/su
4. reebot in twrp instal sushed rebbot rom
5.instal Pokemon go, log in with cont club...and error this software is not compatible...
Help
Click to expand...
Click to collapse
SuperSU method is no longer working according to some people, due to a SafetyNet Update..
Try without SuperSU and report back