Develop Bugs

adb drivers in Win7 64

I have no problem connecting my Epic 4G Touch to a WinXP system with adb.
On Win7 64, I installed Kies, but when I plug the phone in, I am told that no drivers for CDC Serial and SAMSUNG_Android were found. And "adb devices" finds nothing.
I can mount the device just fine for transferring files. But I need adb for software development.

arpruss said:
I have no problem connecting my Epic 4G Touch to a WinXP system with adb.
On Win7 64, I installed Kies, but when I plug the phone in, I am told that no drivers for CDC Serial and SAMSUNG_Android were found. And "adb devices" finds nothing.
I can mount the device just fine for transferring files. But I need adb for software development.
Click to expand...
Click to collapse
Unless you're going to use it, I would uninstall KIES. Having it running in the background can mess up other functions like flashing with odin. I would just install the Samsung Drivers by themselves. It worked for my adb install in windows 7.
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe

tdunham said:
Unless you're going to use it, I would uninstall KIES. Having it running in the background can mess up other functions like flashing with odin. I would just install the Samsung Drivers by themselves. It worked for my adb install in windows 7.
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Click to expand...
Click to collapse
Just did that. Uninstalled KIES and tried to install the driver package. Driver installer says: "The MSS Installation for SAMSUNG USB Driver for Mobile Phones V1.3.2360.0 has failed."
Were you using 64-bit Win7?

arpruss said:
Just did that. Uninstalled KIES and tried to install the driver package. Driver installer says: "The MSS Installation for SAMSUNG USB Driver for Mobile Phones V1.3.2360.0 has failed."
Were you using 64-bit Win7?
Click to expand...
Click to collapse
Uninstall all your drivers from device manager and start fresh. Only install the driver.exe from samsungs support page. Once that is installed plug your phone in and let it run through the drivers before you try anything else.
If your computer isn't recognizing your phone in the first place then it's not a problem with adb, its the drivers, so start there.

OK, so I uninstalled KIES and the drivers.
I then tried to install the drivers. No go: The installer continues to fail, with the progress bar at around 80-90%. I experimented with running the installer as administrator, installing off of \Program Files (x86) and off of \SAMSUNG, instead of the default \Program Files, and still no go.
I then re-installed KIES, turned off debug in the phone, and plugged it in. Win7 installed a driver for the phone and all was well.
I then unplugged the phone, turned on debug, and plugged it back it. Now Win7 installed the following drivers:
Code:
USB Composite Device
USB Mass Storage Device
Android UMS Composite USB Device (two of these!)
and said they're ready to use. But it also tried to install:
Code:
CDC Serial
SAMSUNG_Android
and it gave "Driver not found" for these.
And "adb devices" lists nothing.
To make sure adb works fine I then plugged in a Kindle Fire. Windows set up the drivers for it and it showed up in "adb devices" just fine.

I still can't get it working.
I even tried using the advice I saw on some blog to use the Device Manager, and then update the non-working devices by directing Windows to look in the "\Program Files (x86)\SAMSUNG\USB Drivers" directory for drivers. No effect--Windows says it can't find an appropriate driver there.
The 25_escape\ssudadb.inf file seems to contain stuff with hardware IDs that match the device that Windows can't find a driver for. BUT there is no x64 section in the inf file. Is there supposed to be one?
I even tried turning off Windows' driver signature checks. Didn't help.
Does anybody have this working 64-bit Win7?

arpruss said:
I still can't get it working.
I even tried using the advice I saw on some blog to use the Device Manager, and then update the non-working devices by directing Windows to look in the "\Program Files (x86)\SAMSUNG\USB Drivers" directory for drivers. No effect--Windows says it can't find an appropriate driver there.
The 25_escape\ssudadb.inf file seems to contain stuff with hardware IDs that match the device that Windows can't find a driver for. BUT there is no x64 section in the inf file. Is there supposed to be one?
I even tried turning off Windows' driver signature checks. Didn't help.
Does anybody have this working 64-bit Win7?
Click to expand...
Click to collapse
Have it working - and did remember I have Kies installed.
Maybe I downloaded both the separate driver and Kies?
USB Driver Link:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Kies Link:
http://org.downloadcenter.samsung.c...0111012045653670/KiesPC_2.0.3.11082_152_4.exe
Know I have problem still with Kies... but I can use ODIN without issues.

Finally got it!
I can't really explain how I did it, as there was a lot of trial and error and I wasn't keeping notes. But the basic trick was to right click in device manager on the unknown SAMSUNG_Android device, choose Update Driver, choose "Let me pick", choose "Have disk", point to the "SAMSUNG\USB Drivers\25_escape" folder from the KIES installation, and then choose "Samsung Mobile USB Composite Device".
You may then get another unknown device, which using the same method you set to ADB. I did a bunch of stuff in different ways, trying to match different drivers from the 25_escape folder to different devices, until it finally worked.

Same issue, solved twice
I have had similar problems in win7 64bit twice now. I got it working once, then ended up reinstalling windows for other reasons. I then had the same problem when trying to install cm9alpha3.
Both times it took a strange combination of installing the drivers manually, plugging in the phone, etc. to get it working. The best advice I have for others is to keep trying.
Also, it seems that Kies almost never gets it right. I personally don't even keep it installed.

