Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,770,363 Members 46,876 Now Online
XDA Developers Android and Mobile Development Forum

[RECOVERY][Fascinate]TWRP 2.3.1.1 touch recovery [2012-10-16]

Tip us?
 
Dees_Troy
Old
(Last edited by Dees_Troy; 20th December 2012 at 08:33 PM.)
#1  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 9155
Posts: 1,592
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
Default [RECOVERY][Fascinate]TWRP 2.3.1.1 touch recovery [2012-10-16]

Team Win Recovery Project 2.3, or twrp2 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.

Phone look:


Tablet look:


CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present

CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)

While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.

Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.

DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!

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 30 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.
The Following 15 Users Say Thank You to Dees_Troy For This Useful Post: [ Click to Expand ]
 
shelby04861
Old
(Last edited by shelby04861; 14th May 2012 at 09:02 PM.)
#2  
shelby04861's Avatar
Senior Member
Thanks Meter 82
Posts: 475
Join Date: Aug 2011
Two thumbs
Flashes fine and boots into recovery and can flash files as well. On aokp 35.1 for the record.
Sent from my SCH-I500 using Tapatalk
 
sageDieu
Old
#3  
sageDieu's Avatar
Senior Member
Thanks Meter 419
Posts: 2,114
Join Date: Oct 2010
Location: Weaverville, NC
I will warn you all to use care with this, it does not play well with other recoveries and roms, and sometimes even with Odin. I used it a lot trying to test things for steve and we decided to put it on the back burner, it is cool but causes trouble sometimes. Basically, it's awesome to use and has lots of handy features (zip queue ftw) but try not to flash anything with it if you aren't near a computer that you can Odin with just in case.

Sent from my SCH-I500 using Tapatalk 2


Samsung Galaxy S4

Google Nexus 7 2013
The Following 3 Users Say Thank You to sageDieu For This Useful Post: [ Click to Expand ]
 
shelby04861
Old
(Last edited by shelby04861; 15th May 2012 at 12:06 AM.)
#4  
shelby04861's Avatar
Senior Member
Thanks Meter 82
Posts: 475
Join Date: Aug 2011
Thanks for the heads up. I did go ahead and flash to play around with it. You are right. There are a bug or two in there. Is there a easy way to get the reg cwm back on like Odin or flashing, or do I need to Odin back to stock first. Its no biggy, just didn't want to waste time when I get home tonight. It is very responsive and easy to navigate though and looks very promising
edit:so odin back to stock and then restore is the way to go. I still like it a lot either way.
Sent from my SCH-I500 using Tapatalk
 
tonu42
Old
#5  
Senior Member
Thanks Meter 312
Posts: 1,004
Join Date: Nov 2010
Quote:
Originally Posted by shelby04861 View Post
Thanks for the heads up. I did go ahead and flash to play around with it. You are right. There are a bug or two in there. Is there a easy way to get the reg cwm back on like Odin or flashing, or do I need to Odin back to stock first. Its no biggy, just didn't want to waste time when I get home tonight. It is very responsive and easy to navigate though and looks very promising
edit:so odin back to stock and then restore is the way to go. I still like it a lot either way.
Sent from my SCH-I500 using Tapatalk
Reflashing AOKP glitched version should work? Unless TWRP messes with the way it handles scripting.
 
sageDieu
Old
#6  
sageDieu's Avatar
Senior Member
Thanks Meter 419
Posts: 2,114
Join Date: Oct 2010
Location: Weaverville, NC
Quote:
Originally Posted by tonu42 View Post
Reflashing AOKP glitched version should work? Unless TWRP messes with the way it handles scripting.
yeah it changes some boot stuff and tries to reinject itself when you flash kernels. Which is handy if you want it but if you don't it causes problems. I was able to flash a glitch kernel from twrp but then it would just keep rebooting to glitch (cwm) recovery as though I had done three finger reboot. I flashed cm7 which put me back on blue older cwm5 and after flashing it again the phone booted so then I flashed back to ics.

