yashsingh1/xdaforums huggingface dataset:
[Kindle Fire General] squidblaster:
Need a Hint on a fix for my Kindle fire.

To start things off I know how to use adb commands and I am familiar with using twrp for a few years now. Before this problem occurred I had otterx bootloader and rom with gapp working okay but I was going to try and upgrade as the device was a bit slow.

I decided to upgrade twrp to 2.8 and I did so successfully. However little did I realize I could no longer push and pull stuff onto my kindles /sdcard. (unauthorized)

I did some searching around and realized that other people were having the same issue with 2.8... so I decided to revert back to 2.6.3.1. That solved my unauthorized adb commands problem but created a bigger one I do not know how to solve at the moment.

Twrp was formatted in f2fs and 2.6.3.1 does not have the capabilities that I know to format back to ext4. Also I forgot to format the storage back to amazon using the otterx bootloader before trying to go back to everything stock.

So my storage is most likely formatted in the otterx format as well as f2fs but twrp is recognizing it as 0mb of sdcard and internal storage does not show up at all. I am not able to flash the otterx bootloader back or a newer version of twrp as it is unable to mount itself. I dun goofed and now I am in need of some friendly assistance.

I was wondering if I could manually format the storage using the terminal command in twrp. I did some googling and it looks like some people have done this with other devices. However I'm not sure what commands I would use to fix my kindles storage.

So right now my Kindle fire has twrp 2.6.3.1, firefirefire bootmenu is working sort of, but i cannot flash anything I push to the device through adb, there is no ROM/OS to boot into.

Hopefully what I'm trying to explain makes some sense to anyone. Your help would be greatly appreciated. Thanks
[Kindle Fire General] sd_shadow:
You must use OtterX twrp and OtterX bootloader

I don't consider 2.04 & 2.05 OtterX bootloaders to be fff.

which bootloader version is installed?
[Kindle Fire General] squidblaster:
FFF is installed. When I boot up I get the old FFF menu. I had OtterX, I tried flashing FFF and compatible twrp but forgot to format storage.

I tried flashing OtterX in twrp but twrp can't flash anything 2.6.3.1 isn't recognizing the partition.
[Kindle Fire General] sd_shadow:
flash OtterX 2.7.1.0 twrp in fff

basic steps in [Video] Flashing TWRP in OtterX bootloader
[Kindle Fire General] squidblaster:
I tried flashing OtterX using adb commands like that video this morning. A few times. I got an error said something like "this image is too large for the partition."

I tried flashing a newer version of twrp using adb, (2.7.1.0) yet when trying to reboot to recover it never boots up past the booting screen.

Flashing older version than 2.6.3.1 seem to work however. I tried 2.6 and 2.2 both were able to boot into recovery but they both are not able to erase storage or flash zips.

Both versions show 0mb SDcard and no internal memory.
[Kindle Fire General] sd_shadow:
what do yo mean flashing OtterX ?

Yes, you still have OtterX partitions, 2.6.3.1 has no idea what to do with that.

Try in 2.6.3.1 Mount>check system>select mount usb

may get a storage device in window, if so copy otterx-u-boot_v2.05.zip and zip-otterx-twrp-2.7.1.0-recovery.zip

unmount, install files

if you get a volume/device needs formatted

Choose a quick format (if possible) and format it as "fat32", block size "4096".
[Kindle Fire General] squidblaster:
By flashing OtterX I meant flashing twrp 2.7 using fastboot mode (fastboot flash recovery recovery.zip) This will give me the error this image is too large for the partition. As my partition is messed up.

Unfortunately it won't even let me check system before mounting usb. or sdcard/cache/data

And mounting with nothing checked doesn't show up in windows. This was a good idea though I didn't think of trying to format using windows.
[Kindle Fire General] sd_shadow:
You can try flashing OtterX Bootloader, download otterx-u-boot_v2.05.bin, verify md5:241a3fd1edad0a0d95886ddeb4693e1c

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

fastboot reboot

if that works, try selecting OtterX partitions, reboot, wipe cache in twrp, reboot, select amazon partitions, reboot, wipe cache, reboot, wipe>advances, check everything, swipe to wipe

then try mounting sd card and system

---------- Post added at 09:59 AM ---------- Previous post was at 09:40 AM ----------

you can't flash .zips with fastboot, must use .imgs like otterx-twrp-2.7.1.0-recovery.img

.zips are installed in TWRP, .imgs are flashed in bootloader
[Kindle Fire General] meXico12:
Bootloader loop?

