Database Develop

[Q] xperia z fasboot

my xperia z cant connect in fastboot anymore , right after I unlocked it .heres what my drivers look like.
https://docs.google.com/file/d/0B9_2y2HWWD2aZ1RmYi1NMm1kN2c/edit?usp=sharing
it says waiting for device .

9breaker said:
my xperia z cant connect in fastboot anymore , right after I unlocked it .heres what my drivers look like.
https://docs.google.com/file/d/0B9_2y2HWWD2aZ1RmYi1NMm1kN2c/edit?usp=sharing
it says waiting for device .
Click to expand...
Click to collapse
Just a question : Why do you have unlocked your bootloader? So many people unlock it for nothing, i'm sure i can do nearly same things with a locked bootloader, also with an unlocked bootloader you can't use PCC and SUS. Also unlocking bootloader avoid your warranty.

QualQuek said:
Just a question : Why do you have unlocked your bootloader? So many people unlock it for nothing, i'm sure i can do nearly same things with a locked bootloader, also with an unlocked bootloader you can't use PCC and SUS. Also unlocking bootloader avoid your warranty.
Click to expand...
Click to collapse
to flash cm 10.

9breaker said:
to flash cm 10.
Click to expand...
Click to collapse
Ok you got the point, you need an unlocked bootloader for a custom kernel.
So have you tried to restore it with PCC/SUS or Flashtool and retry? Maybe something haven't worked correctly the first time.
Do you have followed this thread http://forum.xda-developers.com/showthread.php?t=2153261 ?

This is after flashing the unlock token?
Can you power on the phone normally?
Are there any signs of life (LED indicator, screen backlight, vibration, etc.)?

QualQuek said:
Ok you got the point, you need an unlocked bootloader for a custom kernel.
So have you tried to restore it with PCC/SUS or Flashtool and retry? Maybe something haven't worked correctly the first time.
Do you have followed this thread http://forum.xda-developers.com/showthread.php?t=2153261 ?
Click to expand...
Click to collapse
I didn't flash anything the first time . i just unlocked the bootloader , i think the its a driver problem .when i plug it in in fastboot it says 'waiting for device' .the phone still works perfectly btw.
more info : Kernel 10.1.A.1.350 there's an update to .253 but I haven't installed it yet

9breaker said:
I didn't flash anything the first time . i just unlocked the bootloader , i think the its a driver problem .when i plug it in in fastboot it says 'waiting for device' .the phone still works perfectly btw.
more info : Kernel 10.1.A.1.350 there's an update to .253 but I haven't installed it yet
Click to expand...
Click to collapse
I can't tell exactly by your comments, but are you aware you need to start the phone in a different mode to access it via fastboot?
Disconnect USB
Hold Power & Volume Up until the phone vibrates three times in quick succession.
Let go of the buttons.
While holding Volume Up, connect USB cable between phone and computer.
The LED should turn blue to indicate you are in fastboot mode at which point you will need to install fastboot (not ADB) drivers. It shouldn't be possible to install ADB drivers if you do this properly.

Rekoil said:
I can't tell exactly by your comments, but are you aware you need to start the phone in a different mode to access it via fastboot?
Disconnect USB
Hold Power & Volume Up until the phone vibrates three times in quick succession.
Let go of the buttons.
While holding Volume Up, connect USB cable between phone and computer.
The LED should turn blue to indicate you are in fastboot mode at which point you will need to install fastboot (not ADB) drivers. It shouldn't be possible to install ADB drivers if you do this properly.
Click to expand...
Click to collapse
whilst in fastboot i get the message waiting for device .the device has connected in fastboot before , that's how i unlocked the boot loader .

[Q] Unable to access Fastboot mode

I read through many threads and have followed the official Sony bootloader unlocking instructions. I have requested and received the unlock code from Sony via email. I have downloaded the inf file and placed it in the correct folder in Android SDK (which I also updated). But I am cannot access fastboot mode, I hold down Vol + and plug in the USB cable but the device shows a red led and goes into charging mode. Also the PC never prompts me to install fastboot driver it simply loads the SP as Sony mass storage device (in device manager).
I have read that some people seem to think that the SIM lock affects the ability to access fastboot but this SP is SIM unlocked. Sony's official guide to unlocking the bootloader says I need to access fastboot mode to enter the unlock code but how can I unlock the bootloader if I can't get into fastboot mode?

