Related
I have just edited the AnyKernel updater script by koush to work with eMMC devices :-D
hope ppl can make use of this
its very simple
1) grab the attached .zip file
2) extract
3) add the zImage to the /kernel/ directory
4) add .ko modules to /system/lib/modules/ directory
5) **optional** change the boot partition location in the updater-script (not normaly needed)
6) zip up the file
7) its ready to flash in CWM
Credits
Koush for the original boot unpack / repack bin's and scripts
IEF for the stand alone dd binary
Apache14 said:
I have just edited the AnyKernel updater script by koush to work with eMMC devices :-D
hope ppl can make use of this
its very simple
1) grab the .tar.gz file
2) extract
3) add the zImage to the /kernel/ directory
4) add .ko modules to /system/lib/modules/ directory
5) **optional** change the boot partition location in the updater-script (not normaly needed)
6) zip up the file
7) its ready to flash in CWM
Credits
Koush for the original boot unpack / repack bin's and scripts
IEF for the stand alone dd binary
Click to expand...
Click to collapse
When you say grab the .tar.gz file, your referring to the file attached correct?
Just making sure I have everything clear before I use this.
Thanks! Great work!!
BAh yep thats a typo lol the .zip file
Apache14 said:
BAh yep thats a typo lol the .zip file
Click to expand...
Click to collapse
Thanks! I figured it was.
This ROM is custom build based on OTA update -> 1.57.415.3
Android version 2.3.5 - build (1.57.415.3)
Zipaligned
Busybox
Busybox scripts run-parts enabled
Zipalign
Updated kernel support for ext4 and swap
and full rooted su
Nothing removed or deleted (Application)
apps moved from system/app to data/app:
facebook
gmail
Maps
YouTube
talk
Apps added:
a2sd
Cube calculator
Android_Terminal
Thanks to
dsixda for Kitchen
Install all ROMs using clockworkmod recovery: (Install at own risk)
Download ROM
http://www.mediafire.com/?dbs7v9wf7zislxv
Same as Above but Sense UI and all dependent widgets removed and ADWLauncher added
http://www.mediafire.com/?si2s5828zjuisak
Awesome! Good job
hello,
can you explaint what does this Rom gives you?
1. full arabic menus?
2. support fo arabic keys?
thanks
stayfidz said:
1. full arabic menus?
2. support fo arabic keys?
Click to expand...
Click to collapse
Both full Arabic menu and Arabic keys support and any function that stock Rom support...
It is based on official Arabic Stock Rom.
thanks for the rom
I installed it but I don't know how to activate app2sd if you can show us it will be great
thanks again
Hello,
1. My chacha is rooted with an European RUU, can i reflash it with this rom?
2. Does this rom offer both menus, English and Arabic,or only arabic?
how to activate app2sd
ts3010 said:
thanks for the rom
I installed it but I don't know how to activate app2sd if you can show us it will be great
thanks again
Click to expand...
Click to collapse
Do you want to check??
- (root needed) Use the app Rootexplorer or ES File Explorer and browse to the places (/system/sd) if you see directories app, app-private and any-other directories a2sd is working. you can check which app has been moved to ext partition in app directory. If you do not see directories follow bellow steps.
I am not be held responsible for any lost data or turning your phone into a brick.
partitioning your SD card will format it and you will lose all data on the card. Please do yourself a favor and backup all contents of your SD card to your PC!
Typically it’s best to have a2sd setup before you flash a ROM
Back up all your data from the SD card to your PC
Clockwork -?creates ext3 partitions by default, if you are using latest ClockworkMod Recovery v5.0.2.8 port for the HTC Chacha by adlx.xda's, I believe it creates ext4 partitions by default & limited size choices. I believe the options are 512, 1024, 2048, respectively
Boot into recovery.
Main menu in recovery scroll down to advanced press the enter button.
Now in the advanced menu scroll down to the Partition SD card option and press the enter button
When asked for the ext size, I recommend using 512mb or 1GB. There can be stability issues going over 1.5GB
When asked for the swap size 0mb, 128mb or 250mb, its your choice if you want to use swap otherwise select 0mb. (This Rom support swap)
Time to flash ROM.
To view the help of a2sd you need to have terminal emulator for android, Evey time you run terminal emulator you will need to type this command “su” (without the ” ) hit enter this gives terminal super user access.
Type a2sd check and hit enter again, It will display the settings for apps, private apps, dalvik, swap, zipalign, & low memory killer settings, it will also display suggested commands for each parameter. You can also type a2sd help for a list of all supported commands. It is very easy to use.
If you had already installed Rom, you may need to issue this command in Terminal Emulator in order to enable it
a2sd reinstall
Moves all current and future non-system apps to the sd card & performs a full reboot
stayfidz said:
Hello,
1. My chacha is rooted with an European RUU, can i reflash it with this rom?
2. Does this rom offer both menus, English and Arabic,or only arabic?
Click to expand...
Click to collapse
Yes you can Flash
This ROM offer both menus, English and Arabic
Install all ROMs using clockworkmod recovery
Click to expand...
Click to collapse
1. so my next step is clockworkmod, then your flash?
2. where i can get the latest cwm?
thank you.
stayfidz said:
1. so my next step is clockworkmod, then your flash?
2. where i can get the latest cwm?
thank you.
Click to expand...
Click to collapse
latest CWM is by adlx.xda...
If any query regarding CWM installation instruction and using it follow these links..
http://forum.xda-developers.com/showthread.php?t=1481135
http://forum.xda-developers.com/showthread.php?t=1164468
How did you add ext4 and swap support to the kernel? I want to do that on an European ROM that i'm cooking, but it only supports ext2,ext3 and no swap (it's stock HTC kernel)
you will have to build a new kernel to support ext4 and swap.
just Google it how to build kernel for android..
I think it is only possible in Linux.
faizkalwar said:
you will have to build a new kernel to support ext4 and swap.
just Google it how to build kernel for android..
I think it is only possible in Linux.
Click to expand...
Click to collapse
Yes I know... but maybe you have patched HTC kernel sources for ChaCha, and added the code to support ext4 and swap... just want to know if I'm correct what patches you have applied.
absolutely correct.
faizkalwar said:
Do you want to check??
- (root needed) Use the app Rootexplorer or ES File Explorer and browse to the places (/system/sd) if you see directories app, app-private and any-other directories a2sd is working. you can check which app has been moved to ext partition in app directory. If you do not see directories follow bellow steps.
I am not be held responsible for any lost data or turning your phone into a brick.
partitioning your SD card will format it and you will lose all data on the card. Please do yourself a favor and backup all contents of your SD card to your PC!
Typically it’s best to have a2sd setup before you flash a ROM
Back up all your data from the SD card to your PC
Clockwork -?creates ext3 partitions by default, if you are using latest ClockworkMod Recovery v5.0.2.8 port for the HTC Chacha by adlx.xda's, I believe it creates ext4 partitions by default & limited size choices. I believe the options are 512, 1024, 2048, respectively
Boot into recovery.
Main menu in recovery scroll down to advanced press the enter button.
Now in the advanced menu scroll down to the Partition SD card option and press the enter button
When asked for the ext size, I recommend using 512mb or 1GB. There can be stability issues going over 1.5GB
When asked for the swap size 0mb, 128mb or 250mb, its your choice if you want to use swap otherwise select 0mb. (This Rom support swap)
Time to flash ROM.
To view the help of a2sd you need to have terminal emulator for android, Evey time you run terminal emulator you will need to type this command “su” (without the ” ) hit enter this gives terminal super user access.
Type a2sd check and hit enter again, It will display the settings for apps, private apps, dalvik, swap, zipalign, & low memory killer settings, it will also display suggested commands for each parameter. You can also type a2sd help for a list of all supported commands. It is very easy to use.
If you had already installed Rom, you may need to issue this command in Terminal Emulator in order to enable it
a2sd reinstall
Moves all current and future non-system apps to the sd card & performs a full reboot
Click to expand...
Click to collapse
A2SD can be confirmed by just using Titanium Backup.. Simplest Way..
can pls post a different mirror, i cant download from mediafire
does this ROM support Farsi/Persian characters too? many people are looking for Farsi/Persian support out there
tOz666 said:
Yes I know... but maybe you have patched HTC kernel sources for ChaCha, and added the code to support ext4 and swap... just want to know if I'm correct what patches you have applied.
Click to expand...
Click to collapse
See https://github.com/adumont/htc-kernel-msm7227/commit/877407bf1c32536e9059f03f642f7e6c3764a91f
What is the recommended microsd class speed if I want to use app2sd and move all my apps/apps data/dalvik cache to sdcard? I don't know what is the limitation of the implemented app2sd in this rom. For what I know app2sd+ does that.
Thanks.
Hello,
I am new to this cha cha business...
Just want to try out this rom and want to flash but do I have to go through all those cumbersome unlocking and rooting activity mentioned in the [Unlock ] Official Unlock via HTCdev!
Pls advice.
(Sorry for english !!)
!! Some problems with Android 5.1.x installed on External.
[Dual-Boot] I9305 [SCRIPT]
Hi. Because i dont find any kernel/script for I9305 with Dual-Boot, i try to make this script for test roms (but can be use day by day without problem).
This script help to patch .zip rom/kernel/gapps (and other i think) for install him on SDCARD. (without touch your internal rom).
How can you do this? Need to repartition your sdcard in 3 parts
1. With your sdcard data (files/music..etc)
2. external System (for system rom)
3. external Data (for data rom)
What you need to know !!!!
- Thanks on @Nicene Nerd for this App. I'm inspired from him.
- I'm not a developer.
- I don't now so much about linux (so, script not have a best optimization)
- This script is better good for people who test roms (like Lollipop).
- If you dont try this script, don't say anything. (only if you have some problem/stucks)
- Install on Internal roms like: Amcha / N4 / ..etc (big roms)..because i try to install on external rom and dosen't work
- Rom like Nameless / RR / ..etc can be install on external
- Anyone who want help me to make this script better, say here where need to edit (with what) and who can code help
- Say here what rom/kernel/script work or dosen't work to install on external. For modify script
What you need.
MiniTool Partition Wizard (or other program to repartition sdcard)
USB Cable (for repartition)
A phone (i9305 of course)
SDCARD 16gb (or more) Class 10 (if you have class 4 or other..your external rom run slow)
Backup your sdcard data (for safe)
Backup your phone (for safe)
ROM with root permision.
Water (because is good for your health)
First time you need to repartition sdcard
First partition: FAT32 (split memory from this..is good option)
Second: 1600 mb (1,6 gb) for system
Third: 2500 mb (2,5 gb) minimum memory for data
How can do this:
On MiniTool show your sdcard (like this)
{
"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"
}
1. Right click on him > Split
2. On New Partition Size you need to have minimum (system + data) 1600 + 2500 = 3600 mb (3,6 gb)..If you want more memory on data, you can type more than 3600 mb (i need more so i split 7000 mb)
After write your value, press ok
Now look like this
3. Right click on new partition (H on me) > Delete
Now you have unallocated partition
4. Right click on unallocated partiton > Create > Ok (on warning)
5. On box you need to edit:
Create As: Primary
File System: Ext4
Partition Size: 1600 (because is system partition)
After this. Press Ok
6. Right click on unallocated partition > Create > Ok (on warning)
Create As: Primary
File System: Ext4
Partition Size: dont modify
After this. Press Ok
7. Before press Apply, check if look like this
Now you can press Apply and wait
Good
After sdcard was partitioned, go to next step
Put my script on your SDCARD
(Why in sdcard? because internal/external rom view the sdcard everytime)
(internal/external rom have separated 'internal memory')
1. Unrar on desktop (right click on archive > extract here)
2. Copy 'db' folder to your sdcard
3. Check if 'db' folder is on your sdcard
4. With file explorer (i use Root Browser), go to db folder and install 'terminal.apk'
5. After install run him
On terminal:
Type: su (for superuser permision)
Type: cd /mnt/extSdCard/db (or anywhere is db folder location..on LolliPop is: cd extSdCard/db)
Type: sh db.sh
Now you are in script menu
Option: 1 -> Save Internal BOOT.IMG
Option: 2 -> Flash Internal BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 3 -> Mount Internal partitions on root direcotry (/.dbSystem & /.dbData)
Option: 4 -> Clean Internal partitions (use this if you are in External rom)
Option: 5 -> Save External BOOT.IMG
Option: 6 -> Flash External BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 7 -> Mount External partitions on root direcotry (/.dbSystem & /.dbData)
Option: 8 -> Clean External partitions (use this if you are in Internal rom)
Option: 9 -> Patch file for External rom (file like rom/gapps/pa-gapps/kernel..etc)
Option: 0 -> uMount /.dbSystem & /.dbData
Option: fb -> Flash manualy BOOT.IMG file
Option: ie/ei (hidden command) -> I'm work on this.. Is a experimental function. Don't use it
Patch files for external rom:
1. Copy on 'db' folder rom who want to patch, gapps archive and kernel your need
2. Run script on terminal
3. Need to save your Internal boot.img (Option 1 on menu)
4. Option 8 to clean your external partitions (if was used before with other rom).
5. Option 9 to patch
6. Type rom/gapps/kernel..etc archive name like: my_rom.zip > And press enter
7. Wait to patch (all patched files have pre name ext-
NOTE: If you patch rom/kernel (with boot files), you need to watch if script modify any fstab file. If no, external rom not work!
8. After you patch all you archive need..go to recovery (i use TWRP 2.8.5.0) and flash him but need to kep order:
- First ROM zip
- Second GAPPS (or PA-GAPPS) (or without this)
- Third KERNEL (if is need)
- .. other patched scripts
9. After flashing, reboot and wait to new external rom start up
(if you have any error (boot loop/other) you can flash internal boot stored in "sdcard/db/.db/.imgs/boot-int.zip")
10. After your external rom is ON, install 'terminal.apk' from sdcard
11. Run script on terminal
12. Save your External BOOT.IMG (Option 5)
13. Enjoy with your external rom.
(To switch rom you have option 2 and 6 or flash manualy .zip stored in "sdcard/db/.db/.imgs/boot-*.zip")
I forgot something?
Another explain: http://forum.xda-developers.com/showpost.php?p=59570171&postcount=11
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
Version 1.0:
+ It's alive !
thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?
LeoDeos said:
thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?
Click to expand...
Click to collapse
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion
il3gal said:
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion
Click to expand...
Click to collapse
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?
LeoDeos said:
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?
Click to expand...
Click to collapse
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?
il3gal said:
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?
Click to expand...
Click to collapse
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?
LeoDeos said:
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?
Click to expand...
Click to collapse
aaaaaa...no..
il3gal said:
aaaaaa...no..
Click to expand...
Click to collapse
ok thanks
LeoDeos said:
ok thanks
Click to expand...
Click to collapse
I make now how i use this script ..with images..
Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.
Explain 2
I made a tutorial how i use this script. Skip the repartition step because is easy (repartition need to make one time..not everytime want you install external rom)
On my rom (N4 Elite Lite v5).
1. Copy what files need to patch in db directory (where is script). In my case (pa_gapps-modular-pico-5.0.1-20150221-signed.zip & nameless-5.0.2-20150318-i9305.zip)
2. Run script.
3. First time need to save your internal boot.img (kernel). (for swich roms)
(because script modify kernel (mount point on kernel) and when you swich rom, all who make script is to flash kernel for internal/external rom)
4. After you save internal kernel, go back to menu and type option 9 to patch zip rom/gapps/kernel..etc
(if rom have a included kernel, watch if script find a fstab.* file and if can be edited. If not edited, external rom not work)
(all rom/kernel/gapps..other script need to modify updater-script or update-binary (pa-gapps use this)..if not edited, you cannot install rom on external partitions
5. After i patch rom file, i need and gapps because i use Google Play Store, so, i patch and gapps (go in menu, option 9 and type gapps file name)
(Now my db directory look like this)
6. All good. Now i want to be sure about my external partitions is clean, and i go to option 8 to clean him
7. After clean, reboot in recovery and flash ROM (ext-nameless-5.0.2-20150318-i9305.zip) and after GAPPS (ext-pa_gapps-modular-pico-5.0.1-20150221-signed.zip)
8. Reboot phone and wait to rom boot complete..(first boot may during a time)
(At Total Memory, is total memory allocated on 'data' partition (from repartition) (third partition))
9. After boot is complete..install 'terminal.apk' from db folder (script folder)
10. Run script from terminal.
11. Option 5 (for save this external boot.img)
12. Voila..now i have 2 separated roms..installed in 2 separate partitions (internal system/data and external system/data)
To swich i have 2 option. From terminal (script). (example) If i'm in internal rom and i want to swich, open script an type option 6..For flash external kernel and reboot phone to boot in external rom.
From recovery: flash manualy .zip files stored in sdcard/db/.db/.imgs/boot-*.zip
Now is good explication?
djb77 said:
Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.
Click to expand...
Click to collapse
Is not same. Do you know dual windows on pc?
Partiton C have Windows 7 (example)
and partition D have Windows 8.1 (for example)
If you boot pc, have a question "Who windows want to boot" 7 or 8.1..and you choose.
My script is same, but for 'choose', need to flash a kernel (external/internal..depend what you want to boot)
hmm.
This script is same with http://forum.xda-developers.com/showthread.php?t=2639112 ...but is not app..and dont have some options like "backup"..
Tested with:
ROM
- AICP 8.0
- Resurrection Remix® LP
- NamelessROM
- Cyanogenmod 12
- SlimLP
KERNEL
- Boeffla 3.0-alpha9
Changelog
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
I see some people was download script. Can give me feedback? (db_1.0.rar - [Click for QR Code] (1.11 MB, 32 views))
What rom is work and what not? (i dont have time to test all roms)
Abandoned.
il3gal said:
Abandoned.
Click to expand...
Click to collapse
why?
LeoDeos said:
why?
Click to expand...
Click to collapse
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this
il3gal said:
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this
Click to expand...
Click to collapse
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method
LeoDeos said:
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method
Click to expand...
Click to collapse
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.
il3gal said:
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.
Click to expand...
Click to collapse
thanks
+Tested with:
ROM
- AICP 9.0 (test version)
Changelog
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)
+Tested with:
ROM
- N4 Elite Lite v7 (but i don't now how much fast is) (when i have time, i will tested)
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Who know a universal reboot command for any rom? Because reboot not work on N4 Elite Lite rom
When I first installed KatKiss 6, I had to unpack and repack kernels in order to try out different combinations of zImage, ramdisk files, and modules. Many people may not want to go through the trouble, but there is an easier way to do that.
So, why do we want to try different combinations of zImage, ramdisk files, and modules? To see if performance is better could be an incentive, but the main reason is that sometimes a different combination of zImage, ramdisk files, and modules may fix things that are not working properly. For example, with cm kernel, GPS can't get good signals in the PAC ROM 5.1.1 I compiled. The problem is solved by using ramdisk of Cyanogenmod, and zImage and modules of Grimlock kernel 5.1.1.
Actually, @_that mentioned the two ways that can accomplish this back in January, but I went with the more complicated one because I had little knowledge of programming. I finally figured out how to do that the easier way recently.
The downside is that you must use a zImage supporting preinit in order to load ramdisk files that are not packed in the kernel. that kernel and Grimlock kernel both support preinit.
If you don't use kexecboot, zImage will always be from the kernel you installed for internal ROM. If it's a ROM2SD installation, the ramdisk files will be from the kernel you choose during ROM2SD installation. The modules are usually copied from internal during ROM2SD installation.
If you want to change zImage, then you have to flash a different kernel to /boot partition. If you want to change ramdisk file for ROM2SD installation, then you need to first delete the boot/ folder on the /system partition of the micro SD card. Then you can flash the kernel containing the ramdisk files between rom2sd1.zip and rom2sd2.zip following the method by @_that. Alternatively, you can also use the ones in this post. The differences are that the updated scripts from ZOMBi-POP will copy modules from internal /system, instead of using the ones packed by @_that.
If you want to use that kernel with KatKiss 6, you have to load ramdisk files from KatKernel to use with zImage of that kernel. To load different ramdisk files for a ROM installed on internal storage, you need to revise '20detect-microsd' file in internal /system/boot/preinit.d/ , which will copy ramdisk files from internal /system/boot/ramdisk to /. You can download the one I used, which is attached. The following lines are added to the original file.
Code:
else
# copy ramdisk files from internal /system/boot/ramdisk to /
$BB cp -a /system/boot/ramdisk/* / || echo "failed to copy ramdisk files from /system/boot/ramdisk"
You certainly need to extract the ramdisk files to internal /system/boot/ramdisk/ . To do that, you can use the attached extract ramdisk to internal system.zip. Just replace the 'boot.blob' inside with the one you'd like to use. Basically, it's the rom2sd2.zip from @_that, but without the scripts doing revision for ROM2SD.
At least for some ROMs, you can see performance gain with F2FS /cache. If you want to try to see if F2FS /cache works better for you. You can convert /cache to F2FS with TWRP 2.8.+. Just go to Wipe->Advanced Wipe, select Cache, and Change file system to F2FS. You also need to revise 'fstab.cardhu' in /system/boot/ramdisk/ for all the ROMs you are running. Just replacing the line for /cache with the following one
Code:
/dev/block/mmcblk0p2 /cache f2fs noatime,nosuid,nodev,errors=panic wait,encryptable=footer
Alternatively, you can use attached extract ramdisk to internal system f2fs cache .zip or rom2sd2 f2fs cache.zip when extracting the ramdisk files to internal or ROM2SD /system. The following line is added to 'extract-ramdisk.sh' so that 'fstab.cardhu' will be revised during extraction.
Code:
sed -i '/mmcblk0p2/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime,//;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' $f
I am able to use different zImages for internal and external ROMs and choose which one to boot with kexecboot. If someone is interested in how to set that up, please just ask in the comments.
There is a 'boot.blob' (I beleive it's for PAC511) in 'extract ramdisk to internal system f2fs cache .zip' You need to replace it with the one you'd like to use, or delete it and flash your kernel before flashing this zip.
This is only for the Micromax Unite 3 Q372 on stock ROM
Waiting is over!!! Hi, guys there are not many custom Roms or tweaks for the Unite 3 device as there are for its predecessor Unite 2. This made me to do extensive search and compile myself necessary tweaks to boost the device performance. As I believe I have made considerable progress on this, I dare to share them here with you. These tweaks have been devised after searching lot through the Internet, especially xda forum and modified to suite to Unite 3. Many of them are directly embedded in boot.img as they are related to boot.img or are required to be set during boot. Some are shipped in zip files for flashing through custom recovery (in second posting). Here are my works and explanation of what they feature and do.
A. Features of boot.img
1. Encryption disabled: It is found that encryption of data partition affects device performance. Apps on data partition don't open up quickly and on launching also their performance is not as good as sys apps due to encryption. Hence in the tweaked boot.img I have completely disabled the encryption which results in improved performance of user installed apps. Another added advantage of unencrypted data partition is that in recovery mode we can mount data partition which otherwise is not possible in any of the recovery images of unite 3. Further with this, it is also possible to take backup of data partition and restore it. However, for the data partition to be unencrypted, after porting the boot.img, you have to factory reset the device (in TWRP custom recovery, wipe -> swipe to factory reset) that wipe the data partition (take back up of data through Titanium app in case you want to restore later). This is one time job. After this, data partition would be unencrypted enabling mounting while in recovery.
2. Insecure adbd (root required): With insecured adb binary, while connected to the computer (of course ADB platform tools are to be installed on the computer) device's root shell can be directly entered by typing just 'adb shell' at the prompt.
Thanks: chainfire
3. init.d enabled (root required): init.d is enabled in boot.img. init.d scripts can simply be put in the /system/etc/init.d folder and tweak zips requiring init.d folder for running scripts at boot be flashed after entering recovery mode.
4. Disabled unnecessary daemon services: Some services which have been disabled are BTW, logd, PPLAgent, DMAgent, etc to improve upon battery as well as device performance.
5. swap partition on data partition: Tweaked boot.img creates swap partition on data partition. Swap virtually increases the ram of the device facilitating the apps to perform without glitches. Along with creation of swap partition, minfree values will also get changed. Modified minfree values allow apps to remain longer in ram without being killed in oom (out of memory) situations. As a result, apps quickly open if already launched. I have created three versions of boot.img. First one does not create swap partition while other two versions create swap partition of sizes 300mb and 500mb. Before porting the images that create swap partition, please ensure that required size of free space is available in data partition.
Thanks: Defiant07
6. Various kernel tweaks: Besides, there are many kernel, VM, entropy tweaks incorporated in boot.img. Thermal.off.conf file will be loaded so that device performance is not diminished on increase in device heat after prolonged working (against default settings of diminished performance in case of heat increase).
7. Selinux set to permissive: Selinux is set to permissive during boot. It is a prerequisite for some root apps for functioning.
Download links:
For no_swap_boot.img - http://www.mediafire.com/file/3zfw5dsp8kq1sk5/no_swap_boot.img
For with300mb_swap_boot.img - http://www.mediafire.com/file/8gj8drrvdmf694a/with300mb_swap_boot.img
For with500mb_swap_boot.img - http://www.mediafire.com/file/anjxeag2rcy58xc/with500mb_swap_boot.img
B. TWRP 3.0.2.0 recovery.img
TWRP img version 3.0.2.0 works perfectly except that it's image is upside down. You've to hold the device upside down while in recovery. That is not at all a problem. And all other features work perfectly. You can take back up, restore the back up, flash custom Roms and install zip files in the custom recovery.
Thanks: TWRP TEAM
Download link: http://www.mediafire.com/file/36332mlomcz9444/TWRP3.0.2-0_unite_3recovery.img
Method to flash boot and custom recovery images
Requirements:
1. Root the device (with KingRoot)
2. Install busybox
3. Install flashify app
You can flash boot and recovery images through flashify app (root required - root Unite 3 with KingRoot app) and busybox installed. However, the app does not readily work on Unite 3. You have to do a small adjustment of changing the order of contents of PATH variable before app becomes functional. For this, you require android Terminal Emulator app installed on the device. In the Terminal Emulator app, type at the prompt the following, PATH=/system/xbin:/system/bin, and press enter button. This sets the PATH variable to our requirement. Now we are ready for flashing (in flashify app). Place first the downloaded boot and recovery img files in internal or external memory and open up the flashify app, go for flash boot and recovery as the case may be and select the img file. Be careful to select boot.img file while flashing boot and recovery.img (TWRP recovery file) while flashing recovery. That's all :good:
Once again it is reiterated that after porting (flashing) boot.img, do a factory reset in recovery mode (after flashing TWRP custom recovery, reboot into recovery, select wipe and swipe for factory reset) for data partition to become unencrypted afterwards.
C. Zip files for installation:
All zip files are to be flashed after entering into recovery mode. First place zip files in internal or external SD card, reboot into recovery i.e., TWRP, press install button and select the zip file and swipe the swipe bar.
1. JournalingDisabler zip: Journaling is a security feature of ext4 file system. Journaling feature is a mechanism of writing in the journal first, then flushing the same on to memory device later. This is a precautionary measure against data loss on sudden shutting down or break down of system in real time scenarios. Journal features are not very much required on mobile phones. Journaling is with some performance overhead. Hence disabling feature results in considerable performance boost and battery saving.
An important note to bear in mind while installing this zip in custom recovery is first unmount system, data and cached partitions by unchecking these partitions in mount option in recovery mode. Then install.
Thanks: skynet28
2. Tools zip (tools.zip): This installs some binary tools which I feel essential for the device and replaces certain stock files with the tweaked ones. It installs SQLite binary compatible with Unite 3, zipalign binary for zipaligning apps (this zip will not zipalign apps, look elsewhere for script to zipalign your apps) and a small shell script to display the entropy level in terminal emulator (type 'entropy' at prompt in android terminal emulator and press enter. Maximum entropy level is 4096. Tweaked boot.img is tweaked to keep entropy level high). Further, it replaces stock build.prop with modified one with various performance properties, hosts file in /etc folder for ad blocking, hacked platform.xml to grant apps permission to write on external sd card, and tweaked settings.db in /data/data/com.android.providers.settings folder for unlocking hotspot. One more important thing is that this zip replaces stock linker binary with hacked one to obviate the problem of position independent executables faced while using some binaries.
3. Modded systemUI apk (SystemUIReplacer.zip): modded systemUI displays transparent status bar in place of dark background.
4. Hacked service.jar (servicejarReplacer.zip): This is the prized one. This hacked service.jar is attempted to modify all the things what famous Zeppelinrox's script does to ics and jellybean service.jar. minfrees values have been changed which among other things set adj value of launcher app to 0 so that there will not be any redraws of launcher app in case of oom (out of memory situations). Max Background cached apps limit has been increased to 70 from stock 32 and in addition, values have been modified in an attempt to increase lock in period of apps from stock 30 minutes to 24 hours provided apps are not killed for want of ram, but this is experimental. After replacing, you please tell me the results.
Thanks: zeppelinrox, and other untraceable developer
not working custom rom
shankar_vl said:
C. Zip files for installation:
All zip files are to be flashed after entering into recovery mode. First place zip files in internal or external SD card, reboot into recovery i.e., TWRP, press install button and select the zip file and swipe the swipe bar.
1. JournalingDisabler zip: Journaling is a security feature of ext4 file system. Journaling feature is a mechanism of writing in the journal first, then flushing the same on to memory device later. This is a precautionary measure against data loss on sudden shutting down or break down of system in real time scenarios. Journal features are not very much required on mobile phones. Journaling is with some performance overhead. Hence disabling feature results in considerable performance boost and battery saving.
An important note to bear in mind while installing this zip in custom recovery is first unmount system, data and cached partitions by unchecking these partitions in mount option in recovery mode. Then install.
Thanks: skynet28
2. Tools zip (tools.zip): This installs some binary tools which I feel essential for the device and replaces certain stock files with the tweaked ones. It installs SQLite binary compatible with Unite 3, zipalign binary for zipaligning apps (this zip will not zipalign apps, look elsewhere for script to zipalign your apps) and a small shell script to display the entropy level in terminal emulator (type 'entropy' at prompt in android terminal emulator and press enter. Maximum entropy level is 4096. Tweaked boot.img is tweaked to keep entropy level high). Further, it replaces stock build.prop with modified one with various performance properties, hosts file in /etc folder for ad blocking, hacked platform.xml to grant apps permission to write on external sd card, and tweaked settings.db in /data/data/com.android.providers.settings folder for unlocking hotspot. One more important thing is that this zip replaces stock linker binary with hacked one to obviate the problem of position independent executables faced while using some binaries.
3. Modded systemUI apk (SystemUIReplacer.zip): modded systemUI displays transparent status bar in place of dark background.
4. Hacked service.jar (servicejarReplacer.zip): This is the prized one. This hacked service.jar is attempted to modify all the things what famous Zeppelinrox's script does to ics and jellybean service.jar. minfrees values have been changed which among other things set adj value of launcher app to 0 so that there will not be any redraws of launcher app in case of oom (out of memory situations). Max Background cached apps limit has been increased to 70 from stock 32 and in addition, values have been modified in an attempt to increase lock in period of apps from stock 30 minutes to 24 hours provided apps are not killed for want of ram, but this is experimental. After replacing, you please tell me the results.
Thanks: zeppelinrox, and other untraceable developer
Click to expand...
Click to collapse
i successfully installed rom, but remix boot logo animation showing not booting properly,,
i need stable custom rom,
i tried all custom rom for q372, all get bootloop,,
if i port a rom , showing set_metadata_recursive error even i using latest TWRP 3.0.2.0
---------- Post added at 08:16 AM ---------- Previous post was at 08:12 AM ----------
All micromax q372 tweaking well which i trid:good::good::fingers-crossed::fingers-crossed:
Moded lollicraft 5.1.1 for q372 by me
:good::fingers-crossed:
Finally working custom rom for micromax unite 3, modded and tested my mee....
:good::fingers-crossed::good::fingers-crossed:
younsahamed said:
:good::fingers-crossed:
Finally working custom rom for micromax unite 3, modded and tested my mee....
:good::fingers-crossed::good::fingers-crossed:
Click to expand...
Click to collapse
What SoC Unite 3 has ?
Sudarshankakoty said:
What SoC Unite 3 has ?
Click to expand...
Click to collapse
MTK6582
hi sir my micromax unite3 q372 is in fully death conditions even the the usb are not connected with pc(charing port problem) so I'm now how to flash os on unite3. if any another method please reply me my email id is [email protected]
Decryption not happening
After installing tweaked.img we get twrp but no decryption of data
Can we have to flash boot.img to decrypt data and storage