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 ?
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
{
"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"
}
MultiROM for the Samsung Galaxy S4 (Qualcomm variants)
Brought to you by AntaresOne
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy S4. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from external SD card. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the image above. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from Internal memory and MicroSD Card
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file and flash it in recovery.
Modified recovery - download the ZIP file and flash it in recovery or Mobile Odin app to flash the recovery.img contained inside ZIP.
Patched kernel - Download the ZIP file and flash it in recovery or keep stock kernel (only for CM11-based ROMs after 6 August 2014 & CM12-based ROMs)
You current rom will not be erased by the installation.
Download links are in the third post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
3. Other systems (once ported to device)
Firefox OS and Sailfish OS are just another Android ROM under MultiROM's point of view, so add them as if it were Android.
Using MicroSD Card
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - Add ROM to boot manager
- List ROMs - List installed ROMs and manage them
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - Well, settings
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
- Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Source Code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Alucard Kernel w/ kexec-hardboot patch - https://github.com/Alucard24/Alucard-Kernel-jfltexx
Googy-Max3 kernel w/ kexec-hardboot patch - https://github.com/googyanas/Googy-Max3-Kernel
Hulk kernel w/ kexec-hardboot patch - https://github.com/Tkkg1994/Hulk-Kernel
Imperium kernel w/ kexec-hardboot patch - https://github.com/Slim80/Imperium_Kernel_TW_4.4.2
KT kernel w/ kexec-hardboot patch - https://github.com/ktoonsez/KT-SGS4
CM11 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-11.0
CM12 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-12.0
CM12.1 stock kernel w/ kexec-hardboot patch - https://github.com/CyanogenMod/android_kernel_samsung_jf/tree/cm-12.1
MultiROM device tree - https://github.com/AntaresOne/multirom_device_samsung_jflte
Big thanks to Tasssadar for this awesome utility.
Thanks a lot to @daveyannihilation for the S4 template.
XDA:DevDB Information
MultiROM, multiboot for Galaxy S4 (Qualcomm variants) (GRUB-like), Tool/Utility for the Samsung Galaxy S4
Contributors
AntaresOne
Version Information
Status: No Longer Updated
Current Stable Version: 20151029-v32b
Stable Release Date: 2014-09-01
Created 2014-09-01
Last Updated 2017-05-19
Changelog
15/6/2015 - v32a
Update after 6 months!! read post #669
Modified TWRP:
Base updated to 2.8.6.0
Sacrificed crypto and embedded SuperSU installer to get an image that fits 10.5MB recovery partition size
Detailed changes here
MultiROM:
Base update to v32
Added support for 5.1.x Lollipop ROMs
Better support for 5.0.x Lollipop ROMs
Detailed changes here
16/12/2014 - v30c
Modified TWRP:
Base updated to 2.8.2.0
Better support for primary/secondary Lollipop ROMs install/update
MultiROM:
Better support for Lollipop-based ROMs
Fixed the ghost update found in previous build
26/11/2014 - v30
Modified TWRP:
Add partial support for block_image_update in secondary ROMs ZIPs (Lollipop's default flashable zip format)
MultiROM:
Assume fstab version 2 by default
Fix klog saving and text size on emergency reboot screen
Write fstab for fw_mounter as version 2
12/11/2014
Device source:
Disable TWRP event logging
Modified TWRP:
Build an updated image without event logging
4/11/2014
Modified TWRP:
Add back "Share kernel" option (same behavior can be obtained by pressing "Remove boot.img" under MultiROM>List ROMs>*rom name*)
30/10/2014
Modified TWRP:
Update to v2.8.1.0
25/10/2014 - v29
MultiROM:
Minor updates
Full MultiROM Manager support (this fixes the ghost update)
Modified TWRP:
Full MultiROM Manager support
Uninstaller ZIP:
Add support for other jf variants
2/10/2014
Add support for MultiROM Manager app
1/10/2014 - v28c
Device source:
Add MicroSD Card to init devices
Fixed device autoboot in recovery after a reboot/shutdown
30/9/2014 - v28b
MultiROM:
ROM boot from external SD (MicroSD card) is now supported
TWRP Recovery:
General update (branch master)
Removed "Share kernel" option
ROM Installation to external SD (MicroSD card) is now supported
Uninstaller ZIP added back and now working
16/9/2014
TWRP Recovery:
Better MTP compatibility
12/9/2014
TWRP Recovery:
Merge twrp28 branch (now has MTP connection inside to transfer files between PC and device)
6/9/2014
Device source:
Clean and update init devices
Add volume keys init (now you can select ROM/tabs also with volume keys)
3/9/2014
Fixed installation on other jflte devices
1/9/2014 - v28
Device source:
add power button init (needed to reboot device when "an error occurred" and to exit from pong game, available by clicking on Miri)
Downloads
1. Main downloads
MultiROM EXT4 (20151029-v32b): https://www.androidfilehost.com/?fid=24052804347849558
MultiROM F2FS (20151029-v32b): https://www.androidfilehost.com/?fid=24052804347849563
Modified TWRP (20151029-v2.8.7.0): https://www.androidfilehost.com/?fid=24052804347849556
MultiROM Manager App: Google Play Store (by default it will install the EXT4 version!)
2. Kernels for primary ROM (Internal) based on Android 5.1.x Lollipop
Kernel with kexec-hardboot patch for AOSP/CM 5.1 ROMs:
AOSP 5.1 & Optimized CyanogenMod 12.1 from JDCTeam: Alucard is embedded and always up to date
Alucard AOSPv2 5.1 v1.3ba
Stock CM12.1 kernel (included in ROM's zip)
3. Kernels for primary ROM (Internal) based on Android 5.0.x Lollipop
Kernel with kexec-hardboot patch for AOSP/CM 5.0 ROMs:
Optimized CyanogenMod 12 from me and @alucard_24: Alucard is embedded and up to date
Alucard AOSPv2 5.0 v1.1a
Googy-Max3 v1.3.0
Hulk Kernel v1.3.1
KT-SGS4-LP5.0
Stock CM12 kernel (included in ROM's zip)
Kernel with kexec-hardboot patch for Google Edition 5.0 ROMs:
Alucard GE5 v1.1a
Hulk Kernel GE5 v1.3.1
Googy-Max3 GE5 v1.2.3c
Kernel with kexec-hardboot patch for TouchWiz 5.0.1 ROMs:
Hulk Kernel TW5 v1.3.1
Imperium LL v2.0
4. Kernels for primary ROM (Internal) based on Android 4.4.x KitKat
Kernel with kexec-hardboot patch for AOSP/CM 4.4 ROMs:
(builds up to 6 August, including CM11 M9)
Alucard AOSP v2.7.2a
(builds after 6 August, including CM11 M10)
Alucard AOSPv2 v1.4r
Googy-Max3 CM v1.2.5
KT-SGS4-KK
Stock CM11 kernel (included in ROM's ZIP) - All CM11-based ROMs after 6/08 with this android_kernel_samsung_jf source
Kernel with kexec-hardboot patch for Google Edition 4.4.x ROMs:
Alucard GE v2.4d
Googy-Max3 GE v1.2.8
Kernel with kexec-hardboot patch for TouchWiz 4.4.4 ROMs:
Googy-Max3 v1.3.0 TW 4.4.4
Hulk Kernel v1.2 TW 4.4.4
Imperium v1.14 TW 4.4.4
Kernel with kexec-hardboot patch for TouchWiz 4.4.2 ROMs:
Alucard TW v2.3ga
Googy-Max3 v1.3.0 TW 4.4.2
Hulk Kernel v1.2 TW 4.4.2
Imperium v1.14 TW 4.4.2
5. Uninstaller
MultiROM uninstaller ZIP: https://www.androidfilehost.com/?fid=95747613655050515
Just flash this to disable MultiROM and delete all secondary ROMs.
Alucard-PWR-CORE dev thread by @alucard_24: http://forum.xda-developers.com/showthread.php?t=2590246
Googy-Max3 dev thread by @googy_anas: http://forum.xda-developers.com/showthread.php?t=2741181
Hulk Kernel dev thread by @Tkkg1994: http://forum.xda-developers.com/galaxy-s4/i9505-develop/kernel-hulk-kernel-v1-stweaks-based-t3050469
Imperium dev thread by @slim80: http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/kernel-imperium-kernel-v1-0-t2910801
KT-SGS4 dev thread by @ktoonsez: http://forum.xda-developers.com/showthread.php?t=2297379
Useful tips
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
What storage for ROMs is supported?
Internal memory (/data/media-/sdcard) is supported as well as MicroSD card (/external_sd).
How many ROMs can I have and where are stored?
You can have as many ROMs as you can fit in internal memory and MicroSD card. All the ROMs are stored in /data/media/0/multirom/roms (in case of internal memory) and /external_sd/multirom/roms (in case of MicroSD card) drive. These folders are unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
I'm a F2FS user. Can I still enjoy MultiROM?
Yes, you can. Just flash F2FS version of MultiROM zip. NOTE: it is compatible only with full F2FS (so cache, data and system both at once), if you use a custom layout like F2FS for cache/data and EXT4 for system just edit the mrom.fstab file inside the MultiROM zip before flashing the first time or after with reflashing.
Can I have different versions of Android working alongside?
Yes. As long as you select "Don't share kernel" when installing the secondary ROM, systems are separated.
Can I flash TouchWiz-based ROMs as secondary ROMs?
You can, but it's strongly unrecommended and not all the TW ROMs work if installed as secondary, plus are very bigger than other ROMs. I suggest to flash them only as primary ROM.
Can I configure boot menu to be showed only when I want?
You can. Boot in TWRP recovery, go under Advanced>MultiROM>Settings>Configure autoboot and set Keypress-based, then select a ROM to autoboot. In this way, if you power on your device boot menu isn't showed and the ROM you choose to autoboot is booted, but if you power on and rightly when you see "Samsung Galaxy S4" bootlogo you press and keep pressed Vol+ or Vol- button, boot menu is showed.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Hi!
I have been trying this out tonight with four different ROMs and unfortunetley I've only been able to get two of them working:
http://forum.xda-developers.com/galaxy-s4/unified-development/rom-dirty-unicorns-t2863642
http://forum.xda-developers.com/showthread.php?t=2582596
With these the phone just rebooted into recovery:
http://forum.xda-developers.com/showthread.php?t=2544474
http://forum.xda-developers.com/showthread.php?t=2304815
I'm using the Alucard kernel (with the patch) that you posted in the old thread and I chose not to share kernel when installing them.
Do you have any suggestions to why those two ROMs doesn't work for me?
Thank you for your work with this!
nds850 said:
Hi!
I have been trying this out tonight with four different ROMs and unfortunetley I've only been able to get two of them working:
http://forum.xda-developers.com/galaxy-s4/unified-development/rom-dirty-unicorns-t2863642
http://forum.xda-developers.com/showthread.php?t=2582596
With these the phone just rebooted into recovery:
http://forum.xda-developers.com/showthread.php?t=2544474
http://forum.xda-developers.com/showthread.php?t=2304815
I'm using the Alucard kernel (with the patch) that you posted in the old thread and I chose not to share kernel when installing them.
Do you have any suggestions to why those two ROMs doesn't work for me?
Thank you for your work with this!
Click to expand...
Click to collapse
Alright I tried beanstalk like you mentioned and it rebooted into recovery the first time I tried booting in to it. It worked fine the 2nd time however. Currently have dirty unicorns, pa, and now bs. Sometimes when I click reboot on either one of these ROMs, it automatically reboots to recovery instead of multiboot. Don't know of this is a bug or not.
@bdog2015
No, it's not a bug.
RAM memory works in this way: temporary data is loaded inside, but when you reboot or shutdown the system, RAM content is lost (deleted).
Kexec hardboot patch born to let the first 256 MB of RAM (where the kernel is loaded) survive after a reboot. Since that memory portion it's still alive, if you load a ROM and reboot your device may happen that it goes in recovery because bootloader think that it should load recovery (you can see that when you load secondary ROMs you have "Recovery booting......."), so the best method to change ROM or reboot is to shutdown the device and wait 10 (symbolic, to surely get rid of this "problem") seconds for full RAM reset then power on again
Inviato dal mio GT-I9505
AntaresOne said:
@bdog2015
No, it's not a bug.
RAM memory works in this way: temporary data is loaded inside, but when you reboot or shutdown the system, RAM content is lost (deleted).
Kexec hardboot patch born to let the first 128 MB of RAM (where the kernel is loaded) survive after a reboot. Since that memory portion it's still alive, if you load a ROM and reboot your device may happen that it goes in recovery because bootloader think that it should load recovery (you can see that when you load secondary ROMs you have "Recovery booting......."), so the best method to change ROM or reboot is to shutdown the device and wait 10 (symbolic, to surely get rid of this "problem") seconds for full RAM reset then power on again
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Cool. Thanks for the explanation. This multiboot is really awesome
I'm not sure I understand how you mean. I completely shut the phone off and wait for the RAM to reset. I then start the phone and in the MultiROM menu choose the ROM I want to use. The phone restarts and load to recovery. Does the RAM need to be cleared after choosing the ROM? If that is the case how do I do that?
sorry for the dumb question but didn't see answer anywhere.
does multirom work for i337m / jfltecan?
BakaB said:
sorry for the dumb question but didn't see answer anywhere.
does multirom work for i337m / jfltecan?
Click to expand...
Click to collapse
I would assume so. It should work on all jflte's. It works fine on my jflteusc.
@BakaB @bdog2015
Yes, it works on all jflte devices.
I337, I545, L720, M919, R970, I9505, I9507, I9508
Inviato dal mio GT-I9505
I have been trying to flash the MultiROM zip through TWRP Recovery and I keep getting the following errors:
Code:
assert failed: getprop("ro.product.device") == " jflte" | | getprop("ro.build.product") == " jflte "
But what's weird is that both the lines that script is looking for (ro.product.device & ro.build.product) both say jflte in my build.prop so I'm very confused. I'm running Alliance ROM v2.0 I9505XXUGNG2 with stock permissive kernel and TWRP 2.7.1.0
Any help/advice would be appreciated.
@daveyannihilation
What model number has your device?
Thanks for reporting, new build tomorrow with fixed assert for all jflte devices.
For now, open MultiROM zip through WinRAR, go under META-INF/com/google/android and open updater-script, delete:
Code:
assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte");
Then save the file and confirm modified file in WinRAR, now flash that zip
Inviato dal mio GT-I9505
AntaresOne said:
@daveyannihilation
What model number has your device?
Thanks for reporting, new build tomorrow with fixed assert for all jflte devices.
For now, open MultiROM zip through WinRAR, go under META-INF/com/google/android and open updater-script, delete:
Code:
assert(getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte");
Then save the file and confirm modified file in WinRAR, now flash that zip
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Ok MultiROM is installed. After installing MultiROM I flash TWRP_multirom_jflte_20140901.zip through TWRP and then reboot recovery. When TWRP reboots, I don't have any options under Advanced for MultiROM. Recovery is now showing 2.7.1 in the top left whereas before it was showing as 2.7.1.0 so I know that the recovery has changed.
Have I done something wrong? When I reboot the phone I get the MultiROM boot screen coming up asking me to either let it boot into the internal ROM or touch to change, but when I boot into recovery I have no options for MultiROM. I am happy to upload any logs that might help to decipher the issue I am having.
Thanks for your help mate.
@daveyannihilation
Here no problem, do you read "MultiROM TWRP v2.7.1" on the left?
EDIT: New build available
Changes: Fixed installation on other jflte devices
Inviato dal mio GT-I9505
AntaresOne said:
@daveyannihilation
Here no problem, do you read "MultiROM TWRP v2.7.1" on the left?
EDIT: New build available
Changes: Fixed installation on other jflte devices
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Dude... I'm just an idiot. I had twrp holofied which wasn't showing the menus and buttons. This mod is AMAZING!!! Dude I have been looking for this forever, you are a king. I'm definitely gonna be using this from now on, thank you so very very much! [emoji4]
Alliance I9505
@daveyannihilation
Hahaha don't worry
Now just remember this
Inviato dal mio GT-I9505
Is the new build recommended or am I fine if everything is working for me?
bdog2015 said:
Is the new build recommended or am I fine if everything is working for me?
Click to expand...
Click to collapse
The only change in new build is the fixed installation on other jflte devices. If you installed the previous build without errors, no need to update [emoji1]
Inviato dal mio GT-I9505
{
"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"
}
YOU MUST BE ON THE ASUS STOCK JB 4.2.1 BOOTLOADER VERSION ENDING IN 27.1 or 27.5 AND TWRP 2.6.3.2+ OR CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
You must do a full wipe in recovery if coming from another ROM base. Do not do a full wipe from the bootloader. Don't forget to do a Nandroid Backup first and give the ROM 10 mins to stabilise!
Features and Tweaks
This ROM is based from OMNI AOSP sources
Supports EXT4 and F2FS Data partitions
Based off omni-4.4.4-20141030-zombi_tf300t-KANG source by lj50036/hardslog
Full Aroma Installer for main rom including choice of 3 kernels and ROM2SD/DATA2sd/F2FS support
Remixed _thatv11 kernel with OMNI ramdisk - repacked by sbdags/lj50036
Grimlock kernel with OMNI ramdisk and _that init - by hardslog
DPI Size: 213 (TF700 recommended small fonts), 240 (Stock fonts), 224 (Medium fonts) & 200 (Small fonts), 180 (Tiny fonts) & 160 (Specsavers fonts)
Launchers: Omni, Google Experience Launcher, Apex , Nova
Boot Animations: ZOMBi-X, Android-L, Nexus Phase Beam
Gapps (updated by me to Google latest apks and libs)
Misc Apps: ESFile Explorer, Adobe Flash, AdAway, Titanium Backup, Keyboard Manager
Asus Apps: Compiled by kansasboy001; Asus Battery Widget, Asus Calculator, Asus Calendar, Asus Clock, Asus Dayscene Live Wallpaper, Asus Dictionary, Asus Email, Asus Gallery, Asus Keyboard, Asus Photo Story, Asus Sound Recorder, Asus Tasks, My Frame, My Water I & II, Asus Supernote Pro, Weather & Time Widget, Asus Framework, Asus Settings, Asus Audio (V4A), Asus Contacts, Asus File Manager(Root Browser), Asus Camera, Asus Browser
Tweaks: File system and performance optimised, Init.d support!, Zip Align, Force GPU Rendering, Browser2RAM
Continued Best Support of any ROM!
Warning - experimental tweaks
[*]Option to enable / disable data journaling on /data during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Option to enable / disable fsync during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Tip 1: Go to Settings - About Tablet, Click build number 7 times
Now you will see Developer Settings & Performance menus
[*]Tip 2: In Dev Settings, enable advanced reboot & change window animation,
transition animation & animator scales down to 0.2x for extra snappiness
[*]Tip 3: FLOATING WINDOWS: Settings - Interface - more... - Omni Switch
Bug List
[*] Dock works as do most special keys - just no battery available in the system bar
Change Log
20141030 Beta 5 changes
- Merged tinted status bar into ZOMBi
- Tweeked muti-window [issues with tinted window]
- Added SU as a prebuit [updateable from the playstore]
20141006 Beta 4 changes
- FIxed dock battery reporting with app/widget ! Thx @hardslog
20141002 Beta 3 changes
- Added thatv11 to installer
- Added Grimlockv4 to installer
- Fixed BT not turning on without rebooot
- Fixed Bluethooth Share crash on first boot
- Fixed Dock battery reporting (needs an app/widget to work)
- updated dolphin browser to version 11.2.3
- updated google tts to 3.2.12
- updated google music to version 5.6.1523p
- updated google mail to version 4.9
- updated google search to version 3.6.14.1337016
- updated google talkback to version 3.5.2
- updated google play store to version 4.9.13
- updated google core services to version 5.0.89
- updated youtube to version 5.10.1.5
- updated apex launcher to version 2.6.0
- updated adaway to version 2.9.1
20140829 Beta 2 changes
- Fixed issues with Root being lost - reverted to cm11 ramdisks rather than omni as this was causing the issue
- SuperUser and SU Binary updated to version 2.0.2
- Dynamic fsync properly enabled on Grimlock kernel when fsync disabled selected in installer
20140826 Beta 1 changes
- New Base - Rebuilt from latest source which has updated bluetooth config - thanks lj50036
- 90% of dock should be working - battery display is not
- Added CM11 Kernel as option in installer - runs well
- Themed framework with a splash of RED
- Final Tweaks to Aroma Theme
- Updated GravityBox to version 3.3.3
- Removed DropBox as bloatware (30MB!) - still available on the Play Store
- Removed Google Plus as bloatware (33MB!) - still available on the Play Store
- Small changed to aroma themes to fix dark text on dark backgrounds
- Changed the transition config in aroma to see if it fixes screen freezes
- Fixed installer script to allow rom2sd on grimlock kernel install
- Fixed aroma freezes - or reduced them
- Re-themed Zombi-X aroma theme
- Updated performance switch for CPU to allow OC to 1800 on _that's kernel
- Fixed correct rom version in the build.prop
- Updated SU Binary to latest version
- Updated Chrome, Gmail, Google Now, YouTube
- Added Android Terminal to ROM
- New Red Aroma Theme for Zombi-X - requires less memory
- Initial release - omni cromified after source build
- Added SuperUSer and su binary for root capability
- Browser tweaked for speed and touch smoothness
- Added all the CROMBi/CROMi goodness to the base rom
- Aroma tuned for ZOMBi-X
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X/CROMBi-kk ROMS)
@lj50036 - Source Guy (From CROMBi-kk ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
Credits
Google, wow is all I can say!
Omni Team - Thanks!
@_that For all the great advice, watching over us and fixing everything we break!!!!!
All the beta testers for your patience and feedback : BxMxK, canito10, duckredbeard, mikew29, nameneeded, cgf, cyberknight2001, Mikey1969, Ozark_8125, tiernan22, boldnuts, tonyh51, Vathan, erisi, Thibor69
To Do
Fix Buetooth and other little bugs
XDA:DevDB Information
ZOMBI-X, ROM for the Asus Transformer TF300T
Contributors
lj50036, sbdags, hardslog, _that
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: bootloader ending in 27.1 or 27.5
Based On: OMNI AOSP
Version Information
Status: Beta
Current Beta Version: 20141008
Beta Release Date: 2014-10-08
Created 2014-09-18
Last Updated 2014-10-02
DOWNLOADS!
UPGRADE INSTRUCTIONS
Steps
1. If you haven’t yet, unlock your TF300 by now following these instructions.
2. Install the latest version of Team Win Recovery Project (TWRP) 2.6.3.2+ or ClockWorkMod Recovery 6.0.4.6+ Note this ROM will NOT install with older versions of recovery!
OFFICIAL TWRP 2.8.1.0
Flashable zip being made ....
FLASHING THE ROM FROM RECOVERY
Steps
1. Download the ROM below and save to your internal or external SD Card. Do not unzip the file.
ZOMBi-X ROM DOWNLOAD
Note: The first boot after install will take 10 mins whilst everything is built. Some people might think it is looping but it is not
ZOMBi-X Beta 3 Full Mirror 1
ZOMBi-X Beta 3 Full Mirror 2
ZOMBi-X Beta 3 Full Mirror 3
BOTH FILES ARE SIGNED. IF YOU ENABLE SIGNATURE VERIFICATION IN RECOVERY IT WILL VALIDATE THE FILE BEFORE FLASHING.
ASUS APPS DOWNLOAD - Flash from Recovery : Compiled by kansasboy001
Don't forget ROM2SD1.zip / DATA2SD1.zip first if you are not running an internal setup
Asus Battery Widget, Asus Calculator, Asus Calendar, Asus Clock, Asus Dayscene Live Wallpaper, Asus Dictionary, Asus Email, Asus Gallery, Asus Keyboard, Asus Photo Story, Asus Sound Recorder, Asus Tasks, My Frame, My Water I & II, Asus Supernote Pro, Weather & Time Widget, Asus Framework, Asus Settings, Asus Audio (V4A), Asus Contacts, Asus File Manager(Root Browser), Asus Camera, Asus Browser
[THREAD][APPS] [ASUS Apps][ CROMBi-kk & ZOMBi-kk]
ROM2SD/DATA2SD USERS PLEASE READ!
ROM2SD only works if you have ZOMBi-X, CROMBi-kk, CROMi-X or miniC flashed on internal with a THATv10+ kernel. Just choose ROM2SD in the installer of ZOMBi-X to flash it to ROM2SD and the installer will do the rest.
- Install ZOMBi-X and choose ROM2SD or DATA2SD install
The ROM2SD1.zip below is only needed if you need to switch your recovery to between normal and rom2sd mode. For Example you want to backup or restore a rom2sd installation. Flash once to go rom2sd and flash again to go back to normal. A reboot always puts you back to normal. Thanks to _that!
ROM2SD1.zip Download Mirror 1
ROM2SD1.zip Download Mirror 2
MD5 Sum: 7b699136d59ea3d5538570ccaf422acf
The DATA2SD1.zip below is only needed if you need to switch your recovery to between normal and data2sd mode. For Example you want to backup or restore a data2sd installation. Flash once to go data2sd and flash again to go back to normal. A reboot always puts you back to normal.
DATA2SD1.zip Download Mirror 1
DATA2SD1.zip Download Mirror 2
MD5 Sum: 9d5e9e2fd32593f981624499b37924b2
2. Boot to recovery – Either choose Boot to Recovery from the Power Menu if available on your current ROM or from the tablet power off hold the [volume down] button and press the [power] button. Once your see the flashing RCK icon, press [volume up] to select. If another icon is flashing use [volume down] to move between icons.
3. Using your recovery make a Nandroid Backup of your current setup
4. Select install and navigate to where you saved your ROM zip file.
5. Choose the ZOMBi-X zip file and follow the on screen prompts to customize your installation.
6. Reboot and enjoy.
Using GParted to setup a micro SD for ROM2SD or DATA2SD support
First and foremost - DO NOT USE MINI TOOL!
Formatting a micro sd card for ROM2SD
Note for DATA2SD just do one partition in stead of 2
We will be using a GParted Live boot USB and a FAST good quality micro sd like a Sandisk or Samsung Class 10 - SDHC/SDXC UHS-1 card with read speed of at least 20MB/S. If you have a cheap chinese eBay card don't bother - they are not good enough.
You will also need a USB Stick with at least 1GB size. Note this process formats the USB disk so don't keep any important files on it. It will also wipe your micro sd so make sure you are prepared.
1. Go to the link below and download the GParted Live CD/USB/HD/PXE Bootable Image and save it somewhere you remember
http://gparted.sourceforge.net/download.php
2. Download Linux Live USB Creator and install it
http://www.linuxliveusb.com/
3. Fire up LiLi USB Creator:
a. Choose your USB key - I,e, the drive letter for your USB (not sd card)
b. Choose your GParted iso image for the source
c. Choose the check box to Format Key in FAT32 and hide files
d. Click the lightning bolt to create
4. Now you have a bootable disk you need to boot from it. You may need to alter you BIOS Settings on your PC to boot from a USB Stick but mine did it without messing.
5. Insert your micro SD card into an SD Card adapter and insert into PC
6. Boot into GParted
7. Choose Gparted Live <Enter>
8. Don’t touch keymap <Enter>
9. Languge <Enter>
10. Start Gparted Automatically
11. Change device to your micro sd )it will default to you hard disk - hda– mine is /dev/sdc
12. Delete all existing partitions
For a 64GB card: (resize as needed but /system doesn't need to be bigger than 1GB)
13. Create new, always select primary: do this 3 times.
14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
15. EXT4 : Size 42GB – this will be /dev/sdc2 in gparted and will be your /data partition in Android
16. EXT4 : Size 1GB – this will be /dev/sdc3 in gparted and will be your /system partition in Android (not needed for data2sd)
Apply, wait until it finishes and then reboot. Remember to remove the usb stick
*Images stolen from elsewhere as I couldn’t get it to save mine
Now you are ready to install ROM2SD. Note if you want to use DATA2SD then only do 2 partitions 1x FAT32 and 1x larger EXT4
Then reinstall ZOMBi-X but this time choose the ROM2SD / DATA2SD option
HUGE THX
@spudsmac
@miduku
@robbie888
@lightiv
@Bigred007
@Waldo_
@emfanitek
@rlanza1054
@Unidave199
@Lock-N-Load
@Fear Knot
@lvrijn
@mitsublw
@scouzers
@zdebel
@jhr5474
@Eddie Hicks
@smchadwell
@dladz
@eRPeeX
@LocusofZen
Thx everyone that has donated, if you do not see your user name here and have donated, shoot me an PM and I will add you....
Thx Josh
Reserved!
I have been looking forward to this. nice and fresh.
many thanks to you all =)
Does the official TWRP 2.8.0.1 support f2fs on /data?
k-kuchen said:
Does the official TWRP 2.8.0.1 support f2fs on /data?
Click to expand...
Click to collapse
Yes It is working very nicely.. :laugh:
It even has MTP now.... Thx TWRP...
Thx Josh
sneaky buggers
Moar good things are coming
twrp 2.8
Can I just use terminal to install twrp like "dd if=/sdcard/twrp28.blob of=/dev/block/mmcblk0p4" before I install new zombi-x? I renamed file to twrp28.blob already.
xxxericxxx said:
Can I just use terminal to install twrp like "dd if=/sdcard/twrp28.blob of=/dev/block/mmcblk0p4" before I install new zombi-x? I renamed file to twrp28.blob already.
Click to expand...
Click to collapse
I had no idea this would become a TWRP thread... :cyclops:
Take a look here mate TWRP TF300T
Thx Josh
differences between this and the crombi-kk?
how do you get the ES file explorer as pop up?
albyzaf said:
differences between this and the crombi-kk?
how do you get the ES file explorer as pop up?
Click to expand...
Click to collapse
Crombi-KK - Based on CyanogenMod sources
Zombi-X - Based on OmniRom sources and includes some OmniRom specific experimental features that aren't in official nightlies yet (like the floating windows)
If you want floating windows, I suggest activating the "OmniSwitch" app. With this app, if you long press on either the recent apps, or your favourite apps, it will give you the option to "float view"
hardslog said:
Crombi-KK - Based on CyanogenMod sources
Zombi-X - Based on OmniRom sources and includes some OmniRom specific experimental features that aren't in official nightlies yet (like the floating windows)
If you want floating windows, I suggest activating the "OmniSwitch" app. With this app, if you long press on either the recent apps, or your favourite apps, it will give you the option to "float view"
Click to expand...
Click to collapse
It's beem much quieter here than i thought it would be..
I'm just wondering if it would be possible to get some actions on the nav bar for floating window mode. going in through omni switch each time a a bit of a pain. Maybe something like that have done on the katkiss rom?
I'd report more useful stuff like bugs if i had found any =)
I'm just curious if the f2fs and f2fsSD are working in this?
gargash said:
I'm just curious if the f2fs and f2fsSD are working in this?
Click to expand...
Click to collapse
Yep they are. If you mean internal, data2sd and rom2sd.
Nice ROM
Thanks @sbdags, @lj50036, and @hardslog ! You guys still actively working on this? I was wondering if the dock battery status bar indicator would be included in the future.
shawnbrennan55 said:
Thanks @sbdags, @lj50036, and @hardslog ! You guys still actively working on this? I was wondering if the dock battery status bar indicator would be included in the future.
Click to expand...
Click to collapse
Of course we are still working on it. We have just begun. Currently working out other kinks before we try to tackle the dock battery status bar indicator again. Already tried to implement it once but failed miserably.
I can't wait to try this one guys, do you have any idea when it will be out if beta?
robgee789 said:
I can't wait to try this one guys, do you have any idea when it will be out if beta?
Click to expand...
Click to collapse
Don't be afraid of beta. This ROM is awesome combined with an F2FS file system and kernel.
robgee789 said:
I can't wait to try this one guys, do you have any idea when it will be out if beta?
Click to expand...
Click to collapse
Nope, but it is mostly a beta because of unimplemented functionality that we want in the future and some very nit-picky things (we all have some form of OCD :laugh
Could always take a nandroid and give it a try :cyclops:
{
"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"
}
YOU MUST BE ON THE ASUS STOCK JB 4.2.1 BOOTLOADER VERSION ENDING IN 27.1 or 27.5 AND TWRP 2.7+ OR CWM 6.5.0.0+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
You must do a full wipe in recovery if coming from another ROM. Do not do a full wipe from the bootloader. Don't forget to do a Nandroid Backup first and give the ROM 15 mins to stabilise! The first boot will take 15 minutes!
SCREENSHOTS
Features and Tweaks
This ROM is based from OMNI AOSP sources
Supports EXT4 and F2FS Data partitions
Based off omni-5.1.1-20150508-zombi_tf300t-KANG source by lj50036/hardslog
Full Aroma Installer for main rom including choice of 4 kernels and ROM2SD/DATA2SD/F2FS support
Remixed _thatv11 kernel with OMNI ramdisk - repacked by sbdags
Grimlock kernel with OMNI ramdisk and _that init - by hardslog
DPI Size: 160 (TF300 recommended small fonts), 240 (Stock fonts), 224 (Medium fonts) & 200 (Small fonts), 180 (Tiny fonts) & 160 (Specsavers fonts)
Launchers: Omni, Google Experience Launcher, Apex , Nova
Boot Animations: ZOMBi-POP, Android-L, Nexus Phase Beam
Gapps (updated by me to Google latest apks and libs)
Misc Apps: ESFile Explorer, Adobe Flash, AdAway, Titanium Backup, Keyboard Manager
Tweaks: File system and performance optimised, Init.d support, Zip Align, Force GPU Rendering, Browser2RAM
Continued Best Support of any ROM!
Warning - experimental tweaks
[*]Option to enable / disable data journaling on /data during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Option to enable / disable fsync during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Tip 1: Go to Settings - About Tablet, Click build number 7 times
Now you will see Developer Settings & Performance menus
Bug List
[*]No Floating windows yet
Change Log
20150728 ZOMBi-POP RC1 changes
- RELEASE CANDIDATE 1!
- Fixed the problem with ROM2SD and DATA2SD not working correctly on beta 4
- Added SuperUser and Secure Kernel as options to the installer (Turn these off for work wifi or watching sky go, etc)
- Added dock battery icon as an option to the installer under tweaks
- Fixed partitions not getting unmounted correctly for tuning during installation
- Fixed WiFi across the unified bases for TF700/TF300/TF201
- OmniSwitch now working - thanks hardslog
- Tidied up some installer messages
- Google play services updated to unified version for all devices
- Updated Google Maps to version 9.12.0
- Updated Google TTS to version 3.5.6
- Updated Google Calendar to version 5.2.2-98195638
- Updated YouTube to version 10.28.59
- Updated Apex Launcher to version 3.1.0
20150723 ZOMBi-POP Beta 4 changes
- Unified Aroma installer for TF700/TF300/TF201
- Rebased from omni-5.1.1-20150718-zombi_tf300t-KANG maintained by lj50036, hardslog, sbdags
- Merged source from omni-5.1.1-20150718-zombi_tf700t/tf201t-KANG maintained by lj50036, hardslog
- Updated all kernels and modules to the unified versions - thanks lj50036
- Added inverted kernel for TF201 users
- Aroma re-written to allow multi device selection and detection
- Additional tweaks added from TF701 Zombi-pop
- Amended SuperSU installer script to give correct permissions and install locations
- Reverted to latest Banks Gapps - means another wipe - sorry!
- Updated Google Calendar, Google Mail, Google Hangouts, YouTube, Google Search & Google Maps to latest versions
- Updated ESFile Explorer and Nova Launcher to latest versions
- Added flashable zip to enable dock battery - NOTE - this means you can't change the battery icon
20150119 ZOMBi-POP Beta 3 changes
- Rebased from omni-5.1.1-20150508-zombi_tf300t-KANG maintained by lj50036, hardslog
- Repacked Grimlock kernel for 5.1.1 (Grimlock lite is still using 5.0)
- Retweaked some File System and Virtual Memory parameters - focus on smoothness and battery
- Added Aroma code to remember previous selections as well as offer various installs
- sbdags best auto install, omni default auto install, previous options and previous auto install
- Viper4Android sound enhancer updated to lollipop version + updated the audio_effect.conf file
- Updated Google Play Store to version 5.5.8
- Updated Google Play Services to version 7.3.29
- Updated Google Search to version 4.5.13.19
- Updated Google Maps to version 9.8.1
- Updated Google Hangouts to version 3.2.91698097
- Updated Google Play Music to version 5.9.1854R
- Updated Google Calendar to version 5.2-91668080
- Updated ESFileExplorer to version 3.2.5.1
- Fixed swipe gestures on google keyboard
- Fix for Battery Drain on Google Play Services
- Removed Titanium Backup from the zip file
20150422 ZOMBi-POP 5.1 Beta 2 changes
- Rebased from omni-5.1.1-20150422-zombi_tf300t-KANG maintained by lj50036, hardslog
- New base is from OMNI 5.1.1 merged by lj50036
- Browser History is back again! Thanks lj50036 or Hardslog
- You can now choose to install, no GAPPS or minimal GAPPS (just playstore and syncs)
- Updated Google Maps to version 9.7.1
- Updated Google Search to version 4.4.11.16
- Updated Google Mail to verison 5.1.90765967
- Updated Google Calendar to version 5.2-90091543
- Updated Google Hangouts to version 3.1.89134953
- Updated Google Text-to-Speech to version 3.4.6.1819666
- Updated YouTube to version 10.14.56
- Updated ESFileExplorer to version 3.2.5
- Updated Android Terminal to version 1.0.70
- Updated Banks Gapps:
- Google Play Services 7.3.28 (1863718-438)
- Google Play Store 5.4.12
- fixed OC on Some TF201's running Grimlock-lite
20150330 ZOMBi-POP 5.1 Beta 1 changes
- Rebased from omni-5.1-20150330-zombi_tf300t-KANG maintained by lj50036 & harslog
- Adaptive brigtness fixed and values changed
- Browser speed tweaks incorporated into source
- OmniSwitch updates
- Settings changes to alarms and notification interruptions
- Updated Google Music to version 5.8.1836R
- Removed Titanium Launcher - as it needs to be installed form the store now
- Testing Aroma 3.00 scripts from Amarullz
- Repacked omni / _that kernel with preinit init binary
- Updated YouTube, Hangouts, Google Search, Calendar, Maps to latest 5.1 versions
- Updated Google Play Store and Services to 5.1 versions
- Updated Apex Launcher to version 3.0.3
- Recompiled Browser.apk with speed tweaks
- Moved tibu to system to try and fix install issues
- Shrunk all gapps by removing duplicate lib files from binaries
- Cleaned up gapps inconsistencies (sbdags)
20150218 ZOMBi-POP Beta 4 changes
- Rebased from omni-5.0.2-2015-02-19-zombi_tf300t-KANG source maintained by lj50036
- Show Optimizing app dialog on first boot
- Prevent copyNativeLib of package scanning to reduce booting time
- Keyguard: don't refresh ui when screen off which causes high power when screen off
- Prevent App Not Responding when broadcast receiver is killed
- lowmemorykiller: Fix high min-free values
- Removed my minfree init.d script to test new default values
- Changed the interactive governor tweaks to help battery life and heat
- min_sample_time from 40000 to 10000
- go_maxspeed_load from 90 to 98
- max_normal_freq from 1500000 to 1300000
- midrange_freq from 760000 to 1150000
- Updated SuperSU to version 2.46
- Updated Apex Launcher to 3.0.2
- Updated Google Maps to version 9.4.0
- Updated YouTube to version 10.05.6
20150212 ZOMBi-POP Beta 3 changes
- Rebased from omni-5.0.2-2015-02-11-zombi_tf300t-KANG source maintained by lj50036
- Updated Grimlock Kernels for exfat and ntfs support (hopefully!)
- New Kernel - Grimlock LITE - OC reduced to 1700mhz and voltage reduced for better battery/heat
- Rebuilt _that/omni kernel with oom patches and repacked ramdisk
- Reverted some vm and kernel tweaks which seems to have got performance back on track
- Reverted read_ahead_kb to 4096 as no benefit to 2048
- Fixed Tibu not installing correctly and updated to version 7.0.0.2
- Removed Chrome and Dolphin / Flash
- Rebuilt all GAPPS from latest PA GAPPS modular package Feb 2015
- Resized Nexus-Lollipop bootanimation
- Added the Unknown Pleasures bootanimation
- Aroma theme updated - thanks Shonkin for the bg picture
- Fixed Overclocking not working on data2sd with _that's kernel. You now get 4x1800 cores on data2sd
- CPU will use all 4 cores at 90% max load instead of 85% on basic cpu tweaks
- Fixed missing sdcardi on grimlock kernel
- Fixed init.d on Grimlock 5 kernel by repacking init.zombi.rc
- Fixed zipalign script so it runs properly once after a dirty or clean install
- Set the lowmemorykiller to less aggressive 2048,4096,8192,16384,24576,32768 via init.d script
- Rewrote Aroma installer which gets us a step closer to it remembering previous installs (but not yet!)
- Split out the extra tweaks into two parts for further debugging - Basic and Extended
- Spilt out Disable Software Rendering and Force GPU rendering for further testing
- Reordered init.d scripts to make more sense
- Updated Titanium Backup to version 7.0.0 and cleaned up installation script
- Force GPU Rendering is not getting applied correctly - do it manually for now
20150127 ZOMBi-POP Beta 2 changes
- Rebased from omni-5.0.2-20150127-zombi_tf300t-KANG source maintained by lj50036/hardslog
- Fixed Auto-rotation - thanks hardslog/lj50036!
- NEW Material AOSP Broswer - very nice!
- Omni Switch but no windows mode yet
- Fixed missing sdcardi folder for data2sd and rom2sd users
- Fixed the Apex and Nova Launchers getting missed up on install
- CLEANTweaks init.d re-balanced to be less aggressive - hopefully stops so many reboots
- Recompiled latest framework-res.apk with zombi-pop default_wallpaper.jpg
- Updated Google Chrome to version 40.0.2214.89
- Updated Google Maps to version 9.3.0
- Updated YouTube to version 10.02.3
- Updated Android Terminal Emulator to version 1.0.64
20150121 ZOMBi-POP Beta 1 changes
- Fixed Auto-rotation
- Added Linaro build of Grimlock Kernel (needs more testing)
- AOSP Browser: Materialize (green)
- First Release for TF300/TF201
20150119 ZOMBi-POP Pre-Release 3 changes
- New name - new logo! ZOMBi-POP
- Rethemed Aroma to new ZOMBi-POP theme
- Added 2 optional beta tweaks for testing (screen and kernel)
- Fixed _thatv11 kernel option
- Added Grimlock v5.0 (not tested)
20150118 Lollipop Pre-Release 2 changes
- Updated to latest OMNI Lollipop source omni-5.0.2-20150117-zombi_tf700t-KANG maintained by lj50036
- Fixed issue with AOSP Browser getting installed when not selected
- Fixed issue with Live Wallpapers getting installed when not selected
- Fixed issue with Launcher3 getting installed when not selected
- Fixed issue with Terminal not getting installed when selected
- Fixed issue with DSPManager still getting installed when Viper4fx is installed
- Removed stock calendar as google app one is far superior
- Fixed init.d scripts not running due to wrong permissions and wrong ramdisk init.rc call
20150117 Lollipop Pre-Release 1 changes
- Updated system and data apps to use new lollipop structures
- Updated all apps to latest versions
- Removed xposed as not compaitble with lollipop
- Tweaked the force gpu options
20150111 Lollipop Alpha 1 changes
- Updated to latest OMNI Lollipop source maintained by lj50036
- New PA GApps Lollipop version 2015
- Initial Beta test build to see what works and what doesn't
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X/CROMBi-kk/ZOMBi-X ROMS)
@lj50036 - Source Guy (From CROMBi-kk/ZOMBI-X ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
@ikkeT- The Fin
Credits
Google
Omni Team - Thanks!
@_that For all the great advice, watching over us and fixing everything we break!!!!!
All the beta testers for your patience and feedback : fatboyinlycra, berndblb, drewski_1, duckredbeard, keshavmot2, corb06, jmaybush, JoJoDaClown, kansasboy001, TrofeoSC
To Do
Fix loads of stuff!
XDA:DevDB Information
ZOMBi-POP, ROM for the Asus Transformer TF300T
Contributors
hardslog, lj50036, sbdags, _that
Source Code: https://github.com/zombi-x
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: JB Ending with 27.1 or 27.5 bootloader
Based On: OMNI AOSP
Version Information
Status: Stable
Current Stable Version: 20150728 RC1
Stable Release Date: 2015-07-28
Current Beta Version: 20150723 Beta 4
Beta Release Date: 2015-07-23
Created 2015-01-24
Last Updated 2015-07-27
Reserved
UPGRADE INSTRUCTIONS
Steps
1. If you haven’t yet, unlock your TF300 by following these instructions.
2. Install the latest version of Team Win Recovery Project (TWRP) 2.7+ Note this ROM will NOT install with older versions of recovery!
TWRP OFFICIAL DOWNLOADS
Download the recovery file from above, put it into the same folder where you have adb and fastboot files. Please rename it to twrp.blob or cwm.img and follow the instructions below:
CWM:
Connect your transformer to your PC, reboot to the bootloader to enable fastboot by either holding down [power] and [volume down] or opening a command prompt in your adb.exe folder in windows:
Code:
adb reboot bootloader
To flash the recovery:
Code:
fastboot -i 0x0B05 flash recovery cwm.img
or
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
A blue bar will go accross the screen on the tab and the command prompt will indicate it was successful in about 10 seconds
Then reboot the tablet either back to the bootloader or to android to complete
Code:
fastboot -i 0x0B05 reboot-bootloader
fastboot -i 0x0B05 reboot
You can now access the recovery by pushing [volume up] on the RCK icon in the bootloader screen
Click to expand...
Click to collapse
FLASHING THE ROM FROM RECOVERY
Steps
1. Download the ROM below and save to your internal or external SD Card. Do not unzip the file.
ZOMBi-POP ROM DOWNLOAD
Note: The first boot after install will take 15 mins whilst everything is built. Some people might think it is looping but it is not. The ROM also takes about 15 mins to stabilise after the first boot
ZOMBi-POP RC1 LP 5.1.1 Full Mirror 1
ZOMBi-POP RC1 LP 5.1.1 Full Mirror 2
MD5 sum: e3980e1bffa539e676ac1269268abcd1
Flash this patch please as there is a file missing that gives better performance
RC1 Performance Patch
Remember if you are on rom2sd you beed to flash rom2sd1.zip first and if on data2sd use data2sd1.zip first.
FILES ARE SIGNED. IF YOU ENABLE SIGNATURE VERIFICATION IN RECOVERY IT WILL VALIDATE THE FILE BEFORE FLASHING.
ROM2SD/DATA2SD USERS PLEASE READ!
ROM2SD only works if you have ZOMBI-POP, ZOMBi-X, CROMBi-kk, CROMi-X or miniC flashed on internal with a THATv10+ kernel. Just choose ROM2SD in the installer of ZOMBi-POP to flash it to ROM2SD and the installer will do the rest.
- Install ZOMBi-POP and choose ROM2SD or DATA2SD install
The ROM2SD1.zip below is only needed if you need to switch your recovery to between normal and rom2sd mode. For Example you want to backup or restore a rom2sd installation. Flash once to go rom2sd and flash again to go back to normal. A reboot always puts you back to normal. Thanks to _that!
ROM2SD1.zip Download Mirror 1
ROM2SD1.zip Download Mirror 2
MD5 Sum: 7b699136d59ea3d5538570ccaf422acf
The DATA2SD1.zip below is only needed if you need to switch your recovery to between normal and data2sd mode. For Example you want to backup or restore a data2sd installation. Flash once to go data2sd and flash again to go back to normal. A reboot always puts you back to normal.
DATA2SD1.zip Download Mirror 1
DATA2SD1.zip Download Mirror 2
MD5 Sum: 9d5e9e2fd32593f981624499b37924b2
2. Boot to recovery – Either choose Boot to Recovery from the Power Menu if available on your current ROM or from the tablet power off hold the [volume down] button and press the [power] button. Once your see the flashing RCK icon, press [volume up] to select. If another icon is flashing use [volume down] to move between icons.
3. Using your recovery make a Nandroid Backup of your current setup
4. Select install and navigate to where you saved your ROM zip file.
5. Choose the ZOMBi-POP zip file and follow the on screen prompts to customize your installation.
6. Reboot and enjoy.
Using GParted to setup a micro SD for ROM2SD or DATA2SD!
First and foremost - DO NOT USE MINI TOOL!
Formatting a micro sd card for ROM2SD
Note for DATA2SD just do one partition in stead of 2
We will be using a GParted Live boot USB and a FAST good quality micro sd like a Sandisk or Samsung Class 10 - SDHC/SDXC UHS-1 card with read speed of at least 20MB/S. If you have a cheap chinese eBay card don't bother - they are not good enough.
You will also need a USB Stick with at least 1GB size. Note this process formats the USB disk so don't keep any important files on it. It will also wipe your micro sd so make sure you are prepared.
1. Go to the link below and download the GParted Live CD/USB/HD/PXE Bootable Image and save it somewhere you remember
http://gparted.sourceforge.net/download.php
2. Download Linux Live USB Creator and install it
http://www.linuxliveusb.com/
3. Fire up LiLi USB Creator:
a. Choose your USB key - I,e, the drive letter for your USB (not sd card)
b. Choose your GParted iso image for the source
c. Choose the check box to Format Key in FAT32 and hide files
d. Click the lightning bolt to create
4. Now you have a bootable disk you need to boot from it. You may need to alter you BIOS Settings on your PC to boot from a USB Stick but mine did it without messing.
5. Insert your micro SD card into an SD Card adapter and insert into PC
6. Boot into GParted
7. Choose Gparted Live <Enter>
8. Don’t touch keymap <Enter>
9. Languge <Enter>
10. Start Gparted Automatically
11. Change device to your micro sd )it will default to you hard disk - hda– mine is /dev/sdc
12. Delete all existing partitions
For a 64GB card: (resize as needed but /system doesn't need to be bigger than 1GB)
13. Create new, always select primary: do this 3 times.
14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
15. EXT4 : Size 42GB – this will be /dev/sdc2 in gparted and will be your /data partition in Android
16. EXT4 : Size 1GB – this will be /dev/sdc3 in gparted and will be your /system partition in Android (not needed for data2sd)
Apply, wait until it finishes and then reboot. Remember to remove the usb stick
*Images stolen from elsewhere as I couldn’t get it to save mine
Now you are ready to install ROM2SD. Note if you want to use DATA2SD then only do 2 partitions 1x FAT32 and 1x larger EXT4
Then reinstall ZOMBi-POP but this time choose the ROM2SD / DATA2SD option
Reserved
All,
The ROM is still in BETA and by flashing it you are helping the BETA Testing process
It may still have some bugs, spontaneously reboot, drain the battery faster or heat up a bit. The aim is to make it better and fix them.
If you find a bug and want to report it here please post a logcat (after it occurred) with a description of what you were doing at the time and the rough timing in the logcat to look at (these things get huge!).
You can also post a dmesg which is the kernel boot logs and can indicate issues with data corruption or hardware.
If you get a reboot then please post a last_kmsg from the /proc folder.
How to get a logcat
How to get useful logs
Thank you!!
Join us on IRC for a chat or if you have questions:
Freenode
zombi-x
There is no Q&A section for this rom as it is still in dev so you are ok to post your questions here!
One for me
MIRROR 1 & 2 are up for your flashing needs ..... :good:
Thx Josh & Team ZOMBI
Cannae reserve a post but this one will do
@lj50036
I know all the kinks haven't been worked out yet, but is dock battery icon in this version?
toolhas4degrees said:
@lj50036
I know all the kinks haven't been worked out yet, but is dock battery icon in this version?
Click to expand...
Click to collapse
No not yet, most of the dock keys are working, but no battery support as of yet....
Thx Josh
Could it be possible to enjoy this project with the transformer prime???
Thx un any case, great effort, great success team!
jacmat said:
Could it be possible to enjoy this project with the transformer prime???
Thx un any case, great effort, great success team!
Click to expand...
Click to collapse
I am testing it now and have had good results....
Just need a bit more testing and then I will make a thread for the 201 ...... :good:
Thx Josh
lj50036 said:
I am testing it now and have had good results....
Just need a bit more testing and then I will make a thread for the 201 ...... :good:
Click to expand...
Click to collapse
so good to hear that, thanks so much for your work Josh!
Good to know! It would be great if it could work on the ME301T also! Is the hardware that different?
Hi, this rom work on TF300TG ???
Thanks
lj50036 said:
I am testing it now and have had good results....
Just need a bit more testing and then I will make a thread for the 201 ...... :good:
Thx Josh
Click to expand...
Click to collapse
Thanks! Flashed with grimlock 5.0 and it runs well, but I had issues with chrome browser lockups...
lj50036 said:
I am testing it now and have had good results....
Just need a bit more testing and then I will make a thread for the 201 ...... :good:
Thx Josh
Click to expand...
Click to collapse
Thank you very much, Josh, you and your team bring to prime's owners a reason to smile
jlamaeli said:
so good to hear that, thanks so much for your work Josh!
Click to expand...
Click to collapse
You will see a thread when its ready... :good:
EV0LU710N said:
Good to know! It would be great if it could work on the ME301T also! Is the hardware that different?
Click to expand...
Click to collapse
There maybe a compatible pack but we will have to wait and see... :good:
medievalspawn said:
Hi, this rom work on TF300TG ???
Thanks
Click to expand...
Click to collapse
It should but you will lose 3G....
luismiguel1977 said:
Thanks! Flashed with grimlock 5.0 and it runs well, but I had issues with chrome browser lockups...
Click to expand...
Click to collapse
Logcat after the browser crashes .....
jacmat said:
Thank you very much, Josh, you and your team bring to prime's owners a reason to smile
Click to expand...
Click to collapse
Will have to wait and see.... :good:
Thx Josh
lj50036 said:
There maybe a compatible pack but we will have to wait and see... :good:
Click to expand...
Click to collapse
That would be fantastic, surely would make a bunch of people very happy, myself included!
By the way, if you need a beta tester or some help with the development, I would be very happy to help out! I have a tablet ready to test drive!
lj50036 said:
There maybe a compatible pack but we will have to wait and see... :good:
Click to expand...
Click to collapse
Thank you man, would be great! :good:
excellent, downloading now, can you recomend a good gapps package for the rom
thanks
matt_simpson said:
excellent, downloading now, can you recomend a good gapps package for the rom
thanks
Click to expand...
Click to collapse
It's built in as choices.