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.
Related
Does anyone has by any chance the mount points table for the N915F?
Thank you.
Instruction
starbucks2010 said:
Does anyone has by any chance the mount points table for the N915F?
Thank you.
Click to expand...
Click to collapse
If you can instruct me - I'll do it.
I tried with (adb shell) cat /proc/partitions and cat /proc/mounts but I don't know which partition is which mmcblk.
I checked also in fstab file but the mount point information is missing from it.
PS. Finaly I found out. If anyone need it:
lrwxrwxrwx root root 2014-01-10 11:07 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-10 11:07 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-10 11:07 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-10 11:07 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-01-10 11:07 dbi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-10 11:07 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-10 11:07 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-10 11:07 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-10 11:07 hidden -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-10 11:07 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-10 11:07 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-10 11:07 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-10 11:07 param -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-10 11:07 persdata -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-10 11:07 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-10 11:07 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-10 11:07 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-10 11:07 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-10 11:07 sbl1bak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-10 11:07 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-10 11:07 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-10 11:07 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-10 11:07 userdata -> /dev/block/mmcblk0p27
Good luck.
does anyone knows which mount point is for "data": mmcblk0p26 (hidden) or mmcblk0p27 (userdata)?
thank you
Here's some info from the N915T
Code:
lrwxrwxrwx 1 root root 20 Jan 3 2014 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 3 2014 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 3 2014 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 3 2014 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 Jan 3 2014 dbi -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 3 2014 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jan 3 2014 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 3 2014 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefsc -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 3 2014 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 3 2014 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 3 2014 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 3 2014 param -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 3 2014 persdata -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 3 2014 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 3 2014 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Jan 3 2014 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 3 2014 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 3 2014 sbl1bak -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 3 2014 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 3 2014 system -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 3 2014 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 3 2014 userdata -> /dev/block/mmcblk0p26
Hi,
I would like to know if anyone here owned an Asian version of S6?
Is it any different from the international version?
thanks
Yes it speaks Chinese.
only support TD-LTE
Sent from my unknown using XDA Free mobile app
Is this version bootloader locked? Can it be rooted at the moment?
The HK version GM-9200 dual sim which also supports TD-LTE and is sold in China too is boot locked and there is no root yet for the new firmware. I suggest you to buy this phone rather than G9208. G9200 supports all LTE Bands and might be better.
can.
[email protected]:/dev/block/platform/15570000.ufs/by-name # ll
ll
lrwxrwxrwx root root 2015-04-21 14:57 BOOT -> /dev/block/sda8
lrwxrwxrwx root root 2015-04-21 14:57 BOTA0 -> /dev/block/sda1
lrwxrwxrwx root root 2015-04-21 14:57 BOTA1 -> /dev/block/sda2
lrwxrwxrwx root root 2015-04-21 14:57 CACHE -> /dev/block/sda19
lrwxrwxrwx root root 2015-04-21 14:57 DNT -> /dev/block/sda13
lrwxrwxrwx root root 2015-04-21 14:57 EFS -> /dev/block/sda3
lrwxrwxrwx root root 2015-04-21 14:57 OTA -> /dev/block/sda10
lrwxrwxrwx root root 2015-04-21 14:57 PARAM -> /dev/block/sda7
lrwxrwxrwx root root 2015-04-21 14:57 PERSDATA -> /dev/block/sda16
lrwxrwxrwx root root 2015-04-21 14:57 PERSISTENT -> /dev/block/sda14
lrwxrwxrwx root root 2015-04-21 14:57 RADIO -> /dev/block/sda11
lrwxrwxrwx root root 2015-04-21 14:57 RECOVERY -> /dev/block/sda9
lrwxrwxrwx root root 2015-04-21 14:57 SBFS -> /dev/block/sda17
lrwxrwxrwx root root 2015-04-21 14:57 STEADY -> /dev/block/sda15
lrwxrwxrwx root root 2015-04-21 14:57 SYSTEM -> /dev/block/sda18
lrwxrwxrwx root root 2015-04-21 14:57 TOMBSTONES -> /dev/block/sda12
lrwxrwxrwx root root 2015-04-21 14:57 USERDATA -> /dev/block/sda20
lrwxrwxrwx root root 2015-04-21 14:57 m9kefs1 -> /dev/block/sda4
lrwxrwxrwx root root 2015-04-21 14:57 m9kefs2 -> /dev/block/sda5
lrwxrwxrwx root root 2015-04-21 14:57 m9kefs3 -> /dev/block/sda6
Is there any update on Nougat availability for this S6 version?
Sprint Galaxy Note 5 SM-N920P Partition Table
credits @rlmiller for helping retrieve this
lrwxrwxrwx root root 2015-08-30 20:02 BOOT -> /dev/block/sda7
lrwxrwxrwx root root 2015-08-30 20:02 BOTA0 -> /dev/block/sda1
lrwxrwxrwx root root 2015-08-30 20:02 BOTA1 -> /dev/block/sda2
lrwxrwxrwx root root 2015-08-30 20:02 CACHE -> /dev/block/sda17
lrwxrwxrwx root root 2015-08-30 20:02 CARRIER -> /dev/block/sda18
lrwxrwxrwx root root 2015-08-30 20:02 DNT -> /dev/block/sda12
lrwxrwxrwx root root 2015-08-30 20:02 EFS -> /dev/block/sda3
lrwxrwxrwx root root 2015-08-30 20:02 OTA -> /dev/block/sda9
lrwxrwxrwx root root 2015-08-30 20:02 PARAM -> /dev/block/sda6
lrwxrwxrwx root root 2015-08-30 20:02 PERSDATA -> /dev/block/sda15
lrwxrwxrwx root root 2015-08-30 20:02 PERSISTENT -> /dev/block/sda13
lrwxrwxrwx root root 2015-08-30 20:02 RADIO -> /dev/block/sda10
lrwxrwxrwx root root 2015-08-30 20:02 RECOVERY -> /dev/block/sda8
lrwxrwxrwx root root 2015-08-30 20:02 STEADY -> /dev/block/sda14
lrwxrwxrwx root root 2015-08-30 20:02 SYSTEM -> /dev/block/sda16
lrwxrwxrwx root root 2015-08-30 20:02 TOMBSTONES -> /dev/block/sda11
lrwxrwxrwx root root 2015-08-30 20:02 USERDATA -> /dev/block/sda19
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs1 -> /dev/block/sda4
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs2 -> /dev/block/sda5
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs3 -> /dev/block/sdd1
Hello!
I have a moto g xt1033 dual sim BR. It goes into fastboot mode but accepts no recording. I believe he is not with usb mode debbugin enabled, as in recovery mode (stock recovery) adb does not recognize ..
when I do a wipe, message me:
blkdiscard on partition failed /dev/block/platform/msm_sdcc.1/by-name/userdata
I can do the adb recognize him as recovery with the following command:
fastboot boot openrecovery-TWRP-2.8.1.0-xt1032.img
he gets the M on the screen and can enter the shell mode.
the adb shell, can not see the partitions:
/dev/block/platform/msm_sdcc.1/by-name # ls -la
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx root root 1970-01-01 06:08 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 06:08 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 06:08 abootBackup -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 06:08 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 06:08 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 06:08 cid -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 06:08 clogo -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 06:08 dhob -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 06:08 fsc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 06:08 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 06:08 hob -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 06:08 kpan -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 06:08 logo -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 06:08 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 06:08 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 06:08 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 06:08 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 06:08 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 06:08 padA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 06:08 padB -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 06:08 pds -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 06:08 persist -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 06:08 recovery -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 06:08 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 06:08 rpmBackup -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 06:08 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 06:08 sdi -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 06:08 sdiBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 06:08 sp -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 06:08 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 06:08 system -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 06:08 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 06:08 tzBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 06:08 userdata -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 06:08 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 06:08 utagsBackup -> /dev/block/mmcblk0p15
I am not presenting solution because I decided not to. but it can help someone with more knowledge in the area ...
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]:/ $