Related
*disclaimer: I am posting here because for all of my searching, I don't see help for unbricking on a Mac when you're already rooted...
********UPDATE: I SOLVED THE ISSUE! I WILL POST A HOW-TO FOR MAC USERS VERY SOON!********
My problem:
I can't use the usual steps in this forum to get past the boot animation because I can't see my device on my Mac anymore since this whole boot loop started. How do I get into adb if my kindle is in boot limbo..?
Note: My Kindle is rooted, I have adb on my Mac and everything was fine until I updated my GoEx Launcher. Help!
Thanks in advance, and I'll donate/buy beers for whoever can help!!!
Am I seriously the only one in this forum who uses a Mac to access adb??
I heard issues, so I dual booted into windows to run the commands.
Sent from my HTC Glacier using xda premium
smirkis said:
I heard issues, so I dual booted into windows to run the commands.
Click to expand...
Click to collapse
Ok. I guess I'm just gonna have to bite the bullet and find a PC. Still, I don't understand how being on a PC or a Mac will make a difference if the kindle is stuck at the boot animation, how will the PC ever get to communicate with it..? I'm mean if it's looping then it never gets to initialize enough for adb to access it... right?
Ok, so for some unexplainable reason, I got my iMac to recognize that my kindle is attached (unlike my Macbook, which never sees it while it's boot looping). Yes, I am still in boot loop though. I think my problem is I never make it into fastboot mode.
When I am in adb, I can see that my kindle is rooted (the permissions pop up in the Terminal) but when I get to the fastboot part, it always returns "permission denied" for any command I enter.
If I've gotten this kindle to talk to adb via Terminal (on Mac) while it's in boot loop mode, there HAS to be a way to push it even further and get it to wipe the system and back to stock... right?
Help!!!!
***UPDATE***
I've somehow gotten into fastboot mode (i think) because the logo is no longer flashing. But of course now that it's in fastboot, Terminal says:
error: device not found
I downloaded fastboot.exe (but what folder should it be in???) and run the fastboot commands, starting with: cd /system/bin
...but it just says: No such file or directory
I feel like I'm really close here lol.. someone, throw me a bone!
im not really familure with macs I know that it is unix based but how do the drivers work? is it like PC or more like linux?
***UPDATE***
PROGRESS!!!
I was able to enter the fastboot commands to erase user data, told it to boot into bootmode 4000, and then I entered the command to reboot...
...that's where it ends. lol
Apparently the Terminal is stuck at: "rebooting..."
I'm gonna stare at it as long as I can, hopefully it reboots because if it does, I can post a new thread for all the Mac users who got stuck like me...
**cross your fingers!***
wtphoto said:
im not really familure with macs I know that it is unix based but how do the drivers work? is it like PC or more like linux?
Click to expand...
Click to collapse
...more like Linux!
OMG OMG OMG OMG!!!! I DID IT!!!!
LOL AWESOME!!!!!!!!!!!!!!!!
Ok! So I'm gonna post my steps for Mac users.. unfortunately, not tonight because I'll be up trying to get CM7 on this bad boy! lol
...and yeah, I know what you're sayin. 'Why hack it some more after you just got it back up and running?!"
Well, that's the life of a geek lol. Not to mention that now I know how to get it back if I crash it again, so.. yeah. Here's to being a geek baby!
Thanks for NOT helping guys... I guess trial and error IS the best teacher!
I know when I was having an issue getting fastboot to recognize I had to add 51-android.rules to my /etc/udev/rules.d directory
**edit** NM looks like you got it, sorry I came in late
wtphoto said:
I know when I was having an issue getting fastboot to recognize I had to add 51-android.rules to my /etc/udev/rules.d directory
**edit** NM looks like you got it, sorry I came in late
Click to expand...
Click to collapse
Hey, thanks! Yeah I already had it in the bag by the time you posted, but thanks for trying to help...
I am in the process of organizing a new post with the steps I went through to get unbricked on my mac. I will be posting soon!
webmastertroi said:
Hey, thanks! Yeah I already had it in the bag by the time you posted, but thanks for trying to help...
I am in the process of organizing a new post with the steps I went through to get unbricked on my mac. I will be posting soon!
Click to expand...
Click to collapse
Thanks so much man!!!!! <3 you (no homo) ur a life saver!!!! can't wait for this guide epic thanks to you!
LOL!!! Glad to know someone else can use it! I have been busy working and now I'm in airport to fly out for the holidays, but I'm working to post it hopefully tomorrow or Friday... I'm on it!
Sent from my Kindle Fire using xda premium
Well, I'm now in the same boat and also on a mac...stuck at boot and can't seem to get it to be recognized by adb... If someone could post the steps, I'd be very grateful...
bikeracer4487 said:
Well, I'm now in the same boat and also on a mac...stuck at boot and can't seem to get it to be recognized by adb... If someone could post the steps, I'd be very grateful...
Click to expand...
Click to collapse
I apologize for the wait. I'm traveling for the holiday and simply haven't had the time. I will try to work on it asap. It's a pretty lengthy post with a lot of steps and I will have to organize it all lol. I will soon though...
Merry Christmas in the meantime..
Here is the fix that should work on Windows/Mac/Linux:
1. first have your kindle plugged in and off
2. in the command prompt, browse to the android platform tools, where fastboot is.
3. type in fastboot -i 0x1949 oem idme bootmode 4000
4. It should show < waiting for device >
5. Turn on your Kindle
If its still sitting at the yellow triangle, then type fastboot -i 0x1949 reboot
lchanmanl said:
Here is the fix that should work on Windows/Mac/Linux:
1. first have your kindle plugged in and off
2. in the command prompt, browse to the android platform tools, where fastboot is.
3. type in fastboot -i 0x1949 oem idme bootmode 4000
4. It should show < waiting for device >
5. Turn on your Kindle
If its still sitting at the yellow triangle, then type fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
HOLY CRAP!! That just fixed my kindle that has been bricked for 2 weeks. THANKS!
HELP!
Troi:
I am in the same boat as you. Can you post the steps you used to unbrick your Fire on a Mac?
Thanks,
David
lchanmanl said:
Here is the fix that should work on Windows/Mac/Linux:
1. first have your kindle plugged in and off
2. in the command prompt, browse to the android platform tools, where fastboot is.
3. type in fastboot -i 0x1949 oem idme bootmode 4000
4. It should show < waiting for device >
5. Turn on your Kindle
If its still sitting at the yellow triangle, then type fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
I'm still stuck at the triangle after step 5. So I tried the fastboot -i 0x1949 reboot and I get this message
ERROR: usb_read failed with status e00002ed
any thoughts?
EDIT: the error now says
ERROR: could not get pipe properties
I was rooted, just stock though, use BurritoRoot. Also had TWRP working fine. I tried several times to install MoDaCo Custom ROM for the Kindle Fire but it would just throw me into a bootloop at the Kindle Fire splash screen, couldn't get it to work. Someone suggested that I unrooted back to stock and started over.
So I followed this guide: http://forum.xda-developers.com/showthread.php?t=1399072
Now I'm stuck at the "Kindle Fire" splash screen, been sitting here stuck for 10 minutes now and still going. Anyone to get out of this? Oh and while I'm sitting here stuck at the splash screen, my power button is still orange, if that means anything to anyone?
I also still see "android phone" in device manager and it says my drivers for it are installed correctly.
EDIT: I have KF connected to my PC, when I type in "adb shell" I get this now:
c:\>cd android
c:\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\Android>
Click to expand...
Click to collapse
I also tried following this:
I have also heard of the problem with some people getting caught in a boot loop and see a constant Kindle Fire boot screen. To fix this you must open up your cmd and type:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
But when I type in "fastboot -i 0x1949 oem idme bootmode 4000" I just get this, doesn't do anything?
c:\Android>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
Click to expand...
Click to collapse
I also tried reinstalling my drivers. I removed them, restarted my PC and followed these directions again: http://forum.xda-developers.com/showthread.php?t=1431785&page=2
I tried typing in "fastboot -i 0x1949 oem idme bootmode 4000" but still just sits at "waiting for device".
to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19
bal1985 said:
I was rooted, just stock though, use BurritoRoot. Also had TWRP working fine. I tried several times to install MoDaCo Custom ROM for the Kindle Fire but it would just throw me into a bootloop at the Kindle Fire splash screen, couldn't get it to work. Someone suggested that I unrooted back to stock and started over...
Click to expand...
Click to collapse
We are in the same boat my friend. I think we're gonna have to get/make a factory cable.
Refot_Sirk said:
We are in the same boat my friend. I think we're gonna have to get/make a factory cable.
Click to expand...
Click to collapse
so you tried everything that is listed above and nothing worked? by the way what is a factory cable, what does it do and how do you get one?
theres gotta be a way to get out of this bootloop...someone has to know.
b63 said:
to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19
Click to expand...
Click to collapse
ive tried all of those.
for making a factory cable look here:
http://forum.xda-developers.com/showthread.php?t=1392693
it puts the kf in fastboot mode
b63 said:
to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19
Click to expand...
Click to collapse
- the first one didn't work.
- the second, the unbrick utility didn't do anything. everything just sits at "waiting for device".
the third, [fastboot] stock 6.2.1 wont work for me. this is what i get when i try that option:
C:\Android>adb push fbmode /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
2457 KB/s (510876 bytes in 0.203s)
C:\Android>adb shell chmod 755 /data/local/tmp/fbmode
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\Android>
Click to expand...
Click to collapse
b63 said:
for making a factory cable look here:
http://forum.xda-developers.com/showthread.php?t=1392693
it puts the kf in fastboot mode
Click to expand...
Click to collapse
yeah im not soldering anything, ill just make things worse. if i could buy one that would be great. my only option is to get my kindle replaced again. no choice. hopefully someone here can help or knows something before i call amazon.
this is the other option - you have to open it:
http://forum.xda-developers.com/showthread.php?p=20565446
would buy a factory cable - there are at least 2 guys selling them here in the forum - one of them is SkOrPn
make a search for factory cable or SkOrPn
it's also good to have one for the future ...
EDIT:
here you can order one:
http://forum.xda-developers.com/showpost.php?p=21309629&postcount=123
u need to slow down and read more carefully.
buy a cable from skorpn, fastboot flash twrp than new fff1.2
Sent from my HTC Glacier using xda premium
smirkis said:
u need to slow down and read more carefully.
buy a cable from skorpn, fastboot flash twrp than new fff1.2
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
i read very carefully, but before i start throwing money around, i dont know how much he charges, but maybe someone else can get my through this little issue.
i did message him a bit ago, just waiting for his reply.
Make sure your computer is set up properly to read your kindle...the easiest thing to do is download Kindle Fire Utility, extract it to your desktop, navigate to the tools folder within the Kindle Fire Utility folder, hold shift while right clicking and select open command prompt here. Once the window opens up, try the commands over again where you push the fastboot file and then change the permissions.
Adb shell (press enter)
Su (press enter, if already showing # sign than you are already in su)
Chmod blah blah (press enter)
Sent from my HTC Vision using XDA App
bal1985 said:
i read very carefully, but before i start throwing money around, i dont know how much he charges, but maybe someone else can get my through this little issue.
i did message him a bit ago, just waiting for his reply.
Click to expand...
Click to collapse
i think i have read he charges ~ $15 with shipping
G1ForFun said:
Make sure your computer is set up properly to read your kindle...the easiest thing to do is download Kindle Fire Utility, extract it to your desktop, navigate to the tools folder within the Kindle Fire Utility folder, hold shift while right clicking and select open command prompt here. Once the window opens up, try the commands over again where you push the fastboot file and then change the permissions.
Adb shell (press enter)
Su (press enter, if already showing # sign than you are already in su)
Chmod blah blah (press enter)
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
im not rooted so adb wont work properly...
i did what you said:
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>su
'su' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>
Click to expand...
Click to collapse
b63 said:
to flash the stock stock rom was probably not the best idea....
Click to expand...
Click to collapse
So are threads like this:
http://forum.xda-developers.com/showthread.php?t=1399072
just bad advice? Or is there some inherent risk in flashing or removing any recovery?
bad advice ? don't know - it is written in the title what happens
i think this is for people who want to return the kf to amazon and mostly it works.
if i want to keep my kf and have a working recovery system i would NEVER EVER flash the original stock rom from amazon
there are prerooted stock images available as i mentioned earlier
also a pure update version to 6.2.1 is available (i used it from 6.2 to 6.2.1 - very fine)
There sending me a knew one, I learned my lesson. I'll get more info before flashing. Well at least people know not to use that thread above. He should put a little warning in his thread so no one else gets my promblem.
Sent from my HTC Rezound using XDA Premium
Hi all, I have the same problem, while I was using TWRP I don't know how but I have bricked my kindle, now it is in "kindle fire screen boot loop", when I attach the kindle at computer it is seen, kindle fire utility say:
ADB status: online
Boot status: unknown
I tried to change boot mode from kindle fire utility and it reboot my kindle but in the same situation, so I try to make a factory cable, I connect the red wire with the connector that have not any wire (on the rear), as I read in some threads, but when I reboot kindle pressing power button for 20 sec, with this modified usb insert, and power up kindle....never happens and it still say "kindle fire"
sorry for my english and please help me
Hi, i got my kindle fire 3 days ago. The first day I installed ice cream sandwich, the March 19th ICS CM9 Kang ROM, everything was running excellent and smooth. Last night, before going to sleep I plugged it. This morning i press the power button and it wakes up, but after 2 minutes of use the screen started to flash in gray tones, I though it had crashed and reboot it(press the power button for 25 secs), after I turn it back on it shows the FIREFIREFIRE triangle for 1 sec and started to flash this awful gray screen. And after that it didn't show any image, the back light turns on but it doesn't show nothing.
I know its booting into ICS because I still get the email alert sound.
I'm thinking on returning it as i bought it at a local walmart. I'm just concern about the fact its flashed to ICS. I know the way on how to take it back to stock, the thing is i just can't see anything on the screen and I'm not sure if the touch sensors still work.
Also when i plug it to the pc and run the KFU it show the status as offline and the power button turn orange.
I really don't know what to do right now, i guess it's just bad luck for getting a defective one. Any tip, advice or suggestion will be appreciated.
Is adb working? Use adb or fastboot to install the stock room
Sent from my Amazon Kindle Fire using Tapatalk
ammubarak said:
Is adb working? Use adb or fastboot to install the stock room
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Hey thank you for your answer, Excuse me but I'm not that experienced with android and adb, can you tell me how to check if adb is working. Also how to install the stock rom through it.
gustavosuarez4 said:
Hey thank you for your answer, Excuse me but I'm not that experienced with android and adb, can you tell me how to check if adb is working. Also how to install the stock rom through it.
Click to expand...
Click to collapse
OK, plug kindle into computer, go to cmd, change directory to android-sdk/platform-tools, type:
Code:
adb
adb remount
adb devices
then your kindle serial should popup in cmd... report back and I can help.
BiteBlaze said:
OK, plug kindle into computer, go to cmd, change directory to android-sdk/platform-tools, type:
Code:
adb
adb remount
adb devices
then your kindle serial should popup in cmd... report back and I can help.
Click to expand...
Click to collapse
I did that but when i type remount it says "error: device not found" and on adb devices it doesn't show any device. :/ Is the any other possibility?
PD: The touch screen is working, and I wanna try to do the stock restoration through the kindle. Right now i'm able to unlock to the main screen. I just need to mount the usb storage to copy the official update in the kindle's sd card root and then try to restore using TWRP it being blind wow. Any other ideas?
PD: How can i check if the drivers are working properly?
gustavosuarez4 said:
I did that but when i type remount it says "error: device not found" and on adb devices it doesn't show any device. :/ Is the any other possibility?
PD: The touch screen is working, and I wanna try to do the stock restoration through the kindle. Right now i'm able to unlock to the main screen. I just need to mount the usb storage to copy the official update in the kindle's sd card root and then try to restore using TWRP it being blind wow. Any other ideas?
PD: How can i check if the drivers are working properly?
Click to expand...
Click to collapse
Look for the drivers in KFU... if not u can Google kindle fire drivers
Sent from my Kindle Fire with CM9
BiteBlaze said:
Look for the drivers in KFU... if not u can Google kindle fire drivers
Sent from my Kindle Fire with CM9
Click to expand...
Click to collapse
would you do me a favor? please, if you have cm9 can you upload screenshots of this specific screens on your kindle?
-locked screen on portrait mode.
-screen when you plug your kindle to your computer and it ask you to mount as USB massive storage on portrait mode.
I will try to restock it this way cuz i already tried with the KFU drivers and is not working and i dont know if i have adb enabled on the kindle.
http://db.tt/dPqw4dTv
Here... hope this helps!
Keep in mind that this is a custom version of Cm9 I am working on
Sent from my Kindle Fire with CM9
Sorry, forgot other link http://db.tt/BUdgrORZ
Sent from my Kindle Fire with CM9
BiteBlaze said:
Here... hope this helps!
Keep in mind that this is a custom version of Cm9 I am working on
Sent from my Kindle Fire with CM9
Click to expand...
Click to collapse
Thank you, believe it or not that picture helped me a lot, i was able to access the sd card and copy the original update, now I'm charging the kindle in order to restore it being blind. God help me, I've been watching lots of videos. Wish i could use adb.
gustavosuarez4 said:
Thank you, believe it or not that picture helped me a lot, i was able to access the sd card and copy the original update, now I'm charging the kindle in order to restore it being blind. God help me, I've been watching lots of videos. Wish i could use adb.
Click to expand...
Click to collapse
Well, its good that you figured it out
Sent from my Kindle Fire with CM9
I missed it I believe and just "fastboot reboot"
after installing twrp recovery in th 6.3 root by jcase.
Now I'm stuck at the yellow fire and adb does not recognize my device any more and fastboot says waiting for device.
Did leaving this line out brick it? I got too excited after seeing the recovery screen I must have missed the line. I'm scared to do anything. Please help.
KennyCap said:
I missed it I believe and just "fastboot reboot"
after installing twrp recovery in th 6.3 root by jcase.
Now I'm stuck at the yellow fire and adb does not recognize my device any more and fastboot says waiting for device.
Did leaving this line out brick it? I got too excited after seeing the recovery screen I must have missed the line. I'm scared to do anything. Please help.
Click to expand...
Click to collapse
connect it and hit normal boot in kfu and when it says waiting for device turn the kindle off by holding the power button then turn it right back on and it will connect during boot
KFU utility? or unbrick? I tried to use the utility to root option 2 but I believe I had the path wrong. I had adb set up correctly cuz it recognized my device and I made it all the way to flashing the recovery img.
I'm not that command line savy any help would be greatly appreciated thanks
KennyCap said:
KFU utility? or unbrick? I tried to use the utility to root option 2 but I believe I had the path wrong. I had adb set up correctly cuz it recognized my device and I made it all the way to flashing the recovery img.
I'm not that command line savy any help would be greatly appreciated thanks
Click to expand...
Click to collapse
Oh I thought you had fff and twrp installed already where are you in the process and what's going wrong
Sent from my Hellfire Kindle using Tapatalk 2
i was rooting using the 6.3 method I made it through the first set of command lines. I installed the twrp.img. i saw it on my kf's screen. I got excited cuz I've been at it for a few hours typed fastboot reboot without the idme oem 500 something(sorry from memory I know thats not right) So the device rebooted into fast boot(yellow triangle with fire) and immediately tried to download drivers as the device was no longer recognized by fastboot(waiting for device) or adb (daemon started but no connected device) although after reinstalling the driver through kfu its now recognized in fastboot but not kfu. i think it has something to do with putting kfu in platform tools. So I know I'm not bricked just not sure where to start I'm gonna try the command line I believe I missed or a couple right before it.
KennyCap said:
i was rooting using the 6.3 method I made it through the first set of command lines. I installed the twrp.img. i saw it on my kf's screen. I got excited cuz I've been at it for a few hours typed fastboot reboot without the idme oem 500 something(sorry from memory I know thats not right) So the device rebooted into fast boot(yellow triangle with fire) and immediately tried to download drivers as the device was no longer recognized by fastboot(waiting for device) or adb (daemon started but no connected device) although after reinstalling the driver through kfu its now recognized in fastboot but not kfu. i think it has something to do with putting kfu in platform tools. So I know I'm not bricked just not sure where to start I'm gonna try the command line I believe I missed or a couple right before it.
Click to expand...
Click to collapse
OK cool so you have twrp and fff flashed.... do like I said before hook it up in kf utility hit the number for normal boot and it will say waiting for device.. turn your kindle off by long pressing the power button and then turn it back on and it will connect and switch to normal boot wile the kindle is turning on
if our using just adb in a command promp type this
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Sent from my Hellfire Kindle using Tapatalk 2
Thanks for the advice. The problem was I had the wrong path for kfu. I have rooted an Evo an epic and my transformer all fairly easy. That actually took me around 4 hours. I really should use adb more. That was my sister's KF I was rooting. I couldn't stand to see her using it stock like that. I got Hell Fire up and running. Thanks for trying to help.
Sent from my PC36100 using xda premium
KennyCap said:
Thanks for the advice. The problem was I had the wrong path for kfu. I have rooted an Evo an epic and my transformer all fairly easy. That actually took me around 4 hours. I really should use adb more. That was my sister's KF I was rooting. I couldn't stand to see her using it stock like that. I got Hell Fire up and running. Thanks for trying to help.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
No problem glad you got it going and good choice for a rom
Hello, my kindle fire is stuck on the kindle fire logo, i have tried to hold the power button to do a reset, but it just stays on the logo after the reset. I don't have TWRP installed. I have attached an image to the post that shows the driver. I have tried to use the kindle fire utility, but my kindle appears offline. I will be very grateful to anyone that can help.
Thanks In Advance,
Zachary.
kinfauns said:
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on device drivers.
"Android ADB Device" typically means the device is in fastboot mode and you cannot use adb while in fastboot mode.... you must use fastboot.
With your KF off and disconnected from your work computer, run this command...
Code:
fastboot -i 0x1949 getvar product
and then connect it to the computer. The KF will turn on automatically. The computer will say "<waiting for device>" for a bit, but if the command works, it will eventually return "product: kindle" as output. If that works, you can actually flash TWRP from there, but if you are anxious for it to do something again...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
should get it booting normally again. If it doesn't, look at the link I gave you and focus on getting your drivers fixed. You won't be able to execute any commands (fastboot or adb) through Windows if the device drivers don't work. You might want to go back to Firekit if drivers remain problematic for you.
Everything you need to know to fix your KF is in that link at the beginning of my post, including the commands you need to run. At the bottom of post #3 is also another link to a how-to root/install ROMs page.
Click to expand...
Click to collapse
Try this. Originally posted by kinfauns.
Next time you have an issue search the forum before making a thread.
Sent from a thingymajig that sends things.
Can you please walk me through the whole process? Are you talking about cmd???
When i type it in there it says fastboot is not recognized as an internal or external command .
As mentioned your answers are in the kinfaux "beginners guide".
Sent from my Galaxy Nexus using xda premium
veeman said:
Try this. Originally posted by kinfauns.
Next time you have an issue search the forum before making a thread.
Sent from a thingymajig that sends things.
Click to expand...
Click to collapse
What did you do to the KF to end up with it in it's current position? Prior to the current issues have you ever used ADB or the Kindle Fire Utility to connect to your KF? If not, or even if so, you need to read the entire Kindle Fire for Beginners. The entire second post will take you through installing the Kindle Fire Utility and verify you can connect to your KF. When that is done you can use it as josepho1997 suggested.