Database Users

G2 white lines -> can't connect for reflash

Hi, I have a G2 I need some help with. This is a partial repost from [HELP THREAD][Noob Friendly].
Just got a LG G2 for my wife (wedding anniversary). It arrived by post yesterday, yay I though, I got a couple of weeks to sort it out. Am trying to transition her from her old iPhone4S over to Android, and from checking things out, it looked like the OptimusG3 rom was the way to go, in terms of a nice interface.
I shoulda slowed down and been more meticulous with the process, but anyway… I have little knowledge of these things, but have managed to flash custom ROMS to a couple of devices before (HP Touchpad, Ainol Fire), noting that any problems I’d previously encountered were usually due to skipping or not following steps properly.
G2 model is D802. Kitkat 4.4.2 installed by default. From an ebay seller - back case, software and printed instructions all say D802. Opening the back case, internal bottom left corner says D801/D803.
Tried to follow guide here http://forum.xda-developers.com/show....php?t=2788077
Tried to root as per here http://forum.xda-developers.com/show....php?t=2448887
I think the root went through ok, although I had to try more than once (had other stuff happening in the background so not paying 100% attention).
Tried to flash TWRP as per here http://forum.xda-developers.com/show....php?t=2633941
Didn’t seem to be able to get this working.
Uncertain at this point if I was properly rooted, so redid it with https://towelroot.com/ - which seemed to be fine
Then tried to install TWRP with Autorec: http://www.droidviews.com/install-twr...
Which seemed to be successful, and I’m sure I picked the D802 TWRP recovery file, but THIS IS WHERE THE TROUBLE REALLY BEGAN - on reboot to recovery the trouble started – no logo, I’m just seeing a black screen with vertical lines that change for a bit, then go static.
My understanding now (thanks to Art Vanderlay) is this is probably the result of me having a JDI panel - so now I need to reflash a JDI kernal to fix the LGIT kernal that Autorec installed.
I can't read the screen at all - it is just black with white lines and change a bit before going static. I have tried to connect the phone up to the computer in DOWNLOAD mode using the VOLUME UP and ATTACH USB CABLE technique.
When I do this, the computer beeps to let me know a device is attached, and a ADB device turns up in device manager - but then nothing else thinks a device is attached, including SimpleTool, LGFlashTool2014, PDANET (which does say device connected to begin with, but then doesn't proceed any further), ADB (via commandline), MinimalADB, or Linux.
I have tried various permutations and combinations of:
1. different USB ports
2. different USB cables
3. different computers (x3)
4. different drivers (from various places, including LG website, SimpleTool, PDANET). (I even tried a Verizon G2 driver just for the hell of it)
5. two different LINUX distros
...and nothing seems to see the G2.
Any suggestions very very welcome, cos I'm out of ideas.

Did you manage to find a solution to that problem. I am having the same problem

LG E617G Will not turn on.

Hello everyone. Recently, I used this tutorial: http://forum.xda-developers.com/showthread.php?t=2392762 to obtain Cm11. What happened was when I tried to unlock the bootloader, and used adb commands to execute the files on my root. After I did reboot, the phone wouldn't turn on. No signs of life, can't boot into recovery mode. I've done the tutorial before on this phone, and I reverted back to stock. Now that I'm doing it again it won't work. I think it may be hardbricked. When I plug it into my PC, I can go to device manager and the PC will recognize it as a Qualcomm driver. I really want to fix this problem without needing to call LG or get repair for it. I looked at some tutorials and found this one: http://forum.cyanogenmod.org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/ I'm not sure if this'll work for me. Can someone please provide me with some help with this situation.

Custom rom without gui

Hi,
I recently broke the screen. Phone's display is working while the touch panel isnt. I was able to recover all the data via adb pull.
I want to use this device for computational purposes. Any suggestions for a ROM which is prerooted ?(i dont need a gui either).
Remember, if su via adb pops put a dialog box on the screen, i wont be able to accept it since touch isnt working.
Current rom : Stock 4.4.4 (rooted)
Recovery : twrp
Bootloader : unlocked
Much thanks.

You can use that phone from your computer like normal
http://forum.xda-developers.com/showthread.php?t=2786395
I had nexus 4 in the same condition. Bad thing that no one posted this info in my thread (not on this site) So i tried to change digitizer and broke LCD too

Newbie trying (and failing so far) at my first root

Hi all,
First message in this wonderful community.
Anywas, having owned a Galaxy Note 3 for a few years now I thought I'd give it a shot at installing a new ROM to get it in better shape and try to stay with it a bit longer. Nothing really wrong with the phone other than getting a bit sloooow, specially the camera.
Anyways, not being a very geeky person, I soon realized the learning curve is steep.
This is what I've done so far:
1) Identified the model (SM-N9005)
2) Downloaded and unzip the SDK platform tools
3) Downloaded the TWRP custom recovery
4) Unlocked developer tools, allow unknown source (not sure if that is needed) and allowed USB debugging. In this phone I think there is no option for OEM unlocking.
5) Installed latest Samsung USB driver
5) Tried to proceed with unlocking the bootloader. This is where I ran into issues:
- I installed ADB Installer saying YES to everything
- Connected phone to pc with a usb cable
- From the command prompt (in my user) I executed adb reboot bootloader. I initially got an error (something about daemon and a port?....) but was able to move ahead
- The green android logo appeared along with this message "Downloading ...Do not turn off target!!"
At this point, pressing the volume down, power and select at the same time I tried to get out but kept on coming back to the same android menu stuck in "Downloading ...Do not turn off target!!". After the third try, a new warning message came up asking me if I want to proceed or reboot phone (pressing volume down) and I rebooted the phone to "escape" this predicament. I thought I was going to brick the thing!
Anyways, any recommendations on how to proceed? Is there an easier method to root the phone? Or to circumvent the issue I encountered?
As you might have guessed by my message, I can (sometimes) follow instructions but the underlying knowledge of what I am doing is .... well ...missing? :silly:
Hope you guys can help me. Thank you all in advance for your assistance.

