Code:
adsp -> /dev/block/mmcblk0p16
board_info -> /dev/block/mmcblk0p3
boot -> /dev/block/mmcblk0p42
cache -> /dev/block/mmcblk0p46
carrier -> /dev/block/mmcblk0p37
cdma_record -> /dev/block/mmcblk0p33
cir_img -> /dev/block/mmcblk0p40
control -> /dev/block/mmcblk0p30
custdata -> /dev/block/mmcblk0p22
ddr -> /dev/block/mmcblk0p14
debug_config -> /dev/block/mmcblk0p28
devlog -> /dev/block/mmcblk0p39
dsps -> /dev/block/mmcblk0p15
extra -> /dev/block/mmcblk0p32
fataldevlog -> /dev/block/mmcblk0p27
fsc -> /dev/block/mmcblk0p34
fsg -> /dev/block/mmcblk0p19
hboot -> /dev/block/mmcblk0p11
local -> /dev/block/mmcblk0p31
mfg -> /dev/block/mmcblk0p5
misc -> /dev/block/mmcblk0p24
modem_st1 -> /dev/block/mmcblk0p25
modem_st2 -> /dev/block/mmcblk0p26
pdata -> /dev/block/mmcblk0p29
pg1fs -> /dev/block/mmcblk0p2
pg2fs -> /dev/block/mmcblk0p6
radio -> /dev/block/mmcblk0p20
radio_config -> /dev/block/mmcblk0p18
recovery -> /dev/block/mmcblk0p43
reserve -> /dev/block/mmcblk0p41
reserve_1 -> /dev/block/mmcblk0p4
reserve_2 -> /dev/block/mmcblk0p23
reserve_3 -> /dev/block/mmcblk0p44
rpm -> /dev/block/mmcblk0p8
sbl1 -> /dev/block/mmcblk0p1
sbl1_update -> /dev/block/mmcblk0p7
sdi -> /dev/block/mmcblk0p10
sensor_hub -> /dev/block/mmcblk0p38
skylink -> /dev/block/mmcblk0p36
sp1 -> /dev/block/mmcblk0p12
ssd -> /dev/block/mmcblk0p35
system -> /dev/block/mmcblk0p45
tool_diag -> /dev/block/mmcblk0p21
tz -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p47
wcnss -> /dev/block/mmcblk0p17
wifi -> /dev/block/mmcblk0p13
Sent from my HTC One_M8 using Tapatalk
What exactly is this?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
partition list:
Code:
B2B -> /dev/block/mmcblk0p25
DDR -> /dev/block/mmcblk0p17
FOTAKernel -> /dev/block/mmcblk0p16
LTALabel -> /dev/block/mmcblk0p18
TA -> /dev/block/mmcblk0p1
aboot -> /dev/block/mmcblk0p5
alt -> /dev/block/mmcblk0p8
apps -> /dev/block/mmcblk0p22
boot -> /dev/block/mmcblk0p14
cache -> /dev/block/mmcblk0p24
dbi -> /dev/block/mmcblk0p4
fsg -> /dev/block/mmcblk0p21
modemst1 -> /dev/block/mmcblk0p19
modemst2 -> /dev/block/mmcblk0p20
ramdump -> /dev/block/mmcblk0p15
rpm -> /dev/block/mmcblk0p6
s1sbl -> /dev/block/mmcblk0p3
sbl1 -> /dev/block/mmcblk0p2
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p7
userdata -> /dev/block/mmcblk0p26
Original kernel: https://drive.google.com/file/d/0B8rpJsF4EG0YLXV4bi1FRC04V0k
System dump: https://drive.google.com/file/d/0B8rpJsF4EG0YTFItSXRkTVZVM1E
Hi,
is it possible to dump the original ROM which is installed on GearBest Phones before putting TWRP and MIUI 8 via EDL on the Mi Max? I think if the phone is faulty you have a chance to remain warranty if you can flash the GB ROM back.
Thanks
I don't think there is any easy way to dump the content of all partitions. Fastboot does not provide the way, maybe some other tool?
You can use dd command like this on rooted device:
Code:
su
dd if=/dev/block/platform/soc.0/7824900.sdhci/by-name/system of=/sdcard/system.img
All Mi Max partitions:
Code:
# ls -l /dev/block/platform/soc.0/7824900.sdhci/by-name
DDR -> /dev/block/mmcblk0p17
aboot -> /dev/block/mmcblk0p38
abootbak -> /dev/block/mmcblk0p39
apdp -> /dev/block/mmcblk0p13
bk1 -> /dev/block/mmcblk0p1
bk2 -> /dev/block/mmcblk0p9
bk3 -> /dev/block/mmcblk0p10
bk4 -> /dev/block/mmcblk0p12
bk5 -> /dev/block/mmcblk0p51
bk6 -> /dev/block/mmcblk0p52
bk7 -> /dev/block/mmcblk0p53
bluetooth -> /dev/block/mmcblk0p50
boot -> /dev/block/mmcblk0p60
cache -> /dev/block/mmcblk0p62
cmnlib -> /dev/block/mmcblk0p30
cmnlib64 -> /dev/block/mmcblk0p32
cmnlib64bak -> /dev/block/mmcblk0p33
cmnlibbak -> /dev/block/mmcblk0p31
config -> /dev/block/mmcblk0p6
cust -> /dev/block/mmcblk0p63
devcfg -> /dev/block/mmcblk0p20
devcfgbak -> /dev/block/mmcblk0p21
devinfo -> /dev/block/mmcblk0p45
dip -> /dev/block/mmcblk0p46
dpo -> /dev/block/mmcblk0p3
dsp -> /dev/block/mmcblk0p58
frp -> /dev/block/mmcblk0p19
fsc -> /dev/block/mmcblk0p2
fsg -> /dev/block/mmcblk0p40
hyp -> /dev/block/mmcblk0p28
hypbak -> /dev/block/mmcblk0p29
keymaster -> /dev/block/mmcblk0p34
keymasterbak -> /dev/block/mmcblk0p35
keystore -> /dev/block/mmcblk0p18
limits -> /dev/block/mmcblk0p7
logo -> /dev/block/mmcblk0p48
mcfg -> /dev/block/mmcblk0p44
mdtp -> /dev/block/mmcblk0p56
misc -> /dev/block/mmcblk0p43
modem -> /dev/block/mmcblk0p49
modemst1 -> /dev/block/mmcblk0p41
modemst2 -> /dev/block/mmcblk0p42
mota -> /dev/block/mmcblk0p15
msadp -> /dev/block/mmcblk0p14
oem -> /dev/block/mmcblk0p59
oops -> /dev/block/mmcblk0p54
persist -> /dev/block/mmcblk0p57
pmic -> /dev/block/mmcblk0p22
pmicbak -> /dev/block/mmcblk0p23
recovery -> /dev/block/mmcblk0p61
rpm -> /dev/block/mmcblk0p26
rpmbak -> /dev/block/mmcblk0p27
sbl1 -> /dev/block/mmcblk0p24
sbl1bak -> /dev/block/mmcblk0p25
sdi -> /dev/block/mmcblk0p11
sec -> /dev/block/mmcblk0p4
splash -> /dev/block/mmcblk0p55
ssd -> /dev/block/mmcblk0p5
sti -> /dev/block/mmcblk0p47
switch -> /dev/block/mmcblk0p8
syscfg -> /dev/block/mmcblk0p16
system -> /dev/block/mmcblk0p64
tz -> /dev/block/mmcblk0p36
tzbak -> /dev/block/mmcblk0p37
userdata -> /dev/block/mmcblk0p65
Nice
Are the Block ids for/from Hydrogen or Helium?
But how to root a Stock device? I Mean i could Flash twrp on a locked device via edl and maybe put supersu via twrp on it but then i don't have the stock recovery because I overwrited it with TWRP.
Dacoco said:
Nice
Are the Block ids for/from Hydrogen or Helium?
But how to root a Stock device? I Mean i could Flash twrp on a locked device via edl and maybe put supersu via twrp on it but then i don't have the stock recovery because I overwrited it with TWRP.
Click to expand...
Click to collapse
Both hydrogen and helium have same block ids but if you use .../by-name/... it doesn't matter...
China dev MIUI has root but you want to backup the original state so that is not a option...
The only option is to flash TWRP, mount all partitions posible and do dd command from TWRP to preserve /system original no root state and forget about stock recovery which btw is just a picture and nothing else...
There is even a TWRP mod that enables all those partitions in mount screen...
Why do dd commands if he can just do full nandroid backup of all partitions, if he flashes twrp? That way he can restore it if needed and eventually flash stock recovery and be done Whit it!
Aren't the partitions encrypted? I'm not sure but I think a backup with TWRP didn't work because of encrypted partitions. At least data.
Stock recovery is a picture - I know - but it's about to send the phone in case of a warranty back and therefore it should be 100% stock. But I think this won't work...
[email protected] said:
Why do dd commands if he can just do full nandroid backup of all partitions, if he flashes twrp? That way he can restore it if needed and eventually flash stock recovery and be done Whit it!
Click to expand...
Click to collapse
If you can backup all partitions you need with TWRP then yeah...
But I don't think you can...
I have a problem with my Mi A2 Lite.
I have installed the Lineage OS ROM: https://forum.xda-developers.com/mi-a2-lite/development/lineageos-16-0-xiaomi-mi-a2-lite-t3919060
It seems that works only one slot, the slot B.
I flash the updates of the rom following this guide: https://github.com/tkchn/daisyinstall/blob/master/README.md
If the active slot is the slot B, when I install an update of the rom in the slot A and then change the active slot to slot A in TWRP, then reboot and the phone goes in bootloop with the androidone logo.
Then I reboot the phone holding the power button, boot to fastboot and boot to recovery.
As this point I repeat the whole process, flashing the rom to slot B and changing the active slot to slot B and now if I reboot the phone all work.
I had this problem with all the updates that I have done.
You have probably different firmware versions on each partition. You can fix that by writing the B partitions into the A ones.
Go to twrp, and through either 'adb shell' or the recovery shell:
Code:
su
dd if=/dev/block/mmcblk0p32 of=/dev/block/mmcblk0p31
dd if=/dev/block/mmcblk0p27 of=/dev/block/mmcblk0p26
dd if=/dev/block/mmcblk0p25 of=/dev/block/mmcblk0p24
dd if=/dev/block/mmcblk0p14 of=/dev/block/mmcblk0p13
dd if=/dev/block/mmcblk0p45 of=/dev/block/mmcblk0p44
dd if=/dev/block/mmcblk0p29 of=/dev/block/mmcblk0p28
dd if=/dev/block/mmcblk0p48 of=/dev/block/mmcblk0p47
dd if=/dev/block/mmcblk0p55 of=/dev/block/mmcblk0p54
dd if=/dev/block/mmcblk0p20 of=/dev/block/mmcblk0p19
dd if=/dev/block/mmcblk0p18 of=/dev/block/mmcblk0p17
dd if=/dev/block/mmcblk0p59 of=/dev/block/mmcblk0p58
You should have exactly similar A/B partitions after this (except for system and boot, the ones updated), and there should be no problem.
With custom rom...
Install the rom , TWRP and disable encryption in slot A
Install gapps, magisk, kernel, etc in slot B
The device only boots in B slot
In stock rom boots in A slot
Its ok
GDFI said:
You have probably different firmware versions on each partition. You can fix that by writing the B partitions into the A ones.
Go to twrp, and through either 'adb shell' or the recovery shell:
Code:
su
dd if=/dev/block/mmcblk0p32 of=/dev/block/mmcblk0p31
dd if=/dev/block/mmcblk0p27 of=/dev/block/mmcblk0p26
dd if=/dev/block/mmcblk0p25 of=/dev/block/mmcblk0p24
dd if=/dev/block/mmcblk0p14 of=/dev/block/mmcblk0p13
dd if=/dev/block/mmcblk0p45 of=/dev/block/mmcblk0p44
dd if=/dev/block/mmcblk0p29 of=/dev/block/mmcblk0p28
dd if=/dev/block/mmcblk0p48 of=/dev/block/mmcblk0p47
dd if=/dev/block/mmcblk0p55 of=/dev/block/mmcblk0p54
dd if=/dev/block/mmcblk0p20 of=/dev/block/mmcblk0p19
dd if=/dev/block/mmcblk0p18 of=/dev/block/mmcblk0p17
dd if=/dev/block/mmcblk0p59 of=/dev/block/mmcblk0p58
You should have exactly similar A/B partitions after this (except for system and boot, the ones updated), and there should be no problem.
Click to expand...
Click to collapse
Thank you very much @GDFI!
Probably I have android 8 in slot A and android 9 in slot B.
I will try to do this. Will all my data and settings survive this?
For knowledge, is there a list to understand what mmcblk**** partitions match?
leechgid said:
With custom rom...
Install the rom , TWRP and disable encryption in slot A
Install gapps, magisk, kernel, etc in slot B
The device only boots in B slot
In stock rom boots in A slot
Its ok
Click to expand...
Click to collapse
I don't understand, can you explain better?
I found how to see the list of partitions of the Mi A2 Lite:
Code:
daisy:/ # ls -l /dev/block/platform/soc/7824900.sdhci/by-name/
total 0
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 DDR -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 aboot_a -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 aboot_b -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 apdp -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 bk1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 bk2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 bk3 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 bk4 -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 bk5 -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 bk6 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 boot_a -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 boot_b -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 cmnlib64_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 cmnlib64_b -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 cmnlib_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 cmnlib_b -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 config -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 devcfg_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 devcfg_b -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 devinfo -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 dip -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 dpo -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 dsp_a -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 dsp_b -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 fsc -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 fsg -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 keymaster_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 keymaster_b -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 keystore -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 limits -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 lksecapp -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 lksecappbak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 logdump -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 mcfg -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 mdtp_a -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 mdtp_b -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 modem_a -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 modem_b -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 modemst1 -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 modemst2 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 mota -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 msadp -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 persist -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 persistbak -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 rpm_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 rpm_b -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 sbl1_a -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 sbl1_b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 sec -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 splash -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 20 1970-05-16 13:21 ssd -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 syscfg -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 system_a -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 system_b -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_a -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_b -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 userdata -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 vendor_a -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 vendor_b -> /dev/block/mmcblk0p59
@GDFI You have omitted three partitions: system, boot, tz.
I understand system and boot, but what is the tz partition?
Should not be copied?
Code:
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_a -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_b -> /dev/block/mmcblk0p36
epcesp said:
@GDFI You have omitted three partitions: system, boot, tz.
I understand system and boot, but what is the tz partition?
Should not be copied?
Code:
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_a -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-05-16 13:21 tz_b -> /dev/block/mmcblk0p36
Click to expand...
Click to collapse
Sorry I omitted the TZ partition by error, it must be copied from b to a too. (not important here but if you want to have an idea about every partition "role" : https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565 )
For the boot and system partitions, you can also flash them from the B slot to the A one if you want, but when you flash an update from the B slot, the new system.img and boot.img from the update will be flashed into the A partitions ; so there's no absolute need to copy them manually unless you want to try booting from the A slot without updating. (I hope I am somehow clear lol )
Oh and it won't affect your data at all!
GDFI said:
Sorry I omitted the TZ partition by error, it must be copied from b to a too. (not important here but if you want to have an idea about every partition "role" : https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565 )
For the boot and system partitions, you can also flash them from the B slot to the A one if you want, but when you flash an update from the B slot, the new system.img and boot.img from the update will be flashed into the A partitions ; so there's no absolute need to copy them manually unless you want to try booting from the A slot without updating. (I hope I am somehow clear lol )
Oh and it won't affect your data at all!
Click to expand...
Click to collapse
Thanks, you were very clear!
Definitely, I used these commands:
Code:
su
dd if=/dev/block/mmcblk0p32 of=/dev/block/mmcblk0p31 # aboot_b -> aboot_a
dd if=/dev/block/mmcblk0p52 of=/dev/block/mmcblk0p51 # boot_b -> boot_a
dd if=/dev/block/mmcblk0p27 of=/dev/block/mmcblk0p26 # cmnlib64_b -> cmnlib64_a
dd if=/dev/block/mmcblk0p25 of=/dev/block/mmcblk0p24 # cmnlib_b -> cmnlib_a
dd if=/dev/block/mmcblk0p14 of=/dev/block/mmcblk0p13 # devcfg_b -> devcfg_a
dd if=/dev/block/mmcblk0p45 of=/dev/block/mmcblk0p44 # dsp_b -> dsp_a
dd if=/dev/block/mmcblk0p29 of=/dev/block/mmcblk0p28 # keymaster_b -> keymaster_a
dd if=/dev/block/mmcblk0p48 of=/dev/block/mmcblk0p47 # mdtp_b -> mdtp_a
dd if=/dev/block/mmcblk0p55 of=/dev/block/mmcblk0p54 # modem_b -> modem_a
dd if=/dev/block/mmcblk0p20 of=/dev/block/mmcblk0p19 # rpm_b -> rpm_a
dd if=/dev/block/mmcblk0p18 of=/dev/block/mmcblk0p17 # sbl1_b -> sbl1_a
dd if=/dev/block/mmcblk0p57 of=/dev/block/mmcblk0p56 # system_b -> system_a
dd if=/dev/block/mmcblk0p36 of=/dev/block/mmcblk0p35 # tz_b -> tz_a
dd if=/dev/block/mmcblk0p59 of=/dev/block/mmcblk0p58 # vendor_b -> vendor_a
Now I have to wait the next update to see if it works.
I have a doubt, if the custom roms only change the system and boot partitions, does that mean that without having the original rom the other partitions will no longer be updated?
epcesp said:
Now I have to wait the next update to see if it works.
I have a doubt, if the custom roms only change the system and boot partitions, does that mean that without having the original rom the other partitions will no longer be updated?
Click to expand...
Click to collapse
Nice!
Yep, the custom roms rely on stock vendor, modem etc... and if you install one on the top of 10.0.0.3 stock for example, the vendor, modem, about, and other partitions will keep the same version and won't be updated with the custom rom updates.
You can update them manually by flashing newer images of those partitions (that can be extracted from ota updates), as long as the new version is still compatible with the rom ; for example a custom rom made to be compatible with an Oreo vendor may not work if the vendor is updated to its Pie version (The vendor having an Oreo version in the slot A might be the reason you couldn't boot :v ). Some developers recommend to use certain versions sometimes.
In short, those partitions won't be updated unless you want to do it manually
Clear, but if I want to update to latest version, mantaining my data and my rom, which partitions should I flash?
All except system and boot?
Yes, you flash everything except system and boot.
But one important thing is : if you have disabled encryption, flashing an update of vendor partition will re-enable forced encryption, so you would need to go to TWRP just after flashing and install Encryption disabler zip BEFORE the first boot, otherwise your data would be encrypted directly after first booting.
I made an update of the rom and now the phone works also in slot a, thanks @GDFI!
GDFI said:
Yes, you flash everything except system and boot.
But one important thing is : if you have disabled encryption, flashing an update of vendor partition will re-enable forced encryption, so you would need to go to TWRP just after flashing and install Encryption disabler zip BEFORE the first boot, otherwise your data would be encrypted directly after first booting.
Click to expand...
Click to collapse
What happens if I have my data already encrypted? I encrypted the phone from android settings.
When I installed the rom for the first time I flashed also force encryption disabled, as reported in the installation guide. Then in the rom from android security settings I encrypted the phone.
I'm not very sure about the purpouse of force encryption disabler.
epcesp said:
What happens if I have my data already encrypted? I encrypted the phone from android settings.
When I installed the rom for the first time I flashed also force encryption disabled, as reported in the installation guide. Then in the rom from android security settings I encrypted the phone.
I'm not very sure about the purpouse of force encryption disabler.
Click to expand...
Click to collapse
Happy it worked
Some ROMs don't support encryption, and TWRP especially cannot read encrypted data so most people prefer disable it. Since you're already encrypted, you can ignore the Disabler stuff!
Ok, thank you very much for all the support!
please help me, I just bricked my lg k10 2017, and I urgently need a dump file from /dev/block/mmcblk0p7 , please back up this directory/patition ,and upload it to me
To make a backup you need to run this command on terminal if=/dev/block/mmcblk0p7 of=/sdcard/aboot.img , and pls send me the aboot.img via email [email protected]
aboot?
OP -> /dev/block/mmcblk0p48
boot -> /dev/block/mmcblk0p13
cache -> /dev/block/mmcblk0p47
cust -> /dev/block/mmcblk0p44
efuse -> /dev/block/mmcblk0p34
eksst -> /dev/block/mmcblk0p26
encrypt -> /dev/block/mmcblk0p27
expdb -> /dev/block/mmcblk0p18
factory -> /dev/block/mmcblk0p33
flashinfo -> /dev/block/mmcblk0p50
frp -> /dev/block/mmcblk0p45
ftm -> /dev/block/mmcblk0p4
keystore -> /dev/block/mmcblk0p23
laf -> /dev/block/mmcblk0p11
lgfota -> /dev/block/mmcblk0p31
lk -> /dev/block/mmcblk0p9
lk2 -> /dev/block/mmcblk0p10
lo_bak_go -> /dev/block/mmcblk0p17
logo -> /dev/block/mmcblk0p16
md1arm7 -> /dev/block/mmcblk0p42
md1dsp -> /dev/block/mmcblk0p41
md1img -> /dev/block/mmcblk0p40
md3img -> /dev/block/mmcblk0p43
metadata -> /dev/block/mmcblk0p39
misc2 -> /dev/block/mmcblk0p3
mpt -> /dev/block/mmcblk0p30
nvcfg -> /dev/block/mmcblk0p37
nvdata -> /dev/block/mmcblk0p38
nvram -> /dev/block/mmcblk0p5
oemkeystore -> /dev/block/mmcblk0p20
para -> /dev/block/mmcblk0p12
persist -> /dev/block/mmcblk0p36
persist_lg -> /dev/block/mmcblk0p29
proinfo -> /dev/block/mmcblk0p1
protect1 -> /dev/block/mmcblk0p7
protect2 -> /dev/block/mmcblk0p8
rct -> /dev/block/mmcblk0p32
recovery -> /dev/block/mmcblk0p14
recoverybak -> /dev/block/mmcblk0p15
seccfg -> /dev/block/mmcblk0p19
secro -> /dev/block/mmcblk0p21
spare1 -> /dev/block/mmcblk0p2
spare2 -> /dev/block/mmcblk0p6
spare3 -> /dev/block/mmcblk0p22
spare4 -> /dev/block/mmcblk0p28
spare5 -> /dev/block/mmcblk0p35
system -> /dev/block/mmcblk0p46
tee1 -> /dev/block/mmcblk0p24
tee2 -> /dev/block/mmcblk0p25
userdata -> /dev/block/mmcblk0p49
Click to expand...
Click to collapse
And if it's bricked, how you restore that partition?
CXZa said:
aboot?
And if it's bricked, how you restore that partition?
Click to expand...
Click to collapse
I 'll use lglaf in linux
CXZa said:
aboot?
And if it's bricked, how you restore that partition?
Click to expand...
Click to collapse
Protect1 and Protect2 is same? A backup?
JunioJsv said:
Protect1 and Protect2 is same? A backup?
Click to expand...
Click to collapse
Not quite the same. There are texts that say the partition name in them.
No idea if a copy from a different device works at all.
That is, what they are used for... these protects...
Have you tried LGUP using refurbish mode?
It should do some wiping before writing.
Or LGBridge?
>LGlaf
Haven't been able to write a partition with that, in windows.
It "writes", that is, it takes its time but it doesn't stick...
I could write into some partitions in terminal mode,
but not into boot and recovery etc.
Now, with root writing into those partitions is possible but useless.
Corrupted, not trusted, whatever errors if them are modified...
Bootloader...
CXZa said:
Not quite the same. There are texts that say the partition name in them.
No idea if a copy from a different device works at all.
That is, what they are used for... these protects...
Have you tried LGUP using refurbish mode?
It should do some wiping before writing.
Or LGBridge?
>LGlaf
Haven't been able to write a partition with that, in windows.
It "writes", that is, it takes its time but it doesn't stick...
I could write into some partitions in terminal mode,
but not into boot and recovery etc.
Now, with root writing into those partitions is possible but useless.
Corrupted, not trusted, whatever errors if them are modified...
Bootloader...
Click to expand...
Click to collapse
Lgup wont work in my case. Already "unblock" the phone or simply gave a dd if=/dev/block/mmcblk0p8 of=/ if=/dev/block/mmcblk0p7 with lglaf and the revible phone
JunioJsv said:
Lgup wont work in my case. Already "unblock" the phone or simply gave a dd if=/dev/block/mmcblk0p8 of=/ if=/dev/block/mmcblk0p7 with lglaf and the revible phone
Click to expand...
Click to collapse
:highfive:
I fixed the same problem with the help of this forum, Thank you so much!.