Database Users

Rooted KF not started This device cannot start. (Code 10).

Hi,
Could REALLY do with some help here ... starting to pull my hair out. Rooted my KF with the steps from http://forum.xda-developers.com/showthread.php?t=1410766. Got through the root and the process hung on the recovery install.
Now my KF just shows the Kindlefire booting screen. I've tried loads of edits to the drivers re-installed many times, etc ..
In device manager, I see the device as Android Phone / Android Composite ADB Interface. The problem is that the device status always stays at: This device cannot start. (Code 10).
adb returns nothing. It's like I can't connect to the device at all.
Can ayone please help?

i think its stuck in fast boot??

http://forum.xda-developers.com/showpost.php?p=20729347&postcount=5

Tried the various restarts as suggested in the thread. No luck.
Device Manager still has a problem with the device. KFU can't connect or see the device.
I've tried re-installing the drivers several times, but always get the same result. Searched the threads for a similiar problem and it seems most issues are when people get to the the Yellow Triangle page. I'm not getting that far.
Seems to me to be a driver problem, but I can't trick Windows into figured it out.

follow and join this thread:
http://forum.xda-developers.com/showthread.php?t=1413495
i don't want to write everything twice

Still not working. tried that link and everything in it. Been struggling woudl this for a few days now, so any help would be appreciated.

When kf is pluged in right click my computer then click manage then device manager there should be a yellow ! Next to a device. What device does it show next to it
Edit; sorry answers in the question. Lol
Keep it plugged in. Hold down power for 30 secs turn back on
What does your pc say
Sent from my Kindle Fire using xda premium

NewKindleUser said:
Still not working. tried that link and everything in it. Been struggling woudl this for a few days now, so any help would be appreciated.
Click to expand...
Click to collapse
some more information would be helpful
os/bit of computer ?
have you tried to remove the old drivers ?
http://support.microsoft.com/kb/315539/en-us
which drivers have you used ?
in the meantime there is a new kfu available 0.9.2 which has a new driver installer.
http://forum.xda-developers.com/showthread.php?t=1399889
would download it, extract to c:\ and rename to "kfu" cause it don't likes spaces in the pathname - sometimes. run install_drivers.bat
then run the utility with run.bat and try to set bootmode to normal (option 1)
the 3 status messages from kfu may also be helpful for us
this post from vashypooh might also be helpful:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506

Thanks for direction and feedback.
I had previously installed the drivers with kfu 0.8 and 0.9.1.
I'm using Win7 x64 running in a VM (I have a MAC) as well as WinXP 32.
I've downloaded and installed the drivers from the latest KFU. When I connect the KF, it appears under the USB Controllers Group in Device Manager with a Yellow Warning Triangle. KFU cannot connect:
ADB Status: Offline
ADB Rooted: No
Boot Status: Unknown

NewKindleUser said:
Thanks for direction and feedback.
I had previously installed the drivers with kfu 0.8 and 0.9.1.
I'm using Win7 x64 running in a VM (I have a MAC) as well as WinXP 32.
I've downloaded and installed the drivers from the latest KFU. When I connect the KF, it appears under the USB Controllers Group in Device Manager with a Yellow Warning Triangle. KFU cannot connect:
ADB Status: Offline
ADB Rooted: No
Boot Status: Unknown
Click to expand...
Click to collapse
are both win systems running on the mac ?
that will not function - someone ported kfu to mac - will try to find it for you
here it is:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653

The WinXp isn't on the MAC. But the Win7 one is.
I'll try the MAC port as well.

NewKindleUser said:
The WinXp isn't on the MAC. But the Win7 one is.
I'll try the MAC port as well.
Click to expand...
Click to collapse
then you have 2 options:
1. try the mac port
2. use winxp machine and be prepared for a little hassle with the drivers
good luck !

I've seen it show up as unknown USB device before. You can't install the drivers when it's in this state. Usually doing a hard reset on the device (hold power for ~20 seconds to turn off then turn it back on) fixes the device and it will show up as either Amazon Kindle with a yellow exclamation (without drivers) or as ADB Device or some such if you do have the drivers. If it shows up as Amazon Kindle without drivers, install them (right click, update drivers, browse your pc, point it to the drivers folder inside KFU). You should then be able to run KFU option 1 and select Bootmode Normal.
If you can't get that to work, download the android SDK on your Mac, use the SDK manager to download the Android platform-tools, open up a Terminal, cd to that platform-tools directory, and run
./fastboot -i 0x1949 oem idme bootmode normal
Which should get you back in normal mode.

