Hi guys
I am really desperate with my cell phone, my E10i, i.e., SE x10 mini.
I have bought it in the end of 2010, and for about 1 year I have not used it.
Now my wife was starting to use it and she blocked the screen password that appears when you start it, (she tried more than 20 times
Of course, I do not remember the email to recover the pass since I do not used it for so much time, i tried several email of mine but none of them worked.
I searched the forum for all information to delete all info from the cell phone to factory settings but the problem is that has it is blocked I can not change the USB setttings in the cell menu.
I have tried it all, flashtool, PC Suite, PC Companion, S1tool but the main problem is that usb connection is off
The only one that detects the cell is flashtool im flashmode, when I try to flash it it gives message:
ERROR - (X10flash.java:374) - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
To flash my cell phone I need to download the firmware file? Where can I find it? Is this the reason I can not flash with flashtool right?
How can I solve this problem? Sorry but i am new in this....
Anyone can help me?
matrixpt76 said:
Hi guys
I am really desperate with my cell phone, my E10i, i.e., SE x10 mini.
I have bought it in the end of 2010, and for about 1 year I have not used it.
Now my wife was starting to use it and she blocked the screen password that appears when you start it, (she tried more than 20 times
Of course, I do not remember the email to recover the pass since I do not used it for so much time, i tried several email of mine but none of them worked.
I searched the forum for all information to delete all info from the cell phone to factory settings but the problem is that has it is blocked I can not change the USB setttings in the cell menu.
I have tried it all, flashtool, PC Suite, PC Companion, S1tool but the main problem is that usb connection is off
The only one that detects the cell is flashtool im flashmode, when I try to flash it it gives message:
ERROR - (X10flash.java:374) - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
To flash my cell phone I need to download the firmware file? Where can I find it? Is this the reason I can not flash with flashtool right?
How can I solve this problem? Sorry but i am new in this....
Anyone can help me?
Click to expand...
Click to collapse
hi bro, did you unlock your x10 mini bootloader???
Here are some solutions :
1- call your mobile when press back button, you are in menu, go to settings, accounts, add a new account .
Then next time you can add the new account information to remove pattern.
2- download stock frimware, add to frimware folder of flashtools (its in .ftf format) then go to drivers folder of flashtools and install "Gordon's gate "app to reinstall drivers
Open flash tools then press flashmode (other steps are easy)
Sent from my E15i using Tapatalk 2
matrixpt76 said:
Hi guys
I am really desperate with my cell phone, my E10i, i.e., SE x10 mini.
I have bought it in the end of 2010, and for about 1 year I have not used it.
Now my wife was starting to use it and she blocked the screen password that appears when you start it, (she tried more than 20 times
Of course, I do not remember the email to recover the pass since I do not used it for so much time, i tried several email of mine but none of them worked.
...
Anyone can help me?
Click to expand...
Click to collapse
Find the PUK code if you still have the original documentation, otherwise ask your provider for it.
jay-z-s said:
Here are some solutions :
1- call your mobile when press back button, you are in menu, go to settings, accounts, add a new account .
Then next time you can add the new account information to remove pattern.
2- download stock frimware, add to frimware folder of flashtools (its in .ftf format) then go to drivers folder of flashtools and install "Gordon's gate "app to reinstall drivers
Open flash tools then press flashmode (other steps are easy)
Sent from my E15i using Tapatalk 2
Click to expand...
Click to collapse
1. When I turn on the phone i can do it because pattern blocks acess to menu.
2. I'll try it and give you notice.
I have download firmware. Used flashtool to try to flash it but it gives an error:
10/038/2013 08:38:42 - INFO - <- This level is successfully initialized
10/038/2013 08:38:42 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
10/038/2013 08:38:42 - INFO - You can drag and drop ftf files here to start flashing them
10/038/2013 08:38:51 - INFO - Device connected with USB debugging off
10/038/2013 08:38:51 - INFO - For 2011 devices line, be sure you are not in MTP mode
10/038/2013 08:38:57 - INFO - Selected X10i_3.0.1.G.0.75_TMN-PT_GENERIC_1237-0324.ftf
10/038/2013 08:38:57 - INFO - Preparing files for flashing
10/039/2013 08:39:00 - INFO - Please connect your device into flashmode.
10/039/2013 08:39:03 - INFO - Device disconnected
10/040/2013 08:40:28 - INFO - Device connected in flash mode
10/040/2013 08:40:28 - INFO - Opening device for R/W
10/040/2013 08:40:29 - INFO - Reading device information
10/040/2013 08:40:29 - INFO - Phone ready for flashmode operations.
10/040/2013 08:40:29 - INFO - Current device : E10i - CNBC006278 - 1239-7455_R6B - 1235-3408_2.1.1.A.0.6 - WORLD-1-8_2.1.1.A.0.6
10/040/2013 08:40:29 - INFO - Start Flashing
10/040/2013 08:40:29 - INFO - Processing loader
10/040/2013 08:40:29 - INFO - Checking header
10/040/2013 08:40:29 - INFO - Ending flash session
10/040/2013 08:40:29 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Why it does not work? What am I doing wrong? Anyone can help?
matrixpt76 said:
I have download firmware. Used flashtool to try to flash it but it gives an error:
10/038/2013 08:38:42 - INFO - <- This level is successfully initialized
...
10/038/2013 08:38:57 - INFO - Selected X10i_3.0.1.G.0.75_TMN-PT_GENERIC_1237-0324.ftf
...
10/040/2013 08:40:29 - INFO - Current device : E10i - CNBC006278 - 1239-7455_R6B - 1235-3408_2.1.1.A.0.6 - WORLD-1-8_2.1.1.A.0.6
...
10/040/2013 08:40:29 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Why it does not work? What am I doing wrong? Anyone can help?
Click to expand...
Click to collapse
Be happy it failed, because you downloaded firmware for the big X10, and it could have bricked your phone. Get this, it's original E10i Sony firmware, flashable on a phone with a locked bootloader (and that is where your error came from). It's around 211Mb, although it may say something different when downloading, just wait till it's done.
Alomost done
SmG67 said:
Be happy it failed, because you downloaded firmware for the big X10, and it could have bricked your phone. Get this, it's original E10i Sony firmware, flashable on a phone with a locked bootloader (and that is where your error came from). It's around 211Mb, although it may say something different when downloading, just wait till it's done.
Click to expand...
Click to collapse
Thanks bro
You really helped me here
I flashed it and is working fine.
Now I just need to unlock it because I bought this in Portugal and now want to use it in Brazil.
Tried Crux Calculator but it does not work
Tried ezSEMC_S1_Android_v1.22 which give me this log:
Power off phone,press and hold Back or Volume Down key,attach usb cable
Waiting phone attach...OK
EROM VER: R8A029
CXC: 1229-3593
IMEI: 01240300518903
SIM_LOCK_ROOT: S1_SL_Root_a640
Model: E10i
Get server list...Fail
elapsed: 76Secs
Sent request id/psw for ezSEMC_S1_Android_v1.22 to user ferraripassion, to unlock it but still not received help or any help.
Hope someone can give me a hand here.
thx guys
please help????
Anyone??
matrixpt76 said:
Anyone??
Click to expand...
Click to collapse
Ask your portuguese provider for the emma/imei code
SmG67 said:
Ask your portuguese provider for the emma/imei code
Click to expand...
Click to collapse
I already have the Imei code (see my prior message), but what do I do with it?
matrixpt76 said:
I already have the Imei code (see my prior message), but what do I do with it?
Click to expand...
Click to collapse
put in the sim from your new provider, and when the phone starts up it will ask you for the code.
SmG67 said:
put in the sim from your new provider, and when the phone starts up it will ask you for the code.
Click to expand...
Click to collapse
When the phone starts with the sim from my new provider it gives the message: Introduce PIN for SIM NETWORK UNLOCK......this i do not understand, I put SIM IMEI but it does not work, says "Request for unlock network failed".
What maybe the problem here? What I am doing wrong?
matrixpt76 said:
When the phone starts with the sim from my new provider it gives the message: Introduce PIN for SIM NETWORK UNLOCK......this i do not understand, I put SIM IMEI but it does not work, says "Request for unlock network failed".
What maybe the problem here? What I am doing wrong?
Click to expand...
Click to collapse
There is an unlock code that works with your phone's imei code, you have to get it from your previous provider.
SmG67 said:
There is an unlock code that works with your phone's imei code, you have to get it from your previous provider.
Click to expand...
Click to collapse
Bro, I would gladly do that, the only problem is that vodafone only has local free calls,
So if i called from here I would surely pay more than 50€ just to get this information since we all know that assistance call there takes an eternity.
I have been here for more than a year in Brazil and give up to call them has it takes many time and €€€€ just to get 1 info from them....well I think i will give up to put this phone to work here.
matrixpt76 said:
Bro, I would gladly do that, the only problem is that vodafone only has local free calls,
So if i called from here I would surely pay more than 50€ just to get this information since we all know that assistance call there takes an eternity.
I have been here for more than a year in Brazil and give up to call them has it takes many time and €€€€ just to get 1 info from them....well I think i will give up to put this phone to work here.
Click to expand...
Click to collapse
Don't they have a website? My provider does it online, no need to call.
SmG67 said:
Don't they have a website? My provider does it online, no need to call.
Click to expand...
Click to collapse
They do not deliver that info online.
matrixpt76 said:
They do not deliver that info online.
Click to expand...
Click to collapse
That's a pain
Any more suggestion?
Anyone can give me any other solution?
Related
hello guys, I need help here ..
I just can not do flash my X10 mini pro, already try different versions of the flash tool and nothing ..
always gives the same error
"26/020/2012 22:20:15 - INFO - Preparing files for flashing
26/020/2012 22:20:16 - INFO - Searching Xperia ....
26/020/2012 22:20:16 - INFO - Found at USB \ VID_0FCE & PID_ADDE \ 5 & 0 & 5 & 10EF021E
26/020/2012 22:20:16 - INFO - Start Flashing
26/021/2012 22:21:22 - INFO -
26/021/2012 22:21:22 - INFO - Flashing loader
26/021/2012 22:21:22 - ERROR - Error flashing. Aborted
26/021/2012 22:21:22 - INFO - Now unplug the device and power it on
26/021/2012 22:21:22 - INFO - Then go to application settings
26/021/2012 22:21:22 - INFO - turn on and Debugging Unknown Sources "
always
What am I failing?
My device is:
Xperia X10 mini pro (u20i)
Android v2.1 Update 1 (operator Vodafone Portugal)
Karnel: 02/06/29 (SonyEricsson)
Number of compilation: 2.1.1.A.0.6
GreenFox07 said:
hello guys, I need help here ..
I just can not do flash my X10 mini pro, already try different versions of the flash tool and nothing ..
always gives the same error
"26/020/2012 22:20:15 - INFO - Preparing files for flashing
26/020/2012 22:20:16 - INFO - Searching Xperia ....
26/020/2012 22:20:16 - INFO - Found at USB \ VID_0FCE & PID_ADDE \ 5 & 0 & 5 & 10EF021E
26/020/2012 22:20:16 - INFO - Start Flashing
26/021/2012 22:21:22 - INFO -
26/021/2012 22:21:22 - INFO - Flashing loader
26/021/2012 22:21:22 - ERROR - Error flashing. Aborted
26/021/2012 22:21:22 - INFO - Now unplug the device and power it on
26/021/2012 22:21:22 - INFO - Then go to application settings
26/021/2012 22:21:22 - INFO - turn on and Debugging Unknown Sources "
always
What am I failing?
My device is:
Xperia X10 mini pro (u20i)
Android v2.1 Update 1 (operator Vodafone Portugal)
Karnel: 02/06/29 (SonyEricsson)
Number of compilation: 2.1.1.A.0.6
Click to expand...
Click to collapse
I think there are problems with drivers, the computer does not recognize your phone
Other
kulroyal said:
I think there are problems with drivers, the computer does not recognize your phone
Click to expand...
Click to collapse
Already got it, and yes, some files were missing ..
But now I'm the serious problem ..
I changed the kernel, but my SIM card is not recognized. it is recognized but you can not register on the network .. and I can not solve the problem ..
and thanks anyway
This forum is for xperia mini pro not the x10 mini pro. Look for x10 mini pro forum.
Sent from my SK17a using XDA App
strykme said:
This forum is for xperia mini pro not the x10 mini pro. Look for x10 mini pro forum.
Sent from my SK17a using XDA App
Click to expand...
Click to collapse
Sorry if someone can .. delete my Thread
We have same problem w/ my wt19i is there anyway you can help us guys.
ephraim25 said:
We have same problem w/ my wt19i is there anyway you can help us guys.
Click to expand...
Click to collapse
ok so you can't flash your phone?? mmmm and what do you want to flash?? is the bootloader unlocked?? do you have access to fastboot??
i don't want to sound rude as i am not being but please be more specific and before asking use the search function of the forum there are plenty of threads about this you only have to read.
ginryu said:
ok so you can't flash your phone?? mmmm and what do you want to flash?? is the bootloader unlocked?? do you have access to fastboot??
i don't want to sound rude as i am not being but please be more specific and before asking use the search function of the forum there are plenty of threads about this you only have to read.
Click to expand...
Click to collapse
It's all fine sir...
This is my LOG
I have this LOG on my Flashtool
05/054/2012 08:54:50 - INFO - <- This level is successfully initialized
05/054/2012 08:54:57 - INFO - Device connected with USB debugging on
05/054/2012 08:54:58 - INFO - Connected device : WT19
05/054/2012 08:54:58 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
05/054/2012 08:54:58 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
05/054/2012 08:54:59 - INFO - Root Access Allowed
05/055/2012 08:55:15 - INFO - Device disconnected
05/055/2012 08:55:31 - INFO - Device connected in flash mode
05/055/2012 08:55:43 - INFO - Selected Xperia Live (WT19i)_4.0.2.A.0.42_UA.ftf
05/055/2012 08:55:43 - INFO - Preparing files for flashing
05/056/2012 08:56:06 - INFO - Searching Xperia....
05/056/2012 08:56:06 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&32488A7&0&2
05/056/2012 08:56:06 - INFO - Start Flashing
05/056/2012 08:56:10 - ERROR - Error flashing. Aborted
05/056/2012 08:56:10 - INFO - Now unplug the device and power it on
05/056/2012 08:56:10 - INFO - Then go to application settings
05/056/2012 08:56:10 - INFO - turn on Unknown Sources and Debugging
05/056/2012 08:56:14 - INFO - Device disconnected
05/056/2012 08:56:28 - INFO - Device connected with USB debugging off
I already searched several threads regarding USB Debugging problems but nothing worked with my device.
Had installed these drivers theyve Linked, I only Repaired the Driver Problems
but the problem is still present during Flashmode, it states that My USB Debugging is OFF but Debugging Mode is already Enabled.
Device: WT19i
Locked Bootloader
Stock ROM .58 Firmware Gingerbread
I wanted to Upgrade to .62 Firmware Stockrom and then Unlock the Bootloader
Other Issue: Can't Upgrade to Firmware OTA.
ephraim25 said:
It's all fine sir...
I already searched several threads regarding USB Debugging problems but nothing worked with my device.
Had installed these drivers theyve Linked, I only Repaired the Driver Problems
but the problem is still present during Flashmode, it states that My USB Debugging is OFF but Debugging Mode is already Enabled.
Device: WT19i
Unlocked Bootloader
Stock ROM .58 Firmware Gingerbread
I wanted to Upgrade to .62 Firmware Stockrom and then Unlock the Bootloader
Other Issue: Can't Upgrade to Firmware OTA.
Click to expand...
Click to collapse
You have to enable both Debugging Mode and Unknown Source.
If you have unlocked bootloader, upgrading via OTA is not possible.
ephraim25 said:
Device: WT19i
Unlocked Bootloader
Stock ROM .58 Firmware Gingerbread
I wanted to Upgrade to .62 Firmware Stockrom and then Unlock the Bootloader
Other Issue: Can't Upgrade to Firmware OTA.
Click to expand...
Click to collapse
try upgrading firmware thru wotanserver...
why do want to update firmware then unlock?
what are you trying to accomplish?
the-osiris said:
You have to enable both Debugging Mode and Unknown Source.
If you have unlocked bootloader, upgrading via OTA is not possible.
Click to expand...
Click to collapse
That is my problem sir, just check the LOG
Debugging Mode and Unknown Source is already Enabled but In Flashmode
It will detect my device that Debugging Mode is off even though it is Already Enabled. Yes, I have still Locked Bootloader.
melander said:
try upgrading firmware thru wotanserver...
why do want to update firmware then unlock?
what are you trying to accomplish?
Click to expand...
Click to collapse
I want to Install Custom Rom, Hybrom, Because Feedback says that, Flashing
to Hybrom with stockrom .58 will have problems in during Boot Up. It will stack up on the SE Logo.
Man if you want to flash a custom rom you just have to unlock your bootloader you don't need to change your firmware or root first.
Does wotan server free of charge for flashing? it says i have invalid account even though I registered.
ephraim25 said:
Does wotan server free of charge for flashing? it says i have invalid account even though I registered.
Click to expand...
Click to collapse
Yes, WotanServer is free.
Make sure you entered correct email and password.
ephraim25 said:
I want to Install Custom Rom, Hybrom, Because Feedback says that, Flashing
to Hybrom with stockrom .58 will have problems in during Boot Up. It will stack up on the SE Logo.
Click to expand...
Click to collapse
i would disagree on that,
my friend has .58fw and unlocked his phone thru official method,
flashed bbooff kernel and installed hyborm v16 without any issues,
just make sure to wipe data, cache partition and dalvik..
ephraim25 said:
That is my problem sir, just check the LOG
Debugging Mode and Unknown Source is already Enabled but In Flashmode
It will detect my device that Debugging Mode is off even though it is Already Enabled. Yes, I have still Locked Bootloader.
I want to Install Custom Rom, Hybrom, Because Feedback says that, Flashing
to Hybrom with stockrom .58 will have problems in during Boot Up. It will stack up on the SE Logo.
Click to expand...
Click to collapse
Custom ROMs require custom kernel.
Sent from my WT19i using xda premium
melander said:
i would disagree on that,
my friend has .58fw and unlocked his phone thru official method,
flashed bbooff kernel and installed hyborm v16 without any issues,
just make sure to wipe data, cache partition and dalvik..
Click to expand...
Click to collapse
thanks you helped a lot, Flashing thru wotan server did the job, already updated my phone.
ephraim25 said:
I want to Install Custom Rom, Hybrom, Because Feedback says that, Flashing
to Hybrom with stockrom .58 will have problems in during Boot Up. It will stack up on the SE Logo.
Click to expand...
Click to collapse
Once again, it does not matter what ROM you have in first place(.58 or .62, MIUI, CM....does NOT matter).
You must install custom kernel ALSO, else phone will not boot.
Cleaning cache, dalvik cache and factory reset must also be done if installing new ROM.
1 More question sir, If I flashed a ROM to a Locked Network Unit, will it be openline after Flashing?
ephraim25 said:
1 More question sir, If I flashed a ROM to a Locked Network Unit, will it be openline after Flashing?
Click to expand...
Click to collapse
Custom ROMs require also custom kernel.
Custom kernel requires unlocked bootloader.
Unlocked bootloader requires Bootloader Unlock Allowed: Yes, which on some network locked phones is not like this.
Hi!
I got my Xperia S a day ago, rebranded it to Nordic firmware while waiting for my sim unlock code. Today received a message from second place that there some trouble with imei and code can not be provided. So I need to get back on rogers firmware in order to exchange it.
I have tried to do it my self but when flashing in the middle it returns an error
18/048/2012 14:48:50 - INFO - Phone ready for flashmode operations.
18/048/2012 14:48:50 - INFO - Start Flashing
18/048/2012 14:48:50 - INFO - Flashing loader
18/048/2012 14:48:51 - INFO - Ending flash session
18/048/2012 14:48:51 - ERROR - Error in processHeader
18/048/2012 14:48:51 - ERROR - Error flashing. Aborted
18/048/2012 14:48:51 - INFO - Device connected in flash mode
18/048/2012 14:48:52 - INFO - Device disconnected
18/048/2012 14:48:55 - INFO - Device connected in flash mode
now redownloaded and install flash tool again, created bundle now with error:
18/002/2012 15:02:27 - INFO - <- This level is successfully initialized
18/002/2012 15:02:30 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
18/002/2012 15:02:30 - INFO - You can drag and drop ftf files here to start flashing them
18/002/2012 15:02:39 - INFO - Device disconnected
18/002/2012 15:02:54 - INFO - Decrypting FILE_3
18/003/2012 15:03:58 - INFO - Decrypting FILE_2
18/004/2012 15:04:00 - INFO - Decrypting FILE_1
18/004/2012 15:04:01 - INFO - Decryption finished
18/004/2012 15:04:29 - INFO - Starting bundle creation
18/004/2012 15:04:29 - INFO - Adding loader.sin renamed as loader.sin to the bundle
18/004/2012 15:04:29 - INFO - Adding apps_log_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as apps_log.sin to the bundle
18/004/2012 15:04:29 - INFO - Adding partition-image_S1-SW-LIVE-DE72-PID1-0002-MBR.sin renamed as partition-image.sin to the bundle
18/004/2012 15:04:29 - INFO - Adding cache_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as cache.sin to the bundle
18/004/2012 15:04:30 - INFO - Adding amss_fsg_S1-MODEMSW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as amss_fsg.sin to the bundle
18/004/2012 15:04:30 - INFO - Adding amss_fs_1_S1-MODEMSW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as amss_fs_1.sin to the bundle
18/004/2012 15:04:30 - INFO - Adding system_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as system.sin to the bundle
18/005/2012 15:05:27 - INFO - Adding simlock.ta renamed as simlock.ta to the bundle
18/005/2012 15:05:27 - INFO - Adding amss_fs_2_S1-MODEMSW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as amss_fs_2.sin to the bundle
18/005/2012 15:05:27 - INFO - Adding userdata_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as userdata.sin to the bundle
18/005/2012 15:05:32 - INFO - Adding kernel_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as kernel.sin to the bundle
18/005/2012 15:05:32 - INFO - Adding fotakernel_S1-SW-LIVE-DE72-PID1-0002-S1-PARTITION.sin renamed as fotakernel.sin to the bundle
18/005/2012 15:05:33 - INFO - Finished bundle creation
18/005/2012 15:05:58 - INFO - Selected S_73_rogers.ftf
18/005/2012 15:05:58 - INFO - Preparing files for flashing
18/006/2012 15:06:20 - INFO - Please connect your device into flashmode.
18/006/2012 15:06:24 - INFO - Device connected in flash mode
18/006/2012 15:06:25 - INFO - Opening device for R/W
18/006/2012 15:06:25 - INFO - Reading device information
18/006/2012 15:06:25 - INFO - Phone ready for flashmode operations.
18/006/2012 15:06:25 - INFO - Start Flashing
18/006/2012 15:06:25 - INFO - Flashing loader
18/006/2012 15:06:27 - INFO - Loader : null - Version : R5C004 / Bootloader status : NOT_ROOTABLE
18/006/2012 15:06:27 - INFO - Flashing kernel.sin
18/006/2012 15:06:32 - INFO - Flashing fotakernel.sin
18/006/2012 15:06:36 - INFO - Flashing amss_fs_2.sin
18/006/2012 15:06:39 - INFO - Flashing amss_fs_1.sin
18/006/2012 15:06:40 - INFO - Flashing partition-image.sin
18/006/2012 15:06:40 - INFO - Ending flash session
18/006/2012 15:06:40 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0076";ERR_DYNAMIC="failed to set ta config";
Corrected ftf bundle by not including partition-image.sin
So far so good, flashed correctly.
Now everything is good.
hows the phone run on nordic firmware?
glad I've been reading, I'm having a hard time figuring out if i need to sim unlock before i unlock the boot loader.
as the statement above it seems you did not sim unlock first.
do i need to sim unloack a rogers locked xperia s first, before i unlock the bootloader?
Thanks
I just got an unlock code from MobileInCanada, took about 18 hours. Popped in my Bell Simcard and it worked. The thing is that the bootloader is still locked.
On Nordic firmware phone is running great, and best part no rogers start up screen and crapware apps!!! ( make sure you got rogers back up firmware just in case)
I think that if you use official boot loader unlock you have to sim unlock your phone first.
In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
What i noticed that before I sim unlocked my first xperia S (had dead pixels returned same day) it said No in that menu, and after sim unlock it changed to Yes.
Sim unlock does not unlock bootloader. You got to use sony mobile developer website and follow all instruction on there.
unlockbootloader.sonymobile.com/instructions
ok mine says unlock boot loader allowed = no
I ordered my sim unlock 2 hours ago, so i guess im done tonight. really dont want to setup my new toy just to do it again in a day or two.
Thanks
zimbashka said:
On Nordic firmware phone is running great, and best part no rogers start up screen and crapware apps!!! ( make sure you got rogers back up firmware just in case)
I think that if you use official boot loader unlock you have to sim unlock your phone first.
In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
What i noticed that before I sim unlocked my first xperia S (had dead pixels returned same day) it said No in that menu, and after sim unlock it changed to Yes.
Sim unlock does not unlock bootloader. You got to use sony mobile developer website and follow all instruction on there.
unlockbootloader.sonymobile.com/instructions
Click to expand...
Click to collapse
Mine didn't change to yes...
Matt1408 said:
Mine didn't change to yes...
Click to expand...
Click to collapse
Have you try unlockbootloader.sonymobile.com/instructions ?
zimbashka said:
Have you try unlockbootloader.sonymobile.com/instructions ?
Click to expand...
Click to collapse
2.In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Mine says no, can't be unlocked... I can try the rest of the steps, nothing will happen...
sorry don't know what to advise, have no phone on me any longer.
zimbashka said:
( make sure you got rogers back up firmware just in case)
Click to expand...
Click to collapse
How did you back up the rogers firmware?
still waiting for my sim unlock key from canadagsm.ca, might be a late one tonight. lol
What I did to back up rogers firmware is use SEUS to update your phone even if it has latest software. After update is successful go to C:\Program Files\Sony Ericsson\Update Service\ db folder there should be 3 files named FILE_XXXXX, (their size is 64kb,9487kb,288381kb you should have something similar).
Copy those 3 files to some folder that is easy for you to find.
Then open latest flashtool go to advanced>decrypt files
when window opens select folder where those files saved.
Select those 3 file and wait for it to finish decrypting.
Once it is done another window will pop up that will assist you to create ftf bundle. Just select all files accept for partition-image.sin and wait for it to finish. Created ftf bundle will be in directory where falashtool was instaled in folder called firmwares.
You are done!
Now you can flash your phone anytime you need to put Rogers firmware back in.
thanks, i have been using htc for a few months and coming back to se (sony) i feel as though im starting all over again.
do you know if you can enter the sim unlock code with out using a different sim? i don't have one.
if you need a sim from another carrier i guess ill have to buy one.
Yeah, you will need to use another sim card. I found an old Bell one and I cut it up to fit. Worked, but easy to screw up.
Matt1408 said:
Mine didn't change to yes...
Click to expand...
Click to collapse
I think that rebranding of the phone is necessary step for your phone to be boot loader unlockable. At least that is what I understand from reading forum.
I just got new xperia S (sim unlocked it few hours ago) will put another software and let you know if that changed anything.
edit:
Just finished with flasing still boot loader not unlockable.
ok i entered my sim unlock code and the service menu still says bootloader unlock allow=no
does this mean i cant use sony's site to unlock the bootloader?
I guess it's the same boat as I am on. I guess we have to wait for the test point method to become active. (And in the proccess tear apart our phones)
I really want to like this phone but it's hard to do with the Sony interface. I would love to load up some CM9 right now but I can't due to this stupid carrier crap. I do wish it was more like Europe were unlocked phones are not some kind of secret market.
Oh well, I guess I will have to do with using a custom launcher for now...
yeah it might be a while before the test point id ready.
i have a question for rogers users, in the service menu my model says, LT26i, should we not be LT26a
I thought se versions with i at the end was for international versions?
Yeah, I noticed that right away. I don't think an "a" version of the phone exists. I believe the "i" is just capable of all bands.
zimbashka said:
On Nordic firmware phone is running great, and best part no rogers start up screen and crapware apps!!! ( make sure you got rogers back up firmware just in case)
Click to expand...
Click to collapse
just had a thought, i wonder if using the ftf files of a rogers phone that can have the boot loader unlocked and using the se update service with those files would allow me to unlock the bootloader on se sites.?
maybe a dev can answer this.
Hi. I have a rooted xperia u.
It says
kernel-version:
2.6.35.7+
[email protected] #1
Build-Number:
6.0.B.1.564
It has been a long time ago, so i dont remember wich program i have used.
Now there is new firmware of sony (android 4 now i have android 2)
But i can't update it via the original way with pc companion it says i dont have a official version.
I want the original version, i have searched alot but i couldn't find any solution. thats why i made an account for xda.
I'm not sure this is the right forum to ask so plz correct me if i did it wrong.
I think the thread is right But can you tell me/us if your bootloader is locked or unlocked? Of course if you can
http://forum.xda-developers.com/showthread.php?t=1974430
Sent from my Xperia U using xda premium
bawss said:
Hi. I have a rooted xperia u.
It says
kernel-version:
2.6.35.7+
[email protected] #1
Build-Number:
6.0.B.1.564
It has been a long time ago, so i dont remember wich program i have used.
Now there is new firmware of sony (android 4 now i have android 2)
But i can't update it via the original way with pc companion it says i dont have a official version.
I want the original version, i have searched alot but i couldn't find any solution. thats why i made an account for xda.
I'm not sure this is the right forum to ask so plz correct me if i did it wrong.
Click to expand...
Click to collapse
The program is called Flashtool by Androxyde & Bin4ry, heres the link: androxyde.github.io
NOTE: If your bootloader is unlocked do not accept any Over-The-Air updates or through PC Companion/Bridge, that's why you got the error
lol98lol98 said:
I think the thread is right But can you tell me/us if your bootloader is locked or unlocked? Of course if you can
Click to expand...
Click to collapse
I dont know how, i have not done alot with phones.
@bawss
Have you tried repair with PC Companion?
ChikeD said:
@bawss
Have you tried repair with PC Companion?
Click to expand...
Click to collapse
PC Companion won't install my phone..
it says installing and then that it cant be installed.
bawss said:
PC Companion won't install my phone..
it says installing and then that it cant be installed.
Click to expand...
Click to collapse
if u unlocked your phone well just search for the stock ftf for you device and then flash it using the flashtool mentioned above this will update your phone to newer version although if u flash stock ftf i doesnt matter if u have loacked or unloacked bootloader you can flash it for both and if u didn't unlocked you bootloader then u can usee sus or pcc to get the update but
wich one
garvitdelhi said:
if u unlocked your phone well just search for the stock ftf for you device and then flash it using the flashtool mentioned above this will update your phone to newer version although if u flash stock ftf i doesnt matter if u have loacked or unloacked bootloader you can flash it for both and if u didn't unlocked you bootloader then u can usee sus or pcc to get the update but
Click to expand...
Click to collapse
Thanx for the reply, i went to the site mentioned and i see 10 links with diffrent software (i gues) and the link to the flash tool is death
If i try it with pc compannion it downloads the software, then it says shut your phone down.
then hold volume down and reconnect the usb.
I did that but then PCC says i have the wrong software on it and it can't be updated.
@bawss
Flashtool has new site http://www.flashtool.net
If PC Companion already download the files you can build the FTF file and flash with flashtool.
http://mytechencounters.wordpress.c...eate-an-ftf-file-of-your-xperia-ics-firmware/
I have installed flashtools now and have located the files downloaded by PCC
im useing the tutoral, and i am at step 6 but i cant click on advanced.
There is a SEUS decrypt option at tools but that wont let me select the files.
Is it right?
Hi,
I have tryd it with:
tools -> bundle creation -> browse location of files from PCC
Device: Xperia U
Branding : None
Version : version PCC says is available.
Is it the same as selecting the 3 files?
it has made a file called:
Xperia U_6.1.1.B.1.54_None.ttf
And if its right how can i flash it to the phone?
Click SEUS Decript, then the 3 dots right to source folder and navigate to the blob_fs folder select it and ok.
ChikeD said:
Click SEUS Decript, then the 3 dots right to source folder and navigate to the blob_fs folder select it and ok.
Click to expand...
Click to collapse
Ok it worked, i now have a ttf file from 363 mb what do i do now to set in on the phone? the last popupwindow with device selection didn't appear.
bawss said:
Ok it worked, i now have a ttf file from 363 mb what do i do now to set in on the phone? the last popupwindow with device selection didn't appear.
Click to expand...
Click to collapse
Yes it's a bit different with new flashtool but the result is just the same flashable FTF dilr.
Just click the flash icon in flashtool.and flash this file in flash mode.
EDIT: Exclude TA if it's in the file, just to be safe.
is it supposed to be done in 1 seconds.
I shut down the phone and connect it while holding volume down it says:
08/017/2013 21:17:08 - INFO - Start Flashing
08/017/2013 21:17:08 - INFO - Processing loader
08/017/2013 21:17:08 - INFO - Checking header
08/017/2013 21:17:08 - INFO - Flashing data
08/017/2013 21:17:09 - INFO - Loader : S1_Root_3065 - Version : R5E003 / Bootloader status : ROOTED
08/017/2013 21:17:09 - INFO - Disabling final data verification check
08/017/2013 21:17:09 - INFO - Ending flash session
08/017/2013 21:17:09 - INFO - Flashing finished.
08/017/2013 21:17:09 - INFO - Please unplug and start your phone
08/017/2013 21:17:09 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
08/017/2013 21:17:09 - INFO - Device connected in flash mode
08/017/2013 21:17:25 - INFO - Device disconnected
I restarted my phone but nothing has changed.should i unselect No Final Verification on the flash menu?
bawss said:
is it supposed to be done in 1 seconds.
I shut down the phone and connect it while holding volume down it says:
08/017/2013 21:17:08 - INFO - Start Flashing
08/017/2013 21:17:08 - INFO - Processing loader
08/017/2013 21:17:08 - INFO - Checking header
08/017/2013 21:17:08 - INFO - Flashing data
08/017/2013 21:17:09 - INFO - Loader : S1_Root_3065 - Version : R5E003 / Bootloader status : ROOTED
08/017/2013 21:17:09 - INFO - Disabling final data verification check
08/017/2013 21:17:09 - INFO - Ending flash session
08/017/2013 21:17:09 - INFO - Flashing finished.
08/017/2013 21:17:09 - INFO - Please unplug and start your phone
08/017/2013 21:17:09 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
08/017/2013 21:17:09 - INFO - Device connected in flash mode
08/017/2013 21:17:25 - INFO - Device disconnected
I restarted my phone but nothing has changed.should i unselect No Final Verification on the flash menu?
Click to expand...
Click to collapse
Are you sure you chose the right file to flash?
ChikeD said:
Are you sure you chose the right file to flash?
Click to expand...
Click to collapse
What a fool i am i selected the old file wich was very small, now i have it working on android 4 thank you so much for the helping !
Finaly google chrome on my phone haha
bawss said:
What a fool i am i selected the old file wich was very small, now i have it working on android 4 thank you so much for the helping !
Finaly google chrome on my phone haha
Click to expand...
Click to collapse
LOL I immediately disable chrome on my phone.
Which is it ICS or JB? You may be lower on ram now so it's good idea to uninstall apps you don't use and disable services/apps you don't need
ChikeD said:
LOL I immediately disable chrome on my phone.
Which is it ICS or JB? You may be lower on ram now so it's good idea to uninstall apps you don't use and disable services/apps you don't need
Click to expand...
Click to collapse
Ok wich browser is recomended then? it was boatware for xperia u i have android version : 4.0.4 now
Hi everybody!
When you try to upgrade operate system from version 2.1 (everything is the same as in the video) to version 4.x runs everything is fine until the moment you try to flash. BootLoader is unlocked. Mobile device is functional, just need higher OS version for application
link - video tutorial
hell, I'm a new user, I will not link here - I can send the email?
Lists me when you try to flash the device this error:
10/044/2014 16:44:45 - INFO - <- This level is successfully initialized
10/044/2014 16:44:53 - INFO - Selected E10_2.6.32.60-nAa-05.ftf
10/044/2014 16:44:53 - INFO - Preparing files for flashing
10/044/2014 16:44:54 - INFO - Please connect your device into flashmode.
10/045/2014 16:45:06 - INFO - Device connected in flash mode
10/045/2014 16:45:07 - INFO - Opening device for R/W
10/045/2014 16:45:07 - INFO - Reading device information
10/045/2014 16:45:07 - INFO - Phone ready for flashmode operations.
10/045/2014 16:45:07 - INFO - Start Flashing
10/045/2014 16:45:07 - INFO - Flashing loader
10/045/2014 16:45:08 - INFO - Ending flash session
10/045/2014 16:45:08 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ER R_DYNAMIC="SIN header verification failed"
Do not know what to do?
I use the same software as in the video, I can possibly send log from flashtool.
Thanks. VERY, VERY!
Milan 2514 said:
Hi everybody!
When you try to upgrade operate system from version 2.1 (everything is the same as in the video) to version 4.x runs everything is fine until the moment you try to flash. BootLoader is unlocked. Mobile device is functional, just need higher OS version for application
link - video tutorial
hell, I'm a new user, I will not link here - I can send the email?
Lists me when you try to flash the device this error:
10/044/2014 16:44:45 - INFO - <- This level is successfully initialized
10/044/2014 16:44:53 - INFO - Selected E10_2.6.32.60-nAa-05.ftf
10/044/2014 16:44:53 - INFO - Preparing files for flashing
10/044/2014 16:44:54 - INFO - Please connect your device into flashmode.
10/045/2014 16:45:06 - INFO - Device connected in flash mode
10/045/2014 16:45:07 - INFO - Opening device for R/W
10/045/2014 16:45:07 - INFO - Reading device information
10/045/2014 16:45:07 - INFO - Phone ready for flashmode operations.
10/045/2014 16:45:07 - INFO - Start Flashing
10/045/2014 16:45:07 - INFO - Flashing loader
10/045/2014 16:45:08 - INFO - Ending flash session
10/045/2014 16:45:08 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ER R_DYNAMIC="SIN header verification failed"
Do not know what to do?
I use the same software as in the video, I can possibly send log from flashtool.
Thanks. VERY, VERY!
Click to expand...
Click to collapse
Looks like your bootloader is not unlocked
Can you look at the output from S1Tool?
SmG67 said:
Looks like your bootloader is not unlocked
Can you look at the output from S1Tool?
Click to expand...
Click to collapse
Now I look at it, how do I know that it is not unlocked?
phone menu item added superuser
thanks
SmG67 said:
Looks like your bootloader is not unlocked
Can you look at the output from S1Tool?
Click to expand...
Click to collapse
X10 Flashing tool 0.7.1.0 write Root Access Allowed :-/
Milan 2514 said:
X10 Flashing tool 0.7.1.0 write Root Access Allowed :-/
Click to expand...
Click to collapse
Getting Root Access is NOT the same as unlocking your bootloader.
Root Access gives you access to the system files in the ROM part of the phone.
Bootloader unlocking gives you access to change the Kernel. So your bootloader is NOT unlocked by the rooting process.
SmG67 said:
Getting Root Access is NOT the same as unlocking your bootloader.
Root Access gives you access to the system files in the ROM part of the phone.
Bootloader unlocking gives you access to change the Kernel. So your bootloader is NOT unlocked by the rooting process.
Click to expand...
Click to collapse
Thank you, I understand, I'm finally someone explained clearly, there are some easy software to unlock?
Thank you very much
Milan 2514 said:
Thank you, I understand, I'm finally someone explained clearly, there are some easy software to unlock?
Thank you very much
Click to expand...
Click to collapse
Flashtool will do it, but you have to be careful.
There are some checks to be done before you go and unlock it because it can break your phone. There is a link in the kernel-thread to unlocking the bootloader, that will tell you what to look for to see if it's safe. If it is you can unlock it with flashtool.
SmG67 said:
Flashtool will do it, but you have to be careful.
There are some checks to be done before you go and unlock it because it can break your phone. There is a link in the kernel-thread to unlocking the bootloader, that will tell you what to look for to see if it's safe. If it is you can unlock it with flashtool.
Click to expand...
Click to collapse
Ok, thank you for your answer, I'll look into it. Thank you very much for your help, if something hits it, I'll write more here
SmG67 said:
Flashtool will do it, but you have to be careful.
There are some checks to be done before you go and unlock it because it can break your phone. There is a link in the kernel-thread to unlocking the bootloader, that will tell you what to look for to see if it's safe. If it is you can unlock it with flashtool.
Click to expand...
Click to collapse
Hi, thanks to your Board of everything I did, thanks again. There was yet another problem once tel after the completion of all events will go with the version E10i JBMP Release 4 (based on a E_10_2.3.62, freezes on the welcome screen in the setup first run .. anything that is not responding, phone is unavailable, unfortunately it can not connect to or pc and I can not do on the memory card to record another version of Android. tried to repeat the process but without success ... what? thank you very much
Milan 2514 said:
Hi, thanks to your Board of everything I did, thanks again. There was yet another problem once tel after the completion of all events will go with the version E10i JBMP Release 4 (based on a E_10_2.3.62, freezes on the welcome screen in the setup first run .. anything that is not responding, phone is unavailable, unfortunately it can not connect to or pc and I can not do on the memory card to record another version of Android. tried to repeat the process but without success ... what? thank you very much
Click to expand...
Click to collapse
Hi, the problem is solved .. I recorded a higher kernel version 2.3.32.61_06 and everything goes as it should . Thanks so much for your help
I'm getting an error when trying to unlock my phone's bootloader :
FAILED remote: Command not allowed.
I am copy/pasting "fastboot -i 0x0fce oem unlock 0xBEA3575C8951F712"
When I type "fastboot devices" it recognizes my device, and I installed all the drives from flashtool so I don't think its a driver issue.
I've tried using flashtool, the sdk, and minimal adb and falshboot. For flashtool I've tried adding the ulcode.txt to registerd devices folder.
I've tried different PC's and different cables. I've also tried it on androids 5, 6, 7, all of which I've flashed from the flashtool download tool (Custom UK versions).
I have USB Debuggin on, OEM unlock on, and Unkonwn Sources on. When I type *#*#7378423*#*# the phone says "Bootloader unlock allowed : yes".
A final thing to note is when I flashed android 7 the OEM unlock butto was grayed out - "Bootloader already unlocked", even though the *#*#.... code still said "Bootloader unlock allowed : yes".
I've searched all the forums and none of the fixes seem to work. Any help would be greatly appreciated - thanks!
Edit : I tried this on my old z1 compact and it worked, so its nothing wrong with my computer. I guess my z5 is just broken.
Nope, I am having the exact same issue you are. I have model E5823.
Got the unlock code off sony.
Trying everthing I can.. Can't get past that damn FAILED (remote: Command not allowed). error.
Installed 5 different fastboot/adb programs, sony drivers are latest. fastboot and adb do work, they see the device OK, it just won't accept any unlocking.
Unlockable is yes, in service settings view.
I am currently in the middle of trying to get the sony emma flashtool program to actually access my phone - it just gives me a "phone is locked" message..
going to try flashing a stock ROM with flashtool next.. but you're not giving me hope.
It is possible, because sony itself says it is, and there are other people out there who have done it. There must be a way.
Hey guys,
same here.
After fastboot fails to unlock the bootloader with
fastboot -i 0x0fce oem unlock 0xKEY
Click to expand...
Click to collapse
I tried it with flashtool and this post https://forum.xda-developers.com/showpost.php?p=58070067&postcount=34 and it worked!
But now I want to flash the modified kernel with TWRP and SuperSU with
fastboot flash boot kernel.img
Click to expand...
Click to collapse
but without success
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Same in Flashtool using option >>>>lightning icon"/Fastboot mode/Select kernel to Flash/path to boot.img.
Now bootloader is unlocked but DRM Keys still activ - if i can trust the system information.
Backup the TA-Partition was successful with iovyroot.
Whats wrong with this piece of plastic? I'm rooted all my Galaxy's before, but without any problems - this Z5c is annoying. And only because I want to change my MAC address, because my wife has same phone and same MAC Both in the same network isn't good.
Anybody who can help?
Thanks!
lfjriazr6kp6w95 said:
Hey guys,
same here.
After fastboot fails to unlock the bootloader with
I tried it with flashtool and this post https://forum.xda-developers.com/showpost.php?p=58070067&postcount=34 and it worked!
But now I want to flash the modified kernel with TWRP and SuperSU with
but without success
Same in Flashtool using option >>>>lightning icon"/Fastboot mode/Select kernel to Flash/path to boot.img.
Now bootloader is unlocked but DRM Keys still activ - if i can trust the system information.
Backup the TA-Partition was successful with iovyroot.
Whats wrong with this piece of plastic? I'm rooted all my Galaxy's before, but without any problems - this Z5c is annoying. And only because I want to change my MAC address, because my wife has same phone and same MAC Both in the same network isn't good.
Anybody who can help?
Thanks!
Click to expand...
Click to collapse
You helped me fix it! Turns out I had named my ulcode file ulcode.txt so it was actually ulcode.txt.txt
I still don't get why adb didn't work but flashtool does, though.
For your other point, I used this guide to flash a kernel.sin:
https://twigstechtips.blogspot.ca/2016/04/sony-z5-compact-root-without-losing-ta.html
Hope it helps, and thanks again!!!!!
lfjriazr6kp6w95 said:
>> I tried it with flashtool and this post ***pasted*** and it worked!
1.: Go to the folder where Flashtool was installed
2.: Open the folder named "custom"
3.: Open the folder named "mydevices" (if it exists, in my case Flashtool version 0.9.18.4)
4.: Right button, New, Folder. Name the folder with your device code.
5.: Open the folder created previously
6.: Right button, New, Text Document. Name the text document as ulcode
7.: Open the text document created previously
8.: Paste your unlock code and save
9.: Open Flashtools and try the BLU option again.
obs 1: the step #3 I think it depends on your Flashtool version, because it wasn't mentioned at the solution
obs 2: at the step #4 is mentioned your device code. your device code is showed in the log when you click the button BLU, at the "Current device", after your device model.
Search a line like:
09/045/2015 23:45:08 - INFO - Current device : C2104 - AB100C2DE3 - 1272-4136_R5B - 1269-5420_15.3.A.1.17 - WORLD-a_15.3.A.1.17
in this case, the device code is AB100C2DE3 and this should be the new folder name (step 4)
Click to expand...
Click to collapse
I tried that method, it does not work. It SEEMS to work from face value, yes, but it is faulty I think.
Also, the location of the folder is wrong - it should go in /users/USERNAME/.flashtool/registeredDevices/
It 'unlocks' it during the flash stage of BLU in flashtool, yes, but it's supposed to do it in the fastboot stage according to other instructions I've read! It also freezes up and does not complete the operation unless I 'cancel' it - but it's supposed to go through a wipe process. It never does.
The system info has no status on whether or not it's unlocked or unlockable after flashtool 'unlocks' it using that method. Also, no other flashing can be done, because it returns the same Command not allowed error every time.
I believe fastboot is set up correctly as it returns getversion 0.5 and the device shows up in fastboot devices. I checked the IMEI was a correct one by going to imei.info. Don't know what else to do.
Why the heck are our devices refusing to unlock when others are doing it fine, and it's claiming to be unlockable?!?
I returned my Z5C and got a new one from the manufacturer and it's again refusing to unlock.
Hi,
I am late on this thread, but just buy a Z5C and face exactly that situation : no way to unlock the device ! Using flashtool and BLU results as a Rooting Status unknown, so I have to unlock the device using flashtool again...
The only thing I succeed is to flash the latest firmware with the help of XperiFirm. Still have "Bootloader unlock allowed : yes" but impossible to unlock it.
Has anyone found a solution for that problem ? Could it be related to a specific firmware to install ?
I am totally lost after two days of reading and unsuccessful attempts ; I would really like to install LineageOS on my new Z5C.
Any help would be greatly appreciated. Thanks.
Hi,
After some hours fighting with windows, drivers, signature (all in a VM), I switched back to Linux/Ubuntu. At least flashtool seems to work better (out of the box), and it asks me to reconnect the device in fastboot mode... But still the same error at the end. It adds "Maybe the OEM is not enabled", but it is of course (double checked).
But what means "Bootloader status : ROOTABLE" ? Did I miss something ?
Can somebody help please ? I contacted Sony support, but they don't support such operation...
Here is the log from flashtool :
====================
05/032/2018 17:32:18 - INFO - Please connect your device into flashmode.
05/032/2018 17:32:35 - INFO - Opening device for R/W
05/032/2018 17:32:35 - INFO - Device ready for R/W.
05/032/2018 17:32:35 - INFO - Reading device information
05/032/2018 17:32:36 - INFO - Phone ready for flashmode operations.
05/032/2018 17:32:36 - INFO - Opening TA partition 2
05/032/2018 17:32:37 - INFO - Current device : E5823 - CB5A274154 - 1299-1743_R12C - 1295-6639_32.2.A.5.11 - GENERIC_32.2.A.5.11
05/032/2018 17:32:37 - INFO - Closing TA partition
05/032/2018 17:32:37 - INFO - No loader in the bundle. Searching for one
05/032/2018 17:32:37 - INFO - Processing loader.sin
05/032/2018 17:32:37 - INFO - Checking header
05/032/2018 17:32:37 - INFO - Flashing data
05/032/2018 17:32:37 - INFO - Loader : S1_Root_f936 - Version : MSM8994_41 / Boot version : S1_Boot_MSM8994_LA1.2.2_42B / Bootloader status : ROOTABLE
05/032/2018 17:32:37 - INFO - Max packet size set to 4M
05/032/2018 17:32:37 - INFO - Opening TA partition 2
05/032/2018 17:32:37 - INFO - Start Reading unit 00 00 08 B2
05/032/2018 17:32:37 - WARN - ERR_SEVERITY="MINOR";ERR_CODE="0025";ERR_DYNAMIC="00000000";
05/032/2018 17:32:37 - INFO - Closing TA partition
05/032/2018 17:32:37 - INFO - Ending flash session
05/032/2018 17:32:37 - INFO - Now unplug your device and restart it into fastbootmode
05/033/2018 17:33:51 - INFO - Unlocking phone using key AF668B4FXXXXXXXX
05/033/2018 17:33:51 - INFO - ...
05/033/2018 17:33:51 - INFO - FAILED (remote: Command did not succeed)
05/033/2018 17:33:51 - INFO - finished. total time: 0.032s
05/033/2018 17:33:51 - WARN - Maybe the OEM is not enabled
05/033/2018 17:33:58 - INFO - Device disconnected
05/033/2018 17:33:58 - INFO - Device connected in fastboot mode
05/034/2018 17:34:07 - INFO - Device disconnected
I give up ! Tried almost everything (Win7x32, Win8.1x64, Flashtool v0.9.25 & 0.9.23 with ulcode.txt file created in user profile, Ubuntu, adb/fastboot command, from simple package, or Android studio), without any success. Some feedback though about Flashtool :
> Much easier to use the Linux version. On Ubuntu 18.10, it just works out of the box. I can easily flash the latest firmware ("Customized FR" in my case) though I downloaded it with Xperifirm on windows, as I did want to install mono on my Ubuntu desktop. At least I am now running Android 6.0.1.
> With version 0.9.25, I can use UBL button, Flashtool asks first for connect device in Flashboot mode (green light), then asks to disconnect and reconnect in Fastboot mode (blue But same error at the end : FAILED (remote: Command did not succeed). After a reboot, I can see "Rooting status : Unknown" in the service page.
> If I reflash, unknown rooting status is still there. I have to use Flashtool 0.9.23.2 (found link on another xda thread, only for windows) to "relock" the device and get back the "Bootloader unlock allowed : yes".
I don't understand what happens, what is the reason for that... Total mystery to me. There are so many posts about this issue, no one gives a real solution, Sony support does not care.
I am sad to be unable to install LineageOS on my device... Now will look how to "clean" Xperia Android as much as possible. Don't know if this is even possible. Don't know if I can root my phone, etc...
Last, why did I buy a Sony Z5C ? was looking for small (4.6") & afordable phone with good camera... Never thought I would be unable to install LineageOS.
That does sound frustrating. Have you checked the settings in the developer options? There's one there about "allow oem unlocking". If it's not set, you can't do it from fastboot, so maybe that's your problem? It's worth a try, at the very least.
tonsofquestions said:
That does sound frustrating. Have you checked the settings in the developer options? There's one there about "allow oem unlocking". If it's not set, you can't do it from fastboot, so maybe that's your problem? It's worth a try, at the very least.
Click to expand...
Click to collapse
Yes, I checked that for sure... Same for "Enable USB debug" and "Allow Unknown sources" in Security options.
Yesterday, as a last try, I follow that thread : I flashed old Lollipop firmware (E5823_32.0.A.6.200), backup TA partition, and tried unlock booloader again : same error FAILED (remote: Command did not succeed).
Probably something changed on Sony side that makes unlocking bootloader impossible ? That's what I think now.
Hmm, and in the service menu it says bootloader locking is allowed?
I'd be very surprised if Sony changed anything recently (if they even could, on a released phone), and I was able to do it successfully a few weeks back.
What's the error if you use an invalid unlock key? Maybe there's a typo (or request it from Sony again)? I know I'm grasping at straws, but I'm otherwise not sure. I had no difficulties at all...
tonsofquestions said:
Hmm, and in the service menu it says bootloader locking is allowed?
I'd be very surprised if Sony changed anything recently (if they even could, on a released phone), and I was able to do it successfully a few weeks back.
What's the error if you use an invalid unlock key? Maybe there's a typo (or request it from Sony again)? I know I'm grasping at straws, but I'm otherwise not sure. I had no difficulties at all...
Click to expand...
Click to collapse
Yes, Bootloader is OK, and providing a invalid unlock results in the same error : FAILED (remote: Command did not succeed).
From Sony website, you always get the same number when providing your EMEI.
Note there tones of threads about this issue, and really no clear solution, at least none from what I tried...
hi man!. Have you figure out how to unlock the bootloader? Same situation over here. This is my 3th xperia but first time facing this issue. Tomorrow I will install win 7 and will see if works
minos_cr said:
hi man!. Have you figure out how to unlock the bootloader? Same situation over here. This is my 3th xperia but first time facing this issue. Tomorrow I will install win 7 and will see if works
Click to expand...
Click to collapse
Unfortunately no. It is still the same, and I gave up for now, as I tried everything I could.
But I have a last plan : my Z5C is now running Android 6.0.1, which I installed myself using Flashtool & Xperifirm. Actually I got that phone with Android 5.1.1, and no upgrade was available when looking at system parameters, or even the Sony website). So I did it myself, using last package for French in Xperifirm.
And now, when looking at http://www.sonymobile.com/update, providing my EMIE code, it says my phone is up to date and running Android 7.1, which is wrong.
So I contacted Sony support for that, and they asked me to run a System -> Factory settings -> ReInit -> Clear everything. (or something simmilar).
I did not do it, because I am pretty sure this will not work, and I will probably go back to Android 5.1.1.
But I may contact the repair service (http://support.sonymobile.com/fr/repair/) and send my phone back to them asking for Android 7.1. I can complain for that, because my warranty is still valid !
My last hope is that when I will get back the phone from them, totally reinitialized, unlocking may work !!
I cannot do it for now, because I am going to move the next 2 months, but will try this when I am back. As I said, this is my last hope, unless someone find a solution to that problem.
Good luck to you, and keep us informed... By the way, which Android version are you running, and what says the Sony update site ?
man, yesterday I was frustrated too. Today, I installed windows 7 (it was a pain in the a**) and flashtool did the job like a champ.
pled said:
Unfortunately no. It is still the same, and I gave up for now, as I tried everything I could.
But I have a last plan : my Z5C is now running Android 6.0.1, which I installed myself using Flashtool & Xperifirm. Actually I got that phone with Android 5.1.1, and no upgrade was available when looking at system parameters, or even the Sony website). So I did it myself, using last package for French in Xperifirm.
And now, when looking at http://www.sonymobile.com/update, providing my EMIE code, it says my phone is up to date and running Android 7.1, which is wrong.
So I contacted Sony support for that, and they asked me to run a System -> Factory settings -> ReInit -> Clear everything. (or something simmilar).
I did not do it, because I am pretty sure this will not work, and I will probably go back to Android 5.1.1.
But I may contact the repair service (http://support.sonymobile.com/fr/repair/) and send my phone back to them asking for Android 7.1. I can complain for that, because my warranty is still valid !
My last hope is that when I will get back the phone from them, totally reinitialized, unlocking may work !!
I cannot do it for now, because I am going to move the next 2 months, but will try this when I am back. As I said, this is my last hope, unless someone find a solution to that problem.
Good luck to you, and keep us informed... By the way, which Android version are you running, and what says the Sony update site ?
Click to expand...
Click to collapse
I imagine (but can't say for certain) that whatever check Sony is using to display that info is either the last version that "called home" (maybe it needs the Xperia Companion software?), or the latest version that the phone was ever updated to. If you flash an old one with Flashtool (or worse: never connect to the internet with it), how on earth would you expect them to know the right version? Why would it even matter? The OS version is (largely) unrelated to the fastboot version, and shouldn't affect unlocking, other than the "allow oem unlocking" option in the developer settings.
I agree that the factory reset will leave it on the same OS; there's no reason it would upgrade.. I'm not sure why the OS wouldn't show updates available, maybe that customization version never had more releases. But is there any reason not to just download it and flash with Flashtool?
I couldn't find any other threads with people reporting problems - the majority of reports I saw were of successes. Not that I don't believe what you're seeing, mind you, just that I know there have been a lot of people getting things to work without a lot of issues.
minos_cr said:
man, yesterday I was frustrated too. Today, I installed windows 7 (it was a pain in the a**) and flashtool did the job like a champ.
Click to expand...
Click to collapse
Would be happy to know which Win7 (x32 or x64) and which flashtool version you used. Also if you setup the ulcode.txt file ?
---------- Post added at 09:59 AM ---------- Previous post was at 09:40 AM ----------
tonsofquestions said:
I imagine (but can't say for certain) that whatever check Sony is using to display that info is either the last version that "called home" (maybe it needs the Xperia Companion software?), or the latest version that the phone was ever updated to. If you flash an old one with Flashtool (or worse: never connect to the internet with it), how on earth would you expect them to know the right version? Why would it even matter? The OS version is (largely) unrelated to the fastboot version, and shouldn't affect unlocking, other than the "allow oem unlocking" option in the developer settings.
I agree that the factory reset will leave it on the same OS; there's no reason it would upgrade.. I'm not sure why the OS wouldn't show updates available, maybe that customization version never had more releases. But is there any reason not to just download it and flash with Flashtool?
I couldn't find any other threads with people reporting problems - the majority of reports I saw were of successes. Not that I don't believe what you're seeing, mind you, just that I know there have been a lot of people getting things to work without a lot of issues.
Click to expand...
Click to collapse
Well, this is a mystery to me. What I can say is that Sony website displays now :
Votre Xperia Z5 Compact est à jour !
Sortie : 32.2.A.5.11
Informations sur mon Android™
Android™ 7.1 Nougat est publié pour Xperia Z5 Compact.
Initially, I got the phone with Version 32.0.A.6.200. So they know somewhere I did an upgrade.
I would be happy to download the 7.1 version, but using Xperifirm, the only one I can find for the French country is the one I got, resulting in Android 6.0.1.
And because I have no knowledge at all on Sony specific things, I did try another firmware : I don't want to brick my phone.
Honestly, I have tried everything I could (Linux, Win, adb, flshtool, x32, x64, ulcode.txt, etc...) will always the same error, despite I agree most of people appears to success at one time. But most of the time without any clear explanation of what happen ! (except ulcode file story).
I read somewhere my problem could be related to the "Customization Version" (1299-1743_R12C in my case). Don't even understand what it could be related to, and how to change it.
What I expect is that Sony repair service will wipe everything on my phone, so that I could unlock it after it that.
Would be happy to know which Win7 (x32 or x64) and which flashtool version you used. Also if you setup the ulcode.txt file ?
Click to expand...
Click to collapse
I've personally used both Windows 10 (x64) and Linux. I used the latest version of Flashtool (0.9.25.0) and 0.9.24.4, though I couldn't tell you which combination I used on which OS.
[OS woes]
Let's start from the beginning. What OS are you trying to get to. Why?
Also note that there are multiple download versions in XperiFirm for your 1299-1743, make sure you're taking the right one.
I see 32.2.A.5.11, which it looks like you have (according to the earlier screenshot), which should be Marshmallow.
I also see 32.4.A.1.54, which should be Nougat.
Either should be straightforward to install with FlashTool (it sounds like you installed 5.11 with it?).
In the end, the customization option is mostly some regional differences - language, built-in apps, some VoLTE/fingerprint options for some regions, etc. Nothing significant ... or important if all you want to do is unlock it. That should be completely independent of the OS version.
Downgraing your OS and unlocking the bootloader should both end up resetting your phone/wipe the data.
So you should back up anything you want, and then mess around from there. I also fear the Sony Repair will wipe data, but it s also called "repair" so maybe it will backup/restore some of it. I'm not sure.
It's also possible that something is wonky with the OEM unlock setting, so wiping data will kick it back into working. It can't hurt to try, and is certainly easier than sending in a phone...
tonsofquestions said:
So you should back up anything you want, and then mess around from there. I also fear the Sony Repair will wipe data, but it s also called "repair" so maybe it will backup/restore some of it. I'm not sure.
It's also possible that something is wonky with the OEM unlock setting, so wiping data will kick it back into working. It can't hurt to try, and is certainly easier than sending in a phone...
Click to expand...
Click to collapse
Thank you for your advice. Will try again from scratch when I am back from travelling : 2 months in Asia ! At least, I will benefit of the "panorama" feature from the Sony camera that I may lose with LineageOS !