Database Develop

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

The SoupKit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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

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
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

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

I actually wish I needed this because god damn this is a sexy piece of kit.

Thanks soup
Sent from my Amazon Kindle Fire2 using xda app-developers app

Awesome. So glad to see the kf1 devs working for us over here!
I'll probably never need this, but there are MANY who will find this useful.
Thanks soupmagnet!
--
Sent from my Kindle Fire 2, CM 10.1

Wilkinsss said:
this is a sexy piece of kit.
Click to expand...
Click to collapse
Oh, I see what you did there...

soupmagnet said:
Oh, I see what you did there...
Click to expand...
Click to collapse
Well I don't need it I have adb and fastboot running fine on linux already but I still downloaded it anyways, just because I can.

Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install

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

2strokenut said:
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
Click to expand...
Click to collapse
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?

soupmagnet said:
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?
Click to expand...
Click to collapse
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 >

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"

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.

empoy78th said:
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.
Click to expand...
Click to collapse
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.

soupmagnet said:
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.
Click to expand...
Click to collapse
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 ----------
empoy78th said:
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!
Click to expand...
Click to collapse
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!

empoy78th said:
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!
Click to expand...
Click to collapse
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.

3-16-2013: Fixed issue with permissions on the rootplus script

soupmagnet said:
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.
Click to expand...
Click to collapse
You understood it. Good to know. Thanks!
soupmagnet said:
3-16-2013: Fixed issue with permissions on the rootplus script
Click to expand...
Click to collapse
Do I download both soupkit and rootplus for updates? Sorry for the noob question.

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.

[ADB/FB/APX Driver] Universal Naked Driver 0.73

Universal Naked Driver 0.73
** Nvidia Shield ADB added (ADB & Fastboot Only)
** Will update with APX asap
Universal Naked Driver 0.72
** HTC One Added (HTC phones are pretty much future proof with my driver)
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 5B9EA9C73066E8F655D14BBA8318C176
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!

Thank you very much! I just used your drivers and successfully unlocked my bootloader on my Nvidia Shield!

jadengore said:
Thank you very much! I just used your drivers and successfully unlocked my bootloader on my Nvidia Shield!
Click to expand...
Click to collapse
You are welcome, glad to know it making things easier.
I will make an auto root batch job once a recovery is made for the device. Shouldn't be too long...

1wayjonny said:
You are welcome, glad to know it making things easier.
I will make an auto root batch job once a recovery is made for the device. Shouldn't be too long...
Click to expand...
Click to collapse
I used to have one (TWRP) but because touch will be much harder (or impossible) on this device, TWRP isn't a viable recovery for SHIELD. Instead, it looks like we'll need to use CWM, the dpad, and the A and B buttons.

agrabren said:
I used to have one (TWRP) but because touch will be much harder (or impossible) on this device, TWRP isn't a viable recovery for SHIELD. Instead, it looks like we'll need to use CWM, the dpad, and the A and B buttons.
Click to expand...
Click to collapse
What's wrong with the touchscreen on the device? Or did you not know it had a multitouch screen? (I can't imagine a modern Android implementation without one, ick)

AndrewNeo said:
What's wrong with the touchscreen on the device? Or did you not know it had a multitouch screen? (I can't imagine a modern Android implementation without one, ick)
Click to expand...
Click to collapse
Nothing is wrong with the touchscreen, but its awkward to use when you have the controller attached to the screen. I'm very scared about the modding community for this device. It looks like the streaming might be broken by custom roms. That being said, I really want to root and put a custom rom on mine. We'll have to see how popular it gets here in the community.

PR0XIDIAN said:
Nothing is wrong with the touchscreen, but its awkward to use when you have the controller attached to the screen. I'm very scared about the modding community for this device. It looks like the streaming might be broken by custom roms. That being said, I really want to root and put a custom rom on mine. We'll have to see how popular it gets here in the community.
Click to expand...
Click to collapse
The issue with the touchscreen is the driver. While it runs great in Android, it doesn't work in recovery, making a touch-based recovery a nightmare. Believe me, I already tried for a few days. I'm sure with enough time, I could get it working, but I didn't want to invest that much time with all the other things on my plate at the moment. I just don't expect recovery to come out this week with touch.

I made a very high quality tutorial (video) on how to do this! Thanks @1wayjonny!
http://www.youtube.com/watch?v=--6OlA4agPo
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Fix Fastboot issues on Windows 8: http://www.youtube.com/watch?v=XSisjVwcPbE

wwjoshdew said:
I made a very high quality tutorial (video) on how to do this! Thanks @1wayjonny!
http://www.youtube.com/watch?v=--6OlA4agPo
Click to expand...
Click to collapse
Thanks for the video, I was testing something for Nvidia today and did 10 re-install without the SSD RAID 0 i have and it was killing me.
Once you have SSD you cant go back and yes daughters are LOUD! I have one ... =)
I will probably post the video in the OP of all my UNDriver threads.

1wayjonny said:
Thanks for the video, I was testing something for Nvidia today and did 10 re-install without the SSD RAID 0 i have and it was killing me.
Once you have SSD you cant go back and yes daughters are LOUD! I have one ... =)
I will probably post the video in the OP of all my UNDriver threads.
Click to expand...
Click to collapse
haha. She's a trip though. Thanks a lot dude, you don't see to many "screen captures" that show the computer rebooting and everything! lol

Ok I'm clearly doing something wrong. I need to reinstall the fastboot driver. I had it working properly before but need to install them on a different computer.
I plug the shield in and Windows auto installs a driver. The device is identified as the SHIELD but it's an adb driver (but doesn't allow me to send fastboot commands). When I try to update the driver it says it is up to date. If I uninstall that adb driver that gets auto installed by Windows and try to navigate to the universal driver folder and click one of the inf files in there windows says it isn't a compatible and to make sure it is for an x64 system. If I browse to the i386 folder nothing comes up. I'm really getting irritated.
Is there just a normal fastboot driver somewhere that isn't a universal driver? Typically if I have a correct driver and choose "Have Disk" and browse to my driver it will install, but not this time.
I am not sure if I have a previous driver conflicting or something. I don't have like 4 Android devices I used to have any more so uninstalling those drivers isn't possible. I just don't understand why Windows can be so difficult on something so trivial.
I'm using Windows 7.

