Related
Here's what I'm seeing...I've restarted the Kindle 4 times now and nothing is happening.
Any ideas?
Here's a link the pic : img18.imageshack.us/img18/6505/image1cb[dot]png
What are you seeing on your Kindle now? Are you in fastboot (Yellow Triangle with fire)?
I don't have FireFireFire installed. Basically I ran the Kindle Fire Utility and did a Permanent Root (after I unrooted using BurritoRoot)...and then ran latest install of TWRP....and everytime it gets to the actually instal part...I see that screen....
and when I restart my kindle (like it says to do in Kindle Fire Utility) it just restarts normally and then goes to USB connected screen.
Steps:
1. Download this .img for twrp.
2. Place it in the adb folder. (where ever you have to cd to)
3. Do the following commands:
adb shell
su
idme bootmode 4002
reboot
4. Download fastboot and place it in the adb folder and do:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5. Enjoy your newly added recovery.
I'm now stuck in fastboot (yellow triangle with fire)
I tried to just press the power butter to load into recover but it didn't work.
I tried adb reboot, but it says no device is found...
Any ideas?
Edit: I saw a post that I need to re-install the drivers?
Which one:
Image: img809.imageshack.us/img809/7474/image3si[dot]png
did you do
idme bootmode 4000
to get it to boot normal?
adb commands arent working....do i need to reinstall the drivers? if so which one...it gives me three choices...
ADB interface
Bootloader Interface
Composite ADB Interface...
I'm assuming once I get adb commands working again...then I can use idme bootmode 4000 to get into regular boot mode again.
Edit: I tried chaning to Normal boot with Kinde Fire Utility...didn't work...
Really wondering if I should reinstall the drivers and try agian...but the KFU doesn't really seem to be playing nice with my device.
Not to say KFU is bad but I never used it. If you started with the directions that came with twrp we might not need so many topic about twrp help.
I just ran into the same problem!
ADB and fastboot commands don't work for me too, and I also tired to reinstall the drivers and still didn't work..
edit: try using KFU on another computer, and then changing to normal boot!
that seemed to work for me!
try to uninstall old/faulty drivers:
disconnect kf and use:
http://support.microsoft.com/kb/315539/en-us
connect KF and select the last installed driver (which you installed by running "install_drivers.bat") manually (check the date/time on selection)
Yeah, the KFU has just been a headache for me.. I finally got it working though, i have to use burrito root everytime I want to do anything after a reboot in KFU, but it works perfectly fine after that. Make sure you have good drivers installed under android phone also! Don't use the install_drivers.bat from KFU, just caused me more headaches...
i used the drivers from kfu - but after a cleanup - that seems to be the point
the difference is they are te only ones with entries for device 18D1 you'll nedd in fastboot mode or you can add the entries to your drivers under "kindle" or "kindle fire" or what it is called in your android_winusb.inf:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
Well I was assuming they used a root method that already had them set up their own driver files etc. already.
no they don't - they try to provide drivers that are working in every bootmode - i've made corrections in the driver installer script for non english os which vashipooh implemented off ver. .9 - i have also device 18D1 in my adb_usb.ini - if it helps ? - but there's no downside
Maybe I'm just too tired (its 4:30 AM here) But I don't understand what you said... And the current version of KFU has a bad install_drivers.bat, it replaces the mass USB storage driver and it made my ADB stop working...
i think it don't replace the mass storage driver, it just reinstalls it - that's not they'r fault - it's the tool they are using from microsoft (devcon) to update existing drivers - devcon seems to be working this way - good or not ? - who know's ?
Wait, are you talking about the most current 9.1 or 9.0? Because 9.0 works fine, the new 9.1 kills USB storage, and for me ADB which kind of destroys the point.
9.0 - will download 9.1 and take a look - perhaps i can help to sort the problems out and contact vashi to correct the issue - thanks for the hint !!!
No problem, haha I knew there was something missing in that conversation, hope you guys can figure it out!
tec2030 said:
adb commands arent working....do i need to reinstall the drivers? if so which one...it gives me three choices...
ADB interface
Bootloader Interface
Composite ADB Interface...
I'm assuming once I get adb commands working again...then I can use idme bootmode 4000 to get into regular boot mode again.
Edit: I tried chaning to Normal boot with Kinde Fire Utility...didn't work...
Really wondering if I should reinstall the drivers and try agian...but the KFU doesn't really seem to be playing nice with my device.
Click to expand...
Click to collapse
Here is how to manually install the drivers step by step.. If you think you may have a problem with the drivers that you have on your computer it would be smart to get download another .android folder and put it on the root of your c:drive just to be sure that nothing is wrong with it before you attempt this
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
Hope that helps..!
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
Adb isn't. Finding my kindle fire 6.2.2 NEED HELP IM TRYING TO ROOT IT
Did you set up the device drivers as outlined in this?
http://forum.xda-developers.com/showpost.php?p=22145030&postcount=6
Adb still says its offline
When you go into device manager, what does it display it as?
It says Android Composite Adb Interface
Th3-Chronikk said:
It says Android Composite Adb Interface
Click to expand...
Click to collapse
This is what I recommend: if you installed Android SDK, go ahead and uninstall it. It's only an absolute necessity if you're a developer or running it a virtual environment. Clean all traces of any part of Android drivers or leftovers files and folders. Next, uninstall the drivers from Device Manager under Computer or My Computer. Reboot your PC or laptop.
Next, download vashypoo's Kindle Fire Utility, available in the Kindle Fire's Android Development forum, and extract it. Inside of the extracted folder should be a .bat file to install drivers. Right click, select Run As Administrator, and follow the on-screen instructions. Once it's completed, reboot.
Inside one of the KFU folders (I can't remember if it's files or tools) is ADB. Right click while pressing Shift on your PC keyboard, open a command window, and type the following:
adb devices
If all goes well, your Fire should be listed. These are the steps I followed when I ran into this exact same issue. I hope it works!
Sent from my Kindle Fire using xda premium
Thats what I did I truer both the SDK method and the kindle fire utility my kindle fire isn't recognized by either one
Does anyone know what I can do
did you try to cold-reset ? hold pwr ~20sec and pwr on again
sometimes restarting the computer helps ...
Yes tryed that and still no luck
the driver (android composite adb interface) is the right one
did you check the adb_usb.ini file in .android folder in your personal folder ?
ist should include 0x1949 & 0x18d1 - if not add in a new line
restarting adb : adb kill-server
check again: adb devices
I did that already
sorry i'm really running out of ideas at this point ...
adb relies on:
adb_usb.ini in .android folder with the correct entries:
0x1949 & 0x18d1
drivers with the correct entries in android_winusb.inf (drivers of kfu do):
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
in the 32 and 64 bit section
Did that.... still not recrecognized
Have you tried a different usb port? My Fire is finocky about which port i use.
Sent from my Kindle Fire using Tapatalk
WhoRuJudge said:
Have you tried a different usb port? My Fire is finocky about which port i use.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Yes I did no luck
This is before doing anything to it yet? (just to make sure we're on the same page)
Does it show up as an external drive in Windows? Windows, right?
Seems possible to me that if you haven't done anything at all yet and it doesn't show up in Windows you might have a bad USB cable or port on your device.
If you haven't done anything yet, have you tried calling Amazon for troubleshooting / possible replacement?
(Sorry, I'm just trying to cover the things that haven't been asked.)
gadgetman13 said:
This is before doing anything to it yet? (just to make sure we're on the same page)
Does it show up as an external drive in Windows? Windows, right?
Seems possible to me that if you haven't done anything at all yet and it doesn't show up in Windows you might have a bad USB cable or port on your device.
If you haven't done anything yet, have you tried calling Amazon for troubleshooting / possible replacement?
(Sorry, I'm just trying to cover the things that haven't been asked.)
Click to expand...
Click to collapse
It is recognized by windows as a storage device but what I'm saying is that it wouldnt show up on Adb even after I added the kindle fire driver
Use the app in unlockroot.com you won't need driver
Sent from my LG-P500 using xda premium
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.
My nephew managed to get into TWRP and somehow wiped the entire thing clean. I purposely keep a recovery .zip in there but even that's gone. When the Kindle is turned on it displays the Fire triangle but then the screen goes black and stays like that. I can boot into TWRP but can't use the mount option or adb because my computer, and the three others I've tried, refuses to recognize the Kindle. It shows up in Device Manager as Unknown and I can't manually install the driver. I've tried every combination of booting it with the computer off or on, uninstalling the Unknown driver, everything. Can you kind folks please save my butt? Thanks in advance for your responses.
wiped in TWRP and Windows only displays device as Unkown
Lance Uppercut,
Have you tried starting adb services and going back through the FireFireFire Utility, this has fixed a lot of boot errors that I had in the pass?
Let me know if you need help with starting adb services.
Thanks,
JohninLex
Thanks for your reply
Can you please elaborate on this a bit more? Maybe I'm not understanding correctly but I thought starting adb services wouldn't do anything in this instance since it wouldn't recognize the Kindle as being there at all? For instance, when I run Kindle Fire Utility it shows adb devices as being offline. If I could get the Kindle to show up as anything other than Unknown I'm certain I could just update the driver to an android device and have KFU take it over from there.
wiped in TWRP and Windows only displays device as Unkown
Lance Uppercut,
Did you root your Kindle "adb devices"
and the following commands?
adb shell chmod 777 /data/local/tmp
adb install Burritoroot3.apk
or did you download a file from the market to get root?
if you did it the above way with adb commands from a terminal would be great.
Either way lets set the driver, download the Kindle Fire Utility extract it to your desktop. or take note where you extracted it. Then go to your device manager and right click on the Kindle (unknown device) look for update driver and browse the the Kindle Fire Utility folder double click on the drivers folder and let it update the right driver you need for your OS (XP,Vista, 7 x86 or 64). Once it finds the right driver Open up a command prompt by going to start run and typing cmd and hitting enter. Once that is done download the KindleADB files and place them in the C:\ (drag and drop should be fine here ) go back to your command prompt and do the following commands:
** urname** C:\ " cd KindleADB " then hit enter
and then do " adb devices " it may or may not come back with your device sn but as long as it has started is what we are looking for.
Once that is done go back to your desktop leaving everything open and look through the Kindle Fire Utility until you find a file named Run.bat double click and hit run this will reinstall twrp and allow it to be remount-able. If you need a stock Kindle rom with update 6.2.2 I have a back up I can share with you.
I hope this helps but if it does not let me know and we can go back over the the driver section.
Thanks,
JohninLex
I've attempted installing the driver manually many times like you stated and on different PCs all containing KFU and the modified .ini file in the .android folder and the message I get when I attempt to manually update the driver is "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems." When I first got the message I attempted to do it in an x86 system and the driver would still not install. My inability to get ANY computer to read the kindle as anything other than Unknown is the main issue. Even if I could make it read as the default "kindle" with the exclamation point it would be enough for me to fix it. But if I can't get a driver to load I'm hopeless to fix it in any way.
Use Android composite driver on your PC to get adb working. Once the adb is working, there multiple ways to boot or install a new ROM. I recommend to start doing the following commands:
Fastboot mode.
Try these ADB commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Ng you have an Android phone, connect to you PC first to see if adb is working using composite ad driver for Windows operating system
Sent from my Amazon Kindle Fire using Tapatalk
I can't use android composite driver. Every time I attempt to install the driver manually I get the error listed above. No matter what I do I can't get the Kindle to be anything other than Unknown
i had a problem where i could only get the fire symbol screen computer would not recognize. I had to start the kindle fire utility plug my kindle into the computer then turn it off, then have kfu install latest twrp again when it says waiting for device turn device on and it will reinstall that and get you back to the recovery. so maybe you can do the same with obtain stock update. not really sure to the kindle. my computer would recognize kindle fire for a few seconds and thats how i could install new twrp
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
if you can't get rid of the drivers:
http://forum.xda-developers.com/showthread.php?t=1430038
nevertheless i would never install the original stock rom cause you loose fff,twrp and root
use one of the prerooted stock roms instead:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
I had this exact same problem and ended up with a bricked kindle for a few weeks. I tried everything on the forum...uninstalling/reinstalling drivers/sdk/etc. At the end of it all I had the drivers installed properly (which was a real pain in the keyster) but my computer still would not recognize my device.
I found 2 posts that finally helped me:
1) in the .android file for adb_usb.ini, you need to add in 0x006 in another line. Also dont forget to add the 3-line code @ [Google.NTx86] and [Google.NTamd64]
Here is a link. This link has just about everything else you need to do to solve this issue.
http://www.kindle-fireforum.com/forum/amazon-kindle-fire-development/1086-adb-issues-solved-how.html
2) manually mount the drive and flash update.zip. For some reason my kindle got locked in fastboot, then when i switched it to normal it would get stuck on the loading animation. If this happens you probably need to flash and start over.
Here is that process.
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
hope this helps and good luck
Help me save my kindle fire
I used KFU to install TWRP and up to CM9. But after that i restore to rom stock 6.2.
But after kindle start the error sorry loop in screen . I can not access to kindle.
process.android.acore force close
We try to connect and re install TWRP but not successfull. when i connect kindle to my pc (XP and window 7) it only recognize kindle as disk driver (athough i try to uninstall and setup manual driver )..
Help me urgent.
Thanks alot
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
mhb1509 said:
I had this exact same problem and ended up with a bricked kindle for a few weeks. I tried everything on the forum...uninstalling/reinstalling drivers/sdk/etc. At the end of it all I had the drivers installed properly (which was a real pain in the keyster) but my computer still would not recognize my device.
I found 2 posts that finally helped me:
1) in the .android file for adb_usb.ini, you need to add in 0x006 in another line. Also dont forget to add the 3-line code @ [Google.NTx86] and [Google.NTamd64]
Here is a link. This link has just about everything else you need to do to solve this issue.
http://www.kindle-fireforum.com/forum/amazon-kindle-fire-development/1086-adb-issues-solved-how.html
2) manually mount the drive and flash update.zip. For some reason my kindle got locked in fastboot, then when i switched it to normal it would get stuck on the loading animation. If this happens you probably need to flash and start over.
Here is that process.
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
hope this helps and good luck
Click to expand...
Click to collapse
This comment gave a ton of hope since I have tried everything that has been mentioned already except for adding 0x006 but sadly it did not work. There's absolutely nothing I can do to get out of the Unknown state. I've never had my ass kicked this hard by a piece of hardware. I surrender.
maybe this as a last resort:
http://forum.xda-developers.com/showthread.php?t=1430038
b63 said:
maybe this as a last resort:
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
I was reading through that earlier and it was a little too intimidating. I'm just going to sit here and cry for a couple of minutes.
Kindle still recognize as disk driver
I try to do something but adb not working (device not found because it recognize as normal disk driver). My pc use window xp professional.
How can i solve this
My kindle still recognize as normal disk driver
I try to test on some computers (xp, win7) but unfortunately, my kindle still recognize as normal usb only. (not adb device).
So i don know how to fix this problem
Please help me, or give me a hint
xp is a good choice - you don't have to care about the uac (user acces control)
have you checked according to my post #12 above ?
to shorten things up i could take a look with teamviewer if you like
just gimme a pm ...
Have you added the second vendor and the second set of USB command lines in your google/extras folder? If not add those turn off the kindle then turn it back on do "fastboot devices" then put the update.zip in your platform-tools folder then push the update to your kindle to be flashed by twrp. The command for that would be "advt push update.zip /sdcard/update.zip" you can have the kindle already in twrp by this point. Also when all is over you will have to reroot and reinstall fff and twrp. If you need help send me a message.
Sent from my Kindle Fire using Tapatalk
Hard reset on main-board KF
My KF is frozen. I try to do hard reset by hold pw button 20s, but not effected.
So i've just open back-slide my KF, and see KF main-board.
Have hard reset trick on this main-board.
Help me please.