Database Users

[LB] Create ROOTED update package from stock FTF (Windows)

With the latest firmwares not directly rootable you need to download or create an update package with root and recovery and update your system via recovery. This won't delete your data and root will be there on 5.x.x. I made this complete tutorial so that everyone can make an update from an FTF file.
THIS IS FOR LOCKED BOOTLOADER and/or STOCK KERNEL ONLY !!!
MAKE SURE YOU HAVE A BACKUP !!!​
1.1 You need obviously an already rooted phone with [NUT]'s DualRecovery installed and working (this can be achieved on firmwares with Android 4.4 and 5.0.2)
If you don't have the recovery, you can install it from here: [Z2][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A see post #2 there for instructions. 2.8.12 and later should work on KitKat and Lollipop too!
1.2 You need Flashtool with working USB drivers (Make sure flashmode works - which means the drivers are properly installed on your system, especially on Windows 8/8.1/10 - before you start this tutorial).
2. Download the newest FTF update file for your phone/branding. Use the same customization version (xxxx-xxxx) that is on your phone now!
This you can do with Flashtool (Devices/Check Updates menu) or download it from the [FTF] STOCK FIRMWARES for Xperia Z2 thread.
(Alternative option for advanced users: XperiFirm -> you can create an FTF from the downloaded firmware files with Flashtool.)
3.1 Download PRFCreator v1.1.zip from [TOOL] PRFCreator - easily create pre-rooted firmwares.
3.2 Download latest stable SuperSU update package from here.
3.3 Download XZDualRecovery's latest - 2.8.23 - flashable version (Z2-lockeddualrecovery2.8.xx-RELEASE.combined.zip) from here (XZDualRecovery section).
You will have 5 files so far:
PRFCreator v0.5.zip
D650x_23.x.1.A.x.xxx.ftf (with different name and firmware version number)
UPDATE-SuperSU-v2.46.zip
Z2-lockeddualrecovery2.8.x-RELEASE.flashable.zip
Click to expand...
Click to collapse
4. Unzip PRFCreator and run it.
5. Load the FTF, SuperSU and Z2-lockeddualrecovery (flashable) zip files into the three section.
6. Uncheck all the Include options [ ], we don't need them, we will flash them with Flashtool after the update. I think it's still safer to flash kernel, baseband, boot and other system critical parts of the firmware from Flashtool.
(But if you want to include them anyway then you can skip part 11 and start your phone normally.)
There is a Legacy mode option in the latest version. Without it PRFCreator will use a direct sin flashing method for system update. If you check the legacy option it will use the older repack method for system. The direct sin flashing should work in most cases if not then use the legacy option.
7. Push Create. After it's finished (wait for the Create button to be available again), you'll find a flashable.zip in the folder of PRFCreator.
Check the contents of the zip file, it should look like this with PRFCreator v0.5:
Code:
data
META-INF
system
utils
partition-image.sin
system.sin
dualrecovery.zip
SuperSU.zip
If something is missing, redo the process from step #4 until all is there.
8. Copy flashable.zip to the internal/external SD card of your phone. If you want to go for 100% working root and recovery copy UPDATE-SuperSU-v2.46.zip and Z2-lockeddualrecovery2.8.x-RELEASE.flashable.zip there too.
9. Boot your phone into recovery (use TWRP!).
10. Install flashable.zip in recovery. After finished DO NOT REBOOT !!!
*Optional step: install SuperSU and Recovery again so if something went wrong during the system flashing you'll still have a working recovery.
Clear Cache/Dalvik only and go back to Home and choose Reboot/Power off.
11. Start Flashtool and with the Flash device icon flash the kernel and other baseband files from the FTF in Flashmode.
Use the following configuration (or similar):
Wipe:
Code:
[ ] APPSLOG
[ ] CACHE
[ ] DATA
Which means nothing is wiped, this is good for a system update only, that reserves your settings, applications and data. (If you want a clean system or run into errors after updating only the system, you can wipe all the three.)
Exclude:
Code:
[ ] BOOTBUNDLE
[x] PARTITION
[ ] KERNEL
[ ] FOTA
[ ] BASEBAND
[x] SYSTEM
[ ] ELABEL
Which means system, partition and ta options are unchanged and won't be wiped/overwritten. You can exclude fota, elabel and baseband too, but some phone functions may be limited. Always use your phone's original customization version when choosing FTFs. Never exclude = never check (x) kernel. It is the main reason we're flashing this.
TA -> not always present in the FTF file, but if you see it, then EXCLUDE it, just to be sure, you don't simlock your device
Code:
[x] No final verification
[ ] Reset customization
Connect the micro USB to your phone and get ready with the other end of the cable in your hand
Push Flash button.
Push the Volume down button and connect the USB cable to the computer's USB port. Wait until Flashtool begins with the flashing and you can release the Volume button now.
When finished, unplug the the phone, start it and wait until it completes the first boot. After it is fully working, check SuperSU and if you can mount system R/W too (in Root Explorer or in other root file manager).
ENJOY another rooted version of Android I can give support only for this process, for the tools you need to ask your questions in the appropriate threads above.
Thanks to @zxz0O0 for creating the PRFCreator and the Lollipop fixes, it makes things easier in this process (you don't need to mess with linux mounts, virtual machines and other scripts copying system images and recovery updates to a zip).

hi
I look forward to your work to install on my z2
:good:

Nice guide. Please let me know the bugs in PRFCreator v0.6 (you can drop me a pm as I don't have a lot of time for xda at the moment). Also, is step 12 really necessary? Dualrecovery should already be included in the flashable zip (same for step 11 if you include those files).

Will downgrading 4.4.4 to 4.4.2 without wiping data cause a bootloop?

ravdo said:
Will downgrading 4.4.4 to 4.4.2 without wiping data cause a bootloop?
Click to expand...
Click to collapse
Yes. At least that's what i'm getting. And i'm currently stuck because my last TiBu backup is months old :/ bummer...

zxz0O0 said:
Nice guide. Please let me know the bugs in PRFCreator v0.6 (you can drop me a pm as I don't have a lot of time for xda at the moment). Also, is step 12 really necessary? Dualrecovery should already be included in the flashable zip (same for step 11 if you include those files).
Click to expand...
Click to collapse
I didn't use the v0.6 because more people complained in the tool's thread about it. V0.5 is working, I can test v0.6 later (maybe tomorrow).
Dualrecovery is included with the flashable.zip but the RIC killer isn't working in that version, it needs to be installed again with the PC installer. Maybe someone (I mean @[NUT] ) could clean up the process

Thx! This is really useful for noobs like me!

Hi zxz0O0, the updater script is looking for 3 files in /utils but when the zip is created on 0.6 those files remain in the root of the zip so you get error when flashing. i think that's the problem with 0.6 but i can be wrong as i didn't test it

norti said:
I didn't use the v0.6 because more people complained in the tool' thread about it. V0.5 is working, I can test v0.6 later (maybe tomorrow).
Dualrecovery is included with the flashable.zip but the RIC killer isn't working in that version, it needs to be installed again with the PC installer. Maybe someone (I mean @[NUT] ) could clean up the process
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56542112&postcount=130
It may be an alternative for Step 12 to modify the flashable dualrecovery .zip file as the post of the link above, I think.

ptmaniac said:
Hi zxz0O0, the updater script is looking for 3 files in /utils but when the zip is created on 0.6 those files remain in the root of the zip so you get error when flashing. i think that's the problem with 0.6 but i can be wrong as i didn't test it
Click to expand...
Click to collapse
Please use his thread for error reporting, thanks!
Ningyou Higeki said:
http://forum.xda-developers.com/showpost.php?p=56542112&postcount=130
It may be an alternative for Step 12 to modify the flashable dualrecovery .zip file as the post of the link above, I think.
Click to expand...
Click to collapse
I don't want to change [NUT]'s recovery installers (everyone can edit scripts if wants), this may be a longer process but more user friendly.

Hi,
Stuck in a ****ing bootloop.. How do I recover?

Puffin617 said:
Hi,
What will happen if I tick RESET CUSTOMIZATION as well?
Click to expand...
Click to collapse
It will reset your phone to factory state after flashing the firmware. If you want a clean update (here we don't) only then you should use this option.

Puffin617 said:
Hi,
Stuck in a ****ing bootloop.. How do I recover?
Click to expand...
Click to collapse
Flash a previous ftf (not 4.4.4), root it, install recovery and restore your backup.
Did you got any errors during the process?

norti said:
Flash a previous ftf (not 4.4.4), root it, install recovery and restore your backup.
Did you got any errors during the process?
Click to expand...
Click to collapse
During the flashing of the ZIP (before FTF), there was something that failed (set_perm) but it still said SUCCESSFUL... But I want a clean update. Can I clean DATA at least?

Puffin617 said:
During the flashing of the ZIP (before FTF), there was something that failed (set_somethingorother) but it still said SUCCESSFUL... But I want a clean update. Can I clean DATA at least?
Click to expand...
Click to collapse
Of course, I'll put this in the OP as an option.

@norti, I tried EVERYTHING again. This does NOT work. Bootloop...
When flashing the Zip, I get an error with the set_perm:
Please link a pre-rooted ROM which has NOT been de-odexed or de-bloated...
PS: After selecting to turn off the phone, it tells me "the phone does not seem to be rooted. Do I want to root" Do I need to select to root it?
---------- Post added at 11:26 PM ---------- Previous post was at 11:18 PM ----------
I get the following when flashing the FTF as-is:
08/025/2014 23:25:54 - ERROR - Processing of system.sin finished with errors.
08/025/2014 23:25:54 - INFO - Ending flash session
08/025/2014 23:25:54 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="8009001C";

now where is that "Thanks" button located.....

Succeeded!!! But I can't make system R/W, though I do as Step 12... Any ideas?

Can someone please link me a good FTF?

Puffin617 said:
Can someone please link me a good FTF?
Click to expand...
Click to collapse
Where did your FTF on your computer NOW come from?

Pre-Rooted Xperia Z1 C6903_5.0.2_C6903_14.5.A.0.242_Customized SG Flashable

This is my First Post......
Finally the File is Uploaded....
Mega Down loader:- " mega.co.nz/#!LgAjzLCJ!IDSitCzjZMs1tpzE8QUFTnVCV_7DSn8dMf14t-MMnMo "
(im new so CDA want allow to post links so..... please copy and paste the link to your browser...)
Thank you.
Steps For Rooting Xperia Z1 C6902/C6903 14.5.A.0.242 Firmware
1. Downgrade to .108 / .157 Firmware and Root It
If you have already updated your smartphone to Android 5.0.2 Lollipop, then you have to downgrade your device to KitKat OS and Root it.
Use this guide to Install .108 firmware.
Root using this guide.
Now Install XZ Dual Recovery.
Now phone is rooted, USB Debugging must be enabled.
Download latest installer for Xperia Z1 from here. (Z1-lockeddualrecovery2.8.10-RELEASE.installer.zip)
Connect phone to PC using OEM date cable and run install.bat.
It will install the custom recovery.
Now work here is done. Lets move on to next step.
2. Root and Install Recovery on Z1 C6902/C6903 5.0.2 Lollipop Firmware
Custom recovery was installed in the first step.
The pre-rooted firmware was created and copied to phone in next step.
Now you have to turn off phone.
Turn it on again and press volume up or down repeatedly to enter custom recovery.
Click on install and locate the folder where you placed the flashable zip earlier.
Tap on it and install it.
Now reboot the phone.
If phone is still connected to PC via USB cable, disconnect it.
Now go back to the .242 ftf you downloaded in second step and copy it to /flashtool/fimrwares
Open flashtool and click on lightning icon in the top left.
Click on it and click on flashmode.
Select the .242 firmware.
In the right bar, in the exclude options, exclude System only. It means that untick System only there. Leave every other options as it is (See the Picture).
While flashtool prepares the software for flashing, turn off your phone.
Keep the volume down button pressed and connect it to PC via USB cable.
The button must be pressed during it.
The phone will enter flashmode.
Flashtool will automatically detect it and start flashing.
After flashing phone will reboot and you will be done...
thanks to 'Hayder Ameen'.....
Mega Down loader:- " mega.co.nz/#!LgAjzLCJ!IDSitCzjZMs1tpzE8QUFTnVCV_7DSn8dMf14t-MMnMo "

I think this guide for Unlockbootloader only.

You just copied and pasted the text from this page:
http://techbeasts.com/2015/04/14/root-xperia-z1-c6902c6903-14-5-a-0-242-5-0-2-lollipop-with-dual-recovery
And you did that without all the instructions, without any links to the mentioned guides and without proof-reading it to make sure it made any sense...
Seriously...

stoan123 said:
I think this guide for Unlockbootloader only.
Click to expand...
Click to collapse
It can be installed on LB. I just installed and try it.

C6902?!
Hey bro, I just want to know if this one is for C6903 only or what? How about C6902. The instruction says C6902/C6903 but the Mega file is C6903??
Appreciate your work!!!

I downloaded the mega link in the first post, but it was not SG customized, C6903_14.5.A.0.242_HK.ftf. thank for advice.
Sent from my HM NOTE 1LTE

(ROOT) (CUSTOM RECOVERY) FOR MOTO G 1st GEN

Hello, guys this is my first post but i am quite sure that my methods work.If there any problems then u can surely ask in the section below. This thread will be a GUIDE TO ROOT AND INSTALL CUSTOM RECOVERY FOR MOTO G 1st Gen users.
Some prerequisites are:
1. Motorola drives (https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481)
2.Fastboot and recovery files (https://www.dropbox.com/sh/9jf2va51ffg0pzq/AAAxDT-ETf7AESIcHGnfEgv7a?dl=0)
[ Let these files be downloaded and kept in Cdrive of ur pc and and place them on the desktop.. Please name this folder MOTO FILES]
3. SuperSu files https://download.chainfire.eu/696/supersu/ and[/url] paste it in ur phones internal memory and please do this after unlocking the bootloader cause bootloader unlocking will delete everything so its better to do it after unlocking bootloader
Download these files and ur done... Now lets continue to the fun part
This process involves three very simple steps :
1. Unlocking the Bootloader:-
This process is infact very easy to do. There are several guides on the internet regarding this process but the one that i suggest is by High On Android/ Max Lee . Follow his method and u can very easily unlock ur bootlader. Copy this url and see it for urself fellow guys...http://highonandroid.com/android-smartphones/how-to-unlock-bootloader-on-motorola-android-smartphone
2. Erasing ur previous recovery and installing a new one and rooting ur phone all in one process
Some users have been reporting that even after installing custom recovery , whenever they go into recovery they enter into stock recovery. The actual problem is that the stock rom of the Moto G rewrites over the new custom recovery installed.
So we have to install the recovery actually twice but it only takes a few minutes
i) Firstly be sure to have lots of juice in your phone
ii) Boot ur phone into the bootloader by power offing ur device and then pressing the volume down and power button together for 10 seconds and then leaving both of them together.
iii) Now connect ur device to ur pc/laptop
iv) Now open a cmd and enter the following commands(press enter after every command)
- cd Desktop
-cd MOTO FILES
-fastboot flash recovery Recovery2.img
-fastboot reboot-bootloader
[MAKE SURE NOT TO REBOOT UR DEVICE ]
v) Now ur phone has custom recovery installed in it and u shud now enter into recovery mode by choosing the option from the bootloader, by pressing volume down and then volume up while in bootloader mode.
vi) This will open the Philz recovery that i have provided with. I prefer the philz recovery over the cwm one. Now go on and install the SuperSu update zip file. And BOOM ur Device is now rooted !!!!.
vii) Now reboot ur phone and u must install
-ROOT CHECKER (to check root)
- and most importantly ROOT EXPLORER
viii) After following step (vii), now if u try to go into recovery, u will be booted to stock recovery. So to prevent that use the ROOT EXPLORER app and go to the root \system\etc and delete the file named install-recovery.sh .
ix) After deleting the file u will once again have to follow step (iv) and install custom recovery this will ensure u having custom recovery even after rebooting ur device and u will have ROOT access as well