PierreBCN said:
Hi all,
First message in this wonderful community.
Anywas, having owned a Galaxy Note 3 for a few years now I thought I'd give it a shot at installing a new ROM to get it in better shape and try to stay with it a bit longer. Nothing really wrong with the phone other than getting a bit sloooow, specially the camera.
Anyways, not being a very geeky person, I soon realized the learning curve is steep.
This is what I've done so far:
1) Identified the model (SM-N9005)
2) Downloaded and unzip the SDK platform tools
3) Downloaded the TWRP custom recovery
4) Unlocked developer tools, allow unknown source (not sure if that is needed) and allowed USB debugging. In this phone I think there is no option for OEM unlocking.
5) Installed latest Samsung USB driver
5) Tried to proceed with unlocking the bootloader. This is where I ran into issues:
- I installed ADB Installer saying YES to everything
- Connected phone to pc with a usb cable
- From the command prompt (in my user) I executed adb reboot bootloader. I initially got an error (something about daemon and a port?....) but was able to move ahead
- The green android logo appeared along with this message "Downloading ...Do not turn off target!!"
At this point, pressing the volume down, power and select at the same time I tried to get out but kept on coming back to the same android menu stuck in "Downloading ...Do not turn off target!!". After the third try, a new warning message came up asking me if I want to proceed or reboot phone (pressing volume down) and I rebooted the phone to "escape" this predicament. I thought I was going to brick the thing!
Anyways, any recommendations on how to proceed? Is there an easier method to root the phone? Or to circumvent the issue I encountered?
As you might have guessed by my message, I can (sometimes) follow instructions but the underlying knowledge of what I am doing is .... well ...missing? :silly:
Hope you guys can help me. Thank you all in advance for your assistance.
Click to expand...
Click to collapse
flash custom recovery.download supersuzip latest version is 2.82.push it to your phone.reboot to recovery mode.flash supershu zip.reboot to system.your phone is rooted.that's it.
Sent from my SM-N930F using Tapatalk

Normal method .
Flash TWRP via Odin.Put custom rom on SD card .
Boot to TWRP recovery and flash .
N9005 does not have a locked bootloader .

HELP! SG S4 i9505! Broken and Black Screen. Help on Enable USB Debugging! Please!

first of all, i'm sorry if i'm posting this o the wrong section (i'm new here seeking help)
second, I NEED HELP!
i tried using Dr. Fone for recovery and unlock but i'm getting "flash recovery packaged failed" on the end. when on recovery device mode, i can hear the new device/unplugged sound.
if only i can use OTG and mouse to enable USB debugging. but obviously i cant see. when i open the phone normally and try using screenshot, i can hear the sound. so that means that my phone is not dead and only have broken lcd/screen. i also cant open the device folder because its locked (i think its locked). i also looked some class a ldc/screen digitizer but its kinda expensive and going to technician doubles the cost. from this point, i don't know what to do anymore. i just want to get important pictures and video. been trying to find a solution for hours.

I have not seen a method to enable USB debugging without a working screen.