yashsingh1/xdaforums huggingface dataset:
[Kindle Fire General] 404-Not Found:
1) I would totally update, been years since my last boot of the Amazon OS. I can get any Amazon App from Google Play, Non-Amazon Prime Users should NOT have a problem, unless they are and usae Instant Video.

2) In theory this should way better, but there might be a problem: Harder Developing. If it is in fact harder to develop a ROM for this specific type of system, we may look into very few ROMs available, which I am pretty sure I community does NOT want. Even though, I am doubtful it will get any harder.

3) Dual Booting might be awesome, but on this device, the Hardware will be much slower and otherwise defeat the purpose of building this new "OtterX".

In other words, I FULLY AGREE, that we should continue or start the OtterX project. We might wanna do a poll to assure that our community in fact will want this. Hope you have success in this Hashcode!!!
[Kindle Fire General] Samuelgames:
Dual booting can be really useful for me specially if we can boot tar images easily with chroot with also a specific kernel instead of repartitioning every time
[Kindle Fire General] Hashcode:
Small update as I work on the new bootloader.

Some of the new screens.

Image #1: I really like the new ultra simple bootscreen of the HDX's so I thought I'd start there... tho I may still change "kindle fire" to something else.

Image #2: Is the low battery charging screen

Image #3: Is a new screen similar to what the KFireHD 8.9" has for anytime you enter fastboot mode.

(Text responses from fastboot are shown on the fastboot screen)

Once I get the menu system up and running, I'll try and put some shots of that up as well.
[Kindle Fire General] QuasiTD:
Hashcode, you are constantly amazing with what you have managed to make work on this device. I love all the ideas of this project, I'm definitely a #2 user from your first question. I primarily use my Kfire as a reader(Amazon Kindle app) and internet browser, with some gaming/email here and there.

Discussion Points:

1) I definitely would, I tried going back to the Amazon software about a year ago and couldn't stand it then, let alone since all the work you've done in the last year to get the newer 4.3 and 4.4 revs available.

2) I feel this is a less likely to use situation. the Kfire has a horrendous partition layout for a normal tablet use, I know why it was, but compared to how fluid it feels on my Gnex(similar in that it has no SDcard slot either) the kfire could definitely see better usage in your proposed setup.

3) I have no large interest in dual boot myself, as you mentioned it had a limited amount of storage on the device, something I've found running into limits quickly just using Multiple profiles in CM let alone adding a whole extra system of data to the tablet. Personally I'd prefer the tablet made as functional/quick as possible without worrying about a second OS. I'll be perfectly content with one Os that runs great rather than 2 that could both stand to run better.
[Kindle Fire General] Hashbang173:
make sure you backup your vital partitions

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

Just got that code from how to install the bootloader from here
[Kindle Fire General] dokie80:
[MENTION=4535397]miguelmt[/MENTION]. i never check md5.. i usually check if the zip is fine by opening the zip, usually using es file explorer.. if it open the zip without problem, then it should be fine. i still belive that the zip is corrupt.. perhaps u can try to put the file on /sdcard/

NOT /sdcard/TWRP ?
[Kindle Fire General] miguelmt:
I finally got it working. Here's how:

I thought that I'd rather have a non-working recovery than an non-working bootloader and used flashboot to install Hashcode's custom TWRP. It worked just fine. I rebooted into recovery, tried to install otterx-u-boot_v2.04.zip... and it failed the SHA1 hash check. Again.

Then I got a sudden strike of inspiration and used TWRP to wipe clean the /cache partition (and another of the non-essential partitions... I don't remember now which one, but I'll doublecheck). I tried again to install otterx-u-boot_v2.04.zip and, boom! It worked all right! The SHA1 test passed and the new bootloader was installed.

After that, I only had to follow the remaining steps in Hashcode's instructions (repartition, flash CM11 and GApps) and I am now the proud owner of a brand new OtterX tablet! :victory:

After all this mess, do you think that it would be a good idea to add "Wipe the cache partition before installing otterx-u-boot_v2.04.zip" to the official OtterX installation instructions? It can't hurt and it might save someone like me, with a rotten /cache partition, a lot of headaches.

Thanks everyone (@dokie80, [MENTION=3816775]koop1955[/MENTION], [MENTION=4410674]lovejoy777[/MENTION], [MENTION=4267571]sd_shadow[/MENTION], [MENTION=4630246]joshuabg[/MENTION])! And, of course, thanks a million to [MENTION=4243514]Hashcode[/MENTION]. I almost cried when I looked at Settings->Storage saw just one big partition.
[Kindle Fire General] dokie80:
congrats!

welcome aboard! :D

