Trying to unlock the bootloader unlocked, fleshtool writes, but in fact is not, does not fill recovery failed The writes,
to unlock: Bootloader unlock allowed: Yes
after unlocking: UNAVAILABLE
log
4/054/2016 00:54:57 - INFO - Processing loader.sin
04/054/2016 00:54:57 - INFO - Checking header
04/054/2016 00:54:57 - INFO - Flashing data
04/054/2016 00:54:58 - INFO - Processing of loader.sin finished.
04/054/2016 00:54:58 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_37 / Bootloader status : ROOTABLE
04/054/2016 00:54:58 - INFO - Start Reading unit 000008B2
04/054/2016 00:54:58 - INFO - Reading TA finished.
04/054/2016 00:54:59 - INFO - Unlocking device
04/054/2016 00:54:59 - INFO - Writing TA unit : [00, 00, 08, B2, 00, 00, 00, 12, 30, 78, 30, 33, 45, 37, 43, 38, 31, 34, 39, 41, 30, 42, 42, 44, 39, 39]
04/054/2016 00:54:59 - INFO - Unlock finished
04/055/2016 00:55:05 - INFO - Ending flash session
04/055/2016 00:55:05 - INFO - You can now unplug and restart your device
c:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (30268 KB)...
OKAY [ 2.870s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 2.875s
liwetlt said:
Trying to unlock the bootloader unlocked, fleshtool writes, but in fact is not, does not fill recovery failed The writes,
to unlock: Bootloader unlock allowed: Yes
after unlocking: UNAVAILABLE
log
4/054/2016 00:54:57 - INFO - Processing loader.sin
04/054/2016 00:54:57 - INFO - Checking header
04/054/2016 00:54:57 - INFO - Flashing data
04/054/2016 00:54:58 - INFO - Processing of loader.sin finished.
04/054/2016 00:54:58 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_37 / Bootloader status : ROOTABLE
04/054/2016 00:54:58 - INFO - Start Reading unit 000008B2
04/054/2016 00:54:58 - INFO - Reading TA finished.
04/054/2016 00:54:59 - INFO - Unlocking device
04/054/2016 00:54:59 - INFO - Writing TA unit : [00, 00, 08, B2, 00, 00, 00, 12, 30, 78, 30, 33, 45, 37, 43, 38, 31, 34, 39, 41, 30, 42, 42, 44, 39, 39]
04/054/2016 00:54:59 - INFO - Unlock finished
04/055/2016 00:55:05 - INFO - Ending flash session
04/055/2016 00:55:05 - INFO - You can now unplug and restart your device
c:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (30268 KB)...
OKAY [ 2.870s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 2.875s
Click to expand...
Click to collapse
Relock the bootloader with the same steps through flashtool. When you relock it, the bootloader status will go back to normal. Than, go to developer settings and enable the: OEM Unlocking. Allow the bootloader to be unlocked. If you don't have that option in Developer settings, than try to flash different firmware (different branding/region), because some firmware's doesn't have that option in the developer settings. In Marshmallow, you have that option, so you could flash Marshmallow firmware. If you manage to flash, and allow the bootloader to be unlocked, than try again with unlocking the bootloader. But this time, try unlocking the bootloader by Sony "official" way through CMD. When you asked for the unlocking code on Sony, they gave you this tutorial, with required commands for unlocking the bootloader.
ekin_strops said:
Relock the bootloader with the same steps through flashtool. When you relock it, the bootloader status will go back to normal. Than, go to developer settings and enable the: OEM Unlocking. Allow the bootloader to be unlocked. If you don't have that option in Developer settings, than try to flash different firmware (different branding/region), because some firmware's doesn't have that option in the developer settings. In Marshmallow, you have that option, so you could flash Marshmallow firmware. If you manage to flash, and allow the bootloader to be unlocked, than try again with unlocking the bootloader. But this time, try unlocking the bootloader by Sony "official" way through CMD. When you asked for the unlocking code on Sony, they gave you this tutorial, with required commands for unlocking the bootloader.
Click to expand...
Click to collapse
this function is the developer and it is turned off, did not help
liwetlt said:
this function is the developer and it is turned off, did not help
Click to expand...
Click to collapse
It's supposed to be turned ON.
Yes. turn, did not open bootloader
liwetlt said:
Yes. turn, did not open bootloader
Click to expand...
Click to collapse
Turning on will not open your bootloader. Turning on, will allow the bootloader to be unlocked. After turning on, try to unlock your bootloader again with flashtool.
ekin_strops thank you, the problem decided flashtoo wrong IMEI showed.
Locked
Related
My bootloader, trim area were damaged. A friend from America helped me rewriting, etc.Now I can flash, fastboot (features that didnt work no more), but the problem is that the network is disconecting every 2-3 minutes; its frustrating, I cant even sent a message , have to wait until it's reconecting... Please, if somebody from Europe coul send me a seetool backup of the TA Thank you in advance!
Well I have similar problems in past with so called “Trim Area Damaged”.
After search I found out : http://forum.xda-developers.com/showpost.php?p=14774499&postcount=1
Unzip de package (FlashTool_0.2.9.1_FOTAUnbrick). You will have Flashtool inside. Clik X10FlashTool.exe and select Xperia 2011 Range_FreeXperia_ALL.
Be aware that I am not responsible if you damage your phone with this procedure.
Good luck
Thanks! but I dont think thatt will work! I need those TA files tooked from another good european Mt15i phone, preferably backuped with setool in flash mode...
benga_mircea said:
My bootloader, trim area were damaged. A friend from America helped me rewriting, etc.Now I can flash, fastboot (features that didnt work no more), but the problem is that the network is disconecting every 2-3 minutes; its frustrating, I cant even sent a message , have to wait until it's reconecting... Please, if somebody from Europe coul send me a seetool backup of the TA Thank you in advance!
Click to expand...
Click to collapse
hi.
i edited my xperia u TA using flash tool and no any reaction like flash mod.
please help me to fix it i have back up of trim area using flash tool,also i have stool box for flashing.
with regards ramin/iran(there is no any Sony service center)
Bricked SE Xperia neo
I still have the same problem TA brick or other Phone Brick , when i try to put on the phone the led are red and blinking ... i also tryed to flash new firmware first with se updater then with flashtool and last with s1tool nothing works ... can anyone help me to solve this problem end get my phone to run
here the flashtool log
02/000/2012 16:00:48 - INFO - Preparing files for flashing
02/000/2012 16:00:49 - INFO - Searching Xperia....
02/000/2012 16:00:49 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&C1101A7&0&1
02/000/2012 16:00:49 - INFO - Start Flashing
02/000/2012 16:00:49 - INFO - VER="R9A021";DATE="20110128";TIME="11:49:00";
02/000/2012 16:00:49 - INFO - Flashing loader
02/000/2012 16:00:50 - INFO - PROT_VER="03";DATE="20110217";TIME="15:47:00";VER="R4A066";CXC="1234-5769";TYPE="S1_LOADER";UNIQUE_DEV_ID="A7D3303906A1F4A3467CF8537F3216931810B748";SEC_LOCK_STATUS="LOCKED";OTP_DATA="4B6D7100471404C81508042800D32070B001002000000000";IMEI="01270300405617";AID_VERSION="0004";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";HWCONF_AID="0001";PROD_ID="0001";ACTIVE_LOADER_AID="0001";MEMDEVS="02:00:002C:00B3:0000:00002000:00020000:00000800:00000040";MAN_ID="002C";DEV_ID="00B3";SIN_VER="0001";AID_TAMP="NOT_TAMPERED";MAX_PKT_SZ="00010000";AUTH_LEVEL="NONE";AUTH_MET="0001";CARD_PRESENT="NO";LOADER_ROOT="S1_Loader_Root_773f";EROM_ROOT="S1_EROM_Root_d601";SW_ROOT="S1_SW_Root_883f";CUST_ROOT="S1_Cust_Root_9603";SIM_LOCK_ROOT="S1_SL_Root_c422";HW_CONF_ROOT="S1_HWConf_Root_08af";BIM_STATE="DISABLED";
02/000/2012 16:00:50 - INFO - Flashing preset
02/000/2012 16:00:50 - INFO - TA value : [00, 00, 08, FD, 00, 00, 00, 02, 00, 00, ]
02/000/2012 16:00:50 - INFO - Flashing finished.
02/000/2012 16:00:50 - INFO - Now unplug the device and power it on
02/000/2012 16:00:50 - INFO - Then go to application settings
02/000/2012 16:00:50 - INFO - turn on Unknown Sources and Debugging
Click to expand...
Click to collapse
So i got my xperia z2 from o2 and wanted to debrand it, followed this tutorial:
http://www.xperiablog.net/2014/06/01/debrand-your-xperia-z2-tutorial/
But, it wont flash the firmware, its stuck here, when i start the phone i get an error that the software update has failed and to connect to my computer.
This is what im getting in Flashtool64;
03/040/2014 16:40:16 - INFO - <- This level is successfully initialized
03/040/2014 16:40:16 - INFO - Flashtool Version 0.9.10.2beta4 built on 2013-03-21 19:00:00
03/040/2014 16:40:21 - INFO - Device connected in flash mode
03/040/2014 16:40:25 - INFO - Selected D6503 / 17.1.A.2.55 / EURO_LTE
03/040/2014 16:40:25 - INFO - Preparing files for flashing
03/041/2014 16:41:11 - INFO - Please connect your device into flashmode.
03/041/2014 16:41:15 - INFO - Opening device for R/W
03/041/2014 16:41:15 - INFO - Reading device information
Ive started it over and over and it just gets stuck at this step, help
03/058/2014 16:58:40 - INFO - Device disconnected
03/058/2014 16:58:48 - INFO - Please connect your device into flashmode.
03/059/2014 16:59:00 - INFO - Device connected in flash mode
03/059/2014 16:59:01 - INFO - Opening device for R/W
03/059/2014 16:59:01 - INFO - Reading device information
03/059/2014 16:59:01 - INFO - Phone ready for flashmode operations.
03/059/2014 16:59:01 - INFO - Current device : D6503 - BH90CUJA16 - 1281-4648_R5A - 1278-4770_17.1.1.A.0.402 - EURO-LTE_17.1.1.A.0.402
03/059/2014 16:59:01 - INFO - Start Flashing
03/059/2014 16:59:01 - INFO - Processing loader
03/059/2014 16:59:01 - INFO - Checking header
03/059/2014 16:59:01 - INFO - Flashing data
03/059/2014 16:59:01 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_12 / Bootloader status : NOT_ROOTABLE
03/059/2014 16:59:02 - INFO - Processing partition-image.sin
03/059/2014 16:59:02 - INFO - Checking header
03/059/2014 16:59:02 - INFO - Flashing data
03/059/2014 16:59:02 - INFO - Flashing cust-reset.ta
03/059/2014 16:59:02 - INFO - Writing TA unit : [00, 00, 08, A4, 00, 00, 00, 0E, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]
03/059/2014 16:59:02 - INFO - Processing kernel.sin
03/059/2014 16:59:02 - INFO - Checking header
03/059/2014 16:59:02 - INFO - Flashing data
03/059/2014 16:59:03 - INFO - Processing fotakernel.sin
03/059/2014 16:59:03 - INFO - Checking header
03/059/2014 16:59:03 - INFO - Flashing data
03/059/2014 16:59:05 - INFO - Processing fota-reset.ta
now its stuck at this
I'm not familiar with flashing on Z2 but I would try with latest flashtool.
Sent from my C6903 using Tapatalk
Double check it's the correct firmware
Try a different usb port
could be http://forum.xda-developers.com/showpost.php?p=32207092&postcount=7
BTW...flashing ftf on unrooted, unlocked device isn't good idea.
There were many bricked Z1 devices...
I flashed million ftf's and all went well but just want you to know that...
As I said, I'm quite sure you are using old flashtool.
Sent from my C6903 using Tapatalk
funky0308 said:
BTW...flashing ftf on unrooted, unlocked device isn't good idea.
There were many bricked Z1 devices...
I flashed million ftf's and all went well but just want you to know that...
As I said, I'm quite sure you are using old flashtool.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
From my understanding, FlashTool is designed(not only) to flash original firmware on unlocked, unrooted phones. If you follow the instruction carefully, you have all the drivers installed correctly, etc it should work.
raducanmihai said:
From my understanding, FlashTool is designed(not only) to flash original firmware on unlocked, unrooted phones. If you follow the instruction carefully, you have all the drivers installed correctly, etc it should work.
Click to expand...
Click to collapse
Why unlocked?
I'm using it without any problems on LB but for Z1 and Z2 you have to use latest version, I think it's v. 16
Sent from my C6903 using Tapatalk
funky0308 said:
Why unlocked?
I'm using it without any problems on LB but for Z1 and Z2 you have to use latest version, I think it's v. 16
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Sorry, my mistake. I meant to say "locked and unrooted".
I was trying to make a point that the quoted post (many Z1s bricked by flashing rtf on unlocked, unrooted) doesn't make sense.
Hey guys,
Yes, yes! I know this topic has been asked 100 000 times, and I have even googled, and tried to research, but honestly... everything is so freaking confusing! The information is so mixed up!
From what I understand is that you need to root your phone in order to back up your TA Partition, but the problem is some devices has newer firmware model, which in this case isn't possible to backup TA Partition, unless you root, but then you have to unlock your bootloader which means you will loose the DRM Keys! There is of course way to root your phone, but then you must either be super lucky buying a new phone which has old firmware, or you have to downgrade.
Now, I am using the Xperia Z Ultra C6833 - Build Number: 14.1B.1.510, and from what I understand there is a way to root your phone, but then you cannot back up TA Partition. In this case, this makes no sense how to solve this problem. I even have heard you can download a chinese application, but from what I heard, they are steaing your IMEI numbers, and adding virus on it (true, or not?)
I have tried to use the Backup-TA-9.11, which doesn't work by the way, because root is required, and the Flash Tools by following the instruction turning on the Switch to Pro ---> Advanced--> Trim Area---> Back Up (doesn't work, because the color is grey).
I have even tried to take a look to downgrade the firmware, but the problem is that you will have to flash your phone, but this requires root or something, yes? (sorry for not understanding exactly this this problem, because to mix information around on the net).
Now, as you see, I really have dilemma, and I don't think I am the only one who have the problem with this. I am almost giving up to root this phone, like SRS no joke! Been researching couple of hours, and this is driving me nuts!
Hopefully someone could please help me and someone else around the world who have same problems like I do! Sorry for writing not very tidy, but hope you guys understand the idea what I am talking about here!
Thanks!
Ciex said:
Hey guys,
Yes, yes! I know this topic has been asked 100 000 times, and I have even googled, and tried to research, but honestly... everything is so freaking confusing! The information is so mixed up!
From what I understand is that you need to root your phone in order to back up your TA Partition, but the problem is some devices has newer firmware model, which in this case isn't possible to backup TA Partition, unless you root, but then you have to unlock your bootloader which means you will loose the DRM Keys! There is of course way to root your phone, but then you must either be super lucky buying a new phone which has old firmware, or you have to downgrade.
Now, I am using the Xperia Z Ultra C6833 - Build Number: 14.1B.1.510, and from what I understand there is a way to root your phone, but then you cannot back up TA Partition. In this case, this makes no sense how to solve this problem. I even have heard you can download a chinese application, but from what I heard, they are steaing your IMEI numbers, and adding virus on it (true, or not?)
I have tried to use the Backup-TA-9.11, which doesn't work by the way, because root is required, and the Flash Tools by following the instruction turning on the Switch to Pro ---> Advanced--> Trim Area---> Back Up (doesn't work, because the color is grey).
I have even tried to take a look to downgrade the firmware, but the problem is that you will have to flash your phone, but this requires root or something, yes? (sorry for not understanding exactly this this problem, because to mix information around on the net).
Now, as you see, I really have dilemma, and I don't think I am the only one who have the problem with this. I am almost giving up to root this phone, like SRS no joke! Been researching couple of hours, and this is driving me nuts!
Hopefully someone could please help me and someone else around the world who have same problems like I do! Sorry for writing not very tidy, but hope you guys understand the idea what I am talking about here!
Thanks!
Click to expand...
Click to collapse
You have almost the oldest firmware on earth on the phone, almost any method would root it, hell it's probably so full of security holes that if you blew on the phone you could feel it on the back
At the moment the latest 14.4.a.0.108 is easy to root with easyroot or [NUT]'s recovery installer, then just back up the TA. You can either update to the latest firmware using PC companion or flashing a FTF with the latest xxx.16.1 version of flashtool (http://flashtool.net)
So:
Upgrade to 14.4.a.0.108
Root
Backup TA
???
Profit
Really appreciate your answer. A Question, when I Googled the 14.4.a.0.108. It seems like this firmware is also compatible for Xperia Z1 and the other model as well. You sure this will be safe by using this firmware on Xperia Z Ultra?
For some reason I cannot Flash. I get error message:
15/025/2014 21:25:56 - INFO - <- This level is successfully initialized
15/025/2014 21:25:56 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
15/026/2014 21:26:01 - INFO - Device disconnected
15/026/2014 21:26:51 - INFO - Device connected with USB debugging off
15/026/2014 21:26:51 - INFO - For 2011 devices line, be sure you are not in MTP mode
15/026/2014 21:26:51 - INFO - Device connected with USB debugging on
15/026/2014 21:26:52 - INFO - Connected device : Sony Xperia Z Ultra
15/026/2014 21:26:52 - INFO - Installed version of busybox : N/A
15/026/2014 21:26:52 - INFO - Android version : 4.2.2 / kernel version : 3.4.0-perf-gde8296d-02194-ga2561a5 / Build number : 14.1.B.1.510
15/028/2014 21:28:15 - INFO - Selected null
15/028/2014 21:28:15 - INFO - Flash canceled
15/028/2014 21:28:38 - INFO - Selected Bundle for Sony Xperia Z Ultra (C6833). FW release : 14.4.A.0.108. Customization : 1275-9426
15/028/2014 21:28:38 - INFO - Preparing files for flashing
15/029/2014 21:29:07 - INFO - Device disconnected
15/029/2014 21:29:10 - INFO - Device connected in flash mode
15/029/2014 21:29:21 - INFO - Device disconnected
15/029/2014 21:29:29 - INFO - Device connected in flash mode
15/029/2014 21:29:47 - INFO - Selected Bundle for Sony Xperia Z Ultra (C6833). FW release : 14.4.A.0.108. Customization : 1275-9426
15/029/2014 21:29:47 - INFO - Preparing files for flashing
15/029/2014 21:29:47 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\system.sin
15/029/2014 21:29:47 - INFO - Cannot open bundle. Flash operation canceled
15/030/2014 21:30:07 - INFO - Selected Bundle for Sony Xperia Z Ultra (C6833). FW release : 14.4.A.0.108. Customization : 1275-9426
15/030/2014 21:30:07 - INFO - Preparing files for flashing
15/030/2014 21:30:07 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
15/030/2014 21:30:07 - INFO - Cannot open bundle. Flash operation canceled
15/030/2014 21:30:08 - INFO - Please connect your device into flashmode.
15/030/2014 21:30:08 - INFO - Opening device for R/W
15/030/2014 21:30:09 - INFO - Reading device information
15/030/2014 21:30:09 - INFO - Phone ready for flashmode operations.
15/030/2014 21:30:09 - INFO - Current device : C6833 - EP7334DKJD - 1276-1245_R9A - 1274-7565_14.1.B.1.510 - EURO-LTE_14.1.B.1.510
15/030/2014 21:30:09 - INFO - Start Flashing
15/030/2014 21:30:09 - INFO - Processing loader.sin
15/030/2014 21:30:09 - INFO - Checking header
15/030/2014 21:30:09 - INFO - Flashing data
15/030/2014 21:30:09 - INFO - Loader : S1_Root_6732 - Version : LOADER_RELEASE_MSM8974_28_AID_4 / Boot version : S1_Boot_MSM8974_LA1.0_56-A / Bootloader status : ROOTABLE
15/030/2014 21:30:09 - INFO - Processing partition-image.sin
15/030/2014 21:30:09 - INFO - Checking header
15/030/2014 21:30:09 - INFO - Flashing data
15/030/2014 21:30:09 - INFO - Parsing boot delivery
15/030/2014 21:30:09 - INFO - Phone boot version : S1_Boot_MSM8974_LA1.0_56-A. Boot delivery version : S1_Boot_MSM8974_Rhine1.2_LA1.04_19
15/030/2014 21:30:09 - INFO - Going to flash boot delivery
15/030/2014 21:30:09 - INFO - Processing emmc_appsboot_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
15/030/2014 21:30:09 - INFO - Checking header
15/030/2014 21:30:10 - INFO - Flashing data
15/030/2014 21:30:10 - INFO - Flashing Togari_S1BootConfig_MiscTA_130115_1430.ta
15/030/2014 21:30:10 - INFO - Writing TA unit : [00, 00, 08, 4F, 00, 00, 00, 49, 1A, CE, 1D, 00, 01, 00, 04, 05, 00, 02, 02, 51, 00, 10, 03, 00, 02, 04, 02, 05, 00, 01, 03, 02, 00, 10, 05, 00, 03, 03, 05, 00, 10, 0A, 00, 02, 00, A9, 09, BE, BA, A9, 09, 00, 00, 04, 00, 03, 00, 02, 00, 04, 00, 04, 00, B0, 04, 0E, 00, 06, 00, B8, 0B, 01, 4B, 00, 00, 00, 03, 96, 00, 2C, 01]
15/030/2014 21:30:10 - INFO - Writing TA unit : [00, 00, 08, FD, 00, 00, 00, 01, 00]
15/030/2014 21:30:10 - INFO - Processing dbi_S1_Boot_MSM8974_Rhine1.2_19_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
15/030/2014 21:30:10 - INFO - Checking header
15/030/2014 21:30:10 - INFO - Flashing data
15/030/2014 21:30:10 - INFO - Processing s1sbl_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
15/030/2014 21:30:10 - INFO - Checking header
15/030/2014 21:30:10 - INFO - Flashing data
15/030/2014 21:30:10 - INFO - Processing sbl1_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
15/030/2014 21:30:10 - INFO - Checking header
15/030/2014 21:30:10 - INFO - Flashing data
15/030/2014 21:30:10 - INFO - Processing tz_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
15/030/2014 21:30:10 - INFO - Checking header
15/030/2014 21:30:10 - INFO - Flashing data
15/030/2014 21:30:11 - INFO - Processing kernel.sin
15/030/2014 21:30:11 - INFO - Checking header
15/030/2014 21:30:11 - INFO - Flashing data
15/030/2014 21:30:13 - INFO - Processing rpm.sin
15/030/2014 21:30:13 - INFO - Checking header
15/030/2014 21:30:13 - INFO - Flashing data
15/030/2014 21:30:13 - INFO - Processing fotakernel.sin
15/030/2014 21:30:13 - INFO - Checking header
15/030/2014 21:30:13 - INFO - Flashing data
15/030/2014 21:30:15 - INFO - Ending flash session
15/030/2014 21:30:15 - ERROR - C:\Flashtool\.\firmwares\prepared\amss_fs_2.sin (The system cannot find the file specified)
15/030/2014 21:30:15 - ERROR - Error flashing. Aborted
15/030/2014 21:30:15 - INFO - Device connected in flash mode
15/030/2014 21:30:15 - INFO - Device disconnected
15/030/2014 21:30:21 - INFO - Device connected in flash mode
15/030/2014 21:30:33 - INFO - Log written to C:\Flashtool\flashtool_2014-07-15_09-25-56.log
check paths "ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\system.sin":
I managed to fix it!
Just a another quick question. It seems my phone doesn't have mobile data on, even I turned the it on.
Does it have something to do with the kernel or something?
You may need to reenter your apns or redownloaf them if your with a network.
Sent from my C6833 using XDA Premium 4 mobile app
Hi
I followed the guide here: http://goo.gl/b7NTn9
My problem is, I keep getting the error FAILED (remote: Command not allowed) as soon as I press "unlock" after I pasted the unlock code.
Can anyone perhaps help , please? I'm at my wits end on this one.
Log Dump:
Code:
24/052/2016 13:52:13 - INFO - Please connect your device into flashmode.
24/052/2016 13:52:21 - INFO - Device connected in flash mode
24/052/2016 13:52:21 - INFO - Opening device for R/W
24/052/2016 13:52:21 - INFO - Reading device information
24/052/2016 13:52:21 - INFO - Phone ready for flashmode operations.
24/052/2016 13:52:21 - INFO - Opening TA partition 2
24/052/2016 13:52:21 - INFO - Current device : E2303 - [COLOR="red"]DEVICE_CODE_HERE[/COLOR] - 1294-6067_R9A - 1291-5963_26.1.A.2.167 - GENERIC_26.1.A.2.167
24/052/2016 13:52:21 - INFO - Closing TA partition
24/052/2016 13:52:21 - INFO - Processing loader.sin
24/052/2016 13:52:21 - INFO - Checking header
24/052/2016 13:52:21 - INFO - Flashing data
24/052/2016 13:52:22 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_36 / Bootloader status : ROOTABLE
24/052/2016 13:52:22 - INFO - Max packet size set to 512K
24/052/2016 13:52:22 - INFO - Opening TA partition 2
24/052/2016 13:52:22 - INFO - Start Reading unit 000008B2
24/052/2016 13:52:22 - INFO - Reading TA finished.
24/052/2016 13:52:22 - INFO - Closing TA partition
24/052/2016 13:52:22 - INFO - Ending flash session
24/052/2016 13:52:22 - INFO - Now unplug your device and restart it into fastbootmode
24/052/2016 13:52:22 - INFO - Device connected in flash mode
24/052/2016 13:52:23 - INFO - Device disconnected
24/054/2016 13:54:13 - INFO - Device connected in fastboot mode
24/054/2016 13:54:32 - INFO - Unlocking phone using key [COLOR="red"]UNLOCK_KEY_HERE[/COLOR]
24/054/2016 13:54:32 - INFO - ...
24/054/2016 13:54:32 - INFO - FAILED (remote: Command not allowed)
24/054/2016 13:54:32 - INFO - finished. total time: 0.005s
Thank you for reading!
Have you checked to see if unlock is allowed? And if it says it can be unlocked, did you put the right imei for unlock. I found that the unlock code for the Xperia M worked fine
hy
exactly the same problem is occuring to me !
i tried to unlock the bootloader with different options for example the new and the old version of flashtool but it´s not working.
the rooting status is: Bootloader unlock allowed: Yes
i also noticed that when you put in your imei code on the sony developer page you have to put in 15 digits to get the ul-code but the flashtool just shows 14 digits of the imei code when you have to enter it.
i have the e2303 8Gb
build number 26.1.A.2.167
Android 5.0
Thank you !
ardentis said:
Have you checked to see if unlock is allowed? And if it says it can be unlocked, did you put the right imei for unlock. I found that the unlock code for the Xperia M worked fine
Click to expand...
Click to collapse
Thanks for replying! Yeah, I did all that, I tried the M and M2 unlock code, unlock is allowed, it just isn't doing anything though
Make sure you use the imei from the phone and not the unlock tool. It's purposely wrong to protect your imei if you share a picture of the unlock tool. Just keep trying
ardentis said:
Make sure you use the imei from the phone and not the unlock tool. It's purposely wrong to protect your imei if you share a picture of the unlock tool. Just keep trying
Click to expand...
Click to collapse
I have also the Problem, in the settings is Allowed, but the Software can't unlock the
the Bootloader well (remote: Command not allowed),
I have with Blu install't .1.128 but no way.
Do have tips for me?
i have read the Driver can under windows 8.1 a problem, but he find my Smartphone,
also must it work or?!
Greetz
Unlocking the bootloader in M4 Aqua
Was stuck with the same problem. M4, says its bootloader can be unlocked.
13/034/2016 22:34:37 - INFO - Unlocking phone using key XXXXXXXXXXXXXXX
13/034/2016 22:34:37 - INFO - ...
13/034/2016 22:34:37 - INFO - FAILED (remote: Command not allowed)
13/034/2016 22:34:37 - INFO - finished. total time: 0.005s
The solution is to enable OEM unlocking in the developer options. Also, in some cases, it helps to perform a factory reset before unlocking.
Good luck!
I had the same problem with " FAILED (remote: Command not allowed)", even though my device was stated as unlockable. It turned out all I needed to do was turn on "Allow OEM unlocking" in Developer options, on the phone. Then after power off again, fastboot eom unlock worked.
ethoms said:
I had the same problem with " FAILED (remote: Command not allowed)", even though my device was stated as unlockable. It turned out all I needed to do was turn on "Allow OEM unlocking" in Developer options, on the phone. Then after power off again, fastboot eom unlock worked.
Click to expand...
Click to collapse
Thanks bro. It worked
Hi
Same problem, and thanks for oem unlocking in developers menu option.
The unlock option works fine now
ethoms said:
I had the same problem with " FAILED (remote: Command not allowed)", even though my device was stated as unlockable. It turned out all I needed to do was turn on "Allow OEM unlocking" in Developer options, on the phone. Then after power off again, fastboot eom unlock worked.
Click to expand...
Click to collapse
i have same problem, but my device bootlop so i can't allow OEM unlocking. someone help me please? tanks
This thread is dead, but I'll post anyways. I am using xperia xz1c. Bootloader unlock is allowed. OEM unlocking is allowed. Device is being detected on fastboot devices command. On fastboot, the output I am getting is "FAILED (remote: command did not succeed)". I have tried latest platform tools 28.0.1, older platform tools 25.0.5 and 26.0.0 with no success. Thanks for reading.
I Recently Update my Xperia M4 Dual Sim Model E2363 to marshmallow but i am not able to root it
I also tried to unlock it bootlooder and even after being successfull i am not able to install Custom Recovery
Log In Flash tools
Phone ready for flashmode operations.
10/057/2016 21:57:41 - INFO - Opening TA partition 2
10/057/2016 21:57:41 - INFO - Current device : E2363 - YT9115MB7A - 1295-2357_R2C - 1296-1835_26.3.B.0.131 - GENERIC_26.3.B.0.131
10/057/2016 21:57:41 - INFO - Closing TA partition
10/057/2016 21:57:41 - INFO - No loader in the bundle. Searching for one
10/057/2016 21:57:41 - INFO - Processing loader.sin
10/057/2016 21:57:41 - INFO - Checking header
10/057/2016 21:57:41 - INFO - Flashing data
10/057/2016 21:57:43 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_207 / Bootloader status : NOT_ROOTABLE
10/057/2016 21:57:43 - INFO - Max packet size set to 512K
10/057/2016 21:57:43 - INFO - Opening TA partition 2
10/057/2016 21:57:43 - INFO - Start Reading unit 00 00 08 B2
10/057/2016 21:57:43 - INFO - Reading TA finished.
10/057/2016 21:57:43 - INFO - Closing TA partition
10/058/2016 21:58:06 - INFO - Unlocking device
10/058/2016 21:58:06 - INFO - Opening TA partition 2
10/058/2016 21:58:06 - INFO - Writing TA unit 000008B2. Value : 37 41 41 43 38 42 32 43 34 38 36 31 44 34 41 36
10/058/2016 21:58:06 - INFO - Closing TA partition
10/058/2016 21:58:07 - INFO - Unlock finished
10/002/2016 22:02:05 - INFO - Ending flash session
10/002/2016 22:02:05 - INFO - You can now unplug and restart your device
ScreenShot while installing Custom Recovery
Not able to post screenshot here
Here is the error i face while installing custom recovery
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30268 KB)...
OKAY [ 1.060s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.073s
Can someone provide me proper method to root and unlock my Xperia M4 Aqua
diamondfdk said:
I Recently Update my Xperia M4 Dual Sim Model E2363 to marshmallow but i am not able to root it
I also tried to unlock it bootlooder and even after being successfull i am not able to install Custom Recovery
Log In Flash tools
Phone ready for flashmode operations.
10/057/2016 21:57:41 - INFO - Opening TA partition 2
10/057/2016 21:57:41 - INFO - Current device : E2363 - YT9115MB7A - 1295-2357_R2C - 1296-1835_26.3.B.0.131 - GENERIC_26.3.B.0.131
10/057/2016 21:57:41 - INFO - Closing TA partition
10/057/2016 21:57:41 - INFO - No loader in the bundle. Searching for one
10/057/2016 21:57:41 - INFO - Processing loader.sin
10/057/2016 21:57:41 - INFO - Checking header
10/057/2016 21:57:41 - INFO - Flashing data
10/057/2016 21:57:43 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_207 / Bootloader status : NOT_ROOTABLE
10/057/2016 21:57:43 - INFO - Max packet size set to 512K
10/057/2016 21:57:43 - INFO - Opening TA partition 2
10/057/2016 21:57:43 - INFO - Start Reading unit 00 00 08 B2
10/057/2016 21:57:43 - INFO - Reading TA finished.
10/057/2016 21:57:43 - INFO - Closing TA partition
10/058/2016 21:58:06 - INFO - Unlocking device
10/058/2016 21:58:06 - INFO - Opening TA partition 2
10/058/2016 21:58:06 - INFO - Writing TA unit 000008B2. Value : 37 41 41 43 38 42 32 43 34 38 36 31 44 34 41 36
10/058/2016 21:58:06 - INFO - Closing TA partition
10/058/2016 21:58:07 - INFO - Unlock finished
10/002/2016 22:02:05 - INFO - Ending flash session
10/002/2016 22:02:05 - INFO - You can now unplug and restart your device
ScreenShot while installing Custom Recovery
Not able to post screenshot here
Here is the error i face while installing custom recovery
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30268 KB)...
OKAY [ 1.060s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.073s
Can someone provide me proper method to root and unlock my Xperia M4 Aqua
Click to expand...
Click to collapse
What's your bootloader status now? Even if Flashtool showed, that the unlock is finished, It doesn't mean that your bootloader is unlocked. Check the status of your bootloader, by typing this code in your dialer *#*#7378423#*#* , chose service info and then Configuration, and you will se there Rooting status. If it says it's unavailable, than It's not unlocked properly, or you can't unlock it, because it's . bootloader unlock allowed: NO , so that means, you cant unlock your bootloader. If your bootlader status shows Bootloader unlocked: Yes than, your bootlader is unlocked. In that case, you need to check the option OEM Unlocking in developer settings, it is supposed to be turned on. If you don't have that option in developer settings, then you need to flash different firmware (some firmware for different region/branding, doesn't have this option in developer settings). Flash the latest one. For example, Marshmallow has this option in developer settings.