yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] smirkis:
I spoke with deestroy n were gonna try to get it resolved. yay lol

they don't have our device so its hard to know what doesn't work. looking forward to testing the update :)
[Kindle Fire Android Development] DJLamontagneIII:
Sweet id switch back if it was fixed i like how its skinable
[Kindle Fire Android Development] nckfrs:
i cant install any zip files i get unknown md5 error just rooted tonight
[Kindle Fire Android Development] kinfauns:
I just tried playing around with the new version some more and I can confirm the above...

Here's what I get from TWRP's Install section for the few ROMs I tried to test flash.

-- Verify md5 for /sdcard/update-cm7-wipeall.zip

-- No md5 file found, ignoring

-- Installing /sdcard/update-cm7-wipeall.zip ...
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "blaze" || getprop("ro.build.product") == "blaze"
E:Error in /tmp/sideload/package.zip
(Status 7)
* Verifying filesystems...
* Verifying partition sizes...
Error flashing zip '/sdcard/update-cm7-wipeall.zip'

This version is really not ready for use. Hang on to your version 2.0.0 for at least a little while longer.
[Kindle Fire Android Development] raiderep:
While I agree its not ready it did work for me to make a back up and then install Hashcode's test rom and restore a back up another user posted for us.
[Kindle Fire Android Development] treUse:
Reboot to system works perfectly fine for me, and has in previous versions as well.
[Kindle Fire Android Development] dw9906:
Reboot to system works fine for me to. Always has.
[Kindle Fire Android Development] Sblood86:
Yeah it will, until you assign the bootmode outside of using the power button from firefirefire (in other words, use fastboot, adb or 'reboot recovery' from a rom to set the bootmode) the reboot wrappers won't set it back. It is actually a relatively simple solution and Smirkis' is familiar with what's required if he is talking to the OP I would expect a solution for this.
[Kindle Fire Android Development] kinfauns:
If you used the power button to get into recovery while FFF was loading, reboot to system will work fine. That's not what's being discussed here.

If you got to recovery that way, the bootmode was never changed and stayed (presumably) on 4000. So, hitting the reboot from within TWRP will continue to boot in normal mode and it "seems" to work fine.

Try setting the bootmode to recovery (5001) and restart the device to get to TWRP. Then if you try rebooting into the system, it will go back into TWRP because TWRP does not change the bootmode back to normal (4000) before attempting to reboot into the system.

The same problem exists for all the reboot options in 2.1.0... whether normal, recovery, or bootloader, it will not change the bootmode to the appropriate value before restarting the device. As a result, the device will just reboot using whatever bootmode is already set.

EDIT: What Sblood86 said above... I'm just longer winded.
[Kindle Fire Android Development] dw9906:
I knew what you meant, but that's not what you explained in your first post. Had you been this specific in your initial post then this conversation would have never happened. :D

On another note, this recovery might as well be forgotten about. Doesn't seem like they are ever going to fix it completely.

EDIT: Didn't mean for that to sound like i was being rude to kinfauns. That's not how i meant it to be. :)
[Kindle Fire Android Development] kinfauns:
I wasn't offended by your post, so you shouldn't take this post that way either... but I don't think you read the thread very carefully before you posted. I think I was fairly clear about what the problem entailed in my first post of this thread. I made it a point to mention that TWRP does not set the bootmode properly before rebooting. In addition, smirkis noted that he's gotten the developer's ear in getting some problems fixed, so things are looking up in terms of getting past these issues.

Furthermore, TWRP can't simply be "forgotten about" because the super majority of articles on the Internet detailing steps in modifying the Kindle Fire mention TWRP. New users will continue to use TWRP just for the fact that it's simply the more recognized recovery program of the two we have available.

FWIW, I'm more hopeful than ever TWRP will get fixed and continued to be developed.
[Kindle Fire Android Development] dw9906:
I really do hope it gets fixed. I really like the themeing capabilities. It's a great recovery, just doesn't seem to have much support.
[Kindle Fire Android Development] d33dvb:
clockwork recovery ftw.
[Kindle Fire Android Development] koop1955:
Works Great

Thank you, Tera and all Team Win members. Flashed, updated and seems to be working fine. I have a themed version of TWRP and it retained the theme.

Thanks again.
[Kindle Fire Android Development] K4get:
Hello first off thank you for the recovery.

i installed 2.2.2.1 using the flashable zip provided on page 18

tried to reboot into recovery from within recovery,

