yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Go ahead and roll it back. Then...

In the install_drivers.bat that comes with KFU (right click, select edit), there is a line that says:

start .\drivers\dpinst64.exe

Change it to say:

start .\drivers\dpinst64.exe /lm

(obviously for a 32 bit system you would change the "dpinst32" line)

Save the file and run it with the Kindle Fire unplugged.

Next, open a command window and enter the following (you may have to run the command window as admin):

mkdir .android

Open your user directory and confirm there is a folder named ".android", then copy the "adb_usb.ini" from the Kindle Fire Utility folder into that ".android" folder. Plug your Kindle in, select "disconnect" and you should be able to send adb commands or use the KFU with no problem.
[Kindle Fire Q&A, Help & Troubleshooting] Loobster:
Nope.

I don't get a 'disconnect' option (I take it I should be seeing that on the Kindle Screen?).

I realize though that I omitted some information (sorry) that may make a difference. The KF I am using to connect at home is one that has already been rooted and has the bootloader and Jellybean installed. I guess I might get the 'disconnect' option if I still had the stock Kindle ROM installed.

I don't know why that would make a difference as to why the driver won't install though. I just get the same thing ..... Windows searches WU, doesn't find a driver, and reports driver not installed on the second Kindle item.

I have one item which is installed properly and called 'Amazon Kindle Fire' and is under 'Portable Devices' in Device Mangler. The one that has no driver is under 'Other Devices' and is also called 'Amazon Kindle Fire'. From what I remember of the installation on 32-bit Windows, it seems that this is the version that relates to ADB.

I am about ready to give up on this nonsense and load up a spare HDD with Windows 7 32-bit just for when I want to root these devices and do general tasks with them. I could just swap the HDD in when I need to. A pain, but I'm losing the will to live with this ridiculous driver issue.

Thanks for your help guys.
[Kindle Fire Q&A, Help & Troubleshooting] Loobster:
Ok, so maybe it's not Windows 7 x64.

I installed 7 x86 on a spare disk in the laptop, and it does EXACTLY the same thing, and I cannot use the KFU.

I have no idea what is different about my work Windows 7 32-bit laptop, but apparently it's the only computer I can get the drivers to install to, and get KFU to work on. I've tried four Windows 7 x64 builds and two Windows 7 x86 builds. Only my laptop at work, works.

<sigh>
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Yes, it would've been helpful to know this ahead of time.

Do you know what ROM is installed? Look under "About Tablet" in the Cyanogenmod or AOSP Version.
[Kindle Fire Q&A, Help & Troubleshooting] Loobster:
It's Hashcode's release, of 4.2.2.

Kernel Version

3.0.50+

hashcode@hashcode-UB #5

Tue Feb 12 23:04:41 PST 2013

Build Number

full_otter-userdebug 4.2.2 JDQ39 eng.hashcode.20130212.152604 test-keys
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Different ROMs and different recovery builds can have different hardware IDs. When you plug your device into USB, you need to go to the device manager and check the hardware ID of that particular build by right-clicking on the device and selecting properties. Under the details tab, there is a drop down menu...select "Hardware Ids". You should see something similar to the following:

USB\Vid_1949&Pid_0007&Rev_0216&MI_01
USB\Vid_1949&Pid_0007&MI_01

In the KFU drivers folder, there will be a file called "android_winusb.inf" that needs to be edited to accommodate the hardware ID listed for your particular build. Since you are on a 64bit system, you need to

add to

the Kindle section under "[Google.NTamd64]". For the above example, you would add the following to the "android_winusb.inf", and save it.

%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01

Your hardware ID may be different so pay attention to what you are doing. Then go back to the device properties, select the driver tab and update your drivers. From here you should be able to manually install the "android_winusb.inf" by selecting "choose what drivers to install", "Have disk", or however it's laid out on Win7. You may need to do the same for any new ROM you install and you may need to do it for custom recovery also.
[Kindle Fire Q&A, Help & Troubleshooting] Loobster:
I see.

So when a KF is flashed with a different ROM, it presents to the PC as a different hardware string in device mangler, even though it's the same physical device.

That makes sense now since I've rooted two different KFs on the work laptop without any issue, using the same [or very similar] ROM.