I posted a guide on how I got this working.
adb works, but I still can't connect to KIES.

arpruss said:
I posted a guide on how I got this working.
adb works, but I still can't connect to KIES.
Click to expand...
Click to collapse
What Rom are you on. I had same problem with phone running on Calks E4GT v. 3.0 GB Rom, Kies won't recognize Calks Rom, wifeys stock Epic is recognized no problem . Pc Asus G73 win7 64. PC recognizes my phone but Kies won't.
Pp.
Edit
It is rumoured that Kies w will only recognize stock roms.
Pp.
Sent from my tofu plasma converter.

PanchoPlanet said:
What Rom are you on. I had same problem with phone running on Calks E4GT v. 3.0 GB Rom, Kies won't recognize Calks Rom, wifeys stock Epic is recognized no problem . Pc Asus G73 win7 64. PC recognizes my phone but Kies won't.
Pp.
Edit
It is rumoured that Kies w will only recognize stock roms.
Click to expand...
Click to collapse
I am on stock EL29, no root.
It worked once on my WinXP system, but now it doesn't work on either the WinXP or Win7 system.

Oops. I misunderstood the KIES error message to mean that I'm supposed to have the phone in adb mode for KIES to work. But actually adb mode needs to be off for KIES to work. Now it works fine.

arpruss said:
Oops. I misunderstood the KIES error message to mean that I'm supposed to have the phone in adb mode for KIES to work. But actually adb mode needs to be off for KIES to work. Now it works fine.
Click to expand...
Click to collapse
hi, I have same issue with you now, can you teach me how to solve it? thanks.
WIN7 x64 with GT-I9300

Just turn off USB debugging and Kies will connect.
Sent from my SPH-D710 using Tapatalk 2

Chrome DevTools Inspect working again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I couldn't get Chrome Dev Tools to remote debug (chrome://inspect) until I installed the "Android Composite ADB Interface" (just picked the latest version). See screenshot attached (taken before I installed correct driver).
1. To install I right-clicked on the "SAMSUNG_Android" driver under "Other Devices" in the Device Manager.
2. "Update Driver Software..."
3. "Browse my computer for driver software"
4. "Let me pick from a list of device drivers on my computer"
5. Select "Samsung Android Phone"
6. Select "Android Composite ADB Interface Version" (latest one)
7. Ignore warning that Windows does not know if this driver is compatible.
At this point, I saw the "Trust this device" message come up on the Samsung phone
Thanks for the help. This was really killing me as I had tried everything including installing the official drivers from Samsung's site (developer.samsung.com/technical-doc/view.do?v=T000000117)
Note: I don't have Windows Kies installed and I am using Windows 7 x64 OS. Also note that this does not fix the "CDC Serial" error, however, this is not required for remote debugging over USB.

[Q] KFU Online, Boot Unkown, Drivers Working, TWRP Vanished.

I had a working Kindle Fire. Made a Backup of my OS/ROM using TWRP. Moved that to my Desktop.
Formatted and Installed Stock 6.xx
Rebooted...And now i'm in a static Kindle Fire Logo
Tried Fast (5001), Recovery (4002), Normal (4000)
KFU and Plain adb did not help.
When plugged in.. Green Light, Unplugged No Light.
"If it's not broken, Don't fix it." - My Mom
*Face Palm*
Edit* I tried fastboot oem idme bootmode 4000
Just keep saying < Waiting for Device >
Everything says < Waiting for Device >
It will reboot on Command, but after reboot it does < Waiting for Device >
Iv also seen a post with a Pic and it showed ABCDEF1234567 (Or something like that) when I type adb Devices
Mine says 2DDA002600000001
Edit**
"fastboot -i 0x1949 oem idme bootmode 4000"
&
"fastboot -i 0x1949 reboot"
< Waiting for Device >
I love a fix before Monday (24 Hours From Now)
I really Do not want to buy a Graphing Calculator or Hall Collage / High School Books around.

Looks like we have a similar issue. See my thread over here http://forum.xda-developers.com/showthread.php?t=1838201
There might be something that works for you but not for me.

fixed by monday hmm dont think so http://forum.xda-developers.com/showthread.php?t=1392693 you need fff and twrp back on your device after flashing stock ... did you wipe before flashing it? doesnt sound like it

Believe it or not, your problem is as "simple" (sarcasm implied) as fixing your drivers so the computer can communicate with the device in fastboot mode.

More Help is Needed
soupmagnet said:
Believe it or not, your problem is as "simple" (sarcasm implied) as fixing your drivers so the computer can communicate with the device in fastboot mode.
Click to expand...
Click to collapse
How would I go about fixing my Drivers?
I used Device Manager and uninstalled anything related to the Kindle.
I stopped windows from updating it and installed KFU's Drivers.
*Edit Do I need SDK Installed? Iv just been using KFU.
Ill install anyway.
I also Modded my adb_usb.ini (Or something like that)
**Edit I read a reply you made on another Thread.
Code:
adb shell mkdir /data/local/tmp
[/QUOTE]
Failed
Ill stick with the Drivers for Now as you said.
I tried the Push commands and that works. But any Adb Shell commands does nothing.
Can I push a new Adb Shell or Push FFF (What ever that is) or TWRP and go from there?
I was able to push a fbmode file

