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?
Hey guys,
Just got a notification today about new OTA update for my Sony Z3+ Dual SIM (E6533). Version 32.2.A.5.11.
I hope it is Nougat, but I haven't installed it. Will backup and test (since I use rootkernel, magisk v8, xposed systemless, and phph superuser systemless) and report back.
What is changelog and size of update? Can you make a screenshot or write here?
I am still waiting on my OTA E6553
Hmmm... seems to be just November Security Update
http://www.xperiblog.com/2016/12/322a511-hits-xperia-z5-series.html
Successfully installed it!
First, download the FTF files using XperiFirm, then use SIM extractor from flashtool to extract the kernel_S1-SW-LIVE-F936-PID1-0006-MMC.elf from the sin file of the same name.
Then use the tool http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 there, to repack it, but you will need to duplicate the folder 3.10.84-perf-gf1cfa5f in Android/twrp_common_kmodules to 3.10.84-perf-g0802f10 otherwise integrating TWRP will fail (you must integrate it to enable the orange LED to boot TWRP in recovery partition using key up, otherwise you will never be able to boot TWRP, even in recovery partition).
After building the new boot.img, boot the device in flashmode and flash the boot image to boot (fastboot flash boot boot_new.img)
Then reboot device to flashmode and use flashtool to flash the new FTF, exclude the KERNEL SIN file otherwise it will overwrite the modified boot with stock kernel.
After flashtool finishes (it may hang on flashing system for long time, it's normal), unplug USB and boot the device. You will notice the orange LED will light up, quickly go into recovery or device will hang (because magisk needs to be reinstalled to reenable xposed / root, I flashed magisk + xposed 87 + phph superuser, otherwise android will hang). If you missed it, you will need to force power off phone using the tiny button inside the flash and try to go into recovery again.
Once that is done, just reboot system. It will take a long time to boot, and it will reoptimize all apps but it will work and root / xposed will function fine (note Magisk v9 hangs on this device when I tried it with 305 stock kernel with black screen, I used Magisk v8 this time and didn't try v9 on the new build).
Note: THIS WILL NOT WORK WITH SYSTEMLESS XPOSED, YOU MUST USE THE CLASSIC VERSION!
Configuration tested on:
Redmi Note 3 Kenzo 3gb goodix variant.
Officially unlocked bootloader.
Installed latest global dev rom (7.7.20) with miflash in edl mode then installed TWRP official 3.1.1-0 then installed 7.7.6 firmware from LineageOS 14.1 thread.
Latest LineageOS build (2/8/17) with Radon Kernel 5.3.
Steps:
1. Install latest global dev rom to make sure you have the proper nougat binary blobs on your device. Preferable to use miflash and phone in edl mode. Allow phone to boot one time so rom can partition the emmc properly.
2. Install latest TWRP official (3.1.1-0) by putting phone in bootloader mode and connecting to PC via usb cable. Copy the twrp recovery image to the same place that fastboot.exe is located. Open an elevated/admin command prompt and navigate to where fastboot.exe is located. Type "fastboot flash recovery NameOfRecovery.img" (without quotes of course). When that is finished type "fastboot boot NameOfRecovery.img."
3. Install zips in this order. LineageOS rom, OpenGapps, Radon Kernel 5.3 (selected all default settings), Magisk 13.3.
4. Reboot to system, set up phone and install any apps that need to pass cts safety net at this point. E.G. Super Mario Run.
5. Reboot to recovery.
6. Install the latest Xposed build for SDK25 ARM64 from PurifyOS Xposed thread - https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221. DO NOT USE THE SYSTEMLESS MAGISK VERSION.
7. Reboot to system.
8. Install latest Xposed Material installer by DVDAndroid - https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758. At this point you will fail safety net. The next step will fix that.
9. Install Root Switch 1.3.3.2 apk.
10. When you need to pass CTS Safety Net use Root Switch to disable Xposed. It will ask you confirmation to perform a soft reboot. After the soft reboot Xposed will be disabled and you will be able to pass CTS Safety net again. DO NOT USE THE DISABLE ROOT SWITCH! THIS WILL PERMANENTLY MESS UP MAGISK!
THIS HAS ONLY BEEN TESTED ON THE LISTED CONFIGURATION. DO NOT ASK IF IT WORKS ON ANY OTHER CONFIGURATION, TEST IT YOURSELF. I WILL NOT BE RESPONDING TO QUERIES, IF YOU FOLLOW THE STEPS AS LISTED YOU WILL BE JUST FINE.
Linn for root switch
tried this on rr rom redmi note 3 kenzo working absolutely fine highly recommend
Works on One Plus 3T with Oxygen OS 4.1.6!
Thanks!
If the root switch app disables xposed, then what is the use of it
Hi,
I have a Xiaomi Mi 9T Pro Global with :
- Bootloader unlocked
- TWRP v3.3.1-0 (lastest)
- Magisk Manager v7.5.1 (lastest)
- Magisk v20.4 (lastest)
So I am rooted and want to keep it (with my data). ^^
Problem: I am still on MIUI v10.3.3.0 and can't install OTA because it makes me reboot on TWRP
I found some different posts like :
Link: https://www.the***********.com/install-ota-update-rooted-android-device-guide/
-> It doesn't work for me because I don't have the A/B partition (message from Magisk when I tried to flash it) and I don't have the "Install to Inactive Slot (After OTA)" option...
Link: https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
-> I don't know if I have to do it, and when? (if needed, I have the boot.img of my current Global v10.3.3.0)
It seem I have to restore my stock recovery?
-> I see how to do it from TWRP, but I don't have the recovery.img file
How can I install OTA without lose my root and my data?
Thank you in advance,
Best regards.
ptit developer said:
Hi,
I have a Xiaomi Mi 9T Pro Global with :
- Bootloader unlocked
- TWRP v3.3.1-0 (lastest)
- Magisk Manager v7.5.1 (lastest)
- Magisk v20.4 (lastest)
So I am rooted and want to keep it (with my data). ^^
Problem: I am still on MIUI v10.3.3.0 and can't install OTA because it makes me reboot on TWRP
I found some different posts like :
Link: https://www.the***********.com/install-ota-update-rooted-android-device-guide/
-> It doesn't work for me because I don't have the A/B partition (message from Magisk when I tried to flash it) and I don't have the "Install to Inactive Slot (After OTA)" option...
Link: https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
-> I don't know if I have to do it, and when? (if needed, I have the boot.img of my current Global v10.3.3.0)
It seem I have to restore my stock recovery?
-> I see how to do it from TWRP, but I don't have the recovery.img file
How can I install OTA without lose my root and my data?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
You can keep TWRP and Magisk module, you will only need to patch the boot image and install it from TWRP to regain root after the OTA
- Download full Recovery/zip package 2.4 GB for your MI/IN/EU/RU you currently have with MIUI 10
- Flash that zip from TWRP (Install, zip)
- Reboot to TWRP, not to Android, otherwise you will loose TWRP
- Backup Boot in TWRP
- Reboot to Android. You shouldn't have lost your apps and settings. Magisk Manager will be there but no root
- From Magisk Manager take Install, keep Preserve AVB and Preserve Encryption (first two) but UNCHECK Recovery mode
- Choose to Patch image and navigate to the Boot backup you just made in TWRP, boot.emmc.win, 128 MB
- Reboot to TWRP, take Install, Image (not zip) and navigate to magisk_patched.img in Download
- Upon installing keep in TWRP and Wipe Dalwik and Cache, ONlY
-Reboot to Android - you will have root, your previous modules, rooted apps, all
PS: Doing OTA from System Update requires stock Recovery - that's why it reboots for you to TWRP and fails.
To be able to do OTA that way, you would need to first flash back your stock Recovery.
Then OTA update will fail and you wouldl have to force Full OTA.
At the end, you would also loose root - hence the above procedure is simpler, you even don't need PC, you will keep TWRP and you will only need to patch and install the patched boot image to regain root
Hi and thank you @zgfg,
So if I correctly understand, to be able to make OTA without losing my data and restore root, I have to :
1. Install stock ROM
-> When I did it on previous phone, I always lose everything, so are you sure?
2. Restart in TWRP (to not lose it)
3. Backup boot via TWRP
4. Go in Magisk Manager, and check "keep Preserve AVB" and "Preserve Encryption", but uncheck "Recovery mode"
5. Click on "Install" and choose "Patch image", then selected the boot image previous made with TWRP
6. Reboot in TWRP to install (image, not zip) this file created in the 5.
7. Wipe Dalvik and Cache
8. Enjoy
I found the following link on mi.com to allow me to download the Global v10.3.3.0 (zip and tar.gz) :
Link: https://c.mi.com/thread-2459743-1-0.html
Is it the good one?
Can I simply extract the boot.img of the file downloaded in the 1. and go directly to the 4. ?
Thank you in advance,
Best regards.
ptit developer said:
Hi and thank you @zgfg,
So if I correctly understand, to be able to make OTA without losing my data and restore root, I have to :
1. Install stock ROM
-> When I did it on previous phone, I always lose everything, so are you sure?
2. Restart in TWRP (to not lose it)
3. Backup boot via TWRP
4. Go in Magisk Manager, and check "keep Preserve AVB" and "Preserve Encryption", but uncheck "Recovery mode"
5. Click on "Install" and choose "Patch image", then selected the boot image previous made with TWRP
6. Reboot in TWRP to install (image, not zip) this file created in the 5.
7. Wipe Dalvik and Cache
8. Enjoy
I found the following link on mi.com to allow me to download the Global v10.3.3.0 (zip and tar.gz) :
Link: https://c.mi.com/thread-2459743-1-0.html
Is it the good one?
Can I simply extract the boot.img of the file downloaded in the 1. and go directly to the 4. ?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
In the first post you said that you already have v10.3.3.0 and that you want to update
Hence why would you now download v10.3.3.0 - you should download v11 (supposidely), that the same newer version that OTA offers you
Yes, you can extract boot.img from that newer MIUI (v11) that you will download and flash but that requires PC - in my instructions you simply use TWRP and make backup of the boot image upon you do update
By extracting boot.img from v11 you will not save any step, you still must flash its zip (not tgz) from TWRP and you must nevertheless reboot to TWRP first
---
By flashing OTA zip (full, 2.4 GB) from TWRP, you should not loose your data and apps. I did it with Mi 9T (not PRO - you are not on the PRO forum) but things must work the same way for PRO for Global or EU (you must update to the same Global, EU, Indian, Russian as you already have, just fownload the same newer version that OTA offers you)
Hi back,
Yes, I am in Global (EU) v10.3.3.0 and I should want to use OTA (first I have, it is to go on v10.3.4.0, and I guess, I will have more after until v11).
So I can use directly v11 one?
Thank you in advance,
Best regards.
ptit developer said:
Hi back,
Yes, I am in Global (EU) v10.3.3.0 and I should want to use OTA (first I have, it is to go on v10.3.4.0, and I guess, I will have more after until v11).
So I can use directly v11 one?
Thank you in advance,
Best regards.
Click to expand...
Click to collapse
Better follow what OTA gives you. Find and download Recovery/zip for that Global v10.3.4.0 and install as suggested.
Later similarly follow the version numbers the same way as they come by OTA