How to fix LG540GT - GT540 Optimus General

I have flashed a new rom on my lg540gt and after that the android logo stays forever.
When I tryed to reflash another rom,the LG logo stays.
Tryed to go to fastboot but the phone will not comunnicate with the computer.
Thx for any help

restart you pc and try fastboot again

Tryed but it didn't work,I have tryed it on another PC and without success

darac32 said:
I have flashed a new rom on my lg540gt and after that the android logo stays forever.
When I tryed to reflash another rom,the LG logo stays.
Tryed to go to fastboot but the phone will not comunnicate with the computer.
Thx for any help
Click to expand...
Click to collapse
bro this question was answered heaps of times..
search before posting..
Also this is supposed to be in the general section not
development..
Anyways go into clockworkmod if you can't connect to
pc and wipe everything and reflash with Recovery.

there was a post of how to make fastboot recognizr your device
but i forgot because fastboot works fine on linux
maybe if you find

cccb010 said:
there was a post of how to make fastboot recognizr your device
but i forgot because fastboot works fine on linux
maybe if you find
Click to expand...
Click to collapse
yeah i think i saw it as well..
forgot though..
Try the recovery, i had this problem as well!!
uninstall all drivers and reinstall them..
After that go to fastboot and type
fastboot -w
fastboot reboot

Press Power+Volume key to access download mode. Computer will now recognize your GT540.
Reflash .kdz
*fastboot enabled
After that is done, when phone automatically reboot, press Power+Camera till phone stays on black screen.
Open up CMD and run with administrator's rights>*make sure USB is connected
Type in;
cd c:/<location>
Fastboot -w
No more boot loops afterwards

MrAndroid12 said:
Press Power+Volume key to access download mode. Computer will now recognize your GT540.
Reflash .kdz
*fastboot enabled
After that is done, when phone automatically reboot, press Power+Camera till phone stays on black screen.
Open up CMD and run with administrator's rights>*make sure USB is connected
Type in;
cd c:/<location>
Fastboot -w
No more boot loops afterwards
Click to expand...
Click to collapse
I have made this,but the phone gives me a blue screen with "fastboot" ...
Tryed to reflash with original,and fastboot rom but the effect is the same ...
and i have the fasboot in command prompt ...
I can not get to recovery ...
I have win ,and on another xp ...
thx for any help

flash another recovery via fastboot

darac32 said:
I have made this,but the phone gives me a blue screen with "fastboot" ...
Tryed to reflash with original,and fastboot rom but the effect is the same ...
and i have the fasboot in command prompt ...
I can not get to recovery ...
I have win ,and on another xp ...
thx for any help
Click to expand...
Click to collapse
Hold the HOME button along with the POWER button while turning on your phone. You should encounter recovery at some point. If not, flash a recovery rom by typing:
Code:
fastboot flash recovery <image_name>
Replace <image_name>, with the recovery image and remove the brackets.
So for example:
Code:
fastboot flash recovery recovery.img

jhonnyx1000 said:
Hold the HOME button along with the POWER button while turning on your phone. You should encounter recovery at some point. If not, flash a recovery rom by typing:
Code:
fastboot flash recovery <image_name>
Replace <image_name>, with the recovery image and remove the brackets.
So for example:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
THe command prompt says <waiting for device> and stands here
btw. the screen is blue when i press home +power or camera + power and it says
"Display initialized
USB init ept @ 0x6b000
fatstboot_init()
udc_start() "

darac32 said:
THe command prompt says <waiting for device> and stands here
btw. the screen is blue when i press home +power or camera + power and it says
"Display initialized
USB init ept @ 0x6b000
fatstboot_init()
udc_start() "
Click to expand...
Click to collapse
The 'display initialize' thing is a part of fastboot. Do the commands when you're in fastboot.
Sent from my GT540 using XDA App

er dudes remember that the blue screen and white text is only there if you use mur4ik's bootloaders and not the one you get from the kdz

If you have blue screen its not dead
sudo ./fastboot -w
sudo ./fastboot flash boot boot.img
sudo ./fastboot flash system system.img
sudo ./fastboot flash recovery recovery.img
Maybe its your adb server cant remember the exact command but its something like
sudo ./adb kill-server
sudo ./adb server
Or something along those lines look it up on google its the command to restart the adb server if you use more than one device or do alot of work with adb sometimes it will show it cant connect to the phone when really it can it just needs to be rest because something has screwed up on the system and or phone.
Hope this helps and good luck if you still have problems give us a few more details and what happend where but your gt540 is nowhere near broke trust me.
Sent from my tf101 using xda premium 1.54Ghz

