yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Hedied4me:
Windows 7 32bit, these are the drivers I installed : http://xdaforums.com/showthread.php?t=2544410

They installed correctly. Ive rebooted my laptop and Fire several times since then. If you didn't see my previous post I wiped my fire so I currently have no OS. Everytime I shut down, or restart recovery or into bootloader TWRP always asks if I want to install SU which I always say no. Not sure if that's helpful. I really hope I can fix my Fire somehow. I'm super broke so I cannot afford another device, which is why I use the Fire which was a gift from my Dad.

I simply cannot understand why my laptop will not recognize the device. I've tried different cords and USB slots all to no avail. I always see the yellow triangle in device manager.

Sent from my Virgin Mobile CDMA HTC Desire 601 zara_cl
[Kindle Fire Android Development] b.huss2:
Right click on it, update driver, manually find the adb one in the list. This is not uncommon and easy to fix, but it ain't gonna just fix itself.
[Kindle Fire Android Development] dokie80:
I usually use driver from KFU. I M on win7 32bit too
[Kindle Fire Android Development] Hedied4me:
That's what's really weird is I did try this. Right click, select update driver software, select browse my computer for driver software, click the browse button, select desktop, select folder named 2ba63011a0a0d0f35e001696677ec92a825cb, select folder kindle_fire_usb_driver, click ok. So that is the folder where the actual extracted or unzipped driver is located but when I select next it says "Windows was unable to install your Amazon OtterX. Windows could not find driver software for your device". Allowing windows to search for the driver brings the same response.

Edit: I did just notice when my fire is plugged I see a Removable Disk (E: ) although I cannot open it. Not sure what that means.

Sent from my Virgin Mobile CDMA HTC Desire 601 zara_cl
[Kindle Fire Android Development] b.huss2:
Yes windows never finds it automatically. Don't browse for drivers, select from list of drivers and find the adb one. If you've ever installed adb drivers then they should be in the list.
[Kindle Fire Android Development] Ixthusdan:
Did you install the drivers as admin? When you say you cannot open E, what does Windows say? Can you start an admin shell and look at E?
[Kindle Fire Android Development] Hedied4me:
Thanks again. So I select Browse my computer, then Let me pick, then Android USB Devices. Then Im given a list of devices to choose from: My HTC, T-Mobile myTouch 3G Slide, or T-Mobile myTouch 4G. Im sorry for asking you guys hold my hand as I do this but I'm still unsure what to select. Ive never really dealt with driver issues before.

Sent from my Virgin Mobile CDMA HTC Desire 601 zara_cl

---------- Post added at 09:06 PM ---------- Previous post was at 08:49 PM ----------

Yes I installed the drivers as administrator. When trying to open E it says Please insert a disk into Removable Disk (E: ). How does one start an admin shell? Thanks

Sent from my Virgin Mobile CDMA HTC Desire 601 zara_cl
[Kindle Fire Android Development] Ixthusdan:
Windows knows something is there but cannot talk to it because it has the wrong driver. It is reading it as a flash drive. Download kfu, and update the driver again. It may be a poor download. You cannot allow Windows to automatically select because it does not know what to do.

I went thru this with 8.1, and it turned out to be a bad USB cable. A cable can charge but not talk.
[Kindle Fire Android Development] Hashbang173:
Would there there be an advantage to making system and cache F2FS?
[Kindle Fire Android Development] Hedied4me:
Ok, if select let me pick the driver and select ADB I'm given a list 3 devices, none which are the kindle. I did redownload and reinstall the driver using administrator. What is KFU, is that the driver we're talking about? Thank you
[Kindle Fire Android Development] sd_shadow:
KFU=Kindle Fire Utility see Kindle Fire Utility v0.9.9 download, unzip, run install drivers.bat
[Kindle Fire Android Development] Hedied4me:
Thank you soo much. This seems to be what I needed. ADB seems to work. When I type adb devices my kindle finally shows up, but says its unauthorized which keeps me from doing adb push. I've searched some but don't see how what I should do next. Any ideas? Thank you again
[Kindle Fire Android Development] dokie80:
Try running the command with administrator right?
[Kindle Fire Android Development] sd_shadow:
right click on command prompt icon>run as administrator
[Kindle Fire Android Development] Hedied4me:
I did not at first, but even as administrator (says so at top of cmd window) it still reads unauthorized. I'm running it as its trying to boot (no os). Perhaps I need to be doing this in TWRP or mounted or something?
[Kindle Fire Android Development] sd_shadow:
Yes kindle needs to be in twrp recovery to push file to it
[Kindle Fire Android Development] Hedied4me:
Again thank you who responded and helped me very much. I had almost given up hope. Now to try out some AICP [emoji1]
[Kindle Fire Android Development] Hedied4me:
I'm so happy with my new kindle. Its awesome I have just one last question (hopefully last) and perhaps this belongs in the AICP rom thread. I noticed upon flashing that rom that there is usually not much ram available even with no extra apps installed. I remember on the cm nightly (non otterX) rom you could do some fstrim command to make things a little speedier. Does that still apply to otterX? I use a version of gapps called XSgapps that keeps it really minimal, installs almost no apps except only what's needed. Is there anything I can do to increase free ram? Thank you again for all your help. Ill stop spamming this thread.
[Kindle Fire Android Development] Hashbang173:
How much ram do you have free?
[Kindle Fire Android Development] Hedied4me:
Right after installation of the rom, I let it settle for a few minutes before installing any apps. And one thing I noticed is there was only 15 MB of ram available, and performance was slightly sluggish. Perhaps the rom needs to just be restarted a few times and more time settling. What I remember when I had the previous nightly cm is that it was sluggish. Hash then mentioned the fstrim command and all of a sudden it was extremely snappy again.

