Database Users

Fastboot, waiting for device.

Hi guys, I recantly decided to update my gt540 from 2.1 to 2.3.3
I followed steps by steps on by this tutorial - http://fdapps.comuf.com/downloads/The LG GT540 Optimus reference page.pdf
Installed rom with fastboot, tried to install Clockwork with fastboot, I typed fastboot flash recovery C:\recovery.img , and then there's <waiting for device> , doesn't go further, I have everything installed sdk, usb drivers and usb debugging activated. Maybe there's some problem with key combination, to get in fastboot. From google I understood, that I have to turn phone off, then press and hold camera + press power button! I did other combinations too, but didnt work.
Just waiting for device..
Any ideas? I read, that if you're in fastboot there's just a black screen, and on pc desktop appears fastboot usb. I have non of that.
Thanks for help in advance.

ejnahuj said:
Hi guys, I recantly decided to update my gt540 from 2.1 to 2.3.3
I followed steps by steps on by this tutorial - http://fdapps.comuf.com/downloads/The LG GT540 Optimus reference page.pdf
Installed rom with fastboot, tried to install Clockwork with fastboot, I typed fastboot flash recovery C:\recovery.img , and then there's <waiting for device> , doesn't go further, I have everything installed sdk, usb drivers and usb debugging activated. Maybe there's some problem with key combination, to get in fastboot. From google I understood, that I have to turn phone off, then press and hold camera + press power button! I did other combinations too, but didnt work.
Just waiting for device..
Any ideas? I read, that if you're in fastboot there's just a black screen, and on pc desktop appears fastboot usb. I have non of that.
Thanks for help in advance.
Click to expand...
Click to collapse
Hello
1. you need to install a ROM with fastboot the most common is europe + fastboot (KDZ) ROM.
http://www.mediafire.com/?96nu9lb6afx22a7
2. once its finished phone will reboot, then fast login into fastboot mode CAMERA + POWER
3. You are missin 1 thing, OEM usb drivers not GOOGLE usb drivers as some tutorial says, those are just for Android Developer Phones (ADP), Nexus One, and Nexus S.
LG_Android_USB_Driver_Rebuilt
http://www.mediafire.com/?pbigrb8cimmxa4d
* these drivers are for your pc to recognize your phone in fastboot mode, they are not the normal LG usb drivers
4. for install the drivers abouve follow these smll tutorials
* if using windows 7:
http://developer.android.com/sdk/win-usb.html#Win7
* if using windows XP:
http://developer.android.com/sdk/win-usb.html#WinXp
once is installed plug your phone in fastboot mode to your pc, now your pc has to recognize your phone wait until it finish installing the drivers and read it properly
5. unzip the new ROM files into C:\*SDK\tools
6. open CMD Terminal and go to C:\*SDK\tools, type:
cd C:\*SDK\tools
7. once in, type
fastboot flash recovery recovery_clockwork_3.x.x.x_swift.img"
fastboot -w
fastboot erase system
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
*Just in case it drops you an error AdbWinApi.dll missing here is the file. place it in C:\*SDK\tools and try again
http://www.mediafire.com/?3s3z5uym2rw5r7u
Any other question PM me

fastboot "waiting for device"
I have installed all the drivers and everything is working fine except fastboot. I have "nexus s" with me. The problem is:
I do "adb reboot bootloader" to flash the images, but after that if I do "fastboot devices", it doesnot show my device and if I do "fastboot flash ..", it just displays "waiting for device".
Can any one please help, I need it urgently..
THanks in advance

murthy.krishna00 said:
I have installed all the drivers and everything is working fine except fastboot. I have "nexus s" with me. The problem is:
I do "adb reboot bootloader" to flash the images, but after that if I do "fastboot devices", it doesnot show my device and if I do "fastboot flash ..", it just displays "waiting for device".
Can any one please help, I need it urgently..
THanks in advance
Click to expand...
Click to collapse
You need to turn phone off and hold down camera whilst pressing power.
Sent from my GT540 using XDA App

Quinny899 said:
You need to turn phone off and hold down camera whilst pressing power.
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
Can you please clearly explain it, I couldnt get that. The prob was even though I installed the diver fastboot cannot detect the device..

Turn the phone off normally and when you'from holding down power to turn it on, also hold down camera until you get a black screen.
Sent from my GT540 using XDA App

New computer Maybe driver help??!?!

I got a new Razer Blade 14 laptop. For some reason I cannot get the phone to enter download mode properly. It just says disabled and "Connect USB Data Cable".
I've installed the drivers and ADB software. I Have no missing devices in device manager. When booted into the OS and in MTP mode I can send adb commands and "adb devices" sees the phone. Its only when I boot into download mode that the phone says its disabled and to connect a data cable. So theres something up with the Fastboot/Download mode drivers is my guess. I just cant put a finger on the problem.
In device manager it shows as "Android Bootloader Interface" as the device. I'm using the stock nexus 6p cable. My usb drivers are up to date per intel. Computer has windows 10.
Please help!!!

If i put it in sideload mode it is also detected with ADB. Just not fastboot/download mode...

I managed to somehow fix it. I had the right drivers. But for some reason I left the phone in download mode. Then issued the command "fastboot oem ramdump enable" and then restarted the bootloader, now download mode is enabled and I can flash factory images etc.

Windows 10 laptop can't detect softbricked Nexus 4, TWRP, no OS

I've checked other threads but other similar threads were able to get the phone detected in Device Manager so...
I went to factory reset my old Nexus 4 after using it whilst my LG G4 was being repaired. Instead of wiping the data, I accidentally wiped the entire phone, OS included. I wasn't paying attention to what i was doing due to working at the same time and as a result the phone now only boots into TWRP and fastboot mode, but nothing else.
I tried to connect it to my windows 10 laptop so I could flash a new ROM but my laptop can't find the nexus 4 at all. Not when in recovery or when in fastboot.
Opening device manager shows that it is not there at all. There is no ACER usb device driver, nothing that resembles the nexus 4 at all. I've attached an image showing what device manager shows when the nexus 4 is connected and in recovery mode.
As you can see, there are no drivers I can uninstall. I have installed the google USB drivers from Android SDK manager. Still doesn't show. ADB doesn't work either.
I have tried multiple USB cables and every USB port. The phone charges when using an AC adaptor and charges when connected to the laptop. I can't try a different computer because I do not have access to one. Frankly I'm at a loss as to what to do.
When my nexus 4 was previously unable to connect I was able to see the device and just had to uninstall/reinstall/update drivers to get it working. This time, I can't seem to do anything. My LG G4 connects fine and without issue.
Anyone able to help?

The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.

I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.

first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/

For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.

i_need_some_help said:
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
Click to expand...
Click to collapse
Thanks, I will give this a try!

elad.g said:
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
Click to expand...
Click to collapse
I tried removing all USB drivers and then using the toolkit and tried installing each driver. None of them allowed my PC to detect the nexus 4. As you can see in the attachment, nothing in device manager remotely resembling my nexus 4. This is after uninstalling and reinstalling and also updateing the LG G4 drivers (it makes no difference).
i_need_some_help said:
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
Click to expand...
Click to collapse
Alas, this did not work.
audit13 said:
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
Click to expand...
Click to collapse
Unfortunately I don't have access to any other PC for this purpose. I can't connect download software or connect USB devices to the PCs at work due to security. I tried an OTG drive but TWRP wouldn't let me mount it, apparently OTG is not enabled by default for the nexus 4.
I've tried all 3 USB ports, several different cables but no luck. I guess that's it for this nexus 4 then?

If the phone is not booted into its ROM, ADB commands won't work. You need to use "fastboot devices" with the phone in bootloader mode.

