Database Info

[Q] ADB not working with LG GW620

This seems like an incredibly common problem, unfortunately for all the posts on a number of forums I haven't found any solutions. I was hoping if I shared some of the details someone may have something I haven't yet come across to check. I've tried the supplied instructions over at openetna.com on now three different PCs including 64 and 32bit Win7 installs but can never get ADB to recognize my phone.
Phone: LG GW620(EVE)
ROM on phone: openetna v6.1 RC3 (Android 2.2.1)
In device manager I have 5 instances in the Other devices section with yellow exclamations on them all titled "LG Mobile USB Modem", which I believe indicates that the USB driver is not installed correctly. I'm not sure why.
Here's what I've done
1. Install latest JDK(JDK 6 update 22)
2. Install Android SDK(usb drivers revision 3 using SDK manager)
2.1 OpenEtna has the user modify the android_winusb.inf file to add the following lines which I've done.
;LG eve
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D&MI_01
3. Turn phone on, ensure USB debugging is turned on, plug in phone with usb to pc
4. At this point ADB doesn't work when I expect it is supposed to. I believe this because if I type the following commands I get an error
C:\>cd "Android SDK"
C:\Android SDK>cd tools
C:\Android SDK\tools>adb kill-server
C:\Android SDK\tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
5. On some of the PCs I've tried this on, I've installed the USB Drivers provided by LG directly that allow me to mount the SDCard on the phone when I turn off debugg.
Please help

Is this the wrong forum for a question like this?

Nope...right one..just no one with enough knowledge on your issue has noticed your post

Fluidsuit said:
Is this the wrong forum for a question like this?
Click to expand...
Click to collapse
I am just having the very same error. i have my LG gw620 with V10G, and OpenEtna -Cyanogen 6.1 (Froyo 2.2.1) as well.
Even more, i cannot mount/umount the SDcard, thus, i cannot access it via usb (i was thinking that perhaps this is THE error, it hasn't been tested with this, only with v10C as per my search).
Anyone else?, any tip?
PS: ANY tip will help me, perhaps if someones knows if i can fastboot it and then push the file like adb (i don't think this is possible, but i hope to be wrong)

I was finally able to see the SDCARD by installing the "Dual Mount" app from market.
However, the logs keep telling me the error of the usb Tethering.
Any replies?
Does anyone knows why is any pc not recognizing the phone in debug mode ? (i know it looks like a driver issue, but believe me , i have done trillions of times the reinstall of all drivers, after wiping them out again, with no luck, It just seems that the driver is not the correct one).
Without this, my phone is completely isolated from adb and cannot continue flashing it
Regards,

So guys, did you get the adb working in the end on the LG GW620 (EVE) ?
I have the same issue infact. It has something to do with the drivers not being correctly installed, but i can't figure it out.
I keep on getting $ instead of the # after adb shell
There is also a new tool, called Z4mod, which can root your EVE if you are lucky (me not so much ) maybe you should try that?

Well, I just got it rooted... if your phone is not recognized/connected, you may need to modify the "android_winusb.inf" file so that the LG Eve is listed first..
this is what I have...
***
[Google.NTx86]
; LGE GW620
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_0FFF
***
But my problem now is with Fastboot. I got the phone into Fastboot mode but WindowsXP prompt for driver. The same drivers that were working in non-fastboot mode won't work. So, I cannot connect to the phone in Fastboot mode.
Anyone know what I should do next??
Thanks!

cheunt said:
Well, I just got it rooted... if your phone is not recognized/connected, you may need to modify the "android_winusb.inf" file so that the LG Eve is listed first..
this is what I have...
***
[Google.NTx86]
; LGE GW620
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_0FFF
***
But my problem now is with Fastboot. I got the phone into Fastboot mode but WindowsXP prompt for driver. The same drivers that were working in non-fastboot mode won't work. So, I cannot connect to the phone in Fastboot mode.
Anyone know what I should do next??
Thanks!
Click to expand...
Click to collapse
Nevermind my previous question... finally figured it out and got Froyo on it.
Thanks everyone for all the tips though!

cheunt said:
Nevermind my previous question... finally figured it out and got Froyo on it.
Thanks everyone for all the tips though!
Click to expand...
Click to collapse
I finally managed to get this phone into fastboot but adb doesn't see it. Can anyone help me with this?

[Q] Can't seem to install drivers for this phone, in either XP or Vista

I've downloaded the motorola driver installation tool and run it, and it acts like everything worked, but windows still says that the drivers are not installed for the phone.
- Charging works (of course)
- Mass storage works (of course)
- "Phone Mode" works (where the PC sees the phone as a phone or modem - or, for this phone, apparently a CD drive?)
- "ADB Interface" does not work (where you have debugging checked and can do cool stuff with your phone)
I understand that since it doesn't I may have to edit the android_winusb.inf file with the info for my phone, and I know where to get its device ID from. I try to mimic the other entries in that file but there are 4 things I need to enter - single adb, composite adb, and two lines for single bootloader. I guess I don't know exactly what to put there. This is what I tried:
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_42B4&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_42B4&REV_0216&MI_00
%SingleBootLoaderInterface% = USB_Install, USB\VID_22B8&PID_D00D&REV_0216
%SingleBootLoaderInterface% = USB_Install, USB\VID_22B8&PID_D00D
Someone else must have encountered this before. What did you put in that file to make it work? When I tell windows to find a driver for my "Motorola ADB Interface" in the folder C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver ... it just tells me that it can't find any information about my device.
jeez, all this just to be able to tether using pdanet.

Can't use ADB? Look here!

http: //www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
I notice that ADB would never load in recovery, while it would load in regular mode.
The driver was never found in Windows, and it was just called" Transformer."
To fix this you need to do a little driver ini edit to include the hardware IDs in the Google USB driver from the SDK.
Here are the steps that you need to follow in order to enable these drivers:
You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
Open the google-usb_driver folder that you will find inside your Android SDK folder.
Open the android_winusb.inf file in notepad or any text editor to edit it.
Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections.
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
Open a command prompt window and enter this command:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
Choose to view all devices and click ‘Have Disk…’.
Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
Once the drivers have been installed, you should be able to use ADB with your device.
To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB.
Although these instructions were originally written for Toshiba AC100, they should work for any Nviaid Tegra or Tegra 2 based Android device.
Click to expand...
Click to collapse
The hardware device ID used in regular mode is different than the one in recovery enough to cause a problem.
I found that this is for reg mode
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&MI_01
and this worked in receovery
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&REV_9999
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F
After the edit and following the instructions I was able to use ABD in recovery

Useful and often overlooked tip, Thanks!

Problem Dicra tab 307

Hi all, i have a problem with my Dicra Tab 307.
It's a tablet based on A13 boxchip 1.2GHz and 512mb DDR3 ram.
I'm trying to use ADB with SDK but Windows 7 didn't recognize my tablet. I have already tried with this guide:
How to find the new VID/PID in Windows 7:
1. Go to the device manager (hit the start button, and type "Device Manager" to find it).
2. Double-click on ADB, under Android Devices and select details.
3. From the combobox select "Hardware Ids" and write down the VID and PID values. For example, in the screenshot below, my PID is 0BB4 and my VID is 0C99.
Changing the VID/PID values in the ADB driver's .inf file:
1. Go to the folder which has the driver (it should be %somewhere%\android-sdk-windows\usb_driver).
2. Make a backup of android_winusb.inf and open the original using a simple text editor (notepad, notepad++, etc).
3. Right at the end of the [Google.NTx86] or the [Google.NTamd64] section (depending on whether you are 32bit or 64bit), paste the following, replacing <YOUR_PID> and <YOUR_VID> with the hex values you wrote down before:
; MY PHONE SETTINGS
%SingleAdbInterface% = USB_Install, USB\VID_<YOUR_VID>&PID_<YOUR_PID>
%CompositeAdbInterface% = USB_Install, USB\VID_<YOUR_VID>&PID_<YOUR_PID>&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_<YOUR_VID>&PID_0FFF
Now, unplug and plug the phone and install the driver normally when it asks you to, by pointing the wizard to the ADB drivers directory.
Click to expand...
Click to collapse
But windows say Can not find the driver for your device, can not install android. Anyone help me please? Thank you!

Help :\
Solved.

[HOWTO][ROOT]Point of View Protab 2.5xxl

Hallo!
I want to to show you how I gained root-access to a Point of View Protab 2.5xxl Tablet.
I only tell you what I did with my device, without any warranty. If you do the same to your device, you do anything on your own risk. Doing these things might end up in a damaged device. When you are not sure what you are doing, do NOT the same to your device. I do not promise anything, I just tell you what I did
I needed a Windows 7 PC whit an installed java JDK 1.7 (If I would not have this, I would download it from java.oracle.com)
The main problem hereby is not the process of the rooting itself, but getting ADB able USB Drivers.
First step: I download the Android 4.1 firmware from the vendors webpage:
http://downloads.pointofview-online...XXL/TAB-PROTAB25XXL-Android 4.1_201212011.zip
Then I extracted the zip-file and followed the Instructions to update my Device.
Second Step: I download the Android SDK from here:
dl.google.com/android/installer_r21.0.1-windows.exe
I installed the Android sdk on my Win7 Computer by doubleclicking on the installer_r21.0.1-windows.exe and startet the Android SDK Manager.
I took some time to load a ist of available packages, and the I could select
Tools->Android SDK Plattform-tools
Extras->Android Support Library
Extras->Gogle USB Drivers
and I pressed the button 'Install 3 Packages'
A Dialog opened and I checked 'Accept All' and pressed the Button 'Install'. I waited to complete...
Third Step: I checked in the Settings of my Protab:
Security->Allow install from external sources
Developer->USB Debugging
I connected my Protab via USB to my PC and opened the Device Manager.
I selected my device which was marked with a yellow warning sign. With a right-click on it I got the context menu and choose 'Properties'.
In the 'Details' tab i selected the Property 'Hardware Ids' where I found the values VID_18D1 and PID_0003
Fourth Step: I opend Windows Explorer and navigated to the folder:
C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
I opened the file 'android_winusb.inf whit my texteditor and copied the lines
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E21
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
and changed the copy to those values:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01
So it matched the values I found in the properties of my device.
I saved the changed file.
Fifth Step:
In the Device Manager I right clicked on my device and choose 'Update Driver'. In the Driver dialog I selected to 'Browse my computer for driver software' and pressed Next. At the point 'Search for driver software in this location:' I navigated to this folder:
C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver.
I choose to install this driver software even it is not signed.
After this step my Device was correctly recognized by windows.
Sixth Step: Now I followed the Instructions from Bin4ry to root my device:
http://forum.xda-developers.com/showthread.php?t=1886460
I choose option '1 Normal', followed the instructions and after this, my tab was rooted...
I hope it was interesting for you to here what I did...
If you do the same, you do it on your own risk! I do not recommend you to do the same
Kind regards, Uwe

ProTab PRO 2.4 root
Thank you for your know-how. I successfully rooted my PointOfView ProTab PRO 2.4 with Root_with_Restore_by_Bin4ry_v31, mode 1 - New Standard-Root (thx Ariel Berkman).