yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] soupmagnet:
Thank you for your response and your feedback is greatly appreciated. However, the SoupKit you are referencing to was the alpha release of the installer. There is a new version that you should check out.

In this version I wrote the script differently in regards to how the udev rules were set. For one , I already rewrote the script to check for existing udev rules, check for Kindle Fire specific udev rules, and if necessary, append them instead of overwriting. Also, instead of the udev rules defined in the script itself, they are in a separate file that I cat from.
[Kindle Fire Android Development] Gromlakh:
...oops. ;)
[Kindle Fire Android Development] BriDroid-74:
GREAT JOB!

I was re-rooting my fire and accidentally wiped the SD card, had no backup and no ROM. I could boot into TWRP. Then in a moment of brilliance, I decided to Root my fire again :good:. Now I had no TWRP or ROM. My fire would only boot up to the yellow triangle.

I was able to use Soupkit on my desktop running Linux to Fastboot my fire and reload TWRP. From that point, I could reload a custom ROM and everything is good to go!

Thanks again Soupmagnet :highfive:
[Kindle Fire Android Development] chairshot215:
UDEV Rules

Hey guys sorry if this is a dumb question or already covered but had used the initial release and it was a dream come true as I had been fighting with ADB on Ubuntu 10.4. With the original after running setup had simply entered gksu nautalus and navigated to 51-android.rules and added in My Triumph rules and everything worked perfectly after restarting the rules. Long Story but deleted my Bin folder forgetting about Soupkit because of some issues with Source suddenly starting to download into my home folder and not the Android directory. Anyhow I then installed the updated Soupkit and was unable to access my Triumph like I had previously. I checked 51-android.rules and the rules for my Triumph are still present but for the life of me can not get ADB to recognise it as it had previously before deleting my Bin folder . Any help would Rock big time. Also if it helps it does still pick up my Kindle just fine.
[Kindle Fire Android Development] soupmagnet:
Hmm, weird. Two suggestions:

1) Check the adb_usb.ini to ensure the device ID is entered correctly and on a separate line.

2) Delete the udev rules for your Triumph. In the terminal, enter:

sudo udevadm control --reload-rules

Then go back and add the Triumph udev rules, and enter the previous command to reload the rules again.

If that doesn't work, enter "lsusb" to make sure Linux is still detecting your Triumph. If not, I would say it's a device specific issue.
[Kindle Fire Android Development] chairshot215:
Thanks, going to give it a try now. Was just weird because the original 51-android.rules with the Triumph rules as they had been working are still present. I added them after running the og Soupkit. It just stopped recognising after running the update so probably just need to delete and reload like you said. Ill let you know how it goes, thanks.
[Kindle Fire Android Development] ahja0313:
wow, very nice!

thank you
[Kindle Fire Android Development] Lim Wee Huat:
Thank you...
[Kindle Fire Android Development] al_b:
Thanks for your work

Soupmagnet,

Thank you for your creation! I spent three days hung up in fast-boot (entirely my fault), installed Soupkit in Ubuntu 12.04. Worked as advertised, changed boot modes and all is well. Thanks again :good:
[Kindle Fire Android Development] johnsaldivar:
will this work on Ubuntu Live or do I need to install before I use it
[Kindle Fire Android Development] Gromlakh:
Considering there is a very lengthy section in the OP that talks about how this runs on a live boot from a USB drive, I'm going to say there's a fairly obvious answer to your question.
[Kindle Fire Android Development] Thepooch:
Create a live usb with persistent. You need at least a 4 gig USB flash drive to create a live Linux with persistence to run Soupkit on to solve your problems with drivers and repair the mounting problems with your Kindle Fire.

You install Soupkit onto a live usb that is running ubuntu with persistent. The persistent allows the live usb to save data between reboots. What you need: Preferably Ubuntu 12.04 precise pangolin found here http://releases.ubuntu.com/precise/ use desktop cd image PC (intel X86) Desktop CD, Pendrive Universal USB installer found here http://www.pendrivelinux.com/univers...easy-as-1-2-3/ , a USB flash drive between 4-6 gigs.

Select 12.04 desktop from the dropdown in Universal Usb installer, select your usb by drive letter , select format, drag bar for persistent to 1500 mgs or so, then click create, when finished eject cruiser safely, unplug usb flash drive, shutdown computer, insert usb flash drive, power on computer, it will auto boot at startup on Windows 7 but XP takes more work for instance on my XP machine at first boot splash hit escape for advance startup options, then F9 for boot menu, then scandisk cruiser or whatever your USB is by name, it will then boot ubuntu without installing on your Windows machine.

