Database Develop

[HELP] Pi-llama

Hello, my phone is stock (BR 4.1.2) and not root and unlocked bootloader, the problem is that as I begin the process has several flaws and ends when he asks to enter recorvery continuing with the process he gets the logo motorola and no longer goes out, this I thank you.
Code:
"Activa depuracion usb en tu terminal (configuracion, opc. del desarrollador) i
nstala los drivers motorola y conecta el usb."
"Recuerda tener cargada la bateria por lo menos 50 o mas."
Pressione qualquer tecla para continuar. . .
3597 KB/s (1576781 bytes in 0.428s)
< waiting for device >
sending 'system' (102400 KB)...
OKAY [ 9.165s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 9.525s
sending 'boot' (11264 KB)...
OKAY [ 1.375s]
writing 'boot'...
FAILED (remote: Preflash validation failed)
finished. total time: 2.015s
sending 'radio' (8449 KB)...
OKAY [ 1.137s]
writing 'radio'...
OKAY [ 75.934s]
finished. total time: 77.071s
sending 'recovery' (11264 KB)...
OKAY [ 1.397s]
writing 'recovery'...
FAILED (remote: Preflash validation failed)
finished. total time: 1.763s
erasing 'cache'...
Creating EXT4 FileSystem for cache
OKAY [ 3.400s]
finished. total time: 3.400s
"Selecciona Recovery, instala Fix.zip que se encuentra en tu memoria interna."
"CUANDO TE PREGUNTE DISSABLE RECOVERY FLASH SELECCIONA -NO!"
"listo.."
Pressione qualquer tecla para continuar. . .

solution
Synk0 said:
Hello, my phone is stock (BR 4.1.2) and not root and unlocked bootloader, the problem is that as I begin the process has several flaws and ends when he asks to enter recorvery continuing with the process he gets the logo motorola and no longer goes out, this I thank you.
Code:
"Activa depuracion usb en tu terminal (configuracion, opc. del desarrollador) i
nstala los drivers motorola y conecta el usb."
"Recuerda tener cargada la bateria por lo menos 50 o mas."
Pressione qualquer tecla para continuar. . .
3597 KB/s (1576781 bytes in 0.428s)
< waiting for device >
sending 'system' (102400 KB)...
OKAY [ 9.165s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 9.525s
sending 'boot' (11264 KB)...
OKAY [ 1.375s]
writing 'boot'...
FAILED (remote: Preflash validation failed)
finished. total time: 2.015s
sending 'radio' (8449 KB)...
OKAY [ 1.137s]
writing 'radio'...
OKAY [ 75.934s]
finished. total time: 77.071s
sending 'recovery' (11264 KB)...
OKAY [ 1.397s]
writing 'recovery'...
FAILED (remote: Preflash validation failed)
finished. total time: 1.763s
erasing 'cache'...
Creating EXT4 FileSystem for cache
OKAY [ 3.400s]
finished. total time: 3.400s
"Selecciona Recovery, instala Fix.zip que se encuentra en tu memoria interna."
"CUANDO TE PREGUNTE DISSABLE RECOVERY FLASH SELECCIONA -NO!"
"listo.."
Pressione qualquer tecla para continuar. . .
Click to expand...
Click to collapse
hi bro, is a problem too weird, it happened to me once and loading the firmware fix jelly bean, you tried to run back. bat?
sorry for my bad english

max_choco said:
hi bro, is a problem too weird, it happened to me once and loading the firmware fix jelly bean, you tried to run back. bat?
sorry for my bad english
Click to expand...
Click to collapse
the problem continues after this procedure he asks to go into recovery it gets the most out soon and not only do I command the Power + Vol Down

Try to make a full data wype in the Recovery and then try again, opening the .bat file while in the android home screen and don't forget to turn on usb debugging.

The main problem is, that his Razr is not rooted and unlocked bootloader so without CWM. I guess.

I don't understand his Post to 100%, but it looks like he's not unlocked. There're only preflash validation errors, this usually happens when you try to flash an FW that doesn't match with your Phones Region. You have to be unlocked to flash EU Files (System of Pillama) on an BR XT890.
And of course, CWM won't pass, too.
Gesendet von meinem XT890 mit Tapatalk 2

HSD-Pilot said:
I don't understand his Post to 100%, but it looks like he's not unlocked. There're only preflash validation errors, this usually happens when you try to flash an FW that doesn't match with your Phones Region. You have to be unlocked to flash EU Files (System of Pillama) on an BR XT890.
And of course, CWM won't pass, too.
Gesendet von meinem XT890 mit Tapatalk 2
Click to expand...
Click to collapse
Lucki_X said:
The main problem is, that his Razr is not rooted and unlocked bootloader so without CWM. I guess.
Click to expand...
Click to collapse
If I can not unlock it because the assistants motorola say that my device is not developer site and not of assistance.
if this is the problem then I will have to put up stock rom for a while thanks to everyone who helped me.
Version System: 982.50.20.XT890.Brasil.en.BR
Version of the Baseband: SUNRISE_SMB_REV30_V2_R3_1233.C9_sec
Number of Version: 9.82l-50_SML-20.20
NOTE:if you need anything more just ask
Thx

You have to try it again. Some Users here in Germany got the same Problem. This seems to be Moto-Server related.
After some attempts they where finally able to unlock the Device.
Gesendet von meinem XT890 mit Tapatalk 2

http://batakang.com/ftp/RAZRi/HomemadeFastboots/91.2.26001.Retail.en.EU.zip check working my cell
Sent from my XT890 using xda premium

@zipi23 - My cell phone is with the bootloader locked and can not unlock because it appears this message "your device does not qualify for unlocking bootloader and I could not make this homemade.

Synk0 said:
@zipi23 - My cell phone is with the bootloader locked and can not unlock because it appears this message "your device does not qualify for unlocking bootloader and I could not make this homemade.
Click to expand...
Click to collapse
god ... brother did not read the guide?? clarify very well need the bootloader unlocked
Enviado desde mi XT890 usando Tapatalk 2

max_choco said:
god ... brother did not read the guide?? clarify very well need the bootloader unlocked
Enviado desde mi XT890 usando Tapatalk 2
Click to expand...
Click to collapse
sorry :/ I could not quite understand What did it was written

I managed to unlock the bootloader, updating the SML SML 20 to 28, Many thanks for your help and attention.
Send: Razr I Tapatalk 4

[HELP] Moto G2 Hard Brick (XT1068)

Hello, to start my English is very bad so I'll try to explain what's going on with my device.
I bought the XT1068 defective, apparently in the photos would be simple the process, I would install the ROM stock and it would remove the message bootloader and ready. I've tried absolutely everything
It appears the error "Invalid boot image header!"
If I try for a ROM on it it gives some errors, for example "failed to validate ftm image that means its not fih mode load and validate boot image" other "version is downgraded primary_gtp" (this when I tried for the ROM 4.4.4 ).
When I try to install the ROM on mfastboot so it appears these errors "C: \ Users \ PEDRO \ Desktop \ adb> mfastboot flash partition gpt.bin
Reported target max download size of 536870912 bytes
sending 'partition' (32 KB) ...
OKAY [0.050s]
writing 'partition' ...
(Bootloader) Preflash validation failed.
What do I do ?? please help me
---------text in portuguese----------
Olá, pra começar meu ingles é péssimo então vou tentar explicar o que está acontecendo com meu aparelho.
Eu comprei o XT1068 com defeito, aparentemente nas fotos seria simples o processo, eu instalaria a ROM stock nele e tiraria a mensagem de bootloader e pronto. Já tentei absolutamente de tudo
Ele aparece o erro "Invalid boot image header !"
Se eu tento por uma ROM nele ele dá alguns erros, por exemplo "failed to validate ftm image that means its not fih mode load and validate boot image" outro "version downgraded for primary_gtp" ( isso quando eu tentei por a ROM 4.4.4 ).
Quando vou tentar instalar a ROM no modo mfastboot ele aparece esses erros "C:\Users\PEDRO\Desktop\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Preflash validation failed.
O que eu faço ?? por favor me ajudem

Stuck in [Preso em] Fastboot Mode

Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?

@alanduda65 Please use the English language!
XDA Forum Rules:
Spoiler: Rule No. 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.

alanduda65 said:
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
Click to expand...
Click to collapse
Hi!
Same thing here, Asus zenfone 5 ZE620KL, after trying to install twrp, phone got stuck in fastboot mode, can't get anywhere else, not recovery or boot to OS
Tried on AMD pc and Intel too, any ideas on how to get the phone working again?

You'll have to use QFIL to unbrick the phone. A quick google should show you how to do this

asusasus55 said:
You'll have to use QFIL to unbrick the phone. A quick google should show you how to do this
Click to expand...
Click to collapse
Do we really need to open the back?

alanduda65 said:
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
Click to expand...
Click to collapse
Hey guy,
My phone was running the rom "UL-ASUS_X00QD-ASUS-AOSP-17.0615.2005.25-1.1.1-user.zip" (downloaded from Asus Web). I tried to install the TWRP ver 3.3.1 unofficial and my phone was stuck on the fastboot mode only.
After a lot of searching on how to fix the issue, I didn't change anything and almost gave up, until I've read this thread.
My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE???
These are what I did to get the phone into the recovery mode:
1. Extract the rom zip file that my phone was running on.
2. Copy the file boot.img to adb folder.
3. On PC, at adb folder enter CMD, connect the phone then type
fastboot -w
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot recovery
4. After that, my phone can be booted into the recovery mode.
Hope you can solve the same problem as me.
Bye bye ...

ADB or fastboot doesn't accept any flash commands

Any command I try to put to flash the device it crashes and doesn't complete. I've tried recovery flash, boot, bootloader and none of them finish sending the file. I've already downloaded other files from other sites and it still doesn't send.
The device doesn't start recovery mode and I need to change roms.
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot devices
0047929849 fastboot
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot getvar max-sparse-size
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: 0.004s
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot oem fb_mode_set
(bootloader) slot-count-size: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'fb_mode_setfixes' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.006s
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot flash partition gpt.bin
(bootloader) slot-countxes: not found
(bootloader) slot-suf: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'partition' (37 KB)...
-----------------------------------------------------------------------------
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>adb devices
List of devices attached
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot devices
0047929849 fastboot
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot flash recovery twrp-3.4.0-beckham-v2.img
target reported max download size of 536870912 bytes
sending 'recovery' (33308 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.004s
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot flash recovery twrp-3.4.0-beckham-v2.img
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'recovery' (33308 KB)...

I had similar problem with old ROM, device fails to receive any file (for boot or flash); the solution was to update ROM using it's internal update.

MagusWRM said:
I had similar problem with old ROM, device fails to receive any file (for boot or flash); the solution was to update ROM using it's internal update.
Click to expand...
Click to collapse
could you tell me how i do this update?

kauankas said:
could you tell me how i do this update?
Click to expand...
Click to collapse
Configurations > System > Advanced > System update
But there are a chance that there is no update avaiable; in that case you can try ADB after boot: enable developer mod and then activate ADB from there, try the commands again.
Spoiler: Huehuehue
Configurações > Sistema > Avançado > Atualizações do sistema
Há grandes chances de não ter atualização disponível; nesse caso recomendo tentar ADB pelo sistema (depois do boot): ativar modo desenvolvedor e de lá ativar ADB; tentar os comandos novamente.

MagusWRM said:
Configurations > System > Advanced > System update
But there are a chance that there is no update avaiable; in that case you can try ADB after boot: enable developer mod and then activate ADB from there, try the commands again.
Spoiler: Huehuehue
Configurações > Sistema > Avançado > Atualizações do sistema
Há grandes chances de não ter atualização disponível; nesse caso recomendo tentar ADB pelo sistema (depois do boot): ativar modo desenvolvedor e de lá ativar ADB; tentar os comandos novamente.
Click to expand...
Click to collapse
There's only one problem, the device after the lineageOS update doesn't turn on anymore, it gets stuck in the boot animation. huehue

Do you have an AMD processor? Several devices do not like AMD processors for some reason. In my experience they have anything from Nextbit/Razer, Moto Z3 series, and Essential Phone PH-1. They all work fine for me on any Intel based processor.

christian.farmerf said:
Do you have an AMD processor? Several devices do not like AMD processors for some reason. In my experience they have anything from Nextbit/Razer, Moto Z3 series, and Essential Phone PH-1. They all work fine for me on any Intel based processor.
Click to expand...
Click to collapse
You have no idea what you're talking about. I've rooted/rom'd hundreds of devices, including a few dozen RP2's, PH-1's, Pixel's, and International Samsungs... all on an amd cpu. Root and Rom doesn't care AMD or Intel. Something was just wrong with your setup.

KaptinBoxxi said:
You have no idea what you're talking about. I've rooted/rom'd hundreds of devices, including a few dozen RP2's, PH-1's, Pixel's, and International Samsungs... all on an amd cpu. Root and Rom doesn't care AMD or Intel. Something was just wrong with your setup.
Click to expand...
Click to collapse
I have every idea what i'm talking about. Older bootloader versions on some phones don't work by default with an AMD CPU. There is a fix for Windows users that just adds a few registry keys but linux users like myself are more or less out of luck. I suggest the OP and yourself check out this thread: here
Boom roasted.

christian.farmerf said:
Do you have an AMD processor? Several devices do not like AMD processors for some reason. In my experience they have anything from Nextbit/Razer, Moto Z3 series, and Essential Phone PH-1. They all work fine for me on any Intel based processor.
Click to expand...
Click to collapse
por incrivel que seja acabei de fazer no meu celular, pelo meu desktop que é um amd não estava indo nem com reza, mudei para note com intel e deu certo

GUIDE: How to fix black screen after flashing a custom rom / GUÍA: Como solucionar la pantalla negra al flashear una custom rom

I'm going to give a solution for this problem (Note: I don't know if there is another solution, please if you know another fix post it here). I'm doing this post because i had this problem and there wasn't any guide on how to fix it, but wil too much patience and experimenting with my AGS2-W09 i could finally fix it ‍. I'm going to post this on English and Spanish. I'm not a developer, I just want to share this with all that may have this problem, hope this work for you . / Voy a dar una solución para este problema (Nota: no sé si hay otra solución, por favor, si conoce otra solución, publíquela aquí). Estoy haciendo esta publicación porque tuve este problema y no había ninguna guía sobre cómo solucionarlo, pero con demasiada paciencia y experimentando con mi AGS2-W09, finalmente pude solucionarlo. Voy a publicar esto en inglés y español. No soy un desarrollador, solo quiero compartir esto con todos los que puedan tener este problema, espero que esto os funcione también
* First of all, we have to download some things:
- PotatoNV: https://github.com/mashed-potatoes/PotatoNV
- Hisuite Proxy v3.3.0: https://github.com/ProfessorJTJ/HISuite-Proxy/releases
- Huawei Update Extractor (v0.9.9.5): You can download it on this post on XDA
- Huawei test point drivers: https://androidfilehost.com/?fid=14943124697586361242
- Firmware files: Get them on Huawei Firm Finder
- Minimal ADB and Fastboot Tool (V1.4.3): https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
- 7-zip: https://7-zip.org/
* Process:
1.- Ok, first we have to download, extract and execute Hisuite Proxy, because you'll need it to be able to download the firmware (It's important to keep it open)
{
"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"
}
2.- Now, we have to download the firmware for our exact model. I will be using the firmware for the AGS2-W09 model but it work for AGS2-L09 too. We're going to get these files from the Huawei Firm Finder site. HERE, there is a list with all region codes
We have to type our exact model on "Phone Model" ( As I said, i'll be using the AGS2-W09 ). On region..., well our region XD, I'll be using the C432 region code.
Now, click on the three dots on the last firmware avaliable ( I'll be using AGS2-W09 8.0.0.328(OCEC432) ). Click on "Check Rom Status" and it should say "Approved for Installation", if it doen't say that, try another firmware.
If it said Approved, we can continue by clicking on "Download Rom" an downloading all files. It should say something like this:
3.- Extracting Process:
Now, I hardly reccomend to use 7-zip, because WinRAR sometimes cause problems at this step.
Extract update.zip on the folder with the same name and extract update_full_XXX-XXX_xx_xx.zip on a folder with same name. ( For example my update_full file is update_full_AGS2-W09_hw_eu)
Now, go into the update folder, right click on UPDATE.APP and extract the file: 7.oeminfo.img. Flash it onto the tablet using fastboot flash oeminfo (drag here that oeminfo.img file)
4.- Huawei Update Extractor:
Now open Huawei Update Extractor, go to settings and uncheck Verify header checksum and verify file checksum. It should look like this:
Now go back to Extract and on update file, select the UPDATE.APP from the update folder:
Right click on any of them and select "Extract All", then create a folder where you want and extract these files there. After extracting them, go back to Extract and select the UPDATE.APP on the update_full_XXX-XXX_xx_xx folder (In my case it's update_full_AGS2-W09_hw_eu) and choose the UPDATE.APP, then extract them the same way as you did with the other UPDATE.APP, but you have to extract this UPDATE.APP on the same folder you've extracted the other update.app.
5.- FASTBOOT
Now, we are ready to flash all IMG files we've extracted on the tablet. We have to do this one by one in order, I know there are a lot of files but I did that and worked for me. NOTE: There some files that it'll say that it couldn't be flashed but it's not a problem, just continue on flashing. FOR EXAMPLE: fastboot flash cache (drag and drop cache.img here) or fastboot flash recovery_ramdisk (drag and drop recovery_ramdis here)
6.- FINISHING PROCESS
When you finish flashing all files just do fastboot reboot and it should turn on. At this point I recommend you installing a custom rom like LineageOS, LeaOS or crdroid. List of compatible roms for this tablet
I hope it works for you as well, like I said earlier I'm not a developer, I'm just a person who likes technology and had this problem. I just share this because it helped me and because I didn't see any post here explaining something. As I said if you now another fix feel free to comment. / Espero que te funcione también a ti, como dije anteriormente no soy un desarrollador, soy solo una personal que le gusta la tecnología y tuve este problema. Comparto esto porque me ayudó y porque no vi ningún post explicando porqué pasa o como arreglarlo. Como dije si sabes de otra solución, por favor coméntalo.
I'll add the Spanish steps soon. / Añadiré los pasos en Español pronto.

(Reserved)

(Reserved)

Is there an order that these need to be flashed in? I have 33 files (ignoring the header files) and I don't know all of the partitions that the files need to be flashed to. This is the list I have so far, do I need other files and do I have the correct partitions?
Code:
fastboot flash cache CACHE.img
fastboot flash crc CRC.img
fastboot flash curver CURVER.img
fastboot flash cust CUST.img
fastboot flash dts DTS.img
fastboot flash erecovery_kernel ERECOVERY_KERNE.img
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img
fastboot flash erecovery_vbmet ERECOVERY_VBMET.img
fastboot flash erecovery_vendor ERECOVERY_VENDO.img
fastboot flash fastboot FASTBOOT.img
fastboot flash fw_hifi FW_HIFI.img
fastboot flash fw_lpm3 FW_LPM3.img
fastboot flash ptable HISIUFS_GPT.img
fastboot flash kernel KERNEL.img
fastboot flash odm ODM.img
fastboot flash product PRODUCT.img
fastboot flash ramdisk RAMDISK.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash sensorhub SENSORHUB.img
fastboot flash sha256rsa SHA256RSA.img
fastboot flash system SYSTEM.img
fastboot flash trustfirmware TRUSTFIRMWARE.img
fastboot flash vbmeta VBMETA.img
fastboot flash vendor VENDOR.img
fastboot flash version VERSION.img
fastboot flash verlist VERLIST.img
fastboot flash product PRODUCT.img
fastboot flash xloader XLOADER.img

You have to flash them on the same order they have extracted. Example: first cache, second CRC, etc. And the partition hace the same name as the IMG files. Example: fastboot flash xloader xloader

Thx bro very nice tuto . All works for me

woofer50 said:
Thx bro very nice tuto . All works for me
Click to expand...
Click to collapse
Glad it helps

The only part of all the steps that I don't understand is the part "5.- FASTBOOT"
Can you explain how this step has to be done and the programs that have to be used?

Kaparroz said:
The only part of all the steps that I don't understand is the part "5.- FASTBOOT"
Can you explain how this step has to be done and the programs that have to be used?
Click to expand...
Click to collapse
You have to use the minimal adb and fastboot tool to flash all the .img files.

Thank you very much, I'll try it.
I have other Huawei devices with locked Bootloader, I managed to update from download mode without any problem, with the first Firewall downloaded. But this AGS-L09 is burning me to excess and I have never achieved anything until now. There may be some version of Firewall with Android 7.0 that can be installed from download mode from MicroSd. I have two AGS-L09 one with Android 7.0 and one with Android 8.0 which includes a lot of unnecessary problems.