Edit: And after I did restart a few times and flash newest su and and adblocking, installed some apps, uninstalled some things via Titanium, and greenifyed some apps I was able to see about 50-60 free ram but still slightly sluggish.
[Kindle Fire Android Development] Hashbang173:
Hmm I'm getting 128mb free even though I have a few apps open.
[Kindle Fire Android Development] Hedied4me:
Well that's strange. Are you running AICP? Ill play around some more and see if it continues. Does the fstrim command work on otterX?
[Kindle Fire Android Development] sd_shadow:
guessing yes,that [MENTION=4630246]joshuabg[/MENTION] is using his own rom
[Kindle Fire Android Development] lovejoy777:
no fstrim command doesn't do anything anymore.
[Kindle Fire Android Development] dokie80:
I read about Xsgapps, but said that only support up to 4.4.3? Although one post said that any 4.4.x should work.

Aicp is 4.4.4, probably should use Aicp gapps?

Cmmiw
[Kindle Fire Android Development] Hedied4me:
Ya you are right. I was having issues where system ui was constantly force closing. That stopped when I used a different gapps.
[Kindle Fire Android Development] Hedied4me:
You know as happy as I am to have my kindle running again I am still a little uncertain. I know the device is fairly only now but I am still seeing slight lag and sluggishness since installing OtterX. Yesterday I installed SlimKat 6.4 (w/ Slim gapps) and I see a little over 100 MB free ram (300 used). I just remember cm before updating to OtterX (and after fstrim command)) being super snappy. Perhaps I'm just an idiot though lol. Feel free to ignore me at this point. I am happy to have it working again after a few days of uncertainty.

Sent from my Amazon OtterX
[Kindle Fire Android Development] dokie80:
FYI, U can revert to otter if you want to. Just saying, just in case u didn't know.

For me, the overall exp is similar.

Anyway don't remember if Cm ROM is over clocked by default or not, but slim is not. Use app to overclock it if u want. One of the app is trickster mod.

Also, check out 777Kernel thread if u want to try out smartassv2 cpt governor. See if it make things faster or not.
[Kindle Fire Android Development] Hedied4me:
Did not realize I could revert. Thanks for info.

Sent from my Virgin Mobile HTC Desire 601 cdma zara_cl
[Kindle Fire Android Development] sd_shadow:
Yes, I have several times. It can be a little tricky. You need to revert back to kindle Partitions with the bootloader options, flash an old otter or blaze twrp, wipe all partitions in twrp, reboot to twrp, mount sdcard or push a rom to sd card, install, reboot to rom. should be good.
[Kindle Fire Android Development] driz:
had a hell of a time with drivers. prior to the change to otterx i could adb push in twrp (windows 8.1 x64) after, the device name changed to kindle otterx and i couldnt push anymore.

i ended up installing a different adb driver in windows 7 and that resolved the issue for twrp adb and fastboot.

When i ran emmc fix, i got this error

stage1 and stage2 errors on setting bootsize. it ended with a success, but i wonder if it's a false success... any thoughts?
[Kindle Fire Android Development] sd_shadow:
Was emmc broken?
[Kindle Fire Android Development] Roger W:
Just did the conversion last night for the first time and it worked great, thanks!

