Related
here are the partitions you can and can't flash unsigned:
Can:
Code:
boot
recovery
userdata
system
modem
fsg
modemst1
modemst2
logo
devtree
cdrom
tombstones
cache
Can't:
Code:
aboot
tz
rpm
sbl1
sbl2
sbl3
partition (You can't re-partition it either)
Untested:
Code:
cid
dhob
hob
kpan
mbl
misc
padA
padB
pds
persist
utags
sp
ssd
utags
Why didn't you just put this in your noob guide?
Sent from my JokerMATRIX HD MAXX
deeje00 said:
Why didn't you just put this in your noob guide?
Sent from my JokerMATRIX HD MAXX
Click to expand...
Click to collapse
Was in the dev section for developers.
But I'll link to it
After trying to install twrp, my phone bricked.
I managed to unbrick it and flash stock 5.0.2 .kdz ! Through the procedure of unbricking, I performed a low level format which erased everything including my /efs partition and everything included in it.
Therefore my IMEI is currently 0 and my IMEI SV is 00.
I have tried to install my IMEI through QPST but it will not connect to my phone as it will not recognize it (No ESN, No Phone Connected).
I have tried to connect to my phone through CDMA and EFS Professional but still the same.
During my search on the forums, I found that Ishould enter DIAG mode in my phone, but I cannot find an option for this.
LG said I am not covered by warranty as the /EFS partition is not something that could be wiped without root or a modification to the system.
The main problem is that I do not have a backup. Please help me,
Thanks in advance!
If you had a backup made by TWRP then you could restore your EFS partition. Unfortunately I don't know any other way to fix it.
Xemidra said:
If you had a backup made by TWRP then you could restore your EFS partition. Unfortunately I don't know any other way to fix it.
Click to expand...
Click to collapse
That's the thing, my whole trouble begun when I tried to install TWRP!
I'm not sure how could you destroy EFS partition with installing TWRP. You should have stick to instructions.
Xemidra said:
I'm not sure how could you destroy EFS partition with installing TWRP. You should have stick to instructions.
Click to expand...
Click to collapse
TWRP didn't kill my partition, unbricking the device did! Plus If you can't offer a solution or any kind of help, don't answer at all! I am not here for judgement!
baldy21 said:
TWRP didn't kill my partition, unbricking the device did! Plus If you can't offer a solution or any kind of help, don't answer at all! I am not here for judgement!
Click to expand...
Click to collapse
I'm not judging xD
I'm trying to understand how did you exactly destroy your EFS partition. You didn't provide enough information about it, except saying that you did some kind of low-level-format (you didn't mention how or why). What surprised me was that installing TWRP doesn't require to perform any low-level-format. That why I wrote about sticking with instructions. Then you wrote that you messed up your phone while trying to install TWRP and got you IMEI lost during unbricking. You didn't wrote what exactly meant bricking and what "procedure" did you performed to fix your phone.
My point is that you should have written exactly what happened, not only how you got there and what did you tried to do to fix it. In my opinion it's hard to propose any solution when we don't know what exactly did you do.
Try to flash a stock KDZ suitable for your L90 variant.
neverdies said:
Try to flash a stock KDZ suitable for your L90 variant.
Click to expand...
Click to collapse
tried, no success!
I couldn't find any EFS partition in L90, I believe it's stored elsewhere:
Code:
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8389kB 75.5MB 67.1MB fat16 modem
2 75.5MB 76.5MB 1049kB sbl1
3 76.5MB 77.1MB 524kB rpm
4 77.1MB 77.6MB 524kB tz
5 77.6MB 78.1MB 524kB sdi
6 78.1MB 80.2MB 2097kB aboot
7 80.2MB 80.7MB 524kB rpmb
8 80.7MB 81.3MB 524kB tzb
9 81.3MB 83.4MB 2097kB abootb
10 83.4MB 85.5MB 2097kB pad
11 85.5MB 88.6MB 3146kB modemst1
12 88.6MB 91.8MB 3146kB modemst2
13 91.8MB 109MB 16.8MB misc
14 109MB 143MB 33.6MB ext4 persist
15 143MB 166MB 23.1MB laf
16 168MB 191MB 23.1MB boot
17 191MB 214MB 23.1MB recovery
18 214MB 217MB 3146kB fsg
19 218MB 219MB 524kB fsc
20 219MB 219MB 524kB ssd
21 226MB 227MB 524kB DDR
22 235MB 235MB 524kB encrypt
23 235MB 236MB 524kB rct
24 243MB 252MB 8389kB ext4 drm
25 252MB 260MB 8389kB ext4 sns
26 260MB 281MB 21.0MB factory
27 281MB 315MB 33.6MB fota
28 319MB 320MB 1049kB sbl1b
29 320MB 353MB 33.6MB ext4 mpt
30 361MB 466MB 105MB ext4 cust
31 470MB 470MB 524kB eksst
32 478MB 2626MB 2147MB ext4 system
33 2626MB 3569MB 944MB ext4 cache
34 3569MB 7795MB 4225MB ext4 userdata
35 7801MB 7818MB 16.8MB grow
Also, unbricking your phone with other variant image will destroy your radio info and I don't know if there is a way to recover it in L90. Even if you use your variant image, but from other phone, it will probably overwrite your unique info, that's why it's wise to make a backup of your phone after rooting with dd if=/dev/block/mmcblk0 of=/storage/external_SD/unbrick.img bs=1024 count=168960 - this will be YOUR phone backup, don't share with anyone and store it in a safe place.
Back in time when I had the Optimus 2x, it was possible using Tutty (debug mode ON) and accessing LG debug (in our L90 it's 3845#*VARIANT# e.g. 3845#*410#), of course you must use the IMEI printed in the sticker in the back cover (this is not possible anymore FYI).
Actually, there is not EFS partition in L90 indeed, instead, the IMEI and other radio info are stored in modemst1 and modemst1 partitions. As I suspected before, unbrick images takes some NAND blocks and writes to an image file - it takes the partition 1 to 15, which includes modemst1 and modemst2 partitions (11 and 12). These partitions are also not flasheable via KDZ (these partitions are absent), so before doing any modification after rooting your phone, do yourself a favor and backup modemst1 and modemst2 partitions, because if anything goes wrong, unless someone find a way to inject the right IMEI data in modemst1 and modemst1 image files for further flashing, you will end with a "radio brick".
Found a tutorial here at xda how to backup and restore modemst partitions : http://forum.xda-developers.com/lg-g3/development/efs-lg-g3-efs-backup-restore-t2907329
I had the same problem.. I unbricked my phone by low-level format tool .but now I don't have mobile network signal.but I have an twrp recovery .did they help me..
Sent from my LG-D410 using XDA Forums
Hopefully someone here could possibly pull their partition file from their L90 D415 and upload it here, it seems I need it for a possible way to unbrick my d415. The way I found seems to work for all other variants, though from what i've read others with the d415 model have no success, and it is probably due to a different partition table. So please, if one could, post a link or something for the partition text file. I really need it a long with others I assure you. It would be greatly appreciated. Thank you, and have a nice day.
You can find lots of info about partition table here:
http://forum.xda-developers.com/lg-...ck-partition-table-tool-lg-l90really-t2946323
Probably it includes info for D415 as well. Hope it helps.
mattandhimself said:
Hopefully someone here could possibly pull their partition file from their L90 D415 and upload it here, it seems I need it for a possible way to unbrick my d415. The way I found seems to work for all other variants, though from what i've read others with the d415 model have no success, and it is probably due to a different partition table. So please, if one could, post a link or something for the partition text file. I really need it a long with others I assure you. It would be greatly appreciated. Thank you, and have a nice day.
Click to expand...
Click to collapse
If you can get it to boot to recovery, there's a partition tool (executes from recovery) that will fix it up for you. U might be able to get the table from the app itself. Otherwise I have d415 and will get u what u want from mine. Lmk if u still need the help with that
This is from my stock D410HN. Please note the unit.
Code:
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit s
unit s
(parted) print
print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 15269888s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16384s 147455s 131072s fat16 modem
2 147456s 149503s 2048s sbl1
3 149504s 150527s 1024s rpm
4 150528s 151551s 1024s tz
5 151552s 152575s 1024s sdi
6 152576s 156671s 4096s aboot
7 156672s 157695s 1024s rpmb
8 157696s 158719s 1024s tzb
9 158720s 162815s 4096s abootb
10 162816s 166911s 4096s pad
11 166912s 173055s 6144s modemst1
12 173056s 179199s 6144s modemst2
13 179200s 211967s 32768s misc
14 212992s 278527s 65536s ext4 persist
15 278528s 323583s 45056s laf
16 327680s 372735s 45056s boot
17 372736s 417791s 45056s recovery
18 417792s 423935s 6144s fsg
19 425984s 427007s 1024s fsc
20 427008s 428031s 1024s ssd
21 442368s 443391s 1024s DDR
22 458752s 459775s 1024s encrypt
23 459776s 460799s 1024s rct
24 475136s 491519s 16384s ext4 drm
25 491520s 507903s 16384s ext4 sns
26 507904s 548863s 40960s factory
27 548864s 614399s 65536s fota
28 622592s 624639s 2048s sbl1b
29 624640s 690175s 65536s ext4 mpt
30 704512s 909311s 204800s ext4 cust
31 917504s 918527s 1024s eksst
32 933888s 5128191s 4194304s ext4 system
33 5128192s 6971391s 1843200s ext4 cache
34 6971392s 15223807s 8252416s ext4 userdata
35 15237120s 15269854s 32735s grow
If you mean the partition table, it can be retrieved from the stock KDZ using LGFirmwareExtract. Download your KDZ and extract it, extract DZ, extract PrimaryGPT_0.BIN.
mattandhimself said:
Hopefully someone here could possibly pull their partition file from their L90 D415 and upload it here, it seems I need it for a possible way to unbrick my d415. The way I found seems to work for all other variants, though from what i've read others with the d415 model have no success, and it is probably due to a different partition table. So please, if one could, post a link or something for the partition text file. I really need it a long with others I assure you. It would be greatly appreciated. Thank you, and have a nice day.
Click to expand...
Click to collapse
so does this mean that if we found what do we need we weill be able to ubrick our harbricked lg l90 d415
i have my bricked for 2 yeras
lgl90 said:
so does this mean that if we found what do we need we weill be able to ubrick our harbricked lg l90 d415
i have my bricked for 2 yeras
Click to expand...
Click to collapse
Yes, i will post the method now, but it uses another method.
F. Gacrux said:
This is from my stock D410HN. Please note the unit.
Code:
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit s
unit s
(parted) print
print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 15269888s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16384s 147455s 131072s fat16 modem
2 147456s 149503s 2048s sbl1
3 149504s 150527s 1024s rpm
4 150528s 151551s 1024s tz
5 151552s 152575s 1024s sdi
6 152576s 156671s 4096s aboot
7 156672s 157695s 1024s rpmb
8 157696s 158719s 1024s tzb
9 158720s 162815s 4096s abootb
10 162816s 166911s 4096s pad
11 166912s 173055s 6144s modemst1
12 173056s 179199s 6144s modemst2
13 179200s 211967s 32768s misc
14 212992s 278527s 65536s ext4 persist
15 278528s 323583s 45056s laf
16 327680s 372735s 45056s boot
17 372736s 417791s 45056s recovery
18 417792s 423935s 6144s fsg
19 425984s 427007s 1024s fsc
20 427008s 428031s 1024s ssd
21 442368s 443391s 1024s DDR
22 458752s 459775s 1024s encrypt
23 459776s 460799s 1024s rct
24 475136s 491519s 16384s ext4 drm
25 491520s 507903s 16384s ext4 sns
26 507904s 548863s 40960s factory
27 548864s 614399s 65536s fota
28 622592s 624639s 2048s sbl1b
29 624640s 690175s 65536s ext4 mpt
30 704512s 909311s 204800s ext4 cust
31 917504s 918527s 1024s eksst
32 933888s 5128191s 4194304s ext4 system
33 5128192s 6971391s 1843200s ext4 cache
34 6971392s 15223807s 8252416s ext4 userdata
35 15237120s 15269854s 32735s grow
If you mean the partition table, it can be retrieved from the stock KDZ using LGFirmwareExtract. Download your KDZ and extract it, extract DZ, extract PrimaryGPT_0.BIN.
Click to expand...
Click to collapse
Thank you, i will post the method to unbrick the d415, now that you gave the way to get it unbricked. sadly i got rid of it, but now others can be fixed.
mattandhimself said:
Yes, i will post the method now, but it uses another method.
Click to expand...
Click to collapse
OMMMGG HOW CAN I THANK YOU CAN I DONATE TO YOU PLEEAS
OOOMMGG SORRY IM ANNOYING BUT IM SOO HAPPY
ohh yeah and will this unbrick the qhusb 9008
if yes omg i will donate 50 dollars
lgl90 said:
OMMMGG HOW CAN I THANK YOU CAN I DONATE TO YOU PLEEAS
OOOMMGG SORRY IM ANNOYING BUT IM SOO HAPPY
ohh yeah and will this unbrick the qhusb 9008
if yes omg i will donate 50 dollars
Click to expand...
Click to collapse
im sorry. but I'm having issues at the moment, but I will try to fix it. But there is a method for the lg l90 already, but its for all the models BUT the d415. like i said, im making the fix right now
mattandhimself said:
im sorry. but I'm having issues at the moment, but I will try to fix it. But there is a method for the lg l90 already, but its for all the models BUT the d415. like i said, im making the fix right now
Click to expand...
Click to collapse
No luck?? Or did you just say f*** it?
I post this thread to help you see the block partition lists bellow for your needs
For Galaxy S5 Exynos SM-G900H only
dev/block/mmcblk0p1 : BOTA0
dev/block/mmcblk0p2 : BOTA1
dev/block/mmcblk0p3 : EFS
dev/block/mmcblk0p4: m9kefs1
dev/block/mmcblk0p5: m9kefs2
dev/block/mmcblk0p6: m9kefs3
dev/block/mmcblk0p7: CARRIER
dev/block/mmcblk0p8: PARAM
dev/block/mmcblk0p9: BOOT
dev/block/mmcblk0p10: RECOVERY
dev/block/mmcblk0p11: OTA
dev/block/mmcblk0p12: CDMA-RADIO (cdma_modem)
dev/block/mmcblk0p13: RADIO (modem)
dev/block/mmcblk0p14: TOMBSTONES
dev/block/mmcblk0p15: TDATA
dev/block/mmcblk0p16: PERSDATA
dev/block/mmcblk0p17: RESERVED2
dev/block/mmcblk0p18: SYSTEM
dev/block/mmcblk0p19: CACHE
dev/block/mmcblk0p20: HIDDEN (preload)
dev/block/mmcblk0p21: USERDATA
dev/block/mmcblk0p70: PIT
dev/block/mmcblk0p71: MD5HDR
dev/block/mmcblk0p80: BOOTLOADER (sboot)
Thanks to:
@samersh72 : PIT file
@lyriquidperfection : PIT magic tool
I don't accept any question or responsibility about this post. Use this at your risk!
Any request? Ask in this thread
<bump>
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
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.
My thoughts are that this is in the wrong section
Best Regards,
Taker
Taker18 said:
My thoughts are that this is in the wrong section
Click to expand...
Click to collapse
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?
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.
Well, isn't understanding the partitions not part of development? IMHO one could learn something useful out of that.
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.
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://forum.xda-developers.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...
I'm not discussing that. It belongs to Q&A until a practical thing comes up, then it can be in dev section.
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?
@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.
Striatum_bdr said:
I'm not discussing that. It belongs to Q&A until a practical thing comes up, then it can be in dev section.
Click to expand...
Click to collapse
This thread does not belong in Q&A either. General maybe, but development could be right if it's about adding more space to /system.
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.
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
I think a practical case has come up with OOS 9.0.3 with no space left in partition. Adblock and Ifont are not able to write files. Please suggest
-Amateur Dev
Delete play music and play movies from system partition. Should free up enough space for our mods.