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

[oF2pks]

(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

 

[oF2pks]

[EXP] Multirom33 TWRP3.1.1 +TrampolineV27 +MultiROMMgr.apk with No-Kexec work-around

Credits ( @mkasick ) @Tasssadar https://xdaforums.com/showthread.php?t=2104706
p880 ( @Adam77Root ) @Demetris @fritzcola https://xdaforums.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://xdaforums.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

 

[oF2pks]

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.

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 ;

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 (root@nn-pc) (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 ....

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 (root@nn-pc) (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.

(Thx to @Phil_Smith @kessaras for pre-testing)

What: /sys/fs/f2fs/<disk>/gc_max_sleep_time
Date: July 2013
Contact: "Namjae Jeon" <namjae.jeon@samsung.com>
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" <namjae.jeon@samsung.com>
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" <namjae.jeon@samsung.com>
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" <namjae.jeon@samsung.com>
Description:
Controls the victim selection policy for garbage collection.

What: /sys/fs/f2fs/<disk>/reclaim_segments
Date: October 2013
Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
Description:
Controls the issue rate of segment discard commands.

What: /sys/fs/f2fs/<disk>/ipu_policy
Date: November 2013
Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
Description:
Controls the in-place-update policy.

What: /sys/fs/f2fs/<disk>/min_ipu_util
Date: November 2013
Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
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" <jaegeuk@kernel.org>
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" <jaegeuk.kim@samsung.com>
Description:
Controls the issue rate of small discard commands.

What: /sys/fs/f2fs/<disk>/max_victim_search
Date: January 2014
Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
Description:
Controls the number of trials to find a victim segment.

What: /sys/fs/f2fs/<disk>/dir_level
Date: March 2014
Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
Description:
Controls the directory level for large directory.

What: /sys/fs/f2fs/<disk>/ram_thresh
Date: March 2014
Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
Description:
Controls the memory footprint used by f2fs.

What: /sys/fs/f2fs/<disk>/trim_sections
Date: February 2015
Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
Description:
Controls the trimming rate in batch mode.

 

[Salman Al-Badgail]

what still WIP ??

 

[b886b]

what still WIP ??

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.

 

[oF2pks]

@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????

what still WIP ??

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).

 

[ze7zez]

screen flickers

Download : https://www.androidfilehost.com/?fid=673368273298921729

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.

 

[oF2pks]

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).

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]

 

[b886b]

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.

 

[oF2pks]

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...)

 

[oF2pks]

[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...

 

[dave2609]

Hey oF2pks,

Does this recovery flash android 7 without any errors or problems.?

I will flash aosp 7.1 by csk1jw

Thnx

 

[oF2pks]

Hey oF2pks,

Does this recovery flash android 7 without any errors or problems.?

I will flash aosp 7.1 by csk1jw

Thnx

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.

 

[dave2609]

Okay thnx,

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

 

[oF2pks]

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.

 

[ze7zez]

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.

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.

 

[oF2pks]

red error 7 primary

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.

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.

(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]

...
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

New twrp 3.1.0 2017 03 07, check post#1 attached zip

 

[ze7zez]

New twrp 3.1.0 2017 03 07, check post#1 attached zip

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

 

[oF2pks]

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