Database Users

[ROOT][5.02][XZDual Recovery][Xposed] Lollipop stock with root for WiFi SGP611 16GB

Stock lollipop and root for your device. Flash recovery and install xposed framework. Follow the instructions:
1) Backup your apps and settings
2) Make a nandroid backup
3) Download stock ftf file of Sony Xperia Z3 Tablet Compact WiFi SGP611 16GB from here: https://mega.co.nz/#!ZwoyjQbD!8J5LVBi8tH4gIv0RW503UjBYMISy9hKynL752x1W2ug
4) Create a prerooted firmware with the PRFcreator tool from this page http://forum.xda-developers.com/cro...fcreator-easily-create-pre-t2859904?nocache=1
5) Make a factory reset and flash the prerooted firmware via recovery
6) Flash XZDual Recovery from this page (version 2.8.10) http://forum.xda-developers.com/z3-tablet-compact/development/tabz3c-xzdualrecovery-qa-t3014211
7) Now from your recovery flash the zip xposed arm http://forum.xda-developers.com/showthread.php?t=3034811
8) Install xposed installer apk and done
Thanks @[NUT] , @zxz0O0 , @rovo89

Thank you worked great!
Thanks mate, I have been meaning to go back to stock to use Sky Go again.
Just flashed this via flashtool, and now I have lollipop, and I am using Sky Go again
Nice one!

Link not working

Link works for me, you have to make sure you don't take out the space in the link.

Thanks. I made prerooted zip with PRFCreator. Works like a charm.

by flashing, does it wipe the data? i.e. apps and music

Why do you first have to install a stock ftf? Why not install prerooted right away.
Update : I did not read properly. so it seems one time flashing is the case .
Sent from my SGP611 using Tapatalk

[email protected] said:
by flashing, does it wipe the data? i.e. apps and music
Click to expand...
Click to collapse
No, if You uncheck wiping in Flashtool of course.

So, just so I understand, I will end up with a Sony Z3 Compact Tablet with 5.02 LP, rooted, but with no access to recovery?
That explains my confusion then - I kept getting recovery partition errors in Flashify.

Does it require unlocked bootloader?

vonski said:
Does it require unlocked bootloader?
Click to expand...
Click to collapse
No.
BTW. To OP - please add link to RICDefeat from SGP621 thread (mounting /system r/w).

Please help me understand:
- PRFcreator will create a flashable.zip.
- the flashable.zip is a .zip and not a signed .tft; one must flash through recovery, not flashtool.
this is where I get really lost:
- In order to install any recovery (TWRP, Clock, etc), the device must be unlocked,since you cannot install recovery on locked Xperia devices (right?).
- The only way to unlock the device is to request the unlock code from Sony which voids the DRM keys, etc.
Please help me figure this out, since I want to root my SGP611, but I don't want to lose my DRM keys.

Hobbes2099 said:
Please help me understand:
- PRFcreator will create a flashable.zip.
- the flashable.zip is a .zip and not a signed .tft; one must flash through recovery, not flashtool.
this is where I get really lost:
- In order to install any recovery (TWRP, Clock, etc), the device must be unlocked,since you cannot install recovery on locked Xperia devices (right?).
- The only way to unlock the device is to request the unlock code from Sony which voids the DRM keys, etc.
Please help me figure this out, since I want to root my SGP611, but I don't want to lose my DRM keys.
Click to expand...
Click to collapse
You may want to root your device first and backup your DRM keys with giefroot and BackupTA.
http://forum.xda-developers.com/z3-...t-rooting-sgp611-giefroot-bootloader-t3017314

Thanks for your reply. Just to clarify; I will generate a .zip file with PFRCreator that can only be flashed in recovery, correct?
Forgive the noobness: can I flash a .zip file with Flashtool?

Before i had the 4.4.4 running, rooted with the giefroot-method and i also did a ta-backup.
Now i upgraded it using the mentioned way and i do still have root - but now i cant get PS4-Remoteplay to work again.
I get a errorcode which is known to say: You rooted your device and the drm-keys are gone (88001003).
so i restored my 4.4.4 ta-backup again - but it still doesnt work.
Also the proprietary Sony-Updateprog for their pre-installed xperia software is gone.
any ideas how to fix this ?

