Develop Bugs

Stuck at KindleFire white/orange logo. Unresponsive to ADB commands.

First off, thanks to everyone on here who's posted numerous help guides that have helped me in the past. I've rooted several phones in the past and figuered I'd try to root and install Jelly Bean on a Kindle Fire I won at a work event (woohoo!).
The problem right now is the kindle is stuck in fastboot (no root, twrp installed) it boot into the non-animated white and orange "kindle fire" logo screen and stays there.
What I did to put it there:
On a Windows 7 machine, I used KFU 0.96. After reading instructions, I installed TWRP.
Since then, it is not repsonding to adb commands. It will mount the drive to the computer, and the drivers show it's using the correct one from Google Composite device.
After researching, I found someone who mentioned that after several restarts, and smashing "normal boot" commands thru adb while the kindle was starting up (and before it went unresponsive) he was able to move along. When I did this (with KFU), Kindle went into TWRP. From there I followed instructions on flashing pre-rooted 6.2.2 (as the guide indicated, doing wipes) but the flash always failed.
Assuming something wasn't working with Windows, I've gone home to my macbook running Ubuntu 12.04, and while installing SDK from Google, I can not figure out how to get the google sdk running. I followed this guide http://forum.xda-developers.com/showthread.php?t=1550414 but I can't get to step 5, I cannot get the Android SDK Manager to run!!
I have access to dozens of Windows computers, I'm fine with going back to them, but everything I've read makes me think I've got a better shot with Linux due to driver problems on windows.
Also, when I had TWRP loaded on the Kindle, and connected it to KFU 0.96 it said my boot mode was 0x5003.
fastboot commands will not execute. I'm sending them like this:
(Devices list)
[email protected]:~/Android/KR$ ./adb-linux devices
List of devices attached
???????????? no permissions
fastboot:
[email protected]:~/Android/KR$ fastboot getvar product
fastboot: command not found
Someone had a similar problem here- http://forum.xda-developers.com/showthread.php?t=1765546 but I want to see if I should follow that thread or try something else instead, before I go making more changes.
Thanks for reading! Will gladly send pizza to someone who can help

I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?

veeman said:
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
Click to expand...
Click to collapse
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?

Josepho1997 said:
Try uninstalling and reinstalling the drivers. If your in fastboot mode, adb wont work. After reinstalling the drivers, type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If the drivers installed correctly, these commands should work and get you out of fastboot(which it seems your stuck in)
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
drivers installed. command input. no response. Id like to install screenshots, but I'm new user.
hardware driver reads Google ADB interface 4.0.0
c:\KFU\tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
.....nothing?!

wheelzr said:
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Click to expand...
Click to collapse
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.

kinfauns said:
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
Click to expand...
Click to collapse
So, witout popping the cover and screwing with the mobo this thing is bricked?

wheelzr said:
So, witout popping the cover and screwing with the mobo this thing is bricked?
Click to expand...
Click to collapse
</thread>
Just sold the kindle on craigslist for $40 as a bricked device.

wheelzr said:
Just sold the kindle on craigslist for $40 as a bricked device.
Click to expand...
Click to collapse
Oy vey... I'd give you $50 for the "brick" to be used to help others here.

kinfauns said:
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
Click to expand...
Click to collapse
for real, I probably would have paid $50-60 too, it should be an easy fix with a factory cable. (which I already have one of after I bricked my kindle once)
Also, as a side note - Amazon will replace it for $100 "not under warranty" because you bricked it through the tinkering process.

Actually, it turned out better than I could have planned. I told the company whom gifted to me t did not work, they sent a bike ,messenger to exchange it for me! Naturally the first thing I did with the new one was fire up kfu .96 and it worked perfectly this time. Stoked on this hashtaag jelly bean ROM. Hate the keyboard tho. And Google cards are fc'ng.
Love life.
Sent from my Amazon Kindle Fire using xda app-developers app

[Q] Please don't hate me... fastboot "brick" on VM

So, I know not supposed to post questions that are lame, but I can't seem to figure this out. I will state my specs/situation:
I am stuck on the first step of installing FFF on my first Kindle Fire 1st gen.
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
The kindle fire is in fastboot mode (I'm pretty sure, at least).
It is stuck on the stock Kindle fire boot-up logo.
install_Drivers was run successfully after enabling unsigned driver installs.
Run.bat was executed
selected Option 5 first, to install FFF
FFF was downloaded by KFU, the Fire rebooted and then got stuck.
As it rebooted, I had forgotten to automatically have my Fire connect to the Virtual Machine, so VMWare prompted my with what system I wanted the fire connected to. I'm not sure if that delay has something to do with the stall and failure of KFU to install FFF or get out of fastboot.
KFU doesn't recognize the Kindle ("waiting for device" message; ADB: Offline; Boot Status:Unknown).
In my "other devices" on Windows Device Manager I see "Base System Device" and "Unknown Device"
My questions are:
1. How do I go about getting it out of fastboot mode even though KFU can't see the device.
2. What was I doing wrong in the first place?
Before you tell me:
I have read through the Guide
I have read through and searched much of the KFU dev thread
I have searched the forums, without a clear solution.
Thank you very much for your help!!!

escoloader said:
2. What was I doing wrong in the first place?
Click to expand...
Click to collapse
This:
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
Click to expand...
Click to collapse
Use breakdroid instead
Sent from my Amazon Kindle Fire HD using Tapatalk 2

soupmagnet said:
This:
Use breakdroid instead
Click to expand...
Click to collapse
How do I get it back to normal booting first?
Thanks for your help!

escoloader said:
How do I get it back to normal booting first?
Thanks for your help!
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot

Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thank you for the help, but could you please explain how I use that code, step by step if possible?
Thanks a lot
EDIT: I guess I should specify, I do NOT have a fastboot factory cable. Do I need one?

Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.

Thepooch said:
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Click to expand...
Click to collapse
Did the first one, but still says "waiting for device" and nothing is happening. :/ (EDIT: for clarity's sake, nothing happening means its still stuck on the kindle fire white/orange stock boot logo)
btw, thank you for your help.

Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".

soupmagnet said:
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
Click to expand...
Click to collapse
still says "waiting for device" in the terminal.
also, windows still comes up with "usb unrecognized" message at the bottom right of my screen.
What's next?
Thanks for joining to help, soupmagnet

Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.

Thepooch said:
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Click to expand...
Click to collapse
Still doesn't show up. (It also occasionally crashes my mac system when I plug the kindle in now :/ )
If I get a factory cable, will that likely solve this easily?

Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.

Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thepooch said:
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Click to expand...
Click to collapse
Got it! Using Breakdroid, I was able to capture the Kindle as it powered on. I believe my main problem was that there was a significant enough delay in connecting the Kindle via USB to the Windows Virtual Machine, that the ADB couldn't access it in time to capture it. Or whatever.
Solution: I used BreakDroid on my Mac. Turned the kindle off, then back on while Breakdroid was waiting for my device to perform Step 1 on Breakdroid's Kindle Tools. Then it immediately captured the Kindle when I powered it on. Went through the steps on Breakdroid, and it's working with bootloader and recovery
Works great! Have all my stuff back. And...it's rooted
THANKS FOR ALL YOUR HELP, GUYS!
EDIT: Now how do I install Google Play?

[Q] Fastboot is stuck and kindle isn't showing up

So I was working on my kindle iv broken it bootlooped it flashed a rom that just didn't work ect and fixed all of these problems.however recently I went to flash a nightly cm on my kindle and it had no notification bar or action bar.
iv seen It before I used twrp to put my kindle into idme bootmode 4000 fast boot came up like normal after I rebooted.
I used the recovery tool to restore the stock stuff and used fast boot CMD to reboot my kindle from my windows computer.
However it rebooted to fastboot I tryed reboot-boot loader command and same thing hard reset didnt work ether.
I'm at a lose I was trying to reboot it again today and now fastboot commands stopped working as it doesn't show up in adb
So what do I do or want can I try not afraid to mess with anything and I'm pretty good with the cmd adb and fastboot stuff iv googled it and spent a few hours the solutions I found didn't work and it's still broken any help would be cool

axis.fire said:
So I was working on my kindle iv broken it bootlooped it flashed a rom that just didn't work ect and fixed all of these problems but recently I went to flash a nightly cm on my kindle and it had no notification bar or action bar iv seen I before I used twrp to put it in idme bootmode 4000 fast boot came up like normal after I rebooted I used the recovery tool to restore the stock stuff and used fast boot to reboot my kindle from my windows computer but it rebooted to fastboot I feed reboot-boot loader and same thing hard reset don't work ether I'm at a lose I was trying to reboot it again today and now fastboot commands stopped working as it doesn't show up in adb
So what do I do or want can I try not afraid to mess with anything and I'm pretty good with the cmd adb and fastboot stuff iv googled it and spent a few hours the solutions I found didn't work and it's still broken any help would be cool
Click to expand...
Click to collapse
First off, please try to use punctuation when describing your problem. I've had to read this five times just to try and get some comprehension of what you're trying to say. I have no idea where one statement ends and the next one begins.
Second...What device do you have? You posted this in the Kindle Fire 2 forum but you attempted to use a command that only works on the 1st generation Kindle Fires? Do you know the difference between the 1st and 2nd generation devices? Have you read the FAQ posted in the appropriate Q&A forum for your device? If so, what specifically are you trying to accomplish (other than simply unbricking your device)?

soupmagnet said:
First off, please try to use punctuation when describing your problem. I've had to read this five times just to try and get some comprehension of what you're trying to say. I have no idea where one statement ends and the next one begins.
Second...What device do you have? You posted this in the Kindle Fire 2 forum but you attempted to use a command that only works on the 1st generation Kindle Fires? Do you know the difference between the 1st and 2nd generation devices? Have you read the FAQ posted in the appropriate Q&A forum for your device? If so, what specifically are you trying to accomplish (other than simply unbricking your device)?
Click to expand...
Click to collapse
Sorry il work on that. I know the difference between the devices I have a kindle fire 2 and I have reviews the FAQ thread. My device is stuck in fastboot however I'm confident that it will work if I can get it to boot and not go into fast boot. I'm trying to reboot the device normally however the adb commands and fastboot commands are not working and the device isn't listed under ether while it is connected to the computer. It does however show up in my device maniger thank ou for taking the time to review my problem.

You can work on getting your drivers working properly, or you can set up a Linux LiveUSB and install SoupKit. SoupKit will give you the ability to effectively send fastboot commands in the terminal without worrying about properly configured USB device drivers.
On the HD models, performing a hard reset on the device will take them out of fastboot. It may not work on the KF2, but you may want to try that first, just in case.

soupmagnet said:
You can work on getting your drivers working properly, or you can set up a Linux LiveUSB and install SoupKit. SoupKit will give you the ability to effectively send fastboot commands in the terminal without worrying about properly configured USB device drivers.
On the HD models, performing a hard reset on the device will take them out of fastboot. It may not work on the KF2, but you may want to try that first, just in case.
Click to expand...
Click to collapse
I was able to issue the commands fine until my hard reset. It was persistent on going back to fastboot nomatter wht command I issued.
It will not take commands now however I will try the soupkit I'm slightly finisher with Ubuntu and fedora so it shouldn't be hard

axis.fire said:
I was able to issue the commands fine until my hard reset. It was persistent on going back to fastboot nomatter wht command I issued.
It will not take commands now however I will try the soupkit I'm slightly finisher with Ubuntu and fedora so it shouldn't be hard
Click to expand...
Click to collapse
To get out of fastbot mode (says fastboot on the display), you generally only have to enter...
Code:
fastboot -i 0x1949 reboot
If that doesn't work, and you still reboot into fastboot mode, try to change the bootmode to normal...
Code:
fastboot -i 0x1949 oem idme bootmode 1
Also, while in recovery, there should be an option to boot normally, assuming you have a working OS to boot to.
And you need to make damn sure all of your stock partition images are restored before you reboot or your device may get hard-bricked, for good.

[Q] KFHD Boot Logo Problem

Firstly, if there is already a thread about this that I've missed, I'd be appreciative if you'd send me in the right direction to get information.
Anyway, my Kindle Fire HD, rooted CM 10.1, will no longer boot past the orange Kindle Fire Splash screen. I've tried using fastboot commands and all of the button configurations in any and all attempts to get a response from my device, but it remains on that screen with no looping or any kind of change. When plugged in (or turned on while plugged in) it's registered in Device Manager as the usual "Jem-PVT-Prod-04" when drivers aren't installed, and then disappears from the Manager within five seconds. I can't install the ADB drivers because it vanishes, so I cannot communicate with the device from my computer; therefore I cannot fastboot (as far as I can see) and have no possible way to recover it.
Is my last hope a fastboot cable, or is there something that I have missed this whole time? Thanks for any and all help!

Maximus300 said:
Firstly, if there is already a thread about this that I've missed, I'd be appreciative if you'd send me in the right direction to get information.
Anyway, my Kindle Fire HD, rooted CM 10.1, will no longer boot past the orange Kindle Fire Splash screen. I've tried using fastboot commands and all of the button configurations in any and all attempts to get a response from my device, but it remains on that screen with no looping or any kind of change. When plugged in (or turned on while plugged in) it's registered in Device Manager as the usual "Jem-PVT-Prod-04" when drivers aren't installed, and then disappears from the Manager within five seconds. I can't install the ADB drivers because it vanishes, so I cannot communicate with the device from my computer; therefore I cannot fastboot (as far as I can see) and have no possible way to recover it.
Is my last hope a fastboot cable, or is there something that I have missed this whole time? Thanks for any and all help!
Click to expand...
Click to collapse
Thats a kindle fire hd 8.9" model, fastboot cables don't work on them. A easy way to fix this is to boot a ubuntu live cd and install the fastboot command from the repos and run it. Latest ubuntu is 14.04 lts and i haven't checked the package names yet, but if it has the same name as on 13.10 then these instructions should work. Boot a ubuntu live usb/cd and open the settings and look for something like software updates and check off all the download form internet boxes. Hit reload if it asks, and if it asks ignore the first command in the next part of the instructions.
Now open a terminal and run these commands:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
fastboot -i 0x1949 getvar product
Now that it says waiting for device, plug the kindle in while its off and you should be in fastboot mode. From there you can reflash it from windows with kffa or srt, or just do it manually while in ubuntu.

So I used the Linux command to put my Kindle in fastboot mode, but now it says it cannot connect with MTP device, so I still cannot flash any type of recovery. Even though it is in fastboot mode, and the drivers are installed, ADB is still not working on Windows.... and I'm not sure how to do it manually on Linux...

MTP is irrelevant with fastboot, as is adb, you don't use adb commands with fastboot, you use fastboot commands. You can use kffa or SRT to restore it from windows once it is in fastboot, or restore it manually in Linux using SRT's images. You probably will have to use SRT, I have heard a report that kffa's downloads for the images are offline again, though I'm not positive on that.
Sent from my Amazon Tate using Tapatalk

[Q] Bricked during root?

Hey folks! First, thanks for all of your hard work on this! I'm surprised at how active these forums are even with developers moving on to newer tablets - it's really impressive to have such an active community!
My problem:
Kindle won't boot; not recognized by ADB or FastBoot on multiple computers/OS's. Likely bad bootloader but can't push stock bootloader without ADB/FastBoot.
How I got there:
Alright, so, I recently received a Kindle HD 8.9" from a friend and tried to unroot it in Windows. I didn't get very far with multiple attempts and, eventually, got to a place where the adb labeled the device as "offline." After updating the SDK and adb, uninstalling and reinstalling drivers and so on, the Kindle was still listed as "offline." Tried different USB ports and so on, still offline, so I followed the "try a different computer" advice. Fed up and remembering how easy it was to unroot and mod my old Evo 4G in OS X, I decided to boot into OS X.
I quickly came across BreakDroid (KindleWater), which one thread or another suggested would work with the Kindle Fire HD 8.9". I started it up and got further than I had ever gotten before but with errors - the flash at the end of the "Step 1" script worked, but there were permissions error prior.
Stuck in fastboot, I turned off my Kindle and then decided to log-in as root and restart the process, thinking this would resolve any permissions issues, but my Kindle never turned back on. Now my Kindle will not turn on at all (even while holding down volume buttons) and is not recognized by 2 different macs and a windows pc. When issuing "sudo fastboot -i 0x1949 getvar product" I get "ERROR: Unable to create a plug-in (e00002be)" after some time. ADB shows nothing and no device drivers load in Windows.
So, a few questions:
First, Is there anyway to get my Kindle to boot? Looking into it a little, it appears (although is unclear) that BreakDroid is only for the 7". You can see the code attached below - is my phone bricked? I'm going to boot back into Windows and try KFFirstAide and "KFHD System.img Recovery Tool" and, if those don't work, try Ubuntu and SoupKit. I do have a system backup that was made with KFFirstAide. Any thoughts on how to get it up and running again? Although I'm not that fluent in the Windows environment I'm pretty savvy with Linux and OS X.
Second, if it is bricked and I have to send it back to Amazon what risks do I face? Is it likely they'll just send it back fixed and all will be well, or will they keep it and/or sue me for messing with the boot loader? Would I be better off sending it to someone who unbricks and roots Kindles to avoid additional frustration from a gift?
Any thoughts and help are greatly appreciated! Thanks!
P.S. Here is the code BreakDroid ran. I recall "file already exists" and "unable to copy" due to permissions errors but, unfortunately, I killed the terminal before copying the output thinking I could just log-in as root and redo the process (which I did not attempt). The flash at the end of the code, however, was successful (confirmed on Kindle's display).
Code:
/Volumes/BreakDroid/.files/android-sdk/platform-tools/adb kill-server
sleep 5
/Volumes/BreakDroid/.files/android-sdk/platform-tools/adb push /Volumes/BreakDroid/.files/root/fbmode /data/local/fbmode
sleep 5
/Volumes/BreakDroid/.files/android-sdk/platform-tools/adb shell chmod 755 /data/local/fbmode
sleep 2
/Volumes/BreakDroid/.files/android-sdk/platform-tools/adb shell /data/local/fbmode
sleep 5
/Volumes/BreakDroid/.files/android-sdk/platform-tools/adb reboot
sleep 20
/Volumes/BreakDroid/.files/android-sdk/platform-tools/fastboot -i 0x1949 flash bootloader /Volumes/BreakDroid/.files/kindle_files/u-boot.bin
sleep 10
## applescript dialog "Hold the power button until the light goes off" then turn it back on and wait until it is on then continue

Just tried to install an unlocked bootloader from cyanogenmod's jem page (I can't link because I don't have enough posts! - Install_CM_for_jem on the cyanogenmod wiki) but no dice, fastboot just hangs at "waiting for device" on the computer that was able to get the "unable to create a plug-in" error, regardless of USB port, using "sudo ./fastboot -i 0x1949 flash bootloader /Users/USER/Documents/kfhd8-u-boot-prod-8.1.4.bin". Any help or return/warranty advice is appreciated!

Make sure the device is powered off use Ubuntu with soup kit then run the command sudo fastboot -i 0x1949 getvar product then plug in the tablet. That should get you into fastboot.

macman005 said:
Make sure the device is powered off use Ubuntu with soup kit then run the command sudo fastboot -i 0x1949 getvar product then plug in the tablet. That should get you into fastboot.
Click to expand...
Click to collapse
After a lot of effort to get SoupKIt installed (finally got a working install with an i386 version of Ubuntu 12.04, where you'd think that Android development is 64-bit...), I was unable to get fastboot to recognize my Kindle, regardless of which USB controller I used.
Of note, I also wasn't able to use fastboot with sudo, only as the user. Is this because I'm on a live-installation or is SoupKit supposed to be on a 64-bit OS?
Any further suggestions on how to revive this Kindle?

The sudo might not be important when you run the command
fastboot -i 0x1949 getvar product
Do you get a waiting for device?
If so this is when you should plug the tablet in via usb

macman005 said:
The sudo might not be important when you run the command
fastboot -i 0x1949 getvar product
Do you get a waiting for device?
If so this is when you should plug the tablet in via usb
Click to expand...
Click to collapse
I did get "waiting for device" with my Kindle unplugged. I then tried several USB ports, waiting a few minutes at each (~15 minutes), with no luck. :crying: Any thoughts?