Device is corrupt

[aibd]

It is rather frustrating the way the forum shuts down new users, especially when there is a difficulty to solve like this.

@emmesse

I then formatted the two partitions (user and system) and it is why it no longer works.

Yes I wondered about this. How do you do this format? Was it an easy to access option in the e-Recovery?

I do not know for certain if this is a Dynamic Partition device (I had one once) but I think it is from the things you have reported so far. This can lead to unexpected behaviour, loosely speaking, when the partitions (especially system) are disturbed.

You can read more about the concept in the link, but I certainly don’t recommend messing with it without advice from someone who knows the phone.

You probably realised that fastboot flashing get_unlock_ability = 0 means that the phone is not going to unlock with Fastboot commands.

• A clue to whether Murena One is a super partition device if the menu mentioned in Post #8 contains a switch to fastbootd. Fastbootd is specific to Super partition devices.

I think that the solution will involve reimaging the phone at a deeper level than the regular Android Debug Bridge … or possibly, late edit, there is a chance that fastbootd commands might be able to replace system if the phone supports it.

[emmesse]

Was it an easy to access option in the e-Recovery?

yes it was

I’ve contacted MURENA to explain the problem and see if they’ll fix it. I’m waiting two days for a reply if they can do it.

[emmesse]

If not, is there anything else we could do?