When booted into Ubuntu: setup your network connection, download Soupkit move it from its containing folder to the desktop, right click select extract here, open folder, double click on the file marked installer, select run in terminal, select option 1 in terminal menu, hit enter for sudo password prompt as there isn`t one, when its finished working it will return you to the main menu, select option 2 it will detect a 32 bit operating system and skip the work for 64 bit then it will launch Soupkit, close all open windows, click the gear icon upper right, select restart, If on windows 7 it will simply restart the Ubuntu system, if on Xp hit Esc. at first computer splash, then select again the cruiser reboot is not near a clean an action on XP sadly.

When booted back back to Ubuntu open a terminal Ctrl+alt+t type soupkit.sh in the terminal now you can use all the features of Soupkit if everything went right and communication has been established with the Kindle.

Soupkit thread http://xdaforums.com/show....php?t=1850038

Edit: a 2 gig flash drive will work but 4 is better.
[Kindle Fire Android Development] slacka-vt:
Thanks Soupmagnet. Your utility helped un-brick my son's KF. Was stuck on "Kindle Fire" boot screen. :highfive:
[Kindle Fire Android Development] myboyblake:
alright. amazing script you wrote! save my KF from death :) Amazing job op!

My prob now is windows is useless for me...whenever i try root or flashing a recovery, just flashing anything it bricks it on the KF logo.

I try flashing a recovery in soupkit and it says

/dev/block/mmcblk0p5: cannot open for write: Permission denied

Similar thing happens if I try to push Superuser.apk to the KF manually. I am using Ubuntu 12.10.

IDK what else to do....any suggestions?

THanks everyone!! :)
[Kindle Fire Android Development] soupmagnet:
Your device isn't rooted apparently. Turn it off and select the option to install recovery. It will say your device isn't connected. Just follow the instructions it gives you and it will install TWRP through fastboot. TWRP has root privileges so you can use that to install su and superuser.apk, though you don't even have to do that if you plan to install a custom ROM.

If you do install a custom ROM, you must remember to wipe data (factory reset) before installing or you'll need a factory cable to fix it.
[Kindle Fire Android Development] Copcheck:
I've never used Linux before and followed all the instructions and created a LiveUSB drive and got it to boot.

Once it boot I downloaded Soupkit, extracted it to the desktop and clicked soupkit.sh and the options were presented.

When I click execute in terminal, nothing happens.

Am I doing something wrong?

I am running lubuntu 13.4

Thanks

Update

I installed ubuntu 11.10 and I can now get to the parts I need. My problem now is that it does not see my device.

I followed the "read me" and did option 1 and option 2 and rebooted. When I reboot, Soupkit is gone even though I saved it, dragged to the desktop and extracted it there and ran soupkit.sh.

My device is offline. I have a factory cable and tried that and a regular cable, still nothing.

Any advice? I'm ready to give up on this thing.

Edit again

I'm going to make another drive with Ubuntu 12.4 and see if that makes any difference.

Am I missing a step with ADB drivers? I did not see that in any write ups, but people keep mentioning to check ADB status in Linux.

Update:

I'm an idiot, I forgot to include persistence.

Same result after I added persistence. Soupkit does not see my device.
[Kindle Fire Android Development] :
you are awesome dude, i love you and thanks
[Kindle Fire Android Development] Unythios:
I'm guessing this doesn't work with Ubuntu 13.04?

It keeps telling me It's already installed yet I have no folder for it in my bin folder. Ofcourse I'm a major Linux newb.......
[Kindle Fire Android Development] Thepooch:
Do not know haven`t tested it, was it 32 or 64 bit?

