Hi guys,
I few days back i rooted my samsung galaxy gio S5660 (froyo 2.2.1) and explored its file system. I was surprised to know that there wasn't any /efs directory unlike most of the galaxy s variants. Here's how it looked
PHP:
drwxr-xr-x root root 2011-05-19 11:20 acct
dr-x------ root root 2011-05-19 11:20 config
drwxrwx--- system cache 2011-05-19 11:20 cache
drwxrwx--x system system 2011-05-19 11:20 data
drwxr-xr-x root root 2011-05-19 13:42 dev
drwxr-xr-x root root 1970-01-01 12:03 lib
drwxrwxr-x root system 2011-05-19 11:20 mnt
lrwxrwxrwx root root 2011-05-19 11:20 d -> /sys/kernel/debug
lrwxrwxrwx root root 2011-05-19 11:20 etc -> /system/etc
drwxrwx--x system system 2011-05-19 11:20 persist
drwxr-xr-x root root 2011-05-19 11:20 system
drwxr-xr-x root root 1970-01-01 12:03 sys
drwxr-x--- root root 1970-01-01 12:03 sbin
lrwxrwxrwx root root 2011-05-19 11:20 sdcard -> /mnt/sdcard
dr-xr-xr-x root root 1970-01-01 12:03 proc
drwx------ root root 2011-03-18 13:19 root
-rwxr-x--- root root 17250 1970-01-01 12:03 init.rc
-rwxr-x--- root root 3301 1970-01-01 12:03 init.qcom.sh
-rwxr-x--- root root 1116 1970-01-01 12:03 init.qcom.rc
-rwxr-x--- root root 2016 1970-01-01 12:03 init.qcom.post_boot.sh
-rwxr-x--- root root 1512 1970-01-01 12:03 init.goldfish.rc
-rwxr-x--- root root 101828 1970-01-01 12:03 init
-rw-r--r-- root root 224 1970-01-01 12:03 default.prop
-rw-r--r-- root root 10014 1970-01-01 12:03 GIO.rle
Does any body has some insights into it ?? It seems like playing with the nv_data.bin file is not an option any more !!!
Related
Hello,
I've been looking into the issue with WiFi tethering and one interesting thing I've noticed is in the /etc/firmware directory there are two bcm4329.bin files.
Code:
ls -l
-rw-r--r-- root root 9220 2010-04-29 01:47 yamato_pm4.fw
-rw-r--r-- root root 173082 2010-04-29 01:47 Supersonic_20100204_Sprint_Jack_324016_v2.acdb
-rw-r--r-- root root 137911 2010-04-29 01:47 default.acdb
-rw-r--r-- root root 15336 2010-04-29 01:47 BCM4329B1_002.002.023.0360.0361.hcd
-rw-r--r-- root root 137911 2010-04-29 01:47 MFG.acdb
-rw-r--r-- root root 241820 2010-04-29 01:47 fw_bcm4329.bin
-rw-r--r-- root root 239616 2010-04-29 01:47 fw_bcm4329_ap.bin
-rw-r--r-- root root 1156 2010-04-29 01:47 yamato_pfp.fw
One is suffixed with _ap. This to me stands for access point.
I don't know that much about how these firmware files work, but the fact there is two of them makes me suspicious.
Sprint's built in tethering app has no problem with the wireless interface, but the free ones do. What could be the solution?
hi,
could someone please send me the following files of FW 10.4.4.25 WW. i've lost root, don't want to unlock and need to take a look at those config/startup files:
Code:
-rw-r----- root root 616 1970-01-01 01:00 fstab.cardhu
-rwxr-x--- root root 109284 1970-01-01 01:00 init
-rwxr-x--- root root 3012 1970-01-01 01:00 init.00.rc
-rwxr-x--- root root 3012 1970-01-01 01:00 init.01.rc
-rwxr-x--- root root 3012 1970-01-01 01:00 init.02.rc
-rwxr-x--- root root 4020 1970-01-01 01:00 init.03.rc
-rwxr-x--- root root 3046 1970-01-01 01:00 init.04.rc
-rwxr-x--- root root 4136 1970-01-01 01:00 init.05.rc
-rwxr-x--- root root 3012 1970-01-01 01:00 init.07.rc
-rwxr-x--- root root 3012 1970-01-01 01:00 init.0b.rc
-rwxr-x--- root root 3012 1970-01-01 01:00 init.0c.rc
-rwxr-x--- root root 3012 1970-01-01 01:00 init.0d.rc
-rwxr-x--- root root 16632 1970-01-01 01:00 init.cardhu.rc
-rwxr-x--- root root 2344 1970-01-01 01:00 init.goldfish.rc
-rwxr-x--- root root 17081 1970-01-01 01:00 init.rc
-rwxr-x--- root root 244 1970-01-01 01:00 init.tf.rc
-rwxr-x--- root root 1637 1970-01-01 01:00 init.trace.rc
-rwxr-x--- root root 4150 1970-01-01 01:00 init.usb.rc
furthermore, also please a standard directory listing (one level is enough, not recursive) of:
/data/
tx!
I don't know what you want to do with the kernel's initramfs files, but anyway, here they are:
View attachment ramdisk.tar.gz
And a fairly fresh /data directory contains:
Code:
app
app-asec
app-private
backup
cal.bin
dalvik-cache
data
dontpanic
drm
fw_update_progress
gps
lightsensor
local
lost+found
media
misc
modem
nvcam
property
resource-cache
sensors
ssh
system
tf
user
thanks very much! i want to take a look at how parts of the boot process work.
Hi to all!
I post my question here hoping it is the correct place.
I would like to create a link in the /mnt/sdcard directory of my tablet to the place where usb and sdcard are mounted (namely the /Removable directory).
I've tried to create the link using adb shell but with no result at the moment.
This is the situation on my Asus me301t tablet:
Code:
ls -all
drwxr-xr-x root system 2013-12-08 15:49 Removable
drwxr-xr-x root root 2013-12-08 15:49 acct
drwxrwx--- system cache 2013-12-08 16:54 cache
dr-x------ root root 2013-12-08 15:49 config
lrwxrwxrwx root root 2013-12-08 15:49 d -> /sys/kernel/debug
drwxrwx--x system system 2013-12-08 15:49 data
-rw-r--r-- root root 116 1970-01-01 01:00 default.prop
drwxr-xr-x root root 2013-12-08 15:49 dev
lrwxrwxrwx root root 2013-12-08 15:49 etc -> /system/etc
-rw-r----- root root 718 1970-01-01 01:00 fstab.cardhu
-rwxr-x--- root root 113524 1970-01-01 01:00 init
-rwxr-x--- root root 3012 1970-01-01 01:00 init.0b.rc
-rwxr-x--- root root 15918 1970-01-01 01:00 init.cardhu.rc
-rwxr-x--- root root 2487 1970-01-01 01:00 init.goldfish.rc
-rwxr-x--- root root 18247 1970-01-01 01:00 init.rc
-rwxr-x--- root root 244 1970-01-01 01:00 init.tf.rc
-rwxr-x--- root root 1795 1970-01-01 01:00 init.trace.rc
-rwxr-x--- root root 4150 1970-01-01 01:00 init.usb.rc
drwxrwxr-x root system 2013-12-08 15:49 mnt
dr-xr-xr-x root root 1970-01-01 01:00 proc
drwx------ root root 2013-04-19 08:42 root
drwxr-x--- root root 1970-01-01 01:00 sbin
lrwxrwxrwx root root 2013-12-08 15:49 sdcard -> /storage/emulated/legacy
d---r-x--- root sdcard_r 2013-12-08 15:49 storage
drwxr-xr-x root root 2013-12-08 15:49 sys
drwxr-xr-x root root 1970-01-01 01:00 system
-rw-r--r-- root root 2520 1970-01-01 01:00 ueventd.cardhu.rc
-rw-r--r-- root root 272 1970-01-01 01:00 ueventd.goldfish.rc
-rw-r--r-- root root 4024 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx root root 2013-12-08 15:49 vendor -> /system/vendor
So /Removable is a directory.
The same is not true for the /mnt/sdcard
Code:
[email protected]:/mnt $ ls -all
drwxr-xr-x root system 2013-12-08 15:49 asec
drwxr-xr-x root system 2013-12-08 15:49 obb
lrwxrwxrwx root root 2013-12-08 15:49 sdcard -> /storage/emulated/legacy
drwx------ root root 2013-12-08 15:49 secure
drwx------ shell shell 2013-12-08 15:49 shell
Moreover also /storage/emulated/legacy is a link
Code:
[email protected]:/storage/emulated $ ls -all
lrwxrwxrwx root root 2013-12-08 15:49 legacy -> /mnt/shell/emulated/0
The /mnt/shell/emulated/0 is a real directory and these are the owner and permission of the directory which constitute that path:
Code:
[email protected]:/mnt/shell/emulated/0 $ cd ..
[email protected]:/mnt/shell/emulated $ ls -all
drwxrwxr-x root sdcard_rw 2013-12-08 16:17 0
drwxrwxr-x root sdcard_rw 2013-08-29 12:55 legacy
drwxrwxr-x root sdcard_rw 2013-08-29 12:54 obb
[email protected]:/mnt/shell/emulated $ cd ..
[email protected]:/mnt/shell $ ls -all
drwxrwxr-x root sdcard_rw 2013-08-29 12:55 emulated
[email protected]:/mnt/shell $ cd ..
[email protected]:/mnt $ ls -all
drwxr-xr-x root system 2013-12-08 15:49 asec
drwxr-xr-x root system 2013-12-08 15:49 obb
lrwxrwxrwx root root 2013-12-08 15:49 sdcard -> /storage/emulated/legacy
drwx------ root root 2013-12-08 15:49 secure
drwx------ shell shell 2013-12-08 15:49 shell
I've tried to create the link and I obtain the following error:
Code:
ln -s /Removable/ /mnt/shell/emulated/0/Removable
link failed Function not implemented
Is it possible to create such a link without being root?
Otherwise is it possible to get root access only temporarily so that to create such a link or whichever is required to obtain the same functionality (removable sdcard and usb should be visible under /mnt/sdcard).
Thank you for your help,
Xwang
UP, please.
Xwang
UP!
Can anybody help me, please?
Xwang
Since there isn't a T-mobile specific thread, I figure it'd be a good place to start.
For more info, see the T-Mobile variant thread I created.
Code:
[email protected]:/ $ ls -al
drwxr-xr-x root root 2013-12-31 20:56 .system
drwxr-xr-x root root 2013-12-31 20:56 acct
drwxrwx--- system cache 2014-04-27 01:16 cachedr-x------ root root 2013-12-31 20:56 config
lrwxrwxrwx root root 2013-12-31 20:56 d -> /sys/kernel/debug
drwxrwx--x system system 2014-04-26 10:32 data
-rw-r--r-- root root 255 1969-12-31 19:00 default.prop
drwxr-xr-x root root 2014-04-25 15:11 dev
drwxrwx--x system radio 2014-04-25 13:20 efs
lrwxrwxrwx root root 2013-12-31 20:56 etc -> /system/etc
-rw-r--r-- root root 23967 1969-12-31 19:00 file_contexts
dr-xr-x--- system system 2013-12-31 20:56 firmware
dr-xr-x--- system system 2013-12-31 20:56 firmware-modem
-rw-r----- root root 1833 1969-12-31 19:00 fstab.qcom
-rwxr-x--- root root 566100 1969-12-31 19:00 init
-rwxr-x--- root root 4262 1969-12-31 19:00 init.carrier.rc
-rwxr-x--- root root 879 1969-12-31 19:00 init.container.rc
-rwxr-x--- root root 1346 1969-12-31 19:00 init.environ.rc
-rwxr-x--- root root 1702 1969-12-31 19:00 init.mdm.sh
-rwxr-x--- root root 7064 1969-12-31 19:00 init.qcom.class_core.sh
-rwxr-x--- root root 6788 1969-12-31 19:00 init.qcom.early_boot.sh
-rwxr-x--- root root 11239 1969-12-31 19:00 init.qcom.factory.sh
-rwxr-x--- root root 26062 1969-12-31 19:00 init.qcom.rc
-rwxr-x--- root root 2742 1969-12-31 19:00 init.qcom.ril.sh
-rwxr-x--- root root 7248 1969-12-31 19:00 init.qcom.sh
-rwxr-x--- root root 4561 1969-12-31 19:00 init.qcom.ssr.sh
-rwxr-x--- root root 3554 1969-12-31 19:00 init.qcom.syspart_fixup.sh
-rwxr-x--- root root 44934 1969-12-31 19:00 init.qcom.usb.rc
-rwxr-x--- root root 7766 1969-12-31 19:00 init.qcom.usb.sh
-rwxr-x--- root root 46647 1969-12-31 19:00 init.rc
-rwxr-x--- root root 2890 1969-12-31 19:00 init.ril.rc
-rwxr-x--- root root 3572 1969-12-31 19:00 init.ril.sh
-rwxr-x--- root root 12023 1969-12-31 19:00 init.target.rc
-rwxr-x--- root root 1795 1969-12-31 19:00 init.trace.rc
-rwxr-x--- root root 3915 1969-12-31 19:00 init.usb.rc
drwxrwxr-x root system 2013-12-31 20:56 mnt
drwxr-xr-x system system 2013-12-31 20:56 persdata
drwxrwx--x system system 2013-12-31 19:00 persist
dr-xr-xr-x root root 1969-12-31 19:00 proc
-rw-r--r-- root root 3567 1969-12-31 19:00 property_contexts
-rw-r--r-- root root 1509 1969-12-31 19:00 publiccert.pem
drwx------ root root 2014-03-26 00:28 root
drwxr-x--- root root 1969-12-31 19:00 sbin
lrwxrwxrwx root root 2013-12-31 20:56 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 7300 1969-12-31 19:00 seapp_contexts
-rw-r--r-- root root 1712341 1969-12-31 19:00 sepolicy
-rw-r--r-- root root 236 1969-12-31 19:00 sepolicy_version
drwxr-x--x root sdcard_r 2013-12-31 20:56 storage
dr-xr-xr-x root root 2013-12-31 20:56 sys
drwxr-xr-x root root 2013-12-31 19:04 system
drwxr-xr-x root system 2014-04-25 15:11 tmp-mksh
lrwxrwxrwx root root 2013-12-31 20:56 tombstones -> /data/tombstones
-rw-r--r-- root root 8849 1969-12-31 19:00 ueventd.qcom.rc
-rw-r--r-- root root 17983 1969-12-31 19:00 ueventd.rc
lrwxrwxrwx root root 2013-12-31 20:56 vendor -> /system/vendor
As you can see this one looks very similar to the G900F variant.
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name $ ls -al <
lrwxrwxrwx root root 2013-12-31 20:56 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-12-31 20:56 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-12-31 20:56 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-12-31 20:56 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-12-31 20:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2013-12-31 20:56 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-12-31 20:56 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-12-31 20:56 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-12-31 20:56 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-12-31 20:56 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-12-31 20:56 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-12-31 20:56 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-12-31 20:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-12-31 20:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-12-31 20:56 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-12-31 20:56 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-12-31 20:56 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-12-31 20:56 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-12-31 20:56 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-12-31 20:56 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-12-31 20:56 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-12-31 20:56 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-12-31 20:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-12-31 20:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-12-31 20:56 userdata -> /dev/block/mmcblk0p25
MallardDuck said:
Since there isn't a T-mobile specific thread, I figure it'd be a good place to start.
Click to expand...
Click to collapse
FYI, there is a T-Mobile S5 forum. Not sure if you want to post there instead.
BLuFeNiX said:
FYI, there is a T-Mobile S5 forum. Not sure if you want to post there instead.
Click to expand...
Click to collapse
Whoops, I had no clue; thanks for the heads up.
:highfive:
I'll leave this one here just for spreading information; this is my first Samsung device, so I'm a little new to how their specific feature/device classifying works. I assumed that all the S 5 devices were on one forum, since the only device trees i've found on github are a unified device.
I have access to what appears to be a Samsung J7 2016 with stock ROM.
I've noticed that the root of my filesystem contains various fstab and init files relating to qemu, ranchu, and goldfish. While some things are commented outz others are not.
Is this normal? Is there any simple way to absolutely verify this is not some sort of emulated environment? I saw some stuff from dexterlabs but I'm not setup with an environment to build from source for Android right now.
If this is normal, can anybody explain why a ROM destined for mass hardware deployment would be cluttered with useless files like this?
I admit that I am new here and this might be a stupid question, but I did search and did not easily find any good answers.
[email protected]:/ $ ls -la
drwxr-xr-x root root 2017-10-05 15:10 .system
drwxr-xr-x root root 2017-10-05 15:10 acct
drwxrwx--- system cache 2017-01-01 00:02 cache
dr-x------ root root 2017-10-05 15:10 config
drwxrwx--x radio system 2016-06-08 17:03 cpefs
lrwxrwxrwx root root 2017-10-05 15:10 d -> /sys/kernel/debug
drwxrwx--x system system 2017-10-05 15:11 data
-rw-r--r-- root root 681 1969-12-31 16:00 default.prop
drwxr-xr-x root root 2017-10-05 15:10 dev
drwxrwx--x radio system 2017-09-23 21:48 efs
lrwxrwxrwx root root 2017-10-05 15:10 etc -> /system/etc
lrwxrwxrwx root root 2017-10-05 15:10 factory -> /data/app
-rw-r--r-- root root 134186 1969-12-31 16:00 file_contexts
-rw-r----- root root 935 1969-12-31 16:00 fstab.goldfish
-rw-r----- root root 831 1969-12-31 16:00 fstab.ranchu
-rw-r----- root root 1231 1969-12-31 16:00 fstab.samsungexynos7580
-rwxr-x--- root root 813940 1969-12-31 16:00 init
-rwxr-x--- root root 1383 1969-12-31 16:00 init.baseband.rc
-rwxr-x--- root root 424 1969-12-31 16:00 init.carrier.rc
-rwxr-x--- root root 3221 1969-12-31 16:00 init.container.rc
-rwxr-x--- root root 1355 1969-12-31 16:00 init.environ.rc
-rwxr-x--- root root 2551 1969-12-31 16:00 init.goldfish.rc
-rwxr-x--- root root 1411 1969-12-31 16:00 init.ranchu.rc
-rwxr-x--- root root 60959 1969-12-31 16:00 init.rc
-rwxr-x--- root root 173 1969-12-31 16:00 init.rilcarrier.rc
-rwxr-x--- root root 1056 1969-12-31 16:00 init.rilchip.rc
-rwxr-x--- root root 1010 1969-12-31 16:00 init.rilcommon.rc
-rwxr-x--- root root 440 1969-12-31 16:00 init.rilepdg.rc
-rwxr-x--- root root 22837 1969-12-31 16:00 init.samsungexynos7580.rc
-rwxr-x--- root root 13316 1969-12-31 16:00 init.samsungexynos7580.usb.rc
-rwxr-x--- root root 1921 1969-12-31 16:00 init.trace.rc
-rwxr-x--- root root 9283 1969-12-31 16:00 init.usb.configfs.rc
-rwxr-x--- root root 6484 1969-12-31 16:00 init.usb.rc
-rwxr-x--- root root 3306 1969-12-31 16:00 init.wifi.rc
-rwxr-x--- root root 342 1969-12-31 16:00 init.zygote32.rc
drwxrwxr-x root system 2017-10-05 15:10 knox_data
drwxr-xr-x root root 1969-12-31 16:00 lib
drwxr-xr-x root system 2017-10-05 15:10 mnt
drwxr-xr-x root root 1969-12-31 16:00 oem
drwxr-xr-x system system 2017-10-05 15:10 persdata
-rw-r--r-- root root 2088 1969-12-31 16:00 postrecovery.do
drwxrwx--x system system 2017-10-05 15:10 preload
dr-xr-xr-x root root 1969-12-31 16:00 proc
-rw-r--r-- root root 22354 1969-12-31 16:00 property_contexts
-rw-r--r-- root root 1509 1969-12-31 16:00 publiccert.pem
drwx------ root root 2017-06-05 22:43 root
drwxr-x--- root root 1969-12-31 16:00 sbin
lrwxrwxrwx root root 2017-10-05 15:10 sdcard -> /storage/self/primary
-rw-r--r-- root root 11653 1969-12-31 16:00 seapp_contexts
-rw-r--r-- root root 776858 1969-12-31 16:00 sepolicy
-rw-r--r-- root root 487 1969-12-31 16:00 sepolicy_version
-rw-r--r-- root root 37997 1969-12-31 16:00 service_contexts
drwxr-xr-x root root 2017-10-05 15:11 storage
dr-xr-xr-x root root 2017-10-05 15:10 sys
drwxr-xr-x root root 2017-01-01 00:00 system
-rw-r--r-- root root 323 1969-12-31 16:00 ueventd.goldfish.rc
-rw-r--r-- root root 272 1969-12-31 16:00 ueventd.ranchu.rc
-rw-r--r-- root root 5298 1969-12-31 16:00 ueventd.rc
-rw-r--r-- root root 7114 1969-12-31 16:00 ueventd.samsungexynos7580.rc
lrwxrwxrwx root root 2017-10-05 15:10 vendor -> /system/vendor
[email protected]:/ $