Develop Bugs

Unbricking My Kindle Fire

About 3 weeks ago, I bricked my Kindle Fire. It was a "spare" that I had, so I started messing around with it. Got TWRP installed, downloaded a couple of ROMS, and attempted to install them. (fortunately, I made a backup of my base Amazon 6.2)
To make a long story short, the fire got stuck. I was able to adb and various other things on this forum to keep things going, but after a while, Kindle Fire Utility (adb, nothing) could see the device. I thought for sure I had an expensive paper weight.
Enter the factory cable. Because SkOrPn was in the middle of a move, my cable didn't get here right away. Then there were some issues with my PayPal address, which SkOrPn went out of his way to fix. Today, I got the cable at my office.
Looked at the cable. Thought I had been send an unmodified cable. Saw no evidence that anything had been done to the cable. An absolutely perfect professional job.
Couldn't wait to get home. Got home. Plugged cable in Fire, then in Laptop. Nothing. Now what? I thought it was supposed to boot the bootloader? adb didn't see the device. Drivers good, it sees my other Fire. I guess I was one of those 1% that hard brick the fire with no chance of getting it back.
Did a few searched on the forum. Found how to install TWRP on my device. I thought I had it already? Ran the commands. Nothing. Switched to regular cable. Nothing. I figured I was screwed. I unplugged the Fire. connected the factory cable. Ran the command. THEN hooked up the cable. JOY JOY JOY!! i GOT TWRP loaded!!!!
Restored my previously saved image, and now I have a working Kindle Fire. NOW i'm going to install some other ROM on it.
The moral is, never give up. Buy a factory cable!!! One of the things I've ever spent $15 or so on. And I recommend SkOrPn as your source. Quality work, great customer service!!!
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
Sorry for the long post. My wife doesn't understand why this would make me so excited. But you all would, I'm sure.
SteveM

a very nice post for people who have bricked their kindles and need a factory cable!

Thanks for the kind words Steve. I hope this cable gives you confidence in flashing your Kindle long into the future. Glad it worked out for you.
Oh, and you did not see any evidence of modification because I do not modify the cable, I just cut off the original micro connector and install my own, already modified of course with a resistor and all I have to do is re-solder the 4 wires back onto their original pins and then fill the entire casing with 400 degree SureBonder PDR Hot Glue (the worlds strongest known hot glue, according to them anyway lol)... That way it looks and feels like a true manufactured store bought cable. However, doing it my way is still in fact more work, but the end result clearly justifies it.
Anyway, again glad I could be of service to you and my fellow XDA friends.

Where do I run the command from?

The3rdEye said:
Where do I run the command from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3

smoen02 said:
About 3 weeks ago, I bricked my Kindle Fire. It was a "spare" that I had, so I started messing around with it. Got TWRP installed, downloaded a couple of ROMS, and attempted to install them. (fortunately, I made a backup of my base Amazon 6.2)
To make a long story short, the fire got stuck. I was able to adb and various other things on this forum to keep things going, but after a while, Kindle Fire Utility (adb, nothing) could see the device. I thought for sure I had an expensive paper weight.
Enter the factory cable. Because SkOrPn was in the middle of a move, my cable didn't get here right away. Then there were some issues with my PayPal address, which SkOrPn went out of his way to fix. Today, I got the cable at my office.
Looked at the cable. Thought I had been send an unmodified cable. Saw no evidence that anything had been done to the cable. An absolutely perfect professional job.
Couldn't wait to get home. Got home. Plugged cable in Fire, then in Laptop. Nothing. Now what? I thought it was supposed to boot the bootloader? adb didn't see the device. Drivers good, it sees my other Fire. I guess I was one of those 1% that hard brick the fire with no chance of getting it back.
Did a few searched on the forum. Found how to install TWRP on my device. I thought I had it already? Ran the commands. Nothing. Switched to regular cable. Nothing. I figured I was screwed. I unplugged the Fire. connected the factory cable. Ran the command. THEN hooked up the cable. JOY JOY JOY!! i GOT TWRP loaded!!!!
Restored my previously saved image, and now I have a working Kindle Fire. NOW i'm going to install some other ROM on it.
The moral is, never give up. Buy a factory cable!!! One of the things I've ever spent $15 or so on. And I recommend SkOrPn as your source. Quality work, great customer service!!!
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
Sorry for the long post. My wife doesn't understand why this would make me so excited. But you all would, I'm sure.
SteveM
Click to expand...
Click to collapse
Hi there,
Where should I run that command from??
Here´s my case, I hope you could help me..
I need urgent help. Just got my kindle todasy and went through tutorial to use the rooting utitily. My kindle got stuck at loading screen and wouldn´t shut shutdown. I waited until the battery ran out. Waited for few more minutes and plugged in the data cable. The kindle now won´t stop blinking and does not get reckgonized by the pc. I did waited for the battery goes dead again, recharged then for about 30 min and nothing has changed. The loading screen keeps blinking and nothing seems to be happening. Please advise!!

andersonrel said:
Hi there,
Where should I run that command from??
Here´s my case, I hope you could help me..
I need urgent help. Just got my kindle todasy and went through tutorial to use the rooting utitily. My kindle got stuck at loading screen and wouldn´t shut shutdown. I waited until the battery ran out. Waited for few more minutes and plugged in the data cable. The kindle now won´t stop blinking and does not get reckgonized by the pc. I did waited for the battery goes dead again, recharged then for about 30 min and nothing has changed. The loading screen keeps blinking and nothing seems to be happening. Please advise!!
Click to expand...
Click to collapse
Oh boy... I'm going to hope that it was a timing issue and our posts got crossed, because I answered your question for another user just above your post.
Regardless, the answer to that question isn't going to help you. You need this...
http://forum.xda-developers.com/showthread.php?t=1621146
Never let your battery die like you did. You can always force a shutdown by keeping the power button pressed down for 20-30 seconds.
EDIT: I'd been meaning to post this guide for a while...
http://forum.xda-developers.com/showthread.php?t=1623244
and I missed the part of your post about being "stuck at loading screen" the first time I read it. I suggest you read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
make sure the device drivers are working (part 2) and learn some fastboot commands (part 3) so you can reset the bootmode on your device back to normal and reboot it.

kinfauns said:
Oh boy... I'm going to hope that it was a timing issue and our posts got crossed, because I answered your question for another user just above your post.
Regardless, the answer to that question isn't going to help you. You need this...
http://forum.xda-developers.com/showthread.php?t=1621146
Never let your battery die like you did. You can always force a shutdown by keeping the power button pressed down for 20-30 seconds.
EDIT: I'd been meaning to post this guide for a while...
http://forum.xda-developers.com/showthread.php?t=1623244
and I missed the part of your post about being "stuck at loading screen" the first time I read it. I suggest you read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
make sure the device drivers are working (part 2) and learn some fastboot commands (part 3) so you can reset the bootmode on your device back to normal and reboot it.
Click to expand...
Click to collapse
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?

