yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] orb3000:
.

Don´t flash a ROM that is not designed for your device.

Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.

Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
[Kindle Fire Q&A, Help & Troubleshooting] astro11:
I don't want to bother you with stupid threads and things like that, but I've used the search function on XDA and I'm still lost on this really small problem - my Kindle Fire is not being recognized anymore in ADB.

See, a long time ago (few weeks) I rooted my KF and installed Android Market, whatever. Never installed a recovery or custom ROM. Everything was ok until I tried to install TWRP using Kindle Fire Utility.

While trying to install, I got the famous "adbd cannot run as root in production builds". So I thought it was something with my drivers. Ok, then I installed the drivers that come with KFU - just to screw with everything. My Kindle Fire stopped being recognized by ADB.

I tried: (1) uninstall the drivers and install from KFU again. (2) uninstall the drivers and install the drivers I got from the video-tutorial (the famous one). (3) factory reset the kindle fire and do all the drivers install again. (4) hold the power button 900 seconds to reset the kindle fire and install the drivers again. (5) finally install the drivers on ANOTHER computer (running WinXP instead of Win7) and plug my factory reseted KF.

I gave up.

I don't know why my Kindle Fire isn't recognized by ADB on any computer at all. I thought it was my laptop, but then I tried the same steps I did at the first time using a Windows XP and no good. I don't know.

Can someone help me? Thanks a lot.
[Kindle Fire Q&A, Help & Troubleshooting] b63:
i think xp is the better decision for such things

you can try:

power down and disconnect kf

remove any old drivers: http://support.microsoft.com/kb/315539/en-us

remove anything with adb or kindle or unknown device

replug kf without powering it on (does it by itself)

install new drivers:

-choose browse my computer for driver software

-Then select have disk

-Then select browse

-direct to where you downloaded the usb driver

-Select ok and ok

or you can try this solution:

http://xdaforums.com/showthread.php?t=1430038
[Kindle Fire Q&A, Help & Troubleshooting] astro11:
Tried that and didn't work.

I'm going to wait a little more before using Linux, I really wanted to do this using Windows only.
[Kindle Fire Q&A, Help & Troubleshooting] b63:
in what status is your kf now ?

normally booting ? - stuck at whatever ?

at xp now ?

checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)

to run kfu with 6.2.2 you need the patched version:http://xdaforums.com/showthread.php?t=1458841

would put it to something like c:\kfu cause it don't like spaces in pathname

try running install_drivers.bat from kfu
[Kindle Fire Q&A, Help & Troubleshooting] astro11:
Right now my KF is normally booting into stock ROM and stock everything.

I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.

My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).

Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.

Thanks for your support.
[Kindle Fire Q&A, Help & Troubleshooting] b63:
xp will be the better choice cause you don't have to hassle with 32/64 bit drivers and the uac (user access control)

add it in another line

seems that the patched version (the whole thread) is deleted - you will have to do it by yourself - take the original from the dev section and:

http://xdaforums.com/showthread.php?t=1454913
[Kindle Fire Q&A, Help & Troubleshooting] astro11:
The issue persists. I've seen that other people are having the same issue. The device got "unrooted" by unknown reasons and then it's invisible to any adb. As I'm writing to you right now, I'm trying the adb on my brother's Ubuntu. I've tried other solutions using linux but without success.

I'm running out of options here.

I'll admit that I haven't tested the last link you sent, but I can't see how that can change the way adb works on my device. Anyway I'll try that tomorrow.
[Kindle Fire Q&A, Help & Troubleshooting] b63:
in the meantime br3 is out - if you use kfu you will have to use an updated run.bat: http://xdaforums.com/showpost.php?p=21749205&postcount=792

but you'r right - that will not change the communication

firekit http://xdaforums.com/showthread.php?t=1430038

is worth a try cause linux don't use drivers to communicate

only needs some entries which are included in firekit

maybe try an other cable ?

really running out of ideas at this point ...
[Kindle Fire Q&A, Help & Troubleshooting] chituoi:
I got the same problem:mad:.

If you can fix it, please show me how, thank you.

c:\KindleADB>adb devices

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

* daemon started successfully *

List of devices attached

