Hello,
I have a Ulefone Armor 3T with the stock firmware and software. It appears Ulefone has posted a firmware update on the Ulefone Software updates page (I can't post the URL yet, do to XDA new user restrictions, but you can find it on their website).
I have followed the directions, but can't figure out how to boot up the phone, so that the PC sees it as a COM port, not a USB portable device, and keeps it connected via COM port. The directions say to make sure the phone is off, hold the volume up/down at the same time and plug it into the computer using USB, then run the firmware loader's SCAN mode to find the com port. I can do that, it finds the com port (different every time, but usually COM8, COM11, COM12), but then the battery starts charging and the software can't find the phone anymore. It's as if the firmware update mode won't stick?
I'm new to Android and Ulefone. Maybe I"m holding the button too long or not long enough? If I hold the volume buttons too long, it goes into some kind of recovery mode. Any suggestions appreciated.
Thanks, Joe
1 Con el teléfono apagado conecta el cable usb y presiona DESPUES DE CONECTAR el botón Volumen abajo y el flasheo rempezara,la ultima actualizacion que hay para el Armor 3T en la pagina oficial sigue siendo android 8.1 ,no han actualizado el sistema operativo totalmente decepcionado con esta marca
Howdy joedom99
Did you find out? I have same Ulefone Armor 3T and I am not really sure what version is compatible. My basic thing is to upgrade the Android OS (stock still is in 8.1 since 2018 :| ) please let me know.
Thanks in advance.
Related
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
I can't get the Emergency Mode in my phone (LG L3 II E-425g). I want to put another firmware but I can't because the kdz updater shows an error at the final of the process and I don't know why. I guess that it's because the phone isn't in emergency mode. Answers?
-------------------------------------------------------
No puedo poner en Modo Emergencia mi LG L3 II E-425g. Quiero ponerle otro firmware pero no es posible ya que el kdz updater lanza un error al final y supongo que es porque el terminal no esta en modo emergencia.
Thanks :good:
Angelo Jiménez said:
I can't get the Emergency Mode in my phone (LG L3 II E-425g). I want to put another firmware but I can't because the kdz updater shows an error at the final of the process and I don't know why. I guess that it's because the phone isn't in emergency mode. Answers?
-------------------------------------------------------
No puedo poner en Modo Emergencia mi LG L3 II E-425g. Quiero ponerle otro firmware pero no es posible ya que el kdz updater lanza un error al final y supongo que es porque el terminal no esta en modo emergencia.
Thanks :good:
Click to expand...
Click to collapse
1 battery out
2 plug usb to pc
3 press and hold vol- on phone
4 plug usb to phone
5 wait to see "Download Mode" on screen
6 put battery back in
7 flash kdz
IGGYVIP said:
1 battery out
2 plug usb to pc
3 press and hold vol- on phone
4 plug usb to phone
5 wait to see "Download Mode" on screen
6 put battery back in
7 flash kdz
Click to expand...
Click to collapse
Bro, thanks. But I still can't flash my LG. At the final of the flashing process, appears "Error!- WParam: 100 LParam:0". What do I have to do? I've tried it All!
Im with the same isue, the phone is in download mode, but kdz firmware updater fails to flash
Angelo Jiménez said:
I can't get the Emergency Mode in my phone (LG L3 II E-425g). I want to put another firmware but I can't because the kdz updater shows an error at the final of the process and I don't know why. I guess that it's because the phone isn't in emergency mode. Answers?
-------------------------------------------------------
No puedo poner en Modo Emergencia mi LG L3 II E-425g. Quiero ponerle otro firmware pero no es posible ya que el kdz updater lanza un error al final y supongo que es porque el terminal no esta en modo emergencia.
Thanks :good:
Click to expand...
Click to collapse
Angelo:
1.- shuthdown yout cellphone
2.- when your cellphone is off, press, "vol -" while connect the usb cable that is already connected to your PC
there isn't a emergency mode, but there is the download mode and if you want check this solution:
http://forum.xda-developers.com/opt.../updated-lg-l3-ii-e425g-untouchable-t2826286/
---
Angelo:
1.- Apaga tu celu
2.- cuando esté apagado presiona el boton "volumen -" mientras conectas el cable que ya esta conectado a tu PC
no existe emergency mode sino un download mode y si quieres date una pasada por esta solucion:
http://forum.xda-developers.com/opt.../updated-lg-l3-ii-e425g-untouchable-t2826286/
ensarman said:
Angelo:
1.- Apaga tu celu
2.- presiona el boton "volumen -" mientras conectas el cable que ya esta conectado a tu PC
no existe emergency mode sino un download mode y si quieres date una pasada por esta solucion:
http://forum.xda-developers.com/opt.../updated-lg-l3-ii-e425g-untouchable-t2826286/
Click to expand...
Click to collapse
JUST A TIP:
edit the post and add english version
its against the rules to post in other than English languages
IGGYVIP said:
JUST A TIP:
edit the post and add english version
its against the rules to post in other than English languages
Click to expand...
Click to collapse
it is practicaly the same in your post, but in spanish , well, I will put the enlish version too...
(Raising topic in English).
Greetings to all the members of this great Community.
I come to the Forum for some suggestions to try to revive this Cell Phone.
This is the Sony Xperia XZ1 (Trying to solve the problem on the mobile).
Well, from my point of view I have noticed the following:
-The phone does not take charge.
-When Connecting the Charger does not turn on the Led Lights.
-Do not enter Recovery Mode.
-I can not Flash some FTF because it does not enter Mode.
-When connecting to the PC, the PC does not recognize the device but immediately turn it off and press Volume Down (Fastboot Mode), in the Device Manager, in the Section (Other Device) there is a device called QUSB_BULK that needs Driver to install.
Note:
I have left Loading up to 2 hours and nothing,
To see who helps to revive the mobile, I will thank you for the help.
What idea could I give for the Possible Solution?
This forums needs you post English only.
(en este foro no se permiten post que no sean inglés. Por lo que dices yo diría posiblemente es problema del puerto usb, por eso no carga y no lo reconoce el pc. El recovery no sale si tienes el cel stock). Lo encuentras en, por ejemplo
https://www.etradesupply.com/sony-xperia-xz1-charging-port-flex-cable-grade-s.html
https://www.amazon.com/Plug-Cable-Repair-Xperia-Compact/dp/B07FNDTY1M
Hey all
Today in the morning watch showed 9% on battery and I placed it to charge and after an 1 hour I came back to check and it was showing Amazfit logo, the one when you boot the device but logo stays forever. If I hold red button to reset it reloads and starts by itself. Also there is no way to turn it off.
Everything was working fine in the morning before the charge and all other days.
Maybe someone has experienced same stuff. Watch is only 1 month old...
Mioleris said:
Hey all
Today in the morning watch showed 9% on battery and I placed it to charge and after an 1 hour I came back to check and it was showing Amazfit logo, the one when you boot the device but logo stays forever. If I hold red button to reset it reloads and starts by itself. Also there is no way to turn it off.
Everything was working fine in the morning before the charge and all other days.
Maybe someone has experienced same stuff. Watch is only 1 month old...
Click to expand...
Click to collapse
The same situation here. I have tried everything without success. I am thinking that next version of zeep maybe automatically fix the issue.
Mam to samo. W nocy obudził bootloop. Nic nie pomaga.
Same problem here pethatic amazfit support money wasted
Any help for gtr2 bootloop restarting problem any hope help please
How to go in Fastboot mode gtr2 any guy answer please
Hey, I have a GTR 2, and at first I thought that the bootloop issue is software based. That can be easily fixed if you put the watch on the charger as it can finish loading even with a corrupted watchface installed.
In my case however, the watch only worked for a short time after I've put it in the freezer. That is a hardware issue. All that can be done is to get it replaced by the store that sold it to you, or in case that option is not available to you, you need to actually heat the board over 300C so that, hopefully, the bad connection is fixed (mobile repair shops can actually help with that).
As a test: put device in freezer, connect, reset, whatever, then shutdown the watch.
Wait for the watch to reach room temperature (non working state). If it's a hardware bootloop, the watch will not react to any buttons, will not show he charging animation, nothing. Basically black screen.
I also tried removing the battery for 10 seconds, holding any combination of buttons, charging states, screen presses, so simply don't waste time with that.
Every electronic equipment has a failure rate of 0-5%, we just happened to buy those 0 to 5% watches.
From what I understand, it is a design error and some contacts on the circuit board may not make contact...
The Amazfit GTR2 just doesn't work on the touch screen. I only used it for a week .... I restarted in vain, nothing.
Can anyone help me?
Good morning everyone
I wanted to share an experience with you. And the solution in the Amazfit GTR2 that was stuck in the logo
after I read the method of placing it in the freezer for a few minutes and that it really works for a few minutes
thing that and verified!
I came to deduce that it would be ??!!
It could be a violation of 183
well I proceeded to do a reflux since it still turns on I proceeded to use
125 degree heat
60 air
in a uniform way after saying the heat
turned on without problems
I hope it helps you
Buenas.. A todos
les quería compartir una experiencia. Y la solucion en la Amazfit GTR2 que quedaba pegada en el logo
despues que lei el metodo de colocarlo en el freezer por algunos minutos y que en verdad funciona por algunos minutos
cosa que e comprobado!!!
llegue a deducir que seria ??!!
Podría tratarse de una infracción de 183
bueno procegui en hacerle un reflujo ya que el mismo ahun prende procedi a usar
125 grados de calor
60 de aire
de una forma uniforme luego de decir el calor
encendió sin problemas
Espero les ayude
Ronaldvd said:
Good morning everyone
I wanted to share an experience with you. And the solution in the Amazfit GTR2 that was stuck in the logo
after I read the method of placing it in the freezer for a few minutes and that it really works for a few minutes
thing that and verified!
I came to deduce that it would be ??!!
It could be a violation of 183
well I proceeded to do a reflux since it still turns on I proceeded to use
125 degree heat
60 air
in a uniform way after saying the heat
turned on without problems
I hope it helps you
Buenas.. A todos
les quería compartir una experiencia. Y la solucion en la Amazfit GTR2 que quedaba pegada en el logo
despues que lei el metodo de colocarlo en el freezer por algunos minutos y que en verdad funciona por algunos minutos
cosa que e comprobado!!!
llegue a deducir que seria ??!!
Podría tratarse de una infracción de 183
bueno procegui en hacerle un reflujo ya que el mismo ahun prende procedi a usar
125 grados de calor
60 de aire
de una forma uniforme luego de decir el calor
encendió sin problemas
Espero les ayude
Click to expand...
Click to collapse
Hola! tengo el mismo problema, por cuanto tiempo le aplicaste el calor? le colocaste Flux si es así en que parte? no soy muy experto en esto pero quiero intentarlo.
Quedo atento. Saludos!.
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?