Chat_Ghosty said:
**Edit I read a reply you made on another Thread.
Click to expand...
Click to collapse
that was involving a completely unrelated matter
http://forum.xda-developers.com/showpost.php?p=26255153
That post describes how another user fixed the same problem.

soupmagnet said:
that was involving a completely unrelated matter
http://forum.xda-developers.com/showpost.php?p=26255153
That post describes how another user fixed the same problem.
Click to expand...
Click to collapse
I did that to a T.
*Edit: I dont thank this matters. But...
If I turn on the kindle it does one of two things.
#1. Shows KF Logo Bright, Then Dem, Then Bright, then two Green squares apeare on the top and bottom right for 0.2 of a Sec and disappear.
#2. Shows KF Logo, then No Screen and Green Light turns off and screen and light turns back on.
I also included a Picture of KFU.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

have you tried removing the drivers and re-installing them ... i know that it is a pain but it helped me out
Follow http://support.microsoft.com/kb/315539
Open CMD
Code:
set devmgr_show_nonpresent_devices=1
then
Code:
start devmgmt.msc
In device manager do view -> show hidden devices
then remove anything labeled kindle or android adb / android composite
Use KFU install_driver.bat and then play around with KFU to see what happens...

Improvement
Zlatty said:
have you tried removing the drivers and re-installing them ... i know that it is a pain but it helped me out
Follow http://support.microsoft.com/kb/315539
Open CMD
Code:
set devmgr_show_nonpresent_devices=1
then
Code:
start devmgmt.msc
In device manager do view -> show hidden devices
then remove anything labeled kindle or android adb / android composite
Use KFU install_driver.bat and then play around with KFU to see what happens...
Click to expand...
Click to collapse
I did what you said just now and things are now changed.
In Device Manager now says Android adb Interface.
It did say Android adb Composite Interface (Or something like that)
Nothing shows up in adb Devices
KFU Still does nothing and shows nothing.
Ill try some boot commands and see what happens.

Chat_Ghosty said:
Ill try some boot commands and see what happens.
Click to expand...
Click to collapse
It probably won't do any good. You need good communication between the device and your computer (drivers) before anything significant happens. Yes, it's a pain (thank Microsoft), but short of using a different computer or another operating system altogether, it's your only option.

soupmagnet said:
It probably won't do any good. You need good communication between the device and your computer (drivers) before anything significant happens. Yes, it's a pain (thank Microsoft), but short of using a different computer or another operating system altogether, it's your only option.
Click to expand...
Click to collapse
Ill try my Aunts computer. I have never hooked up my Kindle to it.
Ill even install Ubuntu it that will make it work. Ill do just about anything,

Just remember, Linux isn't "plug-n-play" like Windows is. In addition to installing drivers, you have to set up your udev rules and make sure you have all of the appropriate libraries and packages installed, which can be complicated for some users. Luckily there's Google.

soupmagnet said:
Just remember, Linux isn't "plug-n-play" like Windows is. In addition to installing drivers, you have to set up your udev rules and make sure you have all of the appropriate libraries and packages installed, which can be complicated for some users. Luckily there's Google.
Click to expand...
Click to collapse
Honestly. What is the fastest and easiest way to fix this?
Ill re-install my OS if I have too.
Will a Factory Cable Work? Illl buy one.
*Side Note - Iv really only used windows. I fix computers, Build, and some light programming if needed. I don't have much money.*
Thank You for your help so far.

Chat_Ghosty said:
Honestly. What is the fastest and easiest way to fix this?
Ill re-install my OS if I have too.
Will a Factory Cable Work? Illl buy one.
*Side Note - Iv really only used windows. I fix computers, Build, and some light programming if needed. I don't have much money.*
Thank You for your help so far.
Click to expand...
Click to collapse
First of all, the factory cable, while it's extremely useful and nice to have, just in case. It won't help you if you can't get the computer to detect properly. If you know someone with a Mac that would be willing to use it for this purpose, it's likely that would be the easiest route. Linux isn't THAT complicated, just different, and you need to be comfortable using the command line, but it is the most likely to work out of all of them.
As far as reinstalling your OS, there are no guarantees that it will fix the problem, only improve your chances. I'm not going to be the one to tell you it's a good or bad idea either way.

I looked into Linux and FireKit. I do not have a Flash Drive but I did some cds.
Took me a few but I got the basics down for Terminal.
I tryed "Sudo ./fk" & "Sudo ./normal_boot"
But it keeps saying no fastboot.
So I downloaded Kindle Fire Utiltiy and placed FireKit in KFU and still nothing.
I understand it says to use Flash Drive. But is that a must??
I looked on Google and YouTube for a How-To and Nothing,

Short answer...yes.

Chat_Ghosty said:
I looked into Linux and FireKit. I do not have a Flash Drive but I did some cds.
Took me a few but I got the basics down for Terminal.
I tryed "Sudo ./fk" & "Sudo ./normal_boot"
But it keeps saying no fastboot.
So I downloaded Kindle Fire Utiltiy and placed FireKit in KFU and still nothing.
I understand it says to use Flash Drive. But is that a must??
I looked on Google and YouTube for a How-To and Nothing,
Click to expand...
Click to collapse
Have you tried to charge the kindle for a whole day with a wall charger? I found it that ever time I had to screw around with a KF, it was much easier to get stuff done with it fully charged.
Per my earlier comment, deleting old drivers somehow also fixes some issues. Try charging your kindle with the wallcharger, get a good microUSB cable and start anew. It took me 3 computers and about 5 hours to get my third KF rooted and booted.... KF:never again

Use this http://forum.xda-developers.com/showthread.php?t=1850038 mint mate 13 32 bit and pendrive universal usb installer cds wont cut it like this will usb sticks are cheap like 5-8 dollars and your set

Thepooch said:
Use this http://forum.xda-developers.com/showthread.php?t=1850038 mint mate 13 32 bit and pendrive universal usb installer cds wont cut it like this will usb sticks are cheap like 5-8 dollars and your set
Click to expand...
Click to collapse
I got a friends Two GB laying around here somewhere. I just need to find. I might just take my Laptop over there this Sunday.
I broke my Kindle Fire Wall Charger. But they are 5v DC. So I cut a Computer PSU and added a MicroB and shorted the PSU to run with out a computer. I can add a tutorial if wanted.
*Note - Computer PSU is a great stable 3.3, 5v, 12v DC Power. And High Amps. Warning! They will kill you.
Example. My PSU does 2.5A @ 5v. You need 0.01 Amps to kill you. That's 2,500x whats needed to kill you.

I installed Ubuntu on my Computer, I then Installed the :idiot-proof" and adb works.
Any command I type from the List I get eather <Waiting for Device> or waiting for OMAP44xx device

[Q] KF drivers work but still cant get ADB working?

I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks

xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1552547
The second post will help you to get your device drivers in order.

xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
Which version of KFU did you try running.. suggest you try the KFU 0.9.6

my drivers are working. when i plug my KF in i see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
im also using 0.9.6
i plug my kf into my pc, that above screenshot is what i see so i dunno whats going on?

Did u run the first option to reset the boot mode to normal or fast..
If u run this option u can set ur boot mode appropriately and then root it using option 2 which is burrito root installation
Sent from my MB526 using Tapatalk 2

kinfauns said:
http://forum.xda-developers.com/showthread.php?t=1552547
The second post will help you to get your device drivers in order.
Click to expand...
Click to collapse
kishorev said:
Did u run the first option to reset the boot mode to normal or fast..
If u run this option u can set ur boot mode appropriately and then root it using option 2 which is burrito root installation
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
no i never did that...how do i got about that? im horrible at this, apologies.

xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
I'll see if I can help. The description of what you are seeing in the device manager "android adb interface" matches the picture in the upper right box in the table you posted. That is the fastboot driver, look at the description in the left column of the table. ADB doesn't work with the fastboot driver. You need to keep playing with drivers until you get the "normal" ADB driver working, see the listing in the lower right box of the table. The word "composite" must appear in the driver description for your computer to recognize your KF as an ADB device. KFU includes and installs both drivers but windows is easily confused and frequently uses the wrong one. Personally I think it is because the KF goes through different modes as it boots up and windows isn't accustomed to a device changing modes, but that is just my guess.
Sent from my Amazon Kindle Fire using xda premium

xXezmacXx said:
no i never did that...how do i got about that? im horrible at this, apologies.
Click to expand...
Click to collapse
Have uploaded some screenshots for you on checking your driver and also how to run ur KFU
Let me know if u were able to succeed

i try adding the drivers again and it says its up to date already. i have no idea what im doing wrong but im sure is something easily fixable. should i press "disconnect" when i plug the kf in or should i leave usb cable screen up?

xXezmacXx said:
i try adding the drivers again and it says its up to date already. i have no idea what im doing wrong but im sure is something easily fixable. should i press "disconnect" when i plug the kf in or should i leave usb cable screen up?
Click to expand...
Click to collapse
Yes, you have to disconnect mass storage to enable debugging.

soupmagnet said:
Yes, you have to disconnect mass storage to enable debugging.
Click to expand...
Click to collapse
sorry for the stupid ? but how do i do that?

edit: i got rooted following this guide: http://forum.xda-developers.com/showthread.php?t=1638452
for some reason KFU doesnt work for me.

[Q] Having Rooting Problems