it rebooted into system instead. i don't know if this is a bug.

just wanted to inform you.

After trying to reboot into recovery from within recovery a second time it worked

as designed.

thank you k4get
[Kindle Fire Android Development] Jacktheskipper:
flashed 2.2.2.1 via the flashable zip on the last page, it worked like a charm ... thanks for the great work, no bugs to report so far!
[Kindle Fire Android Development] Stage:
Thank you for the new update!
[Kindle Fire Android Development] smirkis:
No Offense, but this flashable zip does not contain any kind of md5 check before replacing the recovery partition. i find this dangerous and highly recommend using smirkit for recovery/bootloader installations. its been updated to support 2.2.2.1
[Kindle Fire Android Development] mendoozer666:
Thank you! I was fearing that my wife would have to kill me. Got Kindle working again. Now that I made a backup, I feel so much better! I clicked the "Thanks" button!!
[Kindle Fire Android Development] nazimster:
wow installed and its working

now i am using ICS 4.0.4

thanks
[Kindle Fire Android Development] HKSpeed:
do i flash the 2.2.2.1 zip file using TWRP? I have 2.0 installed on my KF.
[Kindle Fire Android Development] Stage:
Yes. Flash it in TWRP.
[Kindle Fire Android Development] Thepooch:
agreed not to hurt Tera Tike`s feelings because it was nice of her to do it but this is the safest way http://xdaforums.com/showthread.php?t=1500935
[Kindle Fire Android Development] a1exus:
I'm using AKF and I have TWRP 2.1.1. I want to update my recovery and I've tried using Goomanager, which says "no recovery was found for your device" when I use "install openrecoveryscript".

any ideas?
[Kindle Fire Android Development] verfahrer:
You can download TWRP 2.2.2.1 from the post 180: http://xdaforums.com/showpost.php?p=30780737&postcount=180

After copy this file in the Kindle root you can update (flash) your recovery direct in TWRP
[Kindle Fire Android Development] a1exus:
thanks)
[Kindle Fire Android Development] evgeny9:
The same for me... Can anyone help, please?
[Kindle Fire Android Development] Thepooch:
It`s really quite simple use smirkit http://xdaforums.com/showthread.php?t=1500935
[Kindle Fire Android Development] a1exus:
you can use same link that was provided for me and apply it through TWRP, I was able to install it without any issues!
[Kindle Fire Android Development] Thepooch:
As well if your familiar with using KFU just delete twrp.img in the recovery folder and it will download the new version and install it for you. So now you have 3 different ways to replace TWRP which route you take is your choice.
[Kindle Fire Android Development] evgeny9:
Thank you, guys, for the fast responses, very much!

I already started with *.zip through TWRP and it worked without any problems.

And due to your answers now everyone reading this thread really has 3 different ways to replace TWRP :good:
[Kindle Fire Android Development] Dees_Troy:
Updated to 2.3.0.0!
[Kindle Fire Android Development] x-y-no:
I tried flashing 2.3.0.0 and hardly any touchscreen actions were working for me. Had to go into fastboot and flash the old one back again.
[Kindle Fire Android Development] sthomas38:
Same for me...

Envoyé depuis mon Amazon Kindle Fire avec Tapatalk
[Kindle Fire Android Development] yuidaoren:
Sadly, ditto here. (Object lesson: Always keep backups of everything. ;) )
[Kindle Fire Android Development] powerpoint45:
That's unfortunate. I was excited about the update.
[Kindle Fire Android Development] K4get:
Hello I an running eye candy Kendal fire v3.6

And I have the Galaxy nexus mod .

Goo-manager doesn't see the otter so it says no available update

What can I do to get 2.3.0.0

Anyone care to make a downloadable zip for install in recovery
[Kindle Fire Android Development] x-y-no:
You can get it at http://teamw.in/project/twrp but I don't recommend it because it doesn't work.
[Kindle Fire Android Development] brizey:
Lol, I love TWRP, but the .0.0 releases never work. But it has by far the best UI.
[Kindle Fire Android Development] AstorDev:
Today I have updated my kindle from twrp2.0 to 2.3. When recovery loads I see that interface changed and version is really 2.3. But touches doesn't work correctly. I mean when I click "install" button nothing happens, when I click on some other button wrong menu is shown. It's really bad, because recovery is very useful thing. Does anyone know how to fix this?

