yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Ixthusdan:
Yes, the bootloader and twrp in this thread are installed and the kindle reports it is in recovery. (which it is) I just cannot format the data partition and cannot proceed. Is there s format method from adb? I can even issue fastboot commands, but they do not resolve anything. Fastboot erase cache fails due to too many threads, or something like that.
[Kindle Fire Android Development] dokie80:
I thought recovery means TWRP? Then u can format with it.

Fastboot doesn't mean recovery, right?

Perhaps u should wait for others, I M not really sure about this :D

Sry
[Kindle Fire Android Development] kvestas:
To format Data partition you have to enter recovery mode (to start TWRP). You can enter the recovery mode from the initial bootscreen "by using the power button, ... continue to press power till "RECOVERY" is highlighted". Long press power button to activate the selected menu item.

In TWRP screen select Wipe, Advanced, select Data partition and swipe control.

And please, follow Hash's instructions (the first three posts of this thread) very precisely. He made it really clear you just have to follow them one by one.

If adb driver is installed correctly you should be able to push rom and gapps files when you are in recovery mode.
[Kindle Fire Android Development] Ixthusdan:
Thanks for your input. I am in recovery. I could not have wiped the cach and then rebooted had I not been in recovery. I am in recovery now. I can navigate the new bootloader menus and choose recovery, which is twrp. The steps, which I followed precisely, fail at formatting the data partition. It fails every time. I cannot push any files because of "wrong protocol." I think that means the place I am targeting, sdcard, is not formatted. I could try to go back to stock and start over, but I still cannot format data. When I try to fastboot wipe, all fails due to "too many links."

Precise results:

E: Unable to wipe data using function call

E: Unable to format to remove encryption

Updating partition details...

E: Unable to mount'/data'

E: Unable to mount storage

Every reboot goes into fastboot mode
[Kindle Fire Android Development] koop1955:
I did some research on the "Too Many Links" error. There have been sporadic reports of that across various forums, so it seems a general error. There doesn't seem to be any one particular solution. Try the usual things:

1) Reboot the Kindle by holding the power button down.

2) Try different ports/cables if you have that as an option.

3) Have you run "Fastboot reboot" as yet?

Most people with that error ("Too many links") just sort of stubborn it out. Wish I had a better, more definitive answer.
[Kindle Fire Android Development] kvestas:
I am sorry for giving simple advises but I guess the reason for your failure has to be obvious as well.

May I ask you to check several things:

* you are using Kindle Fire the 1st generation.

* you are using the newest OtterX bootloader.

* you have successfully switched partition mode to OtterX.

* you are using special twrp version for OtterX. To be honest I don't know how to check it but twrp version must be 2.7.0.0.

Just wondering what exactly happens when you do Data formating from twrp? Have you tried to wipe Data and System partition through the Advanced Wipe menu?
[Kindle Fire Android Development] lovejoy777:
make sure youre wiping data from 1st wipe menu and not wipe/advanced. you can check which twrp you have by looking in wipe/advanced the new one has internal storage option and the old one has sdcard option. maybe try toggling amazon/otterx parts. if all else fails you could try reverting back to older versions of bootloader/twrp and do fastboot oem format to return to stock parts the try the whole process again. were your sdcard encrypted before? did you have multiboot? were you on stock parts before the fun started?
[Kindle Fire Android Development] Ixthusdan:
Thank you for all your responses. I may revert to oem layout and start over after trying some of the suggestions. Twrp gives its version at the top of the home screen. I was running twa_priv's kitkat ROM, and his for perhaps a year and a half. I have installed and tried many ROMs, and am comfortable with working the kindle. I had some initial trouble with adb, turned out to be a bad usb cable! The version of twrp is 2.7.0.0. I will be at the kindle later, after work. I did not wipe data prior to formatting it. I know that there is a file system, as twrp file manager shows folders. The folders are empty. Could I send to cache? That formatted correctly.
[Kindle Fire Android Development] lovejoy777:
there is also a normal 2.7

---------- Post added at 06:19 PM ---------- Previous post was at 06:19 PM ----------

check the wipe options just to make sure

---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------

whats checked in mounts?

---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------

no dont send to cache
[Kindle Fire Android Development] shuvabrata:
OtterX Boot Logo