I guess that also means that if I attached a KF with a stock Amazon ROM installed, it may well just work fine. I don't know if it's possible to roll back to the stock Amazon ROM. I did take a backup with TWRP before installing the custom ROM.

I will editing the files with the new hardware IDs on the laptop at home and see what happens.

Thanks!
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Just keep your android_winusb.inf and append new hardware IDs every time you switch to a different ROM or device, then manually install it again.
[Kindle Fire Q&A, Help & Troubleshooting] Loobster:
It worked! Thanks a lot Soupmagnet. KFU sees the KF as online and all is well.

I learned something about driver installation and hardware IDs also.

Hopefully this thread will help others coming up against the same issue.

Had a scare tonight, my KF would not turn on! I thought it had failed right at the point when I had an answer. I did the holding down the power button for 30 seconds things, and it powered on with the next press of the power button.

Thanks again all who contributed to the thread.
[Kindle Fire Q&A, Help & Troubleshooting] [ImperialDev]JonesLabs:
I had the same trouble

But here is how I got it working- http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
[Xperia Arc Q&A, Help & Troubleshooting] Hckmit:
Hi guys i want to share some information who was useful for me with Xperia Arc S 12w07 :

Important : Dont make normal updates with SEUS ou PCC if your phone was unlocked by other tool, because you will brick the phone, you need to start using other firmwares, but ask for opinions first..

After Alejandrissimo unbrick my phone, the phone ask me to do update to new version, so i click yes to make thet update, and after 5 seconds gave me one error in update, so my phone was dead again with yellow triangle with one phone, so i talk to alejandrissimo again and he gave one file to fix the phone again with Flashtool, so i will share with you ok, but i think i already saw this file in other post..

Steps :

1º - Install Flashtool - flashtool-0.9.10.1 - http://xdaforums.com/showthread.php?t=1000012

1.1º - Google and find this file : " [Xperia Device] flashmode & fastboot driver bundle " and install all..

2º - Install all Drivers

3º - In flashtool be sure if the drivers already installed, sometimes the file install but in pc need to install more with the phone connected

4º - Select Flash Mode

5º - Put the fix file in folder firmware of flastool, and you can delete the other file x10 in the same folder you dont need.

6º - In " Program Files\Flashtool\devices\LT18 " you have this file loader.sin, when you try to flash if he give this error : " cant find loader_unlocked.sin ", then you need to rename the " loader.sin " file to " loader_unlocked.sin", and then flash again, and will work..

If was simple bick like my phone it will be fix it, maybe for other phones is the same, check the devices folder for the files and if you need to rename like i did...

Hope this help for some people ok..:good:

Now i need to update to new version of android, but i need to see what is the correct file to flash or i will brick my phone again..

Tks to Alejandrissimo again, he teach me to do that.. :fingers-crossed:
[Verizon Samsung Galaxy Note II] jpatt:
Possible?

Stock G1 .

Galaxy Vibrant w/SlimBean 4.1.2.

Stock Galaxy Note 2
[Verizon Samsung Galaxy Note II] imablackhat:
No
[Verizon Samsung Galaxy Note II] richii0207:
Yes it is, go to applications, then all applications. After that, find the app and select it...you'll see the disable option, that freezes the app.
[Verizon Samsung Galaxy Note II] thinkingbear:
Not quite the same as removing
[Verizon Samsung Galaxy Note II] richii0207:
... Because removing saves you a couple of megs?
[Transformer TF300T Q&A, Help & Troubleshooting] atermify:
So I just bought this and I love the look and feel of it, but I can't get it to work. All of the physical buttons (all three of them lol) work fine; the screen comes on fine..it just doesn't accept touches. But, weirdly, I left it alone for a while and let it charge, and it worked fine for about five minutes. Got to the part of setup where I would normally put in my account info, and the touch screen stopped working.

Is this possibly a defective unit?
[Transformer TF300T Q&A, Help & Troubleshooting] graphdarnell:
Sounds like a hardware problem that can only get worse. You should return it ASAP.
[Transformer TF300T Q&A, Help & Troubleshooting] atermify:
Just sent a message to Amazon Warehouse Deals. Waiting to see if I can get lucky and get a replacement (doubtful). Till then, I suppose I'll admire the beauty of what could've been :<

