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 )
Related
[Q] Attempting to Root, stuck at "Setting Recovery Bootmode. Please Wait..."
Okay, so I decided to root my Kindle Fire, figuring it wouldn't be too complicated. I'm generally great at technical stuff, and if I don't know how to do something then I learn quickly. But I can't figure out what, if anything, I'm doing wrong.
I have downloaded and extracted KFU, installed the drivers, and run the .bat with no problems. However, when I begin the permanent root process, it activates fastboot, installs TWRP, and then nothing. It gets to where it says "Setting Recovery Bootmode. Please wait..." and it doesn't get any further. I've been waiting for maybe an hour now? Surely it's not supposed to take that long, what's going on?
I just realized I put this in the wrong thread, I apologize for that lol.
http://forum.xda-developers.com/showthread.php?p=23747567
http://forum.xda-developers.com/showthread.php?p=23747671
http://forum.xda-developers.com/showthread.php?p=23747804
Will give you some insight to your problem and how to fix it.
Those links all lead to the same page? Thanks though, that helps me understand what SHOULD be happening, but I still don't know why it isn't working..
Well, let's start with...When you turn the device on, what happens?
Uh, what exactly do you mean? It'll turn on just fine if I stop the root and set it back to normal mode. While it's plugged in attempting to do that it just sits at the kindle fire logo.
The links that I gave you point to different posts from the same guide, but I'm learning today that the XDA app has trouble with multiple post links from the same thread.
But, that's not important right now. What is important, is the reason I directed you to that page in the first place. True, it does give you an idea of what's supposed to happen, but it also tells you about the different bootmodes and what it means when you are stuck at the Kindle Fire logo, along with a whole host of other things.
It is very important for you to understand this because it will aid you in understanding that your "problem" is not really a problem at all and that your Kindle is doing exactly what it's supposed to do.
Knowing this, your issue should be relatively easy to fix. I would suggest you go back over that thread and try to get an idea of what's going on.
I understand that it's in fastboot mode. Like it should be. I understand what recovery mode is and does. What I don't understand is why it is taking so long to get past this particular step of the rooting process. My issue isn't that it's stuck on the boot screen and I don't know how to get past that. My issue is that it won't root. After installing TWPR, when it says "Setting Recovery Bootmode" blah blah blah, which I'm guessing means it is setting up TWPR to do what it should do, it doesn't get any further. KFU just stops, telling me to "Please wait..." for hours.
Also, if any of that comes off as rude or anything, I don't intend for it to sound that way lol. I do appreciate your help. I'm just a bit frustrated with this.
1. Which Kindle Fire logo is it booting to, stock or KF w/android
2. Are you familiar with the command line interface?
You need to see if TWRP was ever installed in the first place. Enter the command to set it to recovery:
fastboot -i 0x1949 oem idme bootmode 5001 (for stock bootloader)
or
fastboot oem idme bootmode 5001 (for FFF KF w/android)
...then reboot
If it boots into recovery then all you need to do is install FFF (if it isn't already)
If it doesn't boot into recovery you need to install it manually.
It boots to the logo with the android.
And I am familiar with that, yes. I messed around with some of the commands after reading through the page you linked me to, but it doesn't recognize the commands I enter. I know that you are supposed to change the directory, and I did that, but it still didn't work. I dunno if I'm just not going to the right place, or I have the folder saved somewhere that won't work (which would be my desktop), or if I'm just dumb and doing it completely wrong. I will try those commands now, though.
kodasaur said:
It boots to the logo with the android.
And I am familiar with that, yes. I messed around with some of the commands after reading through the page you linked me to, but it doesn't recognize the commands I enter. I know that you are supposed to change the directory, and I did that, but it still didn't work. I dunno if I'm just not going to the right place, or I have the folder saved somewhere that won't work (which would be my desktop), or if I'm just dumb and doing it completely wrong. I will try those commands now, though.
Click to expand...
Click to collapse
You need to fix your drivers
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
The problem is explained in detail here:
http://forum.xda-developers.com/showthread.php?p=25444709
...also, in that thread, I think gedemis has made a fix for the driver issue, though I'm not sure how well it works.
The drivers are installed properly, it shows up in the device manager as "Android Composite ADB Interface". Still not getting anything.
kodasaur said:
The drivers are installed properly, it shows up in the device manager as "Android Composite ADB Interface". Still not getting anything.
Click to expand...
Click to collapse
Does any device appear when you enter this? With those drivers, the Kindle should be able to be detected, and you can flash the bootloader.
Code:
fastboot devices
I'm sorry, I guess I should have explained it a little better.
When your computer cannot communicate with your device, 99.99999% of the time it's caused by the drivers, regardless of what Windows says. Sometimes you can just reinstall over the old ones, but you usually have to uninstall (and delete if possible) the old ones, reboot the computer and reinstall the drivers manually. The first link I gave you has detailed instructions on how to install your drivers. The second link that I gave you explained the problem in detail and provided information for making sure your drivers are configured properly.
In rare cases, switching out your USB cable or trying different USB ports is enough to fix the problem but chances are, it's more likely to be the drivers.
Go back, read, and make absolutely sure you've done EVERYTHING you can to fix your drivers because based on what you've told us, that's probably what your problem is.
Now, on the chance that you have actually done this but are having trouble communicating it effectively, we are going to need some more detailed information as to what steps you have taken to enter the above posted "fastboot" commands and, if any, what type of error messages you've received.
The more detail you're able to provide, the better, as it will help us pinpoint your exact problem and eliminate any possibility of user error.
But it IS commumicating with the Kindle? At least up until that step. It does everything else that it's supposed to.
I've uninstalled the drivers and manually reinstalled them. I don't know what else to do.
Where exactly am I supposed to enter these commands? I keep getting "fastboot is not a recognized internal or external command, operable program, or batch file"
kodasaur said:
But it IS commumicating with the Kindle? At least up until that step. It does everything else that it's supposed to.
I've uninstalled the drivers and manually reinstalled them. I don't know what else to do.
Where exactly am I supposed to enter these commands? I keep getting "fastboot is not a recognized internal or external command, operable program, or batch file"
Click to expand...
Click to collapse
Shift+right click on the KFU "tools" folder containing fastboot.exe and select "Run in Command..."
The prompt that opens up will be where you enter your fastboot commands. Make sure you understand the command before you enter it, especially if it involves the bootloader.
Okay, thanks. When I use that command, it returns either a series of question marks, or "0123456789ABCDEF". Which I now see means that it's in fastboot mode. Now what?
When it returns 123456789ABCDEF enter the following command
fastboot -i 0x1949 oem idem bootmode 4000
...then reboot
When I do that I get
... FAILED (remote failure)
kodasaur said:
When I do that I get
... FAILED (remote failure)
Click to expand...
Click to collapse
Sorry, typo...
fastboot -i 0x1949 oem idme bootmode 4000
Alright, that worked lol. After rebooting?
Alright, so my Kindle Fire is bricked, and was stuck at the boot screen (the default Kindle Fire loading screen) after attempting to root it with an outdated tutorial (didn't know this at the time, but the program is called SuperOneClick) then I made another foolish attempt to install TWRP (I THINK I did it to restore the Kindle back to the factory software/defaults but I'm not sure exactly what I was thinking as it was probably 2 weeks ago)... After doing a little more research, I made my way back here because the forums have been resourceful in the past concerning my Evo 4G... After that I found a very similar thread and decided to try my luck once again, had extreme problems trying to get my computer to recognize the Kindle (on both Windows 7 and Ubuntu), all of my settings were correct and are now correct to the best of my knowledge (adb/udev files included)... To this day I still have no luck getting my computer to recognize it, after reading through numerous tutorials/threads I've resorted to buying a "factory cable" because the battery died (while plugged in the wall/usb both it just flashed on and off) and I was told by another member here that it is the only way to bypass the dead battery... Yesterday I've received the "factory cable", but the Kindle still flashes on and off while it is plugged in via usb, and still doesn't show up in device manager, or in command prompt/terminal via adb devices/lsusb commands even after multiple restarts and adb kill-server, adb start-server have been applied... Can anybody help guide me through this??? My faith is running extremely dry at this point, and I'm willing to try just about anything to get this thing right, and learn a few things in the process!!!
Thanks in Advance,
CJ
Firekit http://forum.xda-developers.com/showthread.php?t=1430038
I will help you
And you have done sooo much!!! I've spent a total of at least 12 hours trying to figure this thing out, and getting the terminal to recognize it CORRECTLY is the furthest I've seen so far, even if it was for only one command, for a few seconds... My charging attempt has yet again failed miserably, BUT I have however bypassed the boot loop for about 30 seconds, still staying at the default Kindle Fire screen (tried a random tutorial to trick the Kindle into charging, it MIGHT have worked because it was only plugged in via usb for about 1 minute after this trick but instead of the orange light coming on the Kindle just stayed in the power off looking state)... Even with the boot loop bypassed though, fk did not seem to recognize the device so I'm even more lost than I was originally lol...
EDIT: I am positive the Kindle is receiving a charge, the charge light isn't on BUT it is charging!!! Regardless of the power state no command is working to recognize the device, including "adb devices", "lsusb", and "fastboot getvar product"... I guess that it's possible that one of my files have gone corrupt so I'll check them out again but other than that I'm stumped...
After many trial and error's, and with the amazing guidance of "Thepooch", we have finally unbricked the KF!!! Thank you for your time and patience, if it wasn't for you I would've probably given up by now
Great Job Pooch! You da' man. Glad you got it working!
Was an adventure your welcome though
Sent from my Amazon Kindle Fire using Tapatalk 2
An adventure is an understatement, for me at least but in the end you came through once again and it is up and running like a champ!!!
Sent from my GT-P3113 using Tapatalk 2
Bricked Kindle Fire
I was having trouble using KFU. I wanted to install JellyBean 4.1 and after finding a post to perform some command lines the KFU finally found my KF. I installed the permanent root (i thought) and it rebooted the KF into fastboot it stated. Now it loads to a logo and stops. If I hold the power button (5-10 secs) it shuts off and that is the only thing I can do. It does not show up in my device manager so I feel I killed it. I know you guys have the answer and I apologize in advanced for being a newbie but I am desperate. It looked so easy in the YouTube videos but as always that is the famous last words...
gtc954 said:
I was having trouble using KFU. I wanted to install JellyBean 4.1 and after finding a post to perform some command lines the KFU finally found my KF. I installed the permanent root (i thought) and it rebooted the KF into fastboot it stated. Now it loads to a logo and stops. If I hold the power button (5-10 secs) it shuts off and that is the only thing I can do. It does not show up in my device manager so I feel I killed it. I know you guys have the answer and I apologize in advanced for being a newbie but I am desperate. It looked so easy in the YouTube videos but as always that is the famous last words...
Click to expand...
Click to collapse
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Thepooch said:
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Click to expand...
Click to collapse
You are amazing!!!!
GameGuru41 said:
You are amazing!!!!
Click to expand...
Click to collapse
Naww lol don't forget to hit the than button lol
Thank you!!
Thepooch said:
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Click to expand...
Click to collapse
Pooch thank you buddy very much!! I thought I owned a black brick. Now with that newbie mess out of the way could you help with what went wrong using KFU? It would not find my KF and only when I found something about typing in some command lines (similar to your fix) did KFU finally state the KF was online. I then chose option 2 used the permanent root function and viola a brick. I of course followed all the previous directions about loading drivers and making sure the ADB composite was in the device manager. Can you point me in the right direction?
Thanks again...
gtc954 said:
Pooch thank you buddy very much!! I thought I owned a black brick. Now with that newbie mess out of the way could you help with what went wrong using KFU? It would not find my KF and only when I found something about typing in some command lines (similar to your fix) did KFU finally state the KF was online. I then chose option 2 used the permanent root function and viola a brick. I of course followed all the previous directions about loading drivers and making sure the ADB composite was in the device manager. Can you point me in the right direction?
Thanks again...
Click to expand...
Click to collapse
If your main intent is to flash a ROM no need to root simply just allow installation from unknown sources under device in your kindle settings when you plug it it disconnect the USB transfer app. Then select option for twrp it should reboot then swipe open and stop USB app again this time send fff. Then use the boot loader to enter recovery when there select backup make a backup that you will later name noroot631 without spaces after you have created a backup reboot to os then use the USB app to place a ROM zip and a gapp zip on your SD card but do not place it inside of a folder this is considered the root of your sdcard then boot back into recovery . Go to install make sure you can locate the files you intend to flash then use the back button or home button in upper right to return to twrp main screen. At this point you have a safety net and a backup and you are getting familiar with the functions and learning how to navigate in twrp. Now for a flash if you are gonna flash modaco for the stock like adventure its not required to perform any wipes just simply flash and reboot. No gapps required either now you are rooted If you intend to flash a different flavor like cm7 cm9 or jelly bean it gets a bit more technical . After placing ROM and appropriate gapps on your SD card this time your gonna wipe and its very important you do so!!! First go and wipe factory reset then wipe cache then wipe dalvik here's the scary part wipe system do not reboot you have no system!! There is no need to wipe sdcard or external storage as it is called in the new twrp if you did you would have nothing to flash then hit the home button above right taking you back to the twrp main screen this time select install tap on the ROM zip swipe to install then home again install again this time select gapps swipe to install select reboot and system if prompted. It will reboot initial boot takes time I would say 5-8 mins longer and then you need to be a little alarmed If your greeted by an android for account setup your good congrats your rooted. If boot takes longer than 10 mins hold power button return to recovery restore your backup after the wipes I mentioned above try again later with new ROM and new gapps. Good luck as for kfu awhhh so many things broken for so many people near impossble to say why so many fail to root frankly operator error accounts for at least 80% of failures could be more like 90% . Common mistakes thinking you need to root to flash a ROM, bad drivers windows is terrrrrible,wrong cable,using a 3.0 USB port instead of 2.0, and general miscommunication between the device your computer and the utility. Whewwww all that said install twrp install fff if you can 100% verify that you have both and you know how to use both and move files to your SD card and have made a backup every time before you flash. Then flash Awaaaayyy!!! Hope I didnt miss anything oh and the usual disclaimer know what your doing or you shoot your eye out lol and of course I'm not responsible if you brick your kindle!! Good luck
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
Ohh and if you can't read that I'm sorry for the novel punctuation and such costs more
---------- Post added at 11:11 PM ---------- Previous post was at 10:57 PM ----------
PS as well after creating the huge safety net I explained above go ahead after your backup and select permanent root with superuser you have a backup and a bootloder that resets your boot mode have it but IMO that function is broken for too many people these days I don't recommend it because if our gonna flash a ROM all ROMs are rooted so what's the point?
Thepooch said:
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Thepooch said:
Common mistakes thinking you need to root to flash a ROM, bad drivers windows is terrrrrible,wrong cable,using a 3.0 USB port instead of 2.0, and general miscommunication between the device your computer and the utility.
Click to expand...
Click to collapse
So that's probably why I bricked my kindle was due to using a 3.0 port. I don't see how that would affect it though. Either way, I'm trying to charge up the battery on my kindle some since it drained itself to dead over night when I gave up in frustration and went to sleep. Then I'm going to try to unbrick using your methods mentions above and on the first page. If none work you'll be hearing from me again. lol
Well switching to the USB 2 and those commands through dos worked perfectly. Now if only it would download the twrp file. Just can't get a break with this stupid thing.
http://forum.xda-developers.com/showthread.php?t=1836005 twrp problem
where are the simple, easy to follow directions...
to root my Kindle..
All this stuff is overwhemingly confusing for a non-computer speaking person..
I tried to follow the directions listed here:
http://forum.xda-developers.com/showthread.php?t=1638452
but got really confused.
So I read through this thread: http://forum.xda-developers.com/showthread.php?t=1399889 and got even more confused.
I've rooted my Samsung Galaxy SII, but that used a simple one-click process. Trying to decipher the procedures for rooting a kindle fire is confusing to say the least.
Im begining to think that my stock Kindle is ok...
I'd just assume ship my KF off to someone to root it and install a custom ROM.. i've been reading these threads and forums for 3 days now and I just keep spinning myself in circles...
Thepooch said:
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Click to expand...
Click to collapse
Don't worked here. The triangles keep spinnig and the cmd keeps on <waiting for device>.
Reinaque said:
Don't worked here. The triangles keep spinnig and the cmd keeps on <waiting for device>.
Click to expand...
Click to collapse
Start a new thread and explain your problem in detail.
Hi everyone, I have two kindle fire, I messed with both of them.
I've root them the first one has the problem with the yellow triangle logo stucked. And the other one I've tried to reset it to the factory settings and everything was cool until I hit the TWRP utility and I think I erased everything.
I've see tons of posts regarding rooting and troubleshooting related to rooting and i'm pretty sick of rooting, I think that 3 months is sufficient time, please DON'T POST anything related to rooting.
I'm here asking if anyone knows how to flash all the data ofthe kindle from the pc and been able to install the factory software, firmware (I don't know) from scratch from my pc. Anyone, please?
The first one is probably stuck in fastboot. Try giving it a go with "fastboot oem idme bootmode 4000 && fastboot reboot".
For the second one, "I think I erased everything" is as descriptive as not wanting people to post about your procedure is helpful. What exactly is going on with it? For future reference: http://forum.xda-developers.com/showthread.php?t=1644970
You should also update both FFF and TWRP on both devices once they are working normally.
If i may suggest flashing modaco first after a good wipe everything except your sdcard I believe this will make a smoother transition if you desire to return to stock before returning to stock always do a good wioe to remove remnants of previous roms download the latest stock bin and rename it to update.zip do not place it in any folder just at the root of your sdcard flash in twrp this will also wipe out twrp and fff I really dont recommend doing this lots of people fail at doing the procedure correcty modaco is stock with only the market added try this approach first then you can retain fff and twrp for custom backups.
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
Click to expand...
Click to collapse
To restore back to full factory
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip
8. Let it bootloop about 3 times or so...
If you want FFF and TWRP then flash Stock 6.3.1 Basic from TWRP. This has no root or gapps.
Dasanko said:
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
Click to expand...
Click to collapse
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
jRam90 said:
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
Click to expand...
Click to collapse
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Dasanko said:
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Click to expand...
Click to collapse
Both of the kindles, are damaged. I can't access them. I just can access one by USB.
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Dasanko said:
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Click to expand...
Click to collapse
Thanks a LOT, Dasanko !!!!
jRam90 said:
Thanks a LOT, Dasanko !!!!
Click to expand...
Click to collapse
Ok, So, I have the factory cable. How can I test its Ok?
I have another question, the kindle is pratically empty no system, no sdcard memory, probably corrupted ¿How do I use the factory cable, to format the Kindle and install the Stock ROM again?
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Dasanko said:
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Click to expand...
Click to collapse
Well, I'm at my job now. So I will try this at home, but the shell is not working since system/sh (shell) it's not in the Kindle. I was trying to boot it yesterday with "fastboot boot twrp.img" and nothing. I also tried: "fastboot getvar product" and nothing but I only used the console. Anyway, let's see what happens...
Quick question, I've read that the factory cable puts the Kindle straight into bootmode, ¿So the color of the power button, has something to do with it? ¿I mean how do I know the kindle has entered factory mode? ¿The orange light is an indicator? (With a standard USB Cable I only get the green light with the power button, with the factory cable I first get green light, then orange light)
I've also read that if I can see the Kindle fire logo, the bootloader is Ok. Hence my Kindle is OK, but I can't enter fastboot mode. ¿Can anyone confirm this?
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Dasanko said:
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Click to expand...
Click to collapse
OK, I've finally made myself a working factory cable. And in the device manger I can see the kindle listed as "Android phone" and in that root it says "Android ADB Interface". Look like drivers are not working. Where can I download them?
Those are the proper drivers for fastboot you should be able to use kfu to send twrp and fff to the device if that doesn't work you will need to fastboot flash them
All I get is < waiting for device>. Looks like the drivers are not installed.
Simply hold the power button down while connected when it says waiting then power it back on and it should send also try unplug replug when it says waiting
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
If you would like some help I have some time before work but you must finish your thread for the benefit of others
My Kindle was rooted but I decided to try my hand at installing a custom ROM. However, the ROM I tried would not work and the screen stayed black. However, thanks to TWRP I could install Kindle from Amazon again. The installation went thru smoothly, or so I thought. Now, when I boot the Kindle, I see the Kindle Fire Logo and it stays there. The Computer can see the Kindle as an Android device, Android Composite Device. But Kindle Fire Utility cannot see it so I could try and re-install it again. Any suggestions?
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Dasanko said:
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Click to expand...
Click to collapse
I tried the USB pin short trick but now my Kindle won't turn on at all nor will it charge. Thanks anyways!
i have similar problem ......please need help
After successfully rooting kf with kfu and making a backup ... I did factory reset and flashed a custom rom ... now kindle is stuck on " kindle fire" logo and just keeps flashing and rebooting . My computer recognizes it as android phone ( android adb ) and kfu does too but only for a couple of seconds . During those few seconds I try recovery ... fast boot ...normal boot... n none seem to work . Kf just reboots n returns to boot loop . Any advice is appreciated .. thanks
Start a new thread when you're posting your own issues.
What colour is the "kindle fire" logo when you turn on your KF?
Force Kindle into Fastboot
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Not fastboot get var
ComputerGenuis2.0 said:
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Click to expand...
Click to collapse
fastboot getvar product doesn't seem to do the trick. The kindle seems to be in fastboot mode but the adb shell cannot access the device.
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Used Firekit
Dasanko said:
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Click to expand...
Click to collapse
I have TWRP and FFF installed. However, upon booting into TWRP, the sdcard partition cannot be mounted, to the Kindle that is, and as such, I cannot mount the sdcard to the computer. When I researched this some more, I found that I can fix this by using a command via adb shell. The guide instructed using fastboot to achieve this. When would be the best time to use adb shell?
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Can't use adb
Dasanko said:
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Click to expand...
Click to collapse
The problem at hand is using adb. I can never time it exactly right to open adb. I always get an "error: device not found". Windows even recognizes that Android ADB Interface is plugged in.
Okay, things are getting awfully confusing here.
What exactly is it that you can do and that you cannot do?
For example, are FFF and TWRP functional?
GOT IT!
Thank you! I finally figured out that the wrong driver had reinstalled and that was causing my computer to not be able to use adb shell. I fixed that and voila, I am now running CM9. Thanks again!
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