Related
Hola.
Les comento mi problema en detalle.
*Ayer flashie como normalmente lo hacia desde el TWRP, la ultima actualización de CM11.0 de Novafusion (Maclaw). Cuando lo prendí, vi que no funcionaba las aplicaciones de google (Play store, agenda, no sincronizaba con la cuenta de google, etc)
* Entonces, no se me ocurrió mejor idea que volver a un backup que tenia desde mayo, de CM11.0.
Antes de que termine de flashear esta ultima, se pone la pantalla en negro y en letras rojas aparece "RST_STAT 0x000000000"
Seguia prendiendo normalmente, solo que antes del boot logo, se ponia una pantalla por 5 segundos que era blanca con lineas horizontales negras.
*Bueno, despues de esto lo que hice fue flashear con una version anterior de maclaw de hace unos dias (CM11 tambien), pero lo que me ocurre es que me aparece como si tengo señal (pero si bajo la barra de estado me aparece como que no tengo señal y dice solo llamadas de emergencia el icono de la señal). Lo irónico es que si tengo 3G, pero no puedo realizar ni recibir llamadas, ni enviar ni recibir mensajes. Cuando quiero hacer una llamada me aparece "LA RED MOVIL NO ESTA DISPONIBLE"
*Restaure la carpeta EFS, pero sigue sin funcionar..
La verdad es que estoy desesperado, no se que hacer con el celular. Anda todo menos, la función principal de un celular, (llamadas y mensajes.)
Espero que alguien me pueda ayudar por favor.
Desde ya, muchas gracias.
Adrian.
PD: Tengo movistar y soy de argentina. Y el chip en otro celular anda. No es problema del chip ni de la oepradora,
TRADUCIDO CON GOOGLE
Hello .
I commented my problem in detail.
* Yesterday as you normally flashie to TWRP since the last update of Novafusion CM11.0 ( Maclaw ) . When I turned , I saw that did not work google apps (Play store , calendar, not synchronized to google account , etc )
* So, it never occurred to me better idea to go back to a backup I had from May to CM11.0 .
Before the end of this last flash , the screen turns black and red lettering is " RST_STAT 0x000000000 "
She kept turning on normally , just before the boot logo , a screen for 5 seconds that was white with black horizontal lines it was coming down .
* Well, after that I did was flash an earlier version of maclaw a few days ago ( CM11 too) , but what strikes me is that I appear as if I have signal ( but under the status bar appears to me as I have no signal and says emergency calls only the signal icon ) . The irony is that if I have 3G, but I can not make or receive calls or send or receive messages . When I want to make a call appear to me " THE MOBILE NETWORK NOT AVAILABLE "
* Restore the EFS folder but still not working ..
The truth is that I am desperate not to do with the phone. Anda anything but , the main function of a cell phone ( calls and messages. )
I hope someone can help me please .
From already , thank you very much .
Adrian .
PD : I 'm from Argentina and Movistar . And the chip goes in another cell . No problem chip or Attendant
If you have an I8190 go to this thread. If you have L or N variant, search in the same thread for pit file for L or N, I think someone posted for L & N too. Before doing something (bad, brick, whatever), read the thread very carefully. Good luck.
P.S. for N here, for L here.
thanks for your answer.
But the link of the file for I8190L doesnt work :/
you know where I can get that file?
------------
Edit:
I finally found the file.
I flash ir, but the same thing keeps happening. I have 3g, but i cant do any calls o send message.
Any help, please ?
may be that the cell is in negative band after flashing ?
call center movistar and they told me it was negative band for another company . What I have to do ?
because before flashing, the cellphone have signal, and i had 3g, i could make calls, and messages
Don't know mate! Try flashing a stock rom instead or try other basebands here.
No puedo recibir llamadas ni mensajes. Solo me anda el 3G.
Me di cuenta que después de flashear, no tengo los archivos .nv_data.bak y .nv_data.bak.md5
Y no tengo un backup de estos.
Y si borro la carpeta EFS, no aparecen devuelta…
Alguna solución por favor ?
————————
I can not receive calls or messages. Just go my 3G.
I realized that after flashing , I dont have the files .nv_data.bak and .nv_data.bak.md5 in my phone
And I dont have a backup of these .
And if I delete the EFS folder, do not appear these files back..
Any solution please?
Hi, I have a big problem, I deleted the /persint folder, and according to the web thats the reason why my wifi cant be turn on :crying: v, I press the turn on bottom and 0.5 later it turns off. I need some help, I've never had that problem before, and if someone has the folder please upload it and tell me how to restore it again.
Sorry for my english.
Thanks
Hola, tengo un gran problema, borre sin querer la carpeta /persint , de acuerdo a lo que he leido en internet esa es la razon por la cual mi wifi no enciende :crying: :crying: , le doy encender y se apaga inmediatamente, necesito mucha ayuda ya que nunca tuve un problema como ese. SI alguien sabe como hacerlo por favor suba la carpeta y me dice como restaurarla.
Muchas
QHSUSB_DLOAD(Now "Qualcomm HS-USB QDLoader 9008") - Motorola Iron Rock [XT626] !
I dont know if this is on the correct place, maybe not, if its not in correct, im sorry, im newbie around here/ No se si esto está en el lugar correcto, tal vez no, si no lo está, me disculpo, soy nuevo por acá.
Good morning everyone...
A couple of days ago I was asked to check an XT626 to see what it has, the only information they gave me is that the phone worked correctly except for an exaggerated slowness and constant reboots until, in one of these, it stopped working and When was turned on, it only showed the message "fastboot mode" in the upper part of the screen, with the rest of the screen completely black. When i take it, I wanted to see that error by myself, but didn't get any proof of life from the phone, when connected it to my PC in the hope that it would at least charge, I saw that it was detected as "QHSUSB_DLOAD", this sounded bad for me and start searching, then I discovered that it is possibly a HardBrick, the curious thing is that the phone was not exposed to any kind of "tinkering", in fact, with luck it was used to communicate between the owner And his partner.
Now, after spending an entire night searching about this problem, i get the drivers to make it get detected as "Qualcomm HS-USB QDLoader 9008(COMxx)", also i get stock firmware with .HEX and .MBN files, and QPST.
Now ... Is it correct to say that this problem is due to a Hardbrick? Is there a way to solve it without having to spend money in technical service? What could be the causes of this problem in a phone that was practically on factory status?
Thanks in advance.
Buenas a todos...
Hace un par de días me pidieron revisar un XT626 para "ver que tiene", la única información que me dieron es que el terminal funcionaba correctamente a excepción de una lentitud exagerada y constantes reinicios hasta que, en uno de estos, dejo de funcionar y al encenderlo solo mostraba en la parte superior de la pantalla el mensaje "fastboot mode" con el resto de la pantalla completamente en negro. Cuando me lo dieron, quise ver de primera mano dicho mensaje, pero no conseguí que el terminal diera ninguna señal de vida, al conectarlo a mi PC con la esperanza de que al menos cargue, me di cuenta que lo detectaba estando apagado pero bajo el nombre de "QHSUSB_DLOAD", esto me sonaba mal y buscando descubrí que posiblemente se trata de un brickeo, lo curioso es que dicho terminal no fue expuesto a ningún tipo de "manoseo", de hecho, con suerte era utilizado para comunicarse entre el dueño y su pareja.
Ahora bien... Es correcto decir que dicho problema se debe a un brickeo? Hay actualmente forma de solucionarlo sin tener que invertir dinero en servicio técnico? Cuales podrían ser las causas de este problema en un terminal que se encontraba prácticamente en su estado de fabrica?
Desde ya muchas gracias!
~Alexel
AlexelPk said:
I dont know if this is on the correct place, maybe not, if its not in correct, im sorry, im newbie around here/ No se si esto está en el lugar correcto, tal vez no, si no lo está, me disculpo, soy nuevo por acá.
Good morning everyone...
A couple of days ago I was asked to check an XT626 to see what it has, the only information they gave me is that the phone worked correctly except for an exaggerated slowness and constant reboots until, in one of these, it stopped working and When was turned on, it only showed the message "fastboot mode" in the upper part of the screen, with the rest of the screen completely black. When i take it, I wanted to see that error by myself, but didn't get any proof of life from the phone, when connected it to my PC in the hope that it would at least charge, I saw that it was detected as "QHSUSB_DLOAD", this sounded bad for me and start searching, then I discovered that it is possibly a HardBrick, the curious thing is that the phone was not exposed to any kind of "tinkering", in fact, with luck it was used to communicate between the owner And his partner.
Now, after spending an entire night searching about this problem, i get the drivers to make it get detected as "Qualcomm HS-USB QDLoader 9008(COMxx)", also i get stock firmware with .HEX and .MBN files, and QPST.
Now ... Is it correct to say that this problem is due to a Hardbrick? Is there a way to solve it without having to spend money in technical service? What could be the causes of this problem in a phone that was practically on factory status?
Thanks in advance.
Buenas a todos...
Hace un par de días me pidieron revisar un XT626 para "ver que tiene", la única información que me dieron es que el terminal funcionaba correctamente a excepción de una lentitud exagerada y constantes reinicios hasta que, en uno de estos, dejo de funcionar y al encenderlo solo mostraba en la parte superior de la pantalla el mensaje "fastboot mode" con el resto de la pantalla completamente en negro. Cuando me lo dieron, quise ver de primera mano dicho mensaje, pero no conseguí que el terminal diera ninguna señal de vida, al conectarlo a mi PC con la esperanza de que al menos cargue, me di cuenta que lo detectaba estando apagado pero bajo el nombre de "QHSUSB_DLOAD", esto me sonaba mal y buscando descubrí que posiblemente se trata de un brickeo, lo curioso es que dicho terminal no fue expuesto a ningún tipo de "manoseo", de hecho, con suerte era utilizado para comunicarse entre el dueño y su pareja.
Ahora bien... Es correcto decir que dicho problema se debe a un brickeo? Hay actualmente forma de solucionarlo sin tener que invertir dinero en servicio técnico? Cuales podrían ser las causas de este problema en un terminal que se encontraba prácticamente en su estado de fabrica?
Desde ya muchas gracias!
~Alexel
Click to expand...
Click to collapse
There can be many causes for the device to have these kinds of issues. It could be that the software or hardware got corrupted due to some kind of degradation, possibly faulty battery, being dropped, getting wet, overheating, etc..
If you've been reading this thread then you have the correct method to restore the device, now you just need to make sure that you have the correct compatible files for your model number to be flashed at the various flashing steps in these instructions. Flashing the wrong bootloader or any other partitions can be disastrous so make absolutely certain that what you flash at any time is compatible with your model number. You may have to adapt these instructions for your specific model, post in that thread or read all the way through it to see the various other tricks involved if it doesn't work the first time, you might find enough information to understand exactly which files you need and where to get them.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Bien, ya he flasheado el pit junto con los otros 4 archivos por medio de odin, pero el note 5 se niega a encender la pantalla......compre el cel hace unos días y esta intacto, sin marcas, golpes, etc, lo que me da lugar a pensar que la pantalla no ha recibido golpe, maltrato, uso intensivo o algo parecido......todas las luces encienden, teclas, led, sonido, etc....pero la pantalla permanece en negro. Como mencione ya lo he flasheado, use un programa para ponerlo automaticamente en modo download. Después de flashearlo el telefono hace el debido reinicio y se escuchan los sonidos caracteristicos de la pantalla de samsung, de la pantalla de configuracion de idioma, etc...pero la pantalla continua a oscuras y obviamente asi las cosas se dificultan. la pc lo reconoce sin problemas.
Cualquier ayuda extra será bien recibida, gracias.
Well, I have already flashed the pit along with the other 4 files through odin, but note 5 refuses to turn on the screen ...... I bought the cel a few days ago and it is intact, without marks, bumps, etc. , which leads me to think that the screen has not received a blow, abuse, intensive use or something similar ...... all the lights come on, keys, led, sound, etc ... but the screen remains on black. As I mentioned I have already flashed it, use a program to automatically put it into download mode. After flashing it the phone makes the proper restart and the characteristic sounds of the samsung screen, the language setting screen, etc ... are heard, but the screen continues in the dark and obviously things get difficult. The PC recognizes it without problems.
Any additional help will be welcome, thanks.
P.S: I am using a translator
nadie....nobody?
falomore said:
Bien, ya he flasheado el pit junto con los otros 4 archivos por medio de odin, pero el note 5 se niega a encender la pantalla......compre el cel hace unos días y esta intacto, sin marcas, golpes, etc, lo que me da lugar a pensar que la pantalla no ha recibido golpe, maltrato, uso intensivo o algo parecido......todas las luces encienden, teclas, led, sonido, etc....pero la pantalla permanece en negro. Como mencione ya lo he flasheado, use un programa para ponerlo automaticamente en modo download. Después de flashearlo el telefono hace el debido reinicio y se escuchan los sonidos caracteristicos de la pantalla de samsung, de la pantalla de configuracion de idioma, etc...pero la pantalla continua a oscuras y obviamente asi las cosas se dificultan. la pc lo reconoce sin problemas.
Cualquier ayuda extra será bien recibida, gracias.
Well, I have already flashed the pit along with the other 4 files through odin, but note 5 refuses to turn on the screen ...... I bought the cel a few days ago and it is intact, without marks, bumps, etc. , which leads me to think that the screen has not received a blow, abuse, intensive use or something similar ...... all the lights come on, keys, led, sound, etc ... but the screen remains on black. As I mentioned I have already flashed it, use a program to automatically put it into download mode. After flashing it the phone makes the proper restart and the characteristic sounds of the samsung screen, the language setting screen, etc ... are heard, but the screen continues in the dark and obviously things get difficult. The PC recognizes it without problems.
Any additional help will be welcome, thanks.
P.S: I am using a translator
Click to expand...
Click to collapse
hello recently I have acquired a galaxy a71, I have been using it for a week and I have come to notice that the screen usually presents a slight dimming in the brightness from time to time not at all times but if from time to time, deactivate the adaptive brightness and clear the cache and data from the light sensor of the camera but the "problem" persists, my phone has android 10 with one ui 2.5, will this version be the one that is causing this? I have not received any other updates yet, thank you very much for your time.
Hello fellow A71 owner.
First of all, if this issue results to be an OneUI 2.5 thing might be wasted effort to debug much as you could just wait for the A11 OneUI 3.5 Update and check again if the issue is still there (update is around the corner).
In the meanwhile (or after update) I suggest you troubleshoot it this way:
1) Turn off Adaptive Brightness and Night Light
2) Change your display Color Profile to Neutral (might be some dynamic post-processing going on based on content with the other profile)
3) Use a dark room and a lamp of sorts so you can give the light sensor very low and very high input values.
To test try to shine the light on the top part of the display (where the sensor is) in such a way that you don't shine too much light on the entirety of the screen, this way you'll be able to see if there are subtle changes with the screen's backlight.
Always use easy to reproduce content on the screen like a text paragraph or an image, never a video.
ban.codrut said:
Hola, compañero propietario de A71.
En primer lugar, si este problema resulta ser un OneUI 2.5, podría ser un esfuerzo en vano de depurar, ya que podría esperar la actualización A11 OneUI 3.5 y verificar nuevamente si el problema persiste (la actualización está a la vuelta de la esquina).
Mientras tanto (o después de la actualización) le sugiero que lo solucione de esta manera:
1) Apague el brillo adaptable y la luz nocturna
2) Cambie el perfil de color de la pantalla a Neutro (puede haber un posprocesamiento dinámico basado en el contenido del otro perfil)
3) Utilice una habitación oscura y una especie de lámpara para que pueda dar al sensor de luz valores de entrada muy bajos y muy altos.
Para probar, intente hacer brillar la luz en la parte superior de la pantalla (donde está el sensor) de tal manera que no brille demasiada luz en la totalidad de la pantalla, de esta manera podrá ver si hay cambios sutiles con la luz de fondo de la pantalla.
Utilice siempre contenido fácil de reproducir en la pantalla, como un párrafo de texto o una imagen, nunca un video.
Click to expand...
Click to collapse
thanks so mucho bro i try this.