[HACK] Increase Internal Memory Size to Whatever You Want!
- Thread starter Doc_cheilvenerdi.org
- Start date
OFF TOPIC!
Hei, wow... here is my first Android Application!
...just a wrapper to the e2fsck shell tool used to check - once a month - the second partition ext4 filesystem for errors...
>>>ONLY ROOTED PHONES <<<
HOW DOES IT WORK:
- I power off the phone, pull out the SD card and power on the phone to start using the true internal memory;
- I insert the SD card in the slot;
- (first time) I install the application (using adb or from the SDcard, for example);
- I run the application, which will check for a "Doc modded" boot image and several other requirements (rooted phone, busybox, and so on...);
- I push the check button to check the ext4 filesystem for errors;
- Optional: I read the Log file of the operation;
- I reboot the phone to use again the clean pumped-up internal memory!
- I'll repeat this operation once a month...
This is the signed application: EXT4 Checkup.apk
(I'm not a developer so I don't have a market developer account)
and here is the source code packaged for eclipse IDE (indigo version): EXT4_Checkup-1.0-RC3.tar.gz
WARNINGS: I'm not a true developer nor a java skilled one, so you could find "poor programming practice" inside the source code and even occurr in bugs not yet discovered... so you should use it AT YOUR OWN RISK...
Actually the application works fine...I'm only dealing with a timing bug (not solved but workarounded for now) on first time run: while asking for root permissions it fails the check for a "Doc modded" boot image... so I simply need to run it again soon after...
Why did I write this application?
In post n. 33 I explained how to check the 2nd partition filesystem from adb, but I feel that it's not a "user friendly" way to do it... so here there is an easier one...
Finally, on first run you should read the HowTo on the phone:
I have this error:
ROOT ERRORS
2nd Partition Is Mounted
?
Help please.
Sorry, my foult, i've turned on with sdcard.
Last edited:
i have samsung galaxy mini s5570i saudi Arbia PDA S5570iJPLF1 please finde my boot tarFree 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:
All modded images are inside my Google Drive; actually we find:
Code:[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
your firmware not listed? ...take a look into Google Drive first, then let me know if you don't find anything!
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?
The original images, ready for Odin, are stored into my Google Drive too, inside BASE subfolders!
- - - - - - - - - - - - - - - - -
THREAD ADDONS
CHECK FILESYSTEM FOR ERRORS
HOW TO
ADDED PHONE MODELS
ALL IN ONE WONDER AUTOSCRIPT
MEMORY AND OVERCLOCK KERNEL
Hi, this hack belongs to Galxy Mini and few other variants...
I feel you own a Galaxy Pop Plus (Galaxy Next Turbo in Italy):
The hint is the "I" character in the code:
S5570IXXND1
and I never hacked into it, so you should check for different mods:
- - Link2SD;
- - Custom ROM;
- - many others;
...starting from the Galaxy Pop Plus Subdìforum/Threads,
cheers
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
84Free 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:
All modded images are inside my Google Drive; actually we find:
Code:[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
your firmware not listed? ...take a look into Google Drive first, then let me know if you don't find anything!
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?
The original images, ready for Odin, are stored into my Google Drive too, inside BASE subfolders!
- - - - - - - - - - - - - - - - -
THREAD ADDONS
CHECK FILESYSTEM FOR ERRORS
HOW TO
ADDED PHONE MODELS
ALL IN ONE WONDER AUTOSCRIPT
MEMORY AND OVERCLOCK KERNEL
27Patched Boot Image "Deep Inside"
As I stated in the previous Post, I skip the Long Explanation of this How to (Italian Threads online anyway) and briefly describe What I did!
1) Split Boot.img
I splitted boot.img into it's two main parts: The Kernel and the Ramdisk.
2) Edit ramdisk
2.1) Strip Samsung Kernel Modules
I figured out that Samsung modules used for rfs filesystem are compiled with all the debug symbols inside, so I stripped them saving more than 3Mb into the ramdisk!
NOTICE: The boot.img must not exceed 8Mb Size or I cannot flash it! BEWARE!
2.2) Add Ext4 kernel Modules
I compiled the jbd2.ko and ext4.ko modules for the attached Kernel and put them into /lib/modules inside the ramdisk:
Code: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 $
2.3) Patch init.rc file
I patched the init.rc file into the ramdisk to load these modules into the kernel immediately after the first boot stage of the firmware:
Code:# 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]
2.4) Add busybox
I added a copy of busybox into /sbin.
I'll need it to mount ext4 filesystems on microSD later on.
Code: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) $
2.5) Patch init.rc again
I changed the mount command for /data!
Original code:
Code:# 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
Patched code:
Code:# 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
2.6) add init.data.sh file
I added an external shell file, used to mount microsd /data avoiding the Android Init Language used by init.rc.
Code: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 $
3) Repack ramdisk and kernel into boot.img
I used the AOSP mkbootimg tool to repack alltoghether.
4) Prepare Odin Archive ready for flash
I created a PDA Archive with only boot.img inside.
A command sequence could be, for example:
Code: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
That's All!
Enjoy!7Increase Performance? Oh Yes!
Great Script! Really Interesting!
Good Idea to mix /data outside with some programs still onboard, looking to performance...
At a first glance I like a lot this command:
Code: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;
I achieve the same safe result while data=ordered and barrier=1 are defaults for ext4 mount command and because I compiled ext4 kernel modules with the extended attributes disabled (nouser_xattr).
I surely agree with noatime and nodiratime due to microsd lifecycle troubleshootings, but never set noauto_da_alloc...
...after some readings I figured out that it should be a MUST Option for SSD...
While working of this bunch of code
Code:#-- 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;
I surely upgrade AS SOON AS POSSIBLE the attached boot images to gain performance without loosing stability..
Thanks a Lot!
P.S. Great Idea Again; thanks to Amarullz too.
Actually, anyway, I moved the whole GingerBread outside... I have /data, /system and /cache alltoghether into my microSD...
...that is: "free to experiment! No need to halt and reflash on errors"...
I'll take a look. Please Hold on...6Read Ahead...
Antutu Benchmark Total Result on my Stock ROM with a 4Gb SD Class 4 said about 1650...
After moving (without tuning filesystems...) Antutu Said about 1450...
After Amarullz reading I remounted my filesystem from the shell this way:
Left commit=15 backwards, but I'll put it in the new init.rc of patched boot images... I also set barrier, data order and extended attributes, even if defaults...Code:# 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) #
and Antutu said about 1550...
Actually I'm trying on the fly this tweak
While googling for optimum value...Code:# busybox echo "[b]8192[/b]" > /sys/devices/virtual/bdi/179:0/read_ahead_kb #
And Antutu said about 1600
Now I'm trying to stress the system with heavy loads from/to SDCard...
...Anyway I cannot say anything yet about Battery charge..
...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:
It is safe... Up and running very heavy since last month...
Bottlenecks and lags occurr when I stress /data writing and /system reading while /cache is working... sometimes happens...
As I said somewhere else, if You like to play with your phone dont do it! but...
...if you like (for example) to test firmwares or play around deep inside the system without flashing anything and resuming from errors whenever you want... I call it "a Must Option"
I don't have a fast SD card (now on 4Gb class 4 and very old sailor...) so I cannot compare lags and performance for now with faster memories...
I'm working on this in my spare time... Actually - without flashing anything - I cannot change kernel from one boot to another one, but via init.rc I could start following something written somewhere on /cache or /sdcard...I could - for example - shutdown CM7 saying that I want to boot (next time) to Stock GB and viceversa...
I'm not a True Developer (Long time ago I said "Hello World" to somebody but I don't know if I will be able to do it) but I'm trying to start the system asking to th euser what to do during the boot stage...(Hard Task for me, but why not...)6Challenging and...
STOCK OVERCLOCK ! ! !
...let say "Challenging"...
...and after a short debrief of the Squadzone GitHub Kernel Source repository, I found these differences between Stock and Overclocok kernels:
Differences related to Cpu Clock and Cpufreq Governors...Code:. |-- [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
Now, discarding many others Squadzone patches (really interesting anyway - - - investigating on them later on), I simply replaced these files in Stock Kernel and recompiled it...
NOTICE: I sticked the max boot cpu frequency to 600Mhz
...so you have to install an application like "No Frills CPU" to upraise it after boot...
Here my Galaxy Mini benchmarking at 729Mhz:
What's now?
Modded Images (with Memory Hack and OverClock Stock Kernel) List:
These are "update zip files" to be flashed using CWM or a custom recovery of your choice!
Why don't I cook Odin Archives for these Images? My answer in post n. 152!
Modded OC Images for Galaxy ACE and Galaxy FIT too:
...but I'm waiting feedback on them! I cannot test on my Mini...
P.S. Like usually, here you find the patched files (from Squadzone GitHub repository) that I put into stock kernel tree: kernel_diffs.tar.gz