(read the guides so please don't just link it....i've seen that on other threads)
for some reason kfu wont install the kindle driver.... (unsigned driver)
it didn't give me a prompt but i went into my driver signing and clicked allow.... still wont go through
can someone help me out please?
(i've only rooted a MT4G and i had no issues back then...)
running windows xp x32
i've been at it for hours and came across one on youtube but it says android composite ADB instead of android ADB
im still on stock 6.3.1 ( no changes have been made yet to the device )
this is the guide i've been reading which kindav just says " ur own your own" to my unsigned driver problem
http://forum.xda-developers.com/showthread.php?t=1552547

NovaxxBite said:
...
this is the guide i've been reading which kindav just says " ur own your own" to my unsigned driver problem
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Is that really all it says on the topic? Is "you're on your own" truly what you got out of reading the following?
kinfauns said:
If Windows refuses to install unsigned drivers, that feature must be disabled before continuing. The process differs for various Windows releases, so search Google and find a suitable method for your system.
Click to expand...
Click to collapse
I gave you a "search Google" link. The first item the search returns gives you step-by-step directions on how to get around the problem. Have you read it? Have you tried it?

kinfauns said:
Is that really all it says on the topic? Is "you're on your own" truly what you got out of reading the following?
I gave you a "search Google" link. The first item the search returns gives you step-by-step directions on how to get around the problem. Have you read it? Have you tried it?
Click to expand...
Click to collapse
wow i just reread my post. that wasnt what i meant to say. sorry, i hope/wasnt trying to be rude or offend anyone:angel:
the google link kindav felt like i was on my own...i've searched all over google and all the windows xp steps either say press F8
( no driver option there on my PC) or to click ignore /warn for the dialog prompt
( basically.. no link addressed my issue)
( following the first link)
i'm not getting the dialog to begin with, i've clicked both ignore and warn but nothing works
also... when i click instal.bat i get
'and' is not recognized as an internal or external command ( did i miss a step?)
after that the kindle driving window pops up, i hit next and after not even a split second it says it wouldnt install..unsigned driver
-edit-
tried using 2 other computers...same problem

NovaxxBite said:
wow i just reread my post. that wasnt what i meant to say. sorry, i hope/wasnt trying to be rude or offend anyone:angel:
the google link kindav felt like i was on my own...i've searched all over google and all the windows xp steps either say press F8
( no driver option there on my PC) or to click ignore /warn for the dialog prompt
( basically.. no link addressed my issue)
( following the first link)
i'm not getting the dialog to begin with, i've clicked both ignore and warn but nothing works
also... when i click instal.bat i get
'and' is not recognized as an internal or external command ( did i miss a step?)
after that the kindle driving window pops up, i hit next and after not even a split second it says it wouldnt install..unsigned driver
-edit-
tried using 2 other computers...same problem
Click to expand...
Click to collapse
1) Download KFU from this link http://forum.xda-developers.com/show....php?t=1399889
2) Before you start rooting ur device.. do the below
3) Extract the util.. run the install_drivers.bat.. this will help you install the drivers..
4) Once it is successfully done..follow the steps outlined in the document attached below (install drivers for ur kindle.docx)
5) Next step is to root ur device and install the google framework and market
6) To root your device.. run run.bat.. select option 2 to install the root.. it might take sometime and will restart the kindle and notify you
7) to install the google apps..run option 6 and then select 1.. sit back and watch the magic happen
This should help you.. let me know if you are not able to do it.. it will good if you can tell me in which step you are facing trouble

kishorev said:
1) Download KFU from this link http://forum.xda-developers.com/show....php?t=1399889
2) Before you start rooting ur device.. do the below
3) Extract the util.. run the install_drivers.bat.. this will help you install the drivers..
4) Once it is successfully done..follow the steps outlined in the document attached below (install drivers for ur kindle.docx)
5) Next step is to root ur device and install the google framework and market
6) To root your device.. run run.bat.. select option 2 to install the root.. it might take sometime and will restart the kindle and notify you
7) to install the google apps..run option 6 and then select 1.. sit back and watch the magic happen
This should help you.. let me know if you are not able to do it.. it will good if you can tell me in which step you are facing trouble
Click to expand...
Click to collapse
link broken?

NovaxxBite said:
link broken?
Click to expand...
Click to collapse
Thats wierd.. try it again http://forum.xda-developers.com/showthread.php?t=1399889
:good:

kishorev said:
Thats wierd.. try it again http://forum.xda-developers.com/showthread.php?t=1399889
:good:
Click to expand...
Click to collapse
this is the same link from the guide lol
i can't get past your 3rd step...
(unsigned driver )
ALSO... why cant i get ADB in device manger?
i've installed SDK tool, SDK Platorm-tools, Android 2.3.3 SDK Platform and Google USB Driver via Android SDK Manager
but when i plug in my kindle fire, it's listed under "other" instead ADB or Android ( and no driver can be found for it....)
kfu wont install kindle drivers because its unsigned
i've done the methods to allow it / ignore the warning prompt but again... its not working
(i didn't get a warning btw... it just said it wouldnt install after not even a second)
i've installed a different (non-related) unsigned driver perfectly ( to test ) but when i use kfu, i the unsigned error immediately after clicking next :crying:
and i've tested on 3 computers now...its all the same for me :<

NovaxxBite said:
this is the same link from the guide lol
i can't get past your 3rd step...
(unsigned driver )
ALSO... why cant i get ADB in device manger?
i've installed SDK tool, SDK Platorm-tools, Android 2.3.3 SDK Platform and Google USB Driver via Android SDK Manager
but when i plug in my kindle fire, it's listed under "other" instead ADB or Android ( and no driver can be found for it....)
kfu wont install kindle drivers because its unsigned
i've done the methods to allow it / ignore the warning prompt but again... its not working
(i didn't get a warning btw... it just said it wouldnt install after not even a second)
i've installed a different (non-related) unsigned driver perfectly ( to test ) but when i use kfu, i the unsigned error immediately after clicking next :crying:
and i've tested on 3 computers now...its all the same for me :<
Click to expand...
Click to collapse
What you can do is try adding the drivers manually to ur device instead of running the .bat file.. using the update driver option in ur device manager..
The driver will be available in the folder Kindle Fire Utility\drivers\kindle

kishorev said:
What you can do is try adding the drivers manually to ur device instead of running the .bat file.. using the update driver option in ur device manager..
The driver will be available in the folder Kindle Fire Utility\drivers\kindle
Click to expand...
Click to collapse
thanks, that seemed to work
now under android phone, i have Android Composite ADB Interface
-sigh-
when i checked cmd.exe for adb devices, it says
List of devices attached
( shows nothing )

well at this point, i've tried 4 different computers...
3 windows xp x32
1 windows 7 x64
On windows 7, the kfu installed the drivers but when i click run.bat , i get
adb offline
Boot status : unknown
Ive tried uninstalling, reinstalling, manually installing, rebooting computer and device
( everything i can find on xda and google )
nothing works
please help :/
Sent from my HTC Glacier using xda app-developers app

NovaxxBite said:
well at this point, i've tried 4 different computers...
3 windows xp x32
1 windows 7 x64
On windows 7, the kfu installed the drivers but when i click run.bat , i get
adb offline
Boot status : unknown
Ive tried uninstalling, reinstalling, manually installing, rebooting computer and device
( everything i can find on xda and google )
nothing works
please help :/
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
Did u try changing the boot mode by selecting the option 1 (Boot Mode menu)
What error message did u c then?
Was the KFU able to restart ur kindle?

Recovery and Normal hangs on waiting while fastboot gives the " oops " error
no kfu never restarted my device
here's a screenshot from my XP computer ( its the same results on each computer )
( the boot menu is from trying to use fastboot mode )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

there a problem with XP vendor code? apparently
"Thepooch" fixed that for me and showed me how to work kfu so thanks
thanks "kishorev" for helping out also btw

The kindle fire's vendor id was missing from adb_usb.inf . It was just a matter of opening adb_usb.inf with notepad and adding and saving this change.
Code:
0x1949
Then KFU could recognize the kindle as online bootmode 4000.

NovaxxBite said:
well at this point, i've tried 4 different computers...
3 windows xp x32
1 windows 7 x64
On windows 7, the kfu installed the drivers but when i click run.bat , i get
adb offline
Boot status : unknown
Click to expand...
Click to collapse
I hope this isn't redundant or anything, but if you still have your Windows 7 machine still handy, try rolling back the driver. That's how I got mine to work. It should be listed under Android Phone -> Android ADB Interface in the first place. If not, try reinstalling the drivers first.
I hope this helps!

jma9454 said:
I hope this isn't redundant or anything, but if you still have your Windows 7 machine still handy, try rolling back the driver. That's how I got mine to work. It should be listed under Android Phone -> Android ADB Interface in the first place. If not, try reinstalling the drivers first.
I hope this helps!
Click to expand...
Click to collapse
thanks, unfortunately the win 7 laptop i used was borrowed
( i need to get one... XP drivers are crappy lol )
but i'm sure this will help someone whos having this problem, searches xda or google and comes across this :highfive:

Alright, you've been messing around with Windows for far too long. Now it's time to do it the right way.

Indeed I second that the right way

Thepooch said:
Indeed I second that the right way
Click to expand...
Click to collapse
soupmagnet said:
Alright, you've been messing around with Windows for far too long. Now it's time to do it the right way.
Click to expand...
Click to collapse
nice. thanks & thanks again :victory:

:highfive:

CM 11 back to Fire OS but have a question?

I love CM11 but I'm just not having great service anymore like I did with the Fire OS... Now here is the question... I have the At&t version with 464 installed... Then installed the CM11 now is it possible to install 463 OS from the unlocked version so that I can install the play store and Google services... Amazons app store lack a lot of apps I currently use... If so how do I go about doing that?

1. Download the "GSM unlocked" firmware image: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
Assuming you are using Windows 7 / 8 / 10, if not, don't bother reading the following wall of text:
2. Connect device to PC & boot in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. In Windows, run the "CMD": adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin
4. If you have trouble getting your device recognised after entering recovery / ADB sideloading mode:
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try this tool (& driver) ADB, Fastboot and Drivers
It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":

Bingo,
Thanks for the guide, but I cannot get my computers to recognize the Phone in recovery ADB mode. It shows the device description as SD4930UR. It only shows as unknown. The hardware IDs are VID_1949&PID_0800. I tried the linked tool (both the 1.4.2 and 1.3 version he had) and the google drivers.
What is the exact driver that works for you?

wats2u said:
What is the exact driver that works for you?
Click to expand...
Click to collapse
I used the "15 seconds ADB Installer" v. 1.3, so the OS used the drivers from there (on Win 7 x64). Use a USB 2.0 port, just to be sure.
The drivers that work on my system might not work for your configuration...
Are you using Win 10? If so, have you tried updating the drivers with the integrated update function?
g0tNoodles said:
It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one, which also needed updating which I have just done and appears to now let the CMD see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now.
Click to expand...
Click to collapse

I can't access my phone from my computer to run the .bin after rebooting it into recovery mode. The download links for that driver installer you linked to don't work. In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.

powerlocked said:
In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.
Click to expand...
Click to collapse
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface​

powerlocked said:
I can't access my phone from my computer to run the .bin after rebooting it into recovery mode. The download links for that driver installer you linked to don't work. In the device manager my phone shows up as 'SD4930UR' I've tried updating it automatically it returns to that, also after uninstalling.
Click to expand...
Click to collapse
DePingus said:
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface​
Click to expand...
Click to collapse
What DePingus said, regarding the 15 seconds ADB... It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Not the first time people struggling with it, Windows is just too darn complicated.

Bingo Bronson said:
What DePingus said, regarding the 15 seconds ADB... It worked for a few thousand people here on XDA, if it doesn't for you, try this one:
http://adbdriver.com/upload/AdbDriverInstaller.exe
Not the first time people struggling with it, Windows is just too darn complicated.
Click to expand...
Click to collapse
Good lord...tried all of that and more and still not able to get my device to show up in ADB. The last installer gives me the message "[Error] Incompatible with Win8 x64". So two questions...anything else I can try for drivers, or, can I use a method other than ADB, such as Safestrap?
Thanks again for all your insight on this forum
EDIT: For anyone that struggled as much as me to finally get drivers to work, this method ultimately worked as posted by @hijax2001
4) I also grabbed the Kindle Fire ADB drivers from here for convenience in Step 7 (below) https://docs.google.com/file/d/0B1Z1J6LQic8PQjFjS0FpVGVia2M/edit
7) For me, ADB did not initially detect my phone. I ended up having to go into Control Panel in Windows, to Device Manager, find the Fire phone, choose Update Drivers, then Browse My Computer, Let Me Pick, Show All Devices, Have Disk, then find the folder from Step 4 (above) and add Android Composite ADB Interface by hand. Once I did that, I unplugged and replugged the USB to the phone and then typed "ADB devices" again at the ADB command prompt, like in Step 6. There it is! Ok, next step...

