[Q] Device identification fails - G2 Q&A, Help & Troubleshooting

Hi,
I'm trying to root my LG G2 D802 unit, but all my efforts failed. I suspect that the rooting procedure, ioroot, fails to identify my smartphone. I came to this conclusion since running ADB DEVICES ends with an empty device list.
I tried to change the usb connection, but looks like this isn't the source of my failure.
How can solve this problem?
I run ADB on a win 7 system.

You should ask your question here: http://forum.xda-developers.com/lg-g2/help
You are posting in the wrong section.

Related

[Q] SOLVED Possibly brick, need help!

I was in the process of taking my Nexus 7 back to stock yesterday it started giving errors from fastboot. My device is completely wiped clean. Can't boot into recovery since there isnt one, there is no system to boot into, etc. I tried to install 4.2.2 via the toolkit and manually from fastboot and I keep getting errors. The most recent one is no such device or address found. The only the only thing that I have been successful in doing this entire time is oem lock and unlock. I read somewhere else that someone had a similar issue and that fixed it. I have tried every different port on my laptop and every different cable I can find. I haven't used the OEM ASUS cable since i cant find it, but I think it is at work so that the last one I can think of.
Can anyone offer any help or solutions? I've had the worst luck int he last three days with my devices. I've never had a potential bricking issue since my G1 and now i can't seem to avoid them. Any help is greatly appreciated. I can provide screenshots of the errors if that would help as well.
EDIT
Turns out it wasn't a bad device or any of the million cables. It was a bad laptop. I was finally able to get the drivers to install on my win8 desktop and it all went as it should.

[Q] Bricked my LG G2

Hi Friends,
I am new to this Forum and Android as well. I recently bought unlocked LG G2 32 GB in India. It was:
Model - D802
Android version - 4.4.2
Software version D80220b
As it's wifi reception and network reception was not good, I thought of installing the ROM again. The biggest mistake that I did not install any recovery and didn't even rooted my device. I checked with root checker and it showed that your device is not rooted. Then I follow the method given on below link:
http://forum.xda-developers.com/showthread.php?t=2432476
I took the firmware file named "India 32GB D80210C_00.kdz" and select type as "3GQCT" and performed the Normal Flash. It went well but after it booted up, my touch screen calibration was totally lost. I connected mouse using USB OTG cable and calibrated the device but it didn't work out. Calibration still seemed gone.
After all try, I couldn't do much and read of TOT method to go back on Jelly Bean. I did that as well using "BIN_LGD802AT-00-V10b-SEA-XX-SEP-04-2013-32G+0.exe" from which I extracted the TOT file and performed the flashing again by coming in "Download mode".
After that my phone is in boot loop and same issue of lost screen calibration. If I try to go into recovery it gives me option only to factory reset the phone which does not help out at all. I guess it's because i didn't root my phone and didn't even installed any recovery.
I know I have done a lot of mess with no knowledge but please help me out as its my new phone and I have hardly used it for 1 month and it's not even under warranty.
Thanks.
grvshri said:
Hi Friends,
I am new to this Forum and Android as well. I recently bought unlocked LG G2 32 GB in India. It was:
Model - D802
Android version - 4.4.2
Software version D80220b
As it's wifi reception and network reception was not good, I thought of installing the ROM again. The biggest mistake that I did not install any recovery and didn't even rooted my device. I checked with root checker and it showed that your device is not rooted. Then I follow the method given on below link:
http://forum.xda-developers.com/showthread.php?t=2432476
I took the firmware file named "India 32GB D80210C_00.kdz" and select type as "3GQCT" and performed the Normal Flash. It went well but after it booted up, my touch screen calibration was totally lost. I connected mouse using USB OTG cable and calibrated the device but it didn't work out. Calibration still seemed gone.
After all try, I couldn't do much and read of TOT method to go back on Jelly Bean. I did that as well using "BIN_LGD802AT-00-V10b-SEA-XX-SEP-04-2013-32G+0.exe" from which I extracted the TOT file and performed the flashing again by coming in "Download mode".
After that my phone is in boot loop and same issue of lost screen calibration. If I try to go into recovery it gives me option only to factory reset the phone which does not help out at all. I guess it's because i didn't root my phone and didn't even installed any recovery.
I know I have done a lot of mess with no knowledge but please help me out as its my new phone and I have hardly used it for 1 month and it's not even under warranty.
Thanks.
Click to expand...
Click to collapse
There might have been a problem with the firmware that you used and the flash method. Use this to find your firmware and pick cse flash this might solve it.
I searched the firmware in your given link by my IMEI number, but I have a problem. After I click on "Upgrade start" in "Normal web test upgrade", it does not give me country select option. Instead it open LG Mobile support tool which just keeps on showing "Waiting for Connection".
If I click start upgrade without selecting "normal web upgrade test", it gives me country selection window.
What should I do? Can I directly click on "Start upgrade" ?
try this one
http://forum.xda-developers.com/showpost.php?p=51265001
OP I have the same problem, see my recent posts. Let me know if you found a fix.