You created the backup BEFORE opening the bootloader?
Have restored the backup after getting root on the stock firmware?
You must enter the special menu contact ( *#*#7378423#*#* , service tests, security ) , all keys should be ok
I read that some have had this error (withremote play) simply by having SuperSU or superuser installed
Edit: I tried to uninstall SuperSU from the app itself (option cleaning to reinstall after from google play) and now to open remote play does not give the error 88001003. Apparently sony detects if you have the app installed

busybox
I had the stock kitkat rom, which I rooted prior to installing a prerooted lollipop rom.
I still have root access, but I do not have busybox installed and can't seem to install it.
I get the same error message using "busybox installer" and using Stephen (Stericson's) Busybox.
Any suggestions?

You may have forgotten to install ricdefeat (download SGP621-RICDefeat.zip , unzip, run install.bat)
system r/w?

kvi said:
You created the backup BEFORE opening the bootloader?
Have restored the backup after getting root on the stock firmware?
Click to expand...
Click to collapse
yes
kvi said:
Edit: I tried to uninstall SuperSU from the app itself (option cleaning to reinstall after from google play) and now to open remote play does not give the error 88001003. Apparently sony detects if you have the app installed
Click to expand...
Click to collapse
Strange - i'm pretty sure it worked on 4.4.4 while i had superSU installed.

I read here https://talk.sonymobile.com/t5/Xperia-Z3-Z3-Dual/error-88001003-remote-play/td-p/873247

Sony.Z2.D6503.PreRooted.Customized.AU.1281-9715.23.5.A.1.291 (Root+Recovery)(LB/UB)

Info :
Greetings and Welcome. Here's the latest firmware update for Sony Z2(D6503) Build23.5.A.1.291_R4D with (Recovery + Root)
Enjoy!
How To Flash :
Method 1 Clean Flash :
1. Download Prerooted Rom + Bootloop Fix and place them on ur device storage,
2. Reboot to Recovery,
3. Do A Full Wipe Except the storage partition where u put Prerooted Rom + Bootloop Fix,
4. Flash Prerooted Rom and then Bootloop Fix
5. Reboot.
Method 2 Dirty Flash Over Previous Build Of Android MM :
1. Download Prerooted Rom + Bootloop Fix and place them on ur device storage,
2. Reboot to Recovery,
3. Flash Prerooted Rom and then Bootloop Fix,
4. Wipe Cache And Dalvik/Art
5. Reboot.
6. After Finishing booting process wait a few mins,
7. Now go to app drawer and check if supersu is there or not, If not then simply download it from google play store and install it and open it and select SU Binary install normal & Click Reboot,
8. Enjoy!
Stuff Used to Create This Pre-rooted Room :
D6503_Customized AU_1281-9715_23.5.A.1.291_R4D
PRFCreator_v1.3
UPDATE-SuperSU-v2.76-SYSTEMMODE
RecRootV4_combined
My Dell Laptop,
A Keyboard + Mouse,
My Experiences With This Build Of Android MM :
Now We can transfer apps to "EXTSDCARD" using "Transfer data to SD card"
STAMINA mode is back
Multi Tasking Is better than Previous Build Of Course XD
Significantly faster & smoother than previous build (23.5.A.0.575)
Screen Recording Error still exist
Anything Else? :good:
Download Links :
Rom : Click On ME
Bootloop Fix : Click On ME
Screenshots :
http://imgur.com/a/i7icA
Instead of Typing Thanks, You can simply press on it :good:, Try not to spam this thread, If u have any Question regarding my upload Ask here.

First Comment
Keep Up Bro (Y)

Thank you. ?

Thanks!

I'll try to build the same file but for Customized FR (my country) !

Why bootloop fix from 570 build need to flashed too ?
Sent from my D6503 using Tapatalk

itsnie said:
Why bootloop fix from 570 build need to flashed too ?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Because that's a life saver for Z2 with Prerooted rom. That's the only bootloop fix exist here on xda for now. Can you try flashing without it at see if it boots? And report back here! Unless u wanna waste some times on re-flashing LP rom and rooting it again to get back on a rooted mm rom

Will previous D6502 patches work?

RICdefeat & byeselinux
Have you used byeselinux & RICdefeat in the firm compilation??
Or only the bootloopfix?
Thank you

supercfc said:
Will previous D6502 patches work?
Click to expand...
Click to collapse
Can't say since I don't have a D6502 Model. Try and let me know if it works

LunaFree said:
Have you used byeselinux & RICdefeat in the firm compilation??
Or only the bootloopfix?
Thank you
Click to expand...
Click to collapse
"RecRootV4_combined" Include all of those stuff as well as recovery

@op
Will dummy_flashable.zip works as well making the ZIP? im on .575 with root and recovery. i have already downloaded the ftf before seeing this post

Thank you so much!!!!

So I finally made the same thing for the french firmware !
https://www.wetransfer.com/downloads/9d69b9f8a30da16970abc3f5655fa01720160804144653/d99f41

Dilesh Perera said:
@op
Will dummy_flashable.zip works as well making the ZIP? im on .575 with root and recovery. i have already downloaded the ftf before seeing this post
Click to expand...
Click to collapse
As I already said "RecRootV4_combined" Includes Root + Recovery. So u don't need anything else. Except Bootloop Fix

rakeshbro said:
"RecRootV4_combined" Include all of those stuff as well as recovery
Click to expand...
Click to collapse
I've do my compilation with 23.5.A.1.291 firmware using the ITALIAN customized and SUPERSU with PRF creator.
I've install busybox from appstore and DUAL recovery with the install.bat from pc and then in RECOVERY MODE i´ve flashed byeselinux+RICdefeat without bootloopfix, and works too!!
Thank you Rakeshbro!! :good::good:

LunaFree said:
I've do my compilation with 23.5.A.1.291 firmware using the ITALIAN customized and SUPERSU with PRF creator.
I've install busybox from appstore and DUAL recovery with the install.bat from pc and then in RECOVERY MODE i´ve flashed byeselinux+RICdefeat without bootloopfix, and works too!!
Thank you Rakeshbro!! :good::good:
Click to expand...
Click to collapse
Yeah I saw some feedback on "23.5.A.0.575" build as well that some ppl didn't flashed bootloop fix and they got it boot.
But for me I'd to flash bootloop fix to get into os. I remember Last time when I was on MM build "23.5.A.0.570_R4D" I've like 350+ apps installed on my z2 and after a few weeks later Build "23.5.A.0.575" came out. And guess what I've flashed it without the bootloops fix and that's it, I got stucked on lockscreen and whenever I unlock my device it just reboot again & again, And I can't even boot to recovery. With a broken heart I've to flash LP rom again and root it and then flash the latest MM build. I just did't want to take that risk again this time, since I've now more than 360+ apps installed on my Z2. So It's upto All of u guys. U want to flash the old bootloop fix or not. Try and let us know Good Luck!

Yeah you need bootloop fix. The same thing happened to me but I just pressed volume button during the bootloop, I entered TWRP, connected to USB, copied bootloop fix and flashed it without reinstalling everything

rakeshbro said:
Yeah I saw some feedback on "23.5.A.0.575" build as well that some ppl didn't flashed bootloop fix and they got it boot.
But for me I'd to flash bootloop fix to get into os. I remember Last time when I was on MM build "23.5.A.0.570_R4D" I've like 350+ apps installed on my z2 and after a few weeks later Build "23.5.A.0.575" came out. And guess what I've flashed it without the bootloops fix and that's it, I got stucked on lockscreen and whenever I unlock my device it just reboot again & again, And I can't even boot to recovery. With a broken heart I've to flash LP rom again and root it and then flash the latest MM build. I just did't want to take that risk again this time, since I've now more than 360+ apps installed on my Z2. So It's upto All of u guys. U want to flash the old bootloop fix or not. Try and let us know Good Luck!
Click to expand...
Click to collapse
I think we have do the same, but i dont use the bootloop fix...
I will flash recroot v4 next time without bootloop fix and i tell you. Thank you!!

Thanks for your work
flashing without a probleme

ROOTED STOCK KERNELS 1APRIL2017- 32.3.A.2.33 (E6833 E6853 E6883)+ twrp

UPDATE 1-APRIL-2017
I am updating repository for stock modified kernels+twrp3.02 installed for 32.3.A.2.33
https://mega.nz/#F!7VwRCaLQ!GNKLGiggp_TebbBRO1QSug
32.3.A.2.33 for all variants (E6833 E6853 E6883) + twrp Installed
I have used following configuration
Code:
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 7.0
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y
Disabling dm-verity
- Sony RIC is enabled. Disable? [Y/n] Y
Disabling Sony RIC
- Install TWRP recovery? [Y/n] Y
Installing TWRP
Compressing TWRP image
- Found superuser.zip. Install? [Y/n] N
- Install DRM fix? [Y/n] Y
- Install busybox? [Y/n] N
- Creating new initramfs
- Creating boot image
- Cleaning up
-----------------------------------------------------------------------------------------------
I have been asked to SIMPLY state down Root method for
- Xperia z5p on 32.3.A.0.376 Android N- all three variants (E6833 E6853 E6883)
- Xperia z5p on 32.3.A.0.378 Android N - E6853 ( NOBA) (EU)
Prerequisites
1. you are running 32.3.A.0.376 and usb debugging from developer options is ON. IF YOU DON"T KNOW HOW TO ENABLE USB DEBUGGING then THIS POST IS NOT FOR YOU. PLEASE READ POSTS (referenced below) TO UNDERSTAND FLASHING TECHNIQUES
2 unlocked boot loader
3. if DRM KEYS / TA.img you have manage to extract some how then read below post having details to restore
Reference
all kernels are modified using kit by @tobias.waldvogel , 5.21 / 5.22 and E6883 by 5.23
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
https://forum.xda-developers.com/z5...ting-xperia-z5-z5p-variants-drm-keys-t3437902
METHOD
please download
1. 32.3.A.0.376_E68XX.img of your variant
2. superuser-r259 (put it in sdcard)
2a. phh_SuperUser_v1.0.3.3.apk (put it in sdcard)
3. if you want to use SUPERSU then skip 2 and 2a then download UPDATE-SuperSU-v2.79-20161211114519.zip and put it in sdcard
4. flash the KERNEL , reboot into recovery
5 flash superuser-r259 OR superSU
5a. reboot mobile and and install superuser.apk
6. if you had flashed superSU then skip "5a"
repository https://mega.nz/#F!3FYhTbSC!9MraM-zYNRNMPzmTkSSs9g
MAKE /SYSTEM WRITABLE
in order to remove system apps and install ADAWAY
from playstore
1. install busybox, open, grant it root access, INSTALL
2. install terminal for android, open and
type these lines and enter one by one in terminal
Code:
Code:
su
mount -o rw,remount /system
DONE
Code:
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y
- Sony RIC is enabled. Disable? [Y/n] Y
- Install TWRP recovery? [Y/n] Y
- Install kcal kernel module? [Y/n] N
- Install DRM fix? [Y/n] Y
- Install busybox? [Y/n] N
thanking members for providing kernels @ytheekshana @luongvancanh , @ayhanornek , @atif_afzal , @ayhanornek

Thank you, it was simpler.

thanks great work. keep this

Great

Thank you for your instructions!
I have some questions in order to make clear some issues:
1) I am at 32.2.A.0.253 rooted by your method in the other post. Should I update to Nougat first and then do this process?
2) What about the DRM keys? Were they lost? Were they "imaged"? Will they be lost now with this process?