c:\KindleADB>
[Kindle Fire Q&A, Help & Troubleshooting] WhoRuJudge:
Just a quick idea. Have you tried the attach the kindle to a different USB port? I had the same issue until I used a different port. The front ports on my desktop are totally fubar, but the port where my mouse was worked when 4 out of 6 ports did not. This for me is probably a hardware problem, but it may help someone.
[Kindle Fire Q&A, Help & Troubleshooting] Th3-Chronikk:
I am having the same exact problem as the OP and I truer everyway to root it and install the drivers but its still not recognized by adb
[Kindle Fire Q&A, Help & Troubleshooting] chituoi:
Its seems i should give up :(
[Kindle Fire Q&A, Help & Troubleshooting] sudogeek:
Similar problem with cm9, and fixed

I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)

Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and

./android update usb

./android update adb

Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.

YMMV, and this is on a Mac.
[Kindle Fire Q&A, Help & Troubleshooting] chituoi:
Push push push it
[Kindle Fire Q&A, Help & Troubleshooting] cheif_of_smoke:
tried all the steps. and still nothing. dont know what im doing wrong. starting to get pissed. any help would be great, thanks
[Kindle Fire Q&A, Help & Troubleshooting] chalicucu:
Save my KF

Could you help me to fix same problem with window. My PC alway, automatic recognize my KF as normal disk driver. I try to make a factory cab but not success :(.

Thanks.
[Kindle Fire Q&A, Help & Troubleshooting] omeganexusmx:
Edit android-path.sh

1. On my Mac I opened System Profiler, then checked Hardware > USB > and 'MyDeviceName' (for me its: LePan Tablet PC)

2. Opened this file with a text editor: /Users/MyName/.android/android-path.sh

3. Added a new line in this file with the tablet Vendor Id, for example:

0x22a4

4. Executed: adb kill-server

5. Executed: adb start-server

6. Finally adb devices is showing:

List of devices attached

0163AE9D0801F02C0C280002	device

:D
[Kindle Fire Q&A, Help & Troubleshooting] Arananthi:
Bricked?

I think I'm having the same problem, or at least a very similar one.

Using windows XP. I got the drivers working, plugged my kindle into the Kindle Fire Utility, and ran option 2, which seemed like it was the option to create a backup in case you bricked your kindle. It ran, showed up on the Kindle screen, and did it's thing without a problem.

Then, when the kindle rebooted, I got the yellow-triangle-fire symbol. It says 'press power button for recovery', but pressing the power button does nothing. Holding it down for a long time shuts the kindle down, but pressing it again brings it right back to the yellow-triangle-fire symbol.

So I uninstalled the drivers from Windows XP (as another thread mentioned). I now have two ways that I can think of to install the drivers. Using the KFU, I get the "unsigned drivers" shutdown even after I went into the Driver Signing menu and chose "ignore and install regardless".

The other option I have is to install the drivers that I downloaded manually -- the same ones that worked in the first place. Problem with that is that I go through the entire process, selecting the directory the drivers are in and whatnot, and the only thing that happens is I get an error that says "These drivers aren't the drivers for your hardware" or something similar to that.

So neither of my options allow me to actually install drivers for my Kindle Fire, and my Fire itself is in a recovery loop. All of the tools that are supposed to address the recovery loop require drivers, so I seem to be up a creek without a Fire.

Any ideas?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Okay, to enter recovery...When you see the yellow triangle, hold the power button until it turns orange then release. It shouldn't take more than 10-15 seconds. If you still can't get into recovery, reinstall it.

For your drivers...uninstall completely and delete them if you're using Win7. Then reinstall using one of the previous methods.
[Kindle Fire Q&A, Help & Troubleshooting] Arananthi:
The power button doesn't do anything when I push it. It stays bright green until the kindle fire shuts down. I'm not sure what "reinstall it" means, sorry, n00biness.

The drivers (winXP as mentioned) I've uninstalled, but I can't reinstall. One option says "unsigned drivers" and the other doesn't recognize the device as a Kindle and thus quits the install with a "this is not an appropriate driver for your device" message.

Thanks for trying, though! I appreciate your time and effort. :o
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
It should let you install the unsigned drivers, does it not?

Are you signed in as an Administrator or with administrator privledges?
[Kindle Fire Q&A, Help & Troubleshooting] Arananthi:
Yeah, that's the strange thing. I don't have any logons except the Administrator logon (it's a home PC), so I know I have administrator rights. I change the settings for unsigned drivers to 'ignore and install anway', but it still throws up the "unsigned drivers -- can't install" error. :(
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
That's strange, and outside of my realm for sure. I haven't used Windows since XP and I have only a small working knowledge of later versions.
[Samsung Epic 4G Touch] Shoulon:
I've Made this thread in par with the [Dev-only] ICS development only thread so that all questions,comments and or even THANKYOUS can be posted here. Please do try and keep this thread alive without any idiocy (spam). DO NOT post in the Dev thread u less u have actual development. It doesn't matter how argue-mental the post become as long as it still always is related to ICS. As long as everyone just stops making new threads about ICS.

You may spam ur ICS needs here. Enjoy.

I will update this op with any Information regarding our phone and ICS whenever it comes available.
[Samsung Epic 4G Touch] Shoulon:
Most recent information available.
[Samsung Epic 4G Touch] mkuehn10:
I thought this was the thread: http://xdaforums.com/showthread.php?t=1348832

Oh yeah, I forgot that one got closed. :)
[Samsung Epic 4G Touch] Vandam500:
ICS ICS, where art thou? :D
[Samsung Epic 4G Touch] LordJummy:
What can I do to help the devs working on this project?
[Samsung Epic 4G Touch] DevilStrider:
I'm starting to think his phone won't get it. Hell the old Droid got it and we have hardly anything going on for this phone.
[Samsung Epic 4G Touch] Shoulon:
According to someone of a dev level ICS is extremely close so just be patient.

As for you. Read my comment above Mr.negative. If ur running Cm7 or MIUI then u literally just hypocritically commented on yourself. (in a far fetched way) =P
[Samsung Epic 4G Touch] mkuehn10:
Also there are plenty of good ROMs in the dev thread.
[Samsung Epic 4G Touch] Freeroot:
I don't necessarily understand it. I've used ics and it's pretty good, but the roms we currently have in the dev section are really awesome. Yeah, ics has some great tweaks that I look forward to coming to this device, but I'm pretty content and happy with the current roms and development we have. Thanks to all the devs!
[Samsung Epic 4G Touch] Vandam500:
I'm sure ICS will be here. No need to show negativity. Just have patience ;)
[Samsung Epic 4G Touch] Will of fire:
Im sure they dont want to give us something half done. Wait till they have a stable build then they will drop it.

My guess now that chris41g will drop ics hes been aful quiet ;)
[Samsung Epic 4G Touch] DevilStrider:
Call me what you want. I have the money to get a pics phone. I just don't want it. I have ICS on my zoom. Also don't make a thread about discussion of ICS if you don't like hearing others opinions.
[Samsung Epic 4G Touch] DevilStrider:
That's how I feel. I'm on the blaze from and I love it.
[Samsung Epic 4G Touch] DevilStrider:
I'm talking about official release not dev. I can see them doing it but I just want to see if Samsung will come through.
[Samsung Epic 4G Touch] Vandam500:
I'm pretty sure they will release a ICS update for it. The community will more than likely release one first though.
[Samsung Epic 4G Touch] clamknuckle:
Samsung will have one, but it will have TouchWiz. But a lot of us want either pure ICS or a CM9 build, ya know?
[Samsung Epic 4G Touch] bubur_bewok:
The only reason im waiting ics for my epic is native otg support..:(
[Samsung Epic 4G Touch] pyrostic:
Otg? 10 char
[Samsung Epic 4G Touch] bubur_bewok:
Yeah..usb otg...
[Samsung Epic 4G Touch] Vandam500:
Huh? Lol...

Sent from my Epic 4G Touch
[Samsung Epic 4G Touch] ravizzle:
The cm9 music player is dope too, got it on my prime.

Sent from my Galaxy S2
[Samsung Epic 4G Touch] JohnCorleone:
Yeah, when you get a chance to fire up CM9, you are seeing ICS with extra goodies. Correct me if i am wrong but didnt someone at Rootz did get an Epic Touch donated for the specific purpose of getting that going?
[Samsung Epic 4G Touch] Shoulon:
dont they have 2 or 3 devs with the phone already though?
[Samsung Epic 4G Touch] T.C.P:
* points at koush... where's cwm at!?!?
[Samsung Epic 4G Touch] Eddiepapi:
Yes, Someone did. Heard there working on it.
[Samsung Epic 4G Touch] xlGmanlx:
I asked that question on the rootz thread and the TWRP thread and have been ignored
[Samsung Epic 4G Touch] Will of fire:
i flashed ics alpha on my driod incredible its not a big deal to me. I guess since i like Samsung and like touchwiz i dont mind. Don't get me wrong ill try it and flash it when its available. I'm just saying to get to hyped its not the best thing. :)
[Samsung Epic 4G Touch] S_on_my_chest:
There quite a few fantastic devs w this phone and trust me they almost have all the bugs for cm9 worked out!
[Samsung Epic 4G Touch] asteetva:
With or without 4g?
[Samsung Epic 4G Touch] globalninja:
I really wish i could get a dual boot/virtual box going to help out. Unfortunately I need my laptop for school though
[Samsung Epic 4G Touch] odub303:
Don't get crazy now. We don't even have 4g on cm7 for our device.
[Samsung Epic 4G Touch] iBustCh3rries:
Thats because there is only one dev working on it, and he isn't really a dev a much as a code patcher... Great work though I'm running bubby on my e4gt noand its pretty nice
[Samsung Epic 4G Touch] Epix4G:
partition your hard drive give it about 100 GB to be safe install mint and it will install grub 2 easy peasy .... Most newer versions of I Linux are easy to dual boot....right click on my computer in then manage and shrink hard drive first..don't fear the penguin
[Samsung Epic 4G Touch] JohnCorleone:
I am not doing this to piss anyone off...literally just happened...ICS 4.0.4 I believe only on NS4G. Odexed, new kernel, got it rooted, hopefully they worked out the kinks and its our turn next...
[Samsung Epic 4G Touch] JohnCorleone:
And a 3g speedtest....
[Samsung Epic 4G Touch] Dj21o:
Come on man stop doing this to us!!! I was/am still half tempted to trade this in for the Nexus S, but I know this bad boy will be 10x's better with .5" more on the screen. Not to mention this thing is FAST.