[Q] Can't root Verizon LG G2

Hey guys,
I'm having a ***** of a time getting my G2 rooted.
Info:
LG G2 VS980
Android Version: 4.4.2
Software version: VS98026A
I've tried everything under the sun and followed all directions to a "T".
-The main version of ioroot reboots my phone to an android figure with an error sign in his stomach.
-Another version I saw in a forum (ioroot25r1) closes itself as soon as I hit a button to start in command prompt. (This required me installing Android SDK, platform tools, and Google USB drivers, which I did.)
-Towelroot says "This phone isn't currently supported"
-Stumproot says "ERROR: Unsupported device"
Any help would be greatly appreciated! It looks like others have been successful in getting their G2 with this software version rooted, but as I've learned in the past, nothing works for me like it's supposed to.
W77 said:
Hey guys,
I'm having a ***** of a time getting my G2 rooted.
Info:
LG G2 VS980
Android Version: 4.4.2
Software version: VS98026A
I've tried everything under the sun and followed all directions to a "T".
-The main version of ioroot reboots my phone to an android figure with an error sign in his stomach.
-Another version I saw in a forum (ioroot25r1) closes itself as soon as I hit a button to start in command prompt. (This required me installing Android SDK, platform tools, and Google USB drivers, which I did.)
-Towelroot says "This phone isn't currently supported"
-Stumproot says "ERROR: Unsupported device"
Any help would be greatly appreciated! It looks like others have been successful in getting their G2 with this software version rooted, but as I've learned in the past, nothing works for me like it's supposed to.
Click to expand...
Click to collapse
You can either revert back to 24A one step at a time and use ioroot or stump root should work. You may have to do the brute force method or whatever it is called.

[Q] LG Flashtool Model Information Check FAIL

Trying to use LG Flash tool to get back to stock. Whenever I run it and get things going...it just says "Model Information check FAIL" and stops there. I looked in other threads...and couldn't find any answers (although many people seem to have encountered this same problem). Phone boots out of download mode fine still so it's not bricked my any means. This is on a D800. Using Supersport as my guide:
http://forum.xda-developers.com/showthread.php?t=2663369
Any help is appreciated.
EDIT: problem resolved. In case anyone else runs into this issue, I just used a different USB port and it ended up running and now I am back on stock. Not sure how that works, but it did

*[SM-910W8] Broken USB. Root via SD Card?*