On which android version , were you on before rooting . 5.01 or 5.1 .

This method works for both 5.1 and 5.01

Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849

Is the first post too heavy for you?!
Follow the steps and be happy.
Gesendet von meinem Moto G mit Tapatalk

Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!

Andus1988 said:
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Click to expand...
Click to collapse
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:

Ajay P said:
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Click to expand...
Click to collapse
whats the problem u facing ?

sanilch99 said:
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Click to expand...
Click to collapse
It could cumber the inbuilt root!

sanilch99 said:
whats the problem u facing ?
Click to expand...
Click to collapse
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)

Ajay P said:
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Click to expand...
Click to collapse
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:

sanilch99 said:
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
Click to expand...
Click to collapse
Thank you

thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!

notuger said:
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
Click to expand...
Click to collapse
I will recheck that super su. file and make sure its perfect... Thanks for the response:good:

Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device

Works but could be simplified
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!

issam029 said:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
i have edited the previous link and given the new one. You can use this SU file. It will solve ur prob.

pcgardner said:
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
Click to expand...
Click to collapse
Reinstallation of custom recovery is not must its just for safety precautions and I have finally updated the SuperSu link. As far as Busybox u will have to install it customly only.

issam029 said:
once i finished steps all, when i open supersu, popup window says, "there is no su binary installed, and supersu cannot install in it. This is the problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
If i check with root checker,
sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
use the new su files i updated the link

