Develop Bugs

Unable to boot into twrp temporarily

I'm following this guide to root my moto g7 play: https://forum.xda-developers.com/t/how-to-successfully-install-twrp-for-g7-play.3979701/
When I type: fastboot boot recovery.img
it responds with:
downloading 'boot.img'...
OKAY [ 0.613s]
booting...
OKAY [ 0.168s]
finished. total time: 0.782s
And then it just stays at the TWRP splash screen forever.
What am I doing wrong?

[QUOTE = "spinalcmp, publicación: 84084691, miembro: 11330745"]
Estoy siguiendo esta guía para rootear mi moto g7 play: https://forum.xda-developers.com/t/how-to-successfully-install-twrp-for-g7-play.3979701/
Cuando escribo: fastboot boot recovery.img
responde con:
descargando 'boot.img' ...
Bien [0,613 s]
arrancando ...
De acuerdo [0.168 s]
terminado. tiempo total: 0.782s
Y luego permanece en la pantalla de inicio de TWRP para siempre.
¿Qué estoy haciendo mal?
[/CITAR]
Este problema se debe a que el método es antiguo y el twrp es una versión que no funcionó en todos los dispositivos, busque la versión 3.4 de twrp y vuelva a intentarlo

Este problema se debe a que el método es antiguo y el twrp es una versión que no funcionó en todos los dispositivos, busque la versión 3.4 de twrp y vuelva a intentarlo

https://twrp.me/motorola/motorolamotog7play.html <--- Link to official TWRP website.
Redownload twrp file and reinstall it

Help google pixel 3a xl rom stock flash

I bought a google pixel 3a xl phone from amazon spain and this is what happened! when I turn on the phone it has an operating system totally unknown to me, I don't have google services, blocked bootloader, no usb debugging option, apparently it's from Verizon and I don't know what else to do, please help, I post photos and videos for you great help! the phone changed the storage slot from "b" (where the rom is) and "a" where there is nothing, thank you very much, thank you when turning on the phone apparently it is from the matrix
@michbenitez Telegram
{
"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"
}

While on slot_a try visiting this link using chrome browser. It's the latest android 11 factory image. Since you're bootloader locked you're not going to be able to flash anything that's not officially signed. If you have errors, make a note of the errors you receive and post them.

41rw4lk said:
Mientras esté en slot_a, intente visitar este enlace usando el navegador Chrome. Es la última imagen de fábrica de Android 11. Como el gestor de arranque está bloqueado, no podrá actualizar nada que no esté firmado oficialmente. Si tiene errores, tome nota de los errores que reciba y publíquelos.
Click to expand...
Click to collapse
The error I get is that the oem is blocked, no more errors appear, the equipment restarts again.

41rw4lk said:
While on slot_a try visiting this link using chrome browser. It's the latest android 11 factory image. Since you're bootloader locked you're not going to be able to flash anything that's not officially signed. If you have errors, make a note of the errors you receive and post them.
Click to expand...
Click to collapse
in slot_b is the corrupted rom it doesn't matter?

It does matter, but your main goal right now is to get stock flashed (if you can),then enable oem unlocking so you can unlocked your bootloader and get rid of whatever garbage rom that is. There is a thread around here for unlocking VZW bootloader.Try downloading this stock firmware (June patched android 11) and try flashing it yourself using the flash all. I'd try on slot_a first, hopefully that one is more recognized as stock.

41rw4lk said:
Sí importa, pero su objetivo principal en este momento es actualizar el stock (si puede), luego habilite el desbloqueo de oem para que pueda desbloquear su gestor de arranque y deshacerse de cualquier rom basura que sea. Hay un hilo por aquí para desbloquear el cargador de arranque VZW. Intente descargar este firmware de stock (Android 11 parcheado en junio) e intente actualizarlo usted mismo usando el flash all. Primero probaría slot_a, con suerte que uno sea más reconocido como stock.
Click to expand...
Click to collapse
41rw4lk said:
Sí importa, pero su objetivo principal en este momento es actualizar el stock (si puede), luego habilite el desbloqueo de oem para que pueda desbloquear su gestor de arranque y deshacerse de cualquier rom basura que sea. Hay un hilo por aquí para desbloquear el cargador de arranque VZW. Intente descargar este firmware de stock (Android 11 parcheado en junio) e intente actualizarlo usted mismo usando el flash all. Primero probaría slot_a, con suerte que uno sea más reconocido como st
Click to expand...
Click to collapse
41rw4lk said:
Sí importa, pero su objetivo principal en este momento es actualizar el stock (si puede), luego habilite el desbloqueo de oem para que pueda desbloquear su gestor de arranque y deshacerse de cualquier rom basura que sea. Hay un hilo por aquí para desbloquear el cargador de arranque VZW. Intente descargar este firmware de stock (Android 11 parcheado en junio) e intente actualizarlo usted mismo usando el flash all. Primero probaría slot_a, con suerte que uno sea más reconocido como stock.when i flash the rom i get an error flash.bar script on my computer screen, what do you think it could be? and on the adb screen it says: it is blocked
Click to expand...
Click to collapse
41rw4lk said:
It does matter, but your main goal right now is to get stock flashed (if you can),then enable oem unlocking so you can unlocked your bootloader and get rid of whatever garbage rom that is. There is a thread around here for unlocking VZW bootloader.Try downloading this stock firmware (June patched android 11) and try flashing it yourself using the flash all. I'd try on slot_a first, hopefully that one is more recognized as stock.
Click to expand...
Click to collapse
when i flash the rom i get an error flash.bar script on my computer screen, what do you think it could be? and on the adb screen it says: it is blocked

41rw4lk said:
It does matter, but your main goal right now is to get stock flashed (if you can),then enable oem unlocking so you can unlocked your bootloader and get rid of whatever garbage rom that is. There is a thread around here for unlocking VZW bootloader.Try downloading this stock firmware (June patched android 11) and try flashing it yourself using the flash all. I'd try on slot_a first, hopefully that one is more recognized as stock.
Click to expand...
Click to collapse
Could you help me by entering my pc?

No, I don't do remote desktop. Make sure you have the latest adb and fastboot installed. You can check the version you have installed easily. If you need the latest, you can grab them here. Also, if you could post the output of your cmd prompt that would help.

41rw4lk said:
No, no hago escritorio remoto. Asegúrese de tener instalados los últimos adb y fastboot. Puede comprobar la versión que ha instalado fácilmente. Si necesita lo último, puede obtenerlo aquí . Además, si pudiera publicar la salida de su indicador de cmd, eso ayudaríel código
Click to expand...
Click to collapse
41rw4lk said:
It does matter, but your main goal right now is to get stock flashed (if you can),then enable oem unlocking so you can unlocked your bootloader and get rid of whatever garbage rom that is. There is a thread around here for unlocking VZW bootloader.Try downloading this stock firmware (June patched android 11) and try flashing it yourself using the flash all. I'd try on slot_a first, hopefully that one is more recognized as stock.
Click to expand...
Click to collapse
I did everything as you told me but it keeps getting error bounces to bootloader

there is no way to unlock a verizon bootloader. you need to call amazon and request a refund. sometimes you can get lucky if you try to unlock before ever entering a sim card, but given the device was bought used, and can't boot to the system, that ship has long since set sail. this is a full brick. the only way out is to flash a factory image with fastboot, and that can't be done with a locked bootloader.

Well there is a way to unlock a VZW bootloader, I mean they did it to flash whatever garbage is on there. However I do agree, call Amazon and make them sort it. Basic troubleshooting hasn't and isn't going to fix this. As much as I like a challenge, this is just annoying. Call Amazon and tell them you bought someone else's **** up and move on from that mess.

sounds like what's on there is the stock verizon firmware, and the kernel just corrupted somehow. vzw is just an abbreviation for verizon wireless.
that, or like like said, they got lucky and unlocked before they put the sim card in, then relocked it before sending it out.
send it back. Amazon's return policy is too good to be dealing with stress like this.

How To Guide Root Moto G20.

