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.
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
[tipo]Rooting status changed to "No" from "Yes". Can't enter fastboot mode now
This xperia tipo st21i single sim had rooting status: "Bootloader Unlock: Yes" but it changed to "Bootloader unlock allowed : No" may be after flashing 11.0.A.4.22_generic or after a failed root exploit by flashtool or some other reason. I cant enter fastboot mode now. I want to install and test some custom roms on this device. Help please...
[ images attached. Flashtool log (the only log that i have) during bootloader unlocking is also attached.]
THE COMPLETE STORY:
The device was running 11.0.A.4.27_Indian firware. It is detecting sim cards of Reliance and aircel carriers but not of airtel and vodafone carriers. So i decided to flash modems from 11.0.A.4.22_generic.ftf. I successfully unlocked the bootloader yesterday with flashtool. I was able to enter fastboot mode. I tried flashing modem with "fastboot flash modem modem_fs1.sin" and i got "Error: Partition modem not found (remote error)". I tried rooting it using flashtool but root exploit failed. Then i successfully flashed entire 11.0.A.4.22_generic.ftf via flashtool in flashmode. I tried installing cwm using these instructions but then it failed at step3 "error su not found". I had downloaded boot.img which had twrp recovery. But then, i realised the device is not entering fastboot mode with any method. Then I checked rooting status and surprisingly it has now changed to "Bootloader unlock allowed: No". I came to know that unlockable devices cannot enter fastboot mode after searching forums. Flashtool still recognises it as unlocked.. How do i access fastboot mode again? How do i revert the rooting status back to " Bootloader unlock:Yes". My ultimate aim is to install a custom recovery and flash custom roms.
Hi pals,
My excuses if this sort of problem that I post (English is not my native language, so I am sorry for any spelling mistakes), is already posted earlier.
My Nexus 5X is currently stuck on Fastboot mode with the following specifications:
FASTBOOT MODE
PRODUCT_NAME - bullhead
VARIANT - bullhead LGH791 32GB
HW VERSION - rev_1.0
BOOTLOADER VERSION - BHZ11m
BASEBAND VERSION - M8994F-2.6.37.2.21
CARRIER INFO - N/A
SERIAL NUMBER - 00ce1aff0bcc3ea6
SIGNING - production
SECURE BOOT - enabled
DEVICE STATE - unlocked
As you can see, I already unlocked my bootloader with help from the Nexus Root Toolkit. My device is currently in Fastboot mode. The working functions are Restart bootloader and Power Off. Neither Recovery mode and / or Start.
But I can root my Device with help from Nexus Root Toolkit.. When I do that, a TRWP warning pops up, and it says that I don't currently have a OS on my device and that I sure want to do this.
So, my questions now are:
-How can I get to the original OS?
-How to unroot my device?
Edit 1: After I chose the option 'Flash Stock + Unroot' on the Nexus Root Toolkit program, my device is now stuck on the Google logo with a unlocked bootloader, after everything is finished in the Command Prompt.
Any help would be appreciated.
Thanks in advance!
Update 1: I chose the OEM Lock option in the Nexus Root Toolkit program, and I don't have a unlocked bootloader anymore by startup. But my device is still stuck at the Google screen... I created a AB backup before I wanted to root my device, should I apply that backup now to my device?
Best way to fix it is to post in NEXUS 5X FORUM! btw i think its emmc failure, as many 5x got this..
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?