TWRP Recovery
For Galaxy Mini
Team Win Recovery Project 2.x, 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.
BUGS:
If you have found a bug, please consider posting it here.
LIVE SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
chraso: For his precious help.
Me: For compiling it for Galaxy Mini.
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.
DOWNLOAD:
http://www.upload.ee/files/3992673/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
What to test in latest build?:
-NOTHING. IT IS STABLE NOW.
Reserved
Will test it the moment I get home. Which is about 4 hours from now...
Tapatalk-kal küldve az én GT-S5570-el
doesnt boots.hangs on teamwin boot screen. luckily i had pc.currently flashing recovery by odin
+1
arpitkh96 said:
doesnt boots.hangs on teamwin boot screen. luckily i had pc.currently flashing recovery by odin
Click to expand...
Click to collapse
Thanks for feedback.
Now, can you help me find the problem?
How?
-Install recovery.
-Though it's stuck at Teamwin's screen, use adb in pc and give the following command:
Code:
adb pull /tmp/recovery.log
-Now, you will have a recovery.log file at the location where your adb files are there.
Attach that file in your post or use pastebin.com.
AND
Can you try that (terminal emulator) method once?
If you don't know what I'm talking about, see PhilZ recovery FAQs > Alternative way to flash this recovery.
Bhargav97 said:
Thanks for feedback.
Now, can you help me find the problem?
How?
-Install recovery.
-Though it's stuck at Teamwin's screen, use adb in pc and give the following command:
Code:
adb pull /tmp/recovery.log
-Now, you will have a recovery.log file at the location where your adb files are there.
Attach that file in your post or use pastebin.com.
AND
Can you try that (terminal emulator) method once?
If you don't know what I'm talking about, see PhilZ recovery FAQs > Alternative way to flash this recovery.
Click to expand...
Click to collapse
terminal method doesnt works either.here is the log
arpitkh96 said:
terminal method doesnt works either.here is the log
Click to expand...
Click to collapse
Thanks for logs. They helped me.
I forgot to add some things in recovery.
I didn't recompile but repacked with those things added.
If you get a black screen, don't give me logs. (It maybe a repack problem)
But, if you get teamwin logo, I need logs again.
New recovery.img for test:
http://www15.zippyshare.com/v/37395986/file.html
Use terminal emulator method.
Bhargav97 said:
Thanks for logs. They helped me.
I forgot to add some things in recovery.
I didn't recompile but repacked with those things added.
If you get a black screen, don't give me logs. (It maybe a repack problem)
But, if you get teamwin logo, I need logs again.
New recovery.img for test:
http://www15.zippyshare.com/v/37395986/file.html
Use terminal emulator method.
Click to expand...
Click to collapse
loops between black screen and Samsung logo. Cant give log ,adB doesnt recognises
Sent from my GT-S5570 using XDA Premium 4 mobile app
arpitkh96 said:
loops between black screen and Samsung logo. Cant give log ,adB doesnt recognises
Sent from my GT-S5570 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will be back after a re-compile.(15-20 min)
Sorry to be late.
Here's new test:
http://www.upload.ee/files/3989901/recovery.img.html
Bhargav97 said:
Sorry to be late.
Here's new test:
http://www.upload.ee/files/3989901/recovery.img.html
Click to expand...
Click to collapse
Booted! Report time!
It can't flash sd-ext scripts.
Trying to mount or unmount partitions doesn't do anything and can get the vibration engine stuck on working.
hard bricked
cell bricked. time 4 ssc .hahaha.
only teamwin logo appearing.
sushil888 said:
cell bricked. time 4 ssc .hahaha.
only teamwin logo appearing.
Click to expand...
Click to collapse
Use test img files. Do all these only if you know how to recover. You'll have flash an older recovery using odin.
ast00 said:
Booted! Report time!
It can't flash sd-ext scripts.
Trying to mount or unmount partitions doesn't do anything and can get the vibration engine stuck on working.
Click to expand...
Click to collapse
Good...
Atleast it booted now...
You will have to help me.
-Boot into TWRP.
-Go to Mounts
-And select/un-select partitions and then install an sd-ext script and let it fail.
-Now, without doing anything else, give me the recovery log. (method in page #1)
And...you mean vibrator gets stuck in between?
Bhargav97 said:
Use test img files. Do all these only if you know how to recover. You'll have flash an older recovery using odin.
Good...
Atleast it booted now...
You will have to help me.
-Boot into TWRP.
-Go to Mounts
-And select/un-select partitions and then install an sd-ext script and let it fail.
-Now, without doing anything else, give me the recovery log. (method in page #1)
And...you mean vibrator gets stuck in between?
Click to expand...
Click to collapse
It's vibrating non stop and it only stops if I reboot.
http://pastebin.com/Bg5GJ8rF
This logs is weird... It looks like it does mount the stuff, it just doesn't update the ui.
ast00 said:
It's vibrating non stop and it only stops if I reboot.
Tapatalk-kal küldve az én GT-S5570-el
Click to expand...
Click to collapse
For me its not vibrating continuously but duration of vibration on a click or touch is really large.
One bug I noticed is that progress bars are not resized.
While backing up a ROM the indeterminate progress bar is fine but the blue one showing exact progress is not resized.
Its width is larger (it goes out of screen on rhs) and height is smaller than that of indeterminate progress bar so it doesn't actually appears as an overlay.I don't have camera now to show you a pic.I will show you pic after 2hrs
Sent from my GT-S5570 using XDA Premium 4 mobile app
ast00 said:
It's vibrating non stop and it only stops if I reboot.
http://pastebin.com/Bg5GJ8rF
This logs is weird... It looks like it does mount the stuff, it just doesn't update the ui.
Click to expand...
Click to collapse
Logs look fine.
@arpitkh96 says it's not vibrating non-stop but duration of vibration is long. I think, that can be managed somehow.
About the other report you gave of error when installing zip:
Your zip file's update-binary is old. You will need to update it. Replace /META-INF/com/google/android/update-binary file from cm11 or omni4.4 zip. You will need to do it in ANY zip that doesn't install. This is the way it works. KitKat has changed many a things, this is one of them.
Please try this and give result.
And, cm11 or omni or any other ROMs are installing or not?
Also, what do you mean by "mounting-unmounting partitions doesn't do anything." If the partitions are not mounted, your log would have errors but there are no errors.
@arpitkh96,
I know about that progress bar bug. Its theme related. I would fix it after fixing major recovery problems.
You can use any 240x320 twrp theme uptil then. It would work just fine.
For more info on Themes for TWRP, visit here:
http://forum.xda-developers.com/nexus-4/themes-apps/twrp-theme-collection-thread-t2035234
Related
Team Win Recovery Project 2.x, 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.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-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)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
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.
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 40 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.
Reserved.
Dees_Troy said:
This has been available for a little while, but now I'm adding an official thread for it here on XDA.
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.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.
Click to expand...
Click to collapse
Would it work with V28C ?
Thx.
Sent from my LG-P970 using xda premium
florin250 said:
Would it work with V28C ?
Thx.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
i dont think so......
but....we better wait answer from the expert
@OP
wow.....i just dream about this last night and today you give this.....thank you so much....
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Ilko said:
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Click to expand...
Click to collapse
download stuck at 99,99%, why???
edit : downloading without download manager, now it's okay
In ClockworkMod, on Nandroid Backup...(there is no option to save the name as we wish), it defaultly gives a name with date for backup..
So, here in TWRP, is there possibility for giving name for Nandroid Backup ?
And what are the bugs remaining after 2.3.1.0 update ?
Had anyone brick phone or bootloop history with this ?
sekhar13515 said:
In ClockworkMod, on Nandroid Backup...(there is no option to save the name as we wish), it defaultly gives a name with date for backup..
So, here in TWRP, is there possibility for giving name for Nandroid Backup ?
And what are the bugs remaining after 2.3.1.0 update ?
Had anyone brick phone or bootloop history with this ?
Click to expand...
Click to collapse
The old TWRP recoveries never completely worked for OB.Sometimes it was the SD mounting, sometimes you couldn't restore the backup done with the same TWRP version and so on.I will try this because I like TWRP more than CWM but it's the last time if it won't work.
---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------
Ilko said:
the latest is 2.3.1.1
http://techerrata.com/file/twrp2/p970/openrecovery-twrp-2.3.1.1-p970.img
Click to expand...
Click to collapse
No, it's not but it's 2.3.20(not yet for OB of course).
USB storage not mounting.
Back to the "bomb proof" cwm 5.8.1.3 touch.
great share!Very good job, thank you.
there is a new version 2.3.1.1
timvdhoorn said:
there is a new version 2.3.1.1
Click to expand...
Click to collapse
ilko already said it here http://forum.xda-developers.com/showpost.php?p=34469364&postcount=6 and there is a newer version but it haven't been built to our device yet.
Updated!
Dees_Troy said:
Updated!
Click to expand...
Click to collapse
SDcard mounting as mass storage still not working, please check.
I was writing the same report : )
well, too bad. I like it but it's useless to me since I transfer files very often through recovery. I can't compile a flasher with that
Indeed I prefer twrp rather than cwm.
Dees, what you need to solve the SD card?
Enviado desde mi LG-P970 usando Tapatalk
Every new version always the same problem.
re4lsk said:
Indeed I prefer twrp rather than cwm.
Dees, what you need to solve the SD card?
Enviado desde mi LG-P970 usando Tapatalk
Click to expand...
Click to collapse
I need to know the proper path for the lun file. By default it's in /sys/devices/platform/usb_mass_storage/lun0/file
You'll have to look for it in TWRP, not in Android though if you find it in Android then I can try switching kernels... I'd need a copy of your current kernel or boot image to switch.
A lot of newer devices don't support USB storage mode anymore at all, so bear that in mind when you're getting ready to upgrade to a new device. You'll have to get used to using ADB to push files or use ADB sideload mode.
Dees_Troy said:
I need to know the proper path for the lun file. By default it's in /sys/devices/platform/usb_mass_storage/lun0/file
You'll have to look for it in TWRP, not in Android though if you find it in Android then I can try switching kernels... I'd need a copy of your current kernel or boot image to switch.
A lot of newer devices don't support USB storage mode anymore at all, so bear that in mind when you're getting ready to upgrade to a new device. You'll have to get used to using ADB to push files or use ADB sideload mode.
Click to expand...
Click to collapse
well the black is an old device(2011) so usb storage still works, you need zImage or boot.img to get the kernel? i can point you to the CM kernel source, i'll see if my old linux VM still works to get you the zImage. but in the mean time i'll upload you the boot.img from cm10 from 20-12-2012 nightly.
CM kernel source
re4lsk said:
well the black is an old device(2011) so usb storage still works, you need zImage or boot.img to get the kernel? i can point you to the CM kernel source, i'll see if my old linux VM still works to get you the zImage. but in the mean time i'll upload you the boot.img from cm10 from 20-12-2012 nightly.
CM kernel source
Click to expand...
Click to collapse
It's not that I need a kernel as much as I need the proper path to the lun file for whatever kernel I happen to be using. Since I don't have an Optimus Black I can't boot it up and look for it myself.
Key Features:
Ability to save custom recovery settings
Default partitions to back up
Default zip folder location
Default color theme (lots to choose from) (Thanks to ffolkes!)
Default Time Zone (for more accurate time stamps)
Zip Signature Verification
Zip md5 Verification (looks for file with zipname.zip.md5)
Ability to flash multiple zips in one go
Ability to select which individual partitions to backup, and restore.
Ability to choose compression or no compression backups.
Compression takes longer of course, but you save roughly half the space. EVO3D's stock system uncompressed is ~800mb, 380mb compressed. You choose.
Ability to auto restore GAPPS on zip flash (for CM based ROMS)
Ability to auto reboot after successful flashes (for the lazy)
Some devices utilize their capacitive buttons in recovery.
Home - Main Menu
Menu - Advanced Menu
Back - Up a Menu Level
Search - Select Current Selection
Battery Level and Timestamp (Better safe than sorry)
What's new in 2.6.0.0:
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
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)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks
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.
What's new in 2.5.0.0:
Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
Added official theme for 1080x1920 portrait devices (HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
Fixed a problem with directory permissions on split archive backups
Fixed a problem with md5 verification of backups
Added a search function to libtar (thanks to kokotas)
Improve handling of XML errors (fix permissions)
Fixed handling of subpartitions
Improvements to recovery.fstab flags
Fixed a problem with decryption not being able to locate the decryption key in some situations
Special Note: If you are running a custom theme, the changes in 2.5.0.0 will likely not be compatible with your theme.
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
HTC Dumlock Instructions:
Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
Reboot into recovery.
Make a backup of your phone.
Tap Advanced.
Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)
Tap Install HTC Dumlock. This will install the app and binaries needed to make everything work nicely.
Reboot your device.
Find and open the HTC Dumlock app.
If/when prompted, give the app root (SuperUser) permissions.
Tap the Execute HTC Dumlock button.
Wait patiently for a couple of minutes. It takes a little while.
If your device doesn't reboot automatically, reboot it manually. Reboot it normally. DO NOT reboot it to recovery.
You should now be in your recovery, but your recovery is flashed into boot.
Tap Advanced.
Tap HTC Dumlock.
Tap Restore Original Boot.
Use your recovery like normal. Flash a new kernel. Restore a backup with a different kernel. Do whatever you please!
Consider donating!
Note, you must repeat steps 8 through 17 EVERY TIME you need to flash boot.
Installation:
Unlock bootloader at http://www.htcdev.com/bootloader/
Turn phone completely off.
Boot into HBOOT then Fastboot
Erase cache from fastboot before flashing recovery. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Downloads:
http://goo.im/devs/Flyhalf205/MYSTUL/Recovery//openrecovery-twrp-2.6.0.0-mystul.img
Root:
To gain root on stock rom. Flash recovery in fastboot then flash this inside of recovery. There are two root programs. Superuser and SuperSU. Both are listed.
Superuser - http://download.clockworkmod.com/superuser/superuser.zip
OR
SuperSU - download.chainfire.eu/supersu
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
This version of TWRP has OTG-USB support also. Enjoy
The download link is missing the .img extension. Also, once I flashed the recovery and booted into it, the screen started looking crazy, like the recovery was trying to output the wrong resolution or sync rates. Looked crazy: http://db.tt/RIaIsti9
nuclear_eclipse said:
The download link is missing the .img extension. Also, once I flashed the recovery and booted into it, the screen started looking crazy, like the recovery was trying to output the wrong resolution or sync rates. Looked crazy: http://db.tt/RIaIsti9
Click to expand...
Click to collapse
Easy fix. I'll put a new build out later.
New build is up if anyone can test and make sure graphic works?
Flyhalf205 said:
New build is up if anyone can test and make sure graphic works?
Click to expand...
Click to collapse
It's looking better, but the colors are off, and it's duplicated along the X axis. However, if I let the recovery sit long enough to turn off the screen, when it turns back on, it then looks correct (blue and not duplicated).
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.22.jpg
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.25.jpg
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
Forgot to mention that this recovery is able to mount /sdcard and see the contents of it, so hopefully that helps you to improve the clockwork recovery to match.
nuclear_eclipse said:
It's looking better, but the colors are off, and it's duplicated along the X axis. However, if I let the recovery sit long enough to turn off the screen, when it turns back on, it then looks correct (blue and not duplicated).
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.22.jpg
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.25.jpg
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
Forgot to mention that this recovery is able to mount /sdcard and see the contents of it, so hopefully that helps you to improve the clockwork recovery to match.
Click to expand...
Click to collapse
So this could flash zips without adb?
Sent from my HTC first
phositadc said:
So this could flash zips without adb?
Sent from my HTC first
Click to expand...
Click to collapse
It appears that way, though I have not tested that.
nuclear_eclipse said:
It's looking better, but the colors are off, and it's duplicated along the X axis. However, if I let the recovery sit long enough to turn off the screen, when it turns back on, it then looks correct (blue and not duplicated).
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.22.jpg
https://dl.dropboxusercontent.com/u/7859496/Android/2013-04-19 14.52.25.jpg
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
Forgot to mention that this recovery is able to mount /sdcard and see the contents of it, so hopefully that helps you to improve the clockwork recovery to match.
Click to expand...
Click to collapse
Another easy fix It's building CWM right now with the fixed internal sdcard fix then I'll build the fixed TWRP.
New build of TWRP is up. Should be completely 100% to go now...
Man, I swear I love you lol. I was just checking the First/AT&T One section and bam. You pop up with the recoveries! My toolkits will be going this way, thanks to you!
hasoon2000 said:
Man, I swear I love you lol. I was just checking the First/AT&T One section and bam. You pop up with the recoveries! My toolkits will be going this way, thanks to you!
Click to expand...
Click to collapse
I try man. lol. Btw The ATT One works with the just the HTC One toolkit so you could just mirror post.
Sent from my ADR6425LVW using Tapatalk 2
Everything looks correct now.
Sent from my HTC first using xda premium
Hey man. Adb is broken on twrp and I assume cwm too. I'm going to send you a pull request with the fix
Sent from my M7 using xda premium
Pull request sent
Sent from my M7 using xda premium
jmztaylor said:
Pull request sent
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Merged. I'll build them shortly. :good:
Flyhalf205 said:
Merged. I'll build them shortly. :good:
Click to expand...
Click to collapse
I only sent pull request for twrp. I don't use CWM so Im not completely sure that fix will work on CWM or not.
jmztaylor said:
I only sent pull request for twrp. I don't use CWM so Im not completely sure that fix will work on CWM or not.
Click to expand...
Click to collapse
Willing to test it? https://www.dropbox.com/s/nnmfxafdp756ptv/openrecovery-twrp-2.5.0.0-mystul.img
Flyhalf205 said:
Willing to test it? https://www.dropbox.com/s/nnmfxafdp756ptv/openrecovery-twrp-2.5.0.0-mystul.img
Click to expand...
Click to collapse
I'm already in bed. I will check it out tomorrow
Sent from my M7 using xda premium
Works good. I had a bunch of issues trying to boot any recovery earlier. But fastboot erase cache made it work. So its similar to the HTC One. Maybe put that in OP so you can avoid the questions.
Team Win Recovery Project 2.x, 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.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 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
CHANGELOG for 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
CHANGELOG for 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
CHANGELOG for 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)
CHANGELOG for 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
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
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 40 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.
XDA:DevDB Information
[RECOVERY] TWRP 2.6.0.0 [2013-07-08], a Tool/Utility for the Sony Xperia Tablet Z
Contributors
Dees_Troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.6.0.0
Stable Release Date: 2013-07-08
Created 2013-08-20
Last Updated 2013-08-20
Reserved
The images are built using pollux_windy compatible kernels, but if you're using the FOTAKernel setup, it will work with either model. If someone wants to come by #twrp and test builds for regular pollux I'll be happy to try to add support for that model as well.
pls add the information that its for pollux_windy only!
Followed the instruction but " no recoveries were found "
And if you put "for pollux ONLY" on the title that would be great
Sent from my SGP311 using xda app-developers app
I'm at a loss right now. I get up to the point where it's time to connect my tablet to the computer and when I press the volume up button it just flashes this blank screen until I give up. Also my computer doesn't recognize the device being plugged in when I reach this step. Both my mac and Windows computers. I'm at the point where I wanna either return it or pay someone to get twrp on it. I can't stand this Sony skin... I NEED CM 10!
XDA Moderation is contacting OP to clarify the TWRP is for a specific device version.
Thank You.
MD
Moscow Desire said:
XDA Moderation is contacting OP to clarify the TWRP is for a specific device version.
Thank You.
MD
Click to expand...
Click to collapse
AFAIK recovery is bundled within the boot image for Pollux* so we need to know also which kernel is bundled or if they support a multi loader (little kernel or whatever)
Inviato dal mio SGP311 usando Tapatalk 4
I'm just as lost. I'm trying to find a custom recovery for the "POLLUX" and not the "WINDY"
If it's of any use, I'll repeat here what I've already posted in a duplicate TWRP thread in this forum:
If you go to the Team Win website (use the link in the OP), then click on "get TWRP for my device" only the Pollux_windy (wifi only) version is shown.
Again, on the Team Win website, looking at the install instructions for TWRP on the Tablet Z Pollux_Windy, it's not straight forward which makes me think it can't be done using goo. Have a look here : http://www.teamw.in/project/twrp2/185
Very confusing.
is anyone using this recovery? feedback please. thanks
----------------
This was mentioned in the TWRP page
Code:
If you happen to be using lk, then boot your device into lk's fastboot mode and flash using this command:
fastboot flash recovery fotakernel.img
how do I know I'm using "lk"? thanks again
mrjayviper said:
how do I know I'm using "lk"? thanks again
Click to expand...
Click to collapse
If you don't know then you probably aren't using it. LK is a 3rd party bootloader ported to the TabZ
.........
can we fastboot flash this image file ?
golfinggino said:
can we fastboot flash this image file ?
Click to expand...
Click to collapse
No - Sony use a combined kernel/recovery so just flashing the TWRP imgage will not work.
You first have to go through the process of installing the "LK kernel". This effectively splits-out the kernel and recovery.
You can then "fastboot flash boot" the boot.img for whichever custom ROM you have, and then also "fastboot flash recovery" the TWRP recovery image.
See this thread : http://forum.xda-developers.com/showthread.php?t=2333826 , specifically posts #1,2,3,20,39,60,61.
I've done it and I've now got TWRP with my PAC ROM. The process was quite easy - but just watch the timings of when you press the volume buttons. Also, when the tablet goes into LK fastboot mode the LED is red. Bit of a bad choice of colour as it has caused some people to think their tablet has died.
to install TWRP on my stock and unlocked bootloader, I just used the adb commands mentioned in the TWRP site.
mrjayviper said:
to install TWRP on my stock and unlocked bootloader, I just used the adb commands mentioned in the TWRP site.
Click to expand...
Click to collapse
Maybe you have a link to the commands. I cant find it
egosapienz said:
Maybe you have a link to the commands. I cant find it
Click to expand...
Click to collapse
Half way down this page : http://www.teamw.in/project/twrp2/185
Try it out. Maybe I did something wrong but it didn't work for me - maybe it only works on stock ROM.
I had to install LK kernel to get TWRP with PAC ROM - see my post above
GretaLewd said:
Half way down this page : http://www.teamw.in/project/twrp2/185
Try it out. Maybe I did something wrong but it didn't work for me - maybe it only works on stock ROM.
I had to install LK kernel to get TWRP with PAC ROM - see my post above
Click to expand...
Click to collapse
Not shure if I should do it. Its for the WIFI-only Tab. My bootloader is locked too. But anyway thanx for the link
egosapienz said:
Not shure if I should do it. Its for the WIFI-only Tab. My bootloader is locked too. But anyway thanx for the link
Click to expand...
Click to collapse
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
------
I wouldn't do it if yours is the polux. it clearly says wifi only and there seems to be no TWRP for the LTE version.
mrjayviper said:
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
------
I wouldn't do it if yours is the polux. it clearly says wifi only and there seems to be no TWRP for the LTE version.
Click to expand...
Click to collapse
You´re right. I´ll wait. Thanx
Hi,
I managed to build latest TWRP for N5100/N5110.
This a test build you can flash from your existing recovery.
Odin packages and flashable ZIPs are now available for n5100 and N5110.
Download:
http://www.androidfilehost.com/?w=files&flid=15631
What's new since 2.6.3.0?
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
NOTE: This is a test version and does NOT support f2fs, but you can switch to other filesystems
What's new in 2.7.0.0:
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 AOSP decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Changelog:
Build 1:
-First release
Credits:
@sbrissen for original port and maintenance of CM11 for n5100/n5110/n5120.
@Dees_Troy & TEAMWIN for making TWRP
Reserved
i'm waiting for n5110
Is there any chance for a 5120 version, if you don't mind me asking.
Sent from my GT-N5120 using Tapatalk
Thx for your effort. Great to have a updated Recovery. Can this used for all kind of Roms? 4.1.2, 4.2.2 and 4.4.x?
Thank you for planning on including the 5110. I will patiently waiting for the addition of this device.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Build 2 is released.
Now n5100 and n5110 is supported. You can get tar files to flash via Odin or use zip files if you want to flash from your existing recovery (CWM, PhilZ or older versions of TWRP)
User_99 said:
Thx for your effort. Great to have a updated Recovery. Can this used for all kind of Roms? 4.1.2, 4.2.2 and 4.4.x?
Click to expand...
Click to collapse
I only tested with 4.4.x. But it should work with older ROMs too.
Fobz said:
Is there any chance for a 5120 version, if you don't mind me asking.
Sent from my GT-N5120 using Tapatalk
Click to expand...
Click to collapse
For now, I can't provide 5120 support.
whitemolecule said:
I only tested with 4.4.x. But it should work with older ROMs too.
For now, I can't provide 5120 support.
Click to expand...
Click to collapse
No problems!
Sent from my Nexus 4 using Tapatalk
Thanks much for flashable zips.
Works great. I've been waiting a long time for this release. Thank you. You rule.
Sent from my GT-N5110 using XDA Premium HD app
whitemolecule said:
Build 2 is released.
Now n5100 and n5110 is supported. You can get tar files to flash via Odin or use zip files if you want to flash from your existing recovery (CWM, PhilZ or older versions of TWRP)
Click to expand...
Click to collapse
Hello Sir thanks for your great work updating TWRP I been using Philz CWM recovery with no problems im thinking of trying yours which is better Philz CWM or TWRP hate to change since Philz is working let me know thanks
matthewtech770 said:
Hello Sir thanks for your great work updating TWRP I been using Philz CWM recovery with no problems im thinking of trying yours which is better Philz CWM or TWRP hate to change since Philz is working let me know thanks
Click to expand...
Click to collapse
The "better" is the one you choose.
Wow again. Quickly, I want to say, it's nice to get back to TWRP. Been using Philzs and it does a good job but not as smooth and easy as TWRP. The only rom I can't use this with is CivZ's new 4.4.2. It won't allow me to hit the "next" button when installing the rom. All other roms work perfect. This is donation good. Thank you again.
Sent from my GT-N5110 using XDA Premium HD app
Thanks for this. Seems It has problems with Aroma installers. The screen orientation specifically. The screen stays in landscape and only allows the top half of the screen to show the aroma installation, while the touch sensitivity is still in portrait. In other words you have to touch the screen as if it were in portrait and kind of guess where the buttons would be while the actual pictures on the screen are in landscape on only the top half of the screen and very stretched looking. Thanks again for your work.
kstephens98 said:
Thanks for this. Seems It has problems with Aroma installers. The screen orientation specifically. The screen stays in landscape and only allows the top half of the screen to show the aroma installation, while the touch sensitivity is still in portrait. In other words you have to touch the screen as if it were in portrait and kind of guess where the buttons would be while the actual pictures on the screen are in landscape on only the top half of the screen and very stretched looking. Thanks again for your work.
Click to expand...
Click to collapse
And that's why developers that use Aroma (like @civato) specify using Philz's Touch Recovery, which is a modified CWM, to flash their ROM's and kernels.
ramjet73
Nice observation. That is what I figured as well.. I usually have a flashable version of TWRP and Philz touch at the ready. I do a lot of testing with my tablet, with different roms and how apps work and can be modified with each.
Sent from my GT-N5110 using XDA Premium HD app
glockman4519 said:
Nice observation. That is what I figured as well.. I usually have a flashable version of TWRP and Philz touch at the ready. I do a lot of testing with my tablet, with different roms and how apps work and can be modified with each.
Click to expand...
Click to collapse
Yea, I do the same thing.
The easiest way I've found to switch recoveries is to keep "recovery.img" versions of each one on the SD card, then move the files you want to flash to the SD card, use Flashify to install the recovery needed if it's not already there, then reboot into recovery with the advanced power menu. It's still a good idea to keep the .zip version of each recovery on the SD card in case you're already in recovery before you discover that you have the wrong version installed. It would be nice to have USB OTG mount available in this version of TWRP recovery since I can't seem to get USB storage working as there appears to be some conflict with ADB.
I tend to do all my backups with TWRP though since it supports compression and restores have been more reliable for me than using CWM. The backup formats are different so it doesn't make sense to use both.
If the Samsung devices supported "fastboot boot recovery.img" like Nexus, HTC and most other brands it wouldn't be necessary to actually flash an alternate recovery since it could just be booted as needed when the tablet is connected to a computer.
Edit: I just discovered that the "fixed" 2.6.3.0 version of TWRP from this post works fine with Aroma. It doesn't have the USB storage option in mounts (explained in this post) but I can't get that to work with this 2.7.1.0 version anyway. I'd love to use this updated version of TWRP but it would be nice if the Aroma support could be included from the 2.6.3.0 version and an OTG mount option (as opposed to USB storage) could be added.
ramjet73
I was wondering if there would be a possibility of getting this recovery in portrait mode. I am wanting to use a Holofied theme that has more options that can utilize TWRP even better but it does not work with landscape layout. I have already tried to take the Grouper TWRP and used its res folder and added that to the n5110 twrp and repacked the recovery.img and flashed but recovery is still in landscape but is displaying a portrait layout which is unusable.
pimpmaneaton said:
I was wondering if there would be a possibility of getting this recovery in portrait mode. I am wanting to use a Holofied theme that has more options that can utilize TWRP even better but it does not work with landscape layout. I have already tried to take the Grouper TWRP and used its res folder and added that to the n5110 twrp and repacked the recovery.img and flashed but recovery is still in landscape but is displaying a portrait layout which is unusable.
Click to expand...
Click to collapse
Yes, I will try to build in portrait mode when I have time, I think this will also fix aroma installer issues too.
[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of official builds.
Device Config: https://github.com/bigbiff/android_device_google_crosshatch
Hello, this is a test build for crosshatch users.
If others thing don't work, please report the issue and let me know.
I am opening this thread to replace @Dees_Troy's thread with his blessing.
http://twrp.me
Old Info
Download here:
Test1: https://build.twrp.me/test/crosshatch/twrp-3.6.0-0-test1-crosshatch.img
- fix backup and restore
- fix decryption thanks to @Captain_Throwback and his twrp-common tree which fixes the order of proprietary services starting: https://github.com/TeamWin/android_device_qcom_twrp-common
- supports 12 decryption with no pin set
- fully supports 11 decryption with keymaster
Thanks for the build. Tested on Android 11, latest Scorpion rom. Touch does not appear to be working.
ghostcrew said:
Thanks for the build. Tested on Android 11, latest Scorpion rom. Touch does not appear to be working.
Click to expand...
Click to collapse
Scorpion is not using a stock DTBO. You will have to use the fastbooted twrp adb shell session to install this flashable zip:
https://build.twrp.me/test/crosshatch/twrp-installer-3.6.0_11-0-crosshatch.zip
Push it to /sdcard with adb, and do twrp install twrp-installer-3.6.0_11-0-crosshatch.zip inside the adb shell
Then use adb to reboot to TWRP that is now installed as recovery in boot.
Thanks for TWRP for Pixel 3XL!
Thanks bro!. Dont use my pixel for much anymore but great to see someone still developing for it
Thank you for TWRP! Lifesaver. Tried this on my Pixel 3XL running on Evolution X, A11 .... Works great!
bigbiff said:
Scorpion is not using a stock DTBO. You will have to use the fastbooted twrp adb shell session to install this flashable zip:
https://build.twrp.me/test/crosshatch/twrp-installer-3.6.0_11-0-crosshatch.zip
Push it to /sdcard with adb, and do twrp install twrp-installer-3.6.0_11-0-crosshatch.zip inside the adb shell
Then use adb to reboot to TWRP that is now installed as recovery in boot.
Click to expand...
Click to collapse
I followed your instructions and now I have twrp on my phone and touch is working. Thank you for the instructions and thank you for TWRP on Pixel 3xl!
bigbiff said:
[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of official builds.
Device Config: https://github.com/bigbiff/android_device_google_crosshatch
Hello, this is a test build for crosshatch users.
If others thing don't work, please report the issue and let me know.
I am opening this thread to replace @Dees_Troy's thread with his blessing.
Download here:
Test1: https://build.twrp.me/test/crosshatch/twrp-3.6.0-0-test1-crosshatch.img
- fix backup and restore
- fix decryption thanks to @Captain_Throwback and his twrp-common tree which fixes the order of proprietary services starting: https://github.com/TeamWin/android_device_qcom_twrp-common
- supports 12 decryption with no pin set
- fully supports 11 decryption with keymaster
http://twrp.me
Click to expand...
Click to collapse
Hey, Biff. Thanks, of course. Just wondering if you are releasing it for Pixel 3... I am on P3XL, but my wife is on P3.
sliding_billy said:
Hey, Biff. Thanks, of course. Just wondering if you are releasing it for Pixel 3... I am on P3XL, but my wife is on P3.
Click to expand...
Click to collapse
We are supposed to have someone lined up. Has anyone posted in the blueline forums?
Was able to install TWRP on my Crosshatch however whenever I tried to use the ADB Sideload function to install a rom I would get this error:
serving: 'C:\Users\Zero\Downloads\Pixel 3 XL Project\EvolutionX\evolution_crosshatch-ota-sq1d.211205.016.a1-12251000-unofficial-unsigned.zip' (~0%) adb: failed to read command: No error
Logs attached. *XDA wont let me upload the files see below.
Logs
delete...
Zero_Shadow said:
Was able to install TWRP on my Crosshatch however whenever I tried to use the ADB Sideload function to install a rom I would get this error:
serving: 'C:\Users\Zero\Downloads\Pixel 3 XL Project\EvolutionX\evolution_crosshatch-ota-sq1d.211205.016.a1-12251000-unofficial-unsigned.zip' (~0%) adb: failed to read command: No error
Logs attached. *XDA wont let me upload the files see below.
Logs
Click to expand...
Click to collapse
I was able to sideload lineage-18.1. Does adb devices show sideload?
bigbiff said:
We are supposed to have someone lined up. Has anyone posted in the blueline forums?
Click to expand...
Click to collapse
Unfortunately, no.
bigbiff said:
I was able to sideload lineage-18.1. Does adb devices show sideload?
Click to expand...
Click to collapse
Yes I am able to use adb devices in my command prompt and see the device while adb sideload is active in twrp. Heres what happens.
I open up TWRP > Wipe (Factory Reset) then Advanced > ADB Sideload > Swipe to Start Sideload
I see Starting ADB Sideload feature
I go back to my computer and type adb devices (to confirm it see it) > adb sideload filename.zip (being the file of course).
Soon I hit enter I get a crash within TWRP and it goes back to the Main startup page for twrp.
When I go back to ADB Sideload I see this message:
E: fialed to mount /tmp/com.android.apex.cts.shim.
apex to loop device /dev/block/loop0. Reason: Device
or resource busy
E: Unable to create loop devices to mount apex files
E: Unable to load apex images frin /system_root/
system/apex
I did install TWRP to recovery using Advanced > Flash Current TWRP
If I use one of the recoveries for PE or Lineage I am able to flash using adb sideload.
*Edit 1: Now I did download the version from Telegram so let me try the one link above.
*Edit 2: Just tried with the one linked above same thing.
*Edit 3: Logs for review. https://drive.google.com/drive/folders/1PqKN_QzdGnFJTu4Ov-2iUzyzv85ZaD9D?usp=sharing
I could be doing something wrong so any help would be appreciated.
Zero_Shadow said:
Yes I am able to use adb devices in my command prompt and see the device while adb sideload is active in twrp. Heres what happens.
I open up TWRP > Wipe (Factory Reset) then Advanced > ADB Sideload > Swipe to Start Sideload
I see Starting ADB Sideload feature
I go back to my computer and type adb devices (to confirm it see it) > adb sideload filename.zip (being the file of course).
Soon I hit enter I get a crash within TWRP and it goes back to the Main startup page for twrp.
When I go back to ADB Sideload I see this message:
E: fialed to mount /tmp/com.android.apex.cts.shim.
apex to loop device /dev/block/loop0. Reason: Device
or resource busy
E: Unable to create loop devices to mount apex files
E: Unable to load apex images frin /system_root/
system/apex
I did install TWRP to recovery using Advanced > Flash Current TWRP
If I use one of the recoveries for PE or Lineage I am able to flash using adb sideload.
*Edit 1: Now I did download the version from Telegram so let me try the one link above.
*Edit 2: Just tried with the one linked above same thing.
*Edit 3: Logs for review. https://drive.google.com/drive/folders/1PqKN_QzdGnFJTu4Ov-2iUzyzv85ZaD9D?usp=sharing
I could be doing something wrong so any help would be appreciated.
Click to expand...
Click to collapse
What zip are you installing?
Tried the A12 builds for PE, EvoX and PixelDust same issue across the board.
Thanks a lot for this build!!! My Pixel3 XL keeps getting corrupt due to handing/wifi dropping, now finally I can have a Nandroid backup!
Need help installing pls. Tried many times with stock to no avail. Now trying with evolution Rom to no avail. My cmd is fastboot flash boot TWRP.img, which works with stock, but I'm unable to install or sideload and have to reflash the stock kernel to reboot the Rom. Same with evolution besides with stock I can attempt to reboot (after flashing twrp) which reboots to twrp, but won't reboot at all with evolution (until reflashing the kernel) I've been at this for a few hours now, any advice much appreciated.
brandonabandon said:
Need help installing pls. Tried many times with stock to no avail. Now trying with evolution Rom to no avail. My cmd is fastboot flash boot TWRP.img, which works with stock, but I'm unable to install or sideload and have to reflash the stock kernel to reboot the Rom. Same with evolution besides with stock I can attempt to reboot (after flashing twrp) which reboots to twrp, but won't reboot at all with evolution (until reflashing the kernel) I've been at this for a few hours now, any advice much appreciated.
Click to expand...
Click to collapse
You don't flash boot.img with this device. You temporarily boot it with fastboot boot img, then push it to sdcard and use twrp's install recovery ramdisk function.
nithin suresh said:
Thank you for TWRP! Lifesaver. Tried this on my Pixel 3XL running on Evolution X, A11 .... Works great!
Click to expand...
Click to collapse
Is there any possible way you could put instructions or how to install list for me I would greatly appreciate it. I have the pixel 3xl and have been having the hardest time getting twrp install as well as other items.