Guide to Rooting using a BOOT.IMG patched with Magisk.
ONLY WORKS WITH "MINIMAL ADB & FASTBOOT" - USING "PLATAFORM TOOLS" DOES NOT INSTALL.
It must be updated to the latest version "RTA31.68-25"
Turn off your phone. After power off, enter FASTBOOT mode, press volume + button and power button.
fastboot flash boot_a Boot_Root.img
Once it is done, type fastboot reboot and when it starts you will have to install magisk.apk.
(BOOT_ROOT.IMG FILE SHARED IN A TELEGRAM GROUP, AN ATTEMPTED TO PATCH THE BOOT.IMG FILE WITH THE MAGISK APPLICATION BUT DOES NOT BOOT. FOR NOW IT IS THE ONLY METHOD THAT WORKS.)
WE CONTINUE INVESTIGATING METHODS TO INSTALL GSI PERMANENTLY.
UNTIL NOW THE GSI ARE INSTALLED ONLY TEMPORARILY USING DSU.
_---------------------------
Guía para Rootear usando un BOOT.IMG parchado con Magisk.
SOLO FUNCIONA CON "MINIMAL ADB & FASTBOOT" - USANDO "PLATAFORM TOOLS" NO INSTALA.
Debe estar actualizado a la última versión "RTA31.68-25"
Apaga tu teléfono. Una vez apagado, ingrese al modo FASTBOOT, presione el botón de volumen + y el botón de encendido.
fastboot flash boot_a Boot_Root.img
Una vez que termine, escriba fastboot reboot y cuando comience, tendrá que instalar magisk.apk.
(ARCHIVO BOOT_ROOT.IMG COMPARTIDO EN UN GRUPO DE TELEGRAM, SE INTENTO PARCHAR EL ARCHIVO BOOT.IMG CON LA APLICACIÓN DE MAGISK PERO NO BOOTEA. POR AHORA ES EL ÚNICO MÉTODO QUE FUNCIONA.)
SEGUIMOS INVESTIGANDO MÉTODOS PARA INSTALAR GSI DE FORMA PERMANENTE.
HASTA AHORA LAS GSI SE INSTALAN SOLO TEMPORALMENTE USANDO DSU.
DOTOS 5.2 Y PIXEL EXPERIENCE A12 SUPER ESTABLES.

Grom9A said:
Guía para Rootear usando un BOOT.IMG parchado con Magisk.
SOLO FUNCIONA CON "MINIMAL ADB & FASTBOOT" - USANDO "PLATAFORM TOOLS" NO INSTALA.
Debe estar actualizado a la última versión "RTA31.68-25"
Apaga tu teléfono. Una vez apagado, ingrese al modo FASTBOOT, presione el botón de volumen + y el botón de encendido.
fastboot flash boot_a Boot_Root.img
Una vez que termine, escriba fastboot reboot y cuando comience, tendrá que instalar magisk.apk.
(ARCHIVO BOOT_ROOT.IMG COMPARTIDO EN UN GRUPO DE TELEGRAM, SE INTENTO PARCHAR EL ARCHIVO BOOT.IMG CON LA APLICACIÓN DE MAGISK PERO NO BOOTEA. POR AHORA ES EL ÚNICO MÉTODO QUE FUNCIONA.)
SEGUIMOS INVESTIGANDO MÉTODOS PARA INSTALAR GSI DE FORMA PERMANENTE.
HASTA AHORA LAS GSI SE INSTALAN SOLO TEMPORALMENTE USANDO DSU.
DOTOS 5.2 Y PIXEL EXPERIENCE A12 SUPER ESTABLES.
Click to expand...
Click to collapse
Spoiler: Please use English on XDA
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.
📚 XDA Developers Forum Rules 📚
XDA-Developers FORUM RULES List of Forum Moderators, click HERE Delete Your XDA Account HERE 1. Search before posting. Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new...
forum.xda-developers.com
Google translation below
Guide to Rooting using a BOOT.IMG patched with Magisk.
ONLY WORKS WITH "MINIMAL ADB & FASTBOOT" - USING "PLATAFORM TOOLS" DOES NOT INSTALL.
It must be updated to the latest version "RTA31.68-25"
Turn off your phone. After power off, enter FASTBOOT mode, press volume + button and power button.
fastboot flash boot_a Boot_Root.img
Once it is done, type fastboot reboot and when it starts you will have to install magisk.apk.
(BOOT_ROOT.IMG FILE SHARED IN A TELEGRAM GROUP, AN ATTEMPTED TO PATCH THE BOOT.IMG FILE WITH THE MAGISK APPLICATION BUT DOES NOT BOOT. FOR NOW IT IS THE ONLY METHOD THAT WORKS.)
WE CONTINUE INVESTIGATING METHODS TO INSTALL GSI PERMANENTLY.
UNTIL NOW THE GSI ARE INSTALLED ONLY TEMPORARILY USING DSU.
DOTOS 5.2 AND PIXEL EXPERIENCE A12 SUPER STABLE.
Click to expand...
Click to collapse

