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

Search This thread

bettzysdaddy

Senior Member
Jun 8, 2010
68
8
Sorry for the noobish question, what is adb and OP? What if you're on a Mac? I have the same issue of using the Goo manager and when reboot, I'm still on TWRP 2.0.0


---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------

[/COLOR]

And if you have a PC and adb this may help you out, this should be added to the OP for those whose have goo manager problems.
Here ya go
http://goo.im/devs/OpenRecovery/crespo4g/openrecovery-twrp-2.3.1.0-crespo4g.img


Sent from my Team Venom LTE with Z power[/QUOTE]
 

DominoDoug

Senior Member
May 15, 2010
345
32
Minneapolis
I am having issues with fixing permissions on 2.3 & 2.3.1. 2.2 on the other hand works fine. Haven't tried to do a restore yet.

Sent from my Nexus S 4G using Tapatalk 2
 

mercado79

Senior Member
Oct 4, 2008
1,049
395
Boston, MA
I am having issues with fixing permissions on 2.3 & 2.3.1. 2.2 on the other hand works fine. Haven't tried to do a restore yet.

Sent from my Nexus S 4G using Tapatalk 2

Just finished doing some testing on version 2.3.1.0. I had no problems running any of the tools/options, including backup, restore, and fix permissions.

I'm curious why you say you're having issues fixing permissions. Just an FYI, but fixing permissions no longer takes more than a few seconds. If that's what you're experiencing, you should know that it's SUPPOSED to finish super quickly. See the changelog which states:

Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)

Full disclosure. I had an issue restoring the backup, but that was only after I'd changed the settings to use rm -f instead of a standard format. I toggled that back, wiped dalvik manually just in case, and it restored without any problems.
 
  • Like
Reactions: DominoDoug

Nexism

Senior Member
Jul 21, 2011
270
31
I like the idea of "batch flashing" too much. I am switching back to TWRP as I seem to remember it working fine before I started messing wit the settings. I think it is important to have options when it comes to a recovery rather then just one and what that dev says goes (like not being compatible with other apps, that really burns me when I thought the whole idea of android was freedom from being rail roaded into one option). Enough of my rant, back to TWRP for testing. Keep ya'll posted
Thanks again Team Win for another option.
Sent from my phone using my thumbs and a keyboard
 
Last edited:

Nexism

Senior Member
Jul 21, 2011
270
31
No go. Installed but could not flash a few thins I use like wipe all boot animation and font packs...I am sad again.

Sent from my phone using my thumbs and a keyboard
 

matthew0776

Senior Member
Dec 22, 2012
6,030
8,736
Chicago
Re: [RECOVERY] TWRP 2.3.3.0 touch recovery [2012-12-19]

Using twrp 2.3.3.0 and when I do a factory reset and flash new rom it not prompting me to sign back into Google and set up phone... Is twrp fully functioning correctly on ns4g. Have it on Nexus Galaxy and love it....!

Sent from my Galaxy Nexus using xda app-developers app
 

jesusice

Senior Member
Dec 22, 2010
3,027
1,022
Re: [RECOVERY] TWRP 2.3.3.0 touch recovery [2012-12-19]

Using twrp 2.3.3.0 and when I do a factory reset and flash new rom it not prompting me to sign back into Google and set up phone... Is twrp fully functioning correctly on ns4g. Have it on Nexus Galaxy and love it....!

Sent from my Galaxy Nexus using xda app-developers app

Did you forget to flash Gapps?
 

dzee206

Senior Member
Oct 5, 2011
1,057
693
Seattle
everytime i download 2.4.0.0 its always 3.64mb and not 3.65 like it states on the site, also it keeps hanging at 99% on my comp no matter what browser i use or download mangers. havnt tried on mobile yet gf has the phone now.
 

matthew0776

Senior Member
Dec 22, 2012
6,030
8,736
Chicago
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Used goo manager and worked perfectly. On both nexus devices.... Thnx

