[Q] Not coming on! Please Help - G2 Q&A, Help & Troubleshooting

I had rooted my G2, then had some issues... did the LGFlash Tool to go back to stock and now my phone won't come on. I've had it plugged to the wall charger for about an hour and it won't come on.... no download mode either.
Is there anyway to fix it or am I screwed?

Did u try using the pdanet? I was exactly in the same situation as u are. No matter if the lg drivers are installed.... The pc won't recognize the phone as ADB.EXE had stopped working. Here is what I did:
1) install pdanet.
2) it asked me to select the device and then it installed the drivers.
4) with this hopefully the ADB.EXE should start in your device manager. In my case it did.
5) go to google adb bundle folder.
6) go to SDK>platform tools> and paste your CM and gapps there.
7) try bridging the connection by going into the command prompt > and CD into the platform tools directory.
8) in the cmd put the command 'amd push "CM NAME" /sdcard/' and hit enter
9) this should push the file onto the phone... Do the same for gapps... And install it from the TWRP.
10) ALL THE BEST
Sent from my LG-D802 using Tapatalk

I just tried and it came to "Skip USB" or "Cancel Installation". My phone is off and won't turn on at all. Plugged it in the wall for over an hour, tried download mode, tried recovery, tried USB... nothing.

Related

[Q] Help in installing adb drivers