Hi,

How do i get the OtterX bootlogo? I am running the unofficial CM with TWRP for OtterX. But while booting up, i only get the ordinary Kindle Fire bootlogo. Please help.

regards,

Shuvabrata
[Kindle Fire Android Development] lovejoy777:
see slimkat thread op

edit. 2nd post under extras:)
[Kindle Fire Android Development] kvestas:
There is no official OtterX bootlogo. You may flash any bitmap image of the right format (size, color depth, etc.). The only requirement is the OtterX bootloader. You can find several bootlogo images prepared by [MENTION=4410674]lovejoy777[/MENTION] in a few OtterX threads.
[Kindle Fire Android Development] Ixthusdan:
Thanks to everyone for offering ideas for my plight. What I did to get it running was:

1) Go back to Amazon partition scheme

2) Boot twrp and format everything again, including cache and data. Everything mounted and formatted.

3) redownloaded bootloader and twrp, flashed both again.

4) Rebooted and changed to otterx.

5) Booted twrp and formatted data. It worked.

6) pushed ROM and Gapps

7) Installed

8) Rebooted to system

All is good.
[Kindle Fire Android Development] slappydj1:
music bug

Hi, I noticed a bug onevery otterx ROM. Whenever I play a song with Google play music, the audio stops whenever I get a notification and it appears in the play music app that it is still playing. I have tested this on every otterx ROM exept for the PAC man otterx build. That leads to to believe it is an issue with otterx. Has anyone else had this problem. The problem fixes itself only after a reboot.
[Kindle Fire Android Development] lovejoy777:
good find. +1 to ^^ only happens on new notifications and not on recurring ones (seems only when notif sound is played as well).

---------- Post added at 11:10 PM ---------- Previous post was at 11:08 PM ----------

happens on cm based and aosp then. ??
[Kindle Fire Android Development] slappydj1:
It appears that if affects both CM and AOSP ROMs as I get the bug on slimrom as well.
[Kindle Fire Android Development] lovejoy777:
yes. sorry i was agreeing lol

---------- Post added at 11:22 PM ---------- Previous post was at 11:18 PM ----------

did it happen before otterx?
[Kindle Fire Android Development] slappydj1:
Never happened to me before otterx.
[Kindle Fire Android Development] lovejoy777:
mmm interesting it seems to knockout all audio and i couldn't get youtube or TVGuide to even play video until i rebooted. ill take a log☺
[Kindle Fire Android Development] dokie80:
i thought its only for me for the audio issue :p

i still have crashes (lockscreen, systemui), around 2-3 times daily.. sometimes it fix by relaunching the crashed app automatically, sometime KF will reboot itself, but usually end up with systemui crashing over and over. then I have to do manual reboot to fix it.
[Kindle Fire Android Development] Ixthusdan:
Does twrp backup still restore correctly? I know we have to push new files to the kindle, but what about the restore function in twrp? As you can tell, I am playing with ROMs again.
[Kindle Fire Android Development] lovejoy777:
worked ok for me:)
[Kindle Fire Android Development] Ixthusdan:
I have some suggestions after my transition experience. When /data was failing to mount or format, one message said it was encrypted. Since I do not encrypt my partitions, I think that is a clue to my case. I run an antivirus. I suspect the av was blocking changes to my system. When I went back to the Amazon partition scheme and wiped/formatted everything, the av was shut down. So, I think it would be better in the instructions to wipe and format prior to switching to otterx and formatting again. While it may seem like a lot of wiping/formatting, I think it is best. Any thoughts?
[Kindle Fire Android Development] MrBrady:
[MENTION=4243514]Hashcode[/MENTION] thanks again for keeping this device alive!

I just followed the directions to the "t" and have a fresh install of OtterX up and running. How do I know if the new partition setup actually worked? The reason I asked is because previously when I tried to do the partition fix, it threw a bunch of errors and didn't do anything.

Now that I'm up and running without transferring or installing anything, when I go to Settings / Storage I only see Internal Storage with a Total Space of 6.14GB (5.66GB available).

Should I assume that everything is correct?
[Kindle Fire Android Development] Hashbang173:
Same as mine, looks like it worked!
[Kindle Fire Android Development] sabres032:
So all this fighting with Window's drivers and trying to get Ubuntu LiveCD working on my computer has all been for naught. Due to a small mistake on my part (not checking to see if the new bootloader partition was set to Amazon) actually was the solution to all my problems.

Yes, I forgot to check the keep Amazon partitions and accidentally erased my device. Derp-derp... :( So on a whim I plugged the device into the USB port and low and behold OtterX drivers started to load and I have working adb and fastboot. :D Pushing te otter files now...
[Kindle Fire Android Development] Iguanadon:
Well, I've tried for two days. Keep getting unable to mount data and the rest of the E:Unable errors. I can revert back. ...guess I need a video tutorial. :D lol
[Kindle Fire Android Development] Hashbang173:
Try This:
[Kindle Fire Android Development] chykal:
I had the same problem. Check your bootloader version. It must be the 2.04 version from one of the mirror sites. The first link to XDA Downloads only has the 2.03 version which did not work properly for me. Once I flashed the 2.04 version from the first mirror I was able to format and mount /data.

I hope this helps.
[Kindle Fire Android Development] Iguanadon:
That may indeed be the culprit. I'm not home now, but as soon as I'm home I'll check. I did expect when I select otterx partition for something more to happen. Thanks for the input from everyone. I've tried all the fixes I've found. That is the only thing that I've not checked ...the version of boot loader. 2.03 vs 2.04
[Kindle Fire Android Development] sd_shadow:
I made a video of me installing

[Video] OtterX ROM/TWRP/Bootloader [ROM 2014-05-08] -youtube

It's not real smooth as I was reading instructions while recording, but it worked for me.
[Kindle Fire Android Development] Iguanadon:
Thanks chykal, don't know if I would have caught that one without you. v2.03 was the problem for me v2.04 fixed my issues. [MENTION=4243514]Hashcode[/MENTION] check that xda link if you can. :)
[Kindle Fire Android Development] sd_shadow:
correct the xda link does not have Latest File: otterx-u-boot_v2.04.zip, use the goo.im link
[Kindle Fire Android Development] bflobills:
You are using the wrong bootloader. I had the same problem, then realized I was using 2.03 BL instead of 2.04..

Try this and I suspect you will be fine with Hash's instructions
[Kindle Fire Android Development] Iguanadon:
a little late to the game :D but you are correct. :good: that was the problem. thank you for trying. hmm now for slim, pac or stock. :)
[Kindle Fire Android Development] SwoRNLeaDejZ:
I want, so very very badly, to change my Kindle Fire to an OtterX right now, but I can not for the life of me get ADB working in recovery. Shows no attached devices. I have tried everything. Updated drivers a few times, and I can't get it to work. Anyone have any pointers?
[Kindle Fire Android Development] chykal:
PAC and stock ROMs for OtterX? Do you have links? Or am I missing something?
[Kindle Fire Android Development] sd_shadow:
How is it listed in device manager?

Tried uninstalling device, install drivers, reboot PC?
[Kindle Fire Android Development] chykal:
What OS are you running?
[Kindle Fire Android Development] SwoRNLeaDejZ:
Thanks for the quick reply. I figured it out. I just used the "Select from a list of devices on my computer" and selected the "Android ADB Interface" that was installed via my Nexus 7 and it worked out perfectly. Just finished flashing GAPPS, rebooting now :)

All went well.
[Kindle Fire Android Development] Iguanadon:
Pacman otterx, SlimKat otterx and this stock otterx are what I was referring to.
[Kindle Fire Android Development] dokie80:
So Pacman and SlimKat already has otterX version? Good to know :)
[Kindle Fire Android Development] ttakacs:
Here's another one: http://goo.im/devs/loosethisskin/otterx. This would be twa_priv.
[Kindle Fire Android Development] PantherVT:
once in recovery try

adb kill-server

adb start-server

adb devices

you should then see your device.

I use ubuntu OS I have to use sudo when running the start-server command. I assume running the cmd tool as administrator in windows would have the same effect.

good luck otter X rocks
[Kindle Fire Android Development] HoangTuBot:
How to return to stock ROM?
[Kindle Fire Android Development] lovejoy777:
stock. as in kindle fire os?
[Kindle Fire Android Development] Idontwantausername:
I'd like to build using the main CM11 branch. I'm building from the main otter branch now, which is my first time building Android. Hopefully it will go smoothly and I can continue to building an OtterX build.

Does adding to the normal project in this case mean creating a local manifest file, then running repo sync?

If so, does this look like a correct manifest file?

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/amazon/otterx" name="KFire-Android/android_device_amazon_otterx" remote="github"/>
</manifest>
[Kindle Fire Android Development] lovejoy777:
if you can get a normal otter build to build then the easiest way is to make a local manifest folder in .repo with a local_manifest.xml file with this as the content. (i will post off pc so i can c&p).

---------- Post added at 11:47 PM ---------- Previous post was at 11:40 PM ----------

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<!-- removals -->

<remove-project name="CyanogenMod/android_device_amazon_otter" />

<!-- adding new repos -->

<project path="device/amazon/otterx" name="KFire-Android/android_device_amazon_otterx" remote="github" revision="cm-11.0" />

</manifest>

so if in your .repo/manifests/default.xml has "CyanogenMod/android_device_amazon_otter" in it then the above local manifest will delete this and use the new "<project path="device/amazon/otterx" name="KFire-Android/android_device_amazon_otterx" remote="github" revision="cm-11.0" />" to fetch that instead on your repo sync.
[Kindle Fire Android Development] Hashcode:
Fyi, I'm debugging a new F2FS build btw. About 260 commits into what will probably be over 350.

I can access the f2fs userdata in a new recovery, but ROM is bootlooping atm. I had to run out for a bit, so I'll troubleshoot it later.

Once I get a full boot, I'll load the tab up with a bunch of apps and then run some performance tests.

For those that are curious, the WIP kernel branch is here:

https://github.com/KFire-Android/kernel_omap_otter-common/tree/f2fs
[Kindle Fire Android Development] dokie80:
*kneel* Will you marry me hashcode?
[Kindle Fire Android Development] Hashcode:
Who would be interested in a current build update for the ext4 userdata partition? It would contain the audio fixes and quite a but of UI clean up on the CM side.
[Kindle Fire Android Development] muiriddin:
I would flash and test it over the long weekend!
[Kindle Fire Android Development] lovejoy777:
+1
[Kindle Fire Android Development] chykal:
I'm in for some testing.
[Kindle Fire Android Development] slappydj1:
I'd like to test it as well.
[Kindle Fire Android Development] soberarmy:
ADB

I was able to push a apk file to my kindle. C:\users\******>adb push c:\comix.apk /sdcard it pushed the file i can see it on my sdcard but cant push a test file like the OP said what am i doing wrong. Just learning ADB. please help.
[Kindle Fire Android Development] sd_shadow:
I believe that the Test file is any file of you choice, so you did push the test file.
[Kindle Fire Android Development] Hashbang173:
Try maybe running cmmand prompt as admin
[Kindle Fire Android Development] soberarmy:
So as long as I can push an apk to my kindle while in recovery I'm OK. And do I place all the files in c drive to push to sdcard?
[Kindle Fire Android Development] Hashbang173:
When I did this, I didn't put the files at the root of c (C:\) I put them in my user folder just in case of permission errors. (For me i did

adb push \Users\userfolder\Downloads\filename /sdcard/filename
[Kindle Fire Android Development] soberarmy:
I'll give it a try when I get home.thanks.
[Kindle Fire Android Development] lovejoy777:
just do. adb push \Users\userfolder\Downloads\filename /sdcard/
[Kindle Fire Android Development] hutson23:
Ok..this is kinda hard but here goes..

I have 2 kindle fires 1st gen.

Both rooted with custom roms.

One is a dual-boot Modaco rom and Infriction.

The other is my play kindle I guess you could say..I flash all newer stuff

And over the years use it to try out

roms and stuff..

Flashing roms and using adb have never been a problem..all my phones are even custom..I have always

Been able to fix anything I have ever

screwed up..phone or kindle..

So..

I wanted to play with the new otterx..

I guess I got over confident maybe..

I dunno..

But the only thing I can fiqure I have done is flashed the otterx bootloader