andersonrel said:
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
Click to expand...
Click to collapse
Unfortunately, if the device isn't booting up, it won't charge. Like the guide I posted above says, the device needs to load up a ramdisk before it will charge. If all you see is that KF/Android logo, then it's still in the bootloader and it's not charging your battery.
First, you'll have to get your drivers in order so you can send the device fastboot commands. I suggest you disconnect the KF from your computer and make sure it's turned off. Use the KFU driver install file and get it to install the drivers again onto your machine. I'm not sure if it will help, but it wouldn't hurt to reboot your computer after that. When it's back up and running again, open up the device manager. When you connect the KF back up to your computer, it should automatically power up again... look at what device comes up as it boots. The first thing you see (hopefully) is "Android Phone -> Android ADB Interface" appear. If you see that, you can be reasonably sure you can send it fastboot commands.
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
There's a lot of "hopefully" things that have to go right for this to work. You've got a few compounded issues that are giving you problems and all of them have to get fixed for the battery to start charging again.

andersonrel said:
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
Click to expand...
Click to collapse
To fix the "cannot run, adbwin.dll missing", shift + right click on the folder containing adb.exe and select something like "Run as Command"
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
To fix the "cannot run, adbwin.dll missing", shift + right click on the folder containing adb.exe and select something like "Run as Command"
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I´m gonna try this and will post results. Thanks a lot.

kinfauns said:
Unfortunately, if the device isn't booting up, it won't charge. Like the guide I posted above says, the device needs to load up a ramdisk before it will charge. If all you see is that KF/Android logo, then it's still in the bootloader and it's not charging your battery.
First, you'll have to get your drivers in order so you can send the device fastboot commands. I suggest you disconnect the KF from your computer and make sure it's turned off. Use the KFU driver install file and get it to install the drivers again onto your machine. I'm not sure if it will help, but it wouldn't hurt to reboot your computer after that. When it's back up and running again, open up the device manager. When you connect the KF back up to your computer, it should automatically power up again... look at what device comes up as it boots. The first thing you see (hopefully) is "Android Phone -> Android ADB Interface" appear. If you see that, you can be reasonably sure you can send it fastboot commands.
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
There's a lot of "hopefully" things that have to go right for this to work. You've got a few compounded issues that are giving you problems and all of them have to get fixed for the battery to start charging again.
Click to expand...
Click to collapse
I tried to connect to a different pc. It does get recognized on device manager (as kindle) for few seconds and then it dissapears again...not sure what to do now in order to charge it...any suggestions?

Hey guys thanks for all the help so far, i bricked my kindle to the point of no shell after i tried to reflash the stock rom and was stuck in no mans land. So i ordered skorpn's factory cable (thanks again for sending it up north of the border) and when i plug it into the pc it loads the "kindle fire" screen ans stays there. It shows up in device manager but not when i look for it under adb devices and device won't be found in fastboot. Tried reinstalling the drivers and still no luck. Any ideas how i can get this thing back to the point of usability? Thanks for any help you have

andersonrel said:
I tried to connect to a different pc. It does get recognized on device manager (as kindle) for few seconds and then it dissapears again...not sure what to do now in order to charge it...any suggestions?
Click to expand...
Click to collapse
Fix your drivers. Read this:
http://forum.xda-developers.com/showthread.php?p=23747671
djsaxon said:
Hey guys thanks for all the help so far, i bricked my kindle to the point of no shell after i tried to reflash the stock rom and was stuck in no mans land. So i ordered skorpn's factory cable (thanks again for sending it up north of the border) and when i plug it into the pc it loads the "kindle fire" screen ans stays there. It shows up in device manager but not when i look for it under adb devices and device won't be found in fastboot. Tried reinstalling the drivers and still no luck. Any ideas how i can get this thing back to the point of usability? Thanks for any help you have
Click to expand...
Click to collapse
First, fix your drivers:
http://forum.xda-developers.com/showthread.php?p=23747671
Then:
http://forum.xda-developers.com/showthread.php?p=25400963

kinfauns said:
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
Click to expand...
Click to collapse
Well I gave this a shot and it said: "finished. total time: 0.080s"
but it's still just flashing the android logo with kindle fire underneath.

maw230 said:
Well I gave this a shot and it said: "finished. total time: 0.080s"
but it's still just flashing the android logo with kindle fire underneath.
Click to expand...
Click to collapse
That's because you have an entirely different problem.
http://forum.xda-developers.com/showthread.php?p=25400963

soupmagnet said:
That's because you have an entirely different problem.
http://forum.xda-developers.com/showthread.php?p=25400963
Click to expand...
Click to collapse
Thank you.

hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?

jakelongryan said:
hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?
Click to expand...
Click to collapse
There are several reasons why you would get the typical "waiting for device" message, so...
...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.
Step 1. Start a new thread in the Q&A section.
Step 2. Explain in GREAT detail exactly what your problem is.
Step 3. Explain in GREAT detail exactly how your problem started.
Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.
Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.
Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.

soupmagnet said:
There are several reasons why you would get the typical "waiting for device" message, so...
...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.
Step 1. Start a new thread in the Q&A section.
Step 2. Explain in GREAT detail exactly what your problem is.
Step 3. Explain in GREAT detail exactly how your problem started.
Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.
Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.
Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.
Click to expand...
Click to collapse
great advice and exactly what im gonna do. been searching for 2 weeks now reading and learning and still stuck so be looking out for my thread

[Q] Kindle Fire Boot Question

I have recently installed Reloaded's CM9 on my Kindle Fire correctly, rooting first and using KFU. Everything went smoothly, but the other day my battery ran out, and now, whenever i'm charging it, whether it's from the laptop or from an outlet, the red triangle with the fire inside it blimps on screen and nothing happens. When it's disconnected from power, it won't start, won't do anything, and the power button won't turn it on. What does the yellow triangle blimp mean, a discharged battery, bootloop, is something else wrong?
Thanks.

Luppertazzi said:
I have recently installed Reloaded's CM9 on my Kindle Fire correctly, rooting first and using KFU. Everything went smoothly, but the other day my battery ran out, and now, whenever i'm charging it, whether it's from the laptop or from an outlet, the red triangle with the fire inside it blimps on screen and nothing happens. When it's disconnected from power, it won't start, won't do anything, and the power button won't turn it on. What does the yellow triangle blimp mean, a discharged battery, bootloop, is something else wrong?
Thanks.
Click to expand...
Click to collapse
Red triangle? Blimp?
Read this...
http://forum.xda-developers.com/showthread.php?t=1623244

Yellow triangle, blimp. It's now on the wall outlet, charging with the original AC but it still blimps with the yellow triangle. I can't get it turned off by holding the power button for 30+ seconds, nothing happens, just keeps blimping even when in the power outlet. When it's off, it's off and doesn't respond to anything. It says "press power button to enter recovery" but when i press it, nothing. Just blimping.

Luppertazzi said:
Yellow triangle, blimp. It's now on the wall outlet, charging with the original AC but it still blimps with the yellow triangle. I can't get it turned off by holding the power button for 30+ seconds, nothing happens, just keeps blimping even when in the power outlet. When it's off, it's off and doesn't respond to anything. It says "press power button to enter recovery" but when i press it, nothing. Just blimping.
Click to expand...
Click to collapse
I gave you a link to a guide that fully explains what's going on and why "nothing happens." It also gives you a suggestions on what usually works and if it doesn't, the next thing you should attempt in order to fix your problem. If you don't want to try that, you can crack your case open, pull out the battery, find a charger that will charge it offline and stick it back in there.

Luppertazzi said:
Yellow triangle, blimp. It's now on the wall outlet, charging with the original AC but it still blimps with the yellow triangle. I can't get it turned off by holding the power button for 30+ seconds, nothing happens, just keeps blimping even when in the power outlet. When it's off, it's off and doesn't respond to anything. It says "press power button to enter recovery" but when i press it, nothing. Just blimping.
Click to expand...
Click to collapse
Never let your battery complety drain with the new kernel.
Try this:
1. Overnight charge with an iPhone charger (even the Kindle show yellow triangle).
2. If above method won't work,
Extract the kernel from stock firmware (get it from amazon)
Flash the kernel in fastboot (yellow triangle)
Reboot
Charge with wall charger at least 4 hours.
If you're lucky then you can flash Hascode #8 kernel, wipe cache/dalvik and boot normally.

Is it charging even when the yellow blip is on from a wall outlet?

Sorry for the double post.
This new 1.4a bootloader looks like a chance worth taking. Problem is, i can't get into recovery to flash the .zip.
I left it overnight to charge from the wall OEM charger, nothing. Still yellow triangle flashing. It tells me to push power button to get it to recovery but whatever i do or however long i push it it's unusable.
Any other suggestions on how to solve it? I can't use the power button as it's useless and can't get it to recovery. My PC won't recognize it either.

Luppertazzi said:
Sorry for the double post.
This new 1.4a bootloader looks like a chance worth taking. Problem is, i can't get into recovery to flash the .zip.
I left it overnight to charge from the wall OEM charger, nothing. Still yellow triangle flashing. It tells me to push power button to get it to recovery but whatever i do or however long i push it it's unusable.
Any other suggestions on how to solve it? I can't use the power button as it's useless and can't get it to recovery. My PC won't recognize it either.
Click to expand...
Click to collapse
Unzip the archive and extract the .bin file inside it.
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on post #3 to learn how to use fastboot.
Then you'll want to get the device into fastboot mode by issuing a command like...
Code:
fastboot getvar product
and then rebooting the KF. The post above will tell you what to look for when you manage to get it into fastboot mode. It will also tell you how to flash the .bin file you extracted from the .zip file and tell you how to change bootmodes if necessary. Also read the OP for FFF 1.4 for details on how to use your new bootloader.

http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html

soupmagnet said:
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
Click to expand...
Click to collapse
All due respect to all of you, quit giving me links and how-to's that i already read. My problem is unique and i will take my time to describe it one more time, so maybe one of you can actually help.
Kindle fire got discharged completely. Now, whenever it's plugged into a computer or a power outlet, i get a flashing yellow triangle, urging me to hit power button to get into recovery. I hit power button, does nothing. Keep it pressed for hours, does nothing, just the stupid blimp. From what i understand, i need to get the device into fastboot in order to flash a new bootloader, like the 1.4a. Here's where the problem comes in. I have ADB and SDK and whatever else installed correctly, even fastboot and KFU. I have tried one suggestion of a user urging me to write the fastboot commands:
Type or paste the command, fastboot flash bootloader fff-u-boot_v1.4a.bin, when you see <waiting for device>, turn the KF on.
Click to expand...
Click to collapse
This basically meant i should keep my KF unplugged from the PC, write that command and when it's waiting for device, plug it in. It didn't work, it keeps on Waiting for Device and that's it. My Kindle Fire is not recognized by my PC. If it would have worked, just when i plugged in my Kindle Fire it should have executed the flash in that split second it was in fastboot mode and it should have rebooted.
I have tried putting it in fastboot mode over KFU, but the ADB is OFFLINE and my Kindle isn't recognized by my PC.
What else on God's green earth can i try to make sense of all this mess?

Luppertazzi said:
All due respect to all of you, quit giving me links and how-to's that i already read. My problem is unique and i will take my time to describe it one more time, so maybe one of you can actually help.
Kindle fire got discharged completely. Now, whenever it's plugged into a computer or a power outlet, i get a flashing yellow triangle, urging me to hit power button to get into recovery. I hit power button, does nothing. Keep it pressed for hours, does nothing, just the stupid blimp. From what i understand, i need to get the device into fastboot in order to flash a new bootloader, like the 1.4a. Here's where the problem comes in. I have ADB and SDK and whatever else installed correctly, even fastboot and KFU. I have tried one suggestion of a user urging me to write the fastboot commands:
This basically meant i should keep my KF unplugged from the PC, write that command and when it's waiting for device, plug it in. It didn't work, it keeps on Waiting for Device and that's it. My Kindle Fire is not recognized by my PC. If it would have worked, just when i plugged in my Kindle Fire it should have executed the flash in that split second it was in fastboot mode and it should have rebooted.
I have tried putting it in fastboot mode over KFU, but the ADB is OFFLINE and my Kindle isn't recognized by my PC.
What else on God's green earth can i try to make sense of all this mess?
Click to expand...
Click to collapse
With "all due respect" there is absolutely NOTHING about your situation that is unique. I see 15 people with the same exact problem every day. As a matter of fact, it is so NOT unique, that kinfauns had to take the time to write up a small explanation for it.
If you had this so-called "all due respect" you would take into consideration the fact that some of the more experienced users here might actually know what they're talking about. We gain nothing from helping you, remember that.
Your problem is quite simple. Your battery is dead or close to it. Your device doesn't have enough power to boot far enough to start the charging process. The link kinfauns gave you, tells you that explicitly. He offers a few tips on how to fix your problem. But depending on how dead your battery is, they might not always work.
Hence the links I gave you. I gave you information on a "factory cable", its purpose, when you might need one, and how to purchase/make one. Right there is all the information you need to fix your problem. Go back and read the links given to you. Only this time, make sure you understand them before making another presumptive comment.

