Database Info

[Info] Galaxy S 5 SM-G900T Partition Table

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.

[Q] N915F mounting points

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

Asia Versin S6 SM-G9208

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?

LG v20 H990DS partitions table and unlock bootloader Discussion

Hi guys, Lg v20 H990DS partitions table. We have fastboot shell so unlock is possible. for me the right way is work like in thsi thread
http://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882
total 0
drwxr-xr-x 2 root root 1440 2016-01-01 01:00 .
drwxr-xr-x 4 root root 1620 2016-01-01 01:00 ..
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 OP -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 aboot -> /dev/block/sde6
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 abootbak -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 apdp -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 boot -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 cache -> /dev/block/sda15
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 cdt -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 cmnlib -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 cmnlib64 -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 cmnlib64bak -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 cmnlibbak -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 cust -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 ddr -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 devcfg -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 devcfgbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 devinfo -> /dev/block/sdb6
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 dip -> /dev/block/sdb5
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 dpo -> /dev/block/sde28
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 drm -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 eksst -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 encrypt -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 factory -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 fota -> /dev/block/sdb3
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 fsc -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 fsg -> /dev/block/sdb4
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 grow -> /dev/block/sda19
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 grow2 -> /dev/block/sdb7
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 grow3 -> /dev/block/sdc3
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 grow4 -> /dev/block/sdd5
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 grow5 -> /dev/block/sde29
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 grow6 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 grow7 -> /dev/block/sdg2
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 hyp -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 hypbak -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 keymaster -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 keymasterbak -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 keystore -> /dev/block/sda11
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 laf -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 lafbak -> /dev/block/sda13
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 misc -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 modem -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 mpt -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 msadp -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 persist -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 persistent -> /dev/block/sdg1
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 pmic -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 pmicbak -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 raw_resources -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 raw_resourcesbak -> /dev/block/sde9
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 rct -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 recovery -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 recoverybak -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 reserve -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 rpm -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 rpmbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 sec -> /dev/block/sde19
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 sns -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 spare1 -> /dev/block/sdd4
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 spare2 -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 ssd -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 system -> /dev/block/sda14
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 tz -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 tzbak -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 2016-01-01 01:00 userdata -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 xbl2 -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 xbl2bak -> /dev/block/sdc2
lrwxrwxrwx 1 root root 15 2016-01-01 01:00 xblbak -> /dev/block/sdb2

Official LG reply
Hello,
Currently, you can only unlock the bootloader for LG G4/G5/V10 for the European market as below.
- H815 (G4) for the European market
- H850 (G5) for the European market
- H960A (V10) for Android M and the European market (Except France)
We are considering supporting bootloader unlocking for V20, but details such as support range of V20 about bootloader unlocking have yet to be determined.
If there are any changes to the supported devices, we will let you know via our website.
Best regards,
LG Developer site Team

Secret hidden menu (dialer code) is
*#546368#*990#

this is interesting mate.
I am thinking of getting the V20 (DS as i need dual sim) , but i am worried about the lack of devs on it. I honestly just need TWRP and Root. So if you tell me you are some weeks away of making it happen. I'll jump on the wagon with you. But I guess we need to wait on LG to release the bootloader unlocking.

raimondomartire said:
Secret hidden menu (dialer code) is
*#546368#*990#
Click to expand...
Click to collapse
What can you do whilst in this menu? I can't see a bootloader unlock in there?

SAO said:
this is interesting mate.
I am thinking of getting the V20 (DS as i need dual sim) , but i am worried about the lack of devs on it. I honestly just need TWRP and Root. So if you tell me you are some weeks away of making it happen. I'll jump on the wagon with you. But I guess we need to wait on LG to release the bootloader unlocking.
Click to expand...
Click to collapse
Until now I think is possible. It's only question of when we will have it

raimondomartire said:
Until now I think is possible. It's only question of when we will have it
Click to expand...
Click to collapse
Normally if we ask a lot they will provide for the bootloader. As the Root what do you think?

SAO said:
Normally if we ask a lot they will provide for the bootloader. As the Root what do you think?
Click to expand...
Click to collapse
Yeah. Ask @raimondomartire exactly where he's gone to post the question from the webite and we can all ask individually? The more the better. Get behind the movement!!
The initial post makes no sense to me, as i'm obviously not that technical.
I just hope it's NOT a methond that's not as silly as the one released for the G4, or dual sim variant of that model - rooting *EVERY SINGLE* individual system image. For example, my phone came with v10e software, so it needed to be extracted, then rooted. Oh wait a month on, i need to download, root and then inject v10f (and so on). Or are we only able to root this way?
Those (legitimately) willing to contribute to the bounty of unlocking this, please post and contribute here:
http://forum.xda-developers.com/v20/how-to/bounty-thread-lg-v20-root-h990ds-t3493062
RoOSTA

deleted, sorry

speculatrix said:
just adding a link to here:
https://forum.xda-developers.com/v20/how-to/bounty-thread-lg-v20-root-h990ds-t3493062
Click to expand...
Click to collapse
That link was already posted on the post above yours.

Updates?
Update: found the root link: https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296/
Hi There,
Is there any successes, or failure scenarios reported about this Lg v20 H990DS recently?
I just got mine and realised, this is not the officially unlockable V20 version

[URGENT] Requesting Bootloader dump image for HD 10 (2017)?

Hi, I want to (urgently) investigate the bootloader internals of recent Fire devices, so please provide me with a bootloader dump in Fire HD 10 (2017). Here's how to get it;
Get into an ADB command prompt/terminal.
Type the commands in this order;
Code:
adb shell
Code:
su
Code:
cd /dev/block/bootdevice/by-name
Code:
ls -all
Try to find the bootloader image, this is kind of hard. It's usually named as 'aboot'. If you fail to find that then please copy paste the result of the last command, I will try to guess what it is.
If you somehow notices the correct one, look at the text in front of it, in form of "/dev/block/****", and type;
Code:
dd if=/dev/block/**** of=/sdcard/Download/aboot.img
Of course replace the stars with your partition.
(aboot.img works universally I think because the dump name doesn't matter, if that doesn't work, replace aboot.img with [YOUR-ABOOT-ALTERNATIVE].img replacing with the bootloader image text you found above).
Upload the resulting .img file in a post in this thread quickly as possible!
Thank you!

I'm not very good at this, but I can try to help. Not sure which file(s) to grab.
I got the following in /dev/block/platform/soc/by-name
lrwxrwxrwx root root 2018-02-22 22:47 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-02-22 22:47 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2018-02-22 22:47 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2018-02-22 22:47 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-02-22 22:47 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-02-22 22:47 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-02-22 22:47 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-02-22 22:47 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-02-22 22:47 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-02-22 22:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-02-22 22:47 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-02-22 22:47 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2018-02-22 22:47 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-02-22 22:47 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-02-22 22:47 userdata -> /dev/block/mmcblk0p15

luvboox said:
I'm not very good at this, but I can try to help. Not sure which file(s) to grab.
I got the following in /dev/block/platform/soc/by-name
lrwxrwxrwx root root 2018-02-22 22:47 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-02-22 22:47 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2018-02-22 22:47 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2018-02-22 22:47 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-02-22 22:47 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-02-22 22:47 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-02-22 22:47 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-02-22 22:47 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-02-22 22:47 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-02-22 22:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-02-22 22:47 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-02-22 22:47 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2018-02-22 22:47 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-02-22 22:47 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-02-22 22:47 userdata -> /dev/block/mmcblk0p15
Click to expand...
Click to collapse
Uhhh, I'm not sure either. One of Amazon's obscure modifications. :crying::crying:

Supersonic27543 said:
Uhhh, I'm not sure either. One of Amazon's obscure modifications. :crying::crying:
Click to expand...
Click to collapse
Also, try "reserved" please? Thanks!

luvboox said:
I'm not very good at this, but I can try to help. Not sure which file(s) to grab.
I got the following in /dev/block/platform/soc/by-name
lrwxrwxrwx root root 2018-02-22 22:47 MISC -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2018-02-22 22:47 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr0 -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx root root 2018-02-22 22:47 boot0hdr1 -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx root root 2018-02-22 22:47 boot0img0 -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx root root 2018-02-22 22:47 boot0img1 -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx root root 2018-02-22 22:47 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2018-02-22 22:47 dkb -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-02-22 22:47 kb -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-02-22 22:47 lk -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-02-22 22:47 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2018-02-22 22:47 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-02-22 22:47 recovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2018-02-22 22:47 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-02-22 22:47 system -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2018-02-22 22:47 tee1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-02-22 22:47 tee2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-02-22 22:47 userdata -> /dev/block/mmcblk0p15
Click to expand...
Click to collapse
Also, did you try /dev/block/bootdevice/by-name ? Thank you

Supersonic27543 said:
Also, did you try /dev/block/bootdevice/by-name ? Thank you
Click to expand...
Click to collapse
No /dev/block/bootdevice/ I'm afraid, just /dev/block/platform/ and /dev/block/vold (which is an empty folder).

@Supersonic27543 and others
Have you seen this : https://forum.xda-developers.com/showpost.php?p=74987132&postcount=3

The bootloader files you're looking for are in the update .bin (it's really a .zip; look in the "images" folder). The links to the update file are in the thread cited above (in post #2).
As discussed earlier in this thread, the preloader is locked down (read/write commands missing). Absent access to Amz's signature(s) for the DA, what are you looking to do with these files?

retyre said:
The bootloader files you're looking for are in the update .bin (it's really a .zip; look in the "images" folder). The links to the update file are in the thread cited above (in post #2).
As discussed earlier in this thread, the preloader is locked down (read/write commands missing). Absent access to Amz's signature(s) for the DA, what are you looking to do with these files?
Click to expand...
Click to collapse
I'm trying to see if any backdoor has been left by Amazon by looking at unusual differences.