Hey,
I want to create a vendor partition to upgrade from oreo.
But everytime I try to change the filesystem, i'm loosing the ability to decrypt my system.
Rather then most devices the OP5 does not seem to have a eMMC-Storage which seems to make the partioning not possible.
My partitions look like this:
LOGO -> /dev/block/sde8
abl -> /dev/block/sde6
ablbak -> /dev/block/sde7
apdp -> /dev/block/sde3
bluetooth -> /dev/block/sde24
boot -> /dev/block/sde9
boot_aging -> /dev/block/sde20
cache -> /dev/block/sda3
cdt -> /dev/block/sdd2
cmnlib -> /dev/block/sde27
cmnlib64 -> /dev/block/sde29
cmnlib64bak -> /dev/block/sde30
cmnlibbak -> /dev/block/sde28
config -> /dev/block/sda2
ddr -> /dev/block/sdd3
devcfg -> /dev/block/sde39
devinfo -> /dev/block/sde23
dip -> /dev/block/sde4
dpo -> /dev/block/sde33
dsp -> /dev/block/sde
frp -> /dev/block/sda6
fsc -> /dev/block/sdf4
fsg -> /dev/block/sdf3
fw_4g9n4 -> /dev/block/sde45
fw_4jed -> /dev/block/sde43
fw_4t0n8 -> /dev/block/sde46
fw_8vee -> /dev/block/sde44
hyp -> /dev/block/sde5
hypbak -> /dev/block/sde6
keymaster -> /dev/block/sde25
keymasterbak -> /dev/block/sde26
keystore -> /dev/block/sda5
limits -> /dev/block/sde35
logdump -> /dev/block/sde40
logfs -> /dev/block/sde37
md5 -> /dev/block/sdf5
mdtp -> /dev/block/sde5
mdtpsecapp -> /dev/block/sde2
mdtpsecappbak -> /dev/block/sde3
minidump -> /dev/block/sde47
misc -> /dev/block/sda4
modem -> /dev/block/sde0
modemst -> /dev/block/sdf
modemst2 -> /dev/block/sdf2
msadp -> /dev/block/sde32
oem_dycnvbk -> /dev/block/sda7
oem_stanvbk -> /dev/block/sda8
param -> /dev/block/sda9
persist -> /dev/block/sda2
pmic -> /dev/block/sde8
pmicbak -> /dev/block/sde9
recovery -> /dev/block/sde22
reserve -> /dev/block/sdd
reserve -> /dev/block/sda0
reserve2 -> /dev/block/sda
rpm -> /dev/block/sde
rpmbak -> /dev/block/sde2
sec -> /dev/block/sde7
splash -> /dev/block/sde34
ssd -> /dev/block/sda
sti -> /dev/block/sde38
storsec -> /dev/block/sde4
storsecbak -> /dev/block/sde42
system -> /dev/block/sde2
toolsfv -> /dev/block/sde36
tz -> /dev/block/sde3
tzbak -> /dev/block/sde4
userdata -> /dev/block/sda3
xbl -> /dev/block/sdb
xblbak -> /dev/block/sdc
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 3934856 156 3934700 0% /dev
devpts 0 0 0 0% /dev/pts
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
selinuxfs 0 0 0 0% /sys/fs/selinux
tmpfs 3934856 24 3934832 0% /tmp
pstore 0 0 0 0% /sys/fs/pstore
none 0 0 0 0% /config
adb 0 0 0 0% /dev/usb-ffs/adb
/dev/block/sda3 253920 336 248344 0% /cache
/dev/block/sde10 112576 108704 3872 97% /firmware
/dev/block/sda13 116716656 64605000 52095272 55% /data
/dev/block/sda13 116716656 64605000 52095272 55% /sdcard
I go into TWRP, tried most partitioning tools
(fdisk cant find any tables,
the Party_v0.5_ARM zip [creates vendor part by script] cant handle the encryption,
i dont have parted, etc)
and after they fiddle with the table, my data gets unreadable until I revert the table manipulation.
I'm running xXx No Limits with Magisk on Oreo 8.1 but the menus just dont work if I want to decrypt my device.
So even if I want to install a new rom from scratch, I have to somehow get rid of the encryption or TWRP cant mount any storage at all.
Install OxygenOS 5.1.4, lock bootloader, do a complete boot on 5.1.4 and then unlock again. You will be ready for treble now
PierreVicquery02 said:
Install OxygenOS 5.1.4, lock bootloader, do a complete boot on 5.1.4 and then unlock again. You will be ready for treble now
Click to expand...
Click to collapse
No need to lock bootloader, the vendor partition will be created without it too.
knighToFdemonS said:
Hey,
I want to create a vendor partition to upgrade from oreo.
But everytime I try to change the filesystem, i'm loosing the ability to decrypt my system.
Rather then most devices the OP5 does not seem to have a eMMC-Storage which seems to make the partioning not possible.
My partitions look like this:
LOGO -> /dev/block/sde8
abl -> /dev/block/sde6
ablbak -> /dev/block/sde7
apdp -> /dev/block/sde3
bluetooth -> /dev/block/sde24
boot -> /dev/block/sde9
boot_aging -> /dev/block/sde20
cache -> /dev/block/sda3
cdt -> /dev/block/sdd2
cmnlib -> /dev/block/sde27
cmnlib64 -> /dev/block/sde29
cmnlib64bak -> /dev/block/sde30
cmnlibbak -> /dev/block/sde28
config -> /dev/block/sda2
ddr -> /dev/block/sdd3
devcfg -> /dev/block/sde39
devinfo -> /dev/block/sde23
dip -> /dev/block/sde4
dpo -> /dev/block/sde33
dsp -> /dev/block/sde
frp -> /dev/block/sda6
fsc -> /dev/block/sdf4
fsg -> /dev/block/sdf3
fw_4g9n4 -> /dev/block/sde45
fw_4jed -> /dev/block/sde43
fw_4t0n8 -> /dev/block/sde46
fw_8vee -> /dev/block/sde44
hyp -> /dev/block/sde5
hypbak -> /dev/block/sde6
keymaster -> /dev/block/sde25
keymasterbak -> /dev/block/sde26
keystore -> /dev/block/sda5
limits -> /dev/block/sde35
logdump -> /dev/block/sde40
logfs -> /dev/block/sde37
md5 -> /dev/block/sdf5
mdtp -> /dev/block/sde5
mdtpsecapp -> /dev/block/sde2
mdtpsecappbak -> /dev/block/sde3
minidump -> /dev/block/sde47
misc -> /dev/block/sda4
modem -> /dev/block/sde0
modemst -> /dev/block/sdf
modemst2 -> /dev/block/sdf2
msadp -> /dev/block/sde32
oem_dycnvbk -> /dev/block/sda7
oem_stanvbk -> /dev/block/sda8
param -> /dev/block/sda9
persist -> /dev/block/sda2
pmic -> /dev/block/sde8
pmicbak -> /dev/block/sde9
recovery -> /dev/block/sde22
reserve -> /dev/block/sdd
reserve -> /dev/block/sda0
reserve2 -> /dev/block/sda
rpm -> /dev/block/sde
rpmbak -> /dev/block/sde2
sec -> /dev/block/sde7
splash -> /dev/block/sde34
ssd -> /dev/block/sda
sti -> /dev/block/sde38
storsec -> /dev/block/sde4
storsecbak -> /dev/block/sde42
system -> /dev/block/sde2
toolsfv -> /dev/block/sde36
tz -> /dev/block/sde3
tzbak -> /dev/block/sde4
userdata -> /dev/block/sda3
xbl -> /dev/block/sdb
xblbak -> /dev/block/sdc
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 3934856 156 3934700 0% /dev
devpts 0 0 0 0% /dev/pts
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
selinuxfs 0 0 0 0% /sys/fs/selinux
tmpfs 3934856 24 3934832 0% /tmp
pstore 0 0 0 0% /sys/fs/pstore
none 0 0 0 0% /config
adb 0 0 0 0% /dev/usb-ffs/adb
/dev/block/sda3 253920 336 248344 0% /cache
/dev/block/sde10 112576 108704 3872 97% /firmware
/dev/block/sda13 116716656 64605000 52095272 55% /data
/dev/block/sda13 116716656 64605000 52095272 55% /sdcard
I go into TWRP, tried most partitioning tools
(fdisk cant find any tables,
the Party_v0.5_ARM zip [creates vendor part by script] cant handle the encryption,
i dont have parted, etc)
and after they fiddle with the table, my data gets unreadable until I revert the table manipulation.
I'm running xXx No Limits with Magisk on Oreo 8.1 but the menus just dont work if I want to decrypt my device.
So even if I want to install a new rom from scratch, I have to somehow get rid of the encryption or TWRP cant mount any storage at all.
Click to expand...
Click to collapse
Format internal storage, it will wipe everything and twrp can read it.
knighToFdemonS said:
Hey,
I want to create a vendor partition to upgrade from oreo.
But everytime I try to change the filesystem, i'm loosing the ability to decrypt my system.
Click to expand...
Click to collapse
The only partition that is encrypted is Data. Creation of Vendor has zero to do with encryption. However, you can't use Oreo encryption with Pie roms.
1. Flash any Oneplus 5 firmware (you don't need stock rom) above 5.0.3. That's all you need to create Vendor
2. In TWRP, do format/factory reset, where you must enter 'Yes' to confirm. That will wipe encryption together with all data (back up whatever your need).
Now, you are ready to flash Pie roms.
optimumpro said:
The only partition that is encrypted is Data. Creation of Vendor has zero to do with encryption. However, you can't use Oreo encryption with Pie roms.
1. Flash any Oneplus 5 firmware (you don't need stock rom) above 5.0.3. That's all you need to create Vendor
2. In TWRP, do format/factory reset, where you must enter 'Yes' to confirm. That will wipe encryption together with all data (back up whatever your need).
Now, you are ready to flash Pie roms.
Click to expand...
Click to collapse
Thanks, i will try that. Tried to flash stock again in the beginning but that didnt work either. I will try with crDroid or so, thanks.
Related
I apologize in advance if this is somewhere in the threads here but I could not find this information. thanks to our team member @stratatak7 for getting me this info. hopefully we can bring some good things to the Moto X section.
Code:
aboot -> /dev/block/mmcblk0p5
abootBackup -> /dev/block/mmcblk0p13
boot -> /dev/block/mmcblk0p33
cache -> /dev/block/mmcblk0p36
cid -> /dev/block/mmcblk0p29
clogo -> /dev/block/mmcblk0p31
customize -> /dev/block/mmcblk0p39
devtree -> /dev/block/mmcblk0p32
dhob -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p25
hob -> /dev/block/mmcblk0p21
kpan -> /dev/block/mmcblk0p35
logo -> /dev/block/mmcblk0p30
logs -> /dev/block/mmcblk0p9
mbl -> /dev/block/mmcblk0p20
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p18
modemst2 -> /dev/block/mmcblk0p19
padA -> /dev/block/mmcblk0p10
padB -> /dev/block/mmcblk0p17
padC -> /dev/block/mmcblk0p37
pds -> /dev/block/mmcblk0p28
persist -> /dev/block/mmcblk0p23
recovery -> /dev/block/mmcblk0p34
rpm -> /dev/block/mmcblk0p6
rpmBackup -> /dev/block/mmcblk0p14
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl2Backup -> /dev/block/mmcblk0p11
sbl3 -> /dev/block/mmcblk0p4
sbl3Backup -> /dev/block/mmcblk0p12
sp -> /dev/block/mmcblk0p26
ssd -> /dev/block/mmcblk0p24
system -> /dev/block/mmcblk0p38
tz -> /dev/block/mmcblk0p7
tzBackup -> /dev/block/mmcblk0p15
userdata -> /dev/block/mmcblk0p40
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p16
Oh yeah...let's get this thing started.
Nice to see you around the Moto X forums Mr. V. You still have the GS4?
Sent from my XT1053 using xda app-developers app
oquinones said:
Nice to see you around the Moto X forums Mr. V. You still have the GS4?
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
yep, still have it. gonna be doing work for both devices for a while
Here are the partition mount points
Code:
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p12
boot -> /dev/block/mmcblk0p32
cache -> /dev/block/mmcblk0p36
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p29
customize -> /dev/block/mmcblk0p35
dhob -> /dev/block/mmcblk0p20
factorytune1 -> /dev/block/mmcblk0p10
factorytune2 -> /dev/block/mmcblk0p34
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p31
logo -> /dev/block/mmcblk0p28
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p30
recovery -> /dev/block/mmcblk0p33
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p37
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p38
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
Thank you so much for this! I am interested in themeing the stock ROM, and I'm using ArchiKitchen to help in the deodexing(last time i tried any themeing, it was on JB and the only way i knew how to theme was on a deodexed ROM). In the process of recreating the ROM, ArchiKitchen asks for the kernel path since it doesn't seem to be specified in the stock system.img. Would the system path be the correct path to use or is there one that I missed? Any help is appreciated!
EDIT:
Upon selecting the system path, ArchiKitchen responded with this:
The final effect is:
=-=-=-=-=-=-=-=-=
package_extract_file("boot.img", "/dev/block/mmcblk0p37");
I guessing that this means i should specify the boot path instead. I won't make a move until i know for sure, though.
Seems like the partition block numbers have changed between 4.4.4/first 5.0 leak and the newest 5.0 OTA. What does this mean? Be VERY careful when flashing stuff using the block number (mmcblk0p37) The partition you are trying to flash might have changed and you could brick your ****. Use by-name instead
Partition Layout in 4.4.4 and first 5.0 Soak test OTA:
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p12
boot -> /dev/block/mmcblk0p32
cache -> /dev/block/mmcblk0p36
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p29
customize -> /dev/block/mmcblk0p35
dhob -> /dev/block/mmcblk0p20
factorytune1 -> /dev/block/mmcblk0p10
factorytune2 -> /dev/block/mmcblk0p34
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p31
logo -> /dev/block/mmcblk0p28
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p30
recovery -> /dev/block/mmcblk0p33
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p37
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p38
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
New Partition layout after the .6 OTA
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p12
boot -> /dev/block/mmcblk0p33
cache -> /dev/block/mmcblk0p37
cid -> /dev/block/mmcblk0p26
clogo -> /dev/block/mmcblk0p30
customize -> /dev/block/mmcblk0p36
dhob -> /dev/block/mmcblk0p21
factorytune1 -> /dev/block/mmcblk0p10
factorytune2 -> /dev/block/mmcblk0p35
frp -> /dev/block/mmcblk0p16
fsc -> /dev/block/mmcblk0p23
fsg -> /dev/block/mmcblk0p22
hob -> /dev/block/mmcblk0p20
kpan -> /dev/block/mmcblk0p32
logo -> /dev/block/mmcblk0p29
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p28
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p18
modemst2 -> /dev/block/mmcblk0p19
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p17
pds -> /dev/block/mmcblk0p27
persist -> /dev/block/mmcblk0p31
recovery -> /dev/block/mmcblk0p34
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sp -> /dev/block/mmcblk0p25
ssd -> /dev/block/mmcblk0p24
system -> /dev/block/mmcblk0p38
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p39
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
I have unlocked my Australian xt1572 and booted twrp with the following command:
fastboot boot twrp.img
Then I made a nandroid backup selecting all the options apart from /data
Does this backup my original modem as a part of the backup or is there a specific way to back up my modem from twrp?
I want to make sure that I can revert back to stock (Vodafone) so I can return to original state by restoring the nandroid backup i made and apply the 6.0 ota when its get released down here.
-Ivar
This is something I am trying to find out as well. Anyone able to confirm it?
ivaho said:
I have unlocked my Australian xt1572 and booted twrp with the following command:
fastboot boot twrp.img
Then I made a nandroid backup selecting all the options apart from /data
Does this backup my original modem as a part of the backup or is there a specific way to back up my modem from twrp?
I want to make sure that I can revert back to stock (Vodafone) so I can return to original state by restoring the nandroid backup i made and apply the 6.0 ota when its get released down here.
-Ivar
Click to expand...
Click to collapse
LBSpeller said:
This is something I am trying to find out as well. Anyone able to confirm it?
Click to expand...
Click to collapse
Run "ls -al /dev/block/bootdevice/by-name" in TWRP's terminal or ADB while in TWRP.
You need root if you want to run this command while in Android with USB debugging on.
Look for modem, fsg, modemst1, and modemst2.
Once you find them, make note of the blocks.
For example, here are the partitions of the Pure Edition:
ls -al /dev/block/bootdevice/by-name
DDR -> /dev/block/mmcblk0p4
aboot -> /dev/block/mmcblk0p5
abootBackup -> /dev/block/mmcblk0p12
bluetooth -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p36
cache -> /dev/block/mmcblk0p46
carrier -> /dev/block/mmcblk0p45
cid -> /dev/block/mmcblk0p26
clogo -> /dev/block/mmcblk0p32
customize -> /dev/block/mmcblk0p43
dhob -> /dev/block/mmcblk0p23
frp -> /dev/block/mmcblk0p33
fsc -> /dev/block/mmcblk0p25
fsg -> /dev/block/mmcblk0p24
hob -> /dev/block/mmcblk0p22
hyp -> /dev/block/mmcblk0p9
hypBackup -> /dev/block/mmcblk0p15
keystore -> /dev/block/mmcblk0p42
kpan -> /dev/block/mmcblk0p35
limits -> /dev/block/mmcblk0p30
logo -> /dev/block/mmcblk0p31
logs -> /dev/block/mmcblk0p29
logs-charging -> /dev/block/mmcblk0p39
metadata -> /dev/block/mmcblk0p28
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p20
modemst2 -> /dev/block/mmcblk0p21
oem -> /dev/block/mmcblk0p44
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p19
padC -> /dev/block/mmcblk0p40
persist -> /dev/block/mmcblk0p34
pmic -> /dev/block/mmcblk0p2
pmicBackup -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p37
rpm -> /dev/block/mmcblk0p6
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p3
sdi -> /dev/block/mmcblk0p8
sp -> /dev/block/mmcblk0p41
ssd -> /dev/block/mmcblk0p38
system -> /dev/block/mmcblk0p47
tz -> /dev/block/mmcblk0p7
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p48
utags -> /dev/block/mmcblk0p10
utagsBackup -> /dev/block/mmcblk0p16
Click to expand...
Click to collapse
"modem" = /dev/block/mmcblk0p1
"fsg" = /dev/block/mmcblk0p24
"modemst1" = /dev/block/mmcblk0p20
"modemst2" = /dev/block/mmcblk0p21
To back them up in Terminal:
For modem: dd if=/dev/block/mmcblk0p1 of=/sdcard/NON-HLOS.bin
For modemst1: dd if=/dev/block/mmcblk0p20 of=/sdcard/modemst1
For modemst2: /dev/block/mmcblk0p21 of=/sdcard/modemst2
For fsg: dd if=/dev/block/mmcblk0p1 of=/sdcard/fsg.mbn
Check on your internal storage for those files and save them somewhere.
Spasticdroid said:
Run "ls -al /dev/block/bootdevice/by-name" in TWRP's terminal or ADB while in TWRP.
You need root if you want to run this command while in Android with USB debugging on.
Look for modem, fsg, modemst1, and modemst2.
Once you find them, make note of the blocks.
Click to expand...
Click to collapse
Guess I am out of luck then since I already have installed the indian MM modem :crying:
But luckily the phone works great with this version of mm so at least I dont have a brick
SpasilliumNexus said:
Run "ls -al /dev/block/bootdevice/by-name" in TWRP's terminal or ADB while in TWRP.
You need root if you want to run this command while in Android with USB debugging on.
Look for modem, fsg, modemst1, and modemst2.
Once you find them, make note of the blocks.
For example, here are the partitions of the Pure Edition:
"modem" = /dev/block/mmcblk0p1
"fsg" = /dev/block/mmcblk0p24
"modemst1" = /dev/block/mmcblk0p20
"modemst2" = /dev/block/mmcblk0p21
To back them up in Terminal:
For modem: dd if=/dev/block/mmcblk0p1 of=/sdcard/NON-HLOS.bin
For modemst1: dd if=/dev/block/mmcblk0p20 of=/sdcard/modemst1
For modemst2: /dev/block/mmcblk0p21 of=/sdcard/modemst2
For fsg: dd if=/dev/block/mmcblk0p1 of=/sdcard/fsg.mbn
Check on your internal storage for those files and save them somewhere.
Click to expand...
Click to collapse
How can I restore modem which is backed up in TWRP?
Dear Friends,
I need help to find where is the IMEI data of this phone?Is it saved in hardware or in a partition that I can not find it??
This is partition table of this phone:
DDR -> /dev/block/mmcblk0p4
aboot -> /dev/block/mmcblk0p5
abootBackup -> /dev/block/mmcblk0p12
bluetooth -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p36
cache -> /dev/block/mmcblk0p46
carrier -> /dev/block/mmcblk0p45
cid -> /dev/block/mmcblk0p26
clogo -> /dev/block/mmcblk0p32
customize -> /dev/block/mmcblk0p43
dhob -> /dev/block/mmcblk0p23
frp -> /dev/block/mmcblk0p33
fsc -> /dev/block/mmcblk0p25
fsg -> /dev/block/mmcblk0p24
hob -> /dev/block/mmcblk0p22
hyp -> /dev/block/mmcblk0p9
hypBackup -> /dev/block/mmcblk0p15
keystore -> /dev/block/mmcblk0p42
kpan -> /dev/block/mmcblk0p35
limits -> /dev/block/mmcblk0p30
logo -> /dev/block/mmcblk0p31
logs -> /dev/block/mmcblk0p29
logs-charging -> /dev/block/mmcblk0p39
metadata -> /dev/block/mmcblk0p28
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p20
modemst2 -> /dev/block/mmcblk0p21
oem -> /dev/block/mmcblk0p44
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p19
padC -> /dev/block/mmcblk0p40
persist -> /dev/block/mmcblk0p34
pmic -> /dev/block/mmcblk0p2
pmicBackup -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p37
rpm -> /dev/block/mmcblk0p6
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p3
sdi -> /dev/block/mmcblk0p8
sp -> /dev/block/mmcblk0p41
ssd -> /dev/block/mmcblk0p38
system -> /dev/block/mmcblk0p47
tz -> /dev/block/mmcblk0p7
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p48
utags -> /dev/block/mmcblk0p10
utagsBackup -> /dev/block/mmcblk0p16
It's mmcblk0p20 and mmcblk0p21 according to a twrp backup.
No, they are not there.I checked I think IMEI saved in hardware of this phone because not possible to change still with efspro program,the phone connected but get error in restore but backing up efs is ok