soupmagnet said:
With "all due respect" there is absolutely NOTHING about your situation that is unique. I see 15 people with the same exact problem every day. As a matter of fact, it is so NOT unique, that kinfauns had to take the time to write up a small explanation for it.
If you had this so-called "all due respect" you would take into consideration the fact that some of the more experienced users here might actually know what they're talking about. We gain nothing from helping you, remember that.
Your problem is quite simple. Your battery is dead or close to it. Your device doesn't have enough power to boot far enough to start the charging process. The link kinfauns gave you, tells you that explicitly. He offers a few tips on how to fix your problem. But depending on how dead your battery is, they might not always work.
Hence the links I gave you. I gave you information on a "factory cable", its purpose, when you might need one, and how to purchase/make one. Right there is all the information you need to fix your problem. Go back and read the links given to you. Only this time, make sure you understand them before making another presumptive comment.
Click to expand...
Click to collapse
And after reading all that information, which i did, carefully, and trying to understand all of this, the only option i might have is a factory cable to get it into fastboot mode? What about the temporary fastboot, can i profit from that or try to at least?
My main issue is the ADB is offline and i can't get it into fastboot via KFU, shouldn't it be recognized as online nonetheless?
Everybody keeps mentioning the original AC charger, flashing to stock, flashing FFF 1.4a, but i can't even get it to fastboot, recovery is a longshot. How am i supposed to fix this if all the solutions given reffer to fastboot or TWRP, both of which i cannot access?

You already tried temporary fastboot when you turned your Kindle on after seeing "waiting for device".
You can mess around with your drivers to see if you can get it to connect... http://forum.xda-developers.com/showthread.php?p=23747671 ...I think it's unlikely, but definitely not impossible.

soupmagnet said:
You already tried temporary fastboot when you turned your Kindle on after seeing "waiting for device".
You can mess around with your drivers to see if you can get it to connect... http://forum.xda-developers.com/showthread.php?p=23747671 ...I think it's unlikely, but definitely not impossible.
Click to expand...
Click to collapse
Okay, thank you, that's all i wanted to know. I thought my situation was different because ADB kept showing OFFLINE and i couldn't speculate the temporary fastboot or the normal fastboot. If you're saying this is normal when the battery's dead then okay.
I guess i'm buying a factory cable. One last question. When that cable does get in my hands, all i have to do is plug it in my laptop USB port, then into my kindle, gaining automatic fastboot, and then write:
fastboot flash bootloader fff-u-boot_v1.4a.bin
Click to expand...
Click to collapse
and
fastboot reboot
Click to expand...
Click to collapse
and it should have flashed to the newest 1.4a that bypasses this problem, correct?

Yes, assuming your drivers are in good working order.

When I try to troubleshoot someone else's problem, I do my best to understand what it is that they don't understand. Now, I finally see the reason why you are so resistant to trying my suggestions... When the bootloader says "press power button for recovery" it's not URGING you to do anything. It's SUGGESTING and providing a reminder of how to get to recovery. It's like a road sign that says "exit here for rest stop." Whether or not you pass that point with a full bladder, that reminder is ALWAYS there. It has nothing to do with your present situation.
I think you've been convinced that you need to get into fastboot mode. You can follow my previous instructions and send that command during temporary fastboot. If you are successful, it will stop the temporary fastboot countdown and stay in fastboot mode. You can get the factory cable and that will automatically put you in fastboot mode, but you are still going to have to be able to send it fastboot commands anyway. In either case, you'll have to fix whatever is keeping your computer from sending fastboot commands to the device and that's almost always the device drivers. The only difference between my suggestion and soupmagnet's is the factory cable's ability to automatically keep you in fastboot mode so you have more of an opportunity to diagnose the problem.

[Q] Kindle fiire rooting fail

SO recently i tried to root my kindle using one of the guides unfortunately i somehow messed up during it or something, but the problem i have now is whenever i turn my kindle on it has the yellow triangle with a fire logo in it and at the bottom it says "press power button for recovery". Simple enough only the second problem is i do not have TWRP or anything like that so pressing the power button literally does nothing. Unfortunately as well when i plug it into the USB it will identify that something is connected but it won't install it to the pc because it cant find some hardware or something. So i cant get it to start up or connect it to the pc and am desperately looking for a solution. Thanks to anyone who can help.

First off. Do you have a first gen kindle fire?
6.3.x or 10.x.x?
If you have a first gen,
Download this.
http://forum.xda-developers.com/showthread.php?t=2192818
Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer.
Does KFU find the device? If so, good. You will be taken to the main screen at that point I think.
Choose to install recovery (TWRP).
That should be it. Post here if there's any problems.
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

jma9454 said:
First off. Do you have a first gen kindle fire?
6.3.x or 10.x.x?
If you have a first gen,
Download this.
http://forum.xda-developers.com/showthread.php?t=2192818
Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer.
Does KFU find the device? If so, good. You will be taken to the main screen at that point I think.
Choose to install recovery (TWRP).
That should be it. Post here if there's any problems.
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.
Click to expand...
Click to collapse
Attached is a picture of what my kindle screen looks like. I tried resetting it, plugging it into the computer, etc. but this screen never changes. Also on my pc it doesn't recognize it as a kindle, it recognizes it as an unknown device. So I can't put any files onto my kindle at the moment because my PC keeps telling my me driver is not working or something. I attached files showing what my pc says as well. Also I apologize for the bad quality of the pictures i don't own a very nice camera at all so I apologize in advanced for that. The last 3 are readable the 1st one is basically just a yellow triangle with a fire symbol in the middle and it says "press power button for recovery" but nothing happens when i press the power button, and the 2 photo is a little bit blurry but all it says is:
Unknown Device
Device Type: Universal Serial Bus controllers
Manufacturers: (Standard USB Host Controller)
Location: Port_#0009.Hub_#0002
Device Status:
Windows has stopped this device because it has reported problems. (Code 43)

The "press power button for recovery" can be confusing if you don't know what's going on. That version of FireFireFire sits in fastboot mode for...I think...8 seconds before it will recognize the power button. You can repeatedly press the power button until the LED turns orange to see if that gets you into recovery. If not, you're probably looking at something like usbboot to replace your bootloader. You need to replace your bootloader anyway, but hopefully you'll be able to flash a new one in recovery instead.

soupmagnet said:
The "press power button for recovery" can be confusing if you don't know what's going on. That version of FireFireFire sits in fastboot mode for...I think...8 seconds before it will recognize the power button. You can repeatedly press the power button until the LED turns orange to see if that gets you into recovery. If not, you're probably looking at something like usbboot to replace your bootloader. You need to replace your bootloader anyway, but hopefully you'll be able to flash a new one in recovery instead.
Click to expand...
Click to collapse
Repeatedly pressed the power button for about 30 seconds with the same result, green light still, and no screen change. So it looks like its this usbboot, how would i go about doing this in order to replace my bootloader?

KindleFail said:
Repeatedly pressed the power button for about 30 seconds with the same result, green light still, and no screen change. So it looks like its this usbboot, how would i go about doing this in order to replace my bootloader?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1405052
http://forum.xda-developers.com/showthread.php?t=1430038&highlight=firekit
Since you will need Linux anyway, you might as well download and install SoupKit. It comes with Firekit and will probably make your life easier in the long run.

What guide did you use exactly? I can see if we can update that guide to use the latest FFF because that is a very old alpha version that has had many issues with the yellow triangle in the past. I'm surprised its still floating around here.
Sent from my One V using xda app-developers app

Stuck at boot logo
Hey all,
I'm not sure if this is the correct place to post but I didn't want to make a new topic and this seems to be in the area of what is wrong with my kindle... I tried the new KFU v0.9.9 on my first gen KF running 6.3.2. I have rooted it before (not on 6.3.2), but unrooted and restored to factory settings because I thought I was going to sell it. However, the plans fell through and I am keeping it so I wanted to re-root and all that jazz....
My question is, how do I get it boot past the boot logo? I used the KFU, but firstly when it prompts it says:
'findstr' is not recognized as an internal or external command, operable program or batch file.
So none of the commands pop up, however they are still there... For example, i followed:
"Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer."
And I can get to fastboot, but it says there is no device connected to my computer. If you need more details on the problem I'll be glad to give them to you. Hopefully someone checks this thread again
Thanks

What version of Windows do you have that doesn't have 'findstr'?
What do you see in your device manager while the device is plugged in?

soupmagnet said:
What version of Windows do you have that doesn't have 'findstr'?
What do you see in your device manager while the device is plugged in?
Click to expand...
Click to collapse
I'm running a 64 bit version of Windows 7 professional.
There's nothing in the device manager when I plug it in.

[Q]bricked kindle in usbboot mode.

I recently recieved this kindle as is from a friend and i was asked to fix it, i don't really have any information to go off of other that what i could gather. So far, it doesn't turn on/charge, in windows it's recognized as a OMAP4430 device only for a second or two, from there i tried using FireKit on ubuntu via usb. that gave me some success, after using usb_fix_parts_and_install_fff_twrp i saw the yellow triangle on the screen; however, the script seemed to stop with this:
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
and won't progress any further. i'm not really sure what to do at this point since i feel so close and it would be a shame to quit now.
I've also tried using multiple USB cables and a fastboot cable, but none seem to be making a difference. so please if you know of anything that would help, it would be greatly appreciated.

You only have a small window of time to get everything through. When the usbboot script hangs at "waiting for device", leave the script running, unplug the device, hold the power button for 15 seconds, create the short and plug the device back in.
You may have to do it a couple of times.
Once you see the yellow triangle, don't shut the device off until you install FireFireFire1.4a while in recovery. You may have to use adb to push the .zip file to your sdcard first though.

Oh, ok thanks. i didn't know i still had to preform the short, since it was already in usb boot mode. anyway trying it now.

I'm not sure if I'm doing it correctly. I followed what you said and after shorting the device, and plugging it back in, it brings up the yellow triangle again. But pressing the power button doesn't bring me into a recovery and the script still says waiting for device

I should have clarified that a bit, but oh well.
Go ahead and reboot to try to access recovery with the power button. Sometimes when you reboot, depending on how everything went, the device doesn't come on again and you have to start all over...but you should be fine though.

=/ not too much luck there...maybe i'm shorting the cpu incorrectly, not sure. once the script hangs i unplug and power off the device, and essentially just any old conductive piece of wire should do and connect it to the point and the metal bar, right? i'm using a male to male jumper cable at the moment. While doing this i've noticed a couple times the kindle would power back on and display the yellow triangle but still no other responsiveness or progess in the script itself.

When the yellow triangle is displayed, do you have access to fastboot?
Try sending 'fastboot getvar product'

i guess not. it just sits at "< waiting for device >"

Try using a safety pin to make the short....that might help.

so slight update, it turns out i have no problem booting a firefirefire from usb, but from there it just refuses to initiate fastboot and ubuntu can't seem to recognize it. i thought it might have been a possibly issue with the specific version of FFF i was booting from, but so far 1.2, 1.3 and 1.4 all give me the same issue.

dragon0010 said:
so slight update, it turns out i have no problem booting a firefirefire from usb, but from there it just refuses to initiate fastboot and ubuntu can't seem to recognize it. i thought it might have been a possibly issue with the specific version of FFF i was booting from, but so far 1.2, 1.3 and 1.4 all give me the same issue.
Click to expand...
Click to collapse
Make sure you have FFF1.4a and run your fastboot commands as root in Ubuntu.

so i just found out something interesting. i had a spare fully functional kindle that i put into usb boot mode with the shorting trick, and did all the steps, and fastboot was able to recognize it. i haven't done anything differently with the currently bricked kindle, but it just wont get past "waiting for device" when issuing any fastboot command. so at this point is there really anything i can do?

Fire TV 2nd Gen stuck in some kind of kiosk mode?

I purchased a used Fire TV 2nd gen online but when I boot it up, it goes into some kind of kiosk slideshow for 1st gen Amazon Echo devices that I can't exit.
It boots normally at first with the Fire TV logo an all but there's no config screen or anything. It boots to a white AMAZON ECHO screen with pics of the original Echo device then goes into a slide show showing all the various features of Amazon echo. The remote doesn't sync and the device will only show up on the Fire TV remote app for a few seconds before disappearing after boot. I can plug in a physical keyboard and if I press the ESC key, the screen will go black for a second before re-starting the slide show from the beginning. So far I've not been able to find any other keyboard functions that react, only the ESC key so far.
If I had to guess, I'd say it probably has a much older version of the OS on it as the slide show is for the older generations of Echo.
I'm assuming this used to be some kind of demo device, maybe from Best Buy or something but does anyone know how to get out of this slide show so it can be used as a normal device or is this thing just useless? Suggestions?

Hannover2k said:
I purchased a used Fire TV 2nd gen form ebay but when I boot it up, it goes into some kind of kiosk slideshow for Amazon Echo that I can't exit.
It boots normally at first with the Fire TV logo an all but there's no config screen or anything. It boots to a white AMAZON ECHO screen with pics of the original Echo device then goes into a slide show showing all the various features of Amazon echo. The remote doesn't sync and the device will only show up on the Fire TV remote app for a few seconds before disappearing after boot. I can plug in a physical keyboard and if I press the ESC key, the screen will go black for a second before re-starting the slide show from the beginning. So far I've not been able to find any other keyboard functions that react, only the ESC key so far.
If I had to guess, I'd say it probably has a much older version of the OS on it as the slide show is for the older generations of Echo.
I'm assuming this used to be some kind of demo device, maybe from Best Buy or something but does anyone know how to get out of this slide show so it can be used as a normal device or is this thing just useless? Suggestions?
Click to expand...
Click to collapse
Just as an update, I found that if I plug in a USB keyboard, pressing ALT+ESC will pop up a menu telling me to press the home button if I wish to return to the home screen. No remote works with it yet so that doesn't help much. Pressing ALT+Space will bring up what appears to be the FireTV search keyboard but typing doesn't bring up anything, it just echos what I type and there's no 'ENTER' key to submit anything.
If I do this immediately after the slideshow comes up, it will prompt that there's no network connection and take me to the network settings menu. I tried plugging in a LAN cable but the device doesn't seem to pull up an IP address. I manually entered an IP but was unable to find it on the network. Even tried using the APPS2FIRE app to see if it could see it in the search but it doesn't. I connected it to wifi successfully but same issue, it doesn't seem to actually pull an IP address as I can't see it on my network when I scan for it. The network settings know when the LAN is plugged in and removed though.
Plugging in USB A-A doesn't seem to do anything. I tried running the Unbrick batch file from one of the other posts but it's intended to work on non-rooted devices with the jumper trick, I think, and while it does kick off the script, it stops at 0% and never does anything. I'm sure this is an older OS that can still be rooted but I just don't know how to get to anything in it since I can't get into ADB.
Any suggestions would be appreciated though!

