Hello, i need your help. I have a Moto Z2 Play, install the security patch but suddenly the phone while it was installed turned off and since then it only turns on the led light, I connect it in fastboot but only appears ''qualcomm HS-USB QDloader 9008 (COM7), and not let me flash it. I tried with a blankflas file but it doesn't flash, what can i do??. PLEASE HELP.
Thanks.
Como recuperar meu pacote chinês com uma ROM xt1710-11 Nzs26.71-36 / 36. Alguém tem esse estoque ROM? Peça alguma coisa o aparelho aceita ... Por favor ..
robertmello said:
Como recuperar meu pacote chinês com uma ROM xt1710-11 Nzs26.71-36 / 36. Alguém tem esse estoque ROM? Peça alguma coisa o aparelho aceita ... Por favor ..
Click to expand...
Click to collapse
maybe you can test with this: https://forum.xda-developers.com/z2-play/help/fastboot-xt1710-11-china-mobile-modem-t3801969
With this rom: https://mirrors.lolinet.com/firmware/moto/albus_retcn/official/RETCN/XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-97-41-9_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
alghuien logro solucionar el fullbrick de moto z2 play
Si tu moto Z2 Play hicieras lo que hicieras tratando de modificar el sistema se te apago y solo cuando lo conectas prende el led nosotros te enviamos un archivo de manos de 1mb que lo sacara de ahí. Es el Blank Flash, Investiga en internet y veras que hay cientos, este nosotros lo programamos y en menos de 20 segundos tu teléfono encenderá de nuevo. Lo enviamos por email
Did you hard Brick your Moto Z2 Play, We have the only Blank flash that Will boot your cell in less tan 20 seconds. (No screen just blinking led when you plugg it )
Review what is that blank flash, is not aviavle any whare because we program it.
SOLUCION YA !!! (Siguiente Link)
How I solved mine
To be direct, as honest a posible. I just went into AT&T, and my warranty was able to run over the phone. I know, I unlocked the Bootloader, I clearly voided warranty, and Motorola was even aware of that, somehow, due to maybe how the warranty runs with AT&T they finally replaced the main board.
Whenever your phone gets into the QUALCOMM Modem Recovery, is pretty much death, if you do not have a Blankflash for the specific OS, Model, and Bootloader version. But if you got into the problem, without voiding anything your chances area way better then, and maybe just give it a shot.
Or, If you are already outside warranty, It may be the end. Unless a Blackflash for Oreo gets out, that's the only way to actually unbrick these phones, and Motorola is not that good to just going ahead with everyone having the BlankFlash, since that file, can unlock any phone and that means stealing being easier for that specific model.
That's actually my suggestion, if you have warranty; maybe inside a carrier, just go and try.
motorolamexico said:
Si tu moto Z2 Play hicieras lo que hicieras tratando de modificar el sistema se te apago y solo cuando lo conectas prende el led nosotros te enviamos un archivo de manos de 1mb que lo sacara de ahí. Es el Blank Flash, Investiga en internet y veras que hay cientos, este nosotros lo programamos y en menos de 20 segundos tu teléfono encenderá de nuevo. Lo enviamos por email
Did you hard Brick your Moto Z2 Play, We have the only Blank flash that Will boot your cell in less tan 20 seconds. (No screen just blinking led when you plugg it )
Review what is that blank flash, is not aviavle any whare because we program it.
SOLUCION YA !!! (Siguiente Link)
Click to expand...
Click to collapse
tenes el link?, gracias
So I got this phone after new years, and when I got home I decided to unlock the bootloader because I wanted to root it. Long story **** I found the process too complicated (Unlike how I did it years ago for my previous xperia phone) so I gave up. Now my phone says something about phone is unlocked every time I turn it on and that's that.
I seem to be unable to get latest android update for my phone, I looked at the sony website and used my IMEI number and it says I should be able to install oreo on my device, but there are no updates on my device.
What must I do in order to get the oreo update for my phone? At this point I don't care for rooting my device so any help is extremely appreciated.
Thanks in advance
Phone XA1 Plus
G3423 International
Build number : 48.0.A.1.99
sirxazor said:
So I got this phone after new years, and when I got home I decided to unlock the bootloader because I wanted to root it. Long story **** I found the process too complicated (Unlike how I did it years ago for my previous xperia phone) so I gave up. Now my phone says something about phone is unlocked every time I turn it on and that's that.
I seem to be unable to get latest android update for my phone, I looked at the sony website and used my IMEI number and it says I should be able to install oreo on my device, but there are no updates on my device.
What must I do in order to get the oreo update for my phone? At this point I don't care for rooting my device so any help is extremely appreciated.
Thanks in advance
Phone XA1 Plus
G3423 International
Build number : 48.0.A.1.99
Click to expand...
Click to collapse
Hola amigo, yo acabo de desbloquear el bootloader de mi xperia xa1 plus G3423 es facil desde la pagina de sony pides un código con tu numero de imei luego en flashtool colocas el código y en par de segundos desbloqueas bootloader, con la herramienta xperifirm descargas el firmware que desees según tu modelo y luego con flashtool haces el .ftf y lo quemas.
Con todo eso listo te queda el teléfono como nuevo ! en xperifirm esta la versión android oreo
Hola amigo, que bueno encontré alguien que habka español.
Tengo una duda sobre el abrir el bootloader, resulta que tengo igual el Xa1 plus y quiero abrir el bootloader pero no si si al hacerlo y perder las drmkeys se pierda calidad en cámara o las mejoras de imágen o si de alguna forma empeora el equipo al abrir el bootloader, tú que ya lo abriste no taste algo de eso o algún otro problema,?? Agradecería tu consejo
Hi, was to much since I don't modify a Samsung device so I need help please.
Want to convert to multi csc to have clean rom(no carrier apps and logos on boot) and then root with twrp.
With the s9 I remember only download firmware desire and flash with Odin, but with note 10 it's the same?
Do you recommend first unlock bootloader and then convert?
Look in the roms, recovery and kernels section, Dr Ketan posted all you need for the exynos note10+ there, y pues que tengas suerte mi buen! Nomas haz todo con cuidado al pie de la letra, preparate bien, bien cargado el cel, cable original, usa de preferencia una laptop bien cargada en vez de una de una de escritorio, por si se va la luz o algo así
Thanks, I read that already but i need to know if it's possible to install multi csc rom without modify anything and then install root and twrp
Hello, i have Red Magic 6S Pro Battlefield Edition 18/512G from China, is there Global rom to convert it from china rom?
┤Mod Edit├┤Adding automated English translation├
Hi, On youtube there is a video of a Red Magic 6 Pro where they install the Global Rom. In theory it should be the same for 6s Pro (Unless there is some drastic change in the 6s Pro Rom or in the security section). In the video it puts the links of the Global Rom; searching the site there is also Global Rom for 6s Pro. It would be a matter of trying.
Click to expand...
Click to collapse
Spoiler: Original Post
Hi, En youtube hay un video de un Red Magic 6 Pro donde instalan la Rom Global. En teoría tendría que ser lo mismo para 6s Pro (A menos que haya algún cambio drástico en la Rom del 6s Pro o en el apartado de seguridad). En el video pone los links de la Rom Global; buscando en el sitio existe también Rom Global para 6s Pro. Seria cuestión de probar.
cesarkb8 said:
Hi, En youtube hay un video de un Red Magic 6 Pro donde instalan la Rom Global. En teoría tendría que ser lo mismo para 6s Pro (A menos que haya algún cambio drástico en la Rom del 6s Pro o en el apartado de seguridad). En el video pone los links de la Rom Global; buscando en el sitio existe también Rom Global para 6s Pro. Seria cuestión de probar.
Click to expand...
Click to collapse
I already try from system update,local update and same result
one youtuber guy is a scam i wil try fastboot comand my red magic 6s pro is rooted i created orginal boot.img and root img now create backup paratition with persist.bin wil try upload the files
look at this
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