(I can upload a video with this bug)
[Kindle Fire Android Development] jamminjon82:
Read numerous posts above yours, the build is broken for now. Reflash an old one

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

Use that one
[Kindle Fire Android Development] topolovich:
Not sure if anyone posted this as I'm running to work and don't have time to read through it, but the problem with this is that it is in portrait mode despite being displayed in landscape. If you look at it and press where the buttons would be if it was in portrait it will work. Not ideal... obviously... but allows you to flash this old one back pretty easily.

Cheers...
[Kindle Fire Android Development] soupmagnet:
Nice find
[Kindle Fire Android Development] Dees_Troy:
2.3.1.0 out with various bug fixes. If touch is still not working, someone come by our IRC channel that has adb working. Thanks.
[Kindle Fire Android Development] drinkhere:
Is someone planing on making a zip for 2.3.1.0 ?

Thanks
[Kindle Fire Android Development] verfahrer:
This build is still not working correct, the problem is in my opinion not in touch but in orientation of buttons on the screen.
[Kindle Fire Android Development] Dees_Troy:
Like I said, if you want it fixed, come by the IRC channel and know how to use ADB. I don't have a Fire and in fact, I've never even held one in my hands. I can't fix it without a willing and capable tester.
[Kindle Fire Android Development] verfahrer:
Unfortunately I have no idea of IRC-clients. We will wait for an experienced IRC-user .
[Kindle Fire Android Development] tedr108:
Dees_Troy, I'm game. You want to give me your IRC channel? It's not jumping out at me anywere. :o)
[Kindle Fire Android Development] sthomas38:
http://webchat.freenode.net/?channels=twrp
[Kindle Fire Android Development] webdroidmt:
By chance, are you using it with a TWRP theme from a previous version?

Mike T
[Kindle Fire Android Development] verfahrer:
I have only installed the last build to test. But because touch didn't work correct, I installed with "try and error"-method the previous version 2.2.2.1 again.
[Kindle Fire Android Development] webdroidmt:
Well, seems like nothing to do with TWRP theme. I just installed it without any theme, went into settings and couldn't get out. Both the home & back key failed to respond to touch.

Mike T
[Kindle Fire Android Development] dw9906:
If it's not de-bugged by tomorrow, I'll drop by irc and lend a hand.

Sent from my Galaxy Nexus
[Kindle Fire Android Development] verfahrer:
I wrote that the problem is probably related to orientation of buttons. For example back key works when you tap somewhere in the upper left on the screen
[Kindle Fire Android Development] tedr108:
FYI...

Spent an hour or 2 on #twrp irc with Dees_Troy. He gave me a couple of test twrp images to run, but there were still alignment issues. He had to get home, so I told him that I would map out the actual location of all of the buttons, which I have now done. Hopefully, with this complete information, he will be able to figure things out easily enough. Back at it tomorrow...

Followup: In case any of you are interested, attached is a .jpg of how the buttons actually register on the current TWRP 2.3.1.0. The top part is how the buttons look (standard layout). The bottom part is how they actually register. It appears that the entire thing was rotated 90° counter-clockwise, but the main buttons kept the same orientation (wider than they are high).
[Kindle Fire Android Development] firered365:
We should put it in potrait instead of landscape.
[Kindle Fire Android Development] brizey:
The Nexus 7 version is portrait and I prefer it that way.
[Kindle Fire Android Development] Dees_Troy:
Touch should be all fixed now in 2.3.1.1, confirmed by my tester, tedr108. Thanks.
[Kindle Fire Android Development] sthomas38:
Thanks, so portrait or landscape? :)

Envoyé depuis mon GT-I9000 avec Tapatalk
[Kindle Fire Android Development] VaksenDK:
Then that is the reason for all our trouble, I guess?

Since 2.3 is totally rewritten based on aosp Jelly Bean source, and Google have decided that from Jelly Bean all 7" tablets should run phoneUI, then everything gets messed up, when the recovery still is run in landscabe as a tablet, while the system sees it as a phone.

Could be interesting to see how it would run in portrait/phoneUI.
[Kindle Fire Android Development] tedr108:
Landscape, as before.
[Kindle Fire Android Development] webdroidmt:
Any idea if this new version is compatible with a TWRP theme from 2.2.2.1?

@tedr108

Thanks for testing.

