Yes, I don't know why either, but it worksIt doesn't do anything different with since partitions like metadata should be also on /dev/block/by-name
Yes, I don't know why either, but it worksIt doesn't do anything different with since partitions like metadata should be also on /dev/block/by-name
I tested what you said with my testers, nothing different as expected
Very strange. Using your TWRP image it is not possible to decrypt on my Poco M3 with the latest EEA stable ROM. With just the modification I said, TWRP asks for the password and decrypts it correctly.I tested what you said with my testers, nothing different as expected
It works with the twrp img u shared?Very strange. Using your TWRP image it is not possible to decrypt on my Poco M3 with the latest EEA stable ROM. With just the modification I said, TWRP asks for the password and decrypts it correctly.
As TheMalachite seems to be offline for a while and to help those who want to make backups properly to modify their devices, I will attach the TWRP image with the fix in fstab
help me please. in my twrp, i don't have system in wipe. so how can i flash rom lineageos for my poco m3
This is not something easy to do (at least I don't know how, but if someone could help me, that would be great!).you can't flash system + vendor + product because these partitions are read-only. create your own super.img with lpmake
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
- fastboot --disable-verity --disable-verification flash vbmeta vbmetaname.img
- fastboot flash recovery recoveryname.img