[RECOVERY] TWRP 2.3 / 2.2.2.1 TEAMWIN touch recovery

[koeylondon]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

Yep that's exactly what it would be used for. However as a compromise we are looking into a feature of RZRecovery that names backups based on not only the date/time, but also the name of the ROM as written in the build.prop.

Sent from my Nexus 7 using Android Central Forums

Why do I hear "Wind beneath my wings" playing suddenly...

 

[vernotzy21]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

We (sblood86 and I) won't touch TWRP code with a 10 foot pole. The only thing I would kang from TWRP is the on-screen keyboard but the code is too far-flung from CWM to even begin to port it over. Regardless, COT pwns TWRP and that's all that matters

But I gotta ask though their was talk awhile back about makeing changes to cot ui and I was thinking twrp ui is nicer....
What are your thoughts??

Sent from my SPH-M820-BST using Android Central Forums

 

[drewwalton19216801]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

But I gotta ask though their was talk awhile back about makeing changes to cot ui and I was thinking twrp ui is nicer....
What are your thoughts??

Sent from my SPH-M820-BST using Android Central Forums

Code-wise, the TWRP UI is all sorts of complicated for no reason. Also, the UI code they wrote is all sorts of different from COT's. To use it would mean a complete rewrite of just about everything, and several of our custom features would be lost in the process.

Bottom line is, we're not touching the TWRP UI any time soon. We've seen people actually switch from TWRP to COT, so that oughtta tell you something.

Sent from my Nexus 7 using Android Central Forums

 

[koeylondon]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

Personally, I find the differences fascinating. While TWRP has some advantages (no scrolling, simple UI), I find COT to be more powerful and flexible.

That said, I'd be interested in trying TWRP out for a while if I didn't keep hearing rumblings of corrupted zip files on the XDA thread. That may not apply to this build, but as a serial flasher (in the good, legal, not-creepy way), even a single corrupted Nanad would make me absolutely explode.

 

[Buddlespit]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

I haven't had any problems with twrp since I've installed it. I've made and restored backups and flashed zips. I've also read on XDA about people having issues mounting sdcards, which I've also not encountered. The only issue I had, and it wasn't a big deal to me, was restoring cot backups. I got around that by flashing cot, restored my backup (Reborn ROM, btw), flashed twrp and made a backup of it. Then restored my cm9...

 

[clodfelterac]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

been working fine for me... wipe>ext button too close to back softkey... (for big thumbs)...

 

[thekraven]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

I'll move the sd-ext button into the slot above.

It's fixed in the theme ui.zip in the OP.

 

[Badboytoast]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

Gona give this baby for a ride!! OV user!! thanks

Sent from my LG-VM670 using Tapatalk 2

 

[jonny5449]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

Thx for new update

Sent from my LG-LS670 using Tapatalk 2

 

[Deal Trees]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

Going to give this a shot.

 

[thekraven]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

TWRP 2.3.3.0 test build. 2.3 restoring backup is fixed now

Changelog for 2.3.3.0 test 5
-ADB in recovery working
-ddms screen capture working

CHANGELOG for 2.3.3.0 test3
-Fixed restore of backups https://github.com/TeamWin/Team-Win-Recovery-Project/issues/69
-keyboard highlighting when pressed.

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)

Bugs..
--2.2 themes still should work, I'll remove wipe external storage in a newer update.
--Some features are for other phones, i'll work on removing them from the options.
--2.3 Restore backup not working See the above. fixed
--older zip files won't flash due to below. So kernels, roms, and patches need some updated files. It's pain in the ****, for old roms and kernels. So just use this as a test build. CM9, Dante's Rom, and gapps flash correctly. I'll try to update my kernel zips or just post which one doesn't flash.

TWRP 2.3 NOTE about incompatible zips not flashing

NOTE about stuff that wont' flash like older kernels. 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 below. It goes in your zip file in the META-INF/com/google/android folder. This update-binary wouldn't work, but Techerrata Downloads - Downloading update-binary Try this one, works fine in flashing kernels, recoveries, system files ... Goo.im Downloads - Downloading update-binary Another one pulled from my cm9 build .. see below And make sure your mount points look like this when flashing files or kernels.

run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system"); #or whatever you want to put here    
run_program("/sbin/busybox", "umount", "/system");

Or this way pulled from a cm9 rom zip Goo.im Downloads - Downloading update-binary

mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system"); #or whatever you want to put here  
unmount("/system");

DOWNLOAD TWRP 2.3.3.0

test 6 http://goo.im/devs/thekraven/LS670/TWRP-LS670 flashable zip with themes Or extract recovery.img from the zip and flash using Recovery Flasher http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/197483-app-recovery-flasher-utility.html

 

[jonny5449]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

Testing now

Sent from my LG-LS670 using Tapatalk 2

 

[Buddlespit]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

I've read where this recovery is having issues flashing roms. I'll try flashing a rom tonight, after replacing the update-binary in it.

edit: I've downloaded danterom, replaced update-binary. No-go on install. Edited updater-script to match what you posted in code, but it still did nothing. I didn't think it would work, considering that busybox doesn't install on danterom until almost the end, so no sbin/busybox to mount system or data. So I tried mounting system and data before flashing, still a no-go.

So, for s&g's , I've redownloaded danterom and flashed as is. That appeared to work, so I flashed the radio patch (I'm on zvd, of course). That also appeared to flash properly. I had to go back into recovery and reflash the zvj to zvd patch, but it work.

All in all, I guess it was a success. I didn't have to change anything out to make it work.

 

[Buddlespit]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

Crap.... I didn't realize that editing my post wouldn't bump this thread to the top...

 

[Buddlespit]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

OK, it won't restore any of the old backups. I'm trying to get danterom backup to load, so I can adb back to the older 2.2.2.1 version, but that looks borked too.

Crap....

OK, I'll re-install dante, then adb flash_image back to 2.2.2.1....

Wish me luck

edit: It took me about a half hour to figure out that the permissions were set wrong in /system/bin/flash_image in dante. I fixed that and was able to flash the recovery.img from test3.

BUGS: ADB in recovery doesn't work, nor does restoring a backup. Backup appears to work fine.

 

[A-android-B]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

Love this definitely a step in the right direction as far as recoveries go. Just flashed on my zv5 OV. Is there a way to change your your /system and /data to ext 4?


Sent from my LG-VM670 using Android Central Forums

 

[A-android-B]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

The more I use this recovery the more I like it! Thanks a ton and great job! Renaming backups is freaking awesome!

Sent from my LG-VM670 using Android Central Forums

 

[A-android-B]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

PS works fine for bobz cm9.1 and amphetamines and CAI gapps on my zv5 optimus v

Sent from my LG-VM670 using Android Central Forums

 

[Badboytoast]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

:thumbup: this is a really cool recovery! OV user here! Really amazing recovery! Looks great and I really like the FULL touch recovery V-2.2.2.1 keep up the good work

Sent from my LG-VM670 using Tapatalk 2

 

[A-android-B]

Re: [RECOVERY] TWRP 2.2.2.1 touch recovery

I know right it is the only recovery with real touch interface.
@theKraven, Would you consider making a thread in the v forums for this?

Sent from my LG-VM670 using Android Central Forums