I'll update this post with their reply once/if I get one.

Edit: they messaged me back saying they would give me a full refund back for the defective unit. Me, being the impatient person that I am, will probably just turn around and just buy a new one from walmart.
[Transformer TF300T Q&A, Help & Troubleshooting] talatkhurshid:
I am Facing 100% same problem. I am using TF300 more then 6 months now but Yesterday Suddenly touch system stop working. If i left alone for 5 minute it s start working Good. I Delete all data and make factory Reset also.But problem same ,then 2nd time again i Reset Tablet and i try to not Update any apps and also i did not download any apps. it s start working Good . No problem at all but when i am going to install any application after installing any apps from Play store ,i am having same touch Problem . Is it Hardware Problem Or Software Problem ?

Please help me .plzzzzzzzzzzzzzzzzzzzzzzz .
[Transformer TF300T Q&A, Help & Troubleshooting] chuko303:
Dude I just got mine 2 weeks ago and I'm certain mine is defective. I get "ghost touches " all the time to. Downloaded an app to test the touch. Sometimes it's good. And sometimes it's tripping the he'll put put 4 fingers at the bottom of the screen. Then 2 blinker un top (no on touching it) just 2 weeks. I glad I didn't unlock it. I got mine of Amazon as well. Hate the bugs helllllaaaaaaaa wish they would be squash with an update but noooooo. Going to have to return it before it's too late. What do I need to do???

---------- Post added at 08:17 AM ---------- Previous post was at 08:16 AM ----------

Can't believe. Don't they test there devices good before they put in the box
[Transformer TF300T Q&A, Help & Troubleshooting] atermify:
All I did was send Customer Support a message stating that I had issues with it. Someone sent a message back with a link to a packing slip and just said I would have to take it to a ups drop off, which I'll be doing today.

Just go to your recent orders on Amazon and click contact seller.
[Transformer TF300T Q&A, Help & Troubleshooting] chuko303:
Thank you already did it. Ups will be picking it up tomorrow morning. Need to go print my order slip tho. They sent me an email right away they will send me my new one this week. Since I have bought it from them the 11th
[Transformer TF300T Q&A, Help & Troubleshooting] chuko303:
Hey I got one question. Will ups handle the package? ?? Like where it ships? Or can I just handle the tablet in its original box to the ups man with my order comirmation and they will take care of the rest?
[Transformer TF300T Q&A, Help & Troubleshooting] atermify:
If you take it to a ups store, they should be able to box it and everything, but if all you're shipping it in is the actual Asus box and handing it off to the driver..I'd be willing to bet he'd look at you rather funny. To be safe, I'd throw it in a small brown box and attach the shipping label.
[Transformer TF300T Q&A, Help & Troubleshooting] chuko303:
Shipping label?
[Transformer TF300T Q&A, Help & Troubleshooting] atermify:
Amazon should have had you print out a UPS shipping label for your return. Or hell, UPS might have given you one to print out their selves if you went directly through ups for the return and not amazon..
[Transformer TF300T Q&A, Help & Troubleshooting] chuko303:
Well I printed the return authorization the ups man will bring me a prepaid shipping label
[Transformer TF300T Q&A, Help & Troubleshooting] talatkhurshid:
I do not have any Warranty For tablet . Please some body help me. i am crying . do not understand this is hardware problem or software. If we can solve this problem with any Rom aur any other way please let me know. Thanksssssssssssssssss
[Transformer TF300T Q&A, Help & Troubleshooting] talatkhurshid:
Any Help ???
[Transformer TF300T Q&A, Help & Troubleshooting] atermify:
Its a hardware problem. I doubt flashing a new ROM would remedy it. But, I know little about this tablet as I'm still waiting for my replacement I just bought.
[Transformer TF300T Q&A, Help & Troubleshooting] chuko303:
I got my new one next day! Have to admit this one works great thanks Amazon. My stock web browser no longer force close.touch seems much more responsive going to give it a few weeks see how it handles. The previous one was messed up out of the box
[Transformer TF300T Q&A, Help & Troubleshooting] atermify:
+1 that's great. Hoping I could be so lucky.
[Transformer TF300T Q&A, Help & Troubleshooting] chuko303:
Could this become a problem in the near???