Danzano said:
If you have blue screen its not dead
sudo ./fastboot -w
sudo ./fastboot flash boot boot.img
sudo ./fastboot flash system system.img
sudo ./fastboot flash recovery recovery.img
Maybe its your adb server cant remember the exact command but its something like
sudo ./adb kill-server
sudo ./adb server
Or something along those lines look it up on google its the command to restart the adb server if you use more than one device or do alot of work with adb sometimes it will show it cant connect to the phone when really it can it just needs to be rest because something has screwed up on the system and or phone.
Hope this helps and good luck if you still have problems give us a few more details and what happend where but your gt540 is nowhere near broke trust me.
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
You think that I should reinstal the adb server (or the complete adb with sdk)
Killed the server,and startet it again,but with no response from phone ...
I have reflashed the phone with V20D,and now it stucks on android logo ...
The fastboot is still not working

darac32 said:
You think that I should reinstal the adb server (or the complete adb with sdk)
Killed the server,and startet it again,but with no response from phone ...
I have reflashed the phone with V20D,and now it stucks on android logo ...
The fastboot is still not working
Click to expand...
Click to collapse
reinstall LG drivers or whatever drivers needed for our phone and try fastboot again .

Fast boot drivers are missing from your computer, Vernica's pinned post with lots of guides will point you in the correct direction.
Sent from my GT-I9100 using XDA Premium

airbus360 said:
Fast boot drivers are missing from your computer, Vernica's pinned post with lots of guides will point you in the correct direction.
Sent from my GT-I9100 using XDA Premium
Click to expand...
Click to collapse
From what you just said airbus is right
do you use windows or linux because windows uses drivers but linux you will have to set rules for the phone
Sent from my tf101 using xda premium 1.54Ghz

Danzano said:
From what you just said airbus is right
do you use windows or linux because windows uses drivers but linux you will have to set rules for the phone
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
I use Windows 7,but windows xp is no problem

mircea89fzr said:
reinstall LG drivers or whatever drivers needed for our phone and try fastboot again .
Click to expand...
Click to collapse
Tryed that but no response from phone,that is what makes my troubles ...
Everything rechecked twice ... but maybe somthing I miss but I don't think I did

Related

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

Um...Fastboot??

I know this is a very silly question....but um.... how to install via fastboot??
I know how to install with recovery, but im curious about fastboot as well
Plz help!!
Use adb open Cmd.exe with admin right then enter the codes
Sent from my GT540 using XDA App
I never used ADB
This is what I do:
Put files in e.g C:\Android
restart into fastboot Camera button+Power button
Plug in USB (check u have installed fastboot driver)
Start->run->cmd->write
cd c:\android
fastboot -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
yozolios said:
I know this is a very silly question....but um.... how to install via fastboot??
I know how to install with recovery, but im curious about fastboot as well
Plz help!!
Click to expand...
Click to collapse
There is a video about it gere in general threads if its not in page 1 then look in page 2
Veronica
Sent from my GT540 using XDA App
EDIT: here is the thread: http://forum.xda-developers.com/showthread.php?t=1105912
thanks peoples i will try it when i get home....

i deleted my os

hi...
i unlocking bootloader
and i want to install factory image
but first i open recovery and i deleted every thing format system and every thing becase i want clean -_-"
so .. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot
i Didn't have this problem with my other N4
please help me -_-"
Only fastboot works when in bootloader, adb needs a custom recovery or android to work. Use fastboot to flash the images (run the install all bat file).
Marvlesz said:
Only fastboot works when in bootloader, adb needs a custom recovery or android to work. Use fastboot to flash the images (run the install all bat file).
Click to expand...
Click to collapse
i used fastboot
but it still waiting device
when i plug another n4 its work
box_zzz said:
i used fastboot
but it still waiting device
when i plug another n4 its work
Click to expand...
Click to collapse
uppppppppppppppppppppp
Connect your device to the PC in fastboot mode and type "fastboot devices". Do you get an output?
Remember that you have to run the command line from the folder where your fastboot.exe resides.
Sent from my Nexus 4 using XDA Free mobile app
box_zzz said:
hi...
i unlocking bootloader
and i want to install factory image
but first i open recovery and i deleted every thing format system and every thing becase i want clean -_-"
so .. when I plug the phone into my computer while in fastboot and try any adb commands.. I get nothing... It seems like the adb drivers aren't loading while in fastboot
i Didn't have this problem with my other N4
please help me -_-"
Click to expand...
Click to collapse
It happened to me once upon time, I've deleted EVERYTHING, only adb fastboot was working for me, so i connected my phone to my laptop and pushed system.img by wugfresh toolkit.. Try this way.. I hope it will resolve your problem.
Sent from my Nexus 4 using XDA Free mobile app

