Database Develop

[Q] Help... X8 trouble.

OK, first hi everybody I'm new here and will try be helpfull for other members as soon as I deal with my phone.
I bought the Xperia X8 2 months ago, tried to uprade it to gingerbread, failed and gave up. Now im trying again and i've read a lot threads here and unfortunately nothing seems to work. Cant root the stupid thing.
The phone is model E15i, it has 2.1-update1 - Frimware version, Baseband version is M76XX-TSNCJOLYM-53404015, Kernel version is 2.6.29 and 2.1.1.A.0.6 is the Build number.
I tried rooting with SuperOneClick countless times with different version of the program including latest and it always freezes, i get the Not Responding treatment. Also tried x8toolbox and again nothing. I folowed every step from other threads and it cant be rooted. I installed Root Explorer 2.16 apk but wasnt able to copy files from xRecovery to bin folder because i cant change r/o to r/w ( i guess this is because the phone is not rooted ).
Somebody please help
P.S. All suggestions are welcomed !

Bootlocker??
If u wer on the stock firmware and locked bootlocker this can actually happen. See to that u have unlocked the bootlocker. Then try to upgrade once more and if failed then there is plenty of custom roms available here on the rom section so ntng to worry abt. Its fine.
To unlock boot locker :
Turn off phone and start in fastboot mode,
Before that,
First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu. In your phone, open the dialler and enter *#*#7378423#*#* to access the service menu.
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.
On your computer, click Continue at the bottom of this page to start the unlock boot loader process.
Read through the information in the pop up window and click Yes, I’m sure, if you are still confident you want to unlock the boot loader.
Read through and accept the legal terms. Click I Accept.
Enter your name, email address, the first 14 digits (remove the last digit) of your phone’s IMEI number and the two CAPTCHA words in the input boxes. Click Submit. You can view the IMEI number by entering *#06# on your phone.
The unlock boot loader key is displayed. Write it down and save it for later use.
Download and install the latest Android SDK from developer.android.com.
Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager.
Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager.
Turn off your phone.
On your phone, push and hold the unlock button* at the same time as you connect the phone to the computer with a USB-cable. The unlock button may differ between different phone models. See the note in the bottom of this page for more information on what button use on your phone.
On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
Open a command window and go to the tools folder within the Android SDK folder.
Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your phone is connected properly.
Warning! If you perform this step, you will unlock the boot loader. This may void your warranty and/or any warranty from your operator. If you still want to unlock the boot loader of your phone, enter fastboot.exe -i 0x0fce oem unlock 0xKEY, where KEY is the unlock boot loader key you got in the beginning of this instruction. The boot loader should now be successfully unlocked.
And if u still fail come back with the error and dont frget to say thanx for my efforts(press if only it helped.)

Hi there
I would recommend you to use flashtool to root and unlock your phone. Of course it will have many other function as else.
http://www.mediafire.com/download.php?t3baob63v9grqub <== Flashtool
Don't forget to install driver & off AV
Read post until the end of it's page

mustangx8 said:
OK, first hi everybody I'm new here and will try be helpfull for other members as soon as I deal with my phone.
I bought the Xperia X8 2 months ago, tried to uprade it to gingerbread, failed and gave up. Now im trying again and i've read a lot threads here and unfortunately nothing seems to work. Cant root the stupid thing.
The phone is model E15i, it has 2.1-update1 - Frimware version, Baseband version is M76XX-TSNCJOLYM-53404015, Kernel version is 2.6.29 and 2.1.1.A.0.6 is the Build number.
I tried rooting with SuperOneClick countless times with different version of the program including latest and it always freezes, i get the Not Responding treatment. Also tried x8toolbox and again nothing. I folowed every step from other threads and it cant be rooted. I installed Root Explorer 2.16 apk but wasnt able to copy files from xRecovery to bin folder because i cant change r/o to r/w ( i guess this is because the phone is not rooted ).
Somebody please help
P.S. All suggestions are welcomed !
Click to expand...
Click to collapse
I suggest that while you are on stock ROM, "Repair" your phone with PCC to flash back stock.
Then try rooting again.

