Database Develop

MODS PLease delete

MODS PLEASE DELETE , cant find solution , thanks anyway
Im a dare to start my own thread to see if i can solve my problem, anyway, i own a xt1063 in wich i unlocked the bootloader in order to install lollipop and root, i have done this in the past with 3 xt1064's with no problem, however im facing a weird problem this time. So after i installed lollipop rom RETUGLB_XT1063_5.0.2_LXB22.46-28_cid9_CFC.xml via fasboot,everything went smooth as always, the phone boots up but after the world and blue m animation the phone goes into a blank (or black) screen and stays there and it goes no further than that, ive waited 20 plus minutes and nothing happens,i know the phone is on because i can see the screen its a bit bright but black, so i went to the original recovery and did a factory reset wich went nice, reboot and same result, so i instaled twrp via the Moto-G-2014-ToolKit-stable i found here, and booted the twrp recovery, wiped davilk cache,cache and after rebooting i got the same result. One thing i notice is, if i want to erase cache via stock recovery, the phone reboots inmediatly as if something went wrong, i twrp i get an error, trying to install the titan rom [ROM][5.0.2][titan][XT1063/64]The Titan Prime ROM[FEB 1](Version 1.1.2 RC) gives me a bunch of errors and nothing happens. Other thing i notice is that if i boot in twrp and mount the usb storage, i get terrible transfer rate speed, also if i copy something,lets say a rom, i can install such rom but once i restart and boot into twrp and mount the usb again, is like nothing was transfered, thres no rom in there, like if it wipes it self . Dont know what ealse to do, wonder if the cache partition its corrupted and dosnt let the phone fully start. Thanks for any help provided, and pardon my bad grammar, english its my second lenguage...
edited to add more details:
Everytime i try to lock the bootloader i get diferent mesages, but it nevers locks the bootloader.
or if i run the boot logo fix, the tool succesfully does the job as i can tell in the command window, but when i reboot i still get the warning logo as if nothing happened.
Click to expand...
Click to collapse

anyone please? im running out of ideas, thanks.

update 2 just in case someone wants to help, i instaled kk 4.4.4 with titan flasher, then instaled twrp, tried to instal any rom in twrp gets stuck in format system partition....

Have you tried to flash any stock firmware with fastboot?

dpdp73 said:
Have you tried to flash any stock firmware with fastboot?
Click to expand...
Click to collapse
Yes, kk 4.4.4 or lollipop 5.0.2 , no go , both gave the same result.

I wonder if theres a way to install a rom,at the same time wipe all the estructure inside the phone, can that be achieved via adb perhaps? as fastboot seems a bit limited. anyway heres a video that shows how the phone boots to a blank screen on a clean fasboot instaled 5.0.2 stock rom www.youtube.com/watch?v=D8CgqNOp-_g
and this is what happens if i try to clean cache with recovery
www.youtube.com/watch?v=oBivRORNH1I

Try things like "fastboot erase cache", "fastboot erase data(/system etc.)".
But it doesn't look good.

dpdp73 said:
Try things like "fastboot erase cache", "fastboot erase data(/system etc.)".
But it doesn't look good.
Click to expand...
Click to collapse
tried too,was a no go.... dont no what ealse to try, i pretty much done everything

another update while someone steps up and helps.
My phone looks like its write protected, but i can install any recovery i want and boot it. so if i install twrp i can boot to it, if i mount the usb system i can copy files to it, but as soon as i reboot, the files get deleted by magic... so next thing i tried, install stock kk 4 or lollipop via stock recover and sideload adb, i get a fingerprint error message, package expects build fingerprint of motorola/titan_retuglb/titan_umts:4.4.4/KXB/21.85-17/14:user/release , but after that i flashed KK rom via fastboot, all goes well , so i reboot and start recovery and tried to install lollipop via adb side load and i get a fingerprint message again, and dont mater how many roms i flash via fasboot and they look like they installed ok, if i restart stock recovery and try to update with any rom , i get this message,
package expects build fingerprint of motorola/titan_retuglb/titan_umts:4.4.4/KXB/21.85-17/14:user/release-keys or motorola/titan_retuglb/titan_umts:5.0/LXB22.39-6/6:user/release-keys; this device has motorola/titan_retuglb/titan_umts:4.4.4/KXB23/25:u
instalation aborted.
even after flashing lollipop, system says device has KK ,wich lead me to think its been wirte protected.
will keep looking and hope for some smart help, thanks.

please help anyone
Code:
C:\mfastboot-v2>fastboot getvar all > command.txt
(bootloader) version: 0.5
(bootloader) version-bootloader: 4807(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D3239LM
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: D59CBB060F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359297052588158
(bootloader) meid:
(bootloader) date: 10-23-2014
(bootloader) sku: XT1063
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Dec 2 3:44:40 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retuglb/titan_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.85-23/21:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.23.titan_retug
(bootloader) ro.build.version.full[1]: lb.retuglb.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g668a77b ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 26 20:21:50 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V48.07-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.07-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V48.07-0-g71b1aae-dirty
(bootloader) tz.git: git=MBM-NG-V48.07-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V48.07-0-ge875a20
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D3239LM
(bootloader) sutinfo:
all: listed above
finished. total time: 0.088s

I have the exact same problem

xGiorgos said:
I have the exact same problem
Click to expand...
Click to collapse
come here and fight with us http://forum.xda-developers.com/moto-g-2014/help/phone-write-protected-freezed-t3030812

Motorola Moto G (XT1068) - Softbricked?

Hi.
I have black screen after motorola moto g animation (I can see some light, but blank screen).
I can enter on fastboot mode and have the bootloader unlocked. . I tried to reflash the firmware but i have still the same error.
I tried to downgrade from 5.0.2 to 4.4.4 but I can't do it, it displays this error:
"C:\A>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.160s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.472s"
I tried a lot of procedures searching my problem in google, but noone works.
Maybe is a wrong firmware image? can you help me with the correct image or solving the issue?
I'm desperate and need a solution, here you can see some information:
"C:\A>mfastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4882(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D22PPCL
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: C26F6D070F000000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 12-13-2014
(bootloader) sku: XT1068
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jul 14 15:45:22 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.46-28/28:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.28.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:38:33 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.82-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.82-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.82-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.82-0-g72f9f12
(bootloader) aboot.git: git=MBM-NG-V48.82-0-ge004609
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D22PPCL
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.101s"
Very thanks guys. :crying:

If you are trying to downgrade from 5.x/6.x to 4.4, remember you do not flash .mbn file. Flashing .mbn will attempt to downgrade your bootloader and might corrupt it, as bootloader downgrade is not supported/advised. I suggest you flash 5.x stock firmware WITH .mbn file and this should solve your problem.
Try firmware from this thread:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-original-motorola-t3155774

just try to flash a recovery like twrp then install cm like rom first

pank.dhnd said:
If you are trying to downgrade from 5.x/6.x to 4.4, remember you do not flash .mbn file. Flashing .mbn will attempt to downgrade your bootloader and might corrupt it, as bootloader downgrade is not supported/advised. I suggest you flash 5.x stock firmware WITH .mbn file and this should solve your problem.
Try firmware from this thread:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-original-motorola-t3155774
Click to expand...
Click to collapse
What image should I use for XT1068 Europe Dual Sim ??? in relation with the fastboot vars?

When i Install twrp it won't display errors, but when i access to recovery it access to the stock recovery :/
If I manually boot from twrp whitout flashing it, i get stuck on "teamwin" logo.
vaisakmct said:
just try to flash a recovery like twrp then install cm like rom first
Click to expand...
Click to collapse

lsard said:
When i Install twrp it won't display errors, but when i access to recovery it access to the stock recovery :/
If I manually boot from twrp whitout flashing it, i get stuck on "teamwin" logo.
Click to expand...
Click to collapse
That's what I am saying, flash stock Lollipop, it will restore your bootloader and recovery (if any changes were made during downgrade), and then flash recovery.
---------- Post added at 05:46 AM ---------- Previous post was at 05:37 AM ----------
lsard said:
What image should I use for XT1068 Europe Dual Sim ??? in relation with the fastboot vars?
Click to expand...
Click to collapse
Ohh, for Europe dual sim, you can use image from below thread:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
The thread I posted earlier has Indian images mostly, but it won't make much difference.

pank.dhnd said:
That's what I am saying, flash stock Lollipop, it will restore your bootloader and recovery (if any changes were made during downgrade), and then flash recovery.
---------- Post added at 05:46 AM ---------- Previous post was at 05:37 AM ----------
Ohh, for Europe dual sim, you can use image from below thread:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
The thread I posted earlier has Indian images mostly, but it won't make much difference.
Click to expand...
Click to collapse
Still the same error, blank screen after motorola animation, reflashing this firmware -> ***NEW*** DOWNLOAD XT1068 5.0.2 LXB22.99-16.3 RETDSDS WITH STAGE FRIGHT FIX RETAIL DUAL SIM DUAL STANDBY (EU/INDIAN/GLOBAL) 26/08/2015 BUILD ***NEW***

Nobody can help me?
Do you think my phone is not recoverable?
:crying:

lsard said:
Nobody can help me?
Do you think my phone is not recoverable?
:crying:
Click to expand...
Click to collapse
Did u try any custom ROM?
And don't worry, your phone boots perfectly that means no issue with it.

pank.dhnd said:
Did u try any custom ROM?
And don't worry, your phone boots perfectly that means no issue with it.
Click to expand...
Click to collapse
I can't install any ROM, I tried to install cm rom by adb but it fails at the installation process. Can't install neither any recovery.
I think is a blocked partition or something like this.

Please help me solving this.... nobody know why I can't install any rom/recovery?

lsard said:
Please help me solving this.... nobody know why I can't install any rom/recovery?
Click to expand...
Click to collapse
You can try to boot into twrp, you have to use the 2.8.5.0 version, newer ones will fail.
Sent from my Moto G 2014 using XDA Free mobile app

Wolfcity said:
You can try to boot into twrp, you have to use the 2.8.5.0 version, newer ones will fail.
Sent from my Moto G 2014 using XDA Free mobile app
Click to expand...
Click to collapse
Hi Wolfcity, thanks for your support.
I installed twrp 2.8.5.0 version as you told me. I'm still with the same problem. When I installer the twrp recovery it will boot from stock recovery. If I manually boot from trwp it will stuck on the Teawin logo.
I installed this iso -> https://dl.twrp.me/titan/twrp-2.8.5.0-titan.img
I'm desperate

You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks

GhettoButta said:
You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks
Click to expand...
Click to collapse
I tried various processes searching by google, but the last i think was following this thread:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
Thanks you so much, I can post you all the fastboot vars if you need.

You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks
EDIT: Also list your previous motoboot.img version you used for the flashing process.
Tell me your carrier?

http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
go here may be this post will help you for your issue .

GhettoButta said:
You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks
EDIT: Also list your previous motoboot.img version you used for the flashing process.
Tell me your carrier?
Click to expand...
Click to collapse
I tried so many proceduress..
I used this posts:
- http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
- http://forum.xda-developers.com/moto-g-2014/development/rom-stock-lollipop-rom-t3024800
- http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Maybe is not the order... i tried like 4 or 5 reflash to stock but nothing changes, i'm getting the exact same error.
Thanks

Can't believe it can't be solved!!
I have a great commitment with this smartphone

go to service center dont mention about ur bootloader unlocked just told them u face this screen at the time of update .dont touch anything else just submit your handset

Baseband not found after bootloader unlock and clean flash stock ROM.

Hi, This is my first post on XDA and I'm seeking help to solve a problem with my device.
I Have a brazillian moto g6 (with dual SIM support) that was having the random glitch and lags problem that some G6's had after the OTA update to Pie. A friend of mine bought the same device and was having the same issue after the OTA update, the phone was barely usable. After reading online, I decided to do a clean flash of the stock brazillian ROM because I saw people talking that this would solve the problem. I Have some experience in flashing ROMs, unlocking bootloaders, installing recoveries, kernels, etc (In my pixel phone, and before in a moto g5 plus), so I imagine it would be pretty easy.
I Started trying to flash via RSD Lite but for some reason the program didn't recognize the device. I even intalled Windows 7 to see if it was any compatibility issue. RSD could recognize with no problem my old moto G1, but the G6 not. I was using motorola's original USB cable.
So I resolved to flash via fastboot, using a bunch of commands I saw in a XDA post saying that the commands were essentially the same from the Oreo stock flash post. Before that, I unlocked the bootloader in Motorola's official site to be able to install TWRP in case anything gone wrong.
After flashing the stock rom, everything was fine and the lags stopped, but the phone didn't recognize the SIM Card. So I decided to reflash the stock ROM using a python script to convert the XML to fastboot commands, in case any command was missing. The same problem insisted, the phone does not see the SIM card. I tried a bunch of things like flashing oreo modem, US ROM, etc, but there's no way that the phone recognize the SIM card.
In fastboot the phone exibits "Baseband: not found" so I Believe that somehow in the process I bricked the phone. Anyone has a clue on how to solve that? Is it possible to reconstruct the baseband without a Box?
Anyone know why RSD didn't recognize the phone? Could it be a failure in the first flashing proccess? (All comands were essentially the same, except that some .sparcechunks were missing, but the modem stuff was equal).
Since now, I apologize for some bad english and I would really appreciateif someone could give me help.
Thanks in advance.
______________
Build Info from the ROM, downloaded from stockrom.net:
BUILD REQUEST INFO:
SW Version: ali-user 9 PPS29.55-24 a37fd release-keysM450_08.14.10.75R
MBM Version: MBM-2.1-ali_retail-60d7a9f-dirty-190126
Modem Version: M450_08.14.10.75R
FSG Version: FSG-8953-16.114
Build Fingerprint: motorola/ali/ali:9/PPS29.55-24/a37fd:user/release-keys
CQATest App Version: 6.0.4
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 29.11.26.ali.retail.en.US
Model Number: moto g(6)
Android Version: 9
Baseband Version: M450_08.14.10.75R
Build Id: PPS29.55-24
SW Display Build ID: PPS29.55-24
Build Date: Sat Jan 26 02:24:55 CST 2019
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.29.11.26.ali.retail.en.US
Version when read from CPV: ali-user 9 PPS29.55-24 a37fd release-keys
AB Update Enabled: False
Full Treble Enabled: True

Your firmware is neither the latest nor the brazilian one. To get back your baseband try the steps below.
Download and flash the latest firmware for brazilian software channel from here:
https://mirrors.lolinet.com/firmware/moto/ali/official/RETBR/XT1925-3_ALI_RETBR_9.0_PPSS29.55-37-4-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Use ONLY these commands to flash the firmware:
(the commands are extracted from the flashfile.xml inside the firmware.zip)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot

It appears Motorola has recommended to some users of G6 with Pie problems something called the "Lenovo Moto Smart Assistant", which is software they offer to do a "rescue" of any Motorola phone. It runs on Windows 7 and 10, and automatically downloads the correct stock firmware for the phone. It might be worth a try.
https://support.lenovo.com/us/en/downloads/ds101291

I really appreciate WoKoschekk and Peabody424 for taking their time trying to help me. Looking into the build info from the ROM WoKoschekk provided me, I can see that the modem version is different, so this might solve the problem. Is very possible then that stockrom.net site is putting the incorrect ROM in the RETBR release channel. I honestly know very few about baseband and modem.
As soon I have some free time I will test both sugestions from you, but I wanted to thank the replies in advance and not leave the post without response.
In 2 or 3 days I will try to flash the ROM and update with a feedback.

Solved
well, I flashed the firmware WoKoschekk provided and the problem was solved. Kinda embarassing to flash the wrong firmware but let IT stay as advice for people who download from Stockrom.net, the might provide some wrong files.
Really thanks for the help.

WoKoschekk said:
Your firmware is neither the latest nor the brazilian one. To get back your baseband try the steps below.
Download and flash the latest firmware for brazilian software channel from here:
https://mirrors.lolinet.com/firmware/moto/ali/official/RETBR/XT1925-3_ALI_RETBR_9.0_PPSS29.55-37-4-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Use ONLY these commands to flash the firmware:
(the commands are extracted from the flashfile.xml inside the firmware.zip)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Does this work with Europian (xt1925-5) variant? I tried to flash multiple stock oreos and followed steps in faster root guide, but somehow I managed to get unknown baseband.
Edit: I was downgrading my system, September Pie build works fine, but no LDAC. I know it is a bit off-topic, but is downgrading possible with another kernel or something else?

spidereye10 said:
Does this work with Europian (xt1925-5) variant? I tried to flash multiple stock oreos and followed steps in faster root guide, but somehow I managed to get unknown baseband.
Edit: I was downgrading my system, September Pie build works fine, but no LDAC. I know it is a bit off-topic, but is downgrading possible with another kernel or something else?
Click to expand...
Click to collapse
AFAIK downgrading from Pie to Oreo won't work without loosing wifi & mobile network.

Any way to work on locked devices? Since i cant boot, i cant "Allow Oem" and first two commands arent working here =(

neonoafs said:
Any way to work on locked devices? Since i cant boot, i cant "Allow Oem" and first two commands arent working here =(
Click to expand...
Click to collapse
Use RSD Lite if you can find a PC that it works with
Like XP with Usb 2 ports not usb 3
Sent from my mata using XDA Labs
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
Also make sure you have the correct firmware software channel
See my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs

I have the same problem, my moto e5 play XT1920-18 Pettyl, Retar updated itself and suddenly it showed the mmotorola logo and turned off, I flashed it with the latest version of the rom belonging to my mobile uploaded to the page https: // mirrors.lolinet.com/firmware/moto/pettyl/official/
And the mobile continues with the loop that turns on it shows the logo and turns off, oh and in fastboot Mode it shows that the Base Band not found If you could give me a solution I would appreciate it

.

WoKoschekk said:
Your firmware is neither the latest nor the brazilian one. To get back your baseband try the steps below.
Download and flash the latest firmware for brazilian software channel from here:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Use ONLY these commands to flash the firmware:
(the commands are extracted from the flashfile.xml inside the firmware.zip)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
I have the same problem on xt1926-8, could you help me??????

NoxiusBR said:
I have the same problem on xt1926-8, could you help me??????
Click to expand...
Click to collapse
Still need help? What's exactly the problem?

WoKoschekk said:
Still need help? What's exactly the problem?
Click to expand...
Click to collapse
baseband not found. so i can't downgrade because i need to be connected to wifi or operator to unlock the OEM

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-evert_retail-83f0397e7a-200825
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: Brazil
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 0049678880
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 144BA7BD
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351880098469554
(bootloader) meid:
(bootloader) date: 08-11-2018
(bootloader) sku: XT1926-8
(bootloader) carrier_sku: XT1926-8
(bootloader) battid: SB18C20874
(bootloader) battery-voltage: 3357
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/evert_nt/evert_nt:9/PPW29
(bootloader) ro.build.fingerprint[1]: .116-16-29/2b1529:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.18.evert.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gc476b56b6556
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.
(bootloader) kernel.version[2]: x 20150123 (prerelease) (GCC) ) #1 SMP P
(bootloader) kernel.version[3]: REEMPT Tue Aug 25 03:56:27 CDT 2020
(bootloader) git:abl: MBM-3.0-evert_retail-83f0397e7a-200825
(bootloader) git:xbl: MBM-3.0-evert_retail-4149b81ab-200825
(bootloader) gitmic: MBM-3.0-evert_retail-4149b81ab-200825
(bootloader) git:rpm: MBM-3.0-evert_retail-cf74f0b-200825
(bootloader) git:tz: MBM-3.0-evert_retail-3416ac0e4-200825
(bootloader) git:hyp: MBM-3.0-evert_retail-3416ac0e4-200825
(bootloader) git:devcfg: MBM-3.0-evert_retail-3416ac0e4-200825
(bootloader) git:cmnlib: MBM-3.0-evert_retail-3416ac0e4-200825
(bootloader) git:cmnlib64: MBM-3.0-evert_retail-3416ac0e4-200825
(bootloader) git:keymaster: MBM-3.0-evert_retail-3416ac0e4-200825
(bootloader) gitrov: MBM-3.0-evert_retail-3416ac0e4-200825
(bootloader) git:storsec: MBM-3.0-evert_retail-3416ac0e4-200825
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(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

NoxiusBR said:
baseband not found
Click to expand...
Click to collapse
How did that happen?? Your bootloader wasn't unlocked until now and your firmware is untouched. So flashing a new firmware image won't get your baseband back because your device is already in OEM state. You can only try to boot your recovery and wipe /data (factory reset). Other solutions will require an unlocked bootloader.

WoKoschekk said:
How did that happen?? Your bootloader wasn't unlocked until now and your firmware is untouched. So flashing a new firmware image won't get your baseband back because your device is already in OEM state. You can only try to boot your recovery and wipe /data (factory reset). Other solutions will require an unlocked bootloader.
Click to expand...
Click to collapse
is there any way to unlock the OEM without wifi?

NoxiusBR said:
is there any way to unlock the OEM without wifi?
Click to expand...
Click to collapse
Your wifi should work anyway. The baseband version is not related to it.

But in general a RETBR firmware version needs a wifi or mobile connection to toggle on OEM unlocking.

WoKoschekk said:
But in general a RETBR firmware version needs a wifi or mobile connection to toggle on OEM unlocking.
Click to expand...
Click to collapse
is there any version that doesn't need wifi to unlock the OEM?

Fastboot - write protected

Today my cell phone got stuck on the android one logo.
I was using the cell phone when it suddenly fired, so I forced a restart with the power button and from that moment on it never turned on again.
I have the bootloader unlocked and I was running the Paranoid Quartz 4 rom about 3 months ago without any problem.
The first thing I did was try to enter recovery mode (twrp) and it was not possible. The only thing I can do with the cell phone is enter fastboot mode. So I decided to flash the stock rom using MiFlash (I tried with android 9 and android 10), but the error is always the same: "remote: Error flashing partition: Write Protected".
I have been trying to find a solution for several hours, I watched a lot of videos, I read a lot of threads, but there is no case: no solution has worked so far.
In the MiA2 forums the only thread I found is the following:
https://forum.xda-developers.com/mi-a2/help/help-xiaomi-mi-a2-write-protected-t4153629
I followed all the steps you left in the comments but nothing worked.
I wanted to know if this is happening to anyone else, and if anyone can try to help me fix it.
Thank you very much, I appreciate any kind of help.

try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?

KevMetal said:
try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?
Click to expand...
Click to collapse
Thanks for the reply.
This is the output when i put "fastboot getvar all"
(bootloader) crc:1
(bootloader) anti:1
(bootloader) token:/+VhxhMzqIjkRrCKNtCRXkCZccE=
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:10000
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4346
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xBB77F7E00
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-size:vendor_b: 0x80000000
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-size:vendor_a: 0x80000000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xC0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xC0000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x4000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x4000000
(bootloader) partition-type:minidump:raw
(bootloader) partition-size:minidump: 0x8000000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0xC000000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0xC000000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-typeersistbak:raw
(bootloader) partition-sizeersistbak: 0x2000000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x4000000
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-size:mdtp_b: 0x2000000
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-size:mdtp_a: 0x2000000
(bootloader) partition-type:bk1:raw
(bootloader) partition-size:bk1: 0x700000
(bootloader) partition-type:bluetooth_b:raw
(bootloader) partition-size:bluetooth_b: 0x100000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x1000000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x1000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x800000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x800000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x800000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x800000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b: 0x380000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a: 0x380000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:bluetooth_a:raw
(bootloader) partition-size:bluetooth_a: 0x100000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x100000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x100000
(bootloader) partition-type:mdtpsecapp_b:raw
(bootloader) partition-size:mdtpsecapp_b: 0x400000
(bootloader) partition-type:mdtpsecapp_a:raw
(bootloader) partition-size:mdtpsecapp_a: 0x400000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x400000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x400000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x100000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x100000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b: 0x100000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a: 0x100000
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-size:cmnlib64_b: 0x100000
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-size:cmnlib_b: 0x100000
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-size:cmnlib64_a: 0x100000
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-size:cmnlib_a: 0x100000
(bootloader) partition-typemic_b:raw
(bootloader) partition-sizemic_b: 0x80000
(bootloader) partition-typemic_a:raw
(bootloader) partition-sizemic_a: 0x80000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b: 0x80000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a: 0x80000
(bootloader) partition-type:rpm_b:raw
(bootloader) partition-size:rpm_b: 0x80000
(bootloader) partition-type:rpm_a:raw
(bootloader) partition-size:rpm_a: 0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-typeraw
(bootloader) partition-size 0x20000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x5000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x8000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x2000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:switch:raw
(bootloader) partition-size:switch: 0x2000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:ca5094d9
(bootloader) product:jasmine
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
finished. total time: 0.570s
Click to expand...
Click to collapse
And when I put fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
The problem is that I never thought to go back to the stock rom, I am trying to do it because my cell is dead. But the usb debugging was activated (I remember, whenever I connected the cell phone to the car, the notification would appear).
I already tried flashing the stock rom in EDL. I tried different versions but they all end in the same error. At this moment I am again downloading the last stable that they uploaded (V11.0.14.0.QDIMIXM) to try, but without hope hahaha
Finally, it doesn't let me enter TWRP, the only way is with a boot from fastboot (because flashing does not allow me, just like the roms). When I boot the twrp it starts up but gets stuck at the boot logo, it never enters recovery. And I don't know what you mean by "ARB triggered"
This MiA2 literally looks like a stone, I don't know what else to do. In a forum they told me that I have to have an "authorized EDL account" or contact one in order to unbrick the terminal.
Thanks again for the reply, I appreciate it.

ivan.lxc.10 said:
Thanks for the reply.
This is the output when i put "fastboot getvar all"
And when I put fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
The problem is that I never thought to go back to the stock rom, I am trying to do it because my cell is dead. But the usb debugging was activated (I remember, whenever I connected the cell phone to the car, the notification would appear).
I already tried flashing the stock rom in EDL. I tried different versions but they all end in the same error. At this moment I am again downloading the last stable that they uploaded (V11.0.14.0.QDIMIXM) to try, but without hope hahaha
Finally, it doesn't let me enter TWRP, the only way is with a boot from fastboot (because flashing does not allow me, just like the roms). When I boot the twrp it starts up but gets stuck at the boot logo, it never enters recovery. And I don't know what you mean by "ARB triggered"
This MiA2 literally looks like a stone, I don't know what else to do. In a forum they told me that I have to have an "authorized EDL account" or contact one in order to unbrick the terminal.
Thanks again for the reply, I appreciate it.
Click to expand...
Click to collapse
it will work by flashing the stock rom in edl
1. install Qualcomm 9008 drivers
2. run : fastboot oem edl
3.open miflash and refresh and flash rom
make sure you are using THE LATEST miflash ( use it to install drivers)
you can also try just changing to your other slot ...stock android 1 might still be there :
fastboot set_active b
or if you are b just put :
fastboot set_active a

KevMetal said:
it will work by flashing the stock rom in edl
1. install Qualcomm 9008 drivers
2. run : fastboot oem edl
3.open miflash and refresh and flash rom
make sure you are using THE LATEST miflash ( use it to install drivers)
you can also try just changing to your other slot ...stock android 1 might still be there :
fastboot set_active b
or if you are b just put :
fastboot set_active a
Click to expand...
Click to collapse
it didn't work. I'll leave you the log so you can see if you see something that I don't
"ACK count don't match!"
http://www.mediafire.com/file/z746700jxil5d6e/COM8%4020201019114123.txt/file (1st)
http://www.mediafire.com/file/5ba9u2yb0rnzqg9/COM8%402020101911540.txt/file (2nd)

ivan.lxc.10 said:
it didn't work. I'll leave you the log so you can see if you see something that I don't
"ACK count don't match!"
http://www.mediafire.com/file/z746700jxil5d6e/COM8%4020201019114123.txt/file (1st)
http://www.mediafire.com/file/5ba9u2yb0rnzqg9/COM8%402020101911540.txt/file (2nd)
Click to expand...
Click to collapse
I will take a look when i can
were you able to enter EDL correctly ?
did you try changing slots using the commands specified ?

KevMetal said:
I will take a look when i can
were you able to enter EDL correctly ?
did you try changing slots using the commands specified ?
Click to expand...
Click to collapse
Yes, every time I try to flash (so far without success) I try in fastboot mode and in EDL mode. Each mode has a different error: in fastboot mode the error is "remote: Error flashing partition: Write Protected". In EDL mode the error is: "ACK count don't match!".

ivan.lxc.10 said:
Yes, every time I try to flash (so far without success) I try in fastboot mode and in EDL mode. Each mode has a different error: in fastboot mode the error is "remote: Error flashing partition: Write Protected". In EDL mode the error is: "ACK count don't match!".
Click to expand...
Click to collapse
ACK count doesn't match error is because you didn't listen to me ..USE THE LATEST BETA MI FLASH ... uninstall old ones first ... send a photo to show you are using latest
---------- Post added at 11:47 PM ---------- Previous post was at 11:33 PM ----------
I looked at the logs.. you also seem to be using patched programmer files ..STOP ..use only the stock rom ..without copying or replacing files ...
send me a summary of exactly which version of miflash you are using ..which stock rom and explain what you are trying to do correctly

KevMetal said:
ACK count doesn't match error is because you didn't listen to me ..USE THE LATEST BETA MI FLASH ... uninstall old ones first ... send a photo to show you are using latest
---------- Post added at 11:47 PM ---------- Previous post was at 11:33 PM ----------
I looked at the logs.. you also seem to be using patched programmer files ..STOP ..use only the stock rom ..without copying or replacing files ...
send me a summary of exactly which version of miflash you are using ..which stock rom and explain what you are trying to do correctly
Click to expand...
Click to collapse
Sorry but you said to use the latest version of my flash .. not the BETA of my flash.
Anyway I just downloaded the beta version of miflash and it didn't work either, I'm starting to go crazy lol
What do you mean by "patched programmer files"? I am using the latest fastboot rom from 09/28/2020, I did not touch or replace anything (neither now nor in the previous times I tried to flash)
Now the step by step is as follows:
I am using the beta version of my flash that I downloaded from here https://drive.google.com/file/d/12Gy2RP1eWBBKS6R2S2G9qzt-UQRIxpAM/view
and the fastboot rom I downloaded it from here https://xiaomifirmwareupdater.com/archive/miui/jasmine/
(from the xiaomi page the links for the roms do not work)
So what I do is:
- Open cmd and MiFlash
- I put in MiFlash the option "clean all"
- I select the path where the rom is located (I have it in c: \ rom)
- fastboot oem edl
- refresh and flash in MiFlash

ivan.lxc.10 said:
Sorry but you said to use the latest version of my flash .. not the BETA of my flash.
Anyway I just downloaded the beta version of miflash and it didn't work either, I'm starting to go crazy lol
What do you mean by "patched programmer files"? I am using the latest fastboot rom from 09/28/2020, I did not touch or replace anything (neither now nor in the previous times I tried to flash)
Now the step by step is as follows:
I am using the beta version of my flash that I downloaded from here https://drive.google.com/file/d/12Gy2RP1eWBBKS6R2S2G9qzt-UQRIxpAM/view
and the fastboot rom I downloaded it from here https://xiaomifirmwareupdater.com/archive/miui/jasmine/
(from the xiaomi page the links for the roms do not work)
So what I do is:
- Open cmd and MiFlash
- I put in MiFlash the option "clean all"
- I select the path where the rom is located (I have it in c: \ rom)
- fastboot oem edl
- refresh and flash in MiFlash
Click to expand...
Click to collapse
well if that the case you need to consider a hardware failure...
please try the command to change slots and send me a photo of what is says in fastboot
also when you try to edl flash did you check that your phone appears as qualcomm 9008 device in device manager * just to make sure your 9008 drivers were installed correctly.
anyway try another thing .... download the fastboot version aosip-derp from their official page ...then flash all the image files one by one from fastboot ..but before starting first do :
fastboot -w
send me photo of what happens

KevMetal said:
well if that the case you need to consider a hardware failure...
please try the command to change slots and send me a photo of what is says in fastboot
also when you try to edl flash did you check that your phone appears as qualcomm 9008 device in device manager * just to make sure your 9008 drivers were installed correctly.
anyway try another thing .... download the fastboot version aosip-derp from their official page ...then flash all the image files one by one from fastboot ..but before starting first do :
fastboot -w
send me photo of what happens
Click to expand...
Click to collapse
I spoke with a person from the xiaomi forum and checking the log he told me that apparently the device has memory damaged, so it could not be solved with the firmware flashing. After that, he consulted another person and gave him the same diagnosis: the memory is damaged so it does not allow me to write in various sectors. So effectively, my problem is hardware.
I will send it to the technical service and then I will make an update on this thread to tell my experience.
Thank you very much for the answer, I appreciate it.

ivan.lxc.10 said:
I spoke with a person from the xiaomi forum and checking the log he told me that apparently the device has memory damaged, so it could not be solved with the firmware flashing. After that, he consulted another person and gave him the same diagnosis: the memory is damaged so it does not allow me to write in various sectors. So effectively, my problem is hardware.
I will send it to the technical service and then I will make an update on this thread to tell my experience.
Thank you very much for the answer, I appreciate it.
Click to expand...
Click to collapse
yeah hardware failure makes sense

KevMetal said:
yeah hardware failure makes sense
Click to expand...
Click to collapse
Hi there
having a similar issue with regards to flashing a rom over to an Asus Zenfone 5 ZC600KL X017DA has a Qualcomm Chipset 630
the issue i have is the phone is stuck on Asus logo and all i can get from the device using the power and volume Keys is CSC fastboot mode no recovery or anything
downloaded a couple firmwares details are
Asus_Zenfone_5_Lite_ZC600KL_630_14.0400_1808.057_20180903_CMD
And
[firmware27]CSC__ZC600KL(630)_14.0400.1801.006_20191023_Phone_PtoN
both firmwares in fastboot mode will fail and one thing to note is write protected keeps appearing and the interesting thing is the first firmware i listed seems to not do very much it will show several lines and then fail but the second firmware had more activity it seemed to be pushing something but then several points it kept saying write protected
i am to assume the device bootloader is locked
i keep seeing everywhere to try unlock bootloader i need to be able to disable the OEM within the phone settings ( obviously i cannot due to it not booting ) as well as debugging mode being enabled again i cant enable
i have a third firmware that is meant to be used with QPTS / Qfil and that throws up a couple of errors also
really could use some help with this it would be super appreciated and would owe an virtual beer haha
any solutions

nighthawk658 said:
Hi there
having a similar issue with regards to flashing a rom over to an Asus Zenfone 5 ZC600KL X017DA has a Qualcomm Chipset 630
the issue i have is the phone is stuck on Asus logo and all i can get from the device using the power and volume Keys is CSC fastboot mode no recovery or anything
downloaded a couple firmwares details are
Asus_Zenfone_5_Lite_ZC600KL_630_14.0400_1808.057_20180903_CMD
And
[firmware27]CSC__ZC600KL(630)_14.0400.1801.006_20191023_Phone_PtoN
both firmwares in fastboot mode will fail and one thing to note is write protected keeps appearing and the interesting thing is the first firmware i listed seems to not do very much it will show several lines and then fail but the second firmware had more activity it seemed to be pushing something but then several points it kept saying write protected
i am to assume the device bootloader is locked
i keep seeing everywhere to try unlock bootloader i need to be able to disable the OEM within the phone settings ( obviously i cannot due to it not booting ) as well as debugging mode being enabled again i cant enable
i have a third firmware that is meant to be used with QPTS / Qfil and that throws up a couple of errors also
really could use some help with this it would be super appreciated and would owe an virtual beer haha
any solutions
Click to expand...
Click to collapse
Good day, I would like to ask did you resolve the problem we have exactly same problem.

KevMetal said:
try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?
Click to expand...
Click to collapse
Bro i have the same problem with my redmi note 5 pro .one day it running smoothly but suddenly it stuck.when i restarted the device it stuck on logo. Recovery also got stucked.fastboot logo not showing only black screen but computer detected fastboot.i tried many things .but it says that the device is write protected

[ROM][11.0][UNOFFICIAL][Vanilla]LineageOS v18.1 Sofiar

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 18.1​
​
Links
ROM Download
LineageOS Website
Vache's TWRP Recovery
Magisk
FlameGApps
Installation
First Time Installation:
Reboot to recovery
Wipe data, cache, and dalvik if coming from another ROM
Flash ROM zip
(optional) Flash GApps (for vanilla builds)
(optional) Flash Magisk (root)
Format data
Reboot and voila!
Upgrading to a Newer Build:
Reboot to recovery
Flash ROM zip (The update downloaded by the ota updater will be located in /data/ota_package)
(optional) Flash Magisk (root)
Reboot and voila!
Source
LineageOS Source
Device Build Info
​Known Issues
• FM Radio doesn't work
• USB tethering doesn't work on first boot
• Must use android 10 vendor like other sofiar roms
• Android Auto doesn't work on android 10 vendor
• Stylus actions dies between reboots, just open it within settings
• OTA updater still isn't working properly
LineageOS, ROM for Rav/Sofia-R-P(commonly shortened to sofiar)
Devices: Sofiap (Moto G Stylus/G Pro), Sofia/Sofiar (Moto G Power/G⁸ Power), and Rav (Moto G⁸/G Fast)
Maintainer: ph4n70m
Build Type: Unofficial
Credits
- Vache: The initial device and vendor tree
- Beetle84: Giving me a ton of help

@ph4n70m-404 , is signature spoofing enabled for MicroG? Also is it patched for proper TTS functioning?
One more thing, can this be flashed on stock 11 base or like all the others on stock 10?

celrau said:
@ph4n70m-404 , is signature spoofing enabled for MicroG? Also is it patched for proper TTS functioning?
One more thing, can this be flashed on stock 11 base or like all the others on stock 10?
Click to expand...
Click to collapse
No mostly because on telegram there is already Lineage Foss builds (but i might make a magisk module to apply the patch), probably not because no one has brought that edit to my attention, no you must flash it ontop of android 10.

Fantastic thanks for the work on this!
Can confirm working on my moto g power (2020) with Magisk.
Some notes I took that might help others:
Spoiler: instructions
Note: I don't guarantee that my notes give the fastest or best way of installing this ROM! I'm just including these instructions because they detail one working way of doing this. Use at your own risk!
You have two ways to flash, using fastboot (where you need to download lineage-18.1-20211010-UNOFFICIAL-FASTBOOTD-sofiar.zip) or sideloading with TWRP (where you need to download lineage-18.1-20211010-UNOFFICIAL-sofiar.zip). Probably use the newest version (the datestamp in the filename should be the latest). I chose to sideload with TWRP. Since I also wanted magisk (root) I also ended up needing to download lineage-18.1-20211010-UNOFFICIAL-sofiar.zip anyway to flash boot.img, which it contains (see below).
The main instructions I used can be found here: https://wiki.lineageos.org/devices/channel/install
1 - I flashed the linked TWRP to temporary recovery by fastboot flashing to boot_a and boot_b. Upon reboot to recovery it would first reboot to android recovery (pic of dead droid with red exclamation point) and hang. I needed to press the power button until that screen disappeared. It would then reboot into TWRP.
2 - I sideloaded lineage-18.1-20211010-UNOFFICIAL-sofiar.zip using TWRP (Advanced->ADB Sideload) after reverting to factory (i.e. clearing data and cache)
3 - reboot into system and Lineage18.1 will load (first boot takes a while with the loading screen)
4 - I wanted magisk (follow the instructions at https://topjohnwu.github.io/Magisk/install.html) so I installed the Magisk apk and then used its app to flash the boot.img in lineage-18.1-20211010-UNOFFICIAL-FASTBOOTD-sofiar.zip, then transferred that back to my PC ('adb pull /sdcard/Download/magisk_patched_[random_strings].img')
5 - then 'adb reboot fastboot' will take you to fastbootd (this is different from fastboot, although you can probably also use fastboot) where you can run 'fastboot flash boot /path/to/magisk_patched.img'
6 - reboot and done
** In the process of figuring this out I got caught in some softlocks and bootloops. Just turn off the phone and turn it back on holding the down-volume with power to get into fastboot, then restart at step 1. I think this happens sometimes when A/B conflict arises, I'm not sure...
EDIT: @ehidle reminded me that there are some steps before flashing I didn't mention:
You need to first unlock your bootloader. Follow
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
(You'll need to create a Motorola account.)
You also need to have a stock ROM with Android 10 (not 11!). You can find instructions at this guide.
TLDR:
If you have the US version Moto G Power (2020) you can find them here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
If you have the G8 Power you can find them here: https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Addendum: Updating with new release
Just upgraded to the Nov 8th release from the October one. Worked seamlessly! A few notes:
1-You can find the updater at Settings->System->Advanced->Updater. Refresh and then click on the release you want to download. It will download and prepare the image.
2- Once it says it is done, you can reboot to TWRP (which for me isn't permanent so I had to reflash that into boot_a and boot_b as explained above in my first instructions) and "Install" the updated lineage image zip (i.e. flash the ROM) you downloaded. Note: I found the zip in /data/lineageos_updates not in /data/ota_package as indicated by @ph4n70m-404 in the original post.
3- Reboot and you're done. Everything will be saved as before except magisk root will be gone if you had it before. The magisk app will still be there.
4- (Optional to get back root). Repeat the same steps as above in my first instructions to get back root. i.e. download the FASTBOOT version of the corresponding new release (ROM Download) and unzip and transfer boot.img to your phone and patch it with the magisk app, and finally reboot to TWRP and flash boot with this patched magisk_patched*.img (or alternately return to fastboot and 'fastboot flash boot /path/to/magisk_patched.img).

was able to flash the rom fine (used fastbootd version, flashed boot, product, system, vbmeta imgs (in that order) then switched from fastbootd to regular fastboot to do "fastboot -w") but my Sprint LTE internet is not working. it just says 1X or 3G, but there will never be a connection. SMS messages and calls still work. here's my "fastboot getvar all" output after installing patched boot.img from magisk:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofia_retail-3b6d53a311-200901
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(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: 0x8d
(bootloader) uid: 07E6EA84
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805261312
(bootloader) reason: Volume down key pressed
(bootloader) date: 06-18-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) battid: SB18C57587
(bootloader) battery-voltage: 4187
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:10/QPM
(bootloader) ro.build.fingerprint[1]: S30.80-109-5/2d6e7:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(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_34.30.03.38R SOFIA_NA_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 Tue Sep 1 03:2
(bootloader) kernel.version[3]: 3:51 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofia_retail-61355838c-200901
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-61355838c-200901
(bootloader) git:rpm: MBM-3.0-sofia_retail-ffcccb0-200901
(bootloader) git:tz: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:hyp: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:devcfg: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:keymaster: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:prov: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) git:abl: MBM-3.0-sofia_retail-3b6d53a311-200901
(bootloader) git:qupfw: MBM-3.0-sofia_retail-f848623-200901
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-ad26b10f-200901
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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
(bootloader) pcb-part-no: SB28C55260
all: listed above
Finished. Total time: 0.072s

Excellent. I was just looking for a way to restore my horrifically sluggish G Power to some usability.
Question though: no mention in this post of unlocking the bootloader... is that not necessary?

ehidle said:
Excellent. I was just looking for a way to restore my horrifically sluggish G Power to some usability.
Question though: no mention in this post of unlocking the bootloader... is that not necessary?
Click to expand...
Click to collapse
Unlocking the bootloader is a given, you will also need to downgrade back to stock a10.

ph4n70m-404 said:
Unlocking the bootloader is a given, you will also need to downgrade back to stock a10.
Click to expand...
Click to collapse
That's what I figured but it was not listed in the instructions.
Help me out though since I'm not up on all the lingo. Downgrade to stock A10? What does this mean exactly?
EDIT: OOOHHHH duh... stock Android 10... okay so I need to find some stock images for that because it's on 11 now... Got it.. too early

rightonyourtail said:
Fantastic thanks for the work on this!
Can confirm working on my moto g power (2020) with Magisk.
Some notes I took that might help others:
Note: I don't guarantee that my notes give the fastest or best way of installing this ROM! I'm just including these instructions because they detail one working way of doing this. Use at your own risk!
You have two ways to flash, using fastboot (where you need to download lineage-18.1-20211010-UNOFFICIAL-FASTBOOTD-sofiar.zip) or sideloading with TWRP (where you need to download lineage-18.1-20211010-UNOFFICIAL-sofiar.zip). Probably use the newest version (the datestamp in the filename should be the latest). I chose to sideload with TWRP. Since I also wanted magisk (root) I also ended up needing to download lineage-18.1-20211010-UNOFFICIAL-sofiar.zip anyway to flash boot.img, which it contains (see below).
The main instructions I used can be found here: https://wiki.lineageos.org/devices/channel/install
1 - I flashed the linked TWRP to temporary recovery by fastboot flashing to boot_a and boot_b. Upon reboot to recovery it would first reboot to android recovery (pic of dead droid with red exclamation point) and hang. I needed to press the power button until that screen disappeared. It would then reboot into TWRP.
2 - I sideloaded lineage-18.1-20211010-UNOFFICIAL-sofiar.zip using TWRP (Advanced->ADB Sideload) after reverting to factory (i.e. clearing data and cache)
3 - reboot into system and Lineage18.1 will load (first boot takes a while with the loading screen)
4 - I wanted magisk (follow the instructions at https://topjohnwu.github.io/Magisk/install.html) so I installed the Magisk apk and then used its app to flash the boot.img in lineage-18.1-20211010-UNOFFICIAL-FASTBOOTD-sofiar.zip, then transferred that back to my PC ('adb pull /sdcard/Download/magisk_patched_[random_strings].img')
5 - then 'adb reboot fastboot' will take you to fastbootd (this is different from fastboot, although you can probably also use fastboot) where you can run 'fastboot flash boot /path/to/magisk_patched.img'
6 - reboot and done
** In the process of figuring this out I got caught in some softlocks and bootloops. Just turn off the phone and turn it back on holding the down-volume with power to get into fastboot, then restart at step 1. I think this happens sometimes when A/B conflict arises, I'm not sure...
EDIT: @ehidle reminded me that there are some steps before flashing I didn't mention:
You need to first unlock your bootloader. Follow
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
(You'll need to create a Motorola account.)
You also need to have a stock ROM with Android 10 (not 11!).
If you have the US version Moto G Power (2020) you can find them here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
If you have the G8 Power you can find them here: https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Addendum: Updating with new release
Just upgraded to the Nov 8th release from the October one. Worked seamlessly! A few notes:
1-You can find the updater at Settings->System->Advanced->Updater. Refresh and then click on the release you want to download. It will download and prepare the image.
2- Once it says it is done, you can reboot to TWRP (which for me isn't permanent so I had to reflash that into boot_a and boot_b as explained above in my first instructions) and "Install" the updated lineage image zip (i.e. flash the ROM) you downloaded. Note: I found the zip in /data/lineageos_updates not in /data/ota_package as indicated by @ph4n70m-404 in the original post.
3- Reboot and you're done. Everything will be saved as before except magisk root will be gone if you had it before. The magisk app will still be there.
4- (Optional to get back root). Repeat the same steps as above in my first instructions to get back root. i.e. download the FASTBOOT version of the corresponding new release (ROM Download) and unzip and transfer boot.img to your phone and patch it with the magisk app, and finally reboot to TWRP and flash boot with this patched magisk_patched*.img (or alternately return to fastboot and 'fastboot flash boot /path/to/magisk_patched.img).
Click to expand...
Click to collapse
@rightonyourtail. I just found this today. I'm currently using @Beetle84's Havoc 4.8 on my Moto G8 Power 2020 (Sofia), but my battery charge is only lasting about a day. I'm very familiar with LOS and I'm running followmsi's LOS 18.1 on my ancient Galaxy Note 4 Snapdragon, and my 3 Nexus 7 2013 deb (4G/LTE) tablets. Do you think this ROM will increase my battery life, and do I need to do something special considering that I'm already running @Beetle84's Havoc 4.8? I look forward to flashing this ROM pursuant to your useful notes.
Thanks

whenever i try to adb sideload the non fastbootd one i just get a boot loop with the lineage os boot screen with the circle going across the screen. anyone able to help me figure that out?

jhford said:
@rightonyourtail. I just found this today. I'm currently using @Beetle84's Havoc 4.8 on my Moto G8 Power 2020 (Sofia), but my battery charge is only lasting about a day. I'm very familiar with LOS and I'm running followmsi's LOS 18.1 on my ancient Galaxy Note 4 Snapdragon, and my 3 Nexus 7 2013 deb (4G/LTE) tablets. Do you think this ROM will increase my battery life, and do I need to do something special considering that I'm already running @Beetle84's Havoc 4.8? I look forward to flashing this ROM pursuant to your useful notes.
Thanks
Click to expand...
Click to collapse
I don't have any familiarity with Havoc. I can only say that I regularly get >3 days of battery life with LOS but with heavy video streaming it can get down to one day.
If you decide to try LOS, you'll need to flash stock Android 10 on the device with Havoc first.

thep_irate said:
whenever i try to adb sideload the non fastbootd one i just get a boot loop with the lineage os boot screen with the circle going across the screen. anyone able to help me figure that out?
Click to expand...
Click to collapse
3 - reboot into system and Lineage18.1 will load (first boot takes a while with the loading screen)
I assume you've waited over, say 5 minutes (or maybe 10-20 min to be sure)? If so, you might want to try again but first wipe data, system, cache, and dalvik cache in TWRP.

rightonyourtail said:
3 - reboot into system and Lineage18.1 will load (first boot takes a while with the loading screen)
I assume you've waited over, say 5 minutes (or maybe 10-20 min to be sure)? If so, you might want to try again but first wipe data, system, cache, and dalvik cache in TWRP.
Click to expand...
Click to collapse
i know i waited over 20 minutes i let it sit overnight so ill try all that

rightonyourtail said:
3 - reboot into system and Lineage18.1 will load (first boot takes a while with the loading screen)
I assume you've waited over, say 5 minutes (or maybe 10-20 min to be sure)? If so, you might want to try again but first wipe data, system, cache, and dalvik cache in TWRP.
Click to expand...
Click to collapse
i think its still boot looping

thep_irate said:
i think its still boot looping
Click to expand...
Click to collapse
Were you on android 10 or 11 before flashing?

Beetle84 said:
Were you on android 10 or 11 before flashing?
Click to expand...
Click to collapse
11 pretty sure

rightonyourtail said:
I don't have any familiarity with Havoc. I can only say that I regularly get >3 days of battery life with LOS but with heavy video streaming it can get down to one day.
If you decide to try LOS, you'll need to flash stock Android 10 on the device with Havoc first.
Click to expand...
Click to collapse
This brings up a question I've wondered about: We know that if you're running stock A11, you must downgrade to A10 before installing a custom A11 ROM. But is that required when switching from a custom A11 to a different custom A11?
I went straight from OEM A10 to a custom ROM and have switched among a handful without the downgrade (most recently from Beetle's Havoc to Arrow) with no discernable issues. BTW I've always installed via the fastbootd files.

Leroy_Sparks said:
This brings up a question I've wondered about: We know that if you're running stock A11, you must downgrade to A10 before installing a custom A11 ROM. But is that required when switching from a custom A11 to a different custom A11?
I went straight from OEM A10 to a custom ROM and have switched among a handful without the downgrade (most recently from Beetle's Havoc to Arrow) with no discernable issues. BTW I've always installed via the fastbootd files.
Click to expand...
Click to collapse
im a huge noob. how would i go about downgrading to android 10?

thep_irate said:
im a huge noob. how would i go about downgrading to android 10?
Click to expand...
Click to collapse
From my instructions above:
You also need to have a stock ROM with Android 10 (not 11!).
If you have the US version Moto G Power (2020) you can find them here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
If you have the G8 Power you can find them here: https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
Flash stock A10 first and then reboot before trying to flash LOS. Hope this solves your problem!

rightonyourtail said:
From my instructions above:
Flash stock A10 first and then reboot before trying to flash LOS. Hope this solves your problem!
Click to expand...
Click to collapse
flashing A10 now. hope this fixes it