facing problem after unlock bootloader mood for moto g 1st gen
Thanks a lot for your information...:good:
Bro!! I have already unlock bootloader mood.. Before rooting is it necessary to clear all data & app...??

Root Xperia Z5 Compact Android 6.01 (Tested and Working)

I rooted my phone following the guide from user "smartphone-tester". I wanted to update his post as there were 1 or 2 mistakes, and shorten in to make rooting seem a little less scary. His original post is here: http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
STEP 1 Backup your device
Move everything you want to keep onto the SD card or your PC. Your phone will be completely wiped.
STEP 2 Downgrade to exploitable firmware release
2.1 Download XperiFirm from http://forum.xda-developers.com/crossdevice-dev/sony/pc-xperifirm-xperia-firmware-downloader-t2834142
2.2 In XperiFirm - download firmware build 32.0.A.6.200 with XperiaFirm (E5823_StoreFront_1299-6910_32.0.A.6.200_R2B)
2.3 Download flashtool from http://www.flashtool.net/index.php(get latest version)
2.4 In Flashtool - Create FTF file. Select Tools->Bundles->Create
2.5 In FlashTool - Flash the FTF in flashmode. Make sure to select the checkboxes under Wipe. (Takes 10 minutes)
STEP 3 TA / DRM Keys Backup and root current firmware
3.1 Download Ivy Root http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
3.2 Connect your phone in ADB mode, in a command window run:
adb push "root/iovyroot" "/data/local/tmp/iovyroot"
adb push "root/backup.sh" "/data/local/tmp/backup.sh"
open shell: adb shell
chmod 777 /data/local/tmp/iovyroot
chmod 777 /data/local/tmp/backup.sh
mkdir /data/local/tmp/tabackup
/data/local/tmp/iovyroot /data/local/tmp/backup.sh
exit
adb pull "/data/local/tmp/tabackup/"
STEP 4 UPGRADE TO LASTEST ANDROID (6.01)
4.1 In XperiFirm - download firmware 32.2.A.6.224 (get the build for your model, mine is E5823_Customized TW_1298-7315_32.2.A.0.224_R9C)
4.2 In Flashtool - create FTF file from E5823_Customized TW_1298-7315_32.2.A.0.224_R9C and flash in flashmode.
4.3 In your phones setting, under develop options - select "Enable OEM Unlock"
4.4 Unlock your bootloader by following these steps excactly :http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
STEP 5 ROOT ANDROID 6.01
5.1 Download SuperSu 2.74 or greater. Copy the zip file onto your Z5 Compacts internal storage https://download.chainfire.eu/964/SuperSU/BETA-SuperSU-v2.74-2-20160519174328.zip
5.2 In Flashtool -> Tools -> SIN Editor , then extract the kernel from kernel.sin in the directory created by XperiFirm when you downloaded 32.2.A.6.224. It creates an .elf file
5.3 Download rootkernal tool from http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 extract the zip into a folder, then copy the .elf file into the folder
5.4 In a cmd window go into your extracted rootkernal folder, run the command: rootkernel kernel.elf kernel-patched.elf
5.5 When rootkernel is running, select Disable Sony RIC, install TWRP, install busybox, install DRM fix
5.6 Put your phone into fastboot mode (Turn off phone, hold volume up and plug in USB)
5.7 Flash your patched Kernel to your phone with this command: fastboot flash boot kernel-patched.elf
5.8 Go Into TWRP(unplug usb, turn phone on, then keep hitting volume up until phone goes into TWRP)
5.9 Install SuperSu : Select Install, Select SuperSU zip --> systemless mode
STEP 6
6.1 Restart your Device and your done!
DRM KEYS: While we did make a backup for the TA partition containing the DRM keys, this tutorial did not explain how to restore that because in STEP 5 when patching the kernel we selected to use the DRM Fix. This DRM Fix should be good enough - as everything on my phone is working 100%, but should you ever need to restore your TA partition in the future you have your backup.