ElQuixote said:
Good lord...tried all of that and more and still not able to get my device to show up in ADB. The last installer gives me the message "[Error] Incompatible with Win8 x64". So two questions...anything else I can try for drivers, or, can I use a method other than ADB, such as Safestrap?
Thanks again for all your insight on this forum
Click to expand...
Click to collapse
I'm not familiar with adbdriverinstaller, but which ever you use, make sure you are running the installer as admin (right-click on the installer). Also, if you extract the 15 second installer exe with 7zip you get access to the drivers installers separately. Maybe try manually installing them.

DePingus said:
If you installed the "15 second ADB" you should have the drivers. You need to right click that SD4930UR and do...
Update Driver Software
Browse My Computer for Driver Software
Let me Pick for a List of Drivers on My Computer
On the left choose manufacturer Google
On the right choose model Android Composite ADB Interface​
Click to expand...
Click to collapse
Ran 15s ADB. I right clicked SD4930UR in device manager. After selecting update driver, then 'Let me pick from a list..' there is no 'left' or Google listed. It loads a list int he center of the screen of generic hardware devices.. the only one that pertains to a phone is 'mobile' and after selecting that there are no driver options to be found. There is no 'android' to select from that list.
It's doing this on both windows 7 and windows 10.

Bingo Bronson said:
1. Download the "GSM unlocked" firmware image: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
Assuming you are using Windows 7 / 8 / 10, if not, don't bother reading the following wall of text:
2. Connect device to PC & boot in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. In Windows, run the "CMD": adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin
Click to expand...
Click to collapse
I tried this method, to install 4.6.3 unlocked over my ATT (now carrier unlocked) 4.6.4. After I sideloaded, I get the following lines in Recovery, indicating that this didn't work. Any thought? Is there something else I need to do to be able to install the GSM on the ATT version?
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted
EDIT: Determined that the file I originally downloaded may not have been complete and sure enough a second version is larger...

powerlocked said:
Ran 15s ADB. I right clicked SD4930UR in device manager. After selecting update driver, then 'Let me pick from a list..' there is no 'left' or Google listed. It loads a list int he center of the screen of generic hardware devices.. the only one that pertains to a phone is 'mobile' and after selecting that there are no driver options to be found. There is no 'android' to select from that list.
It's doing this on both windows 7 and windows 10.
Click to expand...
Click to collapse
I think those steps are for Windows XP. For Windows 7, 8, or 10 use the following steps to update the driver:
Those steps are for Google USB driver. For Amazon Kindle Fire USB driver, use the following steps:
1) Right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer.
2) Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>.

