Develop Bugs

Stock Recovery

hello
my gx8 got virus and i want to reinstall official firmware but when i try to put phone on force update (vol-vol+power) it goes to twrp(i have twrp installed) and dosen't try to install firmware in dload folder
how can i return to stock recovery?

Hello ! Do that :
download rio-l01 stock rom or update
download huawei update extractor
use it in unknown device mode
select update.app
extract these files :
recovery.img
boot.img
system.img
go to fastboot
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
good luck

Este archivo ZIP para recuperar stock se puede instalar en un gx8 rio- l03 o solo es para el rio-l01???

There is a TWRP flashable orignal ROM too in XDA Huawei GX8 ROM forums serach that and download... no need for stock recovery

Can someone on 7.1.1 pull gpt.bin and bootloader.img?

I was able to recover my bricked device today to fastboot. Because I was updated to 7.1.1 at one time, I need the 7.1.1 gpt.bin and bootloader.img. In the past I backed up modem files by the following commands. Maybe someone knows how to do this to get the gpt.bin and bootloader too?
You need to boot into TWRP, if that does not, maybe we need to boot into the Chinese recovery temporarily by entering fastboot and typing fastboot boot CHINESETWRP.img. I attached it.
adb shell
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/modem of=/sdcard/NON-HLOS.bin
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/modemst2 of=/sdcard/modemst2.img
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/fsg of=/sdcard/fsg.mbn
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/dsp of=/sdcard/adspso.bin
Maybe try this?
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/bootloader of=/sdcard/bootloader.img
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/gpt of=/sdcard/gpt.bin
Thank you in advance!

I tried this but I forgot we have to boot into TWRP and my current new Moto Z Play does not have TWRP yet so I cannot test to see if this works. See OP for new instructions.

Will the verizon version work?
See my 711 post in roms.

Gpt.bin 7.1.1
alguem poderia me ajudar preciso de uma gpt.bin 7.1.1 para celulares com hard brick como esta o meu!

Stock Firmware for XT1789-05

Hi, anyone have the OTA for Android Oreo for our model?
I'm tired to wait VIVO release the upgrade
Please?

https://androidfilehost.com/?fid=746010030569947760
here is the complete fw

Xt1789
El firmware que colocas es para el Xt1789-05? Es una ROM libre de operadora?

Piztache said:
El firmware que colocas es para el Xt1789-05? Es una ROM libre de operadora?
Click to expand...
Click to collapse
si, es libre y si, es para el XT1789-05

Muchas gracias por responder
x-geo said:
si, es libre y si, es para el XT1789-05
Click to expand...
Click to collapse
Gracias por la aportación y por la respuesta

Piztache said:
Gracias por la aportación y por la respuesta
Click to expand...
Click to collapse
Hi Piztache,
Did you manage to install the FW? is it working fine for you? I thinking to do the same with my moto.
----------------------------------------------------------------------------------------------------------------------------
Hola Piztache,
Instalaste el FW? Esta trabajando bien? Estoy pensando en hacer lo mismo en mi moto.
Thanks
Saludos!

Muy bien
Si instale la actualización,aunque como libere el bootloader, actualice todos los archivos , eso hizo que el bootloader se regresara a cerrar, y no me dejaba iniciar el teléfono, lo cual se solucionó, volviendo a abrir el bootloader, el teléfono funciona muy bien y en mi experiencia mejoro la duración de la batería
[email protected] said:
Hi Piztache,
Did you manage to install the FW? is it working fine for you? I thinking to do the same with my moto.
----------------------------------------------------------------------------------------------------------------------------
Hola Piztache,
Instalaste el FW? Esta trabajando bien? Estoy pensando en hacer lo mismo en mi moto.
Thanks
Saludos!
Click to expand...
Click to collapse

darthxa said:
Hi, anyone have the OTA for Android Oreo for our model?
I'm tired to wait VIVO release the upgrade
Please?
Click to expand...
Click to collapse
I have the last Fullflash with the January Patch. I flash in my VIVO via fastboot and it worked normally without the need to have the bootloader unlocked.

djsboy said:
I have the last Fullflash with the January Patch. I flash in my VIVO via fastboot and it worked normally without the need to have the bootloader unlocked.
Click to expand...
Click to collapse
Thanks mate, I did too...and unlocked and rooted with Magisk patched boot image that I made myself with Magisk manager

where do I find the latest ROM with the January patch. I download the file on post #2 and it only has the December patch update

x-geo said:
si, es libre y si, es para el XT1789-05
Click to expand...
Click to collapse
Como le haces para la instalacion? te metes al bootloader del telefono , o usas un software en pc? soy nuevo en el tema, y no se si me podrias explicar paso a paso. te lo agradeceria mucho

