New Boot Image
NEW BOOT IMAGE ADDED!
Just added this boot.img (First Post for downloads):
NEW BOOT IMAGE ADDED!
Just added this boot.img (First Post for downloads):
- S5570JPKQ8 (2.3.4)
Free Memory to > 1Gb!
How to Increase your Internal Memory Size with very low effort!
NOTICE: This method works both on Rooted and NOT Rooted Phones!
You simply need to meet three easy requirements:
- Stock Firmware installed on the Phone (custom ROMS not supported ...They don't need to!)
- A microSD with two primary formatted partitions inside (the former 'to FAT32' and the latter 'to EXT4' filesystems)
- Ready to Flash to your Galaxy Next via Odin
NOTICE: The following Black Box Howto is explained deep inside in the next post of this Thread (short explanation) and in This Thread from outside: Internal Memory to +1Gb! and related ones (long explanation / Italian Language)
HOW TO
1) Download Tass.ops file for Odin!
2) Type this number on your phone keyboard:
*#1234#
and keep note of the PDA code of the Firmware installed.
3) Download boot image ready for Odin and suitable for your firmware:
Your firmware is not listed? ...let me know, I'll give it a try!
- PDA=S5570AIKQ3 (2.3.4)
- PDA=S5570JPKQ8 (2.3.4) (NEW)
- PDA=S5570XIKQC (2.3.4)
- PDA=S5570XXKPI (2.3.4)
- PDA=S5570XXKPK (2.3.4)
- PDA=S5570JPKS1 (2.3.5)
- PDA=S5570XWKS2 (2.3.5)
- PDA=S5570XWKS7 (2.3.5)
- PDA=S5570DDKQ7 (2.3.6)
- PDA=S5570JVKT1 (2.3.6)
- PDA=S5570LWMKPJ (2.3.6)
4) Flash the downloaded archive with Odin
Example image follows:
5) THAT'S ALL FOLKS!
- - -
How does it Work:
Scenario 1:
I switch on the Phone, without a MicroSD slotted in or with a microSD with a single FAT32 partition (broken or damaged microSD also suite this scenario...); GingerBread boots as usual!
No Difference!
Scenario 2:
I switch on The Phone with a microSD slotted in (with the second partition formatted as EXT4 filesystem but still EMPTY); Ginger boots acting as if
/data
is completely moved outside to microSD but just WIPED (not true obviously, and the original /data is safe inside the phone), so it resettle it from beginning...
NOTICE:
...If your second partition is 1Gb wide...
...your new Internal Memory will be 1Gb wide...
Scenario 3:
I switch on the Phone with the second partition of the microsd (EXT4) up and running (already resettled up for use and with my userdata on it); Ginger simply boots with
/data
moved outside to microSD with your userdata there and tons of apps just installed from the market...
Example Image of my New Internal Memory Size follows
- - -
NOTICES & ADVICES:
- If I want to remove the microSD from the slot, FIRST I NEED TO SWITCH OFF THE PHONE!
- When I install apps from the Market, Ginger Misunderstands the actual new Internal Memory SIZE and puts the apk files to External Storage anyway! I simply need to move them "to the phone" via "Settings menu" immediately after!
- When I switch on the Phone without the microSD, I boot using the original /data inside the phone, actually loosing all the apps installed onto the external one untill next boot with SDcard; and, of course, loosing my sms stored there and others personal userdata too.
- Unfortunately this boot image heavy conflicts with Link2SD (great app anyway!), so you must choose one: This Boot image or Link2SD... not both... sorry!
Don't You Like the boot image just installed and You want to revert without flashing the full firmware to the Phone?
Here are the original images ready for Odin:
- PDA=S5570AIKQ3 (2.3.4)
- PDA=S5570JPKQ8 (2.3.4)
- PDA=S5570XIKQC (2.3.4)
- PDA=S5570XXKPI (2.3.4)
- PDA=S5570XXKPK (2.3.4)
- PDA=S5570JPKS1 (2.3.5)
- PDA=S5570XWKS2 (2.3.5)
- PDA=S5570XWKS7 (2.3.5)
- PDA=S5570DDKQ7 (2.3.6)
- PDA=S5570JVKT1 (2.3.6)
- PDA=S5570LWMKPJ (2.3.6)
>> ONLY ROOTED PHONES <<
These application is strictly related to the boot images modded from Doc for the galaxy NEXT/MINI/POP and the galaxy FIT...
While running the smartphone with the internal memory "expanded" and completely moved to the second partition of the SD Card there isn't the possibility to check the ext4 filesystem for safety in "an easy way"...
This application just does the filesystem checkup "dirty job" with minimal user interaction...
HOW TO:
This application MUST BE INSTALLED in the "TRUE" internal memory! So you need to power on the phone, without the SD Card slotted in, to do it!
Once installed, every time you want to check the ext4 2nd partition filesystem, simply:
- Power off the phone
- Pull out the microSD
- Power on the phone
- push in the microSD
- wait for media scan
- launch this app
- push the "check" button
That's all!
Now you can check what's happened reading the Log from menu or simply reboot, with SD slotted in, to revert to the "pumped-up" internal memory!
NOTICE: I'm not a true developer nor a "java" skilled one... I simply assembled snippets of code from the web and followed android tutorials and guides, figuring out how to set this application up and running (of course I know what we are talking about... lucky but not so much, eh eh!)...
It's shared "AS IS" with the source package attached, suitable for eclipse IDE (indigo version)... use it at
YOUR OWN RISK
and feel free to change its code to suite your needs as you wish.
How does it Works:
On start it checks if the phone is rooted and busyboxed, then it looks for the Doc modded boot image, checking that you just booted using the "true" internal memory.
After that, it copies the "e2fsck" tool command cross-compiled from "Linux" to "Arm" to the filesystem and waits for the user to push the start button.
Finally it checks silently the 2nd partition filesystem for errors, eventually repairing them and logging everything for later human readings...
CREDITS:
Everybody who will use this application!
Everybody who will improve this java code!
CHANGELOG:
Version 1.0 RC3
- upgraded "e2fsck" binary from 1.42 to 1.42.1
Version 1.0 RC2
- fully rewritten "SuperUser Engine"
- fixed mayor bugs
You should read the first page. It does not support custom ROMs:If I flash the hacked boot image then I install a Custom ROM, will it still works?
Is the Tass.ops different with the original?
If I use your hacked boot image, will my application be erased?
You should read the first page. It does not support custom ROMs:
You simply need to meet three easy requirements:
Stock Firmware installed on the Phone (custom ROMS not supported ...They don't need to!)
Not quite sure about that.. Better be prepared with application backup if you want to try this..Sorry, I just realized about it.
What about the applications? will my apps be gone after I try this boot image?
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ tar xf CODE_S5570XXKPF_CL189639_REV02_user_mid_true.tar.md5 boot.img
doc@gandalf ~/boot_mod $ ls -l
total 212864
-rw-r--r-- 1 doc doc 211589203 Jan 31 09:39 CODE_S5570XXKPF_CL189639_REV02_user_mid_true.tar.md5
-rw-r--r-- 1 doc doc 6377472 May 7 2011 [b]boot.img[/b]
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ tar -H ustar -c boot.img > CODE_S5570XXKPF_boot.tar
doc@gandalf ~/boot_mod $ md5sum CODE_S5570XXKPF_boot.tar >> CODE_S5570XXKPF_boot.tar
doc@gandalf ~/boot_mod $ mv CODE_S5570XXKPF_boot.tar CODE_S5570XXKPF_boot.tar.md5
doc@gandalf ~/boot_mod $ ls -l
...
-rw-r--r-- 1 doc doc 6379579 Jan 31 09:51 CODE_S5570XXKPF_boot.tar.md5
...
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ ./split_bootimg.pl boot.img
Page size: [b]4096[/b] (0x00001000)
Kernel size: 3221952 (0x003129c0)
Ramdisk size: 3146572 (0x0030034c)
Second size: 0 (0x00000000)
Board name:
Command line:
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
doc@gandalf ~/boot_mod $ ls -l
...
-rw-r--r-- 1 doc doc 6377472 May 7 2011 boot.img
-rw-r--r-- 1 doc doc 3221952 Jan 31 09:56 boot.img-kernel
-rw-r--r-- 1 doc doc 3146572 Jan 31 09:56 boot.img-ramdisk.gz
-rw[b]x[/b]r-[b]x[/b]r-[b]x[/b] 1 doc doc 6121 Jan 31 09:44 split_bootimg.pl
...
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ hexedit boot.img
...
00000000 41 4E 44 52 4F 49 44 21 C0 29 31 00 00 80 60 13 ANDROID!.)1...`.
00000010 4C 03 30 00 00 00 60 14 00 00 00 00 00 00 50 14 L.0...`.......P.
00000020 00 01 [color=blue][b]60[/b][/color] [color=red][b]13[/b][/color] 00 10 00 00 00 00 00 00 00 00 00 00 ..`.............
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
...
doc@gandalf ~/boot_mod $
base address = 0x[color=red][b]13[/b][/color][color=blue][b]60[/b][/color]0000
doc@gandalf ~/boot_mod $ ./mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz --base 0x13600000 --pagesize 4096 -o boot_COPY.img
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ diff boot.img boot_COPY.img
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ mkdir ramdisk
doc@gandalf ~/boot_mod $ [b]cd[/b] ramdisk
doc@gandalf ~/boot_mod/ramdisk $ gunzip -c ../boot.img-ramdisk.gz | cpio -i
14299 blocks
doc@gandalf ~/boot_mod/ramdisk $
doc@gandalf ~/boot_mod/ramdisk $ ls -l
total 744
-rw-r--r-- 1 doc doc 13444 Jan 31 10:17 TASS.rle
drwxrwx--x 2 doc doc 4096 Jan 31 10:17 data
-rw-r--r-- 1 doc doc 118 Jan 31 10:17 default.prop
drwxr-xr-x 2 doc doc 4096 Jan 31 10:17 dev
-rw-r--r-- 1 doc doc 222472 Jan 31 10:17 fsua
-rwxr-x--- 1 doc doc 94380 Jan 31 10:17 init
-rwxr-x--- 1 doc doc 1677 Jan 31 10:17 init.goldfish.rc
-rwxr-x--- 1 doc doc 3048 Jan 31 10:17 init.qcom.post_boot.sh
-rwxr-x--- 1 doc doc 7976 Jan 31 10:17 init.qcom.rc
-rwxr-x--- 1 doc doc 6563 Jan 31 10:17 init.qcom.sh
-rwxr-x--- 1 doc doc 24201 Jan 31 10:17 init.rc
drwxr-xr-x 3 doc doc 4096 Jan 31 10:17 lib
drwxr-xr-x 2 doc doc 4096 Jan 31 10:17 proc
-rw-r--r-- 1 doc doc 331588 Jan 31 10:17 recovery
drwxr-x--- 2 doc doc 4096 Jan 31 10:17 sbin
drwxr-xr-x 2 doc doc 4096 Jan 31 10:17 sys
drwxr-xr-x 2 doc doc 4096 Jan 31 10:17 system
-rw-r--r-- 1 doc doc 0 Jan 31 10:17 ueventd.goldfish.rc
-rw-r--r-- 1 doc doc 5759 Jan 31 10:17 ueventd.rc
doc@gandalf ~/boot_mod/ramdisk $
Surely it could be possible... I actually did it for Galaxy ACE too, but I don't have the possibility to test the modded images... finally, the kernel for Galaxy Fit, Ace and Mini is pretty the same, so I bet on it!
/home/doc/builds/WORKING_DIRECTORY/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/
/home/doc/boot_mod/kernel
doc@gandalf ~/boot_mod $ ls -l
...
-rw-r--r-- 1 doc doc 6377472 May 7 2011 boot.img
-rw-r--r-- 1 doc doc 3221952 Jan 31 09:56 boot.img-kernel
-rw-r--r-- 1 doc doc 3146572 Jan 31 09:56 boot.img-ramdisk.gz
[b]d[/b]rwxr-xr-x 24 doc doc 4096 Jan 26 2011 kernel
-rwxr-xr-x 1 doc doc 28614 Jan 31 10:08 mkbootimg
[b]d[/b]rwxr-xr-x 9 doc doc 4096 Jan 31 10:17 ramdisk
-rwxr-xr-x 1 doc doc 6121 Jan 31 09:44 split_bootimg.pl
...
doc@gandalf ~/boot_mod $
VERSION = [b]2[/b]
PATCHLEVEL = [b]6[/b]
SUBLEVEL = [b]35[/b]
EXTRAVERSION = [b].7[/b]
NAME = Yokohama
CROSS_COMPILE = ...
/home/doc/builds/WORKING_DIRECTORY/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/[b]bin/arm-eabi-[/b]
doc@gandalf ~/boot_mod/kernel $ make [b]tass_rev02_defconfig[/b]
...
#
# configuration written to .config
#
doc@gandalf ~/boot_mod/kernel $
doc@gandalf ~/boot_mod/kernel $ make help
doc@gandalf ~/boot_mod/kernel $ make modules
...
Building modules, stage 2.
MODPOST 7 modules
...
doc@gandalf ~/boot_mod/kernel $
doc@gandalf ~/boot_mod/kernel $ [b]make menuconfig[/b]
2.6.35.7-perf-CL561937
root@DELL88 #1
[b]-perf-CL561937[/b]
< > ...
<[b]M[/b]> CIFS support (advanced network filesystem, SMBFS successor)
[ ] ...
doc@gandalf ~/boot_mod/kernel $ make modules
...
LD [M] fs/cifs/cifs.ko
doc@gandalf ~/boot_mod/kernel $
doc@gandalf ~/boot_mod/kernel $ /home/alberto/builds/WORKING_DIRECTORY/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-[b]strip --strip-unneeded[/b] fs/cifs/cifs.ko
doc@gandalf ~/boot_mod/kernel $
doc@gandalf ~/boot_mod/kernel $ adb push fs/cifs/cifs.ko /data/local
3687 KB/s (252908 bytes in 0.066s)
doc@gandalf ~/boot_mod/kernel $
doc@gandalf ~/boot_mod/kernel $ adb shell
$ su
# lsmod
...
# [b]insmod /data/local/cifs.ko[/b]
# lsmod
[color=blue][b]cifs 210416 0 - Live 0xbf1b9000[/b][/color]
...
# exit
$ exit
doc@gandalf ~/boot_mod/kernel $
# insmod /data/local/cifs.ko
[color=red][b]insmod: init_module '/data/local/cifs.ko' failed (Exec format error)[/b][/color]
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ cp init.data.sh ramdisk/
doc@gandalf ~/boot_mod $ chmod 0750 ramdisk/init.data.sh
doc@gandalf ~/boot_mod $ cp busybox ramdisk/sbin/
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ patch ramdisk/init.rc -i init.rc.patch
patching file ramdisk/init.rc
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ su -c 'modinfo ramdisk/lib/modules/fsr.ko' | grep vermagic
Password: [i](linux root password asked)[/i]
vermagic: 2.6.35.7[b]-perf-CL189639[/b] preempt mod_unload ARMv6
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ sudo modinfo ramdisk/lib/modules/fsr.ko | grep vermagic
[sudo] Password for doc: [i](linux user password asked)[/i]
vermagic: 2.6.35.7[b]-perf-CL189639[/b] preempt mod_unload ARMv6
doc@gandalf ~/boot_mod $
General Setup
[+] Prompt for development and/or incomplete code/drivers
() Cross-compiler tool prefix
([b]-perf-CL189639[/b]) Local version - append to kernel release
[ ] ...
...
File systems
[b]<M>[/b] The Extended 4 (ext4) filesystem
[b][ ][/b] Use ext4 for ext2/ext3 file systems [color=red]<- This must be UNSELECTED![/color]
[+] Ext4 extended attributes (NEW)
[ ] Ext4 POSIX Access Control Lists (NEW)
[ ] Ext4 Security Labels (NEW)
[ ] EXT4 debugging support (NEW)
[ ] JBD2 (ext4) debugging support (NEW)
...
doc@gandalf ~/boot_mod/kernel $ make modules
...
...
LD [M] fs/ext4/ext4.ko
...
LD [M] fs/jbd2/jbd2.ko
...
doc@gandalf ~/boot_mod/kernel $
doc@gandalf ~/boot_mod/kernel $ cd ..
doc@gandalf ~/boot_mod $ cp kernel/fs/jbd2/jbd2.ko ramdisk/lib/modules/
doc@gandalf ~/boot_mod $ cp kernel/fs/ext4/ext4.ko ramdisk/lib/modules/
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ /home/doc/builds/WORKING_DIRECTORY/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-strip --strip-unneeded ramdisk/lib/modules/*.ko
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ su -c 'chown -R root:root ramdisk'
doc@gandalf ~/boot_mod $ su -c 'chmod 04755 ramdisk/sbin/busybox'
doc@gandalf ~/boot_mod $ cd ramdisk/
doc@gandalf ~/boot_mod/ramdisk $ su -c 'find . | cpio -o -H newc | gzip > ../boot.img-ramdisk.gz'
7978 blocks
doc@gandalf ~/boot_mod $ cd ..
doc@gandalf ~/boot_mod $ su -c 'chown -R doc:doc ramdisk'
doc@gandalf ~/boot_mod $ su -c 'chown doc:doc boot.img-ramdisk.gz'
doc@gandalf ~/boot_mod $ ./mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz --base 0x13600000 --pagesize 4096 -o boot.img
doc@gandalf ~/boot_mod $ ls -l
...
-rw-r--r-- 1 doc doc [b]5431296[/b] Jan 31 22:27 boot.img
...
doc@gandalf ~/boot_mod $
doc@gandalf ~/boot_mod $ tar -H ustar -c boot.img > CODE_S5570XXKPF_boot.tar
doc@gandalf ~/boot_mod $ md5sum CODE_S5570XXKPF_boot.tar >> CODE_S5570XXKPF_boot.tar
doc@gandalf ~/boot_mod $ mv CODE_S5570XXKPF_boot.tar CODE_S5570XXKPF_boot.tar.md5
doc@gandalf ~/boot_mod $
Galaxy FIT images:
...list moved to Galaxy FIT development Forum...
Galaxy ACE Modded boot.img:
- PDA=S5830DDKQ5
- PDA=S5830DDKQ8
- PDA=S5830DXKPB
- PDA=S5830DXKPD
- PDA=S5830DXKT5
- PDA=S5830XWKPY (Tested by Kotucisko )
- PDA=S5830XWKS2
- PDA=S5830XWKS9
- PDA=S5830XWKT7
- PDA=S5830XWKTM
- PDA=S5830XWKTQ
- PDA=S5830XXKPH
- PDA=S5830XXKPP
Galaxy ACE Original boot.img:
- PDA=S5830DDKQ5
- PDA=S5830DDKQ8
- PDA=S5830DXKPB
- PDA=S5830DXKPD
- PDA=S5830DXKT5
- PDA=S5830XWKPY
- PDA=S5830XWKS2
- PDA=S5830XWKS9
- PDA=S5830XWKT7
- PDA=S5830XWKTM
- PDA=S5830XWKTQ
- PDA=S5830XXKPH
- PDA=S5830XXKPP
Galaxy GIO Modded boot.img:
- PDA=S5660DXKT8
- PDA=S5660JPKT7
- PDA=S5660MUGKG3
- PDA=S5660XXKPA
- PDA=S5660XXKTF(Tested by GeorgeParaschiv )
- PDA=S5660XXKTI
- PDA=S5660XXKTK
Galaxy GIO Original boot.img:
- PDA=S5660DXKT8
- PDA=S5660JPKT7
- PDA=S5660MUGKG3
- PDA=S5660XXKPA
- PDA=S5660XXKTF
- PDA=S5660XXKTI
- PDA=S5660XXKTK
NEW BOOT IMAGE ADDED!
Just added this boot.img (First Post for downloads):
- S5570DXKPD (2.3.6)
[b][url=https://docs.google.com/folder/d/0B3qe_9NlA1D_QVlKXy01bjZPbVE/edit]Memory Hack Google Drive Archive[/url][/b]
[b][size=3]Galaxy MINI/NEXT/POP[/size][/b]
S5570AIKQ3 S5570BGKS3 S5570BGKT2
S5570BVKQ4 S5570BVKT1 S5570DDKA7
S5570DDKQ7 S5570DXKPD S5570DXKT6
S5570JPKQ8 S5570JPKS1 S5570JPKT2
S5570JVKQ3 S5570JVKT1 S5570MJKS2
S5570XIKQC S5570XWKE3 S5570XWKQG
S5570XWKS2 S5570XWKS7 S5570XWKT7
S5570XWKTH S5570XWKTN S5570XWKTS
S5570XWKTU S5570XXKPF S5570XXKPI
S5570XXKPK S5570XXKS1 S5570XXKS4
S5570ZSKPC
-----------
S5570bVJKPB
-----------
S5570LWMKP9 S5570LWMKPJ S5570LWMKPO
[b][size=3]Galaxy MINI/NEXT/POP[/size][/b]
[b]Froyo[/b]
S5570DXKB1 S5570XIKFI S5570XWKC1
[b][size=3]Galaxy GIO[/size][/b]
S5660AIKT4 S5660DXKT8 S5660JPKT7
S5660XXKPA S5660XXKTF S5660XXKTI
S5660XXKTK S5660XXKTO
-----------
S5660MUGKG3
[b][size=3]Galaxy FIT[/size][/b]
S5670DDKB1 S5670DDKT3 S5670DXKPB
S5670DXKT4 S5670JPKQ7 S5670XWKQA
S5670XWKTI S5670XXKPQ S5670XXKPU
-----------
S5670LUBKP6 S5670LUBKPI
[b][size=3]Galaxy ACE[/size][/b]
S5830BOKS3 S5830DDKQ5 S5830DDKQ8
S5830DXKPB S5830DXKPD S5830DXKT5
S5830XWKPY S5830XWKS2 S5830XWKS9
S5830XWKT7 S5830XWKTM S5830XWKTQ
S5830XXKPH S5830XXKPP
HOW TOOn post n. 43 you can find an Android Application useful to check the 2nd partition filesystem for errors once a month...
EXT4 Checkup Tool 1.0 RC3
P.S. Only for rooted phones!
ADDED PHONE MODELSFrom post n. 52 I explain exactly What I do deep Inside and Step by Step...
ALL IN ONE WONDER AUTOSCRIPTIn post n. 56 I added boot images modded for Galaxy FIT (S5670), Galaxy ACE (S5830) and Galaxy GIO (S5660)!
MEMORY AND OVERCLOCK KERNELIn post n. 78 I added a Linux Script "All in one" to mod your boot Image on your own simply with a double-click!
In post n. 148 you find modded images with OC Kernel inside
P.S. Only for rooted phones with CWM or Custom Recovery!
gandalf $ ls -l ./ramdisk/lib/modules/
totale 1304
-rw-r--r-- 1 root root 236116 11 dic 08.24 [b]ext4.ko[/b]
-rw-r--r-- 1 root root 363932 11 dic 08.24 fsr.ko
-rw-r--r-- 1 root root 211200 11 dic 08.24 fsr_stl.ko
-rw-r--r-- 1 root root 58176 11 dic 08.24 [b]jbd2.ko[/b]
-rw-r--r-- 1 root root 260568 11 dic 08.24 rfs_fat.ko
-rw-r--r-- 1 root root 90968 11 dic 08.24 rfs_glue.ko
-rw-r--r-- 1 root root 99532 11 dic 08.24 sec_param.ko
gandalf $
# insmod fsr/rfs modules
insmod /lib/modules/fsr.ko
insmod /lib/modules/fsr_stl.ko
insmod /lib/modules/rfs_glue.ko
insmod /lib/modules/rfs_fat.ko
insmod /lib/modules/sec_param.ko
[color=red]insmod /lib/modules/jbd2.ko[/color]
[color=red]insmod /lib/modules/ext4.ko[/color]
gandalf $ ls -l ./ramdisk/sbin/
totale 2088
-rwxr-x--- 1 root root 117948 11 dic 08.18 adbd
-rw[color=red][b]s[/b][/color]r-xr-x 1 root root 2016700 11 dic 08.21 [b]busybox[/b]
lrwxrwxrwx 1 root root 7 11 dic 08.18 ueventd -> ../init
(i686) gandalf ~ (i686) $
# Mounting of system/userdata is moved to 'on emmc' and 'on nand' sections
# We chown/chmod /data again so because mount is run as root + defaults
[color=red][b]mount rfs /dev/stl13 /data nosuid nodev check=no[/b][/color]
chown system system /data
chmod 0771 /data
# Mounting of system/userdata is moved to 'on emmc' and 'on nand' sections
# We chown/chmod /data again so because mount is run as root + defaults
[color=red][b]exec /sbin/busybox sh /init.data.sh[/b][/color]
chown system system /data
chmod 0771 /data
gandalf $ cat ./ramdisk/init.data.sh
#!/sbin/busybox sh
/sbin/busybox mount -o nosuid,nodev -t ext4 /dev/block/mmcblk0p2 /data || /sbin/busybox mount -o nosuid,nodev -t rfs /dev/stl13 /data
gandalf $
tar -H ustar -c boot.img > CODE_S5570XWKS7_boot.tar
md5sum CODE_S5570XWKS7_boot.tar >> CODE_S5570XWKS7_boot.tar
mv CODE_S5570XWKS7_boot.tar CODE_S5570XWKS7_boot.tar.md5
...now i am using this: http://xdaforums.com/showthread.php?p=18561098
busybox mount -t ext4 -o noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue,noatime,nodiratime,nosuid,nodev /dev/block/mmcblk0p2 /data;
#-- SDCard Speed Fix
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "8192" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;
Wow, 8 MB ? Is that really useful? I read somewhere that 3 MB is optimum, 4 MB is slightly waste. 8MB? Then again I might be wrong, never tried 8MB myself...
# busybox mount -o remount,nosuid,nodev,noatime,nodiratime,errors=continue,nouser_xattr /cache (ext2 filesystem)
# busybox mount -o remount,ro,noatime,nodiratime,nouser_xattr,barrier=1,data=ordered,noauto_da_alloc /system (ext4)
# busybox mount -o remount,noatime,nodiratime,nouser_xattr,barrier=1,data=ordered,noauto_da_alloc /data (ext4)
#
# busybox echo "[b]8192[/b]" > /sys/devices/virtual/bdi/179:0/read_ahead_kb
#
...Boot images are ready to be shared with these patches on, but I need to test them one by one... I think to be Ready within tomorrow night...
Found and patched 2.3.5 fimware S5570JPKS1 with these tweaks too... scheduled to be tested within tomorrow night too...
distan7 said:...I read at stepph's thread how you MOVED /system to MicroSD but somehow I forgot to ask. Now you mentioned it here. Is it safe ? No i/o bottleneck / noticeable lag ? I know we'll need a really fast and reliable MicroSD card. What's yours doc?
...With /system and /data in MicroSD, does this mean we can MULTIBOOT ?
Let's say I partitioned my sdcard into 5 : 1st one is FAT32 and the other 5 is ext4. I modified boot.img from (let's say) CM7 and stock GB. On CM7's init.rc i put /system and /data into partition 2&3. On stock GB's init.rc i put them into partition 4&5. Partition 6 is used for /cache. I flashed stock with modded boot.img, play around first. Then I flashed CM7 with modded boot.img and played around. Now each time I want to switch ROM, all I have to do is flash the appropriate boot.img using CWM. This boot.img will determine which partition will be used for /system and /data...
i think its possible, but it depend to the dev want to make it or not
.
|-- [color=blue]arch[/color]
| `-- [color=blue]arm[/color]
| `-- [color=blue]mach-msm[/color]
| |-- acpuclock.c
| `-- cpufreq.c
|-- [color=blue]drivers[/color]
| |-- [color=blue]cpufreq[/color]
| | |-- Kconfig
| | |-- Makefile
| | |-- cpufreq.c
| | |-- cpufreq_brazilianwax.c
| | |-- cpufreq_interactive.c
| | |-- cpufreq_interactivex.c
| | |-- cpufreq_lagfree.c
| | |-- cpufreq_minmax.c
| | |-- cpufreq_savagedzen.c
| | |-- cpufreq_scary.c
| | |-- cpufreq_smartass.c
| | |-- cpufreq_smartass2.c
| | |-- cpufreq_smoothass.c
| | `-- cpufreq_stats.c
| `-- [color=blue]cpuidle[/color]
| `-- [color=blue]governors[/color]
| `-- menu.c
`-- [color=blue]include[/color]
`-- [color=blue]linux[/color]
`-- cpufreq.h