Evo_Shift said:
Ok I'm clearly doing something wrong. I need to reinstall the fastboot driver. I had it working properly before but need to install them on a different computer.
I plug the shield in and Windows auto installs a driver. The device is identified as the SHIELD but it's an adb driver (but doesn't allow me to send fastboot commands). When I try to update the driver it says it is up to date. If I uninstall that adb driver that gets auto installed by Windows and try to navigate to the universal driver folder and click one of the inf files in there windows says it isn't a compatible and to make sure it is for an x64 system. If I browse to the i386 folder nothing comes up. I'm really getting irritated.
Is there just a normal fastboot driver somewhere that isn't a universal driver? Typically if I have a correct driver and choose "Have Disk" and browse to my driver it will install, but not this time.
I am not sure if I have a previous driver conflicting or something. I don't have like 4 Android devices I used to have any more so uninstalling those drivers isn't possible. I just don't understand why Windows can be so difficult on something so trivial.
I'm using Windows 7.
Click to expand...
Click to collapse
I had the SAME PROBLEM! I uninstalled the drivers, and chose from the list manually! Eventually you choose have disk and there is a long list of things. Find NVIDIA Fastboot from that list.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I swear I tried that. I think I may have unplugged my device and plugged it back in after uninstalling because I thought I couldn't find it in the device manager after I uninstalled it. I bet it was listed with a yellow exclamation point somewhere in there but I just skipped over it or something.
I wish my work computer didn't lock me out of everything so I didn't have to wait to get home to try it again...
And off topic...I wish I got those kind of speeds in your sig on Sprint. My LTE (Galaxy S3) is hardly faster than 3G in Minneapolis. Though it isn't officially launched yet.

Evo_Shift said:
I swear I tried that. I think I may have unplugged my device and plugged it back in after uninstalling because I thought I couldn't find it in the device manager after I uninstalled it. I bet it was listed with a yellow exclamation point somewhere in there but I just skipped over it or something.
I wish my work computer didn't lock me out of everything so I didn't have to wait to get home to try it again...
And off topic...I wish I got those kind of speeds in your sig on Sprint. My LTE (Galaxy S3) is hardly faster than 3G in Minneapolis. Though it isn't officially launched yet.
Click to expand...
Click to collapse
HERE YOU GO @Evo_Shift! (And others having trouble running fastboot commands on their NVIDIA Shield!)
http://www.youtube.com/watch?v=XSisjVwcPbE
@1wayjonny, (and @agrabren) what do you think?

wwjoshdew said:
HERE YOU GO @Evo_Shift! (And others having trouble running fastboot commands on their NVIDIA Shield!)
http://www.youtube.com/watch?v=XSisjVwcPbE
@1wayjonny, (and @agrabren) what do you think?
Click to expand...
Click to collapse
I have seen this many times if the driver is correct and user is having issues its usually because of the following.
A) Cable is not good, try changing a few cable and all should be well. I have even seen OEM cables give issues with fastboot for some reason on multiple devices.
B) User is trying to use a USB 3.0 port, you can replace the microsoft stack with the intel stack allowing for communication over USB 3.0 - Some other USB 3.0 chipset may have issues as well such as Astek etc.
Its important to remember that not all cables are pinned out the same. For example the Xbox 360 FREE ethernet cable only was 100mbps because they choose to save the money by only using 4 of the 8 available wires to reduce cost.
** UPDATE **
After watching the video it seems like you are forcing the driver which is OK. The driver 0.73 will pick up the shield in adb or fastboot automatically.
If its not the devices is not registering to the computer correct and I would check the cable and avoid USB 3.0 port until you work this out.
Was this a USB 3.0 port? If no go right for the cable and try 3-5 different cables.

I finally got it. I am pretty sure it is because of incorrect adb drivers getting auto installed on me when I plugged in the Shield. I wish you could force Windows not to autoinstall drivers when you plug something in and instead always choose your own location. Once I deleted enough of the incorrect drivers and installed the correct drivers to the SHield again it seems to work.

1wayjonny said:
I have seen this many times if the driver is correct and user is having issues its usually because of the following.
A) Cable is not good, try changing a few cable and all should be well. I have even seen OEM cables give issues with fastboot for some reason on multiple devices.
B) User is trying to use a USB 3.0 port, you can replace the microsoft stack with the intel stack allowing for communication over USB 3.0 - Some other USB 3.0 chipset may have issues as well such as Astek etc.
Its important to remember that not all cables are pinned out the same. For example the Xbox 360 FREE ethernet cable only was 100mbps because they choose to save the money by only using 4 of the 8 available wires to reduce cost.
** UPDATE **
After watching the video it seems like you are forcing the driver which is OK. The driver 0.73 will pick up the shield in adb or fastboot automatically.
If its not the devices is not registering to the computer correct and I would check the cable and avoid USB 3.0 port until you work this out.
Was this a USB 3.0 port? If no go right for the cable and try 3-5 different cables.
Click to expand...
Click to collapse
Nope. A USB 2.0 port. That first video that I made (That you said "I will probably post the video in the OP of all my UNDriver threads."), did it correctly. But for some reason, it would work JUST FINE in ADB mode, but NOT in fastboot. I couldn't get "fastboot oem unlock" to work for the life of me, until forcing it to install after choosing "have disk". After that, it worked fine. Just showing that "manual" method for people that have their Shield working find while in android, but not in fastboot. I'm not saying anyone sole person is responsible for it not working, just showing a manual way around it.

hmm...
I have only "Nvidia Shield" not Nvida Shield ADB in my devices Manager - adb is enabled
Code:
adb devies
List of devices attached
(none)

