OP3 Partitions

Search This thread

DavidXanatos

Senior Member
Mar 22, 2013
302
155
Vienna
I looked on the partition layout of the OP3 and noticed that
1. the free space in the system partition is only about 200 MB (with OOS 3.5.1) so at some point there may be not enough space, is it possible to change the partition layout?
2. sde23 (/bt_firmware) is 1 GB large but uses only a few KiB i.e. its a waist of 1 GB :/
3. The flash seams to be divided into 6 devices and each of those partitioned, the last block device sdf has apparently 1.5 GB of unpartitioned space :/ what a waist!

What are you thoughts on the matter?

Code:
sda	57.940.115.456		55.256,00		
sda1	8.192	ssd	0,01		
sda2	33.554.432	persist	32,00	/persist	
sda3	268.435.456	cache	256,00	/cache	
sda4	1.048.576	misc	1,00		
sda5	524.288	keystore	0,50		
sda6	131.072	devcfg	0,13		/devcfg.mb
sda7	131.072	devcfgbak	0,13		/devcfg.mb
sda8	524.288	frp	0,50		
sda9	10.485.760	oem_dycnvbk	10,00		
sda10	10.485.760	oem_stanvbk	10,00		/static_nvbk.bin
sda11	1.048.576	param	1,00		
sda12	8.290.304	reserve1	7,91		
sda13	16.580.608	reserve2	15,81		
sda14	524.288	config	0,50		
sda15	57.588.297.728	userdata	54.920,48	/data	
			0		
					
sdb	4.194.304		4,00		
sdb1	4.149.248	xbl	3,96		/xbl.elf
			0,04		
					
sdc	4.194.304		4,00		
sdc1	4.149.248	xblbak	3,96		/xbl.elf
			0,04		
					
sdd	134.217.728		128,00		
sdd1	32.768	reserve	0,03		
sdd2	4.096	cdt	0,00		
sdd3	1.048.576	ddr	1,00		
			126,96		
					
sde	4.294.967.296		4.096,00		
sde1	524.288	rpm	0,50		/rpm.mbn
sde2	524.288	rpmbak	0,50		/rpm.mbn
sde3	2.097.152	tz	2,00		/tz.mbn
sde4	2.097.152	tzbak	2,00		/tz.mbn
sde5	524.288	hyp	0,50		/hyp.mbn
sde6	524.288	hypbak	0,50		/hyp.mbn
sde7	2.097.152	fsg	2,00		
sde8	16.384	sec	0,02		
sde9	524.288	pmic	0,50		/pmic.elf
sde10	524.288	pmicbak	0,50		/pmic.elf
sde11	99.614.720	modem	95,00	/firmware	/NON-HLOS.bin
sde12	16.777.216	dsp	16,00	/dsp	/adspso.bin
sde13	1.048.576	dip	1,00		
sde14	33.554.432	mdtp	32,00		
sde15	8.388.608	abootbak	8,00		/emmc_appsboot.mbn
sde16	8.388.608	aboot	8,00		/emmc_appsboot.mbn
sde17	16.777.216	LOGO	16,00		
sde18	67.108.864	boot	64,00		/boot.img
sde19	67.108.864	boot_aging	64,00		
sde20	3.154.116.608	system	3.008,00	/system	
sde21	67.108.864	recovery	64,00		/recovery.img
sde22	4.096	devinfo	0,00		
sde23	1.048.576	bluetooth	1,00	/bt_firmware	/BTFM.bin
sde24	524.288	keymaster	0,50		/keymaster.mbn
sde25	524.288	keymasterbak	0,50		/keymaster.mbn
sde26	262.144	cmnlib	0,25		/cmnlib.mbn
sde27	262.144	cmnlibbak	0,25		/cmnlib.mbn
sde28	262.144	cmnlib64	0,25		/cmnlib64.mbn
sde29	262.144	cmnlib64bak	0,25		/cmnlib64.mbn
sde30	262.144	apdp	0,25		
sde31	262.144	msadp	0,25		
sde32	4.096	dpo	0,00		
sde33	34.226.176	splash	32,64		
sde34	2.097.152	sti	2,00		
			673		
					
sdf	1.610.612.736		1.536,00		
sdf1	2.097.152	modemst1	2,00		
sdf2	2.097.152	modemst2	2,00		
sdf3	4.096	fsc	0,00		
sdf4	524.288	md5	0,50		
			1.531,50		
					
	63.988.301.824
 
Last edited:
  • Like
Reactions: Mostafa Wael

StykerB

Senior Member
Jan 17, 2015
323
124
the nexus 5 has marshmallow on a 1gb /system, I think 3gb in OP3 will be fine especially since there's still empty space in it now.
 

DavidXanatos

Senior Member
Mar 22, 2013
302
155
Vienna
My thoughts are that this is in the wrong section :)

And which one would be the right one?


