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
GThrill ROM for JIAYU G3
The latest version GThrill ROM is based on "CM10" rom from needrom.com. I have applied some tweaks, removed some apps, added some and added option for the selection of EN (ph, us) language. The original purpose was for personal use, but I thought to share it, in case anyone wants to try.
DISCLAIMER
I SHALL NOT BE HELD LIABLE FOR ANYTHING THAT MAY HAPPEN.
SOME IMAGES/LOGOS/FILES/TWEAKS ARE NOT MY CREATION. THEY ARE OWNED AND CREATED BY THEIR RESPECTIVE OWNERS AND CREATORS.
THERE'S NO INTENTION WHATSOEVER TO INFRINGE ANY I.P. RIGHTS.
IF YOU FIND ANYTHING IN THIS POST THAT SHOULD NOT BE HERE, PLEASE LET ME KNOW. I'LL BE HAPPY TO DELETE THEM IF DEEMED VALID.
LIKEWISE, IF YOU FEEL THAT YOUR NAME NEED TO BE MENTIONED HERE, DO LET ME KNOW AS WELL, AND I'LL BE HONORED TO ADD IT.
USE AT YOUR OWN RISK!
Click to expand...
Click to collapse
{
"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"
}
Boot Splash/Logo and Boot Animation Video
- http://www.youtube.com/watch?v=T2d3PgAarA0
NOTES
This thread assumes that your JIAYU G3 is rooted and have a working recovery (CWMR/TWRP).
If your phone is not rooted, b1nary's rooting method works with G3, provided that you have working ADB driver and installed for for it.
Here's the link to b1nary's rooting method: Root MANY ANDROID!
Click to expand...
Click to collapse
GThrill Version 3.0
Features
- based "CM10" which I got from needrom.com post
- Jellybean 4.1.2
- system/framework zipaligned
- init.d support
- zipalign on the fly (script by Wes Garner)
- slim and light: removed unwanted apps
- host file (to block known ad servers/hosts)
- some build.prop tweaks from different sources
- contains some line from V6 supercharger script (by zeppelinrox, particularly kernel tweaks)
- Jellybean Keyboard (SWIPE feature)
- Google Chrome browser (bundled stock browser FCs)
- Language: English and Chinese (some other language can be selected from Settings but i'm not sure if they are completely translated)
Download
- http://d-h.st/xzo
Click to expand...
Click to collapse
GThrill Version 2.1
Features
- version 2.1 is just a maintenance release. it's basically the same as v2.0 with fix to reported Google Chrome issue
- if you are already using GThrill v2.0, no need to upgrade to 2.1, just install the fix for Google Chrome issue
Download
- http://d-h.st/huR
Click to expand...
Click to collapse
GThrill Version 2.0
Features
- based on LEWAOS for JIAYU G3 22.Feb release (http://bbs.lewaos.com)
- Jellybean 4.1.2
- system/framework zipaligned
- init.d support
- zipalign on the fly (script by Wes Garner)
- slim and light: removed unwanted apps (i.e. virus scanner, etc.)
- host file (to block known ad servers/hosts)
- some build.prop tweaks from different sources
- contains some line from V6 supercharger script (by zeppelinrox, particularly kernel tweaks)
- Jellybean Keyboard (SWIPE feature)
- Google Chrome browser (replaced chinese browser)
- Google splash logo, NEXUS Jellybean bootanimation
- Language: English (default), Chinese
Download
- http://d-h.st/JK2
Google Chrome Problem
- A reported problem when launching Google Chrome has been verified
- Here's the fix: http://d-h.st/AYQ
- This fix is to be applied via CWM/TWRP
Click to expand...
Click to collapse
Flashing instructions
As a safety precaution, always make a backup before flashing
1) Download the zip file and put in SD card
2) Boot to recovery mode (CWM, TWRP or Lewa Rec)
3) Flash the zip file you (from #1)
4) (optional, but highly recommended!) Do a factory reset
5) Reboot
6) Once you see the lock screen on first boot after the update, let it set for 1min (to fully settle the update)
7) Unlock and setup things (esp. if you did factory reset)
8) Restart
Click to expand...
Click to collapse
ClockWorkMod Recovery / TeamWin Recovery Project / LewaRec
CWM Recovery 6.0.1.5 for JIAYU G3
- I ported it from Acer Gallant E350 by erlucky to JIAYU G3
- USB mount and adb works
- unlike Lewa Recovery, this creates backup of boot and recovery images
Download
- CWMR_6.0.1.5_JiayuG3 (by ng0tkul4).zip
How to Update
- option 1: Flash via CWMR/TWRP
- option 2: for rooted phone without TWRP/CWMR, you can extract .img file from the zip file, and dd it to /dev/recovery
-
Click to expand...
Click to collapse
Lewa Recovery 2.0 for JIAYU G3
- English verion (translated/converted/moded by me)
- USB mount and adb works
- Original post: LeWa Recovery 2.0 English version
Download
- LewaRecovery2.0 (ENtranslated_by_ng0tkul4).zip
How to Update
- option 1: Flash via CWMR/TWRP
- option 2: for rooted phone without TWRP/CWMR, you can extract .img file from the zip file, and dd it to /dev/recovery
-
Click to expand...
Click to collapse
Boot/Splash Logos for JIAYU G3
DISCLAIMER
Logos, images and trademarks are copyright of their respective owners.
I take no credits for any of these. For personal use only. I just packaged them
as installable boot/splash logos for our G3! Use at your own risk.
Lamborghini
- download
- screenshot
The Punisher (1)
- download
- screenshot
The Punisher (2)
- download
- screenshot
White Google
- download
- screenshot
Colored Google
- download
- screenshot
If you want to go back to original JIAYU stock logo, here's stock boot logo
How to install
- Flash via CWM/TWRP recovery
Click to expand...
Click to collapse
Fonts for JIAYU G3
Each (flashable) zip file contains text file license specific to the font it carries, except for RoseMary and Storopia
(feel free to PM if you feel that those need not be included here). I was not ablt to take screenshots before I let go
of my G3, but I've tested all these fonts with G3
!PaulMal
ActionMan
Amaranth
Arimo
CabinSketch
Diavlo
Exo
Gapstown
Komika
Laconic
LuxiSans
Orbitron
SourceSans Pro
Ubuntu
VeggieBurger
RoseMary
Storopia
How to install
- Flash via CWM/TWRP recovery
Click to expand...
Click to collapse
Credits
Other credits/Special Thanks:
- LewaOS for the LewaOS and Lewa Recovery
- clockworkmod for the CWMR
- TeamWIN for the TWRP (Lewa Recovery)
- erlucky for CWMR 6.0.1.5 for Acer E350
- b1nary for his rooting method that works with G3
- ankadnikov/kadan for his LogoBuilder for MTK phones
- bgcngm/Bruno Martins for his MTK unpack/repack scripts
Click to expand...
Click to collapse
First of all tkank you for the development of this awsome rom. I don´t know if what I´m asking is possible, but why don´t you contact JDStar, who has developed another multilanguage lewa rom and ask him for permissions to add the tranaslations to your rom? This is the link to his rom:
http://forum.xda-developers.com/showthread.php?t=2162425
hugoglezp said:
First of all tkank you for the development of this awsome rom. I don´t know if what I´m asking is possible, but why don´t you contact JDStar, who has developed another multilanguage lewa rom and ask him for permissions to add the tranaslations to your rom? This is the link to his rom:
http://forum.xda-developers.com/showthread.php?t=2162425
Click to expand...
Click to collapse
Thanks for bringing this up. Will try to contact him when i get the time... or he can use this as the base.
Nice work bro, keeping our G3 updated :highfive:
added flashable logos
coming up shortly... fonts.
JDStar, has shared some translations for lewa rom 4.1, It would be great if you could make also flashable zips to add some languages. Here´s the link http://androidtranslator.etomaszow.eu/ . Thank you for your efforts and please keep up the good work!!! :good:
splash logo
First of all Thanks for the Roman. Can I know how to flash back the original jiayu splash logo. I would like to have jiayu logo. Thanks
kvpaul said:
First of all Thanks for the Roman. Can I know how to flash back the original jiayu splash logo. I would like to have jiayu logo. Thanks
Click to expand...
Click to collapse
i have uploaded the original/stock JIAYU splash logo
just flashed the Lewa Gthrill, tnx newbie
- LED indicator ok, BTW I noticed that ICS version has 3 Color indicator R-G-B
- wifi/ data/ GPS is ok
- nice music player w/ artist & lyrics (internet needed)
- stock lockscreen not sensitive, must touch a few times, changed to pattern seems ok
- Theme chooser always FC
- some apps, wechat, chikka, text. sometimes suddenly just close
- still testing the batt. life
- so far so good
with Nova Launcher
Netflix App
Thanks for uploading the stock splash logo. I like this rom, but what I am looking is to run netflix app. Netflix will work on ics but in none of the JB roms. Do you know how to make running the netflix app.?
Thanks
CMW recovery flashed but no go
Hi there,
I tried to get into the newly flashed CWMR but somehow I've failed. What I've done is use mobileuncle tools to get into CWM 5 and from there flash the zipfile I've downloaded from the sources. Now the CWM app does boot into recovery but I get this little android figure with a ! from it's belly. Not good I suppose.
I'd realy like to try out this rom but without working recovery I'm a bit scared I'm going to brick the thing....
Could you please advise??
Greetings,
Andreas
i use gthrill for a couple of days and the only problem i have is that when i open the wifi after some time the signal in one of my two sim drop....
i have it in all roms i try...
Installed last night.
Looks nice, work fine, stable. Well done
I have only one issue.
USB won't work.
When Jiayu is connected to PC, USB storage is not recognised. Any solution for this?
andreasheijdendael said:
Hi there,
I tried to get into the newly flashed CWMR but somehow I've failed. What I've done is use mobileuncle tools to get into CWM 5 and from there flash the zipfile I've downloaded from the sources. Now the CWM app does boot into recovery but I get this little android figure with a ! from it's belly. Not good I suppose.
I'd realy like to try out this rom but without working recovery I'm a bit scared I'm going to brick the thing....
Could you please advise??
Greetings,
Andreas
Click to expand...
Click to collapse
boot into normal Android and run MTKTools again and flash CWMR... this time, do it three (3) times in a row, before rebooting.
Hamacio said:
Installed last night.
Looks nice, work fine, stable. Well done
I have only one issue.
USB won't work.
When Jiayu is connected to PC, USB storage is not recognised. Any solution for this?
Click to expand...
Click to collapse
i'm not sure, may be you need correct drivers installed to your pc.
try using different USB port of your PC
ng0tkul4 said:
i'm not sure, may be you need correct drivers installed to your pc.
try using different USB port of your PC
Click to expand...
Click to collapse
Drivers are ok. Tried every single port. Worked fine 2 days ago - Jiayu was with ICS 4.0.4.
Not recognised as a mass storage.
dd rules!
ng0tkul4 said:
boot into normal Android and run MTKTools again and flash CWMR... this time, do it three (3) times in a row, before rebooting.
Click to expand...
Click to collapse
Didn't work. Got it working using the dd method (way easier if you ask me ).
Now, I've installed CWM 5.5.0.4 in /dev/recovery but when trying to flash the zip file for the LewaOS rom it gives me 'cannot open file'. Is that because I need the newer version of CWM mentioned in the opening post? Or just something else? Perhaps because there's 'spaces' in the filename? I'll let you know if I find something out there !
** Update **
I downloaded the correct rom but still no go It just doesn't want to install the rom...
Hamacio said:
Drivers are ok. Tried every single port. Worked fine 2 days ago - Jiayu was with ICS 4.0.4.
Not recognised as a mass storage.
Click to expand...
Click to collapse
Hi
Reflashed again.
Everything is fine.
I think is slower than original ICS 4.0.4 ROM, but stable and good.
Keep up good work!
***Update:***
Battery life much improved, at least 15-20%
I found this ROM very good so far.
There's only small issue with some mobile web sites. Some of the links cannot be open.
I've installed Opera browser in addition but is exactly the same so
I'm not sure: maybe there is a problem in ROM or badly written mobile web sites.
Thanks a lot
{
"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.
This is a Clockworkmod modified (very) recovery.
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
Update (21-apr-2015):
This is the last batch of builds for porting. I won't do that anymore.
- new GUI theme;
- an extra version with swipe touch support;
- cleaned up the source code;
- reset battery stats option;
- wipe all - preflash option;
- removed nvram backup/restore because it can corrupt the bootloader;
-full track of changes here.
I used it as base for my touch recovery. Basically is a CWM 6.0.3.7 for jellybean and CWM 6.0.5.1 for kitkat modified by me with many extra features.
- aroma file manager menu
- rainbow mode menu
- separate power menu
- separate wipe menu
- nvram backup/restore menu
- advanced backup/restore menu
- toggle signature, toggle md5sum.
To port it follow my new guide from here
All screenshots are made with my new tool from here.
For jellybean version currently there are two lunfile paths in the world of mtk phones. This will make your USB Mass storage to work in recovery or not. Search that path in your device to see what you have.
Lunfile path 1 (old): "/sys/devices/platform/mt_usb/gadget/lun%d/file" - this can be found in many devices mt6572, mt6589, mt6589T, and other old ones.
Lunfile path 2 (new): "/sys/devices/platform/mt_usb/musb-hdrc.0/gadget/lun%d/file" - this is related to new devices mt6582, mt6592...
Find where is your path and download the image to port from correct section.
Depending of your resolution width, choose an image which contains exactly that value or one close to it, and follow the tutorial to port it.
CREDITS:
- Philz-cwm6 - for get partition size method;
- C3C0 - for initial mtk tweack hint - Unused now;
- Koush and all CWM team for the recovery;
- bgcngm for unpack/repack utils;
- sk8erwitskil for aromafm menu
RULES for posting your ports!
If you managed to port this to your device, add proper credits in your thread, post or article.
List of compiled or ported recoveries for various devices.
Lenovo S660 (CN version S026)
THL T100S
THL T11
Elephone P7 mini
Bluboo X1 (mt6582)
Doogee Rainbow DG210
Kuphone 1phone 5s (sanstar72_wet_jb3)
iNew V3 for fw versions up to 1.0.7 (different kernel)
ONN M7 tablet
ZTE V967S
XOLO A500s
XOLO A600
ZOPO ZP999
LAVA Iris 458Q
Wiko Darkfull
Elephone P6000
Ulephone Be Pro
Acer Liquid Jade S (S56)
Acer Liquid Z410
Nvm. Got a black screen same with CTR recovery. Any help?
gatgat23 said:
Nvm. Got a black screen same with CTR recovery. Any help?
Click to expand...
Click to collapse
Usually that means the recovery is bigger than the recovery partition. It happens in some devices with an unusually big kernel (I saw kernels with 4.7 Mb for a recovery at 6 Mb - not much room for ramdisk). Other thing is if you use MobileUncleTools to flash it - this doesn't work in some cases, and you need to flash it with SPFT. Remember, if you have a small partition, any recovery bigger than 5.9 Mb (you need some reserved space) will not work. You can try to shrink some images, or to replace them with blank dummy pngs, but not for stitch and buttons. These have to remain in rgb format, otherwise you have that black screen again, and the phone will reboot to system.
carliv said:
Usually that means the recovery is bigger than the recovery partition. It happens in some devices with an unusually big kernel (I saw kernels with 4.7 Mb for a recovery at 6 Mb - not much room for ramdisk). Other thing is if you use MobileUncleTools to flash it - this doesn't work in some cases, and you need to flash it with SPFT. Remember, if you have a small partition, any recovery bigger than 5.9 Mb (you need some reserved space) will not work. You can try to shrink some images, or to replace them with blank dummy pngs, but not for stitch and buttons. These have to remain in rgb format, otherwise you have that black screen again, and the phone will reboot to system.
Click to expand...
Click to collapse
My device's recovery partition got 6MB. Ported recovery got 5.4MB.
I actually used MobileUncleTool to flash, then I tried to flash using SPFT.
Same issue, black screen. Need to reinsert battery to reboot.
gatgat23 said:
My device's recovery partition got 6MB. Ported recovery got 5.4MB.
I actually used MobileUncleTool to flash, then I tried to flash using SPFT.
Same issue, black screen. Need to reinsert battery to reboot.
Click to expand...
Click to collapse
Try to access the recovery log from temp directory (cache/recovery/last.log), after that happens. If there is nothing there, than the phone didn't even boot in recovery, otherwise you will see where it's stuck.
I think it actually didn't boot recovery.
Log's showing what I did when I was still on Stock Recovery. (Wipe data/cache)
Even the .prop values are using stock ones. (I changed adb secure, debuggable, etc in the one I ported.)
hello carliv,
is it possible to have a version 1.4 with custpack?
@carliv
Thanks for your activity.
Are this recovery compatible with most recent Mediatel ROM based on Android 4.4?
bovirus said:
@carliv
Thanks for your activity.
Are this recovery compatible with most recent Mediatel ROM based on Android 4.4?
Click to expand...
Click to collapse
All my recoveries are compiled on cm-10.1 building environment and in theory they will work better with kernels built for android 4.2 top (in these builds are missing sepolicy files and all selinux related files), but some users report that they used it for flashing and backup lenovo kitkat (vibeUI something) and it was successfull. I can't test that, but my advice is if you have an official Android 4.4 mtk powered phone, I'm sure the recovery partition is bigger than 6Mb, and for that I would recommend you PhilZ recovery if you want to stay on CWM base, or TWRP. I made my recoveries with only one reason in mind: to be small enough to fit a recovery partition of 6Mb.
Thanks for the explanation. What's about Androdi 4.3 compatibility? Like 4.4 ?
Recovery compatibility
Android 4.2.x - OK
Android 4.3.x - ?
Android 4.4.x - ?
Note: personally I like the non touch recovery.
Do you have a link for Philz recovery for Mediatek chipset?
Thanks again.
bovirus said:
Thanks for the explanation. What's about Androdi 4.3 compatibility? Like 4.4 ?
Recovery compatibility
Android 4.2.x - OK
Android 4.3.x - ?
Android 4.4.x - ?
Note: personally I like the non touch recovery.
Do you have a link for Philz recovery for Mediatek chipset?
Thanks again.
Click to expand...
Click to collapse
I think it should work in Android 4.3 but I have no feedback on it. The reason is there are very few mtk devices with Android 4.3 or 4.4 (real not spoofed), and I didn't tested personally any of them.
For PhilZ recovery you can check his official thread http://forum.xda-developers.com/showthread.php?t=2201860 , that support mtk devices nativelly, but you must compile it in cm-11 source,
or the mtk dedicated one started by my friend @yuweng here http://forum.xda-developers.com/showthread.php?t=2748169
The PhilZ recovery require many times a recovery partition bigger than 6MB.
In many acses teh recovery partition is limirted to 6MB.
For this if you can create your recovery from CW11 (compatible with KK) you can sue it.
bovirus said:
The PhilZ recovery require many times a recovery partition bigger than 6MB.
In many acses teh recovery partition is limirted to 6MB.
For this if you can create your recovery from CW11 (compatible with KK) you can sue it.
Click to expand...
Click to collapse
If a mtk phone gets Kitkat then I assure you the recovery and boot partition will be increased by producer in that firmware along with the new kernel. The 6Mb partition is specific to 4.1.x-4.2.2 devices. For these even my recovery, if it's built in CM11, will oversize 6 Mb because of the new modules.
gzip support
Thanks for this non-touch version! Can you update to include the gzip support as in the latest touch version? Thanks.
Hey Sir @carliv.
I ported this recovery to Xolo A500s.Please add it device list.
Here is the link:-Click here
port
Hi Sir ,
I ported it for my device XOLO A600
Please update it in device List .
Thanx Again
Here Is the Link
CWM Recovery MTK 6.0.3.7 carliv non-touch
Hi all!
I just combined some scripts to have a auto make custum recovery.
It is based on BM / michfood / yuweng / carliv work! Version 2014-06-29. See beginning of this thread.
Thank you!
usage: cwmr.bat stock-recovery.img
MTK6575 and MTK6577 tested. May work with MTK6589... (option 3 -> MTK6577)?
It is a question if fstab is matching. It is complete batch source, so you can adapt to alternate partition tabel.
Have fun!
EDIT:
What I did:
I took "old lunfile path" "normal font" file from carliv first thread, I extracted it and added to some old scripts from yuweng (I cannot find anymore to download). I tested it and made it public to all.
The latest CWM is 6.0.4.4 and Carliv release this update. Should be possible to aplly it?
Well, I am not sure about what I understand. You can use my upload and mod it any way you like. I hope to have helped to get latest CWM Recovery.
Hello guys, today i wanna share with you the Android M Bootanimation for the Samsung Galaxy S4.
First of all i have to mention the source where i took the Android M bootanimation >https://plus.google.comu/0/+DustinW...ts/MY9rvYJiNbj, the CyanogenMod team for their Bootanimation binary and VillainRom for his awesome VrTheme script that, with some adjustments, made possible to automatise a backup zip for the Stock Samsung Bootanimation.
SUPPORTED DEVICES
Note: the bootanimation has a 1440x2560 resolution, it may does not fit perfectly your screen!*Note 5Note 4 (All Variants)Note 2 - N7100Note 3S6 - G925S5S4 - i9505Galaxy J5If your device it's not in the list you can try it anyway, my zip automatically creates a flashable backup! if it worked write a feedback! Thank you very much!
DOWNLOAD AND VIDEO PREVIEW
New update! Support for KK and MM added!
[KK]SmartAndroidMBootanimation.zip
https://goo.gl/V76ule
[LL]SmartAndroidMBootanimation.zip
https://goo.gl/r0ZLVn
[MM]SmartAndroidMBootanimation.zip
https://goo.gl/7Hs4o4
INSTALLATION GUIDE
To install it you need a recovery, i suggest you TWRP but other recoveries should go fine too. Should i write the steps? Ok, download the zip and flash it...DONE!*
Note: after the flash a backup zip will be created inside /sdcard/vrtheme-backup/
USEFUL ZIPS
-Do you wanna revert to the original bootanimation binary restoring the Stock Bootanimation? > Flash the autogenerated zip in /sdcard/vrtheme-backup/StockBootanimationRestorer.zip
-Do you wanna totally remove the Shutdown animation? >*ShutdownAnimation Remover* https://goo.gl/MCrekq ( Note: this zip just deletes the ShutdownAnimation.qmg file)
SUPPORT
Did you like my work? Support me via pressing the*button or even sharing your feedback! Have a nice day!