and now I have no recovery and now adb will not connect to push the otterx recovery...

Whats wierd is after I pushed the bootloader I saw it was changed to otterx..and the Rom I had on it booted up..so I was like ok lets flash the otterx rom..I totally forgot about the otterx TWRP..so I went to reboot to recovery and no recovery...and now the rom wont boot either.

I didnt change the partions they are still set to Amazon.

I did get fastboot to work once but

as I said I could not get adb to work.

I do not understand what broke adb

It was working fine to flash the bootloader.

The Otterx bootloader does seems to be working fine...

Has anybody else made this mistake..

and what should I do now..
[Kindle Fire Android Development] sd_shadow:
if you see the otterx bootloader screen, fastboot (not adb) should work from there, just be ready.

When you see the bootloader screen, press the power once (will pause boot for about 60 secs)

you should be able to flash twrp in bootloader or

fastboot reboot-bootloader

should get you the fastboot mode screen (did for me)

then

fastboot flash recovery otterx-twrp-2.7.0.0-recovery.img

---------- Post added at 11:23 PM ---------- Previous post was at 11:21 PM ----------

fastboot reboot-bootloader

is also an easy way to test is fastboot commands are working
[Kindle Fire Android Development] hutson23:
Ok thanks your saying forget adb and just use fastboot..I will be able to fix this then..just curious..did the same thing happen to you?
[Kindle Fire Android Development] sd_shadow:
no, but easy to forget steps, i did record my install

https://www.youtube.com/watch?v=8_poieP0ruI
[Kindle Fire Android Development] kev716:
I would
[Kindle Fire Android Development] HoangTuBot:
Anyone? :(
[Kindle Fire Android Development] lovejoy777:
stock parts or os?
[Kindle Fire Android Development] koop1955:
You haven't provided enough information for me, or anyone, to give you a definite answer. Did you change the partition layout? What have you installed?

That said, about 10 seconds of searching via Google brought me to this: http://xdaforums.com/showthread.php?t=1638452

If you have changed to the OtterX partition layout, you'll need to change back.
[Kindle Fire Android Development] Idontwantausername:
Also, you'll need to format the data partition using the OtterX recovery, before replacing it with another recovery.
[Kindle Fire Android Development] soberarmy:
Going back now I decided to moved the test file to c:\users\username> and now i can push files easily.

Thanks.:good:
[Kindle Fire Android Development] Idontwantausername:
My build is done, and I'm testing it ATM. Thanks to everyone involved, especially hashcode and lovejoy777 :good:

So now I have an OtterX CM nightly build, cm-11-20140525-UNOFFICIAL-otterx. Nothing special about it, but if anyone is interested I'd be happy to upload the file somewhere, just let me know.
[Kindle Fire Android Development] hutson23:
Thanks for the video..

it was really helpful.

OtterX = Bootloader, Recovery.and the Rom are installed and all is well..

I had it done by 10 am this morning. I was able to get ADB and Fasboot

going..

I didnt completely understand

The options in the bootloader..

I had the bootloader installed but I was freaked because I couldnt get in adb, fastboot, or recovery..

I finally got fastboot going like you said and pushed FFF 1.4 ..LoL.

Then I just followed your video..

The only part I didnt get was backing up the partitions.

I think because I Had already installed the bootloader.

ADB kept saying the files didn't exist.

I just finally moved on..

I could be having another brainFa**

but wouldn't a backup of the partitions from say your Kindle work on any Kindle with the same partitions....or am I stupid..

Anyway thanks for the help and Thank you HashCode for keeping our old tablets fresh..

Its just a thought but if you put that

Video in the OP I am sure it

would help some people out.
[Kindle Fire Android Development] lovejoy777:
the backup Hash talks about are to keep your amazon id's. ie. mac address etc. each device has its own info.
[Kindle Fire Android Development] HoangTuBot:
I'm on otterx ROM. I want to return to stock ROM with stock bootloader
[Kindle Fire Android Development] Idontwantausername:
Start here: http://xdaforums.com/showthread.php?p=52511937#post52511937
[Kindle Fire Android Development] koop1955:
Once you have returned to the Amazon partition structure, you should be able to follow the instructions in the post I linked to earlier to get all the way back.