This was also the first time I was able to use the Encrypt Tablet security option, which makes me feel better about syncing work mail with it. For the last year or more, TWRP is said to have supported mounting encrypted /data to re-flash ,by supplying a password, but I couldn't get this to work (going to Mount and tapping Data does nothing). Any tips on how to not have to do a full wipe when I want to update the ROM?
[Kindle Fire Android Development] sd_shadow:
To my understanding the emmc fix is for devices "which were running a CWM recovery built from the initial 3.0 kernel back in May 2012. That kernel was not patched for MMC_CAP_ERASE, and on our emmc chip it caused a wear levelling bug which basically made the device unusable"-http://xdaforums.com/showthread.php?t=2413453

unless that describes your device, the emmc fix is not for you.
[Kindle Fire Android Development] thedarksavant:
Don't wipe just flash. I use CyanDelta and it works fine.
[Kindle Fire Android Development] Roger W:
I tried to flash even the simple zip to tag the device as a Nexus, and the flash failed because it couldn't mount /data.

My understanding is that I have to manually mount it, and it should prompt me for the decryption password, but it doesn't do that.
[Kindle Fire Android Development] thedarksavant:
Sorry, I didn't understand the full context of your question. I'm not sure how to flash updates with an encrypted /data partition.

That's probably something you should take up in the TWRP thread.
[Kindle Fire Android Development] dokie80:
AFAIK, mounting function on twrp for OtterX doesn't work. Have to push via adb.
[Kindle Fire Android Development] Roger W:
Hi, I know I can't mount it on the PC. I can adb push my update to /sdcard fine, but after it's there, the flash fails because TWRP can't mount /data locally. the generic TWRP thread has people saying that this now (past year) works with encryption in general, so maybe there's something specific to this version/platform of it.
[Kindle Fire Android Development] shuvabrata:
Touch screen issue

Hi All,

I have been fairly busy of late and hence have not switched on the Fire for a long time. I am currently running OtterX with May 7 build. (android 4.4.2)

The touch screen is not responsive at all. And whatever i try to do, it come drags down the notifications from the left upper side. And it contnues wherever i touch. What's going on? Any idea?

Please help. It's a bit urgent. I am going on holidays and wanted the Kindle Fire to on handy with some books and movies.

Thanks,

Shuvabrata
[Kindle Fire Android Development] thedarksavant:
I notice weird touch behavior when plugged in. Have you tried not plugged in?

Otherwise you may want to retry the download and rewipe.
[Kindle Fire Android Development] mikeric:
Is anyone else having issues with lag, my Kindle is almost unusable. No matter what I am doing it lags really bad.
[Kindle Fire Android Development] Hashbang173:
What rom are you running, I'm running AICP Linaro build and I'm not getting any lag.
[Kindle Fire Android Development] mikeric:
I'm running cm11, just updated to 8/1 nightly and it seems a little better now.
[Kindle Fire Android Development] OMGLOLetcetc:
So, I got to Step 2 where I placed the recovery zip on the 'SD Card'. It copied over, but wasn't showing on the kindle screen. I rebooted and now I just get the new "Kindle Fire" screen repeatedly turning on and off. Any thoughts on how to fix this?

Edit - Disregard. I figured it out. I extracted the .img from the zip and pushed it via ADB. Sorry for the wasted space!
[Kindle Fire Android Development] sd_shadow:
press the power button once, select recovery mode with long press

---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------

may need to power off, by pressing power button till light turns off, then power back on.
[Kindle Fire Android Development] OMGLOLetcetc:
I was able to push the recovery via adb.

Thanks so much for keeping this device alive a little longer.
[Kindle Fire Android Development] sd_shadow:
Yes, the sd card is wiped in the process, that's why the instructions say to push with adb
[Kindle Fire Android Development] mattmejia:
wtf everytime i try to install otterx in the first step and doesn't work
[Kindle Fire Android Development] sd_shadow:
This step?

adb shell "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin"
adb shell "dd if=/dev/block/mmcblk0boot1 of=/sdcard/boot1.bin"
adb shell "dd if=/dev/block/mmcblk0p1 of=/sdcard/xloader.bin"
adb shell "dd if=/dev/block/mmcblk0p2 of=/sdcard/bootloader.bin"
adb pull /sdcard/boot0.bin
adb pull /sdcard/boot1.bin
adb pull /sdcard/xloader.bin
adb pull /sdcard/bootloader.bin

did you install kindle drivers?

did you install sdk or download adb.exe files?

does this

adb devices

get a response like 123456789 recovery
[Kindle Fire Android Development] mattmejia:
yes, yes, and i dont think i have sdk involved and i get the response 0123456789ABCDEF recovery
[Kindle Fire Android Development] sd_shadow:
ok that's good, so try

