Here is the partition list from the Oneplus 3. Who is interested...
Code:
C:\Users\cargo>adb shell
[email protected]:/ $ su
su
[email protected]:/ # ls -al /dev/block/platform/soc/624000.ufshc/by-name
ls -al /dev/block/platform/soc/624000.ufshc/by-name
lrwxrwxrwx root root 1970-01-20 15:04 LOGO -> /dev/block/sde17
lrwxrwxrwx root root 1970-01-20 15:04 aboot -> /dev/block/sde15
lrwxrwxrwx root root 1970-01-20 15:04 abootbak -> /dev/block/sde16
lrwxrwxrwx root root 1970-01-20 15:04 apdp -> /dev/block/sde30
lrwxrwxrwx root root 1970-01-20 15:04 bluetooth -> /dev/block/sde23
lrwxrwxrwx root root 1970-01-20 15:04 boot -> /dev/block/sde18
lrwxrwxrwx root root 1970-01-20 15:04 boot_aging -> /dev/block/sde19
lrwxrwxrwx root root 1970-01-20 15:04 cache -> /dev/block/sda3
lrwxrwxrwx root root 1970-01-20 15:04 cdt -> /dev/block/sdd2
lrwxrwxrwx root root 1970-01-20 15:04 cmnlib -> /dev/block/sde26
lrwxrwxrwx root root 1970-01-20 15:04 cmnlib64 -> /dev/block/sde28
lrwxrwxrwx root root 1970-01-20 15:04 cmnlib64bak -> /dev/block/sde29
lrwxrwxrwx root root 1970-01-20 15:04 cmnlibbak -> /dev/block/sde27
lrwxrwxrwx root root 1970-01-20 15:04 config -> /dev/block/sda14
lrwxrwxrwx root root 1970-01-20 15:04 ddr -> /dev/block/sdd3
lrwxrwxrwx root root 1970-01-20 15:04 devcfg -> /dev/block/sda6
lrwxrwxrwx root root 1970-01-20 15:04 devcfgbak -> /dev/block/sda7
lrwxrwxrwx root root 1970-01-20 15:04 devinfo -> /dev/block/sde22
lrwxrwxrwx root root 1970-01-20 15:04 dip -> /dev/block/sde13
lrwxrwxrwx root root 1970-01-20 15:04 dpo -> /dev/block/sde32
lrwxrwxrwx root root 1970-01-20 15:04 dsp -> /dev/block/sde12
lrwxrwxrwx root root 1970-01-20 15:04 frp -> /dev/block/sda8
lrwxrwxrwx root root 1970-01-20 15:04 fsc -> /dev/block/sdf3
lrwxrwxrwx root root 1970-01-20 15:04 fsg -> /dev/block/sde7
lrwxrwxrwx root root 1970-01-20 15:04 hyp -> /dev/block/sde5
lrwxrwxrwx root root 1970-01-20 15:04 hypbak -> /dev/block/sde6
lrwxrwxrwx root root 1970-01-20 15:04 keymaster -> /dev/block/sde24
lrwxrwxrwx root root 1970-01-20 15:04 keymasterbak -> /dev/block/sde25
lrwxrwxrwx root root 1970-01-20 15:04 keystore -> /dev/block/sda5
lrwxrwxrwx root root 1970-01-20 15:04 md5 -> /dev/block/sdf4
lrwxrwxrwx root root 1970-01-20 15:04 mdtp -> /dev/block/sde14
lrwxrwxrwx root root 1970-01-20 15:04 misc -> /dev/block/sda4
lrwxrwxrwx root root 1970-01-20 15:04 modem -> /dev/block/sde11
lrwxrwxrwx root root 1970-01-20 15:04 modemst1 -> /dev/block/sdf1
lrwxrwxrwx root root 1970-01-20 15:04 modemst2 -> /dev/block/sdf2
lrwxrwxrwx root root 1970-01-20 15:04 msadp -> /dev/block/sde31
lrwxrwxrwx root root 1970-01-20 15:04 oem_dycnvbk -> /dev/block/sda9
lrwxrwxrwx root root 1970-01-20 15:04 oem_stanvbk -> /dev/block/sda10
lrwxrwxrwx root root 1970-01-20 15:04 param -> /dev/block/sda11
lrwxrwxrwx root root 1970-01-20 15:04 persist -> /dev/block/sda2
lrwxrwxrwx root root 1970-01-20 15:04 pmic -> /dev/block/sde9
lrwxrwxrwx root root 1970-01-20 15:04 pmicbak -> /dev/block/sde10
lrwxrwxrwx root root 1970-01-20 15:04 recovery -> /dev/block/sde21
lrwxrwxrwx root root 1970-01-20 15:04 reserve -> /dev/block/sdd1
lrwxrwxrwx root root 1970-01-20 15:04 reserve1 -> /dev/block/sda12
lrwxrwxrwx root root 1970-01-20 15:04 reserve2 -> /dev/block/sda13
lrwxrwxrwx root root 1970-01-20 15:04 rpm -> /dev/block/sde1
lrwxrwxrwx root root 1970-01-20 15:04 rpmbak -> /dev/block/sde2
lrwxrwxrwx root root 1970-01-20 15:04 sec -> /dev/block/sde8
lrwxrwxrwx root root 1970-01-20 15:04 splash -> /dev/block/sde33
lrwxrwxrwx root root 1970-01-20 15:04 ssd -> /dev/block/sda1
lrwxrwxrwx root root 1970-01-20 15:04 sti -> /dev/block/sde34
lrwxrwxrwx root root 1970-01-20 15:04 system -> /dev/block/sde20
lrwxrwxrwx root root 1970-01-20 15:04 tz -> /dev/block/sde3
lrwxrwxrwx root root 1970-01-20 15:04 tzbak -> /dev/block/sde4
lrwxrwxrwx root root 1970-01-20 15:04 userdata -> /dev/block/sda15
lrwxrwxrwx root root 1970-01-20 15:04 xbl -> /dev/block/sdb1
lrwxrwxrwx root root 1970-01-20 15:04 xblbak -> /dev/block/sdc1
[email protected]:/ #
or without partition names
Code:
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 98304 loop0
8 16 4096 sdb
8 17 4052 sdb1
8 0 56582144 sda
8 1 8 sda1
8 2 32768 sda2
8 3 262144 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 128 sda6
8 7 128 sda7
8 8 512 sda8
8 9 10240 sda9
8 10 10240 sda10
8 11 1024 sda11
8 12 8096 sda12
8 13 16192 sda13
8 14 512 sda14
8 15 56238572 sda15
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
8 64 4194304 sde
8 65 512 sde1
8 66 512 sde2
8 67 2048 sde3
8 68 2048 sde4
8 69 512 sde5
8 70 512 sde6
8 71 2048 sde7
8 72 16 sde8
8 73 512 sde9
8 74 512 sde10
8 75 97280 sde11
8 76 16384 sde12
8 77 1024 sde13
8 78 32768 sde14
8 79 8192 sde15
259 0 8192 sde16
259 1 16384 sde17
259 2 65536 sde18
259 3 65536 sde19
259 4 3080192 sde20
259 5 65536 sde21
259 6 4 sde22
259 7 1024 sde23
259 8 512 sde24
259 9 512 sde25
259 10 256 sde26
259 11 256 sde27
259 12 256 sde28
259 13 256 sde29
259 14 256 sde30
259 15 256 sde31
259 16 4 sde32
259 17 33424 sde33
259 18 2048 sde34
8 32 4096 sdc
8 33 4052 sdc1
8 80 1572864 sdf
8 81 2048 sdf1
8 82 2048 sdf2
8 83 4 sdf3
8 84 512 sdf4
254 0 56238556 dm-0
[email protected]:/ #
cargobr151 said:
I'm trying to find partition name of my OnePlus 3T device to copy its raw disk file in PC. I've been trying since several days. I always stuck on finding partition name of my device.
i have tried diskinfo and many codes that I found randomly on xda but cannot retrieve Oneplus 3T partition name. any help?
Click to expand...
Click to collapse
@Ferga2790 seems to have found the answer! You can flash the Canadian H873 kdz and unlock it. Files are located here: https://forum.xda-developers.com/showpost.php?p=76312669&postcount=10. Good luck! :cyclops: :highfive:
Download mode: power off, hold vol +, plug USB cable into phone
Recovery mode: power off, hold vol - and power, plug USB cable into phone
When you select "reboot to bootloader" in the recovery main menu, it just boots up the phone as normal. ADB nor Fastboot work in either of these modes.
All partitions (after running py lglaf.py --unlock -c "!EXEC ls -la /dev/block/bootdevice/by-name ")
/dev/block/bootdevice/by-name:
total 0
drwxr-xr-x 2 root root 1380 2017-04-28 18:02 .
drwxr-xr-x 4 root root 1560 2017-04-28 18:02 ..
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 aboot -> /dev/block/sde6
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 abootbak -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 apdp -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 boot -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 cache -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 carrier -> /dev/block/sda13
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 cdt -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 cmnlib -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 cmnlib64 -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 cmnlib64bak -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 cmnlibbak -> /dev/block/sde23
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 ddr -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 devcfg -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 devcfgbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 devinfo -> /dev/block/sdb6
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 dip -> /dev/block/sdb5
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 dpo -> /dev/block/sde28
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 drm -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 eksst -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 encrypt -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 factory -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 fota -> /dev/block/sdb3
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 fsc -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 fsg -> /dev/block/sdb4
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 grow -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 grow2 -> /dev/block/sdb7
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 grow3 -> /dev/block/sdc3
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 grow4 -> /dev/block/sdd4
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 grow5 -> /dev/block/sde29
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 grow6 -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 grow7 -> /dev/block/sdg2
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 hyp -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 hypbak -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 keymaster -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 keymasterbak -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 keystore -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 laf -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 lafbak -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 misc -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 modem -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 mpt -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 msadp -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 persist -> /dev/block/sda14
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 persistent -> /dev/block/sdg1
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 pmic -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 pmicbak -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 raw_resources -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 raw_resourcesbak -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 rct -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 recovery -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 recoverybak -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 reserve -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 rpm -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 rpmbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 sec -> /dev/block/sde19
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 sns -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 ssd -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 system -> /dev/block/sda15
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 tz -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 tzbak -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 2017-04-28 18:02 userdata -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 xbl2 -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 xbl2bak -> /dev/block/sdc2
lrwxrwxrwx 1 root root 15 2017-04-28 18:02 xblbak -> /dev/block/sdb2
User @l33tlinuxh4x0r has gotten Download Mode to somewhat work with a modified lglaf, as seen in this post.
Thanks to @Flippy125 for explaining how to access Download Mode in this thread.
Reserved
I have gotten download mode to work somewhat using lglaf.py from this post located here
I am using windows 10 pro
Python 3.6
and the above file.
I have managed to get ls and lsmod commands working.
lsof and lsusb also work.
examples are:
Code:
python lglaf.py --unlock -c "!EXEC ls / "
python lglaf.py --unlock -c "!EXEC ls /system/bin/ "
note that there are 2 spaces between !EXEC and ls and one space after the command ending in /. Capitalization is also important.
I will work on more but I really don't want to mess up my phone.
EDIT: I forgot one of the most important things. How to get your phone to reboot back to normal. Run the following command.
Code:
python lglaf.py --unlock -c "!CTRL RSET"
Figured it out on Windows.
Mr nerd said:
Figured it out on Windows.
Click to expand...
Click to collapse
No updates afaik. I don't have a second device that I am willing to brick to test anything else, but as far as I can tell we are locked down so tight that we will probably never see root on this device unless the rooting methods change 100% and don't require filesystem access and even if that were the case root would be useless as the main reason for root is writing to the filesystem.
EDIT: IF lg allows us to root or unlocks this phone we could have root but I don't see that happening either. Also if we had a tot file for this phone we could have root access but it would be dangerous and if you change anything with it you would get a secure boot error. All we can hope for is that lg releases an engineering build or makes some other major mistake or something else leaks.
l33tlinuxh4x0r said:
No updates afaik. I don't have a second device that I am willing to brick to test anything else, but as far as I can tell we are locked down so tight that we will probably never see root on this device unless the rooting methods change 100% and don't require filesystem access and even if that were the case root would be useless as the main reason for root is writing to the filesystem.
EDIT: IF lg allows us to root or unlocks this phone we could have root but I don't see that happening either. Also if we had a tot file for this phone we could have root access but it would be dangerous and if you change anything with it you would get a secure boot error. All we can hope for is that lg releases an engineering build or makes some other major mistake or something else leaks.
Click to expand...
Click to collapse
Ahh ok ok so do you know how we could start looking for Vulns? I never understood how to debug a phone
Mr nerd said:
Ahh ok ok so do you know how we could start looking for Vulns? I never understood how to debug a phone
Click to expand...
Click to collapse
There is a site that lists all of the known vulnerabilities for linux and android but I forgot what it is. Google probably knows though. However even with a vulnerability root will probably throw an secure boot error. We need a venerability for the bootloader.
Ahh i see what you mean. Well do you know how to debug or fuzz a bootloader?
http://hexdetective.blogspot.com/2017/02/exploiting-android-s-boot-getting.html
Sent from my LG-LS993 using Tapatalk
Hi!
Possible downgrade ZVA to ZV9 or ZV6?
On old model LS996 method to write partitions: https://forum.xda-developers.com/g-flex2/development/lg-g-flex-2-ls996-zv6-sprint-5-1-1-t3169212
I dont' know what to do whith python I cant get to work I enter the codes that are in the instructions and all I get is error after error. telling me that the path is wrong but i got to that path and the file is there .
I was wondering how to create a flashable restore for the stock boot and recovery image I was exploring the partitions and this is where I got stuck(I'm aware that there are A and B partitions, but have no idea what they are(are they split across two partitions or is b a backup of a and vice versa?):
taimen:/dev/block/platform/soc/1da4000.ufshc/by-name $ ls -al .
total 0
drwxr-xr-x 2 root root 1280 1970-01-14 05:56 .
drwxr-xr-x 4 root root 1460 1970-01-14 05:56 ..
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 abl_a -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 abl_b -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 aes_a -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 aes_b -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 align_parti -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 apdp -> /dev/block/sde29
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 boot_a -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 boot_b -> /dev/block/sde22
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 cdt -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 cmnlib64_a -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 cmnlib64_b -> /dev/block/sde24
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 cmnlib_a -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 cmnlib_b -> /dev/block/sde23
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 ddr -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 devcfg_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 devcfg_b -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 devinfo -> /dev/block/sde34
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 dip -> /dev/block/sde35
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 dpo -> /dev/block/sde36
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 dtbo_a -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 dtbo_b -> /dev/block/sde27
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 frp -> /dev/block/sdg1
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 fsc -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 fsg -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 ftm -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 hyp_b -> /dev/block/sde17
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 keymaster_a -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 keymaster_b -> /dev/block/sde21
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 laf_a -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 laf_b -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 limits -> /dev/block/sde37
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 logfs -> /dev/block/sde39
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 metadata -> /dev/block/sde41
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 misc -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 modem_a -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 modem_b -> /dev/block/sde19
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 msadp -> /dev/block/sde30
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 persist -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 pmic_a -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 pmic_b -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 pstore -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 rpm_a -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 rpm_b -> /dev/block/sde15
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 sec -> /dev/block/sde33
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 ssd -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 sti -> /dev/block/sde40
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 storsec -> /dev/block/sde31
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 system_a -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 system_b -> /dev/block/sda8
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 toolsfv -> /dev/block/sde38
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 tz_b -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 userdata -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 vbmeta_a -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 vbmeta_b -> /dev/block/sde26
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 vendor_a -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 vendor_b -> /dev/block/sde28
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 xbl_b -> /dev/block/sdc1
Click to expand...
Click to collapse
There is no recovery partition on this phone. The recovery image is contained within the boot image, which is why the TWRP site has flashable installers that you can download that patch the boot images so that they contain TWRP instead of stock. A and B partitions exist for Google's automatic seamless update feature. Your phone only boots off of either A or B at any given time. If your phone is using A and a software update becomes available, the update will download and install to B, and your phone will boot the B partition on the next reboot instead of A. When a future update is released, the same process will happen with A.
So if you want to backup boot and recovery, all you need to backup is boot of the partition that your phone is currently using (TWRP can tell you which one it is using).
HTC U12+ is an A-B slot phone. There is no recovery partition, but it has boot_a and boot_b partitions, so it CAN boot to recovery mode.
Here is the partitions table from Chinese HTC U12+
Code:
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 abl_a -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 abl_b -> /dev/block/sde30
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 aop_a -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 aop_b -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 apdp -> /dev/block/sde46
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 avb_rec -> /dev/block/sde56
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 bluetooth_a -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 bluetooth_b -> /dev/block/sde27
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 board_info -> /dev/block/sdf1
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 boot_a -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 boot_b -> /dev/block/sde34
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 carrier -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 cmnlib64_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 cmnlib64_b -> /dev/block/sde37
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 cmnlib_a -> /dev/block/sde15
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 cmnlib_b -> /dev/block/sde36
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 control -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 cota -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 devcfg_a -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 devcfg_b -> /dev/block/sde38
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 devinfo -> /dev/block/sde44
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 devlog -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 dip -> /dev/block/sde45
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 dpo -> /dev/block/sde48
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 dsp_a -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 dsp_b -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 dtbo_a -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 dtbo_b -> /dev/block/sde42
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 extra -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 fataldevlog -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 frp -> /dev/block/sda14
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 fsc -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 fsg -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 hosd_a -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 hosd_b -> /dev/block/sde35
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 hvbmeta -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 hyp_b -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 keymaster_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 keymaster_b -> /dev/block/sde32
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 limits -> /dev/block/sde50
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 local -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 lockbooter_a -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 lockbooter_b -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 logdump -> /dev/block/sde54
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 logfs -> /dev/block/sde52
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 mdtp_a -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 mdtp_b -> /dev/block/sde29
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 mdtpsecapp_a -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 mdtpsecapp_b -> /dev/block/sde28
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 mfg -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 misc -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 modemst1 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 modemst2 -> /dev/block/sdf6
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 msadp -> /dev/block/sde47
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 oem_misc -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 padding0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 padding3 -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 persist -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 pg1fs -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 pmic_a -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 pmic_b -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 qupfw_a -> /dev/block/sde18
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 qupfw_b -> /dev/block/sde39
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 radio_a -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 radio_b -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 ramdump -> /dev/block/sda8
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 reserve0 -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 reserve4 -> /dev/block/sde57
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 reserve5 -> /dev/block/sdf7
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 sec -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 sp1 -> /dev/block/sde49
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 ssd -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 sti -> /dev/block/sde53
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 storsec -> /dev/block/sde55
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 system_a -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 system_b -> /dev/block/sda19
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 tool_diag -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 toolsfv -> /dev/block/sde51
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 tz_b -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 userdata -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 vbmeta_a -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 vbmeta_b -> /dev/block/sde41
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 vendor_a -> /dev/block/sde19
lrwxrwxrwx 1 root root 16 1970-01-30 10:42 vendor_b -> /dev/block/sde40
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root 15 1970-01-30 10:42 xbl_config_b -> /dev/block/sdc2
Its pretty much the same for the 64G Unlocked model sold in the US.
Code:
abl_a -> /dev/block/sde9
abl_b -> /dev/block/sde30
aop_a -> /dev/block/sde1
aop_b -> /dev/block/sde22
apdp -> /dev/block/sde46
avb_rec -> /dev/block/sde6
bluetooth_b -> /dev/block/sde27
board_info -> /dev/block/sdf1
boot_a -> /dev/block/sde13
boot_b -> /dev/block/sde34
carrier -> /dev/block/sdd2
cmnlib64_a -> /dev/block/sde16
cmnlib64_b -> /dev/block/sde37
cmnlib_a -> /dev/block/sde15
cmnlib_b -> /dev/block/sde36
control -> /dev/block/sda17
ddr -> /dev/block/sdd3
devcfg_a -> /dev/block/sde17
devcfg_b -> /dev/block/sde38
devinfo -> /dev/block/sda10
dip -> /dev/block/sde45
dpo -> /dev/block/sde48
dsp_a -> /dev/block/sde10
dsp_b -> /dev/block/sde31
dtbo_a -> /dev/block/sde21
dtbo_b -> /dev/block/sde42
extra -> /dev/block/sda12
fataldevlog -> /dev/block/sda11
frp -> /dev/block/sda14
fsc -> /dev/block/sdf4
fsg -> /dev/block/sdf3
hosd_a -> /dev/block/sde14
hosd_b -> /dev/block/sde35
hvbmeta -> /dev/block/sda4
hyp_a -> /dev/block/sde3
hyp_b -> /dev/block/sde24
keymaster_a -> /dev/block/sde11
keymaster_b -> /dev/block/sde32
limits -> /dev/block/sde50
local -> /dev/block/sda15
lockbooter_a -> /dev/block/sde12
lockbooter_b -> /dev/block/sde33
logdump -> /dev/block/sde52
mdtp_a -> /dev/block/sde8
mdtp_b -> /dev/block/sde29
mdtpsecapp_a -> /dev/block/sde7
mdtpsecapp_b -> /dev/block/sde28
mfg -> /dev/block/sdf2
misc -> /dev/block/sda6
modemst1 -> /dev/block/sde47
oem_misc -> /dev/block/sda3
pg1fs -> /dev/block/sda5
pmic_a -> /dev/block/sde4
pmic_b -> /dev/block/sde25
qupfw_a -> /dev/block/sde5
radio_b -> /dev/block/sda8
reserve0 -> /dev/block/sda21
reserve4 -> /dev/block/sde57
reserve5 -> /dev/block/sde43
sp1 -> /dev/block/sde49
ssd -> /dev/block/sda2
sti -> /dev/block/sde53
storsec -> /dev/block/sda18
system_b -> /dev/block/sda19
tool_diag -> /dev/block/sda9
toolsfv -> /dev/block/sde2
tz_b -> /dev/block/sde23
userdata -> /dev/block/sda20
vbmeta_a -> /dev/block/sde20
vbmeta_b -> /dev/block/sde41
vendor_a -> /dev/block/sde19
vendor_b -> /dev/block/sde40
xbl_a -> /dev/block/sdb1
xbl_b -> /dev/block/sdc1
xbl_config_a -> /dev/block/sdb2
xbl_config_b -> /dev/block/sdc2
Hi, guys. I need "modemst1.img" and "modemst2.img" files for my phone(htc_imedugl: 2Q5510000). Can somebody share them. Thank you.
modemst1.img (modemst1 -> /dev/block/sdf5)
modemst2.img (modemst2 -> /dev/block/sdf6)
HTC U11 uses the same partition type too, i checked yesterday
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!