You android device will reboot in several different boot modes (fastboot, recovery, normal). For each of these boot modes a separate device drive might be installed on your Windows. So check the device drive after each change of boot mode. If needed uninstall and reinstall the correct device driver.

LG Leon H340N fastboot not working

Hello!
I have a very big problem. My LG Leon H340N is "bricked" totally, there is only fastboot mode in phone, nothing else.
The problem is that fastboot is not working, when i try to execute some commands it all the time gives me answer: FAILED(Unknow Command) and i don't know how to fix this, i don't have access to download mode, i don't have access to hard reset menu, i don't have access to recovery mode, only fastboot
Could somebody help me ?

How did you get into fastboot mode?

I connect device and laptop via USB and device is starting into fastboot mode automatically.
When device is connected i open cmd (run as administrator) and C:\ cd adb = C:\adb> fastboot devices - and it shows me my device connected as fastboot device then I try to execute some commands but it always gives FAILED(UnknowCommand). The fastboot drivers are installed - original google drivers from android sdk. I'm using Windows 7 Home Premium, i try execute some commands on other laptop with windows 7 starter but the same thing - FAILED(Unknow Command).
Thank you for reply, Regards

Flash the version MS34510d_00

I don't have MetroPCS version it's h340n. And i can't flash anything, because fastboot is not working

Install android 5

Dude, i know, i want to install android 5 but you don't see that fastboot in my phone IS NOT WORKING ? every time, when i try to exec some commands it gives me: FAILED(UnknowCommand)

for mode download

Phone stuck without os and can't access to fastboot or adb

guys I'm in a bad situation, phone is without OS and I can only access to recovery or bootloader, I have a twrp installed and I can't access to an USB otg (simple usb doesn't even blink like they are not working, If I connect an hdd it doesn't recognize it but gives it power) and I can't access to the phone as MTP or with adb devices or adb sideload. Even on bootloader mode device isn't showed when I try the command "fastboot devices" and it says "download mode = DISABLED".
so I only have access to twrp with those limitations, I need a big help, phone is with BTL unlocked and with expired warranty.
thanks in advance

parodiniccolo said:
guys I'm in a bad situation, phone is without OS and I can only access to recovery or bootloader, I have a twrp installed and I can't access to an USB otg (simple usb doesn't even blink like they are not working, If I connect an hdd it doesn't recognize it but gives it power) and I can't access to the phone as MTP or with adb devices or adb sideload. Even on bootloader mode device isn't showed when I try the command "fastboot devices" and it says "download mode = DISABLED".so I only have access to twrp with those limitations, I need a big help, phone is with BTL unlocked and with expired warranty.
thanks in advance
Click to expand...
Click to collapse
Download mode=disabled is the default (normal) displayed in bootloader mode. You seem to infer that is what fastboot returned when you typed devices? MTP works in TWRP automatically when it loads. Sounds like you may have a PC driver/cable issue. When you plug the device into your PC, how is it recognized?

v12xke said:
Download mode=disabled is the default (normal) displayed in bootloader mode. You seem to infer that is what fastboot returned when you typed devices? MTP works in TWRP automatically when it loads. Sounds like you may have a PC driver/cable issue. When you plug the device into your PC, how is it recognized?
Click to expand...
Click to collapse
I'm on mac so I don't have any driver issues and other phones works fine with mtp in TWRP

Up please

parodiniccolo said:
I'm on mac so I don't have any driver issues and other phones works fine with mtp in TWRP
Click to expand...
Click to collapse
You are using OSX, right? Fastboot commands should start with ./ before each command. For example: ./fastboot devices, or ./fastboot flash, or ./fastboot reboot bootloader. Same applies for adb commands. If you are already familiar with flashing images, read my post below about OSX and fastboot.
Do not click into the thread because it is for the Nexus 5X new users guide.
Edit: Whoops! Initially shared the wrong link above. Follow this link instead:
https://forum.xda-developers.com/showpost.php?p=68758793&postcount=3
Sent from my Nexus 5X using Tapatalk