Related
This is a small mod for Sultanxda's CAF kernel. It's intended to ONLY be used with his CM 12.1 and his CM13, but it *might* work with other CAF ROMs.
The zip also replaces the fstab in the ramdisk to support the F2FS filesystem in /data and /cache (both ext4 and f2fs are supported for these, like the official CM builds), and the fsck.f2fs binary in /system/bin to the latest version (1.5.0).
The only kernel changes are:
- Added F2FS filesystem code. I keep it up-to-date with the Motorola github (right now the latest code is from the Moto X 2014 6.0 release): https://github.com/MotorolaMobilityLLC/motorola-kernel/tree/marshmallow-6.0.0-release-victara.
- Added and improved @sollapse's OTG-Y support patch.
- Eventual cherry picked commits from @sultanxda's Marshmallow branch.
- Updated CIFS/NFS code to the latest 3.4 version.
- Improved support for HIDs (joysticks, keyboards, etc.)
I compiled with GCC 4.8 (the same toolchain @sultanxda uses).
All the mods have been tested and I'm using them personally.
To install, you just need to flash his ROM, and then my zip. Then format /data and /cache to F2FS with TWRP if you wish to use F2FS.
I also made a recovery based on the 2.8.7.0-4 unofficial TWRP, it's rebased on the Sultan CM12.1 ROM and this kernel mod, plus it has:
- updated TWRP code (from the 5.1 branch)
- mounts /data and /cache as F2FS by default, with the same mount options as the fstab in my kernel mod
- theme replaced with the "Materialised Play" one
- updated mkfs.f2fs and fsck.f2fs to 1.5.0.
I included all the source code for the kernel changes, you only need to replace the GCC directory in the bash script and then execute it.
Changelogs:
01/13:
- Updated Sultan's kernel sources for CM13 and CM12.1.
- Updated NFS driver to the latest 3.4 code.
- Merged Sultan's charger improvements to the CM12.1 kernel.
- Enabled support for Force Feedback for a lot of controllers - you can enable this in Input.
- Enabled LED and Force Feedback support for the Xbox controllers (fixes the LED blinking forever).
- Fixed Wiimote support - sadly we can't have support for newer Wii Remotes (the "MotionPlus" ones) with a 3.4 kernel, but older ones are working.
- Cherry picked HID commits from the official CyanogenMod kernel, this improves the Wiimote support (Classic Controllers, Nunchucks etc. are supported) and adds/improves support for a lot of joysticks/keyboards/mice/etc.
01/05:
- Updated Sultan's kernel sources for CM13 and CM12.1.
12/30:
- Updated the F2FS driver with the one from Motorola's 6.0.0 release for Moto X 2014 (it's a couple months newer).
- Updated the fstab accordingly, the "nobarrier" option should bring a small performance improvement.
12/29:
- Actually fixed reboots when inserting OTG-Y devices in deep sleep.
- Fixed OTG-Y not starting when the charger is detected *prior* to the USB device (rare cases in which a charger/OTG-Y setup is disconnected and the driver takes a bit to detect that, and an OTG-Y setup is inserted before that).
12/23:
- Updated Sultan's kernel sources for CM13 (fixes inserting OTG devices in deep sleep and being unable to use USB again).
- Fixed reboots when inserting OTG-Y devices in deep sleep (thanks to the above patch!).
- Further clean-up of the OTG-Y patch code.
12/21:
- OTG-Y improvements and general clean-up. Code is cleaner, some race conditions and corner cases when toggling the parameter are handled better, low power mode is enabled when it's possible, and the charging notification going off, on and off again very fast sometimes after unplugging an OTG-Y setup has been fixed.
- Updated Sultan's kernel sources for CM13 and CM12.1
12/16:
- Overhaul of the OTG-Y patch. Now it's less "hacky" and it detects the charger properly. This removes the false charging notifications when connecting a regular OTG cable+device, makes it possible to use OTG again if charging is stopped and restarted, allows for faster charging rates, and fixes kernel panics when the OTG-Y cable/device are removed *after* charging was stopped.
- Updated Sultan's kernel sources for CM13 and CM12.1 (slow charging fixed)
12/12:
- Improved the OTG-Y patch (again): if you mistakenly connected a regular OTG cable+device when OTG-Y was set to Yes, a charging notification would be shown, and it wouldn't go away after disconnection. Now it properly disappears after the device has been disconnected.
12/10;
- Updated Sultan's kernel sources for CM13 and CM12.1 (including a couple changes still not present in the 12/1 CM12.1)
- Merged some changes from the CM13 kernel into the CM12.1 one: 1 2
- Improved the OTG-Y patch. It's now possible to charge the phone normally in AC mode while the OTG-Y parameter is set to Yes, and there are no more kernel panics or inability to use OTG up to the following reboot when you use OTG-Y inappropriately (disconnecting the OTG devices after changing the parameter status).
- Updated f2fs.fsck in the CM12.1 version and the init.rc in the CM13 version.
12/01:
- Updated Sultan's kernel sources for CM13 and CM12.1
11/28:
- Switched the F2FS code to the Motorola Moto G 5.1.1 F2FS branch: https://github.com/MotorolaMobilityLLC/motorola-kernel/tree/lollipop-5.0.2-release-falcon
- Updated Sultan's kernel sources for CM13
- Merged the new touchscreen fixes and CPU boosting logic to the CM12.1 kernel from the CM13 one.
Important: I'd recommend making a nandroid backup, formatting and restoring. This driver is technically older than upstream, and it might have issues with inlined dentries (the new fstab reflects the mount point configuration of the Moto X 2014 - so no inline_dentry).
11/25:
- Bug fix for F2FS from the dev-test branch
- Updated Sultan's kernel sources for CM13
- Included the touch screen bugfix from Sultan from the CM13 branch in the CM12.1 one.
11/18:
- Added other bug fix commits for F2FS from the dev-test branch
- Updated Sultan's kernel sources for both CM12.1 and CM13
- CM13 build should actually be functional now (thanks to @DerRomtester for the init.rc)
- Recovery has been rebuilt from sources, it now uses the Sultan CM12.1 kernel mod and source tree for his ROM.
11/10:
- Added two bug fix commits for F2FS from the dev-test branch (one of them is a fix to potential data corruption)
- Switched to CM's version of Google GCC
XDA:DevDB Information
Mod for Sultanxda's CAF kernel, Kernel for the OnePlus One
Contributors
Phoenix Wright
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 01/13
Stable Release Date: 2016-01-13
Created 2015-11-07
Last Updated 2016-01-13
Have you already tried marshmallow with f2fs? I dont get it working. Cache on f2fs is bootlooping and data on f2fs shows that the phone is encrypted. And it wants a pw. to decrypt it.
DerRomtester said:
Have you already tried marshmallow with f2fs? I dont get it working. Cache on f2fs is bootlooping and data on f2fs shows that the phone is encrypted. And it wants a pw. to decrypt it.
Click to expand...
Click to collapse
I'm not that interested in marshmallow right now (I'll wait until things get stable and xposed is ported over). Have you checked that the fstab is edited properly?
Phoenix Wright said:
I'm not that interested in marshmallow right now (I'll wait until things get stable and xposed is ported over). Have you checked that the fstab is edited properly?
Click to expand...
Click to collapse
The fstab should be ok. I use the same kernel in 5.1.1. I will inform you if i get it working. It is time to debug.
Hey am still facing the same error upon attempting to mount cifs. I believe it's not due to your mod but some dumb thing I might be missing. Can you post using what tools you mount cifs using the command you specified on the sultan thread?
UPDATE I tried using adb shell(which i guess you would've) and still get the same "No such device" error. dmesg doesn't show anything useful (atleast to my knowledge). But 'cat /proc/filesystems' does NOT show cifs(it does show f2fs). Is it normal?
Sent from my A0001 using Tapatalk
Links?
j1i2a3n4g5 said:
Links?
Click to expand...
Click to collapse
Check the downloads tab / section... Not sure if it works on tapatalk.
Sent from my A0001 using Tapatalk
Added to OnePlus One index thread:
[INDEX] OnePlus One
Added to OnePlus One index thread:
[INDEX] OnePlus One
Phoenix Wright said:
I'm not that interested in marshmallow right now (I'll wait until things get stable and xposed is ported over). Have you checked that the fstab is edited properly?
Click to expand...
Click to collapse
I tried sultans mm version with f2fs. And this log looks quite interesting. I am running f2fs on cache and data but it is looking for ext4.
Code:
EXT4-fs (mmcblk0p14): mounted filesystem with ordered data mode. Opts: barrier=1
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/system,target=/system,type=ext4)=0
EXT4-fs (mmcblk0p28): VFS: Can't find ext4 filesystem
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/userdata,target=/data,type=ext4)=-1
fs_mgr: fs_mgr_mount_all(): possibly an encryptable blkdev /dev/block/platform/msm_sdcc.1/by-name/userdata for mount /data type ext4 )
EXT4-fs (mmcblk0p16): VFS: Can't find ext4 filesystem
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/cache,target=/cache,type=ext4)=-1
fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/platform/msm_sdcc.1/by-name/cache at /cache options: barrier=1,data=ordered,noauto_da_alloc,errors=panic error: Invalid argument
EXT4-fs (mmcblk0p15): recovery complete
EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/persist,/persist,ext4)=0: Success
fs_mgr: check_fs(): unmount(/persist) succeeded
fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck: e2fsck 1.42.9 (28-Dec-2013)
e2fsck: /dev/block/platform/msm_sdcc.1/by-name/persist: clean, 29/320 files, 1088/1280 blocks
EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic
Edit i know the problem already
I guess it is a ramdisk problem
ramdisk/sbin/mkfs.f2fs
/system/bin/fsck\.f2fs
Formatting fo f2fs takes a long time
I tried it with the latest 12.1 ROM from 01112015 and it works very fast!
When there's trick to do it with the 6.0 ROM I will try.
ph1dft said:
I tried it with the latest 12.1 ROM from 01112015 and it works very fast!
When there's trick to do it with the 6.0 ROM I will try.
Click to expand...
Click to collapse
It works with my (Tyr) kernel and Sultans CAF 6.0 Rom.
DerRomtester said:
I tried sultans mm version with f2fs. And this log looks quite interesting. I am running f2fs on cache and data but it is looking for ext4.
Code:
EXT4-fs (mmcblk0p14): mounted filesystem with ordered data mode. Opts: barrier=1
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/system,target=/system,type=ext4)=0
EXT4-fs (mmcblk0p28): VFS: Can't find ext4 filesystem
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/userdata,target=/data,type=ext4)=-1
fs_mgr: fs_mgr_mount_all(): possibly an encryptable blkdev /dev/block/platform/msm_sdcc.1/by-name/userdata for mount /data type ext4 )
EXT4-fs (mmcblk0p16): VFS: Can't find ext4 filesystem
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/cache,target=/cache,type=ext4)=-1
fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/platform/msm_sdcc.1/by-name/cache at /cache options: barrier=1,data=ordered,noauto_da_alloc,errors=panic error: Invalid argument
EXT4-fs (mmcblk0p15): recovery complete
EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/persist,/persist,ext4)=0: Success
fs_mgr: check_fs(): unmount(/persist) succeeded
fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck: e2fsck 1.42.9 (28-Dec-2013)
e2fsck: /dev/block/platform/msm_sdcc.1/by-name/persist: clean, 29/320 files, 1088/1280 blocks
EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic
Edit i know the problem already
I guess it is a ramdisk problem
ramdisk/sbin/mkfs.f2fs
/system/bin/fsck\.f2fs
Click to expand...
Click to collapse
interesting, when I use disc info (without executing the ramdisk command) I see that both /data and /cache are show as f2fs. Curious to know if you still belief it is nessesary to solve the ramdisk problem?
---------- Post added at 02:44 PM ---------- Previous post was at 02:42 PM ----------
A question for everyone, why would you chose for f2fs on /data has it not be shown that f2fs is not faster than ext4 on /data and only has benefit on /cache?
joefso said:
interesting, when I use disc info (without executing the ramdisk command) I see that both /data and /cache are show as f2fs. Curious to know if you still belief it is nessesary to solve the ramdisk problem?
---------- Post added at 02:44 PM ---------- Previous post was at 02:42 PM ----------
A question for everyone, why would you chose for f2fs on /data has it not be shown that f2fs is not faster than ext4 on /data and only has benefit on /cache?
Click to expand...
Click to collapse
Already solved the ramdisk problem.
I think the benchmarks on android are similar. http://www.phoronix.com/scan.php?page=article&item=linux-40-ssd&num=2
Also Antutu scores are proofing that.
DerRomtester said:
It works with my (Tyr) kernel and Sultans CAF 6.0 Rom.
Click to expand...
Click to collapse
Tried the rom and it works, but not for daily use. Multirom and f2fs doesn't seem to work so back to 5.1.1. Thanx anyway!
sorry where is the download link?
manup85cupra said:
sorry where is the download link?
Click to expand...
Click to collapse
The links are on Downloads tab. Don't use Tapatalk though. This was discussed a few posts above yours.
I added a new version. I just added two bug fix commits for F2FS from the dev-test branch (one of them is a fix to potential data corruption), and switched to CM's version of Google GCC (previously I used the one from the Google repos).
Also, I added a version for CM13. Functionality of the kernel is the same (latest CIFS, UTF8, latest F2FS & fstab, OTG-Y). However, I don't use CM13 yet so I'd need testing This zip *doesn't have* an updated "fsck.f2fs" binary, as that would require downloading the CM13 source tree (25GB) and I can't do that. I'll do it when I switch to CM13. @DerRomtester I saw your kernel replaces the whole boot.img, I don't think it's wise to do (the ramdisk contains some binaries - adbd, the sepolicy binary etc. and configuration files which get updated frequently). You can use my script to automate fstab replacement if you want!
Hey @PhoenixWright I used your command
Code:
busybox mount -t cifs -o username=xxxx,password=yyyyy,rw,noatime,iocharset=utf8,noperm,nounix,noserverino,sec=ntlmssp,dir_mode=0775,file_mode=0775,uid=1023,gid=1023,context=u:object_r:fuse:s0 //192.168.x.x/yourshare /data/media/0/CIFS
after flashing your latest zip. While it mounts without any errors, the folders are not visible on any file manager.
But i can cd into the directory from terminal and it displays the files.
Any suggestions to get it viewable on file managers?
Since the unnofical thread of TWRP is now closed decided to create my own thread
of my TWRP builds. started this for quite some long.
This TWRP make backup of EFS and can handle firmware files properly.
For more features you can read the change logs, you will fint all there.
All this would not be possible without Omnirom Team guys that work on the recovery part of Omnirom, yes, my TWRP is build based on Omnirom recovery tree.
As for the device tree, the one used its the one from CM13 to our device. To see the changes go to is gerrit / github of Omnirom and CyanogenMod.
Big thanks to all of you guys.
Also would thanks to @ketut.kumajaya and @katinatez , because on my device before starting to make my own builds of TWRP was using is builds for quit long time on my device.
Latest build: ( check seconf post for older builds )
https://www.androidfilehost.com/?w=files&flid=50417
Reserved
TWRP 3.2.1-1-TugaPower 2017-12-10 ( testing )
ADB Backup: Fixup
adds /persist/time/ as Qualcomm time fix source
Process AOSP wipe commands prior to encryption check
Please report some problems if you find since its first release.
Nandroid restore should be working since its fixed on TWRP source
Stuff that need to be tested:
wipe cache and dalvik and see if its slower then before or same as before, test restoring nandroid, test nandroid backup, test flash rom, see how aroma its working, test encryption
If someone go trough this tests please report how its working. ( doing nandroid as we speak and going to restore an older nandroid)
Wipe cache and dalvik for me it seems fast enought but more opinions its welcome.
https://www.androidfilehost.com/?fid=817906626617951858
TWRP 3.1.1-5-TugaPower 2017-09-19
Fixed encryption
https://www.androidfilehost.com/?fid=961840155545597147
TWRP 3.1.1-4-TugaPower 2017-09-17
Fixed slow format of cache
https://www.androidfilehost.com/?fid=673368273298986645
TWRP 3.1.1-3-TugaPower 2017-09-17
Remove duplicate entries & Improve Chinese translation
Fix typos / inconsistencies in German language
SHA2: Enable in landscape and watch xml
Show scrollbar on TWRP Settings
twrpTar: Fix uninitialized current_archive_type
TWRP 3.1.1-2-TugaPower 2017-07-09
backup: fix return handling when no digest is being created
libtar: Fix restore of e4crypt policies
TWRP 3.1.1-1-TugaPower
Fix incorrect 'unlink' return value check
twrpDigest refactor
Fix minui issues for some build trees
ors: Update doc
Improve decrypted partition logging
adbbackup: write smaller reads less than 512 bytes
Fix various memory errors
cryptfs: Remove dm-crypt device on failed table load
TWRP 3.1.1-0-TugaPower
fix logic of TW_USE_MINUI_CUSTOM_FONTS
etc: remove "." from LD_LIBRARY_PATH
mtdutils: Fix mounting partitions by-name
gui: fix line wrapping in terminal, issue #876
3.1.1
TWRP 3.1.0-5-TugaPower
Fix reboot when no OS is present
Complete support for project pathmap
Improve automatic detection of QCOM RTC fix
Adopted Storage: backup keys but do not wipe them
ADB Backup: fix adb restore issues
TWRP 3.1.0-4-TugaPower
Fixed slow formating
Fixed encryption
TWRP 3.1.0-3-TugaPower
Fixed make_ext4fs formatting partitions
TWRP 3.1.0-2-TugaPower
Fixed aroma graphics
TWRP 3.1.0-1-TugaPower
Revert "Fix adb shell in 7.0 tree"
file_contexts: remove symlink to binary file and use text version instead
vold_decrypt: Add back missing xml and get rid of compiler warning
Add TWRP app install to landscape and watch themes
crypto: Use system's vold for decryption
Fix missing libf2fs.so needed by mkfs.f2fs
ADBBU: Cleanup string usage/namespace
Timeout for decrypt
gui: preserve order of gui_print vs gui_msg
languages: update chinese translation
Update Hungarian localization
Tweak MTP startup routine
Fix handling of USB config during MTP switching
twrpDigest: don't crash when zip.md5 file is empty
logd: add seclabel so that service runs in 7.1 tree builds
Use LOGI/LOGE for non-EVENT_LOGGING events
Run language_helper.py from inside languages dir
Update MTP debugging tags
Do not unconditionally remove MTP storage on unmount
Only change USB mode to mtp when ready for MTP
build: [FIXUP] Addendum for BusyBox get/setprop & API 24 vs 25
Fix "ordered comparison between pointer and zero".
Update Russian localization
cryptfs: Fix encryption issue due to stack corruption.
Add a listxattr tool for listing xattrs
libtar: support backing up and restoring new Android user.* xattr
Partition: Remove unused has_data_media variable
GUI: Fix typo in warning message
Symlink file_contexts --> file_contexts.bin
Fix bldr msg file open mode when offset specified
DE language update
Gottardo - languages: update italian translation
Update ru.xml for TWRP ver. 3.0.3.0
Improve backup display names with emulated storage
Fix crash during check for TWRP app
Fill uid/gid for screenshots at compile time
GUI: Improve automatic determination of TW_THEME
Allow custom bootloader msg offset in block misc
gui: Fix Android.mk for TW_CUSTOM_THEME
recovery: adjust mkfs.f2fs location
orscmd: add minimal getcap and setcap tools
Support power key on slideout
Whitespace cleanup in Themes
Disable relocations on orscmd to fix compile error in Omni 7.1
ifdef overlay graphics
Try mounting different filesystems during decryption
Add another license header
Fix detection of TWRP app in /data
gui: bump theme version to 2
bldrmsg: Only emmc /misc is supported
gui: Initialize button render position
HardwareKeyboard: Update event logging
GUI: Mark local flip() function as static
fb2png: Update/Cleanup headers
init: Remove duplicate trigger of load_system_props_action
Add missing file descriptor closes
Restore TW_BACKUP_AVG_IMG_RATE handling
Move sh selection out of GUI makefile
Move pigz symlinks out of GUI makefile
Add missing license headers
flashutils: additional emmc check
gui: Actions: Toggle backlight on power key
SELinux can be assumed for Android 4.4+
Restore file system type logline on restore
Do not disable performance mode too early for backup
Unused variable cleanup
Very minor code cleanup
Whitespace cleanup
gui: remove old unmaintained 2.x theme
libtar: backup and restore posix capabilities
ADBbackups: Fix wrong owner on binary backups.
Include symlink size (path length) in Get_Folder_Size()
gui: Detect device resolution with TARGET_SCREEN_HEIGHT/WIDTH
TWRP device version string
build: AOSP/CM14 fixes (API 24/25, mainly BusyBox-less environment)
updater: link libcrypto_utils_static if it exist
libtar: Use relative path for crypto/ext4crypt include
bootloader_message: Allow TWRP to ignore wipe-data command into misc
Support theme width and height offsets
build: Consolidate the crypto_utils presence tests
Fix compile error on 4.4 tree
Adjust & Improve Chinese translations for zh_CN/TW again
TWRP 3.0.3-5-TugaPower
Fixed bug intruduced on -4 on handling busybox callings
TWRP 3.0.3-4-TugaPower
Change version to 3.0.x to support the app release
Update Ukraine language translation
Add TWRP app install via TWRP recovery ( you can disable the prompt on settings )
TWRP Language Update
Change handling of /cache due to AB devices not having cache
Support backup/restore of FBE policies
Support File Based Encryption
Add boot slot support
Support new AB OTA zips
Improve backup & wipe exclusion handling
To the ones that have problem before on -3 report if all its fine on your side now....
TWRP 3.0.3-3-TugaPower 20-11-2016
Check if mount point is dir during startup
MD5 verification sanity
Fix libcrypto dependency in 6.0 trees
Clean up PartitionSettings
Fix compressed backups with split archives
twrp: Use the correct lib name
MD5 checking: fix issues introduced with adb backup patchset
Make naming scheme more meaningful
Fix compatibility across the board
Fix compatibility with 5.1
Make it backwards compatible with 4.4
TWRP 3.0.3-2-TugaPower 30-10-2016
Fixed the bug intruduced on 3.0.3-0 and 3.0.3-1 formating partitions.
Fixed log error on flashing Nougats ROMs
Added kernels logs as option to copy Logs options
Aroma support
Added Chinese/Japanese as availables languages
Improved image file flas
TWRP 3.0.3-1-TugaPower
Fixed/tweacked little more aroma bug intruduced on TWRP 3.0.3-0-TugaPower
TWRP 3.0.3-0-TugaPower
Fixed log error flashing Android N ROMs
updater: link libcrypto_utils_static if it exist
Copy Kernel Logs
libminiadbd: fix libadbd undefined reference to 'android_pubkey_decode' functions when build in cm-14.0
link libcrypto_utils.so to libminiadbd.so
Fix libcrypto dependency in 6.0 trees
twrp: Use the correct lib name
TWRP 3.0.2-6-TugaPower
Fixed bug introduced on 3.0.2-5 that will fail flashing boot and recovery images files from built in option on TWRP
If you are on 3.0.2-5 you will need to flash with fastboot or use some thirdy app.
TWRP 3.0.2-5-TugaPower
Fixed EFS backup/restore ( tested )
Removed recovery from backup list
Give another go at aroma zips
Clean up PartitionSettings
Fix compressed backups with split archives
Fix restore of subpartitions
MD5 checking: fix issues introduced with adb backup patchset
Added Chinese/Japanese as availables languages
TWRP 3.0.2-4-TugaPower
Added modem and recovery also as backup partitions
minui: Fix gr_set_font() build issue on cm-13.0 tree
NTFS-3g: migrate to PLATFORM_SDK check instead
Gui: replace pow() function
wait for cryptfs device node to come up
Add git revision to startup message in recovery.log
GUI: Use standard routine for auto-reboot
Fixup reboot after install variables
GUI: Add countdown & cancel to install auto-reboot
Finish creating disable_free_space_check variable
Allow running of a custom script after factory reset
Add build flag for forcing single buffer mode
Make input whitelist and blacklist work for mouse devices too
recovery: allow usage of TARGET_CRYPTFS_HW_PATH
bigbiff - Fix md5 creation from adb backup patch
adbbu: fix include path
Optimize and reduce size of PNG files
Add typecode to sgdisk for proper detection in Android
Remove curtainClose() remnants
Remove unused identifier from NotifyTouch
Move cursor after appending date to backup name
gui: fix Enter key in terminal
ADB: Add adb backup for TWRP
Increase EIO retry count
Check the results from applypatch
applypatch: Don't call inflate() when it expects zero-length output
Log source/target build version to last_install
Black screen patch for some HiSilicon devices (FBIOPAN_DISPLAY)
recovery: Make wear recovery more customizable
TWRP 3.0.2-3-TugaPowe
GUI: Use standard routine for auto-rebot
GUI: Add countdown & cancel to install auto-reboo
HACK: Fix AROMA Graphic
updater: Add LZMA support to blockim
Allow restore to read-only partition, part 2
Move force_rgb_565 up
crypto: remove redundant convert_key_to_hex_ascii call
TWRP 3.0.2-2-TugaPower
Fix flash of img files introduced on 3.0.2-1 ( boot / recovery )
Revert: Fixup reboot after install variables
revert: libenc: migrate to android_system_core
revert: ADB: Add adb backup for TWRP
revert: twrp: remove liblz4-static dependency
Wait to mount until after fstab processed
Remove char/string conversions in fstab processing
Rewrite FS fstab flag processing
Rewrite TWRP fstab flag processing
For the ones that have problems before ( backup/restore/openrecoveryscript) , try 3.0.2-2 please and report if its fixed...
Changed slightly the way things are handled
TWRP 3.0.2-1-TugaPower
Fixup reboot after install variables
libenc: migrate to android_system_core
ADB: Add adb backup for TWRP
Note how to use ADB backup:
Using adb backup on the client side you can backup the partitions TWRP knows about.
On the client side you can do the following:
adb backup -f --twrp where options are
--compress: compress data
system: backup system
cache: backup cache
data: backup data
boot: backup boot
etc for each partition.
You can string multiple options,
i.e. adb backup -f --twrp --compress cache system data
To restore the backup use the following convention:
adb restore
twrp: remove liblz4-static dependency
Improve greek translation
Languages: Add font for Japanese
Languages: Update Japanese translation
Restore TW_SCREEN_BLANK_ON_BOOT functionality.
Fix decrypt of odd number length PIN on hardware crypto
Partition: Fix parsing of several twrp fstab flags
Update spanish translation
Update hungarian translation
translate install reboot option to dutch
Greek Translation from the updated en.xml
TWRP 3.0.2-0-TugaPower
Revert: Qualcomm hardware decrypt: Use block device softlink
gui: don't mix up display value with actual value
language: add 2 new strings in it.xml
languages: add 2 new strings for RU
fix typo
TWRP 3.0.1-2-TugaPower
gui: add portrait_ldpi
Redefine yres_virtual only once
Qualcomm hardware decrypt: Use block device softlink
twrp: Unmount firmware partition on boot
Really remove all old SP* flags and code
TWRP 3.0.1-1-TugaPower
Fixed slow format intruduced on 3.0.1-0-TugaPower ( my bad )
Added again EFS and Firmware as Backup Option
TWRP 3.0.1-0-TugaPower
fix missing string Reboot Option
Removed EFS and Firmware Backup
language: add 2 new strings to DE
languages: add Reboot Option translation
HACK: fix input focus on terminal
progress: Initialize display percentage variable
Improve progress bar handling for backup / restore / image flash
DataManager Updates
languages: fix and improve german translation
languages: add Polish translation
twrp: update Dutch translations
Update & Fix ru.xml
recovery: update italian translation
gui: add italian translation
TWRP: hungarian translation
Add language_helper.py
Flashutils: detect /dev/block/sd* as emmc
Stop loading languages for the splash screen
Stop trying to load /script/ui.xml
recovery: czech translation
Improve input box text handling
Detect and install custom themes as part of zip installs
gui: rewrite theme loading code
TWRP 3.0.0-6-TugaPower
TWRP Reboot Option after zip flash 5seconds
Removed slb1 from firmware list as backup
Merge code from upstream libtar + bug fixes
Revert: Update libtar with changes from cm-13.0
SplashScreen less time
TWRP 3.0.0-5-TugaPower
Fixed double restore of firmware backup
Allow setting backup file system from recovery fstab
Don't add subpartitions in firmware to restore list
Unix file endings and remove execute permission
Fix verifier_test build
Revert: WIP: use toolbox for ln instead of busybox
TWRP 3.0.0-4-TugaPower
Include firmware in ramdisk to avoid touching /firmware
Backup firmware re-added
Github for your changes?
Sent from my A0001 using Tapatalk
Awesome, love your ROM and now you've got your own recovery! :good:
Thanks!
Wisiwyg said:
No credit to @katinatez and @ketut.kumajaya for their work for the last year or two?
Click to expand...
Click to collapse
He has written that he is not finished with the original post. Give him some time and I'm sure he'll give credit to whomever credit belongs.
Thank you @danieldmm , I've always been using your version of twrp with your fixed and I'm glad you're carrying on the work for our devices.
Please guide, currently I have official TWRP 2.8.6.0 installed. So can I just flash this over it through TWRP image option or through Flasify or do I need to use adb commands.
[email protected] said:
Please guide, currently I have official TWRP 2.8.6.0 installed. So can I just flash this over it through TWRP image option or through Flasify or do I need to use adb commands.
Click to expand...
Click to collapse
Flashify works fine to install it
love your browser!!!
Sent from my A0001 using XDA-Developers mobile app
*Tuga HI5*
Does fix AROMA graphic mean that aroma installer fully works? Or does it just give the ability to see AROMA graphics but the installer is non functional?
oh yeah... following and subscribed immediately...
f41lbl0g said:
Does fix AROMA graphic mean that aroma installer fully works? Or does it just give the ability to see AROMA graphics but the installer is non functional?
Click to expand...
Click to collapse
id like to know this too :good:
@danieldmm AROMA installer works for me, only problem is that debug log shows on top of the installer making view difficult. I noticed also that in latest build the firmware backup is gone, showing only EFS, is that normal/volunteer?
Lisko said:
@danieldmm AROMA installer works for me, only problem is that debug log shows on top of the installer making view difficult. I noticed also that in latest build the firmware backup is gone, showing only EFS, is that normal/volunteer?
Click to expand...
Click to collapse
Yes, few builds back remove the firmware part because of the risk of restoring goes wrong or corrupt relative to aboot, if this happen phone will not boot, you will not have fastboot, you cannot boot to recovery. Only way to fix it's using qualcomm diag mode to flash bootloader again. Although on my next version will make the option to backup only modem as firmware. Its more then enough nowadays. Relative to aroma what zip did you tried? Tested with open gapps aroma and the debug log will not show. At least with open gapps aroma package.
Wisiwyg said:
No credit to @katinatez and @ketut.kumajaya for their work for the last year or two?
Click to expand...
Click to collapse
The only credits can give to both Devs was back on the time before making my own build of twrp, was using is recovery on my device. My credits on this goes all to Omnirom team that work with the recovery part. My TWRP is build based on Omnirom recovery tree and device tree of bacon from CM13. All this will be written on OP. Just did not managed to have time to that. Sorry
danieldmm said:
Yes, few builds back remove the firmware part because of the risk of restoring goes wrong or corrupt relative to aboot, if this happen phone will not boot, you will not have fastboot, you cannot boot to recovery. Only way to fix it's using qualcomm diag mode to flash bootloader again. Although on my next version will make the option to backup only modem as firmware. Its more then enough nowadays. Relative to aroma what zip did you tried? Tested with open gapps aroma and the debug log will not show. At least with open gapps aroma package.
Click to expand...
Click to collapse
opengapps (tried different builds) and aromafm, latest and previous recovery builds. I have materialized theme installed, may be a theme issue?
Lisko said:
opengapps (tried different builds) and aromafm, latest and previous recovery builds. I have materialized theme installed, may be a theme issue?
Click to expand...
Click to collapse
It could be, just in case be sure you are using my lattest build of TWRP, delete .twrps file inside twrp folder and theme. Then try again.
Enviado do meu A0001 através de Tapatalk
danieldmm said:
It could be, just in case be sure you are using my lattest build of TWRP, delete .twrps file inside twrp folder and theme. Then try again.
Enviado do meu A0001 através de Tapatalk
Click to expand...
Click to collapse
Without materialized theme aroma works as it should be. Sadly was a nice theme.):
Do you guys have any idea as to why kumajaya's TWRP builds seem to read and write nand much faster than these Tuga builds or the official builds? Especially kumajaya's 3.0.0 and 2.8.7 ones perform a significantly faster backup and restore, all other variables same.
NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.
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.2.1-0:
-minui fixes (cryptomilk)
-Better android-8.0 compatibility in ROM trees (Dees_Troy)
-Fix missing library in android-8.0 (nkk71)
-Fix inconsistent SDCard naming (DevUt)
-Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
-Allow restoring adb backups in the TWRP GUI (bigbiff)
-Fix gzip backup error in adb backups (bigbiff)
-Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
-Better support for installing Android 8.0 based zips due to legacy props (nkk71)
-Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
-Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
-Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
-v2 fstab support (Dees_Troy)
-Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
-Various other minor bugfixes and tweaks
CHANGELOG for 3.1.1-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
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!
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.
NOTE: fastboot flash to recovery_ramdisk and not to recovery as this device does not have a regular recovery partition.
Device Page, Download Links, Mirrors:
https://twrp.me/huawei/huaweihonorview10.html
Download:
https://dl.twrp.me/berkeley
If you wanna backup your old recovery, if in-case anything goes wrong, just follow these steps.
1)Root your device with Magisk
2)In a local terminal app or in adb shell, type su and get a root shell.
3)Do
Code:
dd if=/dev/block/bootdevice/by-name/recovery_ramdisk of=/sdcard/recovery_ramdisk_bak.img
4)Now you can just use
Code:
adb pull /sdcard/recovery_ramdisk_bak.img
to copy the backup image file to your desktop.
5)If in-case anything goes wrong, just do
Code:
fastboot flash recovery_ramdisk recovery_ramdisk_bak.img
Thanks for the TWRP mate
EDIT - As soon as you flash the image, remove the USB cable from the device and press and hold VOL+ and Power button to get into recovery.
Many thanks to TWRP team, to bring us the TWRP Recovery.
@Dees_Troy I can't see a link for download, not listed yet at official site. I suppose we have to wait for a while
Thanks.... But can't see the link to download.
https://eu.dl.twrp.me/berkeley/
That's to the download page
Finally twrp is here
Thanks
Thanks for this. Nice work
Finally TWRP [emoji8][emoji8][emoji8][emoji8]
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 02:27 PM ---------- Previous post was at 01:35 PM ----------
Finally flashed TwRp now working fine [emoji7][emoji7]
Sent from my [device_name] using XDA-Developers Legacy app
Thanks to TWRP Team.
Now is there anybody installed xposed successfully using TWRP?
I tried to install it without TWRP and got bootloop. I'm too scared to do it again even using twrp. :crying:
.
netxking said:
Thanks to TWRP Team.
Now is there anybody installed xposed successfully using TWRP?
I tried to install it without TWRP and got bootloop. I'm too scared to do it again even using twrp. :crying:
.
Click to expand...
Click to collapse
Xposed is incompatible for now. Wait until rovo pushes a update and see if it's fixed then
Read more https://github.com/rovo89/Xposed/issues/310
He states also that it is same issues for mate 9 as well as honor view 10. Something in art of Huawei seems to cause issues
Sent from my DUK-L09 using Tapatalk
Is this working for Honor 9 Lite?
Hey, I managed to "not to take backup" of my stock recovery ...where can I download it?
Rj_Param said:
Hey, I managed to "not to take backup" of my stock recovery ...where can I download it?
Click to expand...
Click to collapse
You can't. Your stock recovery is gone if you didn't back it up to your device/cloud.
Sent from my Honor View 10 using XDA Labs
have flashed the recovery but cant see any zip files and i have nothing on my sdcard somehow. pls let me know how to fix this
i have a question, if i flash twrp, huawei erecovery could be disappear？
cstar patrick said:
i have a question, if i flash twrp, huawei erecovery could be disappear？
Click to expand...
Click to collapse
Yes
Enviado desde mi ONE A2003 mediante Tapatalk
---------- Post added at 07:58 AM ---------- Previous post was at 07:56 AM ----------
iTAZUETA said:
have flashed the recovery but cant see any zip files and i have nothing on my sdcard somehow. pls let me know how to fix this
Click to expand...
Click to collapse
Yes, data partition is not accessible because decryption issue
Enviado desde mi ONE A2003 mediante Tapatalk
cstar patrick said:
i have a question, if i flash twrp, huawei erecovery could be disappear？
Click to expand...
Click to collapse
Nope it won't. eRecovery is in a seperate partition, so even if you flash ramdisk, it won't get replaced. But the ordinary recovery would.
---------- Post added at 09:47 AM ---------- Previous post was at 09:30 AM ----------
Rj_Param said:
Hey, I managed to "not to take backup" of my stock recovery ...where can I download it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-view-10/development/stock-recovery-getting-to-stock-t3754797
when i used this recovery, it seems my phone couldn't mount the partitions.
When i flash the zip , it said
unable to mount partitions
-unmounting partitions
updater process ended with ERROR:1
ERROR installing zip file...
updating partitions details...
failed to mount /cache' (invalid argument)
failed to mount /cust' (invalid argument)
failed to mount /data' (invalid argument)
failed to mount /modem_secure' (invalid argument)
failed to mount /product' (invalid argument)
failed to mount /splash2' (invalid argument)
failed to mount /system' (invalid argument)
failed to mount /vendor' (invalid argument)
failed to mount /version' (invalid argument)...done
My phone is Huawei p10p, system is rr.
This twrp is only for Honor view 10.
Take a look into P10plus forum.
Here is the EU link: https://eu.dl.twrp.me/ailsa_ii/twrp-3.3.0-0-ailsa_ii.img
And here the US link : https://dl.twrp.me/ailsa_ii/twrp-3.3.0-0-ailsa_ii.img
Note that the countries refer to the download servers regions for faster download and not the model it is for. Twrp is universal. So it should work on all axon 7 variants (U, G and CN)
Changelog for 3.3
* Merge AOSP 9.0 r3 (Dees_Troy)
* Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
* Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
* vold decrypt updates (CaptainThrowback and nijel8)
* Support vibration on LED class devices (notsyncing)
* Metadata decrypt support for Pixel 3 (Dees_Troy)
* Support rotating the display via build flag (vladimiroltean)
* Reboot to EDL mode button (mauronofrio)
* Support MTP on FFS devices (bigbiff)
* Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
* Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
* Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
* TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
* Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
* Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
Do we know what the changes are?
Updated OP with changelog and direct download links
This is a port of Lanchon REPIT.
- Nexus 10 Manta -
Disclaimer:
I am not responsible for your actions or consequences, directly or indirectly, related to the files and/or advice offered.
It is your choice to proceed.
What is REPIT?
REPIT is a simple, safe, device-only, data-sparing, and easily portable repartitioning tool for Android devices.
See the GitHub README for more on What REPIT is. GitHub - Link
Limitations:
Requires TWRP (or TWRP based) recovery.
Does not support encrypted devices.
Will cause data loss if the repartitioning process is externally interrupted.
See the GitHub README for more on Limitations. GitHub - Link
---
Notes:
A few years ago (September 2018), I made a port of REPIT for deb,flo and manta that was spread out between multiple threads.
Some comments and instructions were lost in thread chatter or just in a different thread altogether.
The file name actually configures the repit script.
Noted that you may have to toggle MTP Disable, Enable, Disable.
Noted that you may have to reboot into TWRP after disabling MTP.
Remember /tmp is wiped after a reboot. Copy repit to /sdcard and after rebooting back into TWRP, copy it from /sdcard to /tmp using TWRP File manager.
Noted that you may have to unmount cache and data.
Do NOT flash repit from USB/OTG.
This is designed for a stock partition layout. If your device has been modified and a vendor partition was created, REPIT will not work.
Side note:
Lanchon added Nexus 7 (2013) to the official list. (November 2019)
Lanchon REPIT GitHub - Port Request - Commit
---
Be Careful.
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start modifying partitions.
Backup what you want to save and store it off device.
Copy it to your computer, cloud storage, USB, ...
Instructions:
This operation might take a long time and must not be interrupted.
- Depending on the device and REPIT configuration, this might take a few hours.
Make sure your battery is fully charged or mostly charged.
- You can connect to a charger while the REPIT script is running. May or may not charge depending on the recovery.
How To:
If you already have a ROM installed, repit will backup, change the partition, restore and resize.
- You can just reboot once the script finishes.
Boot into TWRP
Swipe to Allow Modifications
Copy the repit zip to /tmp
Disconnect from computer
Disable MTP
Disable MTP TWRP -> Mount
Install repit
TWRP -> Install -> navigate to /tmp and flash the repit zip
Reboot to system
If you are doing a clean install, add the +wipe option to system in the zip file name. This will speed up the partitioning since system will not be backed up and restored.
lanchon-repit-20210221-cache=16M+wipe-system=1.3G+wipe-data=max-manta.zip
- Reboot back into TWRP after the script finishes.
- Then follow the instructions from the rom thread to install the rom you are going to use.
Boot into TWRP
Swipe to Allow Modifications
Copy the repit zip to /tmp
Disconnect from computer
Disable MTP
Disable MTP TWRP -> Mount
Install repit
TWRP -> Install -> navigate to /tmp and flash the repit zip
Reboot to recovery
Follow the instructions from the rom thread to install the rom you are going to use.
---
Changes:
Nexus 10 [Manta]
Updated to the current REPIT scripts.
Include userdata in the sector range and modifiable partitions.
Nexus 10 GitHub - Commit
Download Links:
MediaFire - Link
SourceForge - Link
GoogleDrive - Link
Direct Download from MediaFire:
lanchon-repit-20210221-cache=16M+wipe-system=1.3G-data=max-manta.zip MediaFire - Download
REPIT Links:
Lanchon REPIT GitHub - Link
- My fork GitHub - Link
Credits:
Lanchon for his excellent REPIT project.
The Android Community and everyone who has helped me learn through the years.
Cheers all.
Note about configuration.
The user configuration is done by renaming the zip file before flashing it.
The modifiable partitions are cache, system and userdata (7, 8 and 9).
The actual partitioning is done by a sector range. This is declared inside the script along with a default configuration.
Code:
# the set of partitions that can be modified by REPIT:
# <gpt-number> <gpt-name> <friendly-name> <conf-defaults> <crypto-footer>
initPartition 7 cache cache "same keep ext4" 0
initPartition 8 system system "same keep ext4" 0
initPartition 9 userdata data "same keep ext4" $footerSize
# the set of modifiable partitions that can be configured by the user (overriding <conf-defaults>):
configurablePartitions="$(seq 7 9)"
...
# the set of contiguous partitions that form this heap, in order of ascending partition start address:
heapPartitions="$(seq 7 9)"
# the disk area (as a sector range) to use for the heap partitions:
heapStart=$(parOldEnd 6) # one past the end of misc.
heapEnd=$deviceHeapEnd # one past the last usable sector of the device.
The default zip name lanchon-repit-20210221-cache=16M+wipe-system=1.3G-data=max-manta.zip
Creates a 16M cache partition, the wipe option (+wipe) will stop the backup and restore of cache.
Creates a 1.3G system partition, since there is no wipe option, the system partition will be backed up, restored and expanded or compressed.
The rest of the space is used for userdata. (data=max) again, since there is no wipe option, data will be backed up, restored and expanded or compressed.
Setting a 16M cache and a 1.3G system, userdata will not be reduced. If system is set beyond 1.3G, userdata will be reduced by the same amount.
If you change the name to lanchon-repit-20210221-cache=16M+wipe-system=1.5G+wipe-data=max-manta.zip
Creates 16M cache partition, the wipe option (+wipe) will stop the backup and restore of cache.
Creates 1.5G system partition, the wipe option (+wipe) will stop the backup and restore of system and you will need to install a rom.
The rest of the space is used for userdata. (data=max) again, since there is no wipe option, data will be backed up, restored and expanded or compressed.
If you change the name to lanchon-repit-20210221-cache=16M+wipe-system=1.3G+wipe-data=max+wipe-manta.zip.
This will create a 16M cache partition, a 1.3G system partition and use the rest for userdata.
Since the wipe option is added to all, no backup and restore is done. Only empty/formatted partitions are created.
This will speed up the partitioning if you are doing a clean flash.
Userdata is erased also so, make sure to backup what you want/need to keep off device.
See the GitHub README for more on how to configure. GitHub - Link
Cheers all.
<RESERVE>
<RESERVE>
Thanx ipdev 4 your Help, I've successfully copied REPIT-mod & the user configuration File onto my Manta, it Failed w/ the issue that it couldn't unmount all partitons blah bla' & that it's Copied itself 2 /tmp, I re-red your instructions but there isn't eXplicit instructions about where that iz, just poking around in the dark I got 2 Advanced > File Manager & found a /tmp dir but don't know which file 2 eXecute, I Blindly tried a couple, I can't recall which, But No Cigar! I'm Using TWRP 3.5.2_9-0-manta... Sorry about being such a pest...
;-\K
Thanks for this, it's work fine for me
Anybody here, Please Help me. I've got 3 of these Nexus 10 Manta Tablets & I'm Still Stuck!... ;-\K
Thanx ipdev 4 your Help, I've successfully copied REPIT-mod & the user configuration File onto my Manta, it Failed w/ the issue that it couldn't unmount all partitons blah bla' & that it's Copied itself 2 /tmp, I re-red your instructions but there isn't eXplicit instructions about where that iz, just poking around in the dark I got 2 Advanced > File Manager & found a /tmp dir but don't know which file 2 eXecute, I Blindly tried a couple, I can't recall which, But No Cigar! I'm Using TWRP 3.5.2_9-0-manta... Sorry about being such a pest...
;-\K
Can Anybody Please give me a Clue what Iḿ doing wRong?!? ;-\K