wwjoshdew said:
Nope. A USB 2.0 port. That first video that I made (That you said "I will probably post the video in the OP of all my UNDriver threads."), did it correctly. But for some reason, it would work JUST FINE in ADB mode, but NOT in fastboot. I couldn't get "fastboot oem unlock" to work for the life of me, until forcing it to install after choosing "have disk". After that, it worked fine. Just showing that "manual" method for people that have their Shield working find while in android, but not in fastboot. I'm not saying anyone sole person is responsible for it not working, just showing a manual way around it.
Click to expand...
Click to collapse
Had this issues so I installed the "manual" way and still commands wont work in fastboot
Edit: followed the video as opposed to the sceenshots above. Good to go now.

1wayjonny said:
Universal Naked Driver 0.73
** Nvidia Shield ADB added (ADB & Fastboot Only)
** Will update with APX asap
Click to expand...
Click to collapse
Is APX mode available on NVIDIA Shield? I've used APX mode before on my Notion Ink Adam (Tegra 2), but I have read that the OUYA (Tegra 3) has APX mode encrypted or something so you would have to know the key to use it.
Would be nice to have APX mode on the Shield, but probably not necessary.
~Troop

Amazon Fire 7 (2015) 5.1.1 Stuck in Bootloop with No Recovery. Help ):

Hi all,
This is my first post here as I've been using XDA for years without issue, following other threads and seeing the community thrive. But i've gone and got myself stuck.
I recently got the 2015 Amazon Fire 7 and upon tuning it on, it updated to 5.1.1 after this I quickly saw how awful Fire OS is. I rooted (Thanks to RootJunky's Supertool) Installed GAPPS and Nova launcher, before I realised it's potential was wasted with the Fire OS.
After this I used another RootJunky tutorial to use Flashfire and install SlimLP with GAPPS.
This was successful. After this, I moved onto to wanting to install CM12.1. I found an Unofficial build with GAPPS on XDA and many people confirmed it to be working. I installed with FlashFire as I had with Slim, but after 90 minutes it was still trying to install. Then, before I knew it the battery died.
Now, I have the CM boot animation, but nothing loads. I have no recovery because 5.1.1 doesn't allow for it, so i'm stuck with the CM boot animation and no recovery. I've tried to sideload via command prompt, but my computer doesn't register it as an Android device, just an MTP USB Device, and even if it did register it properly, I don't have a recovery to allow me to install via ADB.
My question is; Does anyone know how to install anything without Recovery, ADB or a functioning device? This has been the hardest device I've ever tried to root, and now I'm stuck.
Thanks in advance guys

5.1.1 does allow recovery, it just doesn't have the ==>Booting Recovery... printed on the screen anymore. Hold vol up and power, release power when logo is seen, and sideload.

glitch3yf0x said:
5.1.1 does allow recovery, it just doesn't have the ==>Booting Recovery... printed on the screen anymore. Hold vol up and power, release power when logo is seen, and sideload.
Click to expand...
Click to collapse
Thank you very much for your quick reply. I've tried that and it shows ==> FACTORY apk Mode, then goes straight back to the Cyanogen boot animation. Even after the Factory APK Mode comes up, the device still shows as an MTP USB Device. I'm looking for the drivers for the MTP Device at the moment, but I still have the sideloading issues.
Command prompt shows; 'adb' is not recognized as internal or external command, operable program or batch file, when trying to sideload.
It's clear there's something very obvious I'm missing and I'm sorry for my ignorance.

DizzyJK said:
Thank you very much for your quick reply. I've tried that and it shows ==> FACTORY apk Mode, then goes straight back to the Cyanogen boot animation. Even after the Factory APK Mode comes up, the device still shows as an MTP USB Device. I'm looking for the drivers for the MTP Device at the moment, but I still have the sideloading issues.
Command prompt shows; 'adb' is not recognized as internal or external command, operable program or batch file, when trying to sideload.
It's clear there's something very obvious I'm missing and I'm sorry for my ignorance.
Click to expand...
Click to collapse
You need to change into the directory of the platform-tools folder of android SDK to run adb. Do this with the cd command. As for booting into recovery, use the other volume button... (Down)

i cannot get to recovery using the volumeup and power it gets stuck with amazon logo , rootjunky says there is some issue in 5.1.1 after using flashfire to get in to recovery

glitch3yf0x said:
You need to change into the directory of the platform-tools folder of android SDK to run adb. Do this with the cd command. As for booting into recovery, use the other volume button... (Down)
Click to expand...
Click to collapse
Sorry to sound stupid, but could you explain how I would do it? I've tried to sort the SDK before and just either got it completely wrong (most likely) or just not understood what it is I'm meant to be doing.
Volume Down leaves me hanging at the 'Amazon' start up screen. I'm assuming this is the recovery mode without the options? So from here, sideloading should be completely possible with a fixed ADB command?

can someone please help i am in the same boat, if i hold the vol-up and power get stuck at amazon logo instead of recovery and vol-down and power takes me to fast boot mode. can some one let us know how to fix this issue?
thanks in advance

See this video and make sure to push the correct button.
https://www.youtube.com/watch?v=RQLoH-ahjy4

fastcar22 said:
can someone please help i am in the same boat, if i hold the vol-up and power get stuck at amazon logo instead of recovery and vol-down and power takes me to fast boot mode. can some one let us know how to fix this issue?
thanks in advance
Click to expand...
Click to collapse
I believe the confusion is that it should be "Vol-Down(Left button) + Power". This will put the fire device into restore mode.
Make sure your using the correct 5.11 stock rom restore file.
Once you select, "apply update from adb". It will start to communicate with your machine and ask you to side load the restore rom. Do the deed "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin".
Also if you want to run adb from any directory in windows. There's 2 methods.
#1 Temporary session method. In the command prompt. Enter the path to your adb directory, "path=c:\adb", hit enter and your good to go.
#2 Permanent method. Add the path to your environment variables.
Windows 10:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Edit environment variable > (Select New) > (Enter the path to your adb directory "c:\adb").
Un-updated Win10 or Windows 7:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Goto the end of the long line of paths and Enter the path to your adb directory ";c:\adb".

thekrakah said:
I believe the confusion is that it should be "Vol-Down(Left button) + Power". This will put the fire device into restore mode.
Make sure your using the correct 5.11 stock rom restore file.
Once you select, "apply update from adb". It will start to communicate with your machine and ask you to side load the restore rom. Do the deed "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin".
Also if you want to run adb from any directory in windows. There's 2 methods.
#1 Temporary session method. In the command prompt. Enter the path to your adb directory, "path=c:\adb", hit enter and your good to go.
#2 Permanent method. Add the path to your environment variables.
Windows 10:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Edit environment variable > (Select New) > (Enter the path to your adb directory "c:\adb").
Un-updated Win10 or Windows 7:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Goto the end of the long line of paths and Enter the path to your adb directory ";c:\adb".
Click to expand...
Click to collapse
That has been the problem I am facing; when pushing Vol Down +Power it hangs on the Amazon logo. From what others have said, I believe this is the recovery mode but as it doesn't have the options I need, I don't know how I would go about applying the ADB update.
I will try all the steps you have mentioned when I get back home today and report back. I have the stock ROM file and the drivers installed from the previous processes, but as everything I believe will have to be done via command prompt I just hope i'll be able to apply the ADB update that way.
Thank you very much for your help. I really do appreciate the time you've taken to help.

thekrakah said:
I believe the confusion is that it should be "Vol-Down(Left button) + Power". This will put the fire device into restore mode.
Make sure your using the correct 5.11 stock rom restore file.
Once you select, "apply update from adb". It will start to communicate with your machine and ask you to side load the restore rom. Do the deed "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin".
Also if you want to run adb from any directory in windows. There's 2 methods.
#1 Temporary session method. In the command prompt. Enter the path to your adb directory, "path=c:\adb", hit enter and your good to go.
#2 Permanent method. Add the path to your environment variables.
Windows 10:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Edit environment variable > (Select New) > (Enter the path to your adb directory "c:\adb").
Un-updated Win10 or Windows 7:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Goto the end of the long line of paths and Enter the path to your adb directory ";c:\adb".
Click to expand...
Click to collapse
Hi again,
Currently trying to install the ADB update. I'm in the command prompt, with drivers installed (comes up as HTC Dream) but as there is no visual recovery mode, I cannot select 'apply ADB update'. I use 'adb devices' and it looks for but gives me nothing.
Applying the update via 'adb sideload update-kindle-global-37.5.4.1_user_541112720.bin' just leaves me with the process in command prompt, but nothing on the device. I've tried reinstalling the google drivers, but that hasn't helped. All I need is a way to enable me to apply an update via command prompt but not being able to boot into recovery has made it impossible.
I hope there is some kind of fix :/ but thank you for your help so far.

I have the same problem, Amazon recovery was working at one point as i have used it before, but try as i may it will not boot now, all i have is fastboot and a flashing CM12 logo.

DizzyJK said:
Hi again,
Currently trying to install the ADB update. I'm in the command prompt, with drivers installed (comes up as HTC Dream) but as there is no visual recovery mode, I cannot select 'apply ADB update'. I use 'adb devices' and it looks for but gives me nothing.
Applying the update via 'adb sideload update-kindle-global-37.5.4.1_user_541112720.bin' just leaves me with the process in command prompt, but nothing on the device. I've tried reinstalling the google drivers, but that hasn't helped. All I need is a way to enable me to apply an update via command prompt but not being able to boot into recovery has made it impossible.
I hope there is some kind of fix :/ but thank you for your help so far.
Click to expand...
Click to collapse
If your unable to get your Fire device into "Amazon system recovery <3>", you won't be able to apply the restore rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It also looks like dirty loading a Rom is a currently unresolved issue.

thekrakah said:
If your unable to get your Fire device into "Amazon system recovery <3>", you won't be able to apply the restore rom.
It also looks like dirty loading a Rom is a currently unresolved issue.
Click to expand...
Click to collapse
I can't believe that That's so annoying. so there is no was to force the ADB update without enabling it on the device through recovery first?
I doubt they will, but I hope amazon release something that can fix this issue. I know it's really my own fault, but I did really like working with the Fire 7 before this.

DizzyJK said:
I can't believe that That's so annoying. so there is no was to force the ADB update without enabling it on the device through recovery first?
I doubt they will, but I hope amazon release something that can fix this issue. I know it's really my own fault, but I did really like working with the Fire 7 before this.
Click to expand...
Click to collapse
All 2015 Fires are still under warranty (assuming it hasn't already been replaced). Contact Amazon to request a 1-time exchange.

DizzyJK said:
This was successful. After this, I moved onto to wanting to install CM12.1. I found an Unofficial build with GAPPS on XDA and many people confirmed it to be working. I installed with FlashFire as I had with Slim, but after 90 minutes it was still trying to install. Then, before I knew it the battery died.
Now, I have the CM boot animation, but nothing loads. I have no recovery because 5.1.1 doesn't allow for it, so i'm stuck with the CM boot animation and no recovery. I've tried to sideload via command prompt, but my computer doesn't register it as an Android device, just an MTP USB Device, and even if it did register it properly, I don't have a recovery to allow me to install via ADB.
Click to expand...
Click to collapse
Exact same boat here, long time lurker 1st time poster too. If anyone finds a solution please post here.

Davey126 said:
All 2015 Fires are still under warranty (assuming it hasn't already been replaced). Contact Amazon to request a 1-time exchange.
Click to expand...
Click to collapse
You are an absolute genius! I got in touch with Amazon, told them exactly what I did and they sent me another out for free. It isn't the technical solution I was hoping for, but this more than makes up for it. Thank you so much for showing me this. I will still look for a solution to the problem, but I did get a free tablet out of the whole thing

If anyone else is in this boat. You can try booting recovery from fastboot. You'll have to make sure that adb/fastboot is installed on your computer. See this thread ( http://www.xda-developers.com/15-se...ing-fast-adb-fastboot-and-driver-installation ) for help installing it. After it is installed power on the fire holding the right vol + power. It will boot to fastboot mode. If you installed everything right open a command prompt and type the following without the quotes. "fastboot reboot-recovery" if everything works properly your fire will reboot to recovery. Then you can restore the fire with amazons firmware linked a few posts back. You'll have to use adb sideload.

northmendo said:
If anyone else is in this boat. You can try booting recovery from fastboot. You'll have to make sure that adb/fastboot is installed on your computer. See this thread ( http://www.xda-developers.com/15-se...ing-fast-adb-fastboot-and-driver-installation ) for help installing it. After it is installed power on the fire holding the right vol + power. It will boot to fastboot mode. If you installed everything right open a command prompt and type the following without the quotes. "fastboot reboot-recovery" if everything works properly your fire will reboot to recovery. Then you can restore the fire with amazons firmware linked a few posts back. You'll have to use adb sideload.
Click to expand...
Click to collapse
Hmm - I don't think this will work. "reboot-recovery" is not a valid fastboot parameter. "fastboot reboot recovery" (no hyphen) won't work either as the 3rd parameter needs to be a .img file that resides on the computer. To my knowledge no one has created/extracted a generic Amazon recovery for FireOS v5. There's also the problem of getting to fastboot with a bootloader >5.0.1 but that's a separate issue.
What am I missing?

Davey126 said:
Hmm - I don't think this will work. "reboot-recovery" is not a valid fastboot parameter. "fastboot reboot recovery" (no hyphen) won't work either as the 3rd parameter needs to be a .img file that resides on the computer. To my knowledge no one has created/extracted a generic Amazon recovery for FireOS v5. There's also the problem of getting to fastboot with a bootloader >5.0.1 but that's a separate issue.
What am I missing?
Click to expand...
Click to collapse
Confirmed, both commands just return you to fastboot (one flashed up an error). Absolutely no way to reboot into recovery or sideload that I've found.
If you allow it to boot normally, at the CM logo it connects as an unauthorized device so it is at least getting pasrt way into the boot. But without fully booting you cannot authorize the usb connection.
I think its unlikely a fix will be found for this, unless there's some unknown adb commands in fastboot that might work to somehow sideload a recovery or allow CM to at least boot.
---------- Post added at 11:03 PM ---------- Previous post was at 10:14 PM ----------
Maybe this helps somone:
I wonder if the fact it shows locked is causing the problems. >fastboot unlock or unlock-critical return an error, as does any of the flash commands.
The unlock code is interesting, but I have no idea what it means.
Code:
>fastboot getvar all
(bootloader) max-download-size: 134217728
(bootloader) partition-size:userdata: 17329be00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-size:cache: fa00000
(bootloader) partition-type:cache: unknown
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-size:LOGO: 380000
(bootloader) partition-type:LOGO: unknown
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: unknown
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-size:EXPDB: 1160000
(bootloader) partition-type:EXPDB: unknown
(bootloader) partition-size:DKB: 100000
(bootloader) partition-type:DKB: unknown
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) off-mode-charge: 1
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: FORD
(bootloader) version: 0.5
(bootloader) unlock_status: false
(bootloader) unlock_version: 1
(bootloader) unlock_code: 0x8eaXXXXXXX
(bootloader) prod: 1
all: Done!!
finished. total time: 0.817s

Amazon Fire 7" - Which ROM to install?

Hi,
I have the Amazon Fire 7" (not the Fire HD "7!). I did not find any Android ROM for this model, only for the Fire HD 7". Is it possible that such ROM does not exist?
If I'm mistaken, would appreciate if someone could refer me to the proper thread.

moralshixch said:
Hi,
I have the Amazon Fire 7" (not the Fire HD "7!). I did not find any Android ROM for this model, only for the Fire HD 7". Is it possible that such ROM does not exist?
If I'm mistaken, would appreciate if someone could refer me to the proper thread.
Click to expand...
Click to collapse
You need to identify the version of your Kindle. If its the otter2 try these threads over here:
http://forum.xda-developers.com/kindle-fire-hd/fire-2-development
another helpful discussion for you:
http://forum.cyanogenmod.org/topic/90173-otter-or-otter2/
---------- Post added at 02:43 AM ---------- Previous post was at 02:27 AM ----------
If it helps I can attach all the recovery/rom/and gapps that I'm using that seem to work well. I was using pac-rom but switched to slimkat a while ago. I only use this for a bedside alarm clock right now, but I'm thinking of putting it side mounted in my car into my stereo auxiliary running Kodi with the Car Skin they got going on in a thread. I'm not using the latest slimkat rom either I'm using an old version because it works well for me.