Sent from my GSII.
[Samsung Epic 4G Touch] Dj21o:
Sent from my GSII.
[Samsung Epic 4G Touch] Will of fire:
Nexus s radio is worse than ours.
[Samsung Epic 4G Touch] Dj21o:
Is that even possible? Lol.

Sent from my GSII.
[Samsung Epic 4G Touch] adma84:
I don't want to be mean, but this is completely useless for this thread. A lot of us are subscribing to this thread, and when you update us with speed tests on the new ICS on the NS4G, I have no idea what you are accomplishing. let's stick to discussion on ICS for ET4G. Thanks!
[Samsung Epic 4G Touch] JohnCorleone:
Nope, they are making progress with the Android OS and Android System bugs that was crushing battery which is why the ota was delayed. 4.0.4 they are in single digits instead of 25%. The battery issue is what's holding up the official for everyone
[Samsung Epic 4G Touch] JohnCorleone:
Here's an example... see the Android OS from older release 24%...that was from a full battery. Already in the 70%'s. Now here's a small sample (not fully charged battery at all but almost same screen on time...look at Android OS.. this is the problem being worked on for us all. Also, the Nexus radio is worse than ours so improvement for them is a good sign for us
[Samsung Epic 4G Touch] Dj21o:
Yeah the guy at my work has an extended battery on his evo (3500mah) and the bastard dies within 5-6 hours. I'd rather have a stable release than deal with no hardware acceleration lol.