konstantinos3 said:
Thank you for your instructions!
I have some questions in order to make clear some issues:
1) I am at 32.2.A.0.253 rooted by your method in the other post. Should I update to Nougat first and then do this process?
2) What about the DRM keys? Were they lost? Were they "imaged"? Will they be lost now with this process?
Click to expand...
Click to collapse
sir
you are on oct2016 version of MM, .305 came in december16, .372 in jan17 and now inf feb .376 is the latest one.
1. YES you MUST upgrade to 32.3.A.0.376 to do the process explained above. (i.e. if you want to upgrade)
2. I am assuming that your BOOTLOADER is LOCKED and you NEVER send your imei keys to SONY asking for BOOTUNLOCKER code.
if yes then
- your DRM KEYS are intact. and you cannot ROOT it and the process above is NOT for you.
- in order to have root access, you must first research and find tools such as dirty cow script in order to EXTRACT drm KEYS -- OR downgrade to android 5.1.1 (Dec 2015 stockrom of Z5x) and use Ivory ROOT or KINGROOT to gain root access and EXTRACT DRMKEYS.
- at this point if you simply unlock your bootloader, your DRM KEYS and TA img will be wiped.

YasuHamed said:
sir
you are on oct2016 version of MM, .305 came in december16, .372 in jan17 and now inf feb .376 is the latest one.
1. YES you MUST upgrade to 32.3.A.0.376 to do the process explained above. (i.e. if you want to upgrade)
2. I am assuming that your BOOTLOADER is LOCKED and you NEVER send your imei keys to SONY asking for BOOTUNLOCKER code.
if yes then
- your DRM KEYS are intact. and you cannot ROOT it and the process above is NOT for you.
- in order to have root access, you must first research and find tools such as dirty cow script in order to EXTRACT drm KEYS -- OR downgrade to android 5.1.1 (Dec 2015 stockrom of Z5x) and use Ivory ROOT or KINGROOT to gain root access and EXTRACT DRMKEYS.
- at this point if you simply unlock your bootloader, your DRM KEYS and TA img will be wiped.
Click to expand...
Click to collapse
Thank you for your immediate answer.
In my post above, I wrote that I have my device rooted following your initial method, in which unlocking the bootloader is necessary, so my BL is certainly unlocked.
After rooting, I hadn't restored DRM keys, because the kernel has simulation.
So the question remains: what shall I do now about the DRM keys during this process?
Thank you very much in advance

