yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Q&A, Help & Troubleshooting] backspacepc:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
Actually...I'm a she. :)

Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!

Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda. :(
[Kindle Fire Q&A, Help & Troubleshooting] backspacepc:
Sorry ma'am! :D did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
[Kindle Fire Q&A, Help & Troubleshooting] backspacepc:
You may also want to try to rerun your root script, oddly enough I've had that work before too.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Did you notice the second post in the Linux tutorial?
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
:)

I just ran kfu and I I was able to get it to do a normal boot. YAY!

Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
I did, but I used vi instead of gedit. :) And i verified that 0x149 was in the file on a new line.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
I can't imagine why using vi would make any difference but you could try gedit to see if it works.

As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).

When you're in fastboot mode, hold the power button until the device shuts down.

Shift + right click the KFU folder that contains fastboot (tools) and open as a command

In the prompt that comes up, enter:

fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img

When your prompt says "waiting for device", turn the device back on.

Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
When installing TWRP 2.1 manually, at the adb shell command, the device isn't found. Even when I type in adb devices it doesn't recognize the KF.

I ran the KFU again and also ran the install_drivers.bat. ARGH!!!!
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Most of the time just reinstalling drivers isn't enough. Did you uninstall the old ones?

[Edit:] Also, adb commands won't work in fastboot mode.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
I'm going to completely uninstall everything on my Windows box & do a fresh re-install SDK and start fresh. Let's see how this goes.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
After I uninstalled everything, I did not run KFU at all and I was able to get adb to recognize the KF.

Okay...so I ran these commands:

adb push fbmode /data/local/fbmode

adb shell chmod 755 /data/local/fbmode

adb shell /data/local/fbmode

adb reboot

All was ran successfully.

Then I put fastboot.exe in the platform-tools folder and I ran this:

fastboot flash bootloader u-boot.bin.

Like the directions said from the Kindle Fire 6.3 Root thread, I'm stuck at the 'kindle fire' screen. Screen flashed a couple times, but I'm still at the screen and there's no graphic that's running across the words 'kindle fire' like it does during a regular reboot. I let it go for about 5 minutes, then rebooted the KF while the fastboot command is at 'waiting for device'.

I cycled the power and ran the command:

fastboot oem idme bootmode 4000

And it's still waiting for the device to connect and I'm at the KF screen. Windows does recognize the KF as an Android ADB Interface.

I am hesitant at running FKU if I don't have to...but...with the instruction of backspacepc last time, I was able to go into the Bootmode Menu and and select normal boot and I was able to boot the KF.
[Kindle Fire Q&A, Help & Troubleshooting] backspacepc:
you also need to run the commands in fastboot, not adb.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
I hate to say it but you're just spinning your wheels with Windows.

There is a guide on the Ubuntu website for setting up the sdk that you might want to try.

https://help.ubuntu.com/community/AndroidSDK

[Edit:]Just be sure to add the udev rules from the previous tutorial.
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
If you have not installed the FFF bootloader, then you have the stock bootloader. I believe this must be the case because you report seeing the "kindle fire" bootlogo, but I'm a little concerned that you said the screen flashed a couple of times. It should not do that when you are in fastboot mode. If you are in fastboot mode with the stock bootloader, you MUST provide the vendor ID (that's the "-i 0x1949" part) in your fastboot commands or they will not get sent to your KF device. That's why it's telling you that it's waiting for a device, because without the vendor ID, your KF will not respond to those commands. If your fastboot binary chokes with the -i switch like you stated earlier in this thread, then you have an old/incompatible fastboot executable. Use the one that is in KFU's tools folder. Try issuing...

fastboot -i 0x1949 getvar product

If it returns "product: kindle" then you are in the right place. Now all of your subsequent fastboot commands will need the "-i 0x1949" switch until you boot back up to fastboot mode with FFF.

I actually have all of this laid out near the bottom of this post...

http://xdaforums.com/showpost.php?p=23747804&postcount=3

You'll see that you've done part of the same already. My guide has you put all of the necessary software in the C:\kfu\software folder, so you just need to change your file paths to wherever you have your bootloader and recovery files. Since you want to root, you'll just need to get up to and do step 7 unless you actually want to install a custom ROM instead. Otherwise, you can go back to jcase's post about rooting and finish up the process. You're almost there...
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
I'm wondering that too. I'm downloading Ubuntu 12 and I'll install it on the other partition on my laptop and will this all later tonight.

Thanks, kinfauns!

I have a feeling I'm doing something wrong with fastboot. That is where I always hit a wall. I copied over fastboot.exe from KFU and put it in the appropriate folder under C:\Programs. I ran your suggested command above and it's stuck at "waiting for device". I rebooted the KF, too. Would it return "product: kindle" fairly quickly after running the command? Sometimes I'm not so patient. :)

