Database Info

OpenVPN not working ??

Hi I'm having problems in using openvpn on custom ROM like vituous, saga and coredroid. I can connect to the VPN but when I try to browse, there is no activity.
I tried the ROM of superkid, the CM7, and there, I can connect easily using openvpn.
My question is what might be the problem why I can't use openvpn when I'm on virtuous and saga ROM?
btw here's my log
Wed Jul 13 15:47:03 2011 TLS: Initial packet from 184.164.141.62:9200, sid=04c0ec4c 57d245d0
Wed Jul 13 15:47:03 2011 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Wed Jul 13 15:47:06 2011 MANAGEMENT: Client connected from 127.0.0.1:40342
Wed Jul 13 15:47:06 2011 MANAGEMENT: CMD 'state'
Wed Jul 13 15:47:06 2011 MANAGEMENT: CMD 'state on'
Wed Jul 13 15:47:06 2011 MANAGEMENT: CMD 'bytecount 0'
Wed Jul 13 15:47:06 2011 VERIFY OK: depth=1, /C=ph/ST=ph/L=ph/O=pg/OU=pg_x08/CN=server/name=server/[email protected]
Wed Jul 13 15:47:06 2011 VERIFY OK: depth=0, /C=ph/ST=ph/L=ph/O=ph/OU=ph/CN=server/name=server/[email protected]
Wed Jul 13 15:47:08 2011 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1542', remote='link-mtu 1574'
Wed Jul 13 15:47:08 2011 WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1500', remote='tun-mtu 1532'
Wed Jul 13 15:47:08 2011 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Jul 13 15:47:08 2011 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Jul 13 15:47:08 2011 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Jul 13 15:47:08 2011 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Jul 13 15:47:08 2011 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Jul 13 15:47:08 2011 [server] Peer Connection Initiated with 184.164.141.62:9200
Wed Jul 13 15:47:09 2011 MANAGEMENT: >STATE:1310543229,GET_CONFIG,,,
Wed Jul 13 15:47:09 2011 MANAGEMENT: CMD 'bytecount 0'
Wed Jul 13 15:47:10 2011 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Jul 13 15:47:10 2011 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route 10.9.0.1,topology net30,ping 60,ping-restart 300,ifconfig 10.9.1.6 10.9.1.5'
Wed Jul 13 15:47:10 2011 OPTIONS IMPORT: timers and/or timeouts modified
Wed Jul 13 15:47:10 2011 OPTIONS IMPORT: --ifconfig/up options modified
Wed Jul 13 15:47:10 2011 OPTIONS IMPORT: route options modified
Wed Jul 13 15:47:10 2011 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Jul 13 15:47:10 2011 ROUTE default_gateway=10.31.196.149
Wed Jul 13 15:47:10 2011 TUN/TAP device tun0 opened
Wed Jul 13 15:47:10 2011 TUN/TAP TX queue length set to 100
Wed Jul 13 15:47:10 2011 MANAGEMENT: >STATE:1310543230,ASSIGN_IP,,10.9.1.6,
Wed Jul 13 15:47:10 2011 /system/xbin/bb/ifconfig tun0 10.9.1.6 pointopoint 10.9.1.5 mtu 1500
Wed Jul 13 15:47:10 2011 MANAGEMENT: CMD 'bytecount 0'
Wed Jul 13 15:47:12 2011 /system/xbin/bb/route add -net 184.164.141.62 netmask 255.255.255.255 gw 10.31.196.149
Wed Jul 13 15:47:12 2011 /system/xbin/bb/route add -net 0.0.0.0 netmask 128.0.0.0 gw 10.9.1.5
Wed Jul 13 15:47:12 2011 /system/xbin/bb/route add -net 128.0.0.0 netmask 128.0.0.0 gw 10.9.1.5
Wed Jul 13 15:47:12 2011 MANAGEMENT: >STATE:1310543232,ADD_ROUTES,,,
Wed Jul 13 15:47:12 2011 /system/xbin/bb/route add -net 10.9.0.1 netmask 255.255.255.255 gw 10.9.1.5
Wed Jul 13 15:47:12 2011 Initialization Sequence Completed
Wed Jul 13 15:47:12 2011 MANAGEMENT: >STATE:1310543232,CONNECTED,SUCCESS,10.9.1.6,184.164.141.62
Wed Jul 13 15:47:12 2011 MANAGEMENT: CMD 'bytecount 0'
Wed Jul 13 15:47:12 2011 MANAGEMENT: CMD 'bytecount 3'
Wed Jul 13 15:47:20 2011 MANAGEMENT: CMD 'state'
Wed Jul 13 15:47:20 2011 MANAGEMENT: CMD 'bytecount 3'
Wed Jul 13 15:47:43 2011 MANAGEMENT: CMD 'state'
Wed Jul 13 15:47:43 2011 MANAGEMENT: CMD 'bytecount 3'
Wed Jul 13 15:50:47 2011 event_wait : Interrupted system call (code=4)
Wed Jul 13 15:50:47 2011 TCP/UDP: Closing socket
Wed Jul 13 15:50:47 2011 /system/xbin/bb/route del -net 10.9.0.1 netmask 255.255.255.255
Wed Jul 13 15:50:47 2011 /system/xbin/bb/route del -net 184.164.141.62 netmask 255.255.255.255
Wed Jul 13 15:50:47 2011 /system/xbin/bb/route del -net 0.0.0.0 netmask 128.0.0.0
Wed Jul 13 15:50:47 2011 /system/xbin/bb/route del -net 128.0.0.0 netmask 128.0.0.0
Wed Jul 13 15:50:47 2011 Closing TUN/TAP interface
Wed Jul 13 15:50:47 2011 /system/xbin/bb/ifconfig tun0 0.0.0.0
Wed Jul 13 15:50:47 2011 SIGTERM[hard,] received, process exiting
Wed Jul 13 15:50:47 2011 MANAGEMENT: >STATE:1310543447,EXITING,SIGTERM,,
Click to expand...
Click to collapse

anyone here using openvpn? need help . thanks!

ghuk said:
anyone here using openvpn? need help . thanks!
Click to expand...
Click to collapse
Might be worth writing to the one of the cooks of the customs, as they all use same kernel so must be rom related
Sent from my HTC Desire S using XDA Premium App

hi there.. i have same problem with this..
i tried CM7 and MIUI, it works but when i install insertcoin, acemod, Cool-Sensation-v6 it doesnt work. it shows it connected to server but still doesnt. when i go to whatmyip.com it still shows my ip.
plz help...

Hello, I have read this, this, this and this, and I've also followed these instructions, but I am still confused on how to get this OpenVPN client working on my device.
My OpenVPN server works good, since I am able to connect to it from every PC which is configured correctly.
Of course, I think the problem is due to the following two (well known) lines, in the openvpn.log file:
Code:
Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:1: route (2.1.1)
Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:5: ifconfig (2.1.1)
In the openvpn.log file, on the server, it seems to be all OK with the handshake. Actually the client is authenticated and the IP seems to be assigned, even if I cannot ping or do whatever else.
The file I use on the client to get access credentials on the server are the following:
Code:
ca.crt
home.conf
saga.crt
saga.csr
saga.key
ta.key
Of course the openvpn client says "connected" at the end of handshake.
What is not so clear to me is that I have to do some "hack" into the device (like symbolic link or something else) in order to get it working. Is there a "official" and definitive procedure to get it working? I am asking this because I have seen many different procedures and, as I've said, I am a little bit confused. Why don't they fix the apk in the market, of course if this is necessary?

L2TP Debian-Android

Hi,
I'm trying to connect my HTC desire HD to my linux server (Debian) using L2TP/IPsec.
I connect it but after about 10 second the connection go down.
This is the log of syslog. It seems that the HTC send a request to stop the connection.
Do someone has allready this problem?
Here the log:
Sep 27 01:06:27 gandalf pppd[19824]: rcvd [LCP TermReq id=0x2 "User request"]
Sep 27 01:06:27 gandalf pppd[19824]: LCP terminated by peer (User request)
Sep 27 01:06:27 gandalf pppd[19824]: Connect time 0.2 minutes.
Sep 27 01:06:27 gandalf pppd[19824]: Sent 0 bytes, received 284 bytes.
Sep 27 01:06:27 gandalf pppd[19824]: Script /etc/ppp/ip-down started (pid 19895)
Sep 27 01:06:27 gandalf pppd[19824]: sent [LCP TermAck id=0x2]
Sep 27 01:06:28 gandalf postfix/master[3747]: reload -- version 2.7.1, configuration /etc/postfix
Sep 27 01:06:28 gandalf pppd[19824]: Script /etc/ppp/ip-down finished (pid 19895), status = 0x0
Sep 27 01:06:28 gandalf xl2tpd[21192]: result_code_avp: avp is incorrect size. 8 < 10
Sep 27 01:06:28 gandalf xl2tpd[21192]: handle_avps: Bad exit status handling attribute 1 (Result Code) on mandatory packet.
Sep 27 01:06:28 gandalf pppd[19824]: Modem hangup
Sep 27 01:06:28 gandalf xl2tpd[21192]: Terminating pppd: sending TERM signal to pid 19824
Sep 27 01:06:28 gandalf pppd[19824]: Connection terminated.
Sep 27 01:06:28 gandalf xl2tpd[21192]: Connection 54722 closed to 62.203.116.176, port 62132 (Result Code: expected at least 10, got 8)
Sep 27 01:06:28 gandalf pppd[19824]: Exit.
Sep 27 01:06:33 gandalf xl2tpd[21192]: Unable to deliver closing message for tunnel 43543. Destroying anyway.
Thank you for your help.
Regards
Gian Carlo

Does nobody has this problem before? I try differents possible solutions but with no success

Open tcp port 33003?

Hey friends, I'm fairly new to Linux/Android and trying to learn. Anyway, I just picked up a Skyrocket a couple of days a go and I've noticed something has my tcp port 33003 open all the time. Googled it and couldn't find any information. Any ideas as to what it is, if it's a security threat, and if so how to get that puppy closed? Thanks.
Sent from my SAMSUNG-SGH-I727 using xda premium

i777 SGSII also with Port 33003 open
I have an ATT SGSII, rooted, stock rom/kernel still
(bought black friday 2011 @ sam's club)
I also see 33003 port open
Code:
localhost root # netstat
Proto Recv-Q Send-Q Local Address Foreign Address State
(...)
tcp6 0 0 ::ffff:192.168.0.140:33003 :::* LISTEN
(...)
It looks like some kinda webserver...
Code:
# telnet 192.168.0.140 33003
Trying 192.168.0.140...
Connected to 192.168.0.140.
Escape character is '^]'.
HELP
HELO
HTTP/1.1 400 Bad Request
Content-Type: text/html; charset="utf-8"
Server: Linux/2.6.35.7 DoaHTTP
Content-Length: 0
Date: Fri, 23 Dec 2011 12:09:04 GMT
Doesn't want to answer normal web communications either
Code:
mercury ~ # wget 192.168.0.140:33003
--12:09:28-- http ://192.168.0.140:33003/
=> `index.html'
Connecting to 192.168.0.140:33003... connected.
HTTP request sent, awaiting response... 400 Bad Request
12:09:29 ERROR 400: Bad Request.
No results so far for "Android DoaHTTP web server"
Sketchy
Edit:
Code:
localhost root # fuser 33003/tcp6
18870
localhost root # ps | grep 18870
18870 app_85 147m S {eTransferServer} com.sec.android.app.FileTransferServer
22982 root 1788 S grep 18870
So the port is opened by FileTransferServer
---------- Post added at 01:16 PM ---------- Previous post was at 12:29 PM ----------
This FTS.apk shows up the list of crap-that-may-be-removed:
http://forum.xda-developers.com/showthread.php?t=1386846
Also here some guy randomly mentions renaming it to disable in a thread about battery drain...
http://androidforums.com/samsung-ga.../341084-wifi-sharing-battery-usage-issue.html
Here is a great resource on battery life that includes disabling FTS.apk in a script that disables alot of other stock bloat
http://softbanksucks.blogspot.com/2011/10/getting-most-out-of-your-battery-on.html
For anyone that wants to followup with exactly what FTS.apk does, here is some more info on my File Transfer Service running process ...
This is a list of the file descriptors it currently has open...
Code:
localhost root # ls -l /proc/18870/fd
total 0
lrwx------ 1 10085 10085 64 Dec 23 18:32 0 -> /dev/null
lrwx------ 1 10085 10085 64 Dec 23 18:32 1 -> /dev/null
l-wx------ 1 10085 10085 64 Dec 23 18:32 10 -> /dev/log/system
lr-x------ 1 10085 10085 64 Dec 23 18:32 11 -> /system/framework/core.jar
lr-x------ 1 10085 10085 64 Dec 23 18:32 12 -> /dev/__properties__ (deleted)
lr-x------ 1 10085 10085 64 Dec 23 18:32 14 -> /system/framework/bouncycastle.jar
lr-x------ 1 10085 10085 64 Dec 23 18:32 15 -> /system/framework/ext.jar
lr-x------ 1 10085 10085 64 Dec 23 18:32 16 -> /system/framework/framework.jar
lr-x------ 1 10085 10085 64 Dec 23 18:32 17 -> /system/framework/android.policy.jar
lr-x------ 1 10085 10085 64 Dec 23 18:32 18 -> /system/framework/services.jar
lr-x------ 1 10085 10085 64 Dec 23 18:32 19 -> /system/framework/core-junit.jar
lrwx------ 1 10085 10085 64 Dec 23 18:32 2 -> /dev/null
lr-x------ 1 10085 10085 64 Dec 23 18:32 20 -> /system/framework/framework.jar
lr-x------ 1 10085 10085 64 Dec 23 18:32 21 -> /system/fonts/DroidSans.ttf
lr-x------ 1 10085 10085 64 Dec 23 18:32 22 -> /system/framework/twframework-res.apk
lr-x------ 1 10085 10085 64 Dec 23 18:32 23 -> /system/framework/framework-res.apk
lr-x------ 1 10085 10085 64 Dec 23 18:32 24 -> /system/framework/core.jar
lr-x------ 1 10085 10085 64 Dec 23 18:32 25 -> /dev/urandom
l-wx------ 1 10085 10085 64 Dec 23 18:32 3 -> /dev/log/main
lrwx------ 1 10085 10085 64 Dec 23 18:32 30 -> /dev/binder
lrwx------ 1 10085 10085 64 Dec 23 18:32 31 -> anon_inode:[eventpoll]
l-wx------ 1 10085 10085 64 Dec 23 18:32 32 -> /dev/cpuctl/tasks
l-wx------ 1 10085 10085 64 Dec 23 18:32 33 -> /dev/cpuctl/bg_non_interactive/tasks
lr-x------ 1 10085 10085 64 Dec 23 18:32 34 -> /system/app/FTS.apk
lr-x------ 1 10085 10085 64 Dec 23 18:32 35 -> /system/app/FTS.apk
lrwx------ 1 10085 10085 64 Dec 23 18:32 36 -> /dev/ashmem
lrwx------ 1 10085 10085 64 Dec 23 18:32 37 -> /dev/ashmem
lr-x------ 1 10085 10085 64 Dec 23 18:32 38 -> /system/app/FTS.apk
l-wx------ 1 10085 10085 64 Dec 23 18:32 4 -> /dev/log/radio
lrwx------ 1 10085 10085 64 Dec 23 18:32 41 -> anon_inode:[eventpoll]
lrwx------ 1 10085 10085 64 Dec 23 18:32 44 -> anon_inode:[eventpoll]
lrwx------ 1 10085 10085 64 Dec 23 18:32 47 -> anon_inode:[eventpoll]
l-wx------ 1 10085 10085 64 Dec 23 18:32 5 -> /dev/log/main
l-wx------ 1 10085 10085 64 Dec 23 18:32 6 -> /dev/log/radio
l-wx------ 1 10085 10085 64 Dec 23 18:32 7 -> /dev/log/events
l-wx------ 1 10085 10085 64 Dec 23 18:32 8 -> /dev/log/system
l-wx------ 1 10085 10085 64 Dec 23 18:32 9 -> /dev/log/events

[Q] How many Android partition does it have ?

I am newbie on android , and I just though of few question after reading some of the partition. http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
But what I do not understand is , are those partition a folder or real partition ?
As for commonly known , Windows partition consist of either 4 Primary partition or 3 primary 1 extended partition.
-Master boot record partition
-Primary (max 4 , min 0)
-Extended partition ( multiple logical partition )
What about android ? Let me know whether I am wrong
-/boot ( equal to MBR )
-/system /recovery /data /cache /misc (1 parimary partition with different path like /system32 , /Programs files /My Document and etc)
-/SDcard0 (Extended partition )
External SDcard = something like external hard disk.
Overall any android Device have 2 partition ,1 Primary (/system /recovery /data /cache /misc) and 1 Extended logical ( SDcard0)
Please correct me if I'm getting the idea wrong.

Any expert here able to clear out or confirm them ?

Kindly let me know the correct answer.
I am just a starter

It's a hard question ?
Even for a dev too ?

xdadfm said:
I am newbie on android , and I just though of few question after reading some of the partition. http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
But what I do not understand is , are those partition a folder or real partition ?
As for commonly known , Windows partition consist of either 4 Primary partition or 3 primary 1 extended partition.
-Master boot record partition
-Primary (max 4 , min 0)
-Extended partition ( multiple logical partition )
What about android ? Let me know whether I am wrong
-/boot ( equal to MBR )
-/system /recovery /data /cache /misc (1 parimary partition with different path like /system32 , /Programs files /My Document and etc)
-/SDcard0 (Extended partition )
External SDcard = something like external hard disk.
Overall any android Device have 2 partition ,1 Primary (/system /recovery /data /cache /misc) and 1 Extended logical ( SDcard0)
Please correct me if I'm getting the idea wrong.
Click to expand...
Click to collapse
I'm not an expert but as far as I know :
android has 5 partitions ..
/boot
/system
/recovery
/data
/cache
and there Is the SD card partition
/sdcard
Boot: Contains Kernal and Ramdisk ,, Without This Partition The Device Simply Won't Boot
System: Contains The Entire Android System,Android User Interface and System Apps
Recovery: Another Booting Option For Performing Advanced Recovery And maintenance Operations
Data: Contains The User Data Such As Contacts,Messages ... etc
Cache: Where Android Stores Applications Components and Cache
Hope It Helps

falf123 said:
I'm not an expert but as far as I know :
android has 5 partitions ..
/boot
/system
/recovery
/data
/cache
and there Is the SD card partition
/sdcard
Boot: Contains Kernal and Ramdisk ,, Without This Partition The Device Simply Won't Boot
System: Contains The Entire Android System,Android User Interface and System Apps
Recovery: Another Booting Option For Performing Advanced Recovery And maintenance Operations
Data: Contains The User Data Such As Contacts,Messages ... etc
Cache: Where Android Stores Applications Components and Cache
Hope It Helps
Click to expand...
Click to collapse
The partition is actually real partition like what we did to a hardisk ?
Possible to have 5 partition on a Flash drive ? as for window , maximum is 4 primary partition .

The question you are asking requires a bit of an explanation, but I will do my best (forgive me if I gloss over some things).
When a windows PC boots up, it initializes CMOS which searches for the hard drive or other boot device based on the order set up in BIOS/CMOS. Once it finds a storage device it attempts to boot that device (i.e. hdd=hard disk drive, eMMC=electronic MultiMedia Card). There is a bit set somewhere that determines what type of filing system is on the drive. In linux, you can see the partition table by using fdisk (devices are located in the /dev folder and look like /dev/sda or /dev/mmcblk0, depending on the type and how many there are). Therefore the command would be 'fdisk /dev/sda' and let's take a look at that...
Welcome to fdisk (util-linux 2.32.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: xxxxxxxxxx (omitted)
Device Start End Sectors Size Type
/dev/sda1 2048 2050047 2048000 1000M Windows recovery environment
/dev/sda2 2050048 2582527 532480 260M EFI System
/dev/sda3 2582528 4630527 2048000 1000M Windows recovery environment
/dev/sda4 4630528 4892671 262144 128M Microsoft reserved
/dev/sda5 4892672 1619314687 1614422016 769.8G Microsoft basic data
/dev/sda6 1619314688 1845840078 226525391 108G Microsoft basic data
/dev/sda7 1845840094 1853995007 8154914 3.9G Microsoft basic data
/dev/sda8 1853995008 1858228223 4233216 2G Windows recovery environment
/dev/sda9 1858228224 1859151871 923648 451M Windows recovery environment
/dev/sda10 1859151872 1911580671 52428800 25G Microsoft basic data
/dev/sda11 1911580672 1953523711 41943040 20G Windows recovery environment
As you can see, my device "sda" has 11 partitions. 1,3,8,9,11 are all recovery partitions, 2 is an EFI partition, etc. A short list of possibilities...
1 EFI System C12A7328-F81F-11D2-BA4B-00A0C93EC93B
2 MBR partition scheme 024DEE41-33E7-11D3-9D69-0008C781F39F
3 Intel Fast Flash D3BFE2DE-3DAF-11DF-BA40-E3A556D89593
4 BIOS boot 21686148-6449-6E6F-744E-656564454649
5 Sony boot partition F4019732-066E-4E12-8273-346C5641494F
6 Lenovo boot partition BFBFAFE7-A34F-448A-9A5B-6213EB736C22
7 PowerPC PReP boot 9E1A2D38-C612-4316-AA26-8B49521E5A8B
8 ONIE boot 7412F7D5-A156-4B13-81DC-867174929325
9 ONIE config D4E6E2CD-4469-46F3-B5CB-1BFF57AFC149
10 Microsoft reserved E3C9E316-0B5C-4DB8-817D-F92DF00215AE
11 Microsoft basic data EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
12 Microsoft LDM metadata 5808C8AA-7E8F-42E0-85D2-E1E90434CFB3
13 Microsoft LDM data AF9B60A0-1431-4F62-BC68-3311714A69AD
14 Windows recovery environment DE94BBA4-06D1-4D40-A16A-BFD50179D6AC
15 IBM General Parallel Fs 37AFFC90-EF7D-4E96-91C3-2D7AE055B174
16 Microsoft Storage Spaces E75CAF8F-F680-4CEE-AFA3-B001E56EFC2D
17 HP-UX data 75894C1E-3AEB-11D3-B7C1-7B03A0000000
18 HP-UX service E2A1E728-32E3-11D6-A682-7B03A0000000
19 Linux swap 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F
20 Linux filesystem 0FC63DAF-8483-4772-8E79-3D69D8477DE4
21 Linux server data 3B8F8425-20E0-4F3B-907F-1A25A76F98E8
22 Linux root (x86) 44479540-F297-41B2-9AF7-D131D5F0458A
23 Linux root (ARM) 69DAD710-2CE4-4E3C-B16C-21A1D49ABED3
24 Linux root (x86-64) 4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709
Each partition stores data differently. Windows 95 all the way through Windows ME uses FAT (File Allocation Table) and doesn't use user permissions on files. NTFS (Windows NT File System) is the updated version of FAT which had its evolution and caveats. NTFS is the Windows standard now because it 1) can handle file systems larger than 2GB and 2) has the ability to set user file permissions so only the owner can read/write/execute certain files. Android uses ext4, which is a linux file system. The difference is that linux doesn't have drive letters. In windows, C:\ is your normal hard drive, A:\ is a floppy drive, and all disk devices (Thumb drive, CD ROM drive, tape backup, etc) have a letter and are almost always "mounted". In linux... the "root" is / and every device is either mounted as a subfolder or listed in /dev. So if I do a ls /dev I get this as a result (ls is the same command as dir for windows/dos):
ls -l
total 0
crw-r--r-- 1 root root 10, 235 Aug 27 05:17 autofs
drwxr-xr-x 2 root root 340 Aug 27 05:34 block
drwxr-xr-x 2 root root 60 Aug 27 05:34 bsg
crw------- 1 root root 10, 234 Aug 27 05:17 btrfs-control
drwxr-xr-x 3 root root 60 Aug 26 22:17 bus
drwxr-xr-x 2 root root 3580 Aug 27 14:00 char
crw------- 1 root root 5, 1 Aug 27 05:17 console
lrwxrwxrwx 1 root root 11 Aug 26 22:17 core -> /proc/kcore
drwxr-xr-x 2 root root 60 Aug 26 22:17 cpu
crw------- 1 root root 10, 62 Aug 27 05:17 cpu_dma_latency
crw------- 1 root root 10, 203 Aug 27 05:17 cuse
drwxr-xr-x 8 root root 160 Aug 26 22:17 disk
drwxr-xr-x 3 root root 100 Aug 27 05:17 dri
crw------- 1 root root 245, 0 Aug 27 05:17 drm_dp_aux0
crw-rw---- 1 root video 29, 0 Aug 27 05:17 fb0
lrwxrwxrwx 1 root root 13 Aug 26 22:17 fd -> /proc/self/fd
crw-rw-rw- 1 root root 1, 7 Aug 27 05:17 full
crw-rw-rw- 1 root root 10, 229 Aug 27 05:17 fuse
crw------- 1 root root 247, 0 Aug 27 05:17 hidraw0
crw------- 1 root root 247, 1 Aug 27 05:17 hidraw1
crw------- 1 root root 10, 228 Aug 27 05:17 hpet
drwxr-xr-x 2 root root 0 Aug 27 05:17 hugepages
lrwxrwxrwx 1 root root 12 Aug 27 05:17 initctl -> /run/initctl
drwxr-xr-x 4 root root 580 Aug 27 05:44 input
crw-r--r-- 1 root root 1, 11 Aug 27 05:17 kmsg
crw-rw----+ 1 root kvm 10, 232 Aug 27 05:17 kvm
lrwxrwxrwx 1 root root 28 Aug 27 05:17 log -> /run/systemd/journal/dev-log
crw-rw---- 1 root disk 10, 237 Aug 27 05:17 loop-control
drwxr-xr-x 2 root root 60 Aug 27 05:17 mapper
crw-rw---- 1 root video 243, 0 Aug 27 05:17 media0
crw-rw---- 1 root video 243, 1 Aug 27 05:42 media1
crw-rw---- 1 root video 243, 2 Aug 27 05:43 media2
crw-rw---- 1 root video 243, 3 Aug 27 05:44 media3
crw-rw---- 1 root video 243, 4 Aug 27 05:44 media4
crw-rw---- 1 root video 243, 5 Aug 27 05:44 media5
crw-rw---- 1 root video 243, 6 Aug 27 05:44 media6
crw-rw---- 1 root video 243, 7 Aug 27 05:44 media7
crw------- 1 root root 244, 0 Aug 27 05:17 mei0
crw-r----- 1 root kmem 1, 1 Aug 27 05:17 mem
crw------- 1 root root 10, 59 Aug 27 05:17 memory_bandwidth
brw-rw---- 1 root disk 179, 0 Aug 27 05:17 mmcblk0
brw-rw---- 1 root disk 179, 1 Aug 27 05:17 mmcblk0p1
brw-rw---- 1 root disk 179, 2 Aug 27 05:17 mmcblk0p2
drwxrwxrwt 2 root root 40 Aug 26 22:17 mqueue
drwxr-xr-x 2 root root 60 Aug 27 05:17 net
crw------- 1 root root 10, 61 Aug 27 05:17 network_latency
crw------- 1 root root 10, 60 Aug 27 05:17 network_throughput
crw-rw-rw- 1 root root 1, 3 Aug 27 05:17 null
crw-r----- 1 root kmem 1, 4 Aug 27 05:17 port
crw------- 1 root root 108, 0 Aug 27 05:17 ppp
crw------- 1 root root 10, 1 Aug 27 05:17 psaux
crw-rw-rw- 1 root tty 5, 2 Aug 27 14:05 ptmx
drwxr-xr-x 2 root root 0 Aug 26 22:17 pts
crw-rw-rw- 1 root root 1, 8 Aug 27 05:17 random
crw-rw-r--+ 1 root netdev 10, 58 Aug 27 05:17 rfkill
lrwxrwxrwx 1 root root 4 Aug 27 05:17 rtc -> rtc0
crw------- 1 root root 252, 0 Aug 27 05:17 rtc0
brw-rw---- 1 root disk 8, 0 Aug 27 05:17 sda
brw-rw---- 1 root disk 8, 1 Aug 27 05:17 sda1
brw-rw---- 1 root disk 8, 10 Aug 27 05:17 sda10
brw-rw---- 1 root disk 8, 11 Aug 27 05:17 sda11
brw-rw---- 1 root disk 8, 2 Aug 27 05:17 sda2
brw-rw---- 1 root disk 8, 3 Aug 27 05:17 sda3
brw-rw---- 1 root disk 8, 4 Aug 27 05:17 sda4
brw-rw---- 1 root disk 8, 5 Aug 27 05:17 sda5
brw-rw---- 1 root disk 8, 6 Aug 27 05:17 sda6
brw-rw---- 1 root disk 8, 7 Aug 27 05:17 sda7
brw-rw---- 1 root disk 8, 8 Aug 27 05:17 sda8
brw-rw---- 1 root disk 8, 9 Aug 27 05:17 sda9
crw-rw---- 1 root disk 21, 0 Aug 27 05:17 sg0
drwxrwxrwt 2 root root 40 Aug 27 14:05 shm
crw------- 1 root root 10, 231 Aug 27 05:17 snapshot
drwxr-xr-x 3 root root 220 Aug 27 06:31 snd
lrwxrwxrwx 1 root root 15 Aug 26 22:17 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root root 15 Aug 26 22:17 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root root 15 Aug 26 22:17 stdout -> /proc/self/fd/1
crw-rw-rw- 1 root tty 5, 0 Aug 27 13:16 tty
crw--w---- 1 root tty 4, 0 Aug 27 05:17 tty0
crw--w---- 1 root tty 4, 1 Aug 27 05:18 tty1
crw--w---- 1 root tty 4, 10 Aug 27 05:17 tty10
crw--w---- 1 root tty 4, 11 Aug 27 05:17 tty11
crw--w---- 1 root tty 4, 12 Aug 27 05:17 tty12
crw--w---- 1 root tty 4, 13 Aug 27 05:17 tty13
crw--w---- 1 root tty 4, 14 Aug 27 05:17 tty14
crw--w---- 1 root tty 4, 15 Aug 27 05:17 tty15
crw--w---- 1 root tty 4, 16 Aug 27 05:17 tty16
crw--w---- 1 root tty 4, 17 Aug 27 05:17 tty17
crw--w---- 1 root tty 4, 18 Aug 27 05:17 tty18
crw--w---- 1 root tty 4, 19 Aug 27 05:17 tty19
crw--w---- 1 root tty 4, 2 Aug 27 05:17 tty2
crw--w---- 1 root tty 4, 20 Aug 27 05:17 tty20
crw--w---- 1 root tty 4, 21 Aug 27 05:17 tty21
crw--w---- 1 root tty 4, 22 Aug 27 05:17 tty22
crw--w---- 1 root tty 4, 23 Aug 27 05:17 tty23
crw--w---- 1 root tty 4, 24 Aug 27 05:17 tty24
crw--w---- 1 root tty 4, 25 Aug 27 05:17 tty25
crw--w---- 1 root tty 4, 26 Aug 27 05:17 tty26
crw--w---- 1 root tty 4, 27 Aug 27 05:17 tty27
crw--w---- 1 root tty 4, 28 Aug 27 05:17 tty28
crw--w---- 1 root tty 4, 29 Aug 27 05:17 tty29
crw--w---- 1 root tty 4, 3 Aug 27 05:17 tty3
crw--w---- 1 root tty 4, 30 Aug 27 05:17 tty30
crw--w---- 1 root tty 4, 31 Aug 27 05:17 tty31
crw--w---- 1 root tty 4, 32 Aug 27 05:17 tty32
crw--w---- 1 root tty 4, 33 Aug 27 05:17 tty33
crw--w---- 1 root tty 4, 34 Aug 27 05:17 tty34
crw--w---- 1 root tty 4, 35 Aug 27 05:17 tty35
crw--w---- 1 root tty 4, 36 Aug 27 05:17 tty36
crw--w---- 1 root tty 4, 37 Aug 27 05:17 tty37
crw--w---- 1 root tty 4, 38 Aug 27 05:17 tty38
crw--w---- 1 root tty 4, 39 Aug 27 05:17 tty39
crw--w---- 1 root tty 4, 4 Aug 27 05:17 tty4
crw--w---- 1 root tty 4, 40 Aug 27 05:17 tty40
crw--w---- 1 root tty 4, 41 Aug 27 05:17 tty41
crw--w---- 1 root tty 4, 42 Aug 27 05:17 tty42
crw--w---- 1 root tty 4, 43 Aug 27 05:17 tty43
crw--w---- 1 root tty 4, 44 Aug 27 05:17 tty44
crw--w---- 1 root tty 4, 45 Aug 27 05:17 tty45
crw--w---- 1 root tty 4, 46 Aug 27 05:17 tty46
crw--w---- 1 root tty 4, 47 Aug 27 05:17 tty47
crw--w---- 1 root tty 4, 48 Aug 27 05:17 tty48
crw--w---- 1 root tty 4, 49 Aug 27 05:17 tty49
crw--w---- 1 root tty 4, 5 Aug 27 05:17 tty5
crw--w---- 1 root tty 4, 50 Aug 27 05:17 tty50
crw--w---- 1 root tty 4, 51 Aug 27 05:17 tty51
crw--w---- 1 root tty 4, 52 Aug 27 05:17 tty52
crw--w---- 1 root tty 4, 53 Aug 27 05:17 tty53
crw--w---- 1 root tty 4, 54 Aug 27 05:17 tty54
crw--w---- 1 root tty 4, 55 Aug 27 05:17 tty55
crw--w---- 1 root tty 4, 56 Aug 27 05:17 tty56
crw--w---- 1 root tty 4, 57 Aug 27 05:17 tty57
crw--w---- 1 root tty 4, 58 Aug 27 05:17 tty58
crw--w---- 1 root tty 4, 59 Aug 27 05:17 tty59
crw--w---- 1 root tty 4, 6 Aug 27 05:17 tty6
crw--w---- 1 root tty 4, 60 Aug 27 05:17 tty60
crw--w---- 1 root tty 4, 61 Aug 27 05:17 tty61
crw--w---- 1 root tty 4, 62 Aug 27 05:17 tty62
crw--w---- 1 root tty 4, 63 Aug 27 05:17 tty63
crw--w---- 1 root tty 4, 7 Aug 27 05:18 tty7
crw--w---- 1 root tty 4, 8 Aug 27 05:17 tty8
crw--w---- 1 root tty 4, 9 Aug 27 05:17 tty9
crw-rw---- 1 root dialout 4, 64 Aug 27 05:17 ttyS0
crw-rw---- 1 root dialout 4, 65 Aug 27 05:17 ttyS1
crw-rw---- 1 root dialout 4, 66 Aug 27 05:17 ttyS2
crw-rw---- 1 root dialout 4, 67 Aug 27 05:17 ttyS3
crw------- 1 root root 10, 239 Aug 27 05:17 uhid
crw------- 1 root root 10, 223 Aug 27 05:17 uinput
crw-rw-rw- 1 root root 1, 9 Aug 27 05:17 urandom
drwxr-xr-x 2 root root 80 Aug 27 09:50 usb
drwxr-xr-x 4 root root 80 Aug 27 05:17 v4l
crw------- 1 root root 10, 57 Aug 27 05:18 vboxdrv
crw------- 1 root root 10, 56 Aug 27 05:18 vboxdrvu
crw------- 1 root root 10, 55 Aug 27 05:18 vboxnetctl
drwxr-x--- 4 root vboxusers 80 Aug 27 05:17 vboxusb
crw-rw---- 1 root tty 7, 0 Aug 27 05:17 vcs
crw-rw---- 1 root tty 7, 1 Aug 27 05:17 vcs1
crw-rw---- 1 root tty 7, 2 Aug 27 05:17 vcs2
crw-rw---- 1 root tty 7, 3 Aug 27 05:17 vcs3
crw-rw---- 1 root tty 7, 4 Aug 27 05:17 vcs4
crw-rw---- 1 root tty 7, 5 Aug 27 05:17 vcs5
crw-rw---- 1 root tty 7, 6 Aug 27 05:17 vcs6
crw-rw---- 1 root tty 7, 7 Aug 27 05:18 vcs7
crw-rw---- 1 root tty 7, 128 Aug 27 05:17 vcsa
crw-rw---- 1 root tty 7, 129 Aug 27 05:17 vcsa1
crw-rw---- 1 root tty 7, 130 Aug 27 05:17 vcsa2
crw-rw---- 1 root tty 7, 131 Aug 27 05:17 vcsa3
crw-rw---- 1 root tty 7, 132 Aug 27 05:17 vcsa4
crw-rw---- 1 root tty 7, 133 Aug 27 05:17 vcsa5
crw-rw---- 1 root tty 7, 134 Aug 27 05:17 vcsa6
crw-rw---- 1 root tty 7, 135 Aug 27 05:18 vcsa7
drwxr-xr-x 2 root root 60 Aug 27 05:17 vfio
crw------- 1 root root 10, 63 Aug 27 05:17 vga_arbiter
crw------- 1 root root 10, 137 Aug 27 05:17 vhci
crw------- 1 root root 10, 238 Aug 27 05:17 vhost-net
crw------- 1 root root 10, 241 Aug 27 05:17 vhost-vsock
crw-rw----+ 1 root video 81, 0 Aug 27 05:17 video0
crw-rw----+ 1 root video 81, 1 Aug 27 05:17 video1
crw------- 1 root root 10, 130 Aug 27 05:17 watchdog
crw------- 1 root root 249, 0 Aug 27 05:17 watchdog0
crw-rw-rw- 1 root root 1, 5 Aug 27 05:17 zero
As you can see there are a lot of devices, and some of those are pipes/other linux things. To get a list of BLOCK devices, we can either use the lsblk command or we can go into the /dev/block folder and type ls...
/dev/block$ ls -l
total 0
lrwxrwxrwx 1 root root 10 Aug 27 05:17 179:0 -> ../mmcblk0
lrwxrwxrwx 1 root root 12 Aug 27 05:17 179:1 -> ../mmcblk0p1
lrwxrwxrwx 1 root root 12 Aug 27 05:17 179:2 -> ../mmcblk0p2
lrwxrwxrwx 1 root root 6 Aug 27 05:17 8:0 -> ../sda
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:1 -> ../sda1
lrwxrwxrwx 1 root root 8 Aug 27 05:17 8:10 -> ../sda10
lrwxrwxrwx 1 root root 8 Aug 27 05:17 8:11 -> ../sda11
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:2 -> ../sda2
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:3 -> ../sda3
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:4 -> ../sda4
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:5 -> ../sda5
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:6 -> ../sda6
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:7 -> ../sda7
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:8 -> ../sda8
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:9 -> ../sda9
Here you can see my sdcard (mmcblk0) and my primary hard drive (sda). The number at the end represents the partition number. As you cans see, I have 11 partitions on my hard drive on my laptop and my sdcard has 2 partitions (in liunx the first of almost everything is 0 instead of 1).
Those ARE real partitions... but the storage isn't exactly like a hard disk drive. All of the information is saved on memory chips in the phone, whereas a hard disk drive (HDD) uses magnetic dust to signify bits (if more dust is on the top of the sector it's a 1, and if more dust is down it's a zero). Also, there are MANY more Android partitions than the partitions that you listed.... using the "cat" command you can print a text file to the screen in linux (including Android) and the /proc/ folder has a bunch of text files with information about your device. Typing the command "cat /proc/partitions" on my ZTE prints this out...
$ cat /proc/partitions
major minor #blocks name
253 0 196608 zram0
179 0 7634944 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 90112 mmcblk0p11
179 12 49152 mmcblk0p12
179 13 49152 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 540672 mmcblk0p28
179 29 2621440 mmcblk0p29
179 30 4030447 mmcblk0p30
179 64 4096 mmcblk0rpmb
179 128 31260672 mmcblk1
179 129 31256576 mmcblk1p1
254 0 4030431 dm-0
Each of those partitions stores different information in them. One is the cache partition, which is where all app data is stored. One is for the baseband (cellular radio chip), zram0 is RAM, system contains the Android system file (like c:\windows). Nowadays, there is an frp partition to lock the device if someone attempts to factory reset the device, the account information is still maintained (as the data and cache partitions are formatted but frp isn't, and therefore Android won't let you in unless you supply the username and password). The laf partition has to do with Fastboot (a PC command line program to change the partitions) and there are also vendor, firmware, carrier, and several others that I don't know the purpose of.
I hope this helped you and maybe some other people.

Using fastboot to flash LG firmware

Hi,
Has anyone tried using this approach with LG phones? I have an LG Stylo that I need to restore the original firmware on. I tried some utilities like LG UP and others but couldn't get it done with them.
Any ideas/suggestions? Here's how the extracted LG image looks like:
Code:
$ ls -ln
total 6603364
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 BackupGPT_30784512.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 PrimaryGPT_0.bin
-rw-r--r-- 1 1000 1000 1048576 Jul 19 2018 aboot_300032.bin
-rw-r--r-- 1 1000 1000 1048576 Jul 19 2018 abootbak_304128.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 apdp_1064960.bin
-rw-r--r-- 1 1000 1000 15728640 Jul 19 2018 boot_442368.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 cmnlib64_1086464.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 cmnlib64bak_1087488.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 cmnlib_1084416.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 cmnlibbak_1085440.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 devcfg_1068032.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 devcfgbak_1069056.bin
-rw-r--r-- 1 1000 1000 16777216 Aug 17 2018 dsp_212992.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 factory_704512.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 keymaster_1088512.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 keymasterbak_1089536.bin
-rw-r--r-- 1 1000 1000 18874368 Jul 19 2018 laf_507904.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 lksecapp_1082368.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 lksecappbak_1083392.bin
-rw-r--r-- 1 1000 1000 88080384 Aug 19 2018 modem_16384.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 msadp_1065984.bin
-rw-r--r-- 1 1000 1000 5242880 Jul 19 2018 persist_786432.bin
-rw-r--r-- 1 1000 1000 1572864 Jul 19 2018 raw_resources_770048.bin
-rw-r--r-- 1 1000 1000 1572864 Jul 19 2018 raw_resourcesbak_778240.bin
-rw-r--r-- 1 1000 1000 17825792 Jul 19 2018 recovery_573440.bin
-rw-r--r-- 1 1000 1000 17825792 Jul 19 2018 recoverybak_638976.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 rpm_202752.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 rpmbak_203776.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 sbl1_198656.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 sbl1bak_200704.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 sec_299008.bin
-rw-r--r-- 1 1000 1000 134217728 Jul 19 2018 system_1130496.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 system_1392640.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 system_1394312.bin
-rw-r--r-- 1 1000 1000 131596288 Jul 19 2018 system_1398416.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_1658888.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 system_1918600.bin
-rw-r--r-- 1 1000 1000 131596288 Jul 19 2018 system_1922704.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_2183176.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 system_2442888.bin
-rw-r--r-- 1 1000 1000 131596288 Jul 19 2018 system_2446992.bin
-rw-r--r-- 1 1000 1000 5767168 Jul 19 2018 system_2707464.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 system_2965504.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 system_2967176.bin
-rw-r--r-- 1 1000 1000 131596288 Jul 19 2018 system_2971280.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_3231752.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 system_3491464.bin
-rw-r--r-- 1 1000 1000 131596288 Jul 19 2018 system_3495568.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_3756040.bin
-rw-r--r-- 1 1000 1000 1048576 Jul 19 2018 system_4018184.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 system_4276224.bin
-rw-r--r-- 1 1000 1000 39845888 Jul 19 2018 system_4280328.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 system_4538368.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_4542472.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_4804616.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_5066760.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_5328904.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_5591048.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_5853192.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_6115336.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_6377480.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_6639624.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_6901768.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_7163912.bin
-rw-r--r-- 1 1000 1000 132644864 Jul 19 2018 system_7426056.bin
-rw-r--r-- 1 1000 1000 524288 Jul 19 2018 system_7685768.bin
-rw-r--r-- 1 1000 1000 177733632 Jul 19 2018 system_7689216.bin
-rw-r--r-- 1 1000 1000 1572864 Jul 19 2018 tz_204800.bin
-rw-r--r-- 1 1000 1000 1572864 Jul 19 2018 tzbak_208896.bin

@greerdd
IMHO Google's fastboot is the wrong tool to flash stock firmware onto LG device , the only reliable stock firmware flashing tools are LG Flash Tool and/or LGUp in conjunction with the device-matching USB-driver provided by LG.

I tried both LG UP and LG Flash Tool but did not have much success with them. It's been a while ago but if I remember correctly LG UP did not see the connected phone thus refusing to proceed with the flash, LG Flash Tool recognized the phone but was giving error messages (something about Milky Way or whatever).
That's the reason I was trying to get it done with fastboot. The phone in question is actually LG Stylo 2 (K550 model).