This is my problem:
I flash by MIFlash the official rom of A9 March on MIA3 and I forgot to untick the "flash_all_lock.bat".
The problem is that it was in slot b and now I can't unlock the bootloader.
--------------------------------------------------
Este es mi problema:
Flasee por MiFlash la Rom oficial de A9 de Marzo y me olvide de destildar el "flash_all_lock.bat".
El problema es que estaba en el slot b y ahora no puedo desbloquear el bootloader.
Code:
C:\Users\X7REM\Desktop\MI A3\Twrp para Roms 1\platform-tools> fastboot set_active a
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
C:\Users\X7REM\Desktop\MI A3\Twrp para Roms 1\platform-tools>fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
C:\Users\X7REM\Desktop\MI A3\Twrp para Roms 1\platform-tools>fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
I need help, i'm desperate
You must use EDL mode with an authorized account - either visit a service center or use online one which will do it remotely.
Same thing happened to me but I was able to unlock bootloader again
authorized account
_mysiak_ said:
You must use EDL mode with an authorized account - either visit a service center or use online one which will do it remotely.
Click to expand...
Click to collapse
You know any reliable user with an authorized account?
Thanks for answering me
fastboot continue
resuming boot OKAY [ 0.335s]
Finished. Total time: 0.337s
---------- Post added at 04:01 PM ---------- Previous post was at 03:54 PM ----------
X7REME13 said:
This is my problem:
I flash by MIFlash the official rom of A9 March on MIA3 and I forgot to untick the "flash_all_lock.bat".
The problem is that it was in slot b and now I can't unlock the bootloader.
--------------------------------------------------
Este es mi problema:
Flasee por MiFlash la Rom oficial de A9 de Marzo y me olvide de destildar el "flash_all_lock.bat".
El problema es que estaba en el slot b y ahora no puedo desbloquear el bootloader.
Code:
C:\Users\X7REM\Desktop\MI A3\Twrp para Roms 1\platform-tools> fastboot set_active a
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
C:\Users\X7REM\Desktop\MI A3\Twrp para Roms 1\platform-tools>fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
C:\Users\X7REM\Desktop\MI A3\Twrp para Roms 1\platform-tools>fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
I need help, i'm desperate
Click to expand...
Click to collapse
primero envio este comando fastboot oem device-info
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
Finished. Total time: 0.009s
si le aparece de esa manera, envia el comando fastboot flashing unlock
el movil se reinicia y debe decir erasing
luego envia el comando fastboot getvar current-slot
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
luego si envia el comando de fastboot set_active a
le sale la confirmación del cambio
fastboot continue
cristianodk said:
fastboot continue
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
Finished. Total time: 0.009s
fastboot continue
Click to expand...
Click to collapse
Nop, nada de eso funciona...
Code:
C:\Users\X7REM\Desktop\ADB-MINIMAL>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Users\X7REM\Desktop\ADB-MINIMAL>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.006s
C:\Users\X7REM\Desktop\ADB-MINIMAL>fastboot set_active a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State
)
finished. total time: 0.010s
C:\Users\X7REM\Desktop\ADB-MINIMAL>fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.008s
C:\Users\X7REM\Desktop\ADB-MINIMAL>
Ahi probe todos los comandos, no sabia la existencia del comando "Fastboot continue" fue la primera vez que la use y fue bastante informativos los resultados que arrojo.
Lamentablemente no pude resolverlo, pero muchas gracias por escribirme.
X7REME13 said:
You know any reliable user with an authorized account?
Thanks for answering me
Click to expand...
Click to collapse
It's paid service, you will not find anyone doing it for free. Just use some online service of your preference with good reputation and reviews.
X7REME13 said:
Nop, nada de eso funciona...
Code:
C:\Users\X7REM\Desktop\ADB-MINIMAL>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Users\X7REM\Desktop\ADB-MINIMAL>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.006s
C:\Users\X7REM\Desktop\ADB-MINIMAL>fastboot set_active a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State
)
finished. total time: 0.010s
C:\Users\X7REM\Desktop\ADB-MINIMAL>fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.008s
C:\Users\X7REM\Desktop\ADB-MINIMAL>
Ahi probe todos los comandos, no sabia la existencia del comando "Fastboot continue" fue la primera vez que la use y fue bastante informativos los resultados que arrojo.
Lamentablemente no pude resolverlo, pero muchas gracias por escribirme.
Click to expand...
Click to collapse
que extraño yo tenia el mismo error, y se soluciono de esa manera
compa pregunta? que version esta flasheando o flasheo por miflash?
me refiero al firmware 10.3.4? yo siempre flasheo esta laurel_sprout_global_images_V10.3.4.0.PFQMIXM_9.0
eso que subi a la 1o por ota oficial pero por mucho lagg bajo siempre a esa laurel_sprout_global_images_V10.3.4.0.PFQMIXM_9.0
cristianodk said:
que extraño yo tenia el mismo error, y se soluciono de esa manera
compa pregunta? que version esta flasheando o flasheo por miflash?
me refiero al firmware 10.3.4? yo siempre flasheo esta laurel_sprout_global_images_V10.3.4.0.PFQMIXM_9.0
eso que subi a la 1o por ota oficial pero por mucho lagg bajo siempre a esa laurel_sprout_global_images_V10.3.4.0.PFQMIXM_9.0
Click to expand...
Click to collapse
La version que flashee yo es esta:
laurel_sprout_global_images_V10.3.13.0.PFQMIXM_9.0
flashear la qe le comento y luego intentar hacer de nuevo lo de los comandos
Related
What happens is that any command I make in fastboot sends me
...
FAILED (remote: unknown command)
every command even
fastboot oem get-bootinfo
send me the same I do not know what to do, I'm a little desperate
Why even my cell phone does not pick up a signal at the moment
I hope you can support me .... thanks in advance
Lo que pasa es que cualquier comando que hago en modo fastboot me manda
...
FAILED (remote: unknown command)
todo comando incluso
fastboot oem get-bootinfo
me manda el mismo no se que hacer estoy algo desperado
por que incluso mi celular no levanta señal en este momento
espero me puedan apoyar....gracias de antemano
It looks like your computer don't have installed the fasboot commands, if you use Windows, you can search the fastboot and adb installers.
Parece que tu computadora no tiene instalado fastboot, podes buscar en el foro si tenes Windows para instalar adb y fastboot y poder ejecutar desde la terminal
Enviado desde mi Xperia X corriendo Sailfish OS
This Tutorial I'm doing to get root on our device, I know there are several similar threads, so I gathered the information from them, I've done this post to achieve it in a way easier and faster, without the need to search for thread by thread.
First of all you have to download the files; I leave the official threads, followed by their download links
ADB
Thread: Minimal ADB and Fastboot
ADB Portable
Drivers Motorola
Drivers
Boot Logo
Thread: Remove message "Unlocked Bootloader" of your Moto G6/G6 Plus
Logo White.bin
Automatic BootLogo Installer (Black and White)
TWRP & Magisk
Download TWRP ejecutable
Magisk
Unlock Boot Loader
Thread: Unlock Bootloader
Motorola Unlock
Steps:
¬ Download the files, (Put them in an accessible and fast place, the desk would be good)
¬ Unzip the archives
¬ Copy the files to a single folder (where is the adb)
¬ We open the cmd (you execute the app that is in the folder)
¬ You connect the phone in Quick Start mode (Vol minus + off)
¬ Write this but without the quotes "fastboot oem get_unlock_data"
¬ You will see something in the cmd, copy it in the notebook, Pegua the 5 output lines in a continuous string without (boot manager) or 'INFO' or blanks. It should look like this: 0A40040192024205 # 4C4D355631323030373731363031303332323239 # BD008A672BA4746C2CE02328A2AC0C39F951A3E5 # 1F5328000200000000000000000000000000
¬ We go to the Motorola page, we start session.
¬ We paste the code in step number 6, and we give the blue button
¬ In case it works, we accept terms and conditions
¬ You open your email (With which you started session) you should have received an email from Motorola with a code
¬ Now go back to the cmd and paste this: fastboot oem unlock "you paste your code that came" and hit enter, and put the same again to confirm
¬ Restarts. once turned on, you pay and put in quick start mode
¬ Restarts. Once turned on, you stick it and put it in quick start mode
¬ You execute "white or black" .bat according to what you want to patch the Bootloader notice Unlocked
¬ Wait for me to turn on
¬ You configure it
¬ If you want Root:
Put the Magisk Zip in the Internal Memory
Put the phone in Fastboot mode and connect it to the PC
You execute the "TWRP Executable"
Install the Zip
To install xposed:
Open the Magisk app
Find the module
Install it
Restart
You already have Root
Español
Este Tutorial lo estoy haciendo para lograr obtener el Root en nuestro dispositivo, Se que hay varios hilos similares, así que reuní la información de ellos, he hice este post para lograr hacerlo de una manera más fácil y rápida, sin necesidad de buscar hilo por hilo.
Primero que nada hay que descargar los archivos; les dejo los hilos oficiales, seguidos de sus enlaces de descarga
ADB
Hilo: Minimal ADB and Fastboot
ADB Portable
Drivers Motorola
Drivers
Boot Logo
Hilo: Remove message "Unlocked Bootloader" of your Moto G6/G6 Plus
Descargar Logo Blanco
Instalador Automatico BootLogo (Blanco y Negro)
TWRP & Magisk
Download TWRP ejecutable
Magisk
Liberar el Boot Loader
Hilo: Unlock Bootloader
Motorola Unlock
Pasos:
¬ Descargar los archivos, (Ponerlos en un lugar accesible y rápido, el escritorio sería bueno)
¬ Descomprimimos los archivos("adb")
¬ Abrimos el cmd (ejecutas la app que esta en la carpeta)
¬ Conectas el telefono en modo Arranque Rápido (Vol menos + off)
¬ Escribe esto pero sin las comillas "fastboot oem get_unlock_data"
¬ Te va aparecera algo en el cmd, copialo en el bloc de notas, Pegua las 5 líneas de salida en una cadena continua sin (gestor de arranque) o 'INFO' o espacios en blanco. Debe verse así: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
¬ Nos vamos a la Pág de Motorola, iniciamos sesión.
¬ Pegamos el código en el paso número 6, y le damos al botón azul
¬ En dado caso que funcione aceptamos términos y condiciones
¬ Abres tu correo (Con el que iniciaste sesión) te debió llegar un correo de Motorola con un código
¬ Ahora Volvemos al cmd y pegamos esto: fastboot oem unlock " pegas tu código que te llegó" y le das enter, y vuelves a poner lo mismo para confirmar
¬ Reinicias. una vez encendido, lo pegas y pones en modo arranque rápido
¬ Ejecutas "white o black".bat según lo que desees para así parchar el aviso de Bootloader Desbloqueado
¬ Esperas a que encienda
¬ Lo configuras
¬ Si deseas Root:
Poner el Zip de Magisk en la Memoria Interna
Poner el telefono en Modo fastboot y lo conectas a la pc
Ejecutas el "TWRP Ejecutable"
Instalas el Zip
Para instalar xposed:
Abra la app de Magisk
Busque el modulo
Instalelo
Reinicie
Ya tienes Root
Thread closed...
You were requested to read the FORUM RULES when you registered.
This Rule applies in this case:
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).
Thread can be re-opened if you provide an English translation.
Hi,
after root, etc. this device can i change some settings inside the kernel? like cpu freq, ksm, or others?
Thank You
FYI, this post should be in the Moto G6 Guides, News & Discussion section of the forums.
Hi everyone, i´m trying to flash boot and i get this error using fastboot and mfastboot:
target max-sparse-size: 256MB
sending 'boot' (18992 KB)...
OKAY [ 0.505s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.518s
Someone can help me? plz
Pandarenz said:
Hi everyone, i´m trying to flash boot and i get this error using fastboot and mfastboot:
target max-sparse-size: 256MB
sending 'boot' (18992 KB)...
OKAY [ 0.505s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.518s
Someone can help me? plz
Click to expand...
Click to collapse
You unlocked your bootloader first right?
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
You unlocked your bootloader first right?
Click to expand...
Click to collapse
Yes bro, I tried to flash the patched boot after unlock the bootloader and the same message appeared
Please can you show me how to do for moto g6 (ALI)
can't root motorola g6 plus (xt-1926-3)
I have a Motorola moto g6 plus (XT1926-3). And i've been trying to root it. I'm trying to unlock my bootloader but , whenever i go into fastboot mode.
Suddenly my phone isn't detected by either fastboot or adb. When i'm using my phone normally it gets detected by adb and not fastboot. I have tried to install the usb drivers by installing Motorola device manager but, i hear a Windows error sound when it gets to step 2 and just hangs on the last few percentile of step 2. I also tried to install the drivers from a site called Motorolausbdriver but then the installation hangs at about 60%. To anyone willing to help me, I thank you from the bottom of my heart.
RABBALQAMAR said:
Please can you show me how to do for moto g6 (ALI)
Click to expand...
Click to collapse
Update the Post, it should work for all variants of the Moto g6, the only thing, find a twrp for your device to be able to root
koningboy18 said:
I have a Motorola moto g6 plus (XT1926-3). And i've been trying to root it. I'm trying to unlock my bootloader but , whenever i go into fastboot mode.
Suddenly my phone isn't detected by either fastboot or adb. When i'm using my phone normally it gets detected by adb and not fastboot. I have tried to install the usb drivers by installing Motorola device manager but, i hear a Windows error sound when it gets to step 2 and just hangs on the last few percentile of step 2. I also tried to install the drivers from a site called Motorolausbdriver but then the installation hangs at about 60%. To anyone willing to help me, I thank you from the bottom of my heart.
Click to expand...
Click to collapse
Many times it's Windows problem, try another PC, OR create another user with administrator privileges and retry
sorry to answer so far, but I did not have my pc at hand
Does this guide still work?
I'm planning to buy an G6+. I'd also like to know if on any of this steps it performs a factory reset (wipe Data)?
Thanks
Mod Edit:
Please post in English. If a second language is needed, post it below the English translation, as I did here.
Thank you.
Por favor publicar en Inglés. Si se necesita un segundo idioma, publíquelo debajo de la traducción al inglés, como hice aquí.
Gracias.
hello good this is my first post the truth is not much but I need help: crying: I have my motorcycle z which was being updated and turned off no longer turn on anything and not turn on to put it in fastboot mode only sounds when I connect to the pc and nothing else help please I already try flashbat or something like that but it gives me error does not work either
give me this error
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 3.008] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 3.009] Check qboot_log.txt for more details
[ 3.010] Total time: 3.013s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
o si no este
Motorola qboot utility version 3.37
[ -0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 2375 (0x947)
[ 0.005] ...cpu.sn = 3567941557 (0xd4aa77b5)
[ 0.006] Opening singleimage
[ 0.008] Loading package
[ 0.017] ...filename = singleimage.pkg.xml
[ 0.022] Loading programmer
[ 0.024] ...filename = programmer.elf
[ 0.024] Sending programmer
[ 0.605] Handling things over to programmer
[ 0.610] Identifying storage type
[ 0.615] Waiting for firehose to get ready
[ 36.903] ReadFile() failed, GetLastError()=0
[ 62.350] Could not determine storage type. Assuming eMMC...
[ 62.350] Identifying CPU version
[ 62.362] Waiting for firehose to get ready
[123.499] Waiting for firehose to get ready
[184.825] ...MSM8996 unknown
[184.825] Determining target secure state
[184.825] Waiting for firehose to get ready
[246.522] ...secure = no
[246.768] Initializing storage
[246.777] Waiting for firehose to get ready
[308.102] Configuring device...
[308.102] Waiting for firehose to get ready
[369.168] Waiting for firehose to get ready
[429.524] Waiting for firehose to get ready
[490.939] Waiting for firehose to get ready
[552.025] Initializing storage
[552.255] Waiting for firehose to get ready
[614.280] Configuring device...
[614.417] Waiting for firehose to get ready
[675.911] Waiting for firehose to get ready
[737.245] Waiting for firehose to get ready
[798.434] Waiting for firehose to get ready
[806.385] ReadFile() failed, GetLastError()=0
[806.389] ReadFile() failed, GetLastError()=0
[859.687] Waiting for firehose to get ready
[920.977] Configuring device...
[920.984] Waiting for firehose to get ready
[982.670] Waiting for firehose to get ready
[1044.363] Waiting for firehose to get ready
[1105.525] Waiting for firehose to get ready
[1166.742] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[1166.742] Check qboot_log.txt for more details
[1166.742] Total time: 1166.751s
[1166.742] There were some hiccups in backup and restore.
[1166.742] Please save the following files and see a Bootloader member.
[1166.742] 1) ./qboot_log.txt
[1166.742] 2) ./backup_0xD4AA77B5_2018-09-06_212807.img
[1166.742]
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
if someone can help me please I would appreciate it :RE
Se postea en inglés en el foro, por otro lado actualizando a qué versión estabas? Y aún puedes acceder a fastboot? Desbloqueaste bootloader?
Please, post in english on the forum, for another way,for what version are you upgrading it?, and can you still access to the fastboot mode? Did you unlock the bootloader?
eLaDiio said:
Se postea en inglés en el foro, por otro lado actualizando a qué versión estabas? Y aún puedes acceder a fastboot? Desbloqueaste bootloader?
Click to expand...
Click to collapse
no puedo acceder a fastboot y si tenia desbloqueado el bootloader directamente el telefono se apago cuando se actualizaba y solo quedo en eso no hace nada mas que la pantalla en negro tenia version 8 y quise poner 7 y funciono bien hasta que se actualizo y bueno sucedio lo dicho
eLaDiio said:
Se postea en inglés en el foro, por otro lado actualizando a qué versión estabas? Y aún puedes acceder a fastboot? Desbloqueaste bootloader?
Click to expand...
Click to collapse
Addiction1993 said:
no puedo acceder a fastboot y si tenia desbloqueado el bootloader directamente el telefono se apago cuando se actualizaba y solo quedo en eso no hace nada mas que la pantalla en negro tenia version 8 y quise poner 7 y funciono bien hasta que se actualizo y bueno sucedio lo dicho
Click to expand...
Click to collapse
Please post in English. If a second language is needed, post it below the English translation, as I did here.
Thank you.
Por favor publicar en Inglés. Si se necesita un segundo idioma, publíquelo debajo de la traducción al inglés, como hice aquí.
Gracias.
hola, necesito que me indiques que versión tenías cuando intentaste actualizar, y a qué versión estabas actualizando cuando te paso eso.
Hello, I need you to tell me what version you had when trying to update, and what version is updating when I pass that.
what happened is that I made a downgrade and updated via ota then the team died now it's just a cute adornment nothing before doing the downgrade was android 8
Addiction1993 said:
what happened is that I made a downgrade and updated via ota then the team died now it's just a cute adornment nothing before doing the downgrade was android 8
Click to expand...
Click to collapse
ok here in the forum there is someone who published a blankflash to recover from version 8 of android, it happened to me the same. If your computer is still recognized by the computer, you do not have to worry about anything, it still has a solution, it's just a question of looking for a bit and being calm. leave later to get home and find the files that are needed for you to make it work. but just look for here the blankflash for the version of android that you had
ok aqui por el foro hay alguien que publico un blankflash para recuperar desde la version 8 de android, a mi me paso lo mismo. si tu equipo aun lo reconoce la computadora no hay que preocuparse por nada, aun tiene solucion, solo es cuestion de buscar un poco y tener calma. deja mas tarde llegar a casa y buscar los archivos que se necesitan para que lo puedas hacer funcionar. pero igual busca por aqui el blankflash para la version de android que tenias :good:
My device battery get empty during the update :crying:
my device bricked and i need help
bootloader locked
frp locked
please i need help
sorry for my bad english i am from syria :crying:
---------------------------------
(bootloader) ANE-LX1
OKAY [ 0.006s]
finished. total time: 0.010s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.158(C185)
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.008s
Precio a vol abajo y conecta el cargador no sueltes el botón hasta q apagarse a el menú forzado de undape
Enviado desde mi ANE-LX3 mediante Tapatalk
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
Preciona volumen abajo y no sueltes y conectas el cable conectado a la pared y sin soltar el botón esperas hasta que habra menú de undape
Press volume down and do not release and connect the cable connected to the wall and without releasing the button you wait until there will be undape menu
Enviado desde mi ANE-LX3 mediante Tapatalk
---------- Post added at 05:03 PM ---------- Previous post was at 05:02 PM ----------
Press volume down and do not release and connect the cable connected to the wall and without releasing the button you wait until there will be undape menu
Enviado desde mi ANE-LX3 mediante Tapatalk
posedys said:
Precio a vol abajo y conecta el cargador no sueltes el botón hasta q apagarse a el menú forzado de undape
Enviado desde mi ANE-LX3 mediante Tapatalk
Click to expand...
Click to collapse
i tried erecovery
and tried UPDATE.APP in dload folder in my sdcard (exfat) and not working
i tried FullOTA-MF ANE-LX1C185B158 (8.0.0.158) update.zip and the device stucks at 5% and say faild
you need to use one fo thease files (in dload folder need to be .zip not app) only extract downloaded zip file, then from software folder copy dload folder to sd card
https://androidhost.ru/cAw
or
https://androidhost.ru/cyy
sd card --> dload (folder) --> ANE-L01_hw_eu (folder) and ANE-L21_hw_eu (folder) and update_sd.zip (zip)
but, for you will be different folder names hw_eu will be hw_meafnaf (becasue eu is for c432 and hw/meafnaf is for c185)
Hola disculpen yo tengo un problema , al intentar desbloquear el OEM desde cmd en mi computadora me dice : oem unlock is not allowed y mi dispositivo está brickeado para poder activar el oem desde el OS,algun consejo ? o realmente ya murió ? también intenté flashearlo con el Mi flash tool pero al intentarlo me dice "error : erasing boot failed, maybe the device is locked"
//Hi, sorry, I have a problem, when I try to unlock the OEM from cmd on my computer it says: oem unlock is not allowedand my device is bricked to be able to activate the em from the OS, some advice? or really already died? I also tried to flash it with the My Flash tool but when I try it it says "error: erasing boot failed, maybe the device is locked"
AetherJared720 said:
Hola disculpen yo tengo un problema , al intentar desbloquear el OEM desde cmd en mi computadora me dice : oem unlock is not allowed y mi dispositivo está brickeado para poder activar el oem desde el OS,algun consejo ? o realmente ya murió ? también intenté flashearlo con el Mi flash tool pero al intentarlo me dice "error : erasing boot failed, maybe the device is locked"
//Hi, sorry, I have a problem, when I try to unlock the OEM from cmd on my computer it says: oem unlock is not allowedand my device is bricked to be able to activate the em from the OS, some advice? or really already died? I also tried to flash it with the My Flash tool but when I try it it says "error: erasing boot failed, maybe the device is locked"
Click to expand...
Click to collapse
What version of rom ?
laugeek57 said:
What version of rom ?
Click to expand...
Click to collapse
I think it's Android Oreo 8.1 because he's the one who tried to install him before the error ,so he is not dead yet?
And forgive me if my English is not good, I'm using the google translator
AetherJared720 said:
I think it's Android Oreo 8.1 because he's the one who tried to install him before the error ,so he is not dead yet?
And forgive me if my English is not good, I'm using the google translator
Click to expand...
Click to collapse
you were in 8.1 or you went from 9.0 to 8.1 because I had problems with mine I had to open it to switch to EDL mode and then flash an old 7.1 rom that did not have the security and I could do the command cmd .... look on the thread of discussion mi A1 I explained the procedure