Instal pc companion lol . . Make sure a driver was install
----------------------------------------------------
Xperia X8
| MiniCM9-3.0.1 | nAa-ics-02 | 100% SuperCharger | Chainfire ?! |
Thanx to " nAa and Zeppelinrox "

To rooting (this my way)
-Install sony companion first on computer..
And turn your phone in debugging mode,,plug your phone with the computer..
(wait until the tray icon said the driver install successfully)
-unplug the device from computer
-open superoneclick click root
-when a message "waiting for device" appeared,,plug device then choose recharge
-after this mesage appeared
(Your phone has been rooted!!
Would you like to run a test??)
CHOOSE NO..
That how i rooting..
Sent from my X8 using xda premium

Bootloader Status unknown, How can back to unlockable? SOLVED

Hi Guys,
i have some problem, this is my story:
after unlocking the bootloader without any problem i decided to root, but some reason i get superuser app but root explorer dont worked and no answer for it for superuser access, nothing.. like the root was dummy..
after i tryed to flash stock kernel with recovery for unlocked bootloader (for do the root via Recovery) but nothing adb say me <waiting for the device>... not knowing what to do and why this problem i thinked maybe the XZ is not still with unloked bootloader and i try another time to unlocked it.. result the XZ now is in bootloop
i tryng to relock the bootloader (this was ok) and flash the stock firmware with flashtool...
apparently i dont go in flashmode because no led green appear, but flashtool say me im in flashmode...
but i get this log:
16/059/2013 20:59:27 - INFO - <- This level is successfully initialized
16/059/2013 20:59:27 - INFO - Flashtool Version 0.9.10.2beta built on 2013-03-15 09:11:22
16/059/2013 20:59:34 - INFO - Device disconnected
16/059/2013 20:59:44 - INFO - Device connected in flash mode
16/059/2013 20:59:52 - INFO - Selected C6603 / Generic Uk / Non
16/059/2013 20:59:52 - INFO - Please connect your device into flashmode.
16/059/2013 20:59:52 - INFO - Preparing files for flashing
16/000/2013 21:00:45 - INFO - Device disconnected
16/001/2013 21:01:08 - INFO - Flash canceled
the flash stuck in "Preparing files for flashing"
i dont know why
I revived the XZ with SUS (Is Italian No brand) but this is my situation:
My rooting status (my bootloader) is unknown (before was unlockable) and i cant flash with Flashtool beta because i get the stuck on "Preparing files for flashing".
I would like to unlock my XZ another time to rooting and flashing recovery and cooked rom..
What should I do to make it?
Thanks
EDIT:
Ok, for the problem "the flash stuck in Preparing files for flashing" i solve with this operation http://forum.xda-developers.com/showpost.php?p=39256827&postcount=138
Now i flashed the firmware with flashtool.. but my bootloader still unknown (before relock was unlockable) why the flash dont fix it?
what i must to do for have back bootloader unlockable?

Ok, for the problem "the flash stuck in Preparing files for flashing" i solve with this operation http://forum.xda-developers.com/showpost.php?p=39256827&postcount=138
This is my situation now:
i relock the bootloader with flashtol and flashed the firmware.. my bootloader before lock it was unlockable, after relock and flash firmware is unknown why the flash dont fix it?
i tryed also rooting, after this become NO, i tryed this fix http://forum.xda-developers.com/showpost.php?p=39178406&postcount=96 but not came back to YES but is still another time
to unknown
what i must to do for have back bootloader unlockable?
Please someone Help me
Thanks

For For those who have my problem here http://forum.xda-developers.com/showpost.php?p=39338155&postcount=178 the solutions :good::laugh:

tanoxxx said:
For For those who have my problem here http://forum.xda-developers.com/showpost.php?p=39338155&postcount=178 the solutions :good::laugh:
Click to expand...
Click to collapse
Hi,
I'm having the same problem with the "Rooting status: unknown".
I can't flash kernel (via Flashtools) and can't unlock (via android fastboot).
Unfortunately the file posted in the solution you mentioned is unavailable.
Can you tell me how you proceed to fix it?
Thank you very much

help
Please Help me
I was flashing a stock rom for my xperia z ultra c6833.
After that, the flashing proccess started and done without any problem. When i put the sim card in the phone, it says: "Invalid Sim card" and in the service menu says: "Rooting status: Unknown". Before this, the service menu said: "Rooting status: Unlock Bootloader allowed: yes" then I unlocked my bootloader without any problem and everything was perfect, but after that flashing on flashtool the Rooting status change to "Unknown" and my sim card are unable to read. There is no problem with my sim card because I tried to put it on another phone and works perfect.
How do I fix it?
How I change the roothing status back to "allowed: yes"
and how I fix it to be able to read my sim card again?

and what ? any solution ?

hi exery one
i have the seem problem (Unlock Bootloader Allowed: Unknown)
and i can't Unlock it.
please help me.

Xperia v boot problem

Hi, i have xperia V (protoype). It was working fine, until i decide to put new Android (i was 4.0.4 on it). I don't have much of experience in flashing, but i did success already with my two other phones (ARC and P ), so i thought this time will be easy as usually. but...
phone was dead as stone..i spend more than week to trying all methods what i was able to find. now it's a big mess in my head and my PC, but now i made phone to start in recovery menu. thats all. tried install different roms, cyanomodgens-nothing... it just shows me SONY-->cyanomodgen and freez. at the moment flashtool can't see my phone.
if anyone can help me what to do( step by step), how to make this phone working again -i will be very happy person.
sorry for english.

vibogd said:
Hi, i have xperia V (protoype). It was working fine, until i decide to put new Android (i was 4.0.4 on it). I don't have much of experience in flashing, but i did success already with my two other phones (ARC and P ), so i thought this time will be easy as usually. but...
phone was dead as stone..i spend more than week to trying all methods what i was able to find. now it's a big mess in my head and my PC, but now i made phone to start in recovery menu. thats all. tried install different roms, cyanomodgens-nothing... it just shows me SONY-->cyanomodgen and freez. at the moment flashtool can't see my phone.
if anyone can help me what to do( step by step), how to make this phone working again -i will be very happy person.
sorry for english.
Click to expand...
Click to collapse
Try a clean install :
Wipe Data + Cache + System + Dalvik

vibogd said:
Hi, i have xperia V (protoype). It was working fine, until i decide to put new Android (i was 4.0.4 on it). I don't have much of experience in flashing, but i did success already with my two other phones (ARC and P ), so i thought this time will be easy as usually. but...
phone was dead as stone..i spend more than week to trying all methods what i was able to find. now it's a big mess in my head and my PC, but now i made phone to start in recovery menu. thats all. tried install different roms, cyanomodgens-nothing... it just shows me SONY-->cyanomodgen and freez. at the moment flashtool can't see my phone.
if anyone can help me what to do( step by step), how to make this phone working again -i will be very happy person.
sorry for english.
Click to expand...
Click to collapse
how did you install recovery?

Aria.A97 said:
Try a clean install :
Wipe Data + Cache + System + Dalvik
Click to expand...
Click to collapse
did it 1000000000 times-and nothing... completely lost.

vibogd said:
did it 1000000000 times-and nothing... completely lost.
Click to expand...
Click to collapse
can you tell me how you installed recovery?

isko95 said:
can you tell me how you installed recovery?
Click to expand...
Click to collapse
just make it clear.. is it menu when need to press volume button when "sony" appears on the screen?
i can't tell you exactly how i did it- i did it with flashboot (boot.img or something), don't remember. didn't touch the phone for week, because i don't know what and how to do. as i said, i need step-by-step advice from beginning. if anyone will help me-i will be sooo happy