wiping cache.. doh! i dont think it is a necessary step, cause I didnt do it.. but good to know. thanks for sharing.
[Kindle Fire General] koop1955:
Welcome aboard!

:good::good::good::good:
[Kindle Fire General] GaryScottMartin:
Latest Play Store & Other App won't install--Insufficient Storage

After getting my USB drivers settled, I was able to step through the directions without any issues. Thanks for the clear, concise directions. :good::good: The performance is great and the ROM has been very stable.

However, I have an expanding list of apps that produce an "Insufficient Storage Available" error when I try to update them. If I try to update Google Play Services or install it from the APK, I also get that error. Other apps update without issues. Earlier today, a 38 MB update to Google+ installed without a problem, but just before that, a 5MB update to Gmail failed. Storage in Settings shows 2.83 GB available out of the single 6.14GB partition. The apps that generate the "insufficient Storage Available" error include Amazon Local, Flipboard, Gmail, Drive, Google Search, Instapaper, OneDrive, TWRP, & (mu)Torrent.

I also lost SuperSU when I flashed the 20140508 version and it produces the "Insufficient Storage Available" error when I try to reinstall it from the Play Store. It was installed in the system, so I don't a backup to reinstall from Titanium Backup. SuperSU installed fine under the 20140430 version.

Thanks again for the great ROM,

Gary
[Kindle Fire General] lovejoy777:
sounds like your still on amazon parts. open settings/storage/ whats it say?(screen shot). what version bootloader do you have, 2.03 or 2.04?
[Kindle Fire General] GaryScottMartin:
Latest Play Store & Other Apps won't install--Insufficient Storage

Boot Loader is v2.04 and reports OTTERX for partition setting. Screenshot of Storage Settings Page is attached.
[Kindle Fire General] damystica:
I can't wait for this becoming a major game change for my old Kindle Fire! Please focus on getting it stable, Mr. Hashcode.
[Kindle Fire General] GaryScottMartin:
I started over again (reloaded boot loader v2.04 & TWRP for OTTERX and reformatted Data partition). This time I loaded SlimKat for OTTERX and everything seems to be working properly.
[Kindle Fire General] Os_A:
Adb Push confirmation

Well I am inclined to move to Otter-X and as recommended here

Confirm that you can use ADB to push files to the device while booted into recovery. The mass storage sharing function of the "Sdcard" will no longer work in TWRP due to how /data/media storage works.

I have adb up and running on my W7 PC. When I execute adb puch testfile /sdcard or

adb push testfile /sdcard/testfile everything looks fine (adb reports copy speed and number of bytes) but

I DON'T SEE ANY COPIED FILE on the SDCARD.

How this could be? And is this the thread to ask?
[Kindle Fire General] lovejoy777:
did you do to /sdcard or /sdcard/
[Kindle Fire General] damystica:
Wanting to revert back to otter

Could you please explain to me like, to a 5 years old, more elaborated step-by-step? I am very new at this and still looking for ways to bring my KF back to otter-CM-ROMs if something goes awry after moving to otterx. Thanks.
[Kindle Fire General] Idontwantausername:
It will be easier to understand once you perform the move to OtterX, which is completely stable in my experience. I'm at work so if you still require more detailed instructions I can provide them later, but I think that there are plenty of able and helpful forum members who can assist you through the process should you run into any trouble.

Steps 1 and 2 are basically identical to the OtterX installation steps 3 and 4, but instead of changing from Amazon to OtterX you do the opposite.

What you do after that depends on whether you choose to keep the OtterX recovery. There are plenty of guides on how to flash recovery and ROMs.
[Kindle Fire General] damystica:
Need help ASAP

Alright. I'm moving to otterx now.

*UPDATE* I got to STEP 4: WIPE PARTITION IN RECOVERY but was unable to. I did a search in the thread but didn't find what need.

Here are the errors when trying to wipe cache:

E:Unable to mount '/data'

E:Unable to recreate /data/media folder.

Updating partition details...

E:Unable to mount '/data'

E:Unable to mount storage.

E:Unable to mount /data/media during GUI startup.

Full SELinux support is present.

E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.

Formatting Cache using make_ext4fs function.

Updating partition details...

E:Unable to mount '/data'

E:Unable to mount storage.
[Kindle Fire General] Idontwantausername:
Make sure you have the correct version (2.04) of the bootloader, the XDA download site only has v2.03. There are other links with v2.04.

If it's the correct version, or if you have updated it to 2.04, perform the partitioning operation again by changing to Amazon and then changing again to OtterX.
[Kindle Fire General] Os_A:
figured how to push files

