Why a full restore does not unbrick my phone
Why a full restore does not unbrick my phone
Quote:Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
(22-05-2021, 02:35 PM)Ga Gu I said in my last thread that I made a full backup of all the partitions of my Meizu M5 Note (M1621) before I tried following a tutorial to unlock the bootloader and bricked my phone. In that thread I wanted to know how to flash the preloader partition when error STATUS_SEC_DL_FORBIDDEN is encountered.flash back factory firmware
But here's an update. Today I checked the preloader partition again and found that it was not changed at all. So I don't need to flash that partition.
So I restored all the partitions of my phone using SP Flash Tool. But it still doesn't come back to life!
When I try to switch it on, it says:
Quote:Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then after a few seconds, the screen goes black, and then the logo Flyme shows up with a circle on the bottom half of the screen, and the phone stucks there forever.
It seems that restoring all the partitions I previously backed up doesn't help me unbrick my phone.
I wonder why?
Are there any other places than the eMMC momery chip that store information about whether the phone is bootloader unlocked?
Can anyone please explain that to me?
(22-05-2021, 02:35 PM)Ga Gu ...
It seems that restoring all the partitions I previously backed up doesn't help me unbrick my phone.
I wonder why?
Are there any other places than the eMMC momery chip that store information about whether the phone is bootloader unlocked?
Can anyone please explain that to me?
(23-05-2021, 06:29 PM)X3non depends what your backup contains, any custom images? if yes then you might want to flash back stock before relocking bootloader
on mtk, formatting seccfg partition will relock bootloader
- partition_index: SYS14
partition_name: seccfg
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x29800000
physical_start_addr: 0x29800000
partition_size: 0x800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
is_upgradable: false
empty_boot_needed: false
reserve: 0x00
sgdisk --print /dev/block/mmcblk0
Number Start (sector) End (sector) Size Code Name
32 122109919 122142686 16.0 MiB 0700 flashinfo
- partition_index: SYS33
partition_name: flashinfo
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF0080
physical_start_addr: 0xFFFF0080
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
is_upgradable: false
empty_boot_needed: false
reserve: 0x00
(bootloader) product: MZ6755_66_N
(bootloader) product: WT6755_66_N5_M
(24-05-2021, 04:26 PM)Ga Gu 1. I still can't flash back the flashinfo partition. It gives me "please check the load image file is correct or not" error when I try to do that.
(24-05-2021, 04:26 PM)Ga Gu 2. The product value I get from fastboot mode has changed.
...
All other values I get from fastboot getvar all are identical, such as warranty, unlocked, secure, etc.
Does this mean the product value is in the flashinfo partition?
(25-05-2021, 11:12 AM)X3non no sure you can directly flash flashinfo using spft, you could try the write memory feature in spft or seeing as you still have bootloader unlocked, you can try fastbootTried, but it failed to flash flashinfo partition using SP Flash Tool's write memory feature.
(25-05-2021, 11:12 AM)X3non i doubt it does, but if you're able to flash it back then it'll help confirmI didn't manage to flash it back, but I inspected the data of the flashinfo partition.
you could also search the file if you'll find the product's value within