Nexus do not want to be recognized by pc

Hi everybody, 2 months ago I tried to encrypt my nexus using the security settings. When my n4 rebooted the touch stopped working. I couldn't use the recovery becouse the data partition was encrypted, so I used this tutorial (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060) to reset my phone. Now windows (neither ubuntu) do not recognize the n4. I tried to follow any kind of guide or tutorial i found but uselessly. I'm desperate, the recovery doesn't work, if i try ,it stop on android logo saying "no command". Entering in windows device manager (after i formatted my pc) the nexus is seen as "full jellybean on mako", i tested this driver (http://forum.xda-developers.com/nexus-4/help/phone-detected-jellybean-mako-install-t2411201) but the situation has not changed. I hope someone can help me.
Does your phone boot?
BTW, if you need only driver download from this thread: http://forum.xda-developers.com/nexus-4/general/drivers-nexus-4-driver-windows-t1992345
PsyGik said:
Does your phone boot?
BTW, if you need only driver download from this thread: http://forum.xda-developers.com/nexus-4/general/drivers-nexus-4-driver-windows-t1992345
Click to expand...
Click to collapse
It works perfectly, but I can't copy files on or change rom (now is running stock android 4.2)
werba59 said:
It works perfectly, but I can't copy files on or change rom (now is running stock android 4.2)
Click to expand...
Click to collapse
Boot into bootloader and flash stock rom from here :https://developers.google.com/android/nexus/images
BTW, did you enable developer options?
Sorry, I misread your answer. "It works perfectly" means that i can use it to call or whatever. Using the key combo (vol up+vol dw+power) it doesn't boot in download mode. I think it isn't a driver problem, something in my n4 went wrong. It boot only in fastboot mode and the recovery doesn't work.
werba59 said:
Sorry, I misread your answer. "It works perfectly" means that i can use it to call or whatever. Using the key combo (vol up+vol dw+power) it doesn't boot in download mode. I think it isn't a driver problem, something in my n4 went wrong. It boot only in fastboot mode and the recovery doesn't work.
Click to expand...
Click to collapse
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
Then open the downloaded image from here https://developers.google.com/android/nexus/images and Execute the flash-all script. This script installs the necessary bootloader, firmware,and system. Wait for a couple of minutes and then phone will reboot itself. After phone boots enable developer options in the phone and enable USB debugging.
If you are still not able to mount the storage in Ubuntu, you can install the mtpfs tool for Ubuntu.
Code:
sudo apt-get install mtp-tools mtpfs
sudo gedit /etc/udev/rules.d/51-android.rules
and in the 51-android.rules write the following:
Code:
#LG – Nexus 4
SUBSYSTEM==”usb”, ATTR{idVendor}==”1004?, MODE=”0666?
Then do:
Code:
sudo chmod +x /etc/udev/rules.d/51-android.rules
sudo service udev restart
sudo mkdir /media/nexus4
chmod 755 /media/nexus4
sudo mtpfs -o allow_other /media/nexus4
This should get it working. This thread tells everything in much more detail if you still didn't get it to work.
http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
PsyGik said:
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
My PC do not recognise my phone when it boots into fastboot mode, that's the problem, any pc and any kind of so i tested do not recognise my n4.
Click to expand...
Click to collapse
werba59 said:
PsyGik said:
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
My PC do not recognise my phone when it boots into fastboot mode, that's the problem, any pc and any kind of so i tested do not recognise my n4.
Click to expand...
Click to collapse
If no pc will recognize it it's probably your pc port on the device. Have you tried different cables too? It's pretty easy to replace or have replaced.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Seems like something going wrong with drivers, open the device manager on windows, plug in your phone (in fastboot) and uninstall the driver. Then use this http://www.koushikdutta.com/post/universal-adb-driver
Dunno what that full JB driver is about but it doesn't seem right.
You might have to repeat this process when phone is booted normally too if it won't connect via MTP
Hi, just get here after look in several forums.
my laptop can't recognize my n4, also tried in other two computers. i already updated the drivers, used a toolkit. what should i do next? the phone works good, just can't connect it to any pc. "USB device is not recognized"
as i said, already updated the drivers.
Anything else i can do?

