Related
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
HTC One GSM Unified (m7)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Notice: m7ul, m7att and m7tmo variants are no longer updated. Use the new unified m7
Click to expand...
Click to collapse
Removed warnings as it works on both HTC One GSM and Sprint
Sent from my GT-I9100 using Tapatalk 2
Released v5.08.5
Change list 5.07.1 ---> 5.08.5
5.08.5 (11.07.2013)
- Compile Aroma File Manager (by amarullz) zip installer under recovery:
* either compile whole recovery, zip will be created at first pass
* or only compile aroma zip installer in two pass:
1- mmm bootable/recovery/aromafm
2- mmm bootable/recovery/aromafm/tools
* output: [target_out]/aromafm_out/aromafm_[DeviceID].zip
- detect aroma compatibility with non NEON devices during compiling
- use less conflicting flags: TARGET_NAME --> TARGET_COMMON_NAME
5.08.0 (07.07.2013)
- improve nandroid progress bar update
- fix recovery was not prompting when backup estimated size is larger than free space
- add ors backup support for twrp format requested by BillGoss
- ors backup: when no backup name is given, generate it using same way as nandroid operations (time stamp + rom name tag)
- support separated compiling for Loki patched devices (S4 AT&T and Verizon)
- i9505: revert some changes to fix time bug for some users
- Galaxy S4 US variants: repack around Audism stock JB 4.3 kernel v3 + Samsung exfat modules + revert use of mkefs for partition corruption issue
- fix missing break in set backup compression value menu (misc_nandroid_menu())
- misc clean up code
- sync latest sources
5.07.6 (05.07.2013)
- update version 6.0.3.3
- add exfat-fuse 1.0.1.362 / 2.9.2 optional support by enabling USE_EXFAT_FUSE_BIN CFLAG in BoardConfig (exfat support on cyanogenmod repacks)
- i9505: use Audism kernel v3 (Stock Samsung sources) to fix partition corruption without additional code and for better exfat support
Click to expand...
Click to collapse
Please Note: Device specific threads will no longer be updated. I monitor them for support and feedback though
To check if you have a new version, subscribe to main thread:
http://forum.xda-developers.com/showthread.php?t=2201860
Thank you for your understanding
Update 6.13.1
- fix charger bug
Refresh goo in a while if it doesn't show
Update 6.19.6
Fix charger
6.26.6
Last version can be found here:
HTC One GSM Unified (m7)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Notice: m7ul, m7att and m7tmo variants are no longer updated. Use the new unified m7
Click to expand...
Click to collapse
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:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
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!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
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
Device page on our website
Download links:
Mirror 1
Mirror 2
Hi Dees Troy
This is the official TWRP ? Good job ! & Thanks
Dees_Troy said:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
Click to expand...
Click to collapse
I tried this option, and it says, "NOT SUPPORTED" (sm-g900t)
Delete
Sent from my SM-G900T using Tapatalk
Great Work,
I tried your recovery on my SM-G900F. i have an encrypted device. when rebooting to the recovery the device doesn't ask for a password. so it isn't possible for me to mount /data. normally i would copy a log to sd but only the externalsd can be mounted.
do you have some ideas to solve this?
el7145 said:
I tried this option, and it says, "NOT SUPPORTED" (sm-g900t)
Click to expand...
Click to collapse
Same here.
Works with odin. Thanks.
does this work for the 900p Sprint version???
Thanks
When I would use this:
3) Hit Advanced->Install Recovery
"TWRP Manager stops" pops up.
Great work guys!
I cannot install the recovery from within the app either, assume there are website issues.
A polite suggestion, I have paid to remove the adds as well as for the Live Backup. Would it be too much to ask to have a direct link within the app to download and flash the latest recovery rather than being re-directed to a download site etc...
Just a thought.
Flashed with flashify worked good on tmobile
Sent from my SM-G900T using Tapatalk
flashed .img with flashify
working good. on SM-G900F
date time does not stick
taking first backup on ExtSdCard but taking longer than usual.
Good work though...
casonswag said:
Flashed with flashify worked good on tmobile
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Thanks For the info, worked like a charm using flashify.
Twrp working great on g900t, Thanks!
Side question, why are backups so darn huge? (3gb)
Im coming from a HTC one s, and those backups barely pushed 1gb using twrp
el7145 said:
Thanks For the info, worked like a charm using flashing.
Twrp working great on g900t, Thanks!
Side question, why are backups so darn huge? (3gb)
Im coming from a HTC one s, and those backups barely pushed 1gb using twrp
Click to expand...
Click to collapse
Its cause its stock rom its heavy as hell plus tw on top of that and userdata packs on alot too itll be smaller once aosp comes out for our phone
Sent from my SM-G900T using Tapatalk
Does this work on the Sprint variant? TWRP manager says NOT SUPPORTED.
Sprint - Galaxy S5 - Moto X - Nexus 7 LTE
Any workaround for date and time.
Is this supported on att (900a9
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
zgroten said:
Does this work on the Sprint variant? TWRP manager says NOT SUPPORTED.
Sprint - Galaxy S5 - Moto X - Nexus 7 LTE
Click to expand...
Click to collapse
Yes - it works on my SM-G900P
After flasing, I lose the lte on my SM-G900F.
I try to reflash my old recovery, kernel and radio but I still have the problem...
How can I do ?
Hi all, I'm going to complete this message later, but for now only fresh links with a bit of comments:
EMMC LAYOUT: D/L: [email protected]
CN+/ROW+ == extended BOOT and RECOVERY partitions up to 16mb (stock are 6mb) allow to flash TWRP 3.0.0-0+ (use with stock FT roms - overwrite)
cn+v*-8gb.zip
cn+v*-4gb.zip
row+v*-8gb.zip
row+v*5-4gb.zip
MOVING TO CN+/ROW+ HOWTO:
0) Download SP_Flash_Tools_v5.1352.01
1) Take a ROM for FLASHTOOL (CN for CN+, ROW for ROW+)
2) Replace all files from layout zip
3) Run FT, load scatter
4) Make sure lk.bin is selected for UBOOT!
5) Make sure you've selected twrp recovery.img for RECOVERY
6) Flash in firmare upgrade mode (press reset button and connect the phone)
7) Boot to recovery and format /system (not required if /system size is the same in selected rom and new layout)
8) flash your favorite rom.zip in recovery (it should not contain uboot.img, or replace it with lk.bin from layout zip)
RECOVERY: D/L: [email protected]
2.8.4.0: for stock ROW and CN layout:
openrecovery-twrp-2.8.4.0rev2-p780cn.zip
openrecovery-twrp-2.8.4.0rev2-p780row.zip
3.0.2-1: only for CN+/ROW+ layout
+ new theme!
+ With full F2FS support
recovery-twrp-3.0.2-1-p780cn+.img
recovery-twrp-3.0.2-1-p780row+.img
Bindu Kernel (CUSTOM KK KERNELS): D/L: [email protected]
Current version: 1.3.3
Supported devices:
[EXTRA] Lenovo P780
[STABLE] Lenovo S820/S920/A820/A830
[STABLE] Xolo Q1000, Explay HD Quad, BQ Aquarius 5 HD
[STABLE] Highscreen Alpha Rage
[WIP] Xolo Q800, Fly IQ446
[WIP] Micromax A116
Features:
* [1.3.0] updated kernel sources to 3.4.111
+ [1.3.0] added dynamic fsync
+ [1.3.0] merged PROTON kernel overclocking features (not working for all devices)
+ [1.2.6] fixed LED going down when deep sleeping
* built with UBERTC 6.0 toolchain & optimizations enabled
* added KSM
* removed a lot of debugging stuff
* added i/o schedulers: zen, sioplus, tripndroid, bfq, row (default: sio)
* packed with LZ4 (only for CN+/ROW+ !!!!!!!!!!!!!!!!!!! should not be flashed to CN/ROW - you'll brick the phone or loose recovery)
* [1.1] added F2FS support
* no color flashing on some stock kernels (with newlcm)
* native exfat support
* working hall sensor on custom roms (use "echo 1 > /sys/hall/legacy_mode")
* added some i/o shchedulers
* correct working 3-button wired headsets
* LED working on custom roms
* added support for some USB/OTG devices, incuding CDC NDIS adapters
* newest china phones (07/2014+) camera supported
* ...
Use attached Kernel Injector tool for easy boot.img repacking for your rom.
CUSTOM VOLD: D/L: [email protected]
for stock roms
+ exfat support for SD card
+ exfat, ntfs, ext4 support for OTG
avold-cn-b01.zip
avold-row-b01.zip
DumcharMarkupInfo: the application shows your current EMMC layout (markup) and memory info.
andreya108 said:
Hi all, I'm going to complete this message later, but for now only fresh links with a bit of comments:
EMMC LAYOUT: ROW+ == extended BOOT and RECOVERY partitions up to 16mb (stock are 6mb) allow to flash TWRP 2.8.6.0 (use with stock FT roms - overwrite)
row+v4-8gb.zip
row+v4-4gb.zip
RECOVERY:
2.8.4.0: for stock ROW and CN layout:
openrecovery-twrp-2.8.4.0rev2-p780cn.zip
openrecovery-twrp-2.8.4.0rev2-p780row.zip
2.8.6.0: only for ROW+ layout
openrecovery-twrp-2.8.6.0rev4-p780row+.zip
CUSTOM KERNELS: https://yadi.sk/d/kw1GANTch6o2N
* no color flashing on some stock kernels (with newlcm)
* native exfat support
* working hall sensor on custom roms (use "echo 1 > /sys/hall/legacy_mode")
* added some i/o shchedulers
* correct working 3-button wired headsets
* LED working on custom roms
* added support for some USB/OTG devices, incuding CDC NDIS adapters
* ...
CUSTOM VOLD: for stock roms
+ exfat support for SD card
+ exfat, ntfs, ext4 support for OTG
avold-cn-b01.zip
avold-row-b01.zip
Downloads: https://yadi.sk/d/99hmGTxUgvxbL
Click to expand...
Click to collapse
Thank you.
Sent from my Lenovo P780
THANKS
---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------
Custom Kernel for all the P780 roms???
@andreya108, thanq for your good work. and posting the recoveries and kernels here also. it might be helpful for so many p780 users.
is your kernel can be used in both JB and KK?. b'coz of network signal issues and fast battery drain in KK i switched back to stock JB. will your new kernel solve this two issues in KK. not only for me, i had seen so many unhappy KK users with these two issues .
The kernel is only for KK. Any roms. But one should repack boot.img, only a few provided (stock + miui 5.5.29 + cm11)
Different versions for ROW and China EMMC layout.
Do you know if I can use kernel on Nexus 5 2.2. CN (link)? Asking because I see this ROM there, but ROW, so maybe you have tried? If yes, which of them should I choose (1507, cm11 or miui). Interested because of 3 headset buttons (out of which only 1 works currently).
EDIT: Ok, I read in your post above that I need to repack it somehow. So for now I'll pass. If it's not very complicated process and someone would be willing to describe it, I'll be very grateful.
EDIT2: I see that you are the author of the ROM that's in the files. Didn't know that. Sorry and thank you for providing the fruits of your work to us
jukooz said:
EDIT: Ok, I read in your post above that I need to repack it somehow. So for now I'll pass. If it's not very complicated process and someone would be willing to describe it, I'll be very grateful.
Click to expand...
Click to collapse
Check Kernel Injector tool, I've updated the first post.
Hello!
I have big problem with your kernel. Now I have CM11 beta2 with "boot-cm11-ak-prada.rc8-stocklcm.build191 #2". GPS isn't working. Earlier I had Alice Project v8.4 with your kernel rc5 and still the same problem - GPS isn't working. What should I do? Is any option for efficient GPS on your kernel?
Thanks!
Currently I cannot answer definitely. There are a lot of problems with CM itself, so it cannot be used as everyday rom. Battery drain is awful.
But on Alice Project v8.4 + "boot-1507-ak-prada.rc5-newlcm.build176.zip" is still the same problem. GPS isn't working. Is it possible to have working GPS on your kernel?
Have you repacked the boot with your ramdisk?
http://4pda.ru/forum/index.php?showtopic=576986&st=7660#entry4053
There are the instructions about repacking
Updated kernels (including Lenovo S920, Lenovo S820), twrp and layouts.
andreya108 said:
Updated kernels (including Lenovo S920, Lenovo S820), twrp and layouts.
Click to expand...
Click to collapse
thanks for your good work. any changelogs available for the new releases.
what's the difference between lz4 stocklcm and stocklcm?.
Changelogs only in Russian @4pda.ru for now, sorry.
lz4 - kernel packed with LZ4, not XZ. So, it is larger (only fits in + layout) but has less loading time.
Please give guide to change layout...
How to shift from row to row+, using recovery (if possible)
Soft bricked, reflashed. Lost. The instructions are not quite clear to me. Am I supposed to flash the files in the emmc zip folder via PT and then install the recovery img via recovery flash? If yes can someone tell me a good ROM to install the files with that will work with the 8 gig row version?
I switched it by downloading firmware for flash tool and extracting the files from this thread to the directory with this firmware, then in flashtool you have to set format partitions and download.
AND BEFORE FLASHING YOU MUST BACKUP YOUR IMEI - otherwise it will be deleted. I used mobile uncle tools for this - backup it to your external sd card - the internal sd will be deleted in this process
Sent from my BN NookHD+ using Tapatalk
dkuku said:
I switched it by downloading firmware for flash tool and extracting the files from this thread to the directory with this firmware, then in flashtool you have to set format partitions and download.
AND BEFORE FLASHING YOU MUST BACKUP YOUR IMEI - otherwise it will be deleted. I used mobile uncle tools for this - backup it to your external sd card - the internal sd will be deleted in this process
Sent from my BN NookHD+ using Tapatalk
Click to expand...
Click to collapse
Thanks. And the recovery? It seems it's a flashable zip. Should I flash it from the recovery?
I unpacked the recovery to the same folder as the firmware and also flashed it from flashtool. After flashing lenovo firmware you will have stock recovery so then you need to root your phone etc. This is the fastest option.
Sent from my P780 using Tapatalk
What it is
It is a self twrp build from the official 3.0.2-0 git sources on a omnirom tree with data decryption support. Also some flags are tuned to enable booting for newbootloaders (> 15.4)
This recovery is fully working for my sony xperia z3 (D6603) since september 2015. I give it 'as it is'.
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Who can use it
it is only for z3 and unlocked bootloaders. It should work with
- phone where the sony TA update patch is appliedor
- all AOSP based rom which support FOTAKernel recoveries extraction (extract_elf_ramdisk), ask your rom maintainer.Since 2017-03-16 release this recovery use apps_logs partition as a workaround for N based roms, this will break stock roms!
LeonidasTurk said:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader it partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by a xda member, he developed utility extract_elf_ramdisk https://github.com/Dees-Troy/extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery!
Click to expand...
Click to collapse
Actually it had been tested with CyanogenMod, and SlimRom as I know.
(tested only on D6603 version but should work on D6602,D6643,D6653) let me know if it work for you
The bootloader/reboot pain
From my experience there is 3 versions of the s1 bootloader for D66x3:
s1 D66x3 features:
LA3.0_L_15.4 : provide basic boot functionality, you can only boot in your boot partition.
LA3.0_L_37 : provide normal boot & recovery boot functonality (boot partition & FOTAKernel partition) but doesn't provide reboot to recovery functionality.
LA3.0_L_Hero_17 : (not yet tested): same as l_37 but correct the reboot in recovery bug.s1 D66x3 installation:
LA3.0_L_15.4 : is preinstalled. (.200 and above)
LA3.0_L_37 : is installed with M (.575)
LA3.0_L_Hero_17 : is installed with N preview (.?)Some roms flash other version of s1 that i never test (i only upgrade my bootloader with emma)
Check the s1 version:
Code:
getprop ro.boot.s1boot
What is working
Everything =)
backups
backups on encrypted partitions
restore
restore on encrypted partitions
all settings
change partitions type (f2fs/ext4)
flash zip
reboot
phone doesn't overheat and battery consumption is reasonable
/data decrypt
accessing recovery with new bootloader version (S1_Boot_MSM8974AC_LA3.0_L_37)
Brightness
usb otg
f2fs partition decryption
What is not working
wipe data buton (workaround by format, change type) --> should be ok since 2016-07-14 release.
reboot to recovery. I'm looking for documentation on new bootloader... --> workaround in progress --> should be ok for kernel with extract_elf_ramdisk
with old bootloader (< 15.4: check your cmdline) --> in progress --> should be ok for kernel with extract_elf_ramdisk. Let me know
What is not tested
f2fs partition decryption --> ok on 2016-07-16
what I forget, ask and I test asap
ToDo
create a zip to update this recovery --> re self signed zip since 2015-12-26 builds
change the 'power profile' in use when in recovery mode --> governor changed to 'ondemand' (2015-12-19)
create a VM for weekly builds --> done with jenkins (2016-02-17)
create a folder on webserver for weekly build --> Url will come soon (2016-02-17)
publish my files on a VCS --> https://github.com/nailyk-fr
update my blog to make a full (french) compiling guide -> ENOTIME. Ask here if you need.
make recovery functional for the 'full boot' process released by sony --> ok since 2016-01-09 builds
How to build
Follow the official twrp compiling guide (I start from omnirom tree),
If you are building from omni trees you do not need to change something as device have now official support.
breakfast z3
mka recoveryimage
wait a half hour and it's done
Reading CyanogenMod porting guide was very helpful.
2017-03-17: change manifest
2016-11-05: change manifest
2016-04-14: added the manifest repo url.
2016-03-07: update manifest.xml
2016-02-14: update manifest.xml
2016-02-07: switch to omnirom build tree (except kernel due to f2fs). Manifest is no more up-to-date
2016-01-15: change manifest to include z1&z1c
2016-01-13: add github fork links
2016-01-09: new twrp.fstab
2016-01-07: add patch link for the device/sony/shinano-common
2015-12-26: twrp.fstab & BoardConfigCommon.mk are no more up-to-date. I need to publish it on a public VCS but for now it's q&d. When job is done in a cleaner way a publish all the sources. If you need/want it before ask me and a provide a zip.
How to install
With a first rom installation with extract_elf_ramdisk support:
Ex: Coming from stock rom and installing CyanogenMod:
Follow the cm installation guide, and replace step 4 by:
download and check md5/sha1,
flash cyanogenmod kernel with:
Code:
fastboot flash boot boot.img
flash recovery by using command:
Code:
fastboot flash FOTAKernel <filename>
then reboot with
Code:
fastboot reboot
You can now continue the cm installation guide.
Via fastboot:
download and check md5/sha1,
reboot your phone in fastboot mode,
flash recovery by using command:
Code:
fastboot flash FOTAKernel <filename>
or
Code:
fastboot flash recovery <filename>
Via zip:
You need a custom recovery (like twrp/cwm) supporting flashing zip files,
Download zip to your internal/external sd,
Check md5/sha1,
Reboot to recovery,
flash zip.
Thanks to
@shoey63
@optimumpro
@_infected
@Micha_Btz
@frabe8378910
Team Win
Version Information
Created: 2015-12-18
Last Updated: 2018-03-28
Status: Work in progress --> stable (since 2016-07-16 build)
It's a self build version of twrp. I follow the official twrp compiling guide and add files for z3 (D6603 version in this case) and some 'compiling tricks' to add keymaster/keystore support in recovery to finally support encrypted /data partitions.
( From @LeonidasTurk's kernel thread, this build should work with other models but it not tested! Use it at your own risk, unlocked bootloaders only obviously)
official twrp compiling guide: http://forum.xda-developers.com/showthread.php?t=1943625
official CynogenMod z3 (D6603) thread: http://forum.xda-developers.com/z3/development/rom-cyanogenmod-12-nightlies-xperia-z3-t3010201
I'm not affiliated to TeamWin or CyanogenMod.
Report a problem link
Releases
Before flashing, read carefully the 'Who can use it' part and 'How to install'. If you are unsure, feel free to ask.
2018-03-28 single/unified:
FOTAKernel/recovery binary:
md5: 24cb9f0f64b2d62ef7798957932cc918
sha1: dd61d3f145f25a22b9f4eb9a6c0ec7a6eb92af0e
download mirror (fr)
Changelog
[*] Old boot process is broken. Will only works with new bootloader (See OP top)
Fix Oreo encryption. Need working /system!
[*] Warning this recovery cannot be used with stock roms as it use /misc for rom/recovery communication.
Old releases:
2017-10-02 Single:
FOTAKernel/recovery binary:
md5: 0b4ffccf31e201006937717a98bc8849
sha1: a755e659b4f96b2106b99c310042b8a29475266c
download[/INDENT]
Changelog
Codename fix
[*] Warning this recovery cannot be used with stock roms as it use /misc for rom/recovery communication.
2017-09-28 Single:
FOTAKernel/recovery binary:
md5: c8a004a1aa6a8abd8e85f010fce04f44
sha1: 375f3e48fbdf960970a795436e1b404d9d228fc2
download[/INDENT]
Changelog
Lots of improvement (twrp side)
Lots of changes on trees
adb backups are broken for now, don't use them!
Adjusted functionalities for our device
[*] Warning this recovery cannot be used with stock roms as it use /misc for rom/recovery communication.
2017-07-27 Single:
FOTAKernel/recovery binary:
md5: ad3279f0f4e761c193f2c1296789ac98
downloadflashable zip:
md5: 8acf3ea839ecd11f971032e292be7a8a
download
2017-07-27 Dual:
FOTAKernel/recovery binary:
md5: 7dea87dd9ab920931a769632dc054620
downloadflashable zip:
md5: e4aa892b4fbd2510eeb4e7f6dba8d7e5
download
Changelog
Don't remember
[*] Warning this recovery cannot be used with stock roms as it use /misc for rom/recovery communication.
2017-03-17:
FOTAKernel/recovery binary:
md5: 3f853b388621f60b57d6a56cbf91b8ed
sha1:
downloadflashable zip:
md5: f5984afeb6dc1f2b4bed570950b67445
sha1:
download
Switch back to 3.4 kernel (LineageOS 14.1)
Resolve some apps_logs partition problem
[*] Some functionality are not working (twrp related)
[*] Warning this recovery will break stock roms as it use /misc for rom/recovery communication.
2016-12-23:
FOTAKernel/recovery binary:
md5: b083f6c9594df72497fd647e5cef41c7
sha1: 0d83215e473d89f4586b9bd4ce408cafccf12782
downloadflashable zip:
md5: 7c20318900825eb6e7b814bc433d6c1c
sha1: 75d9e650811b4067b2d8beac26b6e11faca8d3ac
download
Switch to 3.10 1.3.3 (if you experienced problem use the 2016-10-17 version and report with log please)
Add app_log to fstab
2016-10-17:
FOTAKernel/recovery binary:
md5: 5926dcd958da084bb7d67e6f8279bc2c
sha1: x
downloadflashable zip:
md5: ba7abccc3a36dd2ad843b671c0935a44
sha1: faf863efd5a2e19c341e76d4e3bb8e26355a4c7a
download
Periodical build (some corrections bugs from twrp, init problem correction from cm)
still on 3.10 kernel, switch to 3.4 planned.
[*] Maybe a bug into twrp for android <= 5.1 flashing/restore into empty /system partition. Be careful!
2016-07-16:
FOTAKernel/recovery binary:
md5: 4d4316c266b1c9b737113e1a0166cbc4
sha1: 3ca7798021d4845ddc6814102abfc7c08a3bdee0
downloadflashable zip:
md5: abda5283b200eab0c115e8fd0a5e2196
sha1: e02bb10f69e71df10948a9f124c15ab0a627dad8
download
Correct fstab errors
[*] Apparently there is delay in partition opening due to the twrp implementation of adopted storage. I'm currently trying to fix it.
2016-07-14:
FOTAKernel/recovery binary:
md5: 1e76c989b36ff46657e59e3054ccb704
sha1: 9135cbd75ddb5b2611a24a31b372d841e9c6a69d
downloadflashable zip:
md5: 1da3efe239917ed8872638d4d07d7b9d
sha1: 23ff50355b70495dbf4a6b0ef72acadc324ee832
download
change fstab to make wipes easier
lots of improvements/corrections in twrp tree from TeamWin team
2016-04-14:
FOTAKernel/recovery binary:
md5: 70a22897f6b7cace772cd58e7846f224
sha1: ad11321805c1f91fe2500377baaee9b60b53340b
downloadflashable zip:
md5: f07e9d242b249d2c39388203e6a9eb70
sha1: 44f8a91b0c10b3c667246bd664e923d6d884dbdb
download
Change selinux policies (use xen0n repo)
Twrp flags to restore compatibility with old boot process
This build is a major' release which should restore compatibility with old bootloader.
please report feedback as I can know if I need to continue this way .
create a git repo to push local manifests files
for now my Jenkins is off --> added to the todo list
bootloop workaround kernel:
2016-03-07:
md5: b674a8aa843d9be6d801ada018006141
sha1: 22f7b9ecacb262dd6788fc22ac27e1a7c7265226
download
This is a cyanogenmod kernel where I remove the Dees_Troy 'extract_elf_ramdisk'. This way, if there is a soft reboot to recovery the phone restart cyanogenmod and doesn't go to bootloop. I don't try other rom with with kernel.
2016-03-07:
FOTAKernel/recovery binary:
md5: b5f878a70d7663c4a1d89c7b2668ec56
sha1: 87c278b5317b32c383ad0b2a97452843b37b9b3e
downloadflashable zip:
md5: 89de508f23adcede8967c5a61717e7e4
sha1: 6a59626204ef66614e9fa29635749953b7c6052d
download
resync with omnirom tree
change version number according to twrp.me
2016-02-14:
FOTAKernel/recovery binary:
md5: 69f3852c616472e49c5aaa1120a02a64
sha1: b62bc394849d6c0d918492b4472891a1a2128910
download alternativeflashable zip:
md5: 0aebbbc8e2f881ebef5dc5856060c668
sha1: a6979856c31f0efbf34a8470d7155d5c2a4fbcd5
download alternative
A few releases ago (2016-02-07) device was named leo instead of z3 so flashing zip could fail!
Improve display enabling hardware acceleration
tune some twrp flags
cleanup device tree
2016-02-08:
FOTAKernel/recovery binary:
md5: 6326926e5c46acc80fb925cb2838b05d
sha1: 3fb1a375121fef9b7690c6d556d5af934879ff66
download alternativeflashable zip:
md5: 0cdac0861f1a395706616ff75dbe00c7
sha1: e865ec398ed3c3b9a69735f4ccd51c4ea51fb3ba
download alternative
On precedent release (2016-02-07) device was named leo instead of z3 so flashing zip could fail!
Move device tree to correct the ro.product.device
! As twrp 3.0.0-0 is a new release for me I only test 'basic' things. Feel free to report your experience. (decryption and f2fs always working)
2016-02-07:
FOTAKernel/recovery binary:
md5: b69962aaea113f0e55aa9953d4a1f8c2
sha1: addb93e06824c576d893045e6cb2f65270c426df
downloadflashable zip:
md5: 816da3715c82c2f77b3ab5a6aca1612e
sha1: 26f09b99a65ad2100070f29edd8510d4da76a91e
download
Device name was 'leo' instead of 'z3'!
Switch to omnirom android-6.0 sources
twrp 3.0.0-0 release
kernel 3.10
! As twrp 3.0.0-0 is a new release for me I only test 'basic' things. Feel free to report your experience. (decryption and f2fs always working)
2016-01-14:
FOTAKernel/recovery binary:
md5: b2f6f7aee3e685b7b2a817dc2d9f9b45
sha1: 0b23e1e368ca57a14100eae069b3a0d7daedfbd4
downloadflashable zip:
md5: 52bfd146b0cb69bd0c29ce42b42cf995
sha1: 6f7e7b9ec51f662ef0ccb39a1e63567490485125
download
Custom governor to reduce heating
Revert board-name-change commit
2016-01-09:
FOTAKernel/recovery binary:
md5: a50f9b48d89db94bc5ffa5f791a7cd56
sha1: 2b9848d6f1b7cbdc04a6bb28590ae95265f5b2d0
download: http://s000.tinyupload.com/?file_id=47292896408680539327flashable zip:
md5: 2e8766e3a6be34c11470099f4638dd01
sha1: ca1ec7f53d308980e82c09c586882a6a464dbaf5
download: http://s000.tinyupload.com/?file_id=78086454241793216639
Minor changes (cmdline) to be bootable from new bootloader
2016-01-09:
FOTAKernel binary:
md5: 2aaf2d85bbaf40e0118fae9173b2fb69
sha1: c6ca54aafebde25a32a080d5d44172289a1c707e
download: http://s000.tinyupload.com/?file_id=08765682926169309050flashable zip:
md5: d56266b1df54d2731fd0f0a2e1b1eee6
sha1: 243e1f78c9409b638f68616a01c2f28d34cc4981
download: http://s000.tinyupload.com/?file_id=33880692705595869190
Updated build from sources
2015-12-26:
FOTAKernel binary:
md5: 0cf55faa541f861652e73fa62dbfb80a
sha1: 64a5672198b9a0031ecd663cc62cf2b05cd8a482
download: http://s000.tinyupload.com/?file_id=77779745124843827613flashable zip:
md5: 7bf41589eda189c4646ca979e93da047
sha1: 9a109fe526b1eb616acfed1f85f6438a8b0eb278
download: http://s000.tinyupload.com/?file_id=16394970444867985651
add keystore support in a cleaner way
add /system symlinks so mounting /system is no more needed to decrypt /data
make a 'updater-script' to automate flashing-zip generation
2015-12-24:
md5: 8993fdb30ce00e431a59068f9f014e41
sha1: 5a8dfe7b4cba0b79ba1beea70656e2318dbdc9a2
download: http://s000.tinyupload.com/?file_id=10791233217780154379
Add qcom msm8974 keymaster blobs
uncrypt data now working with workaround
2015-12-19:
md5: c6e3859eae39597f984852c41a183620
sha1: b42aa840637640c3934684b3cb1fa992ea5b383a
download: http://www.datafilehost.com/d/e46f08c4
Add qcom msm8974 hardware crypto support
Try to add uncrypt capabilities (failed)
add governor_scaling to 'ondemand'
2015-12-18:
md5: 13b1d5de4e69e4bb49621fbe87b8ae9b
sha1: 9ed93f895897c885d139d723180d50a33ec0a719
download: http://www.datafilehost.com/d/abe4ced7
Initial release
At home my computer are only on linux distros and today I post my release from work. Then I realize that datafilehost download malware on windows computer. I'm really sorry and hope no computer where infected.
For this 'working crypto' release tinyUpload was used but if anyone know a good solution I take-it. Thanks and sorry for inconvenience .
ext4/f2fs
New release.
Apparently this f2fs build is not compatible with ext4 over encryption (Seems only cyanogenmod use f2fs, you can check your encrypted filesystem with mount | grep "dm-0" )
If you need a decrypt for ext4 ask and I build it asap.
I am running CM12.1 on my Z3 with encryption and dm-0 is type ext4 mounted on /data. I did not changed things manualy. I checked the Z3 of my wife and it's ext4 too.
Gesendet von meinem Xperia Z3 mit Tapatalk
dm-0 ext4
frabe8378910 said:
I am running CM12.1 on my Z3 with encryption and dm-0 is type ext4 mounted on /data. [...] I checked the Z3 of my wife and it's ext4 too.
Click to expand...
Click to collapse
Thank you for this information! Is this build of twrp working for you with encryption? If not I rebuild it with the ext4 flag.
frabe8378910 said:
I did not changed things manualy.
Click to expand...
Click to collapse
I switch my /data & /data/media to f2fs before encrypting my CM12.1, maybe that is it
Thanks for your feedback.
nailyk said:
Thank you for this information! Is this build of twrp working for you with encryption? If not I rebuild it with the ext4 flag.
I switch my /data & /data/media to f2fs before encrypting my CM12.1, maybe that is it
Thanks for your feedback.
Click to expand...
Click to collapse
I did not tested it, because I thought it was build only for f2fs.
As our SDcard is also ext4 (I need files size up to 25GB) I had never played with f2fs.
And being honest: Both Z3 are "productive" Smartphones, so currently I'd install only "low risc" options.
Gesendet von meinem Xperia Z3 mit Tapatalk
frabe8378910 said:
I did not tested it, because I thought it was build only for f2fs.
As our SDcard is also ext4 (I need files size up to 25GB) I had never played with f2fs.
Click to expand...
Click to collapse
I switch to f2fs for performance but my last dmesg sounds like the dmcrypt is ext4. Anyway my computer is currently building with the ext4 flag for testing purpose.
frabe8378910 said:
And being honest: Both Z3 are "productive" Smartphones, so currently I'd install only "low risc" options.
Click to expand...
Click to collapse
Totally understand! My z3 is also everyday use and my only phone but it is mine. If i brake yours I go crazy :fingers-crossed:
I'm actually working with the twrp team to port my work, maybe you could try later
Have you find other recovery with working encryption?
nailyk said:
I switch to f2fs for performance but my last dmesg sounds like the dmcrypt is ext4. Anyway my computer is currently building with the ext4 flag for testing purpose.
Totally understand! My z3 is also everyday use and my only phone but it is mine. If i brake yours I go crazy :fingers-crossed:
I'm actually working with the twrp team to port my work, maybe you could try later
Have you find other recovery with working encryption?
Click to expand...
Click to collapse
No, I'm using twrp from LeonidasTurk on both Z3, which works fine except decryption of /data. So if your's would fix this issue, that would be perfect.
frabe8378910 said:
I did not tested it, because I thought it was build only for f2fs.
Click to expand...
Click to collapse
nailyk said:
my computer is currently building with the ext4 flag for testing purpose.
Click to expand...
Click to collapse
Confirmed, the
Code:
TW_CRYPTO_FS_TYPE
flag is deprecated.
(https://github.com/omnirom/android_bootable_recovery/blob/android-5.1/crypto/lollipop/cryptfs.c#L71)
and my dmcrypt is ext4
HTML:
/dev/block/dm-0 on /data type ext4 (rw,relatime,data=ordered)
/dev/block/dm-0 on /sdcard type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type f2fs (rw,relatime,background_gc=on,user_xattr,acl,inline_data,extent_cache)
so the filesystem doesn't matters. I edit the post consequently. Thanks a lot @frabe8378910
frabe8378910 said:
No, I'm using twrp from LeonidasTurk on both Z3, which works fine except decryption of /data. So if your's would fix this issue, that would be perfect.
Click to expand...
Click to collapse
For me it is working fine for a couple of month now. And we have successfully ported twrp with encryption to z1, z1c & z3.
So if you are ok to try it please leave a comment to share the result of your tests (phone heat, encryption, speed, etc...)
Thank for your time!
nailyk said:
For me it is working fine for a couple of month now. And we have successfully ported twrp with encryption to z1, z1c & z3.
So if you are ok to try it please leave a comment to share the result of your tests (phone heat, encryption, speed, etc...)
Thank for your time!
Click to expand...
Click to collapse
I'll check it the coming weekend.
Thanks for your work.
Gesendet von meinem Xperia Z3 mit Tapatalk
frabe8378910 said:
I'll check it the coming weekend.
Thanks for your work.
Gesendet von meinem Xperia Z3 mit Tapatalk
Click to expand...
Click to collapse
I already did it and it works like a charm!
Perfect, now I can use internal sdcard from recovery too!!
Decryption just takes some seconds.
Tomorrow I'll update the Z3 of my wife too.
Thanks a lot for your work!
Gesendet von meinem Xperia Z3 mit Tapatalk
frabe8378910 said:
I already did it and it works like a charm!
Perfect, now I can use internal sdcard from recovery too!!
Decryption just takes some seconds.
Tomorrow I'll update the Z3 of my wife too.
Thanks a lot for your work!
Click to expand...
Click to collapse
Glad it work well for you too.
Thank for your time and your feedback!
nailyk said:
Glad it work well for you too.
Thank for your time and your feedback!
Click to expand...
Click to collapse
But so, you did the work and I just consumed that work...
Btw: I installed your recovery by flashing the zip from recovery.
Gesendet von meinem Xperia Z3 mit Tapatalk
z3 bootloader
frabe8378910 said:
Btw: I installed your recovery by flashing the zip from recovery.
Click to expand...
Click to collapse
Have you upgraded your bootloader or are you using the older?
The new one offer real recovery possibilities: if a rom upgrade fail recovery will still be accessible. That is not possible with the older bootloader. The point is, to upgrade, you need to reflash your entire phone to stock.... (all your datas will be lost) Dedicated xda-thread?
nailyk said:
Have you upgraded your bootloader or are you using the older?
The new one offer real recovery possibilities: if a rom upgrade fail recovery will still be accessible. That is not possible with the older bootloader. The point is, to upgrade, you need to reflash your entire phone to stock.... (all your datas will be lost) Dedicated xda-thread?
Click to expand...
Click to collapse
No, I did not change the bootloader, 'cause I don't like to reflash stock.
I've not read much about it, but doesn't mean reroot it afterwards? I'd just stay tuned that someone provide a better way...
Gesendet von meinem Xperia Z3 mit Tapatalk
frabe8378910 said:
No, I did not change the bootloader, 'cause I don't like to reflash stock.
I've not read much about it, but doesn't mean reroot it afterwards?
Click to expand...
Click to collapse
You are right, the way sony provide, reflash the entire phone (except recovery).
frabe8378910 said:
I'd just stay tuned that someone provide a better way...
Click to expand...
Click to collapse
I am a gambler(?) but with bootloader I take no risk.
Tell me if you find something working.
@nailyk
Welcome to XDA. By the way, you only need to encrypt your phone once. After that you can install any other rom while keeping the same encryption. You just do wiping in TWRP with rm -rf instead of formatting. I tested and was able to successfully install a different rom.
Also, it is important to encrypt your phone (once only) via adb, because otherwise, your data partition is encrypted with the following password: 'default_password', literally. That's no security at all. Adb allows you to have an unlimited length boot password and a separate short pin for screen lock.
Also, once you remove this commit https://gerrit.omnirom.org/#/c/14353/ , and you would want to remove encryption, you can do that by pressing 'cancel' when asked for password and then format system, then data and then /system/data/cache/...
AOSP encryption password
optimumpro said:
@nailyk
Welcome to XDA. By the way, you only need to encrypt your phone once. After that you can install any other rom while keeping the same encryption. You just do wiping in TWRP with rm -rf instead of formatting. I tested and was able to successfully install a different rom.
Click to expand...
Click to collapse
Thank you!
It is good new as I want to have ability to switch between CM and stock rom.
optimumpro said:
Also, it is important to encrypt your phone (once only) via adb, because otherwise, your data partition is encrypted with the following password: 'default_password', literally. That's no security at all. Adb allows you to have an unlimited length boot password and a separate short pin for screen lock.
Click to expand...
Click to collapse
I didn't change my bootpassword yet but it is planned
Also I have some questions:
What I have understood from official AOSP documentation and twrp source code is the dmcrypt password is 'default_password' even if encrypted with your adb way. I suppose 'vdc cryptfs changepw' if the command used by the GUI: if I change my boot password with 'foobar' with 'vdc cryptfs changepw 666f6f626172', then change my screen-unlock password with '0000', I suppose the bootpassword will be erased by '0000'. Is it true?
optimumpro said:
Also, once you remove this commit https://gerrit.omnirom.org/#/c/14353/ , and you would want to remove encryption, you can do that by pressing 'cancel' when asked for password and then format system, then data and then /system/data/cache/...
Click to expand...
Click to collapse
As I can remember and according to this part of code, wiping device by clicking the different 'format' buttons wipe encryption.
So did you say once the phone boot password is changed with your 'adb command' the only way to wipe encryption is to recompile a twrp without this commit? I also planned some tests: wiping encryption, restoring backups on encrypted partitions, etc...
P.S.: I update my build tree to include z1/z1c/z3 with a new recovery/Android.mk. Now mka recoveryimage should work.
@nailyk
Can't seem to reboot recovery from within TWRP on stock .264 (UB). It boots straight to system. Booting to recovery with power button plus volume down combo when device is off works. Any ideas?
Unofficial CyanogenMod 13.0 for Samsung Galaxy Tab 3 10.1
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, ...
* You flash this at your own risks
*/
About CM
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Important information
You need a recent TWRP version to flash this ROM.
Installation
First time installing, coming from another ROM or upgrading from alpha < 4
Copy ROM to SDCard
Copy Houdini to SDCard
Copy GApps to SDCard
Boot into recovery
Backup EFS partition
Wipe -> Advanced Wipe -> Dalvik Cache + System + Cache + Data
Install ROM
Install Houdini
Install GApps
Reboot
First start takes a long time
Upgrading from earlier version of CyanogenMod 13.0 (alpha >= 4)
Copy ROM to SDCard
Boot into recovery
Install ROM
Reboot
[OPTIONAL] Converting filesystem to F2FS (thanks @michiil)
The ROM has F2FS support. You may want to use it instead of the default (EXT4).
This will delete ALL files/data from your tab.
What you will need: A working PC and a working USB cable.
Install the most recent Recovery
Download the most recent Recovery from the second post. Flash the zip file in recovery. Back in the main menu press Reboot > Recovery
Format Data and Cache to F2FS
Wipe > choose Cache > repair or change file system > change file system > F2FS > Swipe to Confirm
Go back and repeat the same steps with Data. I got some error messages when formatting Data but they don't seem to be a problem.
Back in the main menu press Reboot > Recovery
Install Rom + Houdini + Gapps
Connect your tab to your PC and copy the zip files on the tab.
Flash the files, reboot and enjoy :good:
How to get back to EXT4
You will again loose all files/data on the tab.
Just repeat Step 2 but use EXT4 instead of F2FS.
What's working
RIL (audio calls, data, sms, mms)
2D/3D acceleration
HW video encoding/decoding
Screen cast (Miracast/Wifi Display)
MHL/HDMI
Sound
InfraRed
Camera
Wifi
Bluetooth
GPS
Sensors
SDCard, USB OTG
Tethering (USB, Bluetooth, Wifi)
Software DRM (Level 3, see below)
Known to be working
Google Movies
Amazon Prime Video
Molotov TV
myCANAL
Canalplay Kids
Known *not* to be working
6play
Features
Automatic brightness
Change Color profile
Change mDNIe scenario
Enable/disable mDNIe negative mode
Multiuser
Enable/disable capacitive keys
Change capacitive keys width
Buttons backlight on screen touch or key touch only
Smart cover lock/unlock
F2FS and exFAT support
Houdini (allows to install arm only apps on this x86 device)
Updated ZRAM support with LZ4 compression for maximum memory and speed
Updated Xbox Controller driver
Updated interactive CPU governor
Available CPU governors: powersave, interactive, performance, ondemand
Available I/O schedulers: noop, deadline, cfq, bfq (v7r8), fiops
Available battery modes (CM power profiles): power save, balanced, performance
What's not working
Chromecast screencasting (other functions work)
Hardware DRM (Level 1)
SELinux (permissive)
You tell me
How to root
Go to 'Settings/About tablet'
Tap 7 times on 'Build number'
Go back
Go to 'Developer options'
Tap on 'Root access'
Select 'Apps only' ('Apps and ADB' if you plan to use it in adb shell)
How to help
When something is not working correctly, in addition to common informations, I may ask you to provide logs. There are different kind of logs and it's not always easy to get all of them. For this, you can use SysLog (available on F-Droid or Google Play).
Fixed in version 2.1.0 There is currently a bug in the app. Download it from AndroidFileHost. Use this patch if you want to compile it yourself:
Make sure to root device before using this app.
To get the logs:
Start SysLog
Click on 'TAKE LOG'
Once log is taken, SysLog will try to share the resulting file, just cancel
Send me the file /sdcard/SysLog/[YYYY-MM-DD_HH.mm]/[YYYY-MM-DD_HH.mm].zip
If you left 'Scrub potentially personal information from the logs' checked, you should be safe.
Sources
Kernel
Common: https://github.com/santos10-dev/android_kernel_samsung_santos10/tree/cm-13.0
Device trees
Common: https://github.com/santos10-dev/android_device_samsung_santos10-common/tree/cm-13.0
Galaxy Tab 3 10.1 3G: https://github.com/santos10-dev/android_device_samsung_santos103g/tree/cm-13.0
Galaxy Tab 3 10.1 Wifi: https://github.com/santos10-dev/android_device_samsung_santos10wifi/tree/cm-13.0
Galaxy Tab 3 10.1 LTE: https://github.com/santos10-dev/android_device_samsung_santos10lte/tree/cm-13.0
Local manifest
https://github.com/santos10-dev/android_device_samsung_santos10-common/wiki/Local-manifest-CM-13.0
Credits
Angel_666 , moonbutt74 and Restl3ss for starting the work on this device
Android-Andi for his device tree
crpalmer for his work on Intel support
Deltadroid for his GApps package
All testers of the "signup" thread
CyanogenMod and Google for Android
XDA
AndroidFileHost
XDA:DevDB Information
CyanogenMod 13.0 for GT-P52XX, ROM for the Samsung Galaxy Tab 3 10.1
Contributors
nels83
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-03-21
Last Updated 2017-04-11
Downloads
ROM
ROM - Beta 2 (20161210)
Galaxy Tab 3 10.1 3G : santos103g (MD5)
Galaxy Tab 3 10.1 Wifi : santos10wifi (MD5)
Galaxy Tab 3 10.1 LTE : santos10lte (MD5)
You can find old versions on AndroidFileHost. Version code is in file description.
Houdini 6.0.0_x.47745
Houdini for Android 6.0
GApps
See Open Gapps, select Platform x86 and Android 6.0.
Other
Flash player (11.1.112.60)
Flash player for x86
Note: not much used nowadays but useful if you want to play flash games.
Changes
Changelog
Beta 2 (20161210)
- Fixed audio calls
- Switched to dlmalloc
Old changes
Beta 1 (20161204)
- Fixed freezes
- Fixed AGPS
- Cleaned up sensors hal
- Use opensource audio hal
- Added FIOPS io scheduler
Alpha 7 (20161121)
- CM update (android 6.0.1_r74)
- Added software DRM support (Level 3)
- Fixed touchscreen lags (maybe not all lags, thanks to @Alphita and @KNGPN Q w Q)
- Fixed lock screen rotation (thanks to @tinko975)
- Fixed Google SetupWizard loop when no network is available (CM)
Alpha 6 (20161018)
- CM update
- Updated kernel memory management (and removed samsung specific code)
- Updated kernel android drivers
- Fixed button lights always on when disabled
- Fixed rotation (small) bug
- Fixed deep sleep issues
- Fixed many reboot issues
- Enabled CABC
Alpha 5 (20160822)
- Updated to stable/cm-13.0-ZNH5Y branch
- Enabled Doze mode (thanks to @vin_)
- Enabled 180deg rotation by default
- Enabled swap volume keys on rotation by default
- Added MHL/HDMI support
- Added houdini Intel patches for better compatibility
- Added USB charger port support
- Fixed fast/slow charging reports
- Fixed buttons backlight on key touch only
- All kernel modules are now builtin
- Various tweaks
Alpha 4 (20160731)
- Switched back to stable/cm-13.0-ZNH0E branch
Alpha 3 (20160727)
- CM update
- Fixed Flash Player
- Fixed /dev/last_kmsg
- Fixed cpuset
- Tweaked power management
- Implemented CM power profiles (battery modes)
- Added color profile setting (in LiveDisplay)
- Added Advanced Settings (mDNIe scenario, large/small capacitive keys, buttons light on screen/button touch)
- Added stock charger images
Alpha 2 (20160430)
- Based on stable/cm-13.0-ZNH2K branch
- First try at RIL (3G and LTE)
- Fixed Wifi tethering (thanks @deadfun)
- Enabled and tweaked cpusets (fixes SMP "bug")
- Updated and tweaked cpufreq interactive
- Updated xpad driver (thanks @X-Coder)
- Updated kernel config (merged android recommended settings)
- Added bfq io scheduler
- Enabled deadline scheduler
- Enabled powersave cpufreq scaling governor
Alpha 1 (20160321)
- First release
- Based on stable/cm-13.0-ZNH0E branch
Thanka @nels83 i was waiting for this since morning ?
why does RIL not working? its the most important thing for me
Awesome it works
How to Upgrade from CM12?
Spegeli said:
How to Upgrade from CM12?
Click to expand...
Click to collapse
Download TWRP, opengapps, houdini and the rom (corresponding to your device)
Backup all your data (pictures, music etc.) and apps (preferably with apps like titanium backup) to your PC
put the zips from above onto your sd card (if you don't have one, use the internal storage)
boot into recovery of your tab
wipe /system, /cache, /data, dalvik cache and (if you don't have important data like the zips on there) the internal storage
flash the files in the following order:
TWRP (then restart your device into recovery)
ROM
Houdini
Gapps
if you want to do it: reformat /cache and /data now with f2fs
reboot into system
connect your device to the pc again and get your backed up files and apps
reinstall apps through the play store and if you want to: get their data back with Titanium Backup
Done.
EDIT:
it's nice that CM13 is out and that Houdini is working
though I'm going to wait for RIL support before I update
How complicated is it to fix/How long will it take (min)? (if you can say that)
Dj_Fex said:
Download TWRP, opengapps, houdini and the rom (corresponding to your device)
Backup all your data (pictures, music etc.) and apps (preferably with apps like titanium backup) to your PC
put the zips from above onto your sd card (if you don't have one, use the internal storage)
boot into recovery of your tab
wipe /system, /cache, /data, dalvik cache and (if you don't have important data like the zips on there) the internal storage
flash the files in the following order:
TWRP (then restart your device into recovery)
ROM
Houdini
Gapps
if you want to do it: reformat /cache and /data now with f2fs
reboot into system
connect your device to the pc again and get your backed up files and apps
reinstall apps through the play store and if you want to: get their data back with Titanium Backup
Done.
EDIT:
it's nice that CM13 is out and that Houdini is working
though I'm going to wait for RIL support before I update
How complicated is it to fix/How long will it take (min)? (if you can say that)
Click to expand...
Click to collapse
Not possible to Upgrade without loosing all Apps (and there Settings)?
sorry, I won't guarantuee you that anything is working if you leave the data partition and don't format it
even though it might be nice to keep the data
it's safer to backup your the data and apps that you need and then start fresh
and usually it's not even that much of a hassle (you just need to get used to it)
Nels says at the top:
if you come from an earlier version of cm13 then it's possible
but if you come from another rom (cm12) you need to wipe data
@nels83 I just noticed, your changelog link still points to the cm 12 branch (only a copy&paste issue of course so no big deal)
@nels83 Just upgraded from cm12,1 beta 2. This ROM works fine. Thanks
pvt-koffiejunk said:
@nels83 Just upgraded from cm12,1 beta 2. This ROM works fine. Thanks
Click to expand...
Click to collapse
do you fresh install the rom?or just dirty flash it and its work fine?
Anyone know how to make this rom black ?
Rom is buttery smooth, I am having issues with chrome being slow but that also happened on cm 12.1
Lionerx said:
do you fresh install the rom?or just dirty flash it and its work fine?
Click to expand...
Click to collapse
Just dirty. Figured I could always flash again and do the right way.
Strange I don't see option for downloading of GApps 6 86x at open GApps
Mrkijo said:
Strange I don't see option for downloading of GApps 6 86x at open GApps
Click to expand...
Click to collapse
maybe is temporarly down.. it worked for months.. with aosp rom too..
i download it yesterday.
edit:
here are links from few days before..
https://github.com/opengapps/x86/releases/tag/20160320
..
@nels83 just a quick info: if I use your P5210 device tree in my CM 13.0 source, can I build it from scratch? I'd like to experiment with that.
tinko975 said:
maybe is temporarly down.. it worked for months.. with aosp rom too..
i download it yesterday.
edit:
here are links from few days before..
https://github.com/opengapps/x86/releases/tag/20160320
..
Click to expand...
Click to collapse
Thanks, you were right, it was temporary and now it is on again ?
After 20 Hours of Testing, the Rom works good except:
- Kaspersky Internet Security crashed when starting a analysis
- Camera crashed when switching to Focus Effects or Video
The rest seems working fine so far.