Related
DL Desire Series v 5.x
by dandiest & freak
New features:
Totally new init, using full power of aufs, lzma squashfs and ram.
new vinit, with automatic configuration for nand, magldr and sd launch
re-odexed builds
re-engineered packages
working with data2sd/data2ext
Versions and Links:
[4 jun ] - dlz test version - go to this post
[30 apr] - (changelog)
version 5.21.51.18: DesireZ 1.85.72 base: download [CWM] [DAF]
version 5.12.51.18: DesireZ themed 1.85.72 base:download [CWM] [DAF]
[10 apr]
Be careful, actually there is problems with cwm and users with wp7 on nand.
version 5.03.50.15: IncredibleS 1.43.415.3 base: download [cwm] [DAF] (battery percentage is wrong)
Kernel:
current kernel: 1.8 download
You can take a look on current kernel source at : (NOT YET SYNCHRONIZED) http://www.linux4freak.com/gitweb/?p=kernel-freak/.git;a=summary
Tips:
Please remove dialer button sound to prevent robotic voice
If using SD/haret, do not set pin code under wm65
Do not change Desire_DL folder name, our detection method is based on this name
Do not use another kernel, none of them works with our new builds
for data2ext, please reboot your phone twice in order to have all working fine (2nd boot take a long time)
Please use shutdown instead of reboot for your phone
you can use 200M or 250M for cwm
Make a fresh install is highly recommended
sdcard is highly recommended for leo1024 phone.
How to report:
- Using dlreport :
I have created dlreport to have a photography of your system. You can use it with a terminal or with adb. After running it, an archive file /system/dlreport.tar is generated. Please attach this file to your post.
If you don't have adb, use this archive: http://www.multiupload.com/YOZYJGI09N
Code:
adb shell dlreport && adb pull /system/dlreport.tar
- If dlreport not working for you , please usethis naming method:
[DL VERSION] - 5.01.50.19
[LOAD TYPE] - NAND
[LOAD METHOD] - CWM
[DATA TYPE] - EXT4 (2 PARTITIONS 1GB-300Mo)
[DATA LOAD] - From previous build
[CONFIG.TXT] - (if tweaked)
[INIT.LOG/DMESG] - as attachment
Click to expand...
Click to collapse
Options:
no need to put any options at startup, our init detect your phone and launch mode, and apply tweaks accordinly
if you want to modify some options, you have all these possibilities, after creating config.txt file inside Desire_DL folder on sdcard:
load_mode=
0 // (default) load cache.sqsh file to ram
1 // load cache.sqsh normally
data_img=
0 // not using data.img file on sdcard to store data apps
1 // using data.img file on sdard to store data apps
2 // try to increase data.img filesize ( ! experimental !) works with data_size
data_size=
512 // (default) size in Mb of data.img/1st ext4 partition
sd_boost=
0 // (default) load 1st ext4 partition with default (tweaked) options
1 // load 1st ext4 partition without journal
ppp_mode=
0 // rmnet enabled
1 // ppp enabled
format_ext4=
0 // (default) no effect
1 // format all ext4 partitions on sdcard with default (tweaked) options
2 // format 1st ext4 partition with ext2 instead of ext4 - all other ext4 partitions formatted normally
8 // simulate format_ext4=9 to show in init.log future partitions size
9 // works only on nand - remove all data from sdcard and partition it to 4 partitions: FAT / EXT4 / EXT4 / SWAP; the 2nd partition size can be defined with data_size= option
cache_mode= [for WM65/SD/WP7 users]
0 // (default) copy downloaded apps and tmp files to /data
1 // copy downloaded apps and tmp files to ram
sched_mode=
bfq // (default) use bfq scheduler
cfg // use cfq scheduler
noop // use noop scheduler
vdd_mode=
0 //
possible values are: +50 +25 0 -25 -50 -75 -100 -125 -150
Increase/Reduce voltage of phone. For frequencies higher than 576Mhz, vdd is limited to -50 (you can safely use -100 value)
mac_virt=
use your own wifi mac address
gps_zone=
defining your region for gps
backup_img=
0 // (default) no effect
1 // create backup.tgz on sdcard: store /data contents
restore_img=
0 // (default) no effect
1 // restore backup.tgz from sdcard to /data
repair_mode=
0 // (default) no effect
1 // delete dalvik-cache and fix permissions
2 // only for magldr/sd: mount system yaffs2 partition to /mnt/rescue and copy zImage / initrd.gz / vinit from sd to nand
9 // only for magldr/sd: mount system yaffs2 partition to /mnt/rescue
Video and screenshots:
Many thanks to Sklar for this video.
Features details:
aufs + squashfs. This is the 1st android version that can support the aufs+squashfs, we even worked with the author of aufs to make it usable to android. a lot of innovations within this build from the technical perspective, for users, the benefit of it are:
high performance
despite of squashfs is used to reduce the size of file system, user still be able to change any file directly with the power of aufs.
a lot of frequent accessed files are squashed and loaded into ram to improve the performance.
re-odexed. there flood a lot of misleading messages in xda of odexed, same as squashfs. Odex can actually improve system performance, and at the same time, reduce the whole system's size (because the odex is optimized dex), and odex build has less chance of system crash that lead to wipe the davlik-cache. an odex build doest not generate the davlik-cache which is odexed.
re-engineered. we re-packaged all the apk, jar in the build after optimized the png file and etc, to reduce the apk&jar size, which will reduce the consuming of ram.
Naming convention:
the 1st digit is for the build base, 5.
the 2nd field is for the subversion and build model, normally, 5.0x means the first relase which should based on a totally new base, 5.x1 is for dlz, 5.x2 is for dlz themed, and 5.x3 is for incredibleS
the 3rd field is for the init version, actually 5.0 ->50
the 4th field will be used for the kernel version, actually 1.5c ->15
Thanks! :
to all devs at xda and at irc-logs, kernel devs
to Jim, as a linux expert, he gave us a lot of good idea and suggestion.
to J.R. Okajima, the author of aufs, who helps us solve the last performance of aufs on android.
to kajos, manu33xtro, pascalsg2, vlad48, darkony, ..., they are working with us for months to test a lot of builds we released (about 10 builds we released for testing before this version)
Credits:
All these builds and init are made by dandiest and me
Please respect our work, and don't forget to mention ou names and authors if you used some technologies. Don't forget gpl too.
Put a link to this thread if you want to share it.
Changelog:
[30 apr]
- new kernel 1.8: modifying a bit smartass and cpufreq, added more than 50 patches from kernel mainline (2.6.32.28 to 2.6.32.39, 2.6.33 and 2.6.34)
- modified cache/system squashfiles, now cache.sqsh is lzma compressed and system.sqsh is gzip compressed
- re-added htc locations (Laputa) for 5.22 build
- minor things ...
- better reactivity with proximity sensor when calling.
Click to expand...
Click to collapse
[15 apr]
- new version:
modifying bcm4329 branch to _245
corrected init when only 1 partition on sdcard
- no need of setcpu, managing it in kernel with perflock and smartass
- new wpa-supplicant, then wifi tethering now works fine with new kernel
- working dspmanager
- shared media working
- modifying cached/uncached apps
- adding new script: dlreport, which generate a tar file with all we need to have a "photography" of your system.
- modifying swap size to limit out_of_memory errors when installing lot of apps at once.
- modifying vinit/init to solve (i hope so) cwm / wp7 / sd-haret issues.
- kernel 1.6: totally backported net stack from rafpigna instead of tytung, adding 2 way call recording, new bt stack, tweaked smartass and bfq as default scheduler, activating htc boot perflock.
Click to expand...
Click to collapse
[10 apr]
Initial 5.x release
- desireZ, themed and incredibleS version
- aufs/lzma by default
- kernel freak 1.5c
Click to expand...
Click to collapse
MINI HOWTO
No need of config.txt for the first startup.
config.txt is for tweaking your build.
For Nand users:
Download your preferred version, you can choose daf or cwm method.
Magldr 1.13/cwm is already installed on your phone
For daf:
- choose USB Flasher on you phone inside magldr bootloader
- extract archive
- run inside Desire_DL folder: EnterBootloader.exe
(don't forget to run it as administrator).
- After flashing, let our init make everything to setup.
For cwm:
- you can choose cwm 200M or 250M.
- there is lot of threads about how to use cwm.
- Once done, let our init make everything to setup.
Click to expand...
Click to collapse
For magldr users:
- extract daf version in your sdcard
- Desire_DL folder must be on the root of your sdcard
- DON'T RENAME FOLDER
- Enter inside magldr bootloader, choose your AD/SD dir in services
- Run Boot AD/SD option.
- That's all
Click to expand...
Click to collapse
reserved for future use 6
Data2Ext? right?
awesome, will be downloading as soon as you get it upped.. thanks much, guys
[leo model] - eu :d:d
Refresh Refresh Refresh wait download
What is the CWM partition recommended for this?
shared media work with this new builds ??
waiting 4 changelogs - except "initial release" which is Fastest rom in this new series???
I've got Wifi WPA cannot connect in Imilka's Incredible S1.1. Is ur rom working fine?
super a new build !
is the Camera fully working? (preview and sending)
keep up the good work !!
UOT kitchen
Is it possible to flash UOT kitchen with your ROMs?
thanks
for 5.01.50.15, i think it's possible. No idea for 5.02 or 5.03. Dandiest past a long time to have a good framework for 5.03, it should be possible too, but not so easy
matmar said:
Is it possible to flash UOT kitchen with your ROMs?
thanks
Click to expand...
Click to collapse
There is a lot of changes internally. But you can read features and features details to know "the mind" of builds.
All these versions are good, incredibleS is a little but more smoother, but all of them are fast.
arifqur said:
What is the CWM partition recommended for this?
Click to expand...
Click to collapse
dont you read !?
freak007 said:
[*]you can use 200M or 250M for cwm
Click to expand...
Click to collapse
kernel
Is you kernel compatible with eb ?
[Q] i just wanna ask tht wht r the advantages of installing this kernel ???
or
y shud we install this kernel ???
Sent from my GT-S5360 using XDA
Benefits:
Swap Support.
Some Bug Fixes.
CPU Spy App Fix.
Game-Port Modules.
Graphic Engine Driver.
Security Patches Added.
TUN/TAP, Virtual Adapter.
Added USB CORE Support.
HID, EHCI, OHCI, Support.
VibeTunz (TM) Technology.
MERRUK Tempfs for SU Binary.
EXT2/EXT3 & EXT4/JBD2 support.
SD-EXT Support, System & Recovery.
CIFS Support. (Mount Shared Folders).
NETFILTER Compatibility with DROIDWAL.
Recouvery in Read/Write mode & [ADB Root].
Added IO Scheduler. (Deadline, CFQ, VR, SIO).
BLMUNLOCK Added, & a Script to run it at boot.
INIT.D Support & Auto Create init.d in /system/etc.
BusyBox Support PreInstalled (Busybox binary in /sbin).
Root Support [ADB Root] & PreInstalled (SU binary in /sbin).
Added MFC, (MULTI FORMAT CODEC) Firmware From Samsung.
Multi-language Module Support For UTF-8 on CIFS Mount Shares.
/Cache and /Data, Can be mounted as EXT4. (/System Need's Fixes).
Add The Permanent Modded / Fixed CloclWorkMode Recovery. (V.5.8.0.2).
Mount SDCARD WITH EXT4 FS Supported (You Need to Format it With EXT4).
New J4FS SUPPORT. (We Can Mode it to have our new optimized j4fs rw filesystem).
Modules for VPN/IPSec Support. (IPsec AH, IPsec user configuration interface, IP Tunneling, )
Added CPU Governor Feature. (SmartassV2, Conservative, Ondemand, Powersave & Userspace, etc...) (Not All of them for now)
------------------------
DEBUG SCRIPTS ADDED FOR SYSTEM & RECOVERY.
FIXES SCRIPTS ADDED FOR SYSTEM & RECOVERY.
IMPORTANT MODULES LOAD'S NOW AT BOOT.
Plus A Lot of Other Improvements & Fixes.
WHY?
For further development and enhancement of SGY, in order to build the perfect working modification. Android is a linux based OS
if you want to know how important a kernel is to a linux system then check this out:
http://en.wikipedia.org/wiki/Linux_kernelhttp://en.wikipedia.org/wiki/Linux_kernel
i install it so tht "temple run" can wrk but... still it dsnt
Sent from my GT-S5360 using XDA
deathnotice01 said:
Benefits:
Swap Support.
Some Bug Fixes.
CPU Spy App Fix.
Game-Port Modules.
Graphic Engine Driver.
Security Patches Added.
TUN/TAP, Virtual Adapter.
Added USB CORE Support.
HID, EHCI, OHCI, Support.
VibeTunz (TM) Technology.
MERRUK Tempfs for SU Binary.
EXT2/EXT3 & EXT4/JBD2 support.
SD-EXT Support, System & Recovery.
CIFS Support. (Mount Shared Folders).
NETFILTER Compatibility with DROIDWAL.
Recouvery in Read/Write mode & [ADB Root].
Added IO Scheduler. (Deadline, CFQ, VR, SIO).
BLMUNLOCK Added, & a Script to run it at boot.
INIT.D Support & Auto Create init.d in /system/etc.
BusyBox Support PreInstalled (Busybox binary in /sbin).
Root Support [ADB Root] & PreInstalled (SU binary in /sbin).
Added MFC, (MULTI FORMAT CODEC) Firmware From Samsung.
Multi-language Module Support For UTF-8 on CIFS Mount Shares.
/Cache and /Data, Can be mounted as EXT4. (/System Need's Fixes).
Add The Permanent Modded / Fixed CloclWorkMode Recovery. (V.5.8.0.2).
Mount SDCARD WITH EXT4 FS Supported (You Need to Format it With EXT4).
New J4FS SUPPORT. (We Can Mode it to have our new optimized j4fs rw filesystem).
Modules for VPN/IPSec Support. (IPsec AH, IPsec user configuration interface, IP Tunneling, )
Added CPU Governor Feature. (SmartassV2, Conservative, Ondemand, Powersave & Userspace, etc...) (Not All of them for now)
------------------------
DEBUG SCRIPTS ADDED FOR SYSTEM & RECOVERY.
FIXES SCRIPTS ADDED FOR SYSTEM & RECOVERY.
IMPORTANT MODULES LOAD'S NOW AT BOOT.
Plus A Lot of Other Improvements & Fixes.
WHY?
For further development and enhancement of SGY, in order to build the perfect working modification. Android is a linux based OS
if you want to know how important a kernel is to a linux system then check this out:
http://en.wikipedia.org/wiki/Linux_kernelhttp://en.wikipedia.org/wiki/Linux_kernel
Click to expand...
Click to collapse
Supposing I am a noob in all of these technical terms, can u give a simple overview of what improvements it brings to my device usage experience?
merruk technology_kernel 2.0 Pre-final
an i install 2.0 pre-final kernel on any custom ROM ?? If yes, will u suggest some custom ROMs? I m using stock rom. Thanx
mig102 said:
i install it so tht "temple run" can wrk but... still it dsnt
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
probably you can try it first and feel the shock
deathnotice01 said:
Benefits:
Swap Support.
Some Bug Fixes.
CPU Spy App Fix.
Game-Port Modules.
Graphic Engine Driver.
Security Patches Added.
TUN/TAP, Virtual Adapter.
Added USB CORE Support.
HID, EHCI, OHCI, Support.
VibeTunz (TM) Technology.
MERRUK Tempfs for SU Binary.
EXT2/EXT3 & EXT4/JBD2 support.
SD-EXT Support, System & Recovery.
CIFS Support. (Mount Shared Folders).
NETFILTER Compatibility with DROIDWAL.
Recouvery in Read/Write mode & [ADB Root].
Added IO Scheduler. (Deadline, CFQ, VR, SIO).
BLMUNLOCK Added, & a Script to run it at boot.
INIT.D Support & Auto Create init.d in /system/etc.
BusyBox Support PreInstalled (Busybox binary in /sbin).
Root Support [ADB Root] & PreInstalled (SU binary in /sbin).
Added MFC, (MULTI FORMAT CODEC) Firmware From Samsung.
Multi-language Module Support For UTF-8 on CIFS Mount Shares.
/Cache and /Data, Can be mounted as EXT4. (/System Need's Fixes).
Add The Permanent Modded / Fixed CloclWorkMode Recovery. (V.5.8.0.2).
Mount SDCARD WITH EXT4 FS Supported (You Need to Format it With EXT4).
New J4FS SUPPORT. (We Can Mode it to have our new optimized j4fs rw filesystem).
Modules for VPN/IPSec Support. (IPsec AH, IPsec user configuration interface, IP Tunneling, )
Added CPU Governor Feature. (SmartassV2, Conservative, Ondemand, Powersave & Userspace, etc...) (Not All of them for now)
------------------------
DEBUG SCRIPTS ADDED FOR SYSTEM & RECOVERY.
FIXES SCRIPTS ADDED FOR SYSTEM & RECOVERY.
IMPORTANT MODULES LOAD'S NOW AT BOOT.
Plus A Lot of Other Improvements & Fixes.
WHY?
For further development and enhancement of SGY, in order to build the perfect working modification. Android is a linux based OS
if you want to know how important a kernel is to a linux system then check this out:
http://en.wikipedia.org/wiki/Linux_kernelhttp://en.wikipedia.org/wiki/Linux_kernel
Click to expand...
Click to collapse
its really good information for ..
Thanks for the great info
Sent from my GT-S6102 using xda premium
deathnotice01 said:
Benefits:
Swap Support.
Some Bug Fixes.
CPU Spy App Fix.
Game-Port Modules.
Graphic Engine Driver.
Security Patches Added.
TUN/TAP, Virtual Adapter.
Added USB CORE Support.
HID, EHCI, OHCI, Support.
VibeTunz (TM) Technology.
MERRUK Tempfs for SU Binary.
EXT2/EXT3 & EXT4/JBD2 support.
SD-EXT Support, System & Recovery.
CIFS Support. (Mount Shared Folders).
NETFILTER Compatibility with DROIDWAL.
Recouvery in Read/Write mode & [ADB Root].
Added IO Scheduler. (Deadline, CFQ, VR, SIO).
BLMUNLOCK Added, & a Script to run it at boot.
INIT.D Support & Auto Create init.d in /system/etc.
BusyBox Support PreInstalled (Busybox binary in /sbin).
Root Support [ADB Root] & PreInstalled (SU binary in /sbin).
Added MFC, (MULTI FORMAT CODEC) Firmware From Samsung.
Multi-language Module Support For UTF-8 on CIFS Mount Shares.
/Cache and /Data, Can be mounted as EXT4. (/System Need's Fixes).
Add The Permanent Modded / Fixed CloclWorkMode Recovery. (V.5.8.0.2).
Mount SDCARD WITH EXT4 FS Supported (You Need to Format it With EXT4).
New J4FS SUPPORT. (We Can Mode it to have our new optimized j4fs rw filesystem).
Modules for VPN/IPSec Support. (IPsec AH, IPsec user configuration interface, IP Tunneling, )
Added CPU Governor Feature. (SmartassV2, Conservative, Ondemand, Powersave & Userspace, etc...) (Not All of them for now)
------------------------
DEBUG SCRIPTS ADDED FOR SYSTEM & RECOVERY.
FIXES SCRIPTS ADDED FOR SYSTEM & RECOVERY.
IMPORTANT MODULES LOAD'S NOW AT BOOT.
Plus A Lot of Other Improvements & Fixes.
WHY?
For further development and enhancement of SGY, in order to build the perfect working modification. Android is a linux based OS
if you want to know how important a kernel is to a linux system then check this out:
http://en.wikipedia.org/wiki/Linux_kernelhttp://en.wikipedia.org/wiki/Linux_kernel
Click to expand...
Click to collapse
This makes my nose bleed.. Whats a noob friendly explanation for all of these?
Sent from my deodexed potato
Xicorified said:
Supposing I am a noob in all of these technical terms, can u give a simple overview of what improvements it brings to my device usage experience?
Click to expand...
Click to collapse
Did exactly as per instructions, on stock rom. but it shows 832 in cpu master app. but showd about pre final kernel in Setting ==> about phone. What may be the problem?? what to do???
ajay131 said:
Did exactly as per instructions, on stock rom. but it shows 832 in cpu master app. but showd about pre final kernel in Setting ==> about phone. What may be the problem?? what to do???
Click to expand...
Click to collapse
It's cause merruk pre v.2.0 still not overclock so still show 832mhz and 312mhz. But see merruk add governor like conservatif, ondemand, poweruser. I dont use that cz as long as i know some gov can work in 2freq (312-812) so i combine with kernel mdule frm irfanbagus to add interactive gov.
savie said:
It's cause merruk pre v.2.0 still not overclock so still show 832mhz and 312mhz. But see merruk add governor like conservatif, ondemand, poweruser. I dont use that cz as long as i know some gov can work in 2freq (312-812) so i combine with kernel mdule frm irfanbagus to add interactive gov.
Click to expand...
Click to collapse
okk. Thanx for the help. will try accordingly.
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy Nexus S 4G (crespo4g)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
http://d-h.st/users/philz_touch/?fld_id=16785#files
Click to expand...
Click to collapse
5.05.0 (26.05.2013)
- fix potential memory overflow during computing of size stats in backup
- fix /efs backup not possible for devices without /preload, unless preload menu was selected once
- fix custom nandroid and twrp backups for yaffs2 devices (do not force tar format on these)
- misc fixes for supporting more devices mainly during nandroid jobs:
* allow use of device2 for raw backup and restore operations (using dd/cat)
* better nandroid support when device names in fstab do not match actual mtd name (revert statfs for volume->device)- revert cm-10.1 changes: Write correctly fstab info in log (do not print to stderr)
- merge old custom_backup folder to cwm backup folder
- old .efs_backup and .modem_bin folders also should be moved to clockworkmod/backup
- .aromafm folder is now aromafm (no more hidden folder for this)
- add regenerate md5 sum option for nandroid backups (use with caution)
- revert inverting fstype and fstype2 (see github commit for more info on this)
- fix nandroid backup fails before generating md5 for /external_sd devices when card is not inserted/mountable (.android_secure check)
- fix falling back to system mount command will fail when calling ensure_path_mounted(filename)
- htc desire x (protou) support added
- htc droid incredible 4g lte (fireball):
* add support
* allow sd-ext and mount external sd in ext4
* allow backup/restore of /radio- galaxy s4 - i9505:
* support emmc partitions size detection during nandroid jobs
* fix exfat mount for some sdcards (thanks to chenglu)- nexus s/4g (crespo/crespo4g):
* allow raw + yaffs2 backups for /efs and /radio
* allow size detection for mtd partitions during nandroid backup
* fix device name to samsung nexus s
* repack with stock gb kernel to fix usb mount in recovery- nexus 10: Enable efs backup and restore
- galaxy nexus (maguro/toro/toroplus): Enable efs backup and restore
Click to expand...
Click to collapse
Most changes are in nandroid backup operations and external storage mounting
Please test this and report any bugs with a log
To get a log:
- Advanced / Report Error
- Attach here the /sdcard/clockworkmod/philz_recovery.log file
If phone is hanguing and cannot export a log because sdcard is not being mounted:
- adb pull /tmp/recovery.log
- attach the recovery.log file
At worst:
- Reboot into main system, not recovery (adb reboot can achieve it when needed too)
- Grab /cache/recovery files (last_log, last_install)
Click to expand...
Click to collapse
v5.06.1
5.05.0 --> 5.06.1
5.06.1 (02.06.2013)
- HTC One: move to new m7ul device tree
5.06.0 (01.06.2013)
- support dual modem devices nandroid operations (dual sim, i9505)
- merge cm-10.1 changes: support version 2 (2048-bit e=65537) keys in recovery
- Nexus S/4G (crespo/4g): add mmcblk names to recovery.fstab to fix /data mount
- HTC Desire X (protou): support both protou-ics and protu-jb fstab
5.05.9 (31.05.2013)
- do not write backup size progress to log file
- show total time after restore job
- write backup path to log
5.05.7 (30.05.2013)
- use bigger 23x41 roboto font for HD devices (i9500, i9505, Nexus 10)
- do not uselessly statfs partition to refresh backup size progress if we're under NICE_INTERVAL (100ms)
- show backup compression 0% when backup is tar format and compression is disabled
- fix get time events during nandroid jobs and touch events
- universal scroll sensitivity and row height settings (fix hypersensitivity for HD devices)
- fix backup size progress for datamedia devices (special thanks to pickandwhammy for the time he spent in debugging this and providing logs)
- merge Get_Folder_Size() changes from twrp 2.5
- misc logging improvements
- small bug fixes
Click to expand...
Click to collapse
Released v5.08.5
Change list 5.07.1 ---> 5.08.5
5.08.5 (11.07.2013)
- Compile Aroma File Manager (by amarullz) zip installer under recovery:
* either compile whole recovery, zip will be created at first pass
* or only compile aroma zip installer in two pass:
1- mmm bootable/recovery/aromafm
2- mmm bootable/recovery/aromafm/tools
* output: [target_out]/aromafm_out/aromafm_[DeviceID].zip
- detect aroma compatibility with non NEON devices during compiling
- use less conflicting flags: TARGET_NAME --> TARGET_COMMON_NAME
5.08.0 (07.07.2013)
- improve nandroid progress bar update
- fix recovery was not prompting when backup estimated size is larger than free space
- add ors backup support for twrp format requested by BillGoss
- ors backup: when no backup name is given, generate it using same way as nandroid operations (time stamp + rom name tag)
- support separated compiling for Loki patched devices (S4 AT&T and Verizon)
- i9505: revert some changes to fix time bug for some users
- Galaxy S4 US variants: repack around Audism stock JB 4.3 kernel v3 + Samsung exfat modules + revert use of mkefs for partition corruption issue
- fix missing break in set backup compression value menu (misc_nandroid_menu())
- misc clean up code
- sync latest sources
5.07.6 (05.07.2013)
- update version 6.0.3.3
- add exfat-fuse 1.0.1.362 / 2.9.2 optional support by enabling USE_EXFAT_FUSE_BIN CFLAG in BoardConfig (exfat support on cyanogenmod repacks)
- i9505: use Audism kernel v3 (Stock Samsung sources) to fix partition corruption without additional code and for better exfat support
Click to expand...
Click to collapse
Please Note: Device specific threads will no longer be updated. I monitor them for support and feedback though
To check if you have a new version, subscribe to main thread:
http://forum.xda-developers.com/showthread.php?t=2201860
Thank you for your understanding
Any plans for crespo4g? Love this recovery.
kijp15 said:
Any plans for crespo4g? Love this recovery.
Click to expand...
Click to collapse
It is for crespo4g. Just a little typo I believe.
Sent from my Nexus S 4G using XDA Premium 4 mobile app
update to v6.00.5
Phil3759 said:
update to v6.00.5
Click to expand...
Click to collapse
I have heard about your recovery for ages now but I guess I didn't have a phone that you made the recovery for until my old NS4G. Its actually very nice! It also properly installed CM11 zip but TWRP didn't
Sent from my Nexus S 4G using Xparent Gray Tapatalk 2
Welcome to TWRP with F2FS & Thermal Control!
---- Supports Models d800/1/2/3/4/5, LS/VS-980, L01F, lgl22, and F320* ----
(for d804/5 use the d802 version)
Do NOT post a question if you don't read the first FIVE posts of this thread!!!
Features:
Added: Thermal control, thanks to using AICP kernel. [originally dr87's idea]
Added: As of 3.0.2-1: Using modified cm-13 kernel with my additions of thermal and other changes.
Added: As of 3.1.0-0: Using modified cm-14.1 kernel with my additions of thermal and other changes.
Added: Full F2FS support, including updated driver and f2fs-tools.
NOTE: You must NOT have "Use rm -rf instead of formatting." in the Settings page. If you have this option enabled, you will not be able to change partition type.
Added: Proper support for f320 & lgl22 External SD Card.
Added: Tap to wake.
Added: NTFS support.
Added: Working decryption support.
DO NO ENCRYPT f2fs - Bootloop of ROM and Recovery will occur!
Added: AROMA hack to fix graphics.
Uses: dr87's auto-select correct panel type.
Uses: Bump (So loki isn't needed)
& All of the goodies that already come packed in to the latest version of TWRP!
Please enjoy this recovery and I encourage feedback!!!
F2FS Information:
Clicky Clicky (or scroll down to post #5)
Bugs/Issues:
TWRP Issues, Generally:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues
https://github.com/omnirom/android_bootable_recovery/issues
Major Thanks to:
TWRP Team
Dees_Troy
OmniRom Team
Cyanogenmod Team
Drgravy
Team Codefire
Dorimanx
jakew02
dr87
Khaon
bart452
xiaolu
Yoinx
And everyone else involved with these projects!
Installation:
1) First, you need any version of TWRP installed and working:
I'd recommend using Autorec to get initial TWRP running.
This is the link for KK: http://forum.xda-developers.com/showthread.php?t=2715496
There is also an apk for lollipop, this is much preferred! (Google is your friend.)
You can use any number of other methods to get some version of TWRP installed and running.
2) Once you have a working TWRP, simply flash my zip to upgrade to latest version.
If you flash the image directly, the panel detection script will not run!
(This is only important if you have a jdi LCD panel.)
Troubleshooting:
If you have any issues, please try the Official Build and compare to check that bug is only present in my version. If it is present in both versions, report it to TeamWin or Dees_Troy. If it only bugs in my version, please let me know ASAP.
Also, please check FAQ before asking questions. Thanks!
Download:
https://www.gregtwallace.com/lg-g2/g2-twrp/
Downloads are installable zip files, the images inside of which are already BUMPed.
Sources:
https://github.com/blastagator
Source Readme:
https://github.com/blastagator/cm_device_lge_g2-common/blob/cm-13.0-twrp/README.md
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
XDA:DevDB Information
TWRP Touch Recovery w/ Thermal Control and F2FS, Tool/Utility for the LG G2
Contributors
blastagator, TeamWin, and everyone else listed above!
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-12-23
Created 2014-11-02
Last Updated 2019-12-31
Announcements
May 7, 2016
New CM-13 based build is released! Enjoy all.
May 4, 2016
New release coming this weekend. Make any complaints ASAP about version -g!
VOTE on if you want me to TRY to fix AROMA. (No guarantees!!!)
http://forum.xda-developers.com/lg-g2/general/twrp-poll-aroma-t3372512
April 30, 2016
Release candidate! Give it a test!
http://forum.xda-developers.com/showpost.php?p=66626361&postcount=2543
April 17, 2016
New beta using cm-13 sources. Click HERE. Please test!
April 7, 2016
TWRP 3.0.0-2 is here! Versions older than 2.8.7.3 have been removed from my download site.
February 17, 2016
(Working!) TWRP 3 is here!
More info: https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
.
Change Logs
December 23, 2019 (3.3.1-0)
-TWRP Change Log:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Click to expand...
Click to collapse
April 29, 2019 (3.3.0-0)
-TWRP Change Log:
* 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)
Click to expand...
Click to collapse
September 22, 2018 (3.2.3-0)
-TWRP Change Log:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Click to expand...
Click to collapse
July 21, 2018 (3.2.2-0)
-TWRP Change Log:
adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations
Click to expand...
Click to collapse
December 17, 2017 (3.2.1-0)
(Bug fixes for 3.2.0)
-TWRP Change Log:
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)
Click to expand...
Click to collapse
-TWRP 3.2.0-0 Change Log:
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
Click to expand...
Click to collapse
December 3, 2017 (3.2.0-0)
Removed and replaced with 3.2.1-0
May 20, 2017 (3.1.1-0)
-TWRP Change Log:
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)
Click to expand...
Click to collapse
March 13, 2017 (3.1.0-1)
Rebuild of 3.1.0-0 (from 2017.03.10) - Add ability to boot with JB bootloader.
-TWRP Change Log:
-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
Click to expand...
Click to collapse
-Tree
++Bootloader offset is now 128!
If you are having OTA problems, make sure your ROM maintainer adds this to their device tree: https://github.com/blastagator/cm_d...mmit/946434d0881b50437422e7855d5d7a096d9608e1
Also, /misc needs to be mounted: https://review.lineageos.org/#/c/19334/)
++Completely rebased onto cm-14.1
++Remove custom USB - Use G2+TWRP usbs instead
++Tweaks to enable compatibility with old bootloader
-Kernel
++Completely rebased onto cm-14.1
++Tweaks to enable compatibility with old bootloader
++Disable lots of unneeded things and changed kernel compression
------------- All builds above this line are cm-14.1 based. -----------------
------------- All builds below this line are cm-13 based. -------------
May 7, 2016 (3.0.2-1)
-Tree
++Completely rebased onto cm-13
++All file utilities, etc. are now up-to-date with the latest cm-13 tree.
++Changed from debug builds to engineering builds, per TeamWin instructions (thanks @Startrek852)
-Kernel
++Took cm-13 kernel and added my stuff to it
++Disabled some tuner/multimedia stuff we don't need
++Updated f2fs
-TWRP
++New splash screen
++New fstab processing
++Fixed AROMA graphic bug. If AROMA still crashes, try this:
http://forum.xda-developers.com/showpost.php?p=66747442&postcount=2591
++Lots of language updates.
------------- All builds above this line are cm-13 based. -----------------
------------- All builds below this line are omni-4.4 based. -------------
April 7, 2016 (3.0.2-0)
TWRP 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords).
++This fixes decrypt of full device encryption on devices that support decrypt.
++This bug also impacts encrypted backups.
++Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
Click to expand...
Click to collapse
TWRP 3.0.1-0:
-Support new CM 13.0 pattern encryption (sultanqasim)
-Fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-Fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-Translation updates - added Italian, Czech and Polish and significant updates to Dutch
-Progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-Fix input box text display (Dees_Troy)
-Reboot option after zip install complete (bigbiff)
-Other mostly invisible bug fixes and improvements
Click to expand...
Click to collapse
Device / Kernel / etc.
-No changes
February 17, 2016 (3.0.0-4)
TWRP Change Log:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
Click to expand...
Click to collapse
My Change Log:
-TWRP:
++Re-enable RO check/warning - MM is potentially sensitive to RO
++NTFS Support
++Remove bootloader backup (user should use zips to manage bootloader instead)
++Enable extra languages (lots of options!)
-Device Tree:
++Fixed decryption
DO NO ENCRYPT f2fs - Bootloop of ROM and Recovery will occur!
++Fixed USB init problem (created custom usb recovery init by combining parts of g2 init and twrp init)
++Switched to using TWRP init w/ additional inits added via proper method
++Update external_sd init
++Restructure g2 device repo to further isolate 'TWRP' parts
++Enable QCOM Overlay Graphics
++Remove non-functioning LED part of postrecoveryboot.sh
-Kernel
++Fixed decryption
++Updated f2fs (to latest, @dorimanx for helpful commits)
++Enable NTFS
++Update exfat driver
++Fix lge usb gadget config options
++Some other misc. updates
November 9, 2015 (2.8.7.3)
-Sorry about bad 2.8.7.2 build
-Still built off of omni-4.4 source code. (Android-M isn't ready for a full release yet.)
-Vendor: Complete overhaul of vendor blobs, now using cm-12.1-caf branch from lg-devs
-TWRP: Make separate flags for ability to backup or restore partitions
-Device: Add ability to backup/restore Bootloader partitions
++User cannot use TWRP to restore Bootloader, too dangerous!
-Device: Removed system_image
++We don't need this for our phone and it was confusing people who didn't READ the change log
-TWRP/Device: Remove any warnings about system mount RO, this isn't important for our phone
-Device: Set max brightness to actual max (255)
-Device/TWRP: Create default brightness, set it to 175 (~68%)
-Kernel: Latest f2fs driver
++This should fix issue where ROM running kernel with newest f2fs doesn't boot
++Note: This breaks compatibility with ROM using old f2fs driver. Read note below.
-Kernel: Other commits that were needed to make latest f2fs driver work
-Kernel: Config changes that might allow encrypted f2fs to work now!
-Kernel: Enable SELinux
++Before I accidentally completely disabled, now it should boot Enabled, but in Permissive mode.
-TWRP: More tweaking to recreation of media folder / setting internal storage path
-Device: Remove integrated supersu
IMPORTANT - f2fs /data note: If you restore OLD backups, you will probably cause ROM or recovery (or both) to hang! This is obviously bad because your only option at that point is doing a back to stock kdz. To avoid problems, make NEW backups AFTER upgrading to the new version of TWRP. Backups made with 2.8.7.3 can be restored with 2.8.7.3 without causing issue.
October 31, 2015 (2.8.7.2)
-Broken build!
-Device: Add ability to backup/restore Misc partition
++Caused broken build. Do not use this version.
June 24, 2015 (2.8.7.1)
-Make sure you have newest Theme (or no theme).
-Fixed internal storage path, I had it wrong for long time, sorry!!! https://github.com/blastagator/cm_d...mmit/cbfe7d09d95890b4e26f673c9db937840167da9b
-Turned down max screen brightness, no need to fry phone
-Fixed TWRP not assigning proper context to Internal Storage when wiping: https://github.com/blastagator/andr...7903af041ad00146aee866#commitcomment-11848774
++Full wipe of phone will now always recreate folder properly!
++Bumped version up by .1 to reflect change to actual TWRP code.
-Add ability to backup "System Image"
++YOU VERY LIKELY DON'T NEED THIS. (If you're on anything other than stock ROM already, you DEFINITELY don't need it.) We have KDZ flashing to get back to stock.
++This creates a raw, emmc, backup of the System partition (instead of file backup)
++Has to do with new OTA issues (which aren't an issue for G2 yet, if ever)
++Not really important for us, but TWRP added it, so I added it too: https://github.com/omnirom/android_bootable_recovery/commit/eb32b1ff00878e7b01453450fcd04ecb9fcbba52
++See also: https://github.com/blastagator/cm_d...mmit/e28ab9cef31d6574a6f6e1f92b97f94bcbdda584
-TWRP Updates:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Click to expand...
Click to collapse
May 25, 2015 (2.8.6.3)
-Updated f2fs kernel module to match the version used by @dorimanx
-Updated vendor blobs by applying all changes from lg-devs and using newest 12.1 branch
-Updated e2fsprogs (the binaries used to manipulate the filesystem) to latest cm-12.1 version
-Updated to using the newest branch for qcom_common
-Updated f2f2-tools by forking cm-12.1 and making some tweaks (Git)
-Fixes the issue where TWRP won't load if you're using Lollipop with f2fs
-Relocated common manifest to g2-common git
-Enable new Qualcomm HW Decrypt flag
-TWRP Fixes:
++Prevent multiple unlock screens
++<MAYBE> Enable proper decryption of an encrypted /data partition
Much Older Versions:
May 24, 2015 (2.8.6.2)
-Test build that is now removed.
-Only built for d800 & d802.
May 2, 2015 (2.8.6.1)
-Added lgl22 support. All models now supported!
Mar 30, 2015 (2.8.6.1)
-Added ability to backup/restore Sensors partition (per user request)
-Thanks to @_that for tipping my off to my previous error (& @z31s1g who's themeing led to problem discovery)
-TWRP Changelog:
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
Click to expand...
Click to collapse
Mar 28, 2015 (2.8.6.0)
-Improperly built 2.8.6.0
-Used wrong TWRP tree. Oops!
Feb 15, 2015 (2.8.5.1)
-Corrected build of 2.8.5.0
-Edited the init.rc (see: https://github.com/omnirom/android_bootable_recovery/commit/df7abac1a645949ded76418759236bc3b14f107e)
-Also made a slight tweak to move tap-to-wake to a separate init (should make it easier to update the init.rc in the future if it is changed)
-FIXED: sd_card init was not being copied correctly. Relocated it to /etc and made appropriate related changes. (I guess this wasn't getting in the way of sd_card working, but it is proper to include this file.)
-NEW FILE HOST: Now using spideroak.com, they advertise no download limits!
Feb 13, 2015 (2.8.5.0)
-Merged upstream vendor blobs (Updates from lg-devs)
-TWRP Changelog:
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
Click to expand...
Click to collapse
Jan 13, 2015 (2.8.4.0)
-Changed Kernel Configs so default kernel state is SELinux Permissive.
++There was already a change that allowed TWRP to immediately change to Permissive, now it is Permissive immediately.
-Made a few changes to g2-common to accommodate lgl22 (when I get around to getting that working).
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
Click to expand...
Click to collapse
Dec 27, 2014 (2.8.3.1)
-Tweaked the fstab file
++Changed partition type to ext4 from auto - this should fix broken Format Data / Factory Reset. However, f2fs is still supported. My f2fs cache partition still mounted in twrp even though fstab was set to ext4.
++Added the encrypt partition to the fstab. This should enable twrp to mount encrypted /data partitions. I don't know if this is the problem or not. The one person I asked to try it didn't have any luck. Please others try and let me know if it works or what errors you get. NOTE: An encrypted f2fs /data partition will probably NOT work in this configuration.
Dec 24, 2014 (2.8.3.0)
-Version 2.8.3.0
What's new in 2.8.3.0:
MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
MTP will now tell the host PC that storage is removed instead of disabling MTP completely
MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
Update and improve fix permissions and make fixing contexts optional
Update SuperSU in TWRP to 2.40 and update install process
Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
Fix kernel panic during MTP start on some devices
Support unicode fonts on devices with True Type Font support
Fix slider value not showing sometimes (vibration settings page)
Toggle MTP off during adb sideload to set correct USB IDs
Reduce library requirements for 5.0 L decrypt
Other minor fixes and improvements
Click to expand...
Click to collapse
-Update g2-common to ensure se_linux will be set to permissive at boot of recovery
Dec 18, 2014 (2.8.2.1)
-Full repo sync
-Check the omni git for changes
-Looks like Dees_Troy pushed quite a few bug fixes over the past couple of weeks
-Switched device tree to start using 'L' encryption
Dec 11, 2014 (2.8.1.2)
-Rebuild of 2.8.1.1
-Uses the new device trees
-Adds l01f for this version
-BUMPed (2.8.1.1 was not)
-I recompiled this version due to various bug complains involving 2.8.2.0 in general - in case anyone wants to stay on old version til those get sorted out.
++I'm not aware of any specific issues.
Dec 9, 2014
-Created custom l01f kernel config.
-Built and added l01f variant.
Dec 6, 2014 (2.8.2.0)
-Reworked all device trees to use the CM stock device trees + a couple mods to add TWRP support.
-Still using the Omni4.4 source.
-BUMP'ed and new flashing script that still auto-detects panel type but does NOT use loki.
++Bump works on JB & KK bootloader.
-All the other goodies as listed in 2.8.1.9.
-If you're on d800 and want to upgrade to KK bootloader, go here.
Dec 2, 2014 (2.8.1.9)
-Built with Omni 4.4
-TWRP 2.8.2.0 Source (LP5.0 for TWRP source only)
-Labeled as 2.8.1.9 just for clarity when I redo the device trees and rebuild.
-Team Win Change Log:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
Click to expand...
Click to collapse
Oct 25, 2014 (2.8.1.1)
-Corrected bug where "Internal Storage" was being listed as "Data"
-F320: Added additional properties to External SD mount.
++Should now be able to wipe External SD under advanced wipe.
++Should not get error when booting TWRP with no External SD card inserted.
Oct 24, 2014 (2.8.1.0)
-Team Win released version 2.8.1.0 [TeamWin Page]
What's new in 2.8.1.0:
MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
Temperature support - thanks to bigbiff
Various other bugfixes and tweaks
Click to expand...
Click to collapse
-Full repo sync and upstream merges on all sources.
-F320 External SD Card is now supported.
-Ability to backup Modem and Recovery partitions
Oct 20, 2014 (2.8.0.2)
-Because incrementing a digit by 1 is always better!
-Full repo sync and upstream merges on all sources.
(That is - TWRP source, device tree source, g2-common source, and aicp source are all the newest available!)
-Compiled completely from scratch. (No need for hodge-podge as previous version.)
-TWRP now shows CPU temperature.
-F320 variant should work now.
(Which is nice for F320 users since it looks like it has been awhile since getting a new version of TWRP!)
-Simplified file naming convention for the downloads.
-Original release used old loki. New zips are posted with newest loki and newest panel detection script! Should work on all phones now.
Oct 19, 2014 (2.8.0.1)
-Changed to AICP kernel to add thermal control!
-Patched AICP kernel to support F2FS.
-2.8.0.1 Base came from DrGravy (this version is a composite of a few different sources)
-Tap to wake works now.
-TWRP Version 2.8.0.1
-Some bug fixes that came along with 2.8.0.1
Oct 18, 2014
-Not actually a new build, just a big information update!
-Added info for adding full f2fs support to your kernel.
-Looking in to compiling TWRP with the AICP kernel to add thermal support.
Oct 10, 2014
-Full repo sync.
-Changed vendor tree from a CM11 build that I had been using to dr87's git.
-Built for (almost) all LG G2 models.
------------- All builds below this line are for D800 ONLY! -------------
Oct 8, 2014
-Fully sync'd everything to the above listed gits
-Moved the tap to wake code out of bootable/recovery and into a custom recovery init.rc
-Moved a couple files into g2-common/twrp folder to improve organization
-Sync'd with main repo to get any code changes and confirm the init.rc wasn't causing issues anymore
-Posting this build in .img and .zip format
Oct 7, 2014 (Build 2)
-Added postrecoveryboot.sh (Forgot to include it in the original build)
Oct 7, 2014
-Initial Release
-Based on latest OmniRom TWRP Source
-Kernel is based on Stock Kernel patched w/ F2FS for 3.4 kernel
FAQ
My OTA isn't working or I am now in a bootloop to TWRP.
To get out of the bootloop, connect to adb shell, and issue:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
This should resolve the problem. If not, search the thread, some people have other suggestions for various places to nuke the bad commands residing in /misc. To avoid the future problem, contact your ROM maintainer with the following info.
Starting in Android N, the ROM uses /misc partition to communicate with recovery. (Therefore if your ROM is M or lower, OR uses the old communication method, this is not relevant to you). To address OTA problems, it is important to note the newly introduced bootloader offset.
https://review.lineageos.org/#/c/165001
Also, /misc needs to be mounted:
https://review.lineageos.org/#/c/19334/
Your ROM maintainer should add these to their device tree. This will insure that ROM will write to the exact place the recovery is reading from.
I see error: "E: mount -0 bind '/data/media' '/sdcard' process ended with error=255" when I switch partition type on /data.
Update to new version, 2.8.7.1. This problem is fixed.
I see error: "assert failed: run_program(" /tmp/loki.sh") == 0" when I flash X. Why?
Loki is only supported by JB BL. Loki is smart enough to check your BL version before flashing. If you are on KK BL and the thing you are flashing uses loki, you're going to get this error. New BL requires you to use bump.
Now that I have bump, how do I update to the KK bootloader?
If you have a d800 (or d801), see my thread here. If you have a d802, see @dorimanx's thread, here. Credit's to dori for inspiring me to make the package for d800.
USB-OTG isn't working, why not?
To use USB-OTG your device needs to be formatted fat32, not NTFS.
I'm having trouble formatting partitions. Why doesn't it work?
Fixed: As of 2.8.3.1
The option to Format Data or do Factory Reset probably won't work. The fstab is set to auto to support f2fs and those two options don't know how to deal with auto (they don't know if you want them wiped to ext4 or f2fs). Therefore, you need to do Advanced Wipe, which works fine. If you are still having trouble, make sure MTP isn't on and make sure your USB isn't plugged in.
OMG, my TWRP thinks this is the 1970s?! HALP!
This is an issue that arises in Android L (for whatever reason). Member murdoch1 found this and confirmed that installing it fixes the 1970 issue in TWRP.
Does [xyz] work?
As far as I know, everything works except for known issues in the common twrp source.
I want to report [xyz] as not working, how do I do it?
Post in this forum. I'll do what I can to fix it.
When will the next version come out?
I don't plan on building again unless a bug is discovered that I can fix, or if TeamWin releases the next version.
Why don't you do [xyz]?
Why don't you do it?
Why doesn't F2FS work?
It DOES work in the recovery. To get it working on your ROM you need to have proper kernel support. Many AOSP ROMs support f2fs partitions. Additionally, dorimanx has added working f2fs on his stock kernel.
Why doesn't AROMA work?
AROMA is old. As of version 3.0.2-1, I added a hack to fix the graphics. If your zip file still isn't working, try my guide:
http://forum.xda-developers.com/showpost.php?p=66747442&postcount=2591
F2FS Information
WARNING: Changing Partition type of /data WILL wipe ALL data, including INTERNAL SD!
You need to specifically backup Internal SD, TWRP does not automatically do this when you backup /data!
(This only applies if you change from ext4 to f2fs, or vice versa; other operations will not magically wipe your partitions.)
WARNING 2: DO NOT ENCRYPT F2FS - ROM and RECOVERY will BOTH bootloop and you'll be doing back to stock method!!!
If you want to use F2FS:
1) Make sure your kernel and ramdisk support f2fs (the dev of your ROM/kernel should have f2fs support noted). Dorimanx stock kernel as well as many AOSP kernels have full f2fs support.
2) Install and boot into my recovery.
3) Go to Wipe, Advanced Wipe, select /data, then click Change Partition Type. Select f2fs, and it will convert. Repeat this process for /cache.
4) Reboot the recovery, NOT reboot to system. DO NOT DO ANYTHING ELSE UNTIL YOU REBOOT RECOVERY!!!
5) Reboot OS. That's it! You're ready to go.
If you want to switch to F2FS without losing your data:
1) Make sure your kernel and ramdisk support f2fs (the dev of your ROM/kernel should have f2fs support noted). Dorimanx stock kernel as well as many AOSP kernels have full f2fs support.
2) Install and boot into my recovery.
3) Make a backup of your /data partition and copy it to your PC via MTP. Also, copy the content of your /sdcard to your computer. Both of these things will be destroyed when you switch partition type!
4) Go to Wipe, Advanced Wipe, select /data, then click Change Partition Type. Select f2fs, and it will convert. Repeat this process for /cache.
5) Reboot the recovery, NOT reboot to system. DO NOT DO ANYTHING ELSE UNTIL YOU REBOOT RECOVERY!!!
6) Copy your backup via MTP to your phone. Restore your /data partition.
7) Copy your sdcard files back to your sdcard. (NOTE: For some reason, when I do this, the files end up getting deleted, you may need to copy the sdcard files over after your reboot into your OS.)
8) Reboot OS. That's it! You're ready to go.
Don't complain if you didn't read everything in all 5 of these posts!
Very nice! Im glad to see more work being done to bring F2FS to the G2. I dont know enough about getting into the ROM and kernels to get this going myself, but I will be following the development more closely now and hope someone else is gracious enough to port one of the stock based ROMs to work with F2FS. I think I remember seeing Dorimanx kernel has support for the file system already too, just no recovery or ROM that was capable at the time.
blastagator said:
Problem: We need a kernel/ramdisk that will mount the partitions in a ROM!
On my ROM I am using Dori's kernel with which has the f2fs module. However, even though it has the module, the /cache partition does not mount when the rom boots. Perhaps a ramdisk fstab issue? - Possibly my next adventure...
Click to expand...
Click to collapse
You may need to rebuild his kernel (or rip the ramdisk out of a pre-built one and inject it back in after modifying it) and explicitly mount the cache partition as f2fs.
https://github.com/dorimanx/LG-G2-D802-Ramdisk/blob/kitkat-ramdisk/ROOT-RAMDISK/fstab.g2
You'd probably need to add it with these, though I'm unsure why it's not already listed. It may be in the built ramdisk, built into the file during the compile... It may also be mounted after boot in one of the .rc scripts... But I'm used to seeing all the partitions laid out in the fstab on previous devices.
Have you tried manually mounting via terminal once you've booted? I'm assuming that works and you're just trying to make it auto-mount?
Yoinx said:
You may need to rebuild his kernel (or rip the ramdisk out of a pre-built one and inject it back in after modifying it) and explicitly mount the cache partition as f2fs.
https://github.com/dorimanx/LG-G2-D802-Ramdisk/blob/kitkat-ramdisk/ROOT-RAMDISK/fstab.g2
Click to expand...
Click to collapse
I was thinking modify the fstab. However, in dori's kernel, the fstab.g2 doesn't even have entries for /system /data or /cache. In the recovery I changed those partitions from ext4 to auto. I planned to do the same on the kernel. Even though the fstab is different, I was going to try adding mounts for those 3 partitions and see what happened. However, I couldn't get the image repacked. I used the non-standard mkbootimg from the compiling of the recovery. I tried several different commands to repack - all of which led to a boot loop. (Except one, which got me fastboot because the offsets were wrong.)
Alternatively I was going to recompile the dori kernel but I haven't really delved into adding the custom ramdisk into that compile, got too tired last night.
Yoinx said:
Have you tried manually mounting via terminal once you've booted? I'm assuming that works and you're just trying to make it auto-mount?
Click to expand...
Click to collapse
Using: mount -t f2fs /dev/block/platform/msm_sdcc.1/by-name/cache /cache
The partition mounted properly using the dori's build of dori's kernel 8.0.1
You can get something like kernel workshop, extract the boot.img into the kernel and ramdisk to play with whatever then repackage it without recompiling.
Yeah, I saw the fstab is a bit odd. I thought they were moving to a new mount system but I couldn't find it handily
Yoinx said:
You can get something like kernel workshop, extract the boot.img into the kernel and ramdisk to play with whatever then repackage it without recompiling.
Yeah, I saw the fstab is a bit odd. I thought they were moving to a new mount system but I couldn't find it handily
Click to expand...
Click to collapse
Dori was nice enough to point it out for me:
https://raw.githubusercontent.com/dorimanx/LG-G2-D802-Ramdisk/kitkat-ramdisk/ROOT-RAMDISK/fstab.g2
https://github.com/dorimanx/LG-G2-D802-Ramdisk/blob/kitkat-ramdisk/ROOT-RAMDISK/init.target.rc#L45
I plan to fiddle with it
Simple enough. They're just running it in the scripts then. I modified my old phone's kernel to have simulated run levels by running a script from each of the points in the init.rc events, so you could run commands at various points throughout the boot sequence via init.d essentially. I liked the feature, but I don't think many others really had a use for it.
Same concept, the only downside by it being hard-coded is that you need to repack each time instead of just modifying an init.d script on the fly.
Glad you found it though
Yoinx said:
You can get something like kernel workshop
Click to expand...
Click to collapse
Try googling "kernel workshop" --- grumble
Sorry man. I usually post from my phone, so it's hard to verify some of what I'm saying...
http://forum.xda-developers.com/showthread.php?t=2073775
It's android image kitchen. I had the wrong name.
Yoinx said:
Sorry man. I usually post from my phone, so it's hard to verify some of what I'm saying...
http://forum.xda-developers.com/showthread.php?t=2073775
It's android image kitchen. I had the wrong name.
Click to expand...
Click to collapse
Thanks. I've been fighting with that as one of my options. The g2 requires a dt.img as well as a non-standard mkbootimg, so it is driving me up the wall!
blastagator said:
Thanks. I've been fighting with that as one of my options. The g2 requires a dt.img as well as a non-standard mkbootimg, so it is driving me up the wall!
Click to expand...
Click to collapse
Interesting. I haven't started really building anything for the G2 yet.... not enough time IRL at the moment. When I flash kernels though, it's just boot.img.
What's this dt.img that you're talking about? The non-standard mkbootimg is typically just just for offsets.
You may be better off just downloading the kernel sources and building from scratch if the imgtools dont work.
Looks like this guy's got a version of the mkbootimg tools that supports dt.img https://github.com/xiaolu/mkbootimg_tools if you're running linux (hopefully, since it makes things MUCH easier)
Yoinx said:
Looks like this guy's got a version of the mkbootimg tools that supports dt.img https://github.com/xiaolu/mkbootimg_tools if you're running linux (hopefully, since it makes things MUCH easier)
Click to expand...
Click to collapse
You sir are a god send! Unpacked the Dori kernel, repacked, and the repacked image booted right up!!! I'll be sure to update if I make any headway with automount
Oct 8, 2014 Build
-Fully sync'd everything to the above listed gits
-Moved the tap to wake code out of bootable/recovery and into a custom recovery init.rc
-Moved a couple files into g2-common/twrp folder to improve organization
-Sync'd with main repo to get any code changes and confirm the init.rc wasn't causing issues anymore
-Posting this build in .img and .zip format
Signed Zip: https://www.dropbox.com/s/sd1lo0mijouu6kg/2014.10.08-blastagator-twrp-2.8.0.0-w.f2fs-signed.zip?dl=0
Zip MD5: https://www.dropbox.com/s/xmw5e4pzw...gator-twrp-2.8.0.0-w.f2fs-signed.zip.md5?dl=0
Img: https://www.dropbox.com/s/gmzfyg7rs8guw1m/2014.10.08-blastagator-twrp-2.8.0.0-w.f2fs.img?dl=0
Oct 10, 2014 Build
-Full repo sync.
-Changed vendor tree from a CM11 build that I had been using to dr87's git.
-Built for (almost) all LG G2 models.
-deleted- (double post)
Your title for the OP says it is for the vs980 as well...
I don't not see a link for it though
Goodbye Lollipopalooza... Hello Marshmallicious!!
{
"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"
}
This started out as a personal project... a way for me to learn how to develop and custom features for Android. And I decided to share my work with the amazing Android community... something to give back to the community. Back then, this was a ROM called ThunderKat, based on Android 4.4 KitKat. Over time, it evolved into Lollipopalooza, based on Android 5.0. And now, here's Marshmallicious, based on Android 6.0.
Now, before you go on ahead, let me be clear about one thing. This is and will remain a minimal AOSP based ROM. It will include a small, but useful set of features... features which add a bit more flare to Android AOSP. Beyond this minimal feature set, this will also include some relevant spit and polish (bug fixes and asset/image updates). As time progressed, so did the quality of the work behind the features this ROM offers. Whenever I look back at a feature I developed before, I look for ways to improved. If you expect a lot of additional features, I recommend using one of the more popular ROMs available like CyanogenMod, SlimRoms, ParanoidAndroid, etc.
I develop and maintain this ROM on my own for the most case, occasionally seeking help and porting useful features and fixes that others here in the community have developed. You will see all the relevant references in the cherry-picked commit in my GitHub repositories.
Due to my limited availability, I will now no longer support Lollipopalooza builds
Now that I'm done with the fancy introduction, let's get down to business...
Changelog:
2015/11/07
1. Fixed force close when choosing keyboards in Language & input settings
2. Enabled doze/ambient mode auto power saving modes (More details)
3. Removed SVELTE (Nexus 9 LTE) init configs from Nexus 9 Wifi init configs
4. Disabled bug report service (which is triggered by holding down volume down, volume up and power)
5. Updated SELinux policies for experimental systemless root using open source Superuser (instruction below)
6. Fixed experimental systemless root for devices with encrypted userdata
2015/11/04
1. Android Marshmallow 6.0.0_r2 (MRA58N) base [Includes November 2015 security patches by Google]
2. Movable on-screen navigation bar buttons (centre, left or right) [Settings > Device > Display]
3. Cursor control within text boxes using the volume rocker [Settings > Personal > Language & input]
4. Long-press of back button to kill foreground app [Settings > Personal > Language & input]
5. Native Android Marshmallow recents dismiss/clear all
6. User-defined custom device hostname [Settings > Wireless & networks > More]
7. Displays apps installing and optimising storage progress on first boot
8. Uses Google pre-built WebView if it is installed. Falls back to AOSP WebView
9. SystemUI Tuner enabled by default
10. Dessert Cake dream enabled and set as default doze dream
11. Enhanced Location QuickSettings tile (toggles between the different location mode [Off > Sensors Only > Battery Saving > High Accuracy])
12. Long-press action for all QuickSettings tiles (opens relevant Settings section)
13. Enhanced power menu [Power Off, Reboot, Aeroplane Mode, Users & Sound Toggle]
14. Advanced reboot [Reboot, Reboot to recovery, Reboot to bootloader] (only available for primary user when device is unlocked)
15. Default required permissions set for Google applications to allow GoogleApps packs
16. F2FS support for the cache partition in addition to the userdata partition.
17. Additional filesystems supported (with vold auto-mount capabilities not available yet) [exFAT and NTFS (NTFS-3G)]
18. Forced encryption of userdata partition is disabled
19. DM-Verity (key-based partition verification) is disabled system-wide
20. Full-screen on-screen keyboard in landscape mode is disabled
21. Sysinit supported (init.d scripts)
22. @Captain_Throwback's BeyondStock kernel 2.0.0 included [support NTFS, exFAT and fast-charge]
23. Several assets and images updated to Material-styled versions
24. Ambient (Doze) mode enabled along with burn-in protection
25. A lot of unneeded debug logging disabled
26. Default wallpaper replaced with Marshmallow stock default wallpaper and Marshmallow stock bootanimation added
27. Includes bionic busybox (credit CyanogenMod)
28. Increased number of status bar notification icons from 5 to 8
29. Miscellaneous bug-fixes and tweaks included (for more details, check the GitHub commits)
30. Full GoogleApps pack (with ARM64 320DPI apps where applicable) with the latest updates
Instructions:
1. Download the Marshmallicious ROM package and the Prerequisites package
2. [OPTIONAL] Download the GoogleApps package
3. Reboot into recovery [A custom recovery like TWRP is required]
4. Wipe as required
a. Full wipe when coming from another ROM
b. Wipe cache and dalvik-cache when flashing a Marshmallicious update5. Flash the packages in the following order
a. Prerequisites package
b. Marshmallicious ROM package
c. [OPIONAL] GoogleApps package6. Reboot and let the device boot up and remember that the first boot will take a while since this is a de-odex ROM
Root:
I do not support SuperSU because it is closed-source and, hence, cannot be audited. Anything granting low-level privileges to apps and process need to be open-source and auditable. But I will not blankly turn down support requests involving SuperSU if you have chosen to root your ROM using SuperSU.
That said, I am closely following the development of systemless open-source Superuser by @phhusson as well as the SELinux policy changes by @doitright. This is still experimental and may not support all root apps yet.
Because this is currently experimental, this ROM is not pre-rooted. But I have provided a separate ExperimentalRoot package. This package contains a modified boot image with the su binary, init changes and SELinux policy changes and has been built from source. The su binary was built with the latest changes in @phhusson's Superuser GitHub repository. The init and SELinux policy changes are a slightly varied version of the patch created by @doitright. Also included in the zip is the Superuser apk built with the latest changes in @phhusson's Superuser GitHub repository.
I have branches in my GitHub repository which have the SELinux policy and init changes required for systemless Superuser which include all doitright's changes as well as my modifications.
platform_external_sepolicy
platform_system_core
Instructions:
1. Download the ExperimentalRoot package provided above (make sure it matches the ROM release date)
2. Flash the boot image included in the ExperimentalRoot package using fastboot [fastboot flash boot boot.img]
3. Install the Superuser apk included in the ExperimentalRoot package as a regular app
Downloads:
AndroidFileHost
Marshmallicious-Nexus9-Wifi-20151107.zip [Marshmallicious ROM]
GoogleAppsPack-6.x-ARM64-320DPI-20151107.zip [Full Google Apps Pack]
Prerequisites-Marshmallicious-Nexus9-Wifi-MRA58N.zip [Prerequisites (bootloader and vendor images)]
ExperimentalRoot-Marshmallicious-Nexus9-Wifi-20151107.zip [Experimental systemless open-source Superuser]
BasketBuild
Marshmallicious-Nexus9-Wifi-20151107.zip [Marshmallicious ROM]
GoogleAppsPack-6.x-ARM64-320DPI-20151107.zip [Full Google Apps Pack]
Prerequisites-Marshmallicious-Nexus9-Wifi-MRA58N.zip [Prerequisites (bootloader and vendor images)]
ExperimentalRoot-Marshmallicious-Nexus9-Wifi-20151107.zip [Experimental systemless open-source Superuser]
Theming:
This ROM support RRO/Layers themes. But please be aware that not all RRO/Layers themes support Android Marshmallow yet. If you encounter force closes after installing a theme, reboot into recovery mode and delete /vendor/overlay.
Layers/RRO Themes Info:
1. Join the BitSyko Google+ Community for the latest information and themes
2. Download the Layers Manager app to install/uninstall/preview RRO/Layers themes
3. Download the Layers Showcase app to browse available RRO/Layers themes
4. Visit this XDA thread for a comprehensive list of RRO/Layers themes
Help and troubleshooting:
1. Ask for help if you need, but make sure you do your research first.
2. Be patient. It could take a few minutes to flash the ROM.
3. If you flashed a kernel which replaced the SELinux policy file, you may encounter errors and issues. To recover, you will need to reflash the ROM boot image.
4. If you get "failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP", unmount the system partition and try again
5. If you flashed a kernel with SELinux disabled like the one provided by @USBhost on a previous build, make sure you flash that kernel after flashing the update (before you reboot), or you will get a bootloop and will have to perform a recursive restorecon on the /data partition to restore the SELinux contexts.
6. If you have a folder created in TWRP recovery mode which you cannot access when you boot up the ROM, you will need to perform a recursive restorecon on that folder restore the SELinux contexts.
7. Be ready to provide a clear description of your issues and please provide logcats, dmesg logs and kmesg logs whenever possible.
Sources:
Marshmallicious Manifest
All repositories
Disclaimer
Marshmallows are always delicious... but be careful!!! Make sure you know your limits!!! If you don't know what you are doing, the marshmallows provided here could be life-threatening and render your device inedible. Every marshmallow here has undergone extensive scrutiny, but there is always a chance that something slipped through the cracks since baking is more an art than a science. So if you use the marshmallows here, don't hold the chef responsible for baking these goodies (me!)
Support this project:
If you like my work, buy me a beer so that I can pass time while my laptop churns out builds...
Paypal
Google Wallet (Send Money to craigacgomez[at]gmail[dot]com)
Credits:
Google, NVidia, ARM, Chainfire, 0xD34D, CyanogenMod team, PureAOSP team, Chroma team, BitSyko team, AndroidFileHost, BasketBuild, phhusson, doitright, XDA (any probably some more I can't remember)
Reserved...
And one more... just in case!!
Will test and report back
Upload complete at last (AndroidFileHost crapped out on my half way through!) Link in OP!
craigacgomez said:
Upload complete at last (AndroidFileHost crapped out on my half way through!) Link in OP!
Click to expand...
Click to collapse
Can you edit the ROM to not encrypt data
BTW love the Disclaimer!!
USBhost said:
Can you edit the ROM to not encrypt data
Click to expand...
Click to collapse
Definitely planning on doing that next. I will spend some time on this tomorrow...
Awesome, the first rom is out! let the flashing begin!
craigacgomez said:
Definitely planning on doing that next. I will spend some time on this tomorrow...
Click to expand...
Click to collapse
hows its going
found it?
You have a commit that enbales App Opps? Thanks for this. Loved your ROM for my N10.
USBhost said:
hows its going
found it?
Click to expand...
Click to collapse
Found it. It's actually a kernel change... well, a change in the fstab. Changing the forceencrypt mount flag to encryptable makes it encryptable, but with encryption disabled by default.
Change these line in the kernel initrd fstab.flounder & fstab.flounder64
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
to
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
or fstab.flounder in the flounder device tree.
craigacgomez said:
Found it. It's actually a kernel change... well, a change in the fstab. Changing the forceencrypt mount flag to encryptable makes it encryptable, but with encryption disabled by default.
Change these line in the kernel initrd fstab.flounder & fstab.flounder64
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,forceencrypt=/dev/block/platform/sdhci-tegra.3/by-name/MD1
to
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
or fstab.flounder in the flounder device tree.
Click to expand...
Click to collapse
So i change it
Then do a factory reset
And i should be good?
jarjar124 said:
You have a commit that enbales App Opps? Thanks for this. Loved your ROM for my N10.
Click to expand...
Click to collapse
I could get you a diff.... or wait for a day or so till I start pushing stuff to GitHub.
craigacgomez said:
I could get you a diff.... or wait for a day or so till I start pushing stuff to GitHub.
Click to expand...
Click to collapse
I can wait. Thanks for your hard work!
like this right??
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/VNR /vendor ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/EBT /bootloader emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/PST /persistent emmc defaults defaults
/dev/block/zram0 none swap defaults zramsize=533413200
USBhost said:
So i change it
Then do a factory reset
And i should be good?
Click to expand...
Click to collapse
Yes...
USBhost said:
like this right??
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/VNR /vendor ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,errors=recover wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/EBT /bootloader emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/PST /persistent emmc defaults defaults
/dev/block/zram0 none swap defaults zramsize=533413200
Click to expand...
Click to collapse
Correct! There are 2 fstab file (The 64 bit build has 2), edit both...
craigacgomez said:
Yes...
Correct! There are 2 fstab file (The 64 bit build has 2), edit both...
Click to expand...
Click to collapse
ok awesome doing a factory reset now
Edit: can you add long back to kill app
---------- Post added at 07:34 PM ---------- Previous post was at 07:13 PM ----------
it booted
and it worked cheers tytyty
---------- Post added at 07:45 PM ---------- Previous post was at 07:34 PM ----------
it feels so much faster now
Just curious about what people are willing to try when it come to custom ROMs... The Nexus 9 is a 64-bit capable device and AOSP allows for 3 variations in the build
1. 64-bit with 32-bit support (like the stock ROM and this ROM here)
2. Pure 64-bit (no apps with libraries not in 64-bit format would work)
3. 32-bit only (Well, like Android for pretty much every device, though I think Bluetooth doesn't work in that case)
craigacgomez said:
Just curious about what people are willing to try when it come to custom ROMs... The Nexus 9 is a 64-bit capable device and AOSP allows for 3 variations in the build
1. 64-bit with 32-bit support (like the stock ROM and this ROM here)
2. Pure 64-bit (no apps with libraries not in 64-bit format would work)
3. 32-bit only (Well, like Android for pretty much every device, though I think Bluetooth doesn't work in that case)
Click to expand...
Click to collapse
1
Then in about 6-9 months 2
USBhost said:
[/COLOR]it feels so much faster now
Click to expand...
Click to collapse
It doesn't just feel faster. It is faster. And logically so. With encryption enabled there is extra overhead involved in decryption.