Related
Hello My Phone is Honor 9x Pro HLK-L41
Base Software Version:
HLK-LGRP4-OVS 9.1.1.197
Cust Software Version:
HLK-L41-CUST 9.1.1.1(C432)
Preload Software Version:
HLK-L41-PRELOAD 9.1.1.1(C432R4)
I have installed patch update, LZPLAY is dead... no GMS
Huawei in the latest update has closed the backdor:
MDM_INSTALL_SYS_APP
MDM_INSTALL_UNDETACHABLE_APP
To use LZPLAY, you need to downgrade/roolback the firmware...
My old firmware not find...
FirmwareFinder not find my firmware...
Other models Honor 9x pro: HLK-AL10, HLK-TL10, HLK-L42
The only version with old and new firmware downlods is: HLK-AL10,
is this firmware compatible with HLK-L41?
Is there any trick using the termux shell to install the Gapps on root?
I sorry in advance if I violated any term of the rules, thanks to anyone who can be of help...
Hi,
I did not found free lzplay firmware for HKL-L41.
It would be interesting to now the difference between HLK-L41 and HLK-L42. Maybe it's possible to install HLK-L42 firmware with lzplay working.
I have the same problem and cannot install google services.
How have you been able to solve it?
... and I have the same problem. With version 180 the popup error message was show me all the time.
I have upgrade from 180 > 203 > 209 but now, "G" app doesn't work.
Anyone have old rom version working well with lzplay ?
My mobile is HLK-L41 = Hulk-L41FH 9.1.1.209(C432E1R4P1), L41 = European version
Rom link ?
Thanks a lot,
[QUOTE = "demo_123, publicación: 83802293"]
Hola, mi teléfono es Honor 9x Pro HLK-L41
Versión de software base:
HLK-LGRP4-OVS 9.1.1.197
Versión de software personalizada:
HLK-L41-CUST 9.1.1.1 (C432)
Versión de software de precarga:
HLK-L41-PRELOAD 9.1.1.1 (C432R4)
He instalado la actualización del parche, LZPLAY está muerto ... no GMS
Huawei en la última actualización ha cerrado el backdor:
MDM_INSTALL_SYS_APP
MDM_INSTALL_UNDETACHABLE_APP
Para usar LZPLAY, necesita degradar / roolback el firmware ...
Mi antiguo firmware no encuentra ...
FirmwareFinder no encuentra mi firmware ...
Otros modelos Honor 9x pro: HLK-AL10, HLK-TL10, HLK-L42
La única versión con descargas de firmware antiguas y nuevas es: HLK-AL10,
¿Es este firmware compatible con HLK-L41?
¿Hay algún truco para usar el shell termux para instalar Gapps en root?
Lamento de antemano si violé algún término de las reglas, gracias a todos los que puedan ser de ayuda ...
[/CITAR]
Ho, conseguiste hacer alguna cosa?. yo tengo tu mismo movil y versión, pero no se como hacerlo.
Hi, I found a guy on youtube how offers old firmware for HLK-L41.
I didn't test it. But with this firmware version it should be possible to use googlefier.
Edit: Another user posted this already: https://forum.xda-developers.com/t/...3-european-hlk-l41_9-1-1-180-and-189.4202425/
Hello gentlemen,
While flashing the stock ROM in my Cubot X30 using the SP flash tool I have made a mistake selecting "Format and download" instead of "download only". At the end of process I have found a red watermark on my screen "TEE key not write Google key not write". After searching for various solutions with no success I have asked to cubot.net support. Following the answer:
The google key was lost and needs to be written.
Here is the tutorial.
109.52 MB file on MEGA
mega.nz
In the link all the necessary to fix the problem, worked fine for my device.
Hope this will help.
Thanks for providing the fix feedback for those who may need it!
Mod edit - 3 posts merged and translated by https://www.deepl.com/translator:
I'm having the same problem
Thanks, I'll try here
Hello friend I'm with the same problem and with the same device cubot x30 software version 23 downloaded the files available did the procedure I could correct the imei but still follows the red watermark written "TEE key not write google key not write" I understood the whole process but the key that asks in the software SN Write TOOL in the part that says "Attention Key" (something like that) refers to the verification key of google by what I understood that corresponds to a file format (. bin) more in the files available for download I did not see any .bin file that could use or any tutorial that tells me where or how to extract such a .bin file more finally could tell me how you got this google key in your procedure so I can repeat here and tbm get success, I await a return thank you already!
******************************
Estou com o mesmo problema
Obrigado vou tentar aqui
Olá amigo estou com o mesmo problema e com o mesmo aparelho o cubot x30 versão 23 do software baixei os arquivos disponibilizados fiz o procedimento consegui corrigir o imei porém ainda segue a marca d'agua vermelha escrita "TEE key not write google key not write" eu entendi todo o processo porém a chave que pede no software SN Write TOOL na parte que diz "Attention Key" (algo assim) se refere a chave de verificão do google pelo que entendi que corresponde a um arquivo do formato (.bin) mais nos arquivos disponibilizados para download eu não vi nenhum arquivo .bin que pudesse usar ou algum tutorial que me diga onde ou como extrair tal arquivo .bin mais enfim poderia me dizer como você conseguiu obter essa chave google no seu procedimento pra que eu possa repetir aqui e tbm obter sucesso, aguardo um retorno obrigado desde já!!
*****************************
@williammedeiros Please use the English language (or add an English translation at least)!
Please review the XDA Forum Rules with special emphasis on rule no. 4!
Regards
Oswald Boelcke
Can someone share the MBN files from a note 10+ 5G? They may be in /vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/ but I don’t have one to know for sure. If you’re rooted, you can get them with https://play.google.com/store/apps/details?id=ma.wanam.partitions and it should highlight them in yellow by default
I have a OnePlus 8 which has the same modem but isn’t able to access all features on ATT. A work around for previous OnePlus phones was to flash the MBN files from a phone with the same modem that ATT has approved for full access, so hopefully this will let that happen.
taurealis said:
Can someone share the MBN files from a note 10+ 5G? They may be in /vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/ but I don’t have one to know for sure. If you’re rooted, you can get them with https://play.google.com/store/apps/details?id=ma.wanam.partitions and it should highlight them in yellow by default
I have a OnePlus 8 which has the same modem but isn’t able to access all features on ATT. A work around for previous OnePlus phones was to flash the MBN files from a phone with the same modem that ATT has approved for full access, so hopefully this will let that happen.
Click to expand...
Click to collapse
Did you ever get the mbn files?
taurealis said:
Can someone share the MBN files from a note 10+ 5G? They may be in /vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/ but I don’t have one to know for sure. If you’re rooted, you can get them with https://play.google.com/store/apps/details?id=ma.wanam.partitions and it should highlight them in yellow by default
I have a OnePlus 8 which has the same modem but isn’t able to access all features on ATT. A work around for previous OnePlus phones was to flash the MBN files from a phone with the same modem that ATT has approved for full access, so hopefully this will let that happen.
Click to expand...
Click to collapse
Bro una consulta, al decir "modem" te refieres a que usan el modem x24 o te refieres a que usan el mismo mcfg_sw.mbn, porque yo tengo un LG g8x con modem SN855 x24, prueba a poner el MBN de un Xiaomi mi 9T pro, que usan el mismo módem, pero no funcionó. No se a que se debe la incompatibilidad, si deben ser el mismo modem, el mismo snapdragon o el mismo celular, o la misma version de android.
Translated by GT: Bro a query, when you say "modem" you mean that they use the x24 modem or you mean that they use the same mcfg_sw.mbn, because I have an LG g8x with SN855 x24 modem, try to put the MBN of a Xiaomi mi 9T pro, which use the same modem, but it didn't work. I don't know what the incompatibility is due to, if they must be the same modem, the same snapdragon or the same cell phone, or the same version of android.
DiegoKcrz said:
Bro una consulta, al decir "modem" te refieres a que usan el modem x24 o te refieres a que usan el mismo mcfg_sw.mbn, porque yo tengo un LG g8x con modem SN855 x24, prueba a poner el MBN de un Xiaomi mi 9T pro, que usan el mismo módem, pero no funcionó. No se a que se debe la incompatibilidad, si deben ser el mismo modem, el mismo snapdragon o el mismo celular, o la misma version de android.
Translated by GT: Bro a query, when you say "modem" you mean that they use the x24 modem or you mean that they use the same mcfg_sw.mbn, because I have an LG g8x with SN855 x24 modem, try to put the MBN of a Xiaomi mi 9T pro, which use the same modem, but it didn't work. I don't know what the incompatibility is due to, if they must be the same modem, the same snapdragon or the same cell phone, or the same version of android.
Click to expand...
Click to collapse
hehe bro with google translate is enough. Don't make a lot of drama, sometimes I have a hard time understanding slang in English
Tengo un xiaomi redmi 7 estaba en modo fastboot, en el momento de la instalacion del firmware se me desonecto el cable usb y quedo la pantalla en negro, supongo que es modo EDL porque la notebook me lo reconoce en 9008 (COM4), les agradecesia si me pudieran guiar par poder recuperarlo.
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example), translation added below:
I have a xiaomi redmi 7 was in fastboot mode, at the time of the installation of the firmware I desonecto the usb cable and the screen is black, I guess it is EDL mode because the notebook recognizes it in 9008 (COM4), I would thank you if you could guide me to be able to recover it.
Gnar43 said:
Tengo un xiaomi redmi 7 estaba en modo fastboot, en el momento de la instalacion del firmware se me desonecto el cable usb y quedo la pantalla en negro, supongo que es modo EDL porque la notebook me lo reconoce en 9008 (COM4), les agradecesia si me pudieran guiar par poder recuperarlo.
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example), translation added below:
I have a xiaomi redmi 7 was in fastboot mode, at the time of the installation of the firmware I desonecto the usb cable and the screen is black, I guess it is EDL mode because the notebook recognizes it in 9008 (COM4), I would thank you if you could guide me to be able to recover it.
Click to expand...
Click to collapse
If you have mac operating system then i think it is easy to flash fasboot rom through it but if you have windows also you can flash files chek in youtube to flash through windows or you can download fastboot official firmware from internet and flash with mac with easy steps
Rashik lama said:
If you have mac operating system then i think it is easy to flash fasboot rom through it but if you have windows also you can flash files chek in youtube to flash through windows or you can download fastboot official firmware from internet and flash with mac with easy steps
Click to expand...
Click to collapse
bro say it's easy.if realworld need edl auth account.not found for redmi 7 no neeed auth loader firehose.
RMX 3360 / 3363 FULL OTA C.08
1B | TWOP : 1A | ID : 1D | RU : 37 | MYOP : 38 | TH : 39 | PH : 3E | BD : 55 | KZ : 5A | LK : 60 | KE : 74 | EG : 75 | MX : 7B | SA : 83 | LATAM : 9A | BR : 9E | EUEX : 44 | GB : 8A |
how to check your region ?? Dial number *#6776# and find MANIFEST:IMAGE
LATAM Haven't updated to ANDROID 12 ?? anyone know something about this ?? LAST version is
RMX3363_11.A.10_0100_202201200237
https://gauss-componentotacostmanual-sg.allawnofs.com/remove-4e99d6f30df73b025671cd3a1c8cd12a/component-ota/22/01/22/102ace2c0fcd4ac4806e204f1fe226d4.zip
RMX3360.C.08
IN: https://gauss-componentotacostmanua...22/06/23/df4761203d6b483d9a7c902b6fab42f8.zip
RMX3363.C.08
TWOP: https://gauss-componentotacostmanua...22/06/24/500b045e1d5442d590a6209d934f0d60.zip
ID: https://gauss-componentotacostmanua...22/06/24/b0fb5668409042d7a74ee2b7237eae2f.zip
RU: https://gauss-componentotacostmanua...22/06/24/0f2d80cd5e85486b816f333673b0ab3d.zip
MYOP: https://gauss-componentotacostmanua...22/06/24/14de65cb084047799058a2dbda118f46.zip
TH: https://gauss-componentotacostmanua...22/06/24/1d711c8a34a348b19221c877a09fedb1.zip
PH: https://gauss-componentotacostmanua...22/06/24/315fc152952342f09d2544f8e5d0f9fe.zip
BD: https://gauss-componentotacostmanua...22/06/24/20b1bb1619cb479fb57643d4aabe37bf.zip
KZ: https://gauss-componentotacostmanua...22/06/24/4863872d543941dca6f1b9c68db0b7e3.zip
LK: https://gauss-componentotacostmanua...22/06/24/e545067dcba74aa987e3a7488e96a175.zip
KE: https://gauss-componentotacostmanua...22/06/24/0108e1c1b3de4cd590d788e6992f5260.zip
EG: https://gauss-componentotacostmanua...22/06/24/46f10694923343748b448ab4f0fb1b1a.zip
MX: https://gauss-componentotacostmanua...22/06/24/45486cdc807041359a78be790de13fc5.zip
SA: https://gauss-componentotacostmanua...22/06/24/3b28adff23414114b2e00064d109a901.zip
EUEX: https://gauss-componentotacostmanua...22/06/24/8719531099f4431593c2e74e515794c4.zip
BR: https://gauss-componentotacostmanua...22/06/24/4743eb02df5d40e49b52984841fa3582.zip
GB: https://gauss-componentotacostmanua...22/06/24/f7b76a5d9c1041e6ad24131e83f0fbaf.zip
Latam has been updated already? do you know of any dates?
fabio0405 said:
Latam has been updated already? do you know of any dates?
Click to expand...
Click to collapse
LATAM has no OTA at all with RUI 3
"nvId16": "NV9A",
"osVersion": "ColorOS 11.2",
"otaTemplateId": "620375a2124eec00cf83fe09",
"otaVersion": "RMX3363_11.A.10_0100_202201200237",
"paramFlag": 1,
"parent": "ota-template",
"reminderType": 0,
"rid": "4a4ac2bf-065b-4dde-b396-4d12bb7110bc",
"securityPatch": "2022-01-05",
"securityPatchVendor": "2022-01-05",
"silenceUpdate": 0,
"status": "published",
"timestampH5": "2022.02.07",
"versionCode": 100,
"versionName": "RMX3363_11_A.10",
"versionTypeH5": "Official version"
hello. I have LATAM too. can I install version from other region?
engineer000 said:
hello. I have LATAM too. can I install version from other region?
Click to expand...
Click to collapse
if you have unlocked bootloader, yes you can.
to do this you have to use Oppo/Realme Flash .OFP File on Bootloader:
https://github.com/italorecife/OppoRealme-OFP-Flash
and on this page you will find the software for our phone needed to change the region
Realme GT Master Edition Firmware (RMX3363, RMX3360) - Realme Firmware
Realme GT Master Edition Firmware (RMX3363, RMX3360), Official Flash File (Stock ROM). flash your phone using realme flashtool or MSM Download tool.
realmefirmware.com
Przemek212 said:
if you have unlocked bootloader, yes you can.
to do this you have to use Oppo/Realme Flash .OFP File on Bootloader:
https://github.com/italorecife/OppoRealme-OFP-Flash
and on this page you will find the software for our phone needed to change the region
Realme GT Master Edition Firmware (RMX3363, RMX3360) - Realme Firmware
Realme GT Master Edition Firmware (RMX3363, RMX3360), Official Flash File (Stock ROM). flash your phone using realme flashtool or MSM Download tool.
realmefirmware.com
Click to expand...
Click to collapse
I don't want to unlock. I just bought it today.
I guess I need to stay in this version forever. I should I have bought realme gt neo 2
changelog?
mattia.b89 said:
changelog?
Click to expand...
Click to collapse
This update integrates the March and April 2022 Android security patches, fixes some known issues, and improves system performance.
https://gauss-componentotacostmanual-sg.allawnofs.com/remove-92af532e81bcc6e6b86132084cc95d90/component-ota/22/06/28/0ccd33e58b4d400cbf2f07b2d711d0d4.html
Latam has been updated already?
Hello Please put OTA file for region X00MA00
i got myop this time. how to flash the zip file?
Hello,
i installed the Rom C.08 for RMX3363
nearly everything works fine, i rooted it with magisk and without twrp.
I noticed the following problems:
There is no menu in the settings for VoWifi and VoLTE
is it possible that it is set to on automatic? or does RUI 3.0 not support that?
My bluetooth-connection in the car always is interrupted every few seconds and then connects again. (I tried everything...but i can't find a solution for this)
Does somebody have an information or an advice?
engineer000 said:
i got myop this time. how to flash the zip file?
Click to expand...
Click to collapse
unpack the zip file to your phone's storage. you can install OTA manually by choosing this file on the mobile device.
Robro86 said:
unpack the zip file to your phone's storage. you can install OTA manually by choosing this file on the mobile device.
Click to expand...
Click to collapse
thanks. updated by OTA and updated to the latest version.
engineer000 said:
thanks. updated by OTA and updated to the latest version.
Click to expand...
Click to collapse
Ok, super that it worked for you. Do you also have the bluetooth issue? see my before post.
i have bluetooth headset and there's no issue. i dont have a car to try it
HOLA BUENAS A TODOS ME REPORTO DESDE LATINOAMÉRICA ESPECÍFICAMENTE DESDE CUBA.
ME HICE DE UN REALME GT MASTER EDITION ESPECÍFICAMENTE VERSION GLOBAL 3363 ESTA EN LA VERSIÓN 11-A10 PERO NO ME BAJA NINGUNA ACTUALIZACIÓN HE PROVADO VARIAS VPN Y NINGUNA SOLUCIÓN. HE LEIDO VARIOS ARTÍCULOS PERO NO ENCUENTRO SOLUCIÓN A MI PROBLEMA. QUISIERA ACTUALIZARLO DE MANERA NATIVA SIN TENER Q ARRIESGARME A BRIQUIAR EL SISTEMA A TRAVÉS DE OTRAS SOLUCIONES. QUISIERA X FAVOR Q ALGUIEN ME AYUDARA CON ESTE TEMA A PODER ACTUALIZAR A KA VERSIÓN UI-3.0 . GRACIAS DE ANTEMANO MI MOVIL ES VERSION XLA0000
Mod translation:
HELLO GOOD TO ALL I REPORT FROM LATIN AMERICA SPECIFICALLY FROM CUBA.
I GOT A REALME GT MASTER EDITION SPECIFICALLY GLOBAL VERSION 3363 IS IN VERSION 11-A10 BUT NO UPDATE DOWNLOADS ME I HAVE TRIED SEVERAL VPN AND NO SOLUTION. I HAVE READ SEVERAL ARTICLES BUT I CAN'T FIND A SOLUTION TO MY PROBLEM. I WOULD LIKE TO UPDATE IT NATIVELY WITHOUT HAVING THE RISK OF BREAKING THE SYSTEM THROUGH OTHER SOLUTIONS. I WOULD LIKE SOMEONE TO PLEASE HELP ME WITH THIS SUBJECT TO BE ABLE TO UPDATE TO KA VERSION UI-3.0. THANKS IN ADVANCE MY MOBILE IS VERSION XLA0000
Yuniel Avalos said:
HOLA BUENAS A TODOS ME REPORTO DESIDE LATINOAMÉRICA ESPECÍFICAMENTE DESDE CUBA.
ME HICE DE UN REALME GT MASTER EDITION ESPECÍFICAMENTE VERSION GLOBAL 3363 ESTA EN LA VERSIÓN 11-A10 PERO NO ME BAJA NINGUNA ACTUALIZACIÓN HE PROVADO VARIAS VPN Y NINGUNA SOLUCIÓN. HE LEIDO VARIOS ARTÍCULOS PERO NO ENCUENTRO SOLUCIÓN A MI PROBLEMA. QUISIERA ACTUALIZARLO DE MANERA NATIVA SIN TENER Q ARRIESGARME A BRIQUIAR EL SISTEMA A TRAVÉS DE OTRAS SOLUCIONES. QUISIERA X FAVOR Q ALGUIEN ME AYUDARA CON ESTE TEMA A PODER ACTUALIZAR A KA VERSIÓN UI-3.0 . GRACIAS DE ANTEMANO MI MOVIL ES VERSION XLA0000
Mod translation:
HELLO GOOD TO ALL I REPORT FROM LATIN AMERICA SPECIFICALLY FROM CUBA.
I GOT A REALME GT MASTER EDITION SPECIFICALLY GLOBAL VERSION 3363 IS IN VERSION 11-A10 BUT NO UPDATE DOWNLOADS ME I HAVE TRIED SEVERAL VPN AND NO SOLUTION. I HAVE READ SEVERAL ARTICLES BUT I CAN'T FIND A SOLUTION TO MY PROBLEM. I WOULD LIKE TO UPDATE IT NATIVELY WITHOUT HAVING THE RISK OF BREAKING THE SYSTEM THROUGH OTHER SOLUTIONS. I WOULD LIKE SOMEONE TO PLEASE HELP ME WITH THIS SUBJECT TO BE ABLE TO UPDATE TO KA VERSION UI-3.0. THANKS IN ADVANCE MY MOBILE IS VERSION XLA0000
Click to expand...
Click to collapse
If you want to do a native update without risk, you'll have to wait for it.
There is no LATAM file for download in this thread. If there would be one you could update by manual file choosing (you have to unpack the download) on your device's file explorer. (You'll find the extended options for that by pressing the three dots in the upper right corner on ota search screen)
Type in your phone dialer *#6776# and it will show informations of your device. If you see Manifest image: 9A you can't update with the files availible to download in that thread. If it is not 9A see what it is in the first post of that thread and download the file for your device's region. In my case it was 44, so i downloaded the EUEX file. I could update with no risk in stock state of the device.
METROchas
Robro86 said:
Si quieres hacer una actualización nativa sin riesgo, tendrás que esperar.
No hay ningún archivo LATAM para descargar en este hilo. Si hubiera uno, podría actualizarlo eligiendo manualmente el archivo (debe descomprimir la descarga) en el explorador de archivos de su dispositivo. (Encontrará las opciones extendidas al presionar los tres puntos en la esquina superior derecha en la pantalla de búsqueda de ota)
Escriba el marcador de su teléfono *#6776# y mostrará información de su dispositivo. Si ve la imagen del manifiesto: 9A, no puede actualizar con los archivos disponibles para descargar en ese hilo. Si no es 9A, vea cuál es en la primera publicación de ese hilo y descargue el archivo para la región de su dispositivo. En mi caso era 44, así que descargué el archivo EUEX. Podría actualizar sin riesgo en estado de stock del dispositivo.
Robro86 said:
GRAMO.
Robro86 said:
GRAMO.Gracias hermano. Aparece en la imagen del manifiesto 9a, significa que estoy un poco jodido, tendré que esperar y ver. Tengo otra pregunta si desbloqueo el gestor de arranque para instalar otra ROM global Stock cual usted me recomendaría puede ser la última de RUI-3.0 sin que exista ningún problema de briqueo del móvil o en el futuro para una actualización de RUI-4.0 tendría que hacer lo mismo? Gracias
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yuniel Avalos said:
METROchas
Click to expand...
Click to collapse
with an unlocked bootloader it is possible, in this Forum you can find out how. i unlocked my bootloader after update (EUEX). But I think an unlocked bootloader leads to an error doing OTA-Update. (Not sure about that)
At the moment i am on RUI-3.0 and wait for release of RUI-4.0 (I have bluetooth problems on Android 12 RUI3.0 (OTA C08) and hope it will be solved when RUI 4.0 Android 13 is availible. It could also cause problems with connectivity or bluetooth if you unlock the bootloader - there was a hint before unlocking on my device)
But i had to unlock because i wanted to root the device.