adb shell

then

dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin

then

dd if=/dev/block/mmcblk0boot1 of=/sdcard/boot1.bin

did you watch my video? [YouTube] OtterX ROM/TWRP/Bootloader [2014-05-08]
[Kindle Fire Android Development] mattmejia:
Still the same
[Kindle Fire Android Development] sd_shadow:
which is what no response or an error?
[Kindle Fire Android Development] mattmejia:
i just still have old bootloader
[Kindle Fire Android Development] sd_shadow:
those command don't change the bootloader, they back up special files that can not be replaced if wiped

---------- Post added at 12:22 AM ---------- Previous post was at 12:20 AM ----------

did you watch my video?
[Kindle Fire Android Development] mattmejia:
yes i did but bootloader doesn't chnge
[Kindle Fire Android Development] sd_shadow:
what are the current TWRP and bootloader versions?
[Kindle Fire Android Development] mattmejia:
twrp 2.60

bootloader v1.4a
[Kindle Fire Android Development] sd_shadow:
so you downloaded otterx-u-boot_v2.05.zip

531 kb not 234 kb

verified md5;462dee51b484c32bc8632a9aff66a085

copied to sd card

do not unzip

reboot to TWRP

installed

rebooted
[Kindle Fire Android Development] mattmejia:
still nothing
[Kindle Fire Android Development] dokie80:
Try posting screenshot of the screen, when first boot (kindle fire logo / bootloader) and recovery (twrp).

I got a feeling u mixed up bootloader with recovery?
[Kindle Fire Android Development] sd_shadow:
you could give more details, when you install or flash you will get some results, post them
[Kindle Fire Android Development] mattmejia:
i know what im doing. i followed the video. should i restore to factory settings?
[Kindle Fire Android Development] dokie80:
Great.

And no, factory setting only affect ROM. Will not matter if ur problem is bootloader or recovery.
[Kindle Fire Android Development] sd_shadow:
I'm guessing your current TWRP is corrupt, try flashing a different twrp.img in bootloader

like openrecovery-twrp-2.2.2.1-blaze.img

verify md5:e6183f4c6043f2c6a0d519d9f660ee98

place in adb folder

type code but don't press enter

fastboot flash recovery openrecovery-twrp-2.2.2.1-blaze.img

reboot, at bootloader press enter

then

fastboot reboot

select recovery mode in bootloader
[Kindle Fire Android Development] mattmejia:
Still nothing i dont know what im doing wrong
[Kindle Fire Android Development] sd_shadow:
Still nothing, is right.

What happened? Details
[Kindle Fire Android Development] mattmejia:
I now have the different twrp but it won't update the bootloader.. Should I just restore my kindle to factory settings and than do this?
[Kindle Fire Android Development] sd_shadow:
That will not help, probably couldn't restore stock, if you can't even install a bootloader.

---------- Post added at 06:14 AM ---------- Previous post was at 06:10 AM ----------

Try installing bootloader fff 1.3

---------- Post added at 06:20 AM ---------- Previous post was at 06:14 AM ----------

download u-boot.zip

unzip

verify u-boot.bin = MD5: 928ae401d91963e1cb8f4dae6ca9519b

fastboot flash bootloader u-boot.bin
[Kindle Fire Android Development] mattmejia:
Ok now it changed the bootloader
[Kindle Fire Android Development] mattmejia:
Ok so I decided to install bootloader via adb and twrp via adb and they both worked but now I can't push the cm 11 rom to my kindle
[Kindle Fire Android Development] sd_shadow:
Does adb devices command still work?
[Kindle Fire Android Development] mattmejia:
Nope.
[Kindle Fire Android Development] vbdss:
Hey [MENTION=4243514]Hashcode[/MENTION] grea job, apparently the eMMC bug fix works

I used it, but know i cant get Fastboot to recognize the device, on windows device manager, the id of the kindle is USB\SET_ADDRESS_FAILURE

What can i do?

thanks
[Kindle Fire Android Development] lovejoy777:
[MENTION=4182895]vbdss[/MENTION]

hi mate i got mine up and running:) and i too had nothing working.

hash and i had to use the firekit to boot his bootloader over usbboot. heres how.

Power off and unplug from usb (15 sec hold of button) then run the fk script (sudo ./fk) which opens the terminal menu, but do not select anything yet, then open /root/firekit folder and swap the u-boot.img with hashes new one (needs renaming 1st) then go back to the firekit menu term and type usb_i then Tab to auto complete, then enter when you see waiting for omap, short the pin (and keep it shorted) and plug in usb cable. Note: "each time you run the fk script it replaces the files in /root/firekit (took me ages to work out why 1 time it would boot fff then the next 2.03").

