[ROM][2.3.2] I9000XWJV1 (GINGERBREAD) for Galaxy S

Search This thread

ikanikolai

Senior Member
Oct 15, 2010
217
22
Budapest
There's driver for ext4 but using rfs (WTF Samsung?)

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
 

Northern.dj

Senior Member
Nov 14, 2010
155
15
My god 70 pages this is nearly as bad as the Vodafone thread which was 75 pages i think :eek:
Keep posting the first page as this is so big now
 

TettZor

Senior Member
Aug 5, 2010
152
22
Hallabro
I have seen many complaints in this thread and I just realized that this must be the "gingerbeard" that indian guy tweeted about... hehe...

Sent from my GT-I9000 using XDA App
 

iammodo

Senior Member
Mar 12, 2008
1,656
543
hell
I have seen many complaints in this thread and I just realized that this must be the "gingerbeard" that indian guy tweeted about... hehe...

Sent from my GT-I9000 using XDA App

Can't see there problem its working amazingly for beta it's fast and almost everything works.

Sent from my GT-I9000 using XDA App
 

Markyyyyyyyyy

Senior Member
Jan 28, 2011
125
44
Help please, i'm using adb to flash the res file, however i am getting the following


C:\Users\Mark>adb shell
$ su
su
$ mount -o rw,remount /dev/block/st19 /system
mount -o rw,remount /dev/block/st19 /system
mount: Operation not permitted
$
 

theduckking

Senior Member
Aug 16, 2010
383
97
@Lorbas

Since the summary grows and changes, you could link to it so that I can maintain it up to date:D
 

jul8887

Member
May 17, 2010
34
6
...

not bad, i´m waiting for a real release, since this 2.3.2 is too beta for me, i´ll stay on darkys rom until he shows a new one on gingerbread base... hopefully he´ll insert the nice effects of gingerbread for eyecandy :D
 

iammodo

Senior Member
Mar 12, 2008
1,656
543
hell
Help please, i'm using adb to flash the res file, however i am getting the following


C:\Users\Mark>adb shell
$ su
su
$ mount -o rw,remount /dev/block/st19 /system
mount -o rw,remount /dev/block/st19 /system
mount: Operation not permitted
$

First make sure you have root.
This is on the first page of the thread on the first post.

once you have that try su with your phone screen on the home page you should get a super user request then it will change from $ to #

good luck
 

zacharias.maladroit

Recognized Developer
There's driver for ext4 but using rfs (WTF Samsung?)

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

weird Samsung proprietary closed filesystem stuff

How it Works: (If you are curious)
The boot logo is stored /dev/block/stl6 which is mounted in /mnt/.lfs/ on the file system. By typing 'mount' in a terminal you can see it is mounted as a j4fs file system. From what I understand in my research is that j4fs is a closed source type of file system and is not well documented. Also you might notice it is mounted 'rw' but this is only partially true. You CAN create a NEW file in /mnt/.lfs/ but you can NOT delete or modify an existing file in that partition. So how do we get replace that logo.jpg to our custom image? We don't replace it. Instead I used a hex editor on the DK28 stock param.lfs file and changed every instance of '6C 6F 67 6F 2E 6A 70 67' to '6C 30 67 30 2E 6A 70 67' What this did is change the logo.jpg file name to l0g0.jpg. This allows us to flash that modified param.lfs and put a new logo.jpg on that partition. This same method could be used to replace the other files you can see in the /mnt/.lfs/ folder. Ideally I would have liked to delete the original jpg file all together but after many many different attempts, I couldn't find a way to do so. I'm also a noob when it comes to hex editing (this was my first time) so I don't posses the knowledge to do it that way nor do we know enough about the j4fs to make it happen.

(source)
 
Last edited:

sedinix

Senior Member
Feb 22, 2009
317
17
There's driver for ext4 but using rfs (WTF Samsung?)

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

BETA understood ?
 

markdj57

Senior Member
Oct 16, 2010
569
44
Belfast
www.stronge.org.uk
Well I finally got back to 2.2.1. Had to flash JPU and then JS5 to get going again.

MAPS, GPS and COMPASS
While I had 2.3, the compass worked really smoothly and using the maps I could spin the phone and the map would rotate really true to my direction of pointing, so that is improved alot and that's without any calibration.

GPS fix was very quick considering I was inside too, about 20 seconds.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,222
3,018
ykkfive.blogspot.com
The boot logo is stored /dev/block/stl6 which is mounted in /mnt/.lfs/ on the file system. By typing 'mount' in a terminal you can see it is mounted as a j4fs file system

the boot logo is stored in /dev/block/stl6 and mounted as /mnt/.lfs/ j4fs in froyo also

the stl6 is somehow for handling reboot options. i've tried to mount it as ro, and moved it to /system without mounting stl6, but the result was, u could not reboot normally as usual. it kept rebooted in recovery mode if ur last mode was recovery, and booted up in normal mode if it was b4. so probably some data were written in this parition, perhaps the boot option BCB
 

Top Liked Posts