[RECOVERY] [Touchpad] TWRP 2.3.2.3 with on-screen keyboard! [2012-12-17]

Search This thread

ViViDboarder

Inactive Recognized Developer
Mar 25, 2010
1,584
630
San Francisco, CA
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.2.3:
-Fix to libraries to avoid issues when formatting partitions

CHANGELOG for 2.3.2.1:
-Updates to fix permissions
-Fix USB OTG on GNex

CHANGELOG for 2.3.2.0:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses

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!
Direct Download

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.
 
Last edited:

bobtidey

Senior Member
Jul 5, 2011
257
107
I have switched to using TWRP for recovery on both Touchpad and Nook as it is very nice to use without having to fiddle with the buttons.

To make it even easier on Touchpad I thought I'd make the boot to recovery from CM7 go into TWRP rather than have to catch the moboot menu.

So in /boot I did mv uImage.ClockworkMod uImage.ClockworkMod1 and mv uImage.TWRP uImage.ClockworkMod

This superficially worked in that the boot to recovery from CM7 went into TWRP very nicely. But unfortunately when I then select Reboot to System from TWRP it then reboots straight back into ClockworkMod and restarts TWRP rather than go through moboot and into CYanogenMod

I guess there must be something going on in the real ClockworkMod to flip the default boot back which TWRP isn't doing.

For the moment I changed the names back so it uses Clockwork for the default and behaves normally.
 

ViViDboarder

Inactive Recognized Developer
Mar 25, 2010
1,584
630
San Francisco, CA
I have switched to using TWRP for recovery on both Touchpad and Nook as it is very nice to use without having to fiddle with the buttons.

To make it even easier on Touchpad I thought I'd make the boot to recovery from CM7 go into TWRP rather than have to catch the moboot menu.

So in /boot I did mv uImage.ClockworkMod uImage.ClockworkMod1 and mv uImage.TWRP uImage.ClockworkMod

This superficially worked in that the boot to recovery from CM7 went into TWRP very nicely. But unfortunately when I then select Reboot to System from TWRP it then reboots straight back into ClockworkMod and restarts TWRP rather than go through moboot and into CYanogenMod

I guess there must be something going on in the real ClockworkMod to flip the default boot back which TWRP isn't doing.

For the moment I changed the names back so it uses Clockwork for the default and behaves normally.

The bootloader project is here: http://code.google.com/p/moboot/

If you're feeling inclined you can ask how you set the default boot for recovery and whatnot. That would probably be a good start. Maybe someone on my team knows, but it can't hurt to learn anyway. :)
 

bobtidey

Senior Member
Jul 5, 2011
257
107
Thanks for that pointer. There does seem to be some anomaly around the use of moboot.next and moboot.action.d

I think when rebooting from CM7 into recovery then either moboot.next or moboot.action.d is being set up to action ClockworkMod so it goes straight in without the moboot menu. Real ClockworkMod then deletes the action files so that when it does a reboot moboot goes through its menu, times out and re-enters the default CM7.

When TWRP is renamed then the sequence starts the same but there is then a moboot.next file that points to ClockworkMod and when it tries to do a system boot then moboot kicks in and repeats the action back into recovery.

I'll comment back on the moboot project as I suspect the cleanest actions here are for moboot to do the housekeeping of action and next files so it doesn't get stuck in this loop.
 
  • Like
Reactions: bkmo

Crsdr37

Senior Member
Aug 3, 2010
1,866
335
Concord
anyone flash roms with this yet. In the eco people are stating wipin isn't working and hey flash and get stuck in a boot loop

Sent from my PC36100 using xda premium
 

bluedogtouchpad

Senior Member
Nov 29, 2011
81
9
New Castle, DE.
I installed the newest XRON rom along with moboot and TWRP on my Touchpad and TWRP did not seem to install. Is there a way to just install TWRP without having to do the whole thing over again? Maybe threw terminal mode or something. Since I tried to install TWRP I did not install CWM.
 

jcsullins

Senior Member
Jul 20, 2010
237
1,878
Thanks for that pointer. There does seem to be some anomaly around the use of moboot.next and moboot.action.d

I think when rebooting from CM7 into recovery then either moboot.next or moboot.action.d is being set up to action ClockworkMod so it goes straight in without the moboot menu. Real ClockworkMod then deletes the action files so that when it does a reboot moboot goes through its menu, times out and re-enters the default CM7.

When TWRP is renamed then the sequence starts the same but there is then a moboot.next file that points to ClockworkMod and when it tries to do a system boot then moboot kicks in and repeats the action back into recovery.