Hey if it gets here soon that'd be awesome, I'm sure there is a reason for the delay.

Sent from my GSII.
[Samsung Epic 4G Touch] rayprobg:
So I am using this nexus as a way of getting an ICS fix but I am still using my ET as well just thought I would show everyone my battery stats too I mean this would not be good on the ET as the screen is bigger it would be a double whammie killing the battery.
[Samsung Epic 4G Touch] mazook98:
Now, battery life just has never been an issue for me: I've got chargers out the wazoo: home/car/portable/solar etc. , but is that really so bad?

Because you've got users all over the ET4G forums with examples very similar to yours (14 hr's on a slow but steady decline, basically) talking about how GOOD their battery life is....

So, I guess I'm asking, what kind of battery life is everyone really looking for?

["hip", "hip"]
[Samsung Epic 4G Touch] Danial723:
The battery life above looks damn good to me

sent from the near past
[Samsung Epic 4G Touch] rayprobg:
Well the razor Maxx is crazy long
[Samsung Epic 4G Touch] il buono:
With the battery that sucker is packing, it better be long :D
[Samsung Epic 4G Touch] T.C.P:
cm7 doesnt even have 4g :/
[Samsung Epic 4G Touch] anthony67:
So...color me dumb if you wish, but I don't understand what the big difference is between the NS4G and our device other than processor as far as hardware goes. I realize screen size is different blah blah blah........what I'm getting at is why is it so hard to get ICS on the E4GT when the NS4G already has it?? And yes.....I'm talking AOSP, no Whiz....I don't understand why it can't be altered and dropped right in....obviously the code has been written to get Wimax to work with ICS......