I previously rooted and installed fff uboot plus openrecovery twrp 2.2.2.1 blaze img to my AF. I did not have a factory cable, so I followed the directions on how to without factory cable and successfully installed a moded 6.3.3.0 rom and all was well. After a few days of flawless operation, I decided to install the otterx uboot 2.05 and otter-twrp 2.7.1.0 recovery. I booted into my existing twrp 2.2.2.1 and after pushing the uboot and new recovery to the sd card, (verified) I attempted to “install” the boot loader. To do this, I highlighted the 2.05 boot in the sd card screen and mounted it, then pressed the “install” button. It appeared to load fine, but when I rebooted, it remained in the old twrp mode, and when I tried to go to recovery, the device simply would not go. I attemped to power the unit off, but it kept on returning to the kindle fire logo. At some point I pulled the usb and then attempted to restart by plugging it in to the computer, only to have it continuously reboot. The computer does not recognize the kindle, even after reinstalling kindle drivers, so I’m stuck? I DID NOT use a factory cable or use the flashboot commands when I tried to install the new uboot and recovery! Is this what caused the issue? Is this fixable, or do I have a brick? Any help or suggestions are appreciated. Thanks.
[Kindle Fire General] sd_shadow:
you mean it rebooted straight to recovery(TWRP) or it rebooted to old bootloader(FFF 1.4/1.5)?

In FFF bootloader?

Could be a low battery issue, when that happens, it can take hours connected to a wall charger before it will boot again.

---------- Post added at 12:19 PM ---------- Previous post was at 12:16 PM ----------

Once you have FFF bootloader you do not need a fastboot cable, and if you have a working TWRP, you do not need flash commands.
[Kindle Fire General] squidblaster:
Yeah I meant flashing .img not .zip in fastboot.

Okay so I flashed the bootloader via fastboot. Thanks for the .bin files I couldn't find those on the forums. Got OtterX and problem solved. I know what to do now that I got my partitions back.

Thanks so much Shadow.

Flashing TWRP 2.8 was a big mistake. haha
[Kindle Fire General] meXico12:
Quote 1. you mean it rebooted straight to recovery(TWRP) or it rebooted to old bootloader(FFF 1.4/1.5)?

Yes, when the Kindle logo came up, at the bottom it said press button to navigate the recovery menu which I did. It showed the same three options “continue” recovery”and a third which I cannot recall, the same as it did before I attempted to load the uboot v2.05. I navigated to “recovery” and gave it a long push, but it did not enter any twrp menu, but rather started rebooting over and over. So. I think it never actually loaded the v2.05, but in the process lost the ability to get back into the twrp blaze img.

Quote 2. In FFF bootloader?

Initially I was hoping it would boot into v2.05, but it never did. Since the menu navigation instruction at the bottom of the page was the same as the fff booloader, Iam assuming it was trying to boot into the fff bootloader.

Quote 3. Could be a low battery issue, when that happens, it can take hours connected to a wall charger before it will boot again.

NO. I read that battery power could be a problem, so I fully charged the battery before I started. I did verify that before I started.

Quote 4. Once you have FFF bootloader you do not need a fastboot cable, and if you have a working TWRP, you do not need flash commands.

Thanks for answering that question because when I originally loaded up the fff bootloader and twrp 2.2.2.1 blaze image the instructions said that at that point a I could simply installed the modded 6.3.3.3 Rom, That’s why I did not use a factory cable or run the fast boot commands when I decided to go to uboot 2.05 and the otter twrp 2.7.1.0. I was afraid my failing to start over with the fastboot commands might have caused the problem.

Now I am wondering if I incorretly attempted to load the uboot 2.05. I was attempting to load uboot 2.05 out of the twrpo 2.2.2.1 recovery which I had previously installed. From twrp 2.2.2.1 I highlighted the uboot 2.05 in the sd card, clicked mount and then clicked install. I had to swipe before it would actually go forward with the attempted installation. Any help here is appreciated, but it sounds like the boot 2.05 somehow got corrupted while it wass being installed? I did check the md5 checksome on all my download files and all were showing green and said the files were good. Is this device fixable? Without the computer recognizing the device, it seems impossible to do much of anything. Thanks for your quick reply.
[Kindle Fire General] sd_shadow:
Yes, OtterX bootloader looks different and has many more options in boot menu

Even so, connecting it to a wall charge sometimes helps.

I have use 2.2.2.1 to install otterx-u-boot_v2.05.zip and zip-otterx-twrp-2.7.1.0-recovery.zip many times and it works fine.

the zips also verify the md5 for the images before installing.