Sent from my Galaxy Nexus using xda app-developers app
 

matthew0776

Senior Member
Dec 22, 2012
6,030
8,736
Chicago
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Backups not restoring on ns4g...on 2.4.0 and 2.4.1. Any body else having issues

Sent from my Galaxy Nexus using xda app-developers app
 

sleepyEDB

Senior Member
Jul 26, 2010
198
27
Metro Detroit
Most likely the restore issues on the NS4g are now fixed. Give it a shot and let me know if they're not. Either way the restore issues seemed to only deal with boot and only seemed to affect the NS and NS4G. Other devices were unaffected by those issues.
The restore problem is still present. I installed TWRP 2.4.0.1 via GooManager without issue, created a backup, wiped cache, etc. Booted into Android and back into TWRP and restored the backup. Upon rebooting the system, I am put into the bootloader and cannot boot into Android. I will try the boot.img solution posted above, and will pull & post a TWRP log if possible.


sleepy
 

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,582
KC MO
www.teamw.in
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

The restore problem is still present. I installed TWRP 2.4.0.1 via GooManager without issue, created a backup, wiped cache, etc. Booted into Android and back into TWRP and restored the backup. Upon rebooting the system, I am put into the bootloader and cannot boot into Android. I will try the boot.img solution posted above, and will pull & post a TWRP log if possible.


sleepy

If you first fix it by re flashing boot then try to get a log, then the log won't contain anything useful.
 
  • Like
Reactions: sleepyEDB

sleepyEDB

Senior Member
Jul 26, 2010
198
27
Metro Detroit
I wasn't able to get it to flash the boot.img. Windows wouldn't recognize my phone when it was connected and sitting at the bootloader screen, and the fastboot commands wouldn't work when Windows recognized my phone in TWRP. At that point I tried flashing a zip of ClockworkMOD from my SD Card, but the fastboot commands were still unrecognized. Fortunately, I was then able to flash my most recent ROM from the CyanDelta folder and I am back in Android.

If you first fix it by re flashing boot then try to get a log, then the log won't contain anything useful.
I told TWRP to copy the log file to the SD Card before I attempted to restore the boot.img, so hopefully it's useful. Sorry for not using pastebin, but it's blocked here:

[URL]http://codepad.org/Xk2dT2Q9[/URL]

Towards the bottom of the file I see these entries:

I:Backup command: 'dump_image recovery '/sdcard/TWRP/BACKUPS/<serial number removed by me>/CM10.1-N0208-02-11-2013//recovery.mtd.win''
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00380000 (Out of memory)

Maybe the nandroid backup was bad to begin with, and the restore problem wasn't with TWRP after all? I would have expected an error message if this was the case, but I don't know.


sleepy
 
Last edited:

matthew0776

Senior Member
Dec 22, 2012
6,030
8,736
Chicago
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

The screen turn weird colors when it times out on my ns4g ...but not on my gnex. Seems to be working OK I think. But can't see buttons after timeout. Anyone else having this issue.? Also looking for flash able zip for previous ver. Thanx

Sent from my Galaxy Nexus using xda app-developers app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 31
    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.
    5
    2
    Check it out teamwin 2.0 ROM manager/recovery etc....

    http://tinyurl.com/44mfcmo

    Sent from my Nexus S 4G using xda premium
    2
    TWRP2 recovery released!

    http://teamw.in/project/twrp2/74

    Sent from my Nexus S 4G using xda premium
    2
    nice recovery but seems to restore to google normal recovery after boot

    Rename /etc/install-recovery.sh to /etc/install-recovery.sh.bak .



    I checked TWRP under "BACKUPS" and found my backup but "boot.win is 0 kb. What's that about? If i restore this backup, it will most certainly fail on boot, right? A 0 kb boot.win is not correct huh?

    Mine is 8 MB. Hopefully, it would error out at the md5 check.