Database Users

[Q] Bricked/Stuck in Fastboot (How to Remove TWRP?)

So, I've been up all night after buying this Fire trying to fix it, and I've decided to go along with my original decision to just return it. I'll rewind a bit to give you guys a play by play to show how I got to what I've determined is a FUBAR situation, and hopefully you guys can help me at least remove TWRP so I can return it without much issue.
If it's tl;dr, I bolded the main errors I got from the console and TWRP
1. I purchased my Kindle Fire from Best Buy with a 1 Year Protection plan, so in all reality, I could just break it in half and get a replacement, but I don't necessarily want a replacement.
2. I initially purchased it for my mom, but when I found out that the stock Fire OS didn't have Korean input or the option to have a Korean interface, I did a bit of research and started reading up on how to root, how to install the market, things like that. My mom's not a native English speaker, so this was an important thing for her, etc etc.
3. I read multiple guides on this forum and others, and rooted using the guide found here , since a few of the threads I was reading through seemed to point in that direction, and I had a bad experience with SOCR on my Droid X.
4. The root was successful, so I moved on and used KFU .3 to do the rest of the important bits; android market, etc etc.
5. Everything was working fine, but, after looking through it, I realized that it wouldn't work for what I needed it to, and I would have to return it, so, I attempted to unroot the tablet using TWRP's interface.
6. I cleared the cache, the devlak cache, and system wiped, then restored using the system restore point in the TWRP folder, figuring after that, the Kindle would boot up with stock OS and then I would just system restore the default way. This method got me stuck in a recovery-loop, and no matter what I did, the Fire always booted to recovery mode.
7. I figured I had bricked it, so I followed the steps in this guide, but always seemed to have problems at the step where I have to chmod 755 of the zergRush. I get "Not a directory" error, which after doing some research, I believe is on account of me no longer having rw privilege?
8. I looked around some more, ignoring that guide, and found a method to force-push the amazon update, but TWRP would no longer run the update, saying it could not Mount the SD Card due to an Invalid Argument, and I have yet to determine what that means.
9. After manually changing it to fastboot in an attempt to at least get it out of recovery mode, I have the Fire recognizable as a device in my ADB, but it is now stuck in a fastboot loop, and when I attempt to re-root it in order to give myself rw privileges again, it stalls on "waiting for device" and never gets past that point.
Update
I tried to reroot while the Fire was stuck in the Kindle Fire splash screen using the KFU tool, and used zergRush, but the error message I got was - exec '/system/bin/sh' failed: No such file or directory (2) - 4 times over.
What I think the problem is, is that when I wiped the cache/devlak cache/ and system reformatted, it wiped my SU privileges, and as a result, no longer allowed me to write the backup to the Fire, therefore leaving me in a perpetual state of limbo?
What I'm asking for from you is;
What can I do to fix this?
Is there any more information you need/want from me?
And finally,
Is there an easy way for me to remove TWRP from the system?
Thank you.

Hi!
There are a lot of great tips regarding TWRP and fastboot over at RootzWiki.
Some users are reporting the same fastboot loop that you currently experience. I suggest you read the thread and follow the suggestions. One suggestion which you may want to try first is the one in this post.

Thank you for the reply. I did as you suggested and followed the links and the post on the guide, and although that did change the nature of my fastboot loop, I'm still stuck in a fastboot loop.
I was initially stuck in a fastboot loop on the Kindle Fire logo, which I determined by running fastboot devices, while it was stuck on that logo, and it showed the device as being fastboot. After following that guide, and using the hard reset, then using the "How to Unbrick" in order to change back to a normal boot, I'm stuck in a fastboot loop on the TWRP splash screen of a triangle with a fire in it. I'll continue looking through the guides to see if I can solve the problem, but thank you once again, and sorry for not clarifying which type of fastboot loop I was in.

Sorry it didn't work out! However...
isjonamon said:
I'm stuck in a fastboot loop on the TWRP splash screen of a triangle with a fire in it.
Click to expand...
Click to collapse
I really though the solution posted over at RootzWizi would solve this problem. Getting stuck at the yellow triangle is 'common'. I really though adding
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
Click to expand...
Click to collapse
to android_winusb.inf would solve it. But if you are able to recognize your Fire in fastboot mode via your PC, I guess that's not where your problem is.
Is this tip to any help?
And lastly... the great Kindle Fire Utility thread is worth checking out, in case you haven't already
I hope you'll find a solution to this problem!

I've tried the tip you linked me to, and sadly it didn't do anything for me.
Moving on, though, I'm reading through the KFU thread again to see if there was anything I missed, and decided I might as well try re-flashing to CM7 to see if I can at least get it working up to a rooted/rom standpoint. I figure from there, I can at least have a working platform to factory reset from. If I can't do that... well...
Does anyone know a way to just return everything to factory settings? To just wipe everything and make it so it turns on like it's out of the box? Either through adb commands, or TWRP or anything?

Sorry for the double post, but I managed to get CM7 back up on my Fire, and managed to regain SU access. Can anyone point me to a guide to restoring it back to its former "glory" so I can return it?
Fixed it!!
For anyone interested, this is what worked for me;
From where I ended up with the problem, I followed hachiueno's advice and read through the KFU's thread as well as the TWRP thread on Rootzwiki, that led me to adding those lines to the device firmware, which I think was the first step in the solution, so...
Step 1. Add
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
to android_winusb.inf , then restart your computer with your Fire unplugged.
After that, I was inspired, through reading the KFU thread, to attempt to manually install CM7 since I wasn't having much luck zergRushing on my own, so, I went to the CM7 thread and pushed the Update.zip there, and used my TWRP to install that, effectively rebuilding my filestructure, since it seems the Kindle Fire doesn't have so much as a SH folder in it.
Step 2. MANUALLY (maybe) install CM7 if you can.
Once I got CM7 up and working, using the USB mounting option, I replaced the update.zip in the sdcard folder with the Amazon 6.2 firmware downloaded from their website, renamed to update.zip, and then unmounted my fire from my laptop.
Step 3. Download the Amazon 6.2 Firmware from amazon's website (I can't post...), rename it to update.zip, and replace the CM7 mod update.zip in your /sdcard directory with it.
Then, I figured if I ran TWRP like it was supposed to run, and just ran the update.zip like any other ROM, it should fill in the blanks in the filesstructure, bypassing Amazon's own lack of certain folders, and various other things, filling in the gaps as they were. The next step might be entirely redundant, since I'm a bit clueless, and it might have been entirely luck on my part, but I initially forgot to wipe my cache, devlak cache, and system restore, so I did all that and did it again, and my wishful thinking leads me to believe that doing that saved my ass from having a crapton of errors....
Step 4. Using the install function on TWRP, install the renamed Amazon update.zip, reboot, clear your cache, devlak cache, system reformat, then reinstall the update.zip. Reboot one more time, and you should come up to the Kindle Fire splash screen. Leave it for a few minutes, and it'll be like it just came out of the box.
Thanks for all your help. I love you. Seriously. No homo. Maybe a little. I love you.

Good to hear that you managed to boot it again!
isjonamon said:
Sorry for the double post, but I managed to get CM7 back up on my Fire, and managed to regain SU access. Can anyone point me to a guide to restoring it back to its former "glory" so I can return it?
Click to expand...
Click to collapse
This guide seems to be an easy solution to this. However, no one has replied any success or failure, so not sure if it's 100% bulletproof for everyone... if I were you, I would follow JackpotClavin's guide here. He's a known developer here and knows what he's doing, and many successful replies from users having used this method... so yeah, just to be 'sure' (can you ever be...?) that you won't experience any further problems, I recommend the last one.

I actually used the first guide in order to get the Amazon update, but couldn't post a reply since I'm still a noob. I had to do a few things differently, and ultimately got a few different results, but posted up my own version of the steps.
Once again, thanks for all your help!

It seems to me that the majority of problems people are having are driver related. When I was using KFU to install TWRP it stalled half way through and just said waiting for device. Just had to install drivers again and it happily completed the install.
Sent from my Kindle Fire using xda premium

all u needed do initially was change bootmode it seemed. thrn u went and did all kinds of stuff that wasnt necessary.
sent from my kindle fire

smirkis said:
all u needed do initially was change bootmode it seemed. thrn u went and did all kinds of stuff that wasnt necessary.
sent from my kindle fire
Click to expand...
Click to collapse
I actually changed bootmodes quite frequently, following multiple threads and guides, changing from recovery, to normal, to fastboot, and back and forth when called for. Changing to fastboot stuck me in an eternal fastboot loop, changing to normal reverted me to a recovery loop, and recovery was the only bootmode I could access adb from.
Sheolrock said:
It seems to me that the majority of problems people are having are driver related. When I was using KFU to install TWRP it stalled half way through and just said waiting for device. Just had to install drivers again and it happily completed the install.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Driver issues seemed to be part of the problem for me, but just updating the drivers didn't fix the issue entirely. I'm jealous that you got it to work with just a driver update...

Hey i believe im in the same problem but i keep reading the posts and im still stuck and i have no idea what to do im worried that i cant fix it.... Some please help me ASAP
Thanks in advance

wrong boot mode ?
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
bad drivers ?
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54

I have had the looping problem and none of these would fix it. I got it to work by adding those lines to android_winusb and running the run.bat, trying to make it switch to normal mode as the kindle was turning on. Somewhere along the yellow triangle when it was loading it accepted the command from KFU. Hope this helps, only thing that worked for me.

the drivers i included contain all the necessary entries in adb_usb.ini and android_winusb.inf

Please can someone help me!?
I did idme bootmode 4002 and now my fire won't boot up or show up in android adb. Any solution?

awidawad said:
I did idme bootmode 4002 and now my fire won't boot up or show up in android adb. Any solution?
Click to expand...
Click to collapse
you switched it to fastboot (4002) - adb commands are not working in fastboot mode !
little guide:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse

Not sure if this is totally helpful to anyone but originally I thought the thread was started with a posting of being stuck bootlooping into twrp in recovery mode with a complete loss of file structure. I had this same issue my Kindle would not start in anything but straight to twrp and if I tried to flash my CM9 ICS rom it was not there and only the twrp folder empty was. So I went to mount and mounted usb storage and moved the stock update zip file from amazon to the twrp folder and flashed that. Worked like a charm now I appear to be straight stock. I am no developer of this stuff I just am a bit of a tinkerer so don't understand all the code stuff but it starts like a normal kindle and appears totally stock. So hopefuly that helps you return your deice to stock for return or to continue wahtever modifications you intend.
2992

ADB shell not reconizing it.

I rooted it and installed CM7 on it, CM7 was getting a boot loop so I did a factory reset, I read online that I should reinstall CM7 to help get rid o the boot loop, i turned off the kindle, putting it into recovery mod (like a t**t). Stuck in FFF boot loop, windows reconizses its an ADB device but nether the KF utility, nor ADB thinks its plugged in. I can mount it as a mass storage device. Any help is appreciated.
Edit: This picture better explains what is going on, but as i am a new user, i cannot post a link so I'm sorry but you will have to copy and paste this : i.imgur.com/3Lcsh.png

Did you try this?
adb shell
idme bootmode 4000
reboot

Droidanian said:
Did you try this?
adb shell
idme bootmode 4000
reboot
Click to expand...
Click to collapse
As i was trying to explain adb shell keeps telling me the device isn't found
And before you ask, yes i have installed the drivers and yes i have reinstalled them and yes i have rebooted the device and my computer

Did you try using the command prompt instead of the KFU? I had success doing it manually.

yup, no luck

Remove the KF, uninstall the drivers, restart Windows, and install them manually.
That should work.

no luck, still stuck

Did you edit the "adb_usb" and "android_winusb" files?

HOLY **** after ~ 4 hours of tinkering i got it!!!
Within the KFU i installed the TWRP recovery and while it said waiting for device, I restarted it. I had done this before but it didn't take.
I LOVE THE KFU, IF I HAD ANY MONEY I WOULD GIVE IT TO THEM.
If anyone in the future has this problem and has any questions, PM me and I will try to help you as best as I can.

[Q] Yet another bricked KF

Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.

Do you have fastboot access? Try running the following...
fastboot -i 0x1949 oem idme bootmode 4000

Try this: http://forum.xda-developers.com/showthread.php?t=1422832

Thanks guys, ill try those and post back w the results.

so i tried fastboot -i 0x1949 oem idme bootmode 4000
and it seems to have been successful, in that it is now back to its original boot loop state. however, it is still not booting fully.
it seems that adb commands are now working, i can do adb shell, and navigate root folders (system etc).
zombie, i havent had much luck with that route, i had tried that earlier.

I've seen people mentioning that the cause for their brick had something to do with permissions, so i did ls -l in the adb shell, here are the permissions for some of the relevant folders. if there are any others that might be helpful, let me know.
root -> drwx------
system -> drwxr-xr-x
sdcard -> lrwxrwxrwx
oh and framework-res.apk -> -rw-r--r-- (same as all other files in that directory)
i did modify the framework-res to change the background image. it successfully booted at least once after the modification - i used metamorph, i loaded the file, then rebooted for it to take effect. this was successful, but i believe it was the next reboot which did my kindle in, so possibly related.
i rambled a bit, but maybe if i replaced the current framework-res.apk with the stock framework-res.apk, that might be worth trying? are all stock framework-res.apk files the same at stock? because i don't have a copy of the original that came with my kindle.

i would go back into fastboot and then flash over TWRP... and then reinstall your os from scratch. it would probably be easier than trying to root around fixing it from the inside.

Thanks xrishox, I might do that. Is there a thread detailing how to do that?
When I tried doing fastboot I lost the ability to use adb commands so I'm not sure how to go about flashing twrp.

Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.

jackofaiitrades said:
Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.
Click to expand...
Click to collapse
Howdy!
I recently just dealt with this same issue. My KF was stuck in boot loop and wouldn't be recognized by my computer. I left it in bootloop until it ran out of battery. Once it was completely drained, I connected it to my computer and my computer recognized it, I then reinstalled the drivers. Right after that I used KFU to change bootmode to normal boot and let it fully charge! Good to go! Hope this helps someone.

from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and here is a note from vashypooh - the op of kfu
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
maybe it helps someone ...

Thanks guys, I won't be near a computer until tonight but will try these out as soon as I get back

lmntone said:
Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.
Click to expand...
Click to collapse
Tone you're a life saver, thanks. I'm up and good to go.

good that it's working again !
have you seen this one in the dev section - could save a lot of handwork:
http://forum.xda-developers.com/showthread.php?t=1428428

Also, when I get back to my computer again, ill update my OP to include the solution so that others might benefit. its like a 20 minute fix but took me days to resolve it (largely due to lack of comp access but that's beside the point).

[Q] Got stucked on KF Start Screen. [solved]

Hi,
i am searching this forum for about 5-6 hours without finding a solution for my problem.
My KF is stucked on "kindle fire" start screen (it blinks) after i made a bad misstake by editing the account.db . I wanted to add a second google account to my new installed market.
But after that it is stucked.
I tried the kfu 0.9.3 but no matter what i do, i get an error with "operation not permitted" or "Could not access the Package Manager. Is the system runnung?"
[edit]Everytime i try to enter su at adb shell, i got this message "[1] + Stopped (signal) su"[/edit]
My driver seem to work.
And i dont know what i did, after some utility uses i got this yellow triangle and it stucked first. But now it continued again to the blinking kindle fire logo.
Can somebody please help me? I realy dont know what to do.
And i am sorry for my bad english :/ .
Thank you.

Have you tried going into recovery?
Sent from my Kindle Fire using xda premium

Issue the following commands to reboot to normal
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Sent from my Amazon Kindle Fire using Tapatalk

Hey, thanks for the answer.
I was able to get twrp running with this post:
b63 said:
hey cool - thought the shell is messed up - it's not - you can get to fastboot - great
would suggest to follow this thread starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
and your allready downloaded twrp is recovery.img not twrp-blaze-2.0.0RC0.img
simply adapt the corresponding command in the above thread
is you want stock rom i would suggest to use a prerooted stock rom (i prefer the unsecure version):
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
Click to expand...
Click to collapse
Now i tried to install a rom, but i am not sure it worked. Because the kf is starting for over 10 min now and just showing this "kindle fire" logo. Do you or anybody has got a link for the original 6.2.2 or maybe with google play? I have got the problem that the roms i downloaded dont have a md5 file and that discription i used said i have to activate md5 check.
Thank you.
P.S. How long do i have to wait until i can be sure it wont start? And do i realy have to command "adb shell idme bootmode 4000" and "adb reboot" after flashing? Or can i just click on reboot?

Check the check sum md5 before you install.
It looks like the KF is booting into fastboot mode. You need to issue the mentioned commands to boot normal either before or after you install a new ROM. First you to boot to normal and find the ROM you like to install. As you know, use TWRP to install a new ROM.
Sent from my Amazon Kindle Fire using Tapatalk

Guys, thank you. Its alive..again .
I just found a rom that worked .
Its is 5 am and i rly have to sleep now..what a night -.- .
Again, thanks for your help.

just for info:
had a case where a prerooted stock rom needed 20min for first boot
so be patient ...
please mark the subject of the topic (edit first post) with [Solved]

my problem

my problem is that when i used rom toolbox after flashing twrp recovery from hashcode (do all and dont flash the recovery only)for reset my tab into recovery. my tablet entered in a endless recovery, it charged but i could enter the os, then it was with few battery and i recharged it, then it had a few battery and i dont charged it, and now it dont boot, i charged it and nothing, i know that i can use fastboot but my device wasnt recognoized, so i think i will need the drivers. please help me

Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
persano said:
my problem is that when i used rom toolbox after flashing twrp recovery from hashcode (do all and dont flash the recovery only)for reset my tab into recovery. my tablet entered in a endless recovery, it charged but i could enter the os, then it was with few battery and i recharged it, then it had a few battery and i dont charged it, and now it dont boot, i charged it and nothing, i know that i can use fastboot but my device wasnt recognoized, so i think i will need the drivers. please help me
Click to expand...
Click to collapse
persano,
OK, so if I understand you correctly, you performed Hascodes steps to install TWRP Recovery and now your device loops the Recovery, correct?
If yes, plug in the Fastboot cable to the Kindle first then to your PC but first use our utility to install the drivers then proceed to recover the device.
Here is a link: http://forum.xda-developers.com/showthread.php?t=2096888
We have an option in the software to install the driver - do not use the backup or OTA disable feature, we are working on that function.
If you have trouble with that driver, which you should not but if you do, reply back and we will add instructions. Do Not worry, we will get you back online.

prokennexusa said:
persano,
OK, so if I understand you correctly, you performed Hascodes steps to install TWRP Recovery and now your device loops the Recovery, correct?
If yes, plug in the Fastboot cable to the Kindle first then to your PC but first use our utility to install the drivers then proceed to recover the device.
Here is a link: http://forum.xda-developers.com/showthread.php?t=2096888
We have an option in the software to install the driver - do not use the backup or OTA disable feature, we are working on that function.
If you have trouble with that driver, which you should not but if you do, reply back and we will add instructions. Do Not worry, we will get you back online.
Click to expand...
Click to collapse
the only option of drivers is the adb one

Kindle Bootloops After Installing TWRP On The Kindle
persano said:
the only option of drivers is the adb one
Click to expand...
Click to collapse
persano,
The ADB Driver and Fastboot driver are one of the same drivers, so having said this when you have a working ADB Driver, you will have a working Fastboot driver. Now, we have no idea what Hashcode did when developing TWRP on the Kindle, although he is a genius so I am sure he thought of everything.
Have you posted the issue in his Thread? He may have a way to recover TWRP directly since our Method will place you back to a stock Kindle.

prokennexusa said:
persano,
The ADB Driver and Fastboot driver are one of the same drivers, so having said this when you have a working ADB Driver, you will have a working Fastboot driver. Now, we have no idea what Hashcode did when developing TWRP on the Kindle, although he is a genius so I am sure he thought of everything.
Have you posted the issue in his Thread? He may have a way to recover TWRP directly since our Method will place you back to a stock Kindle.
Click to expand...
Click to collapse
yeah i posted in his thread

How To End A TWRP Bootloop
persano said:
yeah i posted in his thread
Click to expand...
Click to collapse
persano,
Any response yet? Here are some pointers that apply to TWRP on other Androids, so it should apply to your Kindle:
If you get stuck at a screen with a yellow triangle, run:
Code:
fastboot oem idme bootmode 4000 -i 0x1949
If your device is always booting TWRP run:
Code:
adb shell "idme bootmode 4000"
Step 1: If you still can't get out of booting TWRP (A Bootloop), first run:
Code:
adb shell "idme bootmode 4002"
Step 2: Reboot your device, then run:
Code:
adb shell "idme bootmode 4000"
Step 3: Reboot again and you should be out of your bootloop.
Please let us know if one of these solves your issue.

prokennexusa said:
persano,
Any response yet? Here are some pointers that apply to TWRP on other Androids, so it should apply to your Kindle:
If you get stuck at a screen with a yellow triangle, run:
Code:
fastboot oem idme bootmode 4000 -i 0x1949
If your device is always booting TWRP run:
Code:
adb shell "idme bootmode 4000"
Step 1: If you still can't get out of booting TWRP (A Bootloop), first run:
Code:
adb shell "idme bootmode 4002"
Step 2: Reboot your device, then run:
Code:
adb shell "idme bootmode 4000"
Step 3: Reboot again and you should be out of your bootloop.
Please let us know if one of these solves your issue.
Click to expand...
Click to collapse
but my tablet dont boot, it get out of battery after alot of bootloops

How To End A TWRP Bootloop
persano said:
but my tablet dont boot, it get out of battery after alot of bootloops
Click to expand...
Click to collapse
persano,
So at the moment you battery is dead or your Kindle is dead, period?
If the Kindle is dead and will no longer accept a charge, you will need to send it back to Amazon for replacement. If you are out of Warranty or concerned Amazon will not warranty the device, send it to our office and we will get you a new one. We know you are Argentina but if you send it vis UPS or FedEx we will get it quickly.
If you would like a new Kindle send us a PM and we will post our shipping address.

prokennexusa said:
persano,
So at the moment you battery is dead or your Kindle is dead, period?
If the Kindle is dead and will no longer accept a charge, you will need to send it back to Amazon for replacement. If you are out of Warranty or concerned Amazon will not warranty the device, send it to our office and we will get you a new one. We know you are Argentina but if you send it vis UPS or FedEx we will get it quickly.
If you would like a new Kindle send us a PM and we will post our shipping address.
Click to expand...
Click to collapse
thanks then i will see. i think hashcode is a killer developer xD
and how a new kinlde, what you will do with the old?
i bougth it from ebay, amazon will renplace it ?

How To Ship Th Kindle To Xerocomm, Inc.
persano said:
thanks then i will see. i think hashcode is a killer developer xD
and how a new kinlde, what you will do with the old?
i bougth it from ebay, amazon will renplace it ?
Click to expand...
Click to collapse
persano,
If you ship it to us, we will register the device to our business Amazon account, where we own 40 Kindles, then we will ask Amazon to replace it. The old Kindle will go back to Amazon for parts - we will take care of having the device swapped out for you. Be sure you De-register the device from your Amazon Account, if you did not register the device to Amazon better yet.
The only caveat is the Kindle need to be in excellent condition without signs of being dropped, otherwise Amazon will reject the replacement.
If Hashcode can not fix the problem, ship the Kindle (well packaged and insured) to us:
Xerocomm, Inc.
dba The Noob Series
Attn: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954-6603
USA
Main Phone: 707-774-5923

prokennexusa said:
persano,
If you ship it to us, we will register the device to our business Amazon account, where we own 40 Kindles, then we will ask Amazon to replace it. The old Kindle will go back to Amazon for parts - we will take care of having the device swapped out for you. Be sure you De-register the device from your Amazon Account, if you did not register the device to Amazon better yet.
The only caveat is the Kindle need to be in excellent condition without signs of being dropped, otherwise Amazon will reject the replacement.
If Hashcode can not fix the problem, ship the Kindle (well packaged and insured) to us:
Xerocomm, Inc.
dba The Noob Series
Attn: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954-6603
USA
Main Phone: 707-774-5923
Click to expand...
Click to collapse
in the box and with the usb?
its in exellent

II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2

Hashcode said:
II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
but my tablet dont boot when i connect it

Hashcode said:
II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
how to configure it in the sdk

persano said:
but my tablet dont boot when i connect it
Click to expand...
Click to collapse
With fastboot cable?

Maromi said:
With fastboot cable?
Click to expand...
Click to collapse
yeah

persano said:
how to configure it in the sdk
Click to expand...
Click to collapse
in the Android SDK manager
click tools
click manage add-on sites
click user defined sites
click new
paste this address
http://kindle-sdk.s3.amazonaws.com/addon.xml

Maromi said:
in the Android SDK manager
click tools
click manage add-on sites
click user defined sites
click new
paste this address
http://kindle-sdk.s3.amazonaws.com/addon.xml
Click to expand...
Click to collapse
and then

amazon will remplace it !!!!! yeah!!!!
i live in argentina but they will remplace it

How To Stop A Kindle Fire HD Bootloop
persano said:
in the box and with the usb?
its in exellent
Click to expand...
Click to collapse
persano,
No, just the tablet. First open a chat with Amazon, see if they will replace the device, if no, send it to us and we will have the device replaced.