Database Develop

[Q] Accidentally formatted /system on unlocked BL Xperia T: now it won't boot.

Hi guys,
I accidentally formatted /system on my T with UB.
Now it won't start (it says "Sony", then nothing happens). It now has no recovery and if I connect the phone in fastboot or flashmode, the usual PC I use to flash says me that "Sony ADB interface" is connected, but it can't find any driver.
What can I do now?
Thanks in advance for the reply.

DS-1 said:
Hi guys,
I accidentally formatted /system on my T with UB.
Now it won't start (it says "Sony", then nothing happens). It now has no recovery and if I connect the phone in fastboot or flashmode, the usual PC I use to flash says me that "Sony ADB interface" is connected, but it can't find any driver.
What can I do now?
Thanks in advance for the reply.
Click to expand...
Click to collapse
If it says "Sony ADB interface" when you connect it, then you don't need a driver, it's already installed (you can confirm this if you open Device Manager in Windows and check if it's listed as an "ADB interface" and there are no "Unknown Devices" and/or devices named in relation to your phone that have a yellow exclamation mark.
Just flash a stock FTF, or download one of the kernels for T that have a recovery, and flash any ROM you like.

First of all, thanks for the reply.
The strange thing about this time brick is that my pc doesn't recognize the phone. Other times, infact, I used it with the same phone to relive the Xperia T, after strange things happened.
Instead, this time the phone is recognized as "Sony ADB interface" and the pc says there's no driver in it. And it can't find in the system (I'm using an old laptop with Windows XP on it).
That's the reason why the system (and Flashtool, too: it says, in red, that I need to install the drivers for my phone) doesn't recognize the phone.
Now I'm trying the T into another Windows XP old laptop system...I hope it works (and I hope USB 1.1 will be fine, too...).
EDIT: this "new" pc see my phone, connected in fastboot mode, as "SEMC Flash Device" and it is installing the drivers. I've already installed fastboot/flashmode drivers from Flashtool Drivers folder.
RE-EDIT: PC can see the Xperia T, but Flashtool always says that it is connected in "flash mode", even if I connect it in fastboot mode. What should I do, now?
RE-RE-EDIT: The phone is recognized only in flashmode, even if I installed all the drivers. I'm trying to flash .141 and it seems to work. Let's see what happens.
Antiga Prime said:
If it says "Sony ADB interface" when you connect it, then you don't need a driver, it's already installed (you can confirm this if you open Device Manager in Windows and check if it's listed as an "ADB interface" and there are no "Unknown Devices" and/or devices named in relation to your phone that have a yellow exclamation mark.
Just flash a stock FTF, or download one of the kernels for T that have a recovery, and flash any ROM you like.
Click to expand...
Click to collapse

DS-1 said:
First of all, thanks for the reply.
The strange thing about this time brick is that my pc doesn't recognize the phone. Other times, infact, I used it with the same phone to relive the Xperia T, after strange things happened.
Instead, this time the phone is recognized as "Sony ADB interface" and the pc says there's no driver in it. And it can't find in the system (I'm using an old laptop with Windows XP on it).
That's the reason why the system (and Flashtool, too: it says, in red, that I need to install the drivers for my phone) doesn't recognize the phone.
Now I'm trying the T into another Windows XP old laptop system...I hope it works (and I hope USB 1.1 will be fine, too...).
EDIT: this "new" pc see my phone, connected in fastboot mode, as "SEMC Flash Device" and it is installing the drivers. I've already installed fastboot/flashmode drivers from Flashtool Drivers folder.
RE-EDIT: PC can see the Xperia T, but Flashtool always says that it is connected in "flash mode", even if I connect it in fastboot mode. What should I do, now?
Click to expand...
Click to collapse
Ok, well, no idea about it being stuck in flash mode, but, isn't that exactly what you want? To flash a stock FTF you need to be in flash mode. As a matter of fact, you can even flash only the kernel of an FTF in flash mode, it wouldn't have a recovery, since it would be a stock kernel, but at least you could get a working kernel, if that were the issue, which it is not.
What are you doing to put your phone into fastboot mode?

I wanted to use fastboot to flash a kernel with recovery and then flash the backup of my old ROM.
However, it doesn't worked. Only flashmode worked. So I flashed (really slowly, because of USB 1.1 ports of this old IBM laptop!) .141 and now the phone is living again.
Dunno why fastboot didn't work. Maybe because there wasn't any firmware on?
Antiga Prime said:
Ok, well, no idea about it being stuck in flash mode, but, isn't that exactly what you want? To flash a stock FTF you need to be in flash mode. As a matter of fact, you can even flash only the kernel of an FTF in flash mode, it wouldn't have a recovery, since it would be a stock kernel, but at least you could get a working kernel, if that were the issue, which it is not.
What are you doing to put your phone into fastboot mode?
Click to expand...
Click to collapse

DS-1 said:
Dunno why fastboot didn't work. Maybe because there wasn't any firmware on?
Click to expand...
Click to collapse
No because the whole point of fastboot mode is to be able to flash firmware related files. Fastboot mode, just as Flash mode, starts before the Android OS starts. If they depended on there being an OS installed it would defeat the whole point.

So I really dunno why it didn't work. Later I'll try to see if now fastboot is working again.
Antiga Prime said:
No because the whole point of fastboot mode is to be able to flash firmware related files. Fastboot mode, just as Flash mode, starts before the Android OS starts. If they depended on there being an OS installed it would defeat the whole point.
Click to expand...
Click to collapse

When you don't have a ROM installed,stock kernels recovery won't work. Flash CM 11s Kernel, you'll have recovery then restore you're backup

[Q] Boot loop, no usb debug, no cmw

Hi all! like most I have joined with a problem
I Have an xperia SP-C5303
I successfully rooted the device with the Towelroot app, Then used the sony mobile flasher by Androxyde to flash cyanogenmod 10.2 onto my phone. This was all working fine.
I used CMW to install an update downloaded through cyanogenmod. When I rebooted the device it was stuck in a bootloop. The device connects top the computer in flash mode, but will not accept a flash because somehow "USB Debugging" is not enabled. It was obviously enabled before because I had already flashed the device.
ADB drivers are installed but to be honest Im a bit lost now. Does anyone have any ideas how to turn on usb debugging so that I can flash my phone again?
Korbey
I can connect to sony mobile flasher in flash mode but flashing fails at the end with the program saying "For flashtool, Unknown Sources and Debugging must be checked in phone settings" how can I activate these when in a boot loop?

Korbey said:
Hi all! like most I have joined with a problem
I Have an xperia SP-C5303
I successfully rooted the device with the Towelroot app, Then used the sony mobile flasher by Androxyde to flash cyanogenmod 10.2 onto my phone. This was all working fine.
I used CMW to install an update downloaded through cyanogenmod. When I rebooted the device it was stuck in a bootloop. The device connects top the computer in flash mode, but will not accept a flash because somehow "USB Debugging" is not enabled. It was obviously enabled before because I had already flashed the device.
ADB drivers are installed but to be honest Im a bit lost now. Does anyone have any ideas how to turn on usb debugging so that I can flash my phone again?
Korbey
I can connect to sony mobile flasher in flash mode but flashing fails at the end with the program saying "For flashtool, Unknown Sources and Debugging must be checked in phone settings" how can I activate these when in a boot loop?
Click to expand...
Click to collapse
I would like to know if your Xperia SP has its bootloader unlocked?
The error most likely appear because you have no drivers for Xperia SP. Yes you might said that you installed it already but let's try again. Navigate to the Flashtool installation directory, which is C:\Flashtool by default. Then go into drivers folder and run the installer therein. Please tick fastboot drivers and flashmode drivers. Scroll down a bit and find Common drivers for Viskan board. Tick that as well and continue the driver installation.
After everything is completed. Close Flashtool and open in again (in case you've disabled UAC, please run Flashtool as an administrator). Then retry to flash a stock ROM's .ftf file.

[Q] Please help me, i'm giving up!! Nothing works!!

Hey XDA.
For long i have been trying to get a custom ROM for my android, but to be able to do that, i need to unlock bootloarders for my device.
I have been trying for a couple of months now, and everytime i try, i hope that it will work this time... but i always end up quitting, because i always encounter some problem, i cant seem to resovle.
I was wondering if anyone would like to help me through, step by step, until it actually works.
This is what i have tried
- I have entered the system configurator, and it says yes to that my device can be unlocked.
- I have enabled all the developer options descirbed everywhere
- I have downloaded the Android SDK, with the google USB drivers.
- I have gotten my unlock-code from Sony
But everytime i try to follow the steps from Sony, I get an error when coming to install the drivers.
The tutorial says, that when i plug the usb-cable to my computer, i would be prompted to install some drivers... I dont, it automaticly installs something called "S1Boot Fastboot".
Then i enter my device-manager, finds the device, and updates drivers manually from my computer.
But when i point to the downloaded drivers, i get this error:
Windows found a driver-software for your device, but encountered an error while trying to install it.
Windows ADB Interface
The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tampered with.
The files i have downloaded are all those Sony told me to download, from the official distributors... I got no idea how to solve this issue!!
Can anybody please help to fix this issue, or guide me through another way that works?
I have given up trying...

Download flashtool, and instal drivers from his directory (flashtool and fastboot) drivers.
Also instal PC Companion, but restart pc after instal (PC Companion also installs drivers)
Also, you might turn of driver signature checking if you are on windows 8.1, google it.

electrash said:
Download flashtool, and instal drivers from his directory (flashtool and fastboot) drivers.
Also instal PC Companion, but restart pc after instal (PC Companion also installs drivers)
Also, you might turn of driver signature checking if you are on windows 8.1, google it.
Click to expand...
Click to collapse
I agree with this. I just did it the other day.
I'm using a Win 8.1 laptop and it was driving me mad. I followed the information regarding changing some of my start up settings on the laptop and flashtool installation of drivers worked. Follow this. http://forum.xda-developers.com/showthread.php?t=1913245&page=6
In my case i had Flashtool installed, but when i went to install the drivers for my z1 , the windows installer would always fail. After using the information on that page I Linked, it worked straight away!
Good luck .

Thanks alot!
Thank you very much guys, that was just what i missed!

Glad you finally got it!
Sent from my C6903 using XDA Free mobile app

Black screen in bootloader, storage not recognized in Windows and fastboot.

I've been searching for quite some for the solution but I wasn't lucky to find it anywhere online.
I flashed my phone several years ago with a custom ROM and haven't touched it since then. I unlocked the bootloader, flashed kernel and installed a new ROM as was described in the guide.
However, now when I try to access the bootloader or recovery I just see a black screen and a constant blue LED. On top of that, Windows tells me to "Insert a disc into the drive" when it's connected. The phone is also not recognized by Sony PC Companion or Sony Emma when it's plugged in. Flashtool by Androxyde sits there waiting to detect my phone.
The device, however, is listed in ADB under "adb devices", but "fastboot devices" shows an empty list.
I have tried a different PC just to see if I messed up the drivers, but same thing happens there too.
CORRECTION: Flashtools actually sees the phone, my bad. It identifies it EXCEPT for fastboot drivers (of course while the phone is in fastboot mode).
Any ideas on what's happening and how can I fix this issue?

I think your drivers are not installed correctly. In Windows you need to disable driver signature verification first. Then, you can install the drivers in Flashtool, if I remember it right.

M1chiel said:
I think your drivers are not installed correctly. In Windows you need to disable driver signature verification first. Then, you can install the drivers in Flashtool, if I remember it right.
Click to expand...
Click to collapse
Is it necessary to disable that? I have never had to disable that in order to install drivers for my Android phones. Whenever I try to install the drivers, some of them fail:
http i.imgur dot com/dguUIj6.jpg
http i.imgur dot com/1mTjnp0.jpg
List of drivers I choose to install:
Flashmode Drivers
Fastboot Drivers
Xperia Z3 Compact Device Driver

Yes, at least in Windows 10 you do. It is not difficult.

Help,device not detcted in fastboot

this is my frist time doing this. I follow step by step guide. I even look for solution online and still dont work. I dont know whats wrong. I want to unlock bootloader to install LOS 17.1.
im using windows 10. device not detected in fastboot.
I SURRENDER. I need help. T_T
thank you !

HELP...i tried installing flashtool driver and adb 1.4.3 still dont work

do you think I need original sony cable to be recognized?

ADB / FastBoot drivers are not all you need to access your phone via USB: you must also have the OEM specific "Android USB Driver" installed on your computer.
More here: https://www.getdroidtips.com/download-latest-sony-usb-drivers/

You mean OEM driver is, my device driver (viskan,Xperia sp driver)in picture 2.everytime I manually installed it (device can't start code error 10.)
pictures 3 and 4 show that I successfully installed the oem Sao sony adb driver and still device is not detected in fastboot mode?
I even tried it on windows 7 ultimate same problem.maybe I'm missing something?