yashsingh1/xdaforums huggingface dataset:
[Kindle Fire General] Os_A:
Otter-X vs. Otter-X-F2FS

I was on Otter-X and plain vanilla CM11 ROM.

I moved to F2FS-partioned user data and flashed Hashcode's first 4.4.3 ROM.

There was a significant lag increase and some images in Google Play went awry.

I turned on ART and that made the ROM unusable. So I took this as a prompt to revert back to non-F2FS otter-X, did it and flashed same ROM (but non-F2FS)/ And guess what? The speed and smoothness is back and even the Google Play graphics are back.

I have no idea why this happened but that's what I experienced.
[Kindle Fire General] damystica:
Please use OtterX ROMs only! Make sure you follow his instructions carefully. And why did you turn on ART when Hashcode noted that it's VERY BUGGY!?!?!? *facepalm*

Again, please make sure you are using OtterX bootloader, OtterX TWRP and OtterrX CM 11 5.28.14!
[Kindle Fire General] Hashcode:
Thank you for the feedback. F2fs is still very beta. And I have more changes coming.
[Kindle Fire General] SchmidtA99:
Boot Problem

I have a problem maybe someone can point me to the right direction on fixing. I'm familiar with rooting/adb/etc.

I rooted and installed cyanogen mod 4.2 a while back with a twrp on it. I was reading about otterx and wanted to try it. I went through the otterx steps and was at the part where you wipe the partitions and adb the rom you want on your phone. The power went out at my place (transformer blew from someone crashing into it). My battery was almost full (90 some percent). So i thought nothing of it and I would finish it up when we got power back. So I went to bed.

In that time my battery died before I got up. Now when I start up my kindle fire I get a white kindle fire logo. Then it goes to the cyanogen mod bootup logo. Which I know will never go anywhere because the partitions have been changed. Both the Kindle Fire Utility and Unbrick utility do nothing. My device shows up as an Android Composite ADB interface in device manager. I'm running Windows 8.1.
[Kindle Fire General] sd_shadow:
looks like this?

.

or

.

.

if like first just press power, select boot to recovery
[Kindle Fire General] SchmidtA99:
I imagine the first picture is "kindle fire" in white. And I can press the power button or hold the power button and nothing happens.
[Kindle Fire General] sd_shadow:
this better?
[Kindle Fire General] SchmidtA99:
That is what I have. Except at the bottom it doesn't say anything.
[Kindle Fire General] Hashbang173:
Did you start up your kindle through plugging it in the charger, if you did, just hold the powerbutton down for a while after unpluging the cable until the screen goes off. Think you have to hold it for about 30 seconds.
[Kindle Fire General] sd_shadow:
have sdk installed? if not copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, and fastboot.exe

from KFU (Kindle Fire Utility v0.9.9 folder >tools) to c:\adb (create a folder named adb)

download otterx-u-boot_v2.05.bin

verify md5 checksum

copy to c:/adb

connect kindle fire, power down

open command prompt

cd\adb

fastboot reboot-bootloader

turn on kindle

should reboot to fastbootmode

in command prompt

fastboot flash bootloader otterx-u-boot_v2.05.bin

fastboot reboot

should be able to see 'press power to open bootmenu' option

press power select recovery boot

if it boots to twrp do the wipes and continue steps, if no bootmenu options or does not reboot to twrp, post how far you got.
[Kindle Fire General] SchmidtA99:
Thanks

Thanks guys. Got it working and got the otterx pacman rom installed. So far noticeably quicker then the cm rom I had on there for a while.
[Kindle Fire General] Jersey846:
Unfortunately my first gen Kindle Fire kicked the bucket before I was able to try this out. Wanted to try it since I first heard about it too.

Sent from my Moto X
[Kindle Fire General] Lickenleon:
Help!

Hi dude!

I got my Otter become Otter X with TWRP 2.7.1.0, installation step by step as the guider and every things ok

Now in my Advance Wipe menu, it's have 5 Partitions:

Davik Cache, Data, Internel Storage, Cache and System

is this nomal? Cause after i flash the newest rom CM11.0/SGT7 F2FS (2014-06-05) my Google Play alway force close

