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
Hi guys, im already hopeless but i'm here to beg for your experience.
I got a G2 D805, the screen broke, then i replaced with a new one. But, when it powered on gave the message that it was going to turn off. The battery icon was with an X.
Soooo... i thought, ok the battery is gone. Bought another one. Nope, it wasnt the battery.
Then I tried the "factory reset". As soon as it starts, it restarts, loads the welcome screen(where you first customize the phone), 1 second and it gives the power off message.
Tried the recovery mode. Same.
Download mode? Ok, i read something about the kdz recovery. The LG Flash Tool cant see the phone. Neither the pc. Doesnt make a sound when i connect it on download mode.
Then tried the "fastboot mode" thingy where you press something against a single chip part inside the phone until it makes fastboot avaiable. On fastboot, thought it was finally going to work. The device even appeared on the pc. Tried those below with drivers from: "universal adb drivers", "pdanet", "android sdk", even some "15 adb install" drivers. No results.
I typed "fastboot devices" = ? fastboot
I typed "fastboot erase recovery" = failure sending erase group start command to the card (on pc remote: failed to erase partition)
I typed "fastboot continue" = failure sending read command to the card AND failure setting read block count for card AND cannot read boot image header
"adb devices" = list of devices attached (nothing, just that)
Im close to losing my mind here. Any help is appreciated.
Thanks for your time.
Hello all,
Just a heads up that I have little to no knowledge of modding/rooting phones whatsoever.
My phone decided to reboot by itself earlier today and was stuck in a boot loop for around 30 minutes before I managed to get into recovery mode. At this point it is still boot looping. Afterwards it just stop the boot loop and now stuck on recovery mode. Powering it off from recovery mode or by holding power button for 10s will only results in the phone rebooting itself into recovery mode again. I can get into Fastboot mode, however. Wiping cache and rebooting does not seem to do the trick as it would only go back to recovery screen after the OnePlus logo again.
Please advise on this matter
install drivers. connect to fastboot. Type "fastboot continue", this should turn on your phone but it's a temporary fix. Once it's on copy your data & perform a factory reset. - found it on oneplus forums (haven't tested by me)
Sent from my ONE A2001 using XDA-Developers mobile app
B!Gguy said:
install drivers. connect to fastboot. Type "fastboot continue", this should turn on your phone but it's a temporary fix. Once it's on copy your data & perform a factory reset. - found it on oneplus forums (haven't tested by me)
Click to expand...
Click to collapse
Thanks for your reply, where exactly do i type "fastboot continue" ?
> First you need to install ADB & Fastboot to your Computer (Use This guide)
> Then Install Oneplus 2 Drivers (Use This Guide)
> Connect phone via Fastboot mode (Turn off the phone. Hold Volume Up + Power to enter fastboot mode. Connect phone to pc)
On the first guide (ADB & Fastboot) you'll find how to open a Command Window to issue fastboot commands. That's where you need to type "fastboot continue"
Let me know if this post belongs somewhere else.
My Mi A1 is stuck in a bootloop as a result of trying to install magisk 14.4. At the moment I can boot it into fastboot mode, but not into recovery mode. In fastboot I can execute the command
fastboot devices
that returns the hex number followed by "fastboot." However, it does not respond to any other fastboot commands, e.g.
fastboot reboot
fastboot oem device-info
I have been attempting to flash the stock rom without success as follows:
in win10 32-bit environment:
fastboot responds as above. I cannot install the MiFlash-2017-7-20 version. Windows complains. I conclude that version must be a w10 64-bit app, although it doesn't say so.
win10 64-bit
MiFlash-2017-7-20 installs and runs, but does not see the device. Apparently, the adb drivers are at fault. I have turned off signature enforcement and tried installing various versions of the adb drivers. The device manager shows them as installed, but reports that they cannot start.
Centos 7 linux
Adb drivers install. "Fastboot devices" reports correctly. All other fastboot commands fail, i.e. they hang. I tried installing the tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image using the linux shell script provided, but that just hung also.
Is this phone well and truly bricked at this point? Is there any other recovery available?
I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.
Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works
GalihBK said:
Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works
Click to expand...
Click to collapse
As he said, he can't execute fastboot commands so that isn't a option.
@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.
The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps
Edwin Hamal said:
I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.
Click to expand...
Click to collapse
1. I tried this method to boot into EDL with no luck. Is there any other way?
C:\Downloads\xiaomi mi a1 root>adb reboot edl
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
2. On my win10 32-bit installation I am able to run MiFlash-2017045. It reports the device. I attempted to flash this image:
tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794
It completed and reported "success" however it did so in only 7 seconds, so it must not actually have succeeded. In any case the phone still will not boot.
3. However, I distrust MiFlash 20170425 because it comes from an androidmtk.com site and the processor is Qualcomm, not Mediatek. So I attempted to install MiFlash2017-07-20. However, that program will not install on my win10 32-bit installation. There is a Windows msg saying it cannot be installed, but does not give a reason. I suspect it is a 64-bit program. So, I installed MiFlash2017-7-20 in a win 10 64-bit installation. The program does run, but it does not see the device. I suspect that the adb drivers do not install correctly. I did turn off signature enforcement and the drivers appear to install, but the device manager reports that the drive cannot start.
The tissot images include bourne shell scripts to install, so I installed the adb drivers on my Centos box. Fastboot reports the device, but just as in win10 no other fastboot commands work. So, even though I did try to execute the install_all.sh script, it just hung on the first "fastboot getvar product" command.
So, I do not have a way to flash the stock rom.
_mysiak_ said:
@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well
Click to expand...
Click to collapse
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.
dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Use fastboot commands manually. Mi flash tool is very buggy. Many time it doesn't work.
_mysiak_ said:
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.
Click to expand...
Click to collapse
Did the command:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
"Missmatching image and device"
So this is a little interesting. However, I don't think that the image is actually the wrong one, but that the script cannot get the device info since both "fastboot getvar product" and "fastboot oem device-info" fail on a timeout.
zazzy24 said:
The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps
Click to expand...
Click to collapse
When I do that it just keeps going back to the "no command" screen. I think the recovery image is either damaged or gone.
yuoip said:
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.
Click to expand...
Click to collapse
1. & 2. It sounds like you don't have installed fastboot drivers (install them manually via device manager) or phone isn't connected in fastboot mode (make sure there is a picture with fastboot written on the phone).
3. this IS the recovery mode, just press power + volume up again to show the menu
4. you won't see ADB devices in fastboot or recovery mode, unless you enable ADB sideload from recovery
Device Manager shows:
Android Phone
yuoip said:
Device Manager shows:
Android Phone
Click to expand...
Click to collapse
Wrong drivers then, it should say Android bootloader interface. Reinstall them correctly.
1. I did the manual install, but I don't see anything labeled "fastboot driver."
Device manager now reports:
Android Phone
Android ADB Interface
Android Bootloader Interface
Android Bootloader Interface
Android Composite ADB Interface
However, all these entries have a warning symbol on them. The Device status for each is:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Is one of these the fastboot driver? Apparently not, since the behavior of the fastboot command hasn't changed.
When I try using the fastboot command the A1 shows "Fastboot" with the rabbit character and the sick robot.
I should mention that in the Centos environment I have installed the android-tools package, which include adb and fastboot drivers and tools. The behavior of the fastboot command there is the same.
So, this leads me to believe that the problem is the A1, not the windows or linux environment, but I don't know enough to know for sure. Also, I would assume that if the fastboot drivers were not installed, the command "fastboot devices" would fail, but it doesn't.
3. At the "no command screen" if I do press and hold the power button and then the vol. up button it boots right back into the "no command" screen. There is no menu.
4. With no recovery menu I can't set any options.
Uninstall/remove everything with android name in it, disconnect phone, reconnect phone in fastboot mode. Make sure that there is only one item under Android Phone - Android Bootloader Interface. You should not see 4 devices - do you have Android emulator running or anything else connected?
When in recovery, do not hold power + volume up, just press it briefly. Sometimes it takes few tries to show the menu, but I can assure you that it's there.
Yes! You're right. The recovery menu is indeed there. I didn't know that it had to be a short press to bring it up. Thanks.
Device manager now shows only one "Android Bootloader Interface" entry. I am not running any emulator.
So now what do I do? Do I need to flash the tissot... image? The fastboot command still behaves as before.
Quick Google search suggests to avoid using USB 3.0 ports. So..maybe try another ports on your PC..?