[BETA][RECOVERY][TF101] TWRP 2.6.0.0 with on-screen keyboard! [SUPERCEEDED]

Search This thread

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
Does Aroma work with TWRP 2.3.2.3 ?

I tried to flash it but it froze TWRP and didn't flash

I've asked around. Seemingly all that's required for AROMA to work, it needs to have a kernel with a "touch screen driver". So this is most likely a kernel-issue, and not an issue with TWRP itself.

As TWRP itself depends on touch input, it would be logical to assume that it has some sort of touch screen driver already, but if it's the right one, and how things needs to be setup, I have no idea.

Anyone willing/able to provide some feedback on this? Any kernel options I should look into adding/stripping/changing?
 
  • Like
Reactions: jrohwer

wn1ytw

Senior Member
Nov 25, 2012
219
41
Worcester
Flashed the zip.
Rebooted to ROM EOS4 117 kk 103.
reboot to recovery and indeed I have 2.5.0.0
reboot to ROM - it boots but in notification I get triangle with 'overclocking not applied'

I went to EOS Control Center and indeed my overclock on boot to 1400 was all set back to 1000
I reset it and reboot, NG

cannot overclock until I restore my backup before installing TWRP 2.5.0.0
so I'm back to 2.3.2.3 and overclocked 1400 with nightly 117 & kk103
 

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
Flashed the zip.
Rebooted to ROM EOS4 117 kk 103.
reboot to recovery and indeed I have 2.5.0.0
reboot to ROM - it boots but in notification I get triangle with 'overclocking not applied'

I went to EOS Control Center and indeed my overclock on boot to 1400 was all set back to 1000
I reset it and reboot, NG

cannot overclock until I restore my backup before installing TWRP 2.5.0.0
so I'm back to 2.3.2.3 and overclocked 1400 with nightly 117 & kk103

Sounds strange. Technically speaking ROM and recovery should be 100% separate and unable to affect each other in that way.

Out of curiosity... did you ever try reflashing the ROM and kernel from the updated recovery?

Sent from my Galaxy Nexus using Tapatalk 4 Beta
 

wn1ytw

Senior Member
Nov 25, 2012
219
41
Worcester
Sounds strange. Technically speaking ROM and recovery should be 100% separate and unable to affect each other in that way.

Out of curiosity... did you ever try reflashing the ROM and kernel from the updated recovery?

Sent from my Galaxy Nexus using Tapatalk 4 Beta

I tried several times and each time I went to recovery I had to do a double reboot as I got this 'error'. I then tried to flash my ROM Gapps & kernal, and each time I did it wiped my apps. I tried the advanced and the 'most times tis is the only wipe you'll need.' wipes. When in the advanced I tried to NOT do a factory reset, but both times that seems to what I got. The screens/choices are not the same so probable confused me but I tried for an hour, my battery needs recharging after so many restores/flashes/reboots.

I appreciate the work but this version is not ready for general use by dummies like me!
 

Attachments

  • Screenshot_2013-06-07-05-38-00.jpg
    Screenshot_2013-06-07-05-38-00.jpg
    17.9 KB · Views: 241

i9apps

Senior Member
Sep 1, 2011
458
83
Flashed the zip.
Rebooted to ROM EOS4 117 kk 103.
reboot to recovery and indeed I have 2.5.0.0
reboot to ROM - it boots but in notification I get triangle with 'overclocking not applied'

I went to EOS Control Center and indeed my overclock on boot to 1400 was all set back to 1000
I reset it and reboot, NG

cannot overclock until I restore my backup before installing TWRP 2.5.0.0
so I'm back to 2.3.2.3 and overclocked 1400 with nightly 117 & kk103

Try to OC with CPU Master..working great here
 

josteink

Senior Member
Feb 8, 2011
2,243
1,808
Oslo
I tried several times and each time I went to recovery I had to do a double reboot as I got this 'error'. I then tried to flash my ROM Gapps & kernal, and each time I did it wiped my apps. I tried the advanced and the 'most times tis is the only wipe you'll need.' wipes. When in the advanced I tried to NOT do a factory reset, but both times that seems to what I got. The screens/choices are not the same so probable confused me but I tried for an hour, my battery needs recharging after so many restores/flashes/reboots.

I appreciate the work but this version is not ready for general use by dummies like me!

I know it's always easier to blame someone else, but I'm not experiencing this issue with my own CM10.1 builds.

That said, Tim usually knows pretty well what's going on and where. I can ask him for some feedback on this :)
 

wn1ytw

Senior Member
Nov 25, 2012
219
41
Worcester
I know it's always easier to blame someone else, but I'm not experiencing this issue with my own CM10.1 builds.

