[RECOVERY] [jem] TWRP 3.0.0 touch recovery

Search This thread

davedru

Member
Oct 23, 2010
6
2
Using 3.0.1-0 (160403) can no longer use adb sideload. Reverting to v2.8.7.0 it works again. Anybody else found this?
 

redhonker

Senior Member
May 11, 2008
681
33
If I have 2.7, how could I upgrade? Is it safe to use Fire Flash?

Thanks
 
Last edited:

ipdev

Recognized Contributor
Feb 14, 2016
2,546
1
5,159
Google Nexus 10
Nexus 7 (2013)
Will try tomorrow. (Tonight is for tate....)

kfhd8-twrp-3.0.2-0-recovery
ResurrectionRemix-M-v5.7.2-20160804-jem

Sent from my SM-T230NU using XDA Labs

Edit.
Seems to works just fine.
 
Last edited:
R

r3t3ch

Guest
It is ok to install this Recovery, but where is the red kindle logo?
install latest RR ROM it take about 3 minutes to boot up is it normal?

The red logo is with the recovery's boot, and when you first turn on the kindle, the boot from the rom you flashed is what gets loaded. So you will only see the red logo when you reboot to recovery from android, fastboot, or recovery itself.

Long boot time is associated with the newer kernel changes in transi's roms. You can try flashing the boot.img in this rom and see if that fixes the problem, but I am not sure if it will work so remember to backup your current boot in recovery beforehand.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.



    CHANGELOG for 3.0.0-0:

    -Completely new theme - Much more modern and much nicer looking (by z31s1g)
    -True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
    -Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
    -Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
    -Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
    -Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
    -SuperSU prompt will no longer display if a Marshmallow ROM is installed
    -Update exfat, exfat fuse, dosfstools (by mdmower)
    -Update AOSP base to 6.0
    -A huge laundry list of other minor fixes and tweaks

    WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

    Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

    Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

    We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

    download: https://www.mediafire.com/folder/dtsa7p6v17436/jem
    fastboot -i 0x1949 flash recovery jem_recovery_xxxxxxxx.img

    restore old recovery:fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
    3
    build 160312: http://www.mediafire.com/download/nrd897fvhz8lnq1/jem_recovery_160312.img
    rework f2fs
    for test f2fs make backup, in "Wipe" twrp menu need try convert data and test boot rom, after convert cache and test new f2fs
    2
    USE IT AT YOUR OWN RISK!

    New test build 3.0.2

    https://www.androidfilehost.com/?fid=24665509702140752

    All the credits go to @r3t3ch