When you power off (Long press power button for 15-20 secs), then connect to usb, what happens?
[Kindle Fire General] Sareniah:
Odd issues

So, Ive been experiencing an odd issue. I have no issue installing OtterX or changing the partition, or installing twrp for otterx, however I cannot open TWRP at all when on the OtterX partition setting, it works on Amazon and on the FFF bootloader. I have tried completely reverting the changes made by installing otterx and nothing has changed so far. Any ideas?
[Kindle Fire General] sd_shadow:
Filenames being used?
[Kindle Fire General] Sareniah:
otterx-u-boot_v2.05.bin

otterx-twrp-2.8.3.0-recovery.img

Tested (yet still failed)

otterx-twrp-2.8.2.0-recovery.img

otterx-twrp-2.7.1.0-recovery.img
[Kindle Fire General] sd_shadow:
don't use TWRP 2.8.X.X

use what ever recovery/bootloader that is working

adb push or mount/copy zip-otterx-twrp-2.7.1.0-recovery.zip and otterx-u-boot_v2.05.zip

install both in TWRP, then reboot, and try OtterX partitions again
[Kindle Fire General] meXico12:
When I power off (long press power button for 15-20 secs (or for that matter overnight) and then connect to computer, the device power light lights up and the logo loop starts up and continues., but never "connects" to adb. Computer simply will not recognize the Afire.
[Kindle Fire General] sd_shadow:
you still get boot menu?
[Kindle Fire General] meXico12:
Negative. Just the logo loop. No boot menu and no twrp menu.
[Kindle Fire General] sd_shadow:
is "Fire" Yellow or blue?

[IMG="stock"]http://www.letechnophile.net/wp/wp-content/uploads/KindleFire_BootLogo.jpg[/IMG]

[IMG="FFF"]http://www.jayceooi.com/wp-content/uploads/2012/05/Kindle-Fire-Bootloader-FireFireFire.jpg[/IMG]
[Kindle Fire General] viiblades:
OtterX installation failure

Hi Everyone!

Decided to install OtterX today, did everything as per instructions (http://xdaforums.com/showthread.php?t=2671619), exactly as written, "adb push" worked at the beginning.

Now, at step 5 "adb push" stopped working. I was in TWRP and couldn't do anything. Rebooted a few times - same result.

So, after some thinking, I decided to go back to old state and don't know why I flashed old TWRP via KFU. Somehow it managed to return back old FFF booloader.

Now I can't do anything further. Can boot into TWRP, can issue fastboot command (but most of them doesn't bring any results; can re-flash recovery though). "adb push" doesn't work. Can't revert back to OtterX u-boot, but can go back to TWRP for OtterX.

Understand that messed up with partitions and some other stuff, but any help will be much appreciated.

Thanks in advance, guys!
[Kindle Fire General] sd_shadow:
don't use TWRP 2.8.X.X use 2.7.1.0 (OtterX)

flash OtterX Bootloader, download otterx-u-boot_v2.05.bin, verify md5:241a3fd1edad0a0d95886ddeb4693e1c

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

fastboot reboot

if that works, flash otterx-twrp-2.7.1.0-recovery.img

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

try selecting OtterX partitions, reboot, wipe cache in twrp, reboot, format data, wipe>advances, check everything, swipe to wipe

then try adb push
[Kindle Fire General] viiblades:
sd_shadow, thanks a lot! What a lame move from my side :)

I actually re-flashed u-boot with fastboot already and then did all the moves again. Used TWRP 2.8.X.X though. "adb push" didn't work, obviously, but I managed to get it done via "adb sideload".

Works now, setting up. Will see what happens next.

One Q: CM propose some updates for the ROM, but I guess I shouldn't install them?
[Kindle Fire General] sd_shadow:
guess i haven't tried sideload on 2.8.X.X, would not think side load would work, if error was unauthorized device error

which build did you install? likely you installed an older build, and there is an update. updates should install fine although in some cases a factory reset in TWRP may be necessary.

CM OtterX downloads
[Kindle Fire General] viiblades:
sd_shadow, I installed the one which is available by the link in main topic (cm-11-20140608-UNOFFICIAL-otterx.zip).
[Kindle Fire General] sd_shadow:
yes, that is very old.

but still your choice, updates should install fine, but may not.

safe to stay on current build or download newer, factory reset in twrp, and install newer
[Kindle Fire General] meXico12:
I can't seem to be able to post under my original question, so hopefully you will notice this. The color of the logo is neither yellow or blue, but rather it is white. Thanks again for following up with my issue.
[Kindle Fire General] sd_shadow:
Like this? [IMG="OtterX Bootloader"]http://i1248.photobucket.com/albums/hh500/sd_shadow/2014-06-08_12-01-42_832_zps996eb216.jpg[/IMG]
[Kindle Fire General] meXico12:
Yes, EXCEPT mine does not show the small text message at the bottom of the screen.
[Kindle Fire General] sd_shadow:
and you have tried power off, connect to wall charger.
[Kindle Fire General] meXico12:
Yes, this is what I get whether powered thru the computer and/or an A/C wall outlet. White logo screen but no small text message on the bottom of the screen.
[Kindle Fire General] sd_shadow:
maybe time to read this

Firekit LiveUSB repair kit 1.1- when you're about to kill Windows
[Kindle Fire General] meXico12:
Let me clarify. Completely power off. Black screen and power light off. Power back on with a/c from an electric wall outlet. I get black screen with white kindle logo which appears, disappears and reappears continuously and no small test message on the bottom of the screen. The same thing when I power off and then repower with the computer usb connection.

---------- Post added at 02:32 AM ---------- Previous post was at 02:25 AM ----------

Great! There is hope. I'll try the Fire Kit and report back.
[Kindle Fire General] meXico12:
OK. I did the usb tick and short and now I have a black screen with the word kindle in blue and the word fire in red. I've read till my eyes are popping out, but I'm at a loss as to what step I should take next. I had a early early twrp display, and I did a reboot on it. Now I have the screen described above. I can start over with the usb trick short and get back to the twrp and go from there. Suggestions please. Thanks.
[Kindle Fire General] sd_shadow:
all that has happened since your last post?
[Kindle Fire General] meXico12:
OK, I used the "short circuit" described in you post and successfully got a version of twrp. Afterwards, I was able to finally get u-boot v2.05 and twrp 2.7.1.0 installed after following the guide. I was down to step five, BUT, I was unable to push the rom img and gapps to the sdcard. I rebooted, and as before, I am back to where I started with a black screen, repeating white kindle logo. So, I think tomorrow, I'll start over and see if I can get this done. If I am unable to push the the cm 11 rom and gapps, then I'm stumped. I do not know how to verify whether I can push these into twrp 2.7.1.0. However, before getting to twrp 2.7.1.0, I was able to push u-boot 2.05 and twrp 2.7.1.0. Problem seems to be the final push while in twrp 2.7.1.0. If I power down at any point in this process, I'm back to square one. Hope this makes sense, cause I'm goofy eyed at this point. I really need some help doing that final push into twrp 2.7.1.0. Thanks.
[Kindle Fire General] meXico12:
Easier said than done! I can still get into twrp 2.0.0.0 using Firekit LiveUSB repair kit 1.1. I can push the new Uboot v2.05 and twrp 2.7.1.0, but when I attempt to install them, I'm getting a message that I need to "format" the drive? I think the partition sizes etc. changed when I was previously able to install uboot v.2.05 and twrp 2.7.1.0 such that now the older twrp I get after using the Firekit LiveUSB repair kit 1.1 cannot recognize the new partition sizes. I'm stuck with the old twrp. Will a factory cable help me resolve this dilemma? Suggestions please. Thanks.
[Kindle Fire General] sd_shadow:
Is the "format" the drive? error on the pc? if so Choose a quick format (if possible) and format it as "fat32", block size "4096".
[Kindle Fire General] meXico12:
Yes, it is on PC. I'll format fat34 as described and start over with Firekit fix and report back. Thanks for all your patience.
[Kindle Fire General] sd_shadow:
if you format, copy or push twrp/Bootloader zips and install them, shout not need Firekit
[Kindle Fire General] meXico12:
No go on format. When I plug usb into computer, it boots into twrp 2.0.0.0. I check device manager and it shows Kindle and drive E. So, I push uboot 2.05 and twrp 2.7.1.0 with no problem and they show up when I press install, but it doesn't install. I checked the drive and properties, and it is completely full with no room left. When I try to format, it says insert disk and try again. If I reboot then I lose computer recognition of device when I try to format, but the "devices and printers shows the Kindle fire. Bottom line, I apparfently cannot format from pc.
[Kindle Fire General] sd_shadow:
edit:

wipe>advanced check all boxes swipe to wipe
[Kindle Fire General] meXico12:
In twrp 2.0.0.0, there is only wipe individual items. I wiped I wiped everything available in the wipe menu. Under advanced, I pressed partition sd card, but the menu only gives me EXT3 or EXT4. I used EXT4 and rebooted system, but still no apparent sd card. Unable to format. Windows lets me get to "format" stage, and warns me that all data will be lost, but when I press format, it says unable to format. Computer shows the Kindle as a storage device.??????
[Kindle Fire General] sd_shadow:
what does 'doesn't install' mean?what happens?

