yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
[HOW-TO] Before asking for troubleshooting help...

Frequently Asked Questions - Amazon Kindle Fire

[GUIDE] Kindle Fire For Beginners

[HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)
[Kindle Fire Q&A, Help & Troubleshooting] Zeklandia:
He has all of the drivers installed, but KFU seems to have an issue with file paths. I have redownloaded it for him and I also updated his copy of the SDK with Kindle Fire drivers and a newer ADB. The KFU returns an error "System cannot find the path specified for everything, even though it is extracted straight out of the zip it came in. All he did was choose install TWRP and it didn't even make it to fastboot mode before it bricked.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Thank you for your insight, but all the information needed to fix what is a very common problem can be found in the threads to which links have been provided. The device IS in fastboot. Simply changing the bootmode is the key to resolving the problem. That being said, the KFU is not the end all/be all to changing the bootmode or installing TWRP.
[Kindle Fire Q&A, Help & Troubleshooting] Zeklandia:
It is not in fact in fastboot, it is not even listed in adb devices or fastboot devices.

---------- Post added at 12:52 PM ---------- Previous post was at 12:29 PM ----------

I have a feeling it is trying to boot into stock recovery, as KFU was trying to reboot into TWRP (which never installed because KFU was broken).

---------- Post added at 12:55 PM ---------- Previous post was at 12:52 PM ----------

If we can get out of stock recovery, that would be useful. Do you have any idea how to bring up the menu in stock recovery? Does he need to hold the power button down or press it in a pattern?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
While some who know me better may be prepared to see me respond in my usual manner at this point, I have instead, decided to play nice ;)

I have been a member of this forum for quite some time and have seen hundreds of different problems in just as many scenarios for each, and I can assure you, without even a shred of doubt, that the device is in fact in fastboot mode (unless, of course, the information provided in the OP is inaccurate).

You can find information for properly identifying fastboot mode in the "Frequently Asked Questions" thread and the "Fastboot Guide" linked to within it, so please feel free to prove me wrong.

With that,

Just because the device itself doesn't respond to fastboot commands from the computer, doesn't mean the device isn't in fastboot mode. It simply means (in this case) that the drivers are not properly installed or configured, despite the steps taken to do so. Windows is very tricky when it comes to installing drivers for Android and there are hundreds of posts within these forums that should be able to convince you of that. If you want to eliminate all doubt and ensure that driver problems aren't just compounding the issue, set up a Linux LiveUSB and either install SoupKit, or configure it manually to communicate with the device via USB so that adb and fastboot commands will work properly.

Good luck
[Kindle Fire Q&A, Help & Troubleshooting] Zeklandia:
I appreciate you trying to help, but his device is 100% stock. KFU has set it to boot into recovery, and it will continue to boot into the stock recovery until we can find a way to change that idme bootmode. Tomorrow, I will attempt to use my factory cable on it, but for now all fastboot does is wait for device. I use Linux, so if it truly is in fastboot mode, then it should have no problem, especially with the factory cable.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Looking at your signature, I see that you are technically competent enough to take a look at the KFU 'run.bat' and see how it works. When the option to install TWRP is selected, the script uses Pokey9000's 'fbmode' to boot into fastboot mode. Once KFU is able to detect the device in fastboot, it then uses fastboot commands to flash TWRP to the recovery partition and then reboot to recovery. If the KFU were able to detect the device in fastboot mode and TWRP was not installed due to file paths, then the device would still boot into the stock recovery, normally, and you would see plenty of error messages giving you a clue as to what went wrong. Messages in the KFU window compared to those found in the script itself can also show you where things went wrong.

What happens (more times than I care to try and estimate) is, due to the way Windows handles Android drivers, when the device is put into fastboot mode (even though adb commands were working at the time), the fastboot drivers aren't working properly, the script cannot move forward and the device gets stuck in fastboot mode.

As I mentioned earlier, the "Fastboot Guide" linked to in the FAQ, tells you how to recognize fastboot mode beyond all uncertainty. With all due respect, I'd suggest you look into it before deciding that you know best in this particular situation.

And not to make assumptions about your level of proficiency with Linux, but don't forget that you have to either set up udev rules for the device, or run your fastboot commands as root for it to work properly.
[Kindle Fire Q&A, Help & Troubleshooting] menriquez:
same issue...