still try for ext4 rom and it's the same

in screenshot [MENTION=4243514]Hashcode[/MENTION], his internal storage have total space 6.0GB but i only have 5.6GB
[Kindle Fire General] Ixthusdan:
Partition count is normal. I have not had Google Play fc, but which did you use? For twa_priv, I use the signed file from January. gapps-kk-20140105-signed.zip. My store shows lo-Rez images for apps which twa_priv says is due to some settings which he will change in the next build. The fc may be due to this, but I am not sure. Did you do a complete wipe and use ADB to load your files? Twa_priv's current rom is only fir f2fs, and cannot switch to ext4fs. Later builds may do that, as He bases his rom on Hascode's work.
[Kindle Fire General] Lickenleon:
Thank you. Yeah, i use gapps-kk-20140105-signed.zip too, push file using ADB, everything clear cause i fomat all partition, try for latest f2fs rom and Google Play FC, re format all partition to ext4fs and flash older rom, till using 20140502 otterX and every thing OK, still have some bug when running apps but acceptable, looking for later builds :)

re: how can i upgrading to newer build, dirty flash like other or have to start from first step by fomat internal storage partition?
[Kindle Fire General] lovejoy777:
i wipe system then flash rom and gapps then wipe both caches and reboot
[Kindle Fire General] Ixthusdan:
Hashcode has made his latest rom flash to either f2fs or ext4 data partitions. If you change formats, you will wipe that partition. Since otterx and f2fs are beta, I am wiping every time I change roms. I have tested every f2fs rom.
[Kindle Fire General] Rianon:
Just moved to OtterX & F2FS. Not only all working well, but working even faster.
[Kindle Fire General] darwin_deathcat:
Me too! (2.05 otterx, and SGT7 4.4.3 ROM). Thanks to Hashcode for keeping this device current! With this update it's finally like a "real" tablet - stable, fast, and USEFUL! :)
[Kindle Fire General] yattaro:
It appears I am having a minor WiFi problem. I have a hidden SSID at home and therefore have to type my information manually (no biggie). When I tap "connect" it simply produces a toast saying "Failed to save network." I have tried wiping all partitions and fixing permissions - still to no avail! Help please?

Edit: rebooted again and suddenly it started working. Go figure.
[Kindle Fire General] Os_A:
With TWRP 2.7.1 and twa_priv's SGT7 4.4.4 and Banks minimal GAPPS everything runs smooth with very minor quirks (sometimes Wi-Fi is slow in connecting and very rarely it takes some button pressing persistence when awaking the KF from sleep). Battery drain is a bit higher though but that's good price to pay for all the benefits.

No FCs, no SoDs and a lot's of space for apps. Cool.
[Kindle Fire General] dokie80:
common issue on all CM11 afaik. I use an app "WiFi Manager", seems to be better at saving wifi info. but once you successfully saved all wifi network that u use, u probably wont need this. the hardest part is to save the wifi info at the first time.
[Kindle Fire General] yattaro:
Thanks for the info. I guess the other thing you can do is keep wpa_supplicant.conf backed up. The life of a frequent flasher is a rough one.

Sent from my 56k Refrigerator.
[Kindle Fire General] Lickenleon:
Problem with Location

I'm using Hashcode rom 20140608 and got problem with Location, i can turn on with hight accuracy mode but it's not work, maps, android device manager .... Does it nomal ?
[Kindle Fire General] dokie80:
Try update to newer? Just saw a post in Sgt thread that location was fixed?
[Kindle Fire General] Hashcode:
location issues should be resolved. now if only we had otterx nightlies..
[Kindle Fire General] damystica:
Go away, Otter!

When will that happen and Otter be damned, Hashcode? :victory:
[Kindle Fire General] bobcat131:
Nightlies Here

http://goo.im/devs/loosethisskin/otterx/cm-11.0
[Kindle Fire General] Ixthusdan:
I do not think twa_priv has nightlies on Goo. In fact, his latest rom is found at d-v, as listed in his dev thread.
[Kindle Fire General] bobcat131:
These are not nightlies, right. But they are put up about twice a month or so. Are twa_priv and loosethisskin the same dev?
[Kindle Fire General] :
I guess...... I think loosethisskin changed username to TWA_priv
[Kindle Fire General] calgator:
Stock 6.3.3 with Bootloader v2.05?

