[RECOVERY][dlx] TWRP 3.0.0-0 touch recovery [2016-02-06]

Search This thread

Crewski

Senior Member
Jul 2, 2011
180
174
Cincinnati, OH
Not that it isn't documented already, but just wanted to add that mine is rebooting when trying to make a backup. I've tried about 5 times....all end in a reboot.
 

Crewski

Senior Member
Jul 2, 2011
180
174
Cincinnati, OH
Finally was able to make a backup without it rebooting. Not sure if it's related, but to get into recovery this time I turned off fast boot, powered off the phone, the booted with volume down. Before I was just restarting the phone while holding volume down. I don't understand how/if coming from being off makes a difference or not, but it was the only thing I did differently.

Sent from my HTC6435LVW using Tapatalk 2
 

jschill31

Senior Member
Jul 14, 2010
827
184
Midwest
OP,

I was just on the TWRP git and looked at your BoardConfig.mk file, one thing I notices is that it flags the display as 800x1280. Shouldn't this be 1080x1920?

# TWRP specific build flags
DEVICE_RESOLUTION := 800x1280
TW_INCLUDE_DUMLOCK := true
RECOVERY_SDCARD_ON_DATA := true
BOARD_HAS_NO_REAL_SDCARD := true
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_NO_USB_STORAGE := true
RECOVERY_GRAPHICS_USE_LINELENGTH := true

Cheers
 

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,582
KC MO
www.teamw.in
OP,

I was just on the TWRP git and looked at your BoardConfig.mk file, one thing I notices is that it flags the display as 800x1280. Shouldn't this be 1080x1920?

# TWRP specific build flags
DEVICE_RESOLUTION := 800x1280
TW_INCLUDE_DUMLOCK := true
RECOVERY_SDCARD_ON_DATA := true
BOARD_HAS_NO_REAL_SDCARD := true
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_NO_USB_STORAGE := true
RECOVERY_GRAPHICS_USE_LINELENGTH := true

Cheers

The resolution flag determines which theme gets applied. At this time we don't have a 1080x1920 theme.
 

rhettnis

Senior Member
Oct 17, 2010
91
16
ive pretty much given up any hope for making a backup right now. Basically right now our "recovery" isn't for actually recovering anything, its basically just good for wiping data and installing zips.
 
Last edited:

zounduser

Senior Member
Mar 2, 2012
6,025
1,934
sioux falls SD
ive pretty much given up any hope for making a backup right now. Basically right now our "recovery" isn't for actually recovering anything, its basically just good for wiping data and installing zips.

cwmr is making and restoring backups just fine. dont get me wrong, i would wat rather b using twrp, but its not ready for us yet.
 

rhettnis

Senior Member
Oct 17, 2010
91
16
cwmr is making and restoring backups just fine. dont get me wrong, i would wat rather b using twrp, but its not ready for us yet.

I get the same results with cwr, it just seems to go farther along in the process before it reboots, but the end result is still no successful backup. I was thinking it was just me, but it seems a lot of people are having the same problem with both recoveries.
 

idkwhothatis123

Senior Member
Oct 16, 2010
1,874
461
I get the same results with cwr, it just seems to go farther along in the process before it reboots, but the end result is still no successful backup. I was thinking it was just me, but it seems a lot of people are having the same problem with both recoveries.

I went through several attempts to backup and got reboots as well. The way i got it to perform backup properly is to flash the root zip, then perform the backup. works like a charm every time for me. Idk why it works, but i'll take it for now
 

rhettnis

Senior Member
Oct 17, 2010
91
16
I went through several attempts to backup and got reboots as well. The way i got it to perform backup properly is to flash the root zip, then perform the backup. works like a charm every time for me. Idk why it works, but i'll take it for now

ill give this a try


Nope, didn't work. What root zip did you use?
 
Last edited:

andybones

Retired Forum Moderator / Inactive RD
May 18, 2010
15,092
15,480
Google Pixel 5
why is this not preferred over CWM?
I can't even make a nandroid using CWM.
I was sucessful first time using TWRP flashing the root.zip before.

I haven't tried restoring it but i think it'll be jsut fine..

is it for installing roms u want to CWM??


when doing a nandroid backup on CWM it said finished but it was 32MB small, when TWRP finished, the nandroid is 1.3GB large lol.
 

zounduser

Senior Member
Mar 2, 2012
6,025
1,934
sioux falls SD
why is this not preferred over CWM?
I can't even make a nandroid using CWM.
I was sucessful first time using TWRP flashing the root.zip before.

I haven't tried restoring it but i think it'll be jsut fine..

is it for installing roms u want to CWM??