Figured it out: I did this with Mounted SDcard. That does not work. Push works without mounting sdcard in TWRP.
[Kindle Fire General] damystica:
CONFIRMED: OtterX Bootloader v2.04 & OtterX TWRP 2.7.0.0

Don't worry, sir! I was doing baby-step-by-step so no mistakes could slip in.

It is CONFIRMED with OtterX Bootloader v2.04 & OtterX TWRP 2.7.0.0

The error messages I posted earlier was direct result of 1st-step of STEP 4: Select Wipe -> Advanced -> Check "cache" and Swipe

***I can't wait to have a combine storage and use my KF as daily driver now that I no longer have the Nexus 7 2013. :)
[Kindle Fire General] Os_A:
Well, I bit the bullet. I am now on Otter-X.

All went extremely smooth, no problems following Hashcode instructions at all. I chose Hashcode's CM11-20140520-2224-otterx-sgt7 ROM which I already tried on my Amazon-partioned KF.

The only drawback I can report now is that 'Mount' does not work in TWRP, but that was part of a deal.

Will report more later.
[Kindle Fire General] Idontwantausername:
Have you tried going back to the Amazon partitioning scheme and then again to the OtterX?
[Kindle Fire General] damystica:
Successful - Now using OtterX ROM :)

***UPDATE***

I went ahead and go along with the instructions while ignoring those "Unable to mount..." messages.

I am now an official OtterX user! Thanks.

So nice to have a combine storage, oh man!

5.93GB USAGE out of TOTAL 6.14GB!!!
[Kindle Fire General] Hashcode:
F2FS changes are up on the main OtterX dev thread:

http://xdaforums.com/showpost.php?p=52995722&postcount=286

Please note: to use F2FS for userdata you will need to basically re-do the OtterX conversion.

For those wonder what F2FS is:

http://en.wikipedia.org/wiki/F2FS
[Kindle Fire General] lovejoy777:
[MENTION=4243514]Hashcode[/MENTION] if i sync up with KFire-Android/android_device_amazon_otterx now will i need anymore changes to have a f2fs rom??
[Kindle Fire General] Hashcode:
Need both kernel and otterx device.
[Kindle Fire General] lovejoy777:
thanx :)
[Kindle Fire General] Hashcode:
I also recommend updating to the v2.05 bootloader and toggling between Amazon partitions and then back to OtterX partitions for the new system/cache sizes before swapping to F2FS. Since you'll lose all your storage during the switch anyway.
[Kindle Fire General] lovejoy777:
already done and all went well except i had to do a cache wipe before the format data as it gave an error. thanks again Steve

---------- Post added at 03:46 AM ---------- Previous post was at 03:04 AM ----------

Wow what a difference. Mines built and uploading. Its very fast. Thankyou???
[Kindle Fire General] damystica:
Total space went down from 6.14GB to 5.74GB after implementing f2fs!

All completed! However, I am a little sad that total disk space went down from 6.14GB to 5.74GB after updating to F2FS, hic hic...