I registered just to say that I thought I had bricked my KF (it was just stuck in fast-boot). I tried all of the driver fix stuff but the Kindle Fire Utility still said that no Kindle could be found. I tried your suggestion, skourg3, and it worked perfectly. (slight addendum for the uninitiated: the command is fastboot -i 0x1949 oem idme bootmode normal).

Kindle fire not seen

Ok so I am new hear and I was reading in THIS POST about installing TWRP using the Kindle Fire Utility. So I installed the drivers as directed and I see in my device manager "android ADB device" and in my taskbar I can eject the kindle. In File Manager I do not see the Kindle fire and the Kindle Fire Utility is not seeing my Kindle Fire. I am stuck and cannot post in the above forum because I have not made enough posts. Any help would be greatly appreciated. I would like to install Cynogen Mod to my Kindle fire to be able to access the full capabilities of this wonderful device.
Thank you

a good method to start is using kfu as you suggested but there are some tricks to get it running:
- place it to c:\ and rename it to "kfu" (it don't like spaces in pathname)
- try to install the correct drivers by running install_drivers.bat else install/update them manually:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
- pay attention on the driver verification level:
http://forum.xda-developers.com/showpost.php?p=22065426&postcount=846
- the drivers are in c:\kfu\drivers\kindle
- right drivers for each mode:
normal & recovery boot -> android composite adb interface
fastboot -> android adb interface
once you got rid of the drivers you have to update the run.bat of kfu to work with burritoroot3:
http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
now you should be good to go ...

Thank you BB3 I will give this a try later tonight. appreciate the help

man install buritoroot and TWRP(which installs and FireFireFire) by yourself when i tried with the kindle fire utility all got were errors, but when i installed it by myself everythink went smooth. Just find separate guide for every step
1.Root
2.TWRP and FireFireFire
3.CM7

I'm having the same problem as you and it sucks I just want to root it

Hate to necro post, but I'm having the same issue and none of the posted suggestions work. I have the ADB drivers installed (the Kindle is detected as "Android Composite ADB Interface"), but I did not install the drivers using the KFU batch file; I could never get it to stop producing the unsigned error, no matter what system settings I chose for unsigned drivers. I ended up doing a manual driver install and directing the installer at the driver files that came with KFU. Now KFU refuses to "see" the Kindle connected to my system and therefore I can't do a thing with it. I am able to browse the Kindle files in Windows Explorer (should I be able to? I've seen conflicting answers to this), but KFU always reports its ADB status as "Offline". Soft disconnecting the Kindle (hitting the "Disconnect" button on the Kindle) doesn't change anything, except removes my ability to browse the Knidle files (no surprise there).
This is a fully updated (6.3) Kindle and Windows XP. I did attempt to manually do what KFU does automagically prior to finding out about KFU, but that effort produced similar results; the Kindle was never detected by the SDK tools, despite the drivers loading properly. I have also tried multiple USB ports on my system, but they all produced the same results. About the only thing I haven't tried is a different USB cable, but if the Kindle is able to be "seen" by the OS correctly, I don't think the cable is a problem.

Have you tryed rebooting your computer? http://liliputing.com/2012/03/root-...ogle-play-store-with-kindle-fire-utility.html or http://m.youtube.com/#/watch?desktop_uri=/watch?v=mwMHIkX20YI&v=mwMHIkX20YI&gl=US nat3mil gives good instruction it helps to watch the video do the step while paused then move onto the next its how I did it the first time the second time I just used the utility was easy peasy cause drivers were already installed and functional

Yeah, I followed those exact instructions and video, with no results. Reboot doesn't make any difference, KFU still can't see the device.

cogadh said:
Yeah, I followed those exact instructions and video, with no results. Reboot doesn't make any difference, KFU still can't see the device.
Click to expand...
Click to collapse
If you followed the instructions to the t like not plugging in your device until you have the drivers installed .then you may have something on your computer preventing adb try the 6.2.2 method
http://m.youtube.com/#/watch?desktop_uri=/watch?v=AZ88CYWv0FU&v=AZ88CYWv0FU&gl=US or just keep looking for something that works cause people miss steps all the time sometimes its persistence or trial and error that gets results I'm very surprised your not seeing anything in device manager that applies to your kindle mine installed some drivers immediately when I connected it I had to change them to root it but it did show up in the list of devices as well as appearing next to my c drive as a kindle for SD card access but I'm on windows seven anything I connect does something.

No, Device Manager sees everything fine, it's KFU that refuses to see it. I am getting both a Kindle storage device and an Android ADB device in Device Manager, as well as seeing the Kindle as a removable drive in Windows Explorer. The old 6.2.2 instructions are of no help, that's what I tried the first time I attempted to root the device before the 6.3 update and I got the same exact results. I don't know what on my machine could possibly be interfering, this is a very barebones XP, I don't even run anti-virus on it.

cogadh said:
No, Device Manager sees everything fine, it's KFU that refuses to see it. I am getting both a Kindle storage device and an Android ADB device in Device Manager, as well as seeing the Kindle as a removable drive in Windows Explorer. The old 6.2.2 instructions are of no help, that's what I tried the first time I attempted to root the device before the 6.3 update and I got the same exact results. I don't know what on my machine could possibly be interfering, this is a very barebones XP, I don't even run anti-virus on it.
Click to expand...
Click to collapse
Could be your machine but don't use the utility and when you do put twrp on if ya get there use 2.0 the older version people are having trouble with the new one http://www.techtuple.com/477/how-to-root-kindle-fire-6-3-easily/ this is done through cmd without utility. Original thread here http://forum.xda-developers.com/showthread.php?t=1568340
About all the advice I can give you all else fails use another computer windows 7 machine things are more straight forward than xp
Edit: just a side note a lot of people are bricking their devices I keep remembering the Christmas story be careful you'll shoot your eye out also some people I believe are having success opening kfu attaching thier fire while off then powering up the kindle

I read somewhere that the utility doesn't work for xp wish I could find the post I think you need to push the files the old way using command prompt and you will get it sounds like your drivers are there but utility is useless

If your device isn't recognized it is a driver issue, regardless of whether your computer says they are installed or not.
Scrap your current drivers and start fresh using the tutorial posted here:
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Forget about KFU, get Android SDK and set up the drivers yourself. Learn to use fastboot to manually change your bootmode manually through command prompt. It will save you hours of heartache in the future.
Reinstall your (non KFU) drivers and try again.
Sent from my Amazon Kindle Fire using xda premium

Thanx soup better said than what I was trying

if you want to test to see if your drivers and adb are correctly installed plug your kindle in to your computer type cd c:\kindleadb then hit enter then type adb devices hit enter mine said adb server out of date. killing...
*dameon started successfully*
list of devices attached
42220600000000001 device
c:\KindleADB>
this is all in command prompt at this point I could paste in commands and root my kindle run this test to verify drivers are correctly installed if you dont see this try again on driver installation.

First time i've ever rooted a kindle and i had the same problem.
To fix this just go to device manager and uninstall the driver and then unplug and replug in your kindle then run the utility.

oh no trouble at all rooting rooted rommed and rockin here took the 6.3 ota this morning with 5 mins I was rooted with fff twrp then went back to 1 of my restore points of cm7 after a backup of 6.3 thanx tho

soupmagnet said:
If your device isn't recognized it is a driver issue, regardless of whether your computer says they are installed or not.
Scrap your current drivers and start fresh using the tutorial posted here:
Forget about KFU, get Android SDK and set up the drivers yourself. Learn to use fastboot to manually change your bootmode manually through command prompt. It will save you hours of heartache in the future.
Reinstall your (non KFU) drivers and try again.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
If all newbs do no other work but learn to use fastboot and adb it would save save a lot of grief for them and the ones helping them. jes sayin..

Thepooch said:
if you want to test to see if your drivers and adb are correctly installed plug your kindle in to your computer type cd c:\kindleadb then hit enter then type adb devices hit enter mine said adb server out of date. killing...
*dameon started successfully*
list of devices attached
42220600000000001 device
c:\KindleADB>
this is all in command prompt at this point I could paste in commands and root my kindle run this test to verify drivers are correctly installed if you dont see this try again on driver installation.
Click to expand...
Click to collapse
This will only work if the device is booted to a point where it will receive adb commands. Otherwise, use "fastboot devices". Sometimes if you are stuck at the bootloader it helps to shut your device down completely and restart before issuing fastboot commands.
Beyond that, it's a driver issue.
Sent from my Amazon Kindle Fire using xda premium

I had that same problem., but then I uninstalled the current drivers for my kindle altogether, and disabled them, then I ran install_drivers .bat again, then it worked.
Kindle Fire running KANG CM9
New developer, working on my own custom rom

[HELP]Bricked kindle fire very hard

i bricked my kindle fire ... like flash update.zip and then my fatal mistake i reboot kindle then i was bricked so hard please help me

a bit few information !
what exactly have you done ?
what display on kf ?
fff & twrp installed ?
kfu available ? - and moved and renamed to c:\kfu ?
status in device manager ?
os/bit ?

i install update.zip from kindle fire utility
then i reboot. it sticks on second kindle fire logo whit lower light ,no TWRP,no fff

that means you tried to restore it to pure stock
do you want to return it ?
if not gimme a pm and we can try to get to fastboot mode - reinstall fff & twrp - then it's possible to reinstall a rom of your choice
if it's not possible to get to fastboot then you'r up to a factory cable - sorry

can u give me skype on pm i will show you

Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw

Sweetoz97 said:
Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4

Sweetoz97 said:
Hey i have a sort of similar problem but i had installed MIUI 4 on my kindle fire 6.2.2 and now it is bricked. Im stuck on the yellow triangle and cannot go into recovery mode. also my usb doesnt work and my device wont show up as kindle, only android phone. Someone plzz help. Im new btw
Click to expand...
Click to collapse
Follow the following after you KF to your PC:
Adb kill-server
Adb start-server
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Good luck
Sent from my Amazon Kindle Fire using Tapatalk

I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?

josh24923 said:
I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?
Click to expand...
Click to collapse
Try to use KFU to install Windows driver and changing the booting mode to normal
Sent from my Amazon Kindle Fire using Tapatalk

josh24923 said:
I have had the same problem, but I think mine lies in the drivers. I have been trying to get Windows 7 x64 to recognize my KF as anything, but a mass storage system. It says that the usb driver that comes with SDK isn't compatible with any of the sub devices listed under Kindle fire in Devices and Printers. I'm about ready to toss the KF to the side and buy an iPad if I can't get this working.
Anyone got any ideas to get the drivers working?
Click to expand...
Click to collapse
maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
furthermore check the adb_usb.ini in the .android folder in your personal folder
it should include 0x1949 (and i use to add 0x18d1 also)
would not use the sdk at all - you can save a lot of space and the drivers of the sdk don't have all the necessary entries
the sdk also messes around with the adb_usb.ini and deletes your allready made entries
would recommend to use kfu only (like in the linked in post) - you don't even have to run it but:
- the drivers are in c:\kfu\drivers\kindle and have all necessary entries
- the tools directory (c:\kfu\tools) has all commands you'll ever need (you can run all your adb and fastboot commands from here manually)

I'll try these suggestions out. I've done a wide array of changing in the .android fold and keying in the 01x.... but it hasnt been to any avail. I'll try it in the order that you've introduced.

I've tried the above mentioned and was looking in the actual driver android_winusb file and I can see that the hardware id listed on it and the actual hardware id that my kindle shows are different. It has the same VID but the PID ends in 005 instead of the 006 that is supposed to.
So I created a copy of this and altered the driver file to reflect the PID as 005, and was able to get the driver file to eventually show up as an ADB Device in the hardware description with the driver, but it still would not interact with ADB itself.

adb_usb.ini usually reflects the vid only and is necessary for adb to work
the only other vid's i'hv read that some had success are 0x006 and 0x0e79
you may add them also to adb_usb.ini - if it don't help it don't harm
furthermore would recommend to kill the adb server every time if you have changed something at the drivers with "adb kill-server"

So far, I've gotten Windows to recognize the kindle as and ADB device. Trying to get the .android file to reflect the change hasn't worked at all. The VID isn't really much of and an issue. It's the PID that seems to be different from any post that I have seen. I wish that I could force ADB to recognize the connection, but that's a bar above me. I'm an amateur at best compared to some of the people.
I'm really vying on the power of XDA here; because, this problem is so similar to the other issues that are similar with the driver issue, being stuck at the kindle fire homescreen. However when I tried the update in twerp of the update.zip file, it somehow screwed the pooch on my adb. I have a backup both on the kindle and my computer. I just can't do anything until I get ADB to recognize my KF.

maybe give firekit a try ? no windows - no drivers
http://forum.xda-developers.com/showthread.php?t=1430038

Try to use another computer. If this impossible, Install new Windows in VMWare and connect Kindle to virtual machine. Then use KFU.

Well, I've tried firekit, and ubuntu wouldn't even recognize my kindle fire... I'm half tempted to use the usb trick, but I really dont want to start taking the kindle fire apart if i dont have to.

Tried a different computer and still have had no luck whatsoever... I'm really getting discouraged and think this is something that might not be fixed solely with a keyboard and basic ingenuity. I just hope I dont have to buy another kindle.

josh24923 said:
Tried a different computer and still have had no luck whatsoever... I'm really getting discouraged and think this is something that might not be fixed solely with a keyboard and basic ingenuity. I just hope I dont have to buy another kindle.
Click to expand...
Click to collapse
What exactly do you see when you start up your KF? The stock "kindle fire" logo or the yellow triangle logo? Does the screen ever go black before getting "stuck" on the logo?
If all you ever see is one of these logos without it ever going black, it's in fastboot mode. You'll never get adb to recognize your KF in this state regardless of what drivers are on your machine. adb will only see your device when it's in recovery or booted into the OS. In fastboot mode, you can only issue fastboot commands to the KF.
You say in post #15 that you've gotten Windows to recognize it as an ADB device. What device is shown in the the device manager when you connect it? Please be specific.

[Q] Working with ADB & Fastboot

Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!

feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.

feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?

Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!

feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly

[PSA/FIX] Newest adb doesn't work on WinXP + 5x USB drivers that work

I happen to update platform-tools in the Android SDK from version 23.1 to version 24 on an older PC.
The newest adb.exe included with v24 no longer works on WinXP.
You will get the following error upon startup:
adb.exe - Entry Point Not Found
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.
Click to expand...
Click to collapse
In case anyone is curious, I tracked the change down to this one:
https://android-review.googlesource.com/#/c/203387/
ADB
I've attached the v23.1 adb and fastboot to this post in case someone needs the previous version (which works fine with 5x up to at least MTC20F)
Just unzip and you can use adb/fastboot from the resulting platform-tools-v23.1 directory or copy them over to where your normal platform-tools directory is.
USB drivers for 5x
I also included USB drivers that work with 5x. These should work for 32/64-bit for winxp and vista. Win7 is maybe, haven't tested.
They WILL NOT work with win8 and above due to changes in driver enforcement. I am not sure about win8.x but on win10, there is a built-in driver that works with adb. To get bootloader/fastboot driver, just allow win10 to search for drivers. It will load Marshall London Bootloader Interface. This is for a different phone from music company Marshall, but it works fine since it is an Android-based device.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.

Not sure if it matters to that many people these days, but it was confirmed the change in adb is not a bug and will persist going forward, so if you ever need to run adb on a WinXP box or emulator, you'll need to retrieve platform-tools-23.1 or earlier.

WinXP compatible platform-tools also could be downloaded from official repository:
http://dl-ssl.google.com/android/repository/platform-tools_r23.1.0-windows.zip

Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.

Greefus said:
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Click to expand...
Click to collapse
Actually Windows 7 is still installed on nearly half of all desktop and laptop computers: https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0. Did the most recent SDK drop support for it?

For anyone who wants to use adb on the latest version of Android Studio running on Windows XP use the adb .exe from version 23 and paste it into the platform tool folder. Keep a copy of the new adb.exe just in case you need it. No need to use the entire v23 platform tool folder.

The references in this thread have so far appear to refer to latest adb compatibility, particularly for Windows XP.
Does the latest fastboot still work fine with Windows XP? If not, what was the last known-good or thought to be last known-good version for Windows XP?

Hi
The adb from the v2.3.1 works fine with my win xp, thank you for the file.

Hello,
I am another WinXP user facing the error
"adb.exe - Entry Point Not Found. The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll."
@sfhub & @Sintetix
Thanks for the info and provide the latest version supported by XP ...
Are you aware of any important changes / additions in the future versions to be concerned of?
Regards
---------- Post added at 11:16 ---------- Previous post was at 10:47 ----------
Just to let you know,
C:\v23.1>adb devices
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:
I am trying to connect an Asus Transformer tablet with "MTP file transfer" mode on WinXP Service Pack 3 laptop... cable is fine and the plan is to move from custom ROM (Android 6.0) to Stock (JellyBean) ... Something I already did few years ago having Win10 (I have the receipe used then)
I think I better get a fresh Win7 on my primary Win10 PC and start from there... I never liked W10 anyway ... and since I did mods to [finally &effectively] stop the [annoying, unwanted & plenty of bugs] Win10 updates ... I got funny errors when using dev stuff ... even DotNet ...
And I need to think a better O.S for the XP PC ...
Time to change. Regards

Before jumping to my major O.S actions,
I gave a chance to my Asus Transformer tablet with another cable under the W10 PC and the latest adb (r29.0.2-win) and this second time it worked fine ...
The first time and first cable did not work (reason that drove me to the WinXP PC thinking the cause was Win10)
fastboot devices
was literally returning
???????????? fastboot
But this second time with another cable
fastboot devices
returned
BLAxxIDxxSTRING fastboot
And I was finally able to perform the format and flash series of commands to return my tablet to the stock ROM ...
As I understand this thread is about WinXP, for testing purposes, I hooked my fresh flashed tablet to the WinXP PC with the successful spare cable, and
adb devices
got again
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037
Certainly I don't have the explanation of this, but I can tell you is not because a faulty cable or something related to the tablet.
And something scary to add: the first cable looks in good shape and is the one used every day to charge the tablet without any delays or issues ...
Hope someone find this useful and provide more insight. Regards