SoupKit (again)...When you're fed up with trying to get ADB to connect in Windows

Search This thread

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,990
2,587
Austin, TX
Google Pixel 6
The SoupKit

soupkit.jpg


What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.


How does it work?


The SoupKit ADB Installer --- FOR ALL KINDLE FIRES

This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.



What you need:

First, you need Linux. Don't worry, it's not as bad as you may think.

Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).

Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.

I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).

You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.


If you're using a LiveUSB, there is no root/sudo password, just hit enter.


Do not use a USB 3.0 port


Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.

Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.

SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.



To install:

Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.




Credits:

Don't worry. I didn't forget about you guys. I'll finish this when I have time. In the meantime, you know who you are, and thank you.




Is that all?

NOPE. What SoupKit would be complete without a little something to go with it?
SEE POST #2

 
Last edited:

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,990
2,587
Austin, TX
Google Pixel 6
Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.


ROOT PLUS for 2nd Generation Kindle Fires


2013_04_23.jpg


That's right. This works for ALL 2nd generation Kindle Fires.


What does it do?

The screenshot above should answer that question pretty quickly.


What do you need to know?

Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.


Make sure you have ADB enabled under “Security” in the settings.


Anything else?

At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.




What's next?


I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.



Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.


Credits:

* Bin4ry - of course, for providing the root exploit
* Dees_Troy - for Team Win Recovery
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand

Downloads:

SoupKit - http://d-h.st/PbX

RootPlus for all Kindle Fires - http://d-h.st/jOe
 
Last edited:

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,990
2,587
Austin, TX
Google Pixel 6
Changelog:

04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.

03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images

03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error

03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script

03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install

02-23-2013 - Initial release
 
Last edited:
  • Like
Reactions: mindmajick

Wilkinsss

Member
Dec 26, 2012
20
2
I actually wish I needed this because god damn this is a sexy piece of kit.
 
Last edited:

2strokenut

Senior Member
Sep 4, 2011
121
14
I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"

It also gives me command not found when I try to open soupkit.sh


thanks
 
  • Like
Reactions: soupmagnet

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,990
2,587
Austin, TX
Google Pixel 6
I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"

It also gives me command not found when I try to open soupkit.sh


thanks
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:

Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus

Then you should be able to start it by entering "rootplus" in the terminal with no problem.

Sorry for the inconvenience.


[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?
 
Last edited:
  • Like
Reactions: 2strokenut

2strokenut

Senior Member
Sep 4, 2011
121
14
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:

Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus

Then you should be able to start it by entering "rootplus" in the terminal with no problem.

Sorry for the inconvenience.


[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?

That worked like a charm! Thanks for all you do!

---------- Post added at 02:35 PM ---------- Previous post was at 02:11 PM ----------

I hate to be such a noob, but, I got the thing rooted and now trying to install the bootloader and TWRP, this is as far as I have gotten. Hasn't done anything in about 10 minutes. I've toggled ADB.







Verifying MD5 Checksum...
blaze-stack.img: OK
Checksum matched
Installing stack...
95 KB/s (4096 bytes in 0.041s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
Rebooting...
< waiting for device >

---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------

I exited the terminal and re-ran option 6, this is what it gives me now:


blaze-stack.img: OK
Checksum matched
Installing stack...
93 KB/s (4096 bytes in 0.042s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
failed on '/system/etc/install-recovery.sh' - No such file or directory
Rebooting...
< waiting for device >
 

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,990
2,587
Austin, TX
Google Pixel 6
There may be something off with the timing. In original testing on my KFHD 8.9, that was caused from the script entering the command to reboot too fast. I had the script pause for a second or two before rebooting which seemed to help (or I thought I did). I'll look into it a little further to see if I can make it work better. The error you get on the second time you run the script is because the first time you ran it, that file was renamed so it wouldn't exist the second time around.

[Edit:] Just hold the power button to shut down and then reboot while the script is sitting at "waiting for device"
 
Last edited:

empoy78th

Member
Dec 17, 2008
43
7
Hi Soup,

I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.

I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!

[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.

[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.
 
Last edited:

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,990
2,587
Austin, TX
Google Pixel 6
Hi Soup,

I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.

I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!

[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.

[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.
 
  • Like
Reactions: blively2

empoy78th

Member
Dec 17, 2008
43
7
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.

Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.

I will gladly test your new version. Thanks again!

---------- Post added at 11:39 AM ---------- Previous post was at 11:22 AM ----------

Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.

I will gladly test your new version. Thanks again!

Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!
 

soupmagnet

Retired Forum Moderator
Jan 7, 2012
3,990
2,587
Austin, TX
Google Pixel 6
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!
Assuming I understand you correctly,

I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.
 

empoy78th

Member
Dec 17, 2008
43
7

empoy78th

Member
Dec 17, 2008
43
7
In rootplus, options 1 and 5 worked for me. However, on option 6, I stay at <waiting for device>. Done it twice and also held the power button to no avail.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.


    ROOT PLUS for 2nd Generation Kindle Fires


    2013_04_23.jpg


    That's right. This works for ALL 2nd generation Kindle Fires.


    What does it do?

    The screenshot above should answer that question pretty quickly.


    What do you need to know?

    Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.


    Make sure you have ADB enabled under “Security” in the settings.


    Anything else?

    At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.




    What's next?


    I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.



    Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.


    Credits:

    * Bin4ry - of course, for providing the root exploit
    * Dees_Troy - for Team Win Recovery
    * prokennexusa and his team - for testing this out on all of the second generation devices
    * Thepooch - for extensive testing and always being there to lend a hand

    Downloads:

    SoupKit - http://d-h.st/PbX

    RootPlus for all Kindle Fires - http://d-h.st/jOe
    4
    The SoupKit

    soupkit.jpg


    What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.


    How does it work?


    The SoupKit ADB Installer --- FOR ALL KINDLE FIRES

    This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.



    What you need:

    First, you need Linux. Don't worry, it's not as bad as you may think.

    Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).

    Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.

    I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).

    You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.


    If you're using a LiveUSB, there is no root/sudo password, just hit enter.


    Do not use a USB 3.0 port


    Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.

    Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.

    SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.



    To install:

    Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.




    Credits:

    Don't worry. I didn't forget about you guys. I'll finish this when I have time. In the meantime, you know who you are, and thank you.




    Is that all?

    NOPE. What SoupKit would be complete without a little something to go with it?
    SEE POST #2

    3
    03-19-2013 - Update + bugfix (RootPlus)
    * Fixed issue with 2nd bootloader install - everything works as it should now
    * Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images

    If you downloaded yesterday's update, please install this one. There was a bug preventing the 2nd bootloader install. It is fixed now.
    Sorry for the inconvenience.
    3
    03-18-2013 - Update: (RootPlus)
    * Changed how 2nd bootloader is installed for compatibility with the KF2
    * Added ability to update custom recovery. No need to update the script every time a new recovery is released.
    * Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
    * More intuitive restore of saved partition images - will hopefully prevent any chance of user error
    2
    Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install