Related
Introduction
With every new release in Xperia lineup, the story repeats: device ships with latest security fixes, locked system partition, without root access. If you bought it from a retail store or without a contract, your device's bootloader can be unlocked and you can start messing with it (getting a custom recovery, gaining root access, etc) but as a trade off, your DRM keys are gone and some stock apps/features stops working. Even worse, if you bought your device from a carrier or with a contract it probably came with a permanently locked bootloader and there's nothing you can do about.
However, there's no software free of bugs, sooner or later an exploitable security bug appears and some talented developers may use that to get root access in locked devices. And time has come to Xperia E3, now the community have working exploits capable of getting root access on locked bootloaders and this tutorial will help you achieving that. Let's get started!
Overview
First off, Xperia E3 was released in several variants across the globe and the process differs a bit between them. Starting now, we'll group the variants in two groups:
• If you have D2202 or D2212, I'll refer to your device as HSPA variant
• If you have D2203, D2206 or D2243, I'll refer to them as LTE variant
This guide is mainly aimed at HSPA variants where the process involves downgrading to a initial firmware, running a modded version of giefroot and then using another tool (dd Flasher) to update to the latest firmware version without losing root access.
If you have a LTE variant, unfortunately, the modded version of giefroot we'll use to get root won't work but thanks to @nortonex you still can get root with a slight different process, involving cross flashing an exploitable version of Xperia M2 kernel to get root access and then reverting to the stock kernel and applying a patch to disable RIC protection (it's a Sony "feature" that prevents writing to system partition, even with root, similar to HTC's S-ON/S-OFF flags). So, if you have one of the LTE variants, follow his guide...
Requirements
To get root:
• Exploitable firmware (must be 18.4.B.1.20 -- region/market doesn't matter)
• FlashTool (0.9.18.4 or newer)
• Modded giefroot v3 (attached below)
To update to latest firmware after getting root:
• dd Flasher
• XperiFirm (optional)
Preparing the device
To start, we need to downgrade your device to the old 18.4.B.1.20 firmware, the only one exploitable by giefroot, so, if you need, make a backup of your device's data first, your content will be wiped during the downgrade. You can also use any other FTF that matches your region/market as long as it's 18.4.B.1.20...
• If your device is powered on, turn it off and disconnect USB cable (if connected) now. Now, start FlashTool and click in the Thunderbolt icon, then choose Flash Mode and press OK
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
• If needed, click on the "..." button and point FlashTool to the folder where you've downloaded the FTF linked in the Requirements section of this Tutorial. Then, choose the firmware in the list, mark "No final verification" and "Reset customizations" and press Flash
• Wait until FlashTool prepare the FTF to flash. When it's done, the screen below will appear. Now, with your device turned off, hold Volume Down button and plug the USB cable while you're holding the button. If you did right, the notification LED will briefly flash in green/red and FlashTool should start flashing the firmware
• After the flashing process finishes, close FlashTool, disconnect your device and turn it on. Remember that the first boot will take longer (5-10 minutes), that's normal.
Running the exploit
Now your device is running the exploitable firmware version, let's set up it to run the exploit and get root access...
On phone side:
• We need to "unlock" developer settings. You can do that by going to Settings => About phone and then tapping "Build Number" 7 times
• Now we can go to Settings => Developer Options. Here you should enable "Stay awake", "USB debugging" and "Allow mock locations". Then, disable "Verify apps over USB"
Now on computer side:
• Plug your device in the computer
• Extract the modded giefroot somewhere (it's attached in the end of this thread) and launch it by opening "install.bat" (or, if you're using Linux/Mac, start "install.sh" from Terminal)
• In your device, a small popup about ADB connection will appear, make sure you mark "always allow connection from this computer" and press OK
• From here, just wait until giefroot finishes. Your phone will reboot automatically, that's normal
Note: Sometimes you may not get root in the first attempt, that's normal, just run giefroot more two or three times and it'll eventually work
And that's it. Your device is now fully rooted, however, we are stuck in an older firmware version.
Update procedure
There's more than one way to upgrade to the latest firmware without losing root access and I'll try to explain all methods I know. Before continuing we'll regroup devices accordingly to the bootloader unlockability (you can check your device's bootloader state by entering *#*#7378423#*#* in the Dialer then going to Service info => Configuration)
If your device's bootloader is permanently locked (Bootloader Unlock Allowed: No), your only known option will be using dd Flasher (explained in the next chapter). If your device's bootloader is unlockable (Bootloader Unlock Allowed: Yes) then you can also use the unlock/root/relock procedure which involves backing up your TA partition with Backup TA, unlocking your bootloader, updating to the latest firmware normally (either with FlashTool or Sony PC Companion), flashing a custom recovery, installing SuperSU through it and then relocking your bootloader (restoring your DRM keys too) with the TA backup you took earlier.
I won't explain the unlock/root/relock procedure in details since it's a little trickier and won't work for devices with permanently locked bootloader, which is the main purpose of this tutorial. However, I attached a stripped down version of giefroot which only installs the wp_mod kernel module, in order to disable write protection to system partition. If you updated to the latest firmware with dd Flasher, there's no need to apply this patch, dd Flasher will automatically handle that for you, I posted that focused more on advanced users that opt to use unlock/root/relock procedure and are getting trouble when trying to write to system partition...
Using dd Flasher
This chapter is a little longer and sometimes you need to jump into different routes, because of that, it's splitted in smaller sections and jump notes in the start of each section...
Downloading latest firmware
Note: if you already have a FTF of the latest firmware for your device or if you prefer using XperiFirm to get latest firmware, skip this section and go directly to "Preparing system image"
First off, we need to get a FTF of the latest available firmware for your device/market. Below I explain how we get it using FlashTool, you can do that with XperiFirm or just download a FTF someone else have uploaded too. I'm focusing on FlashTool here since it's the only option for people using Linux/Mac (forget it, apparently XperiFirm also works on Linux/Mac now)
• Open FlashTool and go to Devices => Check Updates. Then, locate Xperia E3 in the list and double click on it
• Here, a small window with tabs for each variant will show. Go to the tab that corresponds to your device's variant, then double click the matching region/market of your device to check latest firmware version available in that region. After that, double click it again so it starts downloading the firmware from Sony servers
• After download and decrypt is finished, bundle creator will open automatically (you can also open it manually through Tools => Bundle creator). Most of the info here will be already entered, we only need to choose all files present in the panel from the left and click the little arrow to move all of them to the right panel. After that, press "Create" and wait until bundle creation (FTF) is finished. After that we're gonna extract system.ext4 (dd Flasher will need it), it's explained in the next section...
Preparing system image
Note: I'm assuming that you already have access to system.sin (and you have if you followed the instructions from previous section to get your FTF). If you don't have access to system.sin, you can extract it directly from the FTF file by opening it with WinRAR/7-Zip or anything capable of extracting ZIP files (yes, FTFs are just regular ZIP files with different extension)
At that point, we have a FTF of the latest firmware, however, dd Flasher doesn't work with FTF files directly, just with raw partition dumps, and we'll extract it from the update now
• Open FlashTool and go to Tools => Sin Editor. In the small window that will appear, click on "..." and point it to system.sin, then, press "Extract Data" (if you downloaded your firmware following the instructions from previous section, a copy of system.sin will be located in C:\Users\<username>\.flashtool\firmwares\Downloads\D22xx_xxxxxxxxx_xxxxxx\decrypted)
• After extraction finishes, a new file named system.ext4 will be created in the same folder where system.sin is. Extract dd Flasher somewhere and move system.ext4 to the same folder, it must be named system.ext4 (rename it if necessary, otherwise dd Flasher will fail) and should be next to dd_flasher.bat/dd_flasher.sh
Flashing new system image
Here's where the magic occurs. First off, make sure FlashTool is closed, otherwise it'll interfere with ADB connection and dd Flasher may fail. Then, follow the procedure:
• Start dd Flasher by opening dd_flasher.bat (or if you're on Linux, launch dd_flasher.sh from a Terminal -- sorry Mac users, dd Flasher isn't compatible with your OS yet)
• If everything is right, dd Flasher should ask you where the system image should be pushed. Remember that the selected location should have enough space to store system.ext4 before (and if you're pushing to SD Card, make sure phone's connection mode is MTP, otherwise dd Flasher will fail)
• After you selected the storage device, dd Flasher will do its work. Just wait until it's done, it'll take a while (about 10 minutes)
• After the process finishes, you should unplug your phone and turn it off through the Off switch found in the back, next to the SIM card (this step is very important!) and don't turn it on yet
Flashing the remaining components from the FTF
That's the last step, in current state your device has the system partition of the latest firmware version with su binaries (to get root access) but kernel, modem, baseband, etc. still are from the old firmware version and because of that it won't boot properly. Let's fix that:
• Start FlashTool and click in the Thunderbolt icon, then choose Flash Mode and press OK
• If needed, click on the "..." button and point FlashTool to the folder where you've downloaded the FTF of the latest update. Then, choose the firmware in the list, mark "Reset customizations" and make absolutely sure you mark "SYSTEM" in the Exclude panel too (if you forget to mark it, root will be lost and you'll need to start the whole tutorial again from beginning). After double checking, press Flash
• Wait until FlashTool prepare the FTF to flash. When it's done, the screen below will appear. Now, with your device turned off, hold Volume Down button and plug the USB cable while you're holding the button. If you did right, the notification LED will briefly flash in green/red and FlashTool should start flashing the firmware
• After the flashing process finishes, close FlashTool, disconnect your device and turn it on. Remember that the first boot will take longer (5-10 minutes), that's normal.
And this is the end of tutorial, your device will now be running the latest firmware version with full root access. Congratulations!
Frequently Asked Questions
Q: I have a D2202 variant, wouldn't crossflashing D2212 firmware brick it?
A: No, your device won't brick since the only difference between D2202 and D2212 is the dual SIM support. In the worst scenario you would see options and icons for second SIM functionality but they would disappear again after updating to the latest D2202 firmware with dd Flasher.
Q: I have a D2202 variant but now I'm stuck with D2212 firmware. How do I switch back to D2202 firmware without losing root?
A: Just follow "Using dd Flasher" chapter but instead of downloading firmware for D2212, download for D2202. If you already did "Using dd Flasher" chapter with D2212 firmware you can repeat this chapter but now selecting D2202 firmware.
Q: Help! I don't have a micro SD card and dd Flasher keeps failing to push system image. What sould I do?
A: The system image is generally around 1 GB but it can be larger depending of the market/branding. If you don't have enough space in Internal Storage, dd Flasher will fail. What you can do is downloading Titanium Backup or another similar app to remove as many bloatware as you can, until you have enough free space to temporarily store system image in Internal Storage.
Credits
Kudos to @zxz0O0 for giefroot and its promptly and helpful collaboration to get Xperia E3 working with it. Kudos also to @MohammadAG for its modded wp_mod kernel module which is used in giefroot and into the stripped down RIC disabler attached below. I would also like to thanks everyone from [Q] Root with locked bootloader? who helped directly or indirectly into this.
Downloads
Screenshots
Will upgrading cause lose to data and apps ?
pranayberry said:
Will upgrading cause lose to data and apps ?
Click to expand...
Click to collapse
By default, yes, everything will be wiped (except SD Card). You can try doing the downgrade/upgrade without wiping data by unchecking "Wipe DATA" option in FlashTool but it's not guaranteed to work (especially at the downgrade step)...
Will this firmware d2212 work on d2202
Sent from my D2202 using XDA Free mobile app
sjunaid1997 said:
Will this firmware d2212 work on d2202
Click to expand...
Click to collapse
Yes, it'll work. However, it's only needed to run the exploit. After getting root you can use a FTF from D2202 with dd Flasher to go back to official firmware, maintaining root access...
Thanks will try it tomorrow and let u know
Sent from my D2202 using XDA Free mobile app
---------- Post added at 08:21 PM ---------- Previous post was at 08:18 PM ----------
What if after rooting on d2212 firmware i back up my ta partion and unlock my bootloader then flash d2202 firmware then root it again
Sent from my D2202 using XDA Free mobile app
sjunaid1997 said:
What if after rooting on d2212 firmware i back up my ta partion and unlock my bootloader then flash d2202 firmware then root it again
Sent from my D2202 using XDA Free mobile app
Click to expand...
Click to collapse
This method works too (in fact it works with any Xperia device with unlockable bootloader). This procedure is not detailed in this guide because it's aimed most at people with permanently locked bootloaders, but it should be as simple as downgrading to the exploitable D2212 firmware to gain root with modded giefroot, backing up TA partition then unlocking the bootloader, updating to the latest firmware for your device and installing SuperSU through a custom recovery. To finish, reflash stock kernel and relock the bootloader with the TA backup you took earlier...
Thanks for the help have been waiting for this post i am new to flashing in xperia i used to flash roms on samsung it was easy as pie but sony with its locked bootloader made developers very hard to root it
Sent from my D2202 using XDA Free mobile app
stuck on boot
Everything went normal at update procedure on the final step Was stuck on boot after flashing the updated kitkat firmware kernel .... as this was my primary device i had to flash the stock rom again to use it can i back up ta partition on d2212 firmware will my drm keys be the same as the stock d2202 then unlock bootloader after backing up ta partition pls reply asap
sjunaid1997 said:
Everything went normal at update procedure on the final step Was stuck on boot after flashing the updated kitkat firmware kernel .... as this was my primary device i had to flash the stock rom again to use it can i back up ta partition on d2212 firmware will my drm keys be the same as the stock d2202 then unlock bootloader after backing up ta partition pls reply asap
Click to expand...
Click to collapse
TA backups (and consequently, DRM keys) are unique to each device. NEVER restore backups of another device, even if it's from the same model and variant, doing that would result in a hard brick. In other words, the firmware doesn't matter at all, as long as your TA backup is from the same unit, you can restore it without any troubles in whatever firmware/ROM you're running (as long as you have root access)...
Rooting was fine until...
Hi @mbc07
(I'm sorry that my first post was not a contribution to the community)
I Have the next problem:
-Using dd flasher to flash the new system.ext4 image didn't work
On dd flasher I get this message:
- SuperSU v2.46 (SELinux) cp: can't stat '/data/local/tmp/ddFlasher/system/bin/sh': No such file or directory
- And some other messages about cp
I followed your guide from beginning to end, everything was fine, but when updating with dd flasher to 18.5.A.0.26 (D2202, Orange DO) and flashing the rest of the .ftf with flashtool, my phone ran into the next situation:
-It just shows Sony and Xperia logo, after 30 seconds (aprox.) no screen change and with power button screen turns off and on but Xperia logo still on screen.
Also, after crossflashing D2212 (18.4.B.1.20) on D2202, trying to download Data services I get an error saying "Insert SIM card"
-Tried flashing 4.4.2 SS kernel on 4.4.2 DS firmware, didnt work.
-Tried flashing 4.4.2 SS firmware and rooting (didn't work).
Anyway, worked great on my D2212, but upgrading failed on D2202, thanks for the guide.
Greetings!
@DatchRM, that's a problem with current beta of dd Flasher =/
I already know what can be and should probably be fixed in the stable release of dd Flasher, however I have no ETA because I'm really busy with other stuff but it'll eventually get fixed...
where to store system image?
If i copy system image to sd card then if i removed sd card after will it effect my phone?
prathameshpatankar said:
If i copy system image to sd card then if i removed sd card after will it effect my phone?
Click to expand...
Click to collapse
No
What is wp_mod kernel, and how to use it?
Sent from my D2202 using XDA Free mobile app
Plzz help
When I was trying to update my e3 to 4.4.4 firmware using dd flasher all went fine but after flashing when I was trying to boot up my phone it's still on Sony logo even after 15 mins
Sent from my D2202 using XDA Free mobile app
Did dd Flasher throw some error at you? If yes, post it in dd Flasher thread, I'll take a look. Also, I didn't test but some users told me you should be able to get to the latest firmware via OTA after you got root in the initial 4.4.2 firmware...
No,not a single error, but i hav old 4.4.2 exploitable firmware did u updated that exploitable firmware after?and also i also not downloaded the wp mod is it happened due to that?
Sent from my D2202 using XDA Free mobile app
That's strange, did you reflash the FTF of latest firmware (excluding system partition) after using dd Flasher? Getting stuck in Sony logo generally occurs when the kernel doesn't match the ROM version, and that suggest you may have skipped the last step. About wp_mod, it's a stripped down package that contains only the root fixer, aimed mostly at the LTE variants that uses a different method. You don't need it because dd Flasher automatically applies that patch too...
Installing stock rom again after unlocking the bootloader for D2202
I have unlocked the bootloader for my Phone D2202 and using costum kernel by Mr Vinay, actually his thread has helped me in unlocking the bootloader of my phone and now I wanna flash the stock rom again which I have got from internet as Commercial Stock rom for D2202. I have uninstalled some system applications to remove the blotware. No, i wanna clean my phone. Can I factory reset the phone after removing the system applications? Or should I have to flash that Commercial stock rom again? If I flash it having a custom Kernel and unlocked bootloader what will be the consequences?
This is my first post in XDA. I think you could see that already. So kindly excuse my mistakes.
Thank you and expecting a reply soon.
Shiva Gali said:
I have unlocked the bootloader for my Phone D2202 and using costum kernel by Mr Vinay, actually his thread has helped me in unlocking the bootloader of my phone and now I wanna flash the stock rom again which I have got from internet as Commercial Stock rom for D2202. I have uninstalled some system applications to remove the blotware. No, i wanna clean my phone. Can I factory reset the phone after removing the system applications? Or should I have to flash that Commercial stock rom again? If I flash it having a custom Kernel and unlocked bootloader what will be the consequences?
This is my first post in XDA. I think you could see that already. So kindly excuse my mistakes.
Thank you and expecting a reply soon.
Click to expand...
Click to collapse
you can flash a stock rom downloaded as an ftf file from flashtool
---------- Post added at 01:00 PM ---------- Previous post was at 12:53 PM ----------
no nothing will happen.. it should be fine..
custom kernel will be replaced with stock one on flashing..
Error Flashing
rohan_0909 said:
you can flash a stock rom downloaded as an ftf file from flashtool
---------- Post added at 01:00 PM ---------- Previous post was at 12:53 PM ----------
no nothing will happen.. it should be fine..
custom kernel will be replaced with stock one on flashing..
Click to expand...
Click to collapse
28/035/2015 22:35:44 - INFO - Selected Bundle for Sony Xperia E3 (D2202). FW release : 18.5.A.0.26. Customization : Commercial
28/035/2015 22:35:44 - INFO - Preparing files for flashing
28/036/2015 22:36:29 - INFO - Please connect your device into flashmode.
28/036/2015 22:36:44 - INFO - Opening device for R/W
28/036/2015 22:36:44 - INFO - Start Flashing
28/036/2015 22:36:44 - INFO - Processing loader.sin
28/036/2015 22:36:44 - INFO - Checking header
28/036/2015 22:36:44 - ERROR - Processing of loader.sin finished with errors.
28/036/2015 22:36:44 - INFO - Ending flash session
28/036/2015 22:36:44 - ERROR -
28/036/2015 22:36:44 - ERROR - Error flashing. Aborted
28/036/2015 22:36:45 - ERROR - Drivers need to be installed for connected device.
28/036/2015 22:36:45 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
I don't understand the problem. I have installed the required drivers and the flashtool is recognizing my phone when connected turned on.
28/040/2015 22:40:11 - INFO - Device disconnected
28/040/2015 22:40:53 - INFO - Device connected with USB debugging on
28/040/2015 22:40:54 - INFO - Connected device : Sony Xperia E3
28/040/2015 22:40:54 - INFO - Installed version of busybox : N/A
28/040/2015 22:40:54 - INFO - Android version : 4.4.4 / kernel version : [email protected] / Build number : 18.5.A.0.26
28/040/2015 22:40:54 - INFO - Checking root access
28/040/2015 22:40:55 - INFO - Root Access Allowed
Click to expand...
Click to collapse
CAN ANYBODY HELP?
Shiva Gali said:
I don't understand the problem. I have installed the required drivers and the flashtool is recognizing my phone when connected turned on.
CAN ANYBODY HELP?
Click to expand...
Click to collapse
connect the phone by switching off device.. connect later when it asks to connect, otherwise the phone starts
install flashmode and fastboot drivers..
I think my phone got busted
rohan_0909 said:
connect the phone by switching off device.. connect later when it asks to connect, otherwise the phone starts
install flashmode and fastboot drivers..
Click to expand...
Click to collapse
29/038/2015 10:38:27 - INFO - Processing system.sin
29/038/2015 10:38:27 - INFO - Checking header
29/038/2015 10:38:27 - INFO - Flashing data
29/038/2015 10:38:42 - ERROR - Processing of system.sin finished with errors.
29/038/2015 10:38:42 - INFO - Ending flash session
29/038/2015 10:38:42 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80080012";
I think my phone got busted. I dont understand the reason but it proceeded through some steps and showing error in here. I can't understand why! Could you please help me? I can't use my phone now. I have experience in flashing and I have done tons of times with my previous Sony Ericsson W8 and Nokia 520.
Problem!
rohan_0909 said:
connect the phone by switching off device.. connect later when it asks to connect, otherwise the phone starts
install flashmode and fastboot drivers..
Click to expand...
Click to collapse
I have heard that it is advised to relock bootloader before flashing the stock rom agian. Is it? I thought what you gave me was a reliable advice and proceeded to flash the stock rom. Am I mistaken or you haven't read my statement, i have unlocked bootloader?
no it is not necessary to relock the bootloader while flashing the stock rom.
i have the same model d2202 and flashed stock rom many times without relocking the bootloader
rohan_0909 said:
no it is not necessary to relock the bootloader while flashing the stock rom.
i have the same model d2202 and flashed stock rom many times without relocking the bootloader
Click to expand...
Click to collapse
Could you please tell me where you have downloaded that ftf file for D2022. I Downloaded it from Xperiafirmware.com. My thanks for you replies.
Shiva Gali said:
Could you please tell me where you have downloaded that ftf file for D2022. I Downloaded it from Xperiafirmware.com. My thanks for you replies.
Click to expand...
Click to collapse
I downloaded from xperiablog commercial and journalist one
here's the download link - https://doc-0k-7c-docs.googleuserco...130/*/0ByCWenUJ7trgTndNUVdMUXgzQWM?e=download
Thank you
rohan_0909 said:
I downloaded from xperiablog commercial and journalist one
here's the download link - https://doc-0k-7c-docs.googleuserco...130/*/0ByCWenUJ7trgTndNUVdMUXgzQWM?e=download
Click to expand...
Click to collapse
Thank you. Your link image worked for me. I flashed the rom and now it is working fine.
Shiva Gali said:
Thank you. Your link image worked for me. I flashed the rom and now it is working fine.
Click to expand...
Click to collapse
you are welcome buddy:good:
how to unlock bootloader in xperia E3 D2202 with flashtools....??????
Xperia e3 d2202 in flastool, fastboot mode my mobile device connected and in flash mode it doesn't connect. even in system it connects in adb mode and not in flash mode pls peply.
Sony e3 gets into boot loop even after flashing rom
My sony e3 gets in boot loop every one or two day even when i try to flash the stock rom or lineage, nitrogen one.
So basically i have to flash any of the rom every now and then to keep it running. Can anyone please suggest me a solution or at least tell me why this happens??
Hi all,
I am facing a problem in flashing 15.3.A.1.17 Rom using Flashtool. Since my phone warranty is over, i thought of trying custom ROM of CM 12.1 in my xperia L. As per the forum instruction, i unlocked the bootloader (Official Way), installed CWM recovery kernal and then flashed the zip file of CM 12.1. The customer ROM was pretty much good and i loved it. But after some time i thought of returning back to the original stock ROM of xperia L ( 15.3.A.1.17). so downloaded the .ftf file and tried to flash using flashtool. But i get some error while flashing. Can somebody help on this issue, since i have to get back by stock ROM. Before changing to CM 12.1, I flashed the same .ftf file using flashtool and it was successful. But after flashing CM 12.1, i getting this error.
Below i have attached the log for the flashtool error.
21/001/2015 22:01:57 - INFO - Device connected in flash mode
21/001/2015 22:01:58 - INFO - Opening device for R/W
21/001/2015 22:01:58 - INFO - Reading device information
21/001/2015 22:01:58 - INFO - Phone ready for flashmode operations.
21/001/2015 22:01:58 - INFO - Opening TA partition 2
21/001/2015 22:01:58 - INFO - Current device : Unknown: Mar 26 2014/01:03:26 - ZH8000XB5V - Unknown: Mar 26 2014/01:03:26 - Unknown: Mar 26 2014/01:03:26 - Unknown: Mar 26 2014/01:03:26
21/001/2015 22:01:58 - INFO - Closing TA partition
21/001/2015 22:01:58 - INFO - Start Flashing
21/001/2015 22:01:58 - INFO - Processing loader.sin
21/001/2015 22:01:58 - INFO - Checking header
21/001/2015 22:01:58 - INFO - Flashing data
21/001/2015 22:01:59 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8X30_R1_25 / Bootloader status : ROOTED
21/001/2015 22:01:59 - INFO - Max packet size set to 512K
21/002/2015 22:02:14 - INFO - Making a TA backup
21/002/2015 22:02:14 - INFO - Opening TA partition 1
21/002/2015 22:02:15 - INFO - Start Dumping TA partition 1
21/002/2015 22:02:15 - INFO - Finished Dumping TA partition 1
21/002/2015 22:02:15 - INFO - TA partition 1 saved to C:\Users\User\.flashTool\registeredDevices\ZH8000XB5V\s1ta\2015-11-21_10-02-14\1.ta
21/002/2015 22:02:15 - INFO - Closing TA partition
21/002/2015 22:02:15 - INFO - Opening TA partition 2
21/002/2015 22:02:15 - INFO - Start Dumping TA partition 2
21/002/2015 22:02:15 - INFO - Finished Dumping TA partition 2
21/002/2015 22:02:15 - INFO - TA partition 2 saved to C:\Users\User\.flashTool\registeredDevices\ZH8000XB5V\s1ta\2015-11-21_10-02-14\2.ta
21/002/2015 22:02:16 - INFO - Closing TA partition
21/002/2015 22:02:16 - INFO - Ending flash session
21/002/2015 22:02:16 - ERROR -
21/002/2015 22:02:16 - ERROR - Error flashing. Aborted
Hope somebody help on this issue.
Thanks
Try on Windows 7 with flashtool-0.9.18.6-windows
Just flash a Android 4.2.2 based rom, then you can flash stock rom without problems
Xperia_L said:
Just flash a Android 4.2.2 based rom, then you can flash stock rom without problems
Click to expand...
Click to collapse
I have the same problem with my c2105, I tried downgrading to 4.4 and installing one of those stock roms, but most of them didn't have a flashable .zip. STRYDER's, Clean n Tweaked, nothing worked. Do I have to wipe when installing those roms? Because I did and it didnt work.
Could you tell me, step by step, how to revert to stock?
stuckbootloader said:
I have the same problem with my c2105, I tried downgrading to 4.4 and installing one of those stock roms, but most of them didn't have a flashable .zip. STRYDER's, Clean n Tweaked, nothing worked. Do I have to wipe when installing those roms? Because I did and it didnt work.
Could you tell me, step by step, how to revert to stock?
Click to expand...
Click to collapse
1. Reboot to recovery, wipe everything
2. Flash a stock based rom
3. Power off your phone, connect to pc
4. Flash stockrom via flashtool
Xperia_L said:
1. Reboot to recovery, wipe everything
2. Flash a stock based rom
3. Power off your phone, connect to pc
4. Flash stockrom via flashtool
Click to expand...
Click to collapse
Which stock-based ROM? I've tried Stryder, and it didn't work. Clean n Tweaked doesn't have a flashable.zip..
stuckbootloader said:
Which stock-based ROM? I've tried Stryder, and it didn't work. Clean n Tweaked doesn't have a flashable.zip..
Click to expand...
Click to collapse
then try with cm11
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
then try with cm11
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
I've tried, man. Omni, CM, the modded stock roms...
I'm gonna try with an older version, somebody PM'd me and said the older version might actually work.
stuckbootloader said:
I've tried, man. Omni, CM, the modded stock roms...
I'm gonna try with an older version, somebody PM'd me and said the older version might actually work.
Click to expand...
Click to collapse
Share your results after flashing..
hemanathanvicky said:
Share your results after flashing..
Click to expand...
Click to collapse
Fuсk, I was so happy that it worked that I forgot to reply with the results. :laugh: :highfive:
It worked perfectly with Flashtool 0.9.18.4.
Strange, considering that I flashed the stock rom after unlocking my bootloader with the new version and it worked...
Now, the only problem I have is with the date and clock resetting with custom kernels on stock... If I find a way to fix that...
I have the same problem while I try to flash the stock ROM (CM12 had problems with wi-fi).
I've tried all of the above and still get the same (above) message from Flashtool. I even tried to flash the zip (converted from ftf) through recvery, but I get an error while on set_perm setup progress.
Please help, I'm about to throw this phone away!
immortalwind said:
I have the same problem while I try to flash the stock ROM (CM12 had problems with wi-fi).
I've tried all of the above and still get the same (above) message from Flashtool. I even tried to flash the zip (converted from ftf) through recvery, but I get an error while on set_perm setup progress.
Please help, I'm about to throw this phone away!
Click to expand...
Click to collapse
Did you try my solution? Flashing with an older version of flashtool, such as 0.9.18.4? I've returned from various ROMs to stock this way and it has always worked for me.
Yes, I've tried older versions of flashtool. Didn't work.
Try on different windows version i am using
Windows 8.1
Flashtool 0.9.18.5
I haven't get any problem.
And make sure the driver's are properly install.
durgesh2401 said:
Try on different windows version i am using
Windows 8.1
Flashtool 0.9.18.5
I haven't get any problem.
And make sure the driver's are properly install.
Click to expand...
Click to collapse
Drivers are ok. I'm pretty sure Windows ver has nothong to do with it (I'm using 10).
Hi I would like to know the correct procedure in flashing ftf firmware using the newest flashtool 0.9.22.3
I will flash Android 5.1.1 firmware to my Xperia Z5 dual E6683 to root it.
Screenshot is attached below. How should I proceed?
Do I have to tick a checkbox under Misc TA? etc.
A simple guide would be greatly appreciated.
Thanks
adize said:
Hi I would like to know the correct procedure in flashing ftf firmware using the newest flashtool 0.9.22.3
I will flash Android 5.1.1 firmware to my Xperia Z5 dual E6683 to root it.
Screenshot is attached below. How should I proceed?
Do I have to tick a checkbox under Misc TA? etc.
A simple guide would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
you should be perfectly fine to flash with the default settings however if you want to reset user data which usually is needed if you want to reset your device or downgrade firmware then you would need to tick "userdata" but for upgrading it isnt needed.
Envious_Data said:
you should be perfectly fine to flash with the default settings however if you want to reset user data which usually is needed if you want to reset your device or downgrade firmware then you would need to tick "userdata" but for upgrading it isnt needed.
Click to expand...
Click to collapse
Thank you mate
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
My friend had the same issue. Back to the previous version of Flashtool, and all working fine !
hi,
i have a z5 dual 6633
i would like to downgrade to 5.1.1
is there any rom ? please help me ,because i tried more roms and they did not worked!
if i dont find any 5.1.1 i send it back to the seller, and buy an xz (i just bought the z5)
Hi all,
a couple of days ago I tried to install CyanogenMod 13 in my Xperia M2 D2305. I followed https://wiki.cyanogenmod.org/w/Install_CM_for_nicki.
After flashing the boot.img the device did not boot. After flashing a CWM-Based Recovery I realized that the CM image I was trying to install did not work casue it was for d2303. I looked for a CM image for 2305 and did not find any.
I've been looking for ANY (not just CM) custom firmware that I could flash in my device, but I did not find any (is it me or there is no custom firmwres for 2305? is that's true, anyone knows why?)
So I decided to flash original firmware (following http://techbeasts.com/update-xperia-m2-to-official-android-5-1-1-lollipop-186a0175-firmware/) but then flashtool does not recognize the TFT file, there is no firmware available (flashtool version 0.9.22.3).
Tried with 2 different TFT files :
D2305_18.6.A.0.175_R1C_Ukraine Generic_1281-4769.ftt
D2305_18.6.A.0.182_R1C_Customized GEL.ftf
Last thing I tried is repairing the phone with PC Companion, but i says:
Code:
Software repair failed
The device contains modified software that cannot be repaired.
Error code: UEGetPhoneInfoRootedDevice
UE_2003
So, at this point I don't know what else I could try. I'd like to use a custom firmware (without all the Sony crap that uses all my memory) but I'm open to any solution cause I'd like to repair the phone.
I've not tried (http://forum.xda-developers.com/xpe...2303-cwm-based-recovery-6-0-4-6-root-t2884503) but I wanted to ask for help before trying another solution.
TIA,
Arnau
pelacables79 said:
Hi all,
a couple of days ago I tried to install CyanogenMod 13 in my Xperia M2 D2305. I followed https://wiki.cyanogenmod.org/w/Install_CM_for_nicki.
After flashing the boot.img the device did not boot. After flashing a CWM-Based Recovery I realized that the CM image I was trying to install did not work casue it was for d2303. I looked for a CM image for 2305 and did not find any.
I've been looking for ANY (not just CM) custom firmware that I could flash in my device, but I did not find any (is it me or there is no custom firmwres for 2305? is that's true, anyone knows why?)
So I decided to flash original firmware (following http://techbeasts.com/update-xperia-m2-to-official-android-5-1-1-lollipop-186a0175-firmware/) but then flashtool does not recognize the TFT file, there is no firmware available (flashtool version 0.9.22.3).
Tried with 2 different TFT files :
D2305_18.6.A.0.175_R1C_Ukraine Generic_1281-4769.ftt
D2305_18.6.A.0.182_R1C_Customized GEL.ftf
Last thing I tried is repairing the phone with PC Companion, but i says:
Code:
Software repair failed
The device contains modified software that cannot be repaired.
Error code: UEGetPhoneInfoRootedDevice
UE_2003
So, at this point I don't know what else I could try. I'd like to use a custom firmware (without all the Sony crap that uses all my memory) but I'm open to any solution cause I'd like to repair the phone.
I've not tried (http://forum.xda-developers.com/xpe...2303-cwm-based-recovery-6-0-4-6-root-t2884503) but I wanted to ask for help before trying another solution.
TIA,
Arnau
Click to expand...
Click to collapse
When you unlock the bootloader of your phone, you'll no longer be able to repair your Xperia phone via Xperia Companion. You'll have to use EMMA from Sony Developers http://developer.sonymobile.com/open-devices/flash-tool/how-to-download-and-install-the-flash-tool/
tromine said:
When you unlock the bootloader of your phone, you'll no longer be able to repair your Xperia phone via Xperia Companion. You'll have to use EMMA from Sony Developers http://developer.sonymobile.com/open-devices/flash-tool/how-to-download-and-install-the-flash-tool/
Click to expand...
Click to collapse
Hi tromine and thanks for your answer.
i forgot to mention that I already was there, but my device is not supported: http://developer.sonymobile.com/open-devices/flash-tool/supported_phones/
Best,
Arnau
pelacables79 said:
Hi tromine and thanks for your answer.
i forgot to mention that I already was there, but my device is not supported: http://developer.sonymobile.com/open-devices/flash-tool/supported_phones/
Best,
Arnau
Click to expand...
Click to collapse
For EMMA: Did you tried it before? (Even if your model isn't in the list)
For Flashtool: Try to uninstall completely the software and reinstall it. I recommend you the 0.9.18.6 version: http://www.flashtool.net/downloads_windows_prev.php
tromine said:
For EMMA: Did you tried it before? (Even if your model isn't in the list)
For Flashtool: Try to uninstall completely the software and reinstall it. I recommend you the 0.9.18.6 version: http://www.flashtool.net/downloads_windows_prev.php
Click to expand...
Click to collapse
Hi again,
thanks for advice on flashboot, previous version do recognize my TFT file (the ukranian one), but the flash process fails:
Code:
19/048/2016 14:48:02 - INFO - Processing system.sin
19/048/2016 14:48:02 - INFO - Checking header
19/048/2016 14:48:02 - INFO - Flashing data
19/050/2016 14:50:14 - ERROR - Processing of system.sin finished with errors.
19/050/2016 14:50:14 - INFO - Ending flash session
19/050/2016 14:50:14 - ERROR -
19/050/2016 14:50:14 - ERROR - Error flashing. Aborted
Will try with another firmware and see if I'm lucky.
About Emma, no, I did not try. I was getting some login error and, after reading that my deveice was not supported, I gave up. Will give it another try.
BTE, there's no custom firmware for my model?
Thanks,
Arnau
pelacables79 said:
Hi again,
thanks for advice on flashboot, previous version do recognize my TFT file (the ukranian one), but the flash process fails:
Code:
19/048/2016 14:48:02 - INFO - Processing system.sin
19/048/2016 14:48:02 - INFO - Checking header
19/048/2016 14:48:02 - INFO - Flashing data
19/050/2016 14:50:14 - ERROR - Processing of system.sin finished with errors.
19/050/2016 14:50:14 - INFO - Ending flash session
19/050/2016 14:50:14 - ERROR -
19/050/2016 14:50:14 - ERROR - Error flashing. Aborted
Will try with another firmware and see if I'm lucky.
About Emma, no, I did not try. I was getting some login error and, after reading that my deveice was not supported, I gave up. Will give it another try.
BTE, there's no custom firmware for my model?
Thanks,
Arnau
Click to expand...
Click to collapse
For Flashtool, you can try to download another FTF via Xperifirm included in Flashtool 0.9.18.6
For EMMA, follow the instructions here: http://developer.sonymobile.com/open-devices/flash-tool/how-to-download-and-install-the-flash-tool/
And I don't know if there's custom ROMs for the D2305.
tromine said:
For Flashtool, you can try to download another FTF via Xperifirm included in Flashtool 0.9.18.6
For EMMA, follow the instructions here: http://developer.sonymobile.com/open-devices/flash-tool/how-to-download-and-install-the-flash-tool/
And I don't know if there's custom ROMs for the D2305.
Click to expand...
Click to collapse
The "old" version of flashtools does not recognize the company's proxy, so I guess Imust wait till I get home and try with a "free" internet connection.
About EMMA, I guess you imagine that I forgot step 5: copy Customization.ini , right? I did copy it, the contents of the file are:
developerworld/enable = true
But, again, I want to try both tools from a free-proxy connection.
Thanks for your help,
Arnau
pelacables79 said:
The "old" version of flashtools does not recognize the company's proxy, so I guess Imust wait till I get home and try with a "free" internet connection.
About EMMA, I guess you imagine that I forgot step 5: copy Customization.ini , right? I did copy it, the contents of the file are:
developerworld/enable = true
But, again, I want to try both tools from a free-proxy connection.
Thanks for your help,
Arnau
Click to expand...
Click to collapse
I'm glad I helped you
tromine said:
I'm glad I helped you
Click to expand...
Click to collapse
Now I'm completly lost.... See what Flashtool says:
19/059/2016 15:59:24 - INFO - Current device : D2303 - ZH800405LR - 1286-4872_R4C - 1278-3081_18.6.A.0.182 - GLOBAL-LTE_18.6.A.0.18
What? now it's 2303, but when I tried CM13 it said it was 2305? What's going on? (I'll try a FTF file for 2303)
Best,
Arnau
tromine said:
I'm glad I helped you
Click to expand...
Click to collapse
Emma also recognize my device as 2303... I'm really confused right now. The CM 13/14 for 2303 did not work for me (boot loop).
Could you please give the link for the CM you run in your device?
TIA,
Arnau
Take a look at these threads:
http://forum.xda-developers.com/xpe...-cyanogenmod-14-1-developement-t3518598/page3
http://forum.xda-developers.com/xperia-m2/orig-development/rom-omnirom-beta-1-development-t3499681
You can try to flash a CyanogenMod 14.1 or OminROM 7.1 with TWRP Recovery.
Regards.
xavinux said:
Take a look at these threads:
http://forum.xda-developers.com/xpe...-cyanogenmod-14-1-developement-t3518598/page3
http://forum.xda-developers.com/xperia-m2/orig-development/rom-omnirom-beta-1-development-t3499681
You can try to flash a CyanogenMod 14.1 or OminROM 7.1 with TWRP Recovery.
Regards.
Click to expand...
Click to collapse
So I'm now running CM14.1.
1.- using Emma in a proxy-free environment recovered my Phone. It flashed stock firmware without any issue (no login issues and it was able to download a valid FTF file)
2.- I used CM14.1 from the first link (BETA 1) and I could flash it without any issue.
Thanks a lot!
PS: But I feel a little bit like this guy:
DavidMKD said:
Definitely there is something going on with different Xperia M2 models/revisions. I have 2 M2's, same D2303, one is lagging the other is not.
Click to expand...
Click to collapse
Again, thanks lot for your help, I'll mark the thread as solved.
pelacables79 said:
So I'm now running CM14.1.
1.- using Emma in a proxy-free environment recovered my Phone. It flashed stock firmware without any issue (no login issues and it was able to download a valid FTF file)
2.- I used CM14.1 from the first link (BETA 1) and I could flash it without any issue.
Thanks a lot!
PS: But I feel a little bit like this guy:
Again, thanks lot for your help, I'll mark the thread as solved.
Click to expand...
Click to collapse
Glad to know you could flashed your device with the custom ROM you like!
I"ve an M2 Eagle D2303 and have tested both OmniROM 7.1 and CyanogenMod, 14.1
And OmniROM 7.1 Beta 2 works wonderful and is the one I have benn using for the last week without any issue on my M2.
If you want, you can install it with the TWRP Recovery and I suggest you to give OmniROM a try.
Regsrds.