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

Flashtool problem help plz

Hello i tried connecting my XSP to flash a new kernel in fastboot mode and windows 7 say unrecognized device i tried installing all drivers provided in the flashtool drivers folder with no result .... I tried installing the fastboot and flashmode drivers but no reaction from the pc it still says unrecognized device .
Sorry for the bad description of the problem but i was typing in a hurry for any details please ask me.

My Z1 doesn't determined by PC in fastboot mode

Hi guys! I need your help. I have z1 with ROOT and custom recovery and i would like to update it to android m. The main probleme - bootloader, i should unlock it. But i can't do it because phone doesn't determined by pc in fastboot mode or flashmode and when phone is off doesn't determined at all. But even when phone is on, pc detected phone not always, just sometimes, and phone doesn't charging. ADB drivers is installed, drivers for flashtool mode and fastboot is installed. Command window says "waiting for device" when i want to boot my phone in fastboot. When phone is on ADB works fine. So i've read many topics about problems like that and didn't find the solution. Maybe can anybody help me please?

In ADB , use the command: adb reboot bootloader
The phone will reboot and you'll be in fastboot mode and the phone will show a deep blue notification light.
You need to install fastboot drivers from the driver package bundled along with flashtool before this. So u have to donwload flashtool first
Also, if u're going to unlock the bootloader then back up your TA partition.

In ADB , use the command: adb reboot bootloader
The phone will reboot and you'll be in fastboot mode and the phone will show a deep blue notification light
Click to expand...
Click to collapse
Yeah, I did it, the phone was showing blue led, but then it goes nothing, then pc doesn't "see" the phone. I have already installed flashtool and drivers with it for fastest and flashtool. Also I have already made a backup of TA through flashtool.
So I can do something with phone through flashtool or adb when phone is on, but when phone is off I can't do anything. I have heard that reason of that problem can be broken phone's USB port. What do you think?
And sorry for my terrible English

I've connected phone to pc in flashmode through NDR Utils, but fastboot still doesn't work

honestly, im stumped!! . AFAIK its not a problem with the usb port cuz as you said it works fine with adb. Did you try a different usb cable.
You should probably try to reinstall the fastboot drivers
But if you just wanna unlock the bootloader then you can do that with flashtool I think.

But if you just wanna unlock the bootloader then you can do that with flashtool I think.
Click to expand...
Click to collapse
Yes, but to unlock bootloader through flashtool I should go to fastboot

wait, does the blue led come on and disappear?? it sounds like a loose USB cable

masterofnocrack said:
wait, does the blue led come on and disappear?? it sounds like a loose USB cable
Click to expand...
Click to collapse
No, the blue led come on and lights until i unplug the cable.
Is it not a normal?

I have the same problem xD
All the time it worked, wtf

zawy. said:
I have the same problem xD
All the time it worked, wtf
Click to expand...
Click to collapse
Did you find the solution?
What did you do to fix it? Maybe we can help to each other

Hi! It's me again And i still didn't solved my probleme. So, i can connect my phone to PC and it recognize as Android device -> ADB interface, and as Xperia z1. If i just connect powered off phone to PC or connect phone in flash mode, then it recognize as USB devices -> SOMC Flash Device, is it right? Ok, when i want to connect phone in fastboot, phone shows blue LED and it goes nothing, PC don't determine the phone and i can't unlock bootloader

Device won't show up on fastboot adb or Mi Flash

So, my MI3W won't show up on fastboot devices command , neither does it show in MiFlash.....
I have installed minimal adb and fastboot also i have installed latest MiPcSuite . Even it doesn't show in device manager . I am runnig windows 10 with driver enforcement disabled .

gauravbhakuni90 said:
So, my MI3W won't show up on fastboot devices command , neither does it show in MiFlash.....
I have installed minimal adb and fastboot also i have installed latest MiPcSuite . Even it doesn't show in device manager . I am runnig windows 10 with driver enforcement disabled .
Click to expand...
Click to collapse
try this
en.miui.com/thread-73348-1-1.html

smh.saad said:
try this
en.miui.com/thread-73348-1-1.html
Click to expand...
Click to collapse
My phone is running fine. Its just that it is not showing up on PC device manager.And I can't use fastboot commands. ADB commands are running fine.

gauravbhakuni90 said:
My phone is running fine. Its just that it is not showing up on PC device manager.And I can't use fastboot commands. ADB commands are running fine.
Click to expand...
Click to collapse
might be windows drivers problem or USB FLex need to be replaced
or a bad USB cable

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?