How do I identify the version of my Kindle? If it helps, it's the 5th generation that was sold during last December in Amazon for $35

moralshixch said:
How do I identify the version of my Kindle? If it helps, it's the 5th generation that was sold during last December in Amazon for $35
Click to expand...
Click to collapse
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.

monster1612 said:
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.
Click to expand...
Click to collapse
I realize this thread is a little old, but I too am trying to get something else on my Kindle Fire other than Fire OS if possible (LineageOS more than likely). Where might I find all of these drivers and utilities, as I have no idea what my Kindle's codename is.
Thanks!

MZGSZM said:
I realize this thread is a little old, but I too am trying to get something else on my Kindle Fire other than Fire OS if possible (LineageOS more than likely). Where might I find all of these drivers and utilities, as I have no idea what my Kindle's codename is.
Thanks!
Click to expand...
Click to collapse
The driver is available on Amazon's developer site, under the "Installing the USB Driver" section. This is assuming you're using Windows, of course.
The ADB binaries can also be downloaded directly from Google as a single .zip file. Once you have both of those downloaded, you should be able to extract the ADB package to an easily accessible directory, right-click on an empty space within the folder view of said directory while holding the shift key down, click "Open command prompt here", and then type the fastboot command I mentioned in the previous reply to identify your kindle.
(Apologies for the late reply!)

Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Code:
< waiting for any device >
Nothing else happens, it just keeps waiting.