Mike T
[Kindle Fire Android Development] tedr108:
Are you asking if the nandroid backups are compatible? According to the TeamWin website, they should be. Haven't tested it myself. I personally always do a nandroid when I load a new recovery, just to be safe. :)
[Kindle Fire Android Development] mlkjuggalo:
here is a zip to flash new TWRP 2.3.1.1 :)
[Kindle Fire Android Development] portezbie:
Was just going to ask for this, thanks!
[Kindle Fire Android Development] Dees_Troy:
Should be compatible but you may be missing a few changes like adb sideload.
[Kindle Fire Android Development] verfahrer:
The touch-problem is solved. Thanks! But I could not restore with this new version some backups from prior versions of TWRP. Do I need to make any settings in the TWRP?
[Kindle Fire Android Development] Dees_Troy:
Do you get any errors in twrp? If so get a log.
[Kindle Fire Android Development] webdroidmt:
Thanks, shouldn't be an issue if I really need to use it, I can just disable the theme.

Mike T

---------- Post added at 07:57 PM ---------- Previous post was at 07:55 PM ----------

No, thanks for the reply but Dees_Troy answered my question.

Mike T
[Kindle Fire Android Development] verfahrer:
Restore process goes through without errors, but after booting boot animation appears and running continuously. The device does not boot. If I turn off the device and then get into recovery, install the version 2.2.2.1 again, so I can restore my old backups
[Kindle Fire Android Development] firered365:
Can you make one for portrait? Some stuff like Pimp my ROM is in portrait.
[Kindle Fire Android Development] Dees_Troy:
No, it's not simply a matter of saying, I want portrait instead of landscape. The framebuffer is defined by the kernel. Any rotation has to be done in software and the recovery graphics engine doesn't have a rotation option. If you really want rotation, feel free to download the source and code it, but I gotta warn you... it won't be easy. ;)
[Kindle Fire Android Development] firered365:
Oh. I don't how to do that, anyways, but OK.
[Kindle Fire Android Development] dw9906:
I got the same problem. I backed up with the newest recovery and restored, but it wouldn't boot. Wiped then flashed a ROM. Wouldn't boot. Went back to previous.

Sent from my Galaxy Nexus
[Kindle Fire Android Development] tedr108:
I was just getting ready to do a restore this morning as a test. You saved me the trouble. Thanks for doing this and reporting back.
[Kindle Fire Android Development] tedr108:
@Dees_Troy (and all) -- been playing around with the backups/restores a little. The backups from 2.3.1.1 seem to be good. I just restored one with 2.2.2.1, and my KF is running just fine. So, the problem with 2.3.1.1 seems to be the restore feature. This is actually a logical conclusion from previous reports, but I just wanted to verify it.
[Kindle Fire Android Development] jamminjon82:
Any way you could change designation from blaze to otter, that way people could automatically flash using goo manager?
[Kindle Fire Android Development] Ixthusdan:
Confirming that back ups are good with 2.3.1.1 but restores do not work. I used a back up from the new release and tried to restore, failed. Reverting to 2.2.2.1, same back up did fine. So, it is the restore function that has a glitch.
[Kindle Fire Android Development] Dees_Troy:
As it turns out, it's the wiping that appears to be problematic. In 2.3 we moved to make_ext4fs instead of mke2fs for wiping ext4 partitions (necessary on some other devices). You can verify by checking the box for "use rm -rf" under settings then running the restore again. The restore should work just fine.

I'll figure out something for switching back to mke2fs for the KF, but you can use the settings change in the meantime.
[Kindle Fire Android Development] soupmagnet:
For some reason I am unable to flash the stock update.zip in recovery, but I am able to flash any other ROM with no problem.

[CheckPartSize]Partition '/dev/block/platform/mmci-omap-hs.1/by-name/system' size is 189644800 - min size required is 536870912
script aborted: assert failed: check_part_size("/dev/block/platform/mmci-omap-hs.1/by-name/system", 536870912)
assert failed: check_part_size("/dev/block/platform/mmci-omap-hs.1/by-name/system", 536870912)E:unknown command [err_string]

E:Error in /sdcard/update-kindle-6.3.1.zip
(Status 7)
Error flashing zip '/sdcard/update-kindle-6.3.1.zip'
Updating partition details...
I:Set page: 'flash_done'

...any idea what "(Status 7)" means?
[Kindle Fire Android Development] tobiascuypers:
I'm pretty sure I've had the status 7 error before, and I think it means the the updater script is not correct or there is something wrong.

