[FTF][Android 7.1.1][ROOT][R/W][32.4.A.1.54] E66xx + Patched Kernels (Google Drive) - Xperia Z5 General

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?

Related

D6503 [6.0.1] 23.5.a.0.570 prerooted+recovery+xposed [unlocked/locked bootloader]

XPERIA Z2 D6503 23.5.A.0.570 UNLOCKED/LOCKED BOOTLOADER
FLASHABLE ZIP
YOU WANT THE NEW ANDROID 6.0.1 MARSHMALLOW UPDATE ON YOUR XPERIA Z2 BUT YOU WANT TO KEEP ROOT, RECOVERY & XPOSED?
THEN KEEP READING THIS THREAD! ​
features::angel:
prerooted (BETA-SuperSU-v2.68)
recovery (twrp)
byeselinux
RICDefeat
bootloop fix
signed zip file
optional:
xposed framework v82
Sound 3 in 1 Bass Loud Stereo MM
DMR Function Restore V3 [Team HSxEXR]
and more!#
ftf:
D6503_23.5.A.0.570_1281-9715_R4D [AUSTRALIA]
https://youtu.be/Zx02x357Mo0​
Checklist:
lollipop (stock or stock based)
root
busybox
recovery
USB Debugging + Unknown Sources
ADB Drivers
non-xposed stock (USE xposed-UNINSTALLER)
Introduction:
Download the "Marshmallow_D6503.zip"
extract the zip file
boot into recovery
X. OPTIONAL flash "xposed-uninstaller-20150831-arm.zip" to remove LP xposed
FACTORY RESET
flash "flashableMM.zip"
flash "byeselinux_flashable.zip"
flash "RICDefeat.zip"
flash "Z2-6.0.1_570_bootloop_fix.zip"
wipe cache & dalvik
now it`s time to flash your favourite zip files like:
X. OPTIONAL XPOSED flash "xposed-v82-sdk23-arm.zip"
X. OPTIONAL UB flash "[Team HSxEXR] DRM function restore V3.zip"
X. OPTIONAL UB SOUND flash "Sound 3 in 1 Bass Loud Stereo MM.zip"
wipe cache & dalvik
reboot
install "BusyBox.apk" and install newest available version
X. OPTIONAL install "XposedInstaller_3.0_alpha4" for Xposed
Enable USB Debugging + Unknown Sources
Run "install.bat from /Z2_MM_TWRP_Recovery_V2_By_Serajr/ to install the Recovery
connect the Z2 to PC, phone will reboot into twrp
DONE:victory:
GOT TROUBLE WITH YOUR RECOVERY? RECOVERY FIX in 2 MINUTES:
open any root explorer app like ES FILE MANAGER
Delete /system/etc/mm_twrp_recovery folder
Go to /system/bin/ folder
Look for the "chargemon.stock" file - If it's present, delete this one: chargemon - and now, rename the chargemon.stock to chargemon
Look for the "taimport.stock" file - If it's present, delete this one: taimport - and now, rename the taimport.stock to taimport
Reboot
download "recovery fix.zip" from mega.nz
extract the file and run "adbrecoveryfix.exe" the .exe file will install some needed files (normally into C:\Minimal ADB and Fastboot\ )
copy the files from the folder "RECOVERY FILES" into the "Minimal ADB and Fastboot" Folder
connect your xperia with the pc
open the "m a a d" folder and then SHIFT+RIGHT CLICK to open a command window
now type:
adb shell
su root
mount -o remount,rw /system
exit
exit
install.bat
Click to expand...
Click to collapse
don´t forget to press enter after "adb shell", "su root" and so on!
now your recovery will install again without any errors!
MEGA.nz] DOWNLOAD:
OPTIONAL UB... optional step for unlocked bootloader
OPTIONAL... optional step for locked and unlockedd bootloader
DO NOT FORGET THAT IF YOU HAVE A LOCKED BOOTLOADER YOU ARE NOT ALLOWED TO FLASH ZIPS FOR UB LIKE THE DMR FUNCTION V3 ZIP FILE!
LIST OF WORKING FLASHABLE ZIPS:
xposed framework v82 sdk 23 arm [XPOSED
Sound 3 in 1 Bass Loud Stereo MM [SOUND MOD]
DRM function restore V3 [UB MOD]
thank you!
:good:
seems to work fine on my z2
can I also flash other zips like this one:
http://forum.xda-developers.com/xperia-z2/general/6-0-1-d6503-23-5-0-570-prerooted-t3364817
?
elitephantompro said:
:good:
seems to work fine on my z2
can I also flash other zips like this one:
http://forum.xda-developers.com/xperia-z2/general/6-0-1-d6503-23-5-0-570-prerooted-t3364817
?
Click to expand...
Click to collapse
if the zip file is comptible with marshmallow and the z2 of course you can i recommand to flash the zip files directly after "the bootloop fix file wipe"!
Recovery fix
UPDATE:
I FINALLY FOUND A SOLUTION FOR THE AFTER A WHILE DISAPPERAING TWRP RECOVERY!
SOMETIMES IT`s GOOD TO SEARCH IN OLDER THREADS
Problem! :/
I have some problems about speaker and headset with microphone.
Anyone can't hear me when I speak with speaker
And I can't talk to anyone with headphone. I hear toppy sound.
I think problems source is boomsound, how can I uninstall other extra mods?
Help me please!
I followed all the instructions but at the end my phone ended up in bootloop. How can I recover my phone now?
Please help, Thanks!
SoloTheWolf said:
I followed all the instructions but at the end my phone ended up in bootloop. How can I recover my phone now?
Please help, Thanks!
Click to expand...
Click to collapse
Well if you don't have recovery you have to flash a ftf with flashtool.
If u have recovery you can wipe amd start the process again.
Have you tried the MMbootloop
fix.zip?
nice tutorial
works 100%
SoloTheWolf said:
I followed all the instructions but at the end my phone ended up in bootloop. How can I recover my phone now?
Please help, Thanks!
Click to expand...
Click to collapse
did you flash the bootloop fix.zip? did you try to flash a recovery like the NUT`s Dualrecovery after flashing the needed files? because there is no working recovery except the one in my tutorial! try to only flash the needed files, and skip every optional step! you can try all the zips you want to install after installing the twrp recovery. this tutotial works 100%
Abdülcelil said:
I have some problems about speaker and headset with microphone.
Anyone can't hear me when I speak with speaker
And I can't talk to anyone with headphone. I hear toppy sound.
I think problems source is boomsound, how can I uninstall other extra mods?
Click to expand...
Click to collapse
hey! you installed a soundmod? then i am sorry, you have to reinstall a lollipop ftf, root it (i do it with kingsroot) and install a recovery (i prefer NUT`s dualrecovery)
then do the whole procedure again but skip all the oiptional steps with xposed and so on! dont forget to install the recovery, and use the fix if it disappears after using it for one time. after doing that, check your sound, if its not working, its 100% a hardware bug. if its working, make a full backup using the recovery, and then flash one zip file, check if sound is working, then flash another one (mabye it`s becasue of an incompatible zip!) thats why you should backup the system.
freaky2xd said:
hey! you installed a soundmod? then i am sorry, you have to reinstall a lollipop ftf, root it (i do it with kingsroot) and install a recovery (i prefer NUT`s dualrecovery)
then do the whole procedure again but skip all the oiptional steps with xposed and so on! dont forget to install the recovery, and use the fix if it disappears after using it for one time. after doing that, check your sound, if its not working, its 100% a hardware bug. if its working, make a full backup using the recovery, and then flash one zip file, check if sound is working, then flash another one (mabye it`s becasue of an incompatible zip!) thats why you should backup the system.
Click to expand...
Click to collapse
I actually don't know these things. I just like some advantages of root and wanted to see android mm. I actually don't know what should I do. If there is a video, instruction, photo etc. I follow them and do it. Could you tell me what should I do at first? If I just turn back to 5.1.1 pre rooted and do that process again, will it be fixed?
not worked
it says md5 skipping (sucessful in 1 sec). pls help sony z2
use my own tft file with your tutorial
Hello, I am still waiting for release of CE1 .570 version by Sony. After that I want to create my own pre-rooted file. Should it work with your tutorial? Any special steps needed when creating own tft file to make it work with your tutorial?
miroslav.novotny said:
Hello, I am still waiting for release of CE1 .570 version by Sony. After that I want to create my own pre-rooted file. Should it work with your tutorial? Any special steps needed when creating own tft file to make it work with your tutorial?
Click to expand...
Click to collapse
of course you can use another .570 ftf for the z2! it works the same way, all the zip files (most important the bootloopfix) do work.
but you have to use the same supersu zip file like in my flashablemm file! download it and extract the supersu zip out of the flashablemm zip using winrar you can also try the newest beta from supersu but the one i used is more likely to be safe. (NOT 2.46!!!) just use the prf creator, select your ftf, for root select the supersu zip i used, CHECK all the features (in the right upper box) like fotakernel and so on and ckeck "sign" the zip file to avoid trouble while flashing it. you are invited to press the thanks button!
SidhuZ said:
it says md5 skipping (sucessful in 1 sec). pls help sony z2
Click to expand...
Click to collapse
model= D6503 or D6502?
did you wipe cache and dalvik and made a factory reset via recovery before trying to flash the flashablemm?
of course you need to exctract all the files from "Marshmallow_D6503.zip" and then flash "FlashableMM.zip" and then the other files like me...
maybe you " checked" something like "zip file signature verification" before "swipe to confirm flash"?
try it with and without enabling the zip file signature verification.
if it still doesnt work`, redownload the file! maybe the file got broken while downloading it
miroslav.novotny said:
Any special steps needed when creating own tft file to make it work with your tutorial?
Click to expand...
Click to collapse
I just tried make my own prerooted flashable zip from US ftf and it works for me. See pic. of my settings.
Now i have [LB] D6503 .570 fw SuperSu 2.71 and twrp 3.0.2.0 after rebooting to twrp again I flashed busybox 1.24
Good luck
btw. Do you have any specific reason to wait for CE ftf. You always can disable /uninstall all bloatware with TB.
{
"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"
}
petrmelis said:
I just tried make my own prerooted flashable zip from US ftf and it works for me. See pic. of my settings.
Now i have [LB] D6503 .570 fw SuperSu 2.71 and twrp 3.0.2.0 after rebooting to twrp again I flashed busybox 1.24
Good luck
btw. Do you have any specific reason to wait for CE ftf. You always can disable /uninstall all bloatware with TB.
Click to expand...
Click to collapse
I see you used higher version of (beta) SuperSU, any reason? Or you just wanted to try and it worked?
I have no special reason waiting for CE1 .570 apart from wanting to have ROM for my region (despite the fact most of the ROM code is probably the same)
freaky2xd said:
of course you can use another .570 ftf for the z2! it works the same way, all the zip files (most important the bootloopfix) do work.
but you have to use the same supersu zip file like in my flashablemm file! download it and extract the supersu zip out of the flashablemm zip using winrar you can also try the newest beta from supersu but the one i used is more likely to be safe. (NOT 2.46!!!) just use the prf creator, select your ftf, for root select the supersu zip i used, CHECK all the features (in the right upper box) like fotakernel and so on and ckeck "sign" the zip file to avoid trouble while flashing it. you are invited to press the thanks button!
Click to expand...
Click to collapse
Thanks freaky2xd, maybe will give it a try even before the CE1 .570 release!
miroslav.novotny said:
I see you used higher version of (beta) SuperSU, any reason? Or you just wanted to try and it worked?
I have no special reason waiting for CE1 .570 apart from wanting to have ROM for my region (despite the fact most of the ROM code is probably the same)
Thanks freaky2xd, maybe will give it a try even before the CE1 .570 release!
Click to expand...
Click to collapse
I used the supersu beta because the newest "stable" version 2.46 doesn`t with Xperia´s marshmallow! but don`t panic, the beta zips are nearly as stable as the 2.46 but not finally completed for marshmallow. when the final supersu zip for marshmallow is available you can download and simply flash it on your marshmallow system if you want. I used this supersu version because I knew 100% that it will work. everything higher than the version I used will work too
petrmelis said:
....btw. Do you have any specific reason to wait for CE ftf. You always can disable /uninstall all bloatware with TB.
Click to expand...
Click to collapse
Just wanted to make sure it will be the same as I have currently.
BTW where did you get the Z2_RecRootV3_combined.zip? I can find only RecrootV4 for Z3 in some other thread....
BTW where did you get the Z2_RecRootV3_combined.zip? I can find only RecrootV4 for Z3 in some other thread....
Click to expand...
Click to collapse
I took it from here: http://forum.xda-developers.com/showpost.php?p=66534297&postcount=535
I dont know what is a different between V3 and V4 except V3 has Z2 in its name.

[Guide] Nougat with DRM fix, root and TWRP* (SGP771)

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!

[TWRP][P9+][3.1.1-1][EMUI 5.x ONLY][DECRYPTION SUPPORT]

{
"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"
}
This is only for Huawei P9 Plus (VIE)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-vie.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_vie/releases/download/3.1.1-1/twrp-3.1.1-1-vie.img"][U]download twrp-3.1.1-1-vie.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which P9+ models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Huawei P9 Plus
Contributors
OldDroid, surdu_petru, xepeleato
Version Information
Status: Stable
Created 2017-04-04
Last Updated 2017-06-11
Reserved
any working twrp for emui 4,1 with decryption support?
Thx bro
Thx for this nice work @OldDroid
This twrp works fine and root too....
VIE-L29C185 does it work?
I think model device is convenient. is it correct? I will be happy if you give me information.
goksemozkan said:
I think model device is convenient. is it correct? I will be happy if you give me information.
Click to expand...
Click to collapse
It is working good on my VIE-L29C185B360! Go ahead, use it and enjoy....
Addymore said:
It is working good on my VIE-L29C185B360! Go ahead, use it and enjoy....
Click to expand...
Click to collapse
my friend. What supersu have you uploaded, give a link.
https://forum.xda-developers.com/p9/...t3565703/page4
DL: http://filestore.to/?d=B9J55H6X9F link empty
goksemozkan said:
my friend. What supersu have you uploaded, give a link.
https://forum.xda-developers.com/p9/...t3565703/page4
DL: http://filestore.to/?d=B9J55H6X9F link empty
Click to expand...
Click to collapse
For root, I flashed this supersu for emui5....in twrp provided up! Working like a charm...! Thx to @OldDroid
Addymore said:
For root, I flashed this supersu for emui5....in twrp provided up! Working like a charm...! Thx to @OldDroid
Click to expand...
Click to collapse
Thanks to all my friends, now root and supersu are working perfectly.
And I will definitely enjoy :good::good::good:
Now, start nel custom rom
Works perfectly on VIE-L29C636 , thank you!
Thank you so much man
successfully got TWRP and root on VIE-L29C185
Good job my friend
Hi,
How can I flash twrp in emui 7? I've tryed several tutorials but I can't do it.
Best Regards
SuperTamagochi said:
How can I flash twrp in emui 7? I've tryed several tutorials but I can't do it.
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Hi guys. Sombody help me. How can i flash magisk on my p9 plus, i try many twrp, but everytime i see loop?
New release is up - TWRP 3.1.1-0 for P9 Plus.
Kernel should now support loop from b381 onwards.
Check OP for download link and github for more information!
P9 Plus Releases + Changelog
Regards
I'm sorry for the inconvenience but i forgot to exclude the special directory inside the /data partition during wipe/factory reset.
I've re-uploaded the fixed release, so everyone who had already installed 3.1.1-0 should now re-download and re-install.
Best regards
I'm sorry if this question has been asked somewhere else before, but can I flash an OTA update (extracted .zip) using TWRP, while keeping TWRP and SU?
It's quite bothersome to go back to full-stock, lock the bootloader, run the update, unlock the bootloader and root again, just for a minor update like B360 to B370.
I'm currently on B360 with TWRP 3.1.0 and SuperSU (rooted).
Rupert van da Cow said:
I'm sorry if this question has been asked somewhere else before, but can I flash an OTA update (extracted .zip) using TWRP, while keeping TWRP and SU?
It's quite bothersome to go back to full-stock, lock the bootloader, run the update, unlock the bootloader and root again, just for a minor update like B360 to B370.
I'm currently on B360 with TWRP 3.1.0 and SuperSU (rooted).
Click to expand...
Click to collapse
Hi, I can tell you in advance that NO, at least with an earlier version and that in principle it is only for normal P9.
Actually, you could only install that recovery, but with that I do not know what to tell you.
Anyway, due to the internal form of Huawei updates, they can not be installed since twrp, at least I have not been able to, nor anyone I know.
Sorry for my bad English, I do not know, and I use a translator.
Enviado desde mi VIE-L09 mediante Tapatalk

Magisk on Stock Xperia Z2 D6503 SAFETY NET PASSED

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 >_>

[Xposed][9.0]Install Xposed on Mi A2

Code:
/**
* Your warranty is now void.
*
* We are 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
**/
Need bootloader unlocked.
​
For Android 9.0(Unofficial):
Required tools:
Magisk
Riru Core(Magisk module) Download
Ed Exposed(Magisk module) Download
EdXposed Installer (Apk) Download
How to use that?
Download files from link(3 files)
Flash all "magisk modules"
Install "Ed Exposed Installer"
Reboot your device
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"
}
Tested on 10.0.7.0.
Work on Android 9.0:
- Mi A2 (Tested)
- Mi A2 lite
- MI A1
For Android 8.0(Beta):
New post:
https://forum.xda-developers.com/mi-a2/development/deodex-flax-t3864601
Required tools:
- Adb & Fastboot
- TWRP ( Download )
- Deodexed zip
Required Version Installed:
- Unlocked Bootloader
- V9.6.15.0 (October security patch)
(or you can update with this method link)
Description:
Android version: v9.6.15.0
Magisk version: v17.1
Xposed version: v90.beta3
It will not lose userdata.
Screenhost:
Download:
For V9.6.15.0
Deodex + Xposed + Magisk(V9.6.15.0)
Deodex + Xposed(V9.6.15.0)
Step 1:
Power off your device and enter fastboot mode.
Then type following code to flash temporary twrp:
Code:
fastboot flash boot twrp.img
Then held Vol+ and type following code to enter twrp
Code:
fastboot reboot
Step 2:
NO WIPE NEEDED.
Now you can flash deodexed_patch.zip
Code:
INSTALL -> Select Zip -> Flash
Step 3: (Xposed)(optional)
You can flash xposed through Twrp(find file at /sdcard, after step2)
Or you can flash xposed with Magisk Module
Code:
INSTALL -> Select Zip -> Flash
[SIZE="1"]([U]/sdcard/xposed-v90-sdk27-arm64-beta3.zip[/U])[/SIZE]
I shouldn't you to wipe dalvik-cache.
Now your can reboot, it is done!!:laugh::laugh:
(No needed re-flash boot.img)
If you have need to install some other zip,
you can flash before reboot.
FQA:
How can i flash deodex patch?
You can flash with twrp, and can flash root/noroot version.
Wiil i lose userdata?
No
Can i flash it in other version?
No
What do the zip do?
Copy deodex file into system, then install boot.img.
How can i unistall deodex patch?
For the moment, you need flash stock system.img
Click to expand...
Click to collapse
Based: V9.6.15.0.ODIMIFE
Created date: 24-10-2015
Last Modification: 25-10-2015
Created by: @Whyle
If you have other problem
https://t.me/whyle
Thanks @rovo89 @Rikka @solohsu...
reserved.
Is deodex include V9.6.15.0 (October security patch)?
Which TWRP is better?
i m in hex kernel, october patch, can i flash it?
kifdnesta said:
Is deodex include V9.6.15.0 (October security patch)?
Which TWRP is better?
Click to expand...
Click to collapse
no, it is based on V9.6.15.0
it is the last version for our Device,
V9.6.15.0 = October Patch
I'm using TingYiChen's Twrp
https://forum.xda-developers.com/mi-a2/development/recovery-unofficial-twrp-recovery-mi-a2-t3825146
Syed Shahriar said:
i m in hex kernel, october patch, can i flash it?
Click to expand...
Click to collapse
if you flashed system.img is V9.6.15.0, so you can install it.
you can reflash Hex kernel atfer flash deodexed zip
Default installed magisk parted boot.
Whyle said:
if you flashed system.img is V9.6.15.0, so you can install it.
you can reflash Hex kernel atfer flash deodexed zip
Default installed magisk parted boot.
Click to expand...
Click to collapse
just one more question, gravity box working? and if i flash the deodexed patch will i lose data?
Syed Shahriar said:
just one more question, gravity box working? and if i flash the deodexed patch will i lose data?
Click to expand...
Click to collapse
Yes, it's work DOWNLOAD XDA LINK
No, it won't lose userdata.
OMG THANKS FOR THIS! I will try ASAP. I was waiting for this for a long time haha
Thank you for your work!!
Edit: Can we use systemless xposed with magisk, since you put it on th title? I mean, is not necessary to instal xposed from recovery, right?
Edit2: Following the instructions in OP, it works like a charm!! Thank you! I flashed the TWRP, installed the zip and then, reboot system, that's all.
why use the command "fastboot flash boot_a twrp.img" ? if you are on slot b it will do nothing. and that command it's not temporary twrp. you need to change slot all time using "set active-slot AorB" using fastboot because flash twrp only works on inactive slot.
you can just use "fastboot boot twrp.img" to boot on twrp then flash zip.
bixirulo said:
OMG THANKS FOR THIS! I will try ASAP. I was waiting for this for a long time haha
Thank you for your work!!
Edit: Can we use systemless xposed with magisk, since you put it on th title? I mean, is not necessary to instal xposed from recovery, right?
Click to expand...
Click to collapse
Since your flashed zip, your system is already deodexed.
So you can install xposed at Xposed Installer or Magisk.
Hi there,
i'm sorry but where can i dload deodexed.zip and why shall i install twrp permament and not temporary???
mahalo
Neyz_ML said:
why use the command "fastboot flash boot_a twrp.img" ? if you are on slot b it will do nothing. and that command it's not temporary twrp. you need to change slot all time using "set active-slot AorB" using fastboot because flash twrp only works on inactive slot.
you can just use "fastboot boot twrp.img" to boot on twrp then flash zip.
Click to expand...
Click to collapse
because you need Twrp to flash this zip.
if you use slob_b, it can deodex olny slot_b
No need switch AoB partition
my zip include boot.img therefore twrp will be replaced.
if you are in "set active_slot b":
Code:
fastboot flash boot = fastboot flash boot_b
The reverse is the opposite
Whyle said:
because you need Twrp to flash this zip.
if you use slob_b, it can deodex olny slot_b
No need switch AoB partition
my zip include boot.img therefore twrp will be replaced.
if you are in "set active_slot b":
The reverse is the opposite
Click to expand...
Click to collapse
You don't really understand how temp twrp and a/b work. I will try to explain.
Unofficial TWRP support "boot" only.
So you can boot into TWRP without installing it, using the command "fastboot boot twrp.img"
(The phone will automatically boot TWRP on active slot, a or b, we don't care)
Then you need to decrypt data using your PIN password.
Now you are able to flash zip, like on official TWRP ... ( it will automatically install on current slot)
Reboot system and done. (TWRP is gone, because it's not install) that's it.
Whyle said:
no, it is based on V9.6.15.0
it is the last version for our Device,
V9.6.15.0 = October Patch
I'm using TingYiChen's Twrp
https://forum.xda-developers.com/mi-a2/development/recovery-unofficial-twrp-recovery-mi-a2-t3825146
Click to expand...
Click to collapse
Thank you!
Are you chinese?
yorkberliner said:
Hi there,
i'm sorry but where can i dload deodexed.zip and why shall i install twrp permament and not temporary???
mahalo
Click to expand...
Click to collapse
You can download zip in Download section.
Or https://drive.google.com/file/d/1n6Eh1b2BSpbv5YItMcmC8dcmv-J_yhUl/view?usp=drivesdk
Because our device have AB slot, so we haven't recovery partition.
kifdnesta said:
Thank you!
Are you chinese?
Click to expand...
Click to collapse
Yes, guy
Whyle said:
Yes, guy
Click to expand...
Click to collapse
Me too.
I can't update October patch because GFW.
Do you have any way?
Neyz_ML said:
you don't really understand how temp twrp and a/b work.
you can just install the zip using
fastboot boot twrp
( it will automatically boot twrp on active slot, a or b, we don't care)
then install zip ( it will automatically install on current slot) then reboot system and done. that's it.
in your guide you say to flash boot_a, but you explain nothing, for exemple my current slot is b, if I flash boot_a then reboot it will do nothing, I hope your understand that. so I think use my steps or explain is really really needed for newbies etc
Click to expand...
Click to collapse
Yes, I understand, I can write a little more.
Now deodexed patch is Fixed on A Slot, I will re-write zip.
Thank you.
kifdnesta said:
Me too.
I can't update October patch because GFW.
Do you have any way?
Click to expand...
Click to collapse
Because you device is rooted, flash stock boot.img and then you can update.

Categories

Resources