Hi all,
I'm just about at my wits end here. I have a Note 4 (N910W8) with a failed USB connection and I would really like to root it. The underlying goal is to remove/disable all samsung bloatware.
WRT the USB, I have tried adjusting developer options, *#0808#, updating drivers, changing cables, changing PC's, etc. I've tried everything I could find online. Recently, I took it to a local shop and learned that the problem is not with the USB port/board, but the motherboard itself. I'm not going to pay to replace it. I have googled far and wide. As far as I can tell, this phone will never again connect to a PC via USB. So, download mode and Odin are out.
I have tried TowelRoot, KingoRoot, and other apk's, but I am on Android 6.0.1 (MMB29M/GLW-N910W8VLS1DPK1) so all of these exploits have been patched.
I am able to boot into (stock) recovery mode, so I thought I'd try recovering via SD card, however that doesn't work either. First I get a loading screen of the mascot with a spinning wireframe polygon in his belly and the message "installing system update". Then after ~15 seconds, the mascot is on his back with a red warning symbol over his belly, and the text "No Command." is displayed. I'm not sure what that's all about, because I have the latest update installed.
Any attempts to install CF-Autoroot or another recovery firmware (ie https://samsung-firmware.org/model/SM-N910W8/region/GLW/ , or https://forum.xda-developers.com/note-4/snapdragon-dev/trltecan-n910w8-aoa1-stock-rooted-t3025538, etc) from SD (in recovery mode) have been met with the same error messages:
E:footer is wrong
E:signature verification failed
I'm not sure why because at least some of these recovery firmwares claim to be official builds. Granted, they are older versions (downgrades), but are signed nonetheless.
I have tried installing TWRP or CWM so I can disable signature verification, but AFAIK the device must already be rooted to install these (which seems like a bizarre catch-22, but maybe I'm confused) so that's a no-go.
It certainly feels like I have explored every possible avenue, but I have one remaining idea. Perhaps if the phone doesn't want to downgrade, I could force its hand by carefully soft-bricking the current rom in a controlled manner, then performing a recovery from SD with an official 4.4.4 KitKat build, and finally, using the towelroot/kingoroot/etc exploit to gain root access.
I mean, why else would there be a recover-from-SD option in the stock recovery menu? There must be a way to get it to accept a recovery build...
It's a last resort. But I'm willing to try it. The phone boots up, but is so bloated and laggy that it's practically unusable. Still. Am I missing anything? Surely there's some way to skip the USB / Odin method. What do you guys think? Is it time to go hulk on this thing? Is there any hope left? Curious to see how much further this rabbithole can go.
Cheers and thanks guys.
I've searched for ways to soft-brick, but have not come across anything. The bootloader appears to be locked, which is odd because I thought that only applied to Verizon variants.
I have recently downloaded an ADB/fastboot package for windows so I could attempt ADB over WiFi, however I can't establish a connection. I thought I'd do some more poking around on the phone side, so I installed some Wireless ADB apps. They all indicate a root is required, so I think that might be a dead end. I also connected to a ubuntu machine. Nothing. The phone charges, but both the PC and Ubuntu machine show zero signs of any connection at all.
There has to be some kind of SD-based solution to this. You can boot a computer from an SD card / USB stick and use that to access files (on an unencryped partition), and I'd be happy to do that here and delete those bloatware APK's directly... but I guess phones don't behave like other computers.
I've picked all the low hanging fruit. A part of me believes that there are some sneaky hacker ways to get at this without USB (ie some sort of rootkit) but that's way beyond my abilities. I'm going to take a break and attack this again once I have fresh ideas.
I'm in the same boat (busted usb port), does your phone still fast charge? Mine stopped fast charging.
I too have the same problem, except with the Note 10.1 2014. I know that is a different forum, but if you find a solution, it might be adaptable to my problem. I too have exhausted all other options as described above. Please someone, there must be a way to root via SD card instead of Odin. Help us please!
Me too. I have a Note Pro 12.1 running Lollipop. USB is busted and I've already replaced the port and ribbon, so it must be the motherboard. I mainly need it for Titanium backup, so I don't have to reinstall large games over my limited connection.
I have the same problem. Note 4 N910H. Not recognized by pc, stopped fast charging shows usb charging in battery settings. AFAIK I just re-rooted the phone before it went bust. There is no solution except changing the motherboard. Also this problem seems to be quite common.

Categories

Resources