I'm also going to run through your link/thread to see if I can get this darn thing working while Ubuntu is downloading.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
So the big thing I'm missing is a factory cable. I saw a Motorola cable could be a factory cable, so I swapped out cables with a Motorola one that I had laying around from a phone. Still waiting for device.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
What you have is a Motorola OEM cable. What you need is this:

http://xdaforums.com/showthread.php?p=20317299
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
A factory cable is different than a normal cable...

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

Did you actually run these commands successfully?

adb push fbmode /data/local/fbmode

adb shell chmod 755 /data/local/fbmode

adb shell /data/local/fbmode

adb reboot

If that part of it worked, you should still be in fastboot. What does your Kindle Fire do when you reboot it? Does the bootlogo come on and stay there? Does the screen ever go black? Do you have the "Android Phone -> Android ADB Interface" in the Windows Device Manager?

Don't move the adb or fastboot programs out of KFU's tools directory. Open the tools folder, shift-right-click inside the folder and "Open command window here" to run the adb and fastboot commands.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
Yes, in Dev Mgr, it's listed as Android ADB Interface.

Yes, I ran those adb commands before. And ADB always recognizes the device, but the KF gets "stuck" at the KF screen. I didn't realize this initially, and hopefully this will help out other peeps, but you WANT it stuck at the Kindle Fire screen so you can run the fastboot commands. Am I right?

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>ad
b push fbmode /data/local/fbmode
* daemon not running. starting it now *
* daemon started successfully *
2907 KB/s (510876 bytes in 0.171s)

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>ad
b shell chmod 755 /data/local/fbmode

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>ad
b shell /data/local/fbmode

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>ad
b reboot

So then I run:

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>fa
stboot -i 0x1949 getvar product
product: kindle
finished. total time: 0.000s

Then I ran:

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>f
stboot -i 0x1949 flash bootloader u-boot.bin
sending 'bootloader' (211 KB)... OKAY [ 0.059s]
writing 'bootloader'... OKAY [ 0.047s]
finished. total time: 0.105s

Then I ran:

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>fa
stboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
sending 'recovery' (5568 KB)... OKAY [ 1.389s]
writing 'recovery'... OKAY [ 1.574s]
finished. total time: 2.962s

Then I ran:

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>fa
stboot -i 0x1949 oem idme bootmode 5001
... OKAY [ 0.693s]
finished. total time: 0.694s

Then:

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>fa
stboot -i 0x1949 reboot
rebooting...
finished. total time: 0.002s

Weeeeeeee!!! I finally got the yellow triangle and it booted into TWRP!!!!!

So I ran a backup in TWRP, then I downloaded the ROM of my choice (CM9), and copied the .zip to the root of the kindle drive. I unmounted the drive on Windows, went back to the install screen on TWRP, select it and selected the CM9 zip, and installed it. I followed your link/directions with that step: http://xdaforums.com/showpost.php?p=23747804&postcount=3

After the ROM was flashed, I selected to wipe cache/dalvik. Then i rebooted the system. I unplugged the cable and couldn't get the KF to turn on after it was powered off. Funny...as soon as I plugged it back in, Windows recognized it and the FK wasn't even on. It finally booted up and I got the yellow triangle, but now it seems like it's "stuck" (yup that's a technical term) and it won't boot into CM9. Any suggestions? I think I've seen a few threads out there with this issue....I'm sure there's a thread out there for this and I know I'm not the only one with this issue.
[Kindle Fire Q&A, Help & Troubleshooting] backspacepc:
Try this, run kfu again, do the normal boot mode thing, then boot into twrp, wipe cache/dalvik as well as system, then reflash your rom. Select system reboot.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
Okay. I was able to boot into twrp and I'll wipe the cache/dalvik and try again.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Which version of CM9 did you flash? What build/version, etc.?
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
http://xdaforums.com/showthread.php?t=1563171

From that thread.

[ROM] |4/21/2012| |ReloadedROM™| |CM9 Reloaded v1.2H| |Kindle Fire| |Kernel 3.0|
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
Congratulations on getting the ROM installed.

When you change out ROMs to a different one... or in your case go from stock to a custom ROM, you should do a "Wipe -> Factory Reset" in TWRP. This will delete the /data partition and give you a clean install of the ROM. I guess I should make a note of that in the guide.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
Maybe I'll do a Factory Reset right now. I did a backup before flashing to CM9 so I should have a solid backup. But really, it makes sense. I hate installing a new OS on PC without wiping the HD flash. Plus, I can't get the KF to boot into the ROM right now.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
When it boots for the first time, leave it alone for a while; sometimes up to 5 minutes. If that doesn't work, try a different rom. You're getting past the bootloader and you have access to recovery so the "hard" part is done already.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
The yellow triangle...is that the new boot screen icon?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
After that, when the screen goes black.

[Edit:]If you are literally stuck at the yellow triangle, change your bootmode to normal.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
I didn't get a chance to do the factory reset...but after I wiped the data cache, I can't boot into twrp now.

Yeah I'm stuck at the triangle. I plugged the FK in & Windows is recognizing it as a "kindle".

I tried to run the fastboot commands to reset the bootmode but since Windows sees it as a "kindle" I'm SOL, I think.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
You're not SOL, you just have to uninstall/reinstall your drivers again.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
I uninstalled the "kindle" drive in Dev Mgr, rebooted my PC and rebooted the KF. Booted it back up, and Windows initially said it was an unknown device. I rebooted the KF again, and then it was listed back as "kindle". Or were you talking about reinstalling the Google/Android WinUSB driver?
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
The second post in the thread soupmagnet mentioned to you before has information on how to install your drivers and make sure they are working correctly.

http://xdaforums.com/showthread.php?t=1552547
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
Wow...you guys rock. I didn't even see that!

Followed the instructions and it worked like a charm.

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>fa
stboot oem idme bootmode 4000
... OKAY [ 0.203s]
finished. total time: 0.203s

C:\Users\name\Downloads\Kindle_Fire_Utility_v0.9.5\Kindle Fire Utility\tools>fa
stboot reboot
rebooting...
finished. total time: 0.000s
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
Okay. So the KF is still doing it's thing. It booted past the yellow triangle and I have a blank screen. Windows sees it as the Android ADB Interface, so that is good. I'll practice patience and leave it alone and not touch the KF for at least 15 minutes. :)

Edit:

After 15 minutes, and at a black screen, any recommendations, once I get to the 15 minutes. At least it's still recognized by Windows and the KF light is orange so at least it's charging and not draining the battery.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Mount your sdcard through the mount option in TWRP. Then transfer a different rom from your computer to your sdcard. Then go back and install it.

[Edit:] Try this rom: http://bit.ly/HXOaPh

In twrp, be sure to "factory reset", wipe system, wipe cache and wipe dalvik. (Before, not after installation)
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
Okay. So I'll drop the zip, then do a factory reset, wipe system, wipe cache, and wipe dalvik.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
You replied while I was editing my post the second time. Be sure that you only wipe before installation, and not after. Doing so after will produce the same results you are experiencing now.
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
Sorry. I'm too quick. :)
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
SUCCESS!!!

I actually ended up getting HellFire ROM to work and I'm going to give this a try for a few days. If I don't like it, I'll try CM9.

I want to thank you guys for help. I owe ya! ;)

My recommendation for other users, run fastboot commands when you are at the "Kindle Fire" screen where it appears to be "locked". That was my initial issue, then other issues sprouted from that, but maybe for current instructions/write-up's, there could be a note about that. And also doing the factory reset/wipe before installing a ROM helps, too. If there's anything I can do to help, please let me know. :)

Now to figure out how to tether the KF to my Galaxy Nexus...
[Kindle Fire Q&A, Help & Troubleshooting] backspacepc:
That's the fff boot screen
[Kindle Fire Q&A, Help & Troubleshooting] AndroidSparty:
Okay. Good to know. So when the triangle is up, I hit the power button to boot into twrp.
[Kindle Fire Q&A, Help & Troubleshooting] CaeloMius:
First and formost thank you for helping a nob out in any case : I tried to use kfu and selected to root my kf. In the process windows seems to have lost the connection with the kf and it is now stuck in boot loop.

Window recognizes the kf as an android phone in the device manager but when I use adb device command the list comes back blank. Can someone tell me whats wrong? Also if disconnect the kf now windows will probably not recognize it when I connect it again.
[Kindle Fire Q&A, Help & Troubleshooting] backspacepc:
What type of boot loop?
[Kindle Fire Q&A, Help & Troubleshooting] GoRabbit07:
closest to my problem that i have found so far.

i too have used the same first link Sparty used, then i went on to use the 0.9.6 (the most recently updated version) of KFU. i am very new to this scene right now, but i decided to delete what i had from that first site, then move on to what vashypooh put up. i go to install the drivers, and it says it cannot complete the device driver. it has a red X next to google, inc (winUSB) .. install failed (unsigned). any and all help is greatly appreciated. and if the issue has been resolved already, please dont hesitate to point me in the right direction.
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
http://xdaforums.com/showthread.php?t=1552547
[Kindle Fire Q&A, Help & Troubleshooting] akalostangel:
I am not a developer, the mother of a developer, and I'm not sleeping with a developer. But I did stay at a Holiday Inn Express last night...