After cleaning up everything, Total Available Disk Space is 5.21GB. :(

All said and done, hoorah to Hashy!
[Kindle Fire General] Hashcode:
Yes, that's correct. :/ The usable /data space is now reduced slightly on the v2.05 partition layout.

I shifted more room to both system and cache to be future proof for the long run and eliminate any further re-partitioning (which i think a lot of users are really shy about doing). It was brought up that we only had 40-50mb free in /system under the old layout. And that under many circumstances a cache size of 250mb wasn't going to fly for long.
[Kindle Fire General] damystica:
No Cry = No Gain! Wonky WiFi

A man like you with that extensive experience, I have no doubt that we will soon be able to mod the mainboard for extra disk space, RAMs and perhaps an SD card slot. My fingers are always crossed.

Can't be shy if you're on XDA, users or developers. Just take baby-step-by-step and ask if needed. I actually spent one week reading OtterX Instruction. The point being: Cry More, Gain More!

***On to the technicality, my KF crashed this morning while reading XDA and along with wonky WiFi refused to turn off during sleep mode even after I set it to "NEVER". The good thing is that many UI visual artifacts are ironed out in latest otterx-5.28.14-build.***
[Kindle Fire General] bflobills:
Hi Hash, sorry for my ignorance, but I don't quite understand your comment 'toggling between Amazon partitions and then back to OtterX partitions for the new system/cache sizes before swapping to F2FS'

I am already running OtterX. Are you saying that I should flash v2.05, then change the partition back to Amazon before doing anything else, or change to Amazon in v2.04 before applying v2.05?
[Kindle Fire General] damystica:
Here's what I did:

***You can try the step-by-step instruction below. I think in order for the userdata partition to apply the new f2fs filesystem, you have to switch back and forth for it to take effect, kinda like what you have to do when updating Windows.***

1. Copy Bootloader v2.05 to /sdcard/ and flash using your current TWRP

2. Reboot your device and on Bootloader menu, select Advanced

3. On Partition Mode, switch it back to Amazon

4. Go back to Main Menu and do another reboot.

5. Do Step 2 and 3 and switch it back to OtterX

6. Go back to Main Menu and do another reboot.

7. Boot to TWRP and adb push recovery-f2fs-filename.zip and flash it from there. (BE SURE TO FLASH THE F2FS ONE)

8. Reboot to your newly-updated TWRP

9. On Main Menu, select Wipe -> Format Data -> Type "yes" and swipe.

10. Now adb push GApps and OtterX-2.28.14-f2fs.zip files and F-L-A-S-H 'EM (AGAIN, BE SURE TO FLASH F2FS OTTERX ROM)

***Note: On my terms, not sure if Step 4 & 6 are necessary but I did anyway.***
[Kindle Fire General] lovejoy777:
you may also need to wipe cache before you can format data. if formatting data throws an error just hit advanced then wipe cache then go back to main wipe screen and then format data.
[Kindle Fire General] bflobills:
Thanks for your help. I flashed v2.05 no problems. I toggled between Amazon and OtterX as you stated - no problems. I then pushed the f2fs TWRP and flashed it, which seemed to go okay, but when I re-booted into recovery it still said it was version 2.7.0.0 and not 2.7.0.1. Is this normal? I haven't done the wipe cache or data part yet ... waiting for help! Cheers.. :)
[Kindle Fire General] lovejoy777:
no. it should say at the top 2.7.0.1.

make sure your dl is the right one. it took me a while to find it. its only in one of the dl folders. i will post a link shortly.

---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------

hosting.crackflasher.com/getdownload.php?file=./Devs/Hashcode0f/otterx/recovery/flash-zip/zip-otterx-twrp-2.7.0.1-recovery-f2fs.zip
[Kindle Fire General] bflobills:
Thanks Lovejoy777

Well I'm definitely using the correct F2FS TWRP - your link took me to the same place as I downloaded from, but I re-downloaded the file anyway and replaced it. Just pushed it again and flashed, but upon re-boot into recovery it still says 2.7.0.0.

I must be doing something wrong - any other thoughts? Thanks again...

Just tried redoing all the steps again with no change - still says 2.7.0.0. I noticed that I get all the 'unable to mount' errors when flashing the TWRP zip though.. I suspect this may be the problem? Am I stuck now, or can I re-flash the old (non F2FS) rom if I can't get this going?
[Kindle Fire General] damystica:
Can't stress enough! Make sure you got the right file!!!

Alright, let's do it.

1. Take 3 deep breaths...VERY IMPORTANT!

2. Check the file to make sure it's the right one --- zip-otterx-twrp-2.7.0.1-recovery-f2fs.zip ---

3. Take the 4th deep breath...AGAIN, REALLY IMPORTANT!

4. ADB push that file to /sdcard/

5. In your current TWRP, hit Install --> Select zip-otterx-twrp-2.7.0.1-recovery-f2fs.zip and FLASH!

6. Reboot to TWRP and you should see version 2.7.0.1

***If that doesn't work, try the the fastboot method that Hashcode wrote on his main OtterX thread.***

Post #286 - http://xdaforums.com/showthread.php?t=2671619&page=29
[Kindle Fire General] bflobills:
Haha.. I feel light headed now! :) Okay, YES I confirm that I have the correct f2fs file. (file size is 7435KB). YES I pushed to /sdcard/ and confirmed it was there with the same file name zip-otterx-twrp-2.7.0.1-recovery-f2fs.zip. I hit install in TWRP, selected it and flashed (7th time now). Rebooted into recovery and confirmed that it still says 2.7.0.0 at the top.

Perhaps I'll try the fastboot method now although I've never used that before..

Thanks for your help again.

Okay, so I used the fastboot command with the f2fs file and it seemed to work (no errors and completed), however I now cannot get into TWRP when I select 'recovery boot' from the main menu - it just takes me to a screen with the 'fastboot mode' logo and sits there - there are no options to select, all I can do is long press the power button to close it out and then re-boot back to the OtterX boot screen... then same thing again. I think I need a beer!
[Kindle Fire General] lovejoy777:
when its installing. what does the output say? does it say that its flashing 2.7.0.1? does it say success at the end?

---------- Post added at 06:57 PM ---------- Previous post was at 06:54 PM ----------