1. Is your bootloader unlocked - and did you test if your BL is/was unlockable?
If BL is unlocked correctly:
2. Try to flash another kernel in recovery,such as http://forum.xda-developers.com/showthread.php?t=2223534
Then try to install a CM-ROM for example.

dyfk3l said:
1. Is your bootloader unlocked - and did you test if your BL is/was unlockable?
If BL is unlocked correctly:
2. Try to flash another kernel in recovery,such as http://forum.xda-developers.com/showthread.php?t=2223534
Then try to install a CM-ROM for example.
Click to expand...
Click to collapse
1. i did kernel install
2. CM install shows me some errors. can you drop me link for rom, please?
p.s. tried another CM-and again: "sony"->"cyanogenmod"->blank screen (phone is on)

We cannot help you unless you answer our questions correctly.
BL unlocked correctly?
Already tried another kernel?

dyfk3l said:
We cannot help you unless you answer our questions correctly.
BL unlocked correctly?
Already tried another kernel?
Click to expand...
Click to collapse
well, i did unlock ( i was thinking i did it-got code, entered it). and now i got message on flashtool
- Reading device information
29/018/2014 19:18:27 - INFO - Unable to read from phone after having opened it.
29/018/2014 19:18:27 - INFO - trying to continue anyway
29/018/2014 19:18:32 - INFO - Processing loader.sin
29/018/2014 19:18:32 - INFO - Checking header
29/018/2014 19:18:32 - ERROR - Error in processHeader : 6 : The handle is invalid.
29/018/2014 19:18:32 - INFO - Your phone bootloader cannot be officially unlocked
when i do that "fastboot.exe -i 0x0fce oem unlock 0xxxxxx" it says "phone is already unlocked! "
yes, i tried different kernels.
there are so many files with *.img, sin, elf, ftf -i don't have clue what has to be done.
when phone was OK i checke in service (?) menu and it was "bootloader unlock allowed-yes"
i'm trying to answer as much as i can.

vibogd said:
29/018/2014 19:18:32 - INFO - Your phone bootloader cannot be officially unlocked
Click to expand...
Click to collapse
That sounds strange - because you said that service menu allowed unlocking bootloader. To be honest, I don't know what happens if try to unlock a bootloader which is not unlockable.
Regarding flashing: Take the NKernel from my link, open the ZIP file and extract the kernel.elf.
Then flash elf file via fastboot: fastboot flash boot kernel.elf
And then try to get into recovery and then try to flash a CM ROM like this from your external SD: https://download.cyanogenmod.org/get/jenkins/39793/cm-10.1.3-RC1-tsubasa.zip (10.1.3-RC1).

dyfk3l said:
That sounds strange - because you said that service menu allowed unlocking bootloader. To be honest, I don't know what happens if try to unlock a bootloader which is not unlockable.
Regarding flashing: Take the NKernel from my link, open the ZIP file and extract the kernel.elf.
Then flash elf file via fastboot: fastboot flash boot kernel.elf
And then try to get into recovery and then try to flash a CM ROM like this from your external SD: https://download.cyanogenmod.org/get/jenkins/39793/cm-10.1.3-RC1-tsubasa.zip (10.1.3-RC1).
Click to expand...
Click to collapse
can't see kernel.elf in zip.

vibogd said:
can't see kernel.elf in zip.
Click to expand...
Click to collapse
It's in #7 where I asked you the first time to try another kernel!
http://forum.xda-developers.com/showpost.php?p=52279445&postcount=7
Try installing the ROM with NKernel recovery, otherwise you can flash the boot.img from the CM ROM (inside zip, also via fastboot). Can you install the ROM with one of the kernels?