hmmm... don't know really... i once entered fastboot mode by mistake, while trying to root stock rom. wasn't reading instructions and put device in a fsatboot mode instead of debugging... was on stock rom so don't know if custom rom would let me do that. should check myself... if anything i know it is possible to get me that blue light shining.

To enter fastboot mode in Xperia SP just power down the phone and hold down the volume up key while pluging your phone into your pc
If you need flashmode do the same thing but with the volume DOWN button held down.

I´ve got the same problem. I can´t enter in flashmode neither in fastboot mode. I´m on windows 8 32bits and I installed the .245 Deodexed ROM with a problem on root and without CWM. I don´t know what to do now, please help me.

As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?

gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.

jackaros said:
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
Click to expand...
Click to collapse
Thanks for trying to help, but I understand that flashmode and fastboot are accessed using the phone. Actually the phone needs a piece of software like flashtool to keep it in flashmode otherwise it drops into charging mode. I didn't mention my computer so I don't know where you got that from.
As I explained, I am unable to access fastboot with stock ROM (1.257) and a custom ROM (based on 2.245) so it can't be a ROM bug or the flashing process having gone wrong.

if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.

Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.

Ze Tolas said:
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Click to expand...
Click to collapse
It may be a flashtool problem you are right because 2 incidents with different Roms that both use flashtool to flash those roms.....
its pretty much self explenatory.