konstantinos3 said:
Thank you for your immediate answer.
In my post above, I wrote that I have my device rooted following your initial method, in which unlocking the bootloader is necessary, so my BL is certainly unlocked.
After rooting, I hadn't restored DRM keys, because the kernel has simulation.
So the question remains: what shall I do now about the DRM keys during this process?
Thank you very much in advance
Click to expand...
Click to collapse
Sir
i am sorry i overlooked the part you mentioning your Root / UB status.
the answer is NO its not necessary! since the modified kernels have DRM FIX, it should work just fine.
please upgrade to .376 and flash your kernel, install superuser or superSU.
later to give /system RW access, please follow the codes to be run in TERMINAL for ANDROID app.

YasuHamed said:
I have been asked to SIMPLY state down Root method for
- Xperia z5p update on 32.3.A.0.376 Android N
I have patched kernels and all three variants (e6833 e6853 e6883)
Prerequisites
1. you are running 32.3.A.0.376 and usb debugging from developer options is ON. IF YOU DON"T KNOW HOW TO ENABLE USB DEBUGGING then THIS POST IS NOT FOR YOU. PLEASE READ POSTS (referenced below) TO UNDERSTAND FLASHING TECHNIQUES
2 unlocked boot loader
3. if DRM KEYS / TA.img you have manage to extract some how then read below post having details to restore
Reference
all kernels are modified using kit by @tobias.waldvogel , 5.21 / 5.22 and E6883 by 5.23
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
https://forum.xda-developers.com/z5...ting-xperia-z5-z5p-variants-drm-keys-t3437902
METHOD
please download
1. 32.3.A.0.376_E68XX.img of your variant
2. superuser-r259 (put it in sdcard)
2a. phh_SuperUser_v1.0.3.3.apk (put it in sdcard)
3. if you want to use SUPERSU then skip 2 and 2a then download UPDATE-SuperSU-v2.79-20161211114519.zip and put it in sdcard
4. flash the KERNEL , reboot into recovery
5 flash superuser-r259 OR superSU
5a. reboot mobile and and install superuser.apk
6. if you had flashed superSU then skip "5a"
repository https://mega.nz/#F!3FYhTbSC!9MraM-zYNRNMPzmTkSSs9g
MAKE /SYSTEM WRITABLE
in order to remove system apps and install ADAWAY
from playstore
1. install busybox, open, grant it root access, INSTALL
2. install terminal for android, open and
type these lines and enter one by one in terminal
Code:
Code:
su
mount -o rw,remount /system
DONE
thanking members for providing kernels @ytheekshana @luongvancanh , @ayhanornek , @atif_afzal , @ayhanornek
Click to expand...
Click to collapse
Thanks for your help.
I have just flash 32.3.A.0.376_E6883.img, ok.
But It cannot into recovery mode (I press power+vol down button when restart phone)
I don't kown the file 32.3.A.0.376_E6883.img included recovery or not yet!
Please help me: Do I need flash recovery files? And where link can I download recovery files?
Thanks for next help.