Edit: yeah, no to much a hassle trying to wing an install because Ubuntu 13.04 doesn`t allow the option to run in a terminal, then when you drag and drop force it it doesn`t push the files to the proper location in fact doesn`t push them at all. Use the PC (Intel x86) desktop CD version form here http://releases.ubuntu.com/precise/ as I described with instructions in post # 64. IMHO 13.04 does not run effectively for the live user and this process.
[Kindle Fire Android Development] cowsquad:
It takes less than ten minutes to get adb to work on Linux . download the SDK then open .bashrc and export your path. Simple as that
[Kindle Fire Android Development] Thepooch:
ADB wasn`t the entire point of the question hence the name of this thread " Soupkit - When you just can't get ADB to connect (and some other things)." Some other things happen to be alot of things if you make use of this utility. As well SDK is pointless bulk on a live usb and really not needed to make this utility work as fantastic as it does;).
[Kindle Fire Android Development] martyxng:
Thanks! Utility works great. I used Ubuntu 12.02 (x86). The 64 bit version didn't work no matter what. (But I am no Linux expert)
[Kindle Fire Android Development] NooBOnTheBlock:
It worked good for me now im stuck on battery charging...21% is enough to boot right? If yes then I am stuck at battery screen....still a victory though cuz befor I couldn't even get it to charge ;)

---------- Post added at 10:11 PM ---------- Previous post was at 09:37 PM ----------

Gotta thank you man you saved me a bunch and I gained knowlegde in working with ubuntu os ;) nice tool by the way
[Kindle Fire Android Development] cejack:
Question.

I see this thread and then the thread here:

http://xdaforums.com/showthread.php?t=2162986

Which *.zip file should I be using for a Kindle Fire original?

I don't see that addressed in the thread though the later thread seems to imply that the ADB function will work for all various forms of Kindle Fire including the original one.

Thx for the software.
[Kindle Fire Android Development] soupmagnet:
I know it's a little confusing, and I'm working to update everything when I get a chance, but you have to look at it as two different tools. Theres an ADB installer that will configure your system to communicate with both first and second generation Kindle Fires, then there is an included utility for each that provides various functions for that particular generation of devices.

If all you need is working ADB or fastboot, either will work, but the

utility

that comes with this one should only be used on the original Kindle Fires.
[Kindle Fire Android Development] vladimirhtg:
Thanks!

Tried 12.04 x64 first but that didn't do it. x86 changed the bootmode first shot. I could'nt grab my device IDs since windows 7 wouldn't recognize my kindle. Now back in normal bootmode.

When trying to install twrp with your soupkit, I get a permissions error like someone else got (I'm not rooted, which is why I'd like twrp). I tried starting the install process with the device off/disconnected, which the kit likes (and gives me the twrp ok message) and then asks if I'd like to boot recovery)....If I try to boot recovery, I bootloop until booting normally. Any tips there? I thought of changing the bootmode to bootloader and then seeing if I could install, but I figured I'd ask first :). This things has been bad enough already in bootmode...

Thanks for the work soupmagnet! The post you wrote on the kfu driver issues was also very good.
[Kindle Fire Android Development] soupmagnet:
I've been meaning to update, but I've been busy with other projects lately. This script is very old and was my first attempt at shell scripting, so there is some room for improvement.

The problem with the 64-bit versions is, fastboot requires 32-bit libraries to be installed and quite often the command used to install them doesn't work because it is no longer supported by Ubuntu.

Since you do have the 32-bit(x86) version, you should have no problem switching back and forth between bootmodes. Since your device isn't rooted, the option to install recovery will fail when booted normally, even if the script says otherwise (that's an error on my part). Just switch back to fastboot and install TWRP from there.
[Kindle Fire Android Development] vladimirhtg:
Yep, I gotcha on the libraries. Just had to try since it's what I had around :) No worries on the old script, honestly I'm shocked people still do work for these things (.....not my kindle).

So I'll try pushing twrp in fastboot and profit from there.
[Kindle Fire Android Development] vladimirhtg:
I forgot to post again and say that this thing worked beautifully from x86 12.04 :) thanks for the work!

Sent from my Etch A Sketch
[Kindle Fire Android Development] xMatter:
Text In Terminal Keeps Going

I am using uBuntu 12.04.3 (duel boot on windows 7 laptop) and USB 2.0. My KF is stuck at Kindle Fire screen and that is why I am trying SoupKit. The ADB states that it is online, but no matter what selection I make with SoupKit, the text in the terminal just keeps running. To fast to really make out, but it appears it keeps repeating. Is this normal???

Background: had TWRP install with CM7 and wanted to go back to stock. I loaded the update.zip and it would not work and had an error of could not find /system/bin/ something.