Now that you know exactly how much expertise I have, I will give you the benefit of my experience with KFU and drivers. After uninstalling a previous Android device driver (phone), I had to use the .exe file located in the drivers folder to install the drivers for my kindle. When I try to use the .bat file, a window comes up that says something about "command 'and' cannot be recognized". I'd go into more detail, but it pops up quickly then goes away. I am using Windows XP, btw.

Do not try and use PnP to install the drivers OR have your Kindle plugged up when you manually install them. But you probably knew that already.

But hey, what works for me may not work for you. But you can always delete drivers if they are not working. "Unbricking" your Kindle is a little harder...
[Optimus One, P500, V General] Kanad:
Can anybody confirm what is a clean build for cm7.2 and for cm9?What should be wiped exactly? Is the procedure varies depending on the type and version of recovery being used?
[Optimus One, P500, V General] vlt96:
Clean BUILD is building from source;) I think you mean clean FLASH

That means in mounts and storage in CWM (recovery) you just wipe everything except SD;) and then flash:D

Seek the signature below the line;)
[Optimus One, P500, V General] Kanad:
Ya you are right it should be clean flash :)
[Optimus One, P500, V General] peter joe:
i don't know

---------- Post added at 01:52 PM ---------- Previous post was at 01:45 PM ----------

i want it
[Optimus One, P500, V General] vlt96:
????????????????????

Seek the signature below the line;)
[HTC Amaze 4G] redw04:
Greetings fellow Amaze users!

Seeing as ICS was just leaked for the Amaze, I feel like the next logical step would be to create an AOSP version of it. What I want to know is: Is this possible? If so, how long will it be until it gets released? I love ICS, but hate sense with a passion!
[HTC Amaze 4G] EclipzeRemix:
hello mate

these two roms are the closest to AOSP:

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

http://xdaforums.com/showthread.php?t=1624433
[HTC Amaze 4G] redw04:
That's perfect, I really just want to get rid of sense alltogether. I noticed that speed rom does have a lot of AOSP apps, however phone and contacts are still sense-ified.

Is there:

A) A way to change them to AOSP myself

B) A future update that will add them
[HTC Amaze 4G] Deleted member 3820412:
Unfortunately, due to wifi driver source code not being released, you have to keep bits and pieces of sense on GB. ICS, you will have to wait until the kernel source is released, hopefully they won't exclude the wifi driver source this go round.
[HTC Amaze 4G] sportsstar89:
Thats not necessarily true there is a way to hack around it but it is not ideal
[HTC Amaze 4G] Deleted member 3820412:
What do you mean by hack around it? As far as I knew, you couldn't get wifi data without some sense processes running to communicate with the wifi module. You can build a pure AOSP Build with working wifi? If you can, I would sure like to know what you are doing. :)
[HTC Amaze 4G] sportsstar89:
You fake the kernel version to match htc stock kernel and you hex edit out where the wifi driver checks for sense and it will load it up thats what max did
[HTC Amaze 4G] redw04:
Bump?
[Upgrading, Modifying and Unlocking] stusgs2:
hi all, new on this forum :) hoping some of you knowledgeable people can help me out!

i have a galaxy s2 GT - I9100 on tmobile in the UK, i was running latest gingerbread and finally they released ics. i tried to update via kies, but it hung on 0% for hours before failing and the phone went black with the yellow triangle and !, message about firmware issue etc. it failed when i tried the recovery code then due to a power outage my pc went off, i lost the recovery code. my phone will enter download mode (thats if my battery will charge, keep getting the low batt cannot download" message, and it gets really hot).

i have tried Odin, although i dont know my admin password so no luck trying to run it on that mode. it keeps hanging on boot.ini and the green bar up top doesnt even begin to move. ive left it for 4+ hours and it just drains the battery and dies or the process just fails. i am now in the position where i dont know whether or not my phone is charging, its just very very hot, sometimes it lets me enter download mode, others its just saying battery too low, cant download ( i dont want to try again unless i know the battery has at least SOME power in it...)

any advice or help would be much appreciated. i dont think updating to ics is going to work, i just want my phone working again, even on gingerbread, i know ill probably need the stock firmware and to start from scratch, i just have no clue what exactly to look for as theres so many different ones out there and i get lost :s i just dont want my phone perma bricked and be stuck on a contract for next 18 months with a piece of plastic only good for throwing at passing tourists.

thanks in advance