Database Develop

[ROM] CyanogenMod 6.1 V1 - CWM - 23-04

Hi every one! I give you another good build. It repark from CM Modded Build V.2 by needo, and work with ClockworkMod, so here is the build:
I. Download needed file:
1. CyanogenMod 6.1 V1 - CWM - 23-04.zip
http://www.multiupload.com/QQF81OD7IE
2. npkboot-cwm-v15-x1-monsterKernel.rar
http://www.multiupload.com/R4A7PJE00T
II. before install :
1. Format your sdcard make 4 Partition with recommended size:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / about 150MB -> depends on the build )
3rd partition: EXT2 (data / about 250MB)
4th partition: EXT2 (cache / about 50MB)
Be sure make all 4 partition primary
2. extract and copy folder npkboot to root of sdcard.
3. Copy Rom ( zip file , don't extract) in to root of sdcard.
III. Install:
1. run Haret, and wait when it will be asked to press "Volume Down" shortly (!!important!! shortly) to launch ClockworkMod Recovery or any other key to usually continue booting into Android.
Press volume Down and wait for menu Recovery.
2. In menu recovery choose "install zip from sd-card" choose zip from sdcard and select "CyanogenMod 6.1 V1 - CWM - 23-04.zip" . Confirm instalation then reboot system.
4. Run HARET again and press any key (except Volume keys) to continue booting into Android.
Tips:
First boot :
*Settings > CyanogenMod Settings > User interface > tweaks extra > load theme > choose CM 6.1 white
- This will change the status bar text colour to white ...
*Launcher settings > change theme > choose the gre theme ...
*disable data transfer
*disable auto-rotate screen
- Android won't performing very well at first running hours, if you have many media files (pic,videos..) .. system will be busy searching for these files & creating thumbnails for them ... the time for that is depending on the quantity of the media on the SD card ..
UPDATE:
- If you can't boot to android, try change modules to Turbo kernel and reinstall.
- If you want stop problem key freeze, download kernel with keyboard as modules and follow this link http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2 how to do ^^!
- For better batterry, download and install SetCPU, then custom it yourself !
- For better speed install ADW Laucher ^^!
Thanks to Neopeek, needo and other developers !

I have done:
- Everything copied to SD following the how to.
- [2011-04-18] FRX06 [CWM] worked, but this rom doesn't work
- Formated ext2 partitions to erease the old rom.
- Using Duckly's Kernel [Turbo Kernel] WITH KEYPAD DRIVERS AS MODULES
Problem:
I can run haret but when I have to click vol down it doesn't launch the recovery mode. it wants to continue.
With the FRX06 it worked but now it doesn't work
BTW: the hyperlink after "Update:" isn't working
Hope you can help me
EDIT: Changing Kernel to Duckly's Kernel [Turbo Kernel] [25-3-2011] WITH KEYPAD DRIVERS NOT AS MODULES has solved my problem.
Is there a way to use the Kernel with keypad drivers as modules?

neoofoox said:
I have done:
- Everything copied to SD following the how to.
- [2011-04-18] FRX06 [CWM] worked, but this rom doesn't work
- Formated ext2 partitions to erease the old rom.
- Using Duckly's Kernel [Turbo Kernel] WITH KEYPAD DRIVERS AS MODULES
Problem:
I can run haret but when I have to click vol down it doesn't launch the recovery mode. it wants to continue.
With the FRX06 it worked but now it doesn't work
BTW: the hyperlink after "Update:" isn't working
Hope you can help me
EDIT: Changing Kernel to Duckly's Kernel [Turbo Kernel] [25-3-2011] WITH KEYPAD DRIVERS NOT AS MODULES has solved my problem.
Is there a way to use the Kernel with keypad drivers as modules?
Click to expand...
Click to collapse
I see, your problem is monster kernel not work with your phone, and when you change it to Turbo kernel it work ^^!
FOr use kernel with kaypad as modules, please read this thread http://forum.xda-developers.com/showpost.php?p=11808067&postcount=2
First: boot to android, then install autostart.apk and GScript.apk.
next: open terminal , remove modules and copy autostart.sh like that thread write. then open GScript and add script like that thread write.
next: reboot to winmobile, copy Turbo Kernel with keypad as modules to your sdcard/npkboot folder, replace the old file in there.
Final: boot to android, then make a shotcut GScript in home screen, when keypad die, just open the shotcut and it will work again.
Hope it have you

I see, your problem is monster kernel not work with your phone, and when you change it to Turbo kernel it work ^^!
Click to expand...
Click to collapse
I have never used Monster Kernel because I think it needs more battery than the Turbo kernel so I changed it to the Turbo Kernel.
After adding "ts-calibration"-file to the npkboot folder, it is starting now
*Settings > CyanogenMod Settings > User interface > tweaks extra > load theme > choose CM 6.1 white
- This will change the status bar text colour to white ...
Click to expand...
Click to collapse
There is no "CM 6.1 white" (CMTheme folder is empty) but the "STOCK_Black" makes the clock visible (status bar still black). Finaly I copied the "CM 6.1 white"-file from the EXT2 version.

Configuring Dual Boot [Flashable Configuration Zip v1.0 Released! 23 Jul 2012]

I developed a flashable zip to help configure dual boot. Zip is designed to be independent of ROM type, version and install method, whether by flashable zip, cloning primary ROM to SD, or in general copying a ROM system image to SD.
Then I overhauled this thread...
Config-Dual-Boot-v1.0-signed.zip: http://www.mediafire.com/?edgat0koyp7d33l
Backs up /sdcard[-ext]/Boot (if it exists) to /sdcard[-ext]/Boot.bak
Creates Boot/ROM1 and Boot/ROM2 directory paths under /sdcard[-ext]
Installs Script Manager on ROM1 and ROM2
Contains shell script “copy-boot.sh” to copy ROM boot partition to boot image file
Contains shell script “boot-rom.sh” to switch to boot ROM2 from ROM1 and vice versa
The updated “boot-rom.sh” script now features generic boot image directory names: Boot/ROM1 and Boot/ROM2, and automatically captures the SD Boot directory path (/sdcard for CM ROMs and /sdcard-ext for Blur ROMs).
Instructions:
1. Boot to ROM1 (emmc)
2. Reboot to CWM and flash: http://www.mediafire.com/?edgat0koyp7d33l . Doing so will backup any existing Boot directory under /sdcard[-ext] and push a new Boot directory containing empty subdirectories ROM1 and ROM2 and two shell scripts: copy-boot.sh (copy boot partition to image file) and boot-rom.sh (boot switcher).
In the following steps, the shell (sh) commands can be run using ADB (Android SDK Platform Tools), Terminal Emulator, Script Manager or other suitable app.
3. Reboot to ROM1
4. Enter: “sh /sdcard[-ext]/Boot/copy-boot.sh”. This detects which ROM is running, ROM1 in this case, and copies its boot image to /sdcard[-ext]/Boot/ROM1
5. Configure Script Manager to execute “sh boot-rom.sh 2” which enables booting to ROM2. But do not run this command until ROM2 “boot.img” is in place. We'll do that now.
6. Reboot to fastboot and connect phone to computer.
7. Enter: “fastboot flash boot boot.img” where boot.img is a boot image file modified to host ROM2 on SD. Please see my Auto-Modify Boot Image thread.
8. Enter: “fastboot reboot"
9. Enter: “sh /sdcard[-ext]/Boot/copy-boot.sh” as in step 4.
10. Configure Script Manager to execute “sh boot-rom.sh 1” which enables booting to ROM1.
More on configuring Script Manager:
Go to Settings > More > Advanced Options > Config > Home Directory. Set home directory to /sdcard/Boot. Then while still in SManager, navigate to /sdcard/Boot and press boot-rom.sh to configure. Valid arguments are:
Code:
blank: Reboot to current ROM
1: Reboot to ROM1 (emmc)
2: Reboot to ROM2 (SD)
3: Reboot to recovery
Press the “Su” box to run as root (note green symbol) and press “Save” at top right. Then press “Run” at top left to launch boot-rom.sh and reboot to the other ROM.
Place shortcut to Script Manager on home screen.
If all goes well, you can now boot ROM2 from ROM1 and vice versa with just a few screen taps.
This procedure was tested working with Neutrino V2.8 EE (CM) on emmc and NottachTrix 1.3.1 ATT (Blur) on SD.
Legacy YouTube video (3:38) showing reboots from one ROM to the other: http://www.youtube.com/watch?v=31TPyAguQ60
Credits
Special thanks to jokersax11, Notorious544d, ATRIXXIRTA, ghost_og, hatefuel19, J-Roc and many others for their technical direction, useful suggestions and encouragement. And of course to the Photon/Atrix/Android dev teams, Koush and https://sites.google.com/site/devwom/

Thanks a lot dude! Im going to try this!

how do you install two roms at the same time? i thought this was showing how to do that but im confused. how do you change the cwm zip installers to .img?
edit:: sorry i thought this was the other thread showing how to install a dual boot system but in fact its how to configure it to boot into them easier. sorry for the mixup ill defiantly read over your 1st thread

Note: Joker recommended as a refinement to place all apps in sdcard to keep apps common to both builds. Good idea.
Click to expand...
Click to collapse
Does this mean that across both on CM7 and CM9, the same apps will be installed? And if you install a new app, it will be seen in both CM7 and CM9?
And is data for apps accessible as well for both CM7 and CM9? So saving a data file with CM9 for example will be saved in /data and when I boot back into CM7, the same data I saved from CM9 will be there in CM7?
Lastly, did you manage to get that dalvik cache thingy working?
That's a lot of questions, but I hope you understand what I'm trying to say.
If it is, then WOW!

Notorious544d said:
Does this mean that across both on CM7 and CM9, the same apps will be installed? And if you install a new app, it will be seen in both CM7 and CM9?
And is data for apps accessible as well for both CM7 and CM9? So saving a data file with CM9 for example will be saved in /data and when I boot back into CM7, the same data I saved from CM9 will be there in CM7?
Lastly, did you manage to get that dalvik cache thingy working?
That's a lot of questions, but I hope you understand what I'm trying to say.
If it is, then WOW!
Click to expand...
Click to collapse
Thanks for the good questions. I haven't yet considered Joker's tip in detail as I spent most of yesterday writing this thread, researching other related topics (and watching Downton Abbey with my beloved wife ). But off the top, I assume that if a given app works on both ROMs, theoretically there should not be a problem hosting it and its corresponding data on the kitchen table (sdcard).
I guess one of the challenging questions is: Are there certain apps for which data should be kept separate to enable ROM-specific customization?

I just updated my thread with this...
"Alternatively (and actually preferred), you can extract the contents of this zip: http://www.mediafire.com/?0kdp4qvy6fv71kp to /sdcard. It makes ROM selections generic, and also fixes a problem with boot-rom.sh (Android shell apparently does not like trailing spaces in script files.) Then drop your boot.img files into /sdcard/Boot/ROM1 and ROM2 and you're good to go."
Cheers.

I developed a flashable zip to help configure dual boot. Zip is designed to be independent of ROM type, version and install method, whether flashable zip, cloning primary ROM to SD, or in general copying a ROM system image to SD.
Then I overhauled this thread...

CronTab for Android: Run task scheduler on your android phone.

We can use crontab on our phones for scheduling various tasks such as reminders, backups, scheduled reboots, wifi on-off, etc.... So i creat this flashable zip file to enable cron on your phone.
- Required: Root + busybox, init.d support (if your kernel doesnt support this feature, u can use universal init.d, uni-init,... instead.
- How to install:
1, Just download the zip file
2, go to recovery and flash it
3, Done, let's go!
USE:
- the "root" direction is "/system/etc/cron.d/root". Just open "root" file and add your task
- there are two default tasks that i added into "root" file. u can also modify it as u want :
1- Clean Ram drop caches every 30 minutes
2- perform Superclean (cache, davik cache,...) at 1h AM monday every week (credit to zeppelinrox)
CHECK CRONTAB WORKING OR NOT
open "/data/clean_ram_caches.log" every 30 minutes to check the cron worrking or not:
or open terminal and type "pgrep crond", cron is working if the result is a PID (example: 425, 489,...)
Worrking fine on my L3. Should worrk on other devices also
Download the attachment and ẹnjoy. sorry for my bad english

hello
kien_vip said:
We can use crontab on our phones for scheduling various tasks such as reminders, backups, scheduled reboots, wifi on-off, etc.... So i creat this flashable zip file to enable cron on your phone.
- Required: Root + busybox, init.d support (if your kernel doesnt support this feature, u can use universal init.d, uni-init,... instead.
- How to install:
1, Just download the zip file
2, go to recovery and flash it
3, Done, let's go!
USE:
- the "root" direction is "/system/etc/cron.d/root". Just open "root" file and add your task
- there are two default tasks that i added into "root" file. u can also modify it as u want :
1- Clean Ram drop caches every 30 minutes
2- perform Superclean (cache, davik cache,...) at 1h AM monday every week (credit to zeppelinrox)
CHECK CRONTAB WORKING OR NOT
open "/data/clean_ram_caches.log" every 30 minutes to check the cron worrking or not:
or open terminal and type "pgrep crond", cron is working if the result is a PID (example: 425, 489,...)
Worrking fine on my L3. Should worrk on other devices also
Download the attachment and ẹnjoy. sorry for my bad english
Click to expand...
Click to collapse
hello, i download your zip, but i donot konw put META-INF into where of my rom? thank you!
---------- Post added at 09:12 AM ---------- Previous post was at 08:28 AM ----------
i hope you give the detailed operation, such as first, second,.... ,thank you !

Thank You for this Guide
kien_vip said:
We can use crontab on our phones for scheduling various tasks such as reminders, backups, scheduled reboots, wifi on-off, etc.... So i creat this flashable zip file to enable cron on your phone.
- Required: Root + busybox, init.d support (if your kernel doesnt support this feature, u can use universal init.d, uni-init,... instead.
- How to install:
1, Just download the zip file
2, go to recovery and flash it
3, Done, let's go!
USE:
- the "root" direction is "/system/etc/cron.d/root". Just open "root" file and add your task
- there are two default tasks that i added into "root" file. u can also modify it as u want :
1- Clean Ram drop caches every 30 minutes
2- perform Superclean (cache, davik cache,...) at 1h AM monday every week (credit to zeppelinrox)
CHECK CRONTAB WORKING OR NOT
open "/data/clean_ram_caches.log" every 30 minutes to check the cron worrking or not:
or open terminal and type "pgrep crond", cron is working if the result is a PID (example: 425, 489,...)
Worrking fine on my L3. Should worrk on other devices also
Download the attachment and ẹnjoy. sorry for my bad english
Click to expand...
Click to collapse
Thanks to You that i could make Cron work in my Xperia SP.....
Actually i needed this for Executing a Command which Increases Touch Sensitivity and Maintains the Values Written by it. The Values Written by the Command are Overwritten by the System automatically after a short period.
Working Really Good and Fine.... :good: :good: :good: :highfive:

@kien_vip It was working fine while I was on stock rom but after switching to custom rom I flashed the script it stopped working, I entered "pgrep crond" in the terminal & there was no output like it used to also no log files on /data/_*logs. Please help cuz this is best script to me on XDA

New Samsung S4 i9295: rooting + custom ROM details plus the attached files

Got my new international version of the S4 (i9295) yesterday. Rooted and flashed a custom ROM this afternoon in about 1 hour. Below are the steps that I took to do this.
1.) Preparation: connect a usb micro SDcard reader (with a card in it) to your laptop and load the following files onto the sdcard,
-Towelroot.apk,
-SuperSU.apk
-terminal emulator such as jackpal.androidterm-1.0.70-71-minAPI4.apk
-root browser such as co.jrummy.root.browserfree.apk
-TWRP custom boot image file, Philz boot, recovery.img
-custom rom such as cm-12.1-20150715-NIGHTLY-jactivelte.zip
-Google Applications (GAPPS)​2.) Next, turn off your phone, remove the SIM card, insert the sdcard card with the above applications copied onto it.
3.) Turn on your phone. Go to Settings and click the "More" tab. Then go into security and check "Unknown Sources."
4.) Log onto a wifi network to gain internet access.
5.) Go to Applications, select the "My Files" browser and go to the sdcard. Locate Towelroot.apk that you just loaded on the card. Install it and run it. Towelroot will want to talk to the mothership regarding precisely how to root your device. This is okay.
6.) Install terminal emulator, and root browser.
7.) Install SuperSU. Open the SuperSU app and allow application to update binaries.
8.) Open terminal emulator, type in "dd if=/storage/extSdCard/recovery.img of=/dev/block/mmcblk0p21". Now type "reboot".
9.) TWRP should now be installed.
10.) Shut down the phone. Now, hold down the volume up and power buttons at the same time to boot into Philz TWRP bootloader.
11.) Select "Install zip", then select "Choose zip from storage/sdcard1", now choose the custom ROM that you have copied to the root of your external sdcard. Note: I had to do a factory reboot at this point as I was getting an "detected filesystem ext4 for /dev/block/platform/..." error message. I used the "factory reset" option under "wipe and format options" in TWRP with no problems. After this I was able to install the most recent 12.x Cyanogenmod rom with no problem.
12.) Repeat step 11 for GAPPS package.​I have moved 5 of the 7 applications listed in step 1 into a zip archive (12.9mb) and uploaded it. The only applications missing are the custom ROM (268mb), and recent GAPPS collection (75mb).
Sources for the resources in step 1 are,
GAPPS- https://itvends.com/gapps/
Cyanogenmod nightlies- http://download.cyanogenmod.org/?type=nightly&device=jactivelte
Towelroot- https://towelroot.com/
SuperSU- https://download.chainfire.eu/396/supersu/
Terminal emulator- http://www.apkmirror.com/apk/jack-p...erminal-emulator-1-0-70-android-apk-download/
Root browser (JRummy apps)- http://jrummy-apps.com/
Philz custom TWRP boot image file- goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte
Have fun.

{VIDEO GUIDE} ONEPLUS 3/3T Insane Battery And Performance (Advanced Kernel Tweaks)

This is not my work main thread
https://forum.xda-developers.com/showpost.php?p=70352820&postcount=2146
I have made video to make it simple . Ill be keep updating screen shots
Download:
https://www.androidfilehost.com/?fid=745425885120711962
How to install:
A flashable zip to be flashed via recovery, which installs scripts of the latest iterations of most profiles (some legacy profiles had to be eliminated for more convenience) and a master script that takes control of all the installed scripts and applies your desired profile at will as soon as you recall it via Terminal Emulator app and get guided by the on-screen instructions.
So to wrap it up:
1- Download the latest AKT_Profile_vX.x.zip file
2- Reboot into TWRP recovery and flash the .zip file
3- After you boot up the phone, leave it to settle for a minute
4- Open up your favorite Terminal Emulator app
5- Grant it superuser permissions by typing in "su" without the quotes
6- After superuser permissions are granted, type in "AKT" without the quotes (yes capitalized)
7- Follow the on-screen instructions and information, don't worry they are very intuitive and easily understandable
8- Profit!
Video:
https://youtu.be/0QYp5tkBaao

Thanks for sharing a video along with the guide.

so, no need to flash any kernel or any app other than terminal? :3