[SOLVED] Z1 not showing up in Linux ADB devices

hi,
trying to flash the breadcrust recovery using my linux pc, but the Z1 doesn't appear in the list of devices when running adb devices. Image attached. Normally I would get a request to accept the RSA key for a trusted pc when enabling usb debug. But I don't get this option.
- Adb tools are loaded and working on my linux laptop
- My nexus 7 responds to ADB devices and shows up ok
- tried on wifes windows laptop with adb/sdk tools loaded and no joy there too
- i have developer USB debug options enabled, i've tripple checked this
could it be the cable? I'm using the one which came with the phone, so that should be ok?!!
cheers
SOLUTION - I ran this One Plus Two script modified with the Z1 device ID and now I can see my device in adb devices and interact with it. I get the SHA screen to allow access and can run commands from linux terminal. YAY!
See the attachments for script.
I think it´s a driver fault. Did u install them in windows?
im using linux, i dont get any rsa pop up confirmation either!
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
and that was the reason, why i installed windows last night. as long you dont get rsa pop up, the device will not listed (i think so)
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
But u said, that u tried ur wifes Windows notebook. Did u install the drivers there?
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
MKKLR21 said:
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
Click to expand...
Click to collapse
Good tip - I'll give it a go.
My nexus 7 works as expected on all PCs and laptops Linux/windows so it must be the phone
Sent from my Nexus 7 using Tapatalk
Maybe sudo or check this:
http://1.bp.blogspot.com/-rDdBnJTh870/U-hxVzxMf3I/AAAAAAAAKwQ/WrZkaMjaReo/s1600/Unlock-Bootloader-linux-terminal-xperia-z.png[img/]
Source: [url]http://linuxwelt.blogspot.de/2014/08/cyanogenmod-unter-linux-installieren.html[/url]
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader, but the device doesn't boot into fastboot, just reboots as normal!
I could also hold down up/down volume buttons and get into the bootloader, but again the device isn't picked by any fastboot oem checks for unlocking!!
arrrgh!!!
You'll have to add -i switch followed by the device ID to your fastboot command. I don't have it at hand, so just read the TWRP thread.
ok! Some progress...ish.
running "adb reboot bootloader"command in windows worked when I switched Cyanogen recovery updates off in developer options. The Z1 reboots into bootloader.
Running "fastboot -i 0x2b4c oem get-device-info" returns nothing just "....."
So I tried "fastboot -i 0x2b4c oem unlock" an error returns cannot unlock use command "fastboot -i 0x2b4c oem unlock-go" which works. The phone wipes data and reboots back into OS.
I re-enable the developer options and adb debug. and reboot into bootloader
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
weird!
Your commands are simply wrong, thats why they don´t work.
It is:
fastboot -i 0x2b4c oem device-info
fastboot -i 0x2b4c oem unlock-go
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
Click to expand...
Click to collapse
Flashing does NOT work on the international version, you have to boot into it directly from fastboot.
fastboot -i 0x2b4c boot z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img
Should be correct instead of the flash command.
EggZenBeanz said:
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader...
...
Click to expand...
Click to collapse
What made the change? I was able to see the RSA screen only once, but after device restored to defaults I can't get it back. same drivers installed, and it appears in the device manager.
I honestly don't know, it just worked after many attempts. I read somewhere about USB 3 ports with Linux so might be the same for windows?
Sent from my Z1 using Tapatalk
It's an USB 3.0 issue. Plug the phone into an USB 2.0 port, or an USB 2.0 hub plugged into an USB 3.0 port and it will magically start working. God knows why this is the case...
Ironically, fastboot works fine even on USB 3.0...
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Planet X said:
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Click to expand...
Click to collapse
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
MrColdbird said:
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
Click to expand...
Click to collapse
Okay, I have found out that it is impossible to boot from TWRP as log as the bootloader is locked. It just took me 2 hours to setup my phone again after unlock.
Have a look at this thread, I am going to give it a try later.
http://forum.xda-developers.com/showthread.php?t=2408802
This did the trick on Linux (Ubuntu):
- run on terminal "sudo gedit ~/.android/adb_usb.ini"
- put "0x2b4c" in
- run on terminal "adb kill-server" and "adb start-server"
And run the fastboot commands with "sudo".

Categories

Resources