Database Develop

[ROM][SNAPSHOT][6.0.1] CyanogenMod 13.0 for Xperia TX

{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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.
*/
About CyanogenMod
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.
All the source code for CyanogenMod is available in the CyanogenMod GitHub repo.
And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
Official CyanogenMod 13 Release post : http://www.cyanogenmod.org/blog/cm-13-0-release-1
Hayabusa CyanogenMod Wiki : https://wiki.cyanogenmod.org/w/Hayabusa_Info​
CyanogenMod 13.0 for Sony Xperia Blue
Xperia T (Mint) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3415827
Xperia TX (Hayabusa) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3418818
Xperia V (Tsubasa) : http://forum.xda-developers.com/xperia-t-v/v-development/rom-t3416938​
Downloads Links
CyanogenMod 13.0 (Unlocked Bootloader) :
Xperia TX (Hayabusa) : https://mega.nz/#F!L8cRRKiI!SzWmsKUyEdJgaMjB8ksxYw
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 6.0, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
TWRP 3.0 : http://forum.xda-developers.com/xperia-t-v/t-development/recovery-twrp-3-0-0-touch-recovery-t3319588
Useful alternatives to CM Updater (with Deltas) : CM Downloader on Play Store
About CyanogenMod : ChangeLog available on http://www.cmxlog.com/13/hayabusa/​
Unification of the user partitions into UserData
Read more about the UserData unification : https://wiki.cyanogenmod.org/w/Hayabusa_Info
Migrate to the one big partition for CM-13.0 :
- (Optional) Backup all your data, applications, internal storage, ...
- (Optional) If wished, do a full Nandroid backup from Recovery
- Flash the latest ROM zip of your device to start the unification
- Read and follow the instructions from the zip if anything goes wrong
- (Optional) Restore your Nandroid backup if you want to
- Flash the same ROM zip for CyanogenMod 13.0
Reverse the migration for older ROMs :
- (Optional) Backup all your data, applications, internal storage, ...
- Reboot to recovery and do a Factory reset (data will be lost)
- Flash restore_sdcard-YYYYMMDD-blue.zip
- Read and follow the instructions from the zip if anything goes wrong
- Flash the ROM you want now and restore your data​
Flashing and updating
CyanogenMod clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the CyanogenMod 13.0 ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
CyanogenMod update / upgrade :
- (Information) Don't wipe anything unless you want to
- (BETA / UNOFFICIAL) Nothing to wipe when switching
- Flash the latest CyanogenMod 13.0 ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot​
About the builds
Device tree : https://github.com/CyanogenMod/android_device_sony_hayabusa/commits/cm-13.0
Common tree : https://github.com/CyanogenMod/android_device_sony_blue-common/commits/cm-13.0
Kernel sources : https://github.com/CyanogenMod/android_kernel_sony_msm8x60/commits/cm-13.0
Vendor blobs : https://github.com/TheMuppets/proprietary_vendor_sony/commits/cm-13.0​
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example​
Q&A - FAQ
CM-13.0 Hayabusa Regular Questions and Answers : Q&A Thread
About CM-13.0 : https://en.wikipedia.org/wiki/CyanogenMod
The CyanogenMod team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!​
CyanogenMod available for Hayabusa also thanks to :
- The CyanogenMod Team
- CodeZero and SdtBarbarossa for originally importing Huashan CM13 sources & confirming the revival was possible
- Everyone involved in working and testing​
XDA:DevDB Information
CyanogenMod 13.0, ROM for the Sony Xperia T
Contributors
Adrian DC
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Snapshot
Current Stable Version: 20161220-SNAPSHOT
Current Beta Version: UNOFFICIAL
Created 2016-07-15
Last Updated 2017-03-20

Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- Dual Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently based on Huashan kernel
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok (RTC real hardware clock, in TWRP recovery too)
- Powered-off alarm : Ok
- Offline Charging : Ok (with SONY design)
- Encryption : Status unknown
- SEPolicies : Fully enforced
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume - to open CyanogenRecovery,
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Powered-off alarm : When you have set an alarm
- If you power down the device, it will wake automatically 5 minutes before
- If you let the device charge offline, it will automatically reboot 5 minutes before
Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds

Reserved
Current status of the ROM Builds
Nightlies : Only once everything is considered working and stable.
Beta : When needed. Newest changes to test, full builds or kernels / packages to flash.
Current local manifest of the ROM build
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://github.com/CyanogenMod/android -->
<manifest>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" />
<project name="CyanogenMod/android_hardware_sony_thermanager" path="hardware/sony/thermanager" remote="github" />
<project name="AdrianDC/android_device_sony_blue-common" path="device/sony/blue-common" remote="github" />
<project name="AdrianDC/android_device_sony_hayabusa" path="device/sony/hayabusa" remote="github" />
<project name="AdrianDC/android_kernel_sony_msm8x60" path="kernel/sony/msm8x60" remote="github" />
<project name="AdrianDC/proprietary_vendor_sony" path="vendor/sony" remote="github" />
</manifest>

Many thanks for porting new CM to this old phone!

Beta? Let's test

A very important change will hit your devices upon next release.
Please do read here : http://forum.xda-developers.com/xpe...od-13-0-xperia-t-t3415827/page11#post67850287

test

Alright migration helpers finished, ready for public release !
Please read the details added to the main post about the process.
No help will be given if you do not want to read everything
I spent time writing & displaying on error during the flash processes.
Should you read everything correctly and follow all the instructions
given to you by all the securities embedded in my zips, and still have issues,
then maybe shall I and other consider helping you.
I'm not saying that to be mean but because this is meant to be performed totally autonomously,
and the details I gave on the first post and all instructions & warnings from the zip
have to be enough for the less experienced users who takes time to read,
since I will then be adding this all on the CM Wiki pages.
To upgrade, you'll need the zips for the unification mentioned in the OP,
the latest CM13 release for your device, and optionally, the latest TWRP release from today.

Thanks for updates! The zip file for user data unification works great. But there seems some UI issue for cm-13.0-20160722-UNOFFICIAL-hayabusa.zip. Tapping on the bottom part of the screen doesn't response properly, but triggers notification drop down menu.

cornpoppy said:
Thanks for updates! The zip file for user data unification works great. But there seems some UI issue for cm-13.0-20160722-UNOFFICIAL-hayabusa.zip. Tapping on the bottom part of the screen doesn't response properly, but triggers notification drop down menu.
Click to expand...
Click to collapse
CM failed commit, fixed last night.
I made a new release overnight.

About the sleep of death : So far, nothing relevant found or a certain way to reproduce it,
totally random & I must be the one who has it the less on the whole planet, which makes it even harder...
About the touchscreen issues in call : I think Xperia TX Hayabusa is not affected by that bug,
because its Clearpad touchscreen already has the support for the new system handling incall suspends,
however I might be wrong and it could not work properly, although it's very unlikely.
Please report on that just to confirm it's alright for Hayabusa too (In-call + proximity, touchscreen must be ignored).

@Adrian DC
Hey, so first of all, thanks for reviving this old phone. Was actually planning on testing, made backup, formatted data/caches/sdcard (ext4) inside TWRP, and tried flashing the unification zip file, I got the error
Code:
Device does not have a SDCard partition anymore
Unification unnecessary
Any ideas? Thanks
Edit:
I previously expanded my data partition according to this guide, don't know if that's relevant or not.

Go in TWRP and share the output of "adb shell /sbin/sgdisk —print /dev/block/mmcblk0".

Adrian DC said:
Go in TWRP and share the output of "adb shell /sbin/sgdisk —print /dev/block/mmcblk0".
Click to expand...
Click to collapse
Here you go, it would seem like the sdcard isn't labeled:
Code:
Number Start (sector) End (sector) Size Code Name
1 256 4351 2.0 MiB FFFF TA
2 4352 7423 1.5 MiB FFFF Boot
3 7424 10495 1.5 MiB FFFF Boot2
4 12288 53247 20.0 MiB FFFF Kernel
5 53248 55295 1024.0 KiB FFFF TZ
6 57344 63487 3.0 MiB FFFF modemst1
7 65536 71679 3.0 MiB FFFF modemst2
8 73728 79871 3.0 MiB FFFF fsg
9 79872 90111 5.0 MiB 8300 ramdump
10 90112 106495 8.0 MiB 8300 apps_log
11 106496 139263 16.0 MiB 8300 FOTAKernel
12 139264 2654207 1.2 GiB 8300 System
13 2654208 3166207 250.0 MiB 8300 Cache
14 3166208 9166015 2.9 GiB 0700 Userdata
15 9166016 30535646 10.2 GiB 0700
Update:
@Adrian DC, so I see your script checks for the partition name at one point, so that was the root of the error, probably something that wouldn't happen to many people; I most likely forgot to give that partition it's name, fixed using `parted` and it worked, rebooting now.

So flash worked, but Android only sees about 3gb of internal storage (the exact same amount that was allocated to the UserData partition originally), even though I can see it has the proper size:
Code:
Number Start (sector) End (sector) Size Code Name
1 256 4351 2.0 MiB FFFF TA
2 4352 7423 1.5 MiB FFFF Boot
3 7424 10495 1.5 MiB FFFF Boot2
4 12288 53247 20.0 MiB FFFF Kernel
5 53248 55295 1024.0 KiB FFFF TZ
6 57344 63487 3.0 MiB FFFF modemst1
7 65536 71679 3.0 MiB FFFF modemst2
8 73728 79871 3.0 MiB FFFF fsg
9 79872 90111 5.0 MiB 8300 ramdump
10 90112 106495 8.0 MiB 8300 apps_log
11 106496 139263 16.0 MiB 8300 FOTAKernel
12 139264 2654207 1.2 GiB 8300 System
13 2654208 3166207 250.0 MiB 8300 Cache
14 3166208 30535646 13.0 GiB 8300 Userdata
I can't see "internal storage" in TWRP, only "Legacy SDCard", and "Legacy SDCard" can't even be mounted.

Antiga Prime said:
So flash worked, but Android only sees about 3gb of internal storage (the exact same amount that was allocated to the UserData partition originally), even though I can see it has the proper size:
I can't see "internal storage" in TWRP, only "Legacy SDCard", and "Legacy SDCard" can't even be mounted.
Click to expand...
Click to collapse
Flash fix-userdata zip, format that new partition ...

dzadzev said:
Flash fix-userdata zip, format that new partition ...
Click to expand...
Click to collapse
Thanks, I was pretty sure I had done that through "parted" but, I guess I didn't. Did that through TWRP and all good!

Adrian DC said:
CM failed commit, fixed last night.
I made a new release overnight.
Click to expand...
Click to collapse
It works now. Many thanks!

Antiga Prime said:
@Adrian DC, so I see your script checks for the partition name at one point, so that was the root of the error, probably something that wouldn't happen to many people; I most likely forgot to give that partition it's name, fixed using `parted` and it worked, rebooting now.
Click to expand...
Click to collapse
Exactly, good job on understanding it all by yourself !
As you can see, my scripts will refuse to work if there is anything wrong on the device.
Also notice the fact that even if you had change the partitions sizes, everything will work.
To everyone : If you restore a backup, or fail to follow the instructions saying you have to Factory Reset,
and when required flash fix-userdata-YYYYMMDD-blue.zip, you won't see the full partition size.
Very important about all TX Users ! I need to know if one of you ever had a Sleep of Death !

New release 20160725 : Latest blue changes, latest CM changes.
Need confirmation Hayabusa never was concerned by sleep of deaths.

[RECOVERY] ufoFFICIAL TWRP 3.1.1-0 & MultiROM33v27 (adb/authorized)

(Download 2016-12-16 TWRP 3.0.3 : https://www.androidfilehost.com/?fid=673368273298921729)
Check attached 'install'.zip (to be flashed via cwm or twrp) file, for a more recent edition of twrp3.1.0-0 !
Built with Omnirom 6 repo, from unmodified bootable /TeamWin branch 7.1 (f2fs-tools v1.4)
More news: https://github.com/omnirom/android_bootable_recovery/commits/android-7.1

[EXP] Multirom33 TWRP3.1.1 +TrampolineV27 +MultiROMMgr.apk with No-Kexec work-around
Credits ( @mkasick ) @Tasssadar https://forum.xda-developers.com/showthread.php?t=2104706
p880 ( @Adam77Root ) @Demetris @fritzcola https://forum.xda-developers.com/optimus-4x-hd/orig-development/mod-multirom-v32-t3116422
Source https://github.com/Tasssadar/device_asus_grouper
https://github.com/P880-dev/android_kernel_lge_x3/commit/de499e8fd657925a74015f62229c5165620f127a
Complete manual : https://forum.xda-developers.com/showthread.php?t=2011403<--donations' thread
DOWNLOAD FILES : https://www.androidfilehost.com/?w=files&flid=146943​
twrpMR3.0.3 sources : https://github.com/multirom-htc/Team-Win-Recovery-Project/commits/android-7.1-mrom
Roms kick-flip are auto-explanatory...
-for 2ndRoms, twrp3__MR33v27 simulates a clean virtual format/data at every new creation (without wiping your internal medias & files !)
-multirom' Trampoline works with all recoveries (cwm&twrp) and provides a stand-by interface (added in your primary installed kernel), with all reboot options, and authorized adb (shell ls /mrom_bin /realdata ...)
-all your roms can be matched with dedicated onboot script.sh https://github.com/Tasssadar/multirom/wiki/run-on-boot-scripts
-attached Cyospak7-2016.zip is a kexec-ed compatible (any)kernel with: cm12 aosp5 aosp6 aosp7
Due to pressPOWER/till1stVIBER trick for 2nd/roms/non_shared_boot.img , p880 will likely NOT be official for MultiROM Manager app
NEW triple EDITION with No-Kexec work-around (boot.img shuv-it)
-20170517 twrp3.1.1(f2fs1.7) img MultiROM : //github.com/multirom-dev/Team-Win-Recovery-Project/commits/android-7.1-mrom
-20170701 Multi-boot zip menu ://github.com/multirom-dev/multirom/commits/master
-MultiROMMgr apk ://github.com/AdrianDC/MultiROMMgr/commits/master
TIP for hard buttons: using one nail to light click isn't as destructive as "fat" fingerprint pressure !
Kernel GPL

f2fs [WIP]
wip (kernel & mount_options*3fstab...)
DOWNLOAD exp f2fs 1.7: X-twrp3_1_0-20170308-f2fs1_7-ufoFLASH-p880.img
TWRPpost#1 are built with (2015-03-04omni6=aosp7=cm12.1)f2fs-tools v1.4.1 & adb authorized
(cm11 uses older 2013-10-25v1.2)
-official p880 recoveries twrp3.0.2/cwm6.0.5 do not include f2fs support
-unmodified p880 recoveries (from source) do not include specific p880 cold boot to recovery : always ext4
-aosp7 & omni7 are using same old f2fs than cm12 : 1.4
-"setup-recovery" is an arbitrary sh designation for one action/phrase to skip p880 cold boot : echo "boot-recovery" | /sbin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
- @laufersteppenwolf twrp2.7.1 was compiled with an added tool fibmap.f2fs, probably to countercheck the specific p880 cold boot (ext4)
-all recoveries can not mount any partition if p880 specific mmcblk0p5 is not void/wiped by postrecoveryboot.sh
- @alfsamsung cm13 doesn't support f2fs for now
So once again, IMHO, Multirom Trampoline is best universal solution to specific p880 cold boot : it provides a stand by menu (linux primary kernel) where you can reboot to bootloader directly (or primary/2nd roms...), and "warm reboot to recovery" option...
I believe that twrp' sources & missing fstab2, have nothing wrong , the origin is the non-standard (secure?) cold boot for p880: all other Tegra3 devices have hybrid ext4/f2fs OK(asusTF700 with official twrp). The best will be to find @laufersteppenwolf twrp2.7.1 repo; the worst is to use cwm editions.
Click to expand...
Click to collapse
with tool like 3CtoolboxFree you can trim/clean etc ; within 3C/terminal/SUticked : type "setup-recovery" then aosp6/7 reboot will get you to twrp & f2fsOK..
3C can behave intrusive, but you can use it static : greenify + autostarts
Finally remember that depending twrp_romVersion and mount/flag used for format/f2fs, can give minor changes (?) : aosp6/7 omni6/7 and cm12 are on "old" regular =1.4.1 ;
Code:
I:operation_start: 'Change File System'
Formatting Cache using mkfs.f2fs...
F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18) [modified by Motorola to reserve space]
Info: Trim is disabled
Info: sector size = 512
Info: total sectors = 786432 (in 512 bytes)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.1.10-CM ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Sun Jan 15 23:58:55 CET 2017"
Info: format successful
I:mkfs.f2fs -t 0 /dev/block/mmcblk0p4 process ended with RC=0
Done.
I:Recreating /cache/recovery DATA.cpp folder.
Nameless3 =1.5
Only cm13 =1.6.1 and cm14.1 =1.7 include more options : defrag ....
Code:
I:operation_start: 'Change File System'
Formatting Cache using mkfs.f2fs...
F2FS-tools: mkfs.f2fs Ver: 1.6.1 (2016-03-22) [modified by Motorola to reserve space]
Info: Debug level = 0
Info: Label =
Info: Segments per section = 1
Info: Sections per zone = 1
Info: Trim is disabled
Info: sector size = 512
Info: total sectors = 786432 (384 MB)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.1.10-aosp67 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Sun Jan 15 00:32:53 CET 2017"
Info: Overprovision ratio = 10.000%
Info: Overprovision segments = 43 (GC reserved = 28)
Info: format successful
I:mkfs.f2fs -t 0 /dev/block/mmcblk0p4 process ended with RC=0
Done.
I:Recreating /cache/recovery folder.
When you format via twrp run the save_log option and check the end.
Click to expand...
Click to collapse
(Thx to @Phil_Smith @kessaras for pre-testing)
What: /sys/fs/f2fs/<disk>/gc_max_sleep_time
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the maximun sleep time for gc_thread. Time
is in milliseconds.
What: /sys/fs/f2fs/<disk>/gc_min_sleep_time
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the minimum sleep time for gc_thread. Time
is in milliseconds.
What: /sys/fs/f2fs/<disk>/gc_no_gc_sleep_time
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the default sleep time for gc_thread. Time
is in milliseconds.
What: /sys/fs/f2fs/<disk>/gc_idle
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the victim selection policy for garbage collection.
What: /sys/fs/f2fs/<disk>/reclaim_segments
Date: October 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the issue rate of segment discard commands.
What: /sys/fs/f2fs/<disk>/ipu_policy
Date: November 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the in-place-update policy.
What: /sys/fs/f2fs/<disk>/min_ipu_util
Date: November 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the FS utilization condition for the in-place-update
policies.
What: /sys/fs/f2fs/<disk>/min_fsync_blocks
Date: September 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the dirty page count condition for the in-place-update
policies.
What: /sys/fs/f2fs/<disk>/max_small_discards
Date: November 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the issue rate of small discard commands.
What: /sys/fs/f2fs/<disk>/max_victim_search
Date: January 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the number of trials to find a victim segment.
What: /sys/fs/f2fs/<disk>/dir_level
Date: March 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the directory level for large directory.
What: /sys/fs/f2fs/<disk>/ram_thresh
Date: March 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the memory footprint used by f2fs.
What: /sys/fs/f2fs/<disk>/trim_sections
Date: February 2015
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the trimming rate in batch mode.

what still WIP ??

Salman Al-Badgail said:
what still WIP ??
Click to expand...
Click to collapse
Was about to ask the same thing, if I remembered correctly I have seen a recovery released by OP supporting f2fs...... but anyway keep up the good work.

b886b said:
@oF2pks do U mean that with twrp 3.0.3 on your AFH, we will be able to flash AOSP 7 rom, gapps and supersu consecutively without the need to reboot recovery in between like that in cwm????
Click to expand...
Click to collapse
Salman Al-Badgail said:
what still WIP ??
Click to expand...
Click to collapse
First, just want to be sure everything works clear with ext4, for aosp6/7 + opengapps without any error/miss; then I'll upload a recoveryTWRP303.zip for CWM's users to easy install.
WIP: concerning f2fs, apparently there is an issue on cold boot to recovery and f2fs/data returns to ext4 (?!), also I did not try f2fs myself since I'm using Multirom with hidden 2nd Roms: I will soon (after I proceed my backups & AsusTF700->f2fs).
The p880-dev/X3/fs/f2fs is 2015Feb update (much better then AsusTF700!): "Controls the trimming rate in batch mode"; and I'm not sure on best mount options flags.
IMHO, most relevant will be to get fstab' [boot.img(1) + recovery.img(*3)]=4 in par for real testing, on this latest Omnirom based recovery303 ( the CM based 303 looks less accurate).

screen flickers
oF2pks said:
Download : https://www.androidfilehost.com/?fid=673368273298921729
Click to expand...
Click to collapse
Is it just me screen flickers when you press the navigation keys at the bottom?
Even worse is TWRP2.8.6_multirom_p880_20150523.img.
While the screen is perfectly stable in twrp-3.0.2-0-p880.img.

Sparkling! edition (ie wip)
Indeed, like twrpMR2.8.6, screen has some hiccups overlays, but works 100% OK.
Comparing to official twrp 3.0.2, both 2.8.6 & 3.0.3 don't load right framebuffer=3 ; I hope @fritzcola tell us more, also hard to get exact device tree (omni br. ?) from master @Dees_Troy .
Anyway it's remind which twrp being in use (versus nice official); also I remember an assertion on lightweight (? with possible lzma/ramdisk).
Code:
TWRP 3.0.2 graphics OKofficial[/U][/B]
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP 3.0.2-0 on Thu Dec 29 14:55:25 2016
(pid 136)
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/tegra-udc.0/gadget/lun0/file'
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:Got max brightness 255 from '/sys/class/leds/lcd-backlight/max_brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:LANG: en
[B]Starting the UI...Skipping adf graphics -- not present in build tree
Skipping drm graphics -- not present in build tree[/B]
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
[B]double buffered
[U]framebuffer: 3 (720 x 1280)[/U] #####instead of 0->flickering (?)######
Using fbdev graphics.[/B]

I initially voted for data + cache in f2fs, but after several testing I found that the cache does not need to be trimmed regularly so I suspect that only data in f2fs can have improve the performance of our device. I have tested for several cycles using the app fstrim for several weeks and it definitely helps in the way our phone performs, after fstrim our device is more snappy and the sluggish feel after long time usage has significantly decreased. However, whenever I run fstrim it always says that cache does not need to be trimmed so I believe the performance boost is due to the trimming of data partition which leads me to believe that the culprit of our sluggish performance was due to the cramming up of data partition. So I think data in f2fs would be enough.

2017 22 Jan update post#1 [.ZIP] attached
Thx to TeamWin, twrp 3.0.3 is a wip "live" edition for now : https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Soon or later TeamWin will push official p880 (non flickering) thread; while waiting, I will frequently update post#1 from latest github, with a :
-cwm compatible zip
-aosp7 OK with queueing list' zip
-f2fs-tools version1.4.1 (=aosp7=cm12.1)
-adb authorized
-(sparkling edition...)

[twrp 3.0.3] MultiROM : back in blue ! (2016-12-16)
@ze7zez , @juantech , @b886b
Thx to @fizbanrapper (github), no more twrp shove-it for roms kickflips : just focus on aosp7/cyospak7 on primary and flash (upRight burger) your favourites on 2nd (cm11/12/13 aosp6 lgJB omni4 beanstalk4...).
Download 3.0.3 (f2fs1.4.1) : https://www.androidfilehost.com/?fid=817550096634741392
Cyospak7 anykernel is compatible with aosp6 (15~20mn install/2ndRom !), and includes iodak fstab2 f2fs switch. I'll try to upgrade cm13 (only multiboots lgJB for now) with latest kexec soon; cm12.1/Nameless2 are already compatible.
Don't forget to flash the trigger MultiROM trampoline AND pressPOWER/till1stVIBER trick for 2nd/roms/non_shared_boot.img (specific to old p880 boot on/off process).
SuperSu.zip flash can be tricky, due to 2*reboot (via MultiROM): try 2.78sr5.zip+AppUpgrade2.79.apk, with aosp6 on 2nd. Xposed flash works fine.
Until now, basic rule was to flash highest android version on primary.
You tell me...

Hey oF2pks,
Does this recovery flash android 7 without any errors or problems.?
I will flash aosp 7.1 by csk1jw
Thnx

dave2609 said:
Hey oF2pks,
Does this recovery flash android 7 without any errors or problems.?
I will flash aosp 7.1 by csk1jw
Thnx
Click to expand...
Click to collapse
Yes indeed, latest twrp3.0.3 build is 2017-01-27 (MultiROM included), but on very new first install, you should always follow OP recommendations : until now @csk1jw is still on cwm6.0.4.5 & OpenGapps stock/WebView; you can still swap cwm/twrp recoveries later, but backups/nandroid are not compatible. Personally I prefer latest twrp3.0.3 and @Deltadroid modular Gapps packages.

Okay thnx,
But how to install aosp 7 by csk1jw
With this recovery?
Just normal procedure?

TWRP MultiROM 2017-02-20 & f2fs 1.6.1
New twrp-MultiROM-20170220 is now built with LineageOs13, f2fs-tools Ver: 1.6.1 (2016-03-22) & adb authorized
https://github.com/nkk71/Team-Win-Recovery-Project/commits/android-7.1-mrom
You can still download regular f2fs_Ver1.4.1 (aosp6/7 cm12.1) in post 1&2.

oF2pks said:
New twrp-MultiROM-20170220 is now built with Omni7.1.1, f2fs-tools Ver: 1.7.0 (2016-07-28) & adb authorized
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
You can still download regular f2fs_Ver1.4.1 (aosp6/7 cm12.1) in post 1&2.
Click to expand...
Click to collapse
Almost success! :good:
The interface in this version flickers occasionally.
But still flickers after the entry mode log.
Nevertheless, it should be a warning for people with photosensitive epilepsy.

red error 7 primary
oF2pks said:
New twrp-MultiROM-20170220 is now built with LineageOs13, f2fs-tools Ver: 1.6.1 (2016-03-22) & adb authorized
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
You can still download regular f2fs_Ver1.4.1 (aosp6/7 cm12.1) in post 1&2.
Click to expand...
Click to collapse
ze7zez said:
Almost success! :good:
The interface in this version flickers occasionally.
But still flickers after the entry mode log.
Nevertheless, it should be a warning for people with photosensitive epilepsy.
Click to expand...
Click to collapse
(One more miss,) sorry for that , I removed this untimely build which was buggy ; I wanted to upload another one (Lineage f2fs1.6.1) but error 7 was always back on aosp/primary: after multiple tests on my ok lucky last build twrp303MR2017-01-27.img (regular omni6 and f2fs 1.4), I noticed that switching from aosp6 to aosp7 on primary, could bring error7/system back on 3# zip flash. In this case, follow:
-wipe /system/data/cache (if error mount/system do => hard/keys cold reboot to recovery and repeat wipes)
-repair /system+/data+/cache
then you can flash up to ten zip consecutive+reboot in one action. (don't forget Cyospak7-2016 for MultiROM)
ALL THIS won't tamper your personal data & secondary roms.
I don't get how old cwm 6.0.4 can handle this (maybe e2fsk auto on fresh install?).
Also I didn't find a solution to get @alfsamsung / @iodak cm13 pass file system f2fs check on boot strange that both guys quit xda at same 2016-11-16 ?!)

oF2pks said:
...
Check attached 'install'.zip (to be flashed via cwm or twrp) file, for a more recent edition of twrp3.1.0-0 !
Built with Omnirom 6 repo, from unmodified bootable /TeamWin branch 7.1 (f2fs-tools v1.4)
More news: https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Click to expand...
Click to collapse
New twrp 3.1.0 2017 03 07, check post#1 attached zip

oF2pks said:
New twrp 3.1.0 2017 03 07, check post#1 attached zip
Click to expand...
Click to collapse
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

f2fs 1.7 post#3 (adb/authorized)
For futur? roms only : post#3 updated with unmodified 2017-03-08 TWRP 3.1.0 and f2fs 1.7 (Omnirom7.1) (adb/authorized).
https://github.com/omnirom/android_external_f2fs-tools

root MEDION Life P5006 Lenovo B5032 failed

I tried to install in said mobile phone in TWRP SuperSU-v2.82-201705271822.zip. Unfortunately this fails - see log.
(adb logcat -d | find /i "installer" > logcat.txt has only Zero logcat.txt. "adb logcat" only -> logcat read failure)
The attempt to install systemmode (SR5-SuperSU-v2.82-SYSTEMMODE.zip) was successful in TWRP but after that the smartphone does not start anymore - it hangs in the bootlogo.
I would like to install SuperSU-v2.82-201705271822.zip - Please help!!!
TWRP is Port from Unofficial_TWRP_v3.1.1-0_For_MT6735_64-bit_3.18.19+_Kernel.img and the original recovery.bin (Tutorial: www.chinaphonearena.com/forum/Threa...752-MT6753-MT6795-MT6797-TWRP-MT67xx-tutorial) TWRP is running and backup in TWRP is ok.
Hardware & Software
-CPU-
SoC Modell: MediaTek MT6735
Kern Architektur: 4xARM Cortex-A53 @ 1300MHz
Befehlssatz: 64-bit ARMv8-A
CPU Kerne: 4
Unterstützte ABIs : (32-bit) armeabi-v7a, armeabi (64-bit) arm64-v8a
AES NEON SHA1 SHA2 : Unterstützt
Build ID : L1288.6.02.05
Baseband : MOLY.LR9.W1444.MD.LWTG.MP.V79.P7,2017/03/27 17:07
Kernel Vision : Linux version 3.18.19+ ([email protected]) (gccversion 4.9.x-google 20140827 (prerelease) (GCC))#1 SMP PREEMPT Mon Jul 10 17:31:07 CST 2017
-SYSTEM-
Hersteller : Lenovo
Modell/Gerät/Produkt : B5032
Marke : MEDION
Hardware/Platform : mt6735
SerienNr.: 11250061740012590
Android ID : 2d76aadb59596ab1
-OS-
Version : 6.0 Marshmallow
API Level : 23
Android Security Patch LVL : 2017-05-05
Fingerprint : MEDION/B5032/B5032:6.0/MRA58K/L1288.6.02.05:user/release-keys
Build ID : MRA58K

card0384 said:
I tried to install in said mobile phone in TWRP SuperSU-v2.82-201705271822.zip. Unfortunately this fails - see log.
(adb logcat -d | find /i "installer" > logcat.txt has only Zero logcat.txt. "adb logcat" only -> logcat read failure)
The attempt to install systemmode (SR5-SuperSU-v2.82-SYSTEMMODE.zip) was successful in TWRP but after that the smartphone does not start anymore - it hangs in the bootlogo...
Click to expand...
Click to collapse
I don't have this device but, the following thread may be helpful to you.
https://forum.xda-developers.com/showthread.php?t=3337484
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Hello, thanks for your Support. This link cannot fixed my Problem, sorry

Maybe chainfire can look at the logs, I've uploaded all the needed ones

card0384 said:
Maybe chainfire can look at the logs, I've uploaded all the needed ones
Click to expand...
Click to collapse
ChainFire has retired from SuperSU development/support.

as is great, I found the mistake and the solution. The TWRP I used was executable but somehow not right. I have another TWRP used as the basis for porting, so read SuperSu install fine. Class - I have rooted my first cell phone without instructions - I put the instructions for this for other interested in the net

[ATT][Stock XML] OCXS27.109_47_17 .xml.zip grabbed from Lenovo Smart Assistant

GDrive: NASH_ATT_OCXS27.109_47_17_subsidy_ATT_regulatory_DEFAULT_CFC.xml.zip
(if anyone can mirror ill put it here)
ATT Oreo Stock update XML official no repack
MD5: 96ed38b40b88be0a45033e3da13c2032
I used rootjunky's XML to Batch script
Quick and dirty tutorial for the precious newbs:
1) extract both fw and script.
2) copy contents of "Place_Extracted_Firmware_Here" to the inside of the " NASH_ATT_OCXS27.109_47_17_subsidy_ATT_regulatory_DEFAULT_CFC.xml" folder
3)
A) for a full erase and flash flashfile.bat run "2-rsd-flash-flashfile-windows.bat" from the firmware folder then run "flashfile.bat"​B) for just the firmware (no data and cache erase) use "1-rsd-flash-servicefile-windows.bat" then run "servicefile.bat"​C) CHECK FOR ERRORS, IF THERE WAS A BOOTLOADER UPDATE YOU MAY NEED TO RUN TWICE​OR MANUALLY FLASH BOOTLOADER .IMG​( run "fastboot flash bootloader bootloader.img" from cmd in fw folder )​ 4) ????
5) Profit!
Details:
BUILD REQUEST INFO:
SW Version: nash_att-user 8.0.0 OCXS27.109-47-17 23 release-keysM8998_20207.117.02.41
MBM Version: MBM-3.0-nash_att-9869834-181102
Modem Version: M8998_20207.117.02.41
FSG Version: FSG-8998-02.37
Build Fingerprint: motorola/nash_att/nash:8.0.0/OCXS27.109-47-17/23:user/release-keys
CQATest App Version: 6.0.1
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 27.241.23.nash_att.att.en.US
Model Number: Moto Z (2)
Android Version: 8.0.0
Baseband Version: M8998_20207.117.02.41
Build Id: OCXS27.109-47-17
SW Display Build ID: OCXS27.109-47-17
Build Date: Fri Nov 2 09:57:17 CDT 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_att_v1.5.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.27.241.23.nash_att.att.en.US
Version when read from CPV: nash_att-user 8.0.0 OCXS27.109-47-17 23 release-keys
AB Update Enabled: True
Full Treble Enabled: False
buy me a slice?

Thanks, this worked great!
I have a Moto Z2 that wouldn't OTA update because it was getting picked up as a XT1601 SKU, but this method worked and I didn't lose any data or have to reinstall any apps!

is it working on sprint?

ltqkiet said:
is it working on sprint?
Click to expand...
Click to collapse
You can flash a newer firmware without losing any installed with flashall.bat.
If I don't mistake, it is the line "fastboot erase userdata" or "fastboot -w".
Remove these lines in flashall.bat won't remove any apps.
Just open flashall.bat with notepad and check. On CMD you can type "fastboot" and hit enter to see what does "-w" mean.

*Working Great[Flyme 7 Erfan GSIs Global] [Android 9][Thanks Vega]

Special thanks to Vega from O grupo de discussões sobre tecnologia e outras coisas!
Information:
Android Version: 9
Brand: meizu
Model: meizu note9
Codename: meizunote9
Build Type: K81923AA1-user
Build Number: PKQ1.181203.001
Incremental: 1552448469
Tags: release-keys
Security Patch: 2019-02-01
Fingerprint: meizu/meizu_note9/meizunote9:9/PKQ1.181203.001/1552448469:user/release-keys
Description: meizu_note9-user 9 PKQ1.181203.001 1552448469 release-keys
Raw Image Size: 2.40 GiB
==============================
Downloads: ARM64 Aonly (https://drive.google.com/file/d/1kc2sDvAh1TX-HWem2Hp5eLKNp-JIqgLC/view?usp=sharing)
===============================
Bug: from my vendor ====NO SIM DETECTED====
==================================
Not Support: exFAT
Step
1. flash latest Firmware https://mega.nz/#!QDplSYab!mrB5f8875VghQHfrrGvid4iJICMopkq3anZCipLWzqo
2. flash Vendor https://mega.nz/#!ECAG1aIS!OuGf9eVoiJpg0xreeLIarAWs5GkuCbu9AwR95MSlO-g
3. flash GSI as System Image
4. flash Permissiver v4.zip https://mega.nz/#!ETIwHQJC!Go5NfpgXFy5gPw8gFG8JbUCch7Eijw4rDp3NVTkhd-M
5. flash Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip https://mega.nz/#!gTohmQaR!ZL5jCeatYXUzUMx_moJseJ9o7b1RoLUf3o_PfOtn_aw
6. flash DisableForceEncryption_Treble_v20.1.zip https://mega.nz/#!BHgRWYDS!jfuIRqTPTjS_lVy2tfpSbVRfqmxqqadeLFttgbKmhYQ
7.Reboot
First Boot
-System is upgrading.
-update GMS https://www.apkmirror.com/apk/googl...0400-282600551-android-apk-download/download/
-------------------------------------
-Edit /system/build.prop ( for Fixing Enable Bluetooth audio media )
enter inside twrp, mount system (and unmark option "mount system as read only"), go to advanced, terminal and write:
echo "persist.vendor.btstack.a2dp_offload_cap=false" >> /system/build.prop
echo "persist.vendor.btstack.enable.splita2dp=false" >> /system/build.prop