Is is just what I think tho, there is probably another reason
[Kindle Fire Android Development] soupmagnet:
I've tried downloading it (the update) 5 or 6 different times, checking the md5 each time.
[Kindle Fire Android Development] Sblood86:
Hehehehe.... Status 7 comes up when the device fails the assert check; the stock zip is listed as blaze, sounds like TWRP finally updated to use Otter for the board name.

I ran into a similar issue, wound up applying a really nasty hack to the build project as a work around (commit log), basically allows for the setting of Blaze and Otter during the build so either zips would work, course this doesn't help with the current issue but it points to the cause (perhaps Dees will get you a solid fix having the full story).

Edit: As a work around you can comment out the assert command in the zip if you go in and edit the update-script.
[Kindle Fire Android Development] kinfauns:
ROM install zip files (including the stock one from Amazon) contain an edify script with a set of commands for the recovery to follow. One of these commands is "assert" and it's typically used to verify that the device meets certain criteria before the install process takes place. If any one of them fails, the install process halts. In this case, the assert is checking to see if the system partition is the correct size. For whatever reason, the recovery or device thinks that partition is a lot smaller than it should be (check the numbers in the failed assert) and does not continue. I don't believe this is a problem with the update zip file because 536870912 bytes is the correct size for the KF's system partition. I don't know what version you're using, but I just flashed stock with 2.2.2.1 and it worked fine.

The reason other ROM zips are working is because they are much more relaxed about the things they check. In fact, they might not even check anything at all and just blindly write to the specified partitions. It's usually not a big deal for custom ROMs since it works nearly every time. Amazon just happens to be more careful because a bad update for them likely means support calls and returns.

Check your partitions.

EDIT: I missed the next page again. :mad:
[Kindle Fire Android Development] soupmagnet:
My partitions check out (at least the partition table does). I was just testing the new SoupKit to see if it would work with 2.3.1.1 . I'll switch back to 2.2.2.1 to see if that makes a difference. If not, it's quite possible I just fouled up somewhere. We'll see what happens.

[Edit:]Oh, I missed your edit.
[Kindle Fire Android Development] Tera Tike:
It seems from the assert check failed because it sees your system partition size as "189644800" smaller than the needed minimum size of "536870912".
[Kindle Fire Android Development] soupmagnet:
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818182656B
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B [B][U]536870912[/U][/B]B ext4 system
10 848822272B 2041053183B 1192230912B ext4 userdata
11 2041053184B 2309488639B 268435456B ext4 cache
12 2309488640B 7690000383B 5380511744B fat32 media
[Kindle Fire Android Development] Sblood86:
apparently I misread part of that; good catch kinfauns... clearly not related to the board name but still an interesting bit never the less (board name has still been a bit of a headache in the past lol)...
[Kindle Fire Android Development] Thepooch:
I have had the same error a few times all that was required was rebooting to recovery and it flashed fine.
[Kindle Fire Android Development] THANHVO31:
To whom headache with fastboot, driver, etc...

I upload flashable zip twrp 2.3.1.1 for people headache with fastboot.

Flash it via recovery. No fastboot, no driver...

Enjoy! :highfive:
[Kindle Fire Android Development] wolf45801:
is this version working good? any problems flashing or recovery?
[Kindle Fire Android Development] Iced666:
Install TWRP 2.3.1.1 - reboot - install cm10 otter - wipe cache/dalvik cache - bootloop :@

Galaxy S - AOKP JB
[Kindle Fire Android Development] Trialz Nexus One:
Tried this last night with new release of CM10/SGT 7. Worked perfectly with no issue. Mine was an update not a clean install.
[Kindle Fire Android Development] ygvuhb:
meet the same problem as others

use 2.3.1.1 full wipe & flash both twa_priv & Hashcode's rom

both cannot boot into android

just hold in the boot animation

flash back 2.2.2.1, everything work fine again
[Kindle Fire Android Development] eg08003:
Is it possible to switch it into portrait mode?
[Kindle Fire Android Development] linktohack:
Possible but not easy, and developers has no intention of working on such feature. :)
[Kindle Fire Android Development] Ixthusdan:
The format method used is the problem. The kindle does not like it.
[Kindle Fire Android Development] Dees_Troy:
Under settings, check the box for use rm rf
[Kindle Fire Android Development] dw9906:
Perry sure you said that already. Guess they missed that. :D

Sent from my SGH-T999
[Kindle Fire Android Development] That Baker Guy:
i did that and i still cant boot into anything. i have wiped everything and reflashed no go.