Related
[ THIS POST IS TEAMWIN'S STOCK TWRP POSTING. USE OF THE WORDS "US" AND "OURS" MEANS "DEES_TROY AND TEAMWIN" NOT HASHCODE ]
*** ALL CREDIT FOR TWRP BELONGS TO DEES_TROY AND TEAMWIN. ***
They do a BANG UP job on making a fantastic customizable touch-based recovery.
Donate to TeamWin:
http://www.teamw.in/project/twrp2
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2100963
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.
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.
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!
** THIS IS A FLASHABLE .ZIP FILE FOR INSTALLING IN YOUR CURRENT VERSION OF TWRP **
DOWNLOAD:
[ DO NOT DOWNLOAD ANY FILES FROM TEAMWIN'S WEBSITE. IN GENERAL, THEY ARE MEANT TO BE FLASHED TO UNLOCKED DEVICES AND WON'T WORK FOR THE KINDLE FIRE 2 ]
You can download from goo.im here and place on your SDCARD:
http://goo.im/devs/Hashcode/otter2/recovery-zip/zip-otter2-twrp-2.6.3.1-recovery.zip
md5sum: b9eb941b1673396c91f73ccda010daf1
INSTALL INSTRUCTIONS:
During the BLUE logo screen press the power button to cycle through options and select "Recovery" to enter TWRP.
Select "Install"
Navigate to where you placed the file on your device
Select the .zip filename
Swipe to confirm flash
Reboot
KNOWN ISSUES:
None at the moment.
BUGS:
First: I'd read through this thread and see if your issue isn't answered.
Second: Try googling for it
Third: If it seems like a Kindle Fire 2 issue, then post in the thread.
Lastly: If you have found a bug, please consider posting it to TeamWin's 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 #kindlefire-dev or #twrp on Freenode with your IRC client or just click this link.
can i just flash the new image from the old (previously available twrp) recovery?
755 said:
can i just flash the new image from the old (previously available twrp) recovery?
Click to expand...
Click to collapse
You flash it via fastboot
Sent from my Amazon Kindle Fire2 using xda app-developers app
The link is dead
Alin1997 said:
The link is dead
Click to expand...
Click to collapse
No, it isn't.
--
Sent from my mind to your screen.
Any chance this will get usb mounting fixed?
I can adb push, but usb mounting would make like much easier
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
any chance for flashable zip?
mindmajick said:
Any chance this will get usb mounting fixed?
I can adb push, but usb mounting would make like much easier
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I dont think TWRP supports USB sharing for /data/media emulated sdcard space.
Sent from my DROID4 using Tapatalk 2
Hashcode said:
I dont think TWRP supports USB sharing for /data/media emulated sdcard space.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Is it possible to port a cwm recovery?
Sent from my A2109A using Tapatalk HD
While I'm waiting on my fastboot cable, I've been trying to get to fastboot mode on my own. No luck, of course, no matter what I try. I guess I don't need twrp-2.4 yet since 2.3 does the job, but not having the latest is bothersome.
Sent from my Amazon Kindle Fire2 using xda premium
TWRP 2.5.0.0 for KF2?
Thanks for this. Wondered if TWRP 2.5.0.0 was on the way for the KF2. Any news?
Squuiid said:
Thanks for this. Wondered if TWRP 2.5.0.0 was on the way for the KF2. Any news?
Click to expand...
Click to collapse
Contact @Hashcode. He can make a newer version.
Gesendet von meinem LG-P990 mit Tapatalk 2
TWRP 2.6.0.0 is being tested.
Once approved, I'll add it to the instructions
Sent from my XT926 using Tapatalk 2
OP Updated with TWRP 2.6.0.0 download and instructions.
NOTE: USB Vendor ID / Product ID's have been reset to match Amazon stock OS for better compatibility
Enjoy
and remember if you like this product you can donate to TWRP at the top of this page:
http://www.teamw.in/project/twrp2
(Maybe mention [KFire2] in the donation so that they know what device you have)
WARNING: IF YOU INSTALLED THIS BEFORE TONIGHT(7/8) THEN I WOULD ADVISE RE-INSTALLING. I MADE SOME LAST MINUTE FIXES.
Hashcode said:
OP Updated with TWRP 2.6.0.0 download and instructions.
NOTE: USB Vendor ID / Product ID's have been reset to match Amazon stock OS for better compatibility
Enjoy
and remember if you like this product you can donate to TWRP at the top of this page:
http://www.teamw.in/project/twrp2
(Maybe mention [KFire2] in the donation so that they know what device you have)
WARNING: IF YOU INSTALLED THIS BEFORE TONIGHT(7/8) THEN I WOULD ADVISE RE-INSTALLING. I MADE SOME LAST MINUTE FIXES.
Click to expand...
Click to collapse
Flashed and looking good.
The WIPE screen has changed. Can I get a general consensus that choosing Advanced Wipe, and then choosing "Internal Storage" will still end in a bricked device, before anyone does it?
Thanks for your work on this Hashcode.
EDIT:
I normally create a backup and then copy it to my PC (Ubuntu 13.04), but I can't copy:
system.ext4.win
data.ext4.win
It gives me an error saying it can't copy them. I've tried a couple of times without joy.
Is there anything you want me to try?
chronicfathead said:
Flashed and looking good.
The WIPE screen has changed. Can I get a general consensus that choosing Advanced Wipe, and then choosing "Internal Storage" will still end in a bricked device, before anyone does it?
Thanks for your work on this Hashcode.
EDIT:
I normally create a backup and then copy it to my PC (Ubuntu 13.04), but I can't copy:
system.ext4.win
data.ext4.win
It gives me an error saying it can't copy them. I've tried a couple of times without joy.
Is there anything you want me to try?
Click to expand...
Click to collapse
Could be leaving those files open for some reason. Can you reboot back into recovery and try copying them again?
Also, the "Internal Storage" option under "Advanced Wipe" is for formatting /data + /sdcard. This should *NOT* result in a brick, but I haven't tested it personally.
Instructions have been changed slightly:
Swapped out the .img file for a flashable .zip file for use by those who already have TWRP installed.
Just download, toss on the SD card and flash in TWRP like anything else.
People who do not have TWRP installed should be using the 2nd-bootloader thread anyway.
Hashcode said:
Could be leaving those files open for some reason. Can you reboot back into recovery and try copying them again?
Also, the "Internal Storage" option under "Advanced Wipe" is for formatting /data + /sdcard. This should *NOT* result in a brick, but I haven't tested it personally.
Click to expand...
Click to collapse
I have rebooted into recovery and mounted USB storage, but it doesn't mount on my Ubuntu PC. The message I get is:
Unable to open MTP device '[usb:002,019]'
If I flick into the terminal in TWRP I see the following message:
E: Unable to locate volume information for USB storage mode.
Off to work. If you want me to try anything, just let me know.
chronicfathead said:
I have rebooted into recovery and mounted USB storage, but it doesn't mount on my Ubuntu PC. The message I get is:
Unable to open MTP device '[usb:002,019]'
If I flick into the terminal in TWRP I see the following message:
E: Unable to locate volume information for USB storage mode.
Off to work. If you want me to try anything, just let me know.
Click to expand...
Click to collapse
Sorry, you are correct. USB mounting inside recovery is not supported for any /data/media sharing type device. This includes the Galaxy Nexus and Nexus 4. :/
Best way to push/pull files from the device is via the Windows Command Line using adb.
To push files to the device:
adb push <filename> <destination>
example: adb push cm-10.1-otter2.zip /sdcard/Download
or to pull files from the device while in recovery:
adb pull /sdcard/Download/cm-10.1-otter2.zip
(This would pull the file from the device to whatever directory you are currently in)
or
adb sideload
eam 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.
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:
Flash through recovery ....i mean any recovery...CWM and TWRP.
https://www.mediafire.com/?4n0yy7d4y8c7inm
Credits:---
xenon92 - being an inspiration.
reserved
reserved.
I love the simplicity of TWRP.
EDIT: @k2wl, you'll have to edit the fstab manually to enable internal and external memory locations.
Finally, someone is sharing twrp new version,
Cool
cool
is this compatible with 4.4 CM ?
This should be SELinux compatible right? You rock as always @k2wl
Don't flash this yet. I think it doesn't Mount sdcard ( internal or external)
CyanogenMod 12.1 is a free, community built distribution of Android 5.1 (Lollipop) which greatly extends the capabilities of your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROM Features:
Based on latest CyanogenMod 12.1 sources
Compiled with SaberMod 4.9 and JustArchi's Optimizations V4.1 for maximum performance
Full F2FS support - no mount issues during ROM updates
SELinux set to 'permissive' by default
Android default UID and GID for internal storage
(No more write issues after formatting sdcard!)
Slim and fast user build
Kernel Features:
Based on latest CAF kernel sources (LA.AF.1.1.c1)
Compiled with ArchiToolchain 4.9 and several Cortex-A9 optimizations
Overclocking up to 1.62 GHz
Underclocking up to 162 MHz for maximum battery life
User-customizable CPU Voltage driver (thanks to faux123)
Intelliactive and IntelliMinMax CPU governors (thanks to faux123)
In-kernel Thermal Driver (thanks to franciscofranco)
SIO and FIOPS IO schedulers
F2FS (Flash-Friendly File System) support (Performance comparison vs EXT4)
FauxSound support for maximum audio gain control (thanks to faux123)
Latest TWRP recovery, including a Materialised TWRP theme by z31s1g
Be aware that improper usage of kernel features can cause serious damage to your device!
Only use the stuff above if you know what you're doing!
In agreement with the GPL, you can find the sources and defconfig used to compile this kernel right here.
Known Issues:
Please keep in mind that CM12.1 sources are still work in progress. As a result, some features may be broken or only partially working.
That's why I decided to only list device-specific issues below.
Below ~60% battery, the displayed battery level will reduce significantly on rebooting. This is a known issue with all AOSP based ROMs.
After switching to a new battery, I noticed this behavior is related to automatic battery calibration and directly affected by the health of your phone's battery.
Disclaimer:
By downloading and installing this ROM, you agree that I cannot be held responsible for any damage caused to your device while installing or using it. Please keep in mind that it's YOU who chose to do these modifications to your device!
Installation:
Make sure your bootloader is unlocked - if not, follow this guide: Link
First installation? Flash the boot.img from ROM zip via Flashtool (use Fastboot mode!)
Boot into TWRP recovery
Do a factory reset and wipe system partition
Flash latest ROM zip (check "Downloads" section)
Flash suitable GApps for CM12.1 or CM12
Flash latest SuperSU from here: Link
Reboot
Downloads:
Final CM12.1 version: Link (Last updated: Jan 08, 2016)
Final CM12 version: Link (Last updated: April 05, 2015)
CM default su binary: Link (Don't flash if you're using SuperSU!)
Uninstaller zip: Link (Restores default storage permissions)
Credits:
CyanogenMod Team for their active development on the CM12.1 sources.
updateing for helping me with lots of compilation issues and initial bugfixing on Xperia V.
JustArchi for his awesome optimizations!
Changelog:
- 20160108 (final build):
Latest CM12.1 changes
Fixed the lags in power save mode by slightly increasing the cpu clock
.Thanks to everyone for using and supporting my work! It's been a great time with you all!
- 20151115:
Latest CM12.1 changes
Optimized system for better RAM performance
Enabled CM Performance Profiles support
Reduced minimum screen brightness
Reverted Toast UI to AOSP default
Experimental fix for vibrate intensity settings
- 20151010:
Latest CM12.1 changes
Reverted SONY lockscreen clock to AOSP default
Reverted softkeys to AOSP default
Removed Xperia fonts
- 20150929:
Latest CM12.1 changes
Added Xperia softkeys
Fixed missing TWRP boot splash screen
- 20150912:
Latest CM12.1 changes
- 20150824:
Latest CM12.1 changes
Recreated NeoKernel with latest CAF sources from here.
Updated ArchiDroid's Optimizations to V4.1
ROM is now built with SaberMod 4.9 toolchain!
Re-colored recoveryboot LEDs. Got sick of this ugly purple!
Replaced stock TWRP ui with latest Materialised Play theme from here. Credits to z31s1g for the great theme and ElArchibald for his help!
Recoveries present on FOTAkernel will be ignored from now on - fixes installation issues caused by broken CWM or outdated TWRP versions
Disabled Dex-Preoptimization to allow greater and easier customizability, as well as more free space on system partition
Fixed Xposed framework causing bootloops
Fixed GPS for some users (Got rid of QUIPC)
- 20150808:
Latest CM12.1 changes
- 20150726:
Latest CM12.1 changes
Added medium L2 clock rates to NeoKernel, should improve battery life
.NOTE: The device tree used to build this ROM is now fully open-source!
- 20150620:
Latest CM12.1 changes
Fixed delayed PIN screen on boot
Added SONY styled lockscreen clock from here. (Credits to idid idamrep!)
Included all stock Xperia fonts in the ROM
- 20150603:
Latest CM12.1 changes
Enabled Multiuser UI with a maximum of 3 users
Fixed Google Play Services repeatedly force closing
Updated TWRP sources to latest
- 20150516:
Latest CM12.1 changes
Minor fixes and optimizations in device source
- 20150424:
Latest CM12.1 changes
Update to Android 5.1.1
- 20150419:
Latest CM12.1 changes
Added unlimited call log mod from here
Fixed backup issues in TWRP (using updated sources now)
Fixed installation reverting system partition to EXT4
- 20150412:
Latest CM12.1 changes
Reverted updates in F2FS sources (should fix the random bootloops)
Fixed non-working sensors (added prebuilt sensors.msm8960.so)
- 20150405 (CM12.1 build):
Initial release of CM12.1 (Android 5.1)
Merged all kernel features and optimizations from CM12
Updated TWRP to 2.8.6.0
.NOTE: A full wipe is recommended, but not required!
- 20150405 (CM12 build):
Final CM12 build (Android 5.0)
Latest CM12 changes
Added SIO and FIOPS io schedulers
Added in-kernel Thermal Driver (thanks to franciscofranco)
Updated F2FS sources in kernel
Switched to official CM12 libril
Reverted to TWRP 2.8.4.0 to fix some ui bugs
- 20150329:
Latest CM12 changes
Compiled with JustArchi's ArchiDroid Optimizations V4
Updated CAF kernel source
Additional kernel optimizations for Cortex-A9
Disabled debug flags in kernel
Switched to ArchiToolchain 4.9 for kernel
Switched to SaberMod 4.8 toolchain for ROM
Removed USB "Mass Storage" and "Charge only" modes
- 20150321:
Latest CM12 changes
- 20150314:
Latest CM12 changes
- 20150309:
Latest CM12 changes
(Introduces a bug: Clock in statusbar disappears on reboot. Hide/unhide statusbar clock in Settings as a workaround)
Removed FM Radio - Have a look at this one!
- 20150303:
Latest CM12 changes
Fixed the segmentation fault when trying to mount/remount
Most likely fixed the volume errors some people encountered
Reverted to AOSP LLVM compiler (QCOM one needs more work)
Other minor bugfixes
- 20150301:
Latest CM12 changes
Added FM Radio
Replaced AOSP LLVM compiler with Qualcomm one, optimized for krait cpus (thanks to MusterMaxMueller)
ROM is now built with Linaro 4.8 instead of SaberMod 4.8
Kernel is now built with Linaro 4.9 instead of SaberMod 4.10
Updated kernel source to latest CAF
Minor changes and improvements in device tree
- 20150222:
Latest CM12 changes
- 20150215:
Latest CM12 changes
FolderMount and "sd issue" fixed - ROM is now using android default uid for sdcard0
Added intellimm and intelliactive cpu governors (thanks to faux123)
Added ultra low CPU clocks to kernel (162 and 270 MHz)
F2FS (Flash-Friendly File System) support
Latest Faux Sound features
Graphite Loop Optimizations in kernel
O3 optimized GPU drivers
Updated TWRP to version 2.8.5.0
Some changes and cleanup in installer zip
.NOTE: From this version on, you will have to flash my neo-uninstall.zip before switching ROMs!
- 20150207:
Latest CM12 changes
- 20150201:
Latest CM12 changes
Removed CMUpdater
- 20150125:
Latest CM12 changes
No HeadsUp Settings in this version (due to build errors)
- 20150117:
Latest CM12 changes
Merged official CM device repos
Updated TWRP to version 2.8.4.0
Added "Charge only" USB mode
Cherry-picked HeadsUp Settings
Other minor fixes and improvements
- 20150104:
Latest CM12 changes
- 20141228:
Latest CM12 changes
New recovery splash screen, best looking with this Material TWRP theme
Fixed volume key not working when screen off
Minor bugfixes and improvements
- 20141224:
Initial release
If you like my work and want to support me, please hit that thanks button, give some positive feedback or consider a small donation for my efforts.
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Sony Xperia T
Contributors
WhiteNeo
Source Code: https://github.com/WhiteNeo-?tab=repositories
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 12.1
Version Information
Status: No Longer Updated
Created 2014-12-26
Last Updated 2016-01-08
FAQ:
How to update to latest build?
1. Reboot to recovery
2. Flash latest rom zip
3. Flash latest gapps linked in OP
4. Flash SuperSU
5. Wipe Cache & Dalvik Cache
6. Reboot
How to safely uninstall this rom?
1. If you were using F2FS, revert to EXT4 before uninstalling!
2. Reboot to recovery
3. Flash neo-uninstall.zip
4. Proceed with the installation steps of your new rom
Should you face storage issues with your new rom, run the following Terminal commands:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 2800:2800 /mnt/media_rw/sdcard0
chown -R 2800:2800 /mnt/media_rw/sdcard0
Troubleshooting:
I can't create folders in internal storage!
Follow the instructions on updating to latest build. While flashing, my rom will apply its required storage permissions automatically.
Alternatively, you may simply run the following Terminal commands:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
Camera any Gallery won't save my photos!
Follow the instructions on updating to latest build. While flashing, my rom will apply its required storage permissions automatically.
Alternatively, you may simply run the following Terminal commands:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
I can't move apps to sdcard!
Moving apps to internal storage is quite buggy and discouraged. I recommend repartitioning your device with the instructions below.
Advanced Modifications:
Switching to F2FS:
First of all, make sure you're running homebuild version 20150215 or later!
1. Copy all important files from internal storage to the external sdcard
2. Reboot to recovery
3. Do a full backup (make sure to select external sdcard as target location)
4. Disable MTP in "Mount" menu
5. Go to "Wipe" > "Advanced Wipe" menu
6. Check "System", then tap "FS Options" and "Change FS"
7. Select "F2FS", then swipe to apply the change
8. Repeat steps 5 and 6 for "Data" and "Cache" partitions, as well as internal storage
9. Navigate to TWRP Settings and check "Use rm -rf instead of formatting"
10. Restore your previous backup
12. Reboot to system
13. Restore your copied files from external sdcard
14. Reboot
Reverting to EXT4:
1. Copy all important files from internal storage to the external sdcard
2. Reboot to recovery
3. Do a full backup (make sure to select external sdcard as target location)
4. Disable MTP in "Mount" menu
5. Go to "Wipe" > "Advanced Wipe" menu
6. Check "System", then tap "FS Options" and "Change FS"
7. Select "EXT4", then swipe to apply the change
8. Repeat steps 5 and 6 for "Data" and "Cache" partitions, as well as internal storage
9. Navigate to TWRP Settings and check "Use rm -rf instead of formatting"
10. Restore your previous backup
12. Reboot to system
13. Restore your copied files from external sdcard
14. Reboot
Repartitioning your device:
Note:
Up to 14GB of free space on external sdcard might be required to perform the steps below! (Should be less if your internal storage isn't completely bloated )
The value XXXX used below has to be replaced with a calculated number and varies depending on your desired space. I recommend 5120, as it's a decent balance between general data storage (used for most apps) and space on internal storage for apps with bigger data (games). Refer to step 13 of this link if you want to calculate your own partition sizes.
1. Copy all important files from internal storage to the external sdcard with the following terminal command:
Code:
rsync -P -a /sdcard /ext_card/sdcard0/
2. Reboot to recovery
3. Do a full backup (make sure to select external sdcard as target location)
4. Navigate to "Mount" menu, disable MTP and unmount all partitions listed there
5. Navigate to "Advanced" > "Terminal Command" and type the following code:
Code:
parted /dev/block/mmcblk0 print
This command should display some text like this:
Code:
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 2228kB 2097kB TA
2 2228kB 3801kB 1573kB Boot
3 3801kB 5374kB 1573kB Boot2
4 6291kB 27.3MB 21.0MB Kernel
5 27.3MB 28.3MB 1049kB TZ
6 29.4MB 32.5MB 3146kB modemst1
7 33.6MB 36.7MB 3146kB modemst2
8 37.7MB 40.9MB 3146kB fsg
9 40.9MB 46.1MB 5243kB ramdump
10 46.1MB 54.5MB 8389kB ext4 apps_log
11 54.5MB 71.3MB 16.8MB FOTAKernel
12 71.3MB 1359MB 1288MB System
13 1359MB 1621MB 262MB Cache
14 1621MB 3769MB 2147MB Userdata
15 3769MB 15.6GB 11.9GB SDCard
We're going to remove Userdata and SDCard partitions, so check if these partitions also have the numbers 14 and 15 on your phone.
6. Type the following terminal commands to proceed with resizing the partitions:
Code:
parted /dev/block/mmcblk0 rm 14
parted /dev/block/mmcblk0 rm 15
parted /dev/block/mmcblk0 mkpartfs logical ext2 1621 [B]XXXX[/B]
parted /dev/block/mmcblk0 name 14 Userdata
parted /dev/block/mmcblk0 mkpartfs logical ext2 [B]XXXX[/B] 15.6GB
parted /dev/block/mmcblk0 name 15 SDCard
7. Leave the terminal screen and go to "Wipe" > "Advanced Wipe" menu
8. Check "Data", then tap "FS Options" and "Change FS"
9. Select "EXT4" or "F2FS", then swipe to apply the change
10. Repeat steps 8 and 9 for internal storage (is named "sdcard" in this menu)
11. Restore your previous backup
12. Restore your backed-up files from external sdcard with the following terminal command:
Code:
cp -a /external_sd/sdcard0/* /sdcard/
13. Reboot
14. Enter the following terminal commands to fix storage permissions:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
Screenshots:
Video:
Here's another video by taaviu that gives you an impression of Android L.
Loving you right now,as this is a new version of Android, if I am coming from 4.4 KK do I need to flash boot.img before right?
Thanks
moliverac8 said:
Loving you right now,as this is a new version of Android, if I am coming from 4.4 KK do I need to flash boot.img before right?
Thanks
Click to expand...
Click to collapse
Should not be necessary, if you're on 4.4.
Waiting your feedback mate!
WhiteNeo said:
Should not be necessary, if you're on 4.4.
Waiting your feedback mate!
Click to expand...
Click to collapse
Now I am in my village without a working internet until January, sorry, I'll see if I managed to download your ROM somehow, I can't wait!?
Happy New Year!
Yes, At last... I'm downloading and testing this right away i've been waiting for this
bro what can i say..you did it! your the man! thank you so much!! Working like a dream!
Thanks mate
Really, thank you WhiteNeo!
Actually: Why is it in "original Android dev"?
Been running for a few hours and i just want to congratulate you once again!
just one minor thing that im sure you already know but i'll point out ..keyboard gesture isn't working..
That's literally the only thing i have noticed that is not working
LeonardK said:
Really, thank you Neo!
Actually: Why is it in "original Android dev"?
Click to expand...
Click to collapse
Because it's built from sources and so on and so forth.
tajimura said:
Because it's built from sources and so on and so forth.
Click to expand...
Click to collapse
So in this case 'original' means the AOSP sources? I thought it meant sth like 'based on the original (=stock) ROM'.
@WhiteNeo: Is it possible to link the sources?
Found Bugs (CM or device specific?):
- Calculator Button Widget behaves strangely (not the 'big' widget)
- Themes Showcase doesn't change tab (eg. to Wallpapers) and Options makes it crash.
Both theme to be general issues I think
PeterGeorgiou said:
Been running for a few hours and i just want to congratulate you once again!
just one minor thing that im sure you already know but i'll point out ..keyboard gesture isn't working..
That's literally the only thing i have noticed that is not working
Click to expand...
Click to collapse
Keyboard gesture won't work on AOSP because it requires a proprietary lib by Google. You can install Google Keyboard to have the same look with swype
Alternatively, check my XV CM12 thread for the material Xperia keyboard I attached to one of my latest comments.
Thank you very much WhiteNeo. You are giving our phone a new live.
By the way, for people that has tried it yet, what about camera quality? Is it better than 4.4 cyanogen roms?
Google Search Bar
The Search bar sometimes has display issues, that is the icons on it arent displayed anymore.
On my previous post: It should be @WhiteNeo of course, didnt know it would automatically link it
LeonardK said:
The Search bar sometimes has display issues, that is the icons on it arent displayed anymore.
On my previous post: It should be @WhiteNeo of course, didnt know it would automatically link it
Click to expand...
Click to collapse
All of the bugs that have been mentioned so far appear to be sources related, so no need to post them here.
I recommend creating a new issue at https://jira.cyanogenmod.org if you detect any bugs that are obviously not related to our phones' hardware.
Thanks for the build! The ROM is super smooth and bug free for me so far, except maybe the front camera being fuzzy when i tested it. I'm going to try and see how long i can live without xposed. Great work!
Oh wait.. snapshare doesn't work. ****!
I've got a glitch - mobile data is on, but the "H" symbol is gone. Meaning there is no "H". Up-and-down arrows are in place when data is being transmitted, but no "H". Other than that everything's just fine.
WhiteNeo said:
Keyboard gesture won't work on AOSP because it requires a proprietary lib by Google. You can install Google Keyboard to have the same look with swype
Alternatively, check my XV CM12 thread for the material Xperia keyboard I attached to one of my latest comments.
Click to expand...
Click to collapse
Thanks a lot mate loving your Xperia keyboard!
My feedback
Everything works well..
im amazed by this new experience..
Some things i've noticed
- From facing camera stretches the image from camera sometime
- I experienced whistle from speaker while calling, however, i flashed a zip, which fixed it, i will attach the zip file
other than that, everything is working well in my point of view..
i will post more soon if i come across some..
All discussion should go the SuperSU BETA thread
Attached find modified boot.img for the Nexus firmwares released so far. Together with SuperSU v2.50+ these allow root with SELinux in Enforcing mode.
These are the stock boot images from Google, with the ramdisk modified as follows:
- patched sepolicy
- disabled dmverity (if applicable)
- disabled forceencrypt (if applicable)
Rooting procedure:
- flash/upgrade to Marshmellow
- flash modified boot.img
- flash/boot TWRP and sideload latest v2.50+
Acquiring root without modifying the boot images is still under investigation. Please note that the current method will not be officially supported. Future roots may require a clean system: we are at a very early stage of root for 6.0, methods used are subject to change.
For the modders, you can do the sepolicy modifications yourself as follows:
- root a reference device (4.4+ with SELinux enabled) with v2.50+
- extract the sepolicy file from the target boot image's ramdisk
- with the reference device connected to ADB:
Code:
adb push sepolicy /data/local/tmp/sepolicy
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out"
adb shell su -c "chmod 0644 /data/local/tmp/sepolicy_out"
adb pull /data/local/tmp/sepolicy_out sepolicy_out
- replace the sepolicy file in the boot image's ramdisk with the sepolicy_out file
- profit
(this trick should also work on the Samsung 5.1.1 kernels that people are having issues with lately)
Fugu requires v2.51+
EXPERIMENT: Root without modifying /system
EXPERIMENTAL, ARE YOU SURE YOU WANT THIS ?
All discussion should go the SuperSU BETA thread
Idea
To have root on modern Android versions, we need our files to be executable and our daemon to be started on boot. We normally do this by making modifications to /system, tapping into binaries and scripts executed by init. If we're also modifying the boot image, then we should be able to do all this without modifying system at all. A benefit of this is that it makes OTAs easier - reflashing the boot image is less hassle than reflashing system.
As the binaries should still be updatable, and we don't know the space we have available in the boot image itself, we're mounting a (writable) ext4 image with /su as mount point from /data, and modifying PATH accordingly. Interestingly, for reasons yet unknown to me, if the image is mounted r/o by init, later remounting it r/w causes a bunch of issues. So we're keeping it r/w (for root) for now.
An overlayfs/unionfs solution would be even more ideal, transparently placing files in /system without modifying the actual partition, but I have not been able to find one that is (a) compatible with all Android architectures and (b) not kernel dependent and (c) not GPL - or even just one of those requirements, really. It's technically all possible, it just needs to be done.
Caveats
- Apps with hardcoded paths to su (seriously?) will bork
- Factory reset unroots
- Factory reset wipes pin
- ...
- Bugs... Bugs everywhere!
Instructions
You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with eachother. The installer for this experiment will not clean up old root files.
- Flash stock /system (and /vendor and /oem, if present)
- Flash the attached boot image
- Flash the attached SuperSU ZIP in TWRP
Ramdisk modifications
- include (post above this one)
- init.rc (devs: please open file for reference)
--- on init
------ mkdir /su ...
--- on post-fs-data
------ copy image from cache to data (for rooting without access to /data in custom recovery)
------ mount image to /su
--- service daemonsu
- init.environ.rc
--- export PATH, prepended with /su/bin
- file_contexts
--- /su(/.*)? ubject_r:system_file:s0
NOTE
- Not all SuperSU options are supported yet in this mode
- I have not tested with encrypted devices
- /system should never be remounted r/w, I hope I didn't miss anything here
- Root with modifying /system is also still operational. I can't predict what the exploiters will need.
- I'm not sure where we're going with this. Future roots may require a clean system.
BETA-SuperSU-v2.56-20151030013730.zip
Changes
(The changelogs for the specific SuperSU versions can be found here: http://forum.xda-developers.com/showpost.php?p=23427824&postcount=3)
2016.01.21
- v2.67 ZIP
2016.01.03
- v2.66 ZIP
2015.12.26
- v2.65 ZIP
2015.12.20
- v2.64 ZIP
2015.12.11
- v2.62-3 ZIP:
--- (systemless) ZIP: Fix calling wrong script name for custom patcher script
--- (systemless) ZIP: Improve APK overwrite
--- (systemless) ZIP: Do not move backups from /cache to /data, just copy them
(there are no changes to SuperSU itself compared to v2.62, just minor script changes in the ZIP)
2015.12.10
- v2.62 ZIP
2015.12.07
- v2.61 ZIP
2015.12.05
- v2.60 ZIP with automated boot image patcher
2015.10.30 #2
- Added systemless root experiment for other Nexus than hammerhead
2015.10.30
- Added systemless root experiment for hammerhead
2015.10.28
- Added Angler kernel
- Added Razor mra58u kernel
2015.10.20
- Added Bullhead kernel
2015.10.08
- New image for Fugu, requires v2.51
2015.10.07
- New images, should fix the factory reset issues some users with encrypted data were seeing
EXPERIMENT: Root without modifying /system #2: Automation
EXPERIMENTAL, ARE YOU SURE YOU WANT THIS ?
All discussion should go the SuperSU BETA thread
Continuing on the previous post, here is SuperSU v2.62 BETA, with automated boot image patching. It's been tested by myself on various Samsung's running anything from 4.3 to 5.1, and all of the recent Nexus devices on 6.0. Even on CM13. Other users have tested it with success on various other devices.
If you are coming from any SuperSU install in /system, you must re-flash the stock system (and vendor and oem, if present) partition contents prior to installing this.
If you are coming from a SuperSU 2.56 system-less install, you must re-flash the stock boot image prior to installing this.
If you are coming from a SuperSU 2.60 system-less install, or were not rooted at all, then you can just flash the ZIP without any special prior instructions.
If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
If on Android 6.0 or Samsung 5.1, the ZIP installer will install SuperSU in systemless mode and patch the boot image. The boot image patcher currently only supports gzip compressed ramdisks and the standard Android boot image format. Some devices do not use the standard format, and many custom kernels use a compression other than gzip. A backup is made (/data/stock_boot_<sha>.img.gz) of the original boot image before patching it.
Further implementation details (including an updated list of changes to the ramdisk) are explained in the installer script itself, as usual.
Notes on 2.62+
A poor man's overlay is used on /system/xbin. We are creating a copy of /system/xbin in /su/xbin_bind, adding a symlink to /su/bin/su there, then mounting the entire thing on top of the original /system/xbin. This is likely to fix some compatibility issues with some apps, without actually modifying /system. Removing /su/xbin_bind and rebooting will disable this feature, or "echo BINDSYSTEMXBIN=false>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash.
If you have one of those devices that refuse to remount system r/w in Android such as the Nexus 6P, but you do want to do this, "echo FSTABSYSTEMRW=true>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash will patch the boot image in such a way that remounting will work. This feature itself breaks OTA compatibility, regardless of if you end up writing to /system or not.
Both of these features are likely temporary.
Notes on 2.64+
There have been a lot of changes to the ZIP installer. Hopefully they won't break a lot of installs. If 2.64 works well, it is likely to be promoted to the "main beta" in place of 2.52, and the How-To SU document will be updated with the relevant information.
A major change in setup is that the ZIP installer will try to detect 6.0 firmwares that can be rooted without doing a systemless install. In other words, a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu").
This may catch (a) firmwares that allow sepolicy reloading from /data but have a locked bootloader and (b) custom firmwares setup to handle this. Regarding the latter, while it is not as clean as systemless, those running custom firmwares are more likely to want to modify /system anyway, it is less likely to mess with updates to those firmwares, and it prevents the necessity of reflashing the ZIP after each kernel switch. Of course, the kernel's SELinux policies must support this! See this thread for details for devs.
Notes on 2.65+
As 2.65 adds /su/xbin, I recommend flashing the ZIP rather than installing the APK from the ZIP, as some people tend to do.
Notes on 2.67+
I recommend flashing the ZIP rather than installing the APK from the ZIP, as some people tend to do.
Downloads
BETA-SuperSU-v2.60-20151205163135.zip
BETA-SuperSU-v2.61-20151207213702.zip
BETA-SuperSU-v2.62-20151210170034.zip
BETA-SuperSU-v2.62-2-20151211155442.zip
BETA-SuperSU-v2.62-3-20151211162651.zip
BETA-SuperSU-v2.64-20151220185127.zip
BETA-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.66-20160103015024.zip
BETA-SuperSU-v2.67-20160121175247.zip
The latest WIP version has become the main BETA version.
For all intents and purposes, this thread is closed. It will be cleaned up and unstickied in good time.
Team Win Recovery Project 3.x, or twrp3 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.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
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.
TWRP is fully open source, port / compile TWRP for your device today!.
Build in CM-13.0 environment w/TWRP source forked : @mdmower
Fork of TWRP
This fork differs from the original in the following ways:
Designed to be built with CyanogenMod 13.0 only
Require fstab v2 syntax (see examples and supported flags below)
Use external repositories for pigz, exfat, fuse
Power key toggles screen on/off
Remove the need to specify either DEVICE_RESOLUTION or TW_THEME so long as TARGET_SCREEN_HEIGHT and TARGET_SCREEN_WIDTH are set
Other minor customizations (see change history)
Versioning
To help distinguish builds of recovery made from this fork, the minor version digit is replaced with M#. Minor version increments will be handled as needed, independent of TWRP. The major and semi-major version digits follow upstream to roughly indicate feature parity (as close as possible with a fork, anyways).
Convention:
3.0.M0-0 incorporates all major features from TWRP 3.0.0-0
3.0.M1-0 is the minor version increment after 3.0.M0-0 and is independent of any TWRP minor version increment(s)
3.1.M0-0 is the semi-major version increment after 3.0.M4-2 and is tied to a TWRP semi-major version increment
3.0.M0-1 is a device-specific fix to 3.0.M0-0; this device digit resets when any other version increments
maintained rework by : @artefvck
DOWNLOADS:
Fastboot Mode
Flashable Zip
source
Convert ext4 partition to F2FS partition without loosing data
Preface
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel.
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Prerequisites
PC with ADB installed for SD backups
F2FS compatible ROM
F2FS compatible Kernel
F2FS compatible TWRP Recovery (this recovery has F2FS support, too)
sdcard Fix Permissions script (scroll down a little bit)
Procedure
Flash the F2FS compatible TWRP Recovery with fastboot or other recovery for example
Boot into Recovery
Backup > Data
Save your internal SD card with one of the following options
Either reboot to system and copy files to your PC via USB (MTP)
Or pull files via adb (adb pull /data/media sd_backup)
Copy the kernel and the sdcard fix script to your created backup folder
Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS
Wipe > Advanced Wipe > Cache > Repair or Change File System > Change File System > F2FS
Copy the saved SD card content back to your device with: adb push sd_backup /data/media/0/
Afterwards the folder structure should look like this: /data/media/0/…Folders like DCIM, Music, Downloads, …
You can check with: adb shell ls -R /data/media
Restore > Choose backup > Data (the warning about ext4 backup doesn’t matter)
Advanced > Fix Permissions
Flash the sdcard Fix Permissions script with: Install > Choose sdcard fix zip
Wipe > Advanced Wipe > Cache & Dalvik Cache
Flash a F2FS compatible kernel with: Install > Choose kernel zip
Reboot to system
Now your Android device should fly again ��
Note:
In my mind it doesn’t make much sense to format/system to F2FS because you would need a modified ROM to use it. Everytime you update your ROM you would have to modify it to use /system as F2FS. On top of that there shouldn’t be a real performance gain with a F2FS /system partition because it’s read-only. And reading operations are fast with ext4, too. The difference is non-existent or very low. In my humble opinion the so called All-F2FS is pretty useless.
You can format your /data and /cache partition to F2FS. Normally you’ll loose all data in this process and have to reinstall everything. But this small howto will show you how to recover your data so you can continue where you left off. Just like a “dirty” ROM flash.
Good.
oh gee nice that you make update for TWRP 3.0 but is it fixes nandroid backup ?
Because I had this error that make me regret it it's called ( extractTarFork() process ended with ERROR: 255 ) and it's from your TWRP 3.0 M-1 ( if i'm not mistaken ) it's a nandroid backup of stock rom when I want to try the custom ROM
and Keep Up The Good Work yes ?
Regards
Awesome0ne ?
Sent from my ASUS_T00F using Tapatalk
RevanEphys said:
oh gee nice that you make update for TWRP 3.0 but is it fixes nandroid backup ?
Because I had this error that make me regret it it's called ( extractTarFork() process ended with ERROR: 255 ) and it's from your TWRP 3.0 M-1 ( if i'm not mistaken ) it's a nandroid backup of stock rom when I want to try the custom ROM
and Keep Up The Good Work yes ?
Regards
Click to expand...
Click to collapse
latest build fixed
try twrp 3.0.M-2.0
X AnwarMov said:
latest build fixed
try twrp 3.0.M-2.0
Click to expand...
Click to collapse
You Mean TWRP 3.0.2 ? I will try that later when all CM 13 or Android 6.0 ROM quite stable enough ( even though it will still has bugs )
Thanks
RevanEphys said:
You Mean TWRP 3.0.2 ? I will try that later when all CM 13 or Android 6.0 ROM quite stable enough ( even though it will still has bugs )
Thanks
Click to expand...
Click to collapse
please report to your Rom development .
this thread i think can't have problem
Hi,
Instalation is for flash or fastboot?
Good joob
marceloz5 said:
Hi,
Instalation is for flash or fastboot?
Good joob
Click to expand...
Click to collapse
oh yeah fastboot for now ,
latest build i can upload flashable.zip for more easly
thanks
i only get white screen after flashing wonder y
Nice ?
Sent from my ASUS_T00F using XDA-Developers mobile app
X AnwarMov said:
Build in CM-13.0 environment w/TWRP source forked : @mdmower
Fork of TWRP
This fork differs from the original in the following ways:
Designed to be built with CyanogenMod 13.0 only
Require fstab v2 syntax (see examples and supported flags below)
Use external repositories for pigz, exfat, fuse
Power key toggles screen on/off
Remove the need to specify either DEVICE_RESOLUTION or TW_THEME so long as TARGET_SCREEN_HEIGHT and TARGET_SCREEN_WIDTH are set
Other minor customizations (see change history)
Versioning
To help distinguish builds of recovery made from this fork, the minor version digit is replaced with M#. Minor version increments will be handled as needed, independent of TWRP. The major and semi-major version digits follow upstream to roughly indicate feature parity (as close as possible with a fork, anyways).
Convention:
3.0.M0-0 incorporates all major features from TWRP 3.0.0-0
3.0.M1-0 is the minor version increment after 3.0.M0-0 and is independent of any TWRP minor version increment(s)
3.1.M0-0 is the semi-major version increment after 3.0.M4-2 and is tied to a TWRP semi-major version increment
3.0.M0-1 is a device-specific fix to 3.0.M0-0; this device digit resets when any other version increments
maintained rework by : [MENTION=4258433]artefvck
- add new touchscreen synaptics driver / update
- built-in modules
- F2FS partitions
- kernel version v3.10.20
DOWNLOADS:
FOLDER UPLOAD
source :
Device tree
Kernel
Click to expand...
Click to collapse
Thanks for this...no lags whatsoever except when booting to twrp and when booting to system... keep up the good work
can install on cm 12.1?
emirfahimi said:
can install on cm 12.1?
Click to expand...
Click to collapse
Yeah.
tank0412 said:
Yeah.
Click to expand...
Click to collapse
but here you said cm 13 "only"
I've tried both 3.0.M-1.0 and 3.0M-2.0.
They are quite lag on my Zenfone 5 when compare with 2.8.7.0
For example, it takes 10-20 seconds to go into recovery and several second before it reboot.
When i tried backup rom twrp suddenly restart and back to first screen twrp again, i tried twice but the problem still persist
abw_bw said:
When i tried backup rom twrp suddenly restart and back to first screen twrp again, i tried twice but the problem still persist
Click to expand...
Click to collapse
When I try to backup System, Data, Config, and System Image, my phone turns off when the backup nearly completed. and ends up with Usb Logo. :silly:
baszu said:
I've tried both 3.0.M-1.0 and 3.0M-2.0.
They are quite lag on my Zenfone 5 when compare with 2.8.7.0
For example, it takes 10-20 seconds to go into recovery and several second before it reboot.
Click to expand...
Click to collapse
i faced this to.
Sent from my ASUS_T00F using XDA-Developers mobile app