darthxa said:
Thanks mate, I did too...and unlocked and rooted with Magisk patched boot image that I made myself with Magisk manager
Click to expand...
Click to collapse
Can I do root on oreo?

lacerdajr said:
Can I do root on oreo?
Click to expand...
Click to collapse
Yes mate. There is a lot of guides here about root this model, what model is yours?

HI, i downloaded the rom stock, but i have the bootloader unlocked and TWPR installed . how can install the firmware via FASTBOOT?

adamantem said:
HI, i downloaded the rom stock, but i have the bootloader unlocked and TWPR installed . how can install the firmware via FASTBOOT?
Click to expand...
Click to collapse
Just use RSD

darthxa said:
Just use RSD
Click to expand...
Click to collapse
I have installed RSD lite 6.2.4, but when i select the zip file i get an error "get decompress file size error"
Can i try it via Fastboot with this? the order is correct?
:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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 erase carrier
fastboot erase cache
fastboot erease userdata
fastboot erase ddr
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot

adamantem said:
I have installed RSD lite 6.2.4, but when i select the zip file i get an error "get decompress file size error"
Can i try it via Fastboot with this? the order is correct?
:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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 erase carrier
fastboot erase cache
fastboot erease userdata
fastboot erase ddr
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
First unzip, then try the .xml files in rsd. The flashfile.xml is for resetting and will wipe your data, the servicefile.xml is for upgrading and should leave your data intact.
Sent from my Moto Z (2) using XDA Labs

skywalker-live said:
First unzip, then try the .xml files in rsd. The flashfile.xml is for resetting and will wipe your data, the servicefile.xml is for upgrading and should leave your data intact.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
The rsd closes as soon as it enters fastboot mode and does nothing. The steps listed by adamantem are correct? Or it could be done only with the command "fastboot flash all? Tks

Dorian Bathory said:
The rsd closes as soon as it enters fastboot mode and does nothing. The steps listed by adamantem are correct? Or it could be done only with the command "fastboot flash all? Tks
Click to expand...
Click to collapse
I answered myself. The steps listed adamantem are fine.
I put the rom without problems by fastboot. Thanks for contributing.:good:

My baseband is <not found> on the fastboot screen and i have no signal or wifi. i was hoping the firmware would correct this, but it didnt. I couldnt use RSD so i did fastboot flash one step at a time,
Any other ideas?
Couldnt get RSD to recognize device and ive read that RSD doesnt play nice with Windows 10

[Guide] Switching OEMINFO versions

I've seen a number of posts asking how to switch the oeminfo of your phone - so I decided to make a quick guide.
Warning: Use this guide at your own risk. I did this on my own p20 Lite without issue but YMMV.​
Pre-req's
Please ensure that you actually have an unlocked boot-loader
Ensure that you still have access to your boot-loader code as switching the oeminfo partition caused my phone's boot-loader to become re-locked
You are rooted
You have enabled USB debugging and your device is detected by adb/fastboot (run
Code:
adb devices
or
Code:
fastboot devices
to check this)
Make a backup of your current oeminfo - this can be shared on this thread for other users (in-case they haven't done this) or for your own piece of mind. You can use Partitions Backup from the Play Store, TWRP etc.
After switching my oeminfo I used the stock recovery to perform a factory reset. I'm not sure this was required but remote backing up of files is probably recommended just in-case...
Getting Ready
To check your current oeminfo run the following command from an ADB shell:
Code:
getprop ro.hw.custPath
This should return something like this:
Code:
/cust/ee/gb
This was what my oeminfo partition was prior to installing the generic European single sim oeminfo.
Similarly, you can run the following fastboot command to check your current oeminfo:
Code:
fastboot getvar vendorcountry
Which will report something like the following:
Code:
vendorcountry: ee/gb
The Good Stuff
Assuming you have followed the pre-req steps (you have been warned!) Do the following:
Download one of the attached oeminfo zips. Choose either single or double sim depending on your device!
Extract the contents of the download zip to your phone e.g. /sdcard/Download (change the location as required in the subsequent commands)
Run
Code:
adb shell
Enter
Code:
su
to gain root access
Overwrite your devices oeminfo using
Code:
dd if=/sdcard/Download/oeminfo.img of=/dev/block/platform/hi_mci.0/by-name/oeminfo
Now What?
When I ran the above my boot-loader became re-locked. To unlock the boot-loader you must have your boot-loader unlock code!. To unlock the boot-loader do the following:
[*]Reboot to fastboot
[*]Run
Code:
fastboot oem unlock <your bootloader code>
[*]I then performed a factory reset with the stock recovery
[/LIST]
Verifying
To check your new oeminfo run the following command from an ADB shell:
Code:
getprop ro.hw.custPath
This should now return something like this:
Code:
/cust/hw/eu
Similarly, you can run the following fastboot command to check your oeminfo:
Code:
fastboot getvar vendorcountry
Which will report something like the following:
Code:
vendorcountry: hw/eu
Oeminfo's
Single Sim - C432
Dual Sim - C432
Warning: Use this guide at your own risk (for a final time).​

For me

p20 lite
hello sorry to be able to replace my current oeminfo with that c432 these are the commands to be executed?
The Good Stuff
Assuming you have followed the pre-req steps (you have been warned!) Do the following:
Download one of the attached oeminfo zips. Choose either single or double sim on your device!
Extract the contents of the zip to your phone e.g. / sdcard / Download (change the location as required in the subsequent commands)
Run
Code:
adb shell
enter
Code:
su
to gain root access
Overwrite your devices oeminfo using
Code:
dd if = / sdcard / Download / oeminfo.img of = / dev / block / platform / hi_mci.0 / by-name / oeminfo
sorry for my English thank you

Yes that's right. Only do this of you are certain you have made a backup and have your boot loader unlock code etc

sykomaniac said:
Yes that's right. Only do this of you are certain you have made a backup and have your boot loader unlock code etc
Click to expand...
Click to collapse
sorry again a question then to install a new firmware that of c432 how should I do? thanks

I use hrupdate tool and flash full firmware through twrp. Ota updates also should work. You can find firmwares using firmware finder on the play store

no puedes especificar mejor
no se entiende el metodo mira yo tengo un zip del oeminfo del c605 lo flasheo desde el twrp ahora crees q se pueda hacer uno asi como este facicilitaria las cosas te subo el archivo asi lo analizas
sykomaniac said:
I've seen a number of posts asking how to switch the oeminfo of your phone - so I decided to make a quick guide.
Warning: Use this guide at your own risk. I did this on my own p20 Lite without issue but YMMV.​
Pre-req's
Please ensure that you actually have an unlocked boot-loader
Ensure that you still have access to your boot-loader code as switching the oeminfo partition caused my phone's boot-loader to become re-locked
You are rooted
You have enabled USB debugging and your device is detected by adb/fastboot (run
Code:
adb devices
or
Code:
fastboot devices
to check this)
Make a backup of your current oeminfo - this can be shared on this thread for other users (in-case they haven't done this) or for your own piece of mind. You can use Partitions Backup from the Play Store, TWRP etc.
After switching my oeminfo I used the stock recovery to perform a factory reset. I'm not sure this was required but remote backing up of files is probably recommended just in-case...
Getting Ready
To check your current oeminfo run the following command from an ADB shell:
Code:
getprop ro.hw.custPath
This should return something like this:
Code:
/cust/ee/gb
This was what my oeminfo partition was prior to installing the generic European single sim oeminfo.
Similarly, you can run the following fastboot command to check your current oeminfo:
Code:
fastboot getvar vendorcountry
Which will report something like the following:
Code:
vendorcountry: ee/gb
The Good Stuff
Assuming you have followed the pre-req steps (you have been warned!) Do the following:
Download one of the attached oeminfo zips. Choose either single or double sim depending on your device!
Extract the contents of the download zip to your phone e.g. /sdcard/Download (change the location as required in the subsequent commands)
Run
Code:
adb shell
Enter
Code:
su
to gain root access
Overwrite your devices oeminfo using
Code:
dd if=/sdcard/Download/oeminfo.img of=/dev/block/platform/hi_mci.0/by-name/oeminfo
Now What?
When I ran the above my boot-loader became re-locked. To unlock the boot-loader you must have your boot-loader unlock code!. To unlock the boot-loader do the following:
[*]Reboot to fastboot
[*]Run
Code:
fastboot oem unlock <your bootloader code>
[*]I then performed a factory reset with the stock recovery
[/LIST]
Verifying
To check your new oeminfo run the following command from an ADB shell:
Code:
getprop ro.hw.custPath
This should now return something like this:
Code:
/cust/hw/eu
Similarly, you can run the following fastboot command to check your oeminfo:
Code:
fastboot getvar vendorcountry
Which will report something like the following:
Code:
vendorcountry: hw/eu
Oeminfo's
Single Sim - C432
Dual Sim - C432
Warning: Use this guide at your own risk (for a final time).​
Click to expand...
Click to collapse

posedys said:
no puedes especificar mejor
no se entiende el metodo mira yo tengo un zip del oeminfo del c605 lo flasheo desde el twrp ahora crees q se pueda hacer uno asi como este facicilitaria las cosas te subo el archivo asi lo analizas
Click to expand...
Click to collapse
My translation + translated by Cambridge Online Dictionary:
"Can you not specify any better? It is not understood the method, also I have a zip of the c605 oeminfo I flashed from the twrp, now do you think that it could be done one as well as this one? Would be easier if I upload the file so you can analyze it."
It is an English only forum please be sure of that.
If you don't talk English or you can't understand what we write, please send a private message to the person you need to talk via username-->send private message.
Cheers,
AS

Hi
Can you please help me with Oeminfo C185

Eteon x said:
Hi
Can you please help me with Oeminfo C185
Click to expand...
Click to collapse
Hello,
C185 dual SIM

-Alf- said:
Hello,
C185 dual SIM
Click to expand...
Click to collapse
Yeah exactly Dual SIM

XT1792 com a bandbase desconhecida e não reconhece o chip

Estou com esse problema após instalar a stock ROM 8.1 no meu Moto G5S (Montana) XT1792. Não aparece a bandbase, IMEI desconhecido e não reconhece o chip. Não ser um problema de hardware pois estava funcionando normalmente após eu fazer o procedimento de instalação da stock ROM. Já fiz downgrade, já instalei uma custom ROM e nada, então por não saber mais o que fazer venho pedir ajuda aos membros do XDA. Desde já obrigado!
Tradução/Translation
I have this problem after installing the stock ROM 8.1 on my Moto G5S (Montana) XT1792. The bandbase does not appear, unknown IMEI and does not recognize the chip. Not to be a hardware problem as it was working normally after I did the stock ROM installation procedure. I've already downgraded, I've installed a custom ROM and nothing, so for not knowing what else to do, I'm asking XDA members for help. Thanks in advance!

same problem ( mesmo problema, amigo, aqui somente em ingles,), problema comigo bootloader esta bloqueado, ate eu sei arrumar
meu telegram @eds_Mat
Tradução/Translation
same problem (same problem, friend, here in english only), problem with me bootloader is blocked, even I know how to fix it
my telegram @eds_Mat

1Josueh said:
Estou com esse problema após instalar a stock ROM 8.1 no meu Moto G5S (Montana) XT1792. Não aparece a bandbase, IMEI desconhecido e não reconhece o chip. Não ser um problema de hardware pois estava funcionando normalmente após eu fazer o procedimento de instalação da stock ROM. Já fiz downgrade, já instalei uma custom ROM e nada, então por não saber mais o que fazer venho pedir ajuda aos membros do XDA. Desde já obrigado!
Click to expand...
Click to collapse
edsmat said:
same problem ( mesmo problema, amigo, aqui somente em ingles,), problema comigo bootloader esta bloqueado, ate eu sei arrumar
meu telegram @eds_Mat
Click to expand...
Click to collapse
Other than English languages are not allowed on xda, so please read rules of xda and follow them.

Hello people!
I found out how to recover the chip (recognize), it will be necessary to install the latest rom stock (h t t p s : / / mirrors.lolinet.com/firmware/moto), there look for MONTANA, then click OFFICIAL and find it by RETAIL (h t t p s : / / mirrors.lolinet.com/firmware/moto/montana/official/RETAIL/), perform the flash procedure after downloading the ROM (more updated with the commands below:
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 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 system system.img_sparsechunk.10
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot flash logo logo.bin
fastboot oem lock
fastboot oem lock
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 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 system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock
fastboot reboot

lopesgang said:
Hello people!
I found out how to recover the chip (recognize), it will be necessary to install the latest rom stock (h t t p s : / / mirrors.lolinet.com/firmware/moto), there look for MONTANA, then click OFFICIAL and find it by RETAIL (h t t p s : / / mirrors.lolinet.com/firmware/moto/montana/official/RETAIL/), perform the flash procedure after downloading the ROM (more updated with the commands below:
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 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 system system.img_sparsechunk.10
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot flash logo logo.bin
fastboot oem lock
fastboot oem lock
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 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 system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
Muito obrigado! Sua dica resolveu meu problema!
Tradução/Translation
Thank you very much! Your tip solved my problem!

1Josueh edsmat clewbber
Como podem observar foi adicionada tradução aos vossos posts anteriores mas esse trabalho deve ser feito por vós conforme ditam as regras do forum
Aconselho vivamente que as leiam e tirem qualquer duvida que possa existir junto da equipa de moderação!
Tradução/Translation
As you can see, translation was added to your previous posts but this work must be done by you as dictated by the forum rules.
I strongly advise you to read them and remove any doubts that may exist with the moderation team!