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

hardbicked my g8 plus (Solved)

Search This thread

Oshmar

Senior Member
Aug 19, 2016
544
198
Rio de Janeiro
Meu XT2019-2 estava e está tendo o mesmo problema, e não importa se você está piscando o mesmo FW ou um mais novo, não funciona, sempre falhará, o bootloader sempre será negado. E os programas disponibilizados por Lenovorola são extremamente inconsistentes, o resgate e assistente da Lenovo é tão problemático quanto os aparelhos da marca. Meu conselho é procurar qualquer assistência que tenha um programa em caixa, depois vendê-lo, jogá-lo fora ou entregá-lo ao seu sobrinho para brincar ... A Motorola é conhecida pela maioria dos técnicos como tendo mais problemas de software em smartphones. Compre um Xiaomi e seja feliz.
 

WoKoschekk

Senior Member
Feb 25, 2019
749
192
Cologne
Moto G9 Plus
Meu XT2019-2 estava e está tendo o mesmo problema, e não importa se você está piscando o mesmo FW ou um mais novo, não funciona, sempre falhará, o bootloader sempre será negado. E os programas disponibilizados por Lenovorola são extremamente inconsistentes, o resgate e assistente da Lenovo é tão problemático quanto os aparelhos da marca. Meu conselho é procurar qualquer assistência que tenha um programa em caixa, depois vendê-lo, jogá-lo fora ou entregá-lo ao seu sobrinho para brincar ... A Motorola é conhecida pela maioria dos técnicos como tendo mais problemas de software em smartphones. Compre um Xiaomi e seja feliz.
I'm using Moto devices since 2014 and never had software issues or update failures. Moto uses a clean Android OS that runs smooth and stable.
 

Oshmar

Senior Member
Aug 19, 2016
544
198
Rio de Janeiro
But you are already aware that the error in the OP isn't attributed to any software issue?

Apart from that, there are not much threads related to software issues. That speaks for itself.
The issue is in the aid programs that few brands offer with real effectiveness. You would hardly find programs that work as randomly as those made available by Lenovorola. By any chance, have you ever heard of a program like; MiFlash, Odin, LGFlash for example, that doesn't work on anything above Windows 7? Well, this is the level of RSD Lite.
 
May 19, 2021
14
0
sometimes I imagine these people standing at the counter at McDonald's and placing an order: Hungry...two burgers...a drink...french fries...sauce...thx!
sorry my english i use translator could help me my moto g8 plus is updated for android 10 i unlocked it and then i wanted to block it i used a command from a guy on youtube but when i gave the command appears on the phone screen the option to choose if I want to block the phone's oem then I accepted it but it is now only on the bootloader screen
 

WoKoschekk

Senior Member
Feb 25, 2019
749
192
Cologne
Moto G9 Plus
sorry my english i use translator
it doesn't matter :) but it's always helpful to get as much information as possible. ;-)

First I would try to flash the complete stock firmware. Your device should accept it even with a locked bootloader. But take care of using the latest firmware version matching your region.

Post your exact device model (XT2019-???) and I'll give you a download link... in case you don't know it yourself. And if needed I will also prepare a flash script for you to install.
 
  • Like
Reactions: eotaldodekinho87
May 19, 2021
14
0
não importa, :) mas é sempre útil obter o máximo de informações possíveis. ;-)

Primeiro, eu tentaria fazer o flash fazer o firmware de estoque completo. Seu dispositivo deve aceitá-lo mesmo com um bootloader bloqueado. Mas tome cuidado ao usar a versão de firmware mais recente correspondente à sua região.

Poste o modelo exato do seu dispositivo (XT2019 - ???) e eu lhe darei um link para download ... caso você não saiba. E se nec
não importa, :) mas é sempre útil obter o máximo de informações possível. ;-)

Primeiro, eu tentaria fazer o flash do firmware de estoque completo. Seu dispositivo deve aceitá-lo mesmo com um bootloader bloqueado. Mas tome cuidado ao usar a versão de firmware mais recente correspondente à sua região.

