yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Q&A, Help & Troubleshooting] sdfyhpromotions:
Ummm, I thoroughly checked the file and it turns out there was actually a few different pieces, BUT I wiped it clean, and copied/pasted what you had written, restarted my computer, and still this:

"cj@cj-VPCEE23FX:~$ adb kill-server

cj@cj-VPCEE23FX:~$ adb start-server

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

adcj@cj-VPCEE23FX:~$ adb devices

List of devices attached

cj@cj-VPCEE23FX:~$ lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 004 Device 008: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless keyboard/mouse

Bus 002 Device 002: ID 0408:03f5 Quanta Computer, Inc.

Bus 003 Device 002: ID 0bda:0186 Realtek Semiconductor Corp.

Bus 001 Device 033: ID 1949:0006 Lab126 "
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Did you reboot after making changes to the Udev rules?
[Kindle Fire Q&A, Help & Troubleshooting] sdfyhpromotions:
Edit: Yes, now my kindle flashes on and off when plugged in (still the stock boot logo), but still isn't recognized...

Here's my "51-android.rules":

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

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

Heres my "adb_usb.ini":

"0x1949"

I thought I was moving in the right direction, but I'm starting to get more confused with each passing hour lol...
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
The flashing on and off is a sign of a dead battery, which puts you in a tough spot because you need access to fastboot to fix it. Installing FFF 1.4 will fix the battery issue. You can keep trying whatever you can to get fastboot working or you can get a factory cable. The factory cable powers the device directly rather than just charging the battery.

http://xdaforums.com/showthread.php?p=20317299
[Kindle Fire Q&A, Help & Troubleshooting] sdfyhpromotions:
Not good... Ummm, can't I just charge it from the wall with the original charger???
[Kindle Fire Q&A, Help & Troubleshooting] Amilmac:
If there is no problem for Sdfy and Soup, i'll join this thread because im in the same situation/point as Sdfy and soupmagnet is helping me in other thread :) (for not "double" posting)

Tanks!

Soup, reading various post/guides i can infer im stuck in Fastboot mode (as you told me), my only progress is Device manager see my KF as android device...

Amilcar
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
See if you can access recovery.

fastboot oem idme bootmode 5001
fastboot reboot

You can try it but it probably won't work.
[Kindle Fire Q&A, Help & Troubleshooting] franciumgoesboom:
I am in a similar position with no ADB.

I'm trying to fix this device for someone that had a failed root so it might need its own thread.

KFU says:

ADB Status: Offline

Boot Status: Unknown

Windows 7 64

ADB confirmed working-My Evo3d works

With Kindle and off, Dev manager sees Android ADB interface

Driver: Google, Inc 4.0.0.0

0x1949 is in my .ini

Unable to boot into recovery:

Yellow triangle

Push power button til it turns orange

Hits Kindle Fire screen

Reboots

Yellow triangle

Reboots

Yellow triangle

Kindle Fire screen

Boots

My next step was going to buy a Factory Cable but wanted to see what others can think of before I tried that. That and I don't want to spend money on a device that isn't mine.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Reinstall your drivers.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Listen people! If you have a problem, start a new thread. It's hard enough keeping track of one conversation per thread. No one wants to scroll back three pages to find out what's going on with the original poster.
[Kindle Fire Q&A, Help & Troubleshooting] franciumgoesboom:
Sorry, in the past when i've started new threads people yell at me to go search first. Similar issue so I thought I'd start here.
[Kindle Fire Q&A, Help & Troubleshooting] tazfanatic:
welcome to xda that is normal so you are damned if you do and damned if you don't..........people need to realize this
[Kindle Fire Q&A, Help & Troubleshooting] sdfyhpromotions:
Agree with you both :p lol...
[Kindle Fire Q&A, Help & Troubleshooting] forest1971:
Hi:

For guys who is still struggling with adb driver, the website below should help.

The webmaster is also an XDA member but does not often post. His site helped me a lot when I start to mess with my KF.

There an easy way with video and a hard way if the first way does not work.

http://www.jayceooi.com/2011/12/29/how-to-install-kindle-fire-adb-usb-driver-video/

http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/

Hope it work out for you well.

cheers.
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
For those of you trying to get adb to work...

On Windows...