dyfk3l said:
It's in #7 where I asked you the first time to try another kernel!
http://forum.xda-developers.com/showpost.php?p=52279445&postcount=7
Try installing the ROM with NKernel recovery, otherwise you can flash the boot.img from the CM ROM (inside zip, also via fastboot). Can you install the ROM with one of the kernels?
Click to expand...
Click to collapse
ok... i installed kernel.elf, when i reboot into recover mode i was unable to choose anything-touchscreen doesn't respond, buttons does nothing aswell.
i'm sure i do everything ok, but every time phone stuck on second screen after "sony"
after flahsing boot.img phone stuck on first screen"sony"
p.s i don't know if that is important, but almost every time pc trying to instal drivers, but...MTP drivers was not instaled

vibogd said:
i'm sure i do everything ok, but every time phone stuck on second screen after "sony"
Click to expand...
Click to collapse
That's normal, you can't boot a CM Rom with NKernel (which is for stock 4.1). You always need the right kernel for every Rom (and Rom generation - a CM 11 kernel won't boot with CM 10.2).
It was just to test if recovery is working. But you say it doesn't respond? Of course tochscreen is not working in CWM! You have to navigate with Vol up/down and enter via power button. I hope you know that?!
Go ahead and try different kernels/Roms. Like this: http://aokp.co/devices/tsubasa
Install boot.img from zip via fastboot, go into recovery and try to install the AOKP Rom from your externel SD card. Does recovery work? Can you install Rom?

dyfk3l said:
That's normal, you can't boot a CM Rom with NKernel (which is for stock 4.1). You always need the right kernel for every Rom (and Rom generation - a CM 11 kernel won't boot with CM 10.2).
It was just to test if recovery is working. But you say it doesn't respond? Of course tochscreen is not working in CWM! You have to navigate with Vol up/down and enter via power button. I hope you know that?!
Go ahead and try different kernels/Roms. Like this: http://aokp.co/devices/tsubasa
Install boot.img from zip via fastboot, go into recovery and try to install the AOKP Rom from your externel SD card. Does recovery work? Can you install Rom?
Click to expand...
Click to collapse
yes, i know have to use vol + -, but noone button works.
one more q.. it doesn't matter prototype phone or not? uufff.. i'm almost give up. looks like i'm doing same and same every time and no effect.
thanks for helping and not leaving me alone with that head pain
p.s. just installed boot.img, but when tried to run recovery-just dead androbot appears on the screen

Sorry, but I've got no idea.
I never had the problem that a flashed kernel's recovery is not working - and I don't know why. Sorry.
Must have to do with the Flashtool message that your bootloader cannot be unlocked. There is sth. really strange...

dyfk3l said:
Sorry, but I've got no idea.
I never had the problem that a flashed kernel's recovery is not working - and I don't know why. Sorry.
Must have to do with the Flashtool message that your bootloader cannot be unlocked. There is sth. really strange...
Click to expand...
Click to collapse
01/022/2014 13:22:35 - INFO - Please check the log before rebooting into system
01/022/2014 13:22:44 - INFO - Device disconnected
01/022/2014 13:22:49 - INFO - Please connect your device into flashmode.
01/022/2014 13:22:55 - INFO - Device connected in flash mode
01/022/2014 13:22:55 - INFO - Opening device for R/W
01/022/2014 13:22:55 - INFO - Reading device information
01/022/2014 13:22:55 - INFO - Phone ready for flashmode operations.
01/022/2014 13:22:55 - INFO - Current device : Unknown: Mar 29 2013/12:30:02 - CB5A1KBDPF - Unknown: Mar 29 2013/12:30:02 - Unknown: Mar 29 2013/12:30:02 - Unknown: Mar 29 2013/12:30:02
01/023/2014 13:23:04 - INFO - Processing loader.sin
01/023/2014 13:23:04 - INFO - Checking header
01/023/2014 13:23:04 - INFO - Flashing data
01/023/2014 13:23:10 - INFO - Loader : S1_Root_7054 - Version : R5A058 / Boot version : R10A112 / Bootloader status : ROOTABLE
01/023/2014 13:23:10 - INFO - Start Reading unit 000008B2
01/023/2014 13:23:10 - INFO - Reading TA finished.
01/023/2014 13:23:14 - INFO - Unlocking device
01/023/2014 13:23:14 - INFO - Writing TA unit : [00, 00, 08, B2, 00, 00, 00, 10, 35, 34, 34, 43, 32, 44, 34, 45, 35, 41, 41, 32, 41, 32, 37, 44]
01/023/2014 13:23:14 - INFO - Unlock finished
01/023/2014 13:23:23 - INFO - Ending flash session
01/023/2014 13:23:23 - INFO - You can now unplug and restart your device
01/023/2014 13:23:23 - INFO - Device connected in flash mode
01/023/2014 13:23:24 - INFO - Device disconnected
01/023/2014 13:23:26 - INFO - Device connected in flash mode
as i can understand-i did unlock.

I suggest to flash stock ROM and then relock your bootloader

Aria.A97 said:
I suggest to flash stock ROM and then relock your bootloader
Click to expand...
Click to collapse
when i flashed ftf (flashmode), phone is not responding at all ( just one vibro when press on button) and screen stays black.

Flashtool error "ERR_CODE="0017" need help

I've try update my software with OTA and PC Companion before and it said error. Then I tried to flash 292 FTF using flashtool 0.9.18.4 and this error keep showing.
07/001/2015 03:01:51 - INFO - Phone boot version : S1_Boot_Lagan_1.0_2. Boot delivery version : S1_Boot_Lagan_1.1.1_1
07/001/2015 03:01:51 - INFO - Going to flash boot delivery
07/001/2015 03:01:51 - INFO - Processing emmc_appsboot_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin
07/001/2015 03:01:51 - INFO - Checking header
07/001/2015 03:01:51 - ERROR - Processing of emmc_appsboot_S1_Boot_Lagan_1.1.1_1_HWID_7190E1_OEM0.sin finished with errors.
07/001/2015 03:01:51 - INFO - Ending flash session
07/001/2015 03:01:51 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80080021 ";
Click to expand...
Click to collapse
I've checked *#*#7378423#*#* and bootloader unlocked is yes
Please solve this error for me
Thank you!
And I've spend 2 days searching, it's not much but I think I can't do anything to solve this problem.

hacphongthan said:
I've try update my software with OTA and PC Companion before and it said error. Then I tried to flash 292 FTF using flashtool 0.9.18.4 and this error keep showing.
I've checked *#*#7378423#*#* and bootloader unlocked is yes
Please solve this error for me
Thank you!
And I've spend 2 days searching, it's not much but I think I can't do anything to solve this problem.
Click to expand...
Click to collapse
Why you're using flashtool instead of fastboot if your bootloader is unlocked either way?
You can try to flash Lollipop 5.0.x ROM : PABX's ROM YUGA 5.0
The instructions are written in the page, but before that you need to download android SDK.
After you will be done that either, you will need to go /sdk/platform-tools/ (where fastboot.exe and adb.exe are installed), then with holding SHIFT button press Right Mous Button and push "Open command prompt here". And then just write the commands which are written in the page, again.
And don't forget to install adb and fastboot drivers.

LaurynasVP said:
Why you're using flashtool instead of fastboot if your bootloader is unlocked either way?
The instructions are written in the page, but before that you need to download android SDK.
After you will be done that either, you will need to go /sdk/platform-tools/ (where fastboot.exe and adb.exe are installed), then with holding SHIFT button press Right Mous Button and push "Open command prompt here". And then just write the commands which are written in the page, again.
And don't forget to install adb and fastboot drivers.
Click to expand...
Click to collapse
So my phone bootlocker has been unlocked right ?
Can I do anything to relock it?
I don't have old TA partition because I've bought an used phone and I just want to use stock ROM

hacphongthan said:
So my phone bootlocker has been unlocked right ?
Can I do anything to relock it?
I don't have old TA partition because I've bought an used phone and I just want to use stock ROM
Click to expand...
Click to collapse
If via *#*#7378423#*#* shows, that status is : "Bootloader unlockED: YES", then yes, your bootloader is unlocked and your DRM keys have been erased permanently, without any way of getting them back (if you don't have TA-Partition backup, of course). If status is : "Bootloader unlock ALLOWED: Yes", then your bootloader isn't unlocked and yours DRM keys is in their "place".
If your bootloader unlocked, then you could ask the person you have bought your phone from for TA-Partition backup, if he/she has it.
If not - don't ever think to flash anyone else's Ta-Partition, otherwise you'll brick your phone permanently.
You can relock it via Flashtool, If I'm right. But it doesn't change the situation you're in, 'cause your DRM keys are lost and you'll not be able to use BE2, Clear Audio+ and other fuctions, which requires the DRM keys to be working.
I'm sorry about that.
You can still flash stock .FTF, I suggest you to flash Generic.
If error persists, you could try other .ftf to fry for flashing.

LaurynasVP said:
If via *#*#7378423#*#* shows, that status is : "Bootloader unlockED: YES", then yes, your bootloader is unlocked and your DRM keys have been erased permanently, without any way of getting them back (if you don't have TA-Partition backup, of course). If status is : "Bootloader unlock ALLOWED: Yes", then your bootloader isn't unlocked and yours DRM keys is in their "place".
If your bootloader unlocked, then you could ask the person you have bought your phone from for TA-Partition backup, if he/she has it.
If not - don't ever think to flash anyone else's Ta-Partition, otherwise you'll brick your phone permanently.
You can relock it via Flashtool, If I'm right. But it doesn't change the situation you're in, 'cause your DRM keys are lost and you'll not be able to use BE2, Clear Audio+ and other fuctions, which requires the DRM keys to be working.
I'm sorry about that.
You can still flash stock .FTF, I suggest you to flash Generic.
If error persists, you could try other .ftf to fry for flashing.
Click to expand...
Click to collapse
It's show me Bootloader unlock allowed: Yes. I've flash C6603_10.5.1.A.0.292_Generic_NCB.ftf for my device but it show the above error.
Then I flash C6603_10.1.1.A.1.307_Generic BE.ftf it's all right nothing error.
Both of them are GENERIC but the 292 ftf error.
Could you please help suggest me which 292 ftf not error on my device.
And one more thing strange, I can't update my device with OTA even on 307 TFT. Someone say it only happen if my bootloader unlocked
I just tried C6603_10.5.1.A.0.292_Generic_UK.ftf too but it still error
The fact is I can't only flash which FTF include S1_Boot_Lagan_1.0_2 that mean I can't update my S1_Boot ?

hacphongthan said:
It's show me Bootloader unlock allowed: Yes. I've flash C6603_10.5.1.A.0.292_Generic_NCB.ftf for my device but it show the above error.
Then I flash C6603_10.1.1.A.1.307_Generic BE.ftf it's all right nothing error.
Both of them are GENERIC but the 292 ftf error.
Could you please help suggest me which 292 ftf not error on my device.
And one more thing strange, I can't update my device with OTA even on 307 TFT. Someone say it only happen if my bootloader unlocked
I just tried C6603_10.5.1.A.0.292_Generic_UK.ftf too but it still error
The fact is I can't only flash which FTF include S1_Boot_Lagan_1.0_2 that mean I can't update my S1_Boot ?
Click to expand...
Click to collapse
Well, you've not unlocked your bootloader. Your bootloader status is locked. However, do you have flashtool drivers? You could give a try on another pc, maybe your pc is causing issues, like mine (my os is Windows 10 and doesn't support fastboot and adb, as I can see).

LaurynasVP said:
Well, you've not unlocked your bootloader. Your bootloader status is locked. However, do you have flashtool drivers? You could give a try on another pc, maybe your pc is causing issues, like mine (my os is Windows 10 and doesn't support fastboot and adb, as I can see).
Click to expand...
Click to collapse
Yes I have flash tool driver on windows 7 Vmware but it error same my Windows 8 main PC :crying:.
Talk about OTA, why I can't update via OTA or PC companion

hacphongthan said:
Yes I have flash tool driver on windows 7 Vmware but it error same my Windows 8 main PC :crying:.
Talk about OTA, why I can't update via OTA or PC companion
Click to expand...
Click to collapse
I don't know anything else whast I could suggest you. U should better contact SONY:
Sony Support. Or if you have warranty - take it to there

LaurynasVP said:
I don't know anything else whast I could suggest you. U should better contact SONY:
Sony Support. Or if you have warranty - take it to there
Click to expand...
Click to collapse
oh ok thanks for your help

Camera freezes in LP but not in JB

My C6903 in LP 5.1.1 doesn't take photos (or videos) when the app tries to focus. Without focus enabled (using other app) it goes perfectly. I've tried with 14.6.A.1.236 Customized BAL, 15.5.A.0.242 Movistar AR and a few more, all obtained from XperiFirm.
I tried pushing that "4k and timeshift" .zip which I read could fix the camera but no luck.
Curious thing is that Rooting Status shows "Unknown", I don't know if this could be related or not. I bought the phone on eBay (used) and I couldn't tell you if it's been unlocked or not.
But I know that everything can't be messed up because in JB 4.3 (14.2.A.1.136 Generic BAL from XperiFirm) camera works well, and Rooting Status shows "Bootloader Unlock Allowed: Yes"; And in KK 4.4 (updated via OTA from mentioned JB firmware) camera stops working in the same way but Rooting Status keeps on "Bootloader Unlock Allowed: Yes".
What could I try? I think I've already read everything related to the Rooting Status Unknown and Camera freeze problems in this forum and still have no clue (even in other Xperias forums too).
Thanks by the way
PS: Yet I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink

matidx said:
PS: Yes I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
Click to expand...
Click to collapse
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!

kentexcitebot said:
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
Click to expand...
Click to collapse
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?

matidx said:
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
Click to expand...
Click to collapse
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.

kentexcitebot said:
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
Click to expand...
Click to collapse
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.

matidx said:
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
Click to expand...
Click to collapse
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Code:
fastboot.exe devices
you'll know that fastboot is working and drivers are set up correctly. If you look at your device LED, the LED will be lit blue. Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
matidx said:
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
Click to expand...
Click to collapse
Go here to download the correct fastboot driver files: http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS4zLTIwMTQwMjA5

If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Click to expand...
Click to collapse
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
Click to expand...
Click to collapse
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?

By the way, I'm also having this issue... http://forum.xda-developers.com/xperia-z1/help/baseband-lost-reboot-t3352858
Maybe it could be related someway (like motherboard going bad or something else).

matidx said:
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
Click to expand...
Click to collapse
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
matidx said:
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Click to expand...
Click to collapse
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.

kentexcitebot said:
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
Click to expand...
Click to collapse
I think I've followed everything right but to be clear I'm gonna explain what I've done so far:
- Installed Android Studio (I believe it comes with those "just the command line tools").
- Installed Flashtool's driver (same as the DoomLord link you provided, even a later update than that link), also did that thing about "Disable Driver Signature Enforcement" because I'm on Win10 64bit.
- Always checked by cmd command line "fastboot.exe devices", I've never get any error (so cmd always detected it as a valid command line) or any other cmd print.
- I have a TA backup but after I made it tried to unlock bootloader but no luck. Anyway, just restored the backup and only sign I got is "Upgrading NFC firmware" or something like that after booting, the "NFC upgrade" went well but still no fastboot access.
---
- When I plug the usb + press volume up button to try get fastboot mode, phone's led goes red then green then it goes off and in flashtool I get flashmode with no led on.
---
By the way, I have an Xperia SP and already unlocked bootloader so I pretty know how it should go. Having no problem with it accessing fastboot or even locking or unlocking on the XSP.
Because of this and baseband problem, I can't stop thinking motherboard is messed up.. But anyway, whatever you think I could try just let me know.