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
imei, baseband is lost after resolder in service center
backup no have
pls give modemst1 (mmcblk0p12) modemst2 (mmcblk0p13) fsg (mmcblk0p16) mi3 wcdma 64gb
thanks
http://en.miui.com/download-101.html
When I was using Moto e2. I messed up with IMEI. And I downloaded the whole factory firmware and flashed it via fastboot using PC. But I lost my precious data.
This post is made for Noobs.
Now I am using Sanders XT1804 and would like to share a short and quick method to backup and understanding IMEI partitions. I am listing here the partition layout of XT1804 Indian variant with block no. And will tell you how to backup and restore the partitions easily by using DD command in terminal emulator app. Pls. read it carefully.
sbl1 mmcblk0p1
rpm mmcblk0p2
tz mmcblk0p3
devcfg mmcblk0p4
aboot mmcblk0p5
cmnlib mmcblk0p6
cmnlib64 mmcblk0p7
keymaster mmcblk0p8
prov mmcblk0p9
sbl1bak mmcblk0p10
rpmbak mmcblk0p11
tzbak mmcblk0p12
devcfgbak mmcblk0p13
abootbak mmcblk0p14
cmnlibbak mmcblk0p15
cmnlib64bak mmcblk0p16
keymasterbak mmcblk0p17
provbak mmcblk0p18
modem mmcblk0p19
fsc mmcblk0p10
ssd mmcblk0p21
dsp mmcblk0p22
DDR mmcblk0p23
sec mmcblk0p24
utags mmcblk0p25
utagsBackup mmcblk0p26
modemst1 mmcblk0p27
modemst2 mmcblk0p28
fsg mmcblk0p29
persist mmcblk0p30
frp mmcblk0p31
cid mmcblk0p32
logo mmcblk0p33
carrier mmcblk0p34
metadata mmcblk0p35
kpan mmcblk0p36
boot mmcblk0p37
recovery mmcblk0p38
misc mmcblk0p39
limits mmcblk0p40
mota mmcblk0p41
dip mmcblk0p42
syscfg mmcblk0p43
logs mmcblk0p44
apdp mmcblk0p45
msadp mmcblk0p46
dpo mmcblk0p47
padA mmcblk0p48
sp mmcblk0p49
hw mmcblk0p50
oem mmcblk0p51
cache mmcblk0p52
system mmcblk0p53
data mmcblk0p54
Requirements:-
1) Stock ROM or any custom ROM
2). ROOT
3) any Terminal Command app from Playstore.
For IMEI u must backup modem, modemst1 and modemst2.
Block no. are mmcblk0p19, mmcblk0p27, mmcblk0p28.
To backup modem partition:-
Open terminal emulator app first type "su" and then
dd if=/dev/block/mmcblk0p19 of=/sdcard/modem.img
To restore modem partition:-
dd if=/sdcard/modem.img of=/dev/block/mmcblk0p19
In the same way,
To backup modemst1 and modemst2 type:-
dd if=/dev/block/mmcblk0p27 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p28 of=/sdcard/modemst2.img
To restore modemst1 and modemst2:-
dd if=/sdcard/modemst1.img of=/dev/block/mmcblk0p27
dd if =/sdcard/modemst2.img of=/dev/block/mmcblk0p28
Make sure that in above commands I give the backup path to "sdcard" which is the internal storage of android device
Click to expand...
Click to collapse
You must copy that .IMG file to other storage or external device.
The partition block no. may vary with different variants of Sanders(G5S PLUS) above one is for XT1804 only.
Modemst1 is for SIM1 and modemst2 for SIM2 IMEI.
In the same way u can backup all the necessary partitions. Just replace the filename with "xxx.img" .IMG is necessary to make the image with IMG. format. I would recommend u do all the necessary partitions backup in your sdcard and than move this images to ur pc or pen drive.
Such as persist, carrier, modem, modemst1, modemst2 etc.
Once u do the backup and u bricked ur device in future. Don't worry, you can restore it anytime if u want.
Just install ADB in ur pc. Go to fastboot mode in ur mobile. Place the file in ADB folder on windows.
Type this command to restore/flash partitions.
For modem partition
Code:
fastboot flash modem modem.img
while doing backup/restore in terminal app using dd command. Keep the filename same as listed in partition layout according to block no.
Click to expand...
Click to collapse
Do enjoy and keep flashing custom roms. Cheers
I have XT1900-2 with unlocked bootloader and Havoc-OS 13022019 build installed. No root. Never flashed 'copy-partition.zip".
Initially when I flashed it, everything was alright, I can boot twrp (never flashed it) and switch the slot.
Now I want to flash newer build. 'fastboot devices' runs fine with the serial number output.
But I can't boot twrp,
Code:
$ fastboot boot twrp.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.001s
fastboot log,
Code:
cmd: getvar:slot-count
cmd:
I can't switch the slot,
Code:
sudo fastboot --set-active='b'
(bootloader) slot-suffi: not found
error: Device does not support slots.
Bootloader shows "Baseband: <not found>".
But the baseband shows up on Settings; the OS runs fine, I have data, call and wifi.
Edit: partition list
Code:
$ ls /dev/block/platform/soc/c0c4000.sdhci/by-name
abl_a bluetooth_b cid cmnlib_b devinfo dto_a fsg_a hyp_b logfs misc modemst2 persist prov_b ssd system_b utags vendor_a
abl_b boot_a cmnlib64_a ddr dpo dto_b fsg_b keymaster_a logo_a modem_a msadp pmic_a rpm_a storsec_a tz_a utagsBackup vendor_b
apdp boot_b cmnlib64_b devcfg_a dsp_a frp hw keymaster_b logo_b modem_b oem_a pmic_b rpm_b storsec_b tz_b vbmeta_a xbl_a
bluetooth_a carrier cmnlib_a devcfg_b dsp_b fsc hyp_a kpan metadata modemst1 oem_b prov_a sp system_a userdata vbmeta_b xbl_b
I can't even restore to stock (using this guide) since all the fastboot commands fail. blankflash is not applicable since fastboot still can recognize the phone.
I ran all the commands (each command is repeated at least five times), remarkably none of the command is executed and everything is still intact.
Edit: Managed to restore to stock using Windows (I'm using Linux), except for oem which failed to flash due to exceeding partition size. The baseband is still "<not found>".
As stated in other threads, I have yet to break my phone to test this.
I still think starting from the blankflash and then flashing stock from the motorola program would be your best bet to restoring your phone.
Thanks. blankflash didn't work for me because I didn't specify the port number (default is 9008, judging from other threads). I managed to restock using Windows 7 and the latest fastboot (r28.0.1). It didn't work for the first reboot, so I flashed the Copy Partition . The baseband somehow came back on bootloader after a few reboots.
Anyhow, I think the issue could be due to corrupted /system. Yalp Store's ota.zip currently doesn't support /system/system, so I modified the script. I also wrote a script to install microG (without using NanoDroid). I probably messed up the scripts...
There was a script once made for my current device that didn't work.
Doing everything manually, step-by-step, worked though so that's the route I go when I can.
I just got a brand new phone straight out of the box and am having the same issue. Did you ever figure it out?
Edit: I got it to work using an older computer with USB 2.0... which is strange because I tried the 2.0 ports on my desktop also...