Hannover2k said:
I'm sure this is an older OS that can still be rooted but I just don't know how to get to anything in it since I can't get into ADB.
Any suggestions would be appreciated though!
Click to expand...
Click to collapse
If you can't get device to show up on adb devices via terminal/command prompt or access settings menu I don't think there's much you can do.
1.Try doing a scan with Fing Network Tools and see if IP shows.
2. Try downloading and installing FireTV remote App on your phone and connecting if it finds stick.
Without adb being activated on the stick, and settings menu unavailable to enable adb there is not much else for it m8, these ebay sticks are dodgy to say the least I've been stung a few times. Even bought one and opened it to find the heat shield casing missing and clk broke lol

Bertonumber1 said:
If you can't get device to show up on adb devices via terminal/command prompt or access settings menu I don't think there's much you can do.
1.Try doing a scan with Fing Network Tools and see if IP shows.
2. Try downloading and installing FireTV remote App on your phone and connecting if it finds stick.
Without adb being activated on the stick, and settings menu unavailable to enable adb there is not much else for it m8, these ebay sticks are dodgy to say the least I've been stung a few times. Even bought one and opened it to find the heat shield casing missing and clk broke lol
Click to expand...
Click to collapse
I'll give those a shot. I tried the jumper technique from the Unbrick Fire TV 2 post and was able to get partway through that process and to the prompt where it tells me to remove the jumper and press enter but it gets an error after copying the files, just before it should boot to twrp. something about the source path being empty. I can post a pic if that's helpful. I think may have forgotten to run the disable modemmanager command so I'll give that another try later. I didn't realize you had to run that every time you reboot linux. I know just enough to be dangerous with it.

Hannover2k said:
I'll give those a shot. I tried the jumper technique from the Unbrick Fire TV 2 post and was able to get partway through that process and to the prompt where it tells me to remove the jumper and press enter but it gets an error after copying the files, just before it should boot to twrp. something about the source path being empty. I can post a pic if that's helpful. I think may have forgotten to run the disable modemmanager command so I'll give that another try later. I didn't realize you had to run that every time you reboot linux. I know just enough to be dangerous with it.
Click to expand...
Click to collapse
Yeah great have a look here too
https://docs.google.com/document/u/0/d/1zYtqmf4RfLOkrPyPjf1C0CjAZf_0E1JohIlTyVY5kGs/mobilebasic
Files here
https://drive.google.com/drive/u/0/mobile/folders/1GbMTBHuFhwT_uyZaJs0ApsG_RQ5Wg_7F
Should work :good:

Bertonumber1 said:
Yeah great have a look here too
https://docs.google.com/document/u/0/d/1zYtqmf4RfLOkrPyPjf1C0CjAZf_0E1JohIlTyVY5kGs/mobilebasic
Files here
https://drive.google.com/drive/u/0/mobile/folders/1GbMTBHuFhwT_uyZaJs0ApsG_RQ5Wg_7F
Should work :good:
Click to expand...
Click to collapse
Unfortunately I can't use those methods. While I can get into the network settings, I can't get into any other settings. I never I never left it connected to wifi so I've been using a LAN cable to test. Booting without the LAN causes it to get an error and takes me to the network settings but I can't get to anything else from there.
Been messing with the jumper method from https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303 but not having any luck yet as per the attached pic. Also tried the unbrick method which gets stuck at 000000200: 0% every time. Just for the heck of it, I shorted DAT0 and ran it and it popped up an error saying it can't locate a 'system' partition. The unit still boots up with the fire tv logo and goes into that demo mode so I'm sure there's a partition present. This is really a challenge! Running out of things to try though.

Hannover2k said:
Unfortunately I can't use those methods. While I can get into the network settings, I can't get into any other settings. I never I never left it connected to wifi so I've been using a LAN cable to test. Booting without the LAN causes it to get an error and takes me to the network settings but I can't get to anything else from there.
Been messing with the jumper method from https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303 but not having any luck yet as per the attached pic. Also tried the unbrick method which gets stuck at 000000200: 0% every time. Just for the heck of it, I shorted DAT0 and ran it and it popped up an error saying it can't locate a 'system' partition. The unit still boots up with the fire tv logo and goes into that demo mode so I'm sure there's a partition present. This is really a challenge! Running out of things to try though.
Click to expand...
Click to collapse
You may have a stick that cannot be rooted/modified via amonet, one with dl mode disabled. These devices around December 2019 started to appear on the market and there's no way round them.

Bertonumber1 said:
You may have a stick that cannot be rooted/modified via amonet, one with dl mode disabled. These devices around December 2019 started to appear on the market and there's no way round them.
Click to expand...
Click to collapse
The device is a Fire TV 2nd gen Sloane so I would expect it to work like others I've rooted, but that kiosk os might do just what you said and disabled DL mode. I'll still play with it a bit but not sure what else can be done. Maybe some new method will come along in the future so I'll just hold on to it.
Thanks for all the input though. Greatly appreciated.

Hannover2k said:
The device is a Fire TV 2nd gen Sloane so I would expect it to work like others I've rooted, but that kiosk os might do just what you said and disabled DL mode. I'll still play with it a bit but not sure what else can be done. Maybe some new method will come along in the future so I'll just hold on to it.
Thanks for all the input though. Greatly appreciated.
Click to expand...
Click to collapse
Sorry mate my bad I thought it was a stick you had I was helping some other guy in firestick tank forum and got mixed up.
Try the short method again only when you get the error :
Leave dc power on (plugged into box)
Remove USB a to USB a cable
Close terminal
Open new terminal up in amonet once again
Run the boot-rom step again BUT hit enter TWICE
Then plug USB cable back in
Pull the dc power and plug it in again
The script should go through
I followed this from another member and it always works for me, has worked on numerous Sloanes. Give it a go, worth a shot mate

Bertonumber1 said:
Sorry mate my bad I thought it was a stick you had I was helping some other guy in firestick tank forum and got mixed up.
Try the short method again only when you get the error :
Leave dc power on (plugged into box)
Remove USB a to USB a cable
Close terminal
Open new terminal up in amonet once again
Run the boot-rom step again BUT hit enter TWICE
Then plug USB cable back in
Pull the dc power and plug it in again
The script should go through
I followed this from another member and it always works for me, has worked on numerous Sloanes. Give it a go, worth a shot mate
Click to expand...
Click to collapse
Thanks for the info, it's worth a try. Just to clarify, when you say to press enter twice, do you mean to press it twice at the prompt where it tells you to remove the short and press enter?

