Mi A1 brickeado // Mi A1 bricked - Android Q&A, Help & Troubleshooting

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

Related

[Q] ASUS PadFone A66 'invalid kernel', how to fix it? Help! Please.

My padfone was bricked when I tried to replace the recovery by TWRP via goomanager (TWRP official recommended).
The procedure of goomanager makes nothing happens, it seems like just download the TWRP package.
The problem is that phone has different protection policies compared to HTC, samsung etc and the bootloader (fastboot mode) is locked by default.
In other words, there is no such a way to connect your phone when your rom, recovery did not pass the verification unless unlock the bootloader by ASUS official tool and void warranty before your operations.
If the recovery or roms did not pass the validation then the left-top corner of screen will show 'invalid kernel' and the phone haven't been unlocked to be premised to visit fastboot mode then the phone will be bricked.
I think there is two way to unbrick, the first is to unlock the bootloader by external connector, the other is to flash official recovery data by external. But when I tried to search solutions, I got nothing about padfone A66 even that RIFFBOX official forum.
Does anyone have an ideal to help me break the difficult circumstances?
s943035 said:
My padfone was bricked when I tried to replace the recovery by TWRP via goomanager (TWRP official recommended).
The procedure of goomanager makes nothing happens, it seems like just download the TWRP package.
The problem is that phone has different protection policies compared to HTC, samsung etc and the bootloader (fastboot mode) is locked by default.
In other words, there is no such a way to connect your phone when your rom, recovery did not pass the verification unless unlock the bootloader by ASUS official tool and void warranty before your operations.
If the recovery or roms did not pass the validation then the left-top corner of screen will show 'invalid kernel' and the phone haven't been unlocked to be premised to visit fastboot mode then the phone will be bricked.
I think there is two way to unbrick, the first is to unlock the bootloader by external connector, the other is to flash official recovery data by external. But when I tried to search solutions, I got nothing about padfone A66 even that RIFFBOX official forum.
Does anyone have an ideal to help me break the difficult circumstances?
Click to expand...
Click to collapse
even after bootloader unlock still got invalid kernel.. and there is no way to connect the device to pc in this case.
Hi, i did fix "invalid kernel" via jtag
Jig
nicolayer said:
Hi, i did fix "invalid kernel" via jtag
Click to expand...
Click to collapse
Hi!
I heave the same problem on my a66 "invalid kernel"!
I would bee wery thankful i you would describe a little bit more about that how you fixed using jig!
My phone is dead for 6 months, it would be great to fix it!
+ 1
Anyone here succeeded in unbricking?
in Windows 7 64 devicemanger the phone does show up as: ASUS android bootloader interface. In other words; Windows can see the phone.
What if you connect the bricked phone to a Linuxcomputer. Would that help? I mean, System and Storage are all on one single eMMc inside the phone. Is there no way to access this and read - write on it?
Nicolayer: you'r still there? A tutorial would be much appreciated.
signed .hex file needed
Hi guys!
Maybe I founded a soution for unbrick asus A66 with qualcomm download mode.
form teh pst ( http://forum.xda-developers.com/showthread.php?t=2136738 ) I take qlod.py and other stuff, just dosen't work because need proer signed MPRG8260.hex file for waking up the phone from a "deep sleep".
This "invalid kernel" has just happened to me for the second time when downgrading to 4.0.3 ICS using TWRP and I'm rather frustrated right now. I'm posting here because I am highly interested in a way to fix this that does not involve ASUS, which I've already done.
What's the deal with this signed MPRG8260.hex file? Also, is there anything new concerning a fix using JTAG? Is there anyone out there who can fix it and would offer a repair? I really want to get this brick back to life.
Thanks in advance,
-L
Padfone A66 JTAG fix for invalid kernel
<delete please>
missing files
my new information is...
QPST and Qualcomm QDload driver need.
manulal for emmcswdownload you can find on the internet
sahara.xml
8260mprg.mbn
8260_msimage.mbn
rawprogram0.xml
patch0.xml
and need a full firmware.
anybody have got these files?
I fnid *.mbn files (on chinese sites) but all was died...
s943035 said:
Mi padfone se bloqueó cuando intenté reemplazar la recuperación por TWRP a través de goomanager (recomendado por el oficial de TWRP).
El procedimiento de goomanager hace que no pase nada, parece que simplemente descargue el paquete TWRP.
El problema es que el teléfono tiene diferentes políticas de protección en comparación con HTC, Samsung, etc. y el gestor de arranque (modo de arranque rápido) está bloqueado de forma predeterminada.
En otras palabras, no existe tal manera de conectar su teléfono cuando su rom, la recuperación no pasó la verificación a menos que desbloquee el cargador de arranque con la herramienta oficial de ASUS y anule la garantía antes de sus operaciones.
Si la recuperación o las roms no pasaron la validación, la esquina superior izquierda de la pantalla mostrará 'kernel no válido' y el teléfono no se ha desbloqueado para visitar el modo fastboot, entonces el teléfono se bloqueará.
Creo que hay dos formas de desbloqueo, la primera es desbloquear el cargador de arranque mediante un conector externo, la otra es actualizar los datos de recuperación oficiales mediante un conector externo. Pero cuando traté de buscar soluciones, no obtuve nada sobre padfone A66 ni siquiera en el foro oficial de RIFFBOX.
¿Alguien tiene un ideal que me ayude a romper las circunstancias difíciles?
Click to expand...
Click to collapse
Mod edit - translated by https://www.deepl.com/translator
Hello, I have exactly the same problem, KERNEL NOT VALID on my asus a66 and it is incredible that 11 years later there is still no other solution than RIFF JTAG to solve this, however for the asus A68 if it exists, it is very strange, The mobile turns on but the computer does not detect it, any help?
***********************
Hola, tengo exactamente el mismo problema, KERNEL NO VÁLIDO en mi asus a66 y es increíble que 11 años después todavía no haya otra solución que no sea RIFF JTAG para solucionar esto, sin embargo para el asus A68 si existe, es muy raro, El móvil enciende pero no lo detecta el ordenador, alguna ayuda?
kevin_23 said:
Mod edit - translated by https://www.deepl.com/translator
Hello, I have exactly the same problem, KERNEL NOT VALID on my asus a66 and it is incredible that 11 years later there is still no other solution than RIFF JTAG to solve this, however for the asus A68 if it exists, it is very strange, The mobile turns on but the computer does not detect it, any help?
***********************
Hola, tengo exactamente el mismo problema, KERNEL NO VÁLIDO en mi asus a66 y es increíble que 11 años después todavía no haya otra solución que no sea RIFF JTAG para solucionar esto, sin embargo para el asus A68 si existe, es muy raro, El móvil enciende pero no lo detecta el ordenador, alguna ayuda?
Click to expand...
Click to collapse
@kevin_23
As courtesy I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Spanish posts.
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.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator

Unlock BootLoader, Boot Logo, Root, TWRP, Motorola Moto G6 Plus, Tutorial, Xposed

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

Moto g6 plus soak update, android 9

Hola a Todos, Este es el proceso de actualización a Android Pie (Soak Test)​
Esto no sería posible sin el apoyo y colaboración de los miembros del grupo "evert "​
"Entre todos podemos hacer las cosas posibles"​
Primero que nada, debemos tener el Bootloader Desbloqueado lo cual pueden conseguir desde cualquiera de estos dos Post
Unlock Bootloader (English & Español)
Preparing-to-unlock-bootloader-t3854240
Luego bajar la Rom Stock con la compilación: OPWS27.113-89-2
Descargar
Seguido de esto bajar los archivos Ota´s
Descargar
No nos olvidemos de los archivos ADB y Los Drivers de Motorola
Hilo: Minimal ADB and Fastboot
ADB Descarga Directa
Drivers
Y de paso los BootLogos
Instalador Automatico BootLogo (Blanco y Negro)
Una vez con todos los archivos ya descargados, procedemos a meterlos a una sola carpeta, para así utilizarlos mas rápidamente.
Descomprimir La ROM 89-2, y adb en una sola carpeta
Ejecutar el Archivo " flash rom.bat
Conectar el Teléfono en modo fastboot y esperar
Saltamos toda la configuración sin permitirle conectarse a Internet
Descomprimimos el zip con las otas y pasamos el archivo mas grande 27.----- a la memoria del teléfono
Nos vamos a permisos de Apps -> Almacenamiento -> Mostrar Sistema -> Activamos, desactivamos y activamos "Actualización de Motorola"
Nos debería aparecer el menú de actualización, si no es así vamos a actualizaciones y aparecerá
Dejamos que se instale y reiniciamos
Ahora ponemos los demás archivos en la memoria interna y automáticamente las actualizaciones serán detectadas, las instalamos y ya.
Después de Instalar todas las actualizaciones, hacemos un hard reset.
Si queremos quitar el anuncio de Bootloader, descomprimimos el zip con los Logos y elegimos el blanco o negro y ejecutamos el ".bat" correspondiente (Importante no usarlo antes o dará error en el proceso de actualizaciones)
Root:
Lo conseguimos con Magisk
Pasamos el zip a la memoria externa (la interna esta encriptada) y ponemos el teléfono en modo fastboot
Descargamos el Recovery y lo ejecutamos
Download TWRP ejecutable
Instalamos el Zip y reiniciamos, en dado caso que presente errores o no aparezca repetimos el paso anterior.
English
Hi Everyone, This is the update process to Android Pie (Soak Test) ​
[FONT= "Century Gothic"] This would not be possible without the support and collaboration of the members of the "evert" group [/FONT]​
"We can do all things together" ​
First of all, we must have the Unlocked Bootloader which can be obtained from any of these two Post
Unlock Bootloader (English & Español)
Preparing-to-unlock-bootloader-t3854240
Then download the Stock Rom with the compilation: OPWS27.113-89-2
Download
Download the Ota's files
Download
Let's not forget the ADB files and Motorola Drivers
Thread: Minimal ADB and Fastboot
ADB Direct Download
Drivers
And of course the BootLogos
BootLogo Automatic Installer (Black and White)
Once with all the files already downloaded, we proceed to put them into a single folder, so they can be used more quickly.
Unzip ROM 89-2, and adb in a single folder
Run the File " flash rom.bat
Connect the phone in fastboot mode and wait
We skipped all the configuration without allowing you to connect to the Internet
Unzip the zip with the otes and pass the largest file 27 .----- to the phone's memory
We go to Apps permissions -> Storage -> Show System -> Activate, deactivate and activate "Motorola Update"
We should see the update menu, if not, let's go to updates and it will appear
We let it install and restart
Now we put the other files in the internal memory and automatically the updates will be detected, installed and now.
After installing all the updates, we do a hard reset.
If we want to remove the announcement from Bootloader, unzip the zip with the Logos and choose the white or black and execute the corresponding ".bat" (Important not to use it before or give an error in the update process)
Root:
We got it with Magisk
We pass the zip to the external memory (the internal one is encrypted) and we put the phone in fastboot mode
Download the Recovery and execute it
Download TWRP executable
We install the Zip and reboot, in case it presents errors or does not appear we repeat the previous step.
OTA files need permission to download
AparecidoFaro said:
OTA files need permission to download
Click to expand...
Click to collapse
I'm uploading the file again, but it might take a while
Miiiis said:
I'm uploading the file again, but it might take a while
Click to expand...
Click to collapse
Can not you just put the file as public?
AparecidoFaro said:
Can not you just put the file as public?
Click to expand...
Click to collapse
The link is not mine, I can not change it
give me two hours and the link will be updated
Miiiis said:
The link is not mine, I can not change it
give me two hours and the link will be updated
Click to expand...
Click to collapse
Got it. All right then, no problem.
Guys, it looks like the stable update has been released in India
https://support.motorola.com/in/en/solution/MS136260
OTA links are not working...
ColaDeveloper said:
OTA links are not working...
Click to expand...
Click to collapse
new links
Thank you. I'm downloading and I will test it. I hope it will work.
I put a massive warning out here for anyone that's going to install this. First of all, with the public version rollout probably very soon, you should ask if it's worth it to install the soak because you have to go back to stock oreo for the official pie ota.
But aside from that, i'm putting a warning here as there have been people bricking their device with the soak.
Obviously, bricking is always a risk factor when your flashing things but i don't know if there will eventually be a fix for those that end up bricked. Do with your device whatever you want but keep this in mind. Yes you get stock pie with soak, but consider if the risk taken is worth the gain.
Miiiis said:
new links
Click to expand...
Click to collapse
Can't seem to open the rar file in the new link. Anyone else having this problem?
The OTA link does not work
The update for Moto G6 plus is started to rolling out buth good take wail before its on youre phone avalbe..
https://www.talkandroid.com/335911-moto-g6-android-pie/
Boot logo fails
Awesome! I flashed this on my Moto G6 plus and it worked, took 30 minutes while all the updates where installing.
I've got this message while running Bootlogo Moto G6 Plus White-Black in fastboot:
Code:
C:\G6+\platform-tools_r28.0.1-windows\platform-tools\roms\stock\Pie\Bootlogo Moto G6 Plus White-Black\Bootlogo Moto G6 Plus>White.bat
C:\G6+\platform-tools_r28.0.1-windows\platform-tools\roms\stock\Pie\Bootlogo Moto G6 Plus White-Black\Bootlogo Moto G6 Plus>fastboot flash logo logo_white.bin
(bootloader) partition-typ: not found
(bootloader) max-download-sizego: not found
target didn't report max-download-size
sending 'logo' (2071 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.007s
Also every time I boot the phone it sends a message in yellow saying: "Verity mode is set to disabled"
Thank you for your work!
Google phone work? Direct from the play store?
angelpradomx said:
Awesome! I flashed this on my Moto G6 plus and it worked, took 30 minutes while all the updates where installing.
I've got this message while running Bootlogo Moto G6 Plus White-Black in fastboot:
Also every time I boot the phone it sends a message in yellow saying: "Verity mode is set to disabled"
Thank you for your work!
Click to expand...
Click to collapse
Hello, what firmware version were you on? I'm on 89-5 and I'm not sure if downgrading to 89-2 can cause bricks

Needing zui 11.5 or 11.1.021 zip

my phone is brick and when I try to install zui 10.5 or 11.0.21 with QFIL always give me sahara error I try to fix with all of solutions but still same and I remember this situation someone can share with me twrp back up file but should be clear after installing for I can install easy with twrp like restore by self data ? anyone can ?
Inténtalo pulsando todos los botones cuando se conecte al PC. Eso de que tienes que hacerlo sumamente rápido no es el problema sino que tienes que pulsar todos los botones.
Venecox said:
Inténtalo pulsando todos los botones cuando se conecte al PC. Eso de que tienes que hacerlo sumamente rápido no es el problema sino que tienes que pulsar todos los botones.
Click to expand...
Click to collapse
I try do this problem like more than 25 hours but still same problem I don't know what is it :S
brujaboy said:
I try do this problem like more than 25 hours but still same problem I don't know what is it :S
Click to expand...
Click to collapse
My phone was bricked, them i followed this tutorial: https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
otaviodsf said:
My phone was bricked, them i followed this tutorial: https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
Click to expand...
Click to collapse
I followed this solutions too but still have this problem sahara I don't know what is it
brujaboy said:
I followed this solutions too but still have this problem sahara I don't know what is it
Click to expand...
Click to collapse
Try to lock boatloader, them try qfil, Ota update, unlock boatloader them install Android 10 w/o boot the sistem . I got this wqy
brujaboy said:
I try do this problem like more than 25 hours but still same problem I don't know what is it :S
Click to expand...
Click to collapse
Disculpa, era solo volumen - y power como me funcionó a mi.
lipeneiva said:
Try to lock boatloader, them try qfil, Ota update, unlock boatloader them install Android 10 w/o boot the sistem . I got this wqy
Click to expand...
Click to collapse
I did actually I fixed but android 10 have so many bugs .S I don't like also antutu 320k

Have a locked optus Mate 20 Pro, used Hiproxy to upgrade to EMUI 12, I rolled back and broke the OS

Hey guys im very new here take it easy on me.
I have a LYA-L09 model Mate 20 pro. For the life of me im not sure what i did wrong.
So i thought i would be clever and download EMUI 12 via the hiproxy plugin seen below and hisuite to my perfectly working stock Optus locked phone Australian version. It was great for a while and then i didnt like that gpay wasnt working so i tried rolling back and failed miserably, when it reboots a black screen with yellow text tells me the device has loaded a different operating system.
Maybe its screwed im not sure but i think you might be able to tell me. I tried All these stock roms seen below to downgrade using the Dload method with usb stick attached to phone using the updater in the recovery mode and no luck, lots of fails.
So now i have nothing but a stock recover mode with no usb debugging enabled i cant even fastboot adb even when im in fastboot mode holding power and down, Tried the wireless recovery method and failed,.
Is there a way to at least fix the EMU 12 and at least getting something to work if i cant rollback anymore, or do i pretty much have a bricked phone.
{
"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"
}
This is what i used with hiproxy to get emui 12, With my phone with no usb debugging enabled and no way for Hiproxy to connect anymore to my phone, is there a way to get these packages below so i can reinstall 12 if i can't rollback anymore or is this only done with hi proxy and enabled debugging. I have probably missed a bunch of information and i apologise hopefully someone get shed some light.
I have Eft pro but im not sure if this is going to do anything...
Oh man no good at all, I plugged mine in to update it and it won't find the emui 12 update. I also have the other version of the phone (LYA-L29) and it updated via this method zero problem was hoping for the same result with the (lya-l09) variant but can't find a version.
Have you tried to download one of the old AU firmware? sounds like your having trouble getting into recovery though which may not help
Glomas1 said:
Have you tried to download one of the old AU firmware? sounds like your having trouble getting into recovery though which may not help
Click to expand...
Click to collapse
I can pretty much get into recovery just no usb debugging, all those firmwares you see in my post ive tried.. I cant find any aussie firmware for my LYA-L09, pretty sure this is the reason why its not flashing, if anyone has for my phone would be great, i think its C432.
Bummer, have you tried recovery in fast boot with a flash drive instead of using the computer?
Also from memory I think from recovery or fast boot you use different drivers with the PC as it does not recognise the phone properly otherwise
Glomas1 said:
Bummer, have you tried recovery in fast boot with a flash drive instead of using the computer?
Also from memory I think from recovery or fast boot you use different drivers with the PC as it does not recognise the phone properly otherwise
Click to expand...
Click to collapse
Yeah i saved the firmware in a folder called dload on my usb to c thumb drive and then the firmware either fail or install and then it goes back to the "your device has loaded a different operating system" just constant loop
Zymdings said:
Sí, guardé el firmware en una carpeta llamada dload en mi memoria usb a c y luego el firmware falla o se instala y luego vuelve a "su dispositivo ha cargado un sistema operativo diferente" solo un bucle constante
Click to expand...
Click to collapse
Hello Zymdings, something happened to me, similar to my mate 20 pro LYA-L09, I had it with android 10 and EMUI 11, with carrier ROM (TIGO C045) I changed it in order to update it to emui 12 because I didn't get an update yet that many times the telephone operators block updates, so I looked for a stock ROM for my LYA-L09 model, and since I couldn't find a ROM with emui 11, which is what I was on, I decided to install a ROM with emui 10 but from EUROPE (C432 ) because this is the one that has the update to emui 12 (DATA I got it from the firm finder V2 servers, I leave you the link: https://professorjtj.github.io/v2/) “YOU MUST PLACE YOUR CELL PHONE MODEL IN THIS PAGE"
I clarify that the method I used was by "dload", I will look for the download link from where I downloaded the ROM with European emui 10, since my internet is slow to upload almost 5 gb, apologies.
The ROM has a folder called dload which contains 3 files.
When installing by dload dialing from the cell phone *#*#2846579#*#* good is the process by dload you can search in inter or if you can't find it ask me friend.
Initially it installed well because I got to 100%, but when I restarted the same thing happened to you, that is to say that I got "the device has loaded a different operating system".
Salio que falló, buscando en internet en XDA encontré que era porque la ROM era diferente a la que tenía instalada entonces lo que hice fue cambiar lo siguiente: (solo estos dos archivos los cambié, el “update_sd_base” lo deje asi)
update_sd_cust_LYA-L09_hw_eu POR update_sd_cust_LYA-L09_tigo_la
update_sd_preload_LYA-L09_hw_eu_R1 POR update_sd_preload_LYA-L09_tigo_la_R1
Cuando hice esto, estaba instalado y listo, pensé que todo estaba bien, ya no tenía el inicio de TIGO, que era la ROM del operador, pero luego me di cuenta de que mi batería no cargaba rápido a pesar de que tenía mi cargador con una super carga que mi computadora no reconoció. Teléfono móvil. Lo que pasa es que cuando averigüé más me enteré de lo siguiente:
- ALERTA: La actualización a la última versión de EMUI 11 desactiva la carga rápida, el arranque rápido, la conexión USB y TestPoint de su teléfono.
- La única forma de solucionarlo es actualizar vía OTA, Erecovery o Dload por tarjeta de memoria a la última versión de EMUI 11.
Todo lo demás creo que funciona bien, algo más les cuento que en mi celular no aparece el explorador de archivos por lo que tuve que instalar uno desde la play store.
NOTA: He probado por Erecovery, por OTA y no lo he conseguido, mi esperanza es encontrar una ROM stock para hacerlo de nuevo por dload pero hasta hoy y casi una semana no he encontrado nada. Si tienes alguna información, te lo agradecería.
My whatsapp Bolivia +591 63931217 I am Daniel.
Yeh im not able to boot into the mobile operating system im actuallyt unable to enable debugging forgot to switch it on, and now im screwed Do you know if im able to fix the emui 12 that i damaged.. I cant download it anywhere only via hiproxy which i have no access to now because no fastboot
Zymdings said:
Hey guys im very new here take it easy on me.
I have a LYA-L09 model Mate 20 pro. For the life of me im not sure what i did wrong.
So i thought i would be clever and download EMUI 12 via the hiproxy plugin seen below and hisuite to my perfectly working stock Optus locked phone Australian version. It was great for a while and then i didnt like that gpay wasnt working so i tried rolling back and failed miserably, when it reboots a black screen with yellow text tells me the device has loaded a different operating system.
Maybe its screwed im not sure but i think you might be able to tell me. I tried All these stock roms seen below to downgrade using the Dload method with usb stick attached to phone using the updater in the recovery mode and no luck, lots of fails.
So now i have nothing but a stock recover mode with no usb debugging enabled i cant even fastboot adb even when im in fastboot mode holding power and down, Tried the wireless recovery method and failed,.
Is there a way to at least fix the EMU 12 and at least getting something to work if i cant rollback anymore, or do i pretty much have a bricked phone.
View attachment 5716995
This is what i used with hiproxy to get emui 12, With my phone with no usb debugging enabled and no way for Hiproxy to connect anymore to my phone, is there a way to get these packages below so i can reinstall 12 if i can't rollback anymore or is this only done with hi proxy and enabled debugging. I have probably missed a bunch of information and i apologise hopefully someone get shed some light.
View attachment 5716997
Click to expand...
Click to collapse
Hi. I have an Australian Huawei Mate 20 Pro LYA-L29 (C636) and I'm stuck with Android 9, didn't get any updates for the last 3 years. Could you give detailed instructions how to flash EMUI 12 (C432) via HiProxy please? Thanks
Zymdings said:
Hey guys im very new here take it easy on me.
I have a LYA-L09 model Mate 20 pro. For the life of me im not sure what i did wrong.
So i thought i would be clever and download EMUI 12 via the hiproxy plugin seen below and hisuite to my perfectly working stock Optus locked phone Australian version. It was great for a while and then i didnt like that gpay wasnt working so i tried rolling back and failed miserably, when it reboots a black screen with yellow text tells me the device has loaded a different operating system.
Maybe its screwed im not sure but i think you might be able to tell me. I tried All these stock roms seen below to downgrade using the Dload method with usb stick attached to phone using the updater in the recovery mode and no luck, lots of fails.
Así que ahora no tengo nada más que un modo de recuperación de stock sin la depuración USB habilitada. Ni siquiera puedo iniciar el adb rápido, incluso cuando estoy en el modo de inicio rápido manteniendo presionado el botón de encendido y apagado. Intenté el método de recuperación inalámbrica y fallé.
¿Hay alguna manera de al menos arreglar el EMU 12 y al menos hacer que algo funcione si ya no puedo retroceder, o tengo un teléfono bloqueado?
View attachment 5716995
Esto es lo que usé con hiproxy para obtener emui 12, con mi teléfono sin depuración USB habilitada y sin forma de que Hiproxy se conecte más a mi teléfono, ¿hay alguna manera de obtener estos paquetes a continuación para poder reinstalar 12 si puedo? t revertir más o esto solo se hace con hi proxy y depuración habilitada. Probablemente me he perdido un montón de información y me disculpo, espero que alguien arroje algo de luz.
View attachment 5716997
Click to expand...
Click to collapse
al final que hizo?

Categories

Resources