Originally Posted by Tera Tike

Here you Go.
Enjoy!


TWRP-Blaze-2.2.0.zip MD5: de0e307d1e543192c2846f85c4c18481

Thanks for this!

Originally Posted by asimons81

Thanks for this!

that zip only works on users with cm9/jb and doesn't check md5. jus sayin. a bad download could nuke it. still fixable, but jus sayin

I used it on MoDaCO. No issues. :thumbup:
Edit: it worked fine, but reboot system would just put you back in recovery. A work around was to hit power button on startup for normal boot. Used KFU to revert for now.

Store TWRP backups on NTFS?

---

Have space issues, also obsessively flashing various ICS and JB ROMs. When I find one for further testing I make a backup.

Question: can I move the TWRP backups to my PC for safe-keeping?
Using TWRP 2.2.0 and FFF 1.4a.

I would have done this automatically without thinking about it except even renaming a backup in TWRP gives an ominous warning about it not being able to be undone. Also saw a post from May alluding to whether storing backups on NTFS would cause issues.

TIA

Originally Posted by asimons81

Thanks for this!

thanks for the zip

True to force

---

Update so fast
Time to give it a try
True to force

No idme in TWRP 2.2.0

---

For some reason, TeamWin appears to have dropped the idme binary from the TWRP 2.2.0 boot image. If adb returns an error that idme cannot be found when setting the bootmode through adb while booted into this recovery, you can use pokey9000's bootmode binaries as a workaround.

Instead of...
adb shell idme bootmode 4000
use...
adb shell nbmode

Instead of...
adb shell idme bootmode 4002
use...
adb shell fbmode

Instead of...
adb shell idme bootmode 5001
use...
adb shell rcmode

I no longer have a Kindle Fire, so I can't test any of this, but it should work just fine.

Someone should ask Dees_Troy to get idme back into the next build, so this doesn't cause problems for users. It's bound to trip them up when using the various guides and it will probably break parts of KFU as well.

Originally Posted by kinfauns

For some reason, TeamWin appears to have dropped the idme binary from the TWRP 2.2.0 boot image. If adb returns an error that idme cannot be found when setting the bootmode through adb while booted into this recovery, you can use pokey9000's bootmode binaries as a workaround.

Instead of...
adb shell idme bootmode 4000
use...
adb shell nbmode

Instead of...
adb shell idme bootmode 4002
use...
adb shell fbmode

Instead of...
adb shell idme bootmode 5001
use...
adb shell rcmode

I no longer have a Kindle Fire, so I can't test any of this, but it should work just fine.

Someone should ask Dees_Troy to get idme back into the next build, so this doesn't cause problems for users. It's bound to trip them up when using the various guides and it will probably break parts of KFU as well.

Awhh thats why your gone someone needs to get you a kindle

Originally Posted by Thepooch

Awhh thats why your gone someone needs to get you a kindle

I've been busy with my own projects and some other conflicts kept me away from spending so much time on XDA. Besides, you do a good job helping out people on Q&A and there are plenty of KFU experts around to fill in the gaps. Like I was saying in one of the Nexus 7 threads in KF General... I got rid of my Kindle Fires and got a Nexus 7, but sometimes I miss having a KF. Occasionally, I wish I had decided to keep one of them around... Are you volunteering to buy me one?

You should definately have a donate button you deserve it for your excellent helps and dedication to all of us here in the kindle forums regardless much appreciation