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).
Related
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??
An error occurred on my OPO while trying to update the ROM to "cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-bacon".
(Using TWRP 2.8.7.0)
TWRP log:
- script aborted: Package expects build fingerprint of
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS3JL:user/release-keys or
- oneplus/bacon/A0001:5.1.1/LMY48Y/YOG7DAS2K1:user/release-keys;
- this device has
- oneplus/bacon/A0001:4.4.2/KVT49L/XNPH25R:user/release-keys.
-
- Error executing updater binary in zip '/sdcard/Download/COS 12.1/cm-bacon-d91bf047f5-to-cee4e8702d-signed.zip'
- Error flashing zip '/sdcard/Download/COS 12.1/cm-bacon-d91bf047f5-to-cee4e8702d-signed.zip'
Build info from Settings/About:
- Android Ver#: 5.1.1
- Model: A0001
- Cyanogen OS Version: 12.1-YOG4PAS3JL
- Build#: LMY48B
Build info from Buiild.Prop:
- ro.build.id=LMY48B
- ro.build.version.release=5.1.1
- ro.build.host=cyanogenmod
- ro.product.brand=oneplus
- ro.product.name=bacon
- ro.build.product=A0001
- ro.build.fingerprint=oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS3JL:user/release-keys
- ...
So the installed version is:
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS3JL
And not as TWRP misidentified:
- oneplus/bacon/A0001:4.4.2/KVT49L/XNPH25R
The bottom line - can't install "cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-bacon"!
Any idea how to fix that problem?
I am getting same error while flashing the latest OTA zip, I think it has something to do with Twrp's 2.8.7.0. I'll try again with 2.8.6.0 as Sultan also recommended that.
usman.aaman said:
I am getting same error while flashing the latest OTA zip, I think it has something to do with Twrp's 2.8.7.0. I'll try again with 2.8.6.0 as Sultan also recommended that.
Click to expand...
Click to collapse
Thanks!
Your suggestion helped me solving my problem.
I flashed TWRP 2.8.7.0.5 (the newest version).
Steps to install the new ROM -
1. Backup your Data (Titanium backup or other)
2. reboot to Recovery
3. Wipe cache/dalvik cache/data/system
4. reboot back to Recovery
5. Install the newer ROM
6. reboot to System
7. Finish installation process
8. Restore your Data (Titanium backup or other)
The original issue probably occurred due to TWRP 2.8.7.0 bug.
The issue is solved.
AmnonD said:
Thanks!
Your suggestion helped me solving my problem.
I flashed TWRP 2.8.7.0.5 (the newest version).
Steps to install the new ROM -
1. Backup your Data (Titanium backup or other)
2. reboot to Recovery
3. Wipe cache/dalvik cache/data/system
4. reboot back to Recovery
5. Install the newer ROM
6. reboot to System
7. Finish installation process
8. Restore your Data (Titanium backup or other)
The original issue probably occurred due to TWRP 2.8.7.0 bug.
The issue is solved.
Click to expand...
Click to collapse
You're welcome.
Where did you find 2.8.7.0.5 ?
Can you link me there?
Thanks.
usman.aaman said:
You're welcome.
Where did you find 2.8.7.0.5 ?
Can you link me there?
Thanks.
Click to expand...
Click to collapse
I just Googled "TWRP 2.8.7.0.5".
Link:
https://www.androidfilehost.com/?fid=24269982087010524
I do not know why this version 2.8.7.0.5 worked, because the latest version is only 2.8.7.0, this "5" at the end it's probably because it has a theme installed.
The default.prop inside the TWRP (ramdisk) you used to flash the zip has the ro.build.fingerprint=oneplus/bacon/A0001:4.4.2/KVT49L/XNPH25R:user/release-keys
It always checks for build fingerprint in the default.prop inside the installed recovery rather than the build.prop in the installed OS, it maybe because they don't want users to flash the OTA over an incorrect ROM to avoid issues.
The default.prop inside the stock recovery always has the build fingerprint of the installed COS so that the future updates can be flashed over correct COS by checking the previous or the last 2 build fingerprints. After the update is flashed the CM recovery gets updated with the new build fingerprint and is ready for the next future updates.
This is just stupid, why not check the build.prop in the system so that users can use any recovery they want.
Stop forcing us to use everything that is CM -_-
TWRP 2.8.7.0 version has a kwnown bug and doesn't flash correctly firmware/modem. TWRP 2.8.6.0 works well and the themed version 2.8.7.0.5 seems to have the fix! Thats all!
Similar problem with TWRP 2.8.7.0.5!
Thank you all for your help!
Now I have a similar issue with TWRP 2.8.7.0.5!
I tried to flash CM-12.1-YOG7DAS2K1.
Current ROM on my OPO - CM-12.1-YOG4PAS3JL
Error details from the TWRP log:
script aborted:
Package expects build fingerprint of
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS3JL:user/release-keys or
- oneplus/bacon/A0001:5.1.1/LMY48Y/YOG7DAS2K1:user/release-keys;
this device has
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS1N0:user/release-keys.
Is it safe to modify the default.prop file?
Same here
AmnonD said:
Thank you all for your help!
Now I have a similar issue with TWRP 2.8.7.0.5!
I tried to flash CM-12.1-YOG7DAS2K1.
Current ROM on my OPO - CM-12.1-YOG4PAS3JL
Error details from the TWRP log:
script aborted:
Package expects build fingerprint of
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS3JL:user/release-keys or
- oneplus/bacon/A0001:5.1.1/LMY48Y/YOG7DAS2K1:user/release-keys;
this device has
- oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS1N0:user/release-keys.
Is it safe to modify the default.prop file?
Click to expand...
Click to collapse
Exactly same error here.
As TWRP has problems with OTA updates, I went back to stock recovery, but installation aborted again.
I have read it would work installing the zip of the fastboot file (cm-12.1-YOG4PAS3JL-bacon-signed-fastboot.zip) and then update via OTA the incremental using stock recovery.
I think I'll wait for the full file for TWRP installation
I succeeded to install the "cm-12.1-YOG4PAS3JL-bacon-signed" after System & Data wipe of previous ROM.
The problem is that TWRP doesn't identify the correct version. It claims that my OPO runs YOG4PAS1N0!
That is the reason for the YOG7DAS2K1 version installation failure.
I'll also wait for the full version.
Thanks.
Still not working, tried TWRP 2.8.6.0, 2.8.7.0, 2.8.7.0.5, and with all the OTA update fails.
Last I tried modifing the OTA by removing the fingerprint check (line 3 from updater-script), reflashed fastboot and did a reinstall with twrp 2.8.7.0, and it worked, system was patched successfully according to twrp, but later it was not bootable, stuck on the 1+ logo.
did a restore to older version, will wait for fastboot version.
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.
Hi,
***I did download all proper drivers for my xperia xz dual.
***I did download the FTF file (and yes it's not corrupted)
***I do have the latest version of Flashtool Androxyde
---------------------------------------------------------------------------------------------
***Now whenever I start the flashing process and connect my phone in flashmode, flashing fails because of the following error(s):
----------------------------------------------------------------------------------------------------------------------------------------------------------
Selected Bundle for Sony Xperia XZ(F8332). FW release : 41.2.A.2.199_R1D. Customization : India Generic_1305-0131
Preparing files for flashing
Please connect your device into flashmode.
Device connected in flash mode
Opening device for R/W
Reading device information
Phone ready for flashmode operations.
Opening TA partition 2
Current device : F8332 - CB512BUK83 - 1305-0127_R1D - 1302-9162_41.2.A.2.199 - GENERIC_41.2.A.2.199
Closing TA partition
INFO - Start Flashing
No loader in the bundle. Searching for one
No matching loader found
WARN - No loader found or set manually. Skipping loader
Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_115 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_115 / Bootloader status : ROOTABLE
Max packet size set to 4M
USB buffer size set to 512K
Parsing boot delivery
No flash script found.
Flash script is mandatory. Closing session
Ending flash session
Flashing finished.
Please unplug and start your phone
For flashtool, Unknown Sources and Debugging must be checked in phone settings
Device connected in flash mode
Device disconnected
------------------------------------------------------------------------------------------------------------------------------------------------------
I'm basically dying for a fresh installation and it would be appreciated if anyone can help
samisawani said:
Hi,
***I did download all proper drivers for my xperia xz dual.
***I did download the FTF file (and yes it's not corrupted)
***I do have the latest version of Flashtool Androxyde
---------------------------------------------------------------------------------------------
***Now whenever I start the flashing process and connect my phone in flashmode, flashing fails because of the following error(s):
----------------------------------------------------------------------------------------------------------------------------------------------------------
Selected Bundle for Sony Xperia XZ(F8332). FW release : 41.2.A.2.199_R1D. Customization : India Generic_1305-0131
Preparing files for flashing
Please connect your device into flashmode.
Device connected in flash mode
Opening device for R/W
Reading device information
Phone ready for flashmode operations.
Opening TA partition 2
Current device : F8332 - CB512BUK83 - 1305-0127_R1D - 1302-9162_41.2.A.2.199 - GENERIC_41.2.A.2.199
Closing TA partition
INFO - Start Flashing
No loader in the bundle. Searching for one
No matching loader found
WARN - No loader found or set manually. Skipping loader
Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_115 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_115 / Bootloader status : ROOTABLE
Max packet size set to 4M
USB buffer size set to 512K
Parsing boot delivery
No flash script found.
Flash script is mandatory. Closing session
Ending flash session
Flashing finished.
Please unplug and start your phone
For flashtool, Unknown Sources and Debugging must be checked in phone settings
Device connected in flash mode
Device disconnected
------------------------------------------------------------------------------------------------------------------------------------------------------
I'm basically dying for a fresh installation and it would be appreciated if anyone can help
Click to expand...
Click to collapse
Rename the 39.fsc under mydevices folder f8332 into 41.fsc before you flash 7.1.1 firmware.
nolihowell said:
Rename the 39.fsc under mydevices folder f8332 into 41.fsc before you flash 7.1.1 firmware.
Click to expand...
Click to collapse
Mydevices folder is empty. Do you mean devices folder?
Update: Thanks it worked! I just had to copy the F83XX folder from Devices and copy it to Devices folder. Then rename the FSC file and all went smooth.
Thanks,
nolihowell said:
Rename the 39.fsc under mydevices folder f8332 into 41.fsc before you flash 7.1.1 firmware.
Click to expand...
Click to collapse
Thank you very much for this tip. I tried nearly two days to get this flashing working for me...
What is the preferred firmware region for an XZ Dual?
Yakkosmurf said:
What is the preferred firmware region for an XZ Dual?
Click to expand...
Click to collapse
Assuming ur phone is unlocked, it doesn't really matter since these unlocked firmware are almost the same. It's better however to download your region's firmware.
nolihowell said:
Rename the 39.fsc under mydevices folder f8332 into 41.fsc before you flash 7.1.1 firmware.
Click to expand...
Click to collapse
This solution worked for me to update to .199 firmware.
But it doesn't work anymore for me to flash .223 firmware like this .
I was already rooted so I just used PRF Creator to create prerooted flashable zip.
But still I want flashing via Flashtool to work. Any idea why the solution of adding 39.fsc to mydevices folder and renaming it to 41.fsc doesn't fix the issue anymore to flash latest .223 firmware?
koekoek91 said:
This solution worked for me to update to .199 firmware.
But it doesn't work anymore for me to flash .223 firmware like this .
I was already rooted so I just used PRF Creator to create prerooted flashable zip.
But still I want flashing via Flashtool to work. Any idea why the solution of adding 39.fsc to mydevices folder and renaming it to 41.fsc doesn't fix the issue anymore to flash latest .223 firmware?
Click to expand...
Click to collapse
i've just flashed .223 with this
did flashtool ask you to use the 41.fsc?
also, did you copy F83XX to mydevices as well?
cal_l_lka said:
i've just flashed .223 with this
did flashtool ask you to use the 41.fsc?
also, did you copy F83XX to mydevices as well?
Click to expand...
Click to collapse
Flashtool didn't ask me to use the script.
No i only copied the fsc file and not the whole F83XX.
Will try that later
Thanks.
might also help if you restart the computer just before flashing
samisawani said:
Assuming ur phone is unlocked, it doesn't really matter since these unlocked firmware are almost the same. It's better however to download your region's firmware.
Click to expand...
Click to collapse
Yeah, it's an unlocked US phone, but I want to change regions to re-enable the finger print sensor. I've used Customized NOBA and Customized CE1 on single sim phones due to their low level of bloat. But, I haven't seen much info on differences in the dual sim firmwares to know if there was a consensus on one being better. I think I'll give Customized RU a go.
Hi. I wanted to install a custom ROM from XDA, however I wanted to backup my ta partition/DRM keys first, so I could revert back should I want to.
I looked in xperifirm, and the oldest they had was 32.2.A.5.11 / R12C, so I flashed it. Apparently it was a 6.0.1 ROM. Is there a way of temporarily rooting 6.0.1, or the latest ROM? If not, does anyone know where a stock 5.1.1 ROM is?
Thanks
Update: I flashed the commercial and journalists rom in xperifirm, and I have now backed up my ta file.
Is there a way of verifying a ta file? Thanks
MegaBytesMe said:
Is there a way of verifying a ta file? Thanks
Click to expand...
Click to collapse
The file size should be 2MB. If in doubt rerun the backup and compare the two via MD5, using different backup methods even if you want to be 110% sure that your TA backup is all good.
As far as I know the TA partition also stores other information that sometimes changes at reboot, MD5-ing will yield different results between reboots.
EDIT: TABackup V2 by rayman verifies the TA dump before pulling. See thread and download here