a) Make sure your device manager is showing "Android Phone -> Android Composite ADB Interface" when you connect your KF to the computer. There must not be an exclamation point or question mark on the icon next to the name. If you see one of those, there's a problem with the device drivers and it has to be fixed before you do anything else...

http://xdaforums.com/showpost.php?p=23747671&postcount=2

Use KFU's installer first. If that doesn't work, use the manual install method described in the above post.

b) Your user directory must have a ".android" folder with an "adb_usb.ini" file inside it that has "0x1949" on a line by itself. The EASIEST way to do this is to use the following two commands on the command line...

mkdir %USERPROFILE%\.android
echo 0x1949 > %USERPROFILE%\.android\adb_usb.ini

These two commands are fairly foolproof, so you might consider doing it even if you are sure the initialization file is there already. You might get an error with the first command if that directory exists... that's not a problem. The second command will overwrite the adb_usb.ini file if it already exists.

If neither one of those things helps... right-click on the device, select properties, and look at the hardware IDs in the details tab. You should be seeing...

USB\VID_1949&PID_0006&REV_0216&MI_01
USB\VID_1949&PID_0006&MI_01

On Linux...

You can get around all the udev rules, setting up groups, adding yourself to the group, permissions, sudo, etc. if you just switch to the root user first. Then the only other thing you need on your system is "/root/.android/adb_usb.ini" with "0x1949" on a line by itself. First set the password for the root user...

sudo passwd

It will ask you for your own user password. Then you will have to set/confirm a new password for the root user. Then switch to the root user...

su

and enter the root password you just set. You should get a hash prompt indicating you are the root user. Now you can create the adb_usb.ini file in the appropriate directory...

mkdir /root/.android
echo 0x1949 > /root/.android/adb_usb.ini

Then...

Run the "adb devices" command and see what you get. If you don't have adb in your path, you'll want to cd back into the directory with the adb binary first.
[Kindle Fire Q&A, Help & Troubleshooting] Amilmac:
caso irpuroo5

Kinfaus, the problem is those (me included) who tried to root the KF and got stuck in some point (fastboot or similar). Reading a lot of post i realize that for us in this situation "someting" (tech skills needed here, lol) happends with ADB and our device.

I read advices about let the battery drain, do things in "this exact secuence", etc, but i think the "adb issues" is the Achilles' heel of the "unbricking process" :)

I´ll keep trying again all the advices... Im stuck in "The device can not start" (Error code 10).

This post put me in the right track, but the error code 10 continues:

http://xdaforums.com/showpost.php?p=21720811&postcount=41

Tanks in advance for your advices!
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
make one of these no more driver issues http://xdaforums.com/showthread.php?t=1670405
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
No offense, but the actual problem are users who are completely vague about what's actually going on with with their devices and don't actually want to try out the proposed solutions to fix the issue. I've suggested a number of possibilities for you to try out. You've provided no indication that you've even attempted to follow those instructions. The post I suggested for you to read gives you a step-by-step guide on what to do if you see a "code 10" error. Have you tried it? If it failed, then describe in explicit detail what happened and how it failed. Did you check the hardware ID?

You should have already looked at these things and provided more information on what you saw. If you force your helpers to repeatedly ask more questions, it's going to take longer to fix and it will be more frustrating for everyone involved. In my experience, questions that provide the most information upfront will get the most/best help out there. You are failing in this regard...

You said, "Device manager see my KF as android device..." in your previous post. I will guarantee you that device manager doesn't show "android device" on your list. Provide the exact, specific information if you want help.

http://xdaforums.com/showthread.php?t=1644970
[Kindle Fire Q&A, Help & Troubleshooting] forest1971:
thanks

Hi Kinfauns:

You are a Genius. Your guide on adb driver and guide for beginner is extremely helpful!

Many thanks!
[Kindle Fire Q&A, Help & Troubleshooting] Amilmac:
Non Taken, because I´ve tried various proposed solutions (im sure the problem is located in the interface betwen the keyboard and the chair, lol). Tonight i´ll try to post a detailed description of my situation (with images). far far away from my intentions is to making waste of your time..

Sorry for my "argentinian english" and tanks in advance :)

Amilcar
[Kindle Fire Q&A, Help & Troubleshooting] Amilmac:
So, here is mi actual situation about my "ADB issue" :)

1) .android folder contains adb_usb.ini with this info:

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.

# USE 'android update adb' TO GENERATE.