sorry just reread your post. go into mounts and unchecck everything then try again
[Kindle Fire General] bflobills:
UPDATE;

Firstly thanks to lovejoy777 and damystica for your help and patience :) I am now up and running. Fastboot worked for installing recovery 2.7.0.1 however, I made an idiotic mistake and sent the .zip file via fastboot instead of the .img file which is why I was stuck in fastboot with nowhere to go :(. Once I loaded the .img file in fastboot it loaded fine and I was able to get back into 2.7.0.1 recovery and flash the rom.

All is good again..

Thanks again for your help - much appreciated
[Kindle Fire General] damystica:
Hate to say 'I told you so!" Deep Breaths work! :D

Awesome!

Yes. Most, if not all, are user mistakes.

.IMG extension files associate with fastboot method while .ZIP extension files with TWRP flashing.
[Kindle Fire General] bflobills:
Agreed, maybe one too many glasses of wine.?

Still don't quite understand why flashing in TWRP didn't work though...
[Kindle Fire General] damystica:
That question is reserved for big man Hashcode. He modded TWRP specifically for OtterX. You can unzip the file and compare the .IMG file to the one you use to flashboot.
[Kindle Fire General] Hashcode:
If we can figure out a good change in the steps please let me know.

The file flashed successfully for me, but I cant predict every circumstance. Flashing the .IMG file via fastboot is really the best way to go.
[Kindle Fire General] micl9:
Thing 1 and Thing 2 updated with no issues. Flashed TWRP via fastboot. Can't wait to see whats next!

This is really a pretty nice little tablet!

Thanks again Hash!
[Kindle Fire General] kornklown69:
I'm hoping for an paranoid android port :D
[Kindle Fire General] Hashcode:
I have a master branch Android build running on my OtterX .. it cannot be rooted at the moment tho.

So I'm hesitant to put it out.. (Meaning I've tried flashing UPDATE-SuperSU-v1.99r#.zip and UPDATE-SuperSU-v1.94.zip and some other versions and they all leave the device in a semi-bricked state.)
[Kindle Fire General] kornklown69:
hmmm I know you can figure it out your the master of the bootstrap
[Kindle Fire General] damystica:
***Battery Life drains during sleep mode.***

So far so good on performance with OtterX Build 5.28.14; however, battery life takes a dive.

I let it fully charged, unplugged but it went down to 5-10% overnight. (WiFi set to "Only when plugged in" and/or "Never" during sleep mode)

Does this have anything to do with OtterX bootloader, TWRP and/or ROM?

I would be glad to do a bug report if you can show me how.

-=UPDATE=-

Kindle Fire froze for the third time during sleep mode.
[Kindle Fire General] bflobills:
Does it go down TO 5-10% overnight? or down BY 5-10% overnight? Mine does the latter. BBS shows ~1.6%/hr using otterX with F2FS partition. I did turn off 'daydream' if that helps?
[Kindle Fire General] Ixthusdan:
I also saw a jump in battery usage when I switched to otterx with f2fs. I turn off the autoupdate feature in the Playstore and wifi is set to never be on when sleeping. I am getting sleep, but it seems when it is awake, the kindle uses more battery. I could let it go for 6 days without use and not drain the battery, but now it is 48-36 hours.
[Kindle Fire General] pfederighi:
I found that some programs, like Dolphin Browser for example, forced closed and behaved oddly using otterx, so I thought I'd revert back. I followed your steps and everything worked great except: Some of the ROMs I've tried can't seem to mount /sdcard. I tried formatting, fixing permissions, changing fs type TWRP can see it, InFriction ROM can see it, the older ICS ROMs I've tried can't. Any ideas? Thanks.
[Kindle Fire General] Hashcode:
Are you sure you reverted to a TWRP that uses split storage again for sdcard and data (ext4)? You can confirm you're on an "otter" TWRP if you can "share" out the sdcard partition in TWRP since it's vfat formatted.

So it's:

- toggle back to "amazon" partitions

- re-flash an otter-style TWRP

- under "Wipe" -> "Advanced" find the storage item and checkbox that and re-format the "sdcard" partition as vfat

- Then do a normal "wipe" to format userdata / cache

Then use adb to push your ROM / gapps back to the /sdcard while in TWRP and re-flash the ROM.

Let me know if that works.
[Kindle Fire General] Hashcode:
I'll do some research and see if I can pin point the battery drain.
[Kindle Fire General] pfederighi:
That is crazy. I have done those steps many times with no luck. You say to do them, I try it one more time, and it works just like it should. Thanks. And thanks for all your hard work on otterx (and the KF in general). I look forward to trying it out again when it's a little more mature.