It must be updated to the latest version "RTA31.68-25"
Click to expand...
Click to collapse
Hi, I've upgraded my system but it's only RTA31.68-20 -> I can't upgrade to 25, because there is no such option.
Should it work if I use your Boot_Root.img?

iolk said:
Hi, I've upgraded my system but it's only RTA31.68-20 -> I can't upgrade to 25, because there is no such option.
Should it work if I use your Boot_Root.img?
Click to expand...
Click to collapse
I don't know, now I'm using Android 12 GSI

iolk said:
Hi, I've upgraded my system but it's only RTA31.68-20 -> I can't upgrade to 25, because there is no such option.
Should it work if I use your Boot_Root.img?
Click to expand...
Click to collapse
There's no more updates? Should be one more

Grom9A said:
There's no more updates? Should be one more
Click to expand...
Click to collapse
I think version 25 is available only for Brasil & Latin America - see this link:
MOTO G20 | Firmware Down
www.firmwaredown.com.br
As I have an European version I have only ver 20-2
How was the Boot_Root.img file produced? I could use Magisk to patch my ver-20-2 system but you wrote that it didn't work with Magisk.

iolk said:
I think version 25 is available only for Brasil & Latin America - see this link:
MOTO G20 | Firmware Down
www.firmwaredown.com.br
As I have an European version I have only ver 20-2
How was the Boot_Root.img file produced? I could use Magisk to patch my ver-20-2 system but you wrote that it didn't work with Magisk.
Click to expand...
Click to collapse
Some people try that on the telegram group, and they share the boot_root file

iolk said:
I think version 25 is available only for Brasil & Latin America - see this link:
MOTO G20 | Firmware Down
www.firmwaredown.com.br
As I have an European version I have only ver 20-2
Click to expand...
Click to collapse
I have to revise what I've written: after one day ver 20 changed to 20-2, and then one day later, it offered to upgrade to ver 25. So now I have ver 25. Sorry for misinformation.

Grom9A said:
fastboot flash boot_a Boot_Root.img
Click to expand...
Click to collapse
Hi again, I tried today to flash, but I got this error:
fastboot: error: boot partition is smaller than boot image
I'm on linux and I'm using regular platform tools. Can this be the reason?
You said "ONLY WORKS WITH "MINIMAL ADB & FASTBOOT" - USING "PLATAFORM TOOLS" DOES NOT INSTALL."
Was that the error that you experienced when using platform tools?
-------- EDIT
I found some Windows machine and can confirm that the Grom9A's method works with Minimal Adb & Fastboot.
I couldn't find any alternative for Linux.

I flashed the boot_root.img but when I reboot the phone magisk says its isn't installed, tried to patch boot.img but same thing, also my pc dosend recognize my device when it's on fastboot, have to enter on bootloader
also I have another problem, i cant unlock bootloader, because when i run the get_oem_data comand the numbers don't shown, it dont have any error mensage just the number are missing

[Guide] Easy Way to Get Lineage+Magisk+Gapps [Xperia 10]