# 1 USB VENDOR ID PER LINE.

0x1949

2) Kindle section of android_winusb:

;Kindle Fire

%SingleAdbInterface%	= USB_Install, USB\VID_1949&PID_0006

%CompositeAdbInterface%	= USB_Install, USB\VID_1949&PID_0006&MI_01

%SingleAdbInterface%	= USB_Install, USB\VID_18D1&PID_0100

%CompositeAdbInterface%	= USB_Install, USB\VID_18D1&PID_0100&MI_01

%SingleAdbInterface%	= USB_Install, USB\VID_1949&PID_0001

%CompositeAdbInterface%	= USB_Install, USB\VID_1949&PID_0001&MI_01

%CompositeAdbInterface%	= USB_Install, USB\VID_1949&PID_0001&REV_0216&MI_01

3) Device Manager:

4) KFU Status:

Im planning 2 curses of action:

1) Im letting battery drain an see if work for me one of the advices in the forum.

2) making a USB Linux to try "the linux way..." of Soupmagnet (a friend of mine is making for me a "factory usb cable")

Any advice are welcome!

Amilcar

PD: I hope this post is little less vague for Kinfaus :)
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
OK... the hardware IDs given by the device manager shows that your Kindle Fire is in fastboot mode with the stock bootloader. This is not an "adb issue" because you cannot use adb in fastboot mode. Your device drivers are not installed properly and Windows is loading the wrong driver.

The adb_usb.ini file is irrelevant because fastboot doesn't care about this file. Don't let your battery drain out. You don't want another problem piled onto this one. You can try to make a Linux bootable USB drive, but I'm fairly sure you can get your Windows situation straightened out. You don't need a factory cable because you are already in fastboot mode.

Again... you must get your device drivers working. In fastboot mode, you should see "Android Phone -> Android ADB Interface" (without the word "Composite" in the name).

http://xdaforums.com/showpost.php?p=23747671&postcount=2

Follow the directions under "What can I do if the drivers won't load?" section to install the drivers manually. You must use the parts of the instructions in parenthesis "()" to install the fastboot drivers. This is critical to getting them installed properly.

When you get the "Android Phone -> Android ADB Interface" to appear in the device manager, use the following command...

fastboot -i 0x1949 getvar product

and it should answer back with "product: kindle" as the output. When you get that far, read this...

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

to learn the fastboot commands you will need to fix whatever problems you were having originally.

This...

could very well mean that your device (like Amilmac) is also in fastboot mode. The "1949:0006" VID:PID pair is used for both the stock bootloader as well as several different ROMs. You'd have to look at...

lsusb -vd 1949:0006 | grep bcdDevice

If it returns "1.00", that's the stock bootloader and you are in fastboot mode... look at my response to Amilmac for a fastboot command to confirm.

You don't really need a factory cable because you have FFF installed. Your bootloader is working fine and your recovery, believe it or not, is also working just as it should. The "problem" is that you don't have a custom recovery (TWRP or CWMR) installed. You still have the stock recovery installed. The stock recovery is designed to run a set of commands and automatically reboot the device normally... this is what you are seeing happening when you push the power button to select recovery and it shows the "kindle fire" logo before rebooting itself. It also sounds like your system software is broken too. You need to stop the temporary fastboot countdown in FFF (Yellow triangle) and flash a new recovery of your choice so you can use it to reflash a system update. You won't get adb working until you have a working recovery or system software.

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

http://xdaforums.com/showpost.php?p=23747804&postcount=3
[Kindle Fire Q&A, Help & Troubleshooting] Amilmac:
Kinfauns, i followed EXACTLY the secuence in "What can i do if the drivers won´t load" but still shows error code 10. Here is an image of my desktop and you can see the instructions in the background :D

Uploaded with ImageShack.us

The KF is freezed in start KindleFire Logo (with no animation)

Any advice?

Amilcar
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
A "code 10" error in the device manager is really a generic error and doesn't tell you a whole lot about what the problem might be. I would suggest downloading the drivers again, reinstalling, rebooting, doing a dance, etc. to see if anything helps the situation. Otherwise, I think Linux might be in your future.
[Kindle Fire Q&A, Help & Troubleshooting] pichettet1:
I don't know if this will help, but I was stuck in a similar place when rooting. My device manager did not give me a code 10 but KFU didn't recognize my device.

