[RECOVERY][ENCORE] TWRP 2.3.1.0 with on-screen keyboard! [2012-10-15]
- Thread starter eyeballer
- Start date
That was the whole reason Eyeballer made the update!
Homer
Sent from my SM-P600 using xda app-developers app
I have somehow corrupted my recovery after using the built in CM11 updater with latest CWM recovery.
I would like to switch back to TWRP anyways. Is there a method to flash the 2.6.3 from here http://techerrata.com/browse/eyeballer/twrp without an SDcard?
Can I somehow write this to recovery from within CM11 or via ADB or fastboot?
Or, can I reinstall the old recovery with goo manager, then install this TWRP recover from within the old recovery?
I would like to switch back to TWRP anyways. Is there a method to flash the 2.6.3 from here http://techerrata.com/browse/eyeballer/twrp without an SDcard?
Can I somehow write this to recovery from within CM11 or via ADB or fastboot?
Or, can I reinstall the old recovery with goo manager, then install this TWRP recover from within the old recovery?
I tried the updated CWM and decided I didn't like it. I downloaded the TWRP zip and installed it with CWM.
Last edited:
Hi, yes, my problem is that my current CWM is corrupted. I had also already updated to latest CWM.
Mount /boot r/w and adb push the files to it. You can overwrite the current uRecRam and uRecImg or push them as uAltRam and uRecImg. (or both so you can always have it as alt boot if this happens again)
Thanks I've been trying to get /dev/block/mmcblk0p1 to mount after making /boot, but I just can't get it to work. The best try I have is:
mount -o remount,rw /
mkdir /boot
mount /dev/block/mmcblk0p1 /boot
which returns
Code:
mount /dev/block/mmcblk0p1 /boot
Usage: mount [-r] [-w] [-o options] [-t type] device directoryfdisk shows the below:
Code:
root@encore:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 935 7060567+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 723 4886052+ 83 Linux
/dev/block/mmcblk0p7 723 768 361327+ 83 Linux
/dev/block/mmcblk0p8 768 935 1347301 c Win95 FAT32 (LBA)Yes. That is odd to me that 'busybox mount' and 'mount' aren't the same thing or at least not functionally equivalent. But it did indeed work!
plz help me, can this TWRP version allow to flash CM7 (in case i dont wanna use CM11 and return to CM7)?
I could not get this TWRP to flash older ROM's without replacing /META-INF/com/google/android/updater-binary in the ROM's zip file.
You could also install older version of TWRP as alt-boot and boot to that to flash CM7 if needed.
TWRP 2.6.3.0 running great.
Been running TWRP 2.6.3.0 since you posted it. No problems, no complaints. Wben you going to post it on the TWRP site. Would have to note it's for CM11 only and leave a prior version available. Your 2.4.1.0 ran fine also with no problems.
Thanks for your great work.
Been running TWRP 2.6.3.0 since you posted it. No problems, no complaints. Wben you going to post it on the TWRP site. Would have to note it's for CM11 only and leave a prior version available. Your 2.4.1.0 ran fine also with no problems.
Thanks for your great work.
Can Someone please post a link to the new TWRP 2.6.3.0, the download currently isn't working for me...
Thanks.
Please attach or repost. I can't find any copy of this version, and 2.6.3.0 is said to be required for CM 11.
Also, dl.twrp.me has twrp-2.6.3.0-encore-signed.zip, but it only contains uRecImg, uRecRam, and META-INF so I'm not sure how to use it (Can I just rename them to uImage and uRamdisk and overwrite the two files on my SD card that successfully installed CM10?)
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
31Team 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.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
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
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.8Well, after a long hiatus, the stirring of CM11 has piqued my interest over here again...
TWRP 2.6.3.0
Please test and report back!
EMMC Recovery install: http://techerrata.com/file/eyeballer/twrp/openrecovery-twrp-2.6.3.0-encore-signed.zip
EMMC AltBoot install: http://techerrata.com/file/eyeballer/twrp/openrecovery-twrp-2.6.3.0-encore-ALT-signed.zip2ReverendJKR posted a great video on TWRP and Goo Manager working together.. Much more to come with this relationship
http://youtu.be/OA0S275XO3U
New posts
-
Question Sony Xperia 1 mark V china up rom SEA, Can use update OTA
- Latest: Laclevuinhon
-
-
