Database Info

oneplus 6 stuck at fastboot

So its just stuck in fastboot mode ive tried fastboot flash boot_a,boot_b and nothing happens its just stuck in fastboot.

That's the best custom kernel I've seen so far. But it is missing information and the GitHub source code

I take it using the volume keys and power keys to select start or recovery do not work? If that's the case, use the MSM Recovery Tool found here and revert back to stock

can you boot twrp? if not, than try to flash ALL partitions manually with fastbootcommands
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
of course U need the -stock-fastboot-rom which u have

Moto G7 Power Failing to restore restore orgional firmware

Hello all,
I have been trying to restore my Moto G7 Power to it's original firmware. I keep getting flash modem "NON-HOLS.bin fail.
I have followed so many methods and different tools and all failing.
I'm also getting permission denied when using adb fastboot.
I really need help on this, I'm definitely a noob here and need some guidance from the experts on this platform.
Thank you all in advance.

Solo-Play said:
Hello all,
I have been trying to restore my Moto G7 Power to it's original firmware. I keep getting flash modem "NON-HOLS.bin fail.
I have followed so many methods and different tools and all failing.
I'm also getting permission denied when using adb fastboot.
I really need help on this, I'm definitely a noob here and need some guidance from the experts on this platform.
Thank you all in advance.
Click to expand...
Click to collapse
Firmware you are trying to flash?
Model number?
Bootloader unlocked?
Sent from my mata using XDA Labs

Hello,
Phone is Moto G7 Power, Retail, XT1955-5, Ocean Retail
Bootloader was unlocked, then some how during my restore attempt it got locked. Unless I read it incorrectly. Not sure if there a way to confirm its locked.
Firmware. PPOS29.114-134-7-1
Hope this helps. Many thanks in advance

Solo-Play said:
Hello,
Phone is Moto G7 Power, Retail, XT1955-5, Ocean Retail
Bootloader was unlocked, then some how during my restore attempt it got locked. Unless I read it incorrectly. Not sure if there a way to confirm its locked.
Firmware. PPOS29.114-134-7-1
Hope this helps. Many thanks in advance
Click to expand...
Click to collapse
The bootloader says
Device: locked
Or
Device: unlocked
Sent from my mata using XDA Labs

sd_shadow said:
The bootloader says
Device: locked
Or
Device: unlocked[/QUOTE
At this point I'm not sure. Is there any easier way to find out?
Click to expand...
Click to collapse

Solo-Play said:
At this point I'm not sure. Is there any easier way to find out?
Click to expand...
Click to collapse
Yes see bootloader screen
Sent from my mata using XDA Labs

Download the LMSA tool and proper drivers. Do the recovery to flash the latest software, you should be good to go. Here is the link: https://www.motorola.com/us/lenovo-motorola-smart-assistant

WaterMan! said:
Download the LMSA tool and proper drivers. Do the recovery to flash the latest software, you should be good to go. Here is the link: https://www.motorola.com/us/lenovo-motorola-smart-assistant
Click to expand...
Click to collapse
Hello WaterMan. I have already tried it. It keeps on failing between 55 and 70%. I do get some other error messages such as partition delay.

Solo-Play said:
Hello WaterMan. I have already tried it. It keeps on failing between 55 and 70%. I do get some other error messages such as partition delay.
Click to expand...
Click to collapse
These are the commands you are using?
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Are you sure you have the correct software channel firmware?
Try
Code:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
Then try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
If you don't get any errors try
Code:
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot-bootloader
If that works
Try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
Post any errors
Sent from my mata using XDA Labs

sd_shadow said:
These are the commands you are using?
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Are you sure you have the correct software channel firmware?
Try
Code:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
Then try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
If you don't get any errors try
Code:
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot-bootloader
If that works
Try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
Post any errors
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Code:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
Then try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
the above codes worked.
However these codes didn't work at
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot-bootloader
I got an error that says
example: (bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.518s
The answer about the right channel firmware. I think I have the right firmware. The one I downloaded was PPOS29.114-134-7-1 , this firmware same as the build number number on my phone in the setting menu

Solo-Play said:
the above codes worked.
However these codes didn't work at
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot-bootloader
I got an error that says
example: (bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.518s
The answer about the right channel firmware. I think I have the right firmware. The one I downloaded was PPOS29.114-134-7-1 , this firmware same as the build number number on my phone in the setting menu
Click to expand...
Click to collapse
There are ~20 different software channels for Ocean
https://mirrors.lolinet.com/firmware/moto/ocean/official/
PPOS29.114-134-7-1 is just the build version not software channel
Like retail, retus, reteu...
It has radio files and apns for your carrier among other things
Sent from my mata using XDA Labs
---------- Post added at 05:08 PM ---------- Previous post was at 04:35 PM ----------
Software channel info is in
Settings/about phone
Sent from my mata using XDA Labs

Hello,
Thanks for replying. I've seen this website site before. And yes my phone is Retail, I bought it at Best Buy. I'm some what aware of different firmwares. My question is and forgive me for sounding dumb with a question. How can I tell or find out which firmware to get. Is there an easier way to find out or is there a program that could automatically download and fix the phone, I mean restore it to it's original state.
Once again, I greatly appreciate all the help, feedback and guidance

Solo-Play said:
Hello,
Thanks for replying. I've seen this website site before. And yes my phone is Retail, I bought it at Best Buy. I'm some what aware of different firmwares. My question is and forgive me for sounding dumb with a question. How can I tell or find out which firmware to get. Is there an easier way to find out or is there a program that could automatically download and fix the phone, I mean restore it to it's original state.
Once again, I greatly appreciate all the help, feedback and guidance
Click to expand...
Click to collapse
If you bought at Best Buy, I would think it was
Retus not Retail
Sent from my ocean using XDA Labs

sd_shadow said:
If you bought at Best Buy, I would think it was
Retus not Retail
Click to expand...
Click to collapse
I may have downloaded it in the past and ran it using RSD Lite and got the same error non-holos.bin
By the way, I used the LMSA tool provided by Motorola. It found the firmware and when I ran it , it gave me a delay error and fastboot fail
I wonder if there is a way or tool to force the firmware update and install on the phone.
Oh by the way when I turn on my phone I get an error message that reads ( Your device has loaded a different operating system. ) then boots up fine after pressing power button.
I honestly wish if there was a way to wipe everything clean on the phone and restore everything back just like the computer when installing Windows

Motorola Z3 play baseband brick HELPME PLEASE (u__u)

hello guys I'm new to this community !! I needed your help to restore my phone's baseband !! in fastboot mode baseband shows how not found !!! I already have the bootloader unlocked .. I would like using TWRP to flash baseband again ???
MY phone specs
BL:MBM3.0-becham_retail-8ca64c4-190220
Baseband: <not found>
Product/Variant: beckham XT1929-5 64GB PVT
if someone can help me with some method to solve with linux or zip flash i am very grateful thanks to all

I finally figured out how to recover a base band from motorola Z3 play !!!
NOTE: <<<< NEED BOOTLOADER UNLOCKED >>>>
After unlocking the bootloader I used this rom
<<<< XT1929-5_BECKHAM_RETBR_9.0_PPWS29.131-27-1-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC >>>
!!! To install the system on the smartphone
correcting the connection problem and corrupted IMEI
Comand line to INSTALL ROM IN ADB TOOLS:
----------------------------------------------------------------------------------------------------------
fastboot oem fb_mode_set
fastboot flash gpt_a gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
----------------------------------------------------------------------------
After installation the problem will be fixed I hope I helped it took me 3 days to solve this problem even having intermediate knowledge of android system !!!
for people who have no knowledge !! a wrong root can cause a briking baseband easily
my email for some help if you want !!
[email protected]

Android 10 Soak Test Underway

Last couple of days people have been receiving the long awaited Android 10. Possibly few more weeks until the broad release.

lollyjay said:
Last couple of days people have been receiving the long awaited Android 10. Possibly few more weeks until the broad release.
Click to expand...
Click to collapse
Fakeeeeeee
Someone got their hands on the soak test and started sharing false information, the update has not released, it is just now going in to soak test (2) and nothing has released officially.

SnowTalker said:
Fakeeeeeee
Someone got their hands on the soak test and started sharing false information, the update has not released, it is just now going in to soak test (2) and nothing has released officially.
Click to expand...
Click to collapse
That is what I posted read the title
Sent from my 7 Pro using XDA Labs

lollyjay said:
That is what I posted read the title
Click to expand...
Click to collapse
Lol, sorry

SnowTalker said:
Lol, sorry
Click to expand...
Click to collapse
NP?
Sent from my 7 Pro using XDA Labs

Brasil Android 10 XT 2019-2 !
https://www.gsmnigeria.com/motorola...-android-10-q-brazil-retbr-qpi30-28-q3-28-26/

Petrica said:
Brasil Android 10 XT 2019-2 !
https://www.gsmnigeria.com/motorola...-android-10-q-brazil-retbr-qpi30-28-q3-28-26/
Click to expand...
Click to collapse
Progress... ?

Yes,first 2 files from the archive must be deleted...otherway is clean.

lollyjay said:
Progress... ?
Click to expand...
Click to collapse
Firmware is released on lolinet for retail. Compatible for all device channels excluding AMX. So you can experience android 10 before it even releases for your country

I have amx
SnowTalker said:
Firmware is released on lolinet for retail. Compatible for all device channels excluding AMX. So you can experience android 10 before it even releases for your country
Click to expand...
Click to collapse
Why is not suport AMX? i have AMX and i install it by adb fastboot and no problem, if you keep your user data wee need to delete line 'erase user data' and keep 'erase Carrier' and 'erase ddr' lines, because if you not keep 'erase Carrier' and 'erase ddr' lines your brick your phone.

This is the code i used to install android 10 for https://mirrors.lolinet.com/firmware/moto/doha/official/RETAIL/
Please be careful and use this code in this order, i not have responsibility if you brick your phone.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase ddr
fastboot reboot
Click to expand...
Click to collapse

LushoxLucid said:
This is the code i used to install android 10 for https://mirrors.lolinet.com/firmware/moto/doha/official/RETAIL/
Please be careful and use this code in this order, i not have responsibility if you brick your phone.
Click to expand...
Click to collapse
Does the bootloader need to be unlocked to flash this?

No need
dneill2006 said:
Does the bootloader need to be unlocked to flash this?
Click to expand...
Click to collapse
You dont need the bootloader unlocked to use this method, you will need enable oem unlock and usb debugging for developer options and put your phone in bootloader mode and use adb fastboot in powershell or cmd.

LushoxLucid said:
You dont need the bootloader unlocked to use this method, you will need enable oem unlock and usb debugging for developer options and put your phone in bootloader mode and use adb fastboot in powershell or cmd.
Click to expand...
Click to collapse
Thanks.
My model is XT 2019-1, will it still work OK?

Tried to flash but it failed on "fastboot flash modem NON-HLOS.bin"
Must be because my model is XT 2019-1.

Here is the code I used successfully. I initially didn't flash both slots, which ended in a bootloop since I was on the wrong slot afterwards. YMMV if you wish to use the following.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash system_b system.img_sparsechunk.3
fastboot flash system_b system.img_sparsechunk.4
fastboot flash system_b system.img_sparsechunk.5
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
Click to expand...
Click to collapse

NeoandGeo said:
Here is the code I used successfully. I initially didn't flash both slots, which ended in a bootloop since I was on the wrong slot afterwards. YMMV if you wish to use the following.
Click to expand...
Click to collapse
Please use these commands Instead, I tested them and they work.
fastboot --set-active=a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse

SnowTalker said:
Please use these commands Instead, I tested them and they work.
Click to expand...
Click to collapse
I made a windows batch file to automate your commands. I had to call it a .zip file just to make it downloadable in XDA. Just download it and rename it from .zip to .bat. Then run it. Any questions, please ask. Thanks to @SnowTalker for the commands.

I think that there is a download on lollinet for the RETAIL version of Android 10. I'm on the road, so if someone can check it out, that would be great.

lollyjay said:
I think that there is a download on lollinet for the RETAIL version of Android 10. I'm on the road, so if someone can check it out, that would be great.
Click to expand...
Click to collapse
That's what I used with these commands.

Relock bootloader

Part, anyone knows an effective method to lock the bootloader so that I have oem_locked written instead of flashing_locked? You unlocked with a code from the Motorola website, which is the official method. I did not modify anything and blocked it with fastboot oem_lock. From now on, instead of oem_locked, I have flashing_locked written. Re-unlocking with the fastboot oem_unlock command is possible without the use of a code from Motorola. Is it normal? Another interesting and strange thing is that after entering recovery mode and trying to install the update from the sd card, he gets the error that he cannot see the card. If he wants to upload updates via ADB he also gets an error. LMSA rescue flashing also crashes when switching to fastboot mode. In general, in fastboot mode, I should be able to flash the stock without unlocking the bootloader and no, I can do it because I also have an error
C: \ adb> fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical: modem_a: not found
Sending 'modem_a' (81048 KB) OKAY [2.072s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Yesterday I started the phone in edl mode and used blankflash. Then I wanted to flash the stock but had to unlock the bootloader. Or rather, there shouldn't be such a need. I do not know how to bring it to the factory state.

gorbatschoff said:
Part, anyone knows an effective method to lock the bootloader so that I have oem_locked written instead of flashing_locked? You unlocked with a code from the Motorola website, which is the official method. I did not modify anything and blocked it with fastboot oem_lock. From now on, instead of oem_locked, I have flashing_locked written. Re-unlocking with the fastboot oem_unlock command is possible without the use of a code from Motorola. Is it normal? Another interesting and strange thing is that after entering recovery mode and trying to install the update from the sd card, he gets the error that he cannot see the card. If he wants to upload updates via ADB he also gets an error. LMSA rescue flashing also crashes when switching to fastboot mode. In general, in fastboot mode, I should be able to flash the stock without unlocking the bootloader and no, I can do it because I also have an error
C: \ adb> fastboot flash modem_a NON-HLOS.bin
(bootloader) is-logical: modem_a: not found
Sending 'modem_a' (81048 KB) OKAY [2.072s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
Yesterday I started the phone in edl mode and used blankflash. Then I wanted to flash the stock but had to unlock the bootloader. Or rather, there shouldn't be such a need. I do not know how to bring it to the factory state.
Click to expand...
Click to collapse
All of that happened to me except for the flashing locked and unlocked part, when I first got my phone before it was ever unlocked, it said flash_locked and I unlocked it and then it's flashing_unlocked. Now when I relock it, it goes back to it's original state, as flashing_locked. I get Motorola updates still so that's a plus to me.
Never had to start the phone in edl and hope I never have to.
Never used LMSA, and hope I never have to.
And my suggestion would be unlock the bootloader and flash stock firmware from lolinet and use these commands
↓
fastboot devices
fastboot set_active a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img_sparsechunk.0 fastboot flash system_a system.img_sparsechunk.1 fastboot flash system_a system.img_sparsechunk.2 fastboot flash system_a system.img_sparsechunk.3 fastboot flash system_a system.img_sparsechunk.4 fastboot flash system_a system.img_sparsechunk.5 fastboot flash system_b system_b.img_sparsechunk.0 fastboot flash system_b system_b.img_sparsechunk.1 fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
↑
After that, boot it up for the first time and setup the phone. After seeing the home screen power off and boot to fastboot and lock your bootloader, the reason I say lock it is because there is no better reason to have it unlocked imo ("totally unnecessary, you can do what you want, I'm just trying to help ") because there isn't really a striving development community with ROMs yet. I think here soon there will be once Android 10 releases for this phone .

Thanks for the answer. I've used these commands and of course they work. The phone works but the ADB and recovery problem is still there. And that worries me.

dont work
SnowTalker said:
All of that happened to me except for the flashing locked and unlocked part, when I first got my phone before it was ever unlocked, it said flash_locked and I unlocked it and then it's flashing_unlocked. Now when I relock it, it goes back to it's original state, as flashing_locked. I get Motorola updates still so that's a plus to me.
Never had to start the phone in edl and hope I never have to.
Never used LMSA, and hope I never have to.
And my suggestion would be unlock the bootloader and flash stock firmware from lolinet and use these commands
↓
fastboot devices
fastboot set_active a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img_sparsechunk.0 fastboot flash system_a system.img_sparsechunk.1 fastboot flash system_a system.img_sparsechunk.2 fastboot flash system_a system.img_sparsechunk.3 fastboot flash system_a system.img_sparsechunk.4 fastboot flash system_a system.img_sparsechunk.5 fastboot flash system_b system_b.img_sparsechunk.0 fastboot flash system_b system_b.img_sparsechunk.1 fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
↑
After that, boot it up for the first time and setup the phone. After seeing the home screen power off and boot to fastboot and lock your bootloader, the reason I say lock it is because there is no better reason to have it unlocked imo ("totally unnecessary, you can do what you want, I'm just trying to help ") because there isn't really a striving development community with ROMs yet. I think here soon there will be once Android 10 releases for this phone .
Click to expand...
Click to collapse
dont work

bugy65 said:
dont work
Click to expand...
Click to collapse
The commands?