when doing a nandroid backup on CWM it said finished but it was 32MB small, when TWRP finished, the nandroid is 1.3GB large lol.

Hey andy, i know u bro, from rez. Anyways....i would way rather use this over cwmr, but its not sized right, i really cant wait until it is 100%!

RATTLED FROM MY ONE XL USING ICS TAPATALK 2
 

andybones

Retired Forum Moderator / Inactive RD
May 18, 2010
15,092
15,480
Google Pixel 5
I believe so. I used it for about 5 seconds......then switched to cwmr. Which i hate!! Backups, and restores take about 15 mins!!! No joke! :mad:

RATTLED FROM MY ONE XL USING ICS TAPATALK 2

I can't even get CWM to backup :(

6.0.1.2 the size is friggin 32MB lmao
and 6.0.1.5 keeps rebooting


.. I think installing roms on TWRP is a prob, ill prob just use CWM to install ROMs, and TWRP for everything else LOL
 
Last edited:

tnez

Senior Member
Dec 30, 2010
613
81
The man issue is flashing Roms, fails. Or so its been said. UKB called for CWM so I went with it. I dont care much about back ups due to storage limits, Rom zips and backups just kill the 11gb that the DNA has available.

The sizing straight sucks too. I also don't like the way wipe options are worded. One option that I'm used to using wipes the SD card on twrp

Sent from my HTC Droid DNA
 
  • Like
Reactions: andybones

rayfin

Senior Member
Jan 19, 2011
169
95
www.derekross.me
I could have sworn the past week I've used ADB in recovery... tonight I needed to and I'm getting List of devices attached ???????????? no permissions. While ADB works fine when Android is fully booted. Maybe I wasn't using ADB in recovery... Anyone else able to get it to work or am I having some sort of late night derp?
 

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,582
KC MO
www.teamw.in
I could have sworn the past week I've used ADB in recovery... tonight I needed to and I'm getting List of devices attached ???????????? no permissions. While ADB works fine when Android is fully booted. Maybe I wasn't using ADB in recovery... Anyone else able to get it to work or am I having some sort of late night derp?

sudo first and adb kill-server then use adb or set up the correct udev permissions.
 

jonno95

Senior Member
Dec 2, 2010
270
130
I can't even get CWM to backup :(

6.0.1.2 the size is friggin 32MB lmao
and 6.0.1.5 keeps rebooting


.. I think installing roms on TWRP is a prob, ill prob just use CWM to install ROMs, and TWRP for everything else LOL

i've only installed 2 roms and both went perfectly on TWRP. CODIS v1.0.0, then UKB DNA 1.1.0 i know nit said that on UKB DNA 1.0.0 that he had to ruu twice to fix sd card issues, but maybe he figured it out for 1.1.0

edit: i should note that i did take most of the default options in aroma to minimize possible issues.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 43
    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!

    CHANGELOG for 2.8.7.0:

    -Initial ground work for software drawn keyboard (_that)
    -Fix handling of wiping internal storage on datamedia devices (xuefer)
    -Allow DataManager to set and read values from the system properties (xuefer)
    -Fix crash when taking screenshots on arm64 devices (xuefer)
    -Fix error message after an ORS script completes (Dees_Troy)
    -Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
    -Add system read only option – more details below (Dees_Troy)
    -Add resize2fs and GUI option to run resize2fs (Dees_Troy)
    -Fix crash loop caused by empty lines in AOSP recovery command file (_that)
    -Prevent duplicate page overlays such as multiple lock screens (mdmower)

    Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

    System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

    resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

    This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

    DOWNLOAD:
    Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
    1) Download the latest version from our website on your device
    2) Reboot to TWRP
    3) Hit Install and tap the "Images..." button in the lower right
    4) Browse to the location of the TWRP image on your device and select it
    5) Select recovery from the partition list and swipe to flash
    OR:
    You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!

    BUGS:
    If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

    SUPPORT:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.
    11
    [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]
    11
    Okay, here it is. This is built with the current cm11 kernel. I fixed the small font problem everything flashes, backs up, and restores fine.

    TWRP 2.7 Beta
    10
    [RECOVERY] TWRP 2.5.0.0 touch recovery [2013-04-09]
    9
    Twrp resized!!!

    Well I messed around and finally sat down and re-sized everything for the DNA :)

    Looky here!! All the touches/buttons work. Just need to size up a few images and viola!!

    uploadfromtaptalk1356053306567.jpguploadfromtaptalk1356053323813.jpguploadfromtaptalk1356053350341.jpguploadfromtaptalk1356053360741.jpguploadfromtaptalk1356053372781.jpg


    Sent from my -HTC ReZound-