nice
you should make a video on how to do this (this is my 1st time rooting and i am completely lost)

I'm an occasional user of all those rooting methods. Here I'm fairly stuck at the Iovyroot step.
I was able to unlock bootload, to flashboot the thing, to even revert to 5.1.1, but then, at the Iovyroot step, I can no long see where to open the cmd. Even when I enter adb devices or android devices, nothing is shown. Although I changed the path in the variables.
I'm getting frustrated big time with the lack of user friendly infos on those tutos. Half of the stuff I had to search for third party tutos to understand how I should go to the next step. Please, help someone who doesn't have his translator on.
EDIT: Well, in the end I couldn't do the backup part, but I just did the rooting and the phone seems all good. Powerful and versatile tool in my pocket, I'm pretty satisfied. Thank you for the tuto, be more user friendly though next time. Some people come here with little knowledge, they need to find their way properly.

Why so many steps when all you have to do is unlock the bootloader, flash twrp and that's it? I rooted on lollipop so I'm confused where it git so complicated.

civicsr2cool said:
Why so many steps when all you have to do is unlock the bootloader, flash twrp and that's it? I rooted on lollipop so I'm confused where it git so complicated.
Click to expand...
Click to collapse
The tutorial covers backing up the TA partition that holds the Sony DRM stuff that's used by the camera (and maybe some other stuff).
This is "just in case" the DRM work around stops working, or if something in the future requires the actual TA partition to have the data there.
If you don't care about anything that is affected by the DRM stuff and don't care that not having a backup could prove to be detrimental in the future, you do only need the few steps of 1) unlock bootloader, 2) flash twrp, 3) flash supersu.