With apologies, I just noticed this thread after following the Development thread (where I haven't yet earned posting rights) for the past few months. Catching up on the early discussion, I'd like to throw in an unpopular vote for a dual-booting capability. This would only be an optional choice in case anyone is willing to sacrifice space for a bit of flexibility.

Mainly, this is so I can watch Amazon Prime videos on my KF. In the pre-OtterX days, I ran a modified version of eldarerathis's dual-boot bootloader that gave the primary ROM most of the resources and a stock 6.3.x unrooted alternate ROM a very small set of resources (only 250 MB for userdata and 128 MB for cache).

I started playing around with Hashcode's v2.05 bootloader, seeing if I could make it work in a dual-boot manner. Sparing the details, the current status is that I've discovered that even with the "Amazon" layout, I can't get my previously working alternate 6.3.2 ROM to boot. In fact, I can't even get a primary 6.3.2 ROM to boot in the primary partitions with the v2.05 bootloader. The KF turns off before any 6.3.x splash screen images are shown. (I know it's off because I have to long-press the power button to get it to turn back on.)

As a side note, I was able to get my old alternate ROM version of the Energy CM9 ROM to boot in the alternate slots with my "hacked" v2.05 bootloader in Amazon partition mode, so I think the bootloader mods themselves are at least close to being correct for Amazon mode.

With that limitation, any work towards the ultimate goal of an OtterX 6.3.x implementation seems to be dependent on getting the Amazon 6.3.x working with the new bootloader.

I'm curious if anyone has any ideas on the 6.3.x issues, although I do realize that not many folks may care :D.

Oh, and [MENTION=4243514]Hashcode[/MENTION], please accept my apologies for bugging you with a couple of PMs -- as I said above I just now noticed this thread as I usually read the Development discussions.
[Kindle Fire General] damystica:
Dude, you're asking Hashcode to re-write everything again? In accordance with his 'scriptures' on his official OtterX thread, most/if not all of Amazon binaries were replaced with custom codes.

Last time I checked, even if you only rooted your KF1, you won't be able to stream from Amazon Prime Videos anyway.

If you know a thing or two about playing Amazon Prime Videos on a rooted KF1, let me know.
[Kindle Fire General] calgator:
Absolutely not -- the man's busy enough with the future, not rolling backwards :).

I'm just curious what in the new bootloader makes the 6.3.x ROMs unbootable.

I'm not looking to run anything but the standard, non-rooted 6.3.x ROM, because as you noted, Amazon Prime videos don't work (yet) on rooted KFs unless the rooted-ness is hidden.
[Kindle Fire General] RagInCajun00:
Fastboot Drivers?

I'm thinking about going back to stock and ended up erasing the complete EMMC and now for the option to boot to either recovery or normal boot, it just shows FASTBOOT MODE DETECTED. Any drivers or anything like that to where I can at least get TWRP back?
[Kindle Fire General] sd_shadow:
why would you wipe emmc? what shows fastboot mode detected?
[Kindle Fire General] lovejoy777:
Sounds right to me dokie:)
[Kindle Fire General] lovejoy777:
Go to mounts and unchecked everything 1st
[Kindle Fire General] liteavenger94:
So far so good!! My kindle is alive again ;) haha. Now that I'm getting CM nightlies for it, it's even better!! Keep up the great work Hashcode!! Android L here we come, in the fall of course!! :P
[Kindle Fire General] bflobills:
Battery Drain

For those with a high battery drain on OtterX, I have changed some settings that seem to have helped - not great but noticable.

Go into your settings, then click on Privacy, then on Privacy Guard.Scroll to 'Google Play Services and long press.

Scroll down to 'Keep Awake' and select 'Denied'. I did this also on 'Google Search'. My battery drain is less than before.

Hope this helps others..
[Kindle Fire General] mpuckett54:
Can't get into fastboot

