Related
Due to new security measures added on recent Android versions (mainly dm-verity), using dd Flasher on newer devices or recent firmwares (Marshmallow, Nougat, etc) will certainly result in a bootloop. dd Flasher probably still works if you have a unlocked bootloader and a modified kernel disabling dm-verity, but due lack of free time and other priorities, this tool is currently unmaintained.
Introduction
This tool is a new version of Nicki Root (originally released for Xperia M), but now compatible with almost any device. The purpose of dd Flasher is keeping root access in any firmware version assuming your device already have an exploitable firmware...
How it works?
Sony updates are packed in .sin files, generally stored in FTF packages. Using FlashTool, you can get an image of the system partition (system.ext4) of the latest firmware available, which is sideloaded into your device by dd Flasher. Next, it'll mount the update image (system.ext4) in a loop device, place SuperSU binaries (and when needed, disable RIC protection) and after that, stop all running processes and "flash" the modified image back into your device by using dd binary.
After dd Flasher finishes its work, all you need to do is rebooting your device into flash mode in order to flash the rest of the FTF file (excluding system partition, of course) with FlashTool. In the end, your device will be running the latest available firmware with full root access, making dd Flasher extremely useful for devices with locked bootloader that have exploitable firmwares but lack recoveries or other means to get root access.
Requirements
• Your device must already have root access. You can downgrade to an older firmware and root it with some known exploit, if needed. Also, if you don't have root access, dd Flasher won't work at all.
• You will need FlashTool and an FTF file of the firmware version you want to upgrade your device to.
• Your device should have enough free space to store system partition image of the update temporarily (around 1.5-2.5GB, depending of the device/firmware). At the moment you can store the image either on its Internal Storage or in external SD Card (when possible). USB OTG support is planned too.
• If pushing system image to SD Card, make sure your phone is connected in MTP mode (in Mass Storage mode only Internal Storage is accessible and dd Flasher will fail)
Instructions
Getting system partition image: FTF files are just ordinary .zip files with lots of .sin files inside, format commonly used by Sony in their firmwares for Xperia devices. We are interested in system.sin (it's the one with the partition image), to use it with dd Flasher, so:
• Open the FTF file with WinRAR or 7-Zip (or any other program compatible with .zip files);
• Extract system.sin somewhere you have easy access;
• Open FlashTool and go to Tools => SIN editor;
• A new window will open. Locate system.sin we extracted before, click in "Extract Data" and wait until FlashTool finishes extracting it
• If everything went well, now you should have a system.ext4 file in the same place you extracted system.sin before (you can already delete system.sin -- we won't need it anymore).
Using dd Flasher: now that we got our system partition image, we can move on to dd Flasher:
• If you didn't already have extracted dd Flasher somewhere, do it now (DUH!). Make sure FlashTool isn't running as well -- it's known to interfere with ADB interface;
• Move system.ext4 extracted previously to the same folder you've extracted dd Flasher (where dd_flasher.bat/dd_flasher.sh is located);
• Open dd_flasher.bat (or start dd_flasher.sh from a Terminal if you're on Linux) and follow the instructions. After selecting a storage device, dd Flasher will do its work;
• Please note some steps take a while to complete (mainly pushing the system image and flashing it), your device will look like it's dead and won't respond but don't worry, it's normal (on compatible devices the notification LED will pulse in different colors to indicate the the script is running);
• If everything went well, dd Flasher will notify you (and your notification light will be green, if compatible). After that, you'll need to power cycle the device, disconnect the USB cable and pull your battery off (if your battery is non-removable, use the Off/Reset microswitch). Wait some seconds and put your battery back but don't turn your device on yet.
Flashing the remaining with FlashTool: at this stage, your device have the latest firmware from the FTF you used and full root access but still have old versions of kernel, baseband, etc., so, trying to start your device now will probably result in a boot loop or something like that, so, let's finish it:
• Open FlashTool again and flash the FTF you used to extract system.ext4 in flash mode, however, make sure you've excluded SYSTEM, if you forget to do so, everything the tool did will be lost and you'll need to restart from the beginning;
• After flashing ends, disconnect the USB cable and start your phone. The first boot may take several minutes but if everything went well you should be now running the latest firmware, with full root access!
Compatibility
This tool uses an internal database to automatically set up everything needed in the officially supported devices, with at the moment are:
• Xperia E series (C1504, C1505, C1604, C1605)
• Xperia E3 series (D2202, D2203, D2206, D2212, D2243)
• Xperia M series (C1904, C1905, C2004, C2005)
What to do if my device isn't officially supported? dd Flasher also comes with a "default" config which is automatically selected when used in a unknown device. It should work by default in any Xperia (and may even work in devices from other brands), but if dd Flasher still refuses to work, PM me your device model and firmware version, I'll try to support it
FAQ
Soon
Credits
Although I wrote this script from scratch, it uses some pieces of code written originally by @zxz0O0, @[NUT] and @Chainfire, so, credits to them. I would like to thank also everyone who helped directly or indirectly in the conception of the original Nicki Root script, which became what we know today as dd Flasher
Changelog
Soon
Download
All currently released versions available in downloads tab.
XDA:DevDB Information
dd Flasher, Tool/Utility for the OEM Cross Device Development
Contributors
mbc07
Version Information
Status: Beta
Current Beta Version: 2.0
Beta Release Date: 2015-03-19
Created 2015-03-19
Last Updated 2015-03-19
Awesome!
Incredible!
Thanks for sharing this with the community.
Nice
Thanks for everything
Amazing
Thank you so much!
Who try it with android 5.0.2 of z2,z3,z3c,??? And is is full root, isn't it????
nhoc_huhu said:
Who try it with android 5.0.2 of z2,z3,z3c,??? And is is full root, isn't it????
Click to expand...
Click to collapse
Not ready yet =/
The current SuperSU package included in this beta version is unlikely to work in Lollipop -- I was working into that but it didn't made it into this beta. I'll try to get it ready for the stable version...
Error: can't stat '/data/local/tmp/ddFlasher/system/bin/sh':
Hallo,
i tried this on a xperia m (C1905) and get this error:
---------------------------------------------------
Initializing ADB [DONE]
Waiting for device [DONE]
Waiting root access [DONE]
Preparing script [DONE]
Pushing system image [DONE]
Stopping device [DONE]
Mounting system image [DONE]
Installing packages...
- SuperSU v2.46 (SELinux) cp: can't stat '/data/local/tmp/ddFlasher/system/bin/sh': No such file or directory
[DONE]
- Disable RIC (RAM Disk) [DONE]
Saving changes [DONE]
Flashing image [DONE]
System partition updated.
Reboot your phone into flash mode to finish.
NOTE: device won't respond in current state, that's
normal, pull your battery or use Off/Reset switch.
Press any key to exit...
--------------------------------------------
I used C1905_15.4.A.1.9_CE.ftf for the system.sin.
rootchecker says everything is fine but "folderMount", for example, dosnt work, it does a "hard" restart without request.... the screen went black and then reboots.
Before the rooting i also had 15.4.A.1.9 on the phone.
for "prerooting" i used towlroot v3
Could someone please help me with this.
I like to get more space for apps on the xperia m. with something like folderMount or swapinternal 2 external SD and i really tried a lot rooting technics and rootfixer and so on but nothing works.
its really frustrating.
kind regards
Oliver
olliD said:
rootchecker says everything is fine but "folderMount", for example, dosnt work, it does a "hard" restart without request.... the screen went black and then reboots.
Click to expand...
Click to collapse
You have partial root access, that's why the device reboots. I added that in to-do list, should be fixed in the stable release of dd Flasher. Since you have Xperia M, it's much easier and quicker to root it with TowelRoot and then applying the root fixer (there's a tutorial in Xperia M forums). In the meantime, if TowelRoot still fails, you can try again with the old Nicki Root, although old and not supported anymore, they should still work, at least with Xperia M...
What is the difference with the prfcreator tool?.cheers
juanpirulo said:
What is the difference with the prfcreator tool?.cheers
Click to expand...
Click to collapse
PRF Creator generates a flashable ZIP, you'll need a recovery to use it, differing from dd Flasher that archive this through ADB bridge, so, it works even if there's no recovery for your device...
Hi mbc07,
thanks for the reply.
I did this (with TowelRoot and then applying the root fixer (there's a tutorial in Xperia M forums).) several times. I have 2 Versions of the rootfixer on my pc in the moment, tried both but dosent work. I also looked for the tutorial you mentioned, but i didnt find it, sorry.
Could you please link to the tutorial or the correct rootfixer.
I just saw that i dont tell you that i have a locked bootloader, just for info.
kind regards
Oliver
Try this tutorial @olliD...
Got SuperSU v2.46 (SELinux) cp: can't stat '/data/local/tmp/ddFlasher/system/bin/sh': No such file or directory
and some related errors
I'm a complete beginner when it comes to rooting, flashing and so on. I've been using my Nexus 4 since the day it came out, and have always had it completely stock, never even rooted it or anything. I'm normally not too bad at stuff like this, but I've been googling how to do all of this and been reading some guides on here, and I'm just getting more and more confused.
My goal is to go from Stock Android 5.1.1 to the newest Cyanogenmod nightly, and to keep all my data. Now, how do i go about this?
I'm already stuck at the first step (or at least I think, that's the first step): Creating a backup of my current Stock phone. Apparently I need to create a NANDROID backup first, but I can't do it with a locked bootloader? And if i unlock the bootloader, my data will be wiped? This alone seems completely illogical to me, because how am I going to backup my device then? Is there no simple step by step guide for Nexus devices, that includes EVERYTHING, from backup to the final flashing of the ROM?
This is a good guide http://forum.xda-developers.com/showthread.php?t=2018179
I've seen it and it doesn't answer my question. How do I unlock the bootloader to create a backup, without wiping my device?
jb91 said:
I've seen it and it doesn't answer my question. How do I unlock the bootloader to create a backup, without wiping my device?
Click to expand...
Click to collapse
You can't unlock the bootloader without wiping the device. The only backup you will be able to make without an unlocked bootloader is copying your sdcard to your pc and use an app like helium to backup your apps and data. Just remember to copy that backup to your pc as well, otherwise it will be wiped.
theminikiller said:
You can't unlock the bootloader without wiping the device. The only backup you will be able to make without an unlocked bootloader is copying your sdcard to your pc and use an app like helium to backup your apps and data. Just remember to copy that backup to your pc as well, otherwise it will be wiped.
Click to expand...
Click to collapse
Thanks. Do you know this "Nexus Root Toolkit" program? I was able to create a backup file containing all apps with it, as well as extract a file with my contacts data from my Nexus 4. I'm guessing this should also include my SMS / WhatsApp messages and so on?
jb91 said:
Thanks. Do you know this "Nexus Root Toolkit" program? I was able to create a backup file containing all apps with it, as well as extract a file with my contacts data from my Nexus 4. I'm guessing this should also include my SMS / WhatsApp messages and so on?
Click to expand...
Click to collapse
Unfortunately I don't know much about that. You could skim through some of the thread or search to find out if someone else has asked that question and if not ask it there. That would probably be the easiest way to find out.
This is extremely confusing, I have no idea how people can say it is simple to put a custom ROM on a Nexus device. I am absolutely lost trying to back up everything. Is a NANDROID backup just a full backup of the phone? Am I not completely screwed if I can't create this? I have some random app files, extracted from a Root Toolkit, and a contacts file. I don't think that's enough to save my device in case anything goes wrong during flashing?
One of the sticky threads here mentions this right at the beginning:
Before you do anything EVER, you'll always have to backup your stuff, even if you don't feel like it, or your dog died (in which case I'm truly sorry), but, no matter what you're about to do, always have a recent backup sitting around.
There are many ways and things you can and will probably have to backup.
1. Backup your entire phone, by creating a Nandroid Backup.
As you saw in the 'Custom Recovery" picture above, you have a "Backup and Restore" option.
Click to expand...
Click to collapse
But it doesn't make any sense. "Before I do anything", I can't even create the NANDROID backup to begin with, because the bootloader is not unlocked by default, and unlocking it will wipe everything on the device. So I don't get how the first step to put a ROM on a phone is to create a NANDROID backup, because from my understanding, it is not possible to do. Also, my Nexus 4 did not come with a "custom recovery" installed and I have no idea how to put this on there (do i do this before or after the NANDROID backup?). I'm really starting to wonder how anyone actually understands these guides.
jb91 said:
This is extremely confusing, I have no idea how people can say it is simple to put a custom ROM on a Nexus device. I am absolutely lost trying to back up everything. Is a NANDROID backup just a full backup of the phone? Am I not completely screwed if I can't create this? I have some random app files, extracted from a Root Toolkit, and a contacts file. I don't think that's enough to save my device in case anything goes wrong during flashing?
One of the sticky threads here mentions this right at the beginning:
But it doesn't make any sense. "Before I do anything", I can't even create the NANDROID backup to begin with, because the bootloader is not unlocked by default, and unlocking it will wipe everything on the device. So I don't get how the first step to put a ROM on a phone is to create a NANDROID backup, because from my understanding, it is not possible to do. Also, my Nexus 4 did not come with a "custom recovery" installed and I have no idea how to put this on there (do i do this before or after the NANDROID backup?). I'm really starting to wonder how anyone actually understands these guides.
Click to expand...
Click to collapse
Following the link to the guide, I see this:
*****
Unlocking the Bootloader:
***NOTE***
This will perform a factory reset on your device. You will lose all applications. Even the data on your SD Card! I'd recommend making a Backup to your computer BEFORE performing this. There is a method for backing your data up, detailed HERE.
For the time being, there is a method available that will allow you to unlock your device (and root it) without losing your data.
For instructions, click HERE. Please note: this is a hack and isn't the "conventional" and "accepted" way of unlocking your bootloader on a nexus device. The wipe requirement is there for your safety, really, and I'm certain this will be patched in the upcoming releases.
*****
But you can always use adb directly from your pc to backup your entire device. How? adb --help
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
greg17477 said:
But you can always use adb directly from your pc to backup your entire device. How? adb --help
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
Click to expand...
Click to collapse
Is ADB this "Android Studio" that I had to install in the first step of this guide (Android SDK)? If so, I opened it but I have no clue how to get anywhere where i could enter code like this. This is what it looks like: http://i.imgur.com/zhujSKR.png
jb91 said:
Is ADB this "Android Studio" that I had to install in the first step of this guide (Android SDK)? If so, I opened it but I have no clue how to get anywhere where i could enter code like this. This is what it looks like: http://i.imgur.com/zhujSKR.png
Click to expand...
Click to collapse
Sorry, i can not help you , if you do not know the basic of basics Lots to read up for you.
cheers
Well ok, lets try it another way: i don't understand how to create a full backup, but i did backup some single apps to my PC using Nexus Root Toolkit (they're .ab files), for which i want to keep my data. I also manually backed up my mp3s and pictures / videos. Would i be fine just starting with the actual process (unlocking bootloader, install custom recovery and so on)?
After all, i should have the possibility to revert anything back for these apps at least, and the official Nexus 4 Stock Android files are available at Google. So, there's no real risk, even without a FULL backup of everything, correct?
This is just a translation of the Windows Binaries to run on Linux.
So if you need some specific help, this is a better place
So, I will quote the original thread.
Backup TA for Sony Xperia
Backup TA can backup and restore the TA partition of the device. When you create a backup before unlocking for the first time, then you will be able to restore to full factory state (including a locked bootloader). This means all DRM keys intact, Bravia Engine working in Album and last but not least your warranty when needed
NOTE: When you did create a backup of your device's TA with another tool or Backup TA v4 or earlier, you are able to convert it to a valid Backup TA package by choosing 'Convert TA.img' from the menu. When you've done this you are able to restore it safely.
Downloads/Source
ChangeLog/Commits
Compatibles Devices
The list is in the original Thread, but is outdated, give it a try.
GUIDE
1. Download the latest version of Backup TA.
2. Extract the ZIP file to a folder location of your choosing.
3. Navigate to the folder location of Backup TA.
4. Make sure no other script or application which is using ADB is running.
5. Make sure the device is booted in normal mode (the way you normally use it).
6. Run Backup-TA.sh
7. Read the last paragraph of the license before continuing.
8. Read the information and follow the instructions given by the tool.
FAQ's and Others
Go to the original thread
Thanks to:
@DevShaft (for creating the tool)
@luminoso (for support and testing)
to the other Dev's that contributed to the original tool.
thanks a lot backed up ta xperia z ultra on ubuntu using ur tool . Thanks a lot and this tool is amazing
NABENDU1 said:
thanks a lot backed up ta xperia z ultra on ubuntu using ur tool . Thanks a lot and this tool is amazing
Click to expand...
Click to collapse
How do you get it to run? All I get is a script, don't know how to run it
Edit* I'm using Linux mint, would I be better with a different distro?
---------- Post added at 04:33 PM ---------- Previous post was at 04:16 PM ----------
zezadas said:
This is just a translation of the Windows Binaries to run on Linux.
So if you need some specific help, this is a better place
So, I will quote the original thread.
Backup TA for Sony Xperia
Backup TA can backup and restore the TA partition of the device. When you create a backup before unlocking for the first time, then you will be able to restore to full factory state (including a locked bootloader). This means all DRM keys intact, Bravia Engine working in Album and last but not least your warranty when needed
NOTE: When you did create a backup of your device's TA with another tool or Backup TA v4 or earlier, you are able to convert it to a valid Backup TA package by choosing 'Convert TA.img' from the menu. When you've done this you are able to restore it safely.
Downloads/Source
ChangeLog/Commits
Compatibles Devices
The list is in the original Thread, but is outdated, give it a try.
GUIDE
1. Download the latest version of Backup TA.
2. Extract the ZIP file to a folder location of your choosing.
3. Navigate to the folder location of Backup TA.
4. Make sure no other script or application which is using ADB is running.
5. Make sure the device is booted in normal mode (the way you normally use it).
6. Run Backup-TA.sh
7. Read the last paragraph of the license before continuing.
8. Read the information and follow the instructions given by the tool.
FAQ's and Others
Go to the original thread
Thanks to:
@DevShaft (for creating the tool)
@luminoso (for support and testing)
to the other Dev's that contributed to the original tool.
Click to expand...
Click to collapse
What distro is recommended to run this? I tried Linux mint but couldn't get it to run
brooker88 said:
How do you get it to run? All I get is a script, don't know how to run it
Edit* I'm using Linux mint, would I be better with a different distro?
---------- Post added at 04:33 PM ---------- Previous post was at 04:16 PM ----------
What distro is recommended to run this? I tried Linux mint but couldn't get it to run
Click to expand...
Click to collapse
You need set the Script as exec and run on terminal "sh . /Scriptname.sh"
Hey friends! I was looking at this thread: http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307 and I decided to create my own thread about the same topic, however this thread is much more simplified and is for those people who are new to rooting Xperia smartphones.
So without further ado here are the steps
Part One: downloading prerequisites
in order to flash .ftf firmware files to downgrade your phone to lollipop for TA backup you will need.
1. Java JDK :
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
2. XperiFirm(not neccesary if you plan to stay on LP)
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
3. Flashtool
http://www.flashtool.net/downloads.php
4. Android SDK
http://developer.android.com/sdk/index.html#downloads
5. iovyroot(not necessary if you do not want to backup DRM)
http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
other prerequisites:
Patience
Mountain Dew or Starbucks
A small bit of knowledge on command line interfaces
Part Two: Downloading firmware
1. Open up XperiFirm
2. Select your device from the list
3. Select your model number(can be checked in Settings > about phone > Model Number
4. Pick your country and carrier(does'nt really matter, best firmware to use is UK customised and Singapore customised)
5. Click the latest release in 'available releases'
6. A dialogue should pop up, tick 'automatic unpack'
7. Wait for download to complete
Part 2.5: Creating FTF
Open up Flashtool
1. Click on tools > bundles > Create
2. Select the firmware folder
3. Double click on the Device section and select your device
4. Type in the firmware build number(at the end of the folder name) as for branding type in the country and carrier from which you downloaded the firmware from.
5. Go to file explorer and delete 'fwinfo.xml' from the firmware folder
6. IMPORTANT DO NOT TRANSFER THE FILES WITH A .TA FILE EXTENSION IT WILL BRICK YOUR DEVICE with that disclaimer out of the way go back to flashtool, transfer all the files using the arrows (except those with a .ta file extension)
7. Click create, you should be able to sit back and relax while it does its thing
Part Three: Downgrading firmware
Download the firmware here: http://www.xperiablog.net/forum/resources/xperia-z5_e6653_32-0-a-6-152_central-europe-5_generic.477/
1. Place the file in c: Users/*account name*/.flashtool/firmwares
Open up Flashtool
2. Press the lightning bolt icon
3. Choose Flashmode and click ok
4. choose the firmware you downloaded(Do not choose the one you created)
5. Tick "user data" in the box at the top right hand corner
6. Press flash and wait
Part Four: DRM backup and unlock
1.Extract iovyroot
2. make sure USB debugging and unknown sources are enabled
3. Open up backupdrm.bat and wait
4. make sure there are no errors before proceeding(this usually takes a couple of tries)
5. IMPORTANT keep a safe online backup of your DRM keys.
6. Open up flashtool
7. click on BLU
8. Go to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
9. Select your device and follow the instructions
9. after getting the unlock key, paste it inside the BLU dialogue in flashtool
10. wait, then profit!
11. now flash the .FTF that you created
12. boot your device into fastboot(plug in power cable and press vol down when your phone is switched off)
13. Download androplus kernel v23 and above from here: https://kernel.andro.plus/
14. Extract boot.img and put it in the android SDK inside of 'platform-tools'
15. Press shift+right click inside of the same folder
be sure to install xperia z5 fastboot drivers)
16. click 'open command window here'
17. run fastboot devices and make sure it detects your device
18. run this command here : fastboot flash boot boot.img
19. Reboot and DONE
Just a quick note, from my experience with downgrading in the past, you MUST wipe your user data, the phone won't boot else. This happened on multiple Sony phones with multiple different firmware versions.
gamer649 said:
Just a quick note, from my experience with downgrading in the past, you MUST wipe your user data, the phone won't boot else. This happened on multiple Sony phones with multiple different firmware versions.
Click to expand...
Click to collapse
I just corrected it, thanks for the quick note. Btw my z5 booted with minor issues when downgrading without wiping userdata
_LLJY said:
I just corrected it, thanks for the quick note. Btw my z5 booted with minor issues when downgrading without wiping userdata
Click to expand...
Click to collapse
Every other Sony phone I've owned (M, Z1 compact, Z2) refused to boot after a downgrade. The main thing to remember when downgrading is to take a backup before doing so to prevent data loss, I've experienced it myself firsthand so I know how stressful it can be.
In the TA backup part you should add a step to make sure the script actually worked and didn't stop with an error, before proceeding on to unlocking BL. I had to reboot my phone & run the script several times before successfully pulling it off.
Hello!
I'm new to the Sony family as you can see in my signature and I wouldn't call myself n00b, but the whole procedure with the extra partitions is so confusing! Thank you for trying to break it down!
the usual 3 step way (1 unlock bootloader, 2 flash recovery, 3 flash SuperSU) is still present but there are some other steps before them.
As i can understand, all the hassle is just for the backup of the TA partition.
I think that we must start with your step 3, just to avoid confusion such as the step 3.4. Please post a direct link to the firmware you suggest, I can't download it because it requires me to register there too.
Also, you should break the part 4 at the step 11. If I'm not mistaken, the order should be 1, 3, 4 (1-10), 2 , 2.5, 4 (11-19).
In the guide, restoring DRM keys also should be added. ?
Nice guide mate.
Sent from my E6683 using Tapatalk
DeathStroke said:
In the guide, restoring DRM keys also should be added. ?
Nice guide mate.
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
Latest andro kernel have drm keys intergrated bro
working for e6633 dual ?
I had a doubt! On Part Three, can I use the given E6653 ftf for my E6683? Or I should download the .152 ftf for my exact device model i.e. E6683?
Help me bro @_LLJY
good guide
easy follow
had overheat problem i need help...!
any one please ?
updated from support ( device no pc)
after update full overheat on camera use
Can you guys please help me?
My friend got a 5803, I backed up his DRM keys and unlocked the bootloader but can't root it.
If someone could be so kind to help us it'll be great, I did it to my 6653 but for some reason I can't root this one.
Sent from my E6653 using XDA-Developers mobile app
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
feesta said:
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
Click to expand...
Click to collapse
Unpack firmware Ftf file with flashtool and see is there file called FWINFO.Delete this file and pack Ftf using Ftool and you will not have peoblems with flash.
Sent from my Sony Xperia Z5
Here is a stupid question, what now that i have don all steps? i still dont have cmw or root?
feesta said:
i am trying to downgrade my z5 from 6.0.1 to a 5.1.1 ftf...but when i begin to flash it stops ERROR - processing of loader.sin finished with errors....please someone can help me?
Click to expand...
Click to collapse
I did two things to try to fix this:
1: Use the previous version of flashtool (0.9.18.6) instead of the current one
2: Use the Software Repair function of Sony's Xperia Companion application
I don't know which of these helped (it might have been neither, actually) but in the end I was able to flash Lollipop 5.1.1 onto my Z5 and use iovyroot to back up the TA partition.
Hi, this is kind of off-topic but this is the best thread for this question I could find.
I was in a hurry to get rid of the bloated, horrible stock rom, and I did not back up my DRM keys. I did patch my current kernel with the DRM fix from another thread here at XDA. Now my question is:
What kind of functionality did I lose from this, except not being able to restore to stock and relocking bootloader?
klemen241 said:
Here is a stupid question, what now that i have don all steps? i still dont have cmw or root?
Click to expand...
Click to collapse
Hello, look at this video:
h**ps:.youtube.com/watch?v=dTlosea6SJE
But at first, i installed at my Z5 the latest Kernal v36 and then i installed the TWRP 2.8.7.0, but i think you can install the newest TWRP too.
At last you install the SuperSu with TWRP, than you have full root!
Creating FTF not possible
hej,
i have a problem creating the FTF as described in Part 2.5:
-i downloaded the latest version via xperifirm (E6653_Customized DE_1298-3675_32.2.A.0.253_R3C)
-i deleted the fwinfo.xml & all .TA files from the folder
-flashtool is hanging here now:
-05/016/2016 09:16:25 - INFO - Streaming from file : C:\Users\hek\Desktop\Sony Xperia Z5\E6653_Customized DE_1298-3675_32.2.A.0.253_R3C\boot\boot_delivery.xml
05/016/2016 09:16:25 - INFO - Adding rpm_S1_Boot_MSM8994_LA1_2_2_40_AID_1_KITAKAMI-TEST-HWID009400E1-SWID0A-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin to the bundle
05/016/2016 09:16:25 - INFO - Adding Sumire_S1BootConfig_MiscTA.ta to the bundle
-tried it with singapore customized and german customized (¬ deleting the .TA-files & manually unselecting all TA files in flashtool)
what could be the issue here or is there another way to get the latest version on the phone after unlocking it?
or is it safe just to install the latest version as described here without deleting the .TA-files? (http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224)
thanks for any input!
--
Part 2.5: Creating FTF
Open up Flashtool
1. Click on tools > bundles > Create
2. Select the firmware folder
3. Double click on the Device section and select your device
4. Type in the firmware build number(at the end of the folder name) as for branding type in the country and carrier from which you downloaded the firmware from.
5. Go to file explorer and delete 'fwinfo.xml' from the firmware folder
6. IMPORTANT DO NOT TRANSFER THE FILES WITH A .TA FILE EXTENSION IT WILL BRICK YOUR DEVICE with that disclaimer out of the way go back to flashtool, transfer all the files using the arrows (except those with a .ta file extension)
7. Click create, you should be able to sit back and relax while it does its thing
I used iovyroot and it created taxxxxxx.img that it has 2mb. I think so I read so time ago that taxxxxx.img had 500kb... Is it my ta wrong?? Or it's normal??
Thanks!
Enviado desde mi Z1 mediante Tapatalk
Why yet another guide? Why should you follow this guide?
This is more of a future reference for myself, but might be beneficial to some other people, hence why I decided to post it.
Thanks to the "dirty cow" exploit (CVE-2016-5195), we now have a more simple way of backing up the TA partition compared to existing guides, which all relied on another exploit that involved downgrading the firmware, thus making the whole process a bit more complicated.
Unfortunately, as you can probably tell, it's still not a painless ordeal, just "less" painful. But hey, at least you have a choice.
To keep this step-by-step walkthrough guide simple and straightforward, I am focusing on just the steps and skipping the explanations.
Let's get started!
Prerequisites
Important: Your phone must be vulnerable to the "dirty cow" exploit, any firmware version with security patch level 2016-12-01 or earlier should work, such as 32.2.A.5.11. Basically, any MM or LP firmware.
Currently there is no way of backing up the TA partition on Android 7.0 Nougat firmware, you will need to downgrade to MM or earlier firmware first.
Remember to backup all your data before you downgrade, since a downgrade is akin to a factory reset. Downgrade instructions:
Follow Step 0, skip Step 1 and 2
In Step 3, download a MM or LP version firmware. For the sake of simplicity, I suggest you download the one labeled Storefront.
Follow Step 4 and 5
Done, your phone is now downgraded, skip the remaining steps. Continue with the guide as usual from Step 1
Note: If the DRM keys are irrelevant to you (TA partition already backed up/restored/lost) and would just like to root, then you can root using this guide on all firmware versions including Android 7.0 Nougat without downgrading. In this case, you can skip Step 1 and Step 7. Depending on your situation, you can also skip other parts of this guide, such as Step 2 if your bootloader is already unlocked, or in Step 5 don't wipe anything (leave all boxes unchecked) to retain your apps and data for a firmware upgrade.
Computer setup with correct drivers and adb/fastboot connection ability.
Enable USB debugging on the phone:
Settings > About phone > Tap multiple times on Build number until Developer options is enabled
Settings > Developer options > USB debugging > Toggle ON
XperiFirm for downloading official Sony firmware directly from Sony's servers
Flashtool for flashing firmware
Battery preferably more than 80% remaining, loss of power while flashing can brick your phone
Step 0 - Backup your phone (optional)
Move all your data to your SD card using the native tool: Settings > Storage > Transfer data to SD card
Use Sony's Backup & restore app to make a backup: Settings > Backup & reset > Xperia Backup & restore > More > Manual backup > Select SD card > Select content to backup
Personally, I choose everything except apps, they can be re-downloaded from the Play Store at any time, plus they take a long time to backup and restore not to mention eats up free space
Step 1 - Backup the TA partition
Download this wonderful TA Backup tool, unzip to desired location
With the phone powered on, connect the USB cable to the computer, then plug the micro USB end to the phone
Open command prompt (Start > Run > cmd), navigate to the directory where you unzipped the TA Backup tool
Run the following command:
Code:
backupTA
The tool will run and if successful, you should see at the bottom the words "TA Successfully pulled to TA_E5823.img".
TA_E5823.img is the TA partition image file, actual filename will be longer and differ for everyone so to keep it simple we'll just refer to it as TA_E5823.img in this guide.
Please check that the file is 2,097,152 bytes. If not or file is missing, then the backup has failed.
If it fails, just run the tool again a few times, or try rebooting your phone then rerun the tool. If you just can't get it to work, seek help from the tool thread.
Step 2 - Unlock the boot loader
Visit Sony's website and follow the instructions carefully
Important: Pay attention to the warnings. No, really, unlocking the boot loader will wipe your DRM keys (hence the need to back them up in Step 1) and trigger a factory reset, erasing everything on your phone.
After you've successfully unlocked the boot loader, unplug your phone and leave it powered off
Step 3 - Download stock firmware
Run XperiFirm, locate the correct Xperia Z5 Compact version of your phone (E5803/E5823) and download the firmware of your choice.
General recommendation is to download the "Customized" version that's available for your country.
Step 4 - Create a FTF file from the firmware
Open Flashtool
Tools > Bundle > Create
Select source file > Locate the folder where you saved the firmware from XperiFirm in step 3 > You should see your device name appear automatically in Device and the folder list below populated
Branding > The same as Operator in XperiFirm, e.g. Customized AU
Version > The version you downloaded, e.g. 32.2.A.5.11
Hint: Both Branding and Version information is in the folder name
In folder list, select the first item, hold SHIFT and select the last item so that all items are highlighted, then click the "- >" button > The folder list should now be empty, and the Firmware content field populated
Click Create, if successful you will see "Bundle creation finished"
Note: The FTF file is saved to %userprofile%\.flashTool\firmwares by default
Step 5 - Flash the FTF file
Click the lightning symbol in Flashtool > Flashmode
Source folder should be pre-selected to the default location mentioned above and "Sony Xperia Z5 Compact" listed in Firmwares
Expand all the arrows and select the version number
Under Wipe/Sin check all options (APPS_LOG, DIAG, SSD, USERDATA), leave all other options unchecked
Click Flash, wait for an instruction prompt to pop up
Plug the USB cable to your computer if it isn't already plugged
Turn off your phone if it isn't powered off, hold the VOLUME DOWN button while connecting the micro USB end to your phone. Keep the VOL DOWN button held until the prompt disappears, which indicates that Flashtool has detected it and is correctly in flashmode.
Flashtool will begin flashing the firmware automatically. It can take a long time, 10~15 minutes is normal, wait until completed
Unplug your phone and do not power it on yet
Step 6 - Patch the kernel
Download this awesome rootkernel tool, unzip to desired location.
Extract the kernel image file kernel.sin from the FTF file using any file compression program such as 7zip, WinZip, WinRAR, etc.
Open Flashtool > Tools > Sin Editor > Sin file > Locate the kernel you just extracted > Click Extract data. You should now have a file named kernel.elf in the same folder
Copy kernel.elf to the rootkernel folder
Download the latest stable version of the SuperSU ZIP file and copy the entire ZIP file to the rootkernel folder. Do NOT unzip it!
Rename the SuperSU ZIP file name so that it starts with SuperSU (case sensitive) instead of UPDATE-SuperSU, e.g. SuperSU-v2.79-20161211114519.zip
Note: if you're patching Nougat firmware, you may want to use phh's superuser instead of SuperSU due to potential battery drain. See rootkernel thread for more info. If you use phh's superuser, you will need to install the apk from the Play store after Step 8.
(optional) Download the latest Xposed framework ZIP file and copy it to the rootkernel folder. Do NOT unzip it!
Note: this only works with rootkernel v5.0 or later, if you're using an earlier version of the rootkernel tool, skip this and skip Step 9
At time of this edit (2017/2/22), Xposed does not support Android 7.0 (Nougat), so if you're trying to patch a Nougat kernel, do not include xposed. You can check the official Xposed thread for latest announcements to see if it's supported
Open command prompt and navigate to the rootkernel directory
Enter the following command:
Code:
rootkernel kernel.elf boot.img
You will be prompted to make a series of choices, including whether you want to install SuperSU and Xposed. Type Y for all of them.
If you didn't see the prompt for SuperSU (required) or Xposed (optional), check the filename of the ZIP files. Remember they're case sensitive.
You should now have a boot.img file in the rootkernel folder, that is your rooted kernel
Step 7 - Flash the DRM keys (one-time procedure)
tobias.waldvogel (rootkernel developer) said:
Flashing this file with flashtool will write your device key to an alternative unit, from where the drmfix library will pick it up.
This is a one-time task. It will survive a complete reset of the phone or Android system upgrade.
Click to expand...
Click to collapse
Copy the TA backup file TA_E5823.img from Step 1 to the rootkernel folder, then enter the following command in command prompt:
Code:
flash_dk TA_E5823.img DK.ftf
This will create a DK.ftf file in the rootkernel folder
Open Flashtool > Click the lightning symbol > Flashmode > Source folder > Locate the rootkernel folder
"Sony Xperia Z5 Compact" should appear under Firmwares, expand the arrows until you see DeviceKey and 1.0. Select 1.0, click Flash and wait for an instruction prompt to pop up
Hold the VOLUME DOWN button while connecting the micro USB end to your phone. Keep the VOL DOWN button held until the prompt disappears, which indicates that Flashtool has detected it and is correctly in flashmode.
Wait until operation is completed, then unplug the cable from your phone. Do not power on yet
Step 8 - Flash the kernel
Hold the VOLUME UP button and plug in the micro USB cable. Wait until the LED indicator turns blue, then release the VOL UP button.
Enter the following command in command prompt to flash the rooted kernel:
Code:
fastboot flash boot boot.img
After completion, congratulations, you've successfully rooted your phone!
Now you can turn on your phone, the first boot will take a very long time to initialize, don't worry.
If you see the boot animation for more than 30 minutes, then it's time to worry. First try again from Step 6, and if you still can't complete boot, go up a step starting from Step 5. If that still fails, start over from Step 3.
Step 9 - Finish installation of Xposed (optional)
In Step 6, if you chose to include the Xposed ZIP file, which means you want to install Xposed, then there's one more step to complete the installation.
Download the unofficial Material Design Xposed Installer.
Currently, this is the only Xposed Installer that works with the systemless Xposed integration method used by the rootkernel tool. Using the official Xposed Installer will not work.
Go to Settings > Security > Unknown sources > Toggle ON
Copy the Xposed Installer apk to your phone and install it.
Done!
Personal list of xposed modules to install for self reference. This is in no way a recommendation list, your preferences will vary.
Amplify
Android Phone Vibrator
App Locale
BootManager
Disable Low Battery Notifications
DynamicAlarmIcon 2
HideBatteryLowAlert
Keep Trash (broken at the moment)
Lockscreen Album Art Remover
MinMinGuard
NeoPowerMenu
NoHeadsetNotification
Ringer and Notification Volume Unlink
RootCloak
Use USB for Marshmallow V 1.2
XperiaFMwoHS
Xposed Torch: Physical keys
Youtube AdAway
Bonus - How to unroot/fully restore DRM/return to 100% factory state
Thank you for taking the time to write this guide!
best guide for root, thanks!
Fantastic guide, Thank you very much for that!
I had trouble getting the latest version of flashtool (09231) to work (mac and PC). It froze when I was trying to create the new bundle.
After downloading the older version (09186) it worked without problems.
However, currently I am stuck at step 6, running cmd 'rootkernel kernel.elf boot.img':
I get the message:
Code:
Rootkernel V5.11
- Unpacking kernel
error: Android boot magic not found
Unknown boot image format
Aborting
UPDATE:
I found the reason for the img file creation failure.
I was not patient enough in copying the kernel.elf file over. While the flashtool says file with size X created it was still compiling and only a minute later or so finished writing the file. In other words, I copied over the 'unfinished' kernel.elf and that's what caused the issue.
Trying to boot now
Thanks again for this nice guide!
Cheers,
Malcolm
Hey Malcolm, did you manage to complete the process successfully?
good news
thanks for your help. very good tutorial, realy made easy to understand
successfully rooted my nougat z5c with this,
you the best thanks
brokich said:
Hey Malcolm, did you manage to complete the process successfully?
Click to expand...
Click to collapse
Hi Brokich,
Unfortunately not (yet).
After finishing step 7 my device is stuck at the bootloader
I've tried now several times re-flashing (steps 5-7) but unfortunately no luck yet...Will try to repeat the whole procedure over the next days again.
I am getting problem with flashing kernel :
FAILED (remote: Command not allowed) my bootloader status was unknown at first, then I got unlock code at sony website, then it said my bootloader is unlocked, followed your tutorial and now I not able to flash kernel..
Hello guys
On step 5 i get this error
5/031/2017 13:31:03 - INFO - Device connected in flash mode
05/031/2017 13:31:28 - INFO - Selected Bundle for Sony Xperia Z5 Compact(E5823). FW release : 1298-5497_32.2.A.5.11_R13C. Customization : Customized UK
05/031/2017 13:31:28 - INFO - Preparing files for flashing
05/033/2017 13:33:12 - INFO - Please connect your device into flashmode.
05/033/2017 13:33:13 - INFO - Opening device for R/W
05/033/2017 13:33:14 - INFO - Start Flashing
05/033/2017 13:33:14 - INFO - Processing loader.sin
05/033/2017 13:33:14 - INFO - Checking header
05/033/2017 13:33:14 - ERROR - Processing of loader.sin finished with errors.
05/033/2017 13:33:14 - INFO - Ending flash session
05/033/2017 13:33:14 - ERROR - null
05/033/2017 13:33:14 - ERROR - Error flashing. Aborted
05/033/2017 13:33:14 - INFO - Device connected in flash mode
Any idea why ?
notabene said:
I am getting problem with flashing kernel :
FAILED (remote: Command not allowed) my bootloader status was unknown at first, then I got unlock code at sony website, then it said my bootloader is unlocked, followed your tutorial and now I not able to flash kernel..
Click to expand...
Click to collapse
Did you backup your TA-partition before the bootloader status was unknown?
zegovernator said:
Did you backup your TA-partition before the bootloader status was unknown?
Click to expand...
Click to collapse
Yes, why?
---------- Post added at 01:13 PM ---------- Previous post was at 12:49 PM ----------
zegovernator said:
Did you backup your TA-partition before the bootloader status was unknown?
Click to expand...
Click to collapse
I was able to flash FTF file. But not the kernel.
notabene said:
yes.
Click to expand...
Click to collapse
Okay. It sounds like you wiped your TA partition. On which firmware did you backup your TA? Lollipop using Iovy.root or Marshmallow using this guide? I experienced the same problem once. I recovered my TA partition via Iovy.root. (because back then the only possibility was to downgrade to LP and then backup/restore TA).
Check if the service menue states:
[Bootloader unlock allowed:no] and [Remote Lock State: Locked]
If so, restore TA.
zegovernator said:
Okay. It sounds like you wiped your TA partition. On which firmware did you backup your TA? Lollipop using Iovy.root or Marshmallow using this guide? I experienced the same problem once. I recovered my TA partition via Iovy.root. (because back then the only possibility was to downgrade to LP and then backup/restore TA).
Check if the service menue states:
[Bootloader unlock allowed:no] and [Remote Lock State: Locked]
If so, restore TA.
Click to expand...
Click to collapse
This guide, latest firmware 32.2.A.5.11.
Currently my phone stucked at after boot in TM logo.
Trying to repair via PC Companion
Phone booted. Will check if bootloader is really unlocked.
Bootloader unlock allowed : yes
Remote Lock state : UnLockd
Checked DRM all OK
notabene said:
This guide, latest firmware 32.2.A.5.11.
Currently my phone stucked at after boot in TM logo.
Trying to repair via PC Companion
Phone booted. Will check if bootloader is really unlocked.
Click to expand...
Click to collapse
Flash a .tft from the MM version your backed up your TA image from. When flashing, ensure to tick everything under wipe except TA Misc.
Well finally was able to do all the steps, but phone wont boot. Stucked in Sony logo, led is yellow and then power off..
Yeah, same here.
Tried now multiple times but it always gets stuck at the xperia screen with orange/yellow LED
One thing that I noticed was "ERROR - root : this bundle is not valid" when I start to create the bundle. Straight after locating the custom firmware that I dowloaded with Xperifirm the message comes up in the log. Thought that this is not an issue though, or is it?
Cheers,
Malcolm
Need to use phone tomorrow, how can i revert to stock for a while since I cannot do it throught Xperia companion?
---------- Post added at 03:37 PM ---------- Previous post was at 03:26 PM ----------
Malcolm143 said:
Yeah, same here.
Tried now multiple times but it always gets stuck at the xperia screen with orange/yellow LED
One thing that I noticed was "ERROR - root : this bundle is not valid" when I start to create the bundle. Straight after locating the custom firmware that I dowloaded with Xperifirm the message comes up in the log. Thought that this is not an issue though, or is it?
Cheers,
Malcolm
Click to expand...
Click to collapse
Did you use customized firmware? I did not, i used Tmobile CZ
Now with bootloader unlocked even PC Companion doesnt work..
So the problem is after flashing custom kernel with rootkernel+DRM fix.
So after hours of trying from step 5 with different settings for kernel, I ended up with stock rom flashed via flashtool..
tried to flash back DRM keys from Dirty cow TA Backup, using this command flash_dk TA_E5823.img DK.ftf but when rebooted in service menu drm keys are still gone..
EDIT:
Seems like there is more users with same issue with Z5C and latest rootkernel
https://forum.xda-developers.com/xp...matic-repack-stock-kernel-dm-t3301605/page200
Hmm, I never ran into the stuck at boot problem, and I just successfully flashed a new phone on the same day I posted the guide. That said, I was using v5.0 of the rootkernel tool, not the latest v5.11. The rootkernel developer mentioned that there's battery drain problems with v5.11, so I decided to use the older v5.0 that helped me root two Z5C's several times in the past. Try patching the kernel again using v5.0 and see if that fixes it.
Note that v5.0 only supports up to firmware version 32.A.0.253 out of the box, you will need to make the following modification to support up to 32.2.A.5.11:
Download and unzip rootkernel v5.11 and v5.0.
Open folder \rootkernel_v5.11_Windows_Linux\Android\twrp_common_kmodules
Copy and overwrite all 7 sub-folders (folder names look like 3.10.49-perf-g83fc9bc etc.) to \rootkernel_v5.0_Windows_Linux\Android\twrp_common_kmodules
Then patch the kernel using v5.0 tool.
mhaha said:
Hmm, I never ran into the stuck at boot problem, and I just successfully flashed a new phone on the same day I posted the guide. That said, I was using v5.0 of the rootkernel tool, not the latest v5.11. The rootkernel developer mentioned that there's battery drain problems with v5.11, so I decided to use the older v5.0 that helped me root two Z5C's several times in the past. Try patching the kernel again using v5.0 and see if that fixes it.
Note that v5.0 only supports up to firmware version 32.A.0.253 out of the box, you will need to make the following modification to support up to 32.2.A.5.11:
Download and unzip rootkernel v5.11 and v5.0.
Open folder \rootkernel_v5.11_Windows_Linux\Android\twrp_common_kmodules
Copy and overwrite all 7 sub-folders (folder names look like 3.10.49-perf-g83fc9bc etc.) to \rootkernel_v5.0_Windows_Linux\Android\twrp_common_kmodules
Then patch the kernel using v5.0 tool.
Click to expand...
Click to collapse
Thanks, will try in the evening.
Just to know, if I'm upgrading from previous firmware version, do I have to do all steps or I can start from step 4 (flashing ftf file)?