skojevac said:
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Click to expand...
Click to collapse
Interesting. Ok, I've read up on the process. So I use the various stock .ftf files and flashtool with the phone in flash mode? Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. If I do it, I will nandroid backup first, of course, but I think I remember reading in one thread that someone managed to soft brick their XSP doing this very thing.

Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. [/QUOTE said:
that's why you need to complete rooting procedure. root stock 1.257 kernel, than back to stock 2.245 with root preserved, and before you would install CWM try to put device in a fastboot mode, this assuming you still have a UB.
Click to expand...
Click to collapse

have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot

SuicideFlasher said:
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
Click to expand...
Click to collapse
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.

i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.

skojevac said:
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
Click to expand...
Click to collapse
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.

gandalf_grey91 said:
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
Click to expand...
Click to collapse
I said before, it's new firmware (maybe RU) with a Windows Flashtool issue. Today i did flash kernel to my SP using Linux client.

Same issues
gandalf_grey91 said:
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
Click to expand...
Click to collapse
Hi, I have some similar issues. I've also been flashing some stuff and whenever I try to go to fastboot it just boots into CWM. Very annoying to say the least. The dark blue light goes on when i hold down volume up and for a short moment I see the fastboot driver installing on my computer. But before it completes it's already in CWM.
Not sure what to do from here on wards, maybe some advice on which kernel to flash? I am pretty sure the latest kernel I flashed is the .254 root kernel from doomlord.
Ps. I really would like to flash CM when it becomes available as nightly :angel:
Thanks in advance!

Fast boot mode for xperia ion hspa???
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
I had already installed cm10.1 jb for my xperia ion.
Now i tried to install cm11 kitkat for my xperia ion.
Every thing is gone good.
But now got stuck up with a problem.
fast boot mode is active only for 5 seconds while connecting my xperia ion to System with flash tool.
help me to do the need ful.
Guide me to download compatible drivers and flash tool for fast booting process.

If you have UNLOCKABLE bootloader, then you dont have a FASTBOOT mode on your phone. Its just pure luck. some phones dont have it... kind of a sony crap... I also happen to be one of those LUCKY ppl. no unlock, so stuck with Stock kernel forever.
When you connect your phone to Flashtools in FLASHMODE...
See for a string BOOTLOADER: NOT_ROOTABLE.... it means you belong in the lucky group...
If it says rootable, then you're doing something wrong.
Pardon me if i read something incorrect. i skimmed through all the posts before posting.

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

xperia z c6603 IMEI corrupt and restarts after flashing a c6602 firmware

I have a sony xperia z c6603 , it was never unlocked from the start but it worked very fine on its original firmware, android 4.1.2. But then someone flashed a c6602 android 4.1 on it and now the IMEI is corrupted and it restarts every 9.3minutes.
It says bootloader unlock allowed: Yes which I guess means the bootloader is locked and can be unlocked, but since IMEI is corrupt, i cant request for unlock code from sony or use fastboot.
My only other option is the famous flashtool. I have three issues with flashtool.
1. I already downloaded the correct firmware and preparing to flash, so I click on the flash icon and start flash (Using Androxyde flash tool). It goes through the normal process and then an empty device selector screen comes up, with no option but to cancel. and when i cancel, it says "loader not found for this device"
2. Okay, after step 1, i am thinking "maybe i have to unlock the bootloader first" so i click on the BLU button and connect the device in flash mode, it starts and the empty device selector screen comes up again, once i cancel, it says "your device can not be officially unlocked"
3. So i did a little bit of digging around on here more and found that i have to update xflasher.jar to beta6, and so i did and flash tool started as "androxyde and bin4ry flash tool" .Only problem is when i click on the flash icon and choose flash mode, nothing comes up, i cant get into flash mode. but I can get into every other thing like fastboot mode and BLU
Please if you think you have an idea on how to solve this problem, please reply. I cant afford a new phone and I would also like to know if my phone can be repaired too, I also dont have a lot of time to waste trying to repair it.

try to reinstall flashtool after deleting it first .. install fastboot and flashmode drivers and drivers for ur device from drivers folder in flashtool folder.. disable any antivirus and any app that could interfere and unplug any usb device ... try to flash with flashmode
---------- Post added at 12:39 AM ---------- Previous post was at 12:35 AM ----------
mordr3d said:
I have a sony xperia z c6603 , it was never unlocked from the start but it worked very fine on its original firmware, android 4.1.2. But then someone flashed a c6602 android 4.1 on it and now the IMEI is corrupted and it restarts every 9.3minutes.
It says bootloader unlock allowed: Yes which I guess means the bootloader is locked and can be unlocked, but since IMEI is corrupt, i cant request for unlock code from sony or use fastboot.
My only other option is the famous flashtool. I have three issues with flashtool.
1. I already downloaded the correct firmware and preparing to flash, so I click on the flash icon and start flash (Using Androxyde flash tool). It goes through the normal process and then an empty device selector screen comes up, with no option but to cancel. and when i cancel, it says "loader not found for this device"
2. Okay, after step 1, i am thinking "maybe i have to unlock the bootloader first" so i click on the BLU button and connect the device in flash mode, it starts and the empty device selector screen comes up again, once i cancel, it says "your device can not be officially unlocked"
3. So i did a little bit of digging around on here more and found that i have to update xflasher.jar to beta6, and so i did and flash tool started as "androxyde and bin4ry flash tool" .Only problem is when i click on the flash icon and choose flash mode, nothing comes up, i cant get into flash mode. but I can get into every other thing like fastboot mode and BLU
Please if you think you have an idea on how to solve this problem, please reply. I cant afford a new phone and I would also like to know if my phone can be repaired too, I also dont have a lot of time to waste trying to repair it.
Click to expand...
Click to collapse
try to install a newer version of flashtool ...

**HELP** Flashed TWRP Zip file. Phone reboots into black screen after boot logo.

Cannot get into recovery. Device seems to be bricked.
After Sony logo there is nothing else other than black screen. Please help me recover my device.

Don't Panic, this can easily be recovered. However the data that was inside I'm afraid is gone forever. Maybe it can be recovered maybe not, anyway I'm giving you some easy steps you can follow to recover your device.
1. Download Flashtool
2. Download the Firmware you want to load into the phone. (Search in the forum for .ftf ---make sure it is for Xperia Z --- files or you can download Xperifirm and make them on your own)
3. Once you have the .ftf file ready click on the Flash (Lightning) icon and select the firmware (.ftf) [Mode to flash is FLASHMODE]
4. When the phone is just one second from booting up (I know you are now in a cycle - loop but try as many times until you get it right), with the VOLUME DOWN button pressed connect it into the PC.
5. Wait for flash - About 10-15 min and you are done.
For any questions ask here. Good luck

I recovered my phone via Sony PC companion. Succesfuly managed to flash dual recovery again. Flashed ROM and Gappps.
This time Phone didnt start after reboot. There is not even a sony logo. No reboots at all and now it seems bricked ?
If anyone is reading please help me out.
I tried using Flashtools getting into Fastboot mode (Blue light flashing), but Flashtoool responded saying needs to installl drivers. I did that as well, but now the flashtools wont start at all.
I am trying via pc companion, Its stuck on a step where its asking me to remove my battery.. How do I recover ? Please help. Thanks in advance.

ProudRed said:
I recovered my phone via Sony PC companion. Succesfuly managed to flash dual recovery again. Flashed ROM and Gappps.
This time Phone didnt start after reboot. There is not even a sony logo. No reboots at all and now it seems bricked ?
If anyone is reading please help me out.
I tried using Flashtools getting into Fastboot mode (Blue light flashing), but Flashtoool responded saying needs to installl drivers. I did that as well, but now the flashtools wont start at all.
I am trying via pc companion, Its stuck on a step where its asking me to remove my battery.. How do I recover ? Please help. Thanks in advance.
Click to expand...
Click to collapse
Can you get to the point where the phone lights up the GREEN LED (flash mode) ?
Also what version of windows are you using?

aaronkatrini said:
Can you get to the point where the phone lights up the GREEN LED (flash mode) ?
Also what version of windows are you using?
Click to expand...
Click to collapse
Hi, Flash mode is working for me. I have recovered couple of times using flashtools in flash mode. But fastboot mode is not working for me. It says drivers are missing though I have installed drivers..
I went through tthe threads and could find a workking method to unlock the bootloader. Sony has too many appps which I do not need, I want to get rid of them as it consumes a lot of batttery. Hence a custom Rom with basic stuffs arre the soolution.
If you can help me unlock my BL I'd be thankful
And one more question, does TWRP's Latest version only works for Unlocked BL ?

ProudRed said:
Hi, Flash mode is working for me. I have recovered couple of times using flashtools in flash mode. But fastboot mode is not working for me. It says drivers are missing though I have installed drivers..
I went through tthe threads and could find a workking method to unlock the bootloader. Sony has too many appps which I do not need, I want to get rid of them as it consumes a lot of batttery. Hence a custom Rom with basic stuffs arre the soolution.
If you can help me unlock my BL I'd be thankful
And one more question, does TWRP's Latest version only works for Unlocked BL ?
Click to expand...
Click to collapse
First, Try to do things in order!!!
You are very messy, first you needed to unbrick the device, now you want to unlock its BL and want to know if you can install TWRP!
Install a stock firmware, make sure you can unlock the phone (by checking in the settings menu)...
And post some info...
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
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.

aaronkatrini said:
First, Try to do things in order!!!
You are very messy, first you needed to unbrick the device, now you want to unlock its BL and want to know if you can install TWRP!
Install a stock firmware, make sure you can unlock the phone (by checking in the settings menu)...
And post some info...
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
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.
Click to expand...
Click to collapse
Device unbricked, stock rom running with Root access and dual recovery installed. Fastboot drivers cant be installed, what to do ? And how to do ? OS Windows 10

All issues solved. On custom ROM now. Thank You to those who tried to help.

ProudRed said:
All issues solved. On custom ROM now. Thank You to those who tried to help.
Click to expand...
Click to collapse
Good for you, for anyone who needs to install fastboot driver on windows 10, when they cannot install they need to disable windows driver signature:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Also for some who is in the same situation please post your solution, it helps the community.
P.S.: you can always hit that thanks button instead of thanking

I would like to know if there are custom kernels available for battery saving ? I flashed Zomie kernel and it was repeatedly booting my device into multirom recovery.
Right now I am on mokee, can I use any custom kernel with it ? If yes what ? I couldnt find many custom kernels for the device and what about Roms ? Not many custom Roms as well, only found RR and Mokee. Slim LP does not have a working link and couldnt find other popular roms too for this device.

I never tried new kernels, only thing install Kernel Adiutor and underclock, also change the governor mode.
As for the rom I use the modified stock rom by @androidexpert35, it provides good balance between performance and battery life. For any Rom you should write in their dedicated post. Keep experimenting but do it in a reasonable way and don't try to ask for everything, search and read others. Good luck