Hannover2k said:
Thanks for the info, it's worth a try. Just to clarify, when you say to press enter twice, do you mean to press it twice at the prompt where it tells you to remove the short and press enter?
Click to expand...
Click to collapse
Hey @Hannover2k, yeah the Sloane is stubborn to root, just keep at it, once you see ***remove short and hit enter** and get an error try leaving it switched on but remove USB, then run the script again and hit enter again after you hit it once, disconnect/reconnect the dc power and plug USB in without the short (if displaying remove short) . Should go through
Another thing...
This what happened to me the other day. If your preloader is gone (it's displaying remove short when there is no short). Disconnect power, disconnect USB, run the the script and connect power and wait 50-70 seconds then plug USB back in.
As I said these Sloanes are tough but you should get it, using the short "jumper" method m8

Bertonumber1 said:
Hey @Hannover2k, yeah the Sloane is stubborn to root, just keep at it, once you see ***remove short and hit enter** and get an error try leaving it switched on but remove USB, then run the script again and hit enter again after you hit it once, diconnect/reconnect the dc power. Should go through
Another thing...
This what happened to me the other day. If your preloader is gone (it's displaying remove short when there is no short). Disconnect power, disconnect USB, run the the script and connect power and wait 50-70 seconds then plug USB back in.
As I said these Sloanes are tough but you should get it, using the short "jumper" method m8
Click to expand...
Click to collapse
Sorry is I'm missing something here. I've been trying to do your method and while I've been getting different error messages and results, I'm still not quite sure I'm doing it right.
After I get the first error after removing the short, you mention above to remove the USB then run the script again, etc. At what point do I plug the USB cable back in? Do I plug the USB back in after removing the power? When I do remove the power, do i need to reconnect the Jumper before plugging it back in?
Sorry if I'm lame, I've just done this jumper thing 100 times and can get many different results but not the one we're looking for! lol
UPDATE: Holy cow, I got it to work the very next time after posting the message! Here's what I did:
1) Ran the script, connected jumper and powered on the device.
2) Got error message.
3) Unplugged USB then re-ran script, pressing enter again after running the command.
4) Plugged USB back in.
I did not reconnect the jumper. When the USB cable was re-connected it did display a message to remove the jumper and press enter, however I did not have to do that. All kinds of stuff started flying all over the screen, then it got to;
Clearing Preloader Header
Flashing Tee
Flashing Bootloader
Flashing Unbrick Image
Flashing Boot
Booting to TWRP
I'm literally grinning ear to ear right now! Thanks for all your help with this! Even if it doesn't work at this point, I'm very happy to have gotten this far!
I can get these kiosk devices for $20 each. Box only, no power or remote. Does anyone think it would be worth it to buy a few of them and try to sell them off with refreshed imaged on them? There's a lot available so just wondering.

Hannover2k said:
Sorry is I'm missing something here. I've been trying to do your method and while I've been getting different error messages and results, I'm still not quite sure I'm doing it right.
After I get the first error after removing the short, you mention above to remove the USB then run the script again, etc. At what point do I plug the USB cable back in? Do I plug the USB back in after removing the power? When I do remove the power, do i need to reconnect the Jumper before plugging it back in?
Sorry if I'm lame, I've just done this jumper thing 100 times and can get many different results but not the one we're looking for! lol
UPDATE: Holy cow, I got it to work the very next time after posting the message! Here's what I did:
1) Ran the script, connected jumper and powered on the device.
2) Got error message.
3) Unplugged USB then re-ran script, pressing enter again after running the command.
4) Plugged USB back in.
I did not reconnect the jumper. When the USB cable was re-connected it did display a message to remove the jumper and press enter, however I did not have to do that. All kinds of stuff started flying all over the screen, then it got to;
Clearing Preloader Header
Flashing Tee
Flashing Bootloader
Flashing Unbrick Image
Flashing Boot
Booting to TWRP
I'm literally grinning ear to ear right now! Thanks for all your help with this! Even if it doesn't work at this point, I'm very happy to have gotten this far!
I can get these kiosk devices for $20 each. Box only, no power or remote. Does anyone think it would be worth it to buy a few of them and try to sell them off with refreshed imaged on them? There's a lot available so just wondering.
Click to expand...
Click to collapse
@Hannover2k Yeah that's you got it sorted then, I tried to explain that method but didn't do a very good job of it lol, make sure you push pre-rooted rom and supersu 2.82 zip to /sdcard, and flash.
Please Remember and note that you cannot flash unsigned zips such as magisk to the Sloane as you're bootloader remains incarcerated , if you're device has cleared preloader and you've entered into twrp it should work
Ps. if you can get a Sloane for that price pm me and we'll sort something, doesn't matter about power cables, remotes etc

Bertonumber1 said:
@Hannover2k Yeah that's you got it sorted then, I tried to explain that method but didn't do a very good job of it lol, make sure you push pre-rooted rom and supersu 2.82 zip to /sdcard, and flash.
Please Remember and note that you cannot flash unsigned zips such as magisk to the Sloane as you're bootloader remains incarcerated , if you're device has cleared preloader and you've entered into twrp it should work
Ps. if you can get a Sloane for that price pm me and we'll sort something, doesn't matter about power cables, remotes etc
Click to expand...
Click to collapse
After flashing the pre-rooted image the first time, everything seemed to work except whenever I restarted via the settings menu, it would show the TWRP pre boot screen but allowing it to continue to boot normally would result in a boot loop. Performing a power cycle would cause the device to skip over the TWRP menu and boot right into the device.
Tried clearing the SD partition and dalvik to free up space as it was only showing about 1.2gb free after the flash. Got the free space back but still the same boot issue after flash, though it did work after a power cycle as opposed to restarting, which I rarely do anyways.
Remembering the Kiosk was for the original echo devices, I got to thinking about it having an older OS again and maybe not liking being flashed directly to the latest version so I re-flashed it to v5.2.6.7_r1. It would boot loop after the TWRP pre login screen but after the first loop it would boot properly. Went ahead and flashed it back to 5.2.7.3_r1 and everything seems to be working perfectly now. Restarts properly and all functionality seems to be present.
I really appreciate your assistance with this. I had them send me another one so I can try this method once more and if it works again, I'll definitely let you know and we'll work something out.
-Han