monster1612 said:
The driver is available on Amazon's developer site, under the "Installing the USB Driver" section. This is assuming you're using Windows, of course.
The ADB binaries can also be downloaded directly from Google as a single .zip file. Once you have both of those downloaded, you should be able to extract the ADB package to an easily accessible directory, right-click on an empty space within the folder view of said directory while holding the shift key down, click "Open command prompt here", and then type the fastboot command I mentioned in the previous reply to identify your kindle.
(Apologies for the late reply!)
Click to expand...
Click to collapse
I realized I never quoted you in my last reply (forums didn't like me quoting links since my account is so new), so you probably wouldn't see my previous reply. Thanks again for your help, I quoted my last post below.
MZGSZM said:
Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Code:
< waiting for any device >
Nothing else happens, it just keeps waiting.
Click to expand...
Click to collapse

MZGSZM said:
I realized I never quoted you in my last reply (forums didn't like me quoting links since my account is so new), so you probably wouldn't see my previous reply. Thanks again for your help, I quoted my last post below.
Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Click to expand...
Click to collapse
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.

monster1612 said:
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.
Click to expand...
Click to collapse
The device does show up in its own category:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Assuming this is the correct one, I'm not sure why I still can't get a readout.

monster1612 said:
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.
Click to expand...
Click to collapse
Hate to sound like a nag, but hoping you saw my last post. Any thoughts on why I'm not getting a readout? Thanks again!

MZGSZM said:
The device does show up in its own category:
Assuming this is the correct one, I'm not sure why I still can't get a readout.
Click to expand...
Click to collapse
That's the right category. Theoretically, the device should be recognized in ADB if you already have it enabled on the Kindle. Try going to the device properties and "updating" the driver by selecting a different one from the list of Fire-specific drivers installed.
My apologies for the extreme lapse in response time - I went through finals earlier this month, and totally forgot about XDA for a while. Anyhow, I haven't worked with the Kindle on Windows in a while - drivers are notoriously finicky, so I tend to use Ubuntu and other Linux OSs for adb and whatnot, seeing as though everything seems to just work without the need for device-specific drivers on that platform.

monster1612 said:
That's the right category. Theoretically, the device should be recognized in ADB if you already have it enabled on the Kindle. Try going to the device properties and "updating" the driver by selecting a different one from the list of Fire-specific drivers installed.
My apologies for the extreme lapse in response time - I went through finals earlier this month, and totally forgot about XDA for a while. Anyhow, I haven't worked with the Kindle on Windows in a while - drivers are notoriously finicky, so I tend to use Ubuntu and other Linux OSs for adb and whatnot, seeing as though everything seems to just work without the need for device-specific drivers on that platform.
Click to expand...
Click to collapse
Hey, no worries. I know how crazy life can get sometimes.
I tried using the different driver versions available without any luck. My laptop currently has a copy of Ubuntu installed, so I could definitely try it on there (with some guidance from you). I'm pretty familiar with how to use the terminal, and would've tried it under Linux had I known it might've been easier.
Thanks again for all of your assistance!

MZGSZM said:
Hey, no worries. I know how crazy life can get sometimes.
I tried using the different driver versions available without any luck. My laptop currently has a copy of Ubuntu installed, so I could definitely try it on there (with some guidance from you). I'm pretty familiar with how to use the terminal, and would've tried it under Linux had I known it might've been easier.
Thanks again for all of your assistance!
Click to expand...
Click to collapse
Nice! I don't know if you need to enable the universe software repo within Ubuntu before you can install the adb programs, but you should be able to type sudo apt-get install android-tools-adb android-tools-fastboot to have them install. After that, you can use the fastboot commands exactly the way you would on Windows, and thus should be able to get the Kindle to boot into fastboot directly from a powered off state. Let me know if you need any other advice or help.

monster1612 said:
Nice! I don't know if you need to enable the universe software repo within Ubuntu before you can install the adb programs, but you should be able to type sudo apt-get install android-tools-adb android-tools-fastboot to have them install. After that, you can use the fastboot commands exactly the way you would on Windows, and thus should be able to get the Kindle to boot into fastboot directly from a powered off state. Let me know if you need any other advice or help.
Click to expand...
Click to collapse
So, I'm still not having any luck. I'm not entirely sure why, I'm guessing maybe I'm missing something?
I've tried getting fastboot to work on three different devices now, two of which were running a Linux OS, the third Windows 7.
I'm running the mentioned fastboot command and then connecting the kindle over USB while it is powered off. ADB is enabled in developer settings.
I've tried running the command with or without the ADB daemon started and with or without the computer in question being authorized as I wasn't sure if that was necessary.
I tried it on my laptop (which is now running Kubuntu) without success but, also read somewhere that fastboot doesn't like USB 3.0. For that reason I tried it also on one of my Raspberry Pi 3s with a fresh install of Raspbian Lite. I didn't have anything else available at the moment running Linux.
I'm guessing I'm probably just missing something small or did one of the steps incorrectly maybe.

MZGSZM said:
So, I'm still not having any luck. I'm not entirely sure why, I'm guessing maybe I'm missing something?
I've tried getting fastboot to work on three different devices now, two of which were running a Linux OS, the third Windows 7.
I'm running the mentioned fastboot command and then connecting the kindle over USB while it is powered off. ADB is enabled in developer settings.
I've tried running the command with or without the ADB daemon started and with or without the computer in question being authorized as I wasn't sure if that was necessary.
I tried it on my laptop (which is now running Kubuntu) without success but, also read somewhere that fastboot doesn't like USB 3.0. For that reason I tried it also on one of my Raspberry Pi 3s with a fresh install of Raspbian Lite. I didn't have anything else available at the moment running Linux.
I'm guessing I'm probably just missing something small or did one of the steps incorrectly maybe.
Click to expand...
Click to collapse
Does your Linux distro recognize the device if you have it plugged in while you're in the Kindle's main OS and you type adb devices? It should work if you have ADB enabled in developer settings.

monster1612 said:
Does your Linux distro recognize the device if you have it plugged in while you're in the Kindle's main OS and you type adb devices? It should work if you have ADB enabled in developer settings.
Click to expand...
Click to collapse
Yep, if I type that a message pops up on screen saying it's unauthorized. The kindle then asks me if it should be authorized.

Try running fastboot as root.

basenjidad said:
Try running fastboot as root.
Click to expand...
Click to collapse
Thanks for the suggestion. I gave that a shot, still no luck getting this Kindle to fastboot.

monster1612 said:
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.
Click to expand...
Click to collapse
After installing LineageOS on another device, I learned of a command that should force the Kindle to fastboot, and it seemed to work. When I ran the suggested fastboot command I got this output:
Code:
product: AUSTIN
finished. total time: 0.004s
Where might be my next step in finding a compatible ROM?
Many thanks again!

Bootlooping with Android 12 beta preview

TL;DR- I'm trying to get back to Android 11 but I only have access to the fastboot menu since my phone is bootlooping. I'm fairly certain I hadn't enabled USB debugging when the phone was fully functional so I'm not sure if I can use ADB to do so. I also don't have the bootloader unlocked
I downloaded the 12 beta preview last week to try the new features, some UI bugs understandably but was mostly fine. A couple days ago while the screen was off and I just had the phone in my hand it randomly activated SOS mode so after a brief panic and cancelation of the 911 call I opted out of the beta immediately. The next morning after using my phone a bit I picked it up and noticed it was rebooting and was a little warm, and it's been bootlooping since then. I still remember the Andoid 12 UI being active so I'm pretty sure it hadn't reverted to the "new" 11 firmware yet.
I'm trying to revert back to 11 using the ADB on my PC, but I realized that I'm pretty sure I hadn't enabled USB debugging when my phone was still functional, so I'm not sure how to bypass that if I can at all. The web firmware flasher tool does detect my phone, but can't properly connect and I assume it's because the USB debugging isn't enabled.
Before I tried using the ADB I had attempted to perform a factory reset to fix the bootloop and the log messages said it was successfully done, but that didn't get it out of the loop.

@jet flyer
I didn't see the word "locked" or "recovery" anywhere in your post. If you are bootloader unlocked, you use fastboot to flash a full image. If you are BL locked, that should have been in your TL;DR. If you are BL locked, you can still flash a full OTA without having usb debug enabled. You just need to have the latest fastboot/adb binaries installed. Download the rescue OTA, put it in your adb folder and then from recovery mode, use the update via adb option. You do NOT need usb debug enabled to do this. You do however need a working Recovery mode. If you are BL locked and cannot access recovery that is the end of the road.

Sorry for the delayed response wanted a day off so I had enough time to properly deal with this. No it's not unlocked, edited OP to indicate that.
I only downloaded adb last week so that should be the most recent, are the fastboot binaries included in that install or is that something separate?
Using this video for help on how to run adb
I get the device connected sound on my PC when I select install from ADB on the recovery menu and I have ADB running at the C:\adb folder location. when I do the adb devices command I get this
'adb' is not recognized as an internal or external command,
operable program or batch file.
using the powershell I got the long list of text that's mentioned in the video after typing \adb but I still get a similar, but different, error when doing the devices command trying to confirm it's connected
Since this is probably just an error on my part not doing the right commands or something I'm hopping on the xda discord, I'll post here if I get it figured out

Download platform tools from here https://developer.android.com/studio/releases/platform-tools. Unzip it and then put the file that you want to side load in the same folder. I prefer PowerShell. Type adb sideload "file name.zip. That might not work if USB debugging isn't checked. If it doesn't try this.
Transfer the download OTA file to your device’s internal or external storage. Don’t put it inside any folder as the system won’t be able to find it.
Next up, boot your device to recovery.
From recovery, navigate to the Apply Update from SD Card option using Volume Keys. Press the Power key to confirm your selection.
Similarly, use the Volume keys to highlight the OTA.zip file and the Power key to install it. Once the process finishes, you could then use the Reboot system now option to boot your device back to OS

ok finally got something to run on my phone but got an error, here's the file paths and what I typed just in case
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here's what the phone says, sorry about the marginal focus my backup pixel 2XL is doing it's best with the reflective screen. The relevant messages start right after the purple of the IR focusing laser reflection
one of the first errors is E: footer is wrong
and Error 21: signature verification failed
I recall hearing on one of those videos or guides I read that something has to be digitally signed, but this is a direct download from the Android website, wouldn't be already be signed?

jet flyer said:
ok finally got something to run on my phone but got an error, here's the file paths and what I typed just in case
View attachment 5333167
And here's what the phone says, sorry about the marginal focus my backup pixel 2XL is doing it's best with the reflective screen. The relevant messages start right after the purple of the IR focusing laser reflection
View attachment 5333175
one of the first errors is E: footer is wrong
and Error 21: signature verification failed
I recall hearing on one of those videos or guides I read that something has to be digitally signed, but this is a direct download from the Android website, wouldn't be already be signed?
Click to expand...
Click to collapse
Sorry for the delayed response, but If you use "reply" to a post the user will get an email notification and so respond more quickly. I normally check this board once a week. Yes, there is one zip file from Google that contains all the binaries you need for adb/fastboot. Yes the image coming from Google is signed. They even include the file hash so you can verify the file is a mirror image and un-corrupted. I'm going to continue down the adb method because it is fool proof and you may not be able to "push" the file to your device and use the sdcard method.
I'm not sure you have added your adb folder to your PC's path statement and this could be causing an issue. If you add this folder to the path, you can call up adb from any folder. However if you have the ota image in the same adb folder, and you navigate to that same folder before typing commands it will still work. I'm not seeing any of your inputs on your photo, so I can't check that. You can easily copy/paste text from the command window so we can clearly see what you are typing and the response back. What response are you getting to "adb devices" and "adb version" ? Until you get back your phone's serial number as a response, you are not connected properly. You can PM me for more assistance or use the reply button on this note. Best of luck.

v12xke said:
Sorry for the delayed response, but If you use "reply" to a post the user will get an email notification and so respond more quickly. I normally check this board once a week. Yes, there is one zip file from Google that contains all the binaries you need for adb/fastboot. Yes the image coming from Google is signed. They even include the file hash so you can verify the file is a mirror image and un-corrupted. I'm going to continue down the adb method because it is fool proof and you may not be able to "push" the file to your device and use the sdcard method.
I'm not sure you have added your adb folder to your PC's path statement and this could be causing an issue. If you add this folder to the path, you can call up adb from any folder. However if you have the ota image in the same adb folder, and you navigate to that same folder before typing commands it will still work. I'm not seeing any of your inputs on your photo, so I can't check that. You can easily copy/paste text from the command window so we can clearly see what you are typing and the response back. What response are you getting to "adb devices" and "adb version" ? Until you get back your phone's serial number as a response, you are not connected properly. You can PM me for more assistance or use the reply button on this note. Best of luck.
Click to expand...
Click to collapse
Ah sorry, still getting used to the specifics of this forum. Thanks for checking though.
I do get the serial number back as a response to verify I'm properly connected, I just didn't do it in that specific instance to avoid posting that online. And yes I did add it to the path(as far as I understand, that's just a convenience thing though?) but I'm still running it from the ADB folder just to be sure.
I'll go ahead and type here what commands I did and what the phone log says, since it's not in focus in the picture.
on adb I typed .\adb sideload coral-[specific file version].zip
adb response: Total xfer: 0.00x
on my phone which was on the load from adb screen it said this:
Now send the package you wan to apply
to the device with "adb sideload <filename> . . .
Supported API: 3
Finding update package. . .
Verifying update package. . .
E:footer is wrong
Update package verification took 0.5 s (result 1).
E:Signiture verification failed
Error: 21
Install from ADB completed with status 2.
Installation aborted.
Then it tried one more time automatically with the exact same text except taking 0.6 seconds but still failing and the same error messages. Should I just download the latest package (now the June update) and try again, or did I do something wrong? The file explorer window is where I opened the powershell from and where the file was extracted to. What does error 21 mean?

jet flyer said:
Ah sorry, still getting used to the specifics of this forum. Thanks for checking though.
I do get the serial number back as a response to verify I'm properly connected, I just didn't do it in that specific instance to avoid posting that online. And yes I did add it to the path(as far as I understand, that's just a convenience thing though?) but I'm still running it from the ADB folder just to be sure.
I'll go ahead and type here what commands I did and what the phone log says, since it's not in focus in the picture.
on adb I typed .\adb sideload coral-[specific file version].zip
adb response: Total xfer: 0.00x
on my phone which was on the load from adb screen it said this:
Now send the package you wan to apply
to the device with "adb sideload <filename> . . .
Supported API: 3
Finding update package. . .
Verifying update package. . .
E:footer is wrong
Update package verification took 0.5 s (result 1).
E:Signiture verification failed
Error: 21
Install from ADB completed with status 2.
Installation aborted.
Then it tried one more time automatically with the exact same text except taking 0.6 seconds but still failing and the same error messages. Should I just download the latest package (now the June update) and try again, or did I do something wrong? The file explorer window is where I opened the powershell from and where the file was extracted to. What does error 21 mean?
Click to expand...
Click to collapse
Sorry, I don't know what error 21 means. Trying the latest image is not going to hurt at this point. Make sure you post the complete file name of the image you are trying to flash. I think there may be bootloader version mismatch that is causing the errors. Verify and post your bootloader version (fastboot menu) and OS version (recovery menu). Have you tried doing a factory reset from recovery and retrying? At this point I would keep searching "rescue ota" for tips and hints. Pasting your screen would be best, rather than retyping. Best of luck!

v12xke said:
@jet flyer
I didn't see the word "locked" or "recovery" anywhere in your post. If you are bootloader unlocked, you use fastboot to flash a full image. If you are BL locked, that should have been in your TL;DR. If you are BL locked, you can still flash a full OTA without having usb debug enabled. You just need to have the latest fastboot/adb binaries installed. Download the rescue OTA, put it in your adb folder and then from recovery mode, use the update via adb option. You do NOT need usb debug enabled to do this. You do however need a working Recovery mode. If you are BL locked and cannot access recovery that is the end of the road.
Click to expand...
Click to collapse
So I read up and Error 21 is because the bootloader is locked. I have the latest bianaries installed like you mentioned, is there something else I was missing in my process?

jet flyer said:
So I read up and Error 21 is because the bootloader is locked. I have the latest bianaries installed like you mentioned, is there something else I was missing in my process?
Click to expand...
Click to collapse
Because your bootloader is locked, you cannot flash a full image . You have to flash an OTA instead.
Secondly, the OTA you choose has to match your current bootloader version or it won't work.
Read the instructions again for flashing a rescue OTA via recovery.
1. Have you accessed the phone's recovery menu and used the update via adb option?
2. What is your current bootloader version? (recovery menu)
3. What is the full name of the file you are attempting to flash? (OTA)
https://developers.google.com/android/ota

v12xke said:
Because your bootloader is locked, you cannot flash a full image . You have to flash an OTA instead.
Secondly, the OTA you choose has to match your current bootloader version or it won't work.
Read the instructions again for flashing a rescue OTA via recovery.
1. Have you accessed the phone's recovery menu and used the update via adb option?
2. What is your current bootloader version? (recovery menu)
3. What is the full name of the file you are attempting to flash? (OTA)
https://developers.google.com/android/ota
Click to expand...
Click to collapse
ohh, I never noticed that tab at the top that says OTA, I get it now that those are needed for non-unlocked bootloaders. I see all the different versions, what does my bootloader version have to do with one of those? I only see the dates pertaining to the monthly updates, how do I know which one is for my bootloader version? I found the section specific to the Pixel 4XL

That worked!!! Thanks for the help, kinda annoyed it was as simple as that tab at the top left of the page saying OTA updated, but glad to have my phone back after 6 weeks. My Pixel 2XL did it's best but a lot of the apps I use for my action camera or drone stuff didn't even work with it haha

jet flyer said:
That worked!!! Thanks for the help, kinda annoyed it was as simple as that tab at the top left of the page saying OTA updated, but glad to have my phone back after 6 weeks. My Pixel 2XL did it's best but a lot of the apps I use for my action camera or drone stuff didn't even work with it haha
Click to expand...
Click to collapse
Happy to hear you are back up and running! Cheers.