So on previous devices, I'm used to the MTD filesystem/partition approach. Today, I was trying to find information on how to access the EMMC partitions from the internal command line and I was not able to find anything.
I know that typing the following gives me a list of all the EMMC partitions (I remember using /proc/mtd on the Evo 4G):
Code:
cat /proc/emmc
However, if I then go to backup my BOOT partition with this command, I find that there is no /dev/emmc device (or anything close):
Code:
dd if=/dev/emmc/mmcblk0p21 of=/sdcard/boot.img bs=4096
So, perhaps stupid question, but I've spent 20 minutes running various searches on EMMC, MTD, mount points, etc. with no answer. How can I run the DD command listed above and access the proper partition?
Slappy_G said:
So on previous devices, I'm used to the MTD filesystem/partition approach. Today, I was trying to find information on how to access the EMMC partitions from the internal command line and I was not able to find anything.
I know that typing the following gives me a list of all the EMMC partitions (I remember using /proc/mtd on the Evo 4G):
Code:
cat /proc/emmc
However, if I then go to backup my BOOT partition with this command, I find that there is no /dev/emmc device (or anything close):
Code:
dd if=/dev/emmc/mmcblk0p21 of=/sdcard/boot.img bs=4096
So, perhaps stupid question, but I've spent 20 minutes running various searches on EMMC, MTD, mount points, etc. with no answer. How can I run the DD command listed above and access the proper partition?
Click to expand...
Click to collapse
Off the top of my head, I forgot the commands and dont have the device in front of me .. BUT I do remember some of the information.
Starting off, the command you give /dev/emmc/mmcblk0p21 is close but not quite. You might need to double check, but I'm thinking /dev/block/mmcblk0p21 ... if that is correct, then the partitions should all be listed under /dev/block.
If not, I'd suggest looking around that area because that is where they are located.
Google'd "/dev/block/mmcblk0p21" and seems to be quite a few results. I'm thinking that should be the area where the partitions are listed, /dev/block. As you mentioned /proc/emmc should give the corresponding labels and block device names.
Hope that helps!
your device needs to be rooted
adb shell
adb su
dd if=/dev/emmc/mmcblk0p21 of=/sdcard/boot.img bs=4096
joeykrim said:
Off the top of my head, I forgot the commands and dont have the device in front of me .. BUT I do remember some of the information.
Starting off, the command you give /dev/emmc/mmcblk0p21 is close but not quite. You might need to double check, but I'm thinking /dev/block/mmcblk0p21 ... if that is correct, then the partitions should all be listed under /dev/block.
If not, I'd suggest looking around that area because that is where they are located.
Google'd "/dev/block/mmcblk0p21" and seems to be quite a few results. I'm thinking that should be the area where the partitions are listed, /dev/block. As you mentioned /proc/emmc should give the corresponding labels and block device names.
Hope that helps!
Click to expand...
Click to collapse
Perfect - I didn't think to look under the "block" device. That was the missing piece for me. I appreciate the help.
globula_neagra said:
your device needs to be rooted
adb shell
adb su
dd if=/dev/emmc/mmcblk0p21 of=/sdcard/boot.img bs=4096
Click to expand...
Click to collapse
Unfortunately, this won't work. The missing piece is that the device name is "block" not "emmc" - thanks to joeykrim above.
179 0 15267840 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 32 mmcblk0p13
179 14 6144 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 46080 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 8190 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 16383 mmcblk0p22
179 23 1022 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 4096 mmcblk0p25
179 26 20480 mmcblk0p26
179 27 4 mmcblk0p27
179 28 256 mmcblk0p28
179 29 16 mmcblk0p29
179 30 1280 mmcblk0p30
179 31 64 mmcblk0p31
179 32 256 mmcblk0p32
179 33 256 mmcblk0p33
179 34 99239 mmcblk0p34
179 35 1277951 mmcblk0p35
179 36 229375 mmcblk0p36
179 37 2260991 mmcblk0p37
179 38 10418176 mmcblk0p38
179 64 30657536 mmcblk1
179 65 30653440 mmcblk1p1
/dev/block/mmcblk0p17 /firmware_radio
/dev/block/mmcblk0p18 /firmware_q6
/dev/block/mmcblk0p19 /firmware_wcnss
/dev/block/mmcblk0p26 /devlog
/dev/block/mmcblk0p35 /system
/dev/block/mmcblk0p37 /data
/dev/block/mmcblk0p36 /cache
I know I'm necrobumping a really old thread, and I'm sorry for that, but which one is for the internal sdcard?
FIXED!
I took a stab in the dark after doing a pull of the partitions to my backup hard drive and formatted the last, and largest partition on the list. It calculated out to about what my internal storage was supposed to be, which made me fairly confident that it was the one.
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p28
I tossed that little command into the shell through adb and /emmc/ mounted right up.
Hey guys, I seem to have corrupted my mmcblk0 rather well. mmcblk0p1-4 have no bounds. (Edit 4: This sounds rather silly now that I know more of what I'm looking at. mmcblk0p4 contains all of the partitions after it. partitions 1 - 4 just don't fall on the cylinder lines like the file system expects it to) Anyway, I was wondering if anyone would be kind enough to either copy/paste a stock emmc partition table (/dev/block/mmcblk0), or toss together a CWM flashable that reformats it properly so I can get my internal storage back.
An example of what I'm talking about:
http://forum.xda-developers.com/showpost.php?p=25436995&postcount=2
Thanks!
What my partition table looks like...
Code:
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 92 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 51 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 1923584 15284271+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 13313 13375 500 47 Unknown
/dev/block/mmcblk0p6 13825 14080 2048 45 Unknown
/dev/block/mmcblk0p7 14337 14649 2500 4c Unknown
/dev/block/mmcblk0p8 14849 16128 10240 48 Unknown
/dev/block/mmcblk0p9 16385 16447 500 46 Unknown
/dev/block/mmcblk0p10 16897 16959 500 5d Unknown
/dev/block/mmcblk0p11 17409 17471 500 91 Unknown
/dev/block/mmcblk0p12 17921 19200 10240 93 Unknown
/dev/block/mmcblk0p13 19457 32000 100352 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p14 32257 32640 3072 4a Unknown
/dev/block/mmcblk0p15 32769 33152 3072 4b Unknown
/dev/block/mmcblk0p16 33281 33664 3072 58 Unknown
/dev/block/mmcblk0p17 33793 46336 100352 8f Unknown
/dev/block/mmcblk0p18 46593 46976 3072 59 Unknown
/dev/block/mmcblk0p19 47105 47488 3072 5a Unknown
/dev/block/mmcblk0p20 47617 48000 3072 5b Unknown
/dev/block/mmcblk0p21 48129 49408 10240 ab Darwin boot
/dev/block/mmcblk0p22 49665 50944 10240 60 Unknown
/dev/block/mmcblk0p23 51201 52480 10240 94 Unknown
/dev/block/mmcblk0p24 52737 183808 1048576 a5 FreeBSD
/dev/block/mmcblk0p25 183809 446208 2099200 a6 OpenBSD
/dev/block/mmcblk0p26 446465 485120 309248 a8 Darwin UFS
/dev/block/mmcblk0p27 485377 501888 132096 a9 NetBSD
/dev/block/mmcblk0p28 502273 1923584 11370496 90 Unknown
Edit: I can tcp/ip adb into the device now. Still not sure what's up with my usb connectivity.
Both TWRP and CWM repartition. Have you tried them?
fprice02 said:
Both TWRP and CWM repartition. Have you tried them?
Click to expand...
Click to collapse
Yes, CWM. It can't mount /emmc/ which is why I'm trying to do it this way. I've spent most of the afternoon going through the steep learning curve that is android/linux file systems on a windows machine. Partition 4 actually contains all the partitions after it, which makes it more fun to figure out which one is the internal storage partition(s).
FIXED
So I fixed it. I took a stab in the dark after doing a pull of the partitions to my backup hard drive and formatted the last, and largest partition on the list. It calculated out to about what my internal storage was supposed to be, which made me fairly confident that it was the one.
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p28
I tossed that little command into the shell through adb and /emmc/ mounted right up.
MSDOS......classic on a linux platform.
hello all
i just trying to make cwm for my brand new SAMSUNG GALAXY STAR G-S5282 but coudnt find any source orsomething like that... its running jelly bean i try to dump boot image but its says
Code:
dump_image boot boot.img
/system/bin/sh: dump_image: not found
ok now something wron it dont have dump_image file in it
partitions of this mobile is
Code:
cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 3840 mmcblk0p1
179 2 3840 mmcblk0p2
179 3 5120 mmcblk0p3
179 4 5120 mmcblk0p4
179 5 10240 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 3840 mmcblk0p12
179 13 3840 mmcblk0p13
179 14 3840 mmcblk0p14
179 15 3840 mmcblk0p15
179 16 256 mmcblk0p16
179 17 256 mmcblk0p17
179 18 256 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 524288 mmcblk0p20
179 21 917504 mmcblk0p21
179 22 131072 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 10240 mmcblk0p24
179 25 2121728 mmcblk0p25
179 26 8 mmcblk0p26
179 27 1024 mmcblk0p27
mounts
Code:
cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1
/dev/block/mmcblk0p21 /system ext4 ro,relatime,
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,node
mit,data=ordered 0 0
/dev/block/mmcblk0p20 /cache ext4 rw,nosuid,nod
bmit,data=ordered 0 0
/dev/block/mmcblk0p19 /efs ext4 rw,nosuid,nodev
commit,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev
up_id=1023,default_permissions,allow_other 0 0
now is there any wy to make dump of boot.img or recovery.img for making cwm?
touseefiqbal said:
now is there any wy to make dump of boot.img or recovery.img for making cwm?
Click to expand...
Click to collapse
Yes you can dump both boot.img and recovery.img provided you have root access by using the following commands:
First:
Code:
cd /dev/block/platform
Then list which platform name you have:
Code:
ls
After change into the platform name directory (The following is an example from my Verizon Galaxy S3):
Code:
cd msm_sdcc.1/by-name
Then:
Code:
ls -l
This command will list what partitions are the boot and recovery partitions make sure to note which block number the recovery and boot partitions are. Now that we know what block number the partitions we want are we can dump them:
Code:
cat /dev/block/recovery_partition_block number > /mnt/sdcard/recovery.img
cat /dev/block/boot_partition_block number > /mnt/sdcard/boot.img
You should now have recovery.img and boot.img files located on your sdcard. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
shimp208 said:
Yes you can dump both boot.img and recovery.img provided you have root access by using the following commands:
First:
Code:
cd /dev/block/platform
Then list which platform name you have:
Code:
ls
After change into the platform name directory (The following is an example from my Verizon Galaxy S3):
Code:
cd msm_sdcc.1/by-name
Then:
Code:
ls -l
This command will list what partitions are the boot and recovery partitions make sure to note which block number the recovery and boot partitions are. Now that we know what block number the partitions we want are we can dump them:
Code:
cat /dev/block/recovery_partition_block number > /mnt/sdcard/recovery.img
cat /dev/block/boot_partition_block number > /mnt/sdcard/boot.img
You should now have recovery.img and boot.img files located on your sdcard. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
sorry i didnt tell you that i dont have root access
I dnt hav root access
Sent from my GT-S5282 using XDA Premium HD app
touseefiqbal said:
sorry i didnt tell you that i dont have root access
Click to expand...
Click to collapse
If you want to root your device I would recommend checking out this thread
http://forum.xda-developers.com/showthread.php?t=2320771 on how to root the Galaxy Star.
Sent from my SCH-I535 using xda premium
As you can see, I can not find where is boot.img in, cuold you pls show me, thank.
shimp208 said:
If you want to root your device I would recommend checking out this thread
http://forum.xda-developers.com/showthread.php?t=2320771 on how to root the Galaxy Star.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
My divice is rooted
Try to get recovery bro
Sent from my GT-S5282 using XDA Premium HD app
touseefiqbal said:
Try to get recovery bro
Sent from my GT-S5282 using XDA Premium HD app
Click to expand...
Click to collapse
I've get recovery.img already thank your method above, but I want to get boot.img and can not see where.
hi
oldmanhp said:
I've get recovery.img already thank your method above, but I want to get boot.img and can not see where.
Click to expand...
Click to collapse
can you plz share recovery? i will help you to get boot.img
one more thing is it recovery for galaxy star gt-s5282? if yes pl share
ter
oldmanhp said:
I've get recovery.img already thank your method above, but I want to get boot.img and can not see where.
Click to expand...
Click to collapse
install terminal emulator and type
Code:
dump_image boot /sdcard/boot.img
touseefiqbal said:
can you plz share recovery? i will help you to get boot.img
one more thing is it recovery for galaxy star gt-s5282? if yes pl share
Click to expand...
Click to collapse
Here you are, post #48, it is for Galaxy Mega gt-i9152.
http://forum.xda-developers.com/showthread.php?p=44268116#post44268116
oldmanhp said:
I've get recovery.img already thank your method above, but I want to get boot.img and can not see where.
Click to expand...
Click to collapse
To get boot.img I would recommend dumping the partition named KERNEL which from the output you provided is /dev/block/mmcblk0p5 the device's kernel is usually stored on the /boot partition, so from what I can tell /dev/block/mmcblk0p5 appears to be the boot partition that you could then dump to get a boot.img file.
q
shimp208 said:
To get boot.img I would recommend dumping the partition named KERNEL which from the output you provided is /dev/block/mmcblk0p5 the device's kernel is usually stored on the /boot partition, so from what I can tell /dev/block/mmcblk0p5 appears to be the boot partition that you could then dump to get a boot.img file.
Click to expand...
Click to collapse
also if you hav cwm reovery then through recovery go for a backup
Good news. Root is on the way. I have found an exploit (namely the dirty cow exploit to gain root access), only problem is my root lasts for 1 command and I am trying to work out a way to transfer over the su binary itself. I will update this post once I have more info.
ALSO, AND THIS IS IMPORTANT. IF YOU WANT ROOT, DO NOT UPDATE TO ZV6 WHEN IT DROPS. ZV6 WILL LIKELY PATCH THIS EXPLOIT.
Reserved
Following!
Noticed on another forum, ZV6 has appeared.
I cannot remember if you are given a choice whether to install these or not...turned off wifi/data just in case, lol.
It will download the update, but it won't install without your permission. As an update on root. I have a root shell, but I cannot do anything thanks to SELinux. I need to find an exploit to get around SELinux.
Code:
λ adb -d shell
[email protected]:/ $ run-as exec whoami
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
root
[email protected]:/ $ run-as exec dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
dd: /dev/block/bootdevice/by-name/boot: Permission denied
I knew about ZV6 because I saw the kernel sourrces when I went to download the ZV5 source
if this helps........
EagerestWolf said:
Reserved
Click to expand...
Click to collapse
https://mega.nz/#!6BMlmIZB!CBKqxLvGl3c2EfYXj6_hIbdUKxPtbfWzgoglQb0d5aA
thats the ZV5 update for the LGLS775ABB that popped up on my LGLS775ABB ZVZ4!
454.4mb.zip, unzips to 1.02gb..............
If you can get any way to recovery from a predicament out of it, please share!
zach
---------- Post added at 11:16 PM ---------- Previous post was at 11:10 PM ----------
EagerestWolf said:
It will download the update, but it won't install without your permission. As an update on root. I have a root shell, but I cannot do anything thanks to SELinux. I need to find an exploit to get around SELinux.
Code:
λ adb -d shell
[email protected]:/ $ run-as exec whoami
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
root
[email protected]:/ $ run-as exec dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
dd: /dev/block/bootdevice/by-name/boot: Permission denied
Click to expand...
Click to collapse
Definitely no dev here, but using a selenix mode changer app, in 5.1.1, linking su binaries from su/bin to system/xbin allowed it to set selenix to permissice on the Samsung Galaxy J3 (2016) SM-J320P until we got a permissive kernel. That phone has one messed up os hyrbid odex & deodex mix..............
zach...........
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
EagerestWolf said:
I knew about ZV6 because I saw the kernel sourrces when I went to download the ZV5 source
Click to expand...
Click to collapse
If your kdz's available you can't be talking about the BOOST Mobile Stylo 2........... only one LG's not coughing up software for........ oh well, damn, thought I had found something going somewhere for this device..............
Yes that link above is for BOOST LG Stylo 2! The update was waiting right out of the box, it was already on ZV4 so factory reset hooked it up immediately and run a log cat until it acquired the update again. Then spent about 20 minutes going through all the https links until finding the one the update was coming from and downloaded to the Windows machine.
zach
If you go to LG's Open Source Website. They have all the kernel sources there. ZV6 is listed so it's coming. As for your update package, I looked and I wasn't sure if I saw a recovery image, but I did see a LAF image, which is also helpful.
As for bypassing SELinux, I have a few leads on that one. Once we have root, we will have recovery and ROM's, but we need root first to fix fastboot.
I am actually going to try injecting a modified kernel into your update an flashing it. Since this is an official FOTA. It may work.
!!!!!!!
EagerestWolf said:
I am actually going to try injecting a modified kernel into your update an flashing it. Since this is an official FOTA. It may work.
Click to expand...
Click to collapse
Coolbeans!!! Its signed, can't remember the name but do remember seeing the signature verification. I used winrar so nothing should be messed up with it as well.
Any help, anything, just let me know! I cannot understand why another excellent phone for this price is drifting str8 past any development. Went to Asus after I first got into modding and my HTC burnt..... left them due to their never unlocking bootloaders, etc.... Samsung next, the J3, one messed up piece of os there but we modded the hell out of it, now LG............ every variant of this device has the kdz available if I'm not mistaken. If temp root had to be forced onto this phone, to dd it it would just about be worth the $119 it cost me!
zach
TWRP
EagerestWolf said:
I am actually going to try injecting a modified kernel into your update an flashing it. Since this is an official FOTA. It may work.
Click to expand...
Click to collapse
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
That won't work, we need root, and before we can do anything related to TWRP, we need fastboot, so this is all in vain.
Sent from my LGLS775 using Tapatalk
coolbeans2016 said:
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
Click to expand...
Click to collapse
I can provide a stock boot.img I have for LS775 ZV5 build, but cat /proc/cmline is useless right now. I do get some output with cat /proc/partitions and cat /proc/mounts
Code:
major minor #blocks name
253 0 485204 zram0
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 1536 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 512 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 24576 mmcblk0p18
179 19 24576 mmcblk0p19
179 20 24576 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 512 mmcblk0p27
179 28 512 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 10240 mmcblk0p31
259 0 8192 mmcblk0p32
259 1 8192 mmcblk0p33
259 2 65536 mmcblk0p34
259 3 1024 mmcblk0p35
259 4 2560 mmcblk0p36
259 5 2048 mmcblk0p37
259 6 6144 mmcblk0p38
259 7 40960 mmcblk0p39
259 8 3207168 mmcblk0p40
259 9 921600 mmcblk0p41
259 10 10915840 mmcblk0p42
259 11 8175 mmcblk0p43
179 32 4096 mmcblk0rpmb
Code:
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
/dev/pstore /dev/pstore pstore rw,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/carrier /carrier ext4 rw,seclabel,nodev,relatime,noauto_da_alloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
EagerestWolf said:
That won't work, we need root, and before we can do anything related to TWRP, we need fastboot, so this is all in vain.
Sent from my LGLS775 using Tapatalk
Click to expand...
Click to collapse
Have you been able to achieve some progress? If you need to try I have some time and one of these phone to try. I really need root on this version.
coolbeans2016 said:
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
Click to expand...
Click to collapse
You can get your cmdline from unpacked boot
Sent from my SM-J320P using Tapatalk
coolbeans2016 said:
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
Click to expand...
Click to collapse
rick.wardenburg said:
You can get your cmdline from unpacked boot
Sent from my SM-J320P using Tapatalk
Click to expand...
Click to collapse
This is cmdline from unpacked boot image.
Code:
cmdline = console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=ph1 user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 vmalloc=600m
Any progress on this or is it a another dead end for us?
Sent from my LGLS775 using Tapatalk
can someone pm me when you do obtain root permanently
....will keep checking...also i can make a stock dimp of my zv4 if ne one needs it since lg likes to keep everything tight....does anyone know how to enter download mode??
Doctur said:
can someone pm me when you do obtain root permanently
....will keep checking...also i can make a stock dimp of my zv4 if ne one needs it since lg likes to keep everything tight....does anyone know how to enter download mode??
Click to expand...
Click to collapse
And if someone tells you, please tell me. : )
I was going to root my friends Android, however after further discovery --- thus far--- it looks like this device has not been rooted yet.
Is anyone able to create a partion.xml for use with tool studio eMMC download tool. Im trying to figure it out myself and having a little trouble but I believe it should allow us to flash the v3 firmware.