Originally Posted by deadman96385
How did you get a non-verfied IMG to boot? Couldn't get mine to allow anything and while messing with a072 firmware I seem to have broken my partition layout because I can't flash system, userdata, vendor anymore with edl userdata and vendor come after system. So I'm stuck on a non-verfied a072 system.
I can access recovery and EDL via DFU so i should be able to recover with a un-verified twrp or if there is a way to disable verity
I'll be honest, I've done nothing to mess with verity; the bootloader seems to support enforcing it but I don't see anywhere that actually sets partitions to require verification. I just modified the rawprogram0.xml to only feature the partitions and images I wanted to flash and used QFIL to flash them. It's been hit-or-miss, but for the most part if stuff won't boot it's because of errors with init or something else. The TWRP is basically just some recovery files from the R2 mashed into a working TWRP for the moto e5 Plus (same screen res, same 425 chipset for some models, seemed like a good choice). The A0722 is a different beast in the same body, with a beefier chipset and a larger eMMC, so it's not really surprising that things didn't go so well.
I did have an issue where some bad flashes left me unable to reflash stock system and vendor partitions the proper way, and they'd basically stop flashing after the first 2M of the image. If that's what's happening for you, you can go to Tools -> Partition manager in QFIL, find the partition you want to flash, right click -> manage partition data -> load image -> select the image you want to flash. It should work with the stock images but if it complains you may need to use simg2img or something similar to convert them to a plain ext4 image first. Honestly I'm still having issues reflashing those partitions 'normally' but the phone boots so I'm not really worried about it.
If you think your partition table is screwed up, you can try just flashing the gpt files first, commenting out or removing everything else in the XML. The flasher looks for offsets on the eMMC rather than the partition table, so it'll flash those where they're supposed to go and ignore everything else. Also, just comment out the userdata section of the rawprogram xml as it's basically designed to throw errors. It tries to flash a zero-byte image as sparse, which means it stops and complains about the headers being wrong. Even if you change the XML so that it's not read as sparse, flashing a null image would probably wipe the partition; a factory reset every flash isn't always useful.
If you want, I can upload the TWRP image and the QFIL settings I used to flash it, but it's largely untested; I know sideloading and flashing ZIPs works, but I've yet to try backing up or restoring partitions. It also hangs (at least in my case) for a minute at startup because it tries to decrypt the data partition without user input, so if there's anything set up it times out before letting the user do anything.
EDIT: Here's the TWRP image, with the XMLs for QFIL.
Again, not really tested, bad things bound to happen, I take no responsibility for bricked phones or lost data, etc., etc. Anyone looking to flash this had better back up whatever data they have.