Question Bootloop after Custom ROM / Rescue & Smart Assistant Moto G Stylus 5g 2022 (milanf XT2215-4)

Search This thread


New member
Jun 7, 2023
I have a Moto G Stylus 5g 2022 (milanf XT2215-4) [MetroPCS / T-Mobile] that recently bootlooped after flashing Arrow OS Android 13 from A-Team and reverting back to stock.

I've downloaded the recent version from their Telegram group and followed their instructions.
I managed to get the Custom Rom to boot although I had no wifi connection, so I decided to revert back to stock ROM using Rescue & Smart Assistant.
Although big mistake because now the Stock OS does not even boot and I'm stuck with a bootloop nor can I install the Custom ROM !

I can access Fastboot & Recovery, although sometimes it reverts back to TWRP that i flashed in order to achieve the custom ROM. The bootloader is unlocked and rooted.

Any answers? I've tried everything and even attempted to use moto's old RSD Lite tool / manually flash the stock rom.
Last edited:


New member
Jun 7, 2023
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-1887fb15044-230427
(bootloader) product: milanf
(bootloader) board: milanf
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB MICRON MT128GAXAU2U227X FV=0107 WB=2048
(bootloader) ram: 6GB MICRON LP4x DIE=16Gb M5-M8=FF 07 00 10
(bootloader) cpu: SM_STRAIT 1.0
(bootloader) serialno: ZY22GR3NSK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x85
(bootloader) uid: FB6D3EB4
(bootloader) token: inactive
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-14-2023
(bootloader) sku: XT2215-4
(bootloader) carrier_sku: XT2215-4
(bootloader) battid: SB18D33989
(bootloader) battery-voltage: 3807
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: tmo
(bootloader)[0]: Must use __system_property_read_ca
(bootloader)[1]: llback() to read
(bootloader) LA.UM.9.16.r1-09800-MANNAR.QSSI12.0
(bootloader) version-baseband[0]: M6375_HI434_12. MILANF_PV
(bootloader) version-baseband[1]: T_NA_CUST
(bootloader) kernel.version[0]: Linux version 5.4.197-PizzaG_x64-g45fbe4
(bootloader) kernel.version[1]: bf439e-dirty (nobody@android-build) (And
(bootloader) kernel.version[2]: roid (6443078 based on r383902) clang ve
(bootloader) kernel.version[3]: rsion 11.0.1 (https://android.googlesour
(bootloader) kernel.version[4]: b397f81060
(bootloader) kernel.version[5]: ce6d701042b782172ed13bee898b79), GNU ld
(bootloader) kernel.version[6]: (binutils-2.27-bd24d23f)
(bootloader) kernel.version[7]: ) #1 SMP PREEMPT Wed Apr 26 21:26:58 CDT
(bootloader) kernel.version[8]: 2023
(bootloader) git:xbl: MBM-3.0-uefi-37c4c3a68-230427
(bootloader) git:xbl_config: MBM-3.0-uefi-37c4c3a68-230427
(bootloader) git:abl: MBM-3.0-uefi-1887fb15044-230427
(bootloader) git:rpm: MBM-3.0-uefi-d808fb4-dirty-230427
(bootloader) git:tz: MBM-3.0-uefi-2b95735f-230427
(bootloader) git:hyp: MBM-3.0-uefi-2b95735f-230427
(bootloader) git:devcfg: MBM-3.0-uefi-2b95735f-230427
(bootloader) git:keymaster: MBM-3.0-uefi-7ec6b152-230427
(bootloader) git:storsec: MBM-3.0-uefi-7ec6b152-230427
(bootloader) git:uefisecapp: MBM-3.0-uefi-7ec6b152-230427
(bootloader) git: qrov: MBM-3.0-uefi-2b95735f-230427
(bootloader) git:qupfw: MBM-3.0-uefi-86fe38d-230427
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D38304
(bootloader) snapshot-update-status: none
(bootloader) primary-display: csot_nt36672e_1080x2460_120_vid
(bootloader) secondary-display:
(bootloader) fdr-allowed: yes
all: listed above
finished. total time: 0.423s


Senior Member
Feb 24, 2011
fastboot says you have a custom kernel installed, did you receive errors when reverting to stock? At what point in bootup is it restarting?


New member
Jun 7, 2023
No i haven't retrieved any errors when flashing to stock using Rescue & Smart Assistant / TinyFastboot . Although still receiving boot loop.
Last edited: