Related
look ill keep this short and simple. im rather new to the rooting an XDA community and i was wondering if there any reputable service techs or anyone who i can send my kindle to to un-brick and install new OS and or just fix the piece of ****? i have searched and read an searched an read an im about out of patience. call it lazy or whatever but ill gladly pay someone to resolve the issue an send the thing back. thanks everyone in advance for any and all help in this matter!
PS: I want cm9 an google play store also an im tired of trying to do it myself. i could care less about amazon streaming video.
Haussenfeffer said:
look ill keep this short and simple. im rather new to the rooting an XDA community and i was wondering if there any reputable service techs or anyone who i can send my kindle to to un-brick and install new OS and or just fix the piece of ****? i have searched and read an searched an read an im about out of patience. call it lazy or whatever but ill gladly pay someone to resolve the issue an send the thing back. thanks everyone in advance for any and all help in this matter!
PS: I want cm9 an google play store also an im tired of trying to do it myself. i could care less about amazon streaming video.
Click to expand...
Click to collapse
I'm sure there are people here that will walk you through the steps over Skype or something for free. Don't give up so easily.
Haussenfeffer said:
look ill keep this short and simple. im rather new to the rooting an XDA community and i was wondering if there any reputable service techs or anyone who i can send my kindle to to un-brick and install new OS and or just fix the piece of ****? i have searched and read an searched an read an im about out of patience. call it lazy or whatever but ill gladly pay someone to resolve the issue an send the thing back. thanks everyone in advance for any and all help in this matter!
PS: I want cm9 an google play store also an im tired of trying to do it myself. i could care less about amazon streaming video.
Click to expand...
Click to collapse
Can you provide some information as to what the problem is with your device and how it got that way?
[Edit:] I suggest reading through it before trying anything
ROOTED 6.3 using KFU
i used the kfu a few weeks ago to root the device. i used another laptop, not my own (i couldnt get mine to recognize the fire) but finally got it! i had it on when i left the house an by the time i go to work the firefirefire triangle was on the screen, and stayed there. im assuming it did an update since i didnt modify the update.bak file name and threw the device into a boot loop. those crutial instructions seemed to be left out of the directions i was fallowing. at least thats what i think happened.
Do you have recovery installed and do you know how to access it?
i do! (i think lol)
i think so. it says press power button to enter recovery mode but whenever i did it it never went into it. it just either shut off (if it was held long enough) and or loaded normally(if i only held it for a few seconds)
It should load if you press the power button until it turns orange. If not, you need to reinstall it.
Are you on a Mac or PC?
PC
im using windows 7
Do you have the Kindle Fire Utility?
i do!
i do, and when i press the button when it first turns on it does change to orange but it just stayes on the triangle screen sn the light remains orange. im on the laptop now that couldnt recognize the fire. im at work on a gas rig in pa an i dont go on days off till thursday morning when i can gain access to the laptop i used for the root install. i do have the KFU but i could never get the POS to find my kindle
There are problems with the driver setup that causes problems on Windows machines, but it can be fixed. To get your computer to recognize the device you simply have to fix the drivers.
A good place to start is this guide:
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
It explains how to make sure your drivers are installed properly in order for you to send adb and fastboot commands so you can reinstall recovery.
ADB drivers are on
when i connect it to my kindle it says kindle an when i go into the properties an check the driver info it says ADB interface and Android Phone on the far right
Shift+right click on the KFU "tools" folder and select "run as command" or "open in command window" or something to that effect. It will open a new command window.
At the prompt, enter:
fastboot devices
or
fastboot getvar product
...and tell me what they return
start over...
how do i completelyremove any and all kindle software an driver an start fresh. im talkin the KFU and the SDk tools as well?
The only Kindle Fire software "installed" on your computer are the drivers which can be removed from the device manager while the device is plugged in.
Uninstall your current drivers and use the guide posted earlier to reinstall and verify them.
Then check for a connection with "fastboot devices" or "fastboot getvar product"
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
favaron88 said:
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
Click to expand...
Click to collapse
Do you have a bootloader installed? Can you boot into recovery?
Eaffon said:
Do you have a bootloader installed? Can you boot into recovery?
Click to expand...
Click to collapse
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
favaron88 said:
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
Click to expand...
Click to collapse
Hmm... Does it show up in device manager?
Dont throw it.. give it to me. Haha
After my sem I will have plenty of time to do all this stuff..
Sent from my SGH-T999 using xda premium
Eaffon said:
Hmm... Does it show up in device manager?
Click to expand...
Click to collapse
I've uploaded a screen shot of my device manager and in "devices and printers"
as you can see, it shows up as a kindle in devices and printers, and as an android phone in the device manager.
I also uploaded "My Computer" so you can see there is no access to it from there.
Okay.
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Eaffon said:
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Click to expand...
Click to collapse
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
favaron88 said:
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
Click to expand...
Click to collapse
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Eaffon said:
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Click to expand...
Click to collapse
alright, I found it and tried those commands and this is what I got.
favaron88 said:
alright, I found it and tried those commands and this is what I got.
Click to expand...
Click to collapse
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Eaffon said:
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Click to expand...
Click to collapse
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
You could try my prefab ISO soupkit is already ran on it and it has teamviewer installed for assistance measures you can find it here post 7 http://forum.xda-developers.com/showthread.php?t=1413358 but what I think you will need is a factory cable found here ultimately post 9 http://forum.xda-developers.com/showthread.php?t=1392693 . The system is trying to run that's why it comes up android composite adb interface, its busy trying to handle the data that you failed to wipe prior to flashing jelly bean and then stock. You could also see if if will allow you to send twrp and fff back to the device with kfu then enter recovery wipe and reflash another ROM.
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
It's totally fixable.
Thepooch is right. My brother had the same problem with his son's. Just get into fastboot and flash a bootloader and twrp and youre set
Sent from my Amazon Kindle Fire using xda app-developers app
Thepooch said:
It's totally fixable.
Click to expand...
Click to collapse
Awesome
Also I didn't want you to think I ignored your post. I just finished making the usb drive with ubuntu on it and was going to attempt your solution in the other thread if whatever we were trying here doesn't work.
I appreciate y'alls help very much.
Eaffon said:
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Ok I loaded KFU and told went and told it to boot in fastboot, it said that it told the device to do it, but it still says Boot Status: Unknown.
Is this a problem or do we know that it's booting in fastmode now? I'm just not sure how to tell if it was successful since it's not giving me the code.
(Ps - I originally posted this before my previous post thanking you guys, but then came back to this window to see that I had screwed up the Captcha, but it wouldn't let me post for 5 more minutes since I'm a new user. Sorry for the wait.)
Its very common for the boot mode to be unknown in fast boot. Try to send twrp with kfu if it says waiting for device for a long time simply power it off while connected then back on it should then pick up and send twrp. If need be do the same thing with the bootloader just wait longer a failed bootloader flash is far worse than the situation your in.
favaron88 said:
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
Click to expand...
Click to collapse
ADB is connected, therefore you are not in fastboot. The Kindle Fire logo you see is actually the stock boot animation. The difference is whether or not it changes in brightness at any point (obviously it does).
You need access to recovery to fix your problem and you need the ability to change bootmodes to get into recovery. Without a working shell you need access to fastboot to change bootmodes.
Unfortunately, in many situations like yours, there is no working shell to change the bootmode. To confirm this, try to launch the shell by entering "adb shell", respectively.
If you receive an error, your only options are to get a factory cable (recommended) or open the device so you can put it in USBboot via the shorting trick and the use of Firekit (not so recommended).
With access to fastboot, you can change your bootmode to recovery or reinstall a custom recovery if necessary. In recovery, the "fix" is as simple as reinstalling a ROM.
"That's a special kind of stupid. The kind that makes me laugh."
I have scoured through pages and google searches for many related subjects and not one has been able to help me thus far.
I have a kindle fire that I rooted and put TWRP on it and android 4.1, a few months back.
The power port is damage so keeping it plugged in can be a challenge but it still works, anyways I digress.
I erased the entire SD apparently and that included my backups.
I can only boot into TWRP and normally that wouldn't be a problem except I can't connect my kindle through ADB commands and it doesn't show up on my computer. I have drivers installed and I have been trying so many different things so if you find something similar to what I'm talking about please let me know as I would love to have this kindle running again.
Many thanks in advance,
-TehRobot.
Mount the sdcard to USB in TWRP.
"That's a special kind of stupid. The kind that makes me laugh."
Ok I tried all the check boxes for mounting, of course mounting the SDcard... but the computer won't recognize the kindle to be even there.
I was running 4.1.0 on c9 and erased the SD card.. After that it wouldn't show up on my computer.
So TWRP is my savior except I can't put any files onto it to flash.. :
Edit****
Does anyone think I should buy a factory cable or breakout board, I think that's what it is called, to try and force the kindle into recovery, then perhaps it would show up on my laptop.
Because I figure if it showed up before, and after the accidental wipe it no longer did I would have to imagine it's the kindle itself.
I don't think that's it, if you're in TWRP you're already in recovery. Have you tried the Linux method in the soupkit sticky thread?
Sent from my Amazon Kindle Fire using xda app-developers app
Tehrobot said:
Ok I tried all the check boxes for mounting, of course mounting the SDcard... but the computer won't recognize the kindle to be even there.
I was running 4.1.0 on c9 and erased the SD card.. After that it wouldn't show up on my computer.
So TWRP is my savior except I can't put any files onto it to flash.. :
Edit****
Does anyone think I should buy a factory cable or breakout board, I think that's what it is called, to try and force the kindle into recovery, then perhaps it would show up on my laptop.
Because I figure if it showed up before, and after the accidental wipe it no longer did I would have to imagine it's the kindle itself.
Click to expand...
Click to collapse
SoupKit will fix your mounting issue OR look for a sticky in the KF General forum that explains how to do it manually.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
SoupKit will fix your mounting issue OR look for a sticky in the KF General forum that explains how to do it manually.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Thanks, going to put Mint 13 on my laptop and get started. I will report back after I get this kindle working again!
soupmagnet said:
SoupKit will fix your mounting issue OR look for a sticky in the KF General forum that explains how to do it manually.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Ok, so I have a partition on my HD with linux mint running on it with all the updates installed.
-DL soupkit.
read the readme.
It wont run in the terminal no matter what I do..
It does however show up in my Home/bin/soupkit.
I tried getting it to run in the terminal manually but to no avail.
I am only a breadth above novice with linux so bear with me please as I am trying to be as specific as possible with the problems I am encountering..
( I had it running in the terminal like normal but it kept asking for a sudo password that wasn't my password, but that was before I fully installed It, I thought I could make it work off the Demo version before full installation was completed.)
Tehrobot said:
Ok, so I have a partition on my HD with linux mint running on it with all the updates installed.
-DL soupkit.
read the readme.
It wont run in the terminal no matter what I do..
It does however show up in my Home/bin/soupkit.
I tried getting it to run in the terminal manually but to no avail.
I am only a breadth above novice with linux so bear with me please as I am trying to be as specific as possible with the problems I am encountering..
( I had it running in the terminal like normal but it kept asking for a sudo password that wasn't my password, but that was before I fully installed It, I thought I could make it work off the Demo version before full installation was completed.)
Click to expand...
Click to collapse
In terminal, are you entering "soupkit.sh" ?
Yes, I followed the instructions as closely as possible.
It wouldn't open, it would say it installed properly but wouldn't run.
Tehrobot said:
( I had it running in the terminal like normal but it kept asking for a sudo password that wasn't my password, but that was before I fully installed It, I thought I could make it work off the Demo version before full installation was completed.)
Click to expand...
Click to collapse
A couple things to note:
In demo (Live) mode, there is no sudo password, you just press enter. Also, in Live mode, nothing gets written to disc, especially if you are running Live from a CD.
If you want to run Live rather than actually installing Linux to your computer, you need to do so from a USB drive with "persistence" (Google it)
I understand this is new to you but all of this information is in the SoupKit thread. Pay close attention to the information you find there, and if there is something it that you don't understand, try to research it to the best of your abilities.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
A couple things to note:
In demo (Live) mode, there is no sudo password, you just press enter. Also, in Live mode, nothing gets written to disc, especially if you are running Live from a CD.
If you want to run Live rather than actually installing Linux to your computer, you need to do so from a USB drive with "persistence" (Google it)
I understand this is new to you but all of this information is in the SoupKit thread. Pay close attention to the information you find there, and if there is something it that you don't understand, try to research it to the best of your abilities.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
No I understand, I had it installed from the windows.exe it gives. You just finish installation whence you log into mint. Anyways,
I was trying to get around having to use a USB, that's all. I will get a bigger USB and try that, I did read the guide pretty closely and I'm sure I can do it, I was just trying to go without USB.
Thanks for all your help though its been a hell of a lot easier.
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
kindlestuck said:
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
Click to expand...
Click to collapse
[HOW-TO] Before asking for troubleshooting help...
Frequently Asked Questions - Amazon Kindle Fire
[GUIDE] Kindle Fire For Beginners
[HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)
He has all of the drivers installed, but KFU seems to have an issue with file paths. I have redownloaded it for him and I also updated his copy of the SDK with Kindle Fire drivers and a newer ADB. The KFU returns an error "System cannot find the path specified for everything, even though it is extracted straight out of the zip it came in. All he did was choose install TWRP and it didn't even make it to fastboot mode before it bricked.
Zeklandia said:
He has all of the drivers installed, but KFU seems to have an issue with file paths. I have redownloaded it for him and I also updated his copy of the SDK with Kindle Fire drivers and a newer ADB. The KFU returns an error "System cannot find the path specified for everything, even though it is extracted straight out of the zip it came in. All he did was choose install TWRP and it didn't even make it to fastboot mode before it bricked.
Click to expand...
Click to collapse
Thank you for your insight, but all the information needed to fix what is a very common problem can be found in the threads to which links have been provided. The device IS in fastboot. Simply changing the bootmode is the key to resolving the problem. That being said, the KFU is not the end all/be all to changing the bootmode or installing TWRP.
soupmagnet said:
Thank you for your insight, but all the information needed to fix what is a very common problem can be found in the threads to which links have been provided. The device IS in fastboot. Simply changing the bootmode is the key to resolving the problem. That being said, the KFU is not the end all/be all to changing the bootmode or installing TWRP.
Click to expand...
Click to collapse
It is not in fact in fastboot, it is not even listed in adb devices or fastboot devices.
---------- Post added at 12:52 PM ---------- Previous post was at 12:29 PM ----------
I have a feeling it is trying to boot into stock recovery, as KFU was trying to reboot into TWRP (which never installed because KFU was broken).
---------- Post added at 12:55 PM ---------- Previous post was at 12:52 PM ----------
If we can get out of stock recovery, that would be useful. Do you have any idea how to bring up the menu in stock recovery? Does he need to hold the power button down or press it in a pattern?
Zeklandia said:
It is not in fact in fastboot, it is not even listed in adb devices or fastboot devices.
Click to expand...
Click to collapse
While some who know me better may be prepared to see me respond in my usual manner at this point, I have instead, decided to play nice
I have been a member of this forum for quite some time and have seen hundreds of different problems in just as many scenarios for each, and I can assure you, without even a shred of doubt, that the device is in fact in fastboot mode (unless, of course, the information provided in the OP is inaccurate).
You can find information for properly identifying fastboot mode in the "Frequently Asked Questions" thread and the "Fastboot Guide" linked to within it, so please feel free to prove me wrong.
With that,
Just because the device itself doesn't respond to fastboot commands from the computer, doesn't mean the device isn't in fastboot mode. It simply means (in this case) that the drivers are not properly installed or configured, despite the steps taken to do so. Windows is very tricky when it comes to installing drivers for Android and there are hundreds of posts within these forums that should be able to convince you of that. If you want to eliminate all doubt and ensure that driver problems aren't just compounding the issue, set up a Linux LiveUSB and either install SoupKit, or configure it manually to communicate with the device via USB so that adb and fastboot commands will work properly.
Good luck
I appreciate you trying to help, but his device is 100% stock. KFU has set it to boot into recovery, and it will continue to boot into the stock recovery until we can find a way to change that idme bootmode. Tomorrow, I will attempt to use my factory cable on it, but for now all fastboot does is wait for device. I use Linux, so if it truly is in fastboot mode, then it should have no problem, especially with the factory cable.
Zeklandia said:
I appreciate you trying to help, but his device is 100% stock. KFU has set it to boot into recovery, and it will continue to boot into the stock recovery until we can find a way to change that idme bootmode. Tomorrow, I will attempt to use my factory cable on it, but for now all fastboot does is wait for device. I use Linux, so if it truly is in fastboot mode, then it should have no problem, especially with the factory cable.
Sent from my Battle Droid
Click to expand...
Click to collapse
Looking at your signature, I see that you are technically competent enough to take a look at the KFU 'run.bat' and see how it works. When the option to install TWRP is selected, the script uses Pokey9000's 'fbmode' to boot into fastboot mode. Once KFU is able to detect the device in fastboot, it then uses fastboot commands to flash TWRP to the recovery partition and then reboot to recovery. If the KFU were able to detect the device in fastboot mode and TWRP was not installed due to file paths, then the device would still boot into the stock recovery, normally, and you would see plenty of error messages giving you a clue as to what went wrong. Messages in the KFU window compared to those found in the script itself can also show you where things went wrong.
What happens (more times than I care to try and estimate) is, due to the way Windows handles Android drivers, when the device is put into fastboot mode (even though adb commands were working at the time), the fastboot drivers aren't working properly, the script cannot move forward and the device gets stuck in fastboot mode.
As I mentioned earlier, the "Fastboot Guide" linked to in the FAQ, tells you how to recognize fastboot mode beyond all uncertainty. With all due respect, I'd suggest you look into it before deciding that you know best in this particular situation.
And not to make assumptions about your level of proficiency with Linux, but don't forget that you have to either set up udev rules for the device, or run your fastboot commands as root for it to work properly.
same issue...
yes perhaps you should be a little more sympathic to the OP as 1. he probably has a valid issue (im having the same problem...neither windows nor Soupkit is recognizing my KF thats stuck in the white and orange logo fastboot and 2. none of the above links help this problem in any manner. I have been researching this issue for days now and have tried a few different distros (just my luck Mint's persistance didnt work...sigh) and no matter what, my computer will not communicate with the KF.
it seems my KF is now bricked because I ran the KFU and selected install "FireFireFire" before rooting...it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem.
if you have any other suggestions it sure would be appreciated...thanks.
menriquez said:
yes perhaps you should be a little more sympathic to the OP as 1. he probably has a valid issue (im having the same problem...neither windows nor Soupkit is recognizing my KF thats stuck in the white and orange logo fastboot and 2. none of the above links help this problem in any manner. I have been researching this issue for days now and have tried a few different distros (just my luck Mint's persistance didnt work...sigh) and no matter what, my computer will not communicate with the KF.
it seems my KF is now bricked because I ran the KFU and selected install "FireFireFire" before rooting...it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem.
if you have any other suggestions it sure would be appreciated...thanks.
Click to expand...
Click to collapse
Make no mistake about it...I am sympathetic to every single person who "bricks" their device. However, I find it very hard to be sympathetic to those who fail to take personal responsibility for a problem they created due to not having done the appropriate amount of research before getting involved in something they didn't understand.
First off, your device does not have to be rooted to install FireFireFire. As a matter of fact, it's better that you install FireFireFire before trying to root...but your drivers have to be in working order from the start. And you have absolutely NO RIGHT to push blame on someone else just because you don't have the knowledge necessary to modify your device without tools made by other people. It is your device and your responsibility...so own up to it.
Second, I can say beyond all uncertainty that the information needed to understand and resolve yours and 90% of all other situations in this forum, can be found in those 4 links posted earlier. But since no one seems to want to believe that, I guess I'll just have to prove it to you.
1) Being stuck at the Kindle Fire logo means your device is in one of two states; in fastboot mode, or in normal mode but without a working system to boot to. This is explained in both the Frequently Asked Questions thread and the Fastboot Guide thread linked to within it. FAQ #16, Fastboot Guide
2) Also explained in the threads mentioned previously, is information on determining what state the device is in by paying attention to the behavior of the Kindle Fire logo as the device starts up. If the Kindle Fire is displayed brightly and stays brightly lit indefinitely, the device is in fastboot mode. If the Kindle Fire logo is brightly lit for a few seconds then flashes and/or goes dim, then it is trying to boot normally to a non-working system. With that knowledge, you can easily determine your next course of action...also based on the information found in the links provided. FAQ #16, Fastboot Guide
3) The key to fixing 99% of all Kindle Fire problems is getting access to custom recovery. There are two ways to access custom recovery when your device is malfunctioning, through FireFireFire, or through fastboot. If you don't have FireFireFire installed, the only option you have left is fastboot. If the device is trying to boot normally to a non-working system, then your only option for accessing fastboot is with a factory cable. FAQ #16, 17, 26, 29, 32, 33, Fastboot Guide
4) If your device is already in fastboot mode, and you are unable to change your bootmodes with the command line in Windows, it is because your drivers aren't properly installed. There is no other possible scenario. FAQ #14, KFFB - post #3
5) If you are using Windows, and you are unable to fix your drivers despite the wealth of information available to you for getting the drivers to work properly, then you use use Linux. FAQ #15
Your situation is no different. If I were to make an educated guess, I would say device is stuck in fastboot mode because your drivers weren't working properly...and you only have Microsoft to blame for that. As for Linux, it will not communicate your device using ADB or fastboot automatically. You have to either run the commands as the root user, or set up udev rules for your device. If you used the SoupKit to set up your udev rules using a LiveUSB, you have to have working persistence. The way it's configured now is to reboot in order for the udev rules to be loaded. If you don't have working persistence, everything you did prior to the reboot will be lost (This is also explained to you in the SoupKit thread).
With that being said, you have NO RIGHT to get offended if I would rather post a few links and expect the user to do the appropriate amount of research on their own to fix a problem THEY CREATED, than spend my personal time to tell every single user that comes to this forum with the exact same problems, everything that I have told you just now.
I wish you the best of luck in getting your device fixed, and I have no qualms about providing you support for the things in the aforementioned threads that you don't understand. But I WILL NOT hold your hand and tell you every single little thing that you need to know in order for you to fix your own device.
soupmagnet said:
Make no mistake about it...I am sympathetic to every single person who "bricks" their device. However, I find it very hard to be sympathetic to those who fail to take personal responsibility for a problem they created due to not having done the appropriate amount of research before getting involved in something they didn't understand.
First off, your device does not have to be rooted to install FireFireFire. As a matter of fact, it's better that you install FireFireFire before trying to root...but your drivers have to be in working order from the start. And you have absolutely NO RIGHT to push blame on someone else just because you don't have the knowledge necessary to modify your device without tools made by other people. It is your device and your responsibility...so own up to it.
Click to expand...
Click to collapse
wow...sigh...listen the last thing my post tried to do is shift blame...i CLEARLY stated *I* made a BIG MISTAKE didn't I?? i dont need a flame war here sheesh im just trying to fix this ****ty kindle for a buddy.
Second, I can say beyond all uncertainty that the information needed to understand and resolve yours and 90% of all other situations in this forum, can be found in those 4 links posted earlier. But since no one seems to want to believe that, I guess I'll just have to prove it to you.
1) Being stuck at the Kindle Fire logo means your device is in one of two states; in fastboot mode, or in normal mode but without a working system to boot to. This is explained in both the Frequently Asked Questions thread and the Fastboot Guide thread linked to within it.
2) Also explained in the threads mentioned previously, is information on determining what state the device is in by paying attention to the behavior of the Kindle Fire logo as the device starts up. If the Kindle Fire is displayed brightly and stays brightly lit indefinitely, the device is in fastboot mode. If the Kindle Fire logo is brightly lit for a few seconds then flashes and/or goes dim, then it is trying to boot normally to a non-working system. With that knowledge, you can easily determine your next course of action...also based on the information found in the links provided.
3) The key to fixing 99% of all Kindle Fire problems is getting access to custom recovery. There are two ways to access custom recovery when your device is malfunctioning, through FireFireFire, or through fastboot. If you don't have FireFireFire installed, the only option you have left is fastboot. If the device is trying to boot normally to a non-working system, then your only option for accessing fastboot is with a factory cable.
4) If your device is already in fastboot mode, and you are unable to change your bootmodes with the command line, it is because your drivers aren't properly installed. There is no other possible scenario.
5) If you are using Windows, and you are unable to fix your drivers despite the wealth of information available to you for getting the drivers to work properly, then you use Linux.
Click to expand...
Click to collapse
lol i read and did ALL of that my chippy friend...the logo starts and stays bright so im sure im in fastboot mode. i got the latest ubuntu on a pen, like i said after i tried Mint 15 and discovered that persistence on a pen doesn't work well with that distro currently. ubuntu did, and in fact recognizes all my other android devices no problem...but nothing at all when i plug the kindle
Your situation is no different. If I were to make an educated guess, I would say device is stuck in fastboot mode because your drivers weren't working properly...and you only have Microsoft to blame for that. As for Linux, it will not communicate your device using ADB or fastboot automatically. You have to either run the commands as the root user, or set up udev rules for your device. If you used the SoupKit to set up your udev rules using a LiveUSB, you have to have working persistence. The way it's configured now, is to reboot in order for the udev rules to be loaded. If you don't have working persistence, everything you did prior to the reboot will be lost (This is also explained to you in the SoupKit thread).
Click to expand...
Click to collapse
like i said both in my original post and above, i figured out the persistence issue its working now. the reboot loaded the rules but when the script runs im getting two errors which, due to my deep frustration at the time i didn't write down the exact wording. i figured i'd chill for a while and then try again later.
With that being said, you have NO RIGHT to get offended if I would rather post a few links and expect the user to do the appropriate amount of research on their own to fix a problem THEY CREATED, than spend my personal time to tell every single user that comes to this forum with the exact same problems, everything that I have told you just now.
I wish you the best of luck in getting your device fixed, and I have no qualms about providing you support for the things in the aforementioned threads that you don't understand. But I WILL NOT hold your hand and tell you every single little thing that you need to know in order for you to fix your own device.
Click to expand...
Click to collapse
hey i totally appreciate your help and your wish of luck lord knows ill take anything right now this stupid "project" has caused me more grief then i could have ever imagined it could. btw, i didnt get "offended" i just thought maybe you were being kinda hard on the OP due to my experience dealing with the exact same issues he posted he was dealing with...
...believe it or not not everyone who doesn't have the same experiences with this stuff as you do aren't necessary idiots or unskilled at using complex systems. thanks again for your continued help and do have a great day!
menriquez said:
wow...sigh...listen the last thing my post tried to do is shift blame...i CLEARLY stated *I* made a BIG MISTAKE didn't I?? i dont need a flame war here sheesh im just trying to fix this ****ty kindle for a buddy....!
Click to expand...
Click to collapse
The last thing I want to do is to get into a flame war with anyone, but when someone comes to the forum and says something like...
it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem
Click to expand...
Click to collapse
...which, by the way, is entirely based on misinformation...it is very easy for someone to assume the author is, whether directly or indirectly, speaking poorly about a developer's work and assigning blame by presuming that the mistake would not have been made if the tool in question had been made differently. Based on the limited information from your original post, one can only assume that your situation is no different from the hundreds of other users with the same exact problem that also swore the information available did not pertain to their situation and that they were somehow unique, only to find out 50 posts later that it was not the case.
But rather than letting this discussion escalate any further, lets try a different approach. I will give you the benefit of the doubt and entertain the thought that your situation is in fact unique and that there is possibly some other solution for your problem. But, in order for me to do that, I'm going to need some information...very detailed information.
From what I gather so far, based on the information you've provided in your second post is...
1) Your device is in fastboot, confirmed by the fact that the Kindle Fire logo stays brightly lit.
2) You are currently using a LiveUSB with Ubuntu installed and working persistence.
3) When you ran the SoupKit install script, you received errors of some sort, but don't you remember what they were.
4) You are unable to send any fastboot commands at all.
The things I would like to know are...
1) What version of Ubuntu are you running?
2) What brand of pendrive are you using?
3) What is the exact error you received when trying to install the SoupKit?
4) With your device connected, enter the following commands (in Linux) and post the results:
Code:
lsusb -vd 1949: | grep 'bcdDevice'
Code:
cat ~/.android/adb_usb.ini
Code:
sudo cat /etc/udev/rules.d/51-android.rules
soupmagnet said:
...
But rather than letting this discussion escalate any further, lets try a different approach. I will give you the benefit of the doubt and entertain the thought that your situation is in fact unique and that there is possibly some other solution for your problem. But, in order for me to do that, I'm going to need some information...very detailed information.
From what I gather so far, based on the information you've provided in your second post is...
1) Your device is in fastboot, confirmed by the fact that the Kindle Fire logo stays brightly lit.
2) You are currently using a LiveUSB with Ubuntu installed and working persistence.
3) When you ran the SoupKit install script, you received errors of some sort, but don't you remember what they were.
4) You are unable to send any fastboot commands at all.
The things I would like to know are...
1) What version of Ubuntu are you running?
2) What brand of pendrive are you using?
3) What is the exact error you received when trying to install the SoupKit?
4) With your device connected, enter the following commands (in Linux) and post the results:
Code:
lsusb -vd 1949: | grep 'bcdDevice'
Code:
cat ~/.android/adb_usb.ini
Code:
sudo cat /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
firstly i'm very appreciative of your decision to get this back on a positive track and even more thankful that you are still trying to help...
1. ubuntu 13.04 32-bit
2 16gb sandisk with 1024m persistance
3. i reinstalled everything and double checked it...i am no longer getting any errors running soupkit it just says "device offline"
4 lsusb -vd 1949: | grep 'bcdDevice' - nothing just the prompt
5. cat ~/.android/adb_usb.ini - 0x1949
6 . sudo cat /etc/udev/rules.d/51-android.rules -
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
well thats it...i plug my nexus 7 and GS3 and even an ultra cheapo zte warp sequent and it connects right up to all of those...
menriquez said:
firstly i'm very appreciative of your decision to get this back on a positive track and even more thankful that you are still trying to help...
1. ubuntu 13.04 32-bit
2 16gb sandisk with 1024m persistance
3. i reinstalled everything and double checked it...i am no longer getting any errors running soupkit it just says "device offline"
4 lsusb -vd 1949: | grep 'bcdDevice' - nothing just the prompt
5. cat ~/.android/adb_usb.ini - 0x1949
6 . sudo cat /etc/udev/rules.d/51-android.rules -
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
well thats it...i plug my nexus 7 and GS3 and even an ultra cheapo zte warp sequent and it connects right up to all of those...
Click to expand...
Click to collapse
Oh........this again....
For reasons I have yet to figure out, there are rare (and I do mean rare) situations where Linux just will not detect the device whatsoever. When you enter the 'lsusb' command, whether the udev rules are configured properly or not, Linux should still detect your device when plugged into the USB. I can probably count on one hand the number of times I've seen this happen, and I've never been able to recreate the problem on my own.
It could be caused by using the wrong USB port (i.e. USB3.0 instead of USB2.0), it could be caused by the USB pendrive itself, you could have a faulty cable, it may even be the Linux install itself, but those are just wild guesses because I have really don't know. My best estimate is that there is a bug in the stock bootloader that sometimes causes it to malfunction when put into fastboot because (in the few instances I've seen), users that were able to resolve their situation did so by using usbboot to install a custom bootloader. This of course requires opening the device and performing the "shorting trick" to drop the device into usbboot mode.
If I were you, considering you probably haven't attempted to usbboot before, you should try a different USB port, a different USB cable, and a different pendrive to see if you have any luck. Otherwise, you may have no other choice but to usbboot.
The unfortunate thing usbbooting is, it's just one of those things you have to somehow figure out on your own, even with the instructions given in the Firekit/usbboot thread (it's really about technique more than anything else). I've done it several times myself, mostly for testing and various other reasons, but the first time (when I really needed it), took practically forever to get it right.
If you do take the usbboot route, you can launch Firekit from the SoupKit utility script (option #4, I think) and follow the instructions in the Firekit thread. Be very careful opening the device, use a safety pin for creating the short (the reason will become apparent when you get the device opened), and most of all...good luck.
[Edit:] And yes, crow is very tasty
kindlestuck said:
I was using KFU (0.9.9) to install TWRP. When it went to reboot into fastboot mode, the kindle fire boot logo (stock) appeared and the power light turned green. It is now stuck like this. KFU and Windows 7 does not recognize the kindle. I have tried turning it off and back on, but it just goes back to the same screen.
Click to expand...
Click to collapse
Charge kindle, boot into the frozen logo screen with no animation, plug into computer, and reboot computer, i want to share this with everyone because it worked for my kindle
Hi All,
Today I should be picking up a KF2 (Kindle Fire 2nd Gen) today from a friend. And although I have experience with this device in the past, as I rooted one a while ago, and installed Google PlayStore bits and bobs for another friend... This was a while back.
A few months back, I read somewhere although cannot find it now... That Amazon have rolled out a serious Update to most Kindles (KF2, KF-HD, and possibally KF-HDX) that has updated the baseband/kernel to a certain version. Which prevents Unlocking, and tampering with it could cause the device to Hard Brick...
So was wondering, what is the best procedure to tackle this? Easy method to Root / Recovery??
And what does this 2nd BootLoader actually do?? Does it allow you to DualBoot both original stock Kindle firmware as well as second partition for Custom Roms??
Thanks, Lister
OK first off which kindle do you have, because a kf2 is. Of a 2nd gen kfhd. If its a 2013 kindle fire HD, don't bother with second bootloader because it will just brick it. If it is in fact a kf2 then here's what second d bootloader does. Basically we can't unlock our devices bootloader so 2nd bootloader is a workaround. It allows us to run our own unsigned kernels and custom recovery. Once we have that we can flash a custom ROM like cm. And no no dual booting, Amazon's os is too different from cm to be able to.
To install 2nd bootloader + twrp you must be rooted, suggest kindle fire first aid for that, there's a tutorial in the dev section for kf2 for installing second bootloader + twrp here.
Make sure you check the md5sum of the bootloader before flashing it so you don't risk hard bricking, also I suggest putting the ROM and its gapps on the kindle ahead of time if your are running 10.4.8 because it will boot loop into recovery after the process until you flash a different rom, so its easier to have the ROM o. Ahead of time rather than "adb push" it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hi @stunts513,
Sorry for the delay getting back to you, my friend didnt bring the device in until yesterday...
I can confirm that it is a Kindle Fire 2nd Gen (Otter2), and it is running 10.4.6 firmware/baseband...
I tried to root it in work, on my Windows 8.1 and Windows 7 based PCs, and unfortunately it wasn't detecting it, or working with the ADB drivers....
I tried at home on my Windows XP and Vista setup, and again wasn't detecting it. However it did detect on my Windows 7 setup at home (triple boot). This must of been the partition I used for my friends one many months ago... (although I found various Kindle related files on each partition).
Anyway, I got the damn thing rooted now, thankfully... and shall move onto the 2nd Bootloader thing... However, is there any other way, or easy way of doing this other than whats in that post?? I don't mind doing it, and will follow it again. However late last night I was losing the will to live as it was hard work getting to do things... (compared to other Android devices that are a breeze to do...).
I tried to backup my partitions on the Kindle what it says to do at the start, and it kept saying it couldnt find these on the Kindle... I read in the guide that it said I could download them from a website, but all I could see was scripts and not backup partitions... Is it really important to backup my own ones, or could I just download someone else's Kindle Fire 2nd (8Gb) model??
And yeah, is there any other way to get custom recovery / rom on, other than the original guide...?? - not gonna give up, just last night kept falling asleep trying to follow it... when things werent working and patiently waiting for things to happen/work... lol
Anyway, thanks so much for replying to my question, and for all the help you have given me to get me started... much appreciated!!
Thanks, Lister
Lister Of Smeg said:
Hi @stunts513,
Sorry for the delay getting back to you, my friend didnt bring the device in until yesterday...
I can confirm that it is a Kindle Fire 2nd Gen (Otter2), and it is running 10.4.6 firmware/baseband...
I tried to root it in work, on my Windows 8.1 and Windows 7 based PCs, and unfortunately it wasn't detecting it, or working with the ADB drivers....
I tried at home on my Windows XP and Vista setup, and again wasn't detecting it. However it did detect on my Windows 7 setup at home (triple boot). This must of been the partition I used for my friends one many months ago... (although I found various Kindle related files on each partition).
Anyway, I got the damn thing rooted now, thankfully... and shall move onto the 2nd Bootloader thing... However, is there any other way, or easy way of doing this other than whats in that post?? I don't mind doing it, and will follow it again. However late last night I was losing the will to live as it was hard work getting to do things... (compared to other Android devices that are a breeze to do...).
I tried to backup my partitions on the Kindle what it says to do at the start, and it kept saying it couldnt find these on the Kindle... I read in the guide that it said I could download them from a website, but all I could see was scripts and not backup partitions... Is it really important to backup my own ones, or could I just download someone else's Kindle Fire 2nd (8Gb) model??
And yeah, is there any other way to get custom recovery / rom on, other than the original guide...?? - not gonna give up, just last night kept falling asleep trying to follow it... when things werent working and patiently waiting for things to happen/work... lol
Anyway, thanks so much for replying to my question, and for all the help you have given me to get me started... much appreciated!!
Thanks, Lister
Click to expand...
Click to collapse
As far as i know offhand that method for the kf2 is the only method, which is kinda sad because its the same manual method as the other hd's, and the hd's have fireflash, but fireflash never had the support added in for the kf2 for some reason last i checked. I wouldn't worry too much about the backups, once you run the dd command on the partitions to store them on the sdcard folder, then even if adb pull doesn't work you can always copy them over mtp. i don't like how adb pull works on windows. Only image i would be concerned with storing is the boot0block.
If i made some incorrect references its probably because i vaguely remember it maybe having a different command than the hd model, but the hd's backup command would work on a kf2 as well.
Hi @stunts513,
Just wanted to say THANK YOU SO MUCH!!!
With your help, you have helped me accomplish what seemed like a scary trip to KindleFire Bricks'ville...
But thanks to you, I am all rooted, TWRP'd and ready to go... Shall flash a rom, and sort dads Birthday Pressie now...
Really appreciated, top guy!! thank you... Lister
stunts513 said:
As far as i know offhand that method for the kf2 is the only method, which is kinda sad because its the same manual method as the other hd's, and the hd's have fireflash, but fireflash never had the support added in for the kf2 for some reason last i checked. I wouldn't worry too much about the backups, once you run the dd command on the partitions to store them on the sdcard folder, then even if adb pull doesn't work you can always copy them over mtp. i don't like how adb pull works on windows. Only image i would be concerned with storing is the boot0block.
If i made some incorrect references its probably because i vaguely remember it maybe having a different command than the hd model, but the hd's backup command would work on a kf2 as well.
Click to expand...
Click to collapse
Rooting KF2
Can you give a list of the links that you used to root you KF2?
I've tried to connect to my with ADB but I can't get it to see my device. I can connect my KF2 to my WINXP machine, and transfer files, but I can't get ADB to recognize the device, and I can't get any root options to work. Any help would be appreciated. Ultimately I would like to install a new ROM like CM, but until I can do the basics, I can't get that done.
You should check to see if it has the driver installed for adb in the device manager, if it doesn't even show up as a adb device in device manager you probably haven't turned USB debugging on on the kindle itself.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You should check to see if it has the driver installed for adb in the device manager, if it doesn't even show up as a adb device in device manager you probably haven't turned USB debugging on on the kindle itself.
Click to expand...
Click to collapse
Checked and verified that USB debugging is in fact turned on on my kindle.
Settings>>Security>>Enable ADB is ON.
Settings>>Device>>Allow Installation of Applications is ON
I still can't get adb to recognize my device.
I installed ADB from adt-bundle-windows-x86-20140321.zip if that makes any difference.
I had read in the forums that I might need a special cable for fastboot. Is that what I'll need to get?
For what it's worth, I just found and followed this tutorial:
EDIT: Well crap, this forum won't let me post the outside url. I guess if you search for "Setting up ADB driver for Kindle Devices" by David Isbitski" on developer dot amazon dot com, you will be able to find the tutorial
It was very helpful, and it was the first tutorial I've found that actually showed how to install adb windows drivers for the kindle fire.
In windows Device Manager >> Portable Devices >> Kindle is installed, then uninstall Kindle, as they are the wrong drivers.
In the SDK Manager
Go to TOOLS >> Manage Add On Sites
Go to the User Defined Sites tab
add the url found in the tutorial listed above, save and quit that window.
Back at the manager, do "Packages >> Reload" to update the list.
For the kindle fire 2nd generation, I had to expand "Android 4.0.3 (API 15) to find and install:
"Kindle Fire 2nd Generation"
Under Extras, install:
Amazon AVD Launcher (Windows)
Kindle Fire Device Deffinitions
Kindle Fire USB Driver
Once installed go to \extras\amazon\kindle_fire_usb_driver and run "KindleDrivers.exe"
You should then find "Device Manager >> Kindle Fire >> Android Cmposite ADB Interface"
You can then stop/start adb, then do a adb devices.
That is what worked for me!
New to the forum and trying to recognize what you are doing here......
I have a Kindle Fire 2nd Gen with 10.4.8 SW installed. Would like to dump a much newer Android version on it and looking for the correct path.
Any help is greatly appreciated.
Thanks