Also does anyone here know what what all this different small partitions do?
for example what is boot_aging apparently its some sort of boot image but its needier a backup of boot.img nor of the recovery.
I also wonder why xbl is so important to have the backup xblbak located with an own partition table in a separated flash section?
 

Striatum_bdr

Senior Member
May 29, 2011
4,650
2,176
Marseille
Q and A section evidently this has nothing to do with dev

And frankly don't begin to mess with partitions, nothing good can come up from this.
 

Striatum_bdr

Senior Member
May 29, 2011
4,650
2,176
Marseille
Development is programming. Building Rom and kernels.
This isn't dev add you don't propose anything related to a script, a program. You're just asking.
 

DavidXanatos

Senior Member
Mar 22, 2013
302
155
Vienna
You can not program without understanding how the underlying system works. Respectively the better you understand the system the more you can get out of the hardware, for example here: http://xdaforums.com/optimus-4x-hd/development/rom-mahdi-rom-2-7-unofficial-beta-t2867590 this ROM apparently exploits a existing but unused partition of the p880 to add a new encryption feature which was not present in the stock OS.

Given how many partitions and unused space the OP3 has I'm sure someone can come up with a nice feature to exploit them. Possibly for a different approach on multi boot or may be some virtualization 1 Gig of space is more than enough for a hyper-visor.

> You're just asking.
Nope I'm finding out stuff and trying to find out more stuff....

I looked into the binaries and found something worrisome in XBL partitions contained in the 2nd and 3rd block device:
Code:
##This flag enables booting to UEFI Shell on LA devices.
##This UEFI in the current form should not be used for
##retail purpose. Fuse check will be added to avoid any
##possible security implications.

Also I'm wondering what the boot_aging partition does, apparently its some sort of boot image. But its needier a backup of the kernel (boot.img) nor of the recovery, I wonder what it is...
 
  • Like
Reactions: Paradoxxx

DavidXanatos

Senior Member
Mar 22, 2013
302
155
Vienna
So a sub forum called: OnePlus 3 ROMs, Kernels, Recoveries, & Other Development
is not intended to talk about development, that's so odd.
What sub forum than is intended to talk about source and hardware and boot loaders on a nun user level?
 
  • Like
Reactions: Paradoxxx

t-ryder

Senior Member
Feb 23, 2011
1,569
1,256
www.t-ryder.de
Google Pixel 6
@DavidXanatos

No offense, Sir... but I guess OnePlus 3 ROMs, Kernels, Recoveries, & Other Development is more for like releases and stuff made by devs.
Maybe your thread belongs in OnePlus 3 Guides, News, & Discussion where you can discuss hat topic and find out stuff, as there are other threads a bit like yours.
Maybe ask a mod to move your thread? Just a suggestion.
 
  • Like
Reactions: BrandonJP_

JumboMan

Senior Member
Aug 3, 2013
575
227
Pink City
I think debating on whether this thread should be in QA section or Dev section why not keep this decision on moderator.
why not just provide proper answer ( of course, if you know ).
I agree this question is more suited in QA section but i think this question can be asked in Dev section because it's very closely related to development.
 
  • Like
Reactions: t-ryder

Sloth

Inactive RC / Retired Forum Moderator
Apr 23, 2012
10,699
11,300
Xda-Dev,NV
Hello,
I've moved it to Guides, New, Discussion, please discuss away. :)
This where it will reside unless someone comes up with a compelling argument as to why it belongs in "Other Development". I don't really believe it does.
Also please be civil to each other.

Cheers Sloth
 

abhibnl