I lost wifi for about a minute out of nowhere kept giving me tht pop up. Just got it 2 days ago if i again start having problems with this one I'm just going to return it for a refund and get a brand i know n trust. Samsung. This tablets are not made well. Even when I hold it it cracks on me. Not well put together like I know Samsungs tablets are just as well made as my note 2. Bought this tablet thinking it was the best. Now it's all but buyers remorse. Rather pay an extra 100 to 200 if it meant my tablet will be well made and no problems. The little time ive had with this device and already messing up. Plain Stupid
[Transformer TF300T Q&A, Help & Troubleshooting] atermify:
Had mine for little less than a week now, and i must say im in love with it. Updated it to jellybean and its running incredibly. Hoping this love story continues for a while; thinking about buying a 64gb sdcard and the dock for it.
[Vibrant Android Development] skinzy98:
​

Features

Disclaimer:

I am not responsible for anything for anything that you do on to your phone by flashing this! You are responsible!

Based on JB 4.2.2 - Built from RootBox Sources

AOKP Features

CM Profiles

Per App DPI

Per App Tablet UI

Per App Language

OTA Updates - Goo Manager

Navigation Bar Colour

Lockscreen vibration option

Phone: Advance Phone Settings (Vibrate on Answer, Every 45 Seconds, On Hangup and On Call Waiting)

Phone: Noise Suppression

MMS: Message rate alerts (Modify SMS message limit for alert)

MMS: Fully Customizable MMS Theme

MMS: Soft Keyboard Type (Emoji, Enter to Send, Enter for a New Line)

Option to control cursor in text fields using volume keys

Home button call answer (Accessibility Option)

Variable size pattern lockscreen

RootBox Settings

RootBox Settings

LockClock (Chronus)

Launch Music app on Headset connection

Pie (Paranoid Android)

Option to disable sound when adjusting volume

Lockscreen Shortcuts (Paranoid)

Lockscreen Targets (CM)

Screen Security Features (Unlock options)

Expanded Desktop

Hardware Keys Remapping

Lockscreen Hardware Keys Remapping

Recommended Installation Steps

Coming from another Custom ROM:

1. Wipe Data/Factory Reset (This does not affect your Internal/External storage)

2. Flash RootBox zip

3. Flash JB GAPPS

4. Wipe Dalvik Cache

5. Reboot

Coming from Stock Samsung ROM:

1. Root Your Phone

2. Wipe Data/Factory Reset (This does not affect your Internal/External storage)

3. Flash RootBox zip

4. Flash JB GAPPS

5. Wipe Dalvik Cache

6. Reboot

How to upgrade RootBox versions:

1. Download RootBox update

2. Flash RootBox update

3. Flash JB GAPPS

4. Wipe Cache (Optional)

5. Wipe Dalvik Cache (Optional)

6. Reboot

​

Credits:

Bajee11 for creating the rom

Jrongi1 for helping to fix key layout and many other various parts in the ROM. Jrongi1 has also said that he will help me with porting the is ROM! Show him some love!

Aways for the amazing rom and for him giving me permission
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

I will try to port an update every weekend. If screenshots are needed I will post
[Vibrant Android Development] daworship:
Im downloading it now, but if you can , is this a stable rom for the vibrant since is a port? any bug or issue?
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

I've tested it on my phone and had no issues. It is stable in the i9000 section all I did was switch a couple files to make it runnable on the vibrant.
[Vibrant Android Development] gunks:
Going to give it a go today... Seen this ROM on the Nexus 7 but will try for the Vib first! :good:
[Vibrant Android Development] Mostdef:
going to install this new rom on my vibrant. ill let you know if i see any bug or issue. Thank for bringing the new rom in vibrant section.

---------- Post added at 11:52 AM ---------- Previous post was at 11:16 AM ----------

I notice that the volume is backward. I try to turn up the volume on phone button it turn down if turn down on the button it go up.
[Vibrant Android Development] mikka06:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

+1 for the volume. Headphones not working, also impossible to hear anyone when calling.
[Vibrant Android Development] Mostdef:
radio firm need to be change to KB5 or KA7. and on About Phone model number should be change for Vibrant. Also I recommend Odin to jfd before flashing this new rom. I try dirty flash and try your method on Op I still get some error. But when I odin it back to JFD before I flash this newest rom running smoothly with no error. Will do more further testing
[Vibrant Android Development] gunks:
That's easily done by yourself and is a personal preference. KA5 is just fine for me.