with kindle in twrp

on pc download openrecovery-twrp-2.6.3.1-otter.img verify md5

place in folder c/adb or where you have adb/fastboot files (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe)

in command prompt enter

fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img

select reboot in twrp

fastboot reboot

---------- Post added at 05:54 PM ---------- Previous post was at 05:39 PM ----------

try mount> check system> mount usb
[Kindle Fire General] meXico12:
Don't know how, but finally got a format complete on pc. I was hoping to be able to say success, but here's where I am now. U-boot v2.05 and Twrp v2.7.1.0 installed. Pushed otterx rom and gapps into sd card. Installed otterx rom and gapps. Did system boot, and everything seemed to be going great and otterx appears to look good, but I get an error message on the gapps stating:

Encryption was interrupted and can't complete. As a result, the data on your tablet is no longer accessible .Tor resume using your tablet, you need to perform a factory reset. When you set up your tablet after the reset, you'll have an opportunity to restore any data that was backed up to your google account.

Then at the bottom of the screen it says "reset tablet" Also at the very bottom of the screen is a return symbol.

I'm kind of afraid to do anything at this point until I hear back from you. My temtation is to press "reset tablet". Let me know please? Thanks.
[Kindle Fire General] sd_shadow:
check the partition sizes

Started a Thread [How To] Fix Lollipop Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
[Kindle Fire General] meXico12:
Success! mostly. I followed the link you provided and all three partitions were significantly off. I did not reinstall uboot, but did reinstall twrp 2.7.1.0. Again after checking, partitions were closer, but not exact. I wiped, repaired and formatted each partition and then rebooted to recovery. I wiped and formatted each of the partitions again, and this time cashe and system were right on, and data was on 5000. Rather than risk getting into some kind of loop, I rebooted recovery, and fastboot mode came up. Don't know how that happened, since its the first time I've seen it on this device. Since it was there, I pushed the rom and gaffs as an img, and then flashed them. Everything came up fine. I now have a nexus like device. I even feel safe enough now to snap the back cover on the device since I don't think I'll have to try the firefix again. I cannot tell you how much I appreciate your attention and suggestions. You have the patience of Job as they say, and you're a big time asset to this website. Thank you again for all of your help.
[Kindle Fire General] byclo:
adb push problems / workaround

I just had a very hard time upgrading to OtterX, but I was ultimately able to do it after discovering a workaround so I wanted to share in case anyone else has a similar problem.

I was following the steps at the beginning of this thread which were successful through step 4 "WIPE PARTITIONS IN RECOVERY". When I tried to continue with step 5 "DOWNLOAD / PUSH CM11 ROM and GAPPS TO SDCARD VIA ADB" I ran into a big problem. ADB Push would not work, giving me the error "device offline." ADB was working fine with the old version of TWRP, so here's what I did:

I rebooted into fastboot and flashed the stock version of TWRP (using the command "fastboot flash recovery <Old_twrp.img>"). Then I rebooted into recovery. This allowed me to use ADB to push files, but it could not mount the sdcard. So I pushed the rom for CM11, gapps, and the OtterX version of TWRP into /cache/.

So now everything is set up and all of the files are on the device. So I re-flashed TWRP for OtterX (from the /cache/ folder )and rebooted into recovery. At this point I was back on track with step 5, and flashed CM11 and gapps (again from the /cache/ folder where I pushed them earlier).

This flip flop between recovery images may seem redundant, but it was the only way that I could get roms onto my device. Once I flashed everything, it booted up into CM11 for OtterX and now everything is working perfectly. If anyone can think of a better way that I should have done this, please feel free to let me know. Otherwise, I hope this post can help anyone else who runs into this problem pushing files while running TWRP for OtterX.
[Kindle Fire General] sd_shadow:
which twrp versions? file names?
[Kindle Fire General] byclo:
The original version of TWRP I was using was "openrecovery-twrp-2.8.3.0-otter.img"

The OtterX version of TWRP was: "zip-otterx-twrp-2.8.3.0-recovery.zip"

[edit] Now that I have OtterX installed, I flashed the openrecovery-twrp-2.8.0.2-otterx.img from techerrata[dot]com/browse/twrp2/otterx. This restored adb functionality.
[Kindle Fire General] sd_shadow:
edit: OtterX twrp 2.8.2.0 should have mtp on by default so you don't need adb push

other wise just use OtterX 2.7.1.0 twrp