Stock Kernel + ROOT + TWRP + DRM Fix
Code:
** Your warranty is now void.
**
** I am not responsible for bricked devices, dead SD cards,
** thermonuclear war, or you getting fired because the alarm app failed. Please
** do some research if you have any concerns about features included in this MOD
** before flashing it! You are choosing to make these modifications, and if
** you point the finger at me for messing up your device, I will laugh at you.
**
Update July 31, 2018
This thread is marked as discontinued. This means that It won't be updated so don't bother asking and I will not publish any more posts here or contribute to the general discussion. However, I might add files from time to time if necessary.
Requirements
If you haven't unlocked bootloader yet check this guide
Good News ! If you have TA.img backup of your device I highly suggest using this tool to patch stock kernel using your own TA image to have drm working with latest Magisk 16.3. Follow TA_POC METHOD instructions below .
- Kernel (boot.img) + Magisk + DRM fix patch
https://drive.google.com/open?id=1wv-Djz38wT_gywlJZPFPG13dATP90-E8
- Latest TWRP from here
And obviously :
- ADB and FASTBOOT : https://forum.xda-developers.com/showthread.php?t=2317790
- Xperia XZ drivers : https://developer.sonymobile.com/downloads/drivers/xperia-xz/
- FlashTool : http://www.flashtool.net/downloads.php
What are DRM Keys ?
If you unlocked the bootloader on a Sony Xperia device, you probably know that the potential loss of warranty is not the only disadvantage you have to accept. Another fairly hidden issue is related to various proprietary features such as the X-Reality color mangement, BIONZ image processor and the active noise cancelling techniques. Once you decide to unlock your bootloader, the process also removes a piece of data referred to as the DRM keys. These are tied to various services (such as streaming video and the like) offered by Sony but are also required for the features mentioned above to work properly. Put simply, once the keys are gone, you’ll face issues such as decreased low light camera image quality and the lack of the X-Reality mode.
Click to expand...
Click to collapse
Kernel features
this is pure stock kernel of the mentioned above firmware with
- RIC disabled
- added DRM patch support
Instructions
Before proceed backup all you important data like pictures, files to another device.. !
Make sure you follow all steps carefully with caution .. !
01- Flash Oreo FTF via Flashtool (Full wipe is recommened exclude nothing except TA files if there's any)
02- When done flashing unplug device ..
03- Enter fastboot mode and flash TWRP (hold vol up + plug usb)
Code:
fastboot flash recovery twrp-3.2.1-0-kagura.img
then flash kernel
Code:
fastboot flash boot boot.img
04- Unplug and enter TWRP (Hold vol down + power button)
05- In TWRP Flash drmfix.zip + SafetyNet Cleaning Tools.zip then Magisk v16.3.zip
06- OPTIONAL Flash ROM Patch to clean system and remove all bloat apps
07- Reboot and enjoy
Click to expand...
Click to collapse
NEW! TA_POC METHOD (Magisk 15.3+ ONLY / For those who have TA.img backup)
After downloading and extracting this tool and these files just copy them to the tool folder and put yout TA.img (case sensetive) there as well
{
"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"
}
Open command prompt in rootkernel tool folder
or
Open cmd --> cd "rootkernel tool dir" for ex for my case I extracted to the c: drive to make simple for you
Code:
cd C:\rootkernel_v5.23_Windows_Linux_UNOFFICIAL_2.5_OREO
Then run this code
Code:
rootkernel kernel.elf boot.img
Say yes (Y) to everything except DRM fix - If you want munjeni's TA PoC option,ensure your TA.img (case sensitive) is located at rootkernel's root folder and say no (N) to DRM fix
Flash patched kernel:
1- Flash Oreo ftf (wiping everything, excluding nothing - except *.ta files - if any)
2- Unplug device and DO NOT turn it on
3- Fastboot newly created boot.img and TWRP recovery
4- Unplug device and DO NOT turn it on again
5- Enter TWRP recovery and flash Magisk 16.3 (16.4 is buggy)
6- OPTIONAL Flash ROM Patch to clean system and remove all bloat apps
7- You're done!
Click to expand...
Click to collapse
TWRP asking for decryption code / Internal Storage showing 32GB only for XZ DUAL
Turn off the phone (from TWRP if you can or hold vol up and power button till the phone vibrates 3 times)
Enter Fastboot and format user data partitions using this code
Code:
fastboot format userdata
If you are getting error try from TWRP recovery > WIPE > Swipe to format data
Now start your phone and set it up the issue should be resolved.
If still storage is not showing correctly
- Do steps 1-2-3 exactly as listed above
- Boot your phone and compelete the setup wizard, go to settigns and check if storage is not 64gb
- If yes turn off the device and enter TWRP and choose WIPE > Swipe to format data
- Boot your phone again and compelete the setup wizard, go to settings and check if storage it should be 64gb by now
- Now go back to TWRP and complete steps 4-5-6
To check drm keys type *#*#7378423#*#* on your phone and go to Service Test > Security
If you have all [Key OK] they are OK! like the pictures I attached below
Extras (Recommended)
- LXT (Battery Life | Speed Tweaks)
- [MOD][THERMAL FIX] FSC™ 4.0 Improve performance & Eliminate heat
- [XZ/XZs/XP]V1 Dontbelive XPERIA XZ1 StereoMOD
- [Magisk][Module] SELinux Manager by Jman420 (Set to permissive)
- [Magisk][Module] Unified Hosts Adblocker
- [Magisk][Module] Youtube Vanced [Official]
Must have apps
- Gboard - the Google Keyboard
- Brevent
- Kiwi Browser - Fast & Quiet
Credits @serjar for unofficial rootkernel update
Old DRM restore by @tobias.waldvogel
Magisk by @topjohnwu
SafetyNet Cleaner by @sceryavuz
TWRP by TeamWin
I may sound foolish but what is drmfix ?
Thanks a lot mate.This works great. BTW those on rooted nougat with recovery can skip until step 5.
---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------
ilininja said:
I may sound foolish but what is drmfix ?
Click to expand...
Click to collapse
it amends for any function lost when unlocking the bootloader.(like low light noise reduction and X-reality)
ilininja said:
I may sound foolish but what is drmfix ?
Click to expand...
Click to collapse
Well if you did a little research you would know..
Basically all Sony xperia phones have a lot of features like BionZ aka camera sharpening/ processing/noise reduction, X-Reality / Bravia engine for display ,Noise Cancelling and other audio enhancing features which is really awesome
But first when you unlock the bootloader , those keys called drm in short.. every sony device have them preinstalled will be gone .. ALL THESE GOODIES WILL STOP WORKING ..
Here came the importance of drm patches to emulate those lost keys and restore full features !
korom42 said:
Well if you did a little research you would know..
Basically all Sony xperia phones have a lot of features like BionZ aka camera sharpening/ procecing, noise reduction, X-Reality / Bravia engine for display ,Noise Cancelling and other audio enhancing features which is really awesome
But first when you unlock the bootloader , those keys called drm in short.. every sony device have them preinstalled will be gone .. ALL THESE GOODIES WILL STOP WORKING ..
Here came the importance of drm patches to emulate those lost keys and restore full features !
Click to expand...
Click to collapse
Thank you for the answer, I did some research but didn't quite get it
bro @korom42
works this also on xzs with already on oreo with unlocked bl?
cant downgrade in that case no ftf for XZs - __-
Verstuurd vanaf mijn G8231 met Tapatalk
@korom42
it is weird but My apps can't detect root.BTW have you experienced slowdown in performance?
josephnero said:
@korom42
it is weird but My apps can't detect root.BTW have you experienced slowdown in performance?
Click to expand...
Click to collapse
- Is magisk manager saying everything is fine ? Maybe try clear its data from settings
- No slowdowns here at all oreo seems to be super smooth (I did full wipe / clean installation )
because you upgraded while keeping data some apps may have problems asking for root .. try wiping those apps data ?
korom42 said:
- Is magisk manager saying everything is fine ? Maybe try clear its data from settings
- No slowdowns here at all oreo seems to be super smooth (I did full wipe / clean installation )
because you upgraded while keeping data some apps may have problems asking for root .. try wiping those apps data ?
Click to expand...
Click to collapse
Magisk doesn't have magisk su..BTW can it be that my XZ is dual sim version?I'll try with full wipe and report back again
josephnero said:
Magisk doesn't have magisk su..BTW can it be that my XZ is dual sim version?
Click to expand...
Click to collapse
I have xz dual too no problem .. I noticed there's new version of magisk v14.5 check it here
Also make sure you followed the instructions carefully (you have to flash the oreo kernel boot image I gave like described )
I'll try again with full wipe and be very careful with steps.will report back soon
Pandemic said:
bro @korom42
works this also on xzs with already on oreo with unlocked bl?
cant downgrade in that case no ftf for XZs - __-
Verstuurd vanaf mijn G8231 met Tapatalk
Click to expand...
Click to collapse
i dont think so bro if you allready run the kernel you will not be able to flash a new kernel without root. At least i attempt this on my xz with oreo with no luck. cheers
@korom42
Total clean install plus latest magisk did it for me. now I'm rooted with DRM fix .thanks a lot.BTW I didn't downgrade the last time.just flashed OREO plus recovery and then the kernel and ....
@juanpirulo
flashing kernel doesn't need root.just unlocked bootloader. try clean install.
im currently at oreo, and can't downgrade cause flashtool refuses to flash because "unknow sources" is dissabled, but oreo removed such option... what should i do?
Solved: has to use latest flashtool...
TNX for share with us the root method
for time saving... No need to downgrade!
1- flash oreo fw with flashtool
2- unplug your phone after flashing is end but don't turn on device. hold VOL-UP and plug phone againe to PC. (fastboot mode)
3- flash twrp-3.1.1-0-kagura.img
4- flash boot_oreo.img
5- unplug your XZ then boot to recovery. hold VOL-DOWN + POWER
6- flash drmfix, SafetyNet_Cleaning_Tools, Magisk-v14.5(1456) zip files step by step
7- reboot your device...
8- NOW, you can setup your new firmware pre-rooted and drmfixed
GenomeX said:
TNX for share with us the root method
for time saving... No need to downgrade!
1- flash oreo fw with flashtool
2- unplug your phone after flashing is end but don't turn on device. hold VOL-UP and plug phone againe to PC. (fastboot mode)
3- flash twrp-3.1.1-0-kagura.img
4- flash boot_oreo.img
5- unplug your XZ then boot to recovery. hold VOL-DOWN + POWER
6- flash drmfix, SafetyNet_Cleaning_Tools, Magisk-v14.5(1456) zip files step by step
7- reboot your device...
8- NOW, you can setup your new firmware pre-rooted and drmfixed
Click to expand...
Click to collapse
have you done a dirty oreo flash? (without wipe data?) because i can get root . i will try with a full wipe. cheers
juanpirulo said:
have you done a dirty oreo flash? (without wipe data?) because i can get root . i will try with a full wipe. cheers
Click to expand...
Click to collapse
when I flash with flashtool, check all wipe for clean install no mater android m,n or p
What does the kernel do? Or is it just a normal "unlocked" .401 kernel?
can someone make it so for XZs?
i have kernel.elf of Oreo, here
https://drive.google.com/file/d/1RmCYNDka390XrLmcTRZnUo9wYSFs2W3O/view?usp=drivesdk
Verstuurd vanaf mijn G8231 met Tapatalk
Pandemic said:
can someone make it so for XZs?
i have kernel.elf of Oreo, here
https://drive.google.com/file/d/1RmCYNDka390XrLmcTRZnUo9wYSFs2W3O/view?usp=drivesdk
Verstuurd vanaf mijn G8231 met Tapatalk
Click to expand...
Click to collapse
Check your WhatsApp/telegram ?
Related
{
"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"
}
Hello guys,
This is my first guide and it is focused on people who just bought their Redmi Note 3 (KENZO/KATE) and having problems with officially unlocking their bootloader. (stuck @ 50% like me)
If you don't want to wait on stock MiUi until you can officially unlock your bootloader (because you need to wait additional ~2 weeks after you received permission from Xiaomi until their servers updated) or you want that extra security layer with locked bootloader this guide is made for you!
Since official LineageOS 14.1 just released, i thought some of you guys are interested in this awesome, easy and safe method.
To save you time searching hours and hours through this forum i made this quick summery.
Downloads :
MiUi 8 Global Developer ROM 6.11.3: KENZO or KATE
ZCX TWRP (direct downloadlink: click here)
Mi Flash 6.8.30
Latest firmware (choose correct device)
[ROM][OFFICIAL][7.1.1][kenzo] LineageOS 14.1 by The_strix
Open GApps - ARM64 - Android 7.1
Instructions : (follow them carefully!)
Extract MiUi 8 Global Developer ROM and replace recovery.img (in images folder) with ZCX TWRP's recovery.img
Flash using Mi Flash (in EDL mode) and check clean_all
After finished flashing process unplug and press [volume up]+[power] until Mi logo shows up then release buttons and it boots to TWRP (change TWRP language from chinese to english: click here)
Reboot to system (if you get prompt: "Disable stock recovery replace now" > just swipe to allow disable)
Boot to MIUI and complete initial setup (important step - don't skip! first boot will take around 10 minutes)
-----------------------------------------------
Shutdown device and boot to TWRP again
(optinal) Backup every partition and safe this backup on an external device
Wipe > Advanced Wipe > check Dalvik / ART Cache, System, Data, Internal Storage, Cache > Swipe to Wipe
Flash Latest firmware, LineageOS 14.1 and GApps (ARM64, Android 7.1)
Reboot to system and you're DONE!!
updated method (works with newest MIUI version) :
There is a new updated method by kuan improved by @N.G. and @razr_96. Thanks for mentioning.
Advantages:
no need to download full MIUI fastboot rom
much faster method, only takes seconds to flash (instead of 4 minutes and you don't have to complete initial MIUI setup which also takes around 5 minutes)
this method is better if you want to stay on MIUI and just want to root
you can stay on your current MIUI version (even 7.1.19 which is currently the latest) and don't have to wipe your data
Disadvantages:
this doesn't clean everything, i would recommend to clean everything if you want to install a custom rom
you have to download a file i can not verify
Instructions : (follow them carefully!)
(optinal) Backup your current MIUI data (Settings > Additional settings > Backup & reset > Local backups > Back up) and copy it to an external media
Download and extract: Kenzo or Kate
(optinal) Replace included ZCX TWRP recovery.img (in images folder) with your preferred TWRP recovery.img
Flash using Mi Flash 20160401 (in EDL mode) and check flash all except data and storage (not clean_all like in the method mentioned above)
BE AWARE: This MiFlash version is different to the MiFlash version mentioned above! This version does only support 64 bit systems and you need atleast Windows 7!
After finished flashing process unplug and press [volume up]+[power] until Mi logo shows up then release buttons and it boots to TWRP (change TWRP language from chinese to english: click here)
Reboot to system
Video tutorial: https://www.youtube.com/watch?v=rCONN1_IPuU
Troubleshooting :
[APP][ROOT][7.1.1]QuickSettings Flashlight fix for all nougat roms
If something goes wrong, start over again and follow my guide step by step.
This guide only works with MiUi 8 Global Developer ROM 6.11.3 or lower.
Put MIUI 8 Global Developer ROM in "C:\ROM" - MiFlash tends to have problems if there are any spaces in folder names.
If you flashed something wrong and have no simcard signal anymore or no IMEI look here for help: EFS Recovery Guide
If you didn't remove your passcode before you did a backuprestore using TWRP:
TWRP > Advanced > Filemanager > /data/system > delete locksettings.db
Issues with locked bootloader :
none
(advanced technique) Higher security with locked bootloader:
Thanks @LeoYL !
A little addition: If you want a even higher level of security, which is nobody except you can flash packages in recovery, you can create a recovery with limited functions and forced signature verification, with your own keys embedded in that recovery.
This is just like the original status of nearly all Android devices when they are shipped: only signed OTA update packages can be applied via recovery. Normally, the packages are signed by OEMs; however, you can become the "OEM" by creating your own private key, which is used during package signing.
Just follow these guides to create a recovery with your own keys. I use CM 13.0 recovery, since it only has basic recovery features, including installing a ZIP file, factory reset, and it has mandatory ZIP signature verification.
http://mjg59.dreamwidth.org/31765.html
https://forum.xda-developers.com/showpost.php?p=62796459&postcount=2
The reason why I don't use TWRP is that it allows update packages with any signature. Although you can enforce signature verification, it can also be switched off in TWRP settings.
Now you get a recovery which only accepts ZIP packages that are signed with your own private key. The only downside is you need to sign every package you want to flash each time. But this also means that if a stranger picks your lost phone up, they can't tamper your phone's OS. If the "reset protection" feature works with locked bootloader on our Redmi Note 3, the only distance between our phones' security and Google devices' is edl mode and encryption.
Wanna try other custom roms?
Just follow this guide and you can flash every other nougat customrom as well like:
[ROM]AOSIP 5.5 for Redmi Note 3(Kenzo)[OFFICIAL BUILDS]
[ROM][Nightlies][android-7.1.1_r6]ResurrectionRemix 5.8.0[OFFICIAL][VoLTE]
[ROM][OFFICIAL][Weekly][7.1.1_R13][Slim 7 For Kenzo]
[ROM] ► [7.1.1 ► N4F26M] ► [OTA][OMS][Goodix] ► Nitrogen OS
credits :
@The_strix: For his development work
@Psy_man: For extracting nougat firmware
@kuan: For creating this method (french forum)
@Tobsucht TM: For answering my questions
If this guide was helpful to you, don't forget to press the Thanks! button :good:
Enjoy your new custom rom!
khajiit
This method also works with Kenzo, obviously using the Kenzo miui rom and firmware instead.
razr96 said:
This method also works with Kenzo, obviously using the Kenzo miui rom instead as well as not flashing the kate firmware.
Click to expand...
Click to collapse
That's right! Thanks for pointing it out.
Redmi Note 3 SE _ Kate
Thanks bro worked on my Kate :good:
How to successfully unlock bootloader(official way) worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
Just use that Miflash : rootjunkysdl.com/files/Redmi%20Note%203%20Pro%20Kenzo/Firmware%20Unbrick/MiFlash.zip
Because that one in thread not working properly.
armo1111 said:
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
Just use that Miflash : rootjunkysdl.com/files/Redmi%20Note%203%20Pro%20Kenzo/Firmware%20Unbrick/MiFlash.zip
Because that one in thread not working properly.
Click to expand...
Click to collapse
The guide you linked is not working for me, thats why i made this guide which works 100%.
I tried this with the Global developer ROM for my kenzo.
When I try to get into TWRP, the Mi logo flashes but nothing else happens.
When I let the MIUI ROM start up and try to get into the recovery again,
it only shows me to connect my device to the Mi PC Manager.
What am I doing wrong?
blitzpeace said:
I tried this with the Global developer ROM for my kenzo.
When I try to get into TWRP, the Mi logo flashes but nothing else happens.
When I let the MIUI ROM start up and try to get into the recovery again,
it only shows me to connect my device to the Mi PC Manager.
What am I doing wrong?
Click to expand...
Click to collapse
Did you follow my instructions correctly?
- replaced recovery.img with ZCX TWRP recovery.img - check?
- EDL mode - check?
- remove usb cable after flash and press volume up+power button until mi logo shows up and then release buttons - check?
- are you sure you have kenzo version? did you download rom for kenzo? - check?
!! caution: the rom linked in this guide is only for kate version!!
thank you ! I've been trying the official route for 6 weeks, getting absolutely nowhere (even though I finally do have unlock permission).
this method worked like a charm, finally I'm off MIUI and running LineageOS
khajiit said:
Did you follow my instructions correctly?
- replaced recovery.img with ZCX TWRP recovery.img - check?
- EDL mode - check?
- remove usb cable after flash and press volume up+power button until mi logo shows up and then release buttons - check?
- are you sure you have kenzo version? did you download rom for kenzo? - check?
!! caution: the rom linked in this guide is only for kate version!!
Click to expand...
Click to collapse
1. I guess, do I have to replace only the recovery.img or more? If only recovery.img, then yes!
2. Yes, otherwise MiFlash would give me an error instead of flashing the ROM
3. Yes, but it appears only for an blink of an eye and then disappears again, the phone screen then stays dark
4. Yes, the newest one. Maybe that's the problem?
blitzpeace said:
4. Yes, the newest one. Maybe that's the problem?
Click to expand...
Click to collapse
Yes, that's the problem! This method only works until version 6.11.3.
You have to flash 6.11.3 (or earlier) to get TWRP and then you can flash what you want.
Good luck!
Excellent :good:
To boot into EDL
If you are lost with chinese language in TWRP, look at the first screenshot
And for Gapps take 64bits
Hi, I just got this ROM but when I plug the device in my computer it keeps connecting/disconnecting rapidly. Did I do something wrong?
Very helpful, but i would like to suggest people to use miunlocktool from windows 7-32 bit operating system. Miunlocktool perfectly works in windows 7 & don't stuck at 50%. Before unlock process, just "add oem unlocking device" from MIUI developer setting then start unlocking process..... Its really works for me & also others who followed these steps.
Skex506 said:
Hi, I just got this ROM but when I plug the device in my computer it keeps connecting/disconnecting rapidly. Did I do something wrong?
Click to expand...
Click to collapse
Yes, you did something wrong
Are you sure you have a "KATE" device not "KENZO"?
Follow my guide carefully and try again. It works 100%!
Rifatspir said:
Very helpful, but i would like to suggest people to use miunlocktool from windows 7-32 bit operating system. Miunlocktool perfectly works in windows 7 & don't stuck at 50%. Before unlock process, just "add oem unlocking device" from MIUI developer setting then start unlocking process..... Its really works for me & also others who followed these steps.
Click to expand...
Click to collapse
You don't think i've/we've tried everything? Official unlock works for you? Great! But it doesn't work for everyone... trust me.
Can we please stop to suggest to unlock officially with different guides? This guide is for people who don't want to or can't unlock officially.
khajiit said:
You don't think i've/we've tried everything? Official unlock works for you? Great! But it doesn't work for everyone... trust me.
Can we please stop to suggest to unlock officially with different guides? This guide is for people who don't want to or can't unlock officially.
Click to expand...
Click to collapse
I also said that million times to other people who suggest me different types of official method. When i success after trying couple of methods then i realized it is possible to unlock kate. I'm not saying that your post is not helpful, i saw many post like that, mostly in whirlpool forum. BTW, good luck with your tips :good:
Sure it is possible to unlock Kate officially but you have to wait for Xiaomi to get permission and wait for their servers to syncronize.
You have to wait up to 1 month (depending on your location and other things) until their servers confirms that you have permission to unlock (unable to verify thing). All these guides outside are working but it's a matter of time until they start working. That's why they didn't work for you in first place. :good:
hi @khajiit
They say not enough storage when I want to flash it. Could you please help me with this?
Spoiler: not enough
actuallyaka said:
hi @khajiit
They say not enough storage when I want to flash it. Could you please help me with this?
Click to expand...
Click to collapse
You are using a really old MiFlash version, try updating to the version mentioned in this guide.
And rename your folder "Redmi note 3 pro" to "Redmi.note.3.pro" or "Redmi_note_3_pro".
MiFlash tends to have problem with spaces.
khajiit said:
You are using a really old MiFlash version, try updating to the version mentioned in this guide.
And rename your folder "Redmi note 3 pro" to "Redmi.note.3.pro" or "Redmi_note_3_pro".
MiFlash tends to have problem with spaces.
Click to expand...
Click to collapse
Thank you khajiit..
it works know with using 2016 version..
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!
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 >_>
Stock Kernel + ROOT + TWRP + DRM Fix
Code:
** Your warranty is now void.
**
** I am not responsible for bricked devices, dead SD cards,
** thermonuclear war, or you getting fired because the alarm app failed. Please
** do some research if you have any concerns about features included in this MOD
** before flashing it! You are choosing to make these modifications, and if
** you point the finger at me for messing up your device, I will laugh at you.
**
Requirements
If you haven't unlocked bootloader yet check this guide
Good News ! For advanced users If you have TA.img backup of your device I highly suggest using this tool to patch stock kernel using your own TA image to have drm working with latest Magisk 16.3. Follow TA_POC METHOD instructions below .
- Kernel (boot.img) + Magisk + DRM fix patch : Here
- Latest TWRP from here[/B]
And obviously :
- ADB and FASTBOOT : https://forum.xda-developers.com/showthread.php?t=2317790
- Xperia X PERFORMANCE drivers : https://developer.sonymobile.com/downloads/drivers/xperia-x-performance-driver/
- FlashTool : http://www.flashtool.net/downloads.php
What are DRM Keys ?
If you unlocked the bootloader on a Sony Xperia device, you probably know that the potential loss of warranty is not the only disadvantage you have to accept. Another fairly hidden issue is related to various proprietary features such as the X-Reality color mangement, BIONZ image processor and the active noise cancelling techniques. Once you decide to unlock your bootloader, the process also removes a piece of data referred to as the DRM keys. These are tied to various services (such as streaming video and the like) offered by Sony but are also required for the features mentioned above to work properly. Put simply, once the keys are gone, you’ll face issues such as decreased low light camera image quality and the lack of the X-Reality mode.
Click to expand...
Click to collapse
Kernel features
this is pure stock kernel of the mentioned above firmware with
- RIC disabled
- added DRM patch support
Instructions
Before proceed backup all you important data like pictures, files to another device.. !
Make sure you follow all steps carefully with caution .. !
01- Flash Oreo FTF via Flashtool (Full wipe is recommened exclude nothing except TA files if there's any)
02- When done flashing unplug device ..
03- Enter fastboot mode and flash TWRP (hold vol up + plug usb)
Code:
fastboot flash recovery twrp-3.2.1-0-dora.img
then flash kernel
Code:
fastboot flash boot boot.img
04- Unplug and enter TWRP (Hold vol down + power button)
05- In TWRP Flash drmfix.zip + SafetyNet Cleaning Tools.zip then Magisk v16.3.zip
06- OPTIONAL Flash ROM Ptach to clean system and remove all bloat apps
07- Reboot and enjoy
Click to expand...
Click to collapse
TWRP asking for decryption code / Internal Storage showing 32GB only for DUAL Model
Turn off the phone (from TWRP if you can or hold vol up and power button till the phone vibrates 3 times)
Enter Fastboot and format user data partitions using this code
Code:
fastboot format userdata
If you are getting error try from TWRP recovery > WIPE > Swipe to format data
Now start your phone and set it up the issue should be resolved.
If still storage is not showing do clean installation in Flashtool wiping everything and exclude nothing then follow then instructions above .. I also noticed that flashing the correct XZ DUAL boot.img the first time before first boot fix this
To check drm keys type *#*#7378423#*#* on your phone and go to Service Test > Security
If you have all [Key OK] they are OK! like the pictures I attached below
Extras (Recommended)
- LXT (Battery Life | Speed Tweaks)
- [MOD][THERMAL FIX] FSC™ 4.0 Improve performance & Eliminate heat
- [XZ/XZs/XP]V1 Dontbelive XPERIA XZ1 StereoMOD
- [Magisk][Module] SELinux Manager by Jman420 (Set to permissive)
- [Magisk][Module] Unified Hosts Adblocker
- [Magisk][Module] Youtube Vanced [Official]
Must have apps
- Gboard - the Google Keyboard
- Brevent
- Kiwi Browser - Fast & Quiet
Credits @serjar for unofficial rootkernel update
Old DRM restore by @tobias.waldvogel
Magisk by @topjohnwu
SafetyNet Cleaner by @sceryavuz
TWRP by TeamWin
Doesn't work. When I did all, phone get infinite bootloading. And why TWRP shows F8131? My phone is F8132
---------- Post added at 08:23 AM ---------- Previous post was at 07:39 AM ----------
OP, before publishing, check it! Tried 2 method, still stuck on boot.
Finally, got it!
{
"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"
}
ramirrat said:
Finally, got it!
Click to expand...
Click to collapse
Great!! Did you do anything other than the OP instructions?
Hi,
I also managed to apply the procedure.
Links in requirement are not pointing to newsest TWRP and Magisk. They are pointign to TWRP 3.0.0 and Magisk 14.3. Now available are TWRP 3.1.1 and Magisk 14.5.
Generallt method one worked with full total wipe while flashing Oreo with flashtool.
serajr said:
Great!! Did you do anything other than the OP instructions?
Click to expand...
Click to collapse
Used method 2, but flashed this TWRP
YES ... the Problem was TWRP and MAGIKS. Thank You. I used Method 1 - ok
but "SHAME ON SONY" - still no RAW Format for Camera with Oreo. I will go back to Oreo AOSP - so i can use Google Camera with RAW.
thnx
gordon
Is it possible to root with SuperSU instead of Magisk? I had a lot of camera problems when I used Magisk. It's up to 2.82 now, I think that' a general Oreo compatible thing.
ok i got it all to work,
steps i performed, on my laptop windows 7 ult x64
downloaded and installed the following
ADB and FASTBOOT extracted it on my c:/adb
Xperia X Performance drivers extracted it on c:/
FlashTool installed it and it's drivers located in the install folder of flashboot
downloaded the folowing files
Oreo Kernel Image copy to c:/adb
https://mega.nz/#!OA5BBJDY!lQ9Xojv5DN45QPbUQt-iQGhI409B7l7WoWvo0GTqYlY]DRM fix patch copy to to phone memory
TWRP 3.1.1.0 have not tried latest yet but 3.1.1.0 works fine, copy to c:/adb
Magisks 14.5 Beta copy to phone memory
folowed the guide methode 1 with slightly changes
01- Flash Oreo FTF via Flashtool ([color=redFull wipe in TWRP since i don't quite know how to use flashtool[/color], exclude FOTAKERNEL !! )
02- When done flashing unplug device .. (Do not boot yet !!)
03- Enter fastboot mode and flash the given kernel image (hold vol up + plug usb)
Code: fastboot flash boot boot_oreo.img
04- Flash TWRP 3.1.1.0 have not tried latest yet but 3.1.1.0 works fine
Code: fastboot flash recovery twrp.img
05- Unplug and enter TWRP (Hold vol down + power button) and did full wipe except system and micro sd
06- Flash drmfix.zip
07- Flash Magisks 14.5 Beta
08- Reboot and enjoy
everything works fine
ramirrat said:
Used method 2, but flashed this TWRP
Click to expand...
Click to collapse
Got it working now, thanks!
Used Method 1 with given twrp.
@korom42 great job mate! :good:
HI, i'm just doing this guide. i've download the firmware from xperifirm, and i got 3 files withount extension. I've googled and i read a guide to converto these 3 files into a ftf via flashtool. At certain point, i have to select all files except all the .ta files, and create the zip. I'm right?
The files are:
auto-boot.ta
cust-reset-ta
fota-reset.ta
master-reset.ta
osv-restriction.ta
reset-kernel-cmd-debug.ta
reset-non-secure-adb.ta
reset-wipe-reason.ta
simlock.ta
thanks... method 1 [email protected] AndroPlus TWRP 3.1.1.0 used.
Up and running with method 1. Unfortunately I had to use Magisk, but so far it seems to behave. SuperSu does NOT work. It will install, but the device does not show root.
Installed and running with method 1 but got a lot of issue using Windows 10. So i do all the work on a Windows 7 laptop without any problem.
Just 1 thing not working: magisk.
I followed the guide step by step with success, but magisk says me to update, and when i hit yes, nothing happen.
See attachment.
And another thing. I've wiped all except fotakernel, so why when I've boot up the Phone, i find all my apps, my settings and wallpaper Like how i leave them?
Sorry for my English.....
Edit: can't use netflix anymore
Edit2: magisk problem solved. I've download The apk from The site, then installed and when i hit yes to install magisk, it download a flashable via twrp zip, flashed it and magisk work, but now I've Lost safetynet for no reason.....
But i can use netflix now.
Safetynet is a important thing?
I forgot to say that I used Windows 10, as always. Regular command prompt (writing cmd in the start menu will give that, nothing else). But problems with that is usually because of wrong drivers for the phone, nothing else.
After 2 days of usage, i noticed a lot of lag, so i've done a factory reset from the android menu, not twrp, and is all working fine withount any kind of lag (except at powe off, the circle stop running, then after 20 seconds, power off, but it's not important, maybe a sony bug).
Now can i reflash from twrp in order drmfix.zip, SafetyNet Cleaning Tools.zip then Magisk v14.5.zip, or i will do any mistake?
I've noticed sone remote play, netflix, sony news and sony lounge are not working, i think cause DRM
Hello korom42
Are you creating a kernel & root for a new release of sony? There are new updates & I'm eager for this new thing
Flashed 41.3.A.2.24 with wipes
Flashed oreo.img
Flashed twrp.img
Get bootloop
Time to update kernel
there is some problem with that kernel, my phone will reboot unexpectly.I'm sure i flash it the right way
---------- Post added at 12:17 PM ---------- Previous post was at 12:11 PM ----------
ramirrat said:
Flashed 41.3.A.2.24 with wipes
Flashed oreo.img
Flashed twrp.img
Get bootloop
Time to update kernel
Click to expand...
Click to collapse
try twrp 3.2 or 3.0
completed the steps, if i wanted to go back to 7 where do i find those files?