What I did was install the drivers, restart my KF, then plugged it in. At this point my device manager showed the android device. I right clicked on the sub menu (android adb) and updated the drivers using the search for new drivers option. At that point, KFU recognized my KF and I was able to complete the root process.

Not sure if that will fix the code 10 but it should fix the problem stated above where KFU was 'waiting for kindle...' or swhatever the specific wording is.
[Kindle Fire Q&A, Help & Troubleshooting] Amilmac:
Yeap, "doing a dance" is a clasic course of action in windows, i´ll try it and then, start "the linux way". (I allready dowloaded Ubuntu ISO to try the soupmagnet way)

I´ll post my progress...

Tks

Amilcar
[Kindle Fire Q&A, Help & Troubleshooting] Jagmar:
I have done absolutely everything I can on my laptop here (since my desktop is doa due to power supply issues) and for the life of me cannot get ADB to see my kindle fire.

I've got device manager saying that its seeing my "android phone" using the "Android Composite ADB Interface". I've also got the adb_usb.ini with "0x1949" tried it with uppercase 'X' and lower case 'x'. I've tried using the fastboot commands, and adb commands. I've done everything possible that I have been able to search upon this website and many others. I just want to root my kindle to put ICS on it.

Anyone able to help me? I'm almost ready to shoot this darn thing.
[Kindle Fire Q&A, Help & Troubleshooting] Amilmac:
Kinfauns, my KF its ALIVEEEEEE !!!!!

The solution? I tried your advices in a 6 diferents PC´s. It was a humble pentium with a WinXP and like an act of magic, error code "10" didn´t show!!

Then i used a conservative strategy (i need to get courage again to try finishing the rooting):

Fastboot -i 0x1949 getvar product ---> a beatifull "Kindle" showed

Fastboot -i 0x1949 oem idme bootmode 4000 -------> Ok

Fastboot -i 0x1949 reboot --------> Ok

Kindle fire logo WITH ANIMATION and...... HAPPYNESSS !!!!!

Tanks all for the Help !!!!, i will gater all the info to try again the rooting.

"Happy Amilcar From Argentina"
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] n0stalgia:
The US government is implementing a Wireless Emergency Alert system similar to that found in other parts of the world. It will provide "congestion-proof" point-multipoint broadcast emergency notifications to mobiles, and alerts can be localized up to the individual cell tower--very useful.

The ATT website lists the SGSII as compatible with it, but not the Skyrocket... I can't imagine why. Can anyone confirm? And also, does which ROM you have matter for support?

ATT info:

http://www.att.com/esupport/article...mercial+Mobile+Alert+System)#fbid=-vsqOvX1SRv

General info:

http://www.washingtonpost.com/blogs...hone-near-you/2012/05/18/gIQAqPBrZU_blog.html
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] cschmitt:
Probably uses cell broadcast with a special app on the phone.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aceownstheworld:
I'd imagine almost any current phone, especially a smart phone, will have it. If they are just now implementing it, that means it passed through whatever hoops it needed to and I'm sure the government contacted carriers and device manufacturers awhile ago.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] n0stalgia:
I know it's different than cell broadcast though, but are those ROM-dependent?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] cschmitt:
CMAS is implemented using Cell Broadcast channels 4370 - 4383, so any CB capable device, such as the skyrocket, can be configured to receive the alerts. I checked the MMS.apk from the lastest ICS leak (UCLE2), and it does contain CMAS specific settings and UI components that allow the alert types to be configured and displayed, but the CMAS Settings menu is currently hidden in this build.

My guess is that it will be supported in a future build.

If you're having trouble sleeping, read this: COMMERCIAL MOBILE ALERT SYSTEM
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] SharpnShiny:
http://www.androidauthority.com/sony-xperia-neo-arc-pro-ics-update-rollout-90591/

Very high praise from these guys! Well done Sony! :)
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
Libs database

Based on XWLPF base.

This is to collect info on what each lib is connected to and if its safe to remove.

Got the idea from this thread, so please if you have info please post and I will update it.
[AT&T Samsung Galaxy S II SGH-I777] cxdz810:
Hello, have a question,

what do we gain with removal of libs? does it reduces battery consumption?
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
Thanks MikeyMike & Howtomen for the contribution.

This is mainly for devs/chefs I wouldn't mess with it if you don't know what this is. ;)

