EDIT: Magisk V13 is fully compatible with Sony stock roms. Please refer to the official release! https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Let me explain before you complain about: "Magsik v12 is already Sony compatible!"
Yes, the installer is - but it only works on devices with disabled Sony RIC service.
TL;DR: Download in attachments.
Do you need this?
If you are using Sonys stock unpatched boot image or drm-fix without RIC disabler you should use this version of magisk, since it includes a RIC disabler.
Recommended workaround without altered Magisk:
1. Patch your boot image with rootkernel tool (disable sony ric at least): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
2. Use orignal magisk with the patched boot image: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Original thread:
How and why
I was stuck with debugging an issue regarding MagiskSU for hours. The Magisk installation was fine, but somehow MagiskSU was not there which made Magisk useless for me (=> no MagiskHide, no modules, no hosts support, etc). I finally realized that Sonys RIC service prevents the magic_mask.sh script (the script that enables Magisk and its features during boot) from symlinking the su binary and magiskpolicy in /sbin
But it works for me without your patch!?
Did you use rootkerneltool from @tobias.waldvogel with your current kernel? It is capable of disabling Sony RIC aswell and maybe you did that or are using a kernel without Sony RIC.
The fix (for developers) @topjohnwu
magic_mask.sh, add this in late_start service mode:
Code:
#Try to disable Sony RIC
echo 0 > /sys/kernel/security/sony_ric/enable
if [ $? -eq 0 ]; then
log_print "* Sony RIC service disabled";
else
log_print "* Sony RIC service NOT disabled :("
fi
Proof that it works and passes SafetyNet (Z5 compact with Android 7)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Original thread
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flashing on z3+ and working flawlesly
If using kernel that use ta_poc got bootloop, but if use kernel with drmfix its work
Fauzi alaik said:
Flashing on z3+ and working flawlesly
If using kernel that use ta_poc got bootloop, but if use kernel with drmfix its work
Click to expand...
Click to collapse
Just tried latest ta_poc (yesterdays release) and it works for me. But since latest ta_poc also supports disabling Sony RIC, you dont need this patched magisk version if you've disable it with ta_poc (or rootkerneltool).
@[email protected],
reicht es nicht aus, ein custom kernel zu flashen bei dem die sony_ric schon deaktiviert wurde?
Gestern habe ich die original magisk v12 geflasht und es hat funktioniert.
Also ich habe auf meinem z5 den androplus kernel, chainfires supersu, die letzte marshmallow rom und es funktioniert.
Oder hab ich irgendwas falsch verstanden?
MysticEnforcer said:
@[email protected],
reicht es nicht aus, ein custom kernel zu flashen bei dem die sony_ric schon deaktiviert wurde?
Gestern habe ich die original magisk v12 geflasht und es hat funktioniert.
Also ich habe auf meinem z5 den androplus kernel, chainfires supersu, die letzte marshmallow rom und es funktioniert.
Oder hab ich irgendwas falsch verstanden?
Click to expand...
Click to collapse
Nope, all well,
take a look at OP's edit:
EDIT: Only required if you didn't patch your boot image with ta_poc or rootkerneltool and disabled Sony RIC with it, if you already patches Sony RIC with these tools, go to this thread instead:
Click to expand...
Click to collapse
i... appear to have bricked my z3 my flashing this. i'm sure i must've missed something crucial.
Check magisk.log in /cache using recovery
Which android version did you use? Modified boot image? Other mods?
I keep getting the CTS profile mismatch on the Z5 Compact, even with a freshly installed ROM. Any tips?
Enable magisk hide, it works on my z5c
[email protected] said:
Enable magisk hide, it works on my z5c
Click to expand...
Click to collapse
That works for me. Thanks
Enviado desde mi D6603 mediante Tapatalk
[email protected] said:
Enable magisk hide, it works on my z5c
Click to expand...
Click to collapse
Already enabled. Even tried toggling and restarting, still fails the safetynet. Also checked the thread for solutions, tried them all and still fails... What firmware are you on?
Thats weird. Please share a copy of /cache/magisk.log
Does safetynet pass without magisk?
iArvee said:
Already enabled. Even tried toggling and restarting, still fails the safetynet. Also checked the thread for solutions, tried them all and still fails... What firmware are you on?
Click to expand...
Click to collapse
See attachment
This mod works for me with untouched stock kernel. Safety net passed, root works, everything went well. However, stock kernel also means that the phone can detect that it has been unlocked, drm-related features will not function. Is there a way to bypass this? I tried your mod with Poc-patched kernel and got bootloop (same with SuperSU or Superuser for some reason). I got my Ta backed up btw.
kientrongtran said:
This mod works for me with untouched stock kernel. Safety net passed, root works, everything went well. However, stock kernel also means that the phone can detect that it has been unlocked, drm-related features will not function. Is there a way to bypass this? I tried your mod with Poc-patched kernel and got bootloop (same with SuperSU or Superuser for some reason). I got my Ta backed up btw.
Click to expand...
Click to collapse
It's only required with stock boot bundle (and at the time I developed the fix, POC TA was broken and didn't patch Sony RIC -> see this post: https://forum.xda-developers.com/cr...ad-drm-fix-t3552893/post71663359#post71663359)
So if you use latest POC TA and disable Sony RIC with it, Magisk v12 from @topjohnwu should work
Edit: Latest PoC TA (and maybe in combination with latest .33 fw) is incompatible to Magisk. Use rootkerneltool in this case
[email protected] said:
Thats weird. Please share a copy of /cache/magisk.log
Does safetynet pass without magisk?
Click to expand...
Click to collapse
Hi! Sorry for the delay, was on vacation. Anyways, magisk.log attached. I'm not sure why it says "Permissive detected" when I didn't do anything to change the SELinux settings.
As for your other question, no. It still failed the safetynet even without magisk, and after a full wipe.
This is weird, it should pass safetynet even with unlocked bootloader (after stock reflash)
It actually sound like you are not using a stock boot image (therefore its permissive)
[email protected] said:
This is weird, it should pass safetynet even with unlocked bootloader (after stock reflash)
It actually sound like you are not using a stock boot image (therefore its permissive)
Click to expand...
Click to collapse
I can't pass SafetyNet too, when I flashed the stock firmware and boot image with unlock boot loader on Z5P .33 fw.
Is "Basic integrity" true and CTS false?
[email protected] said:
It's only required with stock boot bundle (and at the time I developed the fix, POC TA was broken and didn't patch Sony RIC -> see this post: https://forum.xda-developers.com/cr...ad-drm-fix-t3552893/post71663359#post71663359)
So if you use latest POC TA and disable Sony RIC with it, Magisk v12 from @topjohnwu should work
Edit: Latest PoC TA (and maybe in combination with latest .33 fw) is incompatible to Magisk. Use rootkerneltool in this case
Click to expand...
Click to collapse
So that's why MagiskSU wasn't installing on my phone even though I had used PoC TA...
If it's not too much to ask though could you provide a link with where to find rootkerneltool? I haven't heard of that before and are unable to find it by searching either, as I don't know what to look for, or if it's a generic Android or just Sony tool. Never mind I found it.
I want to see if I can get Magisk working on the Concept firmware for Xperia X bu it sounds like ta_poc probabbly won't be able to work with it.
Related
Do not work with Nougat 7.1.1 / 32.4.A.0.160 (Bootloop)
New TWRP (You dont need otg and mouse anymore!):
https://www.androidfilehost.com/?fid=745425885120733410 (thanks to andralex8!)
GUIDE UPDATED, TESTED AND SIMPLIFIED 15.2.2017 (thanks to munjeni)
Tested with Saudi Arabia, Germany and Nordic (.378) firmwares
I managed to get my Xperia Z4 Tablet (SGP771) LTE model to have root, TWRP-recovery*, munjenis DRM fix and Adaway working with Nougat firmware (Saudi Arabia). I will share steps that I have done with my own tablet. If this guide brick your device or something goes wrong, I am not responsible for loss of your device. Use this guide only with your own RISK!
This tutorial is not for beginners. You need to have working adb installed yout pc, unlocked tablet, sonys special driver for fastboot. and TA backup (example TA-21062016.img). Use only this tutorial with Sony USB-cable.
*To get TWRP working, you need: OTG-cable and a mouse with wire or wireless mouse with a dongle.
0. Download Nougat 32.3.A.0.376 (Saudi Arabia) firmware with Xperiafirm 32.3.A.0376. to your PC
1. Flash Nougat 32.3.A.0.376 (Saudi Arabia) with Flashtool 0.9.23.2.
2. Boot your device and enable Developer settings from setting
3. Enable USB debugging setting from Developer settings
4. Download Supersu and Magisk to your device:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
http://tiny.cc/latestmagisk
5. Shutdown your device
6. Download munjenis DRM fix and serajr script package v2 to your pc:
http://munjeni.myiphost.com/ta_poc.rar
https://forum.xda-developers.com/showpost.php?p=70959962&postcount=65
7. Decompress files from munjeni and serajir to same folder.
8. Extract kernel.sin from your nougat firmware ftf (You can use 7zip to do this). Copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin
9. Copy your TA backup to same folder with DRM fix and rename it TA.img
10. Open Cmd with admistrator persimmions and use DOUBLECLICKME_NOUGAT.bat (search cmd rght mouseclick use admistrator).
11. Follow munjenis tool tutorial: You can choose if you want Sony Ric off. I left it on but turned dm verity off.
12. Download TWRP: https://drive.google.com/drive/folders/0B0j3VJ1Xp5N8cnhQamtxRWVtRmc
13. Press vol up and connect your device to pc to use fastboot. Use command: fastboot flash boot new_boot.img
14. After that use command: fastboot flash recovery TWRP-3.0.2-0-20160604.img
15. Disconnect your device and put otg-cable to tablets usb and connect mouse to otg-cable.
16. Press vol down + power to boot to TWRP. Touchscreen is not workin but you can use your mouse to navigate in TWRP!
17. Allow TWRP to make changes to your device and flash Supersu 2.79 and Magisk 11.1.
18 Boot your device and install magisk manager from the play store.
19. Enable from magisk manager settings: busybox, magisk hide and systemless hosts and Install Adaway (Will not work without Magisk, strange).
I have not managed to get my CTS profile approved but that is not major issue if not playing with Pokemon go (You can use magisk to detect this).
Note1 : Change LTE to 1 priority from mobile setting. Default for SA firmware is GSM
Note2: If you have already tried rootkernel to get drm working; do a full wipe and reflash firmware with flashtool. Rootkernel messes something. Tablet do not boot if you have used rootkernel and after that try to use munjenis DRM fix.
Note3: Magisk 11.1 wont work with Xperia Z4 Tablet without Supersu. So flash Supersu first and Magisk 11.1 after that
Note4: You cannot boot to TWRP by using root and reboot to recovery apps. You need to boot to the recovery with keycommand voldown+power
I hope this guide helps some fellow flashers
Special thanks for
munjeni
serajr
Chainfire
Androplus
topjohnwu
Teamwin
Androxyde
mrRobinson
If I forgot someone I am truly sorry!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just tried unable to boot to recovery
sahilg009 said:
Just tried unable to boot to recovery
Click to expand...
Click to collapse
Did you do a full wipe? Try to fastboot flash boot new_boot.img after flashing recovery!
Tried wiping now flashing kernel gives me a no sim card error
sahilg009 said:
Tried wiping now flashing kernel gives me a no sim card error
Click to expand...
Click to collapse
Check this out:
https://forum.xda-developers.com/showpost.php?p=70972513&postcount=115
halfvast said:
Check this out:
https://forum.xda-developers.com/showpost.php?p=70972513&postcount=115
Click to expand...
Click to collapse
Even tried that still giving me signal problem
sahilg009 said:
Even tried that still giving me signal problem
Click to expand...
Click to collapse
Strange, I Did not encourter this problem because I could boot to TWRP and do adb trick there. Do you use orginal Sony usb to flash in fastboot? I had once a problem with Samsung Phone (S7) to flash recovery because the usb was not the one that came with my Phone.
Yeah
Try redownload TWRP image and flash it. If not working do a clean flash and try again or wait for Androplus kernel
Tried it all nothing worked still no sim error
sahilg009 said:
Tried it all nothing worked still no sim error
Click to expand...
Click to collapse
I found out munjeni is fixing his tool:
https://forum.xda-developers.com/showpost.php?p=70993277&postcount=173
I used previous version, which is not availble right now.
He says further in his thread he is going to release tomorrow a new version.
I used this version:
http://www.filedropper.com/tapoc
halfvast said:
I found out munjeni is fixing his tool:
https://forum.xda-developers.com/showpost.php?p=70993277&postcount=173
I used previous version, which is not availble right now.
He says further in his thread he is going to release tomorrow a new version.
I used this version:
http://www.filedropper.com/tapoc
Click to expand...
Click to collapse
Couldnt I just do the root and recovery method you have given on the wifi version as im not too bothered about drm fix for now as it looks abit complicated at the moment for me. It would be much more simple for me to flash recovery then super su. I just wanna know if this is possible?
Thanks
I am not sure. You need atleast a correct TWRP. You can try if You dare with your own RISK
But I doubt that it wont work..
halfvast said:
I am not sure. You need atleast a correct TWRP. You can try if You dare with your own RISK
But I doubt that it wont work..
Click to expand...
Click to collapse
Ok then dont think id like to try incase it doesnt boot so I think I might just wait for andro to do his stuff.
I have updated the guide and tested it today (13.2.2017) and it is working again
Guide updated and simplificed 15.2.2017. Thanks to munjeni!
halfvast said:
Guide updated and simplificed 15.2.2017. Thanks to munjeni!
Click to expand...
Click to collapse
Step 8 says Extract kernel.sin from your nougat firmware copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin. Do I have to extract that from the ftf or my Nougat firmware im currently using? Also does the ftf have to be that region?
RJASSI21 said:
Step 8 says Extract kernel.sin from your nougat firmware copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin. Do I have to extract that from the ftf or my Nougat firmware im currently using? Also does the ftf have to be that region?
Click to expand...
Click to collapse
You need to extract it from ftf-image. I used 7zip. My device was Nee with stock. I used DE with Marshmallow and I am currently using Saudi Arabia. So I dont think it will matter, which kernel you use with your device. But I would use same kernel version with rom. So If you are using Saudi Arabia rom use Saudi Arabia kernel. For Russia rom use Russia kernel, and so on
I will add tft-image extract to tutorial!
DRM fix doesn't work. XReality (among other things I assume) are ever disabled.
On Marshmallow DRM fix was working fine (was using XReality engine despite the unlocked bootloader)
For me it is working!
I'm using mate 9 with Magisk for a while. Here is the steps how I flash my phone.
Notice: Only verified Mate 9 MHA-L29C636B188 (Pass SafetyNet Check).
Magisk: Thanks to @topjohnwu
Huawei Firmware Finder: Thanks to (Team MT)
TWRP 3.1.0-1: Thanks to @Tkkg1994
Prepare:
A. Flash official ROM. (Ex: MHA-L29C636B188) (Refer to : [Guide] Mate 9 Flash Update Package and Rebrand)
B. Download Magisk and related file. (Link)
Download:
A. Download Huawei Firmware Finder PC Tool (Link)
B. Run "FimrwareFinderRewrite.exe" and select "Common Base".
C. Select phone brand (Ex: MHA-L29C636) and click "Find".
D. Select 1A. Firmware (Ex: MHA-L29C636B188) "Filelist" and download the second and third link file.
E. Put 1B. bootimg_data_decrypt_xxx.zip and 2D. files(___data___.zip and ___hw___.zip) into phone SDCard.
Unlock:
A. Phone power off, press vol-down and usb cable to enter fastboot mode.
B. fastboot oem unlock xxxxxx (xxxxxx is your unlock code)
Flash:
A. Enter Fastboot again using "fastboot flash recovery MHA_xxxx-3.1.0-1-hi3660.img" to flash TWRP Recovery.
B. Phone power off, press vol-up and power to enter TWRP.
C. TWRP select "Keep Read Only" (Everytime enter TWRP select this.)
D. Wipe => Format Data => yes
E. Install => Select 2E. bootimg_data_decrypt_xxx.zip file.
F. Install => Select 2E. xxxx__data__xxxx.zip file.
G. Install => Select 2E. xxxx__hw__xxxx.zip file (Ignore errors).
H. Reboot => System => Do Not Install.
Magisk:
A. Download "SafetyNet Test" application in Google Play Store.
B. Run SafetyNet Test, only CTS profile match fail.
C. Put 1B. Magisk-vxxxx.zip and Huawei-Prop-Fix-xxxx.zip into SDCard.
D. Phone power off, press vol-up and power to enter TWRP again.
E. Install => Select Magisk-vxxxx.zip
F. Install => Select Huawei-Prop-Fix-xxxx.zip
G. First boot SafetyNet Test can't pass.
H. After second boot SafetyNet Test pass.
I. If SafetyNet Test failure in the future, disable all modules in Magisk, reboot SafetyNet pass then enable modules.
Update: Huawei-Prop-Fix-v1.2_2017091101.zip (Be sure Magisk has busybox, recommend v14.0) [Link]
Keep UP Good Work.
Sure will try.
Thanks,
goldybewon
MHA-L29
Please note that you need to be on a firmware released on or after 12th of April 2017. If it's before that date you'll fail at flashing Magisk.
And you should probably add a notice that this is for decryption.
If coming from SuperSU or PHH you'll have to flash back stock boot image before flashing.
If you're already decrypted there's no need to format data again.
If you want to stay encrypted, flash this instead: https://mega.nz/#!o4ESgABJ!DyUxQSKo8skyfv05sSuU7FjMmsyeckAO0KD_1dDIctw
I have tried several times flashing magisk with C185B181 and I gave up it fails hiding the root! Ante0 tried to help me but I gave up
Iloudsan said:
I have tried several times flashing magisk with C185B181 and I gave up it fails hiding the root! Ante0 tried to help me but I gave up
Click to expand...
Click to collapse
Try flashing the module linked in OP, the Huawei fix. It seems to work for me. USB debugging is staying on, I just had to go to the service menu and enable logging again. After rebooting several times it's still passing
Before, after it became buggy for me again, I had to enable USB debugging after rebooting/using adb. And yesterday I had to enable logging to get it running.
ante0 said:
Try flashing the module linked in OP, the Huawei fix. It seems to work for me. USB debugging is staying on, I just had to go to the service menu and enable logging again. After rebooting several times it's still passing
Before, after it became buggy for me again, I had to enable USB debugging after rebooting/using adb. And yesterday I had to enable logging to get it running.
Click to expand...
Click to collapse
Thanks I'll give it a try tonight
ante0 said:
Try flashing the module linked in OP, the Huawei fix. It seems to work for me. USB debugging is staying on, I just had to go to the service menu and enable logging again. After rebooting several times it's still passing
Click to expand...
Click to collapse
Fix property script enable persist adb, that's the point to pass safetynet. I didn't enable logging and it passed as well.
It's working now thanks guys!!!!
Is it possible to install xposed too?
Iloudsan said:
Thanks I'll give it a try tonight
Click to expand...
Click to collapse
I got it running but the apps takes really long time to load and freeze a lot is this normal
Iloudsan said:
I got it running but the apps takes really long time to load and freeze a lot is this normal
Click to expand...
Click to collapse
Do you mean the magisk manager?
It shouldn't take long at all. Or it doesn't for me at least.
mankindtw said:
Fix property script enable persist adb, that's the point to pass safetynet. I didn't enable logging and it passed as well.
Click to expand...
Click to collapse
I think it's because usb debugging kept disabling for me.
Not sure why it would stop logging, I couldn't even get a logcat...
Oh well, it works now!
By the way, did you make the module? if so you should post it in the Magisk section of XDA. More people are having trouble with Magisk on other Huawei devices (P10, P9, Honor etc.) , and it might help them too.
ante0 said:
Oh well, it works now!
By the way, did you make the module? if so you should post it in the Magisk section of XDA. More people are having trouble with Magisk on other Huawei devices (P10, P9, Honor etc.) , and it might help them too.
Click to expand...
Click to collapse
Yes, I made the module and already post in Magisk 13.6 thread. I don't want to open a new thread in Magisk.
Because I don't have other devices to test if they fail on SafetyNet test.
Hello
So is it possible to install magisk on rooted with PHsuperuser MHA-L29C185b181 .
what is the best method flash it with TWRP or with Magisk Manager
thankd in advance
reg
repoman728 said:
Hello
So is it possible to install magisk on rooted with PHsuperuser MHA-L29C185b181 .
what is the best method flash it with TWRP or with Magisk Manager
thankd in advance
reg
Click to expand...
Click to collapse
Use twrp, and restore stock B181 boot image first.
Just tested on MHA-L09C185B180 with Magisk v14.
Working perfectly fine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Followed the post as instructed and it works just fine! Installed Magisk on my Mate 9 MHA-L29C567B190. Cheers!!
Hey guys, can I install xposed using magisk without safetynet getting tripped?
Confirmed Mate 9 Pro is working
for those who are interested I followed the instructions to a t however substituted and used update_data_public.zip & update_all_hw.zip files from MATE 9 PRO Firmware LON-L29C636B229.
I also used twrp-3.1.0-1-hi3660 which may be the same but i found mine on a mate 9 pro thread.
It was actually seamless installation and ive had my mate 9 pro rooted with supersu before but never magisk because I couldn't quite get it working but this method worked perfectly.
Like I said I just followed instructions but substituted those two .zip files and used all other files in the instructions.
I will attach a couple screen shots if I can figure out how on here. Man this thing is snappy as Ive ever seen it.... great job on the directions and this thread.... I have seen no lag as far as the magisk apk its all very very fast with no hiccups so far.
pri10 said:
Hey guys, can I install xposed using magisk without safetynet getting tripped?
Click to expand...
Click to collapse
Nope.
Also seems to work on my P10 Plus
Maybe this is old news I just thought id share it in case no one has tested it yet.
model is VKY-L29 and i just substituted those two firmware finder files from B162 of the p10 plus fw
also i used a different twrp obviously but this method has my recent huawei devices running magisk for the first time at least for me its great thing ive never been able to figure out how to do it until this method. thanks
Update 1B. link:
Huawei-Prop-Fix-v1.2_2017091101.zip keeps persist.sys.root.status property zero.
So many LEECHERS exist, It's not hard to press a button..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi xda users,
I am very pleased to present LATEST NOUGAT FTFs Google Drive Mirror, Patched Kernels and TWRP .
I spend lots of time and bandwidth for you, so please hit Thanks :fingers-crossed: button and comment below..
Bootloader LOCKED Devices
-Just follow 1 to 14 steps
Bootloader UN-LOCKED Devices
-Just follow 1 to 30 steps
Google Drive Mirror File List
-7.1.1 (32.4.A.1.54) FTFs (E6603, E6633, E6653, E6683)
-Patched Kernels
-TWRP 3.1.1.0 thanks to @kv123
-ROOT Methods (SuperSU, phh and Magisk)
-Flashtool, Flashtool-drivers (0.9.23.2)
Click this for List view
Patched Kernel Specifications
sony-ric
dm-verity
drm-fix
busybox-1.26.2
fully /system read&write access
If r/w didn't work for you, please do that. It will be fixed.
1.Install Termux on Play Store.
2.Write "su" command and give root access.
3.Then write this
Code:
echo 0 > /sys/kernel/security/sony_ric/enable
4.Lastly write this
Code:
busybox mount -o rw,remount,rw /system
Done
Step by Step Installation
Summary
Install Flashtool & Drivers
Flash FTF
Flash Patched Kernel & TWRP
Flash ROOT
Detailed
1-) Install flashtool-0.9.23.1-windows.exe
2-) Copy x10flasher.jar file into "C:\Flashtool", open Flashtool wait until process done then quit program.
3-) Disable "Driver Signature Verification"
Windows 7 : Tap F8 while booting and select required option
Windows 8, 8.1, 10 : Read This Instructions
4-) Install Flashtool-drivers.exe (flashmode, fastboot, z5)
5-) Copy FTF file into "C:\Users\YOUR PC NAME\.flashTool\firmwares"
6-) Backup your Photos & Videos & Musics etc. on Internal Memory to SDCard or PC
7-) Shutdown your phone
Open Flashtool (x32 suggested)
9-) Click Flash button (top left) then Ok button, select FTF on left side
10-) Select ALL wipe options, no NEED Misc TA for every flash (SKIP this, if you want to just UPDATE and keep data)
11-) Click Flash button, wait 1 minute (you will see an info)
12-) Push VOLUME DOWN button, then connect phone to pc (green led)
13-) When flashing done, disconnect and boot-up your phone, complete setup wizard (required)
14-) If you want to use Patched Kernel or ROOT your phone then continue otherwise flashing FTF process done
You have to BL Unlocked device to continue..
15-) Shutdown your phone
16-) Push VOLUME UP button, then connect phone to pc (blue led)
17-) Copy 32.4.A.1.54_E66XX.img and twrp_recovery.img file into "C:\Flashtool\x10flasher_lib"
1 Open "C:\Flashtool\x10flasher_lib" folder
19-) Then press LEFT SHIFT and click mouse right button into this folder
20-) Then press Open command window here option
21-) Then type this code into cmd (xx your model)
Code:
fastboot.exe flash [COLOR="red"]boot[/COLOR] 32.4.A.1.54_E66[COLOR="red"]xx[/COLOR].img
fastboot.exe flash [COLOR="red"]recovery[/COLOR] twrp_recovery.img
22-) Disconnect your phone and boot-up (required)
23-) If you want to ROOT your phone then continue otherwise flashing Patched Kernel process done
24-) Put ROOT files into Internal Memory
SuperSU - Most common root solution
phh's Superuser - I think best root solution
Magisk - Module solution & It has built-in phh root solution
25-) Boot-up your phone into TWRP
-TWRP : Volume DOWN + Power
26-) If you want to use SuperSU, just flash zip and reboot
27-) If you want to use phh, just flash zip and reboot You have to install "me.phh.superuser.apk"
Latest Magisk
Latest Magisk Uninstaller
2 If you want to use SuperSU & Magisk, flash SuperSU first then Magisk then Install Magisk Manager
29-) If you want to use Magisk, flash latest Magisk then Install Magisk Manager
30-) Have fun :fingers-crossed:
You can delete ALL System Apps with System App Remover ROOT APP
HELP ME!
HI :3
a request, could use the same kernel of the Latin American version of the model 6603? since I use that version, and this device and has the fingerprint sensor, please, I currently use the kernel of the US version and I do not have the fingerprint sensor enabled, or is there any way to reactivate this sensor with the American kernel?
SKGT said:
HI :3
a request, could use the same kernel of the Latin American version of the model 6603? since I use that version, and this device and has the fingerprint sensor, please, I currently use the kernel of the US version and I do not have the fingerprint sensor enabled, or is there any way to reactivate this sensor with the American kernel?
Click to expand...
Click to collapse
No, usa kernel was broken. I use TR and Germany kernels.
Thank You so much!
4th comment!
Sent from my E6653 using XDA-Developers Legacy app
Can I flash this ROM using TWRP?
Sent from my E6653 using XDA-Developers Legacy app
GeramanX said:
Can I flash this ROM using TWRP?
Sent from my E6653 using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. Follow the instructions of the OP.
Sent from my E6653 using Tapatalk
@sceryavuz is it possible to add kcal support on .54 kernel.
s.hossein said:
@sceryavuz is it possible to add kcal support on .54 kernel.
Click to expand...
Click to collapse
+1
s.hossein said:
@sceryavuz is it possible to add kcal support on .54 kernel.
Click to expand...
Click to collapse
devilmaycry2020 said:
+1
Click to expand...
Click to collapse
Flash 7.1.x_kcal_support.zip via TWRP. :fingers-crossed:
I have flashed it. It works so nice. Battery last longer. Phone doesn't heat up, only warm up a bit. But why does the phone heat up while charging only? Is there any way to fix this?
Thank You
s.hossein said:
@sceryavuz is it possible to add kcal support on .54 kernel.
Click to expand...
Click to collapse
sceryavuz said:
Flash 7.1.x_kcal_support.zip via TWRP. :fingers-crossed:
Click to expand...
Click to collapse
Thank you. Working well on .54 kernel
sceryavuz said:
No, usa kernel was broken. I use TR and Germany kernels.
Click to expand...
Click to collapse
Sorry for my english, google translator
So, I have to flash the ftf of germany? Does this kernel have the fingerprint sensor? I want to recover the fingerprint sensor, but I do not want to lose the drm keys I also do not want to lose root, any help? I use an e6603, with the ftf of latin america, but with the kernel of usa, is there any way to enable the fingerprint sensor?
thanks: 3
thank you sir for your work..but twrp still looping after flashing it>>>what shall i do(the phone stocked on twrp )
i did wipe cache and again mounted the system and flashed supersu>>>>>>but unfortunately.....didnot worked ...any suggestions???
thanks in advance
amer78 said:
thank you sir for your work..but twrp still looping after flashing it>>>what shall i do(the phone stocked on twrp )
i did wipe cache and again mounted the system and flashed supersu>>>>>>but unfortunately.....didnot worked ...any suggestions???
thanks in advance
Click to expand...
Click to collapse
Where did you flash it? And what model do you use?
Sent from my E6653 using Tapatalk
saiz136 said:
Where did you flash it? And what model do you use?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
i flashed rooted kernel via flash tool (fastboot)
then flashed twrp (same method)
then flashed supersu as always
my model is E6633 (dual sim z5)
amer78 said:
i flashed rooted kernel via flash tool (fastboot)
then flashed twrp (same method)
then flashed supersu as always
my model is E6633 (dual sim z5)
Click to expand...
Click to collapse
Are you sure you flashed the right firmware? With ".TA" removed? Try to flash the firmware and make sure it's the right model and build number using flashtool. Also check the img file if it's the right model too.
Sent from my E6653 using Tapatalk
saiz136 said:
Are you sure you flashed the right firmware? With ".TA" removed? Try to flash the firmware and make sure it's the right model and build number using flashtool. Also check the img file if it's the right model too.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
i did it all as mentioned but .....no hope...still stocked at twrp..and hone refuse to boot normaly..
i did wipe cahe ..fixing permissions...everything...n chance
amer78 said:
i did it all as mentioned but .....no hope...still stocked at twrp..and hone refuse to boot normaly..
i did wipe cahe ..fixing permissions...everything...n chance
Click to expand...
Click to collapse
Try to flash ftf (firmware without the boot.img and twrp.img) also I might recommend to download the ftf via Xperifirm and not the one provided by the OP. Use the customised version.
Sent from my E6653 using Tapatalk
saiz136 said:
Try to flash ftf (firmware without the boot.img and twrp.img) also I might recommend to download the ftf via Xperifirm and not the one provided by the OP. Use the customised version.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
i think the problem comes from twrp.....
its not compatible with my device
is there any other method to root?
Firstly, I do not take any responsability in case anything happens to your device or your files. You decided to follow this guide at your own risk.
THIS WORKED FOR ME FOR MAGISK v14.3
ALSO WORKS ON MAGISK v14.5
I highly not recommend to use this guide for a different device other than the Xperia Z2 D6503.
All that aside, I managed to install magisk on my Stock Xperia Z2 and still keep ctsProfile and basicIntegrity: true.
HIGHLY RECOMMEND TO BACK EVERYTHING UP BEFORE PROCEEDING
You will need:
(OPTIONAL)Marshmallow FTF Firmware Here
(OPTIONAL)Flashtool Here
Magisk Manager Here
Rootkernel_v4.31_Windows_Linux.zip Here
ADB and Fastboot Here
Advanced Stock Kernel Here
TWRP Sirius Here
(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above. It worked on this version but I can't really guarantee it will work on others. Can't really guarantee it will work on this either.(after you select the file there are 2 versions. pick the modified one).
1) Extract the Rootkernel_v4.31_Windows_Linux.zip and extract from the advanced stock kernel the boot.img (Rename it from boot.img to Old_boot.img)
2) Open cmd and use cd to reach the folder in which you extracted rootkernel.
Use the command "rootkernel Old_boot.img New_boot.img"
Say Yes to everything except installing TWRP.
3) Install Magisk Manager on your phone and copy "New_boot.img" to the phone.
4) Go to Magisk Manager settings , scroll to Update Channel and select Beta
5) Select install Magisk and select modify boot image. Select "New_boot.img" from the folder you copied it to
6) Extract adb to a folder
7) After patching the boot image at step 6, copy "patched_boot.img" from internal storage/MagiskManager to the folder in which you extracted adb
8) Copy TWRP to the adb folder and rename it to TWRP.img
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
10) While still in fastboot, type "fastboot flash recovery TWRP.img"
11) Disconnect your phone from the pc. Wait a few seconds and then boot into TWRP (hold power button and Volume Down). A notification will pop up and select to "Keep System Readonly" (I think something like that). Reboot into system.
If everything worked as intended, a safetynet check will reveal everything in green, allowing you to both have root access and also run apps like Netflix and Android Pay
NOTE: Magisk Modules should be flashed via TWRP. For some reason, Magisk Manager is unable to install them.
EDIT: I tried to install xposed systemlessly but Safetynet was triggered. Don't think I can figure this out.
DahakePL tried with elite kernel and it didn't work. Writing this just in case anyone tries.
This worked for me but I can't guarantee it will work for you. (Photos at the end)
Did this guide help you? If you need any help, I will do my best to answer your questions.
I am not a developer and I do not really understand why or how everything works. I came across this method that worked for me and I thought I'd share it since I couldn't find a guide for my xperia phone when I needed it.
IN CASE SAFETY NET IS TRIGGERED, the only way to restore to everything in green is to reflash the stock rom (you don't have to format everything).
Did it work out for you? Just leave a reply saying that so I can figure out if everything works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
Thank you man
Great job
Hi there and great job. Many thanks for this.
I've a question, "(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above (after you select the file there are 2 versions. pick the modified one)." - what if another .291 stock firmware is used (eg downloaded from Xperifirm)?
fribriz said:
Hi there and great job. Many thanks for this.
I've a question, "(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above (after you select the file there are 2 versions. pick the modified one)." - what if another .291 stock firmware is used (eg downloaded from Xperifirm)?
Click to expand...
Click to collapse
Well, this worked on this exact version. If you don't use it, i can't guarantee it will work.
Well, can't either way
But it worked on that one. I believe you don't have to reinstall your stuff if you already have the stock rom. You can just flash it over without deleting anything
Works fine thank you
Adriano-A3 said:
Thank you man
Great job
Click to expand...
Click to collapse
Awesome
I'm actually surprised.
Doesn't work on elite kernel, just tested, no root and no safetynet
DahakePL said:
Doesn't work on elite kernel, just tested, no root and no safetynet
Click to expand...
Click to collapse
Have you tried with the advanced kernel I linked?
Also, you have to be running stock
Xperia z2
IceGordol said:
Have you tried with the advanced kernel I linked?
Also, you have to be running stock
Xperia z2
Click to expand...
Click to collapse
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
DahakePL said:
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
Click to expand...
Click to collapse
Modified the post in order to specify this. Also credited you. Thanks for this addition.
Where is modified FTF?
Sent from my D6503 using Tapatalk
Why do I need to flash TWRP? It is already included into advanced stock kernel.
After flash magisk, can't mount otg drive in twrp
Sent from my D6503 using Tapatalk
I am running a phone with KK 4.4.4 rooted and xposed installed. What should I do first to use it?
If I want to keep few apks data?
May I install Cyberian Camera MOd after it?
Thanks you! Working finally!
609125 said:
Thanks you! Working finally!
Click to expand...
Click to collapse
How u make it working? I got no clue about step 2... rootkernel old_boot.img new_boot.img? I really have no idea about the instructions...
---------- Post added at 04:10 PM ---------- Previous post was at 04:03 PM ----------
DahakePL said:
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
Click to expand...
Click to collapse
Guys, I once rooted my Z2 with SuperSU in locked bootloader condition (already unroot it). Im interested with magisk and want to try it. Is it possible for me even my device is bootloader locked? Thank you
IceGordol said:
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
Click to expand...
Click to collapse
Perfect for me. Thank you very much!
But your step 9 is wrong. should be "fastboot flash boot patched_boot.img"
My ROM is Marshmallow_Stock_575_ROM_Ultraslim
must remove SuperSU (root) before installing, use UPDATE-unSU-signed.zip
Can't get this to work at all. I'm on Customised UK stock ROM.
No matter what I do, I get bootloops once Magisk is installed. If I use the Magisk Uninstaller from TWRP the phone works fine again.
EDIT: I should have said, I've tried with Magisk 16.0 and 16.7 Beta. No luck with either. I've also tried patching the advanced stock kernel boot.img and I've tried installing via TWRP with Bootloader-SonyELF. No luck again, just the same bootloop!
UPDATE: I managed to fix this by using the latest version of the RootKernel patching tool (v5.23) instead of v4.31 and following the rest of the instructions using the boot.img from advanced stock kernel with Magisk 16.7 installed successfully.
Work fine with Magisk 18
okay after two soft brick, red blinking light and the device wont turn on, i finally succeed installing this. the first issue i'm getting is adb command not found when running the "fastboot flash boot patched_boot.img", so i tried to use TWRP to install the img, which refuse saying it need bootbridge, so i install through the recommend option in magisk manager (installing directly) which cause the first brick
the first brick is restored by using flash tool
the second brick can't be restored by flash tool due to the usb debugging is off causing flash tool to said "device connected but using old drivers", luckily xperia companion software (now called emma) restored it succesfully
and i finally figured what causing the soft brick, since emma said the bootloader is locked and magisk can't be used with locked bootloader and that bricked the device.
anyway finally unlocked the bootloader since emma needed it to unbrick the device. and after unlocking the bootloader and follow again the procedure here i finally succeed installing magisk on my z2
TLDR: YOU NEED UNLOCKED BOOTLOADER TO FOLLOW THIS PROCEDURE. to check easily if your bootloader is locked or not is just by running Emma (xperia updater replacement) or use "fastboot oem device-info".
finally can try magisk, since many apps detect supersu now and refuse to work with it. i didn't unlocked the bootloader the first time since supersu can work with locked bootloader >_>
Working:
Scaner works
Wi-fi
net
camera (photo)
Blutz
LTE
nfc
Does not work:
camcorder (does not write video)
until I found
Installation:
HTML:
fastboot flash boot boot.imgfastboot flash recovery recovery.imgfastboot flash system system.imgfastboot flash userdata userdata.imgfastboot flash cache cache.imgfastboot flash oem ******
Download oem:
https://developer.sony.com/file/dow...es-for-aosp-pie-android-9-0-kernel-4-9-loire/
Firmware
F5122:
https://mega.nz/#!SRU2mITa!QfO1w2dcldZBuCo6V0IXiRWGuw2vQ_sq_AI05pZTxE0
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Will give it a roll on single for u ?
Flashed it and here are some findings :
Everything is smooth, official twrp works but rooting isn't possible just yet.
Bugs I found :those mentioned above, adb doesn't work; it shows the device as offline, the disable absolute volume option in developer settings doesn't work, no auto brightness, random reboots every once in a while, proximity sensor isn't working, camera key doesn't work, no otg, speakers and camera are bad (just like other roms)
Other than that, NFC, gapps work (contacts aren't syncing) , RIL, WiFi, bt work fine.
I can use this as a daily driver.
hello good job i test on my f5121 and return to you !!! thank you
F5121 system not work failed verification at start but work with F5122 dual system.img !!!
hello @twain55 test root with magisk 17.1 it work !!! https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Without the permission of the OP
I bring to you the correct explain for Install the ROM on Xperia X F5121 (Single Sim):
Step 1:
Download the F5121 ROM Build from OP.
Step 2:
Download the F5122 system.img.
Step 3:
Replace recovery.img with the latest TWRP (thanks to @Chippa_a) and renamed the file as "TWRP.img".
Step 4:
Put it all in a folder and use the follow utility for install the ROM:
For Windows (Install Minimal ADB and Fastboot first, and put ROM Files and the Utility there)
For Linux/Mac (Install ADB and Fastboot from Terminal first, and put this utility with the ROM files).
Step 5:
After install DON'T BOOT the phone for now; in change, try boot to TWRP and install the Gapps.
Step 6:
Boot to the phone normally, and enjoy.
Q&A:
Q: Why I need flash the F5122 system.img on my F5121?
A: Cuz, system.img from F5121 build launch a "failed verification" at start, and doesn't work. (Thanks to @xrenoix, for the info).
Q: Can I install the Gapps later to the first boot?
A: You can't, sometimes, doesn't show when you install it after to the first boot.
Q: Can I root the AOSP 9.0 ROM?
A: Maybe, using Magisk 17, I suppose.
Q: Why I can't download anything with the browser?
A: Well, normally the AOSP Browser on alpha builds is bugged in general, the downloads, included.
Q: Why you put an Utility for install the ROM?
A: Easy, for make some time and the new persons in this don't be stressed trying installing the ROM.
Q: Official GApps doesn't show after install, now what?
A: For the moment IDK how to fix it; try ask to the OP @[email protected], for that.
My personal review of this build:
Working:
Boot (Only if you flash the F5122 system.img)
RIL (LTE included)
Bluetooth (Less for calls)
Wi-Fi
Fingerprint (Slow, but safe )
NFC (Works perfectly)
GPS
Audio (Some noisy, but is okay)
Not working
Camera button
Proximity Sensor
Accelerometer
Gyroscope
Ambient Sensor
Video recording
MTP when you don't enable from Dev Options.
(That's for now).
@sebasrock156
mtp work bro with devellopement setting change after connect !!! and majisk 17.1 work too but if you moded you have bootloop i have install xperia home in system bootloop for this moment no test majisk 17.2 sinfff
F5121 Download link is dead
tak40548798 said:
F5121 Download link is dead
Click to expand...
Click to collapse
Try with this AOSP Pie for Xperia X Single Sim
Bootloop
I got bootloop when I tried to install Stock Gapps package
Does anyone know the reason why it caused bootloop?
danghoangkpd said:
I got bootloop when I tried to install Stock Gapps package
Does anyone know the reason why it caused bootloop?
Click to expand...
Click to collapse
Gapps nano okay
Security Patch, October!
https://www.youtube.com/watch?v=2FZ_MYkKvP0&feature=youtu.be
Hi! Is patch October already integrated to your ROM or your ROM can be updated OTA to the latest security patch?
HepCat86 said:
Hi! Is patch October already integrated to your ROM or your ROM can be updated OTA to the latest security patch?
Click to expand...
Click to collapse
https://mega.nz/#!LFE33Y7R!VgJvqjYO5dFZ95O2PzgOT8Jf5x-Gr0LoHMb8N6P0DVU
Can't you upload to Google drive? Mega is kinda slow
twain55 said:
Can't you upload to Google drive? Mega is kinda slow
Click to expand...
Click to collapse
https://drive.google.com/open?id=1H3Wecymk3-CnSewUTFFEI7QozBdx9Eph
[email protected] said:
https://drive.google.com/open?id=1H3Wecymk3-CnSewUTFFEI7QozBdx9Eph
Click to expand...
Click to collapse
Danke!
Anyways, I flashed the ROM and Bluetooth doesn't work. Is this a known bug?
EDIT: Bluetooth, GPS aren't working in this build. And phone calls can't be heard with v2 of software binaries. V1 is more stable.
EDIT 2: I'm done using this. It can't be rooted and every time I try to reboot, it fails verification and powers off. Don't know if it's a problem with the software binaries or the ROM.
twain55 said:
Danke!
Anyways, I flashed the ROM and Bluetooth doesn't work. Is this a known bug?
EDIT: Bluetooth, GPS aren't working in this build. And phone calls can't be heard with v2 of software binaries. V1 is more stable.
EDIT 2: I'm done using this. It can't be rooted and every time I try to reboot, it fails verification and powers off. Don't know if it's a problem with the software binaries or the ROM.
Click to expand...
Click to collapse
Looking for new binars
MY xperia X pie rom
The process is successful until here. goal of the converter and camera port
https://i.hizliresim.com/NDyXrP.png
https://i.hizliresim.com/aY4v2O.png
https://i.hizliresim.com/AzoV3p.png
https://i.hizliresim.com/0zPXy9.png
November security patch !!!