First, a word of thanks for the spectacular job Hashcode. Outstanding and clear upgrade instructions and excellent Otterx code. I have upgraded my KF and running the first otterx f2fs nightly. Decided to go all in and also enabled ART, so far with no issues at all. Everything is running great, maybe just a bit more battery drain but definitely nothing that should delay anyone from doing this excellent KF upgrade.

Now for my question: how do I get the KF into fastboot mode with the new bootloader? I am wanting to replace the initlogo.bmp and I do the "fastboot flash splash initlogo.bmp" which goes into the "< waiting for device >" mode then I reboot into the bootloader and it presents the "fastboot mode" splash screen but the fastboot command never appears to see the device and come out of the waiting mode. While otterx is running, I can see the device and connect just fine using adb so I know that I am able to connect with the device normally and I have used fastboot previously when I upgraded prior to otterx.

Does the new bootloader require the use of the modified USB cable or is there something else I need to do while in fastboot mode?
[Kindle Fire General] lovejoy777:
turn off device. run fastboot script on pc. then plug in kindle when pc says "waiting for device". then to return to normal boot just do "fastboot reboot"

---------- Post added at 10:21 AM ---------- Previous post was at 10:16 AM ----------

fastboot script is.

fastboot flash splash /path/to/new logo/goes here/
[Kindle Fire General] mpuckett54:
Thanks for the reply but this did not work for me. Followed the exact steps here and fastboot stays stuck at "waiting for device". When I connected the cable while the KF was powered off it went into what seemed a charging mode which displayed a battery with the charged percentage. What is even more odd is that when I rebooted the KF, all of my settings had been blasted. And now the quick settings have disappeared from the notification bar and the advanced reboot options have disappeared from the reboot menu the lock screen settings are ignored and the home button is no longer working.

So somehow I managed to mangle all the settings and am not even able to recover some of them. And I'm still not able to get into fastboot mode.

---------- Post added at 01:23 PM ---------- Previous post was at 01:07 PM ----------

Now that my settings are mangled, some of which seem to be non-fixable from the settings app, can any one recommend the way to hard reset the settings again without having to resort to a complete reinstall?
[Kindle Fire General] lovejoy777:
whats your setup. bootloader/recovery & patition otterx or amazon?
[Kindle Fire General] mpuckett54:
Setup is as described in the otterx installation instructions provided by Hashcode. Bootloader is otterx-u-boot_v2.05, recovery is otterx-twrp-2.7.1.0-recovery, partition is otterx set up with the f2fs. I started with the otterx 20140701 nightly cm build, upgraded to the M8 snapshot yesterday which is what got the corrupted settings today. I have just now finished doing a recovery wipe and install of the current 20140712 cm nightly which has now fixed my settings problems. Not that it should matter to the bootloader and fastboot, but I am also running ART.

And I still can't get into fastboot mode. On a reboot to bootloader, the bootloader fastboot splash screen gets displayed, but the fastboot command is still stuck on "waiting for device". Adb works as expected with no issues.
[Kindle Fire General] sd_shadow:
I believe ART is still experimental at this point.
[Kindle Fire General] mpuckett54:
Yes, as is described when you change the setting too. However, I have been running ART since I installed the 20140701 nightly and the system has been running well for 13 days now. Does running ART have an impact on the bootloader?
[Kindle Fire General] lovejoy777:
ok in twrp reboot/bootloader

---------- Post added at 12:52 AM ---------- Previous post was at 12:51 AM ----------

2.05 bootloader?

---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------

sorry just noticed your last post.

---------- Post added at 12:54 AM ---------- Previous post was at 12:53 AM ----------

cable? pc setup?
[Kindle Fire General] mpuckett54:
Plain USB cable, not modded, Ubuntu Linux. I have used both the cable as well as adb and fastboot previously prior to the otterx upgrade.
[Kindle Fire General] sd_shadow:
would not think so