yes perhaps you should be a little more sympathic to the OP as 1. he probably has a valid issue (im having the same problem...neither windows nor Soupkit is recognizing my KF thats stuck in the white and orange logo fastboot and 2. none of the above links help this problem in any manner. I have been researching this issue for days now and have tried a few different distros (just my luck Mint's persistance didnt work...sigh) and no matter what, my computer will not communicate with the KF.

it seems my KF is now bricked because I ran the KFU and selected install "FireFireFire" before rooting...it sure would have been nice if some sort of warning would have popped up asking "ARE YOU SURE YOU WANT TO DO THIS and HAVE YOU CHECKED THAT YOU ARE CURRENTLY ROOTED??" because it sure seems that ANYONE making the big mistake i did of trying to install fff without first having root would have this same problem.

if you have any other suggestions it sure would be appreciated...thanks.
[Kindle Fire Q&A, Help & Troubleshooting] menriquez:
wow...sigh...listen the last thing my post tried to do is shift blame...i CLEARLY stated *I* made a BIG MISTAKE didn't I?? i dont need a flame war here sheesh im just trying to fix this ****ty kindle for a buddy.

lol i read and did ALL of that my chippy friend...the logo starts and stays bright so im sure im in fastboot mode. i got the latest ubuntu on a pen, like i said after i tried Mint 15 and discovered that persistence on a pen doesn't work well with that distro currently. ubuntu did, and in fact recognizes all my other android devices no problem...but nothing at all when i plug the kindle

like i said both in my original post and above, i figured out the persistence issue its working now. the reboot loaded the rules but when the script runs im getting two errors which, due to my deep frustration at the time i didn't write down the exact wording. i figured i'd chill for a while and then try again later.

hey i totally appreciate your help and your wish of luck lord knows ill take anything right now this stupid "project" has caused me more grief then i could have ever imagined it could. btw, i didnt get "offended" i just thought maybe you were being kinda hard on the OP due to my experience dealing with the exact same issues he posted he was dealing with...

...believe it or not not everyone who doesn't have the same experiences with this stuff as you do aren't necessary idiots or unskilled at using complex systems. thanks again for your continued help and do have a great day!
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
The last thing I want to do is to get into a flame war with anyone, but when someone comes to the forum and says something like...

...which, by the way, is entirely based on misinformation...it is very easy for someone to assume the author is, whether directly or indirectly, speaking poorly about a developer's work and assigning blame by presuming that the mistake would not have been made if the tool in question had been made differently. Based on the limited information from your original post, one can only assume that your situation is no different from the hundreds of other users with the same exact problem that also swore the information available did not pertain to their situation and that they were somehow unique, only to find out 50 posts later that it was not the case.

But rather than letting this discussion escalate any further, lets try a different approach. I will give you the benefit of the doubt and entertain the thought that your situation is in fact unique and that there is possibly some other solution for your problem. But, in order for me to do that, I'm going to need some information...very detailed information.

From what I gather so far, based on the information you've provided in your second post is...

1) Your device is in fastboot, confirmed by the fact that the Kindle Fire logo stays brightly lit.

2) You are currently using a LiveUSB with Ubuntu installed and working persistence.

3) When you ran the SoupKit install script, you received errors of some sort, but don't you remember what they were.

4) You are unable to send any fastboot commands at all.

The things I would like to know are...

1) What version of Ubuntu are you running?

2) What brand of pendrive are you using?

3) What is the exact error you received when trying to install the SoupKit?

4) With your device connected, enter the following commands (in Linux) and post the results:

lsusb -vd 1949: | grep 'bcdDevice'

cat ~/.android/adb_usb.ini

sudo cat /etc/udev/rules.d/51-android.rules
[Kindle Fire Q&A, Help & Troubleshooting] menriquez:
firstly i'm very appreciative of your decision to get this back on a positive track and even more thankful that you are still trying to help...

1. ubuntu 13.04 32-bit

2 16gb sandisk with 1024m persistance

3. i reinstalled everything and double checked it...i am no longer getting any errors running soupkit it just says "device offline"

4 lsusb -vd 1949: | grep 'bcdDevice' - nothing just the prompt

5. cat ~/.android/adb_usb.ini - 0x1949

6 . sudo cat /etc/udev/rules.d/51-android.rules -

# adb protocol for blaze / otter (Amazon Kindle Fire)

SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"

# fastboot protocol for blaze / otter (Amazon Kindle Fire)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"

well thats it...i plug my nexus 7 and GS3 and even an ultra cheapo zte warp sequent and it connects right up to all of those...
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Oh........this again....

For reasons I have yet to figure out, there are rare (and I do mean rare) situations where Linux just will not detect the device whatsoever. When you enter the 'lsusb' command, whether the udev rules are configured properly or not, Linux should still detect your device when plugged into the USB. I can probably count on one hand the number of times I've seen this happen, and I've never been able to recreate the problem on my own.

It could be caused by using the wrong USB port (i.e. USB3.0 instead of USB2.0), it could be caused by the USB pendrive itself, you could have a faulty cable, it may even be the Linux install itself, but those are just wild guesses because I have really don't know. My best estimate is that there is a bug in the stock bootloader that sometimes causes it to malfunction when put into fastboot because (in the few instances I've seen), users that were able to resolve their situation did so by using usbboot to install a custom bootloader. This of course requires opening the device and performing the "shorting trick" to drop the device into usbboot mode.

If I were you, considering you probably haven't attempted to usbboot before, you should try a different USB port, a different USB cable, and a different pendrive to see if you have any luck. Otherwise, you may have no other choice but to usbboot.

