can not flash - snapshotted state error


Aung Kyaw Minn

Members
Sep 22, 2021
3
3
When I tried to flash miui any rom to my redmi note10, it keep showing error (flashing of metadata is not allowed in snapshotted state).
How can I fix that? Do I need to change the state? How? Please help.
And my phone has no os installed, so I also tried to install recovery rom, usb debugging is off I think, I can't add my zip file to twrp also. I am lost.
 

Attachments

  • asd.png
    asd.png
    1.2 MB · Views: 58

xMarvin732

Members
Aug 10, 2019
199
52
When I tried to flash miui any rom to my redmi note10, it keep showing error (flashing of metadata is not allowed in snapshotted state).
How can I fix that? Do I need to change the state? How? Please help.
And my phone has no os installed, so I also tried to install recovery rom, usb debugging is off I think, I can't add my zip file to twrp also. I am lost.
I may have a solution to this.

"
regarding my error with "snapshotted state" while flashing with MiFlash.. I found the solution.

first, I tried to flash with "clean all and lock", but it showed the same error - this was not the way.
I researched a little further and found that the metadata partition is in a snapshotted state, which has something to do with the virtual a/b mechanism.
anyway, you can fix the snapshotted state by either merge or cancel the state.
for that you need the *latest* (Android 11) platform-tools with the latest fastboot.exe, because older version do not support this command.

then: fastboot.exe snapshot-update cancel
the snapshot gets cancelled and you can flash fastboot images of ROMs with MiFlash again normally.

more details and background info:"

Source:
 
  • Love
Reactions: Aung Kyaw Minn

Aung Kyaw Minn

Members
Sep 22, 2021
3
3
I may have a solution to this.

"
regarding my error with "snapshotted state" while flashing with MiFlash.. I found the solution.

first, I tried to flash with "clean all and lock", but it showed the same error - this was not the way.
I researched a little further and found that the metadata partition is in a snapshotted state, which has something to do with the virtual a/b mechanism.
anyway, you can fix the snapshotted state by either merge or cancel the state.
for that you need the *latest* (Android 11) platform-tools with the latest fastboot.exe, because older version do not support this command.

then: fastboot.exe snapshot-update cancel
the snapshot gets cancelled and you can flash fastboot images of ROMs with MiFlash again normally.

more details and background info:"

Source:
Thank you for your solution although changing snapshot state doesn't work somehow. But I am finally able to flash cusotm rom using ADB sideload. That saved my heart beat. I found that via your link. Thanks advance.