Any thoughts?
[Kindle Fire Android Development] soupmagnet:
Yep. It looks like you tried to flash the update.zip without a factory reset. That error means you don't have access to a working shell, and you'll need a factory cable to access fastboot so you can then access custom recovery.
[Kindle Fire Android Development] xMatter:
Thank You!

I was looking for the exact cause of this error. I have ordered the cable, since my solder skills are not the greatest. I appreciate your knowledge and time!
[Kindle Fire Android Development] jaxwithanx:
I only have a 2GB stick laying around currently....will go grab a larger one if needed but was wondering if anyone knew of a distro that would work with this.

I know Damn Small Linux is debian-based but not sure if too much has been pared down to work...anyone tried?
[Kindle Fire Android Development] soupmagnet:
As long as it has apt-get installed, you shouldn't have any problems with it. If you do, PM me and I'll send you something else.
[Kindle Fire Android Development] jaxwithanx:
Thanks for the quick reply. Did a quick search and you have to fool around to enable apt-get (http://www.damnsmalllinux.org/wiki/enabling_apt.html). Seems a little dicey to bother trying.
[Kindle Fire Android Development] jaxwithanx:
So finally got Mint installed on a 2GB stick after about 10 failed installed of other distros (mainly Ubuntu, just could not get it to work correctly). Finally troubleshot a display issue, DL'and installed Soupkit and of course it won't recognize device. Spent close to 2 hours trying to run Firekit and short it out within Soupkit and no dice after trying staple, paperclip, unwound key ring, etc.... Never could get it going for even one phase. Any remaining options?
[Kindle Fire Android Development] soupmagnet:
My suggestion is to use a safety pin (or pair of sharp pointed tweezers). Use the pointed end to hold the tool in place on the copper pad to prevent it from slipping, then just squeeze the other end to the metal frame to make the connection. As far as everything else, it's all about timing...
[Kindle Fire Android Development] wfg97079:
I picked up a kindle fire g1. WHen plugged in it boots up to a yellow triangle with a flame on it, then reboots after about 5 seconds. If I tap the power button, it will boot to TWRP 2.0.0

System comes up as unrecognized on all of the 4 windows servers I have tried (windows vista, windows 7, windows 8) after installing the KFU.

I have a factory cable and soupkit installed on a linux live usb stick.

Linux doesnt show the device in lsusb at all

When I plug the device in, for both the factory and standard cable, soupkit cannot see the device and when I try to send command it hangs at waiting for device

I see messages like this in dmesg:

[ 440.436044] usb 3-5: device descriptor read/64, error -62

[ 440.724080] usb 3-5: device descriptor read/64, error -62

[ 441.004091] usb 3-5: new full-speed USB device number 13 using ohci_hcd

[ 441.188055] usb 3-5: device descriptor read/64, error -62

[ 441.476060] usb 3-5: device descriptor read/64, error -62

[ 441.756075] usb 3-5: new full-speed USB device number 14 using ohci_hcd

[ 442.164064] usb 3-5: device not accepting address 14, error -62

[ 442.340066] usb 3-5: new full-speed USB device number 15 using ohci_hcd

[ 442.748061] usb 3-5: device not accepting address 15, error -62

[ 442.749581] hub 3-0:1.0: unable to enumerate USB device on port 5

Any advice?
[Kindle Fire Android Development] soupmagnet:
Seems like you have a dead battery. First do a hard shutdown with the device unplugged. Then plug it into a power source and immediately hold the power button to perform a hard shutdown again. If you can get the device to shut down and stay powered off while plugged in, leave it alone for a few hours and start it up again. Otherwise you might be looking at replacing the battery.
[Kindle Fire Android Development] wfg97079:
interesting

In TWRP the battery shows at about 60% now and it will stay on for a very long time in TWRP as this battery indicator goes down. I am also able to get it to go up by leaving it plugged in.

Is that not accurate?
[Kindle Fire Android Development] wfg97079:
99%

Left it powered off and charging, battery now shows at 99% in TWRP but exhibiting the same boot behavior
[Kindle Fire Android Development] soupmagnet:
Well, here's the deal...

That particular version of FireFireFire stays in fastboot for 10 seconds, then proceeds to load the kernel and such. If you're certain it reboots every 5 seconds, then you should boot into recovery and have SoupKit install FireFireFire 1.4a. Otherwise, it may be as simple as not having a working ROM installed, or installed correctly.
[Kindle Fire Android Development] wfg97079:
ahh

Just tried it, its closer to 15 seconds than 5.

When you say I should boot into recover, do you mean TWRP? I have done that and soupkit doesnt recognize the system as I mentioned earlier.
[Kindle Fire Android Development] soupmagnet:
Yes, TRWP is recovery. Open your terminal in Linux and enter 'lsusb'. Do you see Lab 126 listed?
[Kindle Fire Android Development] wfg97079:
thanks for all your help

Please see my original post:

Linux doesnt show the device in lsusb at all

When I plug the device in, for both the factory and standard cable, soupkit cannot see the device and when I try to send command it hangs at waiting for device

I see messages like this in dmesg:

[ 440.436044] usb 3-5: device descriptor read/64, error -62

[ 440.724080] usb 3-5: device descriptor read/64, error -62

[ 441.004091] usb 3-5: new full-speed USB device number 13 using ohci_hcd

[ 441.188055] usb 3-5: device descriptor read/64, error -62

[ 441.476060] usb 3-5: device descriptor read/64, error -62

[ 441.756075] usb 3-5: new full-speed USB device number 14 using ohci_hcd

[ 442.164064] usb 3-5: device not accepting address 14, error -62

[ 442.340066] usb 3-5: new full-speed USB device number 15 using ohci_hcd

[ 442.748061] usb 3-5: device not accepting address 15, error -62

[ 442.749581] hub 3-0:1.0: unable to enumerate USB device on port 5
[Kindle Fire Android Development] soupmagnet:
A couple of things come to mind, like a loose USB port on the device or using a USB 3.0 port on the PC. But if you're certain you're not using a USB 3.0 port, there is one thing you can do to test out the device's port. Open the terminal and enter the following:

while true; do lsusb | grep 'Lab126'; [[ $? -eq 0 ]] && break; done

While that command runs, and the device is booted into custom recovery, plug the device in and finagle the plug a bit to see if a connection can be made. I would suggest pulling up firmly on the plug for a couple seconds then pushing down for a couple seconds. Once detected, Linux will show the output and break the loop. Then you'll know what you're dealing with. Just remember to end the script (ctrl+c) when you're done or it will continue to loop indefinitely.

Bad USB ports occur quite often on the original Kindle Fires so I'm betting that's part of the problem. Apart from that, the only thing I could suggest is use a different LiveUSB (data corruption is not too uncommon with some flash drives running a LiveUSB).
[Kindle Fire Android Development] wfg97079:
which cable

Should I use a regular cable or factory cable to test this?

Does that
[Kindle Fire Android Development] soupmagnet:
Just a standard USB cable is all you need
[Kindle Fire Android Development] wfg97079:
no luck

I have tried playing with the connecttion. Is this common that the system give that "unable to enumerate USB device" error when the port on the kindle is bad?

Also, anything I can/should try with teh factory cable?
[Kindle Fire Android Development] Lewiswatson99:
Hello what should I do? My soupkit utility Is saying 'waiting for device' I have rebooted it several times to like it said. Also it says device offline. Can someone help me?!? Thanks
[Kindle Fire Android Development] darkmetal:
Thank you Soupmagnet for this awesome tool it has saved so much when trying to install TWRP with windows which my kindle fire gets stuck on the logo. Thanks to your awesome tool i can changed to normal boot, so i have perfectly working kindle fire!

I have tried to install TWRP with Soupkit and i keep getting a permission error. I did factory reset prior to trying to install TWRP, so i can start fresh.

Any ideas?
[Kindle Fire Android Development] A_youu:
I was trying to root my kindle fire 1st generation and some how it got unplugged or something went wrong during Installing permanent Root with Superuser. And now my kindle fire is stuck on "Kindle Fire" logo with "orange color" fire and my computer is not detecting it any more.

Is there any steps by which I can bring my kindle fire back to life.

TIA
[Kindle Fire Android Development] Thepooch:
Depending on what stage you were in the process might be best to start by getting a factory cable from here http://xdaforums.com/showthread.php?t=1392693 . Try holding the power button down for a couple minutes and see what you get when you power it back on. Very good chance you are only stuck in fastboot. That is a driver related issue.
[Kindle Fire Android Development] A_youu:
It stuck on Kindle fire screen with no animation (fire is in orange color)..I am sure it never got rooted, TWRP nothing on it. :'(
[Kindle Fire Android Development] Thepooch:
Your stuck in fastboot is all.