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
If you are looking to flash stock firmware, custom kernel, custom recovery, root via supersu, and remove bloatware for E6883 model only, you came to the right thread, otherwise, go away. Make sure you have at least 50% battery before proceeding. I'm assuming you are running Microsoft Windows 10 Home x64 and have installed all required Google USB Drivers, Android SDK (for fastboot), and an unlocked bootloader. If you have not done this yet, install them first so that your device will be recognized. Don't forget to enable "USB debugging" and "OEM unlocking" from the "Developer options" menu on your device. Come on, you can't be that noob. If you don't even know what that means, you don't belong here and chances are, you will end up with a bricked phone.
/* YOUR WARRANTY IS NOW VOID */
Download all necessary files, preferably the latest version.
Xperia Firmware Downloader
Sony Mobile Flasher by Androxyde
Custom Kernel - Rename the file as boot.img and move it to "C:\Android\SDK\platform-tools\boot.img"
Custom Recovery - Rename the file as recovery.img and move it to "C:\Android\SDK\platform-tools\recovery.img"
SuperSU Stable - Rename the file as supersu.zip and move it to your external SD card.
[STEP 1] Using the Xperia Firmware Downloader.
1. Run "XperiFirm.exe" as Administrator.
2. Select "Xperia Z5 Premium Satsiki" > "E6883 dual" from the list.
3. Select your preferred firmware and download.
4. DONE.
[STEP 2] Using the Sony Mobile Flasher by Androxyde.
// How to prepare a flashable .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Select "Tools" > "Bundles" > "Create" from the menu.
3. "Select source folder" where your firmware folder is located.
4. Double-click "Device" editbox and select "E68XX Sony Xperia Z5 Premium" > "E6883".
5. Fill in the "Branding" editbox.
6. Fill in the "Version" editbox.
7. Select everything from the "folder list" and move them to "Firmware Content".
8. Click on the "Create" button.
9. DONE.
// How to start flashing a .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Click on the "Thunder toolbar button" and choose "Flashmode".
3. Select your "Firmware".
4. Click on the checkboxes to wipe everything and don't exclude anything except SIMLOCK (you can't touch this).
5. Click on the "Flash" button.
6. DONE.
[STEP 3] Flashing the custom kernel.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash boot boot.img"
6. DONE.
[STEP 4] Flashing the custom recovery. - Actually, there is no need for this step. The custom kernel provided above already included TWRP 3, so this is just to show you how to flash a custom recovery. Thanks, @YasuHamed
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash recovery recovery.img"
6. DONE.
[STEP 5] Flashing the SuperSU, hence rooting your device.
1. Turn off your device.
2. Turn on your device.
3. As soon as your device is powering on, press on the "volume-up rocker" continuously until you load TWRP.
4. Flash SuperSU from your SD card.
5. Reboot system.
6. DONE.
Congrats! :laugh:
Now that you have root access, the next part is to remove bloatware but I will post this later on because I need to do some more research just to confirm it won't have FCs in the future. Removing bloatware is rather self-explanatory and depends on your personal preferences. Like me, I would delete all of Google and Sony apps to bare minimum but some people prefer leaving Google Maps or Sony Smart Connect on their phone. I'll see you on the next episode, to be continued...
Reserved for battery management, tips and tricks.
cglegion said:
If you are looking to flash stock firmware, custom kernel, custom recovery, root via supersu, and remove bloatware for E6883 model only, you came to the right thread, otherwise, go away. Make sure you have at least 50% battery before proceeding. I'm assuming you are running Microsoft Windows 10 Home x64 and have installed all required Google USB Drivers, Android SDK (for fastboot), and an unlocked bootloader. If you have not done this yet, install them first so that your device will be recognized. Don't forget to enable "USB debugging" and "OEM unlocking" from the "Developer options" menu on your device. Come on, you can't be that noob. If you don't even know what that means, you don't belong here and chances are, you will end up with a bricked phone.
/* YOUR WARRANTY IS NOW VOID */
Download all necessary files, preferably the latest version.
Xperia Firmware Downloader
Sony Mobile Flasher by Androxyde
Custom Kernel - Rename the file as boot.img and move it to "C:\Android\SDK\platform-tools\boot.img"
Custom Recovery - Rename the file as recovery.img and move it to "C:\Android\SDK\platform-tools\recovery.img"
SuperSU Stable - Rename the file as supersu.zip and move it to your external SD card.
[STEP 1] Using the Xperia Firmware Downloader.
1. Run "XperiFirm.exe" as Administrator.
2. Select "Xperia Z5 Premium Satsiki" > "E6883 dual" from the list.
3. Select your preferred firmware and download.
4. DONE.
[STEP 2] Using the Sony Mobile Flasher by Androxyde.
// How to prepare a flashable .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Select "Tools" > "Bundles" > "Create" from the menu.
3. "Select source folder" where your firmware folder is located.
4. Double-click "Device" editbox and select "E68XX Sony Xperia Z5 Premium" > "E6883".
5. Fill in the "Branding" editbox.
6. Fill in the "Version" editbox.
7. Select everything from the "folder list" and move them to "Firmware Content".
8. Click on the "Create" button.
9. DONE.
// How to start flashing a .ftf file?
1. Run "Sony Mobile Flasher by Androxyde.exe" as Administrator.
2. Click on the "Thunder toolbar button" and choose "Flashmode".
3. Select your "Firmware".
4. Click on the checkboxes to wipe everything and don't exclude anything except SIMLOCK (you can't touch this).
5. Click on the "Flash" button.
6. DONE.
[STEP 3] Flashing the custom kernel.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash boot boot.img"
6. DONE.
[STEP 4] Flashing the custom recovery.
1. Run "Command Prompt" as Administrator.
2. Go to "cd C:\Android\SDK\platform-tools"
3. Turn off your device.
4. Plug in your USB cable while holding on to the "volume-up rocker" until you see a blue LED indicator on the top left of your device. You are now ready to use the fastboot function.
5. Type "fastboot flash recovery recovery.img"
6. DONE.
[STEP 5] Flashing the SuperSU, hence rooting your device.
1. Turn off your device.
2. Turn on your device.
3. As soon as your device is powering on, press on the "volume-up rocker" continuously until you load TWRP.
4. Flash SuperSU from your SD card.
5. Reboot system.
6. DONE.
Congrats! :laugh:
Click to expand...
Click to collapse
the customer kernals by @khab.bros already have recovery installed,
Correct @YasuHamed, and it's newer than the one I provided. I just want new people to know the idea of flashing custom recovery on this device. Thanks for the heads up. It's a shame there is so less development going on for Z5 Premium Dual compared to other flagship devices such as Samsung... I hope we see more custom roms port in the near future.
@cglegion
Maybe minimal adb and fastboot tool would be better than installing the entire android SDK package... It's a small utility around 2 mb only , since you're doing a noob friendly guide it might be more appropriate...
cglegion said:
Correct @YasuHamed, and it's newer than the one I provided. I just want new people to know the idea of flashing custom recovery on this device. Thanks for the heads up. It's a shame there is so less development going on for Z5 Premium Dual compared to other flagship devices such as Samsung... I hope we see more custom roms port in the near future.
Click to expand...
Click to collapse
the way sony is behind in specs, I think in upcoming days the development side of xperia will suffer the most as the sales goes down!
in 2016 we have mobiles reaching specs such as 2.2ghz with 6gb ram and the NEWEST xperia X series has 1.5gb ~ 2gb RAM ONLY~
-DM- said:
@cglegion
Maybe minimal adb and fastboot tool would be better than installing the entire android SDK package... It's a small utility around 2 mb only , since you're doing a noob friendly guide it might be more appropriate...
Click to expand...
Click to collapse
You're right @-DM-, the fact that I recommend using Android SDK was the ability to install packages automatically for example the Google USB Driver though the SDK manager and not solely for fastboot functionality. Some newbies might not even have appropriate drivers installed on their machine so their device won't be recognized hence a simple problem will lead to another problem. But of course, using minimal adb and fastboot is another noob-friendly way (which is also less in size) compared to the 100mb + Android SDK. Thanks, for the heads up too and making this thread a more noob-friendly one! :laugh:
Btw, @YasuHamed do you somehow know how to create a build.prop and updater-script for a stock firmware that I've just tweaked (delete bloatware apk and add some mods and third party apks)? I need to make it flashable via twrp but lack example for this device. Thanks!
cglegion said:
Btw, @YasuHamed do you somehow know how to create a build.prop and updater-script for a stock firmware that I've just tweaked (delete bloatware apk and add some mods and third party apks)? I need to make it flashable via twrp but lack example for this device. Thanks!
Click to expand...
Click to collapse
as far as I have studied, there is no DIRECT way doing that in MM
however for sake of argument, lets say you are using your z5 at 5.x.x
the zips can be flashed if you are REPACKING your STOCK KERNAL. (the post of Khab.bros) is actually points out to
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
here if you have original FTF file of your z5, EXTRACT kernel.sin to kernal.els (using flashtool) then by running it through ROOTKERNELv5.0, you can add custom recovery and other flashable zips (after disabling dm-variety / SONYRIC)
but to remove BLOATWARE From your stockROM,
you must EXTRACT SYSTEM.sin, from FTF file, Dump it fully to location, RESAVE it using Ext2Explorer, now u will have APP folder, see which apk you want to remove, when you are done, repack everything to SYSTEM.sin and now MODIFIED STOCKROM has been created.
i remember doing id for my xperia C6603 back in 2013
http://forum.xda-developers.com/showthread.php?t=1931585
the tutorial was also very helpful https://www.youtube.com/watch?v=DpYxMRlBrR8
btw, I did all that just to learn, later i never did all this because some how i love the xperia stockroms and after rooting you can remove many bloatware and change system app to user app and remove them at your ease...
Command Prompt
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
shaxta said:
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
Click to expand...
Click to collapse
Make sure you have unlocked your bootloader before following this guide and just to inform you again this guide is for E6883.
Yeah I figured it out, the only problem was the fastboot drives weren't installed correctly for some reason windows 10 didn't allow it, also it was having trouble finding the boot.img so I just dragged the fastboot.exe and the boot.img into the command instead and it worked.
All in all great guide, thanks.
YasuHamed said:
as far as I have studied, there is no DIRECT way doing that in MM
however for sake of argument, lets say you are using your z5 at 5.x.x
the zips can be flashed if you are REPACKING your STOCK KERNAL. (the post of Khab.bros) is actually points out to
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
here if you have original FTF file of your z5, EXTRACT kernel.sin to kernal.els (using flashtool) then by running it through ROOTKERNELv5.0, you can add custom recovery and other flashable zips (after disabling dm-variety / SONYRIC)
but to remove BLOATWARE From your stockROM,
you must EXTRACT SYSTEM.sin, from FTF file, Dump it fully to location, RESAVE it using Ext2Explorer, now u will have APP folder, see which apk you want to remove, when you are done, repack everything to SYSTEM.sin and now MODIFIED STOCKROM has been created.
i remember doing id for my xperia C6603 back in 2013
http://forum.xda-developers.com/showthread.php?t=1931585
the tutorial was also very helpful https://www.youtube.com/watch?v=DpYxMRlBrR8
btw, I did all that just to learn, later i never did all this because some how i love the xperia stockroms and after rooting you can remove many bloatware and change system app to user app and remove them at your ease...
Click to expand...
Click to collapse
Hey, bro @YasuHamed managed to make an Aroma installer for myself (learned this from scratch) but now I'm having problem making the updater-script file because I'm not sure how to mount and extract the system files also the command to patch (a repacked) boot.img kernel. From my research, dev block for E6883 are as follow:
1. /cache /data / sdcard = mmcblk0p42
2. /external_sd = mmcblk1p1
3. /system = mmcblk0p43
Can you help me? I'm very close to releasing a custom ROM based on stock firmware without bloatware. Where do I go about... I've been searching all over Google and XDA and has not found answers for E6883 specific problems.
shaxta said:
Hi i successfully flashed the tft file and now im up to using the command prompt so i shift+right clicked and opened a command window in the platform tools folder where the boot.img and recovery.img are and entered the command "flashboot flash boot boot.img" and it comes up saying "error: cannot load boot.img"
I dont know what to do here. please help.
Click to expand...
Click to collapse
use flahstool
---------- Post added at 11:15 AM ---------- Previous post was at 11:13 AM ----------
use flashtool
---------- Post added at 11:34 AM ---------- Previous post was at 11:15 AM ----------
cglegion said:
Hey, bro @YasuHamed managed to make an Aroma installer for myself (learned this from scratch) but now I'm having problem making the updater-script file because I'm not sure how to mount and extract the system files also the command to patch (a repacked) boot.img kernel. From my research, dev block for E6883 are as follow:
1. /cache /data / sdcard = mmcblk0p42
2. /external_sd = mmcblk1p1
3. /system = mmcblk0p43
Can you help me? I'm very close to releasing a custom ROM based on stock firmware without bloatware. Where do I go about... I've been searching all over Google and XDA and has not found answers for E6883 specific problems.
Click to expand...
Click to collapse
although i never liked aroma and i won't usually recommend custom roms specially for xperia... but since you have came this far,
lets say under APK foler you removed many bloatware and also updated
you must repack you SYSTEM folder (only) back to ROOM.zip (originally extracted from ftf file using ext2explorer)
then you need to apply mods,
https://www.youtube.com/watch?v=FdhUK_Ds4Fo (part 2, deleting bloatware) / finding MODS and repacking
http://forum.xda-developers.com/showthread.php?t=1363460 (tutorial about updater script modification by notepad++ )
however just remember what ever studies i did, for android 6.0.1 the prf creator wont work,
but you can try (PRF creator)
http://forum.xda-developers.com/showthread.php?t=1363460
convert your boot.img to kernel.sin and recreate your PRF creator (as mentioned above)
OR keep the custom rom ftf and BOOT.img SAPERATE as many custom roms does that
1. cynogenmod 12+
3. Miui 5 onwards
have boot+recovery file saperate and Rom saperate to flash.
the only reason i could understand is because they flash their system via recovery. if your aroma stock has xd recovery you can keep the flashable zip to install as system ORRRR keep it as FTF file to be flash and then kernal to be flashed saperate
Thanks for this guide I just wish to have root on locked BL...
your pc should have install adb and fast boot drivers imp . and pda net driver just search on google . and install it . after that follow the steps:good::good:
very simple for honor4x Che1-L04 indian
1.your phone shoud be unlock boot loader imp
2.reboot your phone in to fast boot mod
3.just use HuaweiUpdateExtractor.
just go to this link
http://www.mediafire.com/file/z8436c56ccy69fb/HuaweiUpdateExtractor_0.9.9.3_Setup(2).zip
and download it .
4.in update extractor
select your firmware file . *Honor 4X_Firmware_Che1-L04_Android 6.0.1_EMUI 4.0_C675B511_India_Flipkart * from your pc where you have save it
Select all files and right click. Choose Extract selected from the context menu.
Choose the ouput folder and press OK. Or just right click on the list and select Extract all, choose the output folder again and press OK.
5.download flash all tool from below link
http://www.mediafire.com/file/rcw8tojyhlh6wqk/FLASH_ALL.zip
6. extract the flash all tool and Paste all the extracted flash file from the huwei updateextractor in the same folder
just reboot your phone in to bootloader mode and just click flash all option . thats it .
after when your phone is rebooted . thats it :good::good::good::laugh:
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)?
Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel2.img
You will boot with root but modules disabled. If something additional is needed, once booted to core-only, unzip the attached zip onto your pc where you can run ADB/fastboot and run the bat file. It will push .disable_magisk to your cache folder so that your modules will be disabled even after a reboot (zip says crosshatch but will work on any phone)
Boot image uploaded 11-24-19
https://www.androidfilehost.com/?fid=4349826312261644460