That said, Tim usually knows pretty well what's going on and where. I can ask him for some feedback on this :)
Just reporting my results, I have no issues with 2.3.2.3 and am happy-just trying to be helpful. Thanks for the work. :cyclops:
 

timduru

Senior Member
Apr 13, 2011
2,878
18,021
Flashed the zip.
Rebooted to ROM EOS4 117 kk 103.
reboot to recovery and indeed I have 2.5.0.0
reboot to ROM - it boots but in notification I get triangle with 'overclocking not applied'

I went to EOS Control Center and indeed my overclock on boot to 1400 was all set back to 1000
I reset it and reboot, NG

cannot overclock until I restore my backup before installing TWRP 2.5.0.0
so I'm back to 2.3.2.3 and overclocked 1400 with nightly 117 & kk103

Shouldn't be linked to the recovery.

The criteria for not applying the overclock is based onto the time between the reboots. (4 mins minimum)
So if you reboot/flash too close from each other, it'll not apply the overclocking.
Wait a few minutes (It's using thtt for the test which checks that the last reboot was done more than 240 seconds ago), and reboot and it'll be applied again.
It's there to make sure you don't brick your tablet in case you overclock to a value too high and that it constantly crashes.
If it crashes right after one other crash, the overclock is reset that way and you can boot.
 
Last edited:

wn1ytw

Senior Member
Nov 25, 2012
219
41
Worcester
Shouldn't be linked to the recovery.

The criteria for not applying the overclock is based onto the time between the reboots. (4 mins minimum)
So if you reboot/flash too close from each other, it'll not apply the overclocking.
Wait a few minutes (It's using thtt for the test which checks that the last reboot was done more than 240 seconds ago), and reboot and it'll be applied again.
It's there to make sure you don't brick your tablet in case you overclock to a value too high and that it constantly crashes.
If it crashes right after one other crash, the overclock is reset that way and you can boot.

Thanks for the explanation and hint. I've now waited 5 minutes between each reboot and now recovery is 2.5.0.0 and overclocking works in EOS CC as usual. Thank you!
 

csb5731

Senior Member
Jan 6, 2012
156
33
I then tried to flash my ROM Gapps & kernal, and each time I did it wiped my apps. I tried the advanced and the 'most times tis is the only wipe you'll need.' wipes. When in the advanced I tried to NOT do a factory reset, but both times that seems to what I got. The screens/choices are not the same so probable confused me but I tried for an hour, my battery needs recharging after so many restores/flashes/reboots.

Could not replicate:
Started at EOS117/KK103lidpatch/whatever gapps
Wipe/Advanced: checked Dalvik, System, Cache (Not Data)
Flashed 116/same KK/same gapps
Clicked wipe Cache/Dalvik button (probably not necessary)
Rebooted
Data/Apps still there

Did the same thing back to EOS 117, worked fine, no data-loss. I think somewhere, you must have wiped data along the way.

I'll agree that the default wipe option isn't absolutely ideal for MY usage model - I am generally just applying latest EOS version over an older version without data-wiping and no issues, but it probably is for a lot/most of the flashers. The advanced wipe feature is great (though someday I am sure I will inadvertently check SDC, just because I am like that) and a little bit of a time-saver.
 
  • Like
Reactions: josteink and wn1ytw

Alas2708

Member
Oct 5, 2010
28
3
Strange behaviour here :
wipe cache, dalvik and system
flash EOS latest nightly
flash gapps
flash kat kernel 103
wipe cache, dalvik again
boot
try to install the fixes using the kat app (mediascanner, gps and adblock) and all 3 fail...

doing the same with old recovery works fine

maybe the kernel doesn't get fully installed?

Sent from my Galaxy Nexus using Tapatalk 2
 
Last edited:

st0nedpenguin

Senior Member
Jun 13, 2011
419
110
Sometimes the fixes only partially install here too, I just try a couple times and they eventually stick.
 

bfmetcalf

Senior Member
Strange behaviour here :
wipe cache, dalvik and system
flash EOS latest nightly
flash gapps
flash kat kernel 103
wipe cache, dalvik again
boot
try to install the fixes using the kat app (mediascanner, gps and adblock) and all 3 fail...

doing the same with old recovery works fine

maybe the kernel doesn't get fully installed?

Sent from my Galaxy Nexus using Tapatalk 2

I actually had kat app not work as well, wiped delvik/cache and flashed ROM and gapps again and it worked fine, thought maybe it was just the ROM, but may be recovery?
 

jacobsensei

Senior Member
Mar 1, 2011
462
61
East Coast
Guess there's no consensus to move this out of beta yet.

If there is a real problem, will Goo manager flash the current twrp2.3.2.3 version over this?
Is there a 2.3.2.3 zip?

Has anyone gone back?

Can't say I've had any problems with 2.3.2.3.

Just a little cautious when it comes to recoveries and bootloaders.

Running Josteink's 10.1 daylies, works great, just wanted to say thanks again for all you work on the TF101 and this recovery.

Sent from my Transformer
 

the.teejster

Senior Member
Aug 14, 2008
373
96
FYI,
I just used GOO manager to flash back to 2.3.2.3 from the 2.5.0.0 beta.

All seems fine.
I used 2.3.2.3 to flash josteinks 6/12 nightly build w/o issue.

Guess there's no consensus to move this out of beta yet.

If there is a real problem, will Goo manager flash the current twrp2.3.2.3 version over this?
Is there a 2.3.2.3 zip?

Has anyone gone back?

Can't say I've had any problems with 2.3.2.3.

Just a little cautious when it comes to recoveries and bootloaders.

Running Josteink's 10.1 daylies, works great, just wanted to say thanks again for all you work on the TF101 and this recovery.

Sent from my Transformer
 
  • Like
Reactions: josteink

Top Liked Posts

  • There are no posts matching your filters.
  • 45
    Sorry to keep you waiting. As promised: Here's my custom build of TWRP 2.6.0.0 for the TF101.

    I repeat: This is a custom build. This is not an official release from Team Win.

    This thread has been superceeded by another thread by sidneyk.

    For that thead, go here!




    Team Win Recovery Project 2.5, 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:
    1.png
    2.png


    Tablet look:
    3.png

    4.png


    DOWNLOAD:
    An unofficial BETA 2.5.0.0 can be downloaded here:
    http://nexfiles.kjonigsen.net/tf101/twrp/

    Files available:
    - blob file for flashing via terminal
    - SOS partition file for flashing with wheelie+nvflash
    - ZIP for flashing with existing recovery

    Until this build gets approved by Team Win and made official, you can NOT get or install this via Goomanager. Sorry.

    Until then, you can install using a terminal as outlined for the official 2.3.2.3 release.

    KNOWN ISSUES:
    No aroma support?

    BUGS:
    This build is based on VidivBoarder's code for TWRP 2.3.2.3. If you encounter any bugs which you did not have in that version in this beta, do let me know.

    Also: If you have found a bug, please acquire a recovery.log - you can do this in two ways - the fastest is "adb pull /tmp/recovery.log" right after you have the issue. Alternatively in the advanced menu there's an option to copy the log to the sdcard. Also 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 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:
    This release is not yet officially supported by Team Win, but if you still want to chat with them on IRC, you can visit #twrp on Freenode with your IRC client or just click this link.

    THANKS TO:
    A few thanks for this specific build:

    • VividBoarder for preparing the base with the TWRP 2.3.2.3 release. And saving me the work of working out all the TF101 kinks myself. (although I was halfway there by the time I saw that repo had incorrectly checked out the regular CM9 branch and not the TWRP branch)
    • Roach2010 and RaymanFX for the work already invested in TWRP 2.3.2.3
    • And... Dees_Troy for nagging me into completing this :)
    13
    I guess you can tell from my sig now: Finally got the Nexus 7.

    I'll be leaving and wont be maintaining this TWRP anymore.That said: if anybody wants to give it a try, feel free to PM and I can attempt to assist as much as I can.

    Thanks for the good run. Cheers!
    9
    What's new in 2.6.0.0:

    Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.

    • [FONT=Lucida Sans Unicode, arial]Can encrypt a backup to prevent theft of private data from your backup files
      [/FONT]
    • [FONT=Lucida Sans Unicode, arial]Updated graphics / icon courtesy of shift
      [/FONT]
    • [FONT=Lucida Sans Unicode, arial]Updated exFAT to latest commits
      [/FONT]
    • [FONT=Lucida Sans Unicode, arial]Fixed a problem with Samsung TouchWiz decryption
      [/FONT]
    • [FONT=Lucida Sans Unicode, arial]Update SuperSU binary
      [/FONT]
    • [FONT=Lucida Sans Unicode, arial]Fixed saving of backup partitions list
      [/FONT]
    • [FONT=Lucida Sans Unicode, arial]Fixed saving of last used zip install folder
      [/FONT]
    • [FONT=Lucida Sans Unicode, arial]Fixed backup of datadata on devices that use a separate partition for datadata
      [/FONT]
    • [FONT=Lucida Sans Unicode, arial]Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
      [/FONT]
    • [FONT=Lucida Sans Unicode, arial]Fixed some problems with partitioning a SD card
      [/FONT]
    • [FONT=Lucida Sans Unicode, arial]Various other bug fixes and tweaks
      [/FONT]
    [FONT=Lucida Sans Unicode, arial]
    Notes about encrypted backups:
    Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.

    Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.[/FONT]

    What's new in 2.5.0.0:

    Special Note: If you are running a custom theme, the changes in 2.5.0.0 will likely not be compatible with your theme.

    • [FONT=Lucida Sans Unicode, arial]Added scrollable partition lists for mount, backup, restore, wipe, and storage selection[/FONT]
    • [FONT=Lucida Sans Unicode, arial]Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)[/FONT]
    • [FONT=Lucida Sans Unicode, arial]Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache[/FONT]
    • Added official theme for 1080x1920 portrait devices (HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
    • [FONT=Lucida Sans Unicode, arial]Fixed a problem with directory permissions on split archive backups[/FONT]
    • [FONT=Lucida Sans Unicode, arial]Fixed a problem with md5 verification of backups[/FONT]
    • [FONT=Lucida Sans Unicode, arial]Added a search function to libtar (thanks to kokotas)[/FONT]
    • [FONT=Lucida Sans Unicode, arial]Improve handling of XML errors (fix permissions)[/FONT]
    • [FONT=Lucida Sans Unicode, arial]Fixed handling of subpartitions[/FONT]
    • [FONT=Lucida Sans Unicode, arial]Improvements to recovery.fstab flags[/FONT]
    • [FONT=Lucida Sans Unicode, arial]Fixed a problem with decryption not being able to locate the decryption key in some situations[/FONT]
    What's new in 2.4.4.0:


    • Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
    • More fixes for the file selector
    • Switched from using busybox md5sum to a direct C function call
    • Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
    • Update exFAT to latest commits
    • Added a build flag to disable using the ioctl for screen blanking
    What's new in 2.4.3.0:


    • Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
      NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
    • Added a scroll bar to file selectors and listboxes courtesy of Tassadar
    • Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
    • Added a screen dim effect 2 seconds before screen off on some devices
    • Finally fixed file selector crash (one of the joys of working with multi-threaded software)
    • Fixed loading of screen timeout setting during startup
    • Improvements and bugfixes to screen timeout code
    • Fixed persistence of the 24 hour / military time setting
    What's new in 2.4.2.0:


    • Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
    • Add a brightness setting (requires device specific setup and only some devices have been added)
    • Add a root checker and offer to install SuperSU if the device isn't already rooted
    • Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
    • Check and offer to fix root permissions if broken
    • Add an option for a 24 hour clock display instead of AM/PM (aka military time)
    • Move stock recovery reflash check to occur during the reboot cycle
    • Add support for some MTK6xxx devices
    • Change libtar to vfork to help prevent memory problems
    • Add a "clicked" effect to most buttons, file selector, and listbox
    • Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
    • Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
    • Other minor bugfixes and improvements
    What's new in 2.4.1.0:


    • Fixed a problem with mkdosfs that formatted sdcards to 2GB
    • Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
    • Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
    • Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
    What's new in 2.4.0.0:


    • Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
    • Support for exFAT formatted sdcards (also thanks to bigbiff)
    • Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
    • Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
    • Added wipe cache and dalvik after ADB Sideload
    • Replaced many system calls with their native C counterparts
    • Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
    • Fixed AOSP recovery commands to run after decryption on encrypted devices
    • Improvements for building TWRP in CM10.1
    • Other minor bugfixes and improvements
    9
    Flashed the zip.
    Rebooted to ROM EOS4 117 kk 103.
    reboot to recovery and indeed I have 2.5.0.0
    reboot to ROM - it boots but in notification I get triangle with 'overclocking not applied'

    I went to EOS Control Center and indeed my overclock on boot to 1400 was all set back to 1000
    I reset it and reboot, NG

    cannot overclock until I restore my backup before installing TWRP 2.5.0.0
    so I'm back to 2.3.2.3 and overclocked 1400 with nightly 117 & kk103

    Shouldn't be linked to the recovery.

    The criteria for not applying the overclock is based onto the time between the reboots. (4 mins minimum)
    So if you reboot/flash too close from each other, it'll not apply the overclocking.
    Wait a few minutes (It's using thtt for the test which checks that the last reboot was done more than 240 seconds ago), and reboot and it'll be applied again.
    It's there to make sure you don't brick your tablet in case you overclock to a value too high and that it constantly crashes.
    If it crashes right after one other crash, the overclock is reset that way and you can boot.
    8
    Is anyone still visiting or working in the 2.3.2.3 build thread?

    Original creator of that build and thread no longer has a TF101, so he's a goner.

    This is the "new thread" I guess. I'll consider adding a 2.6.0.0 build when I get back from my vacation.