hey am working on Adb devices with Optimus one, but can able to use it..
It is not installing my mobile drivers, i had installed lg px suite and its drivers b4 dng this but its not working... plz help me guyzz
try enabling usb debuging which is under developement in application
i had this problem too but i found out how to install the proper drivers (credits dont belong to me)
dont plug in your phone until i say so
download the lgmobile support tool:
http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe
install it
when its done installing, go to options&help
go to country&language
choose singapore (country) and english
then select install usb driver
scroll down to lgp500, select it and let it download
you should get the window that you get when you install something
install the usb driver
now you can connect your phone to your pc for adb
I was running an older version of adb that worked fine with my g1, but wouldn't talk to the OptT.
After I updated adb to 1.0.26 it started working fine.
Related
Anyone have a line on how I can get this?
Do you mean an adb driver for USB debugging support? If so, I've found that if you install the PDANet client for your version of Windows, it installs a driver that ADB likes. You have to make sure to uninstall the Dell PC Suite first though, if you have that installed.
as far as i'm aware (i'm running win7 atm) there are no specific windows 7 drivers.
Just download the latest Android SDK and run adb from there. Works a treat.
Just install the Dell PC suite. You'll need to restart. after your pc restarts it should be fine. I did this yesterday when I bricked by streak. fastboot = annoying.
Synyster_Zeikku said:
Just install the Dell PC suite. You'll need to restart. after your pc restarts it should be fine. I did this yesterday when I bricked by streak. fastboot = annoying.
Click to expand...
Click to collapse
If the process you used caused you to "brick" your phone, why would you suggest others to follow??? If it didn't work for you, it most likely wont work for others...
Still no luck getting this to work.
go to device manager choose android 1.0 or whatever its called, choose to update drivers, manual option, the bottom option, have disk, choose the folder with the usb drivers from the sdk and then select android.
the drivers work fine then..
if you're trying to get pcsync to work then this isn't related
download Fastboot.exe & Koush's Recovery > unzip to your c:\ , renaming to something like c:\streak ...... Go to control panel>system>device manager ...... rigght click "android 1.0" > let me pick > show all devices > Android phone or Google INC ( i didnt find Google INC in mine , only found Android phone ) > Android Bootloader Interface
It will the bring up a warning , just click "ok" and it will bring up another dialogue saying the device is installed successfully
Hope this helps
winxp sp3 sony tablet s when put in recovery mode for flashing the mtp driver
shows yellow (!).when i try to install driver manually it trys to start but comes
back with code 10.with tablet in normal mode winxp sees mtp & adb drivers.
the problem is only with recovery mode.tryed all i can think of and read all
solutions but driver still fails to start.so i can,t flash fw!. i really need help with
this one. please someone help i`ll give you a big thanks. i know i am not the
only one with this problem.i hope this is clear enough.
Same problem here:
Everything's fine in normal boot, but in recovery mode, I can't install the MPT driver. Win7pro. It tries to install, but ends up with a Code28 (something in the INF file is invalid, can't tell the english error message, because I have German Win7).
This seems to cause my problem flashing to R5a by AiO or the auto flasher by condi.
I get the exact error message on the tablet, as shown in post #72 in this thread:
[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery
Trying since four nights...
At least I managed to flash and root to 4.0.3 R2a from the "unrootable" 3.2 R10 by flashing via recovery mode to Sony original ICS R2a (downloadable from sony) and then using the AIO 5.3 to root. Don't know why this way is not published here... Tried updating to 3.2.1 etc, nothing worked... the found the links to sony's fw and thought "WTF! Let's try ICS R2a, worst case is an also unrootable Tablet but with ICS". Worked, and was rootable then.
Just ignore the problem. I believe seeing the alerted MTP USB Device in Windows Device Manager when your tablet is in Recovery Mode is being cause by your tablet's borked Android System Recovery Revision 36 (i.e., Rev.36). This problem did not occur with earlier revisions of Android System Recovery. Normally, no MTP USB Device (or Sony Tablet S) should be displayed or even installed for Recovery Mode because a tablet in Recovery Mode cannot provide MTP functionality. Recovery Mode only requires Android Composite ADB Device be installed. Normal Mode, however, requires both Android Composite ADB Device (but only when the tablet's USB Debugging is turned on) and MTP USB Device, which Windows Device Manager renames and displays as Sony Tablet S.
You are basically right... it was ADB drivers, not MTP.
I tried all possible drivers from the list, also some "phone" devices. And YES!! Windows accepted one of them...
After that, I had no problem flashing my tablet to ICS R5a!!
please, could somebody who has writing permission in the dev forums, tell Condi, that the AiO 5.3 tools tells you to check this driver ONLY AFTER you are NOT stuck in "status7" error!!!!!
You do NOT get the message in the terminal box, IF you are stuck.
That would have saved me one or two nights trial and error...
But, after all, I have a nice working ICS R5a on my tablet S
I will post a how-to for other 3.2 kernel10
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
phc1234 said:
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
Click to expand...
Click to collapse
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
android phone dosent show in device manager
ThreeEyes said:
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
Click to expand...
Click to collapse
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
phc1234 said:
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
Click to expand...
Click to collapse
But by manually updating the driver and choosing manually, you can assign ANY driver to any device - it may not work or even do some damage to the system, but basically, it's your choice!
Take the device with the "!" and give it the right driver...
"CAT" above is right with rel5 and 5a that they changed the recovery rev to 36 and this rendered the
tablet s from loading any mtp driver or seeing the android phone entry in device manager so no way
to install adb driver.this has killed conis AIO tool flashing firmware and roms until someone breaks
the lockdown sony put in.
This is a Root Tool for Android 4.0/4.1 devices.
How to use it:
1. Download and install ADB Driver.
2.Restart your computer once adb driver is successfully installed.
3.Have your device charged to at least 50% to ensure no power interruptions.
4.Backup your device to your computer or external sdcard (I like My Backup app from the Play Store).
5.Download and extract Bin4ary Root Tool to a new folder on your computer.
6.Power on your device and enable USB debugging (Settings>Developer Options>USB debugging>OK).
7.Connect your device to your computer via MicroUSB to USB cable in MTP mode (option will appear in notification bar when you plug your device into your computer).
9.Your computer should automatically install drivers using the previously downloaded and installed adb driver. It may popup a install wizard; follow the wizards prompts. Let Windows update search for it. The computer may say it can't install MTP device; that's ok, click finish or cancel. Then another wizard will popup to install ADB device and will sucessfully install.
10.Double-click "RunMe.bat" (it may just say "RunMe") in the downloaded Root Tool you extracted to a new folder and follow all instructions you see on the application (for SoftwinerEvb tablet choose option 1 by pressing 1 key and then enter/return key on your keyboard).
I've succesfully rooted my SoftwinerEvb (4.1.1 JB) Tablet with it. I haven't flashed any custom recovery, rom, or kernel yet.
HAVE FUN!!
I'll try and answer any questions if I can.
Does this work for yely kernel on softwinerevb 4.0.4
south956 said:
Does this work for yely kernel on softwinerevb 4.0.4
Click to expand...
Click to collapse
Can you please tell me how to reset an android tablet stuck through sdk? The key combination does not work.
Phone.apk
Hello to all! I have some problem with softwinerevb 13. Can't use 3g modem after deleting Phone.apk . So needed Phone.apk version 4.0.3. Please someone upload there that apk .ps.sorry for bad english ok
Thank you!
It works for me! :laugh:
Thanks it worked,
Had some trouble with drivers,
Had to use samsung usb driver to get the device recoginsed
worked after that :good::good::good:
Hello All,
I have a car mirror that has a 5inch screen running SoftwinerCvr Android 4.0.4.
The above instructions helped to root this device, I choose option #5
Thanks
Been looking and still looking, how can I flash a custom recovery?
Which one should be used?
T.I.A.
Play store
How to install the Google Play Store on it please ? It doesn't work with a simple apk :/
Hello,
it's almost 2-3 hours that i'm stuck with instaling drivers on pc for my Prestigio Multipad PMP5097CPRO.
I wanna root it, but I need first to install drivers propery to debug via USB.
Root with "ICS Root Unlocker"
I used that guide sendspace.com/file/4dwex1
tried with different versions of Rockusb, but still the same. (unable to install drivers)
I even tried different usb cable/port/ and pc, but no work (win7 64bit)
ADB driver don't work too. I've read this thread but find nothing similar http://forum.xda-developers.com/showthread.php?t=1796067 or this http://forum.xda-developers.com/showthread.php?t=1957790
Any idea
thanks
4Cvetko4 said:
Hello,
it's almost 2-3 hours that i'm stuck with instaling drivers on pc for my Prestigio Multipad PMP5097CPRO.
I wanna root it, but I need first to install drivers propery to debug via USB.
Root with "ICS Root Unlocker"
I used that guide sendspace.com/file/4dwex1
tried with different versions of Rockusb, but still the same. (unable to install drivers)
I even tried different usb cable/port/ and pc, but no work (win7 64bit)
ADB driver don't work too. I've read this thread but find nothing similar http://forum.xda-developers.com/showthread.php?t=1796067 or this http://forum.xda-developers.com/showthread.php?t=1957790
Any idea
thanks
Click to expand...
Click to collapse
Go to www.snappea.com and install it on your PC, with phone disconnected from PC. Once snap pea installs it will pop up a message asking you to turn on USB debugging on phone then it will ask you to connect to pc, Snap pea should be able to install a generic ADB driver that will work for what you need.
Hello.
How can I connect my L9 p760 phone with Cyanogenmod installed to run adb? I tried reinstalling LGUnitedMobileDriver, PC suite etc, but nothing works. PC recognizes it as a portable device, but by installing LG drivers, I get error LGE U2 USB Device No driver found.
On stock rom there was option for USB connection "LG PC Suite mode" or something, it worked great with adb, fastboot. On CM there is no such option, just media and camera options, enabling debugging mode also does not make any change.
Why I need it, I need to log issues I have listed here forum.cyanogenmod.com/topic/80758-few-questions-regarding-usability-of-cm-screen-filter-lags-radio/
Maybe someone also had issue with freezes in interface responsiveness and/or call reject button and had those resolved?
Hi,
To solve LGE U2 USB Device driver not found:
- in Device Manager (are you using Windows, right?), go to "Computer/Manage/admin pswd/Device Manager"
- right click LGE U2 USB Device
- choose Update Driver
- now choose the second option (manual installation)
- choose in driver list: Android Sooner Single ADB Interface.
But... wait! One more annoyance. Your adb must be version 1.0.31 (requirement for Android 4.2.2 or higher), or you will receive error "device offline". To show yours, type > adb version
Awesome, works like charm. Thank yo so much!
WOW! Thank you so much. Now I can use my phone again.