Sent from my SCH-I500 using Tapatalk 2


Samsung Galaxy S4

Google Nexus 7 2013
 
shelby04861
Old
#7  
shelby04861's Avatar
Senior Member
Thanks Meter 82
Posts: 475
Join Date: Aug 2011
It is really a 50/50 as to which way to go, a bunch of flashing or a bunch of Odin and then restore. Time difference is not to much. Were you able to do any backups and restores with it. I didn't have time to try that out yet. I also didn't have time to check to see if the problems made the bug report or not

Sent from my SCH-I500 using Tapatalk
 
Stephen.k.spear
Old
#8  
Senior Member
Thanks Meter 3907
Posts: 1,616
Join Date: Jul 2011
Location: West Palm Beach

 
DONATE TO ME
Things I would like tested before I include it in AOKP.

1) data wipe. You can flash the ROM again boot and if all is well go back and restore.

2) flash the ROM or Efpophis kernel and tell me what recovery you have. It should be blue or red not twrp.

If those are good I'll look into including it.

Sent from my Glitched AOKP Unicorn.
Like my work? Buy me a beer. Twitter: @stevespeartweet
The Following 2 Users Say Thank You to Stephen.k.spear For This Useful Post: [ Click to Expand ]
 
shelby04861
Old
#9  
shelby04861's Avatar
Senior Member
Thanks Meter 82
Posts: 475
Join Date: Aug 2011
Stephen, I have not tried those due to time. I can tell you I tried flashing the cwm fixed for cm7 twice and I still remained on twrp. I tried once with the injection button checked and once with it unchecked. Same result but no boot loop issues at all from that or any other flashing. This recovery is a tricky one for sure. When I get more time I will try some of your requests. I have limited time at my home computer lately because of work and studying for a test for work.

Sent from my SCH-I500 using Tapatalk
 
Dees_Troy
Old
#10  
Dees_Troy's Avatar
Senior Recognized Developer - OP
Thanks Meter 9155
Posts: 1,592
Join Date: Mar 2008
Location: KC MO

 
DONATE TO ME
Quote:
Originally Posted by shelby04861 View Post
Stephen, I have not tried those due to time. I can tell you I tried flashing the cwm fixed for cm7 twice and I still remained on twrp. I tried once with the injection button checked and once with it unchecked. Same result but no boot loop issues at all from that or any other flashing. This recovery is a tricky one for sure. When I get more time I will try some of your requests. I have limited time at my home computer lately because of work and studying for a test for work.

Sent from my SCH-I500 using Tapatalk
How did you flash the CWM CM7? If you (or the zip) used flash_image, then you might need to use erase_image first. flash_image checks the first 2KB of the image against what's already in boot. If it matches then it refuses to flash. The 2KB approach works fine for "normal" Android kernels because the first 2KB contains a "unique signature" but it doesn't always work well for Samsung SGS1 kernels because they are packed differently. I've found that I sometimes had to use erase_image in order to get flash_image to work. I've thought about submitting a patch to CM to fix this issue but haven't gotten around to it yet.

TWRP has been tested on the Epic 4G here:
http://forum.xda-developers.com/show....php?t=1622947

And there's a zip here that should re-inject CWM. It would need to be modified slightly to work with the Fascinate, but someone could use this as a base if they wanted:
http://forum.xda-developers.com/show....php?t=1651012

I think most of the issues that you'll experience will be due to the "injection process". If your kernel or ROM developer already includes TWRP in their builds then you don't need to try to reinject TWRP every time and we do make it optional. The recovery itself should be pretty solid because we use the same code across all devices (except for the optional injection code) so there's nothing that's specific to the SGS1 devices. Also, for the record, because sk8 loaned me his Fascinate, I was able to add /datadata support to TWRP, so that issue gone now too.

If you do run into any issues, please let me know. It's best to PM me, submit a bug report on github, or catch me in #twrp on Freenode. With over 20 devices to support I can't frequent the threads on the forums or I won't get any coding done.

The Following 6 Users Say Thank You to Dees_Troy For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes