I was trying to install PDANet yesterday onto my laptop, I follow all the isntructions during installation and allow the drivers to be installed. I choose Samsung as my phone. At one point it asks me to connect my phone to my PC, which I do. It proceeds to dl 4 things, 3 out of the 4 download and install fine, but the ADB Driver installation fails every time (this is windows downloading drivers, not the installation itself). I have tried finding ADB drivers on my own with little success.
to confirm before the question is asked, yes the USB debugging option is turned on. ADB driver just keeps failing to download and install using windows.
same issue with my HP laptop
Driver name is S3c6410 Android ADB
Noob here,
My viewsonic Gtablet has been softbricked and I've been attempting to get it into a functional status for the last couple of weeks.
I have tried -
1) installing the factory reset roms onto the microsd card and booting gtablet in recover mode. This lead to an indefinite "booting recovery kernal image".
2) installing clockword mod in hopes of fixing the bootloader. This led to the same result
I'm now attempting to nvflash the device. I have all folders installed and the entire setup is ready to commence HOWEVER; when I boot the gtablet in APX mode and connect it to my windows pc, there is no prompt indicating a new device. After checking device manager I cannot find the device there either. I have the drivers in a folder and ready to install, but I don't know how when I'm given no indication that the computer even recognizes the gtablets existence.
Any ideas?
Which windows os? 98?
my apologies, I forgot to mention.
I have tried to nvflash on both windows 7 and ubuntu linux but neither OS picked up or detected the presence of the gtablet at all
Have you checked if your usb chord is working? I know, sounds silly. But this happened to me a number of years ago. Really thought it was the computer or my camera. Until I tried another usb chord and voila!
Oh God, wouldn't you know that fixed it instantly. Here I tried everything in the world and it was the USB cable all along. Thanks a bundle man!
When i plug in my phone into the computer and try to manually install the driver it always says that the driver was not found...
i have tried this even in the pc and laptop.
Did you follow the exact steps listed in the sticky in the development section, as well as the recommendation for alternate drivers?
Azed123 said:
When i plug in my phone into the computer and try to manually install the driver it always says that the driver was not found...
i have tried this even in the pc and laptop.
Click to expand...
Click to collapse
If you are taking abut fastboot drivers try this method: http://forum.xda-developers.com/showthread.php?t=1554632
It worked fine for me.
If you are taking about general drivers I don't know, I just plugged the phone and they installed automatically.
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.
Im running Win8 on my PC and want to S-OFF with Racoon. But the drivers in the Racoon Websites are not working with Win8
Any help ?
You need to uninstall all existing drivers and software of your phone from your pc.
You also need to disable driver enforcer signature on your pc.
Then boot your phone Into bootloader and select fastboot, connect your phone into your pc and it should appear on your phone as fastboot usb, nothing will appear on your computer because it has no drivers.
You need to go to device manager on your pc and you would see android 1.0(make sure your phone is still connected).
You need to manually install drivers for it which could be found here( http://forum.xda-developers.com/showthread.php?t=1998650 )
After you successfully install it, everything should work fine and your pc should recognize it on adb or fastboot