jack9955 said:
I think those steps are for Windows XP. For Windows 7, 8, or 10 use the following steps to update the driver:
1) Right click SD4930UR or the device (Unknown device) that shows up when you plug your phone into the computer.
2) Select Update Driver Software> Browse my computer for driver software> Let me pick from a list of device drivers on my computer> Kindle Fire> Next> Android Composite ADB interface> Next> Yes> Close>.
Click to expand...
Click to collapse
Ohhhh okay thank you for explaining this. After finding KindleFire down the list I was able to update my drivers. I've now installed the update to both of my ATT Fire phones, and both are now 4.6.3 and working great with working playstore options.
Thank you jack9955 and everyone else for the tutorials.. much appreciated!

How to Setup the Fire phone for ADB
An illustrated guide ... 2015-09-15​
Open open Device Manager. This is what my 4.6.3 Fire phone looks like when plugged in normally to my Windows 7 computer. Power it off and boot into the stock recovery using PWR + VOL UP (hold both buttons until recovery screen appears). The Fire device will disappear from Device Manager.
At the phone's recovery menu choose "Apply update from ADB". Back in Device Manager do a Scan for Hardware Changes and you should now see this. Right click on the Fire and choose uninstall.
Grab "15 Seconds ADB Installer" and install it as admin and hit yes for everything. http://forum.xda-developers.com/showthread.php?t=2588979
Now scan for hardware changes again and you will see this new device. Right Click this device and choose Update Driver Software.
From this window choose "Browse my computer for driver software."
From this window choose "Let me pick from a list of device drivers on my computer."
From this window choose "Show all devices."
In the section on the left that says Manufacturer find "Google Inc." Then, on the right, choose "Android Composite ADB Interface." Accept through any warnings.
The Device Manager should now show this.
Open up a cmd prompt and test that adb can see your phone with the "adb devices" command. Now you can sideload 4.6.3 or whatever.

DePingus said:
How to Setup the Fire phone for ADB
An illustrated guide ... 2015-09-15​
Open open Device Manager. This is what my 4.6.3 Fire phone looks like when plugged in normally to my Windows 7 computer. Power it off and boot into the stock recovery using PWR + VOL UP (hold both buttons until recovery screen appears). The Fire device will disappear from Device Manager.
At the phone's recovery menu choose "Apply update from ADB". Back in Device Manager do a Scan for Hardware Changes and you should now see this. Right click on the Fire and choose uninstall.
Grab "15 Seconds ADB Installer" and install it as admin and hit yes for everything. http://forum.xda-developers.com/showthread.php?t=2588979
Now scan for hardware changes again and you will see this new device. Right Click this device and choose Update Driver Software.
From this window choose "Browse my computer for driver software."
From this window choose "Let me pick from a list of device drivers on my computer."
From this window choose "Show all devices."
In the section on the left that says Manufacturer find "Google Inc." Then, on the right, choose "Android Composite ADB Interface." Accept through any warnings.
The Device Manager should now show this.
Open up a cmd prompt and test that adb can see your phone with the "adb devices" command. Now you can sideload 4.6.3 or whatever.
Click to expand...
Click to collapse
I see there are atleast two USB drivers you can use to set up ADB on the Fire Phone. Amazon Kindle Fire USB driver and Google USB driver. If Google USB driver is installed, you should select "Google, Inc." for Manufacturer. For Amazon USB driver, you should select "Amazon.com" for the Manufacturer, Device Manager will show the device as Kindle Fire> Android Composite ADB Interface.

jack9955 said:
I see there are atleast two USB drivers you can use to set up ADB on the Fire Phone. Amazon Kindle Fire USB driver and Google USB driver. If Google USB driver is installed, you should select "Google, Inc." for Manufacturer. For Amazon USB driver, you should select "Amazon.com" for the Manufacturer, Device Manager will show the device as Kindle Fire> Android Composite ADB Interface.
Click to expand...
Click to collapse
I've also noticed some people using the Amazon drivers. But they're not included with "15 Seconds ADB".

Works seamlessly too on any linux terminal
Just, so you know, your method works very well too on any linux computer. I had the same issue and now it is fixed. I can write a tutorial complimenting this if needed.

hello lam from china english is very bad thanks for friephone cm l hope you will do cm12 cm12.1 don't abandon our china people have lot's of people hope and camera have better solution official camera and fire os5 Do you have any news thanks

csx21 said:
hello lam from china english is very bad thanks for friephone cm l hope you will do cm12 cm12.1 don't abandon our china people have lot's of people hope and camera have better solution official camera and fire os5 Do you have any news thanks
Click to expand...
Click to collapse
We can't do CM12 because the Fire Phone's bootloader is still locked and the current FireOS 4 is based on KitKat. Unless Amazon unlocks the bootloader or releases FireOS 5 for these phones, we are stuck in KitKat (CM11).

Will applying update from adb format the phone..hopefully it will