Database Users

LG G4 partition info

adb shell ls -la /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root root 2015-01-02 19:51 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-02 19:51 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-02 19:51 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-02 19:51 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-02 19:51 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2015-01-02 19:51 cache -> /dev/block/mmcblk0p54
lrwxrwxrwx root root 2015-01-02 19:51 carrier -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2015-01-02 19:51 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-02 19:51 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-02 19:51 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2015-01-02 19:51 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-02 19:51 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-02 19:51 eri -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-01-02 19:51 factory -> /dev/block/mmcblk0p49
lrwxrwxrwx root root 2015-01-02 19:51 felica -> /dev/block/mmcblk0p48
lrwxrwxrwx root root 2015-01-02 19:51 fota -> /dev/block/mmcblk0p51
lrwxrwxrwx root root 2015-01-02 19:51 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-02 19:51 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-02 19:51 grow -> /dev/block/mmcblk0p56
lrwxrwxrwx root root 2015-01-02 19:51 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-02 19:51 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-02 19:51 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-02 19:51 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-02 19:51 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-02 19:51 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-02 19:51 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-02 19:51 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-02 19:51 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-02 19:51 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-01-02 19:51 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-02 19:51 operatorlogging -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2015-01-02 19:51 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-02 19:51 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-02 19:51 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-02 19:51 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-02 19:51 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-01-02 19:51 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-01-02 19:51 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-02 19:51 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2015-01-02 19:51 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-02 19:51 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-02 19:51 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-02 19:51 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-01-02 19:51 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-02 19:51 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-02 19:51 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-02 19:51 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2015-01-02 19:51 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-02 19:51 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-02 19:51 spare3 -> /dev/block/mmcblk0p50
lrwxrwxrwx root root 2015-01-02 19:51 spare4 -> /dev/block/mmcblk0p52
lrwxrwxrwx root root 2015-01-02 19:51 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-02 19:51 system -> /dev/block/mmcblk0p53
lrwxrwxrwx root root 2015-01-02 19:51 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-02 19:51 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-02 19:51 userdata -> /dev/block/mmcblk0p55

Thx. System dump possible?

Please, adb pull /system.

What are the partitions spare1-4 used for? I've pulled mine using dd, but they appear to be completely empty.

can fix boot loop?
How can i use this to fix my boot loop g4?

LG G Stylo (Boost Mobile) [UPDATED July 27]

Do not use this root method for 5.1.1!! You will get a soft brick and there is no way to recover! If your on 5.0.2 and did not take the update then you can proceed to this root method.
Here is the untouched update to 5.1.1:
udpate.zip
UPDATE: 6/25
BOOST MOBILE HAS RELEASED AN UPDATE! The update is around 413MB. I pulled the update and will be updating it soon. If you are rooted do not update the phone. It could cause a brick and or unroot the device! So far I just found a new radio.img inside of it. I'll check it out later this afternoon.
Hello everyone,
I wanted to make this thread for the LG G Stylo (Boost Mobile) cause I could not find any forums or any post about this device!
Anyways if you are looking for a ROOT method for this device visit here:
Proof (picture) that the device is rooted at the bottom of this post.
LG One Click Root 1.3 (Graphic UI):
Code:
[url]http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951[/url]
Here is the PARTITIONS from the device:
Code:
[email protected]:/ $ su
[email protected]:/ # ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-04 18:18 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-04 18:18 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-04 18:18 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-04 18:18 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-04 18:18 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-04 18:18 carrier -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-04 18:18 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-04 18:18 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-04 18:18 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-04 18:18 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-04 18:18 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-04 18:18 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-04 18:18 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-04 18:18 grow -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-04 18:18 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-04 18:18 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-04 18:18 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-04 18:18 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-04 18:18 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-04 18:18 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-04 18:18 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-04 18:18 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-04 18:18 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-04 18:18 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-04 18:18 pad2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-04 18:18 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-04 18:18 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-04 18:18 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-04 18:18 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-04 18:18 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-04 18:18 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-04 18:18 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-04 18:18 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-04 18:18 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-04 18:18 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-04 18:18 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-04 18:18 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-04 18:18 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-04 18:18 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-04 18:18 userdata -> /dev/block/mmcblk0p39
[email protected]:/ #
Here is how to get into STOCK RECOVERY:
Code:
1) Turn the device off
2) While holding the phone on, press and hold VOLUME -(DOWN) at the same time
3) When you see the LG boot logo hurry up and let go of the VOLUME -(DOWN) and hold it again for a few sec (kinda tricky)
4) Then this will get you into recovery mode
Here is how to get into DOWNLOAD MODE:
Code:
1) Turn the device off
2) While holding the VOLUME +(UP) key plug in the device into the pc
3) A screen should pop up and press the VOLUME +(UP) key until you see DOWNLOAD MODE with the progress bar
4) Done
NOTE: Pull out the battery once your done in DOWNLOAD MODE to get out of it and power the device like normal.
SYSTEM DUMP:
NOTE: These files are from 5.0.2 NOT 5.1.1!
Code:
[URL="http://www.mediafire.com/download/grau3kv5m1rbzwa/aboot.img"]aboot.img[/URL]
[URL="http://www.mediafire.com/download/f6cly93iusa83xz/boot.img"]boot.img [/URL]
[URL="http://www.mediafire.com/download/1opyd4a9fimbw8p/laf.img"]laf.img[/URL]
[URL="http://www.mediafire.com/download/qt3o5rrm4h2qo5o/recovery.img"]recovery.img[/URL]
[URL="http://www.mediafire.com/download/t7a3qq60xh2pm0c/system.zip"]system.img[/URL]
All files will be uploaded to my mediafire account!
Please make mirrors if you like.
NOTE: I am not a DEV! I will upload files to help others try to get something going for this device. I will test things as I go.

Just tried this root method on the TMO version of this and out didn't start. Curiously tried the manual method for the G3/G4 and i get a device offline when doing an ADB device list.
Sent from my LG-H631 using XDA Free mobile app

Make sure you install the right drivers. I had to install the drivers and then restart my laptop. It took me like 2-3 times to finally root the device with the Graphical UI method. On a side note I had to toggle MTP and the other one and then let the drivers install for each one. I then put the phone into charge mode and it finally rooted.

I will give it one more try tonight. I had uninstalled and re installed the LG drivers a few times. I can connect fine to my L90 and my G2. But for some reason this thing shows connected but "offline" in ADB. Toggled back and forth between MTP and PTP a few times too. No response when in download mode ekther.
Sent from my LG-H631 using XDA Free mobile app

Any luck Cahiatt on the root? My LG Flex has an issue that I have to send it back for repairs and I've been considering ordering the Stylo. Just need root though for all the stuff I like to do.
Thanks!

Haven't gone back to it yet. Ended up on other chores for the weekend.
Sent from my LG-H631 using XDA Free mobile app

Well the short answer is this worked on the TMO version also.
I don't have a long answer. For whatever reason when I tried again it just worked. There must have been something software related hanging on my desktop PC that was interfering with the port used by ADB or who knows what. I just went back, plugged the phone in and it worked. Woo Hoo!!!!
Sent from my LG-H631 using XDA Free mobile app

Can anyone with the tmobile stylo confirm the 2gb ram and 13mp cam?
Im considering this over the g4, more budget friendly.
I have a few questions.
Hows the lcd? Does it show alot of pixelation? Im hearing its pretty good for 720p.
Does it have a notification led?
I know it has lollipop but is it 5.0, 5.0.2 or 5.1?
Pretty good specs for under $300 id say.

fix-this! said:
Can anyone with the tmobile stylo confirm the 2gb ram and 13mp cam?
Im considering this over the g4, more budget friendly.
I have a few questions.
Hows the lcd? Does it show alot of pixelation? Im hearing its pretty good for 720p.
Does it have a notification led?
I know it has lollipop but is it 5.0, 5.0.2 or 5.1?
Pretty good specs for under $300 id say.
Click to expand...
Click to collapse
LCD is pretty good. I came from a G2 and don't notice any pixelation. Text and video quality is very good. It isn't as bright outdoors and doesn't have auto brightness but am pleased with it.
Camera is 13mp. Pictures seem better than my G2. Better focus.
Does have notification LED.
Running 5.0.2
It does have 2gb of RAM and performs similarly to my G2 before. WiFi and cell reception actually seem better also.
I think it is a pretty solid device for the price. I actually wish it were a little smaller but it is still relatively thin and light for the size.
Sent from my LG-H631 using XDA Free mobile app

i might pick one up today. anybody know if twrp is available so we can have a backup in case of a softbrick? hoping xda make a section for this device.

As far as TWRP no one has compiled it for this device yet. The device is pretty new so I would give it some time.

HTML:
ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-01 21:24 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 21:24 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 21:24 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 21:24 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 21:24 cache -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-01 21:24 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 21:24 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 21:24 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 21:24 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 21:24 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 21:24 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 21:24 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 21:24 grow -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-01 21:24 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 21:24 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 21:24 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 21:24 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 21:24 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 21:24 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 21:24 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 21:24 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 21:24 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 21:24 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 21:24 pad2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 21:24 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 21:24 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 21:24 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 21:24 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 21:24 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 21:24 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 21:24 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 21:24 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 21:24 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 21:24 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 21:24 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 21:24 system -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 21:24 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 21:24 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 21:24 userdata -> /dev/block/mmcblk0p38
[email protected]:/ $
heres the mounts for the tmobile lg g stylo.

and heres a system dump for the tmobile variant. might help get development going.
mega link: https://mega.co.nz/#!R1VwiLiA!GJ2O1Tw-pVw2P8QEHcpM0c464Qlq6Ro8CZty0YAkNs4

I took the plunge yesterday and got the T-Mobile variant. So far, it's been pretty nice. I would ding the camera app a star, though, since it doesn't seem to offer any manual exposure controls. You can choose between standard and HDR mode, and if HDR is off, you can chose off/manual/auto flash. I'm guessing they don't want to steal the G4's thunder. That being said, it takes very nice pictures, and the autofocus is nice and fast.
This morning, I had one glitch: Google Maps and Google Play Music weren't playing any sounds, even though I could hear sound effects when I tapped the screen. I rebooted and the problem went away, and haven't had any further trouble.
I like the screen - it's nice and bright and has good contrast. Sure, it's 720p instead of qHD, but it's plenty sharp for me. The phone seems nice and snappy, and doesn't seem laggy at all. It's nice that the T-Mobile version has 2 GB RAM and 16 GB internal storage.
From what I've seen so far, the battery should hold up nicely. However, the supplied 1.2A charger seems to run a bit hot. I'll be using the 2A charger that came with my Avant instead. I did make sure to unlock the Avant before upgrading; its supplied app unlocked the phone without any hassle.
Overall, for a budget phablet, it's quite good. I had been considering a ZTE Zmax, but I'm glad I held out for the Stylo, even if I rarely use the stylus.
I'm going to have to update my signature.

The lcd is my biggest issue. Even for 720p hd its got alot of pixelation on the fonts. My moto e 2015 actually renders better. :/ i assume this is becuase its a large lcd at 5.7". Wish lg would of gave it 1080p.
Its strong points are the camera and the overall design of the device, very sleek compared to the g3 or g4. Especially the back of the phone. Little choppy performance to but i suspect this is from the 5.0.2 memory leak.
Ill test for a few days before i decide if ill keep it or not. Good budget device though.

Anyone knows if the boot loader is unlocked? I expect the MetroPCS and T-Mobile variants to have one.

fix-this! said:
HTML:
ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-01 21:24 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 21:24 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 21:24 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 21:24 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 21:24 cache -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-01 21:24 drm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 21:24 eksst -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 21:24 encrypt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 21:24 factory -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 21:24 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 21:24 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 21:24 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 21:24 grow -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-01 21:24 hyp -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 21:24 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 21:24 laf -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 21:24 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 21:24 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 21:24 modem -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 21:24 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 21:24 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 21:24 mpt -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 21:24 pad -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 21:24 pad2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 21:24 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 21:24 persistent -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 21:24 rct -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 21:24 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 21:24 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 21:24 rpmbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 21:24 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 21:24 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 21:24 sec -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 21:24 sns -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 21:24 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 21:24 system -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 21:24 tz -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 21:24 tzbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 21:24 userdata -> /dev/block/mmcblk0p38
[email protected]:/ $
heres the mounts for the tmobile lg g stylo.
Click to expand...
Click to collapse
Could I also get the output of adb shell cat proc/partitions and a backup of the recovery image. I'm going to unpack and repack the image which will cause the signature to change. If the bootloader is unlocked the image will still boot even after the signature has been modified.

Great to see more people on board. I'm almost positive the boot loader is locked by default. I tried to erase my laf and see if it would boot into fast boot but that was a no go. Let me know if anyone can access fast boot?

androidguy1991 said:
Great to see more people on board. I'm almost positive the boot loader is locked by default. I tried to erase my laf and see if it would boot into fast boot but that was a no go. Let me know if anyone can access fast boot?
Click to expand...
Click to collapse
Sounds like the same thing on the G4. What exactly happens after LAF is removed? I'm surprised the Send_Command root method worked for this device as it didn't for the G4.

When I removed laf it goes into the first download screen and says hold volume up to get into download mode or something like that. So I keep holding it and it does nothing. I tried to throw in some fast boot comments while its stuck on that screen and it does nothing. One thing I did find interesting is when you boot into stock recovery there is an option to reboot into bootloader but it just reboots the phone like normal.

Sprint Galaxy Note 5 SM-N920P Partition Table

Sprint Galaxy Note 5 SM-N920P Partition Table
credits @rlmiller for helping retrieve this
lrwxrwxrwx root root 2015-08-30 20:02 BOOT -> /dev/block/sda7
lrwxrwxrwx root root 2015-08-30 20:02 BOTA0 -> /dev/block/sda1
lrwxrwxrwx root root 2015-08-30 20:02 BOTA1 -> /dev/block/sda2
lrwxrwxrwx root root 2015-08-30 20:02 CACHE -> /dev/block/sda17
lrwxrwxrwx root root 2015-08-30 20:02 CARRIER -> /dev/block/sda18
lrwxrwxrwx root root 2015-08-30 20:02 DNT -> /dev/block/sda12
lrwxrwxrwx root root 2015-08-30 20:02 EFS -> /dev/block/sda3
lrwxrwxrwx root root 2015-08-30 20:02 OTA -> /dev/block/sda9
lrwxrwxrwx root root 2015-08-30 20:02 PARAM -> /dev/block/sda6
lrwxrwxrwx root root 2015-08-30 20:02 PERSDATA -> /dev/block/sda15
lrwxrwxrwx root root 2015-08-30 20:02 PERSISTENT -> /dev/block/sda13
lrwxrwxrwx root root 2015-08-30 20:02 RADIO -> /dev/block/sda10
lrwxrwxrwx root root 2015-08-30 20:02 RECOVERY -> /dev/block/sda8
lrwxrwxrwx root root 2015-08-30 20:02 STEADY -> /dev/block/sda14
lrwxrwxrwx root root 2015-08-30 20:02 SYSTEM -> /dev/block/sda16
lrwxrwxrwx root root 2015-08-30 20:02 TOMBSTONES -> /dev/block/sda11
lrwxrwxrwx root root 2015-08-30 20:02 USERDATA -> /dev/block/sda19
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs1 -> /dev/block/sda4
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs2 -> /dev/block/sda5
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs3 -> /dev/block/sdd1
Examples of some new mounting points for the SM-N920P:
Kernel - "/dev/block/platform/15570000.ufs/by-name/BOOT"
Recovery - "/dev/block/platform/15570000.ufs/by-name/RECOVERY"
System - "/dev/block/platform/15570000.ufs/by-name/SYSTEM"

Thanks for sharing. That's gonna be very helpful. The note 5 tar ball sure is light. No carrier img and lacking several other common files in the tar that we're used to seeing. Makes me wonder why Samsung has streamlined the tar balls for the note 5.

tdunham said:
Sprint Galaxy Note 5 SM-N920P Partition Table
credits @rlmiller for helping retrieve this
lrwxrwxrwx root root 2015-08-30 20:02 BOOT -> /dev/block/sda7
lrwxrwxrwx root root 2015-08-30 20:02 BOTA0 -> /dev/block/sda1
lrwxrwxrwx root root 2015-08-30 20:02 BOTA1 -> /dev/block/sda2
lrwxrwxrwx root root 2015-08-30 20:02 CACHE -> /dev/block/sda17
lrwxrwxrwx root root 2015-08-30 20:02 CARRIER -> /dev/block/sda18
lrwxrwxrwx root root 2015-08-30 20:02 DNT -> /dev/block/sda12
lrwxrwxrwx root root 2015-08-30 20:02 EFS -> /dev/block/sda3
lrwxrwxrwx root root 2015-08-30 20:02 OTA -> /dev/block/sda9
lrwxrwxrwx root root 2015-08-30 20:02 PARAM -> /dev/block/sda6
lrwxrwxrwx root root 2015-08-30 20:02 PERSDATA -> /dev/block/sda15
lrwxrwxrwx root root 2015-08-30 20:02 PERSISTENT -> /dev/block/sda13
lrwxrwxrwx root root 2015-08-30 20:02 RADIO -> /dev/block/sda10
lrwxrwxrwx root root 2015-08-30 20:02 RECOVERY -> /dev/block/sda8
lrwxrwxrwx root root 2015-08-30 20:02 STEADY -> /dev/block/sda14
lrwxrwxrwx root root 2015-08-30 20:02 SYSTEM -> /dev/block/sda16
lrwxrwxrwx root root 2015-08-30 20:02 TOMBSTONES -> /dev/block/sda11
lrwxrwxrwx root root 2015-08-30 20:02 USERDATA -> /dev/block/sda19
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs1 -> /dev/block/sda4
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs2 -> /dev/block/sda5
lrwxrwxrwx root root 2015-08-30 20:02 m9kefs3 -> /dev/block/sdd1
Click to expand...
Click to collapse
tx_dbs_tx said:
Thanks for sharing. That's gonna be very helpful. The note 5 tar ball sure is light. No carrier img and lacking several other common files in the tar that we're used to seeing. Makes me wonder why Samsung has streamlined the tar balls for the note 5.
Click to expand...
Click to collapse
Thank you both for all you have done for us on the sprint n5
Thanks,
Chaz187

You're welcome. Having more than one mastermind on this will definitely get things rolling right along. LOL I don't mind helping out. @tdunham has done more than his fair share of helping others here at XDA and I am the same way... I help whenever I can. Enjoy that note 5 @Chaz187

hiii
http://forum.xda-developers.com/note5/help/nvdata-bin-note5-t3194669/post62685509#post62685509

does anyone have the exact pit file and/or the BL,AP,CP, CSC firmware files? I flashed the wrong firmware to it, and it's never been the same even after flashing a single tarball OGD for the N920p, thanks in advance

how can i get n920c running 6.0.1 partition table
i dont have dev/block/sda19 for user data
my last sda is sda17
i want to recover its information s i need to create raw file from my userdata
i need it badly
....
---------- Post added at 09:45 AM ---------- Previous post was at 09:45 AM ----------
how can i get n920c running 6.0.1 partition table
i dont have dev/block/sda19 for user data
my last sda is sda17
i want to recover its information s i need to create raw file from my userdata
i need it badly
....

any chance of a screenshot of that partition list? I need the exact sizes for the 64gb version

newbreedsoftware said:
any chance of a screenshot of that partition list? I need the exact sizes for the 64gb version
Click to expand...
Click to collapse
That is exactly what gets displayed, there's nothing graphical to display. The partition list was generated from a terminal session. I'm not sure how it gets divided size wize and I own the 32gb version.

tdunham said:
That is exactly what gets displayed, there's nothing graphical to display. The partition list was generated from a terminal session. I'm not sure how it gets divided size wize and I own the 32gb version.
Click to expand...
Click to collapse
yeah im looking for the list that shows how many bytes each partition is and where each one stops and starts, like the one attached here that was from my LG v410 that has a messed up partition list i fixed

This is mine. If you want a different view, let me know the list command you prefer to use.
Code:
Filesystem Size Used Free Blksize
/dev 1.8G 140.0K 1.8G 4.0K
/sys/fs/cgroup 1.8G 12.0K 1.8G 4.0K
/mnt 1.8G 0.0K 1.8G 4.0K
/mnt/runtime/default/emulated 24.7G 21.6G 3.0G 4.0K
/mnt/runtime/read/emulated 24.7G 21.6G 3.0G 4.0K
/mnt/runtime/write/emulated 24.7G 21.6G 3.0G 4.0K
/system 4.2G 2.7G 1.5G 4.0K
/efs 15.7M 1.4M 14.3M 4.0K
/cache 290.6M 5.7M 284.9M 4.0K
/data 24.7G 21.6G 3.1G 4.0K
/persdata/absolute 4.9M 292.0K 4.6M 4.0K
/firmware 86.0M 66.9M 19.1M 16.0K
/cpdump 150.0M 0.0K 150.0M 4.0K
/carrier 40.3M 56.0K 40.2M 4.0K
/storage 1.8G 0.0K 1.8G 4.0K
/storage/emulated 24.7G 21.6G 3.0G 4.0K
/su 90.5M 2.4M 88.1M 4.0K

Partition Dump

I'm trying to create a partition dump, specifically to have a backup of my efs partition. My first 6p had it's efs partition corrupted (while stock, unrooted, locked bl). I've got my new 6p in hand, bl unlocked, twrp installed, and chainfires systemless root up and running. I was trying to follow this guide:
http://forum.xda-developers.com/showthread.php?t=2450045
but i cannot access / using any file explorer. The SU prompt never appears. I tried running cat /proc/emmc, and that was a no go as well. I was able to get the partition list, but only in mmcblkxxxx format. I would like the names, so that i can properly organize the dump. If anybody could point me in the right direction, that'd be awesome! Thanks in advance.

Never mind, I've found it. For other's reference, the correct path is:
/dev/block/platform/soc.0/f9824900.sdhci/by-name.
Hope this helps someone in the future

beats4x said:
Never mind, I've found it. For other's reference, the correct path is:
/dev/block/platform/soc.0/f9824900.sdhci/by-name.
Hope this helps someone in the future
Click to expand...
Click to collapse
I don't have a 6p, but I've been looking for someone to post the list by-name. Would you mind sharing?

makers_mark said:
I don't have a 6p, but I've been looking for someone to post the list by-name. Would you mind sharing?
Click to expand...
Click to collapse
Will have to be when I get home from work, but yeah I definitely can
Sent from my Nexus 6P using Tapatalk

makers_mark said:
I don't have a 6p, but I've been looking for someone to post the list by-name. Would you mind sharing?
Click to expand...
Click to collapse
Here you go bro. Sprry for the delay. Been a crazy couple of days at work.
[email protected]:/ # ls -al /dev/block/platform/soc.0/f9824900.sdhci/by-name
lrwxrwxrwx root root 1970-01-26 16:23 DDR -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-26 16:23 aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-26 16:23 abootbak -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-26 16:23 apdp -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-26 16:23 boot -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-26 16:23 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-26 16:23 cmnlib -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-26 16:23 cmnlibbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-26 16:23 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-26 16:23 dpo -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-26 16:23 frp -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-26 16:23 fsc -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-26 16:23 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-26 16:23 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-26 16:23 hypbak -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-26 16:23 keymaster -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-26 16:23 keymasterbak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-26 16:23 keystore -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-26 16:23 limits -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-26 16:23 metadata -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-26 16:23 misc -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-26 16:23 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-26 16:23 modemst1 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-26 16:23 modemst2 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-26 16:23 msadp -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-26 16:23 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-26 16:23 oeminfo -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-26 16:23 persist -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-26 16:23 persistent -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-26 16:23 pmic -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-26 16:23 pmicbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-26 16:23 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-26 16:23 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-26 16:23 rpmbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-26 16:23 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-26 16:23 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-26 16:23 sdi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-26 16:23 sec -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-26 16:23 ssd -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-26 16:23 system -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-26 16:23 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-26 16:23 tzbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-26 16:23 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-26 16:23 vendor -> /dev/block/mmcblk0p37

beats4x said:
...
Click to expand...
Click to collapse
I've been looking since they released the images, I think you may of been the first to post it anywhere that I have access to, thanks!!:good:

makers_mark said:
I've been looking since they released the images, I think you may of been the first to post it anywhere that I have access to, thanks!!:good:
Click to expand...
Click to collapse
No problem, glad I could assist!
Sent from my Nexus 6P using Tapatalk

MCU dump to image file

Hello, I was trying to dump my MCU partition into img file. That way I could try to reflash it back within the update mcu settings on device. My goal was to flash it with the dmcu.ext file that controls the resolution. I read I am supposed to flash MCU with text file dmcu.ext "screen:1" in the root of where the mcu image is. When I flash the entire image it does not seem to work, thought it could be because firmware is in one large bin file that contains all of the images like system and boot. I dumped the tee1 and tee2 to image file, would that be mcu? My resolution is showing 1024x600, instead of 800x480.
no matter what mcu img I attempt to update, MCU update says failed to update file. I was reading about mismatch, but don't see that error.
If I am not on the right track here, please correct me.
FF-5000:/ # ls -al /dev/block/platform/soc/11230000.mmc/by-name
total 0
drwxr-xr-x 2 root root 560 2010-01-01 00:01 .
drwxr-xr-x 4 root root 680 2010-01-01 00:01 ..
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 ANDROID -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 ARM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 BOOTIMG -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 CACHE -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 DKB -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 EXPDB -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 FRP -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 KB -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 LK -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 LOGO -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 METAZONE -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 MISC -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 NVRAM -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 ODMDTBO -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PROTECT_F -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PROTECT_S -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 PRO_INFO -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 SECCFG -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 SEC_RO -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 TEE1 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2010-01-01 00:01 TEE2 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 VENDOR -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 forfanzone -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 tszone -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2010-01-01 00:01 userdata -> /dev/block/mmcblk0p26