Related
After a reboot all of the apps (excluding system apps) and information stored in the phone gets either reset or deleted after flashing 2.2
Sent from my SCH-I400 using XDA App
lincoln3823 said:
After a reboot all of the apps (excluding system apps) and information stored in the phone gets either reset or deleted after flashing 2.2
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
The cached info doesn't. That's why it's a great idea to wipe data prior to loading Froyo for the first time.
Sent from my SCH-I400 using XDA App
i did but every single time my phone dies or i power it off everything gets reset every single time
lincoln3823 said:
i did but every single time my phone dies or i power it off everything gets reset every single time
Click to expand...
Click to collapse
What version of CWM are you using? My guess is yellow. If so, use cyan CWM.
Sent from my SCH-I400 using XDA App
Can you please type this in adb :
Adb shell mount
Then upload your results....
Sent from my SCH-I400 using XDA Premium App
C:\Users\comp>adb shell mount
rootfs / rootfs rw 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
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 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,i
set=utf8 0 0
/dev/block/mmcblk0p1 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,g
d/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data/fota rfs rw,nosuid,nodev,relatime,vfat,llw,check
id/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/
wx,iocharset=utf8 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noati
diratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=
,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,
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,code
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
im using the Cyan CWM
Please help me to fix this. What ever ROM I install, it says Memory Full. Even tried installing the stock rom again.
This is what I see when I wipe cache from CWM (G3 MOD 2.0)
-- Wiping Cache --
Formatting CACHE...
E:Can't mount /dev/block/stl8
(File exists)
Error mounting /cache/!
Skipping format...
Cache wipe complete.
Thanks in advance.
Did you convert your partitions to ext??
yes.. I tried converting to ext4. But now again i tried flashing stock rom. Still issue occurs.
Please help me.
pmanian said:
Please help me.
Click to expand...
Click to collapse
convert it to ext2 and retry.
I had similar problem when i start convert to JFS in G3MOD Kernel but when i convert to ext2 (fs.convert) everything work ok. If you have access to adb shell you could try
mkfs.ext2 /dev/block/stl8
try mount in adb shell and post in thread.
This is the output of my mount.. The cache partition is not in ext4. Still issue occurs.. Please help.
# mount
mount
rootfs / rootfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl7 /intdata ext2 rw,nosuid,nodev,nodiratime,relatime,errors=continue 0 0
/dev/block/stl7 /data ext2 rw,nosuid,nodev,nodiratime,relatime,errors=continue 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl6 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl8 /cache rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl4 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
I think I had fixed. Flashed I5801DXJPC ROM and then flash again the I5800XXJPS. It's fixed now.
Hey everyone,
This is pretty embarrassing... I successfully ran the following:
Code:
mount -w -t vfat /dev/block/mmcblk0p12 /mnt/sdcard
But now I cannot revert back to the original mount point of "/sdcard"
I've even tried umount-ing with the force-flag and still no luck
I'd appreciate any help at all, thanks
It *might* revert when you reboot unless you overwrote something.
Why are you screwing with this anyways?
Thanks for the quick reply.
Rebooting didn't change it.
Edit: Below is fixed, no longer relevant
Except, now I'm noticing I have to root with SuperOneClick each time I reboot to get su access.
The only thing I did after running the mount command, was install BusyBox
Wait, what? Since when does Kindle Fire have an SD Card? I'm so confused
jasongw said:
Wait, what? Since when does Kindle Fire have an SD Card? I'm so confused
Click to expand...
Click to collapse
There's an "sdcard" partition. It's whats mounted when you attach your KF to your PC... But no, there's no removable SD Card
Not sure 100% what the correct command to remount the sdcard partition is so can't say much right now.
check under /proc/mounts and also under /proc/emmc (open them as a text file) and paste what it says.
Didn't see a /proc/emmc but here's what I found
Contents of /proc/mounts:
Code:
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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/splash /dropbox ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:12[B][COLOR="Red"] /mnt/sdcard[/COLOR][/B] 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 0 0
/dev/block/vold/179:12 /mnt/secure/asec 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 0 0
tmpfs[B][COLOR="Red"] /mnt/sdcard/[/COLOR][/B].android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.angrymobgames.muffinknight3rdparty-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I hope you can solve your problem,good luck
looks like you need to mount /dev/block/vold/179:12 so rerun the command you were doing with that instead.
I installed Astro File Manager, through which I can view the sdcard partition's contents in "/sdcard" as well as "/mnt/sdcard"
I only seem to have issues viewing contents of location "/sdcard" in adb shell.
At this point I'm not too terribly concerned about it. Maybe I'm making a deal out of nothing...
I do appreciate your help though.
And if anyone knows the exact solution, then please speak up
EDIT:
Returns nothing:
Code:
ls /sdcard
Returns contents:
Code:
cd /sdcard
ls
I guess nothing was ever wrong after all.. Now I feel extra-dumb
Hi everybody,
i have a galaxy S4 korean version E300L, i been trying to install on it a custom rom of a korean gs4 i9500 through CWM, everything went smooth till i came to discover that there's no signal and the baseband is unknown and the IMEI is blank! and before doing so i made sure to backup my rom and also the efs partition with a dd command using the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/efs and here's the 20mb efs backup if anybody can tell me how to use it:
http://www.4shared.com/file/Ajc7gjXB/efs.html
because trying to restore that backup using dd command like that:
[email protected]:/ # dd if=/sdcard/efs of=/dev/block/mmcblk0p3
dd if=/sdcard/efs of=/dev/block/mmcblk0p3
40960+0 records in
40960+0 records out
20971520 bytes transferred in 4.253 secs (4930994 bytes/sec)
[email protected]:/ # reboot
reboot
as you can see everything goes well but when i check /efs using root explorer the partition would be the same, a blank folder with few recreated files by the system with no nv-data.bin files., so please can you suggest anything to restore my wiped efs partition? i tried to restore the cwm backup many times but it didn't work, and here's the partition table:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,
data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,errors=panic,data=ordere
d 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_
checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journ
al_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journa
l_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p14 /tombstones ext4 rw,seclabel,nosuid,nodev,noatime,data=ord
ered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /dev/memcgrp cgroup rw,relatime,memory 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1
023 0 0
[email protected]:/ #
yakie47 said:
Hi everybody,
i have a galaxy S4 korean version E300L, i been trying to install on it a custom rom of a korean gs4 i9500 through CWM, everything went smooth till i came to discover that there's no signal and the baseband is unknown and the IMEI is blank! and before doing so i made sure to backup my rom and also the efs partition with a dd command using the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/efs and here's the 20mb efs backup if anybody can tell me how to use it:
http://www.4shared.com/file/Ajc7gjXB/efs.html
because trying to restore that backup using dd command like that:
[email protected]:/ # dd if=/sdcard/efs of=/dev/block/mmcblk0p3
dd if=/sdcard/efs of=/dev/block/mmcblk0p3
40960+0 records in
40960+0 records out
20971520 bytes transferred in 4.253 secs (4930994 bytes/sec)
[email protected]:/ # reboot
reboot
as you can see everything goes well but when i check /efs using root explorer the partition would be the same, a blank folder with few recreated files by the system with no nv-data.bin files., so please can you suggest anything to restore my wiped efs partition? i tried to restore the cwm backup many times but it didn't work, and here's the partition table:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,
data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,errors=panic,data=ordere
d 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_
checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journ
al_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journa
l_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p14 /tombstones ext4 rw,seclabel,nosuid,nodev,noatime,data=ord
ered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /dev/memcgrp cgroup rw,relatime,memory 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1
023 0 0
[email protected]:/ #
Click to expand...
Click to collapse
Wrong forum.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
First: Questions go in Q&A
Second: make sure you are in the correct forum for your device
Moved to International S4 and Q&A
FNM
sir, it is not enough to backup only efs partition in s4, you must backup also m9kefs1, 2 and 3 partitions
http://forum.xda-developers.com/showthread.php?t=2284357
samersh72 said:
sir, it is not enough to backup only efs partition in s4, you must backup also m9kefs1, 2 and 3 partitions
http://forum.xda-developers.com/showthread.php?t=2284357
Click to expand...
Click to collapse
what about the CWM back up i have? is there any chance to extract those hidden partitions from it? if my Korean version has that same divided into 4 efs partition?
yakie47 said:
what about the CWM back up i have? is there any chance to extract those hidden partitions from it? if my Korean version has that same divided into 4 efs partition?
Click to expand...
Click to collapse
efs and m9kefs partitions are not a part of the firmware, they are not flashed with it
samersh72 said:
efs and m9kefs partitions are not a part of the firmware, they are not flashed with it
Click to expand...
Click to collapse
you mean that those m9kefs blocks are not part of the system so cwm would never back'em up then..?
and what's the size of each one of those m9kefs blocks in your gs4, for me after making those m9kefs partitions backups i got 4mb size in each one of them as for the main one: /dev/block/mmcblk0p3 partition, it was 20mb, and cheking them with an hex editor they don't seem like an efs partition similar to the gs2 or the gs3 only the 20mb /dev/block/mmcblk0p3 partition that contains some information that seem to have something to do with the efs partition data, and here's a link to one of those partitions check it out yourself:
http://www.mediafire.com/download.php?cwrbz26cdowowuk
yakie47 said:
you mean that those m9kefs partitions are not part of the system so cwm would never backed'em up then..?
and what's the size of each one of those m9kefs partitions in your gs4, for me after making those m9kefs partitions backups i got 4mb size in each one of them as for the main one: /dev/block/mmcblk0p3 partition, it was 20mb, and cheking them with an hex editor they don't seem like an efs partition similar to the gs2 or the gs3 only the 20mb /dev/block/mmcblk0p3 partition that contains some information that seem to have something to do with the efs partition data, and here's a link to one of those partitions check it out yourself:
http://www.mediafire.com/download.php?cwrbz26cdowowuk
Click to expand...
Click to collapse
yes
right size.
those EFS partitions that need to be secured for the S4.
m9kefs contain NV_DATA files
EDIT: in S2 & S3 all are included in efs partition
samersh72 said:
efs and m9kefs partitions are not a part of the firmware, they are not flashed with it
Click to expand...
Click to collapse
samersh72 said:
yes
right size.
those EFS partitions that need to be secured for the S4.
m9kefs contain NV_DATA files
EDIT: in S2 & S3 all are included in efs partition
Click to expand...
Click to collapse
well.. good to know that even though it's too late!
Hi,
May I ask you a link to your efs partition? I might have an idea to fix your device (and in the same time, getting access to an exynos s4 efs might help me adding support to galaxsim unlock)
I believe the link is above, hope you could find a way to restore that efs.bin file.
Sent from my SHV-E300L using xda premium
Hello, since yesterday I can't write anything om my external memory-card (sdcard0) anymore. No idea what caused this
CM: nightly 24.11.2014 (happens also on older builds until 16.11.)
Mounts (recorded with the mount command via terminal):
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data_root ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkHD-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/ginlemon.flowerpro-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/vold/179:27 /mnt/media_rw/sdcard0 ext4 ro,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,data=ordered 0 0
/dev/block/vold/179:27 /mnt/secure/asec ext4 ro,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-2 /mnt/asec/com.sonny.lpi.frost2-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
Hmmm - I hope I did provide enough information ...
I'm wondering whether it is possible to unmount /mnt/media_rw/sdcard0 in a terminal and mount it again with read-write enabled?
Not sure how to proceed and a bit anxious about it as well since I don't know enough about Android despite working with Linux since 20 years
I guess your filesystem is corrupted. Please post dmesg logs.
Here's the dmesg.log -> https://gist.github.com/wimstefan/7af22e19b6ff408a7c22
Thanks for looking into it!
If needed I also can provide the logcat I took this afternoon ...
yep ur filesystem is corrupted. The weird thing is, that errors should be fixed on each boot.
you could reboot to recovery and run "e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system" from a shell.
m11kkaa said:
yep ur filesystem is corrupted. The weird thing is, that errors should be fixed on each boot.
you could reboot to recovery and run "e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system" from a shell.
Click to expand...
Click to collapse
Oh I see
Well running the command above seems not to do that much:
Code:
# e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/msm_sdcc.1/by-name/system: 1944/32768 files (0.5% non-contiguous), 106443/131072 blocks
Same happens with system1 ... but that's not where the errors in dmesg are listed or am I completely wrong now? I see some fs errors passing dmesg regarding device mmcblk0p27 which is /dev/block/platform/msm_sdcc.1/by-name/storage. Running the e2fsck command on that device was a completely different story! A lot of errors and corrections ... the filesystem was modified at the end and after a reboot it is mounted writable again!
So THANK YOU VERY MUCH for pushing me in the right direction !!! :highfive: :victory:
Hopefully everything is alright again and I can continue to enjoy my MI2S
yeah sorry I meant storage. stupid copy&paste errors