Develop Bugs

[Q] Kindle fire stuck in re-boot mode

Not sure what's going on here.. I unrooted my kindlefire with update.zip but I forgot to wipe to factory reset before i flashed update.zip and when i rebooted my kindle i noticed that A ! symbol popped up with "Sorry" that says "The application Calendar Storage (process com.android.providers.calendar) has stopped unexpectedly. Please try again" That isn't the only problem, i click force close and another prompt comes up saying "The process android.process.acore has stopped unexpectedly. Please try again" It waits a few seconds, then proceeds to do a fast reboot? It comes up with the yellow kindle fire and immediately after it boots up it shows the errors.
Not sure what to do. Tried installing TWRP but the kindle doesn't stay on long enough so right now I'm pretty unconvinced of anything..
Any help would be greatly appreciated.

You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...

Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
I'm not sure how to get there.. I don't have any form of backup installed. It's on the complete default rom
Edit: Found out how to get to factory reset, only to discover that I need a 40% charge, when mine is less than 5% and won't charge any more because of my problem

Still haven't figured this out. Can't use my kindle at all until this is fixed :/

iKrotos said:
Still haven't figured this out. Can't use my kindle at all until this is fixed :/
Click to expand...
Click to collapse
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.

kinfauns said:
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.
Click to expand...
Click to collapse
Read the beginners guide for KF, Found about about ADB fastboot etc. Going to install ADB tomorrow and try to figure this all out. Thanks.

I can't do this. It's been over a month. My kindle is finished..

iKrotos said:
I can't do this. It's been over a month. My kindle is finished..
Click to expand...
Click to collapse
"I can't do this"
Well that explains everything, doesn't it? It's a good thing you explained your problem in such great detail or I might spend time trying to help you fix your Kindle thinking you "could" do it. Phew. Saved us all a lot of time, thank you.

I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?

LaszloToth said:
I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?
Click to expand...
Click to collapse
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.

Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2

soupmagnet said:
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.
Click to expand...
Click to collapse
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
Thanks again fro the help!
---------- Post added at 02:31 PM ---------- Previous post was at 02:24 PM ----------
kishorev said:
Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.

Had a similar problem of rebooting every 10 sec or so..I left it on charge overnight and it worked..it got charged decent enough for me to help recover it..
Just try charging it overnight it might just work..I always feel using factory cable shd be the last resort
Sent from my Kindle Fire using Tapatalk 2

LaszloToth said:
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.
Click to expand...
Click to collapse
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.

soupmagnet said:
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.
Click to expand...
Click to collapse
So instead of using fastboot to wipe the user data, I should use it to install TWRP? Can you give me the fastboot command for that? Or can I do that with KFU once I plug in the factory cable?

http://forum.xda-developers.com/showpost.php?p=23747804

Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.

same problem with kindle fire.
LaszloToth said:
Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.
Click to expand...
Click to collapse
hi, i am new here and i got exact the same problem with you, i just ordered the factory cable, can you please give the step by step procedure on solving this problem with the factory cable. your help will be appreciated, thanks.

Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
:good::good::good::good::good::good: works for me thank you

ok, today i had the same problem because i didn't wipe the factory restore!
The solution WASN'T the Factory Cable (I was considering buying one)!
Very easy:
Linux and SOUPKIT! were the solution, when the tablet boots up immediately hit the install recovery, after installing recovery, just set to boot into recovery.
Now is very much you can do (ex. wipe everything and than install update.zip all over)
Very much thank you to the guy who made SOUPKIT! (u've saved my S many many times )

Erased EVERYTHING

I accidently erased everything from the KF2, all I have on it now is the recovery.
How can I get a rom back on the device?
When I plugged it in the computer under Device Manager it says Portable Devices >> F:/
When I go to my computer to try to enter f:/ its inaccessible.
How can I fix this?
Thanks!

Same issue here. Understood the instruction to wipe everything before installing ROM to mean "System" and "Internal Storage" as well. Now the downloaded ROM and "gapps" zip files are gone...
Found something called "ADB Sideload" in TWRP, could that help?
Like the OP, would appreciate some help. Kindle is a brick for now...
chipsndukes

Back Up & Running
First You need a Fastboot Cable.
Run The Recovery Tool. (Options 1 then 2)
When its completed unplug the Fastboot Cable and press and hold the power button until the KF2 turns off.
Turn it back on and you are all set to Root it!
Rooting
[ONE-CLICK] Automated Freedom-Boot and TWRP installer

OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes

chipsndukes said:
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
Click to expand...
Click to collapse
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.

iytrix said:
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
Click to expand...
Click to collapse
Unfortunately usb Mount doesn't work in the kf2 twrp. I would love the option.
You CAN adb sideload from twrp though.
--
Sent from my Kindle Fire 2, CM 10.1

What I did above is the easiest way, the sideload didn't even work!

chipsndukes said:
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Click to expand...
Click to collapse
One change to the above statement. I did have to get out of fastboot mode, but it was confusing how because the terminal emulator was now gone.
I did this instead via a command window with the Fire plugged into the computer. I sent the "fastboot -i0x1949 oem idme bootmode 1" command while in the root directory for the KF2_SRT_10.2.3 restore package, there is a fastboot.exe file there.
Hope that helps.
chipsndukes

[How To] Fix Stock Kindle Fire 2 Bootloop

A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.

hexd said:
A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
Click to expand...
Click to collapse
Where do i enter this in when I'm in fastboot?

Karetus said:
Where do i enter this in when I'm in fastboot?
Click to expand...
Click to collapse
You need to use the fastboot application. You can get it either via the Android Development Kit (just google for it) or just use it from any other source (I know the FlashTool for Sony phones has it along with ADB). Once it is on your PC, open a command prompt window to that folder and run it from there.
Just remember you need the Kindle to be in FB Mode (the screen has a picture of a red and green stoplight on it) and you need fastboot drivers installed for the device (this is a bit tricky for Win8, no problem for Windows 7 though).

hexd said:
You need to use the fastboot application. You can get it either via the Android Development Kit (just google for it) or just use it from any other source (I know the FlashTool for Sony phones has it along with ADB). Once it is on your PC, open a command prompt window to that folder and run it from there.
Just remember you need the Kindle to be in FB Mode (the screen has a picture of a red and green stoplight on it) and you need fastboot drivers installed for the device (this is a bit tricky for Win8, no problem for Windows 7 though).
Click to expand...
Click to collapse
I'm at a screen with a blue arrow a and yellow text that says "fastboot mode"

Karetus said:
I'm at a screen with a blue arrow a and yellow text that says "fastboot mode"
Click to expand...
Click to collapse
Please make sure that you have a Kindle Fire 2 (or at least something in the second generation Fire range). It might help if you take a picture of the device in fastboot mode and post it here.
Also did you boot the kindle into fastboot mode using a factory cable, or using a command from Android itself (it would have involved adb shell).

hexd said:
Please make sure that you have a Kindle Fire 2 (or at least something in the second generation Fire range). It might help if you take a picture of the device in fastboot mode and post it here.
Also did you boot the kindle into fastboot mode using a factory cable, or using a command from Android itself (it would have involved adb shell).
Click to expand...
Click to collapse
From the computer. KFF Aide. I'm still stuck I have been looking for hours.

hexd said:
A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
Click to expand...
Click to collapse
my kindle fire hd 7 7.3.1 just went into a boot loop. it is recognized by my computer the drivers work it says device cant startup. adb wont work. how do i get it into fast-boot without a factory cable

JORDANZ1998 said:
my kindle fire hd 7 7.3.1 just went into a boot loop. it is recognized by my computer the drivers work it says device cant startup. adb wont work. how do i get it into fast-boot without a factory cable
Click to expand...
Click to collapse
Trying to do any work on a Kindle without a cable is a total pain. If you own the device just pay the few dollars to get one and make your life easier.
If you cannot get into ADB with full root, or a 3rd party recovery that was already installed you will need the cable to fix things.

[Q] Fastboot is stuck and kindle isn't showing up

So I was working on my kindle iv broken it bootlooped it flashed a rom that just didn't work ect and fixed all of these problems.however recently I went to flash a nightly cm on my kindle and it had no notification bar or action bar.
iv seen It before I used twrp to put my kindle into idme bootmode 4000 fast boot came up like normal after I rebooted.
I used the recovery tool to restore the stock stuff and used fast boot CMD to reboot my kindle from my windows computer.
However it rebooted to fastboot I tryed reboot-boot loader command and same thing hard reset didnt work ether.
I'm at a lose I was trying to reboot it again today and now fastboot commands stopped working as it doesn't show up in adb
So what do I do or want can I try not afraid to mess with anything and I'm pretty good with the cmd adb and fastboot stuff iv googled it and spent a few hours the solutions I found didn't work and it's still broken any help would be cool

axis.fire said:
So I was working on my kindle iv broken it bootlooped it flashed a rom that just didn't work ect and fixed all of these problems but recently I went to flash a nightly cm on my kindle and it had no notification bar or action bar iv seen I before I used twrp to put it in idme bootmode 4000 fast boot came up like normal after I rebooted I used the recovery tool to restore the stock stuff and used fast boot to reboot my kindle from my windows computer but it rebooted to fastboot I feed reboot-boot loader and same thing hard reset don't work ether I'm at a lose I was trying to reboot it again today and now fastboot commands stopped working as it doesn't show up in adb
So what do I do or want can I try not afraid to mess with anything and I'm pretty good with the cmd adb and fastboot stuff iv googled it and spent a few hours the solutions I found didn't work and it's still broken any help would be cool
Click to expand...
Click to collapse
First off, please try to use punctuation when describing your problem. I've had to read this five times just to try and get some comprehension of what you're trying to say. I have no idea where one statement ends and the next one begins.
Second...What device do you have? You posted this in the Kindle Fire 2 forum but you attempted to use a command that only works on the 1st generation Kindle Fires? Do you know the difference between the 1st and 2nd generation devices? Have you read the FAQ posted in the appropriate Q&A forum for your device? If so, what specifically are you trying to accomplish (other than simply unbricking your device)?

soupmagnet said:
First off, please try to use punctuation when describing your problem. I've had to read this five times just to try and get some comprehension of what you're trying to say. I have no idea where one statement ends and the next one begins.
Second...What device do you have? You posted this in the Kindle Fire 2 forum but you attempted to use a command that only works on the 1st generation Kindle Fires? Do you know the difference between the 1st and 2nd generation devices? Have you read the FAQ posted in the appropriate Q&A forum for your device? If so, what specifically are you trying to accomplish (other than simply unbricking your device)?
Click to expand...
Click to collapse
Sorry il work on that. I know the difference between the devices I have a kindle fire 2 and I have reviews the FAQ thread. My device is stuck in fastboot however I'm confident that it will work if I can get it to boot and not go into fast boot. I'm trying to reboot the device normally however the adb commands and fastboot commands are not working and the device isn't listed under ether while it is connected to the computer. It does however show up in my device maniger thank ou for taking the time to review my problem.

You can work on getting your drivers working properly, or you can set up a Linux LiveUSB and install SoupKit. SoupKit will give you the ability to effectively send fastboot commands in the terminal without worrying about properly configured USB device drivers.
On the HD models, performing a hard reset on the device will take them out of fastboot. It may not work on the KF2, but you may want to try that first, just in case.

soupmagnet said:
You can work on getting your drivers working properly, or you can set up a Linux LiveUSB and install SoupKit. SoupKit will give you the ability to effectively send fastboot commands in the terminal without worrying about properly configured USB device drivers.
On the HD models, performing a hard reset on the device will take them out of fastboot. It may not work on the KF2, but you may want to try that first, just in case.
Click to expand...
Click to collapse
I was able to issue the commands fine until my hard reset. It was persistent on going back to fastboot nomatter wht command I issued.
It will not take commands now however I will try the soupkit I'm slightly finisher with Ubuntu and fedora so it shouldn't be hard

axis.fire said:
I was able to issue the commands fine until my hard reset. It was persistent on going back to fastboot nomatter wht command I issued.
It will not take commands now however I will try the soupkit I'm slightly finisher with Ubuntu and fedora so it shouldn't be hard
Click to expand...
Click to collapse
To get out of fastbot mode (says fastboot on the display), you generally only have to enter...
Code:
fastboot -i 0x1949 reboot
If that doesn't work, and you still reboot into fastboot mode, try to change the bootmode to normal...
Code:
fastboot -i 0x1949 oem idme bootmode 1
Also, while in recovery, there should be an option to boot normally, assuming you have a working OS to boot to.
And you need to make damn sure all of your stock partition images are restored before you reboot or your device may get hard-bricked, for good.

odd situation, bricked kindle. need help!!

So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.

piffdaddy420 said:
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
Click to expand...
Click to collapse
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs

monster1612 said:
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, actually i am using windows 10. My thinkpad has windows 7, so i will try to do this using windows 7. i will post back with results. its funny, out of everywhere i looked nobody mentioned windows 8+ having to disable enforcement. actually it will probably just be easier just to disable the enforcement. ill give it a try and report back.

still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?

piffdaddy420 said:
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
Click to expand...
Click to collapse
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
ok so im in fastboot mode now. i checked out that thread that you sent. but i have another problem, how am i supposed to get cm and gapps onto the kindle? is there a command i can use to put the files on the internal sd card? and i cant do the adb commands to push the stack, and do the other commands adb since i couldnt get it loaded to begin with, i am not able to enable developer mode. it would be nice if i could do those commands in fastboot mode. there has to be a way to do this....

maybe if someone can send me the stock partitions that they backed up stock boot partititons when they did it. maybe if i flashed them onto my kindle it will allow me to get it to atleast boot up so i can get into adb.
right now this is completely bricked.

can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.

piffdaddy420 said:
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
Click to expand...
Click to collapse
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.

piffdaddy420 said:
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
Click to expand...
Click to collapse
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs

monster1612 said:
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
yes it does

piffdaddy420 said:
yes it does
Click to expand...
Click to collapse
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs

monster1612 said:
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.

piffdaddy420 said:
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
Click to expand...
Click to collapse
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.

piffdaddy420 said:
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
Click to expand...
Click to collapse
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.

monster1612 said:
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
Click to expand...
Click to collapse
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)

piffdaddy420 said:
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
Click to expand...
Click to collapse
anyone have any suggestions or can help me with my situation?? i am wondering if maybe someone could just send me the original backed up bootloader, boot, and recovery. i tried the original ones that were posted with that srt file. but it included everything but the bootloader. which is what i need. i know that in original thread they recommended to back up your original files (i was unable to do so because my kindle woulnt boot so i couldnt use adb to back up these files).
so if someone on here can send me the original files so i can try to get my kindle booted back up. that so far is my only theory because i tried everything else. i know people with advance knowledge would be able to help me in a heartbeat. any devs out there wanna help me out? i would greatly appreciate it!

anyone?