My vibrant is stuck on the vibrant logo after I tried to use the one click unroot program. The only solution I found after two days searching on the net, is to use odin. The first problem is that my phone is locked, so I can't use the vol up+down+power button combo to get into recovery or download mode.
Now comes the issue, I want to use adb to reboot the phone, but adb can't see my device. After installing the samsung USB Drivers, I see that the adb drivers are not installed (The drivers for this device are not installed. (Code 28)), and even when I try to manually install them from the SDK drivers (I checked the "include subfolders) it says that it can't find them.
I have windows 7 x64
Anyone have suggestions to how to install the adb drivers and make the adb see my device?
Can you get into download mode? Have you tried to Odin back to stock? If you want to set up ADB type ADB for dummies in search and you should find everything you need.
Here is the link from the sticky thread for help with drivers:
http://forum.xda-developers.com/showthread.php?t=728929
I just figured out a neat trick to get phone to work even if it's stuck on the vibrant screen.
Just connect it to the usb, wait until the grey battery picture appears.
After 5 seconds, take the battery out and put it right back, (leave usb in) and wait again. Do it once more, until you see that the battery picture turns green. After that take the battery out and unplug the usb, and turn the phone on.
It should work now.
The thing is that, next time you turn the phone off and on, it would be stuck again, so do something to fix it like odin.
That how it worked for me.
And about the adb driver problem, I just pointed manually the driver update to the "USB Drivers" that TGA_Gunnman posted here (I can't post link. just search usb drivers here in the forum) and after that adb worked like a charm, rebooted instantly to download mode - it's crucial for those like me that have hardware locked phones.
The thing is, that all the other posts say to point it to the sdk drivers, but that dosen't work.
Good luck to all others.
installing the samsung drivers and installing adb are two different things. the samsung drivers should install normal by double clicking the driver package (you may have to still tell windows where to look). installing adb is simply downloading the sdk, however, if you want adb to work everywhere (instead of just the sdk/tools folder) you need to put the sdk/tools folder in your path.
then 'adb devices' should show your device in win powershell, but will only work if you are in the sdk/tools folder or have added it to your environment variables.

haveing problem for installing 3button download mode to use ODIN3

hello gyes!
i'm in great jeopardy...............
spent 2 days searching-> only 1 thing & its-> how to install a 3 button download mode on my sgs gt i9000.
I crashed my froyo 2.2.1 while debranding it.so i revert it back to eclair 2.1 but now kies won't recognise it for updates
i downloaded every thing i needed-> .pit file\gingerbread file\odin3 v 1.82\the adb a k a sdk what ever.(sdk manager)....even played in commandpromt.1 click root\unroot. decorder update with kies
but all seems worthless unless i don't get the 3 button download mode
i tried all XDA forums-tutorials.....but nothing to come in way of sucess.
so please give some suggestions & links that could save my babe
You really should try to get download mode working, as it will make your life MUCH easier, but if all you need download-mode for is flashing some stock images which Odin, you can force your phone into download mode using ADB.
You said you've installed the SDK, so I'll take your word for it. What you need to do is the following:
1. Locate adb.exe. Open windows explorer, point it to C: and search for adb.exe.
2. Connect your phone with USB Debugging enabled. This setting needs to be enabled before you connect it to your PC (Settings/Applications/Development)
3. If this is the first time you are using USB debugging, you might have to wait for drivers to install.
4. Open a command prompt
5. Change the directory to the one where adb was found in step 1.
6. Type "adb devices" and press enter in your command prompt.
7. Verify that adb actually runs and that your device is listed.
8. Type "adb reboot download".
Your phone should now be in download mode and you can flash things trough Odin.
Beware though: Without the 3-button download mode accessible, you will have much fewer options for recovering your phone later should you mess anything up in the flashing process.
Hope this helps.
Try out the home made JIG
As explaind in thread 819551 if you have a soldering iron, you can put together a micro usb jig to force the phone into download mode.
Yuotube has some clips to show you how to make it. Looks simple, though I haven't tried it personally.

Recovery mode, device not detected by Windows

ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
brandonyoung said:
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
Click to expand...
Click to collapse
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
sparkplugDev said:
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
Click to expand...
Click to collapse
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
brandonyoung said:
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
Click to expand...
Click to collapse
I've heard that unplugging the device from the PC until you're in recovery mode might help. I would also suggest, if that doesn't work, to install the ADB drivers again once you're in recovery mode.
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
When it is running, and usb debugging is enabled, it shows up under Android Phone as Android Composite ADB Interface.
I turn USB debugging off, and it shows up under Portable Devices as Nexus 10
I boot into the bootloader and it shows under Android Phone as Android Bootloader Interface.
but It doesn't show at all when I am in recovery
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
mevensen said:
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
Click to expand...
Click to collapse
I am connecting with a USB cable. I don't know if it is "good' or not, but it works with the tablet in all other modes. I was able to use adb to transfer files, reboot, etc. I was able to use fastboot to flash Chainfire's autoroot, and to flash the factory images.
I was using a USB2 port directly on my laptop, but I just tried the USB3 port and it didn't change anything.
Plugging it into my USB hub, and my hub did not detect that it was plugged in either while it was in recovery mode. It was detected when I rebooted back into the system.
USB debugging is on when I enter recovery. I used "adb reboot recovery" to reboot my tablet into the recovery mode
garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
Thank you !!!!!!!!!
my lenovo a6000 shot no display but detecting n device manager.
it occured due to flash flash.rec.
please help me.

[Q] G2 soft brick!! nooooo

Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
I am not familiar with adb when device is off or fastboot. So if you are desperate follow one of the guides on un-bricking the g2 (which will bring it back to stock and wipe data) but then you'll be up and running and you would just have to re-root and unlock it
djohnson308 said:
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
Click to expand...
Click to collapse
Assuming that you can boot into TWRP, then you probably just need to install the right drivers. Search around the forums.
Stock lg drivers don't seem to recognize phone in recovery mode install pdanet and then connect phone to pc while in recovery mode and open pdanet app in pc and follow instructions to install lg drivers and then pc will find ur device it worked for me when l had the same problem.
Sent from my LG-D800 using xda app-developers app
So i cannot seem to get my computer to install pdanet. i searched for a unbrick thread and found one.. i waited an hour for it to download a 2gig file, the lg program said it was pushing to phone which took 15 seconds (no way it pushed 2gigs that fast) then it said reboot the phone then do a hard reset... i went to do that and the phone just pushed me to TWRP. ahhhh losing my mind
What's the message when installing pdanet
Sent from my LG-D800 using xda app-developers app
access denied followed by x64 issues... Im the domain admin, and the website says its good for x64...
well lets see here are you on windows 8 or 7 ?
this is what i did
I put the phone into fastboot mode then connected it to the computer, well now the customer doesn't recognize it and you should have the drivers installed then what you want to do is search for device manager, look under the Universal Serial Bus Controllers and you will see USB connect with an "!" what you need to do is right click on it then go to update drivers, from there you need to select browse my computer for the drivers not the automatic one then select "let me from a list of devices. next you want to unchecked show compatible hardware now look for Lg in the manufacture list and there should be one that says something about "adb interface" and select it.
Now try using a cmd windows and adb. what i did was i download a fastboot.zip it has adb interface in that zip file then i opened a cmd prompt in that folder by holding shift and right clicking. now once it was open i typed adb list and it recognized my phone
then i went into twrp and adb sideload and I side loaded a stock zip now you be fine and back to square one.

MSM8994DownloadTool.exe Won't Work For My OPT

MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Phil01234 said:
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
Click to expand...
Click to collapse
I've bricked my op2 a while ago. I'm a real noob so I don't know if it will work but have you installed the adb mac drivers or try "fastboot continue" while in fastboot. Just don't give up and keep try. You have absolutely nothing to lose.
chintu1234 said:
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Click to expand...
Click to collapse
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Phil01234 said:
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Click to expand...
Click to collapse
Try connecting your OPT to some other guys pc and see, it may be because of your pc's end that its not getting connected.
And if the same thing happens with a different pc then yeah your usb port or something is fried. Try going to service center if the same thing happens again.

Categories

Resources