OK, here you go, I am making a JTAG adapter PCB for galaxy s. I need to test my pcb, so I bought an as is I9000M from ebay to test my PCB. The phone is in prefect physical condition, except the infamous bootloop problem.
Jump to the steps: http://forum.xda-developers.com/showthread.php?p=16044873#post16044873
Jump to the screen shot of his SD card size: http://forum.xda-developers.com/showthread.php?p=16042946#post16042946
Jump to my progress -> I need some help, I have problem repack kernel Please help me -> http://forum.xda-developers.com/showthread.php?p=16045474#post16045474
Jump to partition SD card on windows: http://forum.xda-developers.com/showthread.php?p=16045880#post16045880
I haven't got my JTAG PCB yet, so i thought, hmm, why not try to fix the phone first? so I spent the last two days, read lots of posts and threads including many many informative posts from this site.... and the conclusion was: it can NOT be fixed.
I have tried many methods, the best method so far I had is to have external SD card plugged in, the flash I900XXJPU using odin, then flash speedmod kernel, after I can boot, I then rooted, and unlocked the phone.
By using this method, in Settings -> SD Card and sorage:
External SD Card:
Total Space: Unavailable
Available Space: Unavailable
Internal SD Card:
Total Space: Unavailable
Available Space: Unavailable
Internal Phone Storage:
Available Space: 1.84GB
The following things work:
1: can make calls or receive calls (using a 7-11 speakout sim card, I think it pigback on Rogers network)
2: can install most apps from market
3: most preinstalled apps work
The following do NOT work:
1: camera
2: video
3: can NOT install any app which require access to /sdcard
I almost gave up, one blog post from coolcode dot org caught my eyes, he has a Korean galaxy S (M110S) with a damaged internal SD card and HE FIXED THE PROBLEM!
this is the original post:
http://www.coolcode.org/?action=show&id=364
It is in Chinese, so I will continue and translate it here...
Before I translate the steps he did, let me post a pic of the fixed phone.
translation:
Internal SD Card:
Total Space: 12.90G
Available Space: 12.90G
Internal Phone Storage:
Available Space: 1.88GB
Available RAM: 98.27MB
{
"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"
}
So his theory is, exchange the mounting point of the internal and external sd card.
His method is different then the posts below:
http://forum.xda-developers.com/showthread.php?t=1088474
and another thread similar to the above but for I9000.
The above methods doesn't completely swap the internal and external sd card. His method involves kernel modification.
ok, this is what he did:
(His was modifying a 2.3.4 VG14 kernel)
Step 1:
Buy a fast micro SD card. Not sure has to be the same size as your internal SD card (I9000M is 16G, I9000 is 8GB), or can be larger. Class 6 or higher is recommended.
Create two partitions, one for /data and one for /sdcard.
partition 1 (mmcblk1p1) is for /sdcard, so it needs to be in FAT32 format.
partition 2 (mmcblk1p2) is for /data, so it needs to be in EXT4 format.
You can format your sd card in Linux or windows. in Windows, you can use Acronis Disk Director Suite.
Step 2:
You need a linux system, any linux is ok, SUSE, Redhat or Ubuntu.
Step 3:
Download samsung arm linux toolchain sdk, can be downloaded from here: http://cs.sch.ac.kr/~choicjy/entry/MV6410-Samsung-Arm-linux-toolchain
Step 4:
untar or unzip then move the whole directory to /usr/local/arm, if you don't have this directory, create it. (why this directory, because one script we will use has hardcoded the above path)
Step 5:
Find the kernel file (zImage) you want to modify (should be in the PDA file if odin format, or inside update directory of the update zip file)
Step 6:
Decompress the zImage file. We need a tool for that. you can download it from https://github.com/mistadman/Extract-Kernel-Initramfs
Step 7:
Run unpack-initramfs zImage, you will get a initramfs_root directory, it contains all the files we need to modify.
Step 8:
Since we need to format /dev/block/mmcblk1p2 to ext4, however, we don't have mkfs.ext4 in initramfs_root, so we need to copy one from http://u.115.com/file/e6yxxut0 , use the same method to decompress zImage to a different directory, then copy mkfs.ext4 from tegrak directory to ROM ? initramfs_root/sbin of the original kernel we are going to modify.
Step 9:
Now, we need to modify the following 5 files:
Code:
init.rc
fota.rc
recovery.rc
res/encryption.conftab
res/recovery.fstab
Step 10:
The theory is to exchange external and internal sd card mounting point. for example, if you see this:
Code:
mount ext4 /dev/block/mmcblk0p2 /data rw nosuid nodev noatime nodiratime wait barrier=1,data=ordered
replace it to:
Code:
mount ext4 /dev/block/mmcblk[SIZE="7"][COLOR="Red"]1[/COLOR][/SIZE]p2 /data rw nosuid nodev noatime nodiratime wait barrier=1,data=ordered
Search mmcblk and replace one by one manually for all 5 files.
Also, there are some lines regarding to
Code:
/sdcard
in fota.rc,res/encryption.conftab and res/recovery.fstab. make sure to change them as well.
in encryption.conftab:
Code:
/ext_sdcard /dev/block/mmcblk1 /dev/mapper/extsdcard sdcard1 vfat PROTECTED_WITH_PASSWORD
replace mmcblk1 to mmcblk0.
Step 11:
add:
Code:
chown root root /sbin/mkfs.ext4
chmod 750 /sbin/mkfs.ext4
after
Code:
chown root root /sbin/fat.format
chmod 750 /sbin/fat.format
They appear in init.rc and recovery.rc. he is not sure if these are needed.. but he added it anyway.
Step 12:
Modify recovery.fstab to format /data in ext4, this is modified content:
Code:
[device]
# mount point fstype device format option mount option
/efs rfs /dev/block/stl3 default default
/system rfs /dev/block/stl9 default default
/dbdata rfs /dev/block/stl10 rfs16 default
/cache rfs /dev/block/stl11 rfs16 default
/sdcard vfat /dev/block/mmcblk1p1 default default
/data ext4 /dev/block/mmcblk1p2 ext4 default
[format]
#index option
rfs16 "/sbin/fat.format -F 16 -s 1 -S 4096"
rfs32 "/sbin/fat.format -F 32 -s 4 -S 4096"
ext4 "/sbin/mkfs.ext4"
[mount]
#index flags options
rfs_opt1 nosuid,noatime,nodev,nodiratime "check=no"
rfs_opt2 ro,nosuid,nodev "check=no"
Step 13:
Now we need to modify vold.fstab and vold.conf. Since they are not in kernel, we need to workaround the problem.
first use adb shell or whatever way to get vold.fstab and vold.conf from system/etc to your pc and swap the mount point:
something like this:
Code:
vold.conf
0. ## vold configuration file for the emulator/SDK
1.
2. volume_sdcard {
3. ## This is the direct uevent device path to the SD slot on the device
4. emu_media_path /devices/platform/goldfish_mmc.2/mmc_host/mmc2
5.
6. media_type mmc
7. mount_point /sdcard
8. ums_path /devices/platform/usb_mass_storage/lun1
9. }
vold.fstab
0. ## Vold 2.0 Generic fstab
1. ## - San Mehat ([email protected])
2. ##
3.
4. #######################
5. ## Regular device mount
6. ##
7. ## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
8. ## label - Label for the volume
9. ## mount_point - Where the volume will be mounted
10. ## part - Partition # (1 based), or 'auto' for first usable partition.
11. ## <sysfs_path> - List of sysfs paths to source devices
12. ######################
13.
14. # sdcard mount for the P1
15. # internal sdcard
16. {
17. ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
18. asec = enable
19. }
20. dev_mount sdcard1 /mnt/sdcard/external_sd 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
21.
22. # externel sdcard
23. {
24. ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
25. discard = disable
26. asec = disable
27. }
28. dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc2
29.
30. #end line ## keep this line
then, copy these two files to initramfs_boot/tmp directory.
search
Code:
mount rfs /dev/block/stl9 /system check=no
in init.rc file, you will see there are a few copy command after that, then you will see this:
Code:
exec umount
add the following after
Code:
exec umount
:
Code:
# switch external mmc & internal mmc
copy /tmp/vold.fstab /system/etc/vold.fstab
copy /tmp/vold.conf /system/etc/vold.conf
so the purpose is to copy these two files from /tmp to /system/etc when system boots.
Step 14:
Now we are done modifying. Time to repack.
First, we need to create initramfs.img file.
create a script in the same directory as the original zImage, lets call it pack-initramfs:
Code:
#/bin/bash
cd initramfs_root
find . | cpio -H newc -o > ../initramfs.img
cd ..
Step 15:
We need another script to do the repack, download from here:
http://forum.xda-developers.com/showthread.php?t=789712
unzip to the same directory as zImage, you will see a directory kernel_repacker is created.
Step 17:
Run:
Code:
./editor.sh ../zImage ../initramfs.img
You will get a new_zImage.
rename it to zImage.
If you just want to flash the kernel, package it in tar format and use odin to flash it:
Code:
tar cvf ExtSD-Kernel-for-M110S-2.3.4-VG14.tar zImage
or put back to the original ROM or update file and flash the whole ROM or update using recovery menu.
OK, I have finished translate of the original blog post. Let me continue with my own progress.
My phone is I9000M from bell.
This is my phone's symptom.
If I place my 16G external SD card in the slot and flash I9000XXJPU ROM, I can boot the system and I can see the following in /dev/block:
Code:
/dev/block/mmcblk0
/dev/block/mmcblk0p1
/dev/block/mmcblk0p2
If I do NOT place external SD card in the slot, after I flash I9000XXJPU, it goes to bootloop. I have to flash the speedmod kernel, after the, system boots, but I do NOT see any files start with mmc in /dev/block.
I think this is different than the blog post.
Anyway, I went ahead and downloaded the JVP update.zip ROM for BELL I9000M from <link to be posted>, extracted zImage from it, now I am stuck at step 17. When I run this command:
Code:
./editor.sh ../zImage ../initramfs.img
I got this error:
Code:
##### My name is ./editor.sh #####
##### The kernel is ../../zImage #####
##### The ramdisk is ../../I9000M.JVP/updates/initramfs.img #####
##### 01. Extracting kernel from ../../zImage (start = 18324)
gzip: stdin: decompression OK, trailing garbage ignored
7034672+0 records in
7034672+0 records out
7034672 bytes (7.0 MB) copied, 32.3349 s, 218 kB/s
##### ERROR : Couldn\\\\\\\'t match start/end of the initramfs .
So I cannot repack the kernel. Anyone can help?
I also have a question, when we flash the ROM (PDA/Kernel, MODEM, CSC files), where are they resides? On good partition of the internal SD card, or a completed different hardware? If it is later, then in theory the method posted in this thread should work for everyone.
This is how to format you sd card in windows:
Anyone has an I9000 with damaged internal SD card? can you please try it out? I am stuck at repack kernel step... :-(
BTW, you need to find the correct kernel for your model.
I asked the blogger why my external sd card showed up as mmcblk0 (not mmcblk1), he said that is for the model of my phone... I am not sure if he is correct, but in my original rc files, I do see the internal device id is mmcblk0.
why system do not see mmcblk0?
OK, I made some progress. I know why kernel_repack failed.
The cpio image in the kernel I have is gzipped. kernel_repack is expecting an uncompressed cpio image, thus it failed.
Now, I need to modify editor.sh in kernel_repack to read gzipped cpio.
Interesting post, good luck mate.
S.U.R.F.A.C.E 2.something
ok, another update.
for some reason, my i9000m decided to shut down, when I power it up again, the internal storage becomes 0.0, so this is the new storage spaces:
External SD Card:
Total Space: 0
Available Space: 0
internal SD Card:
Total Space: Unavailable
Available Space: Unavailable
Internal Phone Storage:
Available Space: 0.0GB
Why?
B: found another script to do the repack of the zimage:
http://forum.xda-developers.com/showthread.php?t=901152
however the script did not work for me:
I always get this error:
./repack-zImage.sh -uv
Warning: there is aready an unpacking directory. If you have files added on
your own there, the repacking result may not reflect the result of the
current unpacking process.
mkdir -p /work/arm/1/zImage_unpacked
cd /work/arm/1/zImage_unpacked
repack-zImage.sh: Can't find a gzip header in file 'zImage'
Terminated
I am using openSUSE 11.2 "Emerald" - Kernel \r (\l).
I tried 2 zImages, one is from
http://derek.theblog.ca/galaxys-i900...rbread-upgrade
(file: http://www.multiupload.com/N8D9XZ1PIF)
and the speedmod kernel speedmod-kernel-k13e-500hz.tar
Both result the same error.
I tried both V6 and V4 of the script, same thing
Anyone can help?
Now I know that you are really investing some time in this but it is a hardware failure so its not really fixed permanently, just permanently rerouted to external sd card?
Aren't even the oldest SGS i9000m's under a year old and thus still under factory warranty (provided you flash a stock rom to it - and then it will not boot).
I know you are supposed to have receipts but I think they can do without also. Have you tried that route or is this just about a challenge?
Will yes, permanently route to external sd card.
I don't have a receipt, yes, I believe it is under one year old, on the back of the machine it has 10.09 printed.
So, how do I get it fixed by Samsung? Call samsung and tell them I lost receipt if they ask? Any recommendations or success stories?
Also, can you please point to me the stock ROM? Since my unit did not start when I got it, I don't know which ROM it has.
Thanks!
BTW, read a few more posts and figured the modified initramfs has to be equal or smaller than the original one. Most custom initrams from xda are already gzipped, thus if I want to add something in initramfs, the size of the initramfs is going to be larger than the original one, thus it won't work... or I need to delete some thing in the initramfs not important (I don't know which to delete), or modify a stock rom, people mention that the stock initramfs is not compressed thus I can add stuff in and gzipped.
Thanks!
gfacer said:
Now I know that you are really investing some time in this but it is a hardware failure so its not really fixed permanently, just permanently rerouted to external sd card?
Aren't even the oldest SGS i9000m's under a year old and thus still under factory warranty (provided you flash a stock rom to it - and then it will not boot).
I know you are supposed to have receipts but I think they can do without also. Have you tried that route or is this just about a challenge?
Click to expand...
Click to collapse
Stock roms are jh2 éclair, jl2 and kc1. The last two need dbdata.rfs to be complete for a flash with repartition ticked or you can flash jh2 with repartition and then the others without as I think it has dbdata.rfs.
And lots of people have gotten warranty without receipts. Read through I9000M links in stickies in general section.
Sent from my GT-I9000M using XDA Premium App
Thanks. called Samsung service number in Montreal around 9AM EST, gave serial number, asked when did I purchase it, I said I purchased 2nd hand, but the machine has 10.09 printed. Rep agreed to repair it for me. I was told that I would receive the instruction in 10 - 30 minutes and a UPS label in 12-24 hours/ However, 3 hours after, I still don't receive any emails from Samsung nor UPS.
Usually how long it takes to receive the instruction email from Samsung? and how long it takes to receive the UPS shipping label?
Should I call them again?
Thanks
Sure why not?
Sent from my GT-I9000M using XDA Premium App
Thanks gfacer!
I got the label later, did not receive any instructions, so I just mailed the phone with battery. I took out my sim card and external sd card.
Hopefully they can receive it tomorrow and I will have the phone back next week!
thanks!
Hey,
I like to mount my external SD Card as ext3 to support large files. The SD Card is formatted with ext3 but now Android shows only an empty folder.
So i tried to remount the SD:
Code:
mount -o rw,remount -t ext3 /dev/block/vold/197:33 /mnt/sdcard/externald_sd
But it doesnt use something... Does anybody has an idea? Some Example or sthing else?
Greetz
FaxXer said:
Hey,
I like to mount my external SD Card as ext3 to support large files. The SD Card is formatted with ext3 but now Android shows only an empty folder.
So i tried to remount the SD:
Code:
mount -o rw,remount -t ext3 /dev/block/vold/197:33 /mnt/sdcard/externald_sd
But it doesnt use something... Does anybody has an idea? Some Example or sthing else?
Greetz
Click to expand...
Click to collapse
u need a kernel that supports ext3. u can ask one of the guys compiling at the moment if they have time to add an ext3 module for u.
May be a stupid question:
would ext4 work instead? I thought the system partition would use this FS.
filesystem is already ext4
wintel_mac said:
May be a stupid question:
would ext4 work instead? I thought the system partition would use this FS.
Click to expand...
Click to collapse
well the system uses ext4 so it should work, but i'm not sure what u're trying to achieve. i use a 16 gb class 10 formatted fat32
Blumdum said:
filesystem is already ext4
Click to expand...
Click to collapse
He's talking about formatting external sd-card
When I get him right, he has a file that exceeds the 4GB FAT32 limit.
So he looks for an alternative to FAT32, which might be some kind of ext*-FS.
wintel your right!
In the Android-Hilfe Forum someone said the system expect first an vfat partition and then the ext. I think thats wrong cause its not working but somehow it has to go.
Hmm should I write these mount command I postet in the init.rc? Or something else. Would be very nice if you post your ideas!
Thanks
init.rc+ ext3 module/object included in kernel
Hmm okay thats good but how do I use them? So I can read and write to my external sd card with an ext3 or ext2 partition.
Thanks
Come on guys where are the great developers?!
Ok I did a test with busybox inbuilt mount, but I tried only with an image.
Not with a real SD card! This worked for me:
On a linux box:
# dd if=/dev/zero of=/tmp/image bs=1M count=1k
# mkfs.ext4 /tmp/image
Copy file to your phone. Then:
On the phone with terminal:
# mkdir /sdcard/mmnt
# busybox mount -o loop /sdcard/image /sdcard/mmnt
To unmount:
# busybox umount -l /sdcard/mmnt
Anybody tried that?
If I understand u right u puting an image file (ext3/4) on the sd and mount that as a virtual disk. Wouldn't the image file be bound to the same restrictoins as other content on a fat32 file system? Like the 4 gig limit!
YOU WILL LOSE ALL DATA ON YOUR SDCARD IF YOUR FDISK
BACKUP WHATEVER IS ON THERE FIRST!!!
YOU'VE BEEN WARNED
using a photon 4g but....
what i did was get an external sdcard reader writer...
(used ubuntu) and let it mount
fdisk device and DELETE ALL PARTITIONS
write
fdisk again
create a linux primary type 83
type mount and grab the /dev/sdcX value (it was /dev/sdc1 for me)
umount that
then
mkfs.ext3 /dev/sdcX ... ( heres the thing though with cyanogen mod 7 kernel 2.6.32.9 SMP PREEMPT)
had to reboot twice for it to be seen in file manager...
its buggy but it does work for the most part
Reviving an old thread, but I just found that I can format a MicroSD under NTFS and it will work with Paragon's NTFS module. At the very least, my phone will mount the drive. I partitioned and formatted it with ext4 on my Linux machine and it didn't recognize it, but I did have it use the GUID partition table. Hoping to be able to load up some videos to take with me.
ext4 sdcard mount works
FaxXer said:
Hey,
I like to mount my external SD Card as ext3 to support large files. The SD Card is formatted with ext3 but now Android shows only an empty folder.
So i tried to remount the SD:
Code:
mount -o rw,remount -t ext3 /dev/block/vold/197:33 /mnt/sdcard/externald_sd
But it doesnt use something... Does anybody has an idea? Some Example or sthing else?
Greetz
Click to expand...
Click to collapse
The problem is with the shell interpreting the special character ":"
To make it work, first create a symlink to the device node:
Code:
ln -s /dev/block/vold/197\:17 /dev/sd2
Then mount it:
Code:
busybox mount /dev/sd2 /mnt/tmp
Code:
sh-4.1# ls -l /dev/sd2
lrwxrwxrwx root root 2013-11-16 14:45 sd2 -> /dev/block/vold/179:17
sh-4.1# mount|grep sd2
/dev/sd2 /mnt/tmp ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
success mounting ext formatted SD Card on Android
An improvement in technique to mount ext formatted SDcard:
1) be root and open terminal
2) insert the card
3) see the block device and partition names from dmesg
4) mount device to location of choice (create the directory if needed)
Below is an example of an SD card with one ext4 partition on it
Code:
bash-4.1# dmesg | tail | grep mmc
<6>[20230.719541] mmc1: new high speed SDHC card at address 0007
<6>[20230.722803] mmcblk1: mmc1:0007 SD32G 29.3 GiB (ro)
<6>[20230.728352] mmcblk1: p1
bash-4.1# busybox mount /dev/block/mmcblk1p1 /data/mnt/sdcard2
tribh said:
An improvement in technique to mount ext formatted SDcard:
1) be root and open terminal
2) insert the card
3) see the block device and partition names from dmesg
4) mount device to location of choice (create the directory if needed)
Below is an example of an SD card with one ext4 partition on it
Code:
bash-4.1# dmesg | tail | grep mmc
<6>[20230.719541] mmc1: new high speed SDHC card at address 0007
<6>[20230.722803] mmcblk1: mmc1:0007 SD32G 29.3 GiB (ro)
<6>[20230.728352] mmcblk1: p1
bash-4.1# busybox mount /dev/block/mmcblk1p1 /data/mnt/sdcard2
Click to expand...
Click to collapse
Would this work just the same way with i9000?
After this, no more access to the extSD by the Windows PC but only with Ubuntu, right?
tetakpatak said:
Would this work just the same way with i9000?
After this, no more access to the extSD by the Windows PC but only with Ubuntu, right?
Click to expand...
Click to collapse
Since it's generic Linux kernel and busybox functionality it should work on any 'droid. The SDcard device name might be different than in the above example - you will see the correct device and partition names after you insert SDcard and run `dmesg | tail` on the tablet or phone.
(of course your device must be rooted and have busybox...)
Typically Windows is engineered not to recognise anything that does not come from Microsoft, so you will not be able to mount the Linux partition via Windows.
Hi all,
after i resize my SD with MiniTool Partition Wizard and create a Linux Swap partition my swap on mobile wan't work. also when i want to create a ext4 for data2sd, it also wan't work -.-
don't have any idea..
Use GingerDX v21 + Alfs v06
safix8 said:
Hi all,
after i resize my SD with MiniTool Partition Wizard and create a Linux Swap partition my swap on mobile wan't work. also when i want to create a ext4 for data2sd, it also wan't work -.-
don't have any idea..
Use GingerDX v21 + Alfs v06
Click to expand...
Click to collapse
hi try this FAT32/EXT2/LINUX SWAP for now
testing only then if work upgrade to ext4
use minitools partition then download userinit.txt
go to this thread
xpraken said:
do this
1) download userinit.txt below to root of sdcard
2) boot into CWM recovery
3)mount /sdcard, /sd-ext (if you have ext partition) and /system
4) run: adb shell
5) move userinit.sh to /sd-ext ->
mv /sdcard/userinit.txt /sd-ext/userinit.sh
6) then,
chmod 755 /sd-ext/userinit.sh
7) reboot
this step will activate the swap without using app like swapper2
Click to expand...
Click to collapse
9) run sdparted: for the differents options see the original thread
This is for my configuration -> sdparted -es 1024M -ss 128M -efs ext3
also when i create partitions with minitool partition?
Swap using terminal emulator:
bash
cd /sdcard
dd if=/dev/zero of=[swap filename] bs=1024k count=[Size in MB]
# E.g. dd if=/dev/zero of=swapfile.swp bs=1024k count=32
# Creates a 32mb empty file called swapfile.swp on sdcard
mkswap [swap filename]
# Formats swap file
[wait at least 30 secs after doing this then]
swapon [swap filename]
# This enables the swap file (NOT swap using Partition)
# [swapoff [swap filename]] (Disable Swap. Be Patient while swap contents are emptied)
----
or if you were looking for partitions...
swapon [Linux swap partition] (/dev/****)
after i successfully parted my sd, moved the userinit tu sd-ext, the Recovery can mount sd-ext.
when i want to boot to rom, it will stuck on Alfs Kernel Boot logo.
i have create an fat32/ext2/swap partition
What do i wrong
{
"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"
}
i'm wondering about people who gets ext and swap work fine.
i work over an week to get swap and ext partition to work -.-
could be the sd card itself be the problem?
safix8 said:
could be the sd card itself be the problem?
Click to expand...
Click to collapse
Safix8 it'a not your fault..it's a problem of kernel..i and few people have this problem..the solution for me is remove the ext partition and for swap partition look here. so, swap work for me..
safix8 said:
9) run sdparted: for the differents options see the original thread
This is for my configuration -> sdparted -es 1024M -ss 128M -efs ext3
also when i create partitions with minitool partition?
Click to expand...
Click to collapse
men this how i work with ext2 and swap (linux swap)
use minitools to partition fat32/ext2/linuxswap
i download the userinit.txt and edit the swappiness to 200 bcoz my linux swap is 257mb
then
poweroff ur phone
boot to cwm or xrecovery
mount /sd-ext and /sdcard
first to know if ur phone is connected
type adb devices
if on the list the phone is connected
next
run adb shell
type this
mv /sdcard/userinit.txt /sd-ext/userinit.sh
and
chmod 755 /sd-ext/userinit.sh
at last reboot
to know the swap is working
goto terminal
type FREE
if swap is 0
is not working
xpraken said:
do this
1) download userinit.txt below to root of sdcard
2) boot into CWM recovery
3)mount /sdcard, /sd-ext (if you have ext partition) and /system
4) run: adb shell
5) move userinit.sh to /sd-ext ->
mv /sdcard/userinit.txt /sd-ext/userinit.sh
6) then,
chmod 755 /sd-ext/userinit.sh
7) reboot
this step will activate the swap without using app like swapper2
Click to expand...
Click to collapse
Sweet! Now I'm able to swap without swapper2. Thanks!
adb shell?where
hajiborojobo said:
adb shell?where
Click to expand...
Click to collapse
read this it may help
ADB
Manage swap over app
Try app resetSwap
"https://market.android.com/details?id=com.guille.resetSwap#?t=W251bGwsMSwxLDIxMiwiY29tLmd1aWxsZS5yZXNldFN3YXAiXQ.." for manage your swap (enable, disable, reset, info..)
it's cool , needn't restart