Yeah I did it through the Motorola website and unlock key. The stock ROMs I've flashed are called:
So you flashed stock android 10, then upgraded to stock 11 before flashing a custom rom, i.e. stock 10 >> stock 11 >> custom rom?Yeah I did it through the Motorola website and unlock key. The stock ROMs I've flashed are called:
Motorola Moto G Power_XT2041-3_SOFIAR_RETEU_10_QPE30.79-25_subsidy-DEFAULT_regulatory-DEFAULT_CFC_(MobileGuru4.com).zip
I only tried the Android 11 version recently. Most of the time I used the first one.
Some of the custom ROMs I've tried are:
CrDroid-v7.4-20210311-Sofiar-Vanilla.zip (also v7.2 before)
lineage-17.1-20210329-UNOFFICIAL-sofiar-images.zip (seemed to work but reboot mode set to fastboot)
And a few others. All taken from links in the Moto G Power forum.
I had to flash stock android 10 because I messed my phone up trying to install a custom ROM on the original out-of-the-box android. Many times after that I was trying to install custom ROM on the stock android 10 that I flashed. It kept failing to install system.img, things kept going wrong, and I kept reflashing android 10. Only recently did I think to try flashing a more updated version, but that didn't work either. I'm going to have another go now. This has taken up a lot of my weekends recently This is the "fastboot getvar all" from the flashed android 10. (On the android 11 ROM the version-bootloader is: MBM-3.0-sofiar_reteu-d09f15b89f-210331)So you flashed stock android 10, then upgraded to stock 11 before flashing a custom rom, i.e. stock 10 >> stock 11 >> custom rom?
Also, can you run fastboot getvar all and post its output?
Did you check https://android.stackexchange.com/q...tyle-due-to-pre-flash-validation-failed-error?
I saw the link where it said about trying to flash an earlier version but I don't think I was doing that most of the time. It just seems that for some reason it doesn't want to work. I've been trying again the past couple of days with various different ways and wipes and formats. I'm going to have a rest from it and just admit defeat for now and use the phone as it is. I might try again soon if I hit upon any brainwaves.Did you check https://android.stackexchange.com/q...tyle-due-to-pre-flash-validation-failed-error?
"In Moto devices, Preflash Validation Error means the factory image you are attempting to flash is older than the one you have currently installed and Moto devices do not support downgrading of the bootloader or partition table (gpt.bin) regardless if the bootloader is locked or unlocked.
There is also a second issue here with the system sparsechunks failing, but that is more related to having other "stuff" in the system folder that is remaining from other ROMs or flashed patches, typically a format (different from a wipe) of /system and /data in TWRP before starting the flash process clears this up.
You are also not beginning or ending your flash process correctly for the image you are using...You should begin with "fastboot oem fb_mode_set" and end with "fastboot oem fb_mode_clear" prior to the reboot, more on this in a second..."
So, suggest you try the following from bootloader:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot bootloader
Hope that'll help.
When you press wipe in twrp, down the bottom is a button 'format data', tap that, type yes and enter.Hi Beetle. I always swipe to the right to wipe the cache etc. And after flashing I swipe to wipe the dalvik. But I'm never given the option to type yes. I'm not sure what you mean.
I've spent a lot of time wondering why TWRP never reboots when I try to reboot into recovery after flashing a zip. I just realised (after reading the instructions for flashing ArrowOS on this forum) that I can flash TWRP to partition b as well by using the commands:
fastboot flash recovery twrp.img
fastboot flash recovery_b twrp.img
By doing that I was able to (or so I thought) install the zip to the inactive slot b, and then reboot to recovery using TWRP, and it comes back as having the active slot b. I got excited but when I went to reboot system the same thing happened. Just some sort of bootloop thing. Nothing seems to work. I've tried OmniROM and Stag zips as well.