Hannover2k said:
After flashing the pre-rooted image the first time, everything seemed to work except whenever I restarted via the settings menu, it would show the TWRP pre boot screen but allowing it to continue to boot normally would result in a boot loop. Performing a power cycle would cause the device to skip over the TWRP menu and boot right into the device.
Tried clearing the SD partition and dalvik to free up space as it was only showing about 1.2gb free after the flash. Got the free space back but still the same boot issue after flash, though it did work after a power cycle as opposed to restarting, which I rarely do anyways.
Remembering the Kiosk was for the original echo devices, I got to thinking about it having an older OS again and maybe not liking being flashed directly to the latest version so I re-flashed it to v5.2.6.7_r1. It would boot loop after the TWRP pre login screen but after the first loop it would boot properly. Went ahead and flashed it back to 5.2.7.3_r1 and everything seems to be working perfectly now. Restarts properly and all functionality seems to be present.
I really appreciate your assistance with this. I had them send me another one so I can try this method once more and if it works again, I'll definitely let you know and we'll work something out.
-Han
Click to expand...
Click to collapse
The recovery partition maybe corrupted.
You may try updating twrp to the latest 3.0.05 from Sloane Twrp recovery page.
There you can download the file from here :
https://www.mediafire.com/file/brae6r8lu1np5jm/firetv2_recovery_v6.zip/file
,push it to Sloane /sdcard and run command
from pc
adb shell
Then run:
sh /sdcard/firetv2_recovery_v6.zip
Reboot
That should fix it.
As soon as you update TWRP
Reboot and flash the pre-rooted firmware and supersu 2.82.zip
Then wipe cache, dalvik
Let it boot up and then factory reset (data, dalvik, cache)
Reboot and it should be okay

Bertonumber1 said:
The recovery partition maybe corrupted.
You may try updating twrp to the latest 3.0.05 from Sloane Twrp recovery page.
There you can download the file from here :
https://www.mediafire.com/file/brae6r8lu1np5jm/firetv2_recovery_v6.zip/file
,push it to Sloane /sdcard and run command
from pc
adb shell
Then run:
sh /sdcard/firetv2_recovery_v6.zip
Reboot
That should fix it.
As soon as you update TWRP
Reboot and flash the pre-rooted firmware and supersu 2.82.zip
Then wipe cache, dalvik
Let it boot up and then factory reset (data, dalvik, cache)
Reboot and it should be okay
Click to expand...
Click to collapse
Thanks for the info. The image I installed already had that version of TWRP installed on it but like I said in my last comment, flashing to an older rom then re-flashing back to the latest one seems to have resolved the issue.
No more Kiosk mode, though I wish I could have gotten a look at those files just to see what was going on there.
Anyways, all good now and I have another one of those kiosk units I'm going to try the process again on and if it works, I have access to a lot of these devices so I may refresh them and sell them cheap.
Thanks again for everyones input! Still surprised I got it working normal again.

Bertonumber1 said:
@Hannover2k Yeah that's you got it sorted then, I tried to explain that method but didn't do a very good job of it lol, make sure you push pre-rooted rom and supersu 2.82 zip to /sdcard, and flash.
Please Remember and note that you cannot flash unsigned zips such as magisk to the Sloane as you're bootloader remains incarcerated , if you're device has cleared preloader and you've entered into twrp it should work
Ps. if you can get a Sloane for that price pm me and we'll sort something, doesn't matter about power cables, remotes etc
Click to expand...
Click to collapse
Good news!
I was given a 2nd unit with the same 'issue' and was able to get it to start taking the image within a couple mins. The guy who has them can't do anything with them and has lowered his price per unit so are these worth anything to anyone?
Again, it's the box only, no power cords or remote but I don't expect that to be an issue for someone looking to replace one.
I hope I'm not breaking any rules by asking that but I'm open to any thoughts on this.
-Han

Hannover2k said:
Good news!
I was given a 2nd unit with the same 'issue' and was able to get it to start taking the image within a couple mins. The guy who has them can't do anything with them and has lowered his price per unit so are these worth anything to anyone?
Again, it's the box only, no power cords or remote but I don't expect that to be an issue for someone looking to replace one.
I hope I'm not breaking any rules by asking that but I'm open to any thoughts on this.
-Han
Click to expand...
Click to collapse
@Bertonumber1

Sus_i said:
@Bertonumber1
Click to expand...
Click to collapse
Yeah I've already replied via pm to @Hannover2k I've already bought one with power brick and remote for Roger @Sus_i hannover2k only has the Sloane itself AFAIK I got the full shebang for £27 so it's all good perhaps @Hannover2k can provide a spare and that's us got a couple to got to work on in the name of furthering development

Bertonumber1 said:
Yeah I've already replied via pm to @Hannover2k I've already bought one with power brick and remote for Roger @Sus_i hannover2k only has the Sloane itself AFAIK I got the full shebang for £27 so it's all good perhaps @Hannover2k can provide a spare and that's us got a couple to got to work on in the name of furthering development
Click to expand...
Click to collapse
Hannover2k said:
Sorry is I'm missing something here. I've been trying to do your method and while I've been getting different error messages and results, I'm still not quite sure I'm doing it right.
After I get the first error after removing the short, you mention above to remove the USB then run the script again, etc. At what point do I plug the USB cable back in? Do I plug the USB back in after removing the power? When I do remove the power, do i need to reconnect the Jumper before plugging it back in?
Sorry if I'm lame, I've just done this jumper thing 100 times and can get many different results but not the one we're looking for! lol
UPDATE: Holy cow, I got it to work the very next time after posting the message! Here's what I did:
1) Ran the script, connected jumper and powered on the device.
2) Got error message.
3) Unplugged USB then re-ran script, pressing enter again after running the command.
4) Plugged USB back in.
I did not reconnect the jumper. When the USB cable was re-connected it did display a message to remove the jumper and press enter, however I did not have to do that. All kinds of stuff started flying all over the screen, then it got to;
Clearing Preloader Header
Flashing Tee
Flashing Bootloader
Flashing Unbrick Image
Flashing Boot
Booting to TWRP
I'm literally grinning ear to ear right now! Thanks for all your help with this! Even if it doesn't work at this point, I'm very happy to have gotten this far!
I can get these kiosk devices for $20 each. Box only, no power or remote. Does anyone think it would be worth it to buy a few of them and try to sell them off with refreshed imaged on them? There's a lot available so just wondering.
Click to expand...
Click to collapse
Just wanted to add my Order of Operations to this post. I also bought one of these "Kiosk" boxes without remote or power supply for $13 off of eBay. Great deal, I thought, if I can get it to root. It appears that the order in which you perform the steps is unique to your setup. After trying all the above suggestions with no success (similar errors as listed above), here's what worked for me:
1. Plug in male-to-male USB cable between FTV2 and Linux box
2. Short DAT0 pin on FTV2 board
3. Connect FTV2 AC power
4. Run script
5. Remove short, press enter once when prompted
After TWRP installed (and I figured out how to use it), I was successful in having a usable FTV2 with all of the perks this process brings. Thanks to all who contributed to make this possible, and an extra big thanks to @Hannover2k for being the first to try this on these specifically-challenged boxes. It was a huge help!