Related
Well, there was a lot of chatter today about the speed increases on cyanogen's JF-1.51 ROM today, attributed to some changes in the ramdisk (see below). Attached is a boot.img with the same modifications but for Haykuro's 6.0r1 build - go ahead and download it now or read on for more details. Note: you'll only notice a difference if you run your apps/cache from your SD card.
The Changes
The only change is to mount your SD card's ext2 partition with the 'noatime' option. This is exactly what cyanogen did in his JF build, as per his post here. I also added the 'nodiratime' option. This is merely a very minor change in the runme.sh script of the boot ramdisk. [See below for more info on the ext3 mod, added 05/27/09]
By default, ext2 maintains the last access time ('atime') of every file and directory in the filesystem. This means that every time you access (read or write to) a file, this time will be reset and you'll be writing to your SD card. Two problems: 1) SD cards are slow as it is; requiring a write every time you access a file is going slow your whole system down. 2) SD cards fail after enough writes to the same location, so you're reducing your card lifetime by not having these options.
ext3 'auto' mod
Cyanogen added this to his latest build, so again, merely making this available for Haykuro 6.0r1 users. He wrote a bit more detail here which is working reading too.
In short: No other ROMs or app2sd solutions handle a clean shutdown of the ext2 partition, and Android doesn't have fsck tools. The result is that shutting down or crashing can corrupt your ext2 partition and you can lose data. Meanwhile, ext3 is a journaling file system; it recovers gracefully from unclean shutdowns. It's also backwards compatible, you can still mount an ext3 as ext2, you just lose journaling capability.
The mod mounts the 2nd SD partition as type 'auto', which means it will read your existing partition as ext2 and in the future as ext3 if you upgrade. This is more for advanced users but I'll try post some simple instructions below. Make sure you download the boot-haykuro-6.0r1-atime-ext3.zip image.
What about hero? (added 06/06/09)
This is a modded kernel 2.6.29 with unionfs support from daproy. Besides the atime+ext3 stuff, by request I also added support to run /system/init.rc and /data/init.rc (needed by some scripts).
http://turtle.wastelands.net/dragon/...uto-initrc.zip
See also:
1) Daproy's release: http://forum.xda-developers.com/showthread.php?p=3905574#post3905574
2) Release in this thread: http://forum.xda-developers.com/showpost.php?p=3909682&postcount=10
Note: you also need to
1) adb remount
2) push wlan.ko /system/lib/modules
How to apply
Download and unzip the file to get your new boot.img
Option 1:
Code:
adb push boot.img /sdcard
adb shell
# cat /dev/zero > /dev/mtd/mtd2 write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/boot.img
(or mount your SD card, copy the image, and run the above commands in a terminal).
Option 2:
1. Boot into fastboot mode (boot with power+camera)
2. fastboot flash boot boot.img
How to check if it's working
Type 'mount' in an adb shell or your phone's terminal, and look for the 'noatime' and 'nodiratime' option on your ext2 mount point. (If you go ahead with the ext3 mod and upgrade, you'll see it will show up as ext3 in the mount list below).
Code:
$ adb shell
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p2 /system/sd ext2 rw,[b]noatime,nodiratime[/b],errors=continue 0 0 <--
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8 0 0
If things go wrong
If for some reason you can't boot after trying this, you can restore your system simply by reapplying Haykuro's image (boot with power+home and alt-s). Alternatively, I'm attaching the original boot.img as well, which you could reflash with option 2 above.
How to upgrade your ext2 partition to an ext3
I found this really easy on Linux. People can write about alternative methods, but this worked great for me: (substitute /dev/sdb2 below as necessary)
1. Connect to USB and mount your SD card in Android
2. Unmount your ext2 partition from inside linux (e.g. sudo umount /dev/sdb2)
3. sudo tune2fs -j /dev/sdb2 (this adds a journal to the filesystem)
4. adb shell, reboot (or just reboot phone without tapping 'turn off USB storage')
Even though I found this really simple and didn't even bother to make a back up first, I'm really familiar with Linux and linux filesystems -- this should be considered advanced use, and I'm not responsible for you losing your entire ext3 partition.
Note - I agree with cyanogen; I don't think the journal writes is a big performance impact or will wear out your card. This is a relatively small amount of extra data on each write... very low performance/wear impact and for me very worth the benefits.
References
1. Original launch thread of cyanogen's JF 1.51 build
2. Boot Image how to referenced by cyanogen's post
I'm also attaching my compiled versions of mkbootfs and mkbootimg in case anyone wants to play around without downloading and compiling the 2.3 GB Android source.
Worked like a charm thanks man!
This worked perfectly for me! Great job on this; noticable speed improvements for me
Not a great improvement.. Apps are starting circa a second faster..
anyone try this or have a method for Haykuro's Hero build?
boot.img for JACHero r1.4
jroid said:
anyone try this or have a method for Haykuro's Hero build?
Click to expand...
Click to collapse
Which build? I think beta 4 is out yes? I haven't moved over to Hero yet because of the bluetooth issue. Nevertheless, I just made a boot.img for JACHero1.4 - it's untested, but can't imagine it giving any problems... you can always just reapply the update.zip if things go wrong (I still take no responsibility though ). It will probably work with the recent hero builds, let me know how it goes.
I was reffering to the official build he dropped w/ rosie.
thanx I'll give it a shot
confirmed. works on hero build.
very noticeable speed improvement. thanks
# cat /dev/zero > /dev/mtd/mtd2 write: No space left on device
cat /dev/zero > /dev/mtd/mtd2 write: No space left on device
write: No space left on device
# flash_image boot /sdcard/boot.img
flash_image boot /sdcard/boot.img
# mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8 0 0
# reboot
reboot
C:\>adb shell
# mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8 0 0
#
Click to expand...
Click to collapse
confirmation #2 it works on hero w/ Rosie
From another thread:
http://forum.xda-developers.com/showpost.php?p=3905574&postcount=42
daproy said:
Ok I reverted the recent commits to the 2.6.29 tree and camera works fine again and I patched in UnionFS. Sorry for the mess guys. I guess it shows I should have tested it before uploading. I put the kernel zImage in there separate as well in case people wanted to make their own boot.img
http://drop.io/tgbvqky
Click to expand...
Click to collapse
For those that were asking, here are some mods to daproy's great work.
* Mounts the 2nd partition as type 'auto' - ext3 if u have it, else ext2.
* Mounts with noatime and nodiratime options
* Includes appropriate calls to /system/init.rc and /data/init.rc
http://turtle.wastelands.net/dragon/android/hero-boot-unionfs-2-atime-auto-initrc.zip
Kinslayer81 said:
From another thread:
http://forum.xda-developers.com/showpost.php?p=3905574&postcount=42
For those that were asking, here are some mods to daproy's great work.
* Mounts the 2nd partition as type 'auto' - ext3 if u have it, else ext2.
* Mounts with noatime and nodiratime options
* Includes appropriate calls to /system/init.rc and /data/init.rc
http://turtle.wastelands.net/dragon/android/hero-boot-unionfs-2-atime-auto-initrc.zip
Click to expand...
Click to collapse
Hey thanks for the new kernel package.
Simple question.
I had now problem fastbooting the boot.img or adb pushing the wlan.ko but what do I do with the kernel file? Anything, or is it just there in case I want to make changes to the boot or wlan.ko files?
Ext3 on flash media drastically reduces the lifetime because of the frequent writes to the journal, a simple search on google brings up tons of things against the idea, yaffs2 or jffs would be a better decision because it is optimized for flash media and has a journal, not everyone has a class 6 sdhc, and ext3 will cause curruption in any lower class sd, and it will reduce a class's lifetime as well, there is plenty of docs and specs on this, if u prefer speed over reliability/sd lifetime have fun
defconoi said:
Ext3 on flash media drastically reduces the lifetime because of the frequent writes to the journal, a simple search on google brings up tons of things against the idea, yaffs2 or jffs would be a better decision because it is optimized for flash media and has a journal, not everyone has a class 6 sdhc, and ext3 will cause curruption in any lower class sd, and it will reduce a class's lifetime as well, there is plenty of docs and specs on this, if u prefer speed over reliability/sd lifetime have fun
Click to expand...
Click to collapse
This has been discussed ad nauseam.
Even in average high use (compiling the linux kernel!), ext3/journalling with the noatime option results in LESS THAN A 4% INCREASE IN WRITES. Even an abnormal case ('make clean' on the linux kernel, i.e. deleting literally thousands of files) maxed out at a 40% increase, which for deletes really isn't such a big deal. http://thunk.org/tytso/blog/2009/03/01/ssds-journaling-and-noatimerelatime/
Yaffs2, etc, ARE WORSE FOR YOUR SD CARD, which implements it's own hardware anti wear levelling. If you have the hardware and software both swapping around locations, you're doing more work, making things slower, and shortening the life of your card. Flash file systems are contra indicated for SD and other such media.
And it's not about preferring speed over reliability. Ext3 will be slightly slower than ext2, but it's definitely more reliable, because when you shut down, your phone crashes or something else goes wrong, it can recover gracefully instead of YOUR EXT2 PARTITION BECOMING CORRUPT and you losing your data.
I hope this issue is closed now.
ccyrowski said:
Hey thanks for the new kernel package.
Simple question.
I had now problem fastbooting the boot.img or adb pushing the wlan.ko but what do I do with the kernel file? Anything, or is it just there in case I want to make changes to the boot or wlan.ko files?
Click to expand...
Click to collapse
Yea I did the steps with the boot.img and wlan.ko and it appears to be working (noatime and nodiratime are showing). But whats the deal with the kernal file?
sacredsoul said:
Yea I did the steps with the boot.img and wlan.ko and it appears to be working (noatime and nodiratime are showing). But whats the deal with the kernal file?
Click to expand...
Click to collapse
It was included by daproy for ROM developers. I just left it in there to provide the complete package. You can safely ignore it
Kinslayer81 said:
It was included by daproy for ROM developers. I just left it in there to provide the complete package. You can safely ignore it
Click to expand...
Click to collapse
Ah. Thanks man! Enjoying my speedy JACHero Optimized build with this boot.img.
i pushed the wlan and use fastboot to flash the boot.img but when i check with the "mount" command it shows :
i'm using Jac's ROM
/dev/block/mmcblk0p2 /systemsd ext2 rw,errors=continue 00
instead of this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0
I get a wifi unable to start.
ifconfig tiwlan0 in Terminal returns No such device. Any help guys? Yes I tried rebooting already.
EDIT: Posted this on JACHero thread too. Posting here to get more response...
adb remount
adb push wlan.ko /system/lib/modules
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Shanker>cd C:\android-sdk-windows-1.5_r1\tools
C:\android-sdk-windows-1.5_r1\tools>adb remount
remount succeeded
C:\android-sdk-windows-1.5_r1\tools>adb push wlan.ko /system/lib/modules
1117 KB/s (676043 bytes in 0.591s)
C:\android-sdk-windows-1.5_r1\tools>
Click to expand...
Click to collapse
I rebooted and I still cant start wifi. Btw I am using the kinslayer81 boot.img for JACHero 1.4...
namsir said:
i pushed the wlan and use fastboot to flash the boot.img but when i check with the "mount" command it shows :
i'm using Jac's ROM
/dev/block/mmcblk0p2 /systemsd ext2 rw,errors=continue 00
instead of this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0
Click to expand...
Click to collapse
i got the samething.... when i check to see if its working with "mount"
it doesnt show the noatime, nodiratime :\
Kinslayer81 said:
From another thread:
http://forum.xda-developers.com/showpost.php?p=3905574&postcount=42
For those that were asking, here are some mods to daproy's great work.
* Mounts the 2nd partition as type 'auto' - ext3 if u have it, else ext2.
* Mounts with noatime and nodiratime options
* Includes appropriate calls to /system/init.rc and /data/init.rc
http://turtle.wastelands.net/dragon/android/hero-boot-unionfs-2-atime-auto-initrc.zip
Click to expand...
Click to collapse
can we do aufs/unionFS on Haykuro's original hero build? I've got the new boot.img and wlan.ko and ext3 FS, just wondering what I would need to do.
After a sleepy ODIN flash, using SPICA ops with G3 firmware => STUPID??? NO, not done yet , next ODIN flash segment, accidentally stick clear phone EFS via Debug options (DOUBLE CRAZY!!!) NOW i lost the precious IMEI and /efs partitions corrupted as well.
i've got the fixed nv_data.bin and both stl4.img and bml4.img from [email protected] (attached). Thanks for his kindness and supportive to the community!
But even with those i still can't fix the issue!!!! /efs did not mounted via mount command...
as in a GOOD G3, mount command result will be as below:
Code:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/stl6 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl7 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl8 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
[B]/dev/block/stl4 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0[/B]
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,f mask=0702,dmask=0602,allow_utime=0020,codepage=cp4 37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
in my case the bold line just missing... so this is must be the problem.
I tried to do the same as SPICA's method as below:
Code:
$su
#dd if=/sdcard/bml4.img of=/dev/block/bml4
#reboot
It's OK then but...
Code:
$su
#dd if=/sdcard/stl4.img of=/dev/block/stl4
/dev/block/stl4: cannot open for write: Invalid agrument
With this error my /efs cannot be mount... and still missing from the mount command. I'm just a linux noob so pls help me out. How can i restore the stl4 partition properly???
My girlfriend now really mad at me due to she don't have her beloved phone this christmas already. OMG!!!!!
and to all rooted i580x user Pls kindly help compare your "good" /efs folder... maybe mine missing something???? due to one time Erase Phone EFS using Odin Debug Options.
Mine /efs now as below:
Code:
/efs/nv_data.bin
/efs/imei/.nvmac.info
/efs/.files/.dm33 (empty folder)
/efs/.files/.dx1 (empty folder)
/efs/.files/.mp301 (empty folder)
And if you can do adb shell, it'll be very kind of you by sharing your good backup stl4 and bml4 - for research purpose (those partitions did not content any of yours personal data - so PLS HELP!!!). Pls do the backup partions as below and share your img here if possible.
Code:
$su
#cat /dev/block/stl4 > /sdcard/efs_dev-block-stl4.img
#cat /dev/block/bml4 > /sdcard/efs_dev-block-bml4.img
TIA and Best Regards
P/S: when do the ls /dev/block/stl* the stl4 is there but cannot restore using the backup img. it's weird...
Code:
#ls /dev/block/stl*
/dev/block/stl1
/dev/block/stl10
/dev/block/stl2
/dev/block/stl3
/dev/block/stl4
/dev/block/stl5
/dev/block/stl6
/dev/block/stl7
/dev/block/stl8
/dev/block/stl9
same for bml4...
I suggest you remove the images.zip
This contains your IMEI, so anyone can clone it.
Szaby59 said:
I suggest you remove the images.zip
This contains your IMEI, so anyone can clone it.
Click to expand...
Click to collapse
This zip only bml4.img and stl4.img, the fixed nv_data.bin still inside the phone @ SAMSUNG SC . Now they still can not redo IMEI yet so i must find someway else.
kenblat said:
This zip only bml4.img and stl4.img, the fixed nv_data.bin still inside the phone @ SAMSUNG SC . Now they still can not redo IMEI yet so i must find someway else.
Click to expand...
Click to collapse
fixed ur phone yet? noob idea: can u try flashing but this time with the right ops?
were you able solve the problem? I am facing exactly same problem.
after flashing CW3.0.2.4 what are we on RFS or EXT4 TY
...bump...
Paleryder said:
after flashing CW3.0.2.4 what are we on RFS or EXT4 TY
Click to expand...
Click to collapse
Looks like EXT4. If you use adb, you can:
adb shell
mount
In the middle of the output, you might see:
Code:
/dev/block/platform/s3c-sdhci.0/by-name/system /system [B]ext4[/B] ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data [B]ext4[/B] rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
Paleryder said:
after flashing CW3.0.2.4 what are we on RFS or EXT4 TY
Click to expand...
Click to collapse
I'm pretty sure that would be Ext4.
Sent from my Nexus S 4G using XDA App
Paleryder said:
after flashing CW3.0.2.4 what are we on RFS or EXT4 TY
Click to expand...
Click to collapse
Before flashing you are ext4 - rfs is not used on the Nexus S.
/efs and /cache are still yaffs2 while /data and /system are ext4
krohnjw said:
Before flashing you are ext4 - rfs is not used on the Nexus S.
/efs and /cache are still yaffs2 while /data and /system are ext4
Click to expand...
Click to collapse
Does anyone know if the original nexus s has mtd6?
Uncle Jimmy says hello
snandlal said:
Does anyone know if the original nexus s has mtd6?
Uncle Jimmy says hello
Click to expand...
Click to collapse
mtdblock6 is /efs
Sent from my Nexus S using XDA Premium App
i just updated to XXLE4 yesterday from cm9
followed the usual process KPE(twice)>XXLE4(twice)
everything was working well but after a reboot i got nasty hangups so i switched off and put my phone in charging
i removed from charginig an hour later and switched on
the phone went to recovery said DELETING CRYPTION DATA and rebooted
since then it showed NO SD CARD in file manager, and UNKNOWN in settings for both internal sd and external sd
i tried factory data reset and wiping partition cache , but i got boot loop
also everytime in recovery it said copying media files
i tried reflashing XXLE4 but again boot loop
i finally flashed full kpe but again boot loop
in recovery this is what the dialogue is
E:failed to mount /data (no such file or directory)
--copying media files...
E :failed to mount /sdcard (file exists)
E :copy_cache_media :cant mount /sdcard
your storage not prepared yet.please use ui menu for format and reboot actions.
Media file copy failed
and the rest was usual manual mode
applying multi csc.....
when wiping data it says
--wiping data..
formatting /data...
E:format_volume : rfs format failed on /dev/block/mmcblk0p3
formatting /dbdata..
formatiing /cache..
data wipe failed
also i inserted my external sd card in my pc to check and it showed 11.7 of 11.7gb free
whereas it was about 9gb full and is and 16gb card
so is my sd card f****ed too ?
so is this real bad like service centre bad(no warranty)?
any solutions?
try flash a .pit to make a repartition, and then try flashing a froyo stock rom, then ginger / value pack ginger
frapeti said:
try flash a .pit to make a repartition, and then try flashing a froyo stock rom, then ginger / value pack ginger
Click to expand...
Click to collapse
i tried with the pit file of xxkpe and flashed xxkpe but again i got boot loop
you are saying i use the pit file of xxkpe(ginger) and flash a froyo rom?
Now this is called a soft brick (no service center needed), but the fact that all these issues even after reflashing xxkpe are still there is worrying.
Are you sure you are doing all the steps correctly?
Try xxkpe with .pit (twice - the pit part once) --> XXKPQ
If that doesn't work then i can't help any further.
Skander1998 said:
Now this is called a soft brick (no service center needed), but the fact that all these issues even after reflashing xxkpe are still there is worrying.
Are you sure you are doing all the steps correctly?
Try xxkpe with .pit (twice - the pit part once) --> XXKPQ
If that doesn't work then i can't help any further.
Click to expand...
Click to collapse
yes pretty sure i followed everything correctly
but no success
now i am really worried
akashsgpgi said:
yes pretty sure i followed everything correctly
but no success
now i am really worried
Click to expand...
Click to collapse
E:format_volume : rfs format failed on /dev/
block/mmcblk0p3
From this line I can say that I think ur internal sd card is broken which is really a serous issue. But I have flashed my phone 100 times but flashing never causes curruption of internal sd card.
akashsgpgi said:
i tried with the pit file of xxkpe and flashed xxkpe but again i got boot loop
you are saying i use the pit file of xxkpe(ginger) and flash a froyo rom?
Click to expand...
Click to collapse
I think there's only one .pit file... but i can confirm that doing a flash of Froyo, then into GB, can fix some issues. I haven't had this problem in particular, though.
boot loop with froyo
any idea how much will the repairs would cost in india
Try hard reset dude.. samseng service center is the last resort
Sent from my GT-I9003 using XDA
Ave666 said:
Try hard reset dude.. samseng service center is the last resort
Sent from my GT-I9003 using XDA
Click to expand...
Click to collapse
by hardreset u mean factory data reset+wiping cache partition?
or reflashing xxkpe with?
i have tried both
even tried froyo
Are you still able to boot into recovery or download mode.
If yes, then you still have some chance to recover your device, yourself.
As a last resort consider doing this.
If you could boot into download, then install any custom Kernel, so as to have root priviledge
and a good bash environment in recovery.
Now boot into recovery and check filesystem type of each partition, if it is correct.
And then try formatting them by yourself.
Here is my partition table information. (for Cyanogenmod9 alpha6 ROM)
Code:
[email protected]:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 248564 32 248532 0% /dev
df: /mnt/.lfs: Function not implemented
/dev/block/stl11 31484 4148 27336 13% /cache
tmpfs 248564 0 248564 0% /mnt/asec
tmpfs 248564 0 248564 0% /mnt/obb
/dev/block/stl9 326552 270852 55700 83% /system
/dev/block/mmcblk0p3 1935128 257784 1677344 13% /data
/dev/block/stl10 74072 4148 69924 6% /dbdata
/dev/block/stl3 6064 5155 909 85% /efs
/dev/block/vold/179:17
3870240 3794432 75808 98% /mnt/emmc
/dev/block/vold/179:1
1595136 1340832 254304 84% /mnt/sdcard
/dev/block/vold/179:1
1595136 1340832 254304 84% /mnt/secure/asec
/dev/block/dm-0 6236 4424 1812 71% /mnt/asec/com.teamviewer.teamviewer.market.mobile-2
/dev/block/dm-1 6236 4508 1728 72% /mnt/asec/com.natenai.glowhockey-2
1|[email protected]:/ # mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
/dev/block/stl11 on /cache type ext4 (rw,nodev,noatime,nodiratime,commit=20,barrier=1,nobh,data=ordered,noauto_da_alloc)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl9 on /system type ext4 (ro,noatime,commit=20,barrier=1,nobh,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p3 on /data type ext4 (rw,noatime,commit=20,barrier=1,nobh,data=ordered,noauto_da_alloc)
/dev/block/stl10 on /dbdata type ext4 (rw,noatime,commit=20,barrier=0,nobh,nodelalloc,data=ordered,noauto_da_alloc)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437)
debugfs on /debug type debugfs (rw,relatime)
/dev/block/vold/179:17 on /mnt/emmc type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.teamviewer.teamviewer.market.mobile-2 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/com.natenai.glowhockey-2 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
[email protected]:/ #
akashsgpgi said:
by hardreset u mean factory data reset+wiping cache partition?
or reflashing xxkpe with?
i have tried both
even tried froyo
Click to expand...
Click to collapse
yes i will try a custom kernel as soon i return from school
i tried to recover using cwm recovery but it did not work
any idea how much would it cost for repair at samsung service centre
my pocket money is roasted
akashsgpgi said:
i tried to recover using cwm recovery but it did not work
any idea how much would it cost for repair at samsung service centre
my pocket money is roasted
Click to expand...
Click to collapse
u need to change motherboard.
vishal24387 said:
u need to change motherboard.
Click to expand...
Click to collapse
any idea vishal bhaiyya how much that would cost ox10)
akashsgpgi said:
any idea vishal bhaiyya how much that would cost ox10)
Click to expand...
Click to collapse
No idea buddy. But surely it is really costly. But I will say that try in every possible way. I think in general section there is a thread regarding solution for this. May 3-4 pages back u will get that thread.
Edit :---
This will help u
http://translate.google.com/transla...es/2012/05/la-resurreccion-del-i9003.html?m=1
Try this also
http://forum.xda-developers.com/showthread.php?t=1241574
vishal24387 said:
No idea buddy. But surely it is really costly. But I will say that try in every possible way. I think in general section there is a thread regarding solution for this. May 3-4 pages back u will get that thread.
Edit :---
This will help u
http://translate.google.com/transla...es/2012/05/la-resurreccion-del-i9003.html?m=1
Try this also
http://forum.xda-developers.com/showthread.php?t=1241574
Click to expand...
Click to collapse
thank you , tomorrow i try my best and as always will revert to xda for any help require
after panicking now i am relaxed
abaout hard reset. Its not just factory data reset. Open up your case, in the middle of the camera and the speaker there is soo tiny hole. You use hairpin or any pointed material to push it. Just read in an article before i forgot. Try it. Not bad for trying for yours is already soft bricked. Just try.\\
EDIT- i forgot the real step but that is the hard reset i think FOR THE READERS PLEASE CORRECT ME IF IM WRONG JUST TRYING TO HELP THE GUY with all the possibilities. Try it with power on/off or while pushing both home or power i dont know try everything with this button.
I remembered it, pushing it while doing the download mode combo.
akashsgpgi said:
i tried with the pit file of xxkpe and flashed xxkpe but again i got boot loop
you are saying i use the pit file of xxkpe(ginger) and flash a froyo rom?
Click to expand...
Click to collapse
the .pit file is the same for any rom, I think it just have info about the partitions and how to do them, just flash latona_20110114.pit, remove the battery, and then, make sure u have a working stock rom, I use XXKC1 ie, if it stills with errors I think its a serious issue
frapeti said:
the .pit file is the same for any rom, I think it just have info about the partitions and how to do them, just flash latona_20110114.pit, remove the battery, and then, make sure u have a working stock rom, I use XXKC1 ie, if it stills with errors I think its a serious issue
Click to expand...
Click to collapse
Everyone said that already, if you have something new to add, go on, if everything is already said, don't post..
Hi !
So...that's my questition. My phone is SGS and i want to check in what file system the /data partition is formatted. Is there any way to do it ?
Thanks in advance, guys !
Open a shell (either install a terminal app or connect via USB and run "adb shell" on your computer) and run the command "mount". This will give you a list of all mounted filesystems. Look for the one mounted to /data.
For example, for my I9505, it reads:
Code:
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
This means my /data is an Ext4 partition.
Open the terminal and run the command
Code:
mount
you will see how and where all partitions are mounted.
For data partition, in my phone, it shows up
Code:
/dev/block/mmcblk0p9 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
that means /data is mounted as ext4