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
Hello,
This must be a dumb question because all the guides seem to skip over this part but I'm having trouble installing the Windows 7 drivers. I downloaded the drivers, connected via USB, right clicked on the Android 1.0 in the device manager and updated the drivers. Everything seemed fine. Then I boot into fastboot and get a "Drivers were not installed successfully" pop-up.
I thought maybe I messed up and was supposed to install the drivers while in fastboot rather than while the phone was all the way booted up. So I rebooted the phone, uninstalled the drivers, booted in fastboot and tried to install the drivers while in fastboot. When I try it this way I right click on Android 1.0 in the device manager, go to the update driver option, select my file (there are two files in the driver folder I downloaded, androidusb and htcrndis, I tried them both) and I get an error before it can finish installing the driver. It says:
Windows found driver software for your device but encountered an error when trying to install it:
HTC Remote NDIS based Device
This device cannot start. (Code 10)
I'm sure it's something simple but I cant figure it out. Thanks for any help.
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.
I Have a Nexus 7 and recently I found that I needed to use ADB for something and I had used my Nexus 7 with ADB on this computer before (thats how I installed KitKat) but whenever I connect my Nexus now it says that is not configured correctly and when I attempted to install the ADB driver it said windows encountered an error. I am currently running windows with Driver verification disabled and on test mode. I am also running windows in test mode so that it wouldn't block the driver. I have tried every driver possible from the one in the SDK to the intel android adb driver and even PDAnet. I have checked inside the driver file that it is properly registered for my nexus 7. I am running Windows 8.1 on my computer and android 4.4.2 kitkat on my Nexus 7. Could anyone please help?
I have already tried
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
http://forum.xda-developers.com/galaxy-nexus/general/tutorial-installing-adb-fastboot-t1982718
Since Lenovo has no intention of updating the A8-50 5500-F ideatab to Android 5.0, I've been looking to root the tablet and throw a new ROM on there. I've seen a couple forum posts on here and done some research and the steps to begin this are pretty much agreed upon with everyone.
1) Enable debugging mode
2) Install drivers
3) Use (Enter root program here)
4) etc.
The problem is happening at the first couple steps. If debugging isn't enabled on the tablet, my computer can see it. It accesses the device's data without issue and Device Manager shows a good driver installed. When I switch it to debugging mode, it loses access to the tablet's data and device manager says the device doesn't have any drivers installed. Also, software like Lenovo Smart Assistant and Kingo ROOT think that the device isn't in debugging mode when it is and keep saying to make sure debugging is enabled. Here's what I've tried so far to mitigate it and where it fell through:
XDA Forum: All about - Lenovo A5500 - When I try to use the drivers provided, Windows states that there are no drivers available in the folder I tell it to look from.
XDA Forum: [TOOL][WINDOWS]ADB, Fastboot and Drivers - The install completes, but when I try to copy the steps provided here, there is no ADB selection.
XDA Forum: [ROOT] Framaroot... - I get error #9 which means it won't work for my device with it's current version when I try to use Borimir.
Youtube: Install driver for Android Tablet - The AdbDriverInstaller software doesn't actually see the device when I plug it in. This is either in or out of debugging mode. Pretty much the same issue I mentioned above with Kingo ROOT and Lenovo Smart Assistant.
Additional steps:
Downloaded SuperSU from the Play store - I get the error "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Downloaded Superuser from the Play store - There's just no apps in the list
I'll keep looking, but I seem to have run out of ideas myself and what I can find in my research is just starting to repeat itself. Has anyone seen this before? I'd really appreciate any help.
Edit: Might help if I include the current device info...
Device Information:
Model Number:
Lenovo A5500-F
Android version:
4.4.2
Kernel version
3.4.67
Build number
A5500F_A442_000_029_150408_ROW
http://www.kingoapp.com
Kongo root works somehow. Not sure about a ROM though?
I used KingRoot (ver 4.8.2) to root my Lenovo Tab2 A8-50F Tablet.
I used KingRoot as part of a SuperTool. The SuperTool, using a batchfile script, also removed KingRoot after the tablet was rooted and then installed SuperSU.
The SuperTool (April 6, 2016 version) was created by xda's RootJunky for the Amazon Fire 7 5th gen tablet, using KingRoot and SuperSU, but it rooted my Lenovo Tab2 A8-50F Tablet, uninstalled KingRoot and installed SuperSU, all with only a couple of mouse clicks.
Even if you are already rooted with KingRoot, you can use this tool to uninstall KingRoot and install SuperSU. (Just run the tool, let it re-install KingRoot, don't run KingRoot but hit Enter on the SuperTool to then uninstall KingRoot and install SuperSU).
Lenovo Tab2 A8-50F Tablet info:
Model Number: Lenovo TAB 2 A8-50F
Android version: 5.1
Kernel version: 3.10.65
Build number: A8-50F_S000037_151023_ROW
Software version: A8-50F_151023
Hardware version; LenovoPad A8-50F
The SuperTool batch file script rooted the tablet with KingRoot and then uninstalled KingRoot and installed SuperSu.
I have since installed ES File Manager, Titanium Backup, Link2sd on the tablet. Root is totally working. Rooted with only a couple of clicks!
Just enable Developer options on Lenovo Tab2 A8-50F (by tapping tablet Build Number 7 to 10 times [Settings, About Tablet, Build Number (tap 7 to 10 times)]), enable USB debugging on Tablet in the Developer options settings.
Connect Tablet to Windows 10 with a USB data cable (I used the USB 2.0 port). When screen message on the Tablet mentions connections, make sure it is in the MTP mode.
Extract RootJunky's SuperTool Zip file to the Windows 10 desktop.
Run RootJunky's SuperTool (Amazon-Fire-5th-gen.bat) You may have to read the instructions on the pages below and install adb drivers. Pick option #6 Root. Choose Option #3: version 5.1.2. This will run a script that installs KingRoot, allows you to run it manually, and then removes KingRoot and installs SuperSU.
Press enter and KingRoot will be installed on the Tablet from the SuperTool. (approve any messages that appear on Tablet screen) Now don't touch the PC SuperTool until the Tablet is rooted.
Open KingRoot on the Tablet and run it. You may have to run KingRoot several times and the Tablet may reboot. Just keep running KingRoot until the Tablet is rooted. After KingRoot reaches 100%, then press ENTER on the PC.
The SuperTool will now uninstall KingRoot and install SuperSU on the Tablet.
Choose NORMAL SuperSU install on the Tablet when prompted. When SuperSU is installed, reboot the Tablet. Disconnect data cable.
After reboot the Lenovo Tab2 A8-50F Tablet is rooted. There will be a request by SuperSU to upgrade. Approve it. You can now install Titanium Backup, Link2sd, ES File Manager, etc. Your Tablet is rooted. As easy as that. THANKS ROOTJUNKY!!!
Info and links to Download RootJunky's SuperTool at these pages:
Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
"AmazonFire5thGenSuperTool.zip" 2016-04-06 version
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool