Tmobile d959 4.4.2 partition table

Search This thread

allenjthomsen

Senior Member
Nov 17, 2010
2,630
3,347
37
Tacoma, WA
Google Pixel 7 Pro
Nothing Phone 2
This is the partition table for the TMOBILE LG-D959 4.4.2 FLEX ONLY


DDR -> /dev/block/mmcblk0p4
aboot -> /dev/block/mmcblk0p5
blus -> /dev/block/mmcblk0p29
boot -> /dev/block/mmcblk0p7
cache -> /dev/block/mmcblk0p35
carrier -> /dev/block/mmcblk0p27
dbi -> /dev/block/mmcblk0p3
dbibak -> /dev/block/mmcblk0p30
drm -> /dev/block/mmcblk0p21
encrypt -> /dev/block/mmcblk0p20
eri -> /dev/block/mmcblk0p28
fota -> /dev/block/mmcblk0p25
fsc -> /dev/block/mmcblk0p17
fsg -> /dev/block/mmcblk0p16
grow -> /dev/block/mmcblk0p39
laf -> /dev/block/mmcblk0p24
misc -> /dev/block/mmcblk0p13
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p10
modemst2 -> /dev/block/mmcblk0p11
mpt -> /dev/block/mmcblk0p26
pad -> /dev/block/mmcblk0p9
pad1 -> /dev/block/mmcblk0p12
pad2 -> /dev/block/mmcblk0p19
persist -> /dev/block/mmcblk0p14
rct -> /dev/block/mmcblk0p33
recovery -> /dev/block/mmcblk0p15
rpm -> /dev/block/mmcblk0p6
rpmbak -> /dev/block/mmcblk0p31
sbl1 -> /dev/block/mmcblk0p2
sns -> /dev/block/mmcblk0p22
spare -> /dev/block/mmcblk0p37
ssd -> /dev/block/mmcblk0p18
system -> /dev/block/mmcblk0p34
tombstones -> /dev/block/mmcblk0p36
tz -> /dev/block/mmcblk0p8
tzbak -> /dev/block/mmcblk0p32
userdata -> /dev/block/mmcblk0p38
ve -> /dev/block/mmcblk0p23
 
Last edited:

allenjthomsen

Senior Member
Nov 17, 2010
2,630
3,347
37
Tacoma, WA
Google Pixel 7 Pro
Nothing Phone 2
Why go that route when its right in /system

And it will help people know the correct partition for their zips

And side note sorry for taking so long on the kernel been busy working nonstop
 

Attachments

  • 1407121343531.jpg
    1407121343531.jpg
    53.4 KB · Views: 235

PlayfulGod

Inactive Recognized Developer
Sep 28, 2010
1,886
3,059
Dalton
Why go that route when its right in /system

And it will help people know the correct partition for their zips

And side note sorry for taking so long on the kernel been busy working nonstop

because we all use /dev/block/platform/msm_sdcc.1/by-name/boot, recovery etc nowa days. Look at the fstabs for most devices done in the last year. ;)

Which also works in the updater-script. ;)


New way of doing things, need to keep up. lol ;)
Makes it easy to remember too. ;)
 
Last edited:

PlayfulGod

Inactive Recognized Developer
Sep 28, 2010
1,886
3,059
Dalton
I was going to build a kernel that would allow us to flash a recovery but i havent had a chance yet

and just what is a kernel going to do about a locked bootloader??

Like I have said numerous times, the jb aboot and currently recovery works fine. Need to find the rebooting issue with the kk kernel when using them. ;)
 

allenjthomsen

Senior Member
Nov 17, 2010
2,630
3,347
37
Tacoma, WA
Google Pixel 7 Pro
Nothing Phone 2
Let me say this again since no one seems to f**king read. Recovery works fine with all models. The issue is on 4.4 and getting the kk kernel to stay booted with the stock kernel and maybe possibly on cm when device has service.

Just so u know i have held off building anything kernel related because of this i am willing to help anyway i can.
ive dug around in the kernel and talked with some other devs .
I would really like to get our heads together PG and get a custom recovery going for 4.4.2 without reboot issues
 
Last edited:

PlayfulGod

Inactive Recognized Developer
Sep 28, 2010
1,886
3,059
Dalton
Just so u know i have held off building anything kernel related because of this i am willing to help anyway i can.
ive dug around in the kernel and talked with some other devs .
I would really like to get our heads together PG and get a custom recovery going for 4.4.2 without reboot issues

And yes i understood that its the kernel causing issues

you arent alone lol.

I get msg's daily asking when FreedomFlex will support kitkat.

savoca seemed to think something was missing from the kernel src back when he first did the edits need to get the 4.4 kernel to boot with our aboot. And since he doesnt have a Flex, its up to us to find out what is causing the reboot isssus. I will try to work on it this week some time. ;)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    why not just use

    Code:
    ls -l /dev/block/platform/msm_sdcc.1/by-name
    ???? ;)
    1
    I was going to build a kernel that would allow us to flash a recovery but i havent had a chance yet