I'll comment back on the moboot project as I suspect the cleanest actions here are for moboot to do the housekeeping of action and next files so it doesn't get stuck in this loop.

All versions of moboot have a README in the moboot_X.X.X.zip file.

From the README (this part was the same in all versions, I think):
##
## to select *next* boot image
##
echo "NAME1" >/boot/moboot.next # will boot uImage.NAME1 without menu
# NOTE: moboot does not delete the file, so the OS booted should

You are correct, it would be cleanest if moboot removed/managed this.
However, there is no code in moboot (or specifically, the ext2 fs code
it uses) to write to the filesystem. After I am done adding lvm support
to moboot, I plan on adding support to moboot to save some state information
to a raw partition (raw lvm volume). Once that is done, I should be able
to lift the requirement that the OS (or recovery, etc.) remove the
moboot.next file.

Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).

Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.
 
  • Like
Reactions: bobtidey

LastQuark

Senior Member
Feb 16, 2011
236
73
I installed the newest XRON rom along with moboot and TWRP on my Touchpad and TWRP did not seem to install. Is there a way to just install TWRP without having to do the whole thing over again? Maybe threw terminal mode or something. Since I tried to install TWRP I did not install CWM.

I had the same problem. I installed CWM first, then install TWRP through CWM.
 

Prey521

Senior Member
Aug 28, 2007
857
209
New Caney, TX
Installed successfully after running the clean boot zip.

I went to the backup section to try and perform a backup but it gives me options that i can select/unselect and am not sure what should and shouldn't be selected.

Thanks
 

bobtidey

Senior Member
Jul 5, 2011
257
107
All versions of moboot have a README in the moboot_X.X.X.zip file.

...

Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).

Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.

Thanks. I should have checked the readme.

I discovered the home key trick the first time I tried this and was beginning to wonder how to get out of the loop.

Good to hear TWRP will remove it as well as I'm keen to use this as the standard and be able to reboot into recovery from CM7.

Extra refinement would be if CM7 reboot menu listed all the boot options it could find so that it wouldn't be necessary to rename the image to match the Clockwork that will be used when recovery is chosen.
 

dallas.maverick

Senior Member
Jul 4, 2009
175
86
Wylie, TX
All versions of moboot have a README in the moboot_X.X.X.zip file.

From the README (this part was the same in all versions, I think):
##
## to select *next* boot image
##
echo "NAME1" >/boot/moboot.next # will boot uImage.NAME1 without menu
# NOTE: moboot does not delete the file, so the OS booted should

You are correct, it would be cleanest if moboot removed/managed this.
However, there is no code in moboot (or specifically, the ext2 fs code
it uses) to write to the filesystem. After I am done adding lvm support
to moboot, I plan on adding support to moboot to save some state information
to a raw partition (raw lvm volume). Once that is done, I should be able
to lift the requirement that the OS (or recovery, etc.) remove the
moboot.next file.

Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).

Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.

Thanks, I tested this extensively in an attempt to get my Touchpad into TWRP by default and ran into the same issue with moboot.next, I tried to make it read only after putting Cyanogemnod into it among other things but couldn't get it to work 100%. For now, seems like other folks are running into the same issues and sounds like you guys will take care of it in the next release of moboot. Thanks for all the work.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 35
    Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.2.3:
    -Fix to libraries to avoid issues when formatting partitions

    CHANGELOG for 2.3.2.1:
    -Updates to fix permissions
    -Fix USB OTG on GNex

    CHANGELOG for 2.3.2.0:
    -Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
    -Fixed a bug with deleting a backup with a space in the name
    -Added highlights on keyboard key presses

    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!
    Direct Download

    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.
    5
    Time for the 2.2.0 update!
    4
    video tutorial

    Here's a video on installing and using TWRP 2.2.0
    http://www.youtube.com/watch?v=RIvWVS_Rkxo
    4
    Could someone upload the zip for 2.2.0? I can't use Goo Manager, and the zip on the main website still 2.1.0.

    I made the below by putting the new 2.2.0 image into the unpacked old 2.1.0 zip from the web site, then zipping and signing it. So, the below should work, but I haven't tried it as I've been waiting for the fixes from TeamWin that hopefully come this week? Be aware that this method brings up TWRP under the CWM pick in moboot, so you might have 2 recovery images in /boot. You are using at your own risk.

    https://dl.dropbox.com/u/8228367/twrp_2.2.0_s.zip
    3
    Bummmmp dat for 2.1!