Poste o modelo exato do seu dispositivo (XT2019 - ???) e eu lhe darei um link para download ... caso você não saiba. E se necessário, também prepararei um script em flash para você instalar.

essário, também prepararei um script em flash para

C:\Users\ItauTec\Desktop\PROGRAMA CELULAR\New Moto Tool\New Moto Tool\Moto Auto
Flash Tool v8.2 By Jamesjerss\Moto Auto Flash Tool v8.2 By Jamesjerss\Files>fast
boot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-7326ad2e6a-200807
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(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) serialno: 0066571883
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: EB3BFDB1
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 353594114419299
(bootloader) imei2: 353594114419307
(bootloader) meid:
(bootloader) date: 05-21-2020
(bootloader) sku: XT2019-2
(bootloader) carrier_sku: XT2019-2
(bootloader) battid: SB18C52857
(bootloader) battery-voltage: 4029
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retbr
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPIS30.28-Q3
(bootloader) ro.build.fingerprint[1]: -28-26-1/01c7f:user/release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.37R DOHA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Thu Sep 17 23:
(bootloader) kernel.version[3]: 56:28 CDT 2020
(bootloader) git:abl: MBM-3.0-doha_retail-7326ad2e6a-200807
(bootloader) frp-state: protected (77)
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C71343
all: listed above
Execution time is 1(s)
 
May 19, 2021
14
0
it doesn't matter :) but it's always helpful to get as much information as possible. ;-)

First I would try to flash the complete stock firmware. Your device should accept it even with a locked bootloader. But take care of using the latest firmware version matching your region.

Post your exact device model (XT2019-???) and I'll give you a download link... in case you don't know it yourself. And if needed I will also prepare a flash script for you to install.
C:\Users\ItauTec\Desktop\PROGRAMA CELULAR\XT2019-2_DOHA_AMX_10_QPIS30.28-Q3-28-2
6-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloa
der.img
target reported max download size of 805263360 bytes
sending 'bootloader' (14204 KB)...
OKAY [ 0.435s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name hyp
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name uefisecapp
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name abl
(bootloader) Invalid partition name qupfw
(bootloader) Invalid partition name xbl_config
(bootloader) Invalid partition name xbl
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.820s
 

WoKoschekk

Senior Member
Feb 25, 2019
749
192
Cologne
Moto G9 Plus
C:\Users\ItauTec\Desktop\PROGRAMA CELULAR\XT2019-2_DOHA_AMX_10_QPIS30.28-Q3-28-2
6-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloa
der.img
target reported max download size of 805263360 bytes
sending 'bootloader' (14204 KB)...
OKAY [ 0.435s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name hyp
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name uefisecapp
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name abl
(bootloader) Invalid partition name qupfw
(bootloader) Invalid partition name xbl_config
(bootloader) Invalid partition name xbl
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.820s
Enter this command
Code:
fastboot oem fb_mode_clear
 

WoKoschekk

Senior Member
Feb 25, 2019
749
192
Cologne
Moto G9 Plus
C:\Users\ItauTec\Desktop\PROGRAMA CELULAR\XT2019-2_DOHA_AMX_10_QPIS30.28-Q3-28-2
...
Moto devices use
fastboot oem fb_mode_set
and
fastboot oem fb_mode_clear
as the first and last commands in their OEM flash scripts.This is to prevent you from accidentally starting your system.
Execute my command in the post before and your device should boot up normally.

In your output of getvar all is one line:
(bootloader) reason: Reboot mode set to fastboot
which indicates what I said before.
 
May 19, 2021
14
0
Moto devices use
fastboot oem fb_mode_set
and
fastboot oem fb_mode_clear
as the first and last commands in their OEM flash scripts.This is to prevent you from accidentally starting your system.
Execute my command in the post before and your device should boot up normally.

In your output of getvar all is one line:

which indicates what I said before.
I used the command but it did not return to normal it does not start because it is blocked with the bootloard in the adb program it shows some errors
I will post again
 
Jun 8, 2021
6
0
Just extract and rom from your device, open cmd and type " fastboot bot bot.img " it will turn on. Enable oem unlock in developer options. And install the rom by "Rescue from Motorola" mine is locked on the bootloader screen and with the flash locked. I did that and fixed my moto g 8 plus.



Basta extrair e rom do seu aparelho, abri o cmd e digitar " fastboot bot bot.img " ele vai ligar. Habila o desbloqueio de oem nas opção de desenvolvedor. E instala a rom pelo " Rescue da Motorola " o meu está travado na tela do bootloader e com o flash travado. Fiz isso e arrumei meu moto g 8 plus.
 
Last edited by a moderator:
Jun 8, 2021
6
0
Meu XT2019-2 estava e está tendo o mesmo problema, e não importa se você está piscando o mesmo FW ou um mais novo, não funciona, sempre falhará, o bootloader sempre será negado. E os programas disponibilizados por Lenovorola são extremamente inconsistentes, o resgate e assistente da Lenovo é tão problemático quanto os aparelhos da marca. Meu conselho é procurar qualquer assistência que tenha um programa em caixa, depois vendê-lo, jogá-lo fora ou entregá-lo ao seu sobrinho para brincar ... A Motorola é conhecida pela maioria dos técnicos como tendo mais problemas de software em smartphones. Compre um Xiaomi e seja feliz.
Get in touch with me and I'll help you... I had the same problem that you had and I fixed mine



Entre em contato comigo que ti ajudo.. tava com o msm problema que vc e concertei o meu
 
Last edited by a moderator:
  • Sad
Reactions: eotaldodekinho87

TNSMANI

Senior Moderator
Staff member
Jan 8, 2014
5,295
1
6,870
Chennai
@BrenoSilva1997

You are welcome to provide any help in the thread itself. Please don't ask members that need help to contact you outside the thread.

And please use English as per Rule 4:
4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
 
May 19, 2021
14
0
HELP ME MOTOROLA

I will leave the error that my G8 Plus phone

I had unlocked it when I went to lock it again I had this problem that doesn't come out of the fastboot screen


C:\Users\Admin\Desktop\motorola\XT2019-2_DOHA_OPENLA_10_QPIS30.28-Q3-28-26-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 805263360 bytes
sending 'bootloader' (14204 KB)...
OKAY [ 0.605s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name hyp
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name uefisecapp
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name abl
(bootloader) Invalid partition name qupfw
(bootloader) Invalid partition name xbl_config
(bootloader) Invalid partition name xbl
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 1.577s
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Successfully recovered your device

    Hey i hard bricked my g8 plus. I forget to unlock oem bootloader and now i cant start the phone. when flash the stock rom the screen stay in "your device is corrupt. it cant be trusted and will not boot" :(
    What can i do? the phone cant start and cant unlock bootloader

    My friend, I found the solution to your problem (I think).

    I'm already sorry because I'm Brazilian and I don't speak the language very well, however I will use the translator to try to explain.
    This week I bought this cell phone, I'm too curious and ended up getting this same problem as you, in the same way.
    And believe me, I found the solution.
    You will do the following, take the adb installation folder with the last stock rom, and do the commands below:

    mfastboot getvar max-sparse-size
    mfastboot oem fb_mode_set
    mfastboot flash partition gpt.bin
    mfastboot flash bootloader bootloader.img
    mfastboot flash modem NON-HLOS.bin
    mfastboot flash fsg fsg.mbn
    mfastboot erase modemst1
    mfastboot erase modemst2
    mfastboot flash bluetooth BTFM.bin
    mfastboot flash dsp dspso.bin
    mfastboot flash logo logo.bin
    mfastboot flash boot boot.img
    mfastboot flash system system.img_sparsechunk.0
    mfastboot flash system system.img_sparsechunk.1
    mfastboot flash system system.img_sparsechunk.2
    mfastboot flash system system.img_sparsechunk.3
    mfastboot flash system system.img_sparsechunk.4
    mfastboot flash system system.img_sparsechunk.5
    mfastboot flash system system.img_sparsechunk.6
    mfastboot flash system system.img_sparsechunk.7
    mfastboot flash system system.img_sparsechunk.8
    mfastboot flash system system.img_sparsechunk.9
    mfastboot flash system system.img_sparsechunk.10
    mfastboot flash system system.img_sparsechunk.11
    mfastboot flash system system.img_sparsechunk.12
    mfastboot flash system_b system_other.img
    mfastboot flash oem oem.img
    mfastboot flash oem_b oem_other.img
    mfastboot flash system_b.img_sparsechunk.0
    mfastboot flash system_b.img_sparsechunk.1
    mfastboot flash system_b.img_sparsechunk.2
    mfastboot flash system_b.img_sparsechunk.3
    mfastboot flash system_b.img_sparsechunk.4
    mfastboot flash vendor vendor.img
    mfastboot flash vbmeta vbmeta.img
    mfastboot erase carrier
    mfastboot erase userdata
    mfastboot erase DDR
    mfastboot oem fb_mode_clear
    mfastboot reboot


    I used mfastboot but if using fastboot just remove the letter m from the beginning of each command
    I believe it arrived in that error because the commands you may have used previously were incomplete, I believe that mainly the vbmeta command was missing.

    I hope you have successfully recovered your device. :D
    2
    congrats on fixing it :good:
    so the extra command was the solution good to know

    Don't you recognize you gave him completely wrong flashing commands in post #9????
    These commands have nothing in common with A/B devices, they're for A-only devices!!

    I can't understand why people are posting commands without even proof them. Inside of EVERY firmware zip is a flashfile.xml and those commands are the right one for your model. There's no need to post any commands, but everyone does. And 80% of them are wrong!
    2
    congrats on fixing it :good:
    so the extra command was the solution good to know

    Exactly.
    I realized that the exact commands that should be used in the fasboot of our beloved moto g8 plus had not been shared anywhere, so I looked file by file and realized that in the commands used by me and others, at no time did I describe the flash from the vbmeta file, so I researched it, in addition to researching the vendor as well, since the other commands divided it and in our rom it had a unique file, so I built this list of commands and it worked perfectly.

    Some commands are not necessary in ROM, however applying them completely was my solution since I don't have (STILL) burning knowledge to assemble a perfect tutorial. Still, I intend to do it soon, at least to guide future "newbies" like me :highfive:
    1
    i had the same message and i fixed my phone, use fastboot and extract the rom into ur minimal adb folder and copy these comands into the terminal
    make sure the rom is the one for your phone model - region

    fastboot oem fb_mode_set
    fastboot flash partition gpt.bin
    fastboot flash bootloader bootloader.img
    fastboot flash logo logo.bin
    fastboot flash boot boot.img
    fastboot flash recovery recovery.img
    fastboot flash dsp adspso.bin
    fastboot flash oem oem.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 modem NON-HLOS.bin
    fastboot erase modemst1
    fastboot erase modemst2
    fastboot flash fsg fsg.mbn
    fastboot erase cache
    fastboot erase userdata
    fastboot erase customize
    fastboot erase clogo
    fastboot oem fb_mode_clear
    fastboot reboot

    btw you should also be able to lock / unlock your bootloader from fastboot terminal how many times you want, just unlock your bootloader 1st, using this guide https://www.getdroidtips.com/how-to...s/#Steps_to_Unlock_Bootloader_on_Moto_G8_Plus
    1
    sorry my english i use translator
    it doesn't matter :) but it's always helpful to get as much information as possible. ;-)

    First I would try to flash the complete stock firmware. Your device should accept it even with a locked bootloader. But take care of using the latest firmware version matching your region.

    Post your exact device model (XT2019-???) and I'll give you a download link... in case you don't know it yourself. And if needed I will also prepare a flash script for you to install.