[Q] Can't connect in fastboot

[Theonewithideas]

In command prompt, I typed "fastboot -i 0x0fce getvar version"
And, it stays at <waiting for device>

I'd like to point out that I succeeded at flashing custom ROM last time, but now, it won't connect in fastmode.

I've installed the SDK (obviously)
Added the .inf file from SE site
Installed drivers from Flashtool folder
LED goes blue when connecting.
I've tried different ports, different OS, different PC altogether, but everything ends up with <waiting for device>.

Is the problem on the phone? How can I fix it?

 

[Someguyfromhell]

Drivers seem to be fine...

Does your phone really go into fastboot? Blue LED stays on, nothing on the screen. If yes, check drivers once again! Does Windows detect the device?

 

[Theonewithideas]

Drivers seem to be fine...

Does your phone really go into fastboot? Blue LED stays on, nothing on the screen. If yes, check drivers once again! Does Windows detect the device?

Yes, the LED is blue, the screen is off.

Windows does make sound when connecting, and it doesn't pop up "new device" wizard.

 

[Theonewithideas]

Hey! Just noticed something.

When uninstall the drivers connect the device, Device Manager says "S1boot fastboot" briefly before going into "SEMC Flash Device"

How can I disable it from going to SEMC Flash Device?

And it happens only when I have drivers uninstalled. Seems they install once I connect the phone. Tried again without uninstalling drivers, and it goes straight to "Flash device"

 

[Someguyfromhell]

Then maybe wrong drivers installed?

 

[Theonewithideas]

Then maybe wrong drivers installed?

Maybe:

I've reinstalled the SDK - didn't work
Added .inf file from SE site - didn't work
Installed Flashtool drivers - didn't work

But now, I'm waiting for Lollylost100 to reupload the drivers he once uploaded on Megaupload - I think those ones worked last time (hopefully)


I'll install Debian and try again with new OS, with no installed drivers or whatever...

 

[xbox360k550]

USB debuging is on?

 

[hsrbnr]

Just wait a few seconds after connecting you phone in fastboot mode, sometimes computer takes time process.

 

[Lasanda]

In command prompt, I typed "fastboot -i 0x0fce getvar version"
And, it stays at <waiting for device>

I'd like to point out that I succeeded at flashing custom ROM last time, but now, it won't connect in fastmode.

I've installed the SDK (obviously)
Added the .inf file from SE site
Installed drivers from Flashtool folder
LED goes blue when connecting.
I've tried different ports, different OS, different PC altogether, but everything ends up with <waiting for device>.

Is the problem on the phone? How can I fix it?

2 things can be resone for this.first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.

https://www.dropbox.com/s/x57ebyha7r65o27/fastboot.rar

Dont forget to thanx if this helpfull...

 

[Theonewithideas]

USB debuging is on?

Yes.

Just wait a few seconds after connecting you phone in fastboot mode, sometimes computer takes time process.

Tried that, left phone on fastboot for a few minutes while looking for solution. No difference.

2 things can be resone for this.first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.

https://www.dropbox.com/s/x57ebyha7r65o27/fastboot.rar

Dont forget to thanx if this helpfull...

Okay, I will try this and post the results.

Actually, will this work with Mini?

 

[Lasanda]

Yes.



Tried that, left phone on fastboot for a few minutes while looking for solution. No difference.



Okay, I will try this and post the results.

Actually, will this work with Mini?

I think it also works with mini as well.just try it.

 

[Theonewithideas]

Installed everything again, on Ubuntu. I've reached the Windows checkpoint: it again says "<waiting for device>".

Could this be a phone-related error?

 

[Lasanda]

Installed everything again, on Ubuntu. I've reached the Windows checkpoint: it again says "<waiting for device>".

Could this be a phone-related error?

try my method in windows pc.it dont works in ubuntu.it seems,there is no problem in your device.it may be there is some thing missing what you want.try my method back with windows pc and post clearly the resault with steps.if something wrong.i will help you.don't worry....

 

[Someguyfromhell]

Windows drivers do not work on Ubuntu, the same vice-versa also.

 

[Theonewithideas]

2 things can be resone for this.first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.

https://www.dropbox.com/s/x57ebyha7r65o27/fastboot.rar

Dont forget to thanx if this helpfull...

Okay, if you say so:

first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed...

This didn't work, it's SEMC Flash Device again, and fastboot doesn't work.


.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder...

Can't find the drivers. It will not help, every fastboot folder is the same.

.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.

... or, you can just type "cd" and then location to fastboot.

 

[Lasanda]

Okay, if you say so:

first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed...

This didn't work, it's SEMC Flash Device again, and fastboot doesn't work.


.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder...

Can't find the drivers. It will not help, every fastboot folder is the same.

.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.

... or, you can just type "cd" and then location to fastboot.

ok.i got that.another thing i need to know is when u do first step is that the device manager recognized your device,if does,is it updates your device drivers when u point the drivers location to x64 or x86?(when u do that it must show android adb interface drivers installed, when u check device manager)which version of windows u used to do those steps? and tell me your device name and model.i will upload a correct fastboot program for u.just keep your hopes alive....

EDIT

When uninstall the drivers connect the device, Device Manager says "S1boot fastboot" briefly before going into "SEMC Flash Device"

just have to mention u one thing..now i read this post u quoted before.it seems there is no any problem in your device.when u uninstall drivers u says this "S1boot fastboot" shows on your device manager it meens your device works well.S1boot fastboot meen device fastboot hardware it exactly not installed yet.u need to update drivers of this "S1boot fastboot" as my methods first step.just send me the progress and answers for my questions thats all.i will send a fix.

 

[Gioo25]

Can't connect in fastboot mode

Hi!

I want to unlock the bootloader of my Xperia Arc S (Lt18i) but i can't connect my phone in fastboot mode. When i connect the cable to PC, the LED flashes blue, but just for a few seconds and turns red. The message that appears in command prompt is "waiting for device". I tried so several solutions but no one worked.
Could you help me?

Thanks.

---------- Post added at 11:37 PM ---------- Previous post was at 11:11 PM ----------

Hi!

I want to unlock the bootloader of my Xperia Arc S (Lt18i) but i can't connect my phone in fastboot mode. When i connect the cable to PC, the LED flashes blue, but just for a few seconds and turns red. The message that appears in command prompt is "waiting for device". I tried so several solutions but no one worked.
Could you help me?

Thanks.

Sorry for my last post. When searching in some forums, I discovered that I can not unlock the bootloader. It seems that is a definition of the system.

Thank You And sorry. :crying:

 

[brixe]

Go to Service Mode to see if it can be unlock.

 

[Gioo25]

Go to Service Mode to see if it can be unlock.

Thank you! I've done that and the result is this: "bootloader unlock allowed: NO".

 

[ganirockz]

SAme Same

Yes.



Tried that, left phone on fastboot for a few minutes while looking for solution. No difference.



Okay, I will try this and post the results.

Actually, will this work with Mini?

Having the same problem with my SE LWW.