Related
Read carefully please!
Froyo and Windows users only at this moment, very busy this days, will make it work with linux and mac os!:
For those who flashed the SBF file with RSD Lite.
Im just trying to make it all easier.
Click to expand...
Click to collapse
You dont need adb installed on your PC!
TIPs: pass MOTOBLUR SETUP.
When you are on the begining of motoblur setup after you flashed your phone, (long press menu) to use the keyboard then type: eebluroff.
You must be done now!
Click to expand...
Click to collapse
Download the zip file and unzip it wherever you want.
Enable "USB debugging" on the phone before proceeding.
Settings -> Applications -> Development -> USB debugging.
1 - Connect your phone to PC (wait for your PC to install drivers) and click on "Install Gingerbreak & 2ndInitDefy".
Note: When commands window closes automatically, check if Gingerbreak and Defy 2init are installed on the phone (MOTOROLA SIDELOADER IS INSTALLED TOO to enable non-market apps), if they are everything is going fine.
2 - Unplug the phone from your PC.
3 - Open Gingerbreak installed on your phone and click on "Root device", (it will take a while) later your phone will reboot when completed.
4 - When your phone boots, go to 2ndinitDefy installed on your phone and download a recovery (try lastest version).
5 - Turn off the phone and turn it on, when you see the led light is blue press volume down button.
You are alredy into bootmenu ready to flash!
Click to expand...
Click to collapse
Donwload:
http://www.mediafire.com/?6kbt33kx64xg11e
I tested it on my PC but I need somebody else to test it, I have adb installed on my PC, need somebody who does not have it installed.
You wont need superoneclick anymore to root!
I will make a video later! I installed Ubuntu I will try it in linux to make this work for every OS and why not MAC OS!
josuearisty said:
Froyo users only:
For those who flashed the SBF file with RSD Lite.
Im just trying to make it all easier.
Testers needed
You dont need adb installed on your PC!
Download the file, unzip it wherever you want.
Remember to enable "USB debugging" before proceding.
Settings -> Applications -> Development -> USB debugging.
Then click on "Install Gingerbreak & 2ndInitDefy"
1 - Open Gingerbreak installed on your phone and click on "Root device", your phone will reboot when completed.
2 - Go to 2ndinitDefy installed on your phone and download a recovery (try lastest version).
Donwload:
http://www.mediafire.com/?6kbt33kx64xg11e
I tested it on my PC but I need somebody else to test it, I have adb installed on my PC, need somebody who does not have it installed.
You dont need superoneclick anymore to root!
Click to expand...
Click to collapse
Hola puedes poner las instrucciones en español y para que sirve ...perdon x mi ignoracia es
Es mejor Gingleblur q froyo cuales son las ventajas y las contras...saludos amigo....
Hi there,
May I know if there is a way to switch from CWM recovery to TWRP? I tried to simply flash the zip for TWRP but then my bravo won't start...
Thanks.
mataflakitas said:
Hola puedes poner las instrucciones en español y para que sirve ...perdon x mi ignoracia es
Es mejor Gingleblur q froyo cuales son las ventajas y las contras...saludos amigo....
Click to expand...
Click to collapse
Voy a hacer guias en español para cada thread que he creado
Esto es para si algo te ha salido mal y tu telefono no quiere iniciar quedandose solamente en el logo de moto y tienes que por desgracia FLASHEAR el SBF de Froyo con RSD LITE.
Entonces despues que estes en Froyo, podras seguir estos pasos y no tener que usar superoneclick, en mi opinion esto es mas facil.
Pruebalo cuando puedas!
brucezyc said:
Hi there,
May I know if there is a way to switch from CWM recovery to TWRP? I tried to simply flash the zip for TWRP but then my bravo won't start...
Thanks.
Click to expand...
Click to collapse
I try doing it too but no success, I think you should flash first a custom rom, then you will be able to flash touch recovery and it will for sure work.
I will let know about some test I make!
I'll be honest, I didn't try it, but it will work. That's really not a bad idea and would work with any phone Gingerbreak works on....You should release that in Android General.
I would use it, I'm just too lazy to flash an sbf and then set my phone back up again. I'm happy with my Bravo for the moment...and its my onlyl phone...That really is a simple, yet useful, solution.
gracias
josuearisty said:
Voy a hacer guias en español para cada thread que he creado
Esto es para si algo te ha salido mal y tu telefono no quiere iniciar quedandose solamente en el logo de moto y tienes que por desgracia FLASHEAR el SBF de Froyo con RSD LITE.
Entonces despues que estes en Froyo, podras seguir estos pasos y no tener que usar superoneclick, en mi opinion esto es mas facil.
Pruebalo cuando puedas!
I try doing it too but no success, I think you should flash first a custom rom, then you will be able to flash touch recovery and it will for sure work.
I will let know about some test I make!
Click to expand...
Click to collapse
Oooo muchas gracias amigo voy a probar que suerte q hablas español estoy aprendiendo muchas cosas contigo amigo josuearisty... saludos
oh no, i'm not unglug my phone after install Install Gingerbreak & 2ndInitDefy, then i click Gingerbreak to root
and now it's not on (, just have logo motorola
help me
now i'm ok, i wipe data, cache and do it again
but i dont click root on Gingerbreak , but on my phone still have superuser icon ? it success or not
i used superoneclick to root, but not success after i installed Gingerbreak & 2ndInitDefy
skeevy420 said:
I'll be honest, I didn't try it, but it will work. That's really not a bad idea and would work with any phone Gingerbreak works on....You should release that in Android General.
I would use it, I'm just too lazy to flash an sbf and then set my phone back up again. I'm happy with my Bravo for the moment...and its my onlyl phone...That really is a simple, yet useful, solution.
Click to expand...
Click to collapse
I think it is still not that simple, I will post some tips and be more specif.
mataflakitas said:
Oooo muchas gracias amigo voy a probar que suerte q hablas español estoy aprendiendo muchas cosas contigo amigo josuearisty... saludos
Click to expand...
Click to collapse
Siempre mi amigo, cualquier cosa estamos aqui.
kevins547 said:
oh no, i'm not unglug my phone after install Install Gingerbreak & 2ndInitDefy, then i click Gingerbreak to root
and now it's not on (, just have logo motorola
help me
now i'm ok, i wipe data, cache and do it again
but i dont click root on Gingerbreak , but on my phone still have superuser icon ? it success or not
i used superoneclick to root, but not success after i installed Gingerbreak & 2ndInitDefy
Click to expand...
Click to collapse
Maybe you did not follow steps as you should, I think I have to make steps easier to understand, so that noobs and advanced users can do it all.
Thanks for trying!
when unglug the phone from Pc, the box USB debugging is tick in or not ?
kevins547 said:
when unglug the phone from Pc, the box USB debugging is tick in or not ?
Click to expand...
Click to collapse
Of course it has to be enable.
Else it is not going to work.
gracias
josuearisty said:
Of course it has to be enable.
Else it is not going to work.
Click to expand...
Click to collapse
amigo podra subir un video para saber con mayor facilida como se hace y las instrucciones en español bueno tambien para ingles claro... creo que novatos como yo ...avemos muchos en este foro y estariamos muy agradecicdo con usted amigo josuearisty ...
oye amigo otra duda que pasa si mi pc tiene adb instalado.... puede ocacionar un error en mi motorola bravo ...?
otra duda por que cuando baje su archivo mi pc me lo detecto como un virus...
mataflakitas said:
amigo podra subir un video para saber con mayor facilida como se hace y las instrucciones en español bueno tambien para ingles claro... creo que novatos como yo ...avemos muchos en este foro y estariamos muy agradecicdo con usted amigo josuearisty ...
oye amigo otra duda que pasa si mi pc tiene adb instalado.... puede ocacionar un error en mi motorola bravo ...?
otra duda por que cuando baje su archivo mi pc me lo detecto como un virus...
Click to expand...
Click to collapse
Esta semana estare algo ocupado, el video creo que lo hare la semana que viene.
Usar el adb del archivo no te va a ocasionar ningun problema, ni a tu telefono ni a la computadora.
La aplicacion gingerbreak tiene un exploit dentro y los antivirus lo identifican como un virus, solo desactivalo si lo vas a usar.
--------------------------------------------------------
If you have adb installed on your pc, using this one will cause no problem to the phone or your pc.
Your antivirus detects gingerbreak as a virus because of an exploit command inside the apk file, you can deactivate your antivirus and use it with no problem, no risk with it.
I'll add, s1c/rage against the cage/gingerbreak all show up as viruses because they are. Not kill you PC virus, but virus none the less. Technically they're exploits, but still get picked up by scanners.
Gonna need some testers for LINUX and MAC, when its ready I will you know people!
Working great!. Will flash a Rom right now . Thnx to make our life easier!.
Took a few flashes, but I got there in the end! Great stuff, thanks!!
Worked like a charm. Thanks!!
Hi everyone,
I have a big problem since yesterday, I am under the version Miui 11 Android 10 rooted under TWRP unofficial and I wanted to install a Rom Custom, I of which wanted to install the official version of TWRP, when I have Flash Recovery Recovery.img after restarting... BLACK SCREEN I could not have returned to FASTBOOT mode and in RECOVERY only the NOTIFICATION which is on, when I stay press POWER + VOLUM UP I have a SOUND on PC like what the PHONE is connected for 5 SECONDS after it DISCONNECTS, so I followed a tutorial to open my phone and disconnect my BATTERY... always the same problem :/
if you can help me please :/
I would like to specify that I never know that when I wanted to put the official version of TWRP my phone was around 30% ... ?
Thanks you.
Test Point
Tiix31Dev said:
Hi everyone,
I have a big problem since yesterday, I am under the version Miui 11 Android 10 rooted under TWRP unofficial and I wanted to install a Rom Custom, I of which wanted to install the official version of TWRP, when I have Flash Recovery Recovery.img after restarting... BLACK SCREEN I could not have returned to FASTBOOT mode and in RECOVERY only the NOTIFICATION which is on, when I stay press POWER + VOLUM UP I have a SOUND on PC like what the PHONE is connected for 5 SECONDS after it DISCONNECTS, so I followed a tutorial to open my phone and disconnect my BATTERY... always the same problem :/
if you can help me please :/
I would like to specify that I never know that when I wanted to put the official version of TWRP my phone was around 30% ... ?
Thanks you.
Click to expand...
Click to collapse
I am writing this for anyone to use at their own risk, it is not complicated.
Once updated from Indonesia Miui 11 Android 9 rom to Android 10 and installed a recovery incorrectly and I have returned to
lock my Redmi Note 8 Pro (Begoña) and this time I have not waited for the battery to drain as in the previous one (post # 196)
I have used the Test Point method.
This is what I have done:
-Copied the folder from the Indonesian rom V10.4.2.0, once the zip is unzipped, in Computer> C
-Installed SP Flash Tool v5. 1924 Win also in C
-Removed the back of the mobile and removed the housing that is above the battery (Photo 1).
-Prepared a piece of fine copper wire, I have connected one end to a screw on the mobile plate making ground (Photo 2) and to
the other end I have connected a nail (Photo 4) .Then I have opened the Flash Tool and I have put the scatter that
*it is in the "images" folder of the rom that I had copied in C, and the DA and the authentication file that is in it
*Flash Tool folder and I have connected the usb cable to the mobile, only to the mobile.
-I pressed "Download Only" and connected the other end of the copper cable, prepared with a nail, in the
*point Kcol0 (Photo 3) and I have connected the usb cable to the computer. The bottom bar of the FlashTool has started to fill in
*color red first and then change color until the "Download Ok" symbol appears
*I have done it with the battery disconnected (others say it is connected) and with all the files marked on the
*Flash Tool (others say that you only have to mark the preolader) and it has worked for me.
*
After a few minutes the mobile has started with MIUI 10 and Android 9, as expected by the rom with which I have done it and
then I have already installed MIUI 11 and then I have updated to Android 10, both with MiFlash20191206 of Xiaomi. To finish
installing the appropriate recovery, this time yes, and doing root
If you have disconnected the battery, open the phone as in photo 1 of the three that I attach.
Esto lo escribo para que lo use quien quiera siempre bajo su propia responsabilidad, no es complicado.
Una vez actualizado de rom Indonesia Miui 11 Android 9 a Android 10 e instalado un recovery de forma incorrecta y he vuelto a
bloquear mi Redmi Note 8 Pro (Begoña) y esta vez no he esperado a que se agote la batería como en la anterior (post #196)
sino que he usado el método del Test Point.
Esto es lo he hecho:
-Copiado la carpeta de la rom de Indonesia V10.4.2.0, una vez descomprimido el zip, en Equipo > C
-Instalado SP Flash Tool v5. 1924 Win también en C
-Desmontado la trasera del móvil y quitado la carcasa que hay por arriba de la batería (Foto 1).
-Preparado un trozo de cable fino de cobre, un estremo lo he conectado a un tornillo en la placa del móvil haciendo masa(Foto 2)
y al otro extremo le he conectado un clavo (Foto 4).luego he abierto el Flash Tool y he puesto el scatter que
hay en la carpeta "images" de la rom que que había copiado en C, y el DA y archivo de autentificación que hay en la propia
carpeta del Flash Tool y he conectado el cable usb al móvil, solo al móvil.
-He pulsado "Download Only" y he conectado el otro extremo del cable de cobre, preparado con un clavo, en el
punto Kcol0 (Foto 3) y he conectado el cable usb al ordenador. La barra de abajo del FlashTool ha empezado a rellenarse en
color rojo primero y luego cambia de color hasta que aparece el simbolo "Download Ok"
Lo he hecho con la batería desconectada (otros dicen que conectada) y con todo los archivos marcados en el
Flash Tool (otros dicen que sólo hay que marcar el preolader) y me ha funcionado.
Después de unos minutos se ha iniciado el móvil con MIUI 10 y Android 9, como era de esperar por la rom con la que lo he hecho y luego ya le he instalado
MIUI 11 y después he actualizado a Android 10, los dos con MiFlash20191206 de Xiaomi. Para terminar instalando el recovery
apropiado, esta vez sí, y haciendo root
javizeta said:
If you have disconnected the battery, open the phone as in photo 1 of the three that I attach.
The first time it crashed I revived it waiting for the battery to drain (post # 196) and now I have it back
to briquet when flashing wrong twrp and I have not waited for it to be exhausted again but I have done it
with a test point.
In photos two and three I show you where you have to connect the cable and privately I send you a link to an explanatory video
because I don't know if I can put links to youtube here.
It worked perfectly for me on the first try.
Click to expand...
Click to collapse
hey how to do me a favor pass the tutorial because I have the same problem:fingers-crossed:
maikiller said:
hey how to do me a favor pass the tutorial because I have the same problem:fingers-crossed:
Click to expand...
Click to collapse
I used the google search engine: tutorial to unbrick Chinese MTK phone and in the results I chose the Azlan Laion video.
Utilicé el buscador de google: tutorial desbrickear telefono MTK chino y en los resultados elegí el video de Azlan Laion.
Updated post # 2
Read please
Actualizado post #2
Leer, por favor
I definitely would appreciate anything that would get this flash to go through... I already have mine apart and have been trying everything to get it unbricked with no success as of yet...
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app
javizeta said:
I am writing this for anyone to use at their own risk, it is not complicated.
Once updated from Indonesia Miui 11 Android 9 rom to Android 10 and installed a recovery incorrectly and I have returned to
lock my Redmi Note 8 Pro (Begoña) and this time I have not waited for the battery to drain as in the previous one (post # 196)
I have used the Test Point method.
This is what I have done:
-Copied the folder from the Indonesian rom V10.4.2.0, once the zip is unzipped, in Computer> C
-Installed SP Flash Tool v5. 1924 Win also in C
-Removed the back of the mobile and removed the housing that is above the battery (Photo 1).
-Prepared a piece of fine copper wire, I have connected one end to a screw on the mobile plate making ground (Photo 2) and to
the other end I have connected a nail (Photo 4) .Then I have opened the Flash Tool and I have put the scatter that
*it is in the "images" folder of the rom that I had copied in C, and the DA and the authentication file that is in it
*Flash Tool folder and I have connected the usb cable to the mobile, only to the mobile.
-I pressed "Download Only" and connected the other end of the copper cable, prepared with a nail, in the
*point Kcol0 (Photo 3) and I have connected the usb cable to the computer. The bottom bar of the FlashTool has started to fill in
*color red first and then change color until the "Download Ok" symbol appears
*I have done it with the battery disconnected (others say it is connected) and with all the files marked on the
*Flash Tool (others say that you only have to mark the preolader) and it has worked for me.
*
After a few minutes the mobile has started with MIUI 10 and Android 9, as expected by the rom with which I have done it and
then I have already installed MIUI 11 and then I have updated to Android 10, both with MiFlash20191206 of Xiaomi. To finish
installing the appropriate recovery, this time yes, and doing root
If you have disconnected the battery, open the phone as in photo 1 of the three that I attach.
Esto lo escribo para que lo use quien quiera siempre bajo su propia responsabilidad, no es complicado.
Una vez actualizado de rom Indonesia Miui 11 Android 9 a Android 10 e instalado un recovery de forma incorrecta y he vuelto a
bloquear mi Redmi Note 8 Pro (Begoña) y esta vez no he esperado a que se agote la batería como en la anterior (post #196)
sino que he usado el método del Test Point.
Esto es lo he hecho:
-Copiado la carpeta de la rom de Indonesia V10.4.2.0, una vez descomprimido el zip, en Equipo > C
-Instalado SP Flash Tool v5. 1924 Win también en C
-Desmontado la trasera del móvil y quitado la carcasa que hay por arriba de la batería (Foto 1).
-Preparado un trozo de cable fino de cobre, un estremo lo he conectado a un tornillo en la placa del móvil haciendo masa(Foto 2)
y al otro extremo le he conectado un clavo (Foto 4).luego he abierto el Flash Tool y he puesto el scatter que
hay en la carpeta "images" de la rom que que había copiado en C, y el DA y archivo de autentificación que hay en la propia
carpeta del Flash Tool y he conectado el cable usb al móvil, solo al móvil.
-He pulsado "Download Only" y he conectado el otro extremo del cable de cobre, preparado con un clavo, en el
punto Kcol0 (Foto 3) y he conectado el cable usb al ordenador. La barra de abajo del FlashTool ha empezado a rellenarse en
color rojo primero y luego cambia de color hasta que aparece el simbolo "Download Ok"
Lo he hecho con la batería desconectada (otros dicen que conectada) y con todo los archivos marcados en el
Flash Tool (otros dicen que sólo hay que marcar el preolader) y me ha funcionado.
Después de unos minutos se ha iniciado el móvil con MIUI 10 y Android 9, como era de esperar por la rom con la que lo he hecho y luego ya le he instalado
MIUI 11 y después he actualizado a Android 10, los dos con MiFlash20191206 de Xiaomi. Para terminar instalando el recovery
apropiado, esta vez sí, y haciendo root
Click to expand...
Click to collapse
----------
Your method does not work because it depends on the motherboard you are using, for example the Mediatek uses another type of test point and they are blocked, I think that is why Xiaomi does not want to give more support to the Xiaomi Redmi Note 8 Pro (Begonia) as devices!
I have tried it several times and it does not work, the only thing is a working method is: Having the volume up pressed until the Mode Flash mode is activated and with the SP Flash Tool. The problem is that it asks for an Authorized Account and it is what I am looking for (of course to payment)
The Procedure
0. Unzip your device's firmware.
1. Install MiFlashPro.
2. Navigate to (installation_directory)/MiFlashPro/SP_Flash_Tool/mi and run "account_auth.exe" (Run as administrator). In the window that opens, log in with an authorized Xiaomi Account.
3. Navigate to (installation_directory)/MiFlashPro/SP_Flash_Tool nad run "flash_tool.exe". The SP_Flash_Tool interface opens. Now you have to select the 3 files:
Download-Agent: (installation_directory)/MiFlashPro/SP_Flash_Tool/MTK_AllInOne_DA_mt6765_mt6785.bin
Scatter-loading File: You will find this one on your stock rom folder, especially on the folder called "images".
Authentication File: (installation_directory)/MiFlashPro/SP_Flash_Tool/auth_sv5.auth
4. Press the "Download" button.
5. Connect the USB cable to your PC but NOT YET to your phone.
6. Hold the vol+ button on your phone pressed and NOW connect the cable to it.
7. The program should now react and start the flashing process without giving an error.
8. Wait for the flashing process to end and enjoy!
javizeta said:
I am writing this for anyone to use at their own risk, it is not complicated.
Once updated from Indonesia Miui 11 Android 9 rom to Android 10 and installed a recovery incorrectly and I have returned to
lock my Redmi Note 8 Pro (Begoña) and this time I have not waited for the battery to drain as in the previous one (post # 196)
I have used the Test Point method.
This is what I have done:
-Copied the folder from the Indonesian rom V10.4.2.0, once the zip is unzipped, in Computer> C
-Installed SP Flash Tool v5. 1924 Win also in C
-Removed the back of the mobile and removed the housing that is above the battery (Photo 1).
-Prepared a piece of fine copper wire, I have connected one end to a screw on the mobile plate making ground (Photo 2) and to
the other end I have connected a nail (Photo 4) .Then I have opened the Flash Tool and I have put the scatter that
*it is in the "images" folder of the rom that I had copied in C, and the DA and the authentication file that is in it
*Flash Tool folder and I have connected the usb cable to the mobile, only to the mobile.
-I pressed "Download Only" and connected the other end of the copper cable, prepared with a nail, in the
*point Kcol0 (Photo 3) and I have connected the usb cable to the computer. The bottom bar of the FlashTool has started to fill in
*color red first and then change color until the "Download Ok" symbol appears
*I have done it with the battery disconnected (others say it is connected) and with all the files marked on the
*Flash Tool (others say that you only have to mark the preolader) and it has worked for me.
*
After a few minutes the mobile has started with MIUI 10 and Android 9, as expected by the rom with which I have done it and
then I have already installed MIUI 11 and then I have updated to Android 10, both with MiFlash20191206 of Xiaomi. To finish
installing the appropriate recovery, this time yes, and doing root
If you have disconnected the battery, open the phone as in photo 1 of the three that I attach.
Esto lo escribo para que lo use quien quiera siempre bajo su propia responsabilidad, no es complicado.
Una vez actualizado de rom Indonesia Miui 11 Android 9 a Android 10 e instalado un recovery de forma incorrecta y he vuelto a
bloquear mi Redmi Note 8 Pro (Begoña) y esta vez no he esperado a que se agote la batería como en la anterior (post #196)
sino que he usado el método del Test Point.
Esto es lo he hecho:
-Copiado la carpeta de la rom de Indonesia V10.4.2.0, una vez descomprimido el zip, en Equipo > C
-Instalado SP Flash Tool v5. 1924 Win también en C
-Desmontado la trasera del móvil y quitado la carcasa que hay por arriba de la batería (Foto 1).
-Preparado un trozo de cable fino de cobre, un estremo lo he conectado a un tornillo en la placa del móvil haciendo masa(Foto 2)
y al otro extremo le he conectado un clavo (Foto 4).luego he abierto el Flash Tool y he puesto el scatter que
hay en la carpeta "images" de la rom que que había copiado en C, y el DA y archivo de autentificación que hay en la propia
carpeta del Flash Tool y he conectado el cable usb al móvil, solo al móvil.
-He pulsado "Download Only" y he conectado el otro extremo del cable de cobre, preparado con un clavo, en el
punto Kcol0 (Foto 3) y he conectado el cable usb al ordenador. La barra de abajo del FlashTool ha empezado a rellenarse en
color rojo primero y luego cambia de color hasta que aparece el simbolo "Download Ok"
Lo he hecho con la batería desconectada (otros dicen que conectada) y con todo los archivos marcados en el
Flash Tool (otros dicen que sólo hay que marcar el preolader) y me ha funcionado.
Después de unos minutos se ha iniciado el móvil con MIUI 10 y Android 9, como era de esperar por la rom con la que lo he hecho y luego ya le he instalado
MIUI 11 y después he actualizado a Android 10, los dos con MiFlash20191206 de Xiaomi. Para terminar instalando el recovery
apropiado, esta vez sí, y haciendo root
Click to expand...
Click to collapse
excuse me , could u wirte in english on these pictures , i can not read ur Lang, please,:highfive::highfive: please
gadmei.tw said:
excuse me , could u wirte in english on these pictures , i can not read ur Lang, please,:highfive::highfive: please
Click to expand...
Click to collapse
These are the texts included in the photos translated into English using the google translator
Photo 2: It is to this screw that I have attached one end of the cable
Photo 3: Upper label: To this round contact you have to connect the other end of the cable
Bottom epigraph: It is just above the battery connector. Battery disconnected.
javizeta said:
These are the texts included in the photos translated into English using the google translator
Photo 2: It is to this screw that I have attached one end of the cable
Photo 3: Upper label: To this round contact you have to connect the other end of the cable
Bottom epigraph: It is just above the battery connector. Battery disconnected.
Click to expand...
Click to collapse
thank u!
i will try through these point
need video please/necesito el video por favor
hi budy, how could you send me the video?, i got the same problem with my redmi note 8 pro
Hola amigo, espero que te encuentres bien, ¿Como podrías enviarme el video?, tengo el mismo problema con mi redmi note 8 pro, se apagó y no ha encendido
leandro iván said:
hi budy, how could you send me the video?, i got the same problem with my redmi note 8 pro
Hola amigo, espero que te encuentres bien, ¿Como podrías enviarme el video?, tengo el mismo problema con mi redmi note 8 pro, se apagó y no ha encendido
Click to expand...
Click to collapse
What video are you referring to?
Hola, quiero cambiarle la rom a mi telefono por una mas mejor, pero no encuentro la version de twrp para el telefono, ademas eh intentado aplicarle root pero no he tenido exito, cualquier ayuda o sugerencia es bienvenida.
Hello, I want to change the rom on my phone for a better one, but I can't find the twrp version for the phone, also I've tried to apply root but I haven't been successful, any help or suggestion is welcome.
Mystery Mx said:
Hola, quiero cambiarle la rom a mi telefono por una mas mejor, pero no encuentro la version de twrp para el telefono, ademas eh intentado aplicarle root pero no he tenido exito, cualquier ayuda o sugerencia es bienvenida.
Hello, I want to change the rom on my phone for a better one, but I can't find the twrp version for the phone, also I've tried to apply root but I haven't been successful, any help or suggestion is welcome.
Click to expand...
Click to collapse
Install DevCheck
https://play.google.com/store/apps/details?id=flar2.devcheck
DevCheck/system/
What is listed as Device and Product?
sd_shadow said:
Install DevCheck
https://play.google.com/store/apps/details?id=flar2.devcheck
DevCheck/system/
What is listed as Device and Product?
Click to expand...
Click to collapse
Esto es lo que me aparece
This is what appears to me
sd_shadow said:
Install DevCheck
https://play.google.com/store/apps/details?id=flar2.devcheck
DevCheck/system/
What is listed as Device and Product?
Click to expand...
Click to collapse
Esto es lo que me aparece
This is what appears to me
Mystery Mx said:
Esto es lo que me aparece
This is what appears to me
Click to expand...
Click to collapse
Yes so you are looking for TWRP for "channel" which is you device's codename
sd_shadow said:
Yes so you are looking for TWRP for "channel" which is you device's codename
Click to expand...
Click to collapse
¿Descargo la version channel de TWRP?
Me aparecio la version TWRP river para el G7 normal, ¿me puede servir esa?
Did you download the channel version of TWRP?
The TWRP river version appeared for the normal G7, can that help me?
Mystery Mx said:
¿Descargo la version channel de TWRP?
Me aparecio la version TWRP river para el G7 normal, ¿me puede servir esa?
Did you download the channel version of TWRP?
The TWRP river version appeared for the normal G7, can that help me?
Click to expand...
Click to collapse
Ya di con la versión correcta de twrp, es esa la que dijiste, pense que era un error en la traduccion ya que uso el traductor de google, no se ingles
I already found the correct version of twrp, is that the one you said, I thought it was an error in the translation since I use the google translator, I don't know English
Mystery Mx said:
Ya di con la versión correcta de twrp, es esa la que dijiste, pense que era un error en la traduccion ya que uso el traductor de google, no se ingles
I already found the correct version of twrp, is that the one you said, I thought it was an error in the translation since I use the google translator, I don't know English
Click to expand...
Click to collapse
Surgio un problema, instale el twrp channel pero cuando intento acceder desde el telefono, este hace bootloop, despues de 3 reinicios vuelve a iniciar normal, tengo que iniciarlo desde el pc ya que no puedo desde el telefono
A problem arose, I installed the twrp channel but when I try to access from the phone, it does bootloop, after 3 reboots it starts again normally, I have to start it from the pc since I can't from the phone
I just bought a Dasaita PX6 Android head unit with wireless CarPlay and android auto and I cannot get it to connect to my phone at all.
1st) I have the phone paired to the head units Bluetooth
2nd) I have the phone connected to the hotspot from the head unit
zlink automatically opens and starts giving the “MFi IC read fail.” And then will continue to try to connect and every 30-60 seconds will then display “HARDWARE ERR,MFi read fail#”
I’ve tried this with my iPhone and my wife’s iPhone. Both phones same issue.
I’ve gone to the CarPlay connection screen where the head unit will populate but then when I try to connect to it it just sits there on the phone and never connects.
Same issue here. Did you find a solution?
I'm guessing, but I don't believe you can run hotspot and WIRELESS carplay at the same time. I'm pretty sure it's a limitation of the phone. Try WIRED carplay and see if that works. If it does then try wireless again with the hotspot off.
I have been working through the installation of a Wondefoo Headunit in a Mercedes GL350. I purchased the unit off AliExpress. The headunit has zlink installed. I have an iPhone so was using it for Carplay. Bluetooth and WIFI connect okay to the headunit. The first time I booted up the unit zLink connected and Carplay worked. The device is connected to constant 12v power so it powers off to sleep mode and warm starts the next time the ACC power is activated. After the device powered off to sleep mode it would not reconnect to zLink on restart. The "Connecting" message would cycle until I got MFi Hardware Fail, MFi IC Fail and MFi Read Fail #2 messages. If I rebooted the unit, either by disconnecting from constant power or using RST button zLink would then connect, but would fail to connect after next sleep phase. The supplier was no help. I thought it must be a power issue so I worked through the power options on the factory settings menu. Changing the default power mode from "On" to "Memory Status of Last" fixed the problem and zLink now connects automatically on start up. I hope this helps.
GL350 said:
I have been working through the installation of a Wondefoo Headunit in a Mercedes GL350. I purchased the unit off AliExpress. The headunit has zlink installed. I have an iPhone so was using it for Carplay. Bluetooth and WIFI connect okay to the headunit. The first time I booted up the unit zLink connected and Carplay worked. The device is connected to constant 12v power so it powers off to sleep mode and warm starts the next time the ACC power is activated. After the device powered off to sleep mode it would not reconnect to zLink on restart. The "Connecting" message would cycle until I got MFi Hardware Fail, MFi IC Fail and MFi Read Fail #2 messages. If I rebooted the unit, either by disconnecting from constant power or using RST button zLink would then connect, but would fail to connect after next sleep phase. The supplier was no help. I thought it must be a power issue so I worked through the power options on the factory settings menu. Changing the default power mode from "On" to "Memory Status of Last" fixed the problem and zLink now connects automatically on start up. I hope this helps.
Click to expand...
Click to collapse
How to enter that menu option, I can't find it anywhere. Please help me.
Virus1988 said:
How to enter that menu option, I can't find it anywhere. Please help me.
Click to expand...
Click to collapse
On my unit the factory settings menu is located in the "car settings" menu, which is one of the options under the main "settings" app. You may need to scroll down to find it.
To add to my earlier post, I am still trying to get the diversity antenna working properly for radio reception and I disconnected the headunit to work on that. When I reconnected it the same problem reappeared; that is, not connecting unless I repowered or reset the unit. I went back to the power settings and it was still set to "Memory Status of Last". It's hard to know what this function actually means. I toggled it back through the other options and played around with a few other settings and eventually the problem went away. I wasn't very structured in my approach to this so I don't know what change fixed the issue. I am about to install some heat sinks and a fan to avoid any overheating issues which means I will need to depower the unit again. I will do some more trial and error to see if I can work out what the answer might be. It doesn't seem to be anything to do with hotspot settings as I didn't change those.
GL350 said:
On my unit the factory settings menu is located in the "car settings" menu, which is one of the options under the main "settings" app. You may need to scroll down to find it.
To add to my earlier post, I am still trying to get the diversity antenna working properly for radio reception and I disconnected the headunit to work on that. When I reconnected it the same problem reappeared; that is, not connecting unless I repowered or reset the unit. I went back to the power settings and it was still set to "Memory Status of Last". It's hard to know what this function actually means. I toggled it back through the other options and played around with a few other settings and eventually the problem went away. I wasn't very structured in my approach to this so I don't know what change fixed the issue. I am about to install some heat sinks and a fan to avoid any overheating issues which means I will need to depower the unit again. I will do some more trial and error to see if I can work out what the answer might be. It doesn't seem to be anything to do with hotspot settings as I didn't change those.
Click to expand...
Click to collapse
Hello. Try disabling WiFi and USB initialization.
Settings MOD - Mod Settings - Car - Check WiFi after reboot and USB initialization
Hey guys, new here.
So I have a Navifly PX6 head unit installed on my 2019 Honda Civic. I’ve been searching everywhere for a fix for this issue and this thread seems to be the best bet.
So I’ve been getting this hardware error code for almost 2 years now. Along with the code, my steering wheel controls stop working and the clock on my dash becomes unsynchronized. That led me to believe that it was the Canbus adapter. I contacted the manufacturer and got a replacement adapter twice now. both times, it would work for a few months and then start acting up again.
I tried looking up the settings you guys are talking about but can’t seem to find anything like it. I’m also on Android 10 if that helps at all
I’ll add that this doesn’t happen all the time, but usually anywhere between every week, to once a month. And I can fix it every time by just resetting my unit via the Reset pin
I don't pretend to be an expert on this issue, but was trying to provide some input on what seemed to work for me. Last weekend I installed a cooling fan and some heatsinks onto my headunit as I have seen a number of reports of overheating issues. To do that I disconnected from the power, and again when I reconnected I got the same error message as you are getting. I tried my fix (changing the power settings) and it worked again. I don't know why. Your unit must have a factory settings menu somewhere. From what I can see online, different manufacturer's put them in different places in the settings menus. If you have a manual for your unit it may show in there how to access the factory settings. You need to be careful when working in the factory settings as other reports indicate you can mess up your entire system. I limited myself to toggling the power options until the problem went away. This may be more difficult for you to do if it occurs sporadically.
Have you considered whether your performance issues might be an overheating problem? Reports on this forum and others indicate that overheating can cause erratic operation.
What is the Mai error can it be fixed? Will the car play dongle help.
Mimix3 said:
What is the Mai error can it be fixed? Will the car play dongle help.
Click to expand...
Click to collapse
Still haven't been able to fix it, but factory resetting the system seemed to work for the time being. Be careful though as some of my apps became unregistered and I needed to contact customer service. Car play dongle may help? At least in my case, I think there's an issue with one of the wiring harnesses.
Mod Translation
Is there an update that will fix the problem I am having with my radio?
when i turn on my car and the radio is on sometimes the wireless carplay works but when i turn off the radio because i leave the car for an hour... two... two... two days.
When I turn the radio off because I leave the car for an hour...two...a day..... When I go back to the car and turn on the radio, it activates the hotspot so that the radio and phone can connect (wireless carplay), the radio does not activate the hotspot automatically, if I navigate through the settings menu and try to activate it it shows me an error. the power button does not stay ON, and I cannot activate it in any way either manually or automatically.
When this happens to me, I have to hold down the power button on the radio and press it until the radio restarts and again activates the hotspot and allows me to use wireless carplay (sometimes I have to repeat the restart process two or three times until it finally works, again the radio automatically activates the hotspot and the phone works with carplay).
android px6 radio
android version 10
build number rk3399- user debug 10 qq2a.200305.004.a1 eng.hct.20210814.092831 test keys
kernel version 4.19.111+ kernel version 4.19.111+ kernel version 4.19.111+
mcu version mtce_hxd_v3.62e_1
19 September 2020 16:46:43
Original
¿Hola como estas? ¿me puedes ayudar?
¿Hay alguna actualización que solucione el problema que tengo con mi radio?
cuando enciendo mi carro y la radio esta activada a veces funciona el carplay inalámbrico pero cuando apago la radio porque dejo el
Cuando apago la radio porque dejo el coche una hora... dos... al día... Cuando vuelvo al coche y enciendo la radio, se activa el punto de acceso para que la radio y el teléfono se puede conectar (carplay inalámbrico), la radio no activa el punto de acceso automáticamente, si navego por el menú de configuración y trato de activar me muestra un error. el boton de encendido no se queda ENCENDIDO, y no puedo activarlo de ninguna forma ni manual ni automatico.
Cuando esto me sucede, tengo que mantener presionado el botón de encendido de la radio y presionarlo hasta que la radio se reinicia y nuevamente activa el punto de acceso y me permite usar carplay inalámbrico (a veces tengo que repetir el proceso de reinicio dos o tres veces hasta que finalmente funciona, nuevamente la radio activa automáticamente el punto de acceso y el teléfono funciona con carplay).
radio android px6
android versión 10
número de compilación rk3399- depuración de usuario 10 qq2a.200305.004.a1 eng.hct.20210814.092831 claves de prueba
versión del núcleo 4.19.111+ versión del núcleo 4.19.111+
versión mcu mtce_hxd_v3.62e_1
19 de septiembre de 2020 16:46:43
Traducido con www.DeepL.com/Translator (versión gratuita)
zaricuecalo said:
¿Hola como estas? ¿me puedes ayudar?
¿Hay alguna actualización que solucione el problema que tengo con mi radio?
cuando enciendo mi carro y la radio esta activada a veces funciona el carplay inalámbrico pero cuando apago la radio porque dejo el
Cuando apago la radio porque dejo el coche una hora... dos... al día... Cuando vuelvo al coche y enciendo la radio, se activa el punto de acceso para que la radio y el teléfono se puede conectar (carplay inalámbrico), la radio no activa el punto de acceso automáticamente, si navego por el menú de configuración y trato de activar me muestra un error. el boton de encendido no se queda ENCENDIDO, y no puedo activarlo de ninguna forma ni manual ni automatico.
Cuando esto me sucede, tengo que mantener presionado el botón de encendido de la radio y presionarlo hasta que la radio se reinicia y nuevamente activa el punto de acceso y me permite usar carplay inalámbrico (a veces tengo que repetir el proceso de reinicio dos o tres veces hasta que finalmente funciona, nuevamente la radio activa automáticamente el punto de acceso y el teléfono funciona con carplay).
radio android px6
android versión 10
número de compilación rk3399- depuración de usuario 10 qq2a.200305.004.a1 eng.hct.20210814.092831 claves de prueba
versión del núcleo 4.19.111+ versión del núcleo 4.19.111+
versión mcu mtce_hxd_v3.62e_1
19 de septiembre de 2020 16:46:43
Traducido con www.DeepL.com/Translator (versión gratuita)
Click to expand...
Click to collapse
Mod Translation
I use a mod of this forum for my radio that cost me 10 €, anyway sometimes it fails equally, the only solution is that before turning on the radio you activate wifi and blueto and then see if the app goes but just as you restart and should go to the first, if you have the option to make carplay zlink open namas turn on the radio is a good option too. I hope to have helped you.
Original
Yo uso un mod de este foro para mi radio que me costo 10€, de todas maneras a veces falla Igualmente, la unica solucion es que antes de encender la radio actives wifi y blueto y luego ver si va la app sino tal cual reinicias y deberia ir a la primera, si tienes la opcion de hacer que carplay zlink abra namas encender la radio es una buena opcion tambien. Un saludo espero haberte ayudado.
Virus1988 said:
Mod Translation
I use a mod of this forum for my radio that cost me 10 €, anyway sometimes it fails equally, the only solution is that before turning on the radio you activate wifi and blueto and then see if the app goes but just as you restart and should go to the first, if you have the option to make carplay zlink open namas turn on the radio is a good option too. I hope to have helped you.
Original
Yo uso un mod de este foro para mi radio que me costo 10€, de todas maneras a veces falla Igualmente, la unica solucion es que antes de encender la radio actives wifi y blueto y luego ver si va la app sino tal cual reinicias y deberia ir a la primera, si tienes la opcion de hacer que carplay zlink abra namas encender la radio es una buena opcion tambien. Un saludo espero haberte ayudado.
Click to expand...
Click to collapse
Yes this is the problem with MTCx devices, including modded ROMs. Consider just using the android on the device, if Android Auto is want you want, these Chinese origin hacked devices are not what you want.
Virus1988 said:
Traducción de mods
Yo uso un mod de este foro para mi radio que me costó 10€, de todos modos a veces falla igual, la única solución es que antes de encender la radio actives wifi y blueto y luego ver si la app va pero igual reinicias y debe ir a la primera, si tiene la opcion de hacer carplay zlink open namas encender la radio tambien es una buena opcion. Espero haberte ayudado.
Original
Yo uso un mod de este foro para mi radio que me costo 10€, de todas maneras a veces falla igualmente, la unica solucion es que antes de encender la radio actives wifi y blueto y luego ver si va la app sino tal cual reinicias y deberia ir a la primera, si tienes la opcion de hacer que carplay zlink abra namas encender la radio es una buena opcion tambien. Un saludo espero haberte ayudado.
Click to expand...
Click to collapse
hello. the problem is that when i turn on the radio if the access point or the wifi does not activate itself, if i go into settings it is impossible to activate it so i have to restart the radio.
Sometimes it activates itself correctly and even then I have to do another reboot because it doesn't connect to the iphone.
marchnz said:
Sí, este es el problema con los dispositivos MTCx, incluidas las ROM modificadas. Considere simplemente usar Android en el dispositivo, si Android Auto es lo que desea, estos dispositivos pirateados de origen chino no son lo que desea.
Click to expand...
Click to collapse
hello i have an iphone 12 ios 14.3
hola tengo un iphone 12 ios 14.3
hello, modifying things I have realized that if in the bluetooth settings you deactivate autoconect and automatic response, when you restart the radio the access point is activated and then I only have to go back to bluetooth settings and activate the autoconect and it works.
Is it possible that there is a conflict between bluetooth and wifi?
hola, modificando cosas me he dado cuenta que si en los ajustes de bluetooth desactivas autoconect y respuesta automatica, al reiniciar la radio se activa el punto de acceso y luego solo tengo que volver a ajustes de bluetooth y activar el autoconect y funciona.
¿Es posible que haya un conflicto entre bluetooth y wifi?
I have an error in the CTS profile match that gives me an error and I have not rooted the mobile...the support team tells me that it is not your original room...and I changed from room cn to room eu.... the McDonald's app doesn't work for me because of that..any solution to fix it without root?
jaimele said:
I have an error in the CTS profile match that gives me an error and I have not rooted the mobile...the support team tells me that it is not your original room...and I changed from room cn to room eu.... the McDonald's app doesn't work for me because of that..any solution to fix it without root?
Click to expand...
Click to collapse
Root it then..lol
Decrypted data, flashed modified super.img that is r/w with modified fstab, deleted some system apps, flashed 676.22 system drivers, gpu undervolted and slight overclocked to 692 mhz, twrp recovery, magisk and still I pass
Also didn't you flash custom recovery? Maybe because bootloader unlocked.. Not sure As soon as I received my device I unlocked bootloader and rooted.
JWnSC said:
No flasheé nada, solo recibió el terminal con la sala CN y lo cambió a través de la configuración y actualicé el archivo eu original de la sala ... y luego reinicié el móvil con el botón y el botón apagar - y me sale bloqueo del gestor de arranque. ..
Click to expand...
Click to collapse
Así que no sé por qué me sale ese error.
jaimele said:
Así que no sé por qué me sale ese error.
Click to expand...
Click to collapse
Reflash firmware to see if issue persist.
Just root it and bypass safteynet once and for all and free your device from 3rd party handcuffs and this type of nonesense. You own your device, not them.
No quiero rootearlo todavía... es difícil para mí instalar todas mis aplicaciones... incluso si hago una copia de seguridad, no copia todos los datos de todas las aplicaciones si no está rooteado
jaimele said:
No quiero rootearlo todavía... es difícil para mí instalar todas mis aplicaciones... incluso si hago una copia de seguridad, no copia todos los datos de todas las aplicaciones si no está rooteado
Click to expand...
Click to collapse
Hmm.. Well if you find out why it won't pass safety net even though your not rooted please let us know. I don't see how a stock device wouldn't pass it.. Like I say before, I think your bootloader being unlocked is affecting it.
Your bootloader is unlocked, that's why you're getting the error. Either install Magisk and patch the error, or go back to your original ROM and relock your bootloader (of course, without root, otherwise your smartphone won't work anymore).
Mitesoro said:
Su cargador de arranque está desbloqueado, por eso está recibiendo el error. Instale Magisk y corrija el error, o vuelva a su ROM original y vuelva a bloquear su cargador de arranque (por supuesto, sin root, de lo contrario su teléfono inteligente ya no funcionará).
Click to expand...
Click to collapse
It does not have root... Its original rom, I don't even know what it is... Last time I downloaded the one that came from the Red Magic website on 4.28 Europe/Asia and it doesn't work... I even installed a 3.18 version and it It left the phone useless and I had to format data..
As I have also seen, changing the text payload properties, deleting the "_un" file, it is configured to the global room, but of course I don't know if it is clean and it will continue with the error...
jaimele said:
It does not have root... Its original rom, I don't even know what it is... Last time I downloaded the one that came from the Red Magic website on 4.28 Europe/Asia and it doesn't work... I even installed a 3.18 version and it It left the phone useless and I had to format data..
Click to expand...
Click to collapse
Is OEM unlocking enabled on your device and you're unable to turn it off? If so, then your smartphone is unlocked, and you need to lock it; otherwise, the error will persist.
[ fastboot flashing unlock ] for unlocking bootloader
[ fastboot flashing lock ] for locking bootloader
The phone has the oem disabled so the bootloader is not unlocked...it is a super rare case. I understand a lot about this type of thing and it has never happened to me, but I will need a specific file to fix in a non-root way, I don't want to root it. I know that with magisk I fix it, but in this case it's a bug in the original room, the safetynet application detects it as if it was tricked
jaimele said:
The phone has the oem disabled so the bootloader is not unlocked...it is a super rare case. I understand a lot about this type of thing and it has never happened to me, but I will need a specific file to fix in a non-root way, I don't want to root it. I know that with magisk I fix it, but in this case it's a bug in the original room, the safetynet application detects it as if it was tricked
Click to expand...
Click to collapse
"Okay, that's really stupid. I thought maybe it would be the same mistake as mine. Maybe just open BL once and then close it again "
Mitesoro said:
"Okay, that's really stupid. I thought maybe it would be the same mistake as mine. Maybe just open BL once and then close it again "
Click to expand...
Click to collapse
I don't know what your problem is...
jaimele said:
The phone has the oem disabled so the bootloader is not unlocked...it is a super rare case. I understand a lot about this type of thing and it has never happened to me, but I will need a specific file to fix in a non-root way, I don't want to root it. I know that with magisk I fix it, but in this case it's a bug in the original room, the safetynet application detects it as if it was tricked
Click to expand...
Click to collapse
I am confused. Have you installed a new ROM or not?
You said you changed from "cn" to "eu". You said one ROM left the phone unusable. You must have "flashed" a new ROM, several times. Maybe the problem is that the original ROM's identity is somehow known, and anything else will cause this mismatch. Try restoring the "cn" ROM.
Mostly out of curiosity: Have you enabled Developer Options? Do they show any kind of entry for "OEM unlock", even if greyed-out?
Maybe you should install one of the idiot "root checkers", like Momo or TBChecker. You might get a more detailed explanation of what it doesn't like, which *might* be related to what is making "CTS Profile" not pass.
J.Michael said:
Estoy confundido. ¿Has instalado una nueva ROM o no?
Dijiste que cambiaste de "cn" a "eu". Dijiste que una ROM dejó el teléfono inutilizable. Debe haber "flasheado" una nueva ROM, varias veces. Tal vez el problema es que la identidad de la ROM original se conoce de alguna manera, y cualquier otra cosa causará esta falta de coincidencia. Intenta restaurar la ROM "cn".
Principalmente por curiosidad: ¿Ha habilitado las Opciones de desarrollador? ¿Muestran algún tipo de entrada para "Desbloqueo OEM", incluso si están en gris?
Tal vez deberías instalar uno de los tontos "verificadores raíz", como Momo o TBChecker. Es posible que obtenga una explicación más detallada de lo que no le gusta, que *podría* estar relacionado con lo que hace que el "Perfil CTS" no pase.
Click to expand...
Click to collapse
If l change from rom uncommon to eucomon and it works correctly but does not pass the cts profile. The oem is grayed out and the bootloader is locked.
jaimele said:
If l change from rom uncommon to eucomon and it works correctly but does not pass the cts profile. The oem is grayed out and the bootloader is locked.
Click to expand...
Click to collapse
I thought you said that you started with "cn" and changed to "eu". I'm saying maybe that's what's wrong. Maybe the device somehow identifies itself as "naturally cn", so if it is not "cn", and you are not using a Magisk module to "spoof" its properties, it fails CTS Profile.
Even if you don't want to install Magisk, you might gain some insight by reading in the Magisk thread. I'm not sure what affects CTS Profile.
J.Michael said:
Pensé que dijiste que comenzaste con "cn" y cambiaste a "eu". Estoy diciendo que tal vez eso es lo que está mal. Tal vez el dispositivo de alguna manera se identifique como "naturalmente cn", por lo que si no es "cn", y no está utilizando un módulo Magisk para "falsificar" sus propiedades, falla el perfil CTS.
Incluso si no desea instalar Magisk, puede obtener información leyendo el hilo de Magisk. No estoy seguro de qué afecta al perfil CTS.
Click to expand...
Click to collapse
Pero antes recuerdo que funcionaba sin ser cn