Hello, after several days trying to get Lineage with Magisk and NikGapps... I have succeeded.
I know that in this forum many people know much more than me and they will not need this tutorial, I am a newbie and this guide is for newbies. I accept corrections.
With my Xperia 10 I had a lot of problems. So I would like to return the help they have given me, the way is by writing this little guide.
1. First we unlock the bootloader:
2. (Optional) Install a clean Stock ROM with Emma (easier) or Newflasher (you need to download the firmware/ROM from Xperifirm first).
3. We put the mobile in Fastboot mode (Power + Vol-) and connect it to the computer. I had to use Linux on the computer, since Windows did not recognize the fastboot mode of the Xperia 10 (but it did in ADB).
4. The command to install TWRP is normally "fasboot boot twrp.img", but it didn't work for me (nor did others I tried). Only this one worked for me:
fastboot flash boot_a twrp.img
fastboot flash boot_b twrp.img
I used both. What this does is install TWRP on partitions A and B. It may be crazy, but it's the only thing that worked for me.
5. Start TWRP with Power+Vol-.
6. Install Lineage.
7. Reboot the System and check that Lineage loads.
8. From this step I had serious problems, because I was trying to keep TWRP (so I could install Magisk and Nikgapps). However, I couldn't get Lineage to work while having TWRP.
8.1. Start Lineage Recovery with Power+Vol-
8.2. "Apply update"
8.3. "Choose from disk"
8.4. Select Magisk-v21.1.zip
8.5. "Signature verification failed. Install anyway?" AND IT IS
8.6. We restart
9.1. Start Lineage Recovery with Power+Vol-
9.2. "Apply update"
9.3. "Choose from disk"
9.4. Select the Gapps file (in my case: NikGapps-core-arm64-11-20220222-signed.zip)
9.5. "Signature verification failed. Install anyway?" AND IT IS
9.6. We restart
I suppose that steps 8 and 9 can be done at once, but I preferred to do it that way for greater security.

Tutorial made in Spanish and translated into English:
---
Hola, tras varios días intentando conseguir tener Lineage con Magisk y NikGapps... lo he conseguido.
Sé que en este foro mucha gente sabe mucho más que yo y no le hará falta este tutorial, yo soy un novato y esta guía es para novatos. Acepto correcciones.
Con mi Xperia 10 tuve muchos problemas. Así que quisiera devolver la ayuda que me han prestado, la forma es escribiendo esta pequeña guía.
1. Primero desbloqueamos el bootloader:
2. (Opcional) Instalamos una ROM Stock limpia con Emma (más fácil) o Newflasher (hace falta primero descargar el firmware/ROM desde Xperifirm).
3. Ponemos el móvil en modo Fastboot (Power+Vol-) y lo conectamos al ordenador. Yo tuve que usar Linux en el ordenador, ya que Windows no me reconocía el modo fastboot del Xperia 10 (pero sí en ADB).
4. El comando para instalar TWRP normalmente es "fasboot boot twrp.img", pero a mí no me funcionó (tampoco otros que probé). Solamente me funcionó este:
fastboot flash boot_a twrp.img
fastboot flash boot_b twrp.img
Usé los dos. Esto lo que hace es instalar TWRP en las particiones A y B. Quizá sea una locura, pero es lo único que me funcionó.
5. Inicia TWRP con Power+Vol-.
6. Instala Lineage.
7. Reinicia el Sistema y comprueba que se carga Lineage.
8. A partir de este paso tuve serios problemas, porque yo intentaba conservar TWRP (y así poder instalar Magisk y Nikgapps). Sin embargo, no pude conseguir que Lineage funcionara teniendo TWRP.
8.1. Inicia el Recovery de Lineage con Power+Vol-
8.2. "Aplly update"
8.3. "Choose from disk"
8.4. Seleccionar Magisk-v21.1.zip
8.5. "Signature verification failed. Install anyway?" YES
8.6. Reiniciamos
9.1. Inicia el Recovery de Lineage con Power+Vol-
9.2. "Aplly update"
9.3. "Choose from disk"
9.4. Seleccionar el archivo de Gapps (en mi caso: NikGapps-core-arm64-11-20220222-signed.zip)
9.5. "Signature verification failed. Install anyway?" YES
9.6. Reiniciamos
Supongo que los pasos 8 y 9 pueden hacerse de una sola vez, pero yo preferí hacerlo así para mayor seguridad.