what are those step exactly (sorry new to this)
---------- Post added at 03:47 PM ---------- Previous post was at 03:31 PM ----------
I am stuck on "2.5 In FlashTool - Flash the FTF in flashmode. Make sure to select the checkboxes under Wipe. (Takes 10 minutes)" all i get is a window with source folder, device, branding, version. and I don't see the word wipe at all

greenkabbage said:
The tutorial covers backing up the TA partition that holds the Sony DRM stuff that's used by the camera (and maybe some other stuff).
This is "just in case" the DRM work around stops working, or if something in the future requires the actual TA partition to have the data there.
If you don't care about anything that is affected by the DRM stuff and don't care that not having a backup could prove to be detrimental in the future, you do only need the few steps of 1) unlock bootloader, 2) flash twrp, 3) flash supersu.
Click to expand...
Click to collapse
Gotcha. I see no reason to worry about backing up ta, the fix has been working for nearly 7 months and no reported troubles

ISO_Metric said:
you should make a video on how to do this (this is my 1st time rooting and i am completely lost)
Click to expand...
Click to collapse
If this rooting turortial is too difficult try this: http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
With this app, you can fully debloat your phone on a completely stock firmware, locked bootloader etc. Because its your phone is not rooted though, you cannot get Xposed framework or CM13, or other advanced stuff - but for those of us who wanted root just to clean up our devices - this method is definitly the best!

