Hi. I've received my XL from service centre. They have replaced mainboard, and it came with locked bootloader. I've generated unlock code, and tried to unlock it. It said this:
Code:
G:\Flashtool\x10flasher_lib>fastboot.exe -i 0x0fce oem unlock 0x1D3FFE653484EEBF
...
FAILED (remote: Command did not succeed)
finished. total time: 0.023s
G:\Flashtool\x10flasher_lib>fastboot.exe -i 0x0fce oem unlock 0x1D3FFE653484EEBF
...
OKAY [ 0.060s]
finished. total time: 0.061s
G:\Flashtool\x10flasher_lib>
It worked only after second try. I see this thing for the first time. Why is this happening? After flashing kernel, the phone doesn't boot, and after coming back to fastboot i can't flash any kernel. It seems like the bootloader isn't unlocking fully.
After booting phone again to fastboot and trying to flash a kernel the console says
Code:
G:\Flashtool\x10flasher_lib>fastboot flash boot bootjbtwrp.img
sending 'boot' (8224 KB)...
OKAY [ 0.263s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.267s
G:\Flashtool\x10flasher_lib>
Download and flash the ftf for your region from here. http://forum.xda-developers.com/xperia-l/general/sony-xperia-l-flashable-ftfs-locked-t2560642
Now boot your phone again.
Go to dialer and type *#*#7378423#*#*
From service info, enter configuration. If bootloader unlocked says "Yes", your bootloader is unlocked. If not, then your bootloader unlock obviously failed.
From what I know, after you unlock bootloader, you have to flash ftf again. I did it, flashed a new kernel and installed CM11 with no problems.
eus4ni4 said:
Download and flash the ftf for your region from here. http://forum.xda-developers.com/xperia-l/general/sony-xperia-l-flashable-ftfs-locked-t2560642
Now boot your phone again.
Go to dialer and type *#*#7378423#*#*
From service info, enter configuration. If bootloader unlocked says "Yes", your bootloader is unlocked. If not, then your bootloader unlock obviously failed.
From what I know, after you unlock bootloader, you have to flash ftf again. I did it, flashed a new kernel and installed CM11 with no problems.
Click to expand...
Click to collapse
It says:
Rooting status:
Bootloader unlocking allowed
I just want to flash cm
Are you on the latest version of flashtool? Make sure you have the drivers installed as well.
Now connect your phone and try unlocking boot loader again. Don't forget to use the correct unlock code. After unlocking, just turn off the phone and flash the firmware again and check boot loader status.
And if it's not working, you should request for a new code from Sony. Some people who encountered the problem solved it with a new code and/or unlocking BL via the official method.
Let me know how it goes.
eus4ni4 said:
Are you on the latest version of flashtool? Make sure you have the drivers installed as well.
Now connect your phone and try unlocking boot loader again. Don't forget to use the correct unlock code. After unlocking, just turn off the phone and flash the firmware again and check boot loader status.
And if it's not working, you should request for a new code from Sony. Some people who encountered the problem solved it with a new code and/or unlocking BL via the official method.
Let me know how it goes.
Click to expand...
Click to collapse
I've now downloaded newest one ( 0.9.16.0 )
I've pasted device folder with unlock code to /custom folder.
And it worked ! D
Thank you sooo much <3 (naah, I'm not g*y )
BEFORE:
Code:
15/008/2014 19:08:22 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8X30_R1_25 / Bootloader status : ROOTABLE
15/008/2014 19:08:22 - INFO - Start Reading unit 000008B2
15/008/2014 19:08:22 - INFO - Reading TA finished.
15/008/2014 19:08:27 - INFO - Unlocking device
15/008/2014 19:08:27 - INFO - Writing TA unit : [00, 00, 08, B2, 00, 00, 00, 10, 31, 44, 33, 46, 46, 45, 36, 35, 33, 34, 38, 34, 45, 45, 42, 46]
15/008/2014 19:08:27 - INFO - Unlock finished
15/008/2014 19:08:34 - INFO - Ending flash session
15/008/2014 19:08:34 - INFO - You can now unplug and restart your device
15/008/2014 19:08:34 - INFO - Device connected in flash mode
15/008/2014 19:08:35 - INFO - Device disconnected
AFTER:
Code:
15/009/2014 19:09:06 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8X30_R1_25 / Bootloader status : ROOTED
15/009/2014 19:09:06 - INFO - Start Reading unit 000008B2
15/009/2014 19:09:06 - INFO - Reading TA finished.
15/009/2014 19:09:06 - INFO - Unlock code saved to C:\Flashtool\custom\mydevices\ZH8000M5MC\ulcode.txt
15/009/2014 19:09:12 - INFO - Ending flash session
15/009/2014 19:09:12 - INFO - You can now unplug and restart your device
15/009/2014 19:09:13 - INFO - Device connected in flash mode
15/009/2014 19:09:13 - INFO - Device disconnected
Glad it worked. Now go and get cm11
aerzjee said:
I've now downloaded newest one ( 0.9.16.0 )
I've pasted device folder with unlock code to /custom folder.
And it worked ! D
Thank you sooo much <3 (naah, I'm not g*y )
BEFORE:
Code:
15/008/2014 19:08:22 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8X30_R1_25 / Bootloader status : ROOTABLE
15/008/2014 19:08:22 - INFO - Start Reading unit 000008B2
15/008/2014 19:08:22 - INFO - Reading TA finished.
15/008/2014 19:08:27 - INFO - Unlocking device
15/008/2014 19:08:27 - INFO - Writing TA unit : [00, 00, 08, B2, 00, 00, 00, 10, 31, 44, 33, 46, 46, 45, 36, 35, 33, 34, 38, 34, 45, 45, 42, 46]
15/008/2014 19:08:27 - INFO - Unlock finished
15/008/2014 19:08:34 - INFO - Ending flash session
15/008/2014 19:08:34 - INFO - You can now unplug and restart your device
15/008/2014 19:08:34 - INFO - Device connected in flash mode
15/008/2014 19:08:35 - INFO - Device disconnected
AFTER:
Code:
15/009/2014 19:09:06 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8X30_R1_25 / Bootloader status : ROOTED
15/009/2014 19:09:06 - INFO - Start Reading unit 000008B2
15/009/2014 19:09:06 - INFO - Reading TA finished.
15/009/2014 19:09:06 - INFO - Unlock code saved to C:\Flashtool\custom\mydevices\ZH8000M5MC\ulcode.txt
15/009/2014 19:09:12 - INFO - Ending flash session
15/009/2014 19:09:12 - INFO - You can now unplug and restart your device
15/009/2014 19:09:13 - INFO - Device connected in flash mode
15/009/2014 19:09:13 - INFO - Device disconnected
Click to expand...
Click to collapse
hello bro. what do you mean by this? device folder with unlock code to /custom folder? do you mean c:/flashtool/custom/IMEI_Device_Number/unlock_code.txt?
Jithin
hi guys .. i am new to this rooting flashing ..
i root my xperia L using iroot.apk .. now my phone is getting restarted when we open any apps or even dialer ...(in 10 secs)
if it is standby mode no problem at all..
USB debugging also available but same prolems.. tried reseting the phone still problem continues..
only rooting done ...
CWM not done ... Bootloder status comes blank ...using *#*#7378423#*#* pls help me out ..
i really wanna install CM 12.1 on my xperia L c2105.. problem is handset getting restarted ...
cant load the flashboot also comes waiting for device... since bootloader unlocked ...
how can i end up this prob.. someone help me.... :crying:
---------- Post added at 02:17 AM ---------- Previous post was at 02:12 AM ----------
aerzjee said:
It says:
Rooting status:
Bootloader unlocking allowed
I just want to flash cm
Click to expand...
Click to collapse
Same problem I am facing pls help me out.. my phone is getting restarted simultaniously after rooting .. cannot install any apps... cannot enter recovery ..
jithinghosh said:
hi guys .. i am new to this rooting flashing ..
i root my xperia L using iroot.apk .. now my phone is getting restarted when we open any apps or even dialer ...(in 10 secs)
if it is standby mode no problem at all..
USB debugging also available but same prolems.. tried reseting the phone still problem continues..
only rooting done ...
CWM not done ... Bootloder status comes blank ...using *#*#7378423#*#* pls help me out ..
i really wanna install CM 12.1 on my xperia L c2105.. problem is handset getting restarted ...
cant load the flashboot also comes waiting for device... since bootloader unlocked ...
how can i end up this prob.. someone help me.... :crying:
---------- Post added at 02:17 AM ---------- Previous post was at 02:12 AM ----------
Same problem I am facing pls help me out.. my phone is getting restarted simultaniously after rooting .. cannot install any apps... cannot enter recovery ..
Click to expand...
Click to collapse
The same thing happened to me .
Just flash stock ftf with out excluding the Data.
Related
i flashed D6603. FW release : 23.0.A.2.93. Customization : Generic GLOBAL
onto my tmobile xperia z3 and flashtool gave an error:
31/046/2014 17:46:22 - INFO - Current device : D6616 - BH9002W61K - 1286-4514_R16B - 1282-2729_23.0.D.1.123 - TMOUS-LTE_23.0.D.1.123
31/046/2014 17:46:22 - INFO - Start Flashing
31/046/2014 17:46:22 - INFO - Processing loader.sin
31/046/2014 17:46:22 - INFO - Checking header
31/046/2014 17:46:22 - INFO - Flashing data
31/046/2014 17:46:22 - INFO - Processing of loader.sin finished.
31/046/2014 17:46:22 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_22 / Boot version : S1_Boot_MSM8974AC_LA3.0_55 / Bootloader status : NOT_ROOTABLE
31/046/2014 17:46:22 - INFO - Processing partition-image.sin
31/046/2014 17:46:22 - INFO - Checking header
31/046/2014 17:46:23 - ERROR - Processing of partition-image.sin finished with errors.
31/046/2014 17:46:23 - INFO - Ending flash session
31/046/2014 17:46:23 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80080028";
now phone says "connect to computer to finish updating instead of booting.
latest flashtool, just want a clean generic firmware on this tmobile xperia z3.
THANK in advance for the help!
mety333 said:
i flashed D6603. FW release : 23.0.A.2.93. Customization : Generic GLOBAL
onto my tmobile xperia z3 and flashtool gave an error:
31/046/2014 17:46:22 - INFO - Current device : D6616 - BH9002W61K - 1286-4514_R16B - 1282-2729_23.0.D.1.123 - TMOUS-LTE_23.0.D.1.123
31/046/2014 17:46:22 - INFO - Start Flashing
31/046/2014 17:46:22 - INFO - Processing loader.sin
31/046/2014 17:46:22 - INFO - Checking header
31/046/2014 17:46:22 - INFO - Flashing data
31/046/2014 17:46:22 - INFO - Processing of loader.sin finished.
31/046/2014 17:46:22 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_22 / Boot version : S1_Boot_MSM8974AC_LA3.0_55 / Bootloader status : NOT_ROOTABLE
31/046/2014 17:46:22 - INFO - Processing partition-image.sin
31/046/2014 17:46:22 - INFO - Checking header
31/046/2014 17:46:23 - ERROR - Processing of partition-image.sin finished with errors.
31/046/2014 17:46:23 - INFO - Ending flash session
31/046/2014 17:46:23 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80080028";
now phone says "connect to computer to finish updating instead of booting.
latest flashtool, just want a clean generic firmware on this tmobile xperia z3.
THANK in advance for the help!
Click to expand...
Click to collapse
Just flash back to stock T-Mobile. Theres NO guarantee that flashing global firmwares on the T-Mobile US Version will work.
I had no access to fast internet, went to t-mobile they gave me a new phone lol
So any success story for putting a global generic firmware on the D6616?
mety333 said:
I had no access to fast internet, went to t-mobile they gave me a new phone lol
So any success story for putting a global generic firmware on the D6616?
Click to expand...
Click to collapse
T-Mobile can charge you for that if they found out, As that does VOID the warranty.
Did you manage to recover with TMO stock?
mety333 said:
I had no access to fast internet, went to t-mobile they gave me a new phone lol
So any success story for putting a global generic firmware on the D6616?
Click to expand...
Click to collapse
abhinav.tella said:
Did you manage to recover with TMO stock?
Click to expand...
Click to collapse
The OP stated they took it to T-Mobile to got it replaced.
Most likely you should be able to flash the T-Mobile stock firmware back if you do this but not 100% sure on that yet.
Glad it worked out you in the end.
abhinav.tella said:
Did you manage to recover with TMO stock?
Click to expand...
Click to collapse
It would have been smart to download the t mobile firmware but after flashing I had no Internet access and just the global generic firmware, so I couldn't try.
The phone was not bricked or anything, it was just firmware-less so the factory reset option in the stock recovery booted in the same logo screen.
For now I'm really enjoying the Z3 even on the t mobile firmware, heck there's no room yet anyways.
hello
if you run crashes. you go out into the cell area "Exclude" and "No final verification" .... then flash i hope Your phone will revive
Hi folks,
I'm trying to recover data from a Xperia J (ST26i - 11.2.A.0.21) which suddenly started to hang on boot at the boot splash.
The phone is locked, so I cannot access fastboot, let alone adb, to get access to the internal filesystem. I believe all I can work with is flashmode (please correct me if I'm wrong). Phone has no recovery mode. So I fear I need to reflash the device.
I've read through these forums and tried several things with no success:
1. starting simple, I tried the PC Companion tool - it was unable to detect the device while it was (a) stuck at boot splash animation and (b) in flashmode (powered up while holding Vol down, end up with greed led lit). No good
2. Tried the Sony Emma tool, to see if it could talk with the device. It detected the device, could read data from it (model, IEMI and other serial numbers) but refused to allow me to interact with the files on the device because the bootloader is locked.
3. Ok, maybe I can unlock the bootloader? Nope, as the unlock steps require access to fastboot, which I can only turn on by being able to boot the device and enable developer mode. No go.
4. So leaves me with flashing the device. Maybe some other software on the phone got corrupted? I downloaded copy of JB firmware via [1], got the amazing flashtool, and managed to flash the device - but not touching the userdata partition/file. This succeeded, but still the device fails to boot beyond the xperia splash animation.
I'm out of ideas really. If I could somehow install clockwork mod recovery, just so I could get adb access to the filesystem, that would be enough for me to continue. But I don't see any way to achieve that. What have I missed?
Thanks in advance
-G
[1] http://forum.xda-developers.com/xpe...ection-one-t2385526/post44115119#post44115119
I should add that flashtool is unable to unlock it for me - I assume carrier locked? I have an unlock code from the sony website
I'm fearing this exercise is doomed...
Flashtool output in case it helps:
Code:
01/032/2015 17:32:42 - INFO - You can now unplug and restart your phone
01/033/2015 17:33:02 - INFO - Please connect your device into flashmode.
01/033/2015 17:33:03 - INFO - Opening device for R/W
01/033/2015 17:33:03 - INFO - Reading device information
01/033/2015 17:33:03 - INFO - Phone ready for flashmode operations.
01/033/2015 17:33:03 - INFO - Current device : ST26i - YT9108C0K6 - 1270-7015_R2E - 1263-8752_11.2.A.0.21 - WORLD-i_11.2.A.0.31
01/033/2015 17:33:03 - INFO - Processing loader.sin
01/033/2015 17:33:03 - INFO - Checking header
01/033/2015 17:33:03 - INFO - Flashing data
01/033/2015 17:33:03 - INFO - Processing of loader.sin finished.
01/033/2015 17:33:05 - INFO - Loader : S1_Root_a8a4 - Version : R5D030 / Boot version : R10D030 / Bootloader status : NOT_ROOTABLE
01/033/2015 17:33:05 - INFO - Start Reading unit 000008B2
01/033/2015 17:33:05 - INFO - Reading TA finished.
01/033/2015 17:33:06 - INFO - Ending flash session
01/033/2015 17:33:06 - INFO - Your phone bootloader cannot be officially unlocked
01/033/2015 17:33:06 - INFO - You can now unplug and restart your phone
-G
Did you try to flash ftf? You'll lose all data but you'll fix the phone. And probably your phone is carrier locked, if it says "bootloader unlock status No" you can't unlock it.
Good Luck.
Sent from Xperia M2 D2303
Dzepar said:
Did you try to flash ftf? You'll lose all data but you'll fix the phone. And probably your phone is carrier locked, if it says "bootloader unlock status No" you can't unlock it.
Good Luck.
Click to expand...
Click to collapse
I could flash the ftf, but then I loose the data, which I'm trying to avoid. Yeah it is carrier locked, so am stuck there
I'm currently trying to build a custom firmware with the CWM recovery included, that I can flash onto the device. That might let me get access to the data partition. Will see anyhow. Thanks!
-G
handset stucks on logo
oem disable for boot unlocking
so can not downgrade-customer said it happened after update to latest version-now info as below
Port : Fastboot Mode
Baud Rate : Not Applicable
Device : Motorola QCOM
Operation : Flash Boot (Fastboot)
Searching for Device in FastBoot Mode... OK
Reading Phone Information...
Model : XT1557
Boot Ver. : moto-msm8939-80.EE
Baseband : <not available>
Software : Blur_Version.24.216.11.merlin_retasia.retasia.en.0 3
IMEI : 352359070354331
CPU : MSM8939
RAM : 2048MB Samsung S8 SDRAM DIE=8Gb
EMMC : 16GB Samsung REV=07 PRV=06 TYPE=57
must need """Blur_Version.24.216.11.merlin_retasia.retasia.e n.03""""" firmware
i got lower firmware versions-tried flash-eror as below
Sending Data [boot]... Denied
Possibly Downgraded Version! Use same version or higher.
Operation Failed.
Elapsed Time: 00:03
help me for Blur_Version.24.216.11.merlin_retasia.retasia.en.0 3 xt1557 firmware
supporters waiting
any way to oem unlock enable in fastboot mode?
set hang in logo-so only fastboot
zonetrichur said:
supporters waiting
any way to oem unlock enable in fastboot mode?
set hang in logo-so only fastboot
Click to expand...
Click to collapse
No... There is no "magic" or anything else... If OEM unlocking is not turned on, then you cannot unlock the bootloader.
how to relock the bootloader:
First of all you're gonna need:
- A PC/Android SDK/ADB Toolkit
- An android with an unlocked bootloader
- A usb cable connected to the device
I made this thread because I had the same problem but I found a way to fix it! I was trying to load into a corrupted recovery and it kept being stuck on the "Your device is unlocked and cant be trusted, your device is booting now" thingy, but I found my way out and it's really easy!
Tutorial:
Steps:
- 1: Hold the power button down till your phone shuts down and re-open by also holding down the "volume-down" key, so it loads into fastboot.
- 2: Go onto your pc/mac (cmd/terminal) and type the command "fastboot oem relock <your unlock number>". Then it should be something like this:
fastboot oem relock <your unlock number>
(bootloader) The device will reboot and do factory reset...
OKAY [ 15.785s]
finished. total time: 15.785s
Click to expand...
Click to collapse
To get your "unlock number" take a look at this:
-We get our Unlock Code for Bootloader, write it somewhere !-
^^^ This is on the emui website = emui . com
(XDA doesnt allow me to add a picture of what I mean because I'm a new user )
If you need more help, leave a comment below! :good::laugh:
Why i got this message that say failed?
All,
Attempting to unlock and root for the first time .
Bootloader unlocked - Done
Issue is with rooting and twrp installation :
RootChecker app says phone is not rooted properly.
Now as i am new to this there is something definitely wrong - i followed this thread and this is the closest i have come to rooting :
Currently the phone in the fastboot and so called rooting in progress :
screen reads :
cmd : OEM unlock
cmd : OEM unlock
cmd : OEM unlock-go
cmd : OEM unlock-go
cmd : Finishing unlock (does not look like it is finishing it)
Any help on this is greatly appreciate - i am practicing this on Moto G as if i am successfull i will move to OP2 and use it with latest android ROM