Related
So I formatted my rooted kindle fire with twrp installed, now whenever I boot I go straight to the TWRP menu, why can/t I boot into a fresh stock ROM?
i assume you told it to boot to recovery (in cm7)
you can use kfu option 1 - bootmode normal
or manually:
adb shell idme bootmode 4000
adb reboot
b63 said:
i assume you told it to boot to recovery (in cm7)
you can use kfu option 1 - bootmode normal
or manually:
adb shell idme bootmode 4000
adb reboot
Click to expand...
Click to collapse
I'm having the same problem, I went into KFU and set option 1 and it shows this
***********************************************
* Activating Normal (4000) *
***********************************************
but doesnt go any further
When trying to install a ROM it says....
E:Cannot load volume /misc!......but it's right after it says that the ROM was installed
where do I insert the command for adb...........for KFU it is reading the Kindle Fire but for some reason when trying to set option 1 it doesn't go further.
It might be good to know that I deleted alot on the Fire in Windows explorer before this happened. Right now on my Kindle fire my
folders are Android, .android_secure, LOST.DIR and TWRP
files are fix_permissions, 3 ROMS, lol- Databasefile, and .config_c38
Any help would be GREATLY appreciated
Ethanzh said:
So I formatted my rooted kindle fire with twrp installed, now whenever I boot I go straight to the TWRP menu, why can/t I boot into a fresh stock ROM?
Click to expand...
Click to collapse
wbales said:
I'm having the same problem, I went into KFU and set option 1 and it shows this
***********************************************
* Activating Normal (4000) *
***********************************************
but doesnt go any further
When trying to install a ROM it says....
E:Cannot load volume /misc!......but it's right after it says that the ROM was installed
where do I insert the command for adb...........for KFU it is reading the Kindle Fire but for some reason when trying to set option 1 it doesn't go further.
It might be good to know that I deleted alot on the Fire in Windows explorer before this happened. Right now on my Kindle fire my
folders are Android, .android_secure, LOST.DIR and TWRP
files are fix_permissions, 3 ROMS, lol- Databasefile, and .config_c38
Any help would be GREATLY appreciated
Click to expand...
Click to collapse
Typing this:
adb shell idme bootmode 4000
adb reboot
In ADB should fix both of y'alls problems
sweetness, Not only did I just learn how to actually use ADB, but it also worked
THANKS
ok that worked great. But any idea why this is happening and how to avoid it from happening in the future?
I'm having the same problem, with "activating normal" stuck.
I also cannot input the command input adb shell idme bootmode 4000 or adb shell in command prompt.
It says that 'adb' is not recognized as an internal or external command.
endari said:
It says that 'adb' is not recognized as an internal or external command.
Click to expand...
Click to collapse
it's a good practice to move kfu to c:\ and rename it to "kfu"
now open a (elevated) command prompt and cd to c:\kfu\tools
now the adb command should work ...
i did the same thing
i did the same thing on accident thinking it was my usb data stick and on top of that i somehow manage to do a complet wipe now it wil only boot up to the kindle fire logo and stay and the only the wtrp 2.0.0 but nothing and my touch screen will only sometime work half [email protected]# i had it usb mounted ounce and only the twrp file was on it nothing inside the file itself iv tried just about everything that was on this site plus the usb ubutun linixi was lost and i want to try this adb but it seems like nothing is installing for my and i really like this kindle fire i had it going so good i just about cried lol cause i had it so fast and clean so could someone e-mail me on how to do this adb iv got the sdk files every file made for the kindle uboot fboot u name it i have it lol but still lost i am a semi noob to all this kindle flashing and rooting i use to have a droid x and was a pro at that plus it was pretty easy lol so my e addy is [email protected] i have my mini hp with me at all time and now my wifes kindle fire and my paper weight for now iv got teamveiwer and i will be sooo willing to ler u log on to my mini to do this for me plz plz plz plz HELP
I am having the same problem here is exactly what i did
rooted
installed android market
installed twrp
made backup in twrp
flashed ics
wasnt happy with the performance of some apps on ics and there were quite a lot of stalls and complete freezes so i used the backup i made in twrp to restore back to original kf rom
most of my apps wouldnt worked and asked me to reinstall them through the kf market. i was unable to access the kf market or the android market as it said there was no connection and to retry even though i could access my email through mail and the internet through browser no problem.
then i decided to do a factory reset through kf rom settings and now twrp starts automatically anytime i try to turn on the kf. i tried to do the recovery again with the backup but the restore factory settings had obviously deleted it along with everything else on the sd card.
has anyone any ideas on how i can get back to the stock kf rom? I am happy with stock kf until hardware acceleration works with ics
thanks in advance
Irish01 said:
I am having the same problem here is exactly what i did
rooted
installed android market
installed twrp
made backup in twrp
flashed ics
wasnt happy with the performance of some apps on ics and there were quite a lot of stalls and complete freezes so i used the backup i made in twrp to restore back to original kf rom
most of my apps wouldnt worked and asked me to reinstall them through the kf market. i was unable to access the kf market or the android market as it said there was no connection and to retry even though i could access my email through mail and the internet through browser no problem.
then i decided to do a factory reset through kf rom settings and now twrp starts automatically anytime i try to turn on the kf. i tried to do the recovery again with the backup but the restore factory settings had obviously deleted it along with everything else on the sd card.
has anyone any ideas on how i can get back to the stock kf rom? I am happy with stock kf until hardware acceleration works with ics
thanks in advance
Click to expand...
Click to collapse
You need to flash a new ROM. If you need to go back to Amazon stock ROM, then you need to download and flash it. Please note FFF and TWRP will be over written by the stock ROM.
Sent from my Amazon Kindle Fire using Tapatalk
ammubarak said:
You need to flash a new ROM. If you need to go back to Amazon stock ROM, then you need to download and flash it. Please note FFF and TWRP will be over written by the stock ROM.
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
thanks for the reply
I just tried to do this. i mounted the kf and moved the stock rom .zip file to the kf. when i mounted it however instead of seeing the usual list of files and folders and selecting the cdcard folder i could only see the twrp folder and nothing else. when I am in twrp i can see the other folders but not when it is mounted to the computer.
i tried anyway and there were numerous errors in the process that i didnt have time to write down
now when i start up the kindle fire it stops on the kindle fire logo screen
any ideas?
It looks like the KF is booting into fast boot mode.
You may use kfu to change the mode to normal or issues the following adb commands
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
If the KF boots to recovery mode i.e. twrp then mount the sdcard and flash the desired ROM.
Sent from my Amazon Kindle Fire using Tapatalk
Thank you, it worked! Enjoying Energy ROM
I have been working on this for over four hours. I have done absolutely everything that is said to do.
Heres my symptoms:
Turn Kindle Fire on and i get the yellow triangle, after a few seconds I get the curtain that says "teamwin" then it just opens TWRP. I cannot get it to boot normally.
I have SDK and ADB. This is the last screen I got from ADB.
C:\Users\Jeff\Desktop\android-sdk\platform-tools>fastboot -i 0x1949 oem idme boo
tmode 4000
< waiting for device >
When I try to do it thru KFU:
ADB Status: Offline
Boot Status: Unkown
I tried hitting 1 then 1 again and all I get is <waiting for device>
The Kindle is just sitting here with the TWRP screen on and I have no idea how to get around it.
PUNKYOU007 said:
I have been working on this for over four hours. I have done absolutely everything that is said to do.
Heres my symptoms:
Turn Kindle Fire on and i get the yellow triangle, after a few seconds I get the curtain that says "teamwin" then it just opens TWRP. I cannot get it to boot normally.
I have SDK and ADB. This is the last screen I got from ADB.
C:\Users\Jeff\Desktop\android-sdk\platform-tools>fastboot -i 0x1949 oem idme boo
tmode 4000
< waiting for device >
Click to expand...
Click to collapse
Fastboot only works in fastboot mode (4002). When you are in recovery or booted into an OS, you have to use adb to reset the bootmode. To get back to normal...
Code:
adb shell idme bootmode 4000
As a side note, the "-i 0x1949" should be dropped when you are using the FIREFIREFIRE bootloader (yellow triangle boot logo). The "-i 0x1949" is only necessary in the stock bootloader (kindle fire boot logo).
Ethanzh said:
So I formatted my rooted kindle fire with twrp installed, now whenever I boot I go straight to the TWRP menu, why can/t I boot into a fresh stock ROM?
Click to expand...
Click to collapse
I am stuck at TWRP on my Kindle Fire
I installed the KFU, installed the drivers, then run, install permanent root with superviser, twrp page came up and is now stuck on
*Verifying filesystems...
*Verifying partition sizes...
Anybody have some advice for me?? Please help me!! :crying:
---------- Post added at 10:26 PM ---------- Previous post was at 09:56 PM ----------
Irish01 said:
I am having the same problem here is exactly what i did
rooted
installed android market
installed twrp
made backup in twrp
flashed ics
wasnt happy with the performance of some apps on ics and there were quite a lot of stalls and complete freezes so i used the backup i made in twrp to restore back to original kf rom
most of my apps wouldnt worked and asked me to reinstall them through the kf market. i was unable to access the kf market or the android market as it said there was no connection and to retry even though i could access my email through mail and the internet through browser no problem.
then i decided to do a factory reset through kf rom settings and now twrp starts automatically anytime i try to turn on the kf. i tried to do the recovery again with the backup but the restore factory settings had obviously deleted it along with everything else on the sd card.
has anyone any ideas on how i can get back to the stock kf rom? I am happy with stock kf until hardware acceleration works with ics
thanks in advance
Click to expand...
Click to collapse
Did you ever get help with this. I am having similar problems.
frannytown said:
I am stuck at TWRP on my Kindle Fire
I installed the KFU, installed the drivers, then run, install permanent root with superviser, twrp page came up and is now stuck on
*Verifying filesystems...
*Verifying partition sizes...
Anybody have some advice for me?? Please help me!! :crying:
---------- Post added at 10:26 PM ---------- Previous post was at 09:56 PM ----------
Did you ever get help with this. I am having similar problems.
Click to expand...
Click to collapse
You're quoting someone from early March. I'm guessing you probably wont hear from them very soon.
On the other hand, if you're willing to start a new thread and explain in great detail what your "similar" problem is, I'm sure you'll be pleased with the quickness in which somebody responds.
KF unbrick utility
Try using the KF unbrick utility for all issues like this...I am a noob but it got me of problems like these...several times..
error: device not found
b63 said:
it's a good practice to move kfu to c:\ and rename it to "kfu"
now open a (elevated) command prompt and cd to c:\kfu\tools
now the adb command should work ...
Click to expand...
Click to collapse
i did this and i got a message saying error: device not found
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 foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Kamakookie said:
I foolishly let someone try to root my Kindle Fire, and now it is stuck in what seems to be the TWRP boot loop (the kindle fire is blue and white). If I leave it alone unplugged it will occasionally continue to the Kindle Fire orange and white screen but will not go any farther. From the Blue/white screen I can hit the power button to enter the boot menu where I get Normal Boot, Recovery, and Reset Boot Mode. I can enter TWRP recovery menus, but otherwise it just keeps rebooting. Once in the TWRP recovery screen I can only navigate for a short time before it locks up and I have to reboot by holding the power button in. The sd card will not mount, and they did not backup anything before they started messing with the os. Ive tried the Kindle Fire utility but it says device not found. The Kindle showed up in my device manager as Other-Kindle before I installed the android drivers mentioned in another thread, and now it is under Android Phone- Android ADB Interface. It doesnt show up in My Computer at all. I've read about the factory cable but cant find on in the US so it would take 2 weeks to get here from China. Any suggestions on how to fix this, or do I now have a $200 paperweight? Thanks in advance.
Click to expand...
Click to collapse
Maybe go into twrp and do a factory reset. Can you get to that menu? Click wipe and then factory reset.
I've tried the factory reset but it seems to have no effect on it. How do I do the adb push? I've tried using the command prompt to run some of the commands on other threads but I'm not doing something right. I always get an 'adb' is not recognized as an internal or external command, operable program or batch file error.
I'll apologize now for my stupidity on this one- I have never worked with android software before this.
The kindle fire utility reads:
ADB status: Offline
Boot Status: Unknown
I can get it to boot in normal and recovery mode, but each time I try to boot in Fastboot I get an error message 'Oops... something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on.' The Kindle shows up in Device Manager under Android Phone as Android ADB Interface
When using the twrp, anything that involves writing to or wiping the sd card receives this error E:failed to mount /sdcard (invalid argument)
I'd appreciate any help I can get. I'm at a standstill on this one.
im in the same position you can open it as a USB by selecting mount in TWRP and selecting mount USB Storage
do you have drivers / ADB on your computer ?
I did manage to get my kindle go into a recovery boot loop by doing the root procedure for the original 6.3 original Amazon ROM while my kindle had the 6.2 ROM . After i realized that the root procedure (intended for ver 6.3) didn't work for me, I had to try the procedure for rooting ver. 6.2.
It worked but after a couple of resets, the tablet went into a recovery boot loop.
what i did was to use ADB comands:
enter windows - > start command prompt (start - > run -> cmd)
check if kindle is connected: adb devices
if the device is found then use:
adb shell
su
idme bootmode 4000
exit
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
lukebunny said:
Hi all, I'm having a problem with my Kindle Fire. It is automatically booting into TWRP no matter what I do.
I have wiped everything, and installed the stock ROM, and when I reboot it just goes back to TWRP.
There is always a message of *verifying file system and *verifying partition. I can mount it and move files via USB.
In the fire utility it reads
ADB Status: Online
Boot Status: Unknown
If I try to change the bootmode it comes back waiting for device. I then got into the command line.
Doing "adb devices" shows it as being in recovery. I can reboot it from here, but goes right back to twrp.
I tried to do the adb shell--> su--> idme bootmode 4000
but after I do the shell it comes back that "su" isn't valid. I'm assuming I am doing something wrong, but I can't
for the life of me figure it out...any suggestions? Thanks in advance!
Click to expand...
Click to collapse
At startup hold thepower button untill you see the bootmenu come up and select "normal boot"
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
lukebunny said:
On the Kindle itself you mean? There is no bootmenu. I get the Kindle Fire (Orange) text, then goes straight to twrp, and if I do normal reboot from there, just straight back to twrp.
Click to expand...
Click to collapse
What version of TWRP do you have?
2.2.0
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
jamminjon82 said:
From twrp try booting into recovery that worked once for me to get a normal boot. Then make sure you put the fire fire fire bootloader on there so it never happens again
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Tried it, no go.
This is what I get in the command line
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Have you tried reboot to bootloader?
Sent from my Galaxy Nexus using Tapatalk 2
hey i got your answer I think? lol anyways...
soupmagnet said:
The "<[6n" is likely the result of pressing the up or down arrow with number lock turned off and it is causing the command to be unrecognized.
Click to expand...
Click to collapse
i'm pretty sure it's bla bla bla \platform-tools in that picture anyways that my answer anyways, maybe not but goodluck anyways........... and this 5 mins between post for low posting users is for the birds
digital_cha0s said:
i'm pretty surs it's bla bla bla \platform-tools in that picture anyways that my answer anyways goodluck
Click to expand...
Click to collapse
As you can see, the "adb shell" command is successful because of the change in the prompt.
~ # <-indicates the shell is working and active, so the actual /path of adb is irrelavent.
soupmagnet said:
Regardless, there's no need to use the "adb shell su -c..." command to get into fastboot. Instead use Pokey9000's bootmode binary "fbmode".
http://forum.xda-developers.com/showpost.php?p=20755810
Click to expand...
Click to collapse
That seems promising, but this is what I got when I tried it.
Also, thanks for your help everyone, I'm learning a lot as I go here!
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.
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.