• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

My phone won't boot properly after I try to install a custom ROM

Search This thread

lazzr

Member
May 3, 2021
17
0
Did you unlock the bootloader with the unlock key from Motorola? Which version of stock and custom ROMs did you flash? Are you sure you flashed the right custom image?

Also, please check this out.
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
XT2041-3_SOFIAR_RETEU_11_RPES31.Q4U-47-35-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.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)
StagOS-sofiar-FastbootD-fixed.zip
And a few others. All taken from links in the Moto G Power forum.
 

tinbilly

Member
Dec 23, 2017
42
10
BlackBerry KEYone
Moto G Power
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
XT2041-3_SOFIAR_RETEU_11_RPES31.Q4U-47-35-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.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)
StagOS-sofiar-FastbootD-fixed.zip
And a few others. All taken from links in the Moto G Power forum.
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?
 
Last edited:

lazzr

Member
May 3, 2021
17
0
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?
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)

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiar_reteu-e711989-191226
(bootloader) product: sofiar
(bootloader) board: sofiar
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805261312
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 08-16-2020
(bootloader) sku: XT2041-3
(bootloader) carrier_sku: XT2041-3
(bootloader) battery-voltage: 4215
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofiar_reteu/sofiar:10/QP
(bootloader) ro.build.fingerprint[1]: E30.79-25/59f4f:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_03.05.03.09R SOFIA_ROWDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Thu Dec 26 07:
(bootloader) kernel.version[3]: 47:50 CST 2019
(bootloader) git:xbl: MBM-3.0-sofiar_reteu-4d9fbfd-191226
(bootloader) git:xbl_config: MBM-3.0-sofiar_reteu-4d9fbfd-191226
(bootloader) git:rpm: MBM-3.0-sofiar_reteu-ffcccb0-191226
(bootloader) git:tz: MBM-3.0-sofiar_reteu-8ef3dba-191226
(bootloader) git:hyp: MBM-3.0-sofiar_reteu-8ef3dba-191226
(bootloader) git:devcfg: MBM-3.0-sofiar_reteu-8ef3dba-191226
(bootloader) git:cmnlib: MBM-3.0-sofiar_reteu-8ef3dba-191226
(bootloader) git:cmnlib64: MBM-3.0-sofiar_reteu-8ef3dba-191226
(bootloader) git:keymaster: MBM-3.0-sofiar_reteu-8ef3dba-191226
(bootloader) git:prov: MBM-3.0-sofiar_reteu-8ef3dba-191226
(bootloader) git:abl: MBM-3.0-sofiar_reteu-e711989-191226
(bootloader) git:qupfw: MBM-3.0-sofiar_reteu-f848623-191226
(bootloader) git:uefisecapp: MBM-3.0-sofiar_reteu-8ef3dba-191226
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
all: listed above
finished. total time: 0.064s
 

tinbilly

Member
Dec 23, 2017
42
10
BlackBerry KEYone
Moto G Power
Can you try fastboot oem get_unlock_data and post its output?

Also, do not go from Android 11 to Lineage 17.1 (lineage-17.1-20210329-UNOFFICIAL-sofiar-images.zip) which is based on Android 10. Such an downgrade might be an issue. Let just stick with Android 10.

Can you flash the stock Android 10 XT2041-3_SOFIAR_RETEU_10_QPES30.79-124-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip >> reboot the system (remember to ignore the Android 11 upgrade notification) >> wipe the phone using System > Advanced > Reset >> set up your device (again, ignore the Android 11 upgrade notification)? Then see and report what happens.
 
Last edited:

sd_shadow

Recognized Contributor
Sep 21, 2011
17,872
1
8,434
South Dakota
goo.gl
Motorola Droid X
Moto X4
Sorry I couldn't post it to take up less space and without smiley faces inserted in the middle of it.
Use the Insert Code option
Screenshot 2021-05-16 085332.png
 

lazzr

Member
May 3, 2021
17
0
This is definitely not an issue with the bootloader not unlocking properly. I sorted that out with no issues weeks ago. I've installed the Android 10 ROM you linked to and followed your reset instructions, but the same issues are occurring. For some reason now though, when I go to flash system it only says 1/2, instead of before when it failed at the 3/3 stage. These are the two main messages I've had below. I get the Preflash validation failed now while flashing Lineage also. I understood from the link you sent previously that that could happen while going from Android 11 to 10, but I am on 10 now and most of the time I've tried has been while on 10.

writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)

writing 'system_a' 3/3...
FAILED (remote: Operation not permitted)

My phone just doesn't seem to want to do it
 

tinbilly

Member
Dec 23, 2017
42
10
BlackBerry KEYone
Moto G Power
Did you unlock the bootloader with the unlock key from Motorola? Which version of stock and custom ROMs did you flash? Are you sure you flashed the right custom image?

Also, please check this out.
Did you check https://android.stackexchange.com/q...tyle-due-to-pre-flash-validation-failed-error?

I quote
"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
fastboot reboot

Hope that'll help.
 

lazzr

Member
May 3, 2021
17
0
Did you check https://android.stackexchange.com/q...tyle-due-to-pre-flash-validation-failed-error?

I quote
"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
fastboot reboot

Hope that'll help.
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.

Thanks very much for your help and time. It's much appreciated. I'll post again if I ever solve it and have anything that might help others with a similar problem.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Here is my suggestions:

    1. Hard reset your device following this or this. They are basically the same instruction. Hopefully this will get your phone back to the stock rom. If not, then just try step 2 below.

    2. Install the xt2041-3 stock rom on your device by following the instructions in the download link. Or you could try this method.

    3. Once you are back to stock rom, you can install any custom rom via fastboot mode.

    Hope that will help.
    1
    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.
    When you press wipe in twrp, down the bottom is a button 'format data', tap that, type yes and enter.

    Then reboot.
    1
    Mine is a XT2041-1. What I did:

    1. flashed back to stock ROM 10_QPE30.69-16
    2. rebooted the phone, then set it up (I did not upgrade to Android 11 as notified by the system)
    3. wiped the phone using System > Advanced > Reset (just to be safe)
    4. flashed to crDroid 7.4 (Android11-based)

    You said you failed to load the custom ROM's system.img. What is the exact error message? Please attach some screenshots as well.