Senior Member
Oct 13, 2011
3,594
1,464
Delete play music and play movies from system partition. Should free up enough space for our mods.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Well, isn't understanding the partitions not part of development? IMHO one could learn something useful out of that.
    1
    I looked on the partition layout of the OP3 and noticed that
    1. the free space in the system partition is only about 200 MB (with OOS 3.5.1) so at some point there may be not enough space, is it possible to change the partition layout?
    2. sde23 (/bt_firmware) is 1 GB large but uses only a few KiB i.e. its a waist of 1 GB :/
    3. The flash seams to be divided into 6 devices and each of those partitioned, the last block device sdf has apparently 1.5 GB of unpartitioned space :/ what a waist!

    What are you thoughts on the matter?

    Code:
    sda	57.940.115.456		55.256,00		
    sda1	8.192	ssd	0,01		
    sda2	33.554.432	persist	32,00	/persist	
    sda3	268.435.456	cache	256,00	/cache	
    sda4	1.048.576	misc	1,00		
    sda5	524.288	keystore	0,50		
    sda6	131.072	devcfg	0,13		/devcfg.mb
    sda7	131.072	devcfgbak	0,13		/devcfg.mb
    sda8	524.288	frp	0,50		
    sda9	10.485.760	oem_dycnvbk	10,00		
    sda10	10.485.760	oem_stanvbk	10,00		/static_nvbk.bin
    sda11	1.048.576	param	1,00		
    sda12	8.290.304	reserve1	7,91		
    sda13	16.580.608	reserve2	15,81		
    sda14	524.288	config	0,50		
    sda15	57.588.297.728	userdata	54.920,48	/data	
    			0		
    					
    sdb	4.194.304		4,00		
    sdb1	4.149.248	xbl	3,96		/xbl.elf
    			0,04		
    					
    sdc	4.194.304		4,00		
    sdc1	4.149.248	xblbak	3,96		/xbl.elf
    			0,04		
    					
    sdd	134.217.728		128,00		
    sdd1	32.768	reserve	0,03		
    sdd2	4.096	cdt	0,00		
    sdd3	1.048.576	ddr	1,00		
    			126,96		
    					
    sde	4.294.967.296		4.096,00		
    sde1	524.288	rpm	0,50		/rpm.mbn
    sde2	524.288	rpmbak	0,50		/rpm.mbn
    sde3	2.097.152	tz	2,00		/tz.mbn
    sde4	2.097.152	tzbak	2,00		/tz.mbn
    sde5	524.288	hyp	0,50		/hyp.mbn
    sde6	524.288	hypbak	0,50		/hyp.mbn
    sde7	2.097.152	fsg	2,00		
    sde8	16.384	sec	0,02		
    sde9	524.288	pmic	0,50		/pmic.elf
    sde10	524.288	pmicbak	0,50		/pmic.elf
    sde11	99.614.720	modem	95,00	/firmware	/NON-HLOS.bin
    sde12	16.777.216	dsp	16,00	/dsp	/adspso.bin
    sde13	1.048.576	dip	1,00		
    sde14	33.554.432	mdtp	32,00		
    sde15	8.388.608	abootbak	8,00		/emmc_appsboot.mbn
    sde16	8.388.608	aboot	8,00		/emmc_appsboot.mbn
    sde17	16.777.216	LOGO	16,00		
    sde18	67.108.864	boot	64,00		/boot.img
    sde19	67.108.864	boot_aging	64,00		
    sde20	3.154.116.608	system	3.008,00	/system	
    sde21	67.108.864	recovery	64,00		/recovery.img
    sde22	4.096	devinfo	0,00		
    sde23	1.048.576	bluetooth	1,00	/bt_firmware	/BTFM.bin
    sde24	524.288	keymaster	0,50		/keymaster.mbn
    sde25	524.288	keymasterbak	0,50		/keymaster.mbn
    sde26	262.144	cmnlib	0,25		/cmnlib.mbn
    sde27	262.144	cmnlibbak	0,25		/cmnlib.mbn
    sde28	262.144	cmnlib64	0,25		/cmnlib64.mbn
    sde29	262.144	cmnlib64bak	0,25		/cmnlib64.mbn
    sde30	262.144	apdp	0,25		
    sde31	262.144	msadp	0,25		
    sde32	4.096	dpo	0,00		
    sde33	34.226.176	splash	32,64		
    sde34	2.097.152	sti	2,00		
    			673		
    					
    sdf	1.610.612.736		1.536,00		
    sdf1	2.097.152	modemst1	2,00		
    sdf2	2.097.152	modemst2	2,00		
    sdf3	4.096	fsc	0,00		
    sdf4	524.288	md5	0,50		
    			1.531,50		
    					
    	63.988.301.824
    1
    My thoughts are that this is in the wrong section :)

    Best Regards,
    Taker
    1
    You can not program without understanding how the underlying system works. Respectively the better you understand the system the more you can get out of the hardware, for example here: http://xdaforums.com/optimus-4x-hd/development/rom-mahdi-rom-2-7-unofficial-beta-t2867590 this ROM apparently exploits a existing but unused partition of the p880 to add a new encryption feature which was not present in the stock OS.

    Given how many partitions and unused space the OP3 has I'm sure someone can come up with a nice feature to exploit them. Possibly for a different approach on multi boot or may be some virtualization 1 Gig of space is more than enough for a hyper-visor.

    > You're just asking.
    Nope I'm finding out stuff and trying to find out more stuff....

    I looked into the binaries and found something worrisome in XBL partitions contained in the 2nd and 3rd block device:
    Code:
    ##This flag enables booting to UEFI Shell on LA devices.
    ##This UEFI in the current form should not be used for
    ##retail purpose. Fuse check will be added to avoid any
    ##possible security implications.

    Also I'm wondering what the boot_aging partition does, apparently its some sort of boot image. But its needier a backup of the kernel (boot.img) nor of the recovery, I wonder what it is...
    1
    So a sub forum called: OnePlus 3 ROMs, Kernels, Recoveries, & Other Development
    is not intended to talk about development, that's so odd.
    What sub forum than is intended to talk about source and hardware and boot loaders on a nun user level?