You need to install drmky after you are root.

luongvancanh said:
Thanks for your help.
I have just flash 32.3.A.0.376_E6883.img, ok.
But It cannot into recovery mode (I press power+vol down button when restart phone)
I don't kown the file 32.3.A.0.376_E6883.img included recovery or not yet!
Please help me: Do I need flash recovery files? And where link can I download recovery files?
Thanks for next help.
Click to expand...
Click to collapse
just press power button,
on sony logo, press volume up / down and as LED turns AMBER, you will be taken to twrp

YasuHamed said:
I have been asked to SIMPLY state down Root method for
- Xperia z5p update on 32.3.A.0.376 Android N
I have patched kernels and all three variants (e6833 e6853 e6883)
Prerequisites
1. you are running 32.3.A.0.376 and usb debugging from developer options is ON. IF YOU DON"T KNOW HOW TO ENABLE USB DEBUGGING then THIS POST IS NOT FOR YOU. PLEASE READ POSTS (referenced below) TO UNDERSTAND FLASHING TECHNIQUES
2 unlocked boot loader
3. if DRM KEYS / TA.img you have manage to extract some how then read below post having details to restore
Reference
all kernels are modified using kit by @tobias.waldvogel , 5.21 / 5.22 and E6883 by 5.23
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
https://forum.xda-developers.com/z5...ting-xperia-z5-z5p-variants-drm-keys-t3437902
METHOD
please download
1. 32.3.A.0.376_E68XX.img of your variant
2. superuser-r259 (put it in sdcard)
2a. phh_SuperUser_v1.0.3.3.apk (put it in sdcard)
3. if you want to use SUPERSU then skip 2 and 2a then download UPDATE-SuperSU-v2.79-20161211114519.zip and put it in sdcard
4. flash the KERNEL , reboot into recovery
5 flash superuser-r259 OR superSU
5a. reboot mobile and and install superuser.apk
6. if you had flashed superSU then skip "5a"
repository https://mega.nz/#F!3FYhTbSC!9MraM-zYNRNMPzmTkSSs9g
MAKE /SYSTEM WRITABLE
in order to remove system apps and install ADAWAY
from playstore
1. install busybox, open, grant it root access, INSTALL
2. install terminal for android, open and
type these lines and enter one by one in terminal
Code:
DONE
thanking members for providing kernels @[email protected] , @ayhanornek , @atif_afzal , @ayhanornek
Click to expand...
Click to collapse
You might want to replace phh superuser with Magisk, I think it's been deprecated (at least topjohnwu's fork has been merged directly into Magisk)