have you rebooted to twrp and selected reboot>bootloader option?
[Kindle Fire General] mpuckett54:
Yep. I have rebooted using the reboot menu from otterx and selected bootloader which is how I got the fastboot mode splash screen to come up originally. I have selected reboot>bootloader option from twrp and that also brought up the fastboot mode splash screen. I have tried following the instructions to power off, connect the usb cable and power on which is what put me into that "battery mode" where the battery icon showed up with the charge percentage showing, after which my settings were trashed. After all these, fastboot just sits at the "waiting for device"
[Kindle Fire General] sd_shadow:
Reflash bootloader zip in twrp?
[Kindle Fire General] mpuckett54:
Now that I have not tried yet. I will try that as a last resort if there are no other options.

I am curious though about that "battery mode" which occurred and which lovejoy777 didn't mention. Is that usual when the KF is powered off and then powers on and goes into the battery mode when the cable is plugged in like I experienced? I notice that Hashcode does mention this new battery mode and I am wondering if the KF going into this mode is what corrupted my settings.
[Kindle Fire General] lovejoy777:
yes its a new feature i forgot about. sorry. if the kindles off and you plug it in it should go into charging mode. it used to work like i said. if your on the fastboot screen then it should work. as mentioned above, try reinstalling bootloader. it has never corrupted any settings for me. thats strange behaviour.
[Kindle Fire General] mpuckett54:
Yes, thanks for your help lovejoy777. I expected it was the case that this was a new feature. And yes, I did sort of expect that once I had seen the bootloader splash screen that said "fastboot mode" that the KF should have been in fastboot mode which was what prompted my original question.

Ok then, looks like I am going to reload the bootloader as the last resort and see if that takes care of the problem I am having trying to get the KF into fastboot mode.

---------- Post added at 12:49 PM ---------- Previous post was at 12:12 PM ----------

Ok, I reflashed the bootloader and tried the command "fastboot flash splash initlogo.bmp" again. First I ran the fastboot command and got the "waiting for device" message as expected, then on the KF I did a "reboot bootloader" and the KF again went into the "fastboot mode" splash screen and nothing further happened. The fastboot was still stuck on "waiting for device".

There was a slightly different behavior though. So, I killed the fastboot command, left the KF still sitting at the fastboot mode splash screen and ran "fastboot devices" and this time I got the message "no permissions	fastboot" which I have not seen before. I then disconnected the KF from the USB cable, reconnected it and ran the "fastboot devices" command again and this time there was no message, the fastboot command ran and generated no output at all which is what I have seen before. And this behavior is repeatable.

So, I was able to adb push the bootloader, reflash the bootloader from recovery, but still not able to get the device recognized and into fastboot mode. Can anyone decode the new message I am seeing, "no permissions	fastboot" with the odd spacing between permissions and fastboot?
[Kindle Fire General] lovejoy777:
what os you using?
[Kindle Fire General] mpuckett54:
The odd spacing in the message turns out to be a tab character. So the message text is: "no permissions\tfastboot:

---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------

Ubuntu 12.04

I have successfully used fastboot prior to the otterx upgrade.
[Kindle Fire General] lovejoy777:
just to confirm in /etc/udev/rules.d

# Kindle Fire fastboot (Google ID)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"

# adb protocol for blaze / ottter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"

# Hashcodes rules
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666", GROUP="plugdev"

in adb_usb ini

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

# USE 'android update adb' TO GENERATE.

# 1 USB VENDOR ID PER LINE.

0x1949

0x18d1

worth checking:)
[Kindle Fire General] mpuckett54:
BINGO! That did the trick. Outstanding and THANK YOU lovejoy777. fastboot now working and my new otterx splash screen looks fantastic too. :)
[Kindle Fire General] lovejoy777:
fancy sharing you splash?
[Kindle Fire General] mpuckett54:
Sure, it is just the modified otterx splash with the otter pic down in the lower left corner that was posted here. Didn't you post the original version of that one?
[Kindle Fire General] lovejoy777:
ha sorry yes that's mine:-s. just thought you may have made a new one;)

edit: actually the one in the corner wasn't mine (cant take the credit there:) )
[Kindle Fire General] BobJayJr:
Finally, found the time to upgrade to OtterX. Followed Hash's instructions and everything went smooth, fast and easy. Flashed TWA's ROM. Again, smooth, fast and easy. Life is good.

Edit: switched to OtterX SlimKat & 777Kernel. Life is still good. Thanks to Hash and Lovejoy777.