1|[email protected]:/ $ /data/local/tmp/iovyroot /data/local/tmp/backup.sh
iovyroot by zxz0O0
poc by idler1984
Error: Device not supported
Someone knows ho to solve this error in step 3.2? Thank you in advance for the help

can I do this tutorial with 32.0.A.6.152 in step 2 and 32.2.A.0.256 in step 5 ?

sheraro said:
can I do this tutorial with 32.0.A.6.152 in step 2 and 32.2.A.0.256 in step 5 ?
Click to expand...
Click to collapse
There is a .256 firmware?

flopower1996 said:
There is a .256 firmware?
Click to expand...
Click to collapse
sorry .253 , I found that iovyroot works only with .200 for E5823 so never mind

Hi all, sorry for the dumb question, but is there any hope for a root without the bootloader unlocked?

gabbodj95 said:
Hi all, sorry for the dumb question, but is there any hope for a root without the bootloader unlocked?
Click to expand...
Click to collapse
No

Thank you
Hi @Dean F , I appreciate your effort to simplify the steps here as it's a bit messy from the original post.
I've been rooting from Xperia Ray to Xperia Z1 but Z5 have been very challenging for me probably due to the lack of understanding from "How to root post" before you actually made this one.
Thank you my friend :good:

Pardon me for being an idiot

Hello Dean F!
Thanks for this tutoial. But before I'll try this, I have two quetions:
1) How do I use your steps WITH restoring the backuped TA-partition?
2) Is the descriped process also usable with a Xperia Z3 Tablet?
Thanks and greetings from GErmany
"klausstoertebeker"

hi,
i cannot download 32.0.A.6.200_R2B from XperiFirm,
"unable to read data from the transport connection: The connection was closed."
i tried like 10 times, and always same i cannot download until done,
are you or member in here know where i can download firmware 32.0.A.6.200_R2B (E5803) for unlock and rooting my phone?
thankyou very much
nb: sorry for my bad english.

bintangsofyan said:
hi,
i cannot download 32.0.A.6.200_R2B from XperiFirm,
"unable to read data from the transport connection: The connection was closed."
i tried like 10 times, and always same i cannot download until done,
are you or member in here know where i can download firmware 32.0.A.6.200_R2B (E5803) for unlock and rooting my phone?
thankyou very much
nb: sorry for my bad english.
Click to expand...
Click to collapse
Hi, you should download the AU Telstra. That's the only working one for that firmware. You can check the firmware of AU Telstra to double confirm if it's the right firmware.