if it boots get ready to activate the emmc fix. good look mate. im sure it will work. I have proved these things are solid. mine took a battering and wouldnt even fire up and it is still good running kitkat. Hashcode is a genius "all hail Hash":)

---------- Post added at 06:31 PM ---------- Previous post was at 06:25 PM ----------

P.S Hash's bootloader will work its just getting it flashed & booted with no fastboot thats the hard bit
[Kindle Fire Android Development] vbdss:
[MENTION=4410674]lovejoy777[/MENTION]

Thank you for the help, will try later

But isnt supposed to the new bootloader enter usbboot without shorting the pin?

I was able to run the eMMC fix, and on the end it said to install the recovery using fastboot but the device isnt reconigzed at all after the fix.

The thing is i installed the otterX 2.03 bootloader using the zip file provided by hash on the official thread using TWRP2.7.0.1 but after running the EMMC fix, Windows doesnt recognize it anymore

Enviado de meu XT1033 usando Tapatalk
[Kindle Fire Android Development] lovejoy777:
Sorry dude just reread your post. "I used it".

mine is still playing up with adb etc. have you tried issuing fastboot with twrp 2.3.3 or lower installed as mine works fine pre that but not after?? still a mystery (use usbboot to flash , i have two terms open 1 with fastboot commands "waiting for device" and 1 with usbboot "waiting for omap) when usbboot boots the bootloader i have fastboot working so the fastboot commands work that way. ..
[Kindle Fire Android Development] vbdss:
After using the eMMC fix from otterX bootloader your device was being recognized by the windows device manager?

Can i flash a recovery using usbboot? Because it seens the only thing that will work in this case

Enviado de meu XT1033 usando Tapatalk
[Kindle Fire Android Development] lovejoy777:
dont use windows but ubuntu couldnt see it. use the firekit and second term like i mentioned above
[Kindle Fire Android Development] vbdss:
How do i install a recovery img using usbboot? Usbboot flash recovery recovery.img?

Enviado de meu XT1033 usando Tapatalk
[Kindle Fire Android Development] lovejoy777:
fire kit will install twrp and bootloader.

---------- Post added at 03:30 AM ---------- Previous post was at 03:29 AM ----------

its in the options
[Kindle Fire Android Development] muiriddin:
Thanks Hashcode!

My kindle fire was definitely acting wonky so after reading up on emmc corruption, and then doing some backups I decided to try it. My kindle is now booting a rom!

Somewhere I must have missed that I need to do a complete wipe after rebooting into the newly installed recovery after doing the emmc fix. Once I got past that one, I appear to have a completely reformatted and clean (and now hopefully no longer wonky) device!

All of your efforts at keeping my kindle relevant are greatly appreciated!
[Kindle Fire Android Development] vbdss:
So you just installed the bootloader, run the eMMC fix on the bootloader options and then installed fine a recovery using fastboot?

[MENTION=4410674]lovejoy777[/MENTION] usbboot would work on a virtual machine?
[Kindle Fire Android Development] muiriddin:
I backed up what I could, installed OtterX, and ran the eMMC fix. When it finishes it asks you to fastboot your recovery back (it got wiped during the process). I did that, booted into recovery, wiped every partition on the device with the newly installed recovery and then adb pushed the rom I wanted and installed it. Then rebooted...

All in all it took me at most 1/2 an hour to transition from a partially corrupt device to something that booted up a rom. My kindle fire would boot into recovery before I started this, so my initial installation of OtterX was fairly easy (get an un-corrupted version of the otterX zip file onto the device and flash it). If your device can not boot into recovery at all, the initial installation would probably be harder than what I had to do.

The shasum check HashCode has in the installation saved me since the first two attempts at getting the OtterX zip onto the device resulted in a corrupted zip file.
[Kindle Fire Android Development] vbdss:
I don't know what happened on my, I installed it and ran the eMMC fix, which took only a minute or so, then after it the device isnt reconigzed on Windows device manager, adb or fastboot doesn't work because of it, and now all I have is a device with a working bootloader, but that is it, can't do anything at all but change the options on the bootloader.

Are you using Windows or Linux?

Enviado de meu XT1033 usando Tapatalk
[Kindle Fire Android Development] muiriddin:
I am using linux. Previously I was using windows and the driver hell it does with android devices caused me to shift to a dual booting setup with linux whenever I want to do android dev stuff. Windows worked fine as long as I was developing for only one android device.