Not really necessary at all. I was on CM10.1, did a factory wipe and a system format and everything is fine.

You might want to mention that you're using the Semaphore kernel ( :good: ) in the OP.

Edit: And +1 with the volume.
[Vibrant Android Development] Mostdef:
making a call doesnt work. I have flash KB5 and KA7. I have signal but cant connection to a caller at all
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

So with odining back to stock did it fix the volume problem? All that is is key layout. See when I tried it I flashed semaphore for vibrant and it rendered the home button as the back button and vice versa so I reflashed the rom and it fixed it. I will try to do a new port tonight and include the semaphore for vibrant to see if that works

Another problem may be that when I was porting the ROM,I didn't change the update-script so it still has i9000 commands. I will also try that
[Vibrant Android Development] Mostdef:
either odin or dirty flash still get the same problem with volume. Most important is that I cant make a call at all.I check my imei it all there fine.
[Vibrant Android Development] gunks:
So I flashed the latest version of the Semaphore kernel (2.9.12) and it corrected the volume but switched my hardware home button to back and vice versa. Just a heads up.
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

Yeah I'm gonna try to do that after I get done with my paper
[Vibrant Android Development] Mostdef:
can u make a call?
[Vibrant Android Development] gunks:
Yeah... seems to work.
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

I tried it my first time and it worked but it could just be that I tried it immediately after I flasged
[Vibrant Android Development] Mostdef:
home button isnt working and also when I go in setting and tap the display to change my brightness then i hit the back button to go back to setting section it exit right away back to home screen.

Gunk I flash the newest semaphore i now have call and text working .Thx Bro!

Skinzy...you should change the Radio firm to KB5 in your next build. Alot of Vibe owner use KB5 or KA7. I find KB5 on better battery life some use KA7 for better signal. Will more further testing
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

So the newest semaphore for vibrant fixed it? That's really weird. Are the keys fixed?
[Vibrant Android Development] xriderx66:
To fix key layout, which is usually caused by kernel

go to /system/usr/keylayout/aries-keypad.kl

change to

key 115 VOLUME_UP WAKE

key 114 VOLUME_DOWN WAKE

key 102 HOME WAKE_DROPPED

key 116 POWER WAKE

reboot
[Vibrant Android Development] Mostdef:
what about BACK button?

everytime i hit the back button it exit right away on any app i used like dolphin browser that i want to go back but it exit right away
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

That was what I was talking about but I'm gonna try to make a new port
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

I was looking at the usr key layout on cm10.1 and they look the same as rootboxs stock layout
[Vibrant Android Development] skinzy98:
http://www.mediafire.com/download.php?rrgggv87kn88q2h new port
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

I don't know how its working right now I haven't flashed it yet
[Vibrant Android Development] Mostdef:
Going to test this now. I'll let you know.

Still the same back button on the hardware key went EXIT
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

Yeah I noticed that when I flashed it last night and I think I've figured out what to do. When you flash our kernel go into the keylayout then and change it to what it was when it was on the i9000 kernel
[Vibrant Android Development] Mostdef:
Take your time no hurry to rush till it all fix
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

So my plan didn't work. I am still working on it though with a couple other people. Although, the other ROM I ported didn't have this problem and I'm trying to figure out why. I may pull the airieskeys.kl from the cyanaosp and put it in this one
[Vibrant Android Development] samsgun357:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

I flashed latest semaphore kernel and it fixed the vol key mapping and I had no in call volume which was also fixed.

id est quod est
[Vibrant Android Development] skinzy98:
yeah i know the newest semaphore fixes the volume mapping but it doesnt fix the home button and back button. i had jrongi1 help me and he fixed the problem:p
[Vibrant Android Development] skinzy98:
Re: [PORT][RoM][UNOFFICIAL][4.2.2] Vanilla Rootbox 4.2.2 v2 [PIE][Per App DPI]

New build that works great. http://www.mediafire.com/download.php?f7uwny282ci4a3t

And this does fix the key layout!