How to root 32.0.A.6.200 please?

[GUIDE] Enable Camera2 API Without Root [mido] [Unlocked Bootloader] [MIUI 9]

DISCLAIMER
I am not responsible for anything that happens to your device on following these steps. These are untested steps that worked for me and might work for you.
PREREQUISITES
1. PC with adb
2. Unlocked Bootloader
3. TWRP
4. MIUI 9 [Might work with other ROMs, not tested]
5. Lazyflasher zip
NOTES
1. If you are on a custom ROM, chances are that camera2 api is already enabled. Use Manual Camera Compatibility to verify.
2. If you are on MIUI, updating using ota might reset build.prop file. This might help, not tested. Update: I successfully updated to MIUI 9 Global 7.10.19 | Beta, see below for steps,
3. I am using Google Camera v4.4.020.163412804 on MIUI 9 Global 7.9.7 | Beta, and it is a HUGE improvement over the stock camera.
STEPS
1. Boot into TWRP. (Guide if you don't have TWRP)
2. Mount System.
3. Take NANDroid backup. (Optional but HIGHLY RECOMMENDED)
4. Connect to PC and execute the following command in terminal:
Code:
[SIZE="3"]adb pull /system/build.prop[/SIZE]
5. This copies build.prop to the current directory. (C:\Users\[USERNAME] by default on windows)
6. Copy it to another directory for backup.
7. Open in editor and add the following line at end:
Code:
[SIZE="3"]persist.camera.HAL3.enabled=1[/SIZE]
8. Save and exit.
9. Execute following commands:
Code:
[SIZE="3"]adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
[/SIZE]
10. Copy lazyflasher to internal storage.
11. Flash using TWRP.
12. Reboot to system.
13. Use Manual Camera Compatibility Checker to verify.
14. PROFIT!
15. Install the latest Google Camera HDR+ Port. (Optional but HIGHLY RECOMMENDED ;P)
UPDATING MIUI
1. Download the official recovery zip from here.
2. Download latest TWRP from here
2. Reboot into TWRP.
3. Take NANDroid. (Optional, just in case . . .)
4. Transfer ROM zip, TWRP img and Lazyflasher zip to internal storage.
5. Flash ROM zip. (Took about 10 minutes)
6. Flash TWRP img. (Go to flash -> select flash image -> select twrp-[v].img)
7. Flash Lazyflasher zip.
8. Follow steps 4 through 9 of above instructions. (Yes, build.prop also gets replaced on update)
9. Reboot to system.
10. Wait patiently.
11. VOILA !!
LINKS
1. Manual Camera Compatibility Checker
2. Lazyflasher Zip
3. Google Camera HDR+ Port
4. Latest MIUI Recovery Image
5. Official TWRP for mido
6. Sources: (1) (2) (3)
Hope this helps. Try and comment if this works for you in other ROMs. Also let me know if anything is unclear.

TWRP Tweaks (MIUI 9 Beta)
The method in this thread basically allows you to edit build.prop without rooting, which opens up a lot of possibilities. Here are some other useful tweaks to build.prop that I use.
(Note: If a line is already present in the file, edit the line otherwise add at end.)
1. Enable MIUI's full screen gestures
Code:
[SIZE="3"]
qemu.hw.mainkeys=0
[/SIZE]
2. Add EIS and disable noise cancellation
Code:
[SIZE="3"]
persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
ro.qc.sdk.audio.fluencetype=fluencepro
[/SIZE]
3. Turn off noise cancellation for audio recordings
Code:
[SIZE="3"]
persist.audio.fluence.voicerec=false
[/SIZE]
4. Fix Google Assistant talkback
Code:
[SIZE="3"]
mm.enable.qcom_parser=245389
[/SIZE]
Sources: (1)
Do reply if you are using some build.prop tweak and I'll add it here!

is it possible to make the flash-able zip work with stock recovery?

What does the lazyflasher zip actually do? A quick search on google shows a custom kernel installer.

joefso said:
is it possible to make the flash-able zip work with stock recovery?
Click to expand...
Click to collapse
I am not sure if it is safe to flash zips from stock recovery. Even if you could, you would not be able to take NANDroid, so you are doomed if things go south. Still, if you want, you could try and then we'll know

mato_d007 said:
What does the lazyflasher zip actually do? A quick search on google shows a custom kernel installer.
Click to expand...
Click to collapse
The source of the lazyflasher zip (2 in sources) says:
This device uses dm-verity
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
When I was trying the adb method, I was getting a bootloop, because (I think) the system partition had been modified (new build.prop replaced old one). Flashing this zip solved this, so I guess it essentially allows modifications to the system partition.

A_K_S_H_ said:
I am not sure if it is safe to flash zips from stock recovery. Even if you could, you would not be able to take NANDroid, so you are doomed if things go south. Still, if you want, you could try and then we'll know
Click to expand...
Click to collapse
I am willing to try because it would be great if this could work withouth using twrp, root or a unlocked bootloader.
Are the scripts compatible?

joefso said:
I am willing to try because it would be great if this could work withouth using twrp, root or a unlocked bootloader.
Are the scripts compatible?
Click to expand...
Click to collapse
They should be, as I used them with stock MIUI, stock kernel. However, are you going to flash a zip on locked bootloader? Is that even possible? Why would modifications to the system partition be allowed with locked bootloader? What would be the point of locking if that is the case?

A_K_S_H_ said:
They should be, as I used them with stock MIUI, stock kernel. However, are you going to flash a zip on locked bootloader? Is that even possible? Why would modifications to the system partition be allowed with locked bootloader? What would be the point of locking if that is the case?
Click to expand...
Click to collapse
I assumed that if OTA updates can be flashed through bootloader then by that logic /system could be modified too, right? hmmm
In Android devices, Recovery is an Android-based, lightweight runtime environment separate from and parallel to the main Android operating system. Recovery's original purpose was:
to apply software updates to the device, e.g. OTA updates, and
to erase user data and cache, e.g. for troubleshooting or preparing the device for resale (factory reset) and
to run (another) external tool from microSD flash memory
https://forum.xda-developers.com/wiki/Recovery
Click to expand...
Click to collapse

Thanks... BTW..
You can simply add that line using any file manager with root permissions and after rebooting device it works..

amit.tiger12 said:
Thanks... BTW..
You can simply add that line using any file manager with root permissions and after rebooting device it works..
Click to expand...
Click to collapse
Read the title : WITHOUT ROOT

A_K_S_H_ said:
Read the title : WITHOUT ROOT
Click to expand...
Click to collapse
yep I found..
do you have any solution for locked bootloader or everything stock??

amit.tiger12 said:
yep I found..
do you have any solution for locked bootloader or everything stock??
Click to expand...
Click to collapse
Unfortunately I don't have access to a stock mido right now, and I don't want to lock my bootloader.
If you're willing to risk it, you could try these steps:
1. Go to developer settings and enable adb.
2. Follow steps 4 to 9 of main post (with device switched on)
3. Reboot.
You might get a bootloop on rebooting, in which case you'd have to get into stock recovery and factory reset, because afaik, stock recovery doesn't give you adb.
Do tell what happens if you try this, good luck!

When I replace the build.prop the phone goes bootloop. It does not matter I use adb or root explorer or something... Why is that? BTW only this method worked: I used an app called build prop editor and worked like a charm! Thank you. If you did not tell that it was possible to enable camera 2 api on miui 9, all my hopes would be lost. So I suggest everyone to use another methods in case this does not work.

Does this work for MIUI 8? I dont want to root my phone but would like camera2

qun said:
Does this work for MIUI 8? I dont want to root my phone but would like camera2
Click to expand...
Click to collapse
It should, provided you have unlocked bootloader, but I haven't tested yet. Take a backup and try! Also, don't forget to reply what happens if you do try.

Can someone tell me what is this?it was set to no hdr+ on default.im on miui 9 global beta 7.12.8

In the end of the TWRP guide it says to flash lazyflasher.zip . In the end of this guide it also says you have to install lazyflasher.zip .
Do you have to install it both times or is once enough ? What would happen if you follow both guides to the letter and install it twice ?

Ghavio1516 said:
Can someone tell me what is this?it was set to no hdr+ on default.im on miui 9 global beta 7.12.8
Click to expand...
Click to collapse
These are configs, check and see which one works best for you.

foxhunt said:
In the end of the TWRP guide it says to flash lazyflasher.zip . In the end of this guide it also says you have to install lazyflasher.zip .
Do you have to install it both times or is once enough ? What would happen if you follow both guides to the letter and install it twice ?
Click to expand...
Click to collapse
No, once should be enough, but flashing twice won't cause any trouble either.