I'm not crying or complaining....just asking, developers are smarter then I am.....that's why I haven't put ICS on anyone's phone.....:confused:
[Samsung Epic 4G Touch] iBustCh3rries:
Dumb!

In all seriousness though in a Non-whining complaining or *****ing manner I too would like this answered if possible...
[Samsung Epic 4G Touch] JohnCorleone:
The Android OS getting fixed in 4.0.4 is huge! I really hope this opens the door for us. Its currently at the very bottom of my usage stats where before it was always 2nd after screen on time. I couldn't even fit the graph and screen % in pic because Android OS is at the bottom.

On a side note, I got someone's ET4G who flashed the international SGS2 ICS ROM to try and fix. The only place you can even tell its ICS is in the settings menu. Looks like CM9 is what we need to be pulling for...
[Samsung Epic 4G Touch] Danial723:
So how is that fix coming along?

sent from the near past
[Samsung Epic 4G Touch] Epix4G:
The difference is ics and gingerbread is huge ..... It's basically written in a different way with smali and back smali....there is not a easy way to port it..... It requires changing alot of files just to get it to boot .... It would be easier to port from sgs2 as it has exynos chip too but then it's gsm ....basically it's trying to get gingerbread drivers to work with ics .....we need a ics leak and it will begin to kick off.....
[Samsung Epic 4G Touch] Mu5ic92:
I havent seen any updates if at all development the last couple of days. Definantly a guess but maybe the developers banded together to get a ics rom atleast off the ground for us.
[Samsung Epic 4G Touch] JohnCorleone:
I need to find sfhub. I had that I9100SGS2 driver and now I can't find it. KIes loading driver didn't work. Time for coffee, and Google tracking down the SGS2 I9100 driver. If anyone comes across it, PLEASE PM me! TIA
[Samsung Epic 4G Touch] Epix4G:
pm's suck

I dont think pm's are working i sent it but didnt show in sent folder but here is link http://www.viceaster.com/2011/11/10/sgs2-i9100-guide-installing-driver/
[Samsung Epic 4G Touch] JohnCorleone:
That's the exact one I got it from first time but I couldn't get it earlier today! Thanks! Maybe I need more coffee!
[Samsung Epic 4G Touch] daniel4653:
Or a beer or two to relax lol
[Samsung Epic 4G Touch] dbaybay:
Not trying to ***** at all, just annoyed that Sprint has dropped an ICS ROM for the Nexus and CM9 has been ported to the Epic 4G, but we are still left behind :(

It's frustrating.
[Samsung Epic 4G Touch] daniel4653:
Just be patient bro :)
[Samsung Epic 4G Touch] Will of fire:
Touchwiz ftw!!!! Enjoy it be chase you know its not bad and once ics(cm9) hits you'll never go back.
[Samsung Epic 4G Touch] ccline84:
+1

I always seem to get the phones that lag behind development wise. It's so freaking frustrating. Especially when other people come into the store running ICS and my super phone is in the corner drooling with it's dunce cap on. All we can really do is wait, it's not like the devs have abandoned us. I know they're chomping at the bit to realease it as much as we are waiting.
[Samsung Epic 4G Touch] Indrid Cole:
Hey Corleone that will not work. The bootloader is corrupt and the USB port is locked out. Trust me Jtag is the only fix for that chics phone bro. Or playing dumb at her local sprint store.lol. Sorry for the bad news.
[Samsung Epic 4G Touch] jprovan1:
Sprint has nothing to do with CM9
[Samsung Epic 4G Touch] Indrid Cole:
If ya can't be with the one ya love. Love the one your with. Lol. Also does it not occur to you that all the phones getting Ports/ICS ROM are single core phones. IE. Dual core phones are twice as hard to get this **** running for them. Especially this phone. Sooo not bustin yer nuts or anything. Buut it's statements like that,that really piss off dev's bro. Think B4 you post.
[Samsung Epic 4G Touch] Epix4G:
Yes it does ....if we could get Samsung or sprint to release a ics leak ...cm9 would have everything it needs.... Much easier that way than to build the files and change drivers to make it work
[Samsung Epic 4G Touch] daniel4653:
I know that brilliant..... I was referring to sprint releasing ICS on nexus so "be patient" for sprint to roll it out for our phones.
[Samsung Epic 4G Touch] odub303:
Sounds a whole lot like *****ing to me. Fyi, check the dev forum