born2bkilled said:
has anyone had any luck getting magisk 21.1 to work with this rom and twrp yet?
im going round in circles trying to root after updating. i can install magisk from twrp, but i end up in a bootloop, then installing the bootloop fix from twrp wipes magisk and breaks root.
i know 21.1 is a beta and likely doesnt support sony phones yet, but someone might have a fix.
EDIT: I have root working now. Anyone having trouble, DONT install twrp to ramdisk. just leave the lineageOS recovery in place and use fastboot on a pc to boot twrp when you need it.
I did the following:
1. fresh stock firmware via newflash
2.flash sony software binaries for a11
3. fastboot boot twrp.img
4.swap to partition b
5. power off
6. fastboot boot twrp.img (check you are booted to partition b)
7. flash lineageos 18
8.reboot select partition a and POWER OFF
9. fastboot boot twrp.img
10. check partition is a
11. flash copy partition.zip
12. flash magisk 21.1.zip
13. flash nikGapps basic for a11
14. reboot system
15. install magiskmanager 8.0.3.apk
16. reboot
17. update your apps on playstore.
18. PROFIT.
lineage os18 rooted on my xperia 10.
Click to expand...
Click to collapse
I tried to do it this way, but it didn't work for me (maybe because I'm very new to Xperia).

LG G7 DOESN'T WANT TO UNLOCK BOOTLOADER

estaba siguiendo un tutorial para desbloquear el botlooader en mi lg g7 , pero cuando llego a la parte de poner el dispositivo en modo botlooader y sigo los pasos de abril powershell en la carpeta de adb plalform-tools escribo cmd , fastboot flash frp y muevo el archivo frp , doy enter y todo bien pero cuando escribo rl comando fastboot oem unlock dice FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed siempre que lo pongo. necesito ayuda
Mod translation via GT:
i was following a tutorial to unlock the botlooader on my lg g7 , but when i get to the part of putting the device in botlooader mode and i follow the steps of april powershell in the adb plalform-tools folder i type cmd , fastboot flash frp and move the frp file, I hit enter and all is well but when I type the command fastboot oem unlock it says FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed whenever I put it. I need help

you must check if your pc detect device in fastboot mode...

bee gees said:
you must check if your pc detect device in fastboot mode...
Click to expand...
Click to collapse
si la detecta pongo en comando fastboot devices y me aparece mi dispositivo
Mod translation via GT: If it detects it, I put the fastboot devices command and my device appears.

JorgeTODOROKI said:
si la detecta pongo en comando fastboot devices y me aparece mi dispositivo
Click to expand...
Click to collapse
Cada vez que pongo fastboot oem unlock me dice eso
Mod translation via GT: Every time I put fastboot oem unlock it tells me that
{
"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"
}

in device manager of your pc check if your device is detected. not is the same android adb interface and android bootloader interface...

Cuando esta en modo EDL mi pc lo reconoce como esta en la imagen , pero cuando esta en modo botlooader mi pc lo reconoce como android device single adb
Mod translation via GT: When it is in EDL mode my pc recognizes it as it is in the image, but when it is in botloader mode my pc recognizes it as android device single adb

asi me aparece en el modo botlooader , pero pongo el comando y no funciona fastboot oem unlock
Mod translation via GT: This is how it appears to me in bootloader mode, but I put the command and fastboot oem unlock does not work

@JorgeTODOROKI
Greetings, and welcome to XDA. As a one time courtesy, I have translated your thread title and first 5 posts! I will ask you politely to PLEASE be respectful and observant of XDA Rule #4
for all of your future posts:
Spoiler: XDA Rule #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.
Thank you for your cooperation, and enjoy your stay on XDA.
-Regards: Badger50