exvargos said:
You might want to replace phh superuser with Magisk, I think it's been deprecated (at least topjohnwu's fork has been merged directly into Magisk)
Click to expand...
Click to collapse
I will try and let you know, so far the superuser support was only given because superSU having problems with battery drainage and reading sdcard in some cases

Thank you,
I work, does anyone know where the terminal on busybox?

Can u suggest me which busybox to instal? So many busybox on playstore..

kendork said:
Thank you,
I work, does anyone know where the terminal on busybox?
Click to expand...
Click to collapse
Terminal is another apk.. Not on busybox..

YasuHamed said:
just press power button,
on sony logo, press volume up / down and as LED turns AMBER, you will be taken to twrp[/QUOTE
Thank for YasuHamed, press volume up will be taken to twrp. We can not use volume down.
Click to expand...
Click to collapse

luongvancanh said:
YasuHamed said:
just press power button,
on sony logo, press volume up / down and as LED turns AMBER, you will be taken to twrp[/QUOTE
Thank for YasuHamed, press volume up will be taken to twrp. We can not use volume down.
Click to expand...
Click to collapse
i will keep that in mind
thank you
Click to expand...
Click to collapse

kendork said:
Thank you,
I work, does anyone know where the terminal on busybox?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=stericson.busybox

here terminal. https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=tr
This program should come to the device originally because android linux already, but unfortunately they do not install.

Help me to twrp/root/xposed/kernel my XC

Hi,
I'll received my XC this week, and I'd like to root it.
I don't want a custom ROM, but just a stock one with xposed and remove some bloatwares.
Here are my needs:
keep DRM
latest stock rom
twrp
untouched system partition
easy OTA
XC Genesis kernel
xposed + module
Do you think it possible to achieve such a configuration?
How-to?
Thanks
EDIT: I'll update this post to make it an HOW-To for futures users with same questions.

Assuming you're unable to unlock your BL the steps are as follows...
Flash back to 198.
Backup your TA.
Unlock your BL
Update to 311
Extract kernel - ftf/sin/elf
Run elf through Rootkernel_v5.23 - (In cmd prompt window - rootkernel kernel.elf boot.img)
Create DK ftf with Rootkernel_v5.23 (In cmd prompt window - flash_dk TA-19022017.img DK.ftf)
Flash new boot.img
Flash TWRP.img
Flash Super User zip
Flash DK.ftf with Flashtool 9.22
...and that should be it.

Latest stock Rom + xposed will not be possible...

mika91 said:
Hi,
I'll received my XC this week, and I'd like to root it.
I don't want a custom ROM, but just a stock one with xposed and remove some bloatwares.
Here are my needs:
keep DRM
latest stock rom
twrp
untouched system partition
easy OTA
XC Genesis kernel
xposed + module
Do you think it possible to achieve such a configuration?
How-to?
Thanks
EDIT: I'll update this post to make it an HOW-To for futures users with same questions.
Click to expand...
Click to collapse
Forget about OTA when rooted...

I though that using xposed leave the system partition untouched, so OTA updates are possible...

mika91 said:
I though that using xposed leave the system partition untouched, so OTA updates are possible...
Click to expand...
Click to collapse
OTA is not possible once bootloader is unlocked. System partition touched or not played no role.

ok.
So if I want root the XC, I have to unlock the bootloader, loose DRM and ota?
How is the camera quality without the drm keys?
Thanks

mika91 said:
ok.
So if I want root the XC, I have to unlock the bootloader, loose DRM and ota?
Click to expand...
Click to collapse
See my post to get a rooted stock with DRM.

mika91 said:
ok.
So if I want root the XC, I have to unlock the bootloader, loose DRM and ota?
How is the camera quality without the drm keys?
Thanks
Click to expand...
Click to collapse
You HAVE to unlock. There is NO root on LOCKED bootloader.
Unlocking bootloader deletes TA partition, containing DRM keys. You should BACKUP your TA partition BEFORE unlocking using DirtyCow Backup tool from Sony Cross Devices forum.
After unlocking, you can either flash kernel that supports DRM patching either by using fake DRM libraries, or your real DRM keys, either flashed in alternative location (see RootKernel tool in Z5 forums, works on almost all modern Xperias) or PoC TA tool from Sony Cross devices, that mounts your TA backup as TA partition, therefore your phone looks as having DRM keys and locked.

XperienceD said:
Assuming you're unable to unlock your BL the steps are as follows...
Flash back to 198.
Backup your TA.
[*]Unlock your BL
[*]Update to 311
[*]Extract kernel - ftf/sin/elf
[*]Run elf through Rootkernel_v5.23 - (In cmd prompt window - rootkernel kernel.elf boot.img)
[*]Create DK ftf with Rootkernel_v5.23 (In cmd prompt window - flash_dk TA-19022017.img DK.ftf)
[*]Flash new boot.img
[*]Flash TWRP.img
[*]Flash Super User zip
[*]Flash DK.ftf with Flashtool 9.22
...and that should be it.
Click to expand...
Click to collapse
Would you mind detailing a bit more those steps, especially the first 2? Im coming from a really old phone so im still a bit lost. (where can i learn about ftf/sin/elf?)
How can we flash back to 198? Flashing doesnt require an unlocked BL, wich to be achieved deletes your TA?
im on a brand new X Compact, 7.0 (34.2.A.0.292), secure patch 01/01/17
managed to get flashtool, adb/fastboot and Universal TA Backup v2 on my pc but no dice on TA backup yet

fredsky2 said:
Would you mind detailing a bit more those steps, especially the first 2? Im coming from a really old phone so im still a bit lost. (where can i learn about ftf/sin/elf?)
Click to expand...
Click to collapse
Sure. You don't really need to learn about those stuff but is handy to know, you'll pick stuff up along the way. They are basically firmware files.
fredsky2 said:
How can we flash back to 198? Flashing doesnt require an unlocked BL, wich to be achieved deletes your TA?
Click to expand...
Click to collapse
Open the flashtool and run Xperifirm (icon with XI) on it, then browse to the XC, then click on F5321 and it will load up the different regions and available firmware. If you click on "check all" it will then show which FW is available to download, Central Europe 5 still shows as 198, so you need to select it on the right of the screen under the picture of the phone, it will then download and it's simply a matter of following the instructions to flash it.
fredsky2 said:
im on a brand new X Compact, 7.0 (34.2.A.0.292), secure patch 01/01/17
managed to get flashtool, adb/fastboot and Universal TA Backup v2 on my pc but no dice on TA backup yet
Click to expand...
Click to collapse
When you get 198 on your phone then you'll be able to back your TA. If you get stuck give us a shout.

XperienceD said:
Sure. You don't really need to learn about those stuff but is handy to know, you'll pick stuff up along the way. They are basically firmware files.
Open the flashtool and run Xperifirm (icon with XI) on it, then browse to the XC, then click on F5321 and it will load up the different regions and available firmware. If you click on "check all" it will then show which FW is available to download, Central Europe 5 still shows as 198, so you need to select it on the right of the screen under the picture of the phone, it will then download and it's simply a matter of following the instructions to flash it.
When you get 198 on your phone then you'll be able to back your TA. If you get stuck give us a shout.
Click to expand...
Click to collapse
Thank you, i was able to successfully backup my TA earlier yesterday. But now im struggling with how to restore it in MM 6.0.1 (34.1.A.1.198).
I've read that i'll need a custom kernel for that (and to get TWRP+supersu+magisk+xposed) but im unsure if i should use Genesis (probably unsuported but the only one that says it'll restore MY TA) or Advanced Stock Kernel from Androplus. Ive read that messing with TA can hardbrick my phone so im trying to be extra careful.
atm im following ondrejvaroscak's quickrecap to make sure everything goes smooth with my TA keys and then i plan to downgrade to 6.0, install Advanced Stock Kernel, supersu 2.79 and magisk and then pray for the best (without reflashing my own DK.ftf?)

fredsky2 said:
Thank you, i was able to successfully backup my TA earlier yesterday. But now im struggling with how to restore it in MM 6.0.1 (34.1.A.1.198).
Click to expand...
Click to collapse
Download Flashtool 9.22.3 and flash your DK.ftf, flashing with a newer version doesn't work, you should then be able to verify it's worked in the service menu.
fredsky2 said:
I've read that i'll need a custom kernel for that (and to get TWRP+supersu+magisk+xposed) but im unsure if i should use Genesis (probably unsuported but the only one that says it'll restore MY TA) or Advanced Stock Kernel from Androplus. Ive read that messing with TA can hardbrick my phone so im trying to be extra careful.
Click to expand...
Click to collapse
You can use the RootKernel tool to modify your own kernel, extract the kernel.sin from the ftf with a zip program, then use the flashtool to extract the kernel.elf, Tools-Sin Editor-Extract Data then run it through the RootKernel tool and flash the boot.img it creates, then flash TWRP separately to the recovery partition which will allow you then to flash SuperSU.
SuperSU and BusyBox are the only options I didn't include when creating my kernel. Others will have to help with the other two things you want as I refuse to use them.

XperienceD said:
Download Flashtool 9.22.3 and flash your DK.ftf, flashing with a newer version doesn't work, you should then be able to verify it's worked in the service menu.
You can use the RootKernel tool to modify your own kernel, extract the kernel.sin from the ftf with a zip program, then use the flashtool to extract the kernel.elf, Tools-Sin Editor-Extract Data then run it through the RootKernel tool and flash the boot.img it creates, then flash TWRP separately to the recovery partition which will allow you then to flash SuperSU.
SuperSU and BusyBox are the only options I didn't include when creating my kernel. Others will have to help with the other two things you want as I refuse to use them.
Click to expand...
Click to collapse
Thanks again. I was worried that the drm-fix from the kernel editing tool could corrupt my TA partition but thankfully i was wrong on that .
Im now at MM 6.0, original DRM keys, TWRP, xposed, rooted with magisk and im almost sure that with busybox. Why do you refuse to use them? Just curious!
Thanks a lot for your help, cheers

fredsky2 said:
Thanks again. I was worried that the drm-fix from the kernel editing tool could corrupt my TA partition but thankfully i was wrong on that .
Click to expand...
Click to collapse
I flashed a kernel I made with the Rootkernel tool without the drm fix but it showed some mumbo jumbo where it should say ok and provisioned, included the drm fix in the next one and it worked fine then.
fredsky2 said:
Im now at MM 6.0, original DRM keys, TWRP, xposed, rooted with magisk and im almost sure that with busybox. Why do you refuse to use them? Just curious!
Thanks a lot for your help, cheers
Click to expand...
Click to collapse
You're welcome. I refuse because I prefer to know how to mod apks directly and I found Xposed to be quite buggy. I can see the benefits, it's just not for me.

NEW KERNEL /FIX FOR BOOTLOOP/Magisk installation in nougat z3+/z4

NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootlooped​credits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
in cmd window :fastboot flash boot new_kernel.img
IMP:steps 1 & 2 are can also be used when u have met with an unexpected bootloop/restart problem at any time( if u don't want to flash the complete stock ftf,this boot image will help u in letting ur device come out of bootloop.
3.proceeding to our main thread....now boot into recovery & flash "magisk.zip"
4.wipe cache & dalvik.and reboot.
PROPERTIES OF THE KERNEL (new_kernel.img:---
Build 32.4.A.1.54
1. Sony RIC- disabled.
2. DM-Verity- disabled.
3. TWRP- disabled.
4. DRM Fix- enabled.
5. Superuser / root- Not present. ( flash magisk its better)
6. Busybox- Not present
7.many more tweaks to reduce heat & increase battery backup
LINK TO THE CONTENT
https://drive.google.com/drive/folders/1ic9zsMi576s1P9H6s1z4_g0ofSJJktIs?usp=sharing

I just want stock rooted rom with magiks
doctorsworld99 said:
NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootlooped​credits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
Click to expand...
Click to collapse
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp

Sumantomar1709 said:
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp
Click to expand...
Click to collapse
u can try flashing magisk over stock.but whenever i did that my device used to go into bootloop.thats why i've to experiment with different twrps,kernels to detect the culprit.
finally i got this awesome kernel which helped me to come out of bootloops everytime.so i will suggest to use this [near to stock ] kernel .
but u can try flashing magisk over stock.....if anything goes wrong ,,,just flash the new_kernel,,and ua fine to go with magisk.

Thnx. I will try & let u know.

thank u sirThis kernel help me from bootloop .how did u make this kernel

Champsingh909 said:
thank u sirThis kernel help me from bootloop .how did u make this kernel
Click to expand...
Click to collapse
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime

This kernel really working in bootloop.thnx

doctorsworld99 said:
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime
Click to expand...
Click to collapse
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot

Champsingh909 said:
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot
Click to expand...
Click to collapse
creating a separate thread isn't a good idea ,i'll update the details of the kernel in this thread itself,plz give me some time.

Kernel properties added.

Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.

LoaderFabi said:
Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.
Click to expand...
Click to collapse
i got frequent bootloops on installing it over stock kernel and also over m-rom .i think the kernel was the culprit.

Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?

chrnodroid said:
Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?
Click to expand...
Click to collapse
Hopefully yes,flash it as instructed.best of luck:good:

Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.

MrHands0m3 said:
Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.
Click to expand...
Click to collapse
confirmed!! this kernel is the ****!.. try it... (don't blame me if you brick your device)

The link to download the kernel won't work anymore, is there a mirror?