Related
[INTRODUCTION]
This ROM is based of the joined effort of a couple of devs (Ejtable, Scanno and Brucelee666) who are working on getting JellyBean working for our device. As soon as JellyBean is getting stable, my goal is also to put everything on github, just like i did with VegaCream. This way other devs can also work on this.
Please remember that I, ejtagle and brucelee666 are *NOT* professionals and do this in our spare time. We all have full time jobs and a family. So be happy that there is an Android ROM based on Android 4.1.1 / JellyBean for a device that was sold with Android 2.2 and never had an update.
We do our best to make this ROM as good as possible. With VegaCream we gave you a ROM that gave a new life to your tablet and unleashed its full potential. But we are not wizzards and there might be problems that we cannot solve or do not have time for.
[SPECIFICATIONS]
This ROM is based on AOSP 4.1.1 and the device config made by Ejtagle, brucelee666 and myself.
- INT2EXT+ (Needs a correctly partitioned SDCard)
- zRAM
- DPI is set at 120dpi
- Default JellyBean Launcher installed
- Apex Launcher installed
- Filemanager installed
- Terminal installed
- Google Apps is installed. This means that the Google base is installed and all the apps that are available in the Play Store are not installed (i.e. GMail, Maps)
- All languages that are available in AOSP are included
- Partition layout is the same as VegaCream / VegaICS beta1 / Modded stock
- /system/app, /system/lib, /system/fonts, /system/framework and /system/usr are Squashfs filesystems.
[INSTALLATION]
There are 2 methods of installation. There is a CWM recovery flashable ZIP and a NVFlash file.
I realy recommend flashing VegaBean the first time with the NVFlash version.
Before installing any version, you have to make sure that you have a SDCard that has the correct partition layout:
- First partition is a primary partition formatted as FAT32
- Second partition is a primary partition formatted as EXT4
EXT4 is a linux filesystem so you will need a program that can handle Linux filesystems when you are using Windows.
Before installing the ZIP file make sure that:
- You have the correct partition layout (if you have VegaCream installed, you have the correct layout, if not then use the NVFlash installer. This will repartition your internal memory))
- Copy the ZIP file to your SD-Card
- Boot into Recovery
- Do a FULL WIPE / FACTORY RESET
- Install the ZIP file from your SDCard
- After installing reboot the tablet.
[WORKING]
- WiFi
- Bluetooth (Tested with a A2DP headset)
- Camera
- HDMI including audio
- 3G (only fro the Huawei internal modem, usb modems may work)
- GPS not tested by me, but some say it kind of works.
[CREDITS]
- Ejtagle
- Brucelee666
- Scanno
- LeoP for his zRAM implementation
- Legionaire (for the VegaBean bootanimation)
[DOWNLOADS]
Please do *NOT* use Link2SD anymore. You do not need it. With the INT2EXT script, your apps will install on SDCard by default. Just make sure you have 2 primary partition. First partition *MUST* be a FAT32 partition. The second partition *SHOULD* be EXT4. When upgrading from a previous version, make sure your EXT partition is empty / reformatted. Also when using the NVflash version !!!
Downloads:
https://www.androidfilehost.com/?w=files&flid=118264
[Changelist]
[Beta 6]
- RIL updated to the latest version (3 october i think)
- updated to AOSP 4.1.2
- Added check to see if there is a second partition on the SDCard. If not INT2EXT is not excecuted (PLEASE TEST !!!)
- Updated GApps
[Beta 5]
Changes compared to Beta 3-1:
- New kernel with the following changes:
- Suspend problem solved. Tablet does not enter LP0 anymore
- Compiled with zRAM support
- zRAM modules added
- zRAM implementation from LeoP included
- RIL from ejtagle updated
[Beta 3-1]
- Included int2ext+
- Included bootanimation for legionnaire
[Beta 3]
- Latest RIL from EJTagle
- CM10 keyboard
- Stock browser with the option to set User Agent
- You can now just wipe cache and dalvik-cache when updating from a previous VegaBean version. Please remember that from other version you will have to do a full wipe / factory reset !!!
[Beta 2.2]
What has changed compared to Beta 2
- AOSP updated to JRO03L
- Latest update to the huaweigeneric RIL (from aug 27) by EJTagle
The stripped version has the following apps removed from /system/app compared to the original version:
- ApexLauncher.apk
- PlayMusic.apk
- Talk.apk
- YouTube.apk
The stripped version should give you around 10 MiB extra on /system. So if you have bad NAND problems and have problems booting (not able to) you can try this.
[Beta 2]
- HDMI audio working
- VegaBean bootanimation added by indigolemon
[Beta 1]
- Rotation really fixed and HW acceleration working
- Disable / Enable GPS would crash, fixed (thanks Eduardo)
Alpha 3:
- Rotation Fixed. Portrait mode is working correctly
- 3G files included... Sadly no 3G because of too old version of Huawei RIL. Need at least version 6 and we have version 4. So if anybody can get his / her hands on a newer version, please let us know.
Hey , very nice to see JellyBean here
I have ViewSonic 10s
I am using at this moment VegaICS , so i am thinking to upgrate it to JB. So my questions :
- kernel with hostdriver ?
- is system rewritable?? its Squashfs so i think its not (like VegaICS, no deletable apps...)
- can I update BusyBOX and Superuser ??? (always after i did it , WIFI was brocken and I lost root (VegaICS))
- is it possible to change DPI to normal 160 ??
............................
One more question about CWM
always after installing any Roms via CWM , it booted , but after first reboot/turnoff my device died... only what help is reflashing via NVflash....
So what should i flash first to use a stable-CWM (without killing device)
any suggestions
If you are still using VegaICS, I suggest you switch to VegaCream RC2. It has an NVFlash installer, so you don't have to use CWM at all. It is by far the most stable and fast ROM ever built for our devices, and is 100% feature complete.
This ROM is a beta, and if you have not experienced VegaCream RC2 yet, you should try that first and wait on this for a later release.
rpmccormick said:
If you are still using VegaICS, I suggest you switch to VegaCream RC2. It has an NVFlash installer, so you don't have to use CWM at all. It is by far the most stable and fast ROM ever built for our devices, and is 100% feature complete.
This ROM is a beta, and if you have not experienced VegaCream RC2 yet, you should try that first and wait on this for a later release.
Click to expand...
Click to collapse
ye but its 120 dpi... its horrible and all is toooo small .. can see pixels
What a great ROM, but I've got a problem where my Viewpad don't boot. Ok, it boots the first time after installing it, but not on 2nd boot. I've tried to install it over both VegaICS and VegaCream RC2. Does anybody have a solution? I really want this ROM. I had the same problem on VegaCream in the past, but it I think it works now, but not in VegaBean. I hope I get any help...
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
2minuutes said:
What a great ROM, but I've got a problem where my Viewpad don't boot. Ok, it boots the first time after installing it, but not on 2nd boot. I've tried to install it over both VegaICS and VegaCream RC2. Does anybody have a solution? I really want this ROM. I had the same problem on VegaCream in the past, but it I think it works now, but not in VegaBean. I hope I get any help...
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
Click to expand...
Click to collapse
ye its the same problem , flashing with CWM kill your Pad at second boot
thats why i am flashing only via NVflash
Vlad87do said:
ye its the same problem , flashing with CWM kill your Pad at second boot
thats why i am flashing only via NVflash
Click to expand...
Click to collapse
VegaCream works now after flashing it through NVFlash. Could the boot problem have something with an uncomplete CWM or something? Like it "destroys" the important partitions?Since both VegaCream and VegaICS use an unofficial build of CWM with Touch-interface? Mabye I'll try to flash an official version and install VegaBean through there! Will report back if it works!
Nice, will test this out!
2minuutes said:
VegaCream works now after flashing it through NVFlash. Could the boot problem have something with an uncomplete CWM or something? Like it "destroys" the important partitions?Since both VegaCream and VegaICS use an unofficial build of CWM with Touch-interface? Mabye I'll try to flash an official version and install VegaBean through there! Will report back if it works!
Click to expand...
Click to collapse
I can now confirm that flashing VegaBean through official CWM works, and it boots and 2nd boot too... Just download the .zip file at the bottom and follow this guide by me: http://forum.xda-developers.com/showthread.php?t=1597556 or this guide by add.thebad: http://forum.xda-developers.com/showthread.php?t=1041036
Don't forget to hit the "Thanks" button if I helped you out
Link: https://dl.dropbox.com/u/85837377/recovery.zip
Thank you , i will do it then today !
Should i do it better via PC-adb and flash 3.0.2.8 with guide from add.thebad or better your method and recovery OR its just the same recovery 3.0.2.8 just deffirend flash method ???
...........................
Permission request to scanno: can I use his rom as base for Remics-Vega??
Vlad87do said:
Thank you , i will do it then today !
Should i do it better via PC-adb and flash 3.0.2.8 with guide from add.thebad or better your method and recovery OR its just the same recovery 3.0.2.8 just deffirend flash method ???
...........................
Permission request to scanno: can I use his rom as base for Remics-Vega??
Click to expand...
Click to collapse
If you want to use this for a new rom go ahead. Just give the credits for the work done (also ejtagle and brucelee666)
Modifications to the standard AOSP source code can be found on my github. Also the kernel sources are there too.
They are not up-to-date yet.
If you find solutions to problems in the ROM, give them back to the community so they can also be used in other ROMS.
scanno said:
If you want to use this for a new rom go ahead. Just give the credits for the work done (also ejtagle and brucelee666)
Modifications to the standard AOSP source code can be found on my github. Also the kernel sources are there too.
They are not up-to-date yet.
If you find solutions to problems in the ROM, give them back to the community so they can also be used in other ROMS.
Click to expand...
Click to collapse
yes ofc i will.
Is there Host-Driver in the kernel included ?
I am searching developers for Advent Vega device : http://remics.bennz.eu
If you have interests to join Remics-Team pm me!
Vlad87do said:
yes ofc i will.
Is there Host-Driver in the kernel included ?
I am searching developers for Advent Vega device : http://remics.bennz.eu
If you have interests to join Remics-Team pm me!
Click to expand...
Click to collapse
If you mean USB host... Yes it is... On my github there are the sources of the 3.1.10 kernel (based on the rel-15r7 version of nvidia) with the patches ejtagle made. But they are not up to date yet.
As soon as i have time i have to clean up the lunch target of beta1 and do a commit on github. Then you can fork from there and build a version for yourself. If you use the manifest file for vegabean you also get the modifications made to the framework, wpa_supplicant etc to make it all work.
See https://github.com/scanno
Again do not use it yet because they are not up to beta 1.
Thanks for the offer, but i do not have time to do a lot of work and join a development team. For the development of roms for the advent vega i would prefer and suggest that you and the Remics team go to the modaco forum and join the kernel development thread and join the efforts.
This way we have more changes of getting a very good base and from there make ROMS. The more roms to choose from, the better for the people using an advent vega.
Thx for answere, but i dont will compile it , i will use the ready zip file and edit it.
I am not a kernel-developer
thats why i asked you about team
Vlad87do said:
Thx for answere, but i dont will compile it , i will use the ready zip file and edit it.
I am not a kernel-developer
thats why i asked you about team
Click to expand...
Click to collapse
Ok... but again all help is welcome, but you know that. Besides kernel development is done by EJtagle and not by me. He reversed engineerd most of the device specific vega stuff.
Also... /system/lib, /system/framework, /system/usr, /system/app are squashfs filesystems. To access the files in there you have to unsquash them.
do you can tell me programm on windows how to unsquash and again to squash after editing ?
Vlad87do said:
do you can tell me programm on windows how to unsquash and again to squash after editing ?
Click to expand...
Click to collapse
Sorry... I am using Linux and it is available in the repository there. On windows I really do not know. You could Google to see if there are any hits on mksquashfs and unsquashfs. That are the tools used on Linux.
You will need to find a version that supports XZ ( LZMA2) compression. That is the compression algorithm used in vegabean.
This is needed because otherwise the ROM does not fit in the /system partition.
very nice!
7zip can do it under windows - unpack
Introduction
This kernel is designed to be more stable than the stock kernel, with more features and more performance. Choose any three.
I do not include any changes that have no clear positive effect on these goals.
Features
zImage (kernel binary) features:
- Asus 10.6.1.14.10 base
- Support for Samsung's F2FS filesystem (experimental) and exFAT
- ISO 9660 + UDF support (CD/DVD filesystems)
- CIFS (for mounting Windows shares)
- BFQ I/O scheduler (http://algo.ing.unimo.it/people/paolo/disk_sched/) v7r5; ROW I/O scheduler v4 (https://patchwork.kernel.org/patch/1862241/) and "deadline" is also available
- fsync control (echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled)
- Overclocking up to 1800 MHz, based on clemsyn's patch, configurable clock frequencies for balanced and performance mode
- User voltage control for undervolting
- Crash fixes when reading various files in /sys
- mount space hack from http://forum.xda-developers.com/show...php?p=36889027 allows mounting across Android processes again (e.g. using CIFS Manager)
- NFS v3/v4 client (supports files > 2 GB)
- NFS v3/v4 server as module (untested, needs userspace tools which I haven't yet compiled)
- Framebuffer console at boot (Android penguins!)
- Keyboard dock: support for F1-F12 function keys, special key mappings for CyanogenMod and GNU/Linux (Esc, Insert, Delete, Alt, Windows)
- Support for various USB Ethernet adapters and FTDI serial port adapters
- Kexec-able and able to kexec other kernels
- SELinux is not included for compatibility with the stock ROM's proprietary NTFS and exFAT drivers
- Tethering via dock USB port (untested), see http://forum.xda-developers.com/showpost.php?p=52917184&postcount=2740
Ramdisk features:
- adbd with root access enabled in default.prop, ro.secure=0
- optimized mount options (noauto_da_alloc)
- init.d script support
- USB IDs for all Tegra 3 based Transformer models (init.xx.rc)
- does not set lcd_density (dpi unlocked), must/can be set in /system/build.prop instead
- preinit system for easy ramdisk customization without repacking or reflashing the kernel: if exists, runs a custom script "/system/boot/preinit" before Android init, e.g. for adding Data2SD detection, ROM2SD, etc.
- File-system auto-detection for use in preinit scripts
Installation/Download
Flash the zip in recovery and reboot; the bootloader will move the kernel to its final place while showing a blue progress bar.
Compatibility
This kernel is compatible with the 10.6.1.14.x bootloaders and stock-based (Asus Android 4.2.1) ROMs that set lcd_density (dpi) in build.prop - in other words, this is the preferred kernel for CleanROM Inheritance. It also works with other ROMs up to Android 4.4 (requires a preinit script to provide the corresponding ramdisk files). The kernel is derived from the original TF700T sources but is known to work also on the TF300.
MD5 sum:
You don't need an MD5 sum. Enable "Zip file signature verification" in TWRP instead - it checks the SHA1 checksum embedded in the archive, which is both more secure and more convenient.
Download the latest version here -> http://forum.xda-developers.com/showpost.php?p=55513454&postcount=484
Credits
- Linux kernel devs and Asus for the base
- Gentoo devs for their easy "crossdev" toolchain-generation tool
- scrosler for the original CleanROM
- sbdags for CleanROM Inheritance
- Ezekeel for the fsynccontrol patch (http://rootzwiki.com/topic/14685-kernel27-jul-glados-v20-for-jb/page__st__700#entry607555)
- faux123 for the user voltage control patch
- clemsyn for the overclocking patch. I still use his frequency and voltage tables but rewrote the EDP handling.
- Hundsbuah for decoding the EDP limit tables and finding an f2fs patch that applies cleanly to our kernel
- cogano for improving the dock key mapping for native Linux
- wenchien for cherry-picking lots of f2fs updates from later kernels
Development Info
Guide for unpacking and repacking kernel blobs and boot images -> http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
XDA:DevDB Information
_that-kernel, Kernel for the Asus Transformer TF700
Contributors
_that
Kernel Special Features: Stock kernel with more stability, more features and more performance. Choose any three.
Version Information
Status: Stable
Current Stable Version: that11
Stable Release Date: 2014-09-17
Current Beta Version: that11
Beta Release Date: 2014-09-17
Created 2014-02-17
Last Updated 2014-10-14
Changelog/History
2014-09-17: 3.1.10-that11
New features:
- enable tethering via dock USB port (untested)
- fix for the Towelroot exploit
- lots of f2fs updates from mainline kernel, thanks to wenchien
- new BFQ (budget fair queueing) I/O scheduler
- added FTDI USB serial support
- exFAT filesystem support from Samsung
download -> http://forum.xda-developers.com/showpost.php?p=55513454&postcount=484
2014-05-14: 3.1.10-that10
New features:
- Removed the special overclocking mode (system_mode 3) - instead, clock speeds for balanced and performance modes are now user-configurable.
- More options for dock key mapping for GNU/Linux and autorepeat
- File system auto-detection in init for use in preinit script
download -> http://forum.xda-developers.com/showpost.php?p=52659251&postcount=446
2014-03-29: 3.1.10-10.6.1.14.10-that9-oc
New features:
- Dock function keys and CyanogenMod-compatible mode for dock keys
- Support for various USB Ethernet adapters
download -> http://forum.xda-developers.com/showpost.php?p=51486800&postcount=414
2014-02-17: 3.1.10-10.6.1.14.10-that8-oc
New features:
- F2FS (Flash Friendly) filesystem by Samsung (experimental, may eat your data)
- USB mass storage support (needs a computer that understands ext4 (i.e. Linux))
- Enabled dual filenames on FAT filesystems for compatibility with some devices
download -> http://forum.xda-developers.com/showpost.php?p=50408485&postcount=396
2013-11-22: 3.1.10-10.6.1.14.10-that7-oc
Security config options disabled to restore compatibility with proprietary exFAT/NTFS modules. Details and download -> http://forum.xda-developers.com/showpost.php?p=47743629&postcount=358
The Data2SD auto-detection add-on is here: http://forum.xda-developers.com/showpost.php?p=40522097&postcount=56
Or if you prefer Data2SD with internal /sdcard: http://forum.xda-developers.com/showpost.php?p=41305526&postcount=159
(these add-ons are unchanged since they were released, so if you already have them installed, you don't need to reinstall when updating the kernel)
2013-11-11: 3.1.10-10.6.1.14.10-that6-oc
Now with 100% more penguins! Get it here -> http://forum.xda-developers.com/showpost.php?p=47361802&postcount=325
2013-09-06: 3.1.10-10.6.1.14.8-that5-oc
Overclocking is back! Get the new version here -> http://forum.xda-developers.com/showpost.php?p=45332265&postcount=263
2013-07-03: 3.1.10-10.6.1.14.8-that4
The latest version is here -> http://forum.xda-developers.com/showpost.php?p=43199757&postcount=237
New kernel features since -that2
- rebased on Asus source release 10.6.1.14.8
- mount space hack from http://forum.xda-developers.com/show...php?p=36889027 allows mounting across Android processes again (e.g. using CIFS Manager)
- some more sysfs crash fixes
- "deadline" I/O scheduler added (default is still ROW)
- NFS v3/v4 client (supports files > 2 GB)
- NFS v3/v4 server as module (untested, needs userspace tools which I haven't yet compiled)
New ramdisk features since -that2
- fstab: optimized mount options (added noauto_da_alloc)
- added init.xx.rc files for other Transformer models
2013-06-25: 3.1.10-10.6.1.14.8-that3
preview release, see http://forum.xda-developers.com/showpost.php?p=42915255&postcount=201
2013-04-11: 3.1.10-10.6.1.14.4-that2
The Asus source release was surprisingly fast this time. I ported all my popular non-intrusive stock kernel improvements (http://forum.xda-developers.com/showthread.php?t=2125783) and recompiled the kernel. Special thanks to buhohitr for testing this release!
I couldn't get the framebuffer console to work, so no UltraCleanROM support for now.
(-that2 downloads deleted)
Documentation
This kernel supports a few additional parameters. As usual these can be set from a root shell or an init script - for details how to do that, read a tutorial about using the Unix/Linux command line.
fsync
To turn off fsync (warning: read this and this before):
Code:
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
To turn it on, write 1 instead of 0.
Clock speeds and overclocking
Note that the special overclocked system_mode 3 has been removed in -that10. There are now only 3 modes, as in the stock kernel (powersave, balanced, performance). To enable overclocking beyond 1700 MHz (or 1600 MHz for more than one core), you need to override the EDP limit:
Code:
echo 1 > /sys/module/cpu_tegra/parameters/override_edp
To set clock speeds for balanced and performance mode, for example:
Code:
echo 1300 > /sys/module/cpu_tegra/parameters/override_mhz_bal
echo 1800 > /sys/module/cpu_tegra/parameters/override_mhz_perf
User voltage control
works exactly like in upstream implementation - ask me to update this if you want to know more.
Keyboard dock tweaks
CyanogenMod has a slightly different mapping for some of the dock function keys. To enable compatibility with CM and CM-based ROMs:
Code:
echo 1 > /sys/module/asusdec/parameters/cm_mode
Function keys F1 to F12 can be entered using right Alt/AltGr and the keys from "Toggle WiFi" to "Next Track". This might only work in native Linux and maybe CM.
For native Linux users, I added additional parameters:
Code:
echo $flags > /sys/module/asusdec/parameters/key_flags
echo 1 > /sys/module/asusdec/parameters/key_autorepeat
where $flags is a number between 0 and 15, by combining these bit flags:
1 = inverts the meaning of Alt for function keys (F1-F12 without Alt, and special functions with Alt. Also, Mute is Insert and Lock is Delete.)
2 = Back is Esc
4 = Search is left Alt
8 = Home is left Windows (aka "Meta" aka "Super_L")
Thanks so much for the RIL patch that seems like fixed my compiling problems lets see
IM just a noob here trying to compile and learn hehe:victory:
EDIT: Yes it compiled
Now I ask myself why Asus released a bad source code lol?
maxrdlf95 said:
Thanks so much for the RIL patch that seems like fixed my compiling problems lets see
Click to expand...
Click to collapse
The RIL include fix is old news - it was already required in the 10.4.4.x kernel, and it's published in my 10.4.4.25 kernel release thread.
maxrdlf95 said:
IM just a noob here trying to compile and learn hehe
Click to expand...
Click to collapse
Learning by doing is still the best way. If you manage to get your own kernel installed and running (if not, read my blob repacking guide), then you have definitely left the "n00b" status.
maxrdlf95 said:
Now I ask myself why Asus released a bad source code lol?
Click to expand...
Click to collapse
Maybe they are using an older compiler that behaves differently.
Thanks man I already knew how to make the blob file and put the signing in, I used to help clemsyn packing its kernel when he didnt have time and well I did it tonight :good: I compile my kernel thanks now will learn how to make it with linaro
EDIT:
P.D I left the n00b status some time ago lol
To install this kernel, do I need to flash both the flash zip and the patch for sbdags' Asus stock rom . I have a US bootloader and a WW rom
lartomar2002 said:
To install this kernel, do I need to flash both the flash zip and the patch for sbdags' Asus stock rom . I have a US bootloader and a WW rom
Click to expand...
Click to collapse
Which patch for sbdags' stock ROM?
_that said:
Which patch for sbdags' stock ROM?
Click to expand...
Click to collapse
In the OP the line just brlow where the krrnel flash zip is.
lartomar2002 said:
In the OP the line just brlow where the krrnel flash zip is.
Click to expand...
Click to collapse
That patch has nothing to do with sdbags roms,that patch contains all the changes made to the original kernel and it's for development only (you can apply that patch to the original or own 4.2.1 kernel source).
Pretoriano80 said:
That patch has nothing to do with sdbags roms,that patch contains all the changes made to the original kernel and it's for development only (you can apply that patch to the original or own 4.2.1 kernel source).
Click to expand...
Click to collapse
Ok, so I only need to flash the kernel zip for 4.2?
lartomar2002 said:
Ok, so I only need to flash the kernel zip for 4.2?
Click to expand...
Click to collapse
Yes.Keep in mind that after flashing the kernel the DPI will be set to 160.
Pretoriano80 said:
Yes.Keep in mind that after flashing the kernel the DPI will be set to 160.
Click to expand...
Click to collapse
In other words: either not be old or have your reading glasses at hand?
Not here. DPI is still at 240.
Flashed kernel, UV 75mV and all looks ok. :good:
Pretoriano80 said:
Yes.Keep in mind that after flashing the kernel the DPI will be set to 160.
Click to expand...
Click to collapse
Snah001 said:
Not here. DPI is still at 240.
Flashed kernel, UV 75mV and all looks ok. :good:
Click to expand...
Click to collapse
Flashed on top of the original Asus 10.6.1.14.4 firmware?
Pretoriano80 said:
Flashed on top of the original Asus 10.6.1.14.4 firmware?
Click to expand...
Click to collapse
I had already changed the build prop file to set dpi to 213 and when I flashed this new kernel it held the setting.
Obviously if you edit the build prop file then your setting remains however if you haven't then maybe it will change to 160. This I'm not sure about since if the default set by stock ROM is 240 and this is what we edit, why would it change to 160?
Pretoriano80 said:
Flashed on top of the original Asus 10.6.1.14.4 firmware?
Click to expand...
Click to collapse
Yes, just flashed kernel as always
Sent from my Asus Infinity TF700 with Dock
Does anyone have the md5 handy for the kernel zip? Thanks in advanced...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
calvinb1 said:
Does anyone have the md5 handy for the kernel zip? Thanks in advanced...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
This
abbea13a9c1f9efa46fd4235a6a2f1b9
eckka said:
Obviously if you edit the build prop file then your setting remains however if you haven't then maybe it will change to 160. This I'm not sure about since if the default set by stock ROM is 240 and this is what we edit, why would it change to 160?
Click to expand...
Click to collapse
For some unknown reason, the default build.prop on the TF700 contains the line "ro.sf.lcd_density=160" - the correct 240 dpi is set by the stock kernel's ramdisk. I removed the latter, so the setting in build.prop takes effect.
calvinb1 said:
Does anyone have the md5 handy for the kernel zip? Thanks in advanced...
Click to expand...
Click to collapse
Ah, I forgot to mention this, which I now added to the OP:
You don't need an MD5 sum. Enable "Zip file signature verification" in TWRP instead - it checks the SHA1 checksum embedded in the archive, which is both more secure and more convenient.
osm0sis' Odds and Ends -- Misc./Batch Tools, Flashable Zips, Scripts, etc.
General Information
In a nutshell, I just wanted a single thread to gather links to some of my other, larger projects, but also serve as a spot I could put some smaller scripts and zips I've created that I don't think merit their own separate threads. This is partially for my own sanity and will hopefully make it easier for others to find some things as well. A lot of the stuff here was developed with the GN, N4, N5, N7s or N5X, OP5/T, OP6/T, OP7Pro/T, OP8Pro/T or OP9Pro (my devices) and Windows in mind, but could generally be applicable to most devices either out-of-the-box or with some slight modification. If you see something that inspires you, go ahead and mod it, just let me know and give me some credit somewhere. If anyone would like to know the specifics of what's in a particular script that I haven't already linked to more information on, just let me know and I'll post that in here as well.
Note: Older zips with a "cwm-" prefix are NOT only for the now-defunct ClockworkMod Recovery, the prefix was used to denote a flashable zip before I adopted Chainfire's "UPDATE-" prefix. Please use a currently maintained recovery, like TWRP, for all zips to ensure the best compatibility/results.
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Misc./Batch Tools
AnyKernel3 (many devices) - link
AnyKernel was a simple template for an update.zip that could apply any kernel to any ROM, regardless of ramdisk to reduce the chance of any issues arising from the custom kernel pairing. The drawback to this is that some kernels require modifications to the ramdisk to enable/set up kernel features, and in the old AnyKernel format there was no way to do this. AnyKernel3 pushes the format even further by allowing kernel developers to modify the underlying ramdisk for kernel feature support easily using a number of included command methods along with properties and variables to customize the install experience.
APK-Patcher (many devices) - link
A proof-of-concept, simplifies APK modification to make it easier for modification creators to keep creating. Using JesusFreke's brilliant bak/smali and iBotPeaches' excellent apktool, modified to run on-device along with the various binaries required, allows on-the-fly APK modifications to be applied via recovery, to whatever ROM APK is present, taking the constant update burden off of the modification creator. The zip is smart and automated, using the APK name to run all the various parts involved for complicated patches and is extensible to any number of APKs in a single zip.
Android Image Kitchen (many devices) - link
A collection of Windows/Android ports of the necessary Linux utilities for Android image (kernel+recovery) mod work, and my own automation script to unpack, edit and repack the ramdisk. Other guides/scripts exist but none of them are universal for target device, compression and/or developed for Windows/Android. Now also Linux builds to bring my improved featureset back to where it came from, recently extended to macOS as well. Has been extremely useful for me in my messing around with kernel ramdisks.
ADB Screenshot (many devices) - attached
Take screenshots while in recovery. Useful for development of recovery apps or error reporting. Original method had lots of different threads around with the general method for various devices but I figured out a couple tricks required for getting it working on the Galaxy Nexus and then automated the process. Tested and confirmed working with both pixel formats of CWM and TWRP. More information in this GN Q&A FFmpeg thread. New method uses fb2png and should work on all ARM devices.
ADBsync sdcard Backup (many devices) - attached
Backs up the entire sdcard so that you can have a complete snapshot of your device when you make periodic backups, and be able to restore things exactly as they were. Automates the sync process of Renate NST's great adbsync utility which makes only newer files get pulled, significantly decreasing backup time for the sdcard compared to "adb pull". Original version posted in the old adbsync thread. Defaults for devices with /data/media/ internal sdcards (Nexus devices, etc.), but is easily customizable to backup other mountpoints or backup via ADB over WiFI.
Flashable Script Zips
TWRP A/B Retention Module script (many devices) - link
We need an interoperable root ecosystem again. A/B and system-as-root were a big setback to the root community in this respect. To help alleviate this issue, this atypical Magisk script zip "module" will keep TWRP installed to both slots when flashed from Magisk Manager after an A/B OTA has installed in the background, but before you use Manager to install Magisk to inactive slot.
Nexus BootUnlocker script (GN, N4, N5, N7 '13, N10) - attached
I don't know about everyone else but sometimes I find I've rebooted into the bootloader only to realize I've forgotten to unlock it in segv11's excellent BootUnlocker App beforehand. Well, I decided to make a BootUnlocker Script for my Galaxy Nexus so I could just boot to recovery quickly, unlock, then adb reboot-bootloader (or use my Reboot To Bootloader script below) to get back without having to fully boot the OS to make the change. Also extremely useful in the case you aren't able to boot. As with the app there is no data loss like there would be with fastboot, allowing you to relock for safety. Originally posted in the GN EDIFY Scripting thread. Modified for the newer Nexus devices and combined into a single Nexus BootUnlocker zip with tamperbit reset support added using information from the BootUnlocker App Dev thread. For newer devices using Factory Reset Protection (N6 and later), the BootUnlocker Script can't directly toggle the lockstate due to new security tokens, but it does now toggle the ability to use "fastboot oem unlock" without needing a booted device.
N7 BootUnlocker script (N7 '12) [creation guide] - link
The Nexus 7 2012 is a special case. Per-device encryption of an entire partition makes it impossible to support the N7 '12 in a simple root app, or flashable zip as above, however using my guide and included script you can now create a working BootUnlocker Script Zip for your specific device. As with the above scripts there is no data loss like there would be with fastboot, allowing you to relock for safety.
sdcard Fix Permissions script (many devices) - attached
A little flashable zip script to fix ownership and permissions of files and directories on the sdcard to what they would be if Android OS had put them there itself, since some apps can't access pushed files that have root.root as owner/group. This is useful when restoring to your sdcard backup, as with my ADBsync sdcard Backup batch script above, since generally, pushed files get root.root from adb shell and higher permissions than usual. Also a solution for a bug where sdcard files get lower permissions somehow, resulting in similar access problems. Currently written for devices with /data/media/ internal sdcards (Nexus devices, etc.), but could easily be modified for other mountpoints. No longer required on Oreo since it fixes these itself at boot.
Recovery SLAM script (many devices) - link
Recovery "Simple Legacy Auto-Mount" (SLAM!) is for devices that have been updated to SAR, but there are older zips that break in TWRP because they rely on the mounts occuring a certain way, especially during a ROM OTA. Recovery SLAM mounts them more as the zips would expect, generally allowing them to proceed. Most useful for premounting /system before a legacy zip with my FlashAfterUpdate addon.d script.
SUmount script (many devices) - attached
Another tool for the toolkit of anyone using Chainfire's SuperSU or topjohnwu's Magisk systemless root, this simple flashable zip script toggles the mounting of the su.img, magisk.img and magisk_merge.img while in recovery to allow easier access to the /su, /magisk and /magisk_merge filesystems, simplifying manipulating it via ADB shell, AROMA Filemanager or TWRP's terminal/file manager. Especially useful to anyone who uses su.d/post-fs-data.d scripts or can't boot due to some issue with a user addition in /su/su.d, /su/bin or a Magisk module.
unSU script (many devices) - link
While experimenting with Chainfire's brilliant SuperSU systemless root, I discovered that uninstalling the older style system-modifying root through his app (<2.60) didn't restore all of the modified system files correctly, so I wrote this script to do so and aid in people wanting to unroot from recovery. Expanded to support uninstallation of Koush's SuperUser, phh's Superuser, SuperSU Systemless (su.img and BINDSBIN), Magisk, LineageOS addonsu and custom ROM su binaries.
Adreno Systemless Installer script (N5, N6, N7 '13) - link
For use with Qualcomm's official updated preview GPU drivers packages for Adreno 3xx/4xx-powered Nexus stock images. This is a different frontend to take whatever device zip from Qualcomm is in the same directory as it (also searching /sdcard), then unpack and install it as a Magisk module or into the SuperSU systemless root /su filesystem, instead of the usual /system.
Kernel MultiROM Injector script (many devices) - attached
Intended for use in Chainfire's excellent FlashFire app to automate re-injecting the current boot image ramdisk with Tasssadar's brilliant MultiROM's trampoline bootmenu; this avoids having to do this as an extra step in MR-TWRP following an OTA, ROM Delta or SuperSU update. Should work for all EMMC devices with MultiROM installed.
GN PIT Editor script (GN) - link
Dumps and alters the Galaxy Nexus' Partition Information Table (PIT) to reclaim unneeded space from the /cache partition and add it to /system to allow for larger ROMs and GApps packages to make continued support for Lollipop+ easier. The resulting file is byte-for-byte identical to those created by external tools like PIT Magic, so that it may be flashed back to the device in Odin Mode to complete the repartitioning.
Kernel Emergency Reset script (many devices) - link
Basically a go-to cure-all for custom kernel users experiencing issues after an upgrade due to old settings left over in a kernel control app (eg. franco.Kernel updater, Trickster, etc.), or problematic init.d/userinit.d scripts. It's also useful if you just want to make sure you're running clean defaults without conflicts.
Reboot To Bootloader script (all devices) - attached
Those who preferred using CWM may have noticed a couple of things missing that the other popular custom recovery, TWRP, has built-in. One of these is a file explorer/manager, which is answered by amarullz' brilliant AROMA Filemanager. Another thing I found myself wanting was a way to reboot back to the bootloader once I'm in recovery, so I created this very very simple flashable zip script. (No longer required on CWM >=6.0.3.5). Note: Once in the bootloader, "Start" will boot you back to recovery. Not sure why, but it's not a big deal, just reboot normally from recovery at that point.
Flashable Installer Zips
Flashlt Installer (many devices) - attached
Installs my Flashlt script to allow easy flash and dump of boot, recovery and radio/modem (possibly others) EMMC or MTD partitions while booted, and trimming of null characters from files. Also installs a script zip that makes flashing boot.img (kernel), recovery.img, and radio.img/modem.img (baseband) files via recovery simple. It aims to save the average user the hassle of repacking their own image zip, or using the command-line or fastboot to flash it. Place an appropriately named file in the same directory as the zip and flash away! Should work on all devices with normal partition naming ("boot", "recovery" and "radio" or "modem") which accept Android standards-compliant images (including a/b slot devices like Pixel). Extremely handy when used with amarullz' brilliant AROMA Filemanager, and/or my Android Image Kitchen: Mobile Edition (linked above).
Busybox Installer (all devices) - attached
A byproduct of building my own static busybox compiles in all Android architectures for my AIK-mobile package, I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. Detects device (ARM/64, x86/_64, MIPS/64) to install the busybox binary, cleans up symlinks from any previous install and generates new ones. Detects and supports SuperSU/Magisk systemless installs. Please read the release post about applet inclusion and special features.
nano Terminal Editor Installer (many devices) - attached
An installer to push my own static Android ARM build of the nano editor and required files to /system/xbin and /system/etc/terminfo, with a wrapper adding a --term option to try terminfo profiles more easily. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted. When flashed in recovery also allows temporary recovery use by pushing a script to /sbin/nano with the required setup, so you can trigger it from adb shell or TWRP Terminal. Makes it extremely easy and worry-free to tweak and mod on the go, knowing you can edit the faulty build.prop or startup script if something goes wrong.
adb + fastboot Installer (many devices) - attached
Marshmallow removed adb from the /system/bin directory. For those wanting this functionality back, here's an installer to push static compiles of adb and fastboot to /system/xbin, with a wrapper to point adb to the correct HOME directory and set TMPDIR for compatibility. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted.
Nexus Media Installer (many devices) - attached
Custom ROMs usually don't include Google ringtones/notifications/system sounds and bootanimation, instead including numerous terrible sounds and often less-than-desirable visuals. This installs the media from old Nexus devices systemlessly (SuperSU and Magisk supported), or to system with an addon.d script to survive a ROM update or dirty flash, and using the zip name (also reading from /data/.nexusmedia) to allow user choice.
mtd-utils Installer (many devices) - attached
mtd-utils (flash_erase, nanddump, nandwrite) are necessary for mod work on a number of Android devices using mtd/char devices instead of the more standard emmc/block devices, and where the busybox versions have been less reliable in the past (especially where it doesn't include flash_erase), using the official suite is preferable. The older ARM builds available on XDA were about a decade old, so I worked out how to configure and cross-compile from the latest source. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted
ZipSigner + Zip Installer (many devices) - attached
Signing zips and APKs on-device has always been a tricky proposition due to memory requirements of the old SignApk.jar, running a jar on an Android device, and other complications for script-based zips. Android has always been missing a zip binary (for unzip see my Busybox Installer). ZipAlign is also handy if you do APK work. To remedy this once and for all, here's an installer to push my dexed version of topjohnwu's brilliant zipsigner.jar and static ARM compiles of zip and zipalign to /system/xbin, with a wrapper to run zipsigner with Android's dalvikvm. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted.
odex Script Installer (all devices) - attached
Based on the great work and binaries from this thread, a simple installer to push my odex script along with the required dexopt-wrapper and zip binaries to /system/xbin and set the appropriate permissions. Automates the procedure to odex any apk or jar from the commandline to potentially improve performance. Dalvik runtime (KitKat and below) only. Also uses cut from busybox.
N5X/6P BLOD Workaround Injector (N5X, N6P) - link
When, unfortunately, my Nexus 5X was recently stricken with the abominable Bootloop of Death, I looked into the well-publicized workaround and turns out it was all contained in the ramdisk and cmdline of a Android image. This is the perfect application of AnyKernel2, so I made an AK2 add-on zip to patch both the current boot and recovery partitions with all the current workarounds to help others afflicted by this issue to hopefully regain their data/device as easily as possible. Linked is the Nexus 5X thread, the Nexus 6P thread may be found here.
N7'13 TWRP flo2flox Injector (N7 '13) - link
The Nexus 7 2013 (flo) has seen a bit of a resurgence with official Lineage 18.1 support repartitioned as "flox". Since official TWRP is still automatically being built only for flo and this isn't compatible with flox, and the minor changes required for flox support were a great application of AnyKernel3, this zip automates the patching process so making official TWRP from flo2flox is easy for all going forward.
GN Synapse Support Injector (GN) - link
This AK2 kernel add-on for the Galaxy Nexus injects support for the Synapse tweaking app into the current boot partition ramdisk, including all the Synapse interfaces for the GN I've maintained since the Franco Kernel and DirtyV Kernel days.
GN Recovery Color Correction Injector (GN) - link
The aging screen on the Galaxy Nexus was looking pretty rough in recovery until I discovered the recently added new OMAP kernel color correction was also present in the most recent TWRP recovery versions. So this add-on zip uses AK2 to patch the current recovery partition ramdisk to add the command to reduce that green/yellow SAMOLED nastiness.
Kernel init.d Support Injector (many devices) - attached
An experimental proof-of-concept. Following from great ideas by Captain_Throwback in my AnyKernel2 thread and using script from my Flashlt script above, this AK2 zip will inject basic init.d bootscript support into any kernel ramdisk on any emmc device with normal partition naming and using the Android bootable image standard, without having to bloat a ramdisk using a busybox binary. This zip is also signed, so could potentially be used with non-Nexus stock recovery on a locked bootloader.
CMSetup Fix for GApps Installer (many devices) - attached
Installs a su.d script fix to work around the CyanogenMod/LineageOS 13 ROM issue of a broken Quick Settings pull-down when CMSetupWizard is removed as part of a GApps installation. Removing CMSetupWizard is useful because it allows Google's SetupWizard to grant apps default permissions, so the workaround automatically executes the only required command at the appropriate time following first boot. Requires a SuperSU/Magisk installation (for su.d/post-fs-data.d support). Flash after the SuperSU/Magisk zip and your GApps.
Dev Team init.d Pack Installer (all devices) [see "950iosettings, etc." below] - link
A simple installer I wrote to create the /system/etc/init.d/ directory, extract the latest init.d scripts as published by the "Franco's Dev Team" tuning collective (of which I was a member), then set correct owner, group and permissions to the entire init.d directory. If you are a developer and would like to include these tunables/scripts in your kernel or ROM please provide credit. A lot of time and effort has gone into this project and that's all we ask.
Scripts
950iosettings + 875mntsettings + 925vmsettings + 975experimental init.d scripts (all devices) [with Franco's Dev Team] - links
Also available bundled in an installer. The scheduler tunables have already gained a bit of attention/adoption on various devices and kernels, but this is the init.d script I wrote to set the new custom scheduler tunables values as "default" by an independent loop, sleeping in the background and detecting each time the scheduler is changed. There is no effect on idle drain or deep sleep. The settings included are the complete work of the "Franco's Dev Team" (or "Team Franco") tuning collective, of which I was a member. We strove to perfect the scheduler, vm and various other settings for the smoothest and fastest experience available. The collective was: malaroth, osm0sis, joaquinf, The Gingerbread Man, pkgnex, Khrushy, shreddintyres. If you are a developer and would like to include these tunables/scripts in your kernel or ROM please provide credit. A lot of time and effort has gone into this project and that's all we ask. Lollipop(+) updated versions now also available through the continued excellent work of pkgnex.
999-flashafterupdate.sh addon.d+addon.d-v2 script (many devices) - attached
For ROMs that don't have "Flash After Update" support built into their delta/update process. During an upgrade, this script will flash zips from an sdcard directory, with several options (listed in the script header) for displayed output, after all other addon.d backup/restore actions have completed. This can be used to flash SuperSU and then an AnyKernel2 kernel on LineageOS, for example. Only zips that specifically support addon.d-v2 can be supported on A/B devices. See this how to for instructions for use with A/B devices. Unzip once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
98-twrp_ab.sh addon.d-v2 script (many devices) - attached
Allows you to keep TWRP installed in a boot partition through A/B OTAs with Magisk installed by copying the TWRP ramdisk from the current slot to the updated one, before Magisk's addon.d-v2 script patches it. Requires a current Magisk installation since we need the tools and Magisk's the only way to ensure a working addon.d-v2 environment across ROMs at the moment. Unzip once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
97-dumpimages.sh addon.d+addon.d-v2 script (many devices) - attached
For ROMs with boot.img, etc. inside an OTA payload.bin or otherwise inaccessible, it dumps the updated chosen partitions before further modifications (TWRP, Magisk, etc.), saving it to /sdcard/Download/boot.img or to/from other customizable locations at the top of the script. Unzip once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
00-omnirootfix.sh addon.d-v2 scipt (many devices) - attached
OmniROM appears to include 69-gapps.sh automatically in its /system/addon.d directory despite not shipping with any GApps; when not rooted this doesn't appear to present a problem, but really this is only because the script doesn't have enough permissions to run how it's supposed to since Omni's sepolicy doesn't let addon.d-v2 work correctly. Once Magisk is installed, providing more privileges to the addon.d-v2 update_engine, Omni's 69-gapps.sh would remove important system files during an A/B OTA when no GApps were installed, so this script will simply prevent that for those wanting to run Omni minimally and with root. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
00-resizesystem.sh addon.d script (many devices) - attached
One common solution for aging devices is to resize the /system partition so that it can hold newer, larger ROMs and, of course, GApps packages. On devices where the /system partition has been resized to hold larger GApps packages, but the ROM in use has system.dat format zips with no resizing functionality, the extra space would get lost in a ROM delta flash, breaking things when GApps attempted to restore. This script will resize the system partition to its maximum before the GApps restore occurs on EMMC-based devices with standard partition naming. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
10-extract-lineage-kernel.sh addon.d script (many devices) - attached
Nowadays with systemless root and other boot.img mods out there, it's good to have a backup of your ROM's unmodified boot.img handy in case you want to do a clean flash of your boot partition. Since LineageOS moved their update zips to a /data/data subdirectory that made this harder to get to, I automated the procedure as an addon.d script so that the newest gets extracted on each update. The output directory may be changed by editing the script. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
999-customkernel.sh addon.d script (many devices) - attached
Addon.d is awesome at restoring your GApps, root app, and other things after a ROM Delta, update, or dirty flash, but of course this can leave a lot of stuff out that you'd also have to re-flash (see below for a personal addon.d script you can modify to cover anything else you want to save). This script aims to help remedy the issue for custom kernel users on EMMC-based devices with standard partition naming by dumping the current kernel as part of the addon.d backup process, and then restoring it after the ROM has flashed its included kernel. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions. This is deprecated by my FlashAfterUpdate addon.d script, above.
logohack.sh (GN) - link
Galaxy Nexus bootloader image replacement hack script. Inspired by bitdomo's brilliant imgdata tool and replicating the functionality of Ezekeel's abandoned, broken paid Logo Me app, this script improves upon the app version by working on all Galaxy Nexus bootloaders and on-the-fly, to allow replacement of the Google logo and lock images within the sbl partition. Remove the .txt extension once downloaded and place in /system/bin/ or /su/bin/ with rwxr-xr-x (755) permissions. It can then be run from the Terminal.
flash_image (many devices) - attached
MTD devices require a little extra finesse when flashing partitions from the command prompt and multiple commands, versus MMC devices, for which we can just use the dd command both ways. I wrote this little script to simplify the process for myself in my MX Box tinkering. It parses /proc/mtd so you only need to enter the partition name. It requires _n0p_'s excellent MTD-Utils compiled for Android, and uses grep and cut from busybox. Remove the .txt extension once downloaded and place in /system/xbin/ with rwxr-xr-x (755) permissions. It can then be run from the Terminal.
getprio (all devices) - attached
Android doesn't allow you to check the priority (or "niceness") of a process with the getpriority command as you would with normal Linux, and busybox doesn't provide this functionality either, so I wrote this reasonably simple script to allow you to check the niceness of a process. Some kernels have been experimenting with increasing the priority of com.android.systemui for smoothness, so this command can be used for testing different levels and whether the renice command set it correctly. Remove the .txt extension once downloaded and place in /system/xbin/ with rwxr-xr-x (755) permissions. It can then be run from Terminal with either the pid (default), class or a class name search string. Uses pidof and pgrep from busybox.
gappsintegrator init.d script (many devices) - link
ROM GApps Auto-Integration of /data/app GApps into /system, complete with libs (unlike Titanium Backup), for Jelly Bean through Marshmallow. It should process things early enough in the boot that afterwards Dalvik will immediately do the cleanup ("Android is upgrading..."), much like following an OTA. An initial GApps installation is one requirement and there are some important notes for support of Lollipop and above. Intended for ROMs with a busybox installation. Can also remove libs from and zipalign the integrated APKs if those binaries are present in the ROM.
lmkwhitelist init.d script (all devices) - link
Users running ROMs or kernels with extremely aggressive custom lowmemorykiller (lmk) driver settings may notice their launcher redrawing frequently. Some kernels/ROMs also include an exclusion for this by making stock (or the included) launcher unkillable, however that still leaves all the 3rd party launchers out there that people use. I wrote this init.d script with a community created list of the most common launchers to make whichever one is installed unkillable. This also has instructions for how to set up init.d scripts. If your launcher isn't included in the list, you can modifiy it by adding the application class name (from the Play Store URL) to the list within quotes, separated by spaces. Also part of the 975experimental Franco's Dev Team init.d script, linked above.
dalvik2cache init.d script (all devices) - link
Bind mounts the dalvik-cache directory to the cache partition. Useful on devices where the cache is sizable and unlikely to be used for OTAs (custom ROM, etc.), and the data partition is not. Every little bit counts!
settingsdump.sh (all devices) - attached
In comparing vm settings from various kernels and ROMs to see what's out there, I wrote this script to generate a list of the values of all the relevant sysfs files and directories. Now expanded to cover cpu and governor as well. Remove the .txt extension once downloaded. To run it, assuming you just put it in /sdcard/, open Terminal Emulator and type: "sh /sdcard/settingsdump.sh" (without quotes). It will output the file to /sdcard/r*-output.txt where * is the revision of the kernel you're running. This makes it easier to compare what's changed between different nightlies, for example.
Other
BootUnlocker app (many devices) [with segv11] - link
With a number of users researching and contributing the bootloader lockbit and tamperbit offsets in threads around xda and to the development thread for seg11's excellent BootUnlocker app, I have begun making beta builds with these new devices added. With hopes of adding any/all that can be, it now supports all the older Nexus devices, OnePlus devices and several others. We are accepting Pull Requests and collaborators for further device/design updates. Check my original revival post for more details.
G-Box Midnight MX2 g18ref ROM, recovery and kernel osmods (MX Box) [with BenniBenassi & relol] - link
I bought one of these unbranded Android TV boxes and was immediately determined to tweak it as much as possible following my work on the Galaxy Nexus. Flashing the official Matricom stock ROM over the generic included one I also discovered the recovery didn't have any A/V output to my old CRT TV. I set out to dump the kernel and recovery images, fix the recovery images and tweak the kernel defaults for the most performance.
Holo Stock Notification Icons for Notification Toggle (many devices) - link
This was likely my first post ever on xda. It is a "Notificon" pack for j4velin's fantastic Notification Toggle App, bringing a seamless stock look to this indespensibly useful app. Also a great way to get back to Settings easily from the notification shade since Android 4.2, and add shutdown/reboot menu functionality to stock/vanilla ROMs.
My GN Kernel Settings + 900colorsettings init.d script (GN) - link
I was being asked a fair amount for my kernel settings over in the GN f.K thread where I helped out, so I posted them up. I also put up an init.d script for setting color values on boot, which can drastically change the outcome on older panels, and at least makes custom values seamless. Instructions for how to set up init.d scripts are included.
Galaxy Nexus Baseband Collection: maguro - i9250 / M420 / SC-04D Radios (GN) [with josteink] - link
Original thread author josteink moved on to other devices and asked me to take over the thread. Lots of great information on the GN radios, posted alphabetically by region and chronologically by the build string date I found embedded in the images. Huge respect and massive thanks to josteink for seeing the need for a baseband thread almost as soon as the Galaxy Nexus was launched, way back in December 2011, and maintaining it diligently.
TK GApps (many devices) [with TKruzze] - link
After helping TKruzze with some of the concept and script work for his famous Paranoid Android Google Apps packages (PA GApps 2.0), we decided to collaborate again for his return to XDA after a much-needed hiatus, with me doing the thread setup and management with DevDB, and a Q&A section so things don't get overwhelming for those trying to follow along. The main thread remains locked and can be subscribed-to for those wanting notification only when there's a new GApps release, and the Q&A functioned as the main discussion thread where people can help each other. Much of the script is the same from PA GApps but TKruzze has added some impressive new features, made many fixes and revamped a large portion of the documentation. I also continued as an adviser and submitted script when needed.
Nexus Louder Audio Improvement Patch (GN, N4, N5, N7 '12, N7 '13) [with Misledz] - link
One of my earliest forays into EDIFY scripting, I wrote the flashable zip install/revert scheme for this great volume boost mod by Misledz. The scripts check to see if the mod is already installed and if so recommends you flash the version-specific revert that goes with it. More on that in the Intelligent EDIFY thread. During install the script also backs up the ROM files it replaces so that you don't need to reflash your whole ROM if something goes wrong, just use the revert to restore the backups. I eventually rewrote this completely in shell script with a Universal install/revert, that detects which files to backup and leaves a list for itself to revert. I also wrote automation batch scripts for Misledz as the "Louder Build Farm" to simplify his work for all the versions of the mod he maintains for various devices, linked in the knowledge base below. GN/Dev thread linked; Other links can be found there.
Payload-Dumper-Go for Android Magisk Module (many devices) [with ssssut] - link
payload-dumper-go arm compile and wrapper for use extracting from payload.bin on-device.
Git for Android Magisk Module (many devices) [with Termux] - link
Hacked arm64 git commands for use on booted Android.
Google Experience XML Magisk Module (many devices) [with Google] - link
Hacked Google Nexus/Pixel/Android One sysconfig feature xml entries for use on non-Google devices.
Digital Wellbeing Add-on Magisk Module (many devices) [with Google & Open GApps] - link
Digital Wellbeing for Android 12L and 13 GApps that don't properly support it (like MindTheGapps).
Model Mod Magisk Module (many devices) - link
Experiment to append _SN to the existing device model to get CTS passing again after the September 2021 server-side SafetyNet changes, (superceded by kdrag0n's excellent Universal SafetyNet Fix module).
Xposed Framework Installer Zip (many devices) [with rovo89 & Tungstwenty] - link
When JB4.3 broke all previous root methods I made this simple frontend script to install rovo89's brilliant Xposed Framework for modding ROMs until they could release a new version themselves. Xposed Framework files and the install.sh used are the work of rovo89 and Tungstwenty; I have only created a recovery flashable zip and shell script to function as an alternative frontend for the framework installation process. Then updated to mimic the APK installation and allow devices with /system write protection like HTC's S-ON to install the framework. (Deprecated as of Xposed 2.5).
BBCode for my xda Signature (n/a) - link
Last and definitely least. A number of people have asked me about the formatting of my signature, so here are some simple BBCode tricks and workarounds I thought others might like too. Keep in mind that my signature can be significantly larger because of my RC status.
Enjoy!
Questions, comments and feedback welcome.
Credits & Thanks: All authors of any included binaries and libraries for their amazing work. Anyone who's helped me with these projects along the way.
Disclaimer: Naturally, you take all the responsibility for what happens to your device when you start messing around with things.
Knowledge Base
Links to information/research posts I've made and other experiments.
----
avbtool-arm (zip package) - link
AOSP's BootSignature.jar for AVB v1 was relatively simple to run on-device for boot.img modifying flashable zips like SuperSU and AnyKernel2 but avbtool for AVB v2 is written in Python, so that makes things a bit trickier. For experimentation I whipped up a little wrapper script to run avbtool on-device with an actual Python interpreter.
Omni SoundPacks (and Nexus Stock pack) - link
My suggested expansion to the Omni SoundPacks feature to allow it to cover all SystemUI sounds.
OnePlus FingerPrint Material Icons (Information) - link
My preferred fingerprint icon for the in-screen OP6T sensor using Zacharee1's excellent OPFPControl app.
----
Complete Shell Script Flashable Zip Replacement + Signing Documentation (Reference) - link
Using a shell script instead of an update-binary in flashable zips can make them universal for architecture and put a lot more power in the hands of the developer. This reference documents all of the analogous functions myself and others have written to make this easy.
Booted Zip Flashing Shell Setup Script (Reference/How-To) - link
My implementation of booted zip flashing, originally for AnyKernel2 in Franco Kernel Updater (now Franco Kernel Manager) and since expanded to support AK3's ability to be flashed from anywhere and support most other flashable zips on devices that allow remounting /.
Unified ext4/f2fs ramdisk + ROM installer (Reference) - link
Supporting multiple filesystems like ext4 and f2fs in a custom kernel boot.img ramdisk required some work before custom ROMs were updated to do this themselves and use fallback fstabs. This is the roll-up post gathering all the changes necessary for someone to add this pre-official support to their ramdisk, kernel and ROM installers.
FlashFire Recipe Book (Reference/How-To) - link
Just a quick reference of common tasks (OTA flashing, etc.) for people figuring out how to use Chainfire's brilliant flashing app.
personal addon.d (How-To/Template) - link
I was tired of having to redo a number of tasks (remove files, backup Nexus sounds and replace the AOSP ones, etc.) to get my device back to where I wanted it after flashing a newer nightly, so I wrote an addon.d script to do it all for me. Provided if anyone wants to modify it for their own personal setups.
KBox2: Set Up A Build Environment On Android (How-To) - link
Very cool Linux-like command prompt environment on Android. I originally had it set up as a native build environment with rudimentary git support. You can follow my steps to do the same.
Keeping SafetyNet Passing With Incremental Google OTA on Virtual A/B Devices (How-To) - link
Post-reboot checks added to the incremental OTA process for Virtual A/B devices using Google's servers made it impossible to remain rooted throughout the OTA process, but following these instructions you can complete the OTA then re-root without SafetyNet catching you.
Cygwin-Linux Cross-Compiler (How-To) - link
Compiling from Cygwin with a Linux target required some fixes to the toolchain, so I detailed them for future reference.
N4/N5/N7 '13 Qualcomm Optimized Bionic/Dalvik Patch Comparisons (updated zips) - link
Using Qualcomm optimized files on Snapdragon devices improves performance greatly on KitKat. Especially good on Nexus devices or AOSP ROMs. I took the time to dissect the required files and see what worked best.
AIK Build Farm (desktop shell script) - link
The Cygwin shell script "build farm" I wrote for my Android Image Kitchen project to perform all of the cross-compiles required for the mobile and Linux versions. Allows someone to setup the repos from scratch and build.
Louder Farm (zip packages) - link
The Nexus Louder project was a pretty massive system file modifcation undertaking. This details my work to make building the patch zips easy for co-dev Misledz, and includes the farm packages at various stages.
----
N7 '13 Bootloader cracking (Information) - link
Sat down with my parents' Nexus 7 2013 (before I got my own) over Christmas and cracked the bootloader for unlock support via my Nexus BootUnlocker Script zip and later the official BootUnlocker App.
N7 '13 Unbricking (Information) - link
Instructions I put together for recovering from a hard brick (bad bootloader flash usually), via the exposed Qualcomm/Marshall London "HS-USB Diagnostics 9006" mode.
Default System Alarm Setting Script (Information) - link
A script snippet function to allow easily changing the default alarm sound on ROMs that hide this ability, like OnePlus' OxygenOS.
SELinux Audit2Allow Script (Information) - link
A script snippet for turning SELinux audits in a logcat into allow statements ready for supolicy or magiskpolicy.
Partition Dumping Script (Information) - link
A script snippet for dumping all non-userland partitions from any eMMC device, useful for bootloader lockstate hacking.
GN Partition Information Table (PIT) Research (Information) - link
Wanting to push the GN as far as possible, several remaining users came together to discuss how it could be repartitioned to add more space to /system to better support Lollipop+ and I contributed a large amount of R&D over several posts throughout the thread which resulted in the PIT Editor script zip (posted above). Could be useful for other devices using PITs as well.
GN/N7 '12 tunables post (deprecated) (Reference) - link
The list of supported basic tunables on franco.Kernel for the Galaxy Nexus and Nexus 7 2012 back when those were my primary supported devices.
GN scheduler tunables HZ scale (Information) - link
The Galaxy Nexus scheduler (and other) tunables opperate on an odd scale due to the the device's HZ value in the source being weird. This post experiments with that and finding the method/equation behind it.
LMK boot timing (Information) - link
The Android lowmemorykiller module default tunables go through a bizarre sequence during boot, so I experimented and came up with a script to allow setting alternates as soon as possible.
LMK Launcher Whitelist/Niceness settings reversion (Information) - link
Setting oom_adj values and changing the niceness on launchers and systemui improved responsiveness and helped avoid these important processes being killed by LMK. Then I noticed sometimes they spontaneously reset; experimentation followed.
MTD partition flashing (Reference) - link
My MTD-based MX Box set-top device gave me a few hours of headaches until I figured out how to dump and flash the boot (kernel) partition correctly. This details my experiments and the correct procedure I discovered.
nano Android static build instructions (Reference) - link
A little documentation of all the dirty tricks I used to get the nano terminal editor utility to build for Android from the official git repo source.
mtd-utils Android static build instructions (Reference) - link
A little documentation of all the dirty tricks I used to get mtd-utils to build for Android from the official git repo source.
Pixel Launcher bind mount instructions (Reference) - link
I was annoyed that on stock Nexus 5X and 6P Pixel Launcher wasn't available and when sideloaded lost the Google Feed pane, so I replaced Google Now Launcher with Pixel Launcher using bind mounts.
Netflix broken DRM workaround instructions (Reference) - link
Custom Nexus 7 2013 ROMs Nougat+ have all had issues with Netflix due to some peculiarities of the DRM libraries the ROMs use, but some found that intentionally semi-breaking DRM using files from other devices allows Netflix to work again, but this broke Google Play Movies. I did some more testing, resolved the Play Movies issue and wrote up how to install the single needed replacement library either to system or with a systemless bind mount.
----
Thanks for the interest! More to come, I'm sure!
What can I say...
SUBSCRIBED
Sent from my Galaxy Nexus
Far superior
thanks
Franco Team always made a great work .... Keep it up.
Thanks for these great useful infos!
Bookmarked, subscribed and rated a well deserved 5 stars :good:
Thanks for sharing. Very useful.
Nice...
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Nice collection osmosis
Many thanks osm0sis, to you and all the team for all your contributions Almost feel as though I know you since I've been hanging round GNex and N7 franco.Kernel threads for so long and if you pop up on the N4 thread it's like seeing an old friend I'm mostly quiet, but really appreciate all you do :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Subscribed... Thanks dude...
-3StarsAndaSun
Subscribed. Thanks
Thanks back to you, everyone! I've learned a hell of a lot about Linux and Android in the year since I got my GN, and I mostly have xda to thank for that, even though I've always been the type to tinker and Google things. Still lots more to learn though! But, at the very least I guess nobody can say I haven't been busy since becoming a RC, huh?
Nice to see all these settings are adopted by others, also the interactive tuneables are used in ak kernel now.
Verstuurd van mijn Nexus 7 met Tapatalk
Subscribed :good: !
New version of testvalue.sh up. I added the input value to the output.txt file to make it easier to read since it starts at 0. Right now we're trying to work out the equation for the scale of certain cfq and deadline tunables on the GN, which is a bizarre one:
7, 15, 23, 31, 39, 46, 54, 62
Increases by 8s but occasionally (on the 5th jump, though sometimes 6th) it increases by 7.
Edit: Every 3rd increase of 7 occurs on the 6th instead of the 5th.
Edit 2: Stats genius of the group, @pkgnex worked out what the trick was; dropping the decimals once calculated.
So in Excel: y=TRUNC(x*7.8125,0)
:good:
The "why" of the GN tunables working this way, with a value of 125/16 is a very good question. No ideas there, personally. Something to do with the GN having a HZ value of 128 (where on others it's 100 or even 200) I'd assume, but I don't see the direct connection.
This was very handy to know though, because the cfq+deadline source requires the number of jumps (x) to hardcode the values, not the actual desired numbers like you'd expect.
Perfect!!!
Very interesting
Created a getprio script last night for use in /system/xbin as a runnable script to check the niceness of a process. It's up in the 2nd post now. It attempts to make up for Android not having "getpriority", and not displaying the niceness in "top" or "ps" like it would on mainstream Linux.
Code:
usage: getprio [-p] <pid> | -c <class> | -s <search string>
note - class name search will only use the top result
So you can either -p the numeric pid of a process if you know it (this is the default so the -p argument is optional), -c the class name of the process (eg. com.android.systemui), or -s a search string using part of the class name (eg. systemui). If there is more than one result for the search only the top result will be returned so if you are trying something like "-s mms", you'll only see the system mms process and not com.android.mms until you get more specific with "android.mms" or something. It's likely you've got a lower level process if you get the response "Warning: empty class name!" so that's your tip your search was too broad. Naturally, processes must be running in order to return info as well. :good:
Edit: ps -p will display niceness on Android, but it's not ideal if you want it only for a specific process like with getpriority. Thanks boype.
{
"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 10.6.1.14.10 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 CM11 AOSP sources
Supports EXT4 and F2FS Data partitions
Based off cm-11.0-20140917-crombi-kk-RC2-tf700t 4.4.4r2 source by lj50036
Full Aroma Installer for main rom including choice of 3 kernels and ROM2SD/DATA2sd/F2FS support
CM11 kernel built from CM11 source by lj50036/sbdags
Remixed _thatv10 kernel with CM11 ramdisk - repacked by sbdags
Grimlock kernel with CM11 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: Trebuchet, Google Experience Launcher, Apex , Nova
Boot Animations: CM Circle of Fire, CM Color Circle, Nexus Phase Beam
Gapps (updated by me to Google latest apks and libs) flashed from separate package
Misc Apps: ESFile Explorer, Adobe Flash, AdAway, Titanium Backup, DropBox, 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
Change Log
20140921 changes
- Rebuilt from latest CM11 4.4.4r2 Kitkat - CROMBi-kk source - maintained by lj50036!
- Reverted TF700 base back to RC2 700 base rather than unified 300 transformer base
- Added Aroma install options to auto select/install options; sbdags best, stock cm11, previous saved....
- sbdags = Internal Only + Apex + _that kernel + 213HDPI/160MDPI + fastest tweaks + useful apps + f2fs or etx4
- cm11 = Internal Only + stock cm11 apps & kernel + no tweaks + Gapps + f2fs or etx4
- Added _that kernel version 11
- Updated CM11 kernel to latest version with f2fs fixes from lj50036 & _that
- Removed SELinux support as causing issues
- Removed discard mount option as f2fs and our kernels don't support it
- Removed CM11 backup and restore scripts as causing more harm than good with bundled apps
- Added better zipalign binary
- Added different set of vm tweaks - thanks to kisskat roms
- Added additional tegra core cap & 3D scaling tweaks - thanks _that
- Improved waking up from sleep
- Fixed wake from keyboard - thanks jonoathome
- Added auto detect file system type to aroma - thanks Archidroid
- Added CROMiX TF701 theme to installer
- Added additional resolutions for TF700 users; 1760x1100 @ 220dpi & 1440x900 @180dpi
- 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 Chrome to version 37.0.2062.117
- 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
- Updated GravityBox to verison 3.4.3
- Note : Google Hangouts cannot be updated to latest version due to Google breaking apps packages with incompatible shared libraries. Going forward it will be a store app only
20140906 changes
- Rebuilt from latest CM11 4.4.4rc2 Kitkat - CROMBi-kk source - maintained by lj50036!
- Merged rom from 2 sources to introduce universal installer for 4 devices
- Updated device ID for TF201 which should fix wifi issues
- Updated options with TF700 and ME301, kernels + Device IDs!
- Dynamic fsync properly enabled on Grimlock kernel when fsync disabled selected in installer
- Made Google Calendar install by default as too many apps rely on it
- Updated Google Chrome to version 36.0.1985.135
- Updated Google Maps to version 8.3.1
- Updated Google Search to version 3.6.14
- Updated YouTube to version 5.9.0.13
- Updated ESFileExplorer to version 3.2.0
- Removed DropBox as bloatware (30MB!) - still available on the Play Store
- Removed Google Plus as bloatware (33MB!) - still available on the Play Store
- Removed alternate stock browser as no longer required
- Set default options to sbdags recommended for best performance
20140810 changes
- ROM is now Release Candidate 2! RC1 cleared private testing.
- ROM Version is TF700T_CROMBi-kk_RC2 KitKat-4.4.4rc2-CM11-DEODEX
- Fixed DPI sticking at 240
- Partially fixed black wallpaper issues - reverted cmwallpaper.apk to older version. Something is borked trying to scale wallpapers to TF700 resolution
- Added my Intergalactic Ultra Touch (TM) settings to ROM Super snappy now
- Changed the dalvik vm optimisation to reduce heap closer to stock as I think Garbage Collection wasn't happening frequently enough and when it did it took too long
- WiFi scan interval reset to 180
- Changed Zip Align script to a more recent version and added SQL Lite tweaks
- Can't see benefit of B2R script so default is off now
- Browsers now have their own section in installer
- Dolphin Browser with Adobe Flash both moved to system apps
- Tidied up gapps package from PA Gapps
- Updated Google Music to version 5.6.1617P
- Updated Google Maps to version 8.2.0
- Updated Google Hangouts to version 2.1.317
- Updated Google Chrome to version 36.0.1985.131
- Updated Google Core Services to version 5.0.89
- Updated Apex Launcher to Version 2.5.0
- Updated ESFileExplorer to version 3.1.9.1
- Updated GravityBox to 3.2.5
- Removed phab7 from xposed modules (no longer works on 4.4.x)
- Removed betterbean theme
- Added Android-L theme and Light / Dark variants
20140719 changes
- Google just released Kitkat 4.4.4r2 so we have a new base!
- Rebuilt from CM11 4.4.4r2 Kitkat - CROMBi-kk source - maintained by lj50036
- Improved the touch sensitivity of the screen - thanks Harsh chauhan
- Rom has SuperUser enabled for adb and apps by default now
- Updated hardslog's grimlock kernel so that it runs up to 1.7GHz on all 4 cores now (default is 1.4GHz so edit it in settings - performance)
- Repacked latest CM11 Kernel with init10 functionality for ROM2SD/DATA2SD/F2FS
- Updated Google Maps to version 8.1.1
- Updated Google Mail to version 4.9
- Updated Google Core Services to version 5.0.84
20140715 changes
- Added Google Chrome as an option to install to /system/app
- Added option to remove the Stock Browser from /system/app
- Added Viper4Android Music FX as an option to replace CM DSP Manager
- Rom has SuperUser enabled by default now
- More virtual machine dalvik tweaks to speed things up
- Updated Apex Launcher to version 2.4.1
20140713 changes
- Rebuilt from CM11 4.4.4 Kitkat - CROMBi-kk source - maintained by lj50036!
- Fixed the settings - staus crashing
- Fixed the screen not shutting off when closing the lid when docked - thanks psudeke!
- Doubled the fling values for extra screen responsiveness
- Updated permissions to 4.4.4 CM11 set in updater script
- Updated the latest CM11 kernel to be init10 compatible for ROM2SD/DATA2SD/F2FS
- Added Hardslog's Grimlock kernel repacked for the TF700!
- Updated YouTube to version 5.7.41
- Updated Google Maps to version 8.1.1
- Updated Google Plus to version 4.4.3.69327528
- Updated Google Search to version 3.5.16
- Updated Google Music to version 5.6.1609P
- Updated Google Hangouts to version 2.1.311
- Updated Google Core Services to version 5.0.84
- Updated DropBox to version 2.4.2
- Updated Apex Launcher to version 2.4.0
- Updated Nova Launcher to version 3.0.1
- Updated Gravity Box to version 3.2.4
- Updated ESFileExplorer to version 3.1.8
20140617 changes
- Re-fixed writing big files to the sdcard failing
- Added option to install _thatv10 to internal for ROM2SD users
20140613 changes
REQUIREMENT for upgrade and ROM2SD - You must update your internal kernel to That v10 if you want to boot ROM2SD.
So you either need a 4.2 based rom like CROMi-X on internal with _thatv10 or 20140613 CROMBi-kk with either kernel on internal before going to ROM2SD.
- Recompiled from new base by lj50036 from 4.4.3 cm11 latest source!
- Updated _that's kernel to version 10 with new init10 binary and preinit scripts and auto file system detection
- Updated _that's cpu frequencies as easier to configure now - don't set them too low and complain!
- Dropped Hunds kernel support - sorry but I don't have the time or capability to get it working
- Updated cm11 kernel with _that init10 and f2fs functionality
- Removed Optimized Remounts from init.d again as already configured in fstab
- Fixed issues with fstab.cardhu not recognising f2fs properly
- Minor changes to kernel, cpu, vm and fs tweaks to help performance - see 50cleantweaks in init.d
- Updated Android Terminal Emulator to version 1.0.60
- Updated Google Play Services to version 4.4.52
- Updated Google Play Store to version 4.3.20
- Updated Google Talkback to version 3.5.1
- Updated Google Plus to version 4.4.1.68642489
- Updated Google Text-to-Speech to version 3.1.3.1162895
- Updated Google Mail to version 4.8
- Updated Google Music to version 5.5.1514O
- Updated Google Maps to version 8.1.0
- Updated Google Hangouts to version 2.1.224
- Updated YouTube to version 5.7.38
- Updated Xposed Framework to version 2.6.1
- Updated GravityBox to version 3.1.5
- Updated ESFile Explorer to version 3.1.6
- Removed the Teleservice.apk as causing FC in some cases
- CM11 stock browser is back to default - alternate browser still available but does not work with ART
- Added another 3 themes to Aroma Installer
- Major clean up of Aroma - manages partitions more intelligently
20140517 changes
- Rebuilt from new CM11 base 20140516
- Removed discard option from f2fs kernel init mount points
- Hopefuylly fixed restarts from notification bar
- Updated script for setting permissions and symlinks to latest CM11 version
- Updated Optimized remounts in init.d
- Updated zipalign script to a better version
- Reduced touch screen sensitivity by 60% as I think it was way too high before - missed touches
- Added an Alternate Stock Browser as an option that appears to work better than the CM11 one
--- Got to Browser settings, debug and Enable OpenGL Rendering, CPU Upload Path, Use Wide Viewport and Light Touch if not already
- Added more tweaks to sysctrl section of init.d script for extra smoothness
- Fixed Tasker crash and other apps that rely on google maps location data
- Fixed writing big files to the sdcard failing - thanks to fatboyinlycra for posting it
- Updated Titanium Backup to version 6.1.5.6
- Updated Gravity Box to version 3.1.2
- Updated Google Now Launcher (previously Google Experience Launcher) to version 1.0.16.1154249
- Updated Google Hangouts to version 2.1.100
- Added option to Aroma to install/remove Google stock live wallpapers
- Changed the way terminal emulator is installed as now built with rom from source
20140511 changes
- Fixed f2fs on internal and external not working with data2sd (bug in fstab and installer)
- Cleaned up installer script
- Added inverted blue CM Theme as it's rather pretty
- Updated Google Maps to version 8.0.0
- Updated Google Search / Now to version 3.4.16.1149292
- Updated YouTube to version 5.6.36
- Updated Apex Launcer to version 2.3.3
- Updated Titanium Backup to version 6.1.5.5
20140505 changes
- More fixes to f2fs installer routines and preinit scripts - added combinations of ext4 and f2fs
- All combinations are working now of data2sd/rom2sd + f2fs and ext4
20140503 changes
- Updated installer so data2sd and data2sd + f2fs are installed correctly
- Change the init mount point for f2fs to use the discard option on /data or datai
- Updated Xposed Framework to version 2.5.1
- Updated Gravity Box to version 3.1.0
- Updated Google Music to version 5.5.15110.1148372
20140501 changes
- Updated to new base compiled from latest CM11 source
- Kernel installer algorithm cleaned up to allow rom2sd, data2sd anf f2fs selection management
- Compiled static busybox for /system/boot which fixes preinit issues for data2sd and rom2sd - thanks _that for your help
- ROM2SD and DATA2SD now working with normal CROMBi-kk on internal!
- Updated 2 new animations (red and blue) from psudeke
- Updated Google Calendar to version 201404014
- Updated You Tube to version 5.6.35
- Updated Google Core Services to latest version
- Updated Google Plus to version 4.3.1.63038142
- Updated Google TTS to version 3.0.11
- Updated Hangouts to version 2.1.0
- Updated Apex Launcher to version 2.3.1
- Updated ESFileExplorer to version 3.1.3
- Updated DropBox to version 2.4.1
- Updated Dolphin Browser to verison 10.3.1
20140403 changes
- Added back missing calendar sync adapter
- Fixed bug in aroma where it exited if data2sd + f2fs setup was selected
20140402 changes
- New base from latest CM11 compiled by lj50036
- Updated the _that cm11 kernel to _that's v9 OC variant
- Added _thatv9 cm11 kernels for data2sd, f2fs and data2sd-f2fs into installer
- Added _that's CM11 Keyboard dock special keys fix if _that kernel is selected
- Added kernel tweak io_is_busy = 1 to improve touch responsiveness - thanks LuciusZen
- Added Res Changer to installer for extra speed : 3 RES available (1920x1200, 1600x1000, 1280x800)
- Increased the dalvikvm heap growth limit to 128MB to see if it stops out of memory errors for certain apps like news360
- Updated CROMBi-kk bootanimation to new one by psudeke
- Updated GApps to offcial CM11 20140105 based and then updated with latest play store versions including lib files
- Updated GApps installer to include Google Ears
- Updated Android Terminal Emulator to version 1.0.59
- Updated Dolphin Browser to version 10.3.0
- Updated Google Core Services to latest version
- Removed Optimized Remounts from init.d as no longer needed
20140322 changes
- Rebuilt from new base from lj50036
---Fixed Wifi Location Services
- Updated _that cm kernel to v9
- Updated data2sd kernel to _that v9
- Updated CM11 kernel to latest version
- Changed the ROM2SD script so that it copies wifi and bluetooth modules from the internal ROM
- Added a new bootanimation by psudeke
- Tidied up Aroma to make it easier to merge new builds
- Updated ES File Explorer to version 3.1.1
- Updated Dolphin Browser to version 10.2.8
- Updated GravityBox to version 3.0.0 KitKat Edition
- GApps now included in main installer
- Updated PlayStore to version 4.6.17
- Removed ROM provided calendar.apk and googlecalendarsyncadapter.apk
- Added latest Google Calendar as an option
- Added latest Google Music as an option
20140315 changes
- Rebuilt from new base from lj50036 - Includes dock fixes (java) from CM11 source
- Repacked _thatv8 kernel with updated init and init.cardhu.cpu.rc for better cpu mode support
- Repacked Hunds 3.4.5 kernel with LetMeKnow's Extreme Tweaks
- Fixed installer so hopefully users won't have an issue with addon.d scripts
- Fixed the CM11 backup and restore scripts not running as ro.cm.version was missing CM11
- Fixed : ROM2SD now correctly maps internal partitions to /datai, /systemi and /storage/sdcardi
-----ROM2SD still only works with a 4.2 JB ROM on internal
- Fixed : DATA2SD now offered again - currently uses _that v8 kernel
- Terminal Emulator lib file only installed when option is chosen in installer
- Added NTFS and extFAT support to stock based kernels
- Added Dolphin Browser and JetPack with FlashPlayer in installer as this is the only way to use flash in KitKat right now
- Updated Stock Browser Icon to Asus 4.3 version
- Updated Nova Launcher to version 2.3
- 20140315 GApps Package updated. See post 2 for changelog
20140314 changes
- Updated Adobe Flash version to hacked version to test with 4.4
- Updated Adaway to version 2.8.1
- Updated Terminal Emulator to version 1.0.58
- Build.prop edit to increase scroll sensitivity
ro.min.fling_velocity=30000
ro.max.fling_velocity=60000
20140312 changes
GApps Package updated. See post 2 for changelog
20140309 changes
- lj50036 has rebased the Rom from CM11 source. No more CMB reliance
- Repacked all 3 kernels so up to date with CM11 changes
- Added Cyanogen Stock Bootanimation as option
- Inverted calendar removed and replaced with stock Google one
- Split GPU rendering into 2 parts - Need to test differences:
Part 1 forces GPU Rendering for 2D operations in the build.prop
Part 2 forces software rendering to be disabled thus the GPU must be used
- Cleaned up updater-script as not using CM Backup / Restore functionality for now
- Added tweaked Browser.apk back in as well as media codecs and lib file for Terminal Emulator
20140308 changes
- Fixed Aroma script error meaning 95CleanTweaks not being given correct permissions to run as init.d
- Reset CPU profiles in the ramdisk so they mirror the ones we are used to from CROMi-X in terms of speed and fps limits
- That's kernel OCs to 1.8GHz with balanced at 1.5GHz and power saving at 1GHz
- lj50036's kernel OCs to 1.7GHz with balance at 1.5GHz and power saving at 1GHz
- Hunds's kernel OCs to 1.8GHz with balanced at 1.6GHz and power saving at 1.4GHz
- Attempted to fix issue with some users not being able to install to ROM2SD - but still broken if CROMBi-kk is on internal
- Updated media codecs from another CM11 build. Hopefully it'll fix dice and other video content
- Recompiled Browser.apk with speed tweaks as they got lost in a recent build
- If ROM2SD is chosen in installer then TWRP stays in ROM2SD mode until a reboot
- Gapps can be flashed to ROM2SD without needing the rom2sd1.zip if flashed straight after the rom installer
- Updated ES FIle Explorer to version 3.1.0.3
20140306 changes
- Updated GravityBox to version 2.9.8
- Final tidy up of ROM and scripts for release
20140305 changes
- Fixed the ROM2SD booting issues - thanks _that!
- New extract ramdisk script to solve the above
- Repacked the 2 CM11 kernels with thatv9 init binary which fixes empty last_kmsg issues
- Remixed Hunds 3.4.5 OC kernel with CM11 ramdisk - experimental not sure it works well
- Updated Titanium Backup to version 6.1.5.4
20140304 changes
- Added ROM2SD and DATA2SD scripting to installer
- Updated the stock CM11 kernel to include pre-init scripting - enables Data2sd & Rom2sd
- Updated Apex Launcher to version 2.30
- Removed CM11 _that kernel for now as wifi non functional due to missing modules during compilation
- Added script to upgrade build.prop from CROMBi-X to CROMBi-kk
20140303 changes
- Fixed Xposed not installing properly
- Added Asus _that kernel repacked with CM11 ramdisk and preinit compatibility
- Fixed missing modules from lj50036 & _that kernel
- Fixed Nexus Flow Bootanimation finishing too early
- Added phab7 as a test
- ROM name changed to CROMBi-kk
20140302 changes
- Built Aroma Script for main ROM installer
- Added new thatv8 kernel for CM11
- Updated dropbox to version 2.3.12.10
- Updated Terminal Emulator to version 1.0.57
20140301 changes
- Added Browser to RAM script
- Repacked Browser.apk with debug options on by default for speed - see labs options
- Added CleanTweaks init.d script from CROMi-X 5.4 as a test (need to analyse what is compatible)
- Build.Prop tweaks from CROMiX
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X ROMS)
@lj50036 - Source Guy (From CMB ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
Credits
Google, wow is all I can say!
CyanogenMod we wouldn't be doing this if if weren't for them (even if they are for profit now hah).
CMB for the basis of our Gapps package!
@nycbjr (CMB ROMS team leader) Thx for all the time teaching me the way (lj50036)!!!!
@_that For all the great advice, watching over us and fixing everything we break!!!!!
To Do
XDA:DevDB Information
CROMBi-kk, ROM for the Asus Transformer TF700
Contributors
sbdags, _that, lj50036, hardslog
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: JB 10.6.1.14.8 - 10.6.1.14.10 bootloader
Based On: CyanogenMod 11 AOSP
Version Information
Status: Stable
Current Stable Version: 20149021 R1
Stable Release Date: 2014-09-21
Current Beta Version: 20140906
Beta Release Date: 2014-04-03
Created 2014-03-06
Last Updated 2014-09-21
How to Upgrade and Downloads
UPGRADE INSTRUCTIONS
Steps
1. If you haven’t yet, unlock your TF700 by 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!
TWRP 2.6.3-that3 By that
lj50036 also made a flashable zip of _that's TWRP recovery Just flash from any recovery.
Flashable TWRP 2.6.3-that3 By that
CWM Touch XDA Thread
CWM XDA Thread
TWRP XDA Thread
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.
CROMBi-kk 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
CROMBi-kk 20140921 Full Mirror 1
CROMBi-kk 20140921 Full Mirror 2
MD5 Sum: f17e7fea8bbfa6e3cece080383149440
If you have any stability issues like freezing please use this patch:
CROMBi-kk R1 Patch Mirror 1
MD5 Sum: 7833f47410f1eea1b164bd48d982fc08
ALL 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, Asus Wallpapers, Asus Boot Animation, Polaris Offce, Asus MyCloud, TF701 Fonts and Sounds
[THREAD][APPS] [ASUS Apps][ CROMBi-kk & ZOMBi-kk]
GOOGLE APPS (GAPPS) DOWNLOAD - NO LONGER NEEDED!
GAPPS NOW INCLUDED AS OPTIONS IN MAIN ROM ZIP
Change Log
crombi_kkgapps_20140315
Updated YouTube to version 5.5.27
Updated Google Maps to version 7.7.0
Updated Google Search and Libs to version 3.3.11
crombi_kkgapps_20140312
Updated Google Calendarsync adapter to latest version
Fixed the issue of GApps not flashing if not done directly after ROM
crombi_kkgapps_20140309
Updated Google Bookmarksync adapter to latest version
crombi_kkgapps_20140308
If Gapps is flashed after CROMBi-kk it should now in ROM2SD mode - no ROM2SD1.zip required
Updated Google TTS to version 3.0.10.1047791
crombi_kkgapps_20140306
Removed calendarprovider.apk from gapps as conflicted with calendar app in rom
crombi_kkgapps_20140301
Updated updater-script
Updated Google Plus to version 4.3.0.62241793
Updated Google Core Services and lib files to latest version
Updated Google Experience Launcher to version 1.0.9
crombi_kkgapps_20140223
Updated Gmail2 to version 4.7.2
Updated Hangouts and lib files to version 2.0.303
Updated Google Maps to version 7.6.1
Updated YouTube to version 5.3.32
Updated Google Now and lib files to version 3.2.17.1009776arm
Updated Play Store to version 4.5.10
Removed Google Calendar as a version is already provided in rom
ROM2SD/DATA2SD USERS PLEASE READ!
ROM2SD only works if you have CROMBi-kk, CROMi-X or miniC flashed on internal with a THATv10+ kernel. Just choose ROM2SD in the installer of CROMBi-kk to flash it to ROM2SD and the installer will do the rest.
- Install CROMBi-kk 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 CROMBi-kk 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 CROMBi-kk but this time choose the ROM2SD / DATA2SD option
Reserved
BIG RED WARNING ABOUT PEOPLE WHO THINK THEY ARE MISSING ROOT!
You are not. The way CM11 works is root is not enabled by default after a clean install. Here is how you enable it.
1. Enable developer options by clicking the build number 7 times in settings - about tablet
2. Go to developer settings
3. In the first section click Root access and change to Apps and ADB
Enjoy your rooted rom
PLEASE SPREAD THE WORD
Q&A Fourm
[SIZE=+3]The Q&A thread has been created for Questions & Answers/Troubleshooting[/SIZE]
[SIZE=+3]Specific to
[ROM]★★★[KitKat 4.4.2][CROMBi-kk 20140316][DATA2SD | ROM2SD | CM11 Base][MAR 16]★★★
Click link here>>[email protected] Forum<<Click link here[/SIZE]
Mod edit: If your post has gone missing from this thread it has probably got moved to the Q&A thread(link above)(Have in mind that posts are sorted by chronological order, so they might not be in the last page). If you think it shouldn't have been moved then please sent a pm to @stamatis with a link of it. Thanks.
Nice, looking forward to it, this will be my first CM rom on this bad boy!!
You are all fantastic that made this possible. Wooow will gonna try this out for sure.
Just setting up uploads for post 2 - bear with me please
In case anyone wants to try it ... in the download section of this ROM you'll also find an unofficial pre-release of TWRP 2.7 compiled by me (2.6.3-that3) that supports both JB and KK ZIPs. I can't say anything about its quality, but the devs of this ROM have tested it. The GUI is much more fluid than in earlier versions.
Note: lj said that formatting data with this recovery takes a very long time (in the order of 1-2 hours) - be patient. It is not only formatting your data, it also trims unused blocks afterwards, and you know our internal storage is not the fastest... but the advantage is that in normal use it will then find enough empty flash blocks so writes will be faster.
Downloads are up - go crazy! :fingers-crossed:
Ok, installed it affer Wipe Data/Factory reset. Upon booting keep getting this message "Unfortunately, the process android.process.media has stopped". I dont have catlog installed yet, but what info do you need, I am assuming a logcat.
kbboykin said:
Ok, installed it affer Wipe Data/Factory reset. Upon booting keep getting this message "Unfortunately, the process android.process.media has stopped". I dont have catlog installed yet, but what info do you need, I am assuming a logcat.
Click to expand...
Click to collapse
Yes a logcat is what we need... If you have any quetions about pulling a logcat we can talk about that in the Q&A section for sure... Thx lj
If you would like to give the recovery in the download section a try that wold be great to.. Just read the FAQ in the Q&A section...
I unsuccessfully tried to install CROMBi-KK as ROM2SD.
Just the facts:
CROMi-X 5.4 on internal
TWRP 2.6.3.1
Flashed rom2sd1 and formatted /data on the external.
Rebooted to internal system
Rebooted into TWRP
Flashed CROMBi-KK as rom2sd with the modified _that v8 kernel.
Installation seemed to go ok - did not notice anything unusual (as in: it taking way long or finishing under a minute etc.)
Back to home in TWRP and flashed rom2sd1 as per instructions although I was wondering:
The Aroma installer changes the mount points so TWRP can flash to the external partitions, right? And the mount points get reset to normal when you reboot or flash rom2sd1 again, right? So if you flash gapps right after the rom flash - why flash rom2sd1? Wouldn't that change the mount points to the internal again????
Anyway, I flashed gapps after flashing rom2sd1 and it failed: Got a warning like: "This package is only for KK roms...." - so I kinda suspect I turned TWRP towards internal with that rom2sd1 flash.....
Ok, I thought, I'll flash gapps later. Rebooted system and got to the preinit script starting. Next thing is a blank screen - nothing happening for 10 minutes. No boot animation, no nothing.
Attached the tab to PC, tried to run a logcat in adb, but got no connection.
Long pressed power and took the card out when it rebooted to boot the internal.
Got to preinit starting, next is a blank screen - nothing happening at all.
TWRP log is attached
I would try it again with another kernel, but it's getting late. I'm leaving for a two week work trip tomorrow and will not take the TF700. The TF701 is going to get road tested ... and then unlocked - finally!
Maybe it's a fluke, maybe it's the card (although CM10.2 was running fine on it) - I'm sure you guys have it all worked out when I try the next time.
Exciting times again! Almost wrote: on this forum. But actually the different CROMi threads should have their own section - would save us a lot of back and forth! LOL
BTW, much fun with trying to separate Q&A and dev sections - this crowd is used to hang out in the CROMi threads and the community aspect of it should not be underestimated. I understand why you'd like to keep it separate, but I'm afraid the policing necessary to enforce it would change the "atmosphere" around here quite a bit.
Agreed mate. The policing will get tiresome but it will help whilst Dev is necessary.
So onto your problem with rom2sd.
I built the rom2sd1 zip script into the installer and call it twice once at the start so it installs to SD and again at the end to revert back to normal.
I didn't want the user left thinking one thing but the ROM forcing another.
But you just gave me an idea of how the gapps package can auto detect which one it should use
BTW, I flashed the rom2sd version many times and it does work. Pm me when you get up and I'll talk you through it.
berndblb said:
I unsuccessfully tried to install CROMBi-KK as ROM2SD.
Just the facts:
CROMi-X 5.4 on internal
TWRP 2.6.3.1
Flashed rom2sd1 and formatted /data on the external.
Rebooted to internal system
Rebooted into TWRP
Flashed CROMBi-KK as rom2sd with the modified _that v8 kernel.
Installation seemed to go ok - did not notice anything unusual (as in: it taking way long or finishing under a minute etc.)
Back to home in TWRP and flashed rom2sd1 as per instructions although I was wondering:
The Aroma installer changes the mount points so TWRP can flash to the external partitions, right? And the mount points get reset to normal when you reboot or flash rom2sd1 again, right? So if you flash gapps right after the rom flash - why flash rom2sd1? Wouldn't that change the mount points to the internal again????
Anyway, I flashed gapps after flashing rom2sd1 and it failed: Got a warning like: "This package is only for KK roms...." - so I kinda suspect I turned TWRP towards internal with that rom2sd1 flash.....
Ok, I thought, I'll flash gapps later. Rebooted system and got to the preinit script starting. Next thing is a blank screen - nothing happening for 10 minutes. No boot animation, no nothing.
Attached the tab to PC, tried to run a logcat in adb, but got no connection.
Long pressed power and took the card out when it rebooted to boot the internal.
Got to preinit starting, next is a blank screen - nothing happening at all.
TWRP log is attached
I would try it again with another kernel, but it's getting late. I'm leaving for a two week work trip tomorrow and will not take the TF700. The TF701 is going to get road tested ... and then unlocked - finally!
Maybe it's a fluke, maybe it's the card (although CM10.2 was running fine on it) - I'm sure you guys have it all worked out when I try the next time.
Exciting times again! Almost wrote: on this forum. But actually the different CROMi threads should have their own section - would save us a lot of back and forth! LOL
BTW, much fun with trying to separate Q&A and dev sections - this crowd is used to hang out in the CROMi threads and the community aspect of it should not be underestimated. I understand why you'd like to keep it separate, but I'm afraid the policing necessary to enforce it would change the "atmosphere" around here quite a bit.
Click to expand...
Click to collapse
berndblb said:
BTW, much fun with trying to separate Q&A and dev sections - this crowd is used to hang out in the CROMi threads and the community aspect of it should not be underestimated. I understand why you'd like to keep it separate, but I'm afraid the policing necessary to enforce it would change the "atmosphere" around here quite a bit.
Click to expand...
Click to collapse
All I know is its the way XDA would like it to be done... It would seem to me, as they have provided this very impressive platform for us to use....For free, I will do what I can to, help them reach there goals.... Thx lj:good:
berndblb said:
I unsuccessfully tried to install CROMBi-KK as ROM2SD.
Just the facts:
CROMi-X 5.4 on internal
TWRP 2.6.3.1
Flashed rom2sd1 and formatted /data on the external.
Rebooted to internal system
Rebooted into TWRP
Flashed CROMBi-KK as rom2sd with the modified _that v8 kernel.
Installation seemed to go ok - did not notice anything unusual (as in: it taking way long or finishing under a minute etc.)
Back to home in TWRP and flashed rom2sd1 as per instructions although I was wondering:
The Aroma installer changes the mount points so TWRP can flash to the external partitions, right? And the mount points get reset to normal when you reboot or flash rom2sd1 again, right? So if you flash gapps right after the rom flash - why flash rom2sd1? Wouldn't that change the mount points to the internal again????
Anyway, I flashed gapps after flashing rom2sd1 and it failed: Got a warning like: "This package is only for KK roms...." - so I kinda suspect I turned TWRP towards internal with that rom2sd1 flash.....
Ok, I thought, I'll flash gapps later. Rebooted system and got to the preinit script starting. Next thing is a blank screen - nothing happening for 10 minutes. No boot animation, no nothing.
Attached the tab to PC, tried to run a logcat in adb, but got no connection.
Long pressed power and took the card out when it rebooted to boot the internal.
Got to preinit starting, next is a blank screen - nothing happening at all.
TWRP log is attached
I would try it again with another kernel, but it's getting late. I'm leaving for a two week work trip tomorrow and will not take the TF700. The TF701 is going to get road tested ... and then unlocked - finally!
Maybe it's a fluke, maybe it's the card (although CM10.2 was running fine on it) - I'm sure you guys have it all worked out when I try the next time.
Exciting times again! Almost wrote: on this forum. But actually the different CROMi threads should have their own section - would save us a lot of back and forth! LOL
BTW, much fun with trying to separate Q&A and dev sections - this crowd is used to hang out in the CROMi threads and the community aspect of it should not be underestimated. I understand why you'd like to keep it separate, but I'm afraid the policing necessary to enforce it would change the "atmosphere" around here quite a bit.
Click to expand...
Click to collapse
Have flashed _that recovery, wiped top four options SD, flashed ROM2SD, rebooted recovery, flashed ROM2SD1, installed gapps, waited 20 minutes with boot animation. Not loading. Restored backup. All good. Think it's looping.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Essentrix said:
Have flashed _that recovery, wiped top four options SD, flashed ROM2SD, rebooted recovery, flashed ROM2SD1, installed gapps, waited 20 minutes with boot animation. Not loading. Restored backup. All good. Think it's looping.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Can you provide a logcat of the bootloop please. Search for how to do a logcat over adb if you are unsure. :good:
Essentrix said:
Have flashed _that recovery, wiped top four options SD, flashed ROM2SD, rebooted recovery, flashed ROM2SD1, installed gapps, waited 20 minutes with boot animation. Not loading. Restored backup. All good. Think it's looping.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Same thing happened to me. Although it flashed perfectly to internal.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Drewman294 said:
Same thing happened to me. Although it flashed perfectly to internal.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes for some people it seems the installer is not managing rom2sd properly. I'll have a look later.
All the people that had this problem can you
a) tell me the recovery you are using
b) provide the aroma log from the end of the ROM flash please.
Thank you!
What more can you tell us about TWRP 2.6.3-that3? Is this unique to installing your CROMBi-kk or can we use it on any Rom that installs on the TF700? So if I already have TWRP 2.6.3.1 installed, do I need to flash TWRP 2.6.3-that3 first or just press on with what is installed. Is there a thread or change log for TWRP 2.6.3-that3?
Thanks
nevertells2 said:
What more can you tell us about TWRP 2.6.3-that3? Is this unique to installing your CROMBi-kk or can we use it on any Rom that installs on the TF700? So if I already have TWRP 2.6.3.1 installed, do I need to flash TWRP 2.6.3-that3 first or just press on with what is installed. Is there a thread or change log for TWRP 2.6.3-that3?
Thanks
Click to expand...
Click to collapse
2.6.3.1 should be fine. That's is a fixed up version of 2.6.3.x or are 2.7 release I think. No changelog avail the moment but I know they implemented his fixes into official 2.7 which is coming soon I believe.
{
"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 10.6.1.14.10 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-20140824-zombi_tf700t-KANG source by lj50036/hardslog
Full Aroma Installer for main rom including choice of 3 kernels and ROM2SD/DATA2sd/F2FS support
Remixed _thatv10 kernel with OMNI ramdisk - repacked by sbdags
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
[*] Bluetooth is flakey - fixed
[*] Dock works as do most special keys - just no battery available in the system bar
Change Log
20141010 Beta 9 changes
- Rebased off latest source omni-4.4.4-20141008-zombi_tf700t-KANG updated by hardslog/lj50036 - omni windows much stabler
- Reduced NV Interposer log spam - thanks for the link BxMxK
- Fixed dock battery reporting with app/widget ! Thx @hardslog
- Rebuilt framework-res and settings apks with red theme
- Changed the Force GPU option to comply with build.prop source changes
- Added _that kernel v11
- Added Grimlock v4 kernel
- Added latest omni/cm11 kernel
- Fixed BT not turning on without rebooot
- 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 Chrome to version 37.0.2062.117
- 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 Google Maps to version 8.3.1
- Updated Google Search to version 3.6.14
- Updated YouTube to version 5.10.3.5
- Updated ESFileExplorer to version 3.2.1.2
- Updated Apex Launcher to version 2.6.0
- Updated AdAway to version 2.9.1
- Updated GravityBox to verison 3.4.3
- Note : Google Hangouts cannot be updated to latest version due to Google breaking apps packages with incompatible shared libraries. Going forward it will be a store app only
- Beta 8 not released
20140827 Beta 7 changes
- Fixed issues with Android Terminal Emulator crashing
- 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 + new installer script
- Dynamic fsync properly enabled on Grimlock kernel when fsync disabled selected in installer
20140825 Beta 6 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
- Removed Omni Stock Kernel for now as was causing root issues
20140825 Beta 5 changes
- Themed framework with a splash of RED
- Final Tweaks to Aroma Theme
- Public release beta
20140824 Beta 4 changes
- Rebased off latest source omni-4.4.4-20140824-zombi_tf700t-KANG updated by lj50036
- 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
20140823 Beta 3 changes
- Fixed installer script to allow rom2sd on grimlock kernel install
- Fixed aroma freezes - or reduced them
- Re-themed Zombi-X aroma theme
20140822 Beta 2 changes
- 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
20140822 changes
- 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 TF700
Contributors
sbdags, hardslog, lj50036, _that
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: JB 10.6.1.14.8 - 10.6.1.14.10 bootloader
Based On: OMNI AOSP
Version Information
Status: Beta
Current Beta Version: 20141010 Beta 10
Beta Release Date: 2014-08-25
Created 2014-08-25
Last Updated 2014-10-08
DOWNLOADS!
UPGRADE INSTRUCTIONS
Steps
1. If you haven’t yet, unlock your TF700 by 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!
TWRP 2.6.3-that3 By that
lj50036 also made a flashable zip of _that's TWRP recovery Just flash from any recovery.
Flashable TWRP 2.6.3-that3 By that
CWM Touch XDA Thread
CWM XDA Thread
TWRP XDA Thread
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-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 9 20141010 Full Mirror 1
ZOMBi-X Beta 9 20141010 Full Mirror 2
MD5 Sum: af7efdd0264cf2a98b8e7b0bdb2ba59d
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, Asus Wallpapers, Asus Boot Animation, Polaris Offce, Asus MyCloud, TF701 Fonts and Sounds
Asus Apps Thread LINK
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
IRC
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!
Both Download links are up! :good:
All Kernels included in this ROM package are unofficial, as they are complied from source, thay may not match the source that they were forked from. I will be linking the kernel source code as per the GNU GPL License.
Unofficial @_that Kernel Source CLICK ME @-V1.0
Official @_that's Kernel Source CLICK ME @-V11
Unofficial @hardslog Kernel Source CLICK ME@V4.0
Official @hardslog Kernel Source CLICK ME@V4.0
How does this compare performance wise to cm11? Is it mostly different features, or does one handle the io issues better? Thanks for continued work on this device!
Hi all,
I really want to test it out AND... i like the codename :good::highfive::silly:
Across how many Transformer Pad models is it / will be available ? TF700T for sure... TF300T ? TF701T ?
Huge thanks to the DEV team and congratulations for your very hard and unvaluable work,
All the best
ne0zone75 said:
Hi all,
I really want to test it out AND... i like the codename :good::highfive::silly:
Across how many Transformer Pad models is it / will be available ? TF700T for sure... TF300T ? TF701T ?
Huge thanks to the DEV team and congratulations for your very hard and unvaluable work,
All the best
Click to expand...
Click to collapse
TF300 is coming, and we hope to get it working for the TF701 as well. @lj50036 just has to work some more of his magic
ne0zone75 said:
Hi all,
I really want to test it out AND... i like the codename :good::highfive::silly:
Across how many Transformer Pad models is it / will be available ? TF700T for sure... TF300T ? TF701T ?
Huge thanks to the DEV team and congratulations for your very hard and unvaluable work,
All the best
Click to expand...
Click to collapse
For now it will most likely just be the 700 & 300 which will mostly work for the 201 on the hairybean bootloader ...
I am looking into the 701 and have started the port but there are some issue with the vendor blobs ..
One day at a time ...
Thx Josh
Just curious, but why create a new ROM from another base? Is OMNI better than CyanogenMod? If so, in what way?
Thx...Scott
ishamm said:
How does this compare performance wise to cm11? Is it mostly different features, or does one handle the io issues better? Thanks for continued work on this device!
Click to expand...
Click to collapse
zabolots said:
Just curious, but why create a new ROM from another base? Is OMNI better than CyanogenMod? If so, in what way?
Thx...Scott
Click to expand...
Click to collapse
IMO it runs faster and smoother But other s have a very good experience with CM11 as well. I would say it is no as stable as CM11 though - hence the BETA name. It is quite different as well - floating windows, etc.
Cool!
Hi,
Thanks for this ROM. I recall a discussion I had with a friend about OmniROM vs. Cyanogenmon (an idea with a simple google search...). First impression is that is really smoother in my opinion and I really like the toggle view in the performance in settings! So, clean install with f2fs internal, _that's kernel and usual settings from crombi-kk. just one question , will the profile chooser be available or I am too blind too find it?
Anyway, I am impressed of your work and wanted more to say thanks rather asking a question.
Regards.
sbdags said:
IMO it runs faster and smoother But other s have a very good experience with CM11 as well. I would say it is no as stable as CM11 though - hence the BETA name. It is quite different as well - floating windows, etc.
Click to expand...
Click to collapse
In for more reviews on this one, just updated to the latest crombi-kk and ROM2SD last night, runs pretty well, but will go to the ZOMBI if its snappier.
sziggins said:
Hi,
Thanks for this ROM. I recall a discussion I had with a friend about OmniROM vs. Cyanogenmon (an idea with a simple google search...). First impression is that is really smoother in my opinion and I really like the toggle view in the performance in settings! So, clean install with f2fs internal, _that's kernel and usual settings from crombi-kk. just one question , will the profile chooser be available or I am too blind too find it?
Anyway, I am impressed of your work and wanted more to say thanks rather asking a question.
Regards.
Click to expand...
Click to collapse
A question - couldn't find it in OP - if I am currently running Crombi-KK (Aug 10) with F2FS ROM2SD - do I need to do a clean install of Zombi or can I flash directly - same as an update to Crombi-KK?
Wanna give this new ROM a try and see if there is fact an improvement - my ROM2SD install of Crombi-KK works so well now - no glitches and runs like a champ.
Thanks to all the devs for their hard work!
toolmanz said:
A question - couldn't find it in OP - if I am currently running Crombi-KK (Aug 10) with F2FS ROM2SD - do I need to do a clean install of Zombi or can I flash directly - same as an update to Crombi-KK?
Wanna give this new ROM a try and see if there is fact an improvement - my ROM2SD install of Crombi-KK works so well now - no glitches and runs like a champ.
Thanks to all the devs for their hard work!
Click to expand...
Click to collapse
Hey, what options for tweaks do you use? Ive only done the disable fsync. Curious if the gpu ones or others work better. Im also doing browswer to sd
toolmanz said:
A question - couldn't find it in OP - if I am currently running Crombi-KK (Aug 10) with F2FS ROM2SD - do I need to do a clean install of Zombi or can I flash directly - same as an update to Crombi-KK?
Wanna give this new ROM a try and see if there is fact an improvement - my ROM2SD install of Crombi-KK works so well now - no glitches and runs like a champ.
Thanks to all the devs for their hard work!
Click to expand...
Click to collapse
I would highly recommend a full wipe as they use diff vendor blobs....
If you do dirty flash and have issues, you know what we are going to say to do...
So I leave it to you, but if you do find out things along the way let us know .. :highfive:
Thx Josh
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
big_sea said:
Hey, what options for tweaks do you use? Ive only done the disable fsync. Curious if the gpu ones or others work better. Im also doing browswer to sd
Click to expand...
Click to collapse
I use them all ...
I dont get a lot of time with one version of the rom or the other as there is some much testing that goes on...
I myself have not had any issue with any of the tweaks ...
Thx Josh
toolmanz said:
A question - couldn't find it in OP - if I am currently running Crombi-KK (Aug 10) with F2FS ROM2SD - do I need to do a clean install of Zombi or can I flash directly - same as an update to Crombi-KK?
Wanna give this new ROM a try and see if there is fact an improvement - my ROM2SD install of Crombi-KK works so well now - no glitches and runs like a champ.
Thanks to all the devs for their hard work!
Click to expand...
Click to collapse
Well as I wrote I did a clean install but in internal using f2fs. Latest TWRP, a factory reset and advanced format as I wasn't sure if DATA had f2fs format because of the twrp's bug of not showing it right. Using Titanium Back Up I restored the preferred app+data. But I see there is not adaptive backlight choice plus the profile for the cpu frequencies but overall for a beta I am really impressed. I suggest with a nandroid backup and TBU you should give it a try!
Good luck.
EDIT:
Clean installation for me is mandatory of not having issues when changing ROMs.. Josh was faster!
big_sea said:
Hey, what options for tweaks do you use? Ive only done the disable fsync. Curious if the gpu ones or others work better. Im also doing browswer to sd
Click to expand...
Click to collapse
Just like Josh I nuse them all including both GPU tweaks and pretty much all of the others (zip-align etc.)
The setup works flawlessly.
I will try a dirty-flash just to see what happens (I'm a masochist I guess and I may learn a few things and share with the community :sly: .
Ok so here's probably a dumb question. Im running ROM2SD now with the correct partitioning. If I want to clean install, how do I do the equivalent of "factory wipe" on the SD card? Previously I would just click factory wipe and then install the rom, im guessing now that its on SD i have to do something different...
Does this have a theme engine, to use an L based theme for example? Thanks