The unfortunate thing usbbooting is, it's just one of those things you have to somehow figure out on your own, even with the instructions given in the Firekit/usbboot thread (it's really about technique more than anything else). I've done it several times myself, mostly for testing and various other reasons, but the first time (when I really needed it), took practically forever to get it right.

If you do take the usbboot route, you can launch Firekit from the SoupKit utility script (option #4, I think) and follow the instructions in the Firekit thread. Be very careful opening the device, use a safety pin for creating the short (the reason will become apparent when you get the device opened), and most of all...good luck.

[Edit:] And yes, crow is very tasty ;)
[Kindle Fire Q&A, Help & Troubleshooting] oliverisboss:
Charge kindle, boot into the frozen logo screen with no animation, plug into computer, and reboot computer, i want to share this with everyone because it worked for my kindle
[HTC One X] leecavturbo:
When I delete contents or all the files they come back. What is happening
[HTC One X] and313:
They dont like being deleted :) maybe you can be a lot more specific
[HTC One X] Sadman Khan:
Try using a different file manager by the name of..File Manager
[HTC One X] Gormsen:
Or you could try connecting the phone to the computer and deleting it through windows. It sounds odd and don't know what is wrong.. last resort go through recovery and delete it there (don't wipe the sdcard though) ;)

Also: this doesn't belong in the General section but rather in Q&A :)
[General Questions and Answers] RobPitt:
Is it possible to set Widget Locker as the lock screen loaded on boot? Currently the ROMs lock screen is shown on boot for a short period until Widget Locker is loaded. I'm being pedantic but it's a minor annoyance.
[Samsung Galaxy Player 4.0, 5.0] NapalmDawn:
I recently picked up a GP 4.2. I immediately got it rooted so now I'm running a 2.3.6 stock rom with root. What's the next step in terms of getting a recovery installed and maybe moving up to an ICS or JB rom? I've kind of poked around a bit but it's some what confusing with all the other types of GPs in the same area. Does anybody have a recovery and rom they'd recommend? Is using rom manager to push CWM feasible?
[Samsung Galaxy Player 4.0, 5.0] MetaMav:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://xdaforums.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community! :D
[Samsung Galaxy Player 4.0, 5.0] NapalmDawn:
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.

I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
[Samsung Galaxy Player 4.0, 5.0] SerkTheTurk:
you should flash CWM via odin first and then flash the ROM via CWM
[Samsung Galaxy Player 4.0, 5.0] NapalmDawn:
Would the instructions here be the right thing to do?

http://www.youtube.com/watch?v=-MbHDbjph8A
[Samsung Galaxy Player 4.0, 5.0] Xenphor:
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
[Samsung Galaxy Player 4.0, 5.0] MetaMav:
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://xdaforums.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.

From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.

Hope that helps. :D
[Samsung Galaxy Player 4.0, 5.0] Xenphor:
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?

Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
[Samsung Galaxy Player 4.0, 5.0] NapalmDawn:
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
[Samsung Galaxy Player 4.0, 5.0] Xenphor:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
[Samsung Galaxy Player 4.0, 5.0] SerkTheTurk:
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
[Samsung Galaxy Player 4.0, 5.0] Xenphor:
Where could I find a stock kernel?
[Samsung Galaxy Player 4.0, 5.0] SerkTheTurk:
US version: http://xdaforums.com/showthread.php?t=1885374

International: http://xdaforums.com/showthread.php?t=1884071
[Samsung Galaxy Player 4.0, 5.0] Xenphor:
Ok thank you. However, will this work with YP-GS1?

But about kernels, on the webpage where I downloaded the stock rooted rom http://tau.shadowchild.nl/attn1/?p=166 it says specifically that the Wifi module in system and kernel must MATCH. This is what I'm talking about in regards to kernel compatibility with roms. How do I know if a kernel I'm downloading will have changes applied to it that will work with another rom like with this stock rom/kernel?
[Samsung Galaxy Player 4.0, 5.0] NapalmDawn:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.

Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
[Samsung Galaxy Player 4.0, 5.0] Xenphor:
Well I had to flash this kernel http://xdaforums.com/showthread.php?t=2198234 to get CWM on mine. I haven't actually flashed anything with CWM because there doesn't seem to be any good roms for the 3.6 unless CM7 comes out sometime. I used Odin to flash a stock rom from here http://tau.shadowchild.nl/attn1/?p=166
[Samsung Galaxy Player 4.0, 5.0] NapalmDawn:
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
[Samsung Galaxy Player 4.0, 5.0] MetaMav:
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://xdaforums.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.

The way I successfully installed (if I remember correctly):

-Do a factory reset of rooted stock ROM

-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)

-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM

-Wait a little while and your device should boot up properly

I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.

SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search. :D
[Samsung Galaxy Player 4.0, 5.0] Xenphor:
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.

I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?