Related
I tried the unbricking guide on here but did not work. I could not get fastboot to work.
Here is the exact message I get on the screen:
'Your Kindle has detected a problem and must clear app storage. The recovery process will erase some applications and data from your device. Apps from the appstore are stored in the cloud and can be reinstalled later.
This will reset your kindle to its original factory settings. you will need to re-register your kindle prior to downloading items from your Amazon account.
Please press power button to proceed.'
After i press the power button I get a status bar indicating the restore, it then says success, then reboots and ultimately comes back to the same restore screen as noted above.
Any help is appreciated.
I have the same issue, I had just used one click to gain root access and was changing permissions to instal Vending.apk under /system/apps
A bit more information I've gathered:
* I can run adb push/shell before the Kindle Fire starts the recovery mode.
* BUT when I try to run a adb shell command I get the error
Code:
/system/bin/sh failed permission denied (13)
I've spent the best part of the day trying to find a solution to no avail. I had a good read through this post too.
I did find a couple of threads talking about a factory reset cable, I don't know if this would be any good?
http://rootzwiki.com/topic/10591-kindle-fire-fastboot-without-idme/
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://www.youtube.com/watch?v=7OCpJbkGb7M&feature=player_embedded
PLEASE HELP
As soon as i get my factory cable and time I'll make a guide. But really all you need to do is flash the images from the 6.2 update via fastboot
Yeah I got to that point to where it doesn't just go into logo, but infinitely boots you into recovery mode. when you launch adb it even says its recovery mode and all the folders are hidden/missing.
Sigh, I fixed my kindle and got it working again then I broke it again by accidentally changing the entire system folder to chmod 644 haha.
Anyways so far I have found no fix around it so I just returned it and got a new one. live and learn I guess.
What did you do exactly to put it in a boot-loop? I did this once before by tampering with some system files, but i was able to push the regular one's back using adb.
I made a factory cable and managed to get fastboot working to flash over a new system image.
Does anyone have a system.img file for the Kindle Fire?
OR know another way to bring up a shell via fastboot?
I might just wait till next week and see what the status is then on the CM7 ROM.
I really need to get me one of those factory cables :S but they are sold out on black hat at the moment.
hey dk560 or JandD
how was u able to get ur kindle work again? where u get the recovery files or original files? my kindle stucks in flashin kindle fire screen over and over..
i try this
http://forum.xda-developers.com/showthread.php?t=1356257
everything worked fine...but at the and had the same problem..i have normal acces with adb and all to the devide but iam not experienced...how i get the original files back to the kindle? Or any help what i can try? i stuck....
plz any suggestions...thx!!
I dunno. But I think I may have the same issue. Got brick while doing wallpaper n now my fire stuck at fastboot and window cannot detect n fastboot nv finish the run always in waiting for device. Does this mean the doom for my 3 dar old kindle fire?
finally i solved it!!
IF YOU THINK MODIFYING PERMISSIONS ON /system/app IS WHAT CAUSED YOU TO BOOTLOOP THEN FOLLOW THESE STEPS:
http://forum.xda-developers.com/showthread.php?t=1356257
thats what was my problem...it worked for me..after tmp root then this steps..and finally kindle was out of bootloop...thanks!!
I have follow that link, but my kindle now seem to be in fastboot n window detect kindle fire as unknown device. In cmd, device cannot be found, and fastboot rerun say waiting for device but nv work, I try, really wanna resolve the mess I created. I try to read n understand how to resolve but my current issue wasn't mention.
I'm still stuck with a screwed /system partition on the Kindle Fire.
I tried Calvin's instructions on installing CM7. I couldn't adb push the update.zip to the sdcard as my system folder was corrupted. I did manage to flash the Clockwork program via flashing updaterecovery.img
I got excited when adb push update.zip /sdcard/update.zip copied over, however following Calvin's instructions for Clockwork gave me a failed to mount /sdcard error. I'm guessing the clockwork mount points are virtual mount points of some kind and not the physical device
Still seeking a system.img for the Kindle Fire. I'll give it a try building one myself I guess.
UPDATE:
This post helped on building a system.img - foiled by remote data too large problem
If a rooted kindle fire user could install mkyaffs2image and grab the system.img file for me I'd be very grateful!
"mkyaffs2image /system/ /sdcard/system.img
factory cable
I think your likely in the same boat as me - though for another reason. I can't get a shell from adb and have screwed up r/w access to /system files trying to change permissions with File Expert in order to get android market to work. Seems to be one of a couple of common themes. Anyway, as far as I can tell I'm going to have to get (or just make) a factory cable in order to throw it into fastboot so that I can boot from usb. If you'll read this entire thread here: http://forum.xda-developers.com/showthread.php?p=20017371#post20017371 then you may get a better idea of what you're dealing with. JackpotClavin has so graciously donated his time and skills. You'll have to be patient for complete instructions but I think they'll be forthcoming soon. Me, I'm going to go ahead with the cable as there's not much else I can do without shell methinks. If I get something workable first, I'll post for all.
kfuller said:
I think your likely in the same boat as me - though for another reason. I can't get a shell from adb and have screwed up r/w access to /system files trying to change permissions with File Expert in order to get android market to work. Seems to be one of a couple of common themes. Anyway, as far as I can tell I'm going to have to get (or just make) a factory cable in order to throw it into fastboot so that I can boot from usb. If you'll read this entire thread here: http://forum.xda-developers.com/showthread.php?p=20017371#post20017371 then you may get a better idea of what you're dealing with. JackpotClavin has so graciously donated his time and skills. You'll have to be patient for complete instructions but I think they'll be forthcoming soon. Me, I'm going to go ahead with the cable as there's not much else I can do without shell methinks. If I get something workable first, I'll post for all.
Click to expand...
Click to collapse
I have the same problem. I did the same thing you did, right after I did it I realized what I had done I had an epic face palm moment. Ill try to make a factory cable from this http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html -- after I'm in fastboot I have no idea what to do. Looking foward to JackpotClavin's guide. Thanks JackpotClavin!
I came across this and couldn't find a solution to my issue. All issues seem to be different, but in my case I could have my device recognized in the Kindle Fire Utility, and it noted that I was in recovery mode. Trying to change one of the boot modes caused it to just hang at the activation screen.
While it's hanging if you just try to cancel the operation, CTRL+C, it will suddenly decide it wants to work, and then you just tell it not to stop. Then you're back in normal boot mode and business as usual.
Just thought I'd share since this was about the only thing that showed up from a series of google searches involving the words recovery loop, lol.
every time i load a rom in recovery (i do all wipes) it always boots back into recovery
Upstreammiami said:
every time i load a rom in recovery (i do all wipes) it always boots back into recovery
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1428428
im having trouble on getting my kindle off from the boot loop and ive read ur thread, but i cant seem to get in to fastboot nor cant i mount my kindel from TWRP so i could inject files to the SD CARD. CAN SOMEONE HELP ME????
Zenroy said:
I have the same problem. I did the same thing you did, right after I did it I realized what I had done I had an epic face palm moment. Ill try to make a factory cable from this http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html -- after I'm in fastboot I have no idea what to do. Looking foward to JackpotClavin's guide. Thanks JackpotClavin!
Click to expand...
Click to collapse
emccalment said:
I came across this and couldn't find a solution to my issue. All issues seem to be different, but in my case I could have my device recognized in the Kindle Fire Utility, and it noted that I was in recovery mode. Trying to change one of the boot modes caused it to just hang at the activation screen.
While it's hanging if you just try to cancel the operation, CTRL+C, it will suddenly decide it wants to work, and then you just tell it not to stop. Then you're back in normal boot mode and business as usual.
Just thought I'd share since this was about the only thing that showed up from a series of google searches involving the words recovery loop, lol.
Click to expand...
Click to collapse
Dj Skama said:
im having trouble on getting my kindle off from the boot loop and ive read ur thread, but i cant seem to get in to fastboot nor cant i mount my kindel from TWRP so i could inject files to the SD CARD. CAN SOMEONE HELP ME????
Click to expand...
Click to collapse
As b63 linked you, download that utility, and then do this:
-Turn your kindle off by holding the power button down for at most 20 seconds.
-Plug kindle into your computer
-Run the unbrick utility
-Turn kindle on
-Wait for the Caution Sign with the fire logo (firefirefire logo)
-Choose first option on utility (Recovery Loop)
-Wait... (a max of 10 minutes)
This should work, if not, try to turn off your kindle on and off, and then try again.
This should work regardless if your device was found or not. This sounds like the problem I had. I wish you guys the best of luck.
emccalment said:
While it's hanging if you just try to cancel the operation, CTRL+C, it will suddenly decide it wants to work, and then you just tell it not to stop. Then you're back in normal boot mode and business as usual.
Click to expand...
Click to collapse
This saved me. 2 Keystrokes...amazing
[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?
Hi All,
First up the device is Kindle Fire 3.6.2, and im on Windows 7 64 bit.
I first tried using KFU to start the root, but KFU kept hanging when trying to reboot in FastbootMode. The Kindle WOULD boot to fastbootmode, but then KFU was frozen on the line that said somthing like "rebooting to Fastboot mode". It then explained to turn off and on your kindle if it gets stuck, which i did numerous times, but it KFU didnt resume the batch file.
So, I have been following the Guide here:
http://forum.xda-developers.com/showthread.php?t=1638452
And i was able to succeffully install TWRP and backup my system, but TWRP keeps getting frozen on "updating partition", so im not confident that the Backup was successfull, however I can see the backup when i reboot the device in TWRP.
Now im attempting to use the Next few steps to root the kindle, specifically this step:
adb shell mount system
But adb says:
Error - more than one device.
When i query devices I get (shortened for clarity):
123 device
123 recovery
Im not sure why each of my steps have been sooo difficult to root my kindle! I really just want to experience Jelly Bean for the first time in my life!
Is there any tool at this point I can use to do the steps for me more easily? I tried KFU again but it always freezes after rebooting in fastboot mode,
If no tool is available, should i somehow disconnect one of the devices in adb? (I dont know how too).
BTW - I have no other devices other than a mouse attached to my PC!
Thanks so much in advance.
Regards,
Dale
Please, anybody? Ill be very grateful for any help!
help
still would love any help anyone!
dalecameron said:
still would love any help anyone!
Click to expand...
Click to collapse
First of all, when using adb (especially in Windows), always start every adb session with the command 'adb kill-server'. This will prevent previous adb sessions from staying active and causing problems down the line, like with the "multiple devices" error you are receiving.
Also, "updating partition details" in TWRP recovery takes only about a split second, but for some reason doesn't specifically let you know when it's finished. Your backup is in it's place so there's nothing to worry about. Beyond that, you shouldn't be having any problems whatsoever. Your adb shows connected in both normal and recovery modes, which suggests you have access to both, so your problems are all but non-existent.
And finally, you don't need to waste your time trying to "root" your device. When you flash a custom ROM in recovery, it gives you "root" automatically, so all you need to do at this point is use adb to push a ROM to your sdcard, factory reset in recovery, then flash the ROM (and Gapps, of course).
soupmagnet said:
First of all, when using adb (especially in Windows), always start every adb session with the command 'adb kill-server'. This will prevent previous adb sessions from staying active and causing problems down the line, like with the "multiple devices" error you are receiving.
Also, "updating partition details" in TWRP recovery takes only about a split second, but for some reason doesn't specifically let you know when it's finished. Your backup is in it's place so there's nothing to worry about. Beyond that, you shouldn't be having any problems whatsoever. Your adb shows connected in both normal and recovery modes, which suggests you have access to both, so your problems are all but non-existent.
And finally, you don't need to waste your time trying to "root" your device. When you flash a custom ROM in recovery, it gives you "root" automatically, so all you need to do at this point is use adb to push a ROM to your sdcard, factory reset in recovery, then flash the ROM (and Gapps, of course).
Click to expand...
Click to collapse
Thanks SoupMagnet! Much appreciated, and thanks for the adb tip!
dalecameron said:
Hi All,
First up the device is Kindle Fire 3.6.2, and im on Windows 7 64 bit.
I first tried using KFU to start the root, but KFU kept hanging when trying to reboot in FastbootMode. The Kindle WOULD boot to fastbootmode, but then KFU was frozen on the line that said somthing like "rebooting to Fastboot mode". It then explained to turn off and on your kindle if it gets stuck, which i did numerous times, but it KFU didnt resume the batch file.
So, I have been following the Guide here:
http://forum.xda-developers.com/showthread.php?t=1638452
And i was able to succeffully install TWRP and backup my system, but TWRP keeps getting frozen on "updating partition", so im not confident that the Backup was successfull, however I can see the backup when i reboot the device in TWRP.
Now im attempting to use the Next few steps to root the kindle, specifically this step:
adb shell mount system
But adb says:
Error - more than one device.
When i query devices I get (shortened for clarity):
123 device
123 recovery
Im not sure why each of my steps have been sooo difficult to root my kindle! I really just want to experience Jelly Bean for the first time in my life!
Is there any tool at this point I can use to do the steps for me more easily? I tried KFU again but it always freezes after rebooting in fastboot mode,
If no tool is available, should i somehow disconnect one of the devices in adb? (I dont know how too).
BTW - I have no other devices other than a mouse attached to my PC!
Thanks so much in advance.
Regards,
Dale
Click to expand...
Click to collapse
Uncheck the backup of android secure and I believe it will stop hanging at updating partitions.
Hello,
Without beating myself up, here is what I did:
1. used steps from another site to root my Kindle Fire HD 8.9 and attempt to load Android 4.4.2 on it. First major mistake.
2. during that process, the steps to make a backup didn't work and I continued. I realize that was my second major mistake, one from which I cannot recover.
3. attempted to use a Factory Image found on this site. I followed the steps, and when I perform the "fastboot -i 0x1949" reboot command, I get the "kindle fire" orange logo, and it sits there. I'm guessing it's bricked.
4. without giving up, I attempted to follow the commands found on this site here (http://forum.xda-developers.com/showthread.php?t=2128175), but I've been unsuccessful.
So, I'm stuck looking at the "kindle fire" orange logo. My thoughts were to get an image on the device and boot into it to at least get all the necessary files for flashing the image. Nope. I would appreciate any assistance. I will also state that I am a very fresh NooB when it comes to these things. I thought I was prepared, but I guess not enough.
TIA!
Mike
mikeroundrock said:
Hello,
Without beating myself up, here is what I did:
1. used steps from another site to root my Kindle Fire HD 8.9 and attempt to load Android 4.4.2 on it. First major mistake.
2. during that process, the steps to make a backup didn't work and I continued. I realize that was my second major mistake, one from which I cannot recover.
3. attempted to use a Factory Image found on this site. I followed the steps, and when I perform the "fastboot -i 0x1949" reboot command, I get the "kindle fire" orange logo, and it sits there. I'm guessing it's bricked.
4. without giving up, I attempted to follow the commands found on this site here (http://forum.xda-developers.com/showthread.php?t=2128175), but I've been unsuccessful.
So, I'm stuck looking at the "kindle fire" orange logo. My thoughts were to get an image on the device and boot into it to at least get all the necessary files for flashing the image. Nope. I would appreciate any assistance. I will also state that I am a very fresh NooB when it comes to these things. I thought I was prepared, but I guess not enough.
TIA!
Mike
Click to expand...
Click to collapse
if you never installed the fastboot drivers that would explain the issue. when the kindle first turns on after you plug it in while off, it should briefly be detected as a jem device in the device manager. if it already has the drivers installed it will briefly show up as a adb device. if you don't have the drivers installed then grab the ones from mg SIG and extract them somewhere and point the update driver box to it in the few seconds it is detected. once it is installed power the kindle off! run the "fastboot -I 0x1949 getvar product" and when it says waiting for device, plug in the kindle while it is off, it should go into fastboot.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
if you never installed the fastboot drivers that would explain the issue. when the kindle first turns on after you plug it in while off, it should briefly be detected as a jem device in the device manager. if it already has the drivers installed it will briefly show up as a adb device. if you don't have the drivers installed then grab the ones from mg SIG and extract them somewhere and point the update driver box to it in the few seconds it is detected. once it is installed power the kindle off! run the "fastboot -I 0x1949 getvar product" and when it says waiting for device, plug in the kindle while it is off, it should go into fastboot.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
OK. I followed your instructions and installed the driver. I then attempted to install a base image following the instructions here:http://forum.xda-developers.com/showthread.php?t=2011126
I chose the following prompts: 1. enable fastboot, then 2. Restore-su/supersu.apk only, then 4. Erase cache and userdata, and finally Reboot normally. No luck.
I'd really appreciate any and all ideas/help. My hope is to turn this brick into something productive again.
What are you using to restore the kindle?
stunts513 said:
What are you using to restore the kindle?
Click to expand...
Click to collapse
All I have are whatever people have shared. As mentioned in my initial post, I do not have a backup of what I had before I started. Perhaps my biggest mistake. My understanding is that I need to get the Kindle software back on it in order to install the Android bits. Perhaps I am in error on that thinking. Please let me know if that is an unneeded step.
Use either kindle fire first aid or system restore tool and stay away from kindle fire utility unless you want a paperweight.
Yesterday was my first time rooting a Kindle Fire, and the root process went very smoothly when I followed this guide which uses saferoot: http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955
While I made use of this guide for flashing FFF and TWRP: http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
After successfully rooting it, I wanted to try the OtterX ROM/TWRP/Bootloader, since I read the comments and saw it would be good to try it out. After flashing the bootloader (otterx-u-boot_v2.05), the kindle kept rebooting showing the logo and the option to 'press power to enter boot menu'. I thought this was normal so I didn't mind it. (During this time, I could still enter recovery.) I proceeded to Step 2 which was flashing TWRP for OtterX (I downloaded zip-otterx-twrp-2.8.2.0-recovery.zip and installed it using the previous TWRP I flashed: openrecovery-twrp-2.2.2.1-blaze.img).
I wasn't able to remember what I did next, but I know I was already having issues. I was getting anxious and sleepy at the same time, I remember exploring the boot menu and foolishly/stupidly tried the EMMC Corruption Fix, without even trying to research about it beforehand, so now I'm stuck at the "fastboot mode" screen (I've attached a photo of the screen). Whenever I turn on the device, it shows the kindle fire logo and the option to enter boot menu. If I let it be for a while, it goes into the "fastboot mode" screen, the same thing happens when I try to choose "continue boot" or "recovery boot". Windows doesn't recognize it anymore whenever I try to connect it too (I'm using Windows 8.1 by the way.)
Please help, I've tried reading about how I could restore the kindle to the state it used to be after I rooted it, but no luck, I couldn't find anyone encountering the same problem as me since I think I'm the only one stupid enough to apply that EMMC corruption fix without knowing or reading what it actually does. Thanks in advance to anyone who could help.
Try
Download adb/fastboot files, if you have not yet.
Power off Kindle
In command prompt
Run command to flash recovery
Power on kindle
See [Video] Flashing TWRP in OtterX bootloader
THANK YOU SO MUCH for your reply. I tried it as soon as I woke up. I found out that the problem was the driver, I reinstalled it and flashed the recovery using the fastboot command.
Sent from my C5502 using XDA Free mobile app