It can cause a bootloop and unable to get you back into your phone without reinstalling your rom.
[AT&T Samsung Galaxy S II SGH-I777] ChefAnt:
The term chef is used incorrectly on XDA. A chef is one who leads, inspires and creates. A cook is one who follows directions per the chef
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
:rolleyes:
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Seriously? If you are inspired and create your own rom you are a chef.
[AT&T Samsung Galaxy S II SGH-I777] MikeyMike01:
Is that not what he said?

Sent from my SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
I read it as he's saying all people who build roms are cooks not chefs.
[AT&T Samsung Galaxy S II SGH-I777] MikeyMike01:
I read it as people who only follow guides aren't doing much of anything.

How that's relevant to this thread is beyond me.

Sent from my SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
Found this...

https://dl.dropbox.com/u/20447007/NOTICE.html

Inside the AT&T version, not sure if that was in other bases and I missed it.
[Xperia Arc Android Development] eryen:
Kernel based on cobrato's thread

Kernel.sin unpacked and added CWM options.

Thnx for

1. cobrato - unpacked his kernel to compare

2. FXP - for the CWM

3. Doomlord - for the sysinit and bootrec script

4.1.B.0.431 LT15i Arc

http://www.mediafire.com/?z26c90ilj969j69

4.1.B.0.431 LT18i Arc S

http://www.mediafire.com/?t75gje77zciea6x

4.1.B.0.587 LT18i Arc S

http://www.mediafire.com/?oejctr39e28lcxw

4.1.B.0.587 LT18i Arc S Stock WiFi Modules Flashable zip

http://www.mediafire.com/?3j5gd579bpe2lkx

11.09.2012

Added 4.1.B.0.587 LT18i kernel.

This kernel support swap natively
[Xperia Arc Android Development] elroysk:
init.d supported?

and only arc?
[Xperia Arc Android Development] eryen:
As i write in first message.

All scripts copied from cobrato's work. That should work, if original one works.

In ramdisk, some strings define phone as LT15. But i'm sure about it will work.
[Xperia Arc Android Development] eryen:
Arc S kernel with CWM added
[Xperia Arc Android Development] Ritmasz:
my phone doesn't charge anymore with this kernel...
[Xperia Arc Android Development] guille26:
Thanks for the warning!
[Xperia Arc Android Development] eryen:
Interesting, because of mine connected to usb and charging right now.
[Xperia Arc Android Development] trenje:
Mine charges fine, too.
[Xperia Arc Android Development] heihei_ivan:
my phone also doesn't charge with this kernel

however, i spotted something strange. i own an arc LT15i, but i flashed the ftf of LT18i in order to have an extra 40MB in /data. but the kernel with cwm i flashed was for LT15i.

i don't know if this is the cause of the problem. anyway, my phone charges again with stock kernel in the ftf.
[Xperia Arc Android Development] X-Droidinary:
I'm currently using this kernel and usb isn't working. How am I supposed to flash a different kernel if I can't connect to my pc? I can't even charge my phone now.

Sorry jumped the gun a bit fastboot and flash mode works.
[Xperia Arc Android Development] BlackMN:
It work, but i dont see difference with cobrato's kernel ?
[Xperia Arc Android Development] dylanicb:
Same problem, doesn't charge, LT18i :(
[Xperia Arc Android Development] eryen:
If you choose MTP or MSC mode manually, i'm sure your problem will be resolved.

Settings=>Xperia=>Connection=>Usb Connection Mode

Uploaded v2 kernels.

Fix MTP, Mass Storage, adb settings.
[Xperia Arc Android Development] Fra31:
If I click arc kernel link it makes me download the arc s kernel. Is it the same? Sorry for my english!
[Xperia Arc Android Development] eryen:
Sorry about that. I will fix link in a hour.
[Xperia Arc Android Development] buzzinkeegs:
is this for unlockd bootloaders only ?
[Xperia Arc Android Development] Dark Fable:
Can you incorporate a few governors into this kernel ? Like smartassv2 and intellidemand ? :D
[Xperia Arc Android Development] tomatos:
Please correcting the LT15i V2 link. The LT18 and LT15 link are same. :(
[Xperia Arc Android Development] eryen:
Renew Lt15i kernel link.

Sorry about wrong link.
[Xperia Arc Android Development] Fra31:
Don't warry !! Thanks :) great work!!!