Related
Copied From ChainFire's Post
Click to expand...
Click to collapse
This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and ClockWorkMod (CWM4/5) recovery. For Galaxy Fit You Need To Flash Clockwork Mod Separately. The Kernel is Custom Supporting Ext4 FS, OC, UV and other Features
THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THIS ENTIRE POST!
Donate
Please Donate to Chainfire or Press Thanks button Here
Click to expand...
Click to collapse
There have now been nearly 1.000.000 downloads of CF-Root for various devices (see for example Galaxy S1, Galaxy Tab 7", and Galaxy S2), and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user had donated me $1...
Features
- Root
- Busybox v1.16.2androidminimal (from CWM)
- Integrated CWM 4.0.0.2
- Integrated Tweaks Manager
- Running All Scripts in /system/etc/init.d
- Custom Bootanimation Workin on All Roms
CF-Root v4.1 and older
- Superuser 2.3.6.1
- In-Secure mode
Instructions - CWM
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Flash CWM Recovery.
- Download the File To Your Sd-Card
- Flash via CWM Recovery
- No Need to Data Wipe
- Initial/First Boot May Take Long Time,Very Long Maybe .
Other kernels
Replacing CF-Root with other kernels and vice-versa sometimes works, sometimes it doesn't. I don't have a list.
When going from CF-Root to another kernel, root will usually stay, while CWM will be lost (unless the other kernel also includes it), but there should not be issues. The CWM Manager app may remain, but probably won't do anything useful. For Galaxy Fit CWM Recovery Wont Go Flashing Other Kernels
CF-Root/CWM4 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly or using the CWM Manager application included with CF-Root
- ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery.
- When connected to ADB in recovery, you need to use "rootsh" command to get root, instead of "su". This will not prompt you, it will just give you root. Obviously the "rootsh" command does not work when booted normally.
CWM Manager
Because of incompatibility with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011). You can find it under Applications -> CWM. It is much faster to use than manually booting into CWM and selecting these options.
Features:
- Boot to CWM
- Backup firmware
- Restore backups (CF-Root v5.0: including partition selection)
- Delete backups
- Install APKs
- Flash CWM3/4/5 update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP) - without changing warning triangle status or increasing flash counter
--- without changing warning triangle status or increasing flash counter
- CF-Root v5.0: Flash complete firmwares (seperate files as well as .tar and .tar.md5 archives, dump files in /sdcard/external_sd/firmware folder)
--- without changing warning triangle status or increasing flash counter
--- can pre-root new firmwares during flash
Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility !
Custom boot / init scripts
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use #!)
- /system/bin/customboot.sh (busybox sh)
- /system/xbin/customboot.sh (busybox sh)
- /data/local/customboot.sh (busybox sh)
Please make sure you chown / chmod the scripts correctly so they can be executed. Pretty much root:root / 755.
Custom boot animations and binaries
CF-Root also supports custom boot animations:
- /system/media/bootanimation.zip
- /data/local/bootanimation.zip
And custom boot binaries:
- /data/local/bootanimation.bin
Installing busybox over the included version
It is possible to install a custom busybox over CF-Root v3.0 and newer. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. Took me a few days to get it to this state. If this works right, however, next time it will probably take me a few hours tops
Downloads (Will Work On Every GB Rom Formatted to Ext4 Partition)
Initial Release-http://www.mediafire.com/?y8242yhozcgvok6 (Flash via CWM Recovery)
Credits
-Chainfire (Please Donate Him or Press Thanks)
-Special Thanks To Ketut.Kumajaya
-zcop
What is that supposed to mean?
Sent from my GT-S5670 using XDA
Great Job Mr. Creed
CF Root kernel is very popular, now come to FIT device ^^
Congratulatioonnn
Hehe im a noob and i dont get it ... This will work on custom and stock roms or only on custom with ext4 support?
Sent from my GT-S5670L using xda premium
Can't you guys read its all described in the op
Sent from my GT-S5670 using xda premium
Mr.Oug said:
Can't you guys read its all described in the op
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
I read it ... But creed put something that made me confuse ... He put will work on every gb ext4 partition ... And the original post says its for stock ... So u tell me works on both or just in ext4 partition gb?
Sent from my GT-S5670L using xda premium
Deshabilitado said:
I read it ... But creed put something that made me confuse ... He put will work on every gb ext4 partition ... And the original post says its for stock ... So u tell me works on both or just in ext4 partition gb?
Sent from my GT-S5670L using xda premium
Click to expand...
Click to collapse
nt stock for us , because our stock kernel dosnt support ext4 ,which is required by the CWM,CWM app and tweaks manager !!! i will soon add a way to make stock roms cf-root and cwm supported !!
I add this one nice job Thanks. it works nice
Sent from my GT-S5670 using xda premium
pratyush.creed said:
nt stock for us , because our stock kernel dosnt support ext4 ,which is required by the CWM,CWM app and tweaks manager !!! i will soon add a way to make stock roms cf-root and cwm supported !!
Click to expand...
Click to collapse
that would be nice, thanks Creed
Jus tell guys if the bootanim is working/
I hope u do something to make stock kernel ext4 support and that way use this
Sent from my GT-S5670L using xda premium
Deshabilitado said:
I hope u do something to make stock kernel ext4 support and that way use this
Sent from my GT-S5670L using xda premium
Click to expand...
Click to collapse
if i mod the stock kernel to add ext4 support it will be called custom kernel, kernels cant be modified they cn be built only !!
Thanks waiting for it...
pratyush.creed said:
if i mod the stock kernel to add ext4 support it will be called custom kernel, kernels cant be modified they cn be built only !!
Click to expand...
Click to collapse
What kernel base for is it?
for CM?
I think it works on Rom using ext4 fstype.
If there ppl.using stock.
Just format em to ext4, and flash a kernel.
Kernel base CM can be used on GB ROM (not CM), too.
I jst share my opinion n my experiences
Sent from my GT-S5660 using Tapatalk
Delanoister said:
What kernel base for is it?
for CM?
I think it works on Rom using ext4 fstype.
If there ppl.using stock.
Just format em to ext4, and flash a kernel.
Kernel base CM can be used on GB ROM (not CM), too.
I jst share my opinion n my experiences
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
not fr CM.
i usd chainfire's Ext4 convert app bt it didnt workd, i will try with cwm flashable scripts...do u have one ??
Just Refreshed this Cf-root ..
*Removed that Boot Splash of Creed(i forgot to remove it before )
*New Kernel
*OC upto 870Mhz
*New Shedulers
I havnt tested it, cuz my phone has gone for repairing ...
someone pls test if this is stable or not..so that i can add this to the main thread!!
Flash via CWM ...working on all roms
pratyush.creed said:
Just Refreshed this Cf-root ..
*Removed that Boot Splash of Creed(i forgot to remove it before )
*New Kernel
*OC upto 870Mhz
*New Shedulers
I havnt tested it, cuz my phone has gone for repairing ...
someone pls test if this is stable or not..so that i can add this to the main thread!!
Flash via CWM ...working on all roms
Click to expand...
Click to collapse
870 Is it a good idea.... o_0
Hi everybody, I'm searching how to multiboot CM9 (KISADWORKS 2.0) with MIUI V4 ? I have already kisadworks 2.0.
Thanks for your answers
Steps for Multi boot:
1) Flash Kernel v1.7+
2) Go to CWM Recovery -> Multiboot -> Backup ROM.
3) Backup your Current ROM to ROM1 (It will backup the system.img at /sdcard/Android/data/g3mod/roms/romname_ROM )
4) Add the system.img of your 2nd ROM to /sdcard/Android/data/g3mod/roms/romname_ROM and similarly for different ROM's.
5) Use the CWM Recovery -> Multiboot -> Switch ROM option to switch between different ROM's.
6) If switching between Froyo ROM and CM6.2 RoM, you will need to wipe data and also change kernel's via update.zip method.
7) Use the data backup and restore option to prevent loss of data when switching between Froyo and CM6.2 ROM's.
Note: Ask the developer of the ROM's to provide you with the system.img for their ROM
http://forum.xda-developers.com/showpost.php?p=17344541&postcount=6
Thanks but does it work with any of android versions ? I mean with 4.0.3 too ?
Newest G3Mod 2.5 should work.
EDIT:
It does. Check this -
Kernel Changelog:
v2.5 (15/05/2012
Supports CM7a8.1
Supports ICS (if colours are screwy, update OpenFIMG)
CWM5 with touch
General source code fixes
[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
Stock Rom Tweaked
Modded and Tweaked by @nrupesh2912
First ever Flashable Stock ROM For A200
Features:
-Android 4.2.2
-Rooted
-Zipaligned
-Deodexed
-Removed Unwanted Apps
-Init.d Support
-Few Build.prop tweaks
-Wifi Tweaks
-Faster Streaming Tweaks
-3G Tweaks
-More Free Ram Tweaks
-Signal Tweaks
-Bravia engine V3
-Xloud and Beats
-All stock A200 Features
And Much More....
DOWNLOAD LINK
Steps:
1) Download ROM
2) Put into external/internal sd card
3) Go to CWM recovery
4) Take backup
5) Wipe data/factory reset
6) From advance menu do dalvik cache clear
7) Go in mount and storage select format system
8) Select install from SD card and flash rom
9) Wipe data/factory reset again & Reboot!!
Bugs:
No Bugs
Tell me If u find any
Credits:
Micromax For A200 Canvas Turbo Mini
@nrupesh2912 (MEEE) : For this rom :laugh:
@maheshmaf : For testing this rom (I dont have this device so was not possible without him) :good:
Kernel : Used Untouched Stock Kernel
Note :
I Will Not Be Responsible For Any Bricked Devices or Any Problem So Flash At Your Own Risk.
ScreenShots
Thanks to @maheshmaf
Reserved
nrupesh2912 said:
Stock Rom Tweaked
Modded and Tweaked by @nrupesh2912
First ever Flashable Stock ROM For A200
Features:
-Android 4.2.2
-Rooted
-Zipaligned
-Deodexed
-Removed Unwanted Apps
-Init.d Support
-Few Build.prop tweaks
-Wifi Tweaks
-Faster Streaming Tweaks
-3G Tweaks
-More Free Ram Tweaks
-Signal Tweaks
-Bravia engine V3
-Xloud and Beats
-All stock A200 Features
And Much More....
DOWNLOAD LINK
Steps:
1) Download ROM
2) Put into external/internal sd card
3) Go to CWM recovery
4) Take backup
5) Wipe data/factory reset
6) From advance menu do dalvik cache clear
7) Go in mount and storage select format system
8) Select install from SD card and flash rom
9) Wipe data/factory reset again & Reboot!!
Bugs:
No Bugs
Tell me If u find any
Credits:
Micromax For A200 Canvas Turbo Mini
@nrupesh2912 (MEEE) : For this rom :laugh:
@maheshmaf : For testing this rom (I dont have this device so was not possible without him) :good:
Kernel : Used Untouched Stock Kernel
Note :
I Will Not Be Responsible For Any Bricked Devices or Any Problem So Flash At Your Own Risk.
Click to expand...
Click to collapse
i just this moment installed this rom on my blu life play s L150u the installation went well as i followed all instructions. now it starts and show the boot logo, then boot animation, then nothing it freezes what can i do? wioed cache, format system, wipe divak reset and wipe ...still the same.
bugs ??
is this rom work well ??
Want Scatter file for Turbo Mini
I have 6582 scatter file which i used for A 120 but it isnt working when i used this scatter with recovery it aays PMT changed
Sent from my Micromax A120 using XDA Free mobile app
For tested and supported ROMs see post#2
As most of us may know from past @croniccorey's int2ext scripts have been the de facto standard for internal memory scripts (for mounting /sd-ext as /data) and also that the zips are notorious for throwing "error executing updater binary" errors for almost everyone. One specific problem i encountered while using @kirmaniarslan's unofficial CM 11 weekly build that when i flashed an ART Optimised version of the script it used to show internal memory full issues at 120~128MB usage but in the storage menu in settings it showed more than a gig free (my sdext measured 1.5 gigs). This hurt a bit since i had been enjoying the awesome (and aw3som3[emoji14]) ROM a lot. So I rigged together a modded version of the script to try and get rid of the error. the attached zip is a direct result of that effort. Try it out on other roms as well if you faced the same problem as me and report in the thread.
Instructions for flashing
INIT.D support is REQUIRED!!!!
It is recommended that you flash this over a clean ROM flash or after removing existing scripts and cleaning up cache and dalvik cache
Flash it using recovery mode no need to wipe data
ensure you have created an sd ext partition before using the script
done enjoy!!!
Download Link for flashable zip : http://d-h.st/ddxG
Supported ROMs
1. CM 11 Weekly Builds by @kirmaniarslan
2. Omni ROM by @thewisenerd
3. Carbon ROM KK by @7alvi
4. Evervolv BETA1 by @thewisenerd
5. PAC ROM Port by @MSF Jarvis
6. Omni ROM by @thewisenerd
7. SlimBean by @7alvi
8. ParanoidAndroid Beta 3 by @thewisenerd
More to be tested and added soon...
For those for whom INT2EXT doesn't work properly, use Mounts2SD from here : [URL=" http://forum.xda-developers.com/showthread.php?t=3162148" ]MOUNTS2SD App Tutorial[/URL]
Sent from my HTC Desire 616 dual sim using Tapatalk
Thread closed at OP's request.