Meizu Pro5 32gb/64gb partition tables/partition information - Meizu Pro 5 Questions & Answers

Hi,
The past week i've been busy in flashing flyme/twrp/ubuntu and all went very well, but i find the experience a little limited until now. Especially when reading about all the ppl who bricked their device or are stuck one way or another with locked bootloaders, missing recovery's etc.
I found that the bootloader unlock status is kept in the /private partition, wether manipulating this partition in order to unlock the device is possible, i dont know.
So in order to up the experience for all i need your help
I've been mapping out the partition layout on my Chinese Meizu Pro5 64gb (converted to global/intl now), but one device only gets you so far. There are differences between the Flyme/Ubuntu devices, the Flyme devices U/A/I and the TWRP recovery (lets all thank faust93) does not work for everyone (it does for me).
For anyone that has access to 'sgdisk' (you successfully installed TWRP or have an Ubuntu edition) i need a layout of your partitions: (your personal info/guid is excluded (-v GUID) from this)
# sgdisk --print /dev/block/sda | grep -v GUID >/sdcard/partition_layout.txt
We have the following devices:
1. G [M576_intl_official] Global 32gb
2. G [M576_intl_official] Global 64gb
3. U: [M576_unicom_custom] Unicom 32gb
4. U: [M576_unicom_custom] Unicom 64gb
5. A: [M576_mobile_public] Mobile Public 32gb
6. A: [M576_mobile_public] Mobile Public 64gb
7. I: [M576_intl_official] Ubuntu Meizu 32gb
8. I: [M576_intl_official] Ubuntu Meizu 64gb
TWRP 3: fstab table (work in progress)
Code:
/private emmc /dev/block/sda1 flags=display="Private";backup=1 # meizu imei/esn/wifi/bluetooth/serial/lock/unlock
/proinfo emmc /dev/block/sda2 # meizu firmware/machine_type/region_id unicom(U)/chicom(A)/intl(G)
#/misc emmc /dev/block/sda3 # empty 0x00
/param emmc /dev/block/sda21 # u-boot active stats
/efs ext4 /dev/block/sda22 flags=display="EFS";backup=1
#/pnv emmc /dev/block/sda23 # empty 0x00
/ldfw emmc /dev/block/sda24 flags=display="Firmware";backup=1
/dtb emmc /dev/block/sda25 flags=display="Device Tree";backup=1
/bootimg emmc /dev/block/sda26 flags=display="Boot"
/recovery ext4 /dev/block/sda27 flags=display="Recovery";backup=1
/bootlogo emmc /dev/block/sda28 flags=display="Bootlogo";backup=1
#/rstinfo emmc /dev/block/sda29 # kernel log
#/mnv ext4 /dev/block/sda30 # nv_protected
#/reserved1 emmc /dev/block/sda31 # empty 0x00
#/reserved2 emmc /dev/block/sda32 # empty 0x00
#/reserved3 emmc /dev/block/sda33 # empty 0x00
/system ext4 /dev/block/sda41 flags=display="System"
#/custom ext4 /dev/block/sda42 # preload: adds applications to system on first install/factory reset
/cache ext4 /dev/block/sda43 flags=display="Cache";backup=1
/sdcard ext4 /dev/block/sda44 flags=display="Internal Storage";storage;settingsstorage
#/u-boot emmc /dev/block/sdb # u-boot bootloader
#- emmc /dev/block/sdc # empty 0x00 ( ?? could be used as backup bootloader for Android 7.0 nougat ??)
/external_sd vfat /dev/block/mmcblk0p1 flags=display="Micro SDcard";storage;wipeingui;removable
/usb-otg vfat ?? flags=display="USB-OTG";storage;wipeingui;removable
*** BRICK WARNING: the bootloader expects >> ldfw << and >>dtb<< ***
*** Make sure ldfw and dtb are flashed, i did not dare to try without ***
*** Also make sure that bootloader and ldfw are from the flyme_5.6.1.19_daily ***
Code:
bootloader: u-boot bootloader
ldfw : u-boot load firmware (TrustZone driver?, can someone verify)
dtb : u-boot device tree blob/binary, to pass to linux kernel
.
Switching from android-to-ubuntu or ubuntu-to-android
requires the following partitions to be flashed:
Code:
/ldfw emmc /dev/block/sda24 flags=display="Firmware";backup=1
/dtb emmc /dev/block/sda25 flags=display="Device Tree";backup=1
/bootimg emmc /dev/block/sda26 flags=display="Boot"
/bootlogo emmc /dev/block/sda28 flags=display="Bootlogo";backup=1
/system ext4 /dev/block/sda41 flags=display="System"
.
My partition table
Code:
Meizu Pro 5 64gb Unicom Edition
Disk /dev/block/sda: 15267840 sectors, 58.2 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID):
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15267834
Partitions will be aligned on 64-sector boundaries
Total free space is 11386 sectors (44.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 1279 1024.0 KiB 0700 private
2 1280 1343 256.0 KiB 0700 proinfo
3 1344 1407 256.0 KiB 0700 misc
21 2048 3071 4.0 MiB 0700 param
22 3072 5119 8.0 MiB 0700 efs
23 5120 5631 2.0 MiB 0700 pnv
24 5632 6655 4.0 MiB 0700 ldfw
25 6656 7679 4.0 MiB 0700 dtb
26 7680 13823 24.0 MiB 0700 bootimg
27 13824 22015 32.0 MiB 0700 recovery
28 22016 30207 32.0 MiB 0700 bootlogo
29 30208 35327 20.0 MiB 0700 rstinfo
30 35328 40447 20.0 MiB 0700 mnv
31 40448 45567 20.0 MiB 0700 reserved1
32 45568 50687 20.0 MiB 0700 reserved2
33 50688 55807 20.0 MiB 0700 reserved3
41 65536 720895 2.5 GiB 0700 system
42 720896 851967 512.0 MiB 0700 custom
43 851968 983039 512.0 MiB 0700 cache
44 983040 15267834 54.5 GiB 0700 userdata
If you find any errors or have contributions, post in the thread or pm me.
Awesome

Wow, what a wasteland ... anyone still here .... here .... here .... ..... .... **dustball** ..... **crickets**
Anyways, i found the partition tables lurking in the bootloader,
they are pretty much the same for all the devices:
The 32gb and 64gb editions are the same, partition 44 userdata is just a leftover partition.
The only difference between Android and Ubuntu is partition 43,
maybe Wimpy can shed some light on this
Code:
< index=43,name=cache,size=[B]512MiB[/B],uuid=${uuid_cache};
---
> index=43,name=cache,size=[B]700MiB[/B],uuid=${uuid_cache};
Android partition table
Code:
index=1,name=private,size=1MiB,start=0x400000,uuid=${uuid_private};
index=2,name=proinfo,size=256KiB,uuid=${uuid_proinfo};
index=3,name=misc,size=256KiB,uuid=${uuid_misc};
index=21,name=param,size=4MiB,start=0x800000,uuid=${uuid_param};
index=22,name=efs,size=8MiB,uuid=${uuid_efs};
index=23,name=pnv,size=2MiB,uuid=${uuid_pnv};
index=24,name=ldfw,size=4MiB,uuid=${uuid_ldfw};
index=25,name=dtb,size=4MiB,uuid=${uuid_dtb};
index=26,name=bootimg,size=24MiB,uuid=${uuid_bootimg};
index=27,name=recovery,size=32MiB,uuid=${uuid_recovery};
index=28,name=bootlogo,size=32MiB,uuid=${uuid_bootlogo};
index=29,name=rstinfo,size=20MiB,uuid=${uuid_rstinfo};
index=30,name=mnv,size=20MiB,uuid=${uuid_mnv};
index=31,name=reserved1,size=20MiB,uuid=${uuid_reserved1};
index=32,name=reserved2,size=20MiB,uuid=${uuid_reserved2};
index=33,name=reserved3,size=20MiB,uuid=${uuid_reserved3};
index=41,name=system,size=2560MiB,start=0x10000000,uuid=${uuid_system};
index=42,name=custom,size=512MiB,uuid=${uuid_custom};
[B]index=43,name=cache,size=512MiB,uuid=${uuid_cache};[/B]
index=44,name=userdata,size=0,uuid=${uuid_userdata};
Ubuntu partition table
Code:
index=1,name=private,size=1MiB,start=0x400000,uuid=${uuid_private};
index=2,name=proinfo,size=256KiB,uuid=${uuid_proinfo};
index=3,name=misc,size=256KiB,uuid=${uuid_misc};
index=21,name=param,size=4MiB,start=0x800000,uuid=${uuid_param};
index=22,name=efs,size=8MiB,uuid=${uuid_efs};
index=23,name=pnv,size=2MiB,uuid=${uuid_pnv};
index=24,name=ldfw,size=4MiB,uuid=${uuid_ldfw};
index=25,name=dtb,size=4MiB,uuid=${uuid_dtb};
index=26,name=bootimg,size=24MiB,uuid=${uuid_bootimg};
index=27,name=recovery,size=32MiB,uuid=${uuid_recovery};
index=28,name=bootlogo,size=32MiB,uuid=${uuid_bootlogo};
index=29,name=rstinfo,size=20MiB,uuid=${uuid_rstinfo};
index=30,name=mnv,size=20MiB,uuid=${uuid_mnv};
index=31,name=reserved1,size=20MiB,uuid=${uuid_reserved1};
index=32,name=reserved2,size=20MiB,uuid=${uuid_reserved2};
index=33,name=reserved3,size=20MiB,uuid=${uuid_reserved3};
index=41,name=system,size=2560MiB,start=0x10000000,uuid=${uuid_system};
index=42,name=custom,size=512MiB,uuid=${uuid_custom};
[B]index=43,name=cache,size=700MiB,uuid=${uuid_cache};[/B]
index=44,name=userdata,size=0,uuid=${uuid_userdata};

I installed ubuntu on a android Meizu Pro 5 and now, when I try to change channels to rc-proposed using system-image-cli I find that the 512MB cache partition is not enough. So I guess that is the reason the Ubuntu version has a 700MB cache partition. That (/dev/sda43) is the place where the files for an upgrade are downloaded and then installed from the recovery mode.

st0rm77 said:
Hi,
The past week i've been busy in flashing flyme/twrp/ubuntu and all went very well, but i find the experience a little limited until now. Especially when reading about all the ppl who bricked their device or are stuck one way or another with locked bootloaders, missing recovery's etc.
I found that the bootloader unlock status is kept in the /private partition, wether manipulating this partition in order to unlock the device is possible, i dont know.
So in order to up the experience for all i need your help
I've been mapping out the partition layout on my Chinese Meizu Pro5 64gb (converted to global/intl now), but one device only gets you so far. There are differences between the Flyme/Ubuntu devices, the Flyme devices U/A/I and the TWRP recovery (lets all thank faust93) does not work for everyone (it does for me).
For anyone that has access to 'sgdisk' (you successfully installed TWRP or have an Ubuntu edition) i need a layout of your partitions: (your personal info/guid is excluded (-v GUID) from this)
# sgdisk --print /dev/block/sda | grep -v GUID >/sdcard/partition_layout.txt
We have the following devices:
1. G [M576_intl_official] Global 32gb
2. G [M576_intl_official] Global 64gb
3. U: [M576_unicom_custom] Unicom 32gb
4. U: [M576_unicom_custom] Unicom 64gb
5. A: [M576_mobile_public] Mobile Public 32gb
6. A: [M576_mobile_public] Mobile Public 64gb
7. I: [M576_intl_official] Ubuntu Meizu 32gb
8. I: [M576_intl_official] Ubuntu Meizu 64gb
TWRP 3: fstab table (work in progress)
Code:
/private emmc /dev/block/sda1 flags=display="Private";backup=1 # meizu imei/esn/wifi/bluetooth/serial/lock/unlock
/proinfo emmc /dev/block/sda2 # meizu firmware/machine_type/region_id unicom(U)/chicom(A)/intl(G)
#/misc emmc /dev/block/sda3 # empty 0x00
/param emmc /dev/block/sda21 # u-boot active stats
/efs ext4 /dev/block/sda22 flags=display="EFS";backup=1
#/pnv emmc /dev/block/sda23 # empty 0x00
/ldfw emmc /dev/block/sda24 flags=display="Firmware";backup=1
/dtb emmc /dev/block/sda25 flags=display="Device Tree";backup=1
/bootimg emmc /dev/block/sda26 flags=display="Boot"
/recovery ext4 /dev/block/sda27 flags=display="Recovery";backup=1
/bootlogo emmc /dev/block/sda28 flags=display="Bootlogo";backup=1
#/rstinfo emmc /dev/block/sda29 # kernel log
#/mnv ext4 /dev/block/sda30 # nv_protected
#/reserved1 emmc /dev/block/sda31 # empty 0x00
#/reserved2 emmc /dev/block/sda32 # empty 0x00
#/reserved3 emmc /dev/block/sda33 # empty 0x00
/system ext4 /dev/block/sda41 flags=display="System"
#/custom ext4 /dev/block/sda42 # preload: adds applications to system on first install/factory reset
/cache ext4 /dev/block/sda43 flags=display="Cache";backup=1
/sdcard ext4 /dev/block/sda44 flags=display="Internal Storage";storage;settingsstorage
#/u-boot emmc /dev/block/sdb # u-boot bootloader
#- emmc /dev/block/sdc # empty 0x00 ( ?? could be used as backup bootloader for Android 7.0 nougat ??)
/external_sd vfat /dev/block/mmcblk0p1 flags=display="Micro SDcard";storage;wipeingui;removable
/usb-otg vfat ?? flags=display="USB-OTG";storage;wipeingui;removable
*** BRICK WARNING: the bootloader expects >> ldfw << and >>dtb<< ***
*** Make sure ldfw and dtb are flashed, i did not dare to try without ***
*** Also make sure that bootloader and ldfw are from the flyme_5.6.1.19_daily ***
Code:
bootloader: u-boot bootloader
ldfw : u-boot load firmware (TrustZone driver?, can someone verify)
dtb : u-boot device tree blob/binary, to pass to linux kernel
.
Switching from android-to-ubuntu or ubuntu-to-android
requires the following partitions to be flashed:
Code:
/ldfw emmc /dev/block/sda24 flags=display="Firmware";backup=1
/dtb emmc /dev/block/sda25 flags=display="Device Tree";backup=1
/bootimg emmc /dev/block/sda26 flags=display="Boot"
/bootlogo emmc /dev/block/sda28 flags=display="Bootlogo";backup=1
/system ext4 /dev/block/sda41 flags=display="System"
.
My partition table
Code:
Meizu Pro 5 64gb Unicom Edition
Disk /dev/block/sda: 15267840 sectors, 58.2 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID):
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15267834
Partitions will be aligned on 64-sector boundaries
Total free space is 11386 sectors (44.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 1279 1024.0 KiB 0700 private
2 1280 1343 256.0 KiB 0700 proinfo
3 1344 1407 256.0 KiB 0700 misc
21 2048 3071 4.0 MiB 0700 param
22 3072 5119 8.0 MiB 0700 efs
23 5120 5631 2.0 MiB 0700 pnv
24 5632 6655 4.0 MiB 0700 ldfw
25 6656 7679 4.0 MiB 0700 dtb
26 7680 13823 24.0 MiB 0700 bootimg
27 13824 22015 32.0 MiB 0700 recovery
28 22016 30207 32.0 MiB 0700 bootlogo
29 30208 35327 20.0 MiB 0700 rstinfo
30 35328 40447 20.0 MiB 0700 mnv
31 40448 45567 20.0 MiB 0700 reserved1
32 45568 50687 20.0 MiB 0700 reserved2
33 50688 55807 20.0 MiB 0700 reserved3
41 65536 720895 2.5 GiB 0700 system
42 720896 851967 512.0 MiB 0700 custom
43 851968 983039 512.0 MiB 0700 cache
44 983040 15267834 54.5 GiB 0700 userdata
If you find any errors or have contributions, post in the thread or pm me.
Awesome
Click to expand...
Click to collapse
Hi, I have lost my partitions due to the latest update of Magisk.
PYCON told me that I could redefine my partitions yet I haven't got a clue about how to do this.
I have a chinese version 32 Gb Pro 5 by the way.
This guy here has the same problem : https://forum.xda-developers.com/meizu-pro-5/help/provide-images-partitions-t3639336
Could somebody help us please ?

Related

How to mount the root filesystem in twrp recovery?

Sorry for this perhaps dumb question and I'm sure it was answered anywhere but searching for "mount root recovery" lists everything to root the device. Last time I need to do this was on my HTC Desire with that S-ON
Ok, but for the backgrounds:
I am running CM13 (rooted of cource) and I need to tweak /init.cm.rc startup script.
When doing this while running CM13 (/ filesystem mounted rw) any changes are gone after reboot.
So how can I do this?
My first thought was: Edit while in recovery. But in TWRP (3.0) the root filesystem isn't mounted - so how can I mount it?
Or on which partition is it located?
Thanks in advance!
Code:
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 44 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 16384 180223 80.0M 0700 modem
2 180224 182271 1024K 0700 sbl1
3 182272 182463 98304 0700 sdi
4 182464 184511 1024K 0700 tz
5 184512 185511 500K 0700 rpm
6 185512 186535 512K 0700 hyp
7 186536 186791 128K 0700 pmic
8 186792 188839 1024K 0700 DDR
9 188840 189095 128K 0700 sec
10 189096 197855 4380K 0700 aboot
11 197856 198111 128K 0700 pmicbak
12 198112 200159 1024K 0700 sbl1bak
13 200160 202207 1024K 0700 tzbak
14 202208 203207 500K 0700 rpmbak
15 203208 204231 512K 0700 hypbak
16 204232 212991 4380K 0700 abootbak
17 212992 212993 1024 0700 devinfo
18 229376 237567 4096K 0700 fsg
19 245760 245761 1024 0700 limits
20 262144 270335 4096K 0700 modemst1
21 270336 278527 4096K 0700 modemst2
22 278528 279039 256K 0700 apdp
23 279040 279551 256K 0700 msadp
24 279552 280063 256K 0700 keymaster
25 280064 280575 256K 0700 cmnlib
26 280576 281087 256K 0700 keymasterbak
27 281088 281599 256K 0700 cmnlibbak
28 281600 281601 1024 0700 dpo
29 281602 281603 1024 0700 fsc
30 281604 281619 8192 0700 ssd
31 281620 294911 6646K 0700 oeminfo
32 294912 311295 8192K 0700 persist
33 311296 344063 16.0M 0700 metadata
34 344064 409599 32.0M 0700 boot
35 409600 475135 32.0M 0700 recovery
36 475136 606207 64.0M 0700 oem
37 606208 1015807 200M 0700 vendor
38 1015808 1220607 100M 0700 cache
39 1220608 1222655 1024K 0700 misc
40 1222656 1223679 512K 0700 keystore
41 1223680 1224703 512K 0700 frp
42 1224704 1225703 500K 0700 persistent
43 1225704 7517159 3072M 0700 system
44 7517160 61071326 25.5G 0700 userdata
markusmuster said:
Sorry for this perhaps dumb question and I'm sure it was answered anywhere but searching for "mount root recovery" lists everything to root the device. Last time I need to do this was on my HTC Desire with that S-ON
Ok, but for the backgrounds:
I am running CM13 (rooted of cource) and I need to tweak /init.cm.rc startup script.
When doing this while running CM13 (/ filesystem mounted rw) any changes are gone after reboot.
So how can I do this?
My first thought was: Edit while in recovery. But in TWRP (3.0) the root filesystem isn't mounted - so how can I mount it?
Or on which partition is it located?
Thanks in advance!
Code:
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 44 entries
First usable sector is 34, last usable sector is 61071326
Click to expand...
Click to collapse
sorry but init.cm.rc is a RAMDISK file... that means you need to change it in the boot.img .... so you will need to compile a new boot.img with your changes or use android image kitchen... but i warn you... playing with boot.img is for devs so dont do mistakes in there!
Sent from my Xperia T using XDA Free mobile app
Thanks for the information. Already guesses that.
Yesterday I saw somewhere in the init scripts that there was a Cyan-test for a user script. I will investigate this.

How to install a new rom with bootloader loocked?

Hello I have a machine Redmi2 that does not boot, only boots with fastboot when I pressed the power off button ans Vol - button
I can execute fastboot commands.
For example:
fastboot devices
Click to expand...
Click to collapse
967354587d12 fastboot
Click to expand...
Click to collapse
fastboot oem device-info
Click to expand...
Click to collapse
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.004s]
finished. total time: 0.004s
Click to expand...
Click to collapse
I could dowloaded various rom (official from xiaomi and not official like aosp-caf_wt88047_64-21-05-2017-eng.pirej.zip or xiaomi-miui-hellas-5.1_wt88047_V8_XTRVbeta2_7.2.24.zip) but I can install a new system in this machine.
First I try to unlock the bootloader with official method from Xiaomi but the result is error.
Now I try to boot with twrp and this is works.
To boot with twrp I cam execute this with fastboot
fastboot flash recovery twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
target reported max download size of 268435456 bytes
sending 'recovery' (11426 KB)...
OKAY [ 0.360s]
writing 'recovery'...
OKAY [ 0.184s]
finished. total time: 0.544s
Click to expand...
Click to collapse
fastboot flash boot twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
target reported max download size of 268435456 bytes
sending 'boot' (11426 KB)...
OKAY [ 0.361s]
writing 'boot'...
OKAY [ 0.132s]
finished. total time: 0.493s
Click to expand...
Click to collapse
And with this comand boots the machine with twrp
fastboot boot twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
When machine boots I have access to external card from my PC and I can put the rom to try to install.
When try to clean the partitions I can not do it:
This is the errors
Error al desmontar '/system' (invalid argument)
Error al desmontar '/data' (invalid argument)
Error al desmontar '/cache' (invalid argument)
Incapaz de montar almacenamiento
Click to expand...
Click to collapse
When I try to install RR-N-v5.8.3-20170516-wt88047-OFFICIAL.zip for example I can not install this rom.
Do you know if it is possible install a rom with bootloader locked?
Doy you know if it is possible unlocked the bootloader if xiaomi unlocker does not works?
Any ideas to install a rom in this machine?
Best regards.
i heard that redmi2 has unlocked bootloader and you are using twrp arm64 ? try official twrp and install rom ?
AKHILR4J said:
i heard that redmi2 has unlocked bootloader and you are using twrp arm64 ? try official twrp and install rom ?
Click to expand...
Click to collapse
Thanks for your help,
I have downloaded the lastest twrp img from redmi 2, and I have the same problems.
Machine boots with twrp but I can not write in the internal partitions and I can not install a rom.
I think that I need unlock the bootloader to can to modify the android partitions but I do not know to do it.
try this one
when in twrp, open mount, give check to system, but uncheck "mount system partition read-only"
then try flash the custom rom
when tried "fastboot oem device-info" to my redmi 2 it also show "(bootloader) Device unlocked: false"
yet i can install just now, LineageOS
Liquid2 said:
try this one
when in twrp, open mount, give check to system, but uncheck "mount system partition read-only"
then try flash the custom rom
when tried "fastboot oem device-info" to my redmi 2 it also show "(bootloader) Device unlocked: false"
yet i can install just now, LineageOS
Click to expand...
Click to collapse
Hello, thanks for your help, but when I open Mount, only I can check Firmware, Persist, Micro SDCard and I can check Mount system partition read only.
I can not check System, Data, Cache and when I select Storage (Internal Storage (0MB).
I can use TWRP becuase I execute fastboot boot twrp-3.1.1-0-wt88047.img, ¿it is possible open twrp with any parameters?
Regards, Julio.
Hello again, I have tried to mount /system with a terminal in TWRP with this command
Code:
# Montamos la carpeta /system como lectura(r) y escritura(w)
mount -o remount,rw /system
but the problem is my /proc/mounts file
Code:
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=967420k,nr_inodes=153983,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,size=967420k,nr_inodes=153983 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p25 /persist ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk1p1 /external_sd vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p1 /firmware vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
Do you know how can I can change this file to include the /system partition to mount read/write and I can install a rom os.
Regards,
jriosa said:
Hello, thanks for your help, but when I open Mount, only I can check Firmware, Persist, Micro SDCard and I can check Mount system partition read only.
I can not check System, Data, Cache and when I select Storage (Internal Storage (0MB).
I can use TWRP becuase I execute fastboot boot twrp-3.1.1-0-wt88047.img, ¿it is possible open twrp with any parameters?
Regards, Julio.
Click to expand...
Click to collapse
have u tried another twrp?? make sure it for your device
Liquid2 said:
have u tried another twrp?? make sure it for your device
Click to expand...
Click to collapse
Thanks for your help, I have tried different versions from twrp with the same result.
Regards, Julio.
sori, cant help much, maybe
i myself in very newbie
how about if you flash fresh with flashboot rom using miflash, see if it can boot into official miui first
then you can try install twrp again and flash custom rom
have you tried twrp
Hello Now I access to android with adb.
When I boot the android with TWRP, I can access with my PC using adb.
I execute this.
adb root
Click to expand...
Click to collapse
adb shell
Click to expand...
Click to collapse
This is the partitions on my machine
~ # cat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1 mmcblk0p16
179 17 8 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 32 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 16 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1048576 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 512 mmcblk0p27
179 28 32 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 13557743 mmcblk0p30
179 32 4096 mmcblk0rpmb
179 64 30375936 mmcblk1
179 65 30371840 mmcblk1p1
Click to expand...
Click to collapse
~ # cd /dev
/dev # find -inme mmcblk0
find: unrecognized: -inme
Segmentation fault
/dev # find -iname mmcblk0
./block/mmcblk0
./block/platform/soc.0/7824900.sdhci/mmcblk0
Click to expand...
Click to collapse
I have added parted to managed partitions in my machine
To see parttions in my disk
~ # /sbin/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) p
Click to expand...
Click to collapse
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 524kB tz
9 139MB 139MB 524kB tzbak
10 139MB 140MB 524kB hyp
11 140MB 141MB 524kB hypbak
12 141MB 142MB 1049kB pad
13 142MB 143MB 1573kB modemst1
14 143MB 145MB 1573kB modemst2
15 145MB 146MB 1049kB misc
16 146MB 146MB 1024B fsc
17 146MB 146MB 8192B ssd
18 146MB 156MB 10.5MB splash
19 201MB 201MB 32.8kB DDR
20 201MB 203MB 1573kB fsg
21 203MB 203MB 16.4kB sec
22 203MB 237MB 33.6MB boot
23 237MB 1310MB 1074MB system
24 1310MB 1646MB 336MB cache
25 1646MB 1679MB 33.6MB ext4 persist
26 1679MB 1713MB 33.6MB recovery
27 1745MB 1745MB 524kB keystore
28 1745MB 1745MB 32.8kB config
29 1745MB 1812MB 67.1MB oem
30 1879MB 15.8GB 13.9GB userdata
Click to expand...
Click to collapse
To see my partitions
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 32.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 13.4G 15.6G 46% /external_sd
Click to expand...
Click to collapse
I think that I can not install a new rom (offcial or unofficial) because the system I can not access to partitions /system for example and I think that system partitions is mmcblk0p23.
Do you know how I can modify my partitions to see in df -h and launch a new rom with twrp?
Thanks a lot,
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
Click to expand...
Click to collapse
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
Click to expand...
Click to collapse
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
jriosa said:
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
Click to expand...
Click to collapse
Have you unmounted the data partition in twrp before executing the rm command?
SidOfficial said:
Have you unmounted the data partition in twrp before executing the rm command?
Click to expand...
Click to collapse
This is my commands and my point mounts are
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 28.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
Click to expand...
Click to collapse
I see a new error
~ # parted /dev/block/mmcblk0p30
Error: Could not stat device /dev/block/mmcblk0p30 - No such file or directory.
Retry/Cancel? C
C
Click to expand...
Click to collapse
maybe the first partition I think is OK
~ # parted /dev/block/mmcblk0p1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p1: 67.1MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 67.1MB 67.1MB fat16
Click to expand...
Click to collapse
adb shell
~ # cp /external_sd/parted /sbin/parted
~ # chmod +x /sbin/parted
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 28.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
~ # 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) unit MiB
unit MiB
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
(parted) rm 30
rm 30
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
(parted) q
q
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk0p30
Error: Could not stat device /dev/block/mmcblk0p30 - No such file or directory.
Retry/Cancel? C
C
~ # 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) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 524kB tz
9 139MB 139MB 524kB tzbak
10 139MB 140MB 524kB hyp
11 140MB 141MB 524kB hypbak
12 141MB 142MB 1049kB pad
13 142MB 143MB 1573kB modemst1
14 143MB 145MB 1573kB modemst2
15 145MB 146MB 1049kB misc
16 146MB 146MB 1024B fsc
17 146MB 146MB 8192B ssd
18 146MB 156MB 10.5MB splash
19 201MB 201MB 32.8kB DDR
20 201MB 203MB 1573kB fsg
21 203MB 203MB 16.4kB sec
22 203MB 237MB 33.6MB boot
23 237MB 1310MB 1074MB system
24 1310MB 1646MB 336MB cache
25 1646MB 1679MB 33.6MB ext4 persist
26 1679MB 1713MB 33.6MB recovery
27 1745MB 1745MB 524kB keystore
28 1745MB 1745MB 32.8kB config
29 1745MB 1812MB 67.1MB oem
30 1879MB 15.8GB 13.9GB userdata
(parted)
Click to expand...
Click to collapse
Do you know Iif it is possible to clean all disk and I can recreate /system, /cache, /persist, /firmware and /data partitions?
jriosa said:
This is my commands and my point mounts are
I see a new error
maybe the first partition I think is OK
Do you know Iif it is possible to clean all disk and I can recreate /system, /cache, /persist, /firmware and /data partitions?
Click to expand...
Click to collapse
Yes, you can recreate all the partitions and can even resize the system and data partitions. Head over to this link https://forum.xda-developers.com/redmi-2/how-to/wt88047-redmi-2-resize-partition-t3612933

Where is the BCT image on the TPT?

Can someone explain me how the TPT does the booting? According to the nvidia manual there should be a BCT image somewhere on the device, either in SPI or in eMMC but I can not find it. According to this post: https://forum.xda-developers.com/showthread.php?t=2318140 there should be 16 partitions, but it looks like I only have 10:
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 15387648 mmcblk0
179 1 6144 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 786432 mmcblk0p3
179 4 921600 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 524288 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 143360 mmcblk0p8
259 1 20480 mmcblk0p9
259 2 12939264 mmcblk0p10
[email protected]:/ # ls -al /dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2018-08-16 09:07 AP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2018-08-16 09:07 CC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2018-08-16 09:07 LX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2018-08-16 09:07 MC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2018-08-16 09:07 PA -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2018-08-16 09:07 SC -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2018-08-16 09:07 SS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2018-08-16 09:07 UA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2018-08-16 09:07 UP -> /dev/block/mmcblk0p8
As p1 is the recovery image and p2 is the kernel, I do not see any more partitions where the BCT image could be.
nvflash does not work on my device, as the APX mode is locked.
What I find a little bit worrying, is that fdisk says I have no partition table:
Code:
[email protected]:/ # fdisk -l mmcblk0
Disk mmcblk0: 15.7 GB, 15756951552 bytes
4 heads, 16 sectors/track, 480864 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk mmcblk0 doesn't contain a valid partition table
Should this command fail?
But there must be the configuration somewhere, right?
I have a TPT 1839-22G
I imaged now the whole eMMC using dd and found out that in difference to the posted partition table, the partitions BCT, PT, EBT and GP1 are missing. the Partitions SOS starts 0x100000 bytes earlier as given in the other thread.
Between 0x0 and 0x00d00000 I can find some non zero bytes but nothing which caught my attention.
Using gdisk I could restore the partition table:
Code:
GPT fdisk (gdisk) version 1.0.3
Unsupported GPT version in backup header; read 0x00000000, should be
0x00010000
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): p
Disk mmcblk0.img: 30775296 sectors, 14.7 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): D3A36F54-6FB0-48C2-B599-DFD0D4E294BF
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 30775262
Partitions will be aligned on 2048-sector boundaries
Total free space is 30775229 sectors (14.7 GiB)
Number Start (sector) End (sector) Size Code Name
Command (? for help): r
Recovery/transformation command (? for help): b
Recovery/transformation command (? for help): p
Disk mmcblk0.img: 30775296 sectors, 14.7 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): D3A36F54-6FB0-48C2-B599-DFD0D4E294BF
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 30775262
Partitions will be aligned on 2048-sector boundaries
Total free space is 30775229 sectors (14.7 GiB)
Number Start (sector) End (sector) Size Code Name
Recovery/transformation command (? for help): c
Warning! This will probably do weird things if you've converted an MBR to
GPT form and haven't yet saved the GPT! Proceed? (Y/N): y
Caution! After loading partitions, the CRC doesn't check out!
Recovery/transformation command (? for help): p
Disk mmcblk0.img: 30775296 sectors, 14.7 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): D3A36F54-6FB0-48C2-B599-DFD0D4E294BF
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 30775262
Partitions will be aligned on 2048-sector boundaries
Total free space is 30653 sectors (15.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 26624 38911 6.0 MiB 0700 体S
2 38912 55295 8.0 MiB 0700 乌X
3 55296 1628159 768.0 MiB 0700 偁P
4 1628160 3471359 900.0 MiB 0700 䅃C
5 3471360 3475455 2.0 MiB 0700 卍C
6 3475456 4524031 512.0 MiB 0700 䥐A
7 4524032 4564991 20.0 MiB 0700 䕓C
8 4564992 4851711 140.0 MiB 0700 单P
9 4851712 4892671 20.0 MiB 0700 䑐A
10 4892672 30771199 12.3 GiB 0700 䑕A
Which also shows, that there are no partitions before 0xd00000.
But where is the BCT stored then?

broken partition table, please help - newbie

Hi, I recently decided to dust off my old nexus 10 and install a current version of android on it. With some guides I unlocked the bootloader, installed TWRP, installed AOSP Android 9.0 Pie and then when I wanted to install open gapps I got an not enough space error. After some searching I found a post with a repit file, which should automatically increase the size of my system partition. Unfortunatelly while this repit thing was running the display flickered for a second and the resize failed. (Stupid as I am I didnt make screenshot of the error :/) I think the screen flickering thing is a hardware problem, as it did this even without cutum recovery/rom from time to time. But i always thought it was only a problem with the the screen backlight, as it had no impact on any running software before. (I replaced the battery now to maybe fix this.) But my main problem now is, that TWRP cant mount any partitions. I think the partition table is broken.
fdisk -l doesnt output anything
fdisk -l /dev/block/mmcblk0
Code:
warning: GPT array CRC is invalid
Found valid GPT with protective MBR; using GPT
Disk mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 52444e41-494f-2044-4d4d-43204449534b
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 8192 49151 20.0M 0700 efs
2 49152 65535 8192K 0700 param
3 65536 98303 16.0M 0700 boot
4 98304 163711 31.9M 0700 recovery
5 163712 163839 65536 0700 metadata
6 163840 172031 4096K 0700 misc
7 172032 376831 100M 0700 cache
8 2301952 2826239 256M 0700
9 2891776 61063167 27.7G 0700 userdata
I think 8 should be the corrupted system partition. But isnt there also "data" missing?
Should I resize 8 to 376832 - 2891775 and fix the missing name?
ls /dev/block
Code:
loop0 loop5 mmcblk0boot1 ram11 ram2 ram7
loop1 loop6 platform ram12 ram3 ram8
loop2 loop7 ram0 ram13 ram4 ram9
loop3 mmcblk0 ram1 ram14 ram5 zram0
loop4 mmcblk0boot0 ram10 ram15 ram6
There mmcblk0p7, mmcblk0p8, etc. are missing. How can I fix this?
Can someone help me please? I dont want to break it even further :/
I think I solved it. I downloaded the factory image and ran flash-all. Now the stock rom is running again and I can try flashing a custom rom again.

Resizing /system and /userdata in Note 3 SM-N9005

Hello to all.
I am trying to resize the partition /system using the parted and gdisk commands. But none of these commands succeed in changing mmcblk0 partitions after execution.
The things I do are as follows:
- install adb and fastboot and put them to the system variables.
- enable Settings>developer options>USB debugging and Root debugging
- install TWRP recovery.
- run cmd in adminitsrator permission.
- write these command in CMD :
adb root
adb reboot recovery
adb push gdisk /sbin
adb push parted /sbin
adb shell chmod 777 /sbin/gdisk
adb shell chmod 777 /sbin/parted
adb shell
~#> cd /dev/block
dev/block> gdisk mmcblk0
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/block/mmcblk0: 61071360 sectors, 29.1 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 61071326
Partitions will be aligned on 2-sector boundaries
Total free space is 8158 sectors (4.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 8192 38911 15.0 MiB 8300 apnhlos
2 38912 156543 57.4 MiB 0700 modem
3 156544 157567 512.0 KiB FFFF sbl1
4 157568 157631 32.0 KiB FFFF dbi
5 157632 157695 32.0 KiB FFFF ddr
6 157696 161791 2.0 MiB FFFF aboot
7 161792 162815 512.0 KiB FFFF rpm
8 162816 163839 512.0 KiB FFFF tz
9 163840 184319 10.0 MiB FFFF pad
10 184320 204799 10.0 MiB 8300 param
11 204800 233471 14.0 MiB 8300 efs
12 233472 239615 3.0 MiB FFFF modemst1
13 239616 245759 3.0 MiB FFFF modemst2
14 245760 268287 11.0 MiB FFFF boot
15 268288 294911 13.0 MiB FFFF recovery
16 294912 321535 13.0 MiB FFFF fota
17 321536 335853 7.0 MiB 8300 backup
18 335854 341997 3.0 MiB FFFF fsg
19 341998 341999 1024 bytes FFFF fsc
20 342000 342015 8.0 KiB FFFF ssd
21 342016 358399 8.0 MiB 8300 persist
22 358400 376831 9.0 MiB 8300 persdata
23 376832 5095423 2.3 GiB 8300 system
24 5095424 5709823 300.0 MiB 8300 cache
25 5709824 5730303 10.0 MiB 8300 hidden
26 5730304 61071326 26.4 GiB 8300 userdata
Command (? for help): d
Partition number (1-26): 26
Command (? for help):w
(curser blinking) and device goes to hang!!!!!
anyone can help me? I do this in parted command. It is like above.
after restarting the device, all of the partition are there, like before...
I also used PIT file with different partition sizes, but nothing change. Odin shown : RQT_CLOSE!!

Categories

Resources