Related
Hello everyone
I know there are already some roms that come pre-rooted and deodexed, but since my phone model is different (p708g) they are not compatible, so im now trying to do it myself.
I have recently managed to root the V20A (p708g) version by copying the necessary files from the rom made by Homero (all credits to him)
"[ROM KDZ] V20A_00 Jelly Bean L7 | ROOT | CWM | Unlock Booloader | by Homero". and following one tutorial here in XDA I could apply the unlock bootloader and flash CWM. I also enabled Init.d support using an app i found also in XDA. so the next step for me is to deodex the rom, so i can customize it more and apply other scripts such as Supercharger V6.
My intention is to be able to create a custom rom that include all that; root, unlock bootloader, CWM, init.d support, and deodexed. and share it with the other P708g (mexico) users.
So again, i need to know how can i Deodex the rom. I have read many posts and most of them use a tool called "Xultimate", but it havent worked for me, so im searching for some other way to deodexit. Any help is wellcome, im not asking for a step by step instruction (but is also wellcome), I just want to gather as much information as i can about it
Hope you guys can help me.
Thanks!!
Muy bien te felicito ojalá y logres tu cometido ya que para el p708g no han sacado nada saludos
i'm trying to make a carrier-crap-free stock for 708g, but i have some error while making the kdz, can you help me please?
h4x0r007 said:
i'm trying to make a carrier-crap-free stock for 708g, but i have some error while making the kdz, can you help me please?
Click to expand...
Click to collapse
I have no experience making a KDZ, what i do is basically extract the system.img.ext4, then mount it on linux, add/remove/modify files, then replace the system.img.ext4 while flashing the original KDZ
with this method, i was able to modify my stock rom(V20A-jellybean) to include: root+CWM+init.d+deodexed, and trying to add some more tweaks (transparent notificatins bar, themes, etc)
i will upload a cwm backup from my rom in a couple of days, so you can flash it to your device. So if you're interested just wait for it
P.D
maybe you can share with me what do you know about making a KDZ and we can work together with this rom :good:
I think I speak through all mexicans (who own an lg l7) by saying thank you for this lol but how is it going with the deodexing? any progress? i found this tutorial to deodex http://goo.gl/SqgbV hope it helps you!
algebraik said:
I think I speak through all mexicans (who own an lg l7) by saying thank you for this lol but how is it going with the deodexing? any progress? i found this tutorial to deodex http://goo.gl/SqgbV hope it helps you!
Click to expand...
Click to collapse
Im glad to say, i made it!
i managed to deodexit using the android kitchen, so far so well, everything works good. the main reason i wanted to deodexit was to be able to use the supercharger v6 script, and it worked, now im trying to take what i did and make a KDZ rom, but im having some problems.
also, as you may know, in order to make the supercharger script work, init.d suppourt is needed, as well as patching the "services.jar", i also managed to do that, but only after flashing the rom (via replacing the "system.img.ext4" during flashing the original kdz), so im trying to find a way to include that also in the KDZ file, but i haven't been lucky.
Im also trying to include some mods, sucha as transparent notificantion area, and a button to "reboot recovery" in the power menu, but im new with all this, so i think im not going to include that yet
it's been a very busy week so i haven't work on it as much as i want, but the progress is still going, just be a little bit more patience, im not giving up on this
vashminted said:
Im glad to say, i made it!
i managed to deodexit using the android kitchen, so far so well, everything works good. the main reason i wanted to deodexit was to be able to use the supercharger v6 script, and it worked, now im trying to take what i did and make a KDZ rom, but im having some problems.
also, as you may know, in order to make the supercharger script work, init.d suppourt is needed, as well as patching the "services.jar", i also managed to do that, but only after flashing the rom (via replacing the "system.img.ext4" during flashing the original kdz), so im trying to find a way to include that also in the KDZ file, but i haven't been lucky.
Im also trying to include some mods, sucha as transparent notificantion area, and a button to "reboot recovery" in the power menu, but im new with all this, so i think im not going to include that yet
it's been a very busy week so i haven't work on it as much as i want, but the progress is still going, just be a little bit more patience, im not giving up on this
Click to expand...
Click to collapse
Dude! that is awesome, looking forward to this! keep up the good work!!! DD
como te fue?
Hola amigo queria saber si lograste hacer todo el procedimiento cuento igual con un p708g de mexico y me interesaria tu rom deodex si pudieras compartirla muchas gracias de antemano saludos: Bueno:
juan domex said:
Hola amigo queria saber si lograste hacer todo el procedimiento cuento igual con un p708g de mexico y me interesaria tu rom deodex si pudieras compartirla muchas gracias de antemano saludos: Bueno:
Click to expand...
Click to collapse
Hi.
I did finish that ROM, but almost at the same time CM10 began to be compatible with P708 model, so I never published the ROM.
honestly it was nothing special compared to cm10. And now we have CM10.2 and slimbean with support for p708 (well, almost)
I don't know if I still have all the files I used to make the deodexed rom. if you really prefer to use a stock rom I could take a look and see if i can make it again, but I suggest you to try a newer rom, CM10.2 by cr3pt, is a good choice
Hola
Sí, termine esa rom, pero casi al mismo tiempo CM10 empezó a ser compatible con el modelo P708, asi que nunca publique la rom.
Honestamente no era nada especial comparada a CM10, y ahora tenemos CM10.2 y Slimbean con soporte para el P708 (bueno, casi)
No se si aun tengo todos los archivos que use para hacer la rom deodexada. si realmente prefieres usar la rom de fabrica, podria ver si puedo velver a hacerla, pero te sugiero probar una rom mas nueva, CM10.2 de cr3pt, es una buena opcion.
gracias por responder
vashminted said:
Hi.
I did finish that ROM, but almost at the same time CM10 began to be compatible with P708 model, so I never published the ROM.
honestly it was nothing special compared to cm10. And now we have CM10.2 and slimbean with support for p708 (well, almost)
I don't know if I still have all the files I used to make the deodexed rom. if you really prefer to use a stock rom I could take a look and see if i can make it again, but I suggest you to try a newer rom, CM10.2 by cr3pt, is a good choice
Hola
Sí, termine esa rom, pero casi al mismo tiempo CM10 empezó a ser compatible con el modelo P708, asi que nunca publique la rom.
Honestamente no era nada especial comparada a CM10, y ahora tenemos CM10.2 y Slimbean con soporte para el P708 (bueno, casi)
No se si aun tengo todos los archivos que use para hacer la rom deodexada. si realmente prefieres usar la rom de fabrica, podria ver si puedo velver a hacerla, pero te sugiero probar una rom mas nueva, CM10.2 de cr3pt, es una buena opcion.
Click to expand...
Click to collapse
HOLA MI AMIGO GRACIAS POR RESPODER! quisiera saber que tal anda la rom cm10.2 ya que la tengo al igual el kernel pero no la eh probado ya que me marco un error al instalarla pero me dijeron que se soluciona borrando una linea de updater script mas aun no lo eh hecho ahorita ando en cm10,1 s4 pero me gustaria saber que beneficio tiene la rom cm10.2 ya que en la que ando se drena muy rapido la bateria espero tu respuesta
juan domex said:
HOLA MI AMIGO GRACIAS POR RESPODER! quisiera saber que tal anda la rom cm10.2 ya que la tengo al igual el kernel pero no la eh probado ya que me marco un error al instalarla pero me dijeron que se soluciona borrando una linea de updater script mas aun no lo eh hecho ahorita ando en cm10,1 s4 pero me gustaria saber que beneficio tiene la rom cm10.2 ya que en la que ando se drena muy rapido la bateria espero tu respuesta
Click to expand...
Click to collapse
Try to post in english only, as is one of the forum rules, if you don't know enough english to write a post you should use private messages, otherwisse moderators could delete your posts.
The main advantage on CM.10.2 by cr3pt, is that NFC is disabled at kernel level, that means that the battery is not drained like in other ROMS I have more than 15 hours of battery life with normal usage.
the main disadvantage is that the camera is working with 6 mp only.
Trata de postear solo en ingles, ya que es una de las reglas del foro, si no sabes suficiente ingles para escribir un post deberias usar los mensajes privados. de otro modo los moderadores podrian borrar tus posts sin previo aviso.
la mayor ventaja de la CM10.2 de cr3pt, es que el NFC esta desactivado a nivel de kernel, lo que significa que la bateria no es drenada como en otras roms. a mi me da mas de 15 horas de bateria con un uso normal.
la mayor desventaja es que la camara funciona solo a 6 mp.
im sorry
vashminted said:
Try to post in english only, as is one of the forum rules, if you don't know enough english to write a post you should use private messages, otherwisse moderators could delete your posts.
The main advantage on CM.10.2 by cr3pt, is that NFC is disabled at kernel level, that means that the battery is not drained like in other ROMS I have more than 15 hours of battery life with normal usage.
the main disadvantage is that the camera is working with 6 mp only.
Trata de postear solo en ingles, ya que es una de las reglas del foro, si no sabes suficiente ingles para escribir un post deberias usar los mensajes privados. de otro modo los moderadores podrian borrar tus posts sin previo aviso.
la mayor ventaja de la CM10.2 de cr3pt, es que el NFC esta desactivado a nivel de kernel, lo que significa que la bateria no es drenada como en otras roms. a mi me da mas de 15 horas de bateria con un uso normal.
la mayor desventaja es que la camara funciona solo a 6 mp.
Click to expand...
Click to collapse
I'm so sorry but my English is not good even so somehow I will try to respect their rules to not bother thank you very much for your information and attention that I do appreciate your prompt response is right now I'm testing the rom hope it's as good as you I said greetings and thanks
can anyone upload a deodexed rom for lg l7 p708g??
ive been looking for a deodexed rom for my lg l7 p708g but i havent found anything whatssoever of the sorth...can anybody please help me or upload one?
There are many roms for p708g already you can search on the forum
•[EN]
Hi, I have a Galaxy S5 MINI (SM-G800H) and I'm asking for help here because no one could help me in the forum of this mobile.
The problem I have is this: an official ROM upgrade to 5.1.1, the phone worked fine until you install BAREBONE CLEAN and it includes audio mod. after a time he began to throw error "DPS + stood still." consistent message that left not use the phone.
Then from the recovery I began to erase everything that had no name "audio" "DPS" etc. and my phone went dead sound.
after that players did not work, call, youtube, nothing to reproduce video, even the boot screen.
Try installing the official ROM, PIT files, but nothing happened.
use the phone so a month, and yesterday did bootloop phone 10 or 15 times, and then I start showing the headset icon and everything worked normally, until you reboot again and returned to the same.
Really I need help is my last resort to ask questions, but you see me here.
when a ROM installed, it replaces all files that can be viewed from the recovery? if you do not like I can reinstall files in the folder
"System"
"Sys" ..... etc?
sorry for my English.
•[ES]
Hola, poseo un Galaxy S5 MINI (SM-G800H) y estoy solicitando ayuda aquí porque nadie pudo ayudarme en el foro de este móvil.
El problema que tengo es el siguiente: actualice a una ROM oficial 5.1.1, el telefono funcionaba bien hasta que instale BAREBONE CLEAN y mod audio que éste incluye. luego de una tiempo comenzó a tirar error "DPS+ se detuvo". mensaje constante que no dejaba utilizar el teléfono.
Entonces desde la recovery comencé a borrar todo lo que tenia nombre "audio" "DPS" etc. y mi telefono se quedo sin sonido.
después de esto no funcionaba reproductores, llamadas, youtube, nada que reprodujera video, ni siquiera la pantalla de boot.
Trate instalando la ROM oficial, archivos PIT, pero nada sucedió.
utilice el teléfono así un mes, y ayer el teléfono hizo bootloop entre 10 o 15 veces, y entonces arranco mostrando el icono de auriculares y todo funcionaba con normalidad, hasta que se reinicio nuevamente y volvio a lo mismo.
Necesito ayuda de verdad, es mi último recurso hacer preguntas, pero ya me ven aquí.
cuando se instala una rom, reemplaza todos los archivos que se pueden ver desde el recovery? si no lo hace como puedo volver a instalar archivos de la carpeta
"system"
"sys" ..... etc?
disculpas por mi inglés.
Two Things: Have you tried putting an Earphone to see if the output sound is working?
And have you tried getting it to an manufacture maintenance to replace the loudspeaker or the sound circuit?
maybe these have burned when you flashed.
•[ES] Hola, el sonido no esta saliendo por auriculares. Y antes de llevar a un servicio técnico quisiera quitar las dudas de que fuera software.
Una pregunta, un problema de hardware puede hacer que las aplicaciones dejen de funcionar? Los reproductores, llamadas, etc?
•[EN] Hello, the sound is not coming out headphones. And before taking a service would remove the doubt that outside software.
A question, a hardware problem can cause applications to stop working? Players, calls, etc?
Yes, if you have an hardware problem, you can't listen to call neither musics.
that is, hardware problem = "Soundboard". which is the case here.
DBlackFireD said:
Yes, if you have an hardware problem, you can't listen to call neither musics.
that is, hardware problem = "Soundboard". which is the case here.
Click to expand...
Click to collapse
•[ES] Perfecto. Muchas gracias por las respuesta. Iré a un servicio técnico a probar el hardware :good:
•[EN] Perfect. Thank you very much for the answer. I will go to a technical service to test the hardware :good:
rodrycapo07 said:
•[ES] Perfecto. Muchas gracias por las respuesta. Iré a un servicio técnico a probar el hardware :good:
•[EN] Perfect. Thank you very much for the answer. I will go to a technical service to test the hardware :good:
Click to expand...
Click to collapse
Buenas tardes, tengo problemas con el sonido del hablante no le oigo y el ami si, alguna solución MM 6.0.1
Enviado desde N910F Tapatalk Movil
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
joscopa said:
Buenas tardes, tengo problemas con el sonido del hablante no le oigo y el ami si, alguna solución MM 6.0.1 GRACIAS
Enviado desde N910F Tapatalk Movil
Click to expand...
Click to collapse
Enviado desde N910F Tapatalk Movil
Buenas noches, lo primero es disculparme por no hacer la pregunta en el idioma natural de la web. Dicho esto, vengo a exponer mi caso con el leeco x727, y es el siguiente: El teléfono un día se me apago y no funcionaba nada, he realizado la instalación qfil, recovery y rom, he instalado 9 o 10 rom, así como diferentes recovery para este modelo y muchas de ellas las instalo correctamente, pero una vez que reinicio el sistema, siempre se queda en la pantalla principal en la que pone LeEco Share the Eco World, no terminando nunca de arrancar la rom.
Llevo un mes prácticamente leyendo foros e intentandolo revivir pero me es imposible, por si me pudieran ayudar. gracias
S_I_f2001 said:
Buenas noches, lo primero es disculparme por no hacer la pregunta en el idioma natural de la web. Dicho esto, vengo a exponer mi caso con el leeco x727, y es el siguiente: El teléfono un día se me apago y no funcionaba nada, he realizado la instalación qfil, recovery y rom, he instalado 9 o 10 rom, así como diferentes recovery para este modelo y muchas de ellas las instalo correctamente, pero una vez que reinicio el sistema, siempre se queda en la pantalla principal en la que pone LeEco Share the Eco World, no terminando nunca de arrancar la rom.
Llevo un mes prácticamente leyendo foros e intentandolo revivir pero me es imposible, por si me pudieran ayudar. gracias
Click to expand...
Click to collapse
You must speak English here or no one will answer you.
Use Google translate like I just did.
Here is your answer: https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
tsongming said:
You must speak English here or no one will answer you.
Use Google translate like I just did.
Here is your answer: https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Click to expand...
Click to collapse
Good afternoon, I have reviewed what you have told me and reinstalled everything.
I still have the same problem, I install everything very well without any problems but then the Rom does not start. Could it be that the hardware is broken ??? because it can not be that the same thing has happened to anyone else than me, that after installing up to 9 different ROMs, none will work, leaving the entire installation process correct.
S_I_f2001 said:
Good afternoon, I have reviewed what you have told me and reinstalled everything.
I still have the same problem, I install everything very well without any problems but then the Rom does not start. Could it be that the hardware is broken ??? because it can not be that the same thing has happened to anyone else than me, that after installing up to 9 different ROMs, none will work, leaving the entire installation process correct.
Click to expand...
Click to collapse
So you completely all steps with error. But the phone will not start? Take another look at the steps ( that is expected) It takes a while to start. Can you now see the phone storage from your PC?
Is it possible to send files to the phone via fastboot?
If so, you may be able to flash a recovery, and root your phone using aDB bridge or restore stock EUI.
Keep in Mind that Un-bricking your phone will be frustrating and will require alot of trial and error.
I have been there and since I had some extra time I decided spent a little more than an hour writing you a whole new guide with working links. Just remember that you can definitely unbrick your phone.
Directly from Leeco Website : When it was still accessible
Music pro3 save bricks line brush
1. Download the QPST tool & driver.
2. Make sure your device has the Power to support flashing.
3. Run Flash and QFIL
Downloads : ( These downloads take a few minutes but works and comes directly from Leeco)
FlashOne1.9 : https://pan.baidu.com/s/1nvttJtf
9008 Driver: https://pan.baidu.com/s/1nvdKHeT Download and install Qualcomm driver. While installing driver avoid using cable for successful installation.
QPST.2.7.460.zip https://easy-firmware.com/home/browse/file/id/102719/QPST.2.7.460.zip/
Flash File: zl1_qfil (1).zip
After installation, connect Phone to PC using USB cable.
* While connecting to PC, phone should be switched off and press volume up & down as boot key.
* If it makes Qualcomm port, then driver has been successfully installed.
If the right Qualcomm driver is installed on your computer
You should see the phone as a Qualcomm HS-USB QLoader 9008 or incorrectly listed as Qualcomm HS-USB Diagnostics 900E both within settings and device manager. )IF your device is showing Qualcomm HS-USB diagnostics 900E(COM4) , then you are not in the correct Qualcomm mode.
When device shows Qualcomm HS USB 9008 then use flash 2.0 to flash your ROM
Fastboot: Press and hold the power button and the volume down (minus) to enter fastboot mode.
Recovery: Press and hold the power button and the volume up (plus) to enter Recovery mode.
QFIL upgrade mode: Press and hold the power key and the volume up and down key ( at same time!) to enter “Qualcomm FIL “Mode!* Again: Qualcomm mode, You need to press all 3 buttons V+,V-, + power buttons simultaneously after connecting to usb!
* Run the Minimal ADB and Fastboot From the Start Menu
* Use the following command to check if your Device is Detected in ADB:
PHP:
adb devices -l
For additional things to try see : https://developer.android.com/studio/command-line/adb.html
* In Flash 2.0 select your file then click Refresh you should see the port COM + and then select File Select QFIL upgrade package, the package release address
Review installation steps here before starting : https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
Note all of the links are dead. But the images are relevant and you have the files from the links above.
I am not fully clear on exactly where your are having the issue. Send me the log files from flash 2.0
You do not need to use 9 different roms. Just uses the files included with the link. These steps WILL NOT work on any other phone other than the X720 and X727. If you have something besides a X727*or X720 then theses steps are not going to help you.
Make sure that you installed the Qualcomm 9008 drivers on your PC
ADB has to be authorized on Windows 10 for this to work, You can update ADB and Android drivers on your computer by using
Apparently, this http://en.miui.com/thread-266598-1-1.html
It is completely possible that you have a hardware issue. Such as a damaged USB card, usually caused by a faulty usb cable ( the usb cable that come with the phone have been known to have quality issues.) If you purchased the phone recently, I would suggest that you contact the vendor that you purchased the phone from and request a warranty exchange.
Excuse me I had to explain badly. I have no problems installing any of the files.
The problem is when after everything is installed, the Rom does not start.
But I repeat everything is installed well.
Sent from my LEX727 using xda premium
I will take it you are using twrp.
You did swipe allow modifications in twrp?
You are clean installs?
mchlbenner said:
Sent from my LEX727 using xda premium
I will take it you are using twrp.
You did swipe allow modifications in twrp?
You are clean installs?
Click to expand...
Click to collapse
I have used both Twrp, the tool all in One and Minimal ADB and Fastboot.
Also use a rom of groosophor that is an executable where you come all inclusive.
S_I_f2001 said:
I have used both Twrp, the tool all in One and Minimal ADB and Fastboot.
Also use a rom of groosophor that is an executable where you come all inclusive.
Click to expand...
Click to collapse
Okay, can you boot into Recovery? In recovery you need to wipe everything, install your firmware, and install Magisk, reboot to recovery. Check your storage, follow the instructions to resolve the storage issue if an issue exists.
Next, go to the Lineage 15.1 page and download all of the files recommended, Flash Lineage 15.1 , mind the Gapps, and Magisk, Also install the correct bootloader for your device.
While we have alot of great Roms. Lineage 15.1 is probably the most stable of all Oreo Roms. I recommend that you either install Lineage or stock EUI until this issue is resolved. If you can boot to recovery, the rest should be easy.
---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------
S_I_f2001 said:
Excuse me I had to explain badly. I have no problems installing any of the files.
The problem is when after everything is installed, the Rom does not start.
But I repeat everything is installed well.
Click to expand...
Click to collapse
Also, if you are responding to me. Click Reply under my comment or I will not get the notification.
S_I_f2001 said:
Buenas noches, lo primero es disculparme por no hacer la pregunta en el idioma natural de la web. Dicho esto, vengo a exponer mi caso con el leeco x727, y es el siguiente: El teléfono un día se me apago y no funcionaba nada, he realizado la instalación qfil, recovery y rom, he instalado 9 o 10 rom, así como diferentes recovery para este modelo y muchas de ellas las instalo correctamente, pero una vez que reinicio el sistema, siempre se queda en la pantalla principal en la que pone LeEco Share the Eco World, no terminando nunca de arrancar la rom.
Llevo un mes prácticamente leyendo foros e intentandolo revivir pero me es imposible, por si me pudieran ayudar. gracias
Click to expand...
Click to collapse
¿De dónde eres? Soy de México, Mándame un mensaje privado y te puedo ayudar, hablo inglés, francés y español, podemos platicar en cualquiera de los 3 para que no batalles con traducciones o problemas de lenguaje.
tsongming thank you. great guide I needed that windows driver for adb and couldn't find it so you helped 2 for the price of one:good:
Hello, does anyone know the procedure to root the Junsun V1pro 4G + 64G CarPlay Android 9.0 DSP device?
or if it is possible to install TWRP Recovery ?.
apparently it is a too new version and I can hardly find any information or firmware. Does anyone know this device and could help me?.
I leave you some photos of it.
https://drive.google.com/file/d/1SdvGPIuCNmLJEyVjwzyuUv2pTqx8E1_f/view?usp=sharing
https://drive.google.com/file/d/1mVPpY3BYOfMVjQ_0f83_UJcj9q2310LD/view?usp=sharing
https://drive.google.com/file/d/1M3LlaijsBsd_voG-wn4UBLgL5TB7detp/view?usp=sharing
https://drive.google.com/file/d/1KQ3wo1rlVjE-1vkBsXyI2BT6UmwXH0MY/view?usp=sharing
https://drive.google.com/file/d/1Col6WMtNp74DElVbf8zUU2q6e-x_nLPx/view?usp=sharing
Greetings to all and thanks.
Hola @alberto 755,
Tengo la misma radio, pero la verdad que estoy completamente perdido sobre como "rooterarla". Estoy usando la radio con un Golf 7, pero tengo muchos problemas con el canbus... algunos accesorios del coche no funcionan. Me podrías ayudar sobre su uso?. Muchas gracias!!!
-----------------------------------
Hi @alberto 755!!!,
I have the same radio too, but I'm complete lost about how to root it. I'm using this radio with a VW Golf 7, and I have a lot of issues with the canbus... some of the car original accessories doesn't works. Could you help me about how to use this unit?. Thanks a lot!
102649259 said:
Extract the contents of the file to a clean flash drive (FAT32).
Click to expand...
Click to collapse
Thank you for your reply @102649259!!!,
Sorry about the question, obviously I'm not an expert about android radios. If I load this ROM version, can this fix my problem with the canbus of my VW Golf 7?. I tried 2 canbus, one of RAISE and the other of HIWORLD. The best results I had it with the HIWORLD, but is not complete compatible with my car.
It is possible to load Android 10 to this radio?
Thank you!
Hola. gracias a todos y siento la tardanza en contestar . @monopilot veras yo estaba igual que tu he ido probando algunas cosas y solventando los problemas sobre la marcha...
empezando por el principio:
en mi caso solo me interesaba el root pero al buscar información sobre el dispositivo no aparece demasiada, y la que aparece tanto en este foro de Xda-deverlopers como en el foro ruso 4pda.ru para mi es muy confusa ya que al parecer hay múltiples dispositivos que parecen compartir similitudes.
Por este motivo me producía mucho temor el flashear algún update modificado con root y que al no ser del todo compatible consiguiese un boatloop. (O tal vez una inscripción roja permanente en pantalla como indican en algunos post por instalar por error un update compatible pero de otro fabricante).
Primero opte por lo mas fácil pero tras intentar comunicarme con el vendedor este no esta dispuesto a facilitarme el firmware de mi dispositivo por lo que no podría recuperarlo de una forma fácil si cometía algún error.
bien llegados a este punto estuve realizando múltiples pruebas, y descubrí que tal vez fue por cuestión de suerte pero el dispositivo si permite el reinicio en modo Fastboot desde el terminal emulator a pesar de no disponer de derechos root, para ello es tan simple como instalar la aplicación y teclear "reboot bootloader" tras pulsar enter el dispositivo reiniciar en modo Fastboot y lo comprobamos por las letras situadas en la esquina superior izquierda.
https://drive.google.com/file/d/1vIE9TQHu5-XF7Ljc0VyITqQUubk7IWsw/view?usp=sharing
Una vez descubierto esto estuve buscando por internet algún método de procedimiento para poder extraer el boot.bin a través de ADB shell utilizando el comando Cat (si se que es necesario root para ello pero aun así quería probar.. y efectivamente continúe con mucha suerte ya que conseguí extraer el boot.img desde mi propio dispositivo.)
Finalmente tras ello copie a la memoria interna del dispositivo el boot,img extraído anteriormente e instale la ultima versión de magisk manager.apk para parchear dicho archivo y flashear desde el pc usando Fastboot con el comando “Fastboot flash boot boot.img” tras ello cruce los dedos en el reinicio y todo salió bien tenia mi Stock ROM con root y magisk funcionando perfectamente.
¡¡Nota!!para poder conectar el dispositivo al pc por medio de Fastboot es necesario cambiar el tipo de conexión USB host para ello vamos a ajustes/sistema/opciones de desarrollo (código 3368) y en la esquina superior derecha pulsamos sobre los puntos y aparece el “submenú” Usb Mode en idioma chino cambiamos al de debajo y ya podemos conectar el USB del dispositivo con el USB del pc usando un cable USB tipo A-A con sus 2 puntas macho.
https://drive.google.com/file/d/1XCEJtNNWEuMSCWTc1aC2T2xzitc3N2go/view?usp=sharing
(nota.!!muy importante al terminar volver a dejar el usb host en su primera opción sino no funcionaran los usb conectados ya que quedarían configurados para conexión a pc).
En cuanto a tu pregunta sobre el canbus yo también he tenido problemas.(en mi caso el equipo lo tengo montado en un Ford Focus) y lo único que he podido realizar es ir probando diferentes configuraciones a partir del menú “ajustes de Fabrica/Selección de modelo” (el código de acceso es 3368) hay están las diferentes configuraciones Can bus para indicarle al dispositivo cual tienes instalado en mi caso he ido probando hasta dar con el más adecuado ya que no he encontrado mucha más información así que siento no poder ayudarte más.
@102649259 gracias por tu ayuda y el archivo facilitado, aunque encontré el método expuesto.
a pesar de ser mucho más complejo quizás a alguien le pueda ayudar esta información.
Os dejo unas web de ejmplos con información sobre la extracción del boot.img a través de ADB (por la red hay mucha información al respecto).
https://www.cnblogs.com/shangdawei/p/4514128.html
http://gadget-tweak.blogspot.com/p/how-to-pullextract-boot-recovery-system.html
por ultimo dejo un .rar tanto con las herramientas ADB/Fastboot junto con sus drivers el archivo Boot.img original y parcheado con magisk de mi dispositivo por si a alguien pudiese ayudarle en algún momento solo tendría que flashear a través de fastboot.
https://drive.google.com/file/d/12TN65jI9p7EpEs9sBo06PO3x6BD8z735/view?usp=sharing
un saludo y muchas gracias a todos por la ayuda.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi. Thank you all and I am sorry for the delay in answering. @monopiLoT you will see I was just like you I have been trying some things and solving problems on the go ...
starting at the beginning:
in my case I was only interested in the root but when looking for information about the device it does not appear too much, and the one that appears both in this Xda-deverlopers forum and in the Russian forum 4pda.ru for me is very confusing since apparently there are multiple devices that seem to share similarities.
For this reason, I was very afraid to flash a modified update with root and that being not completely compatible,would get a bootloop. (Or perhaps a permanent red inscription on the screen as indicated in some post for mistakenly installing a compatible update but from another manufacturer).
First opt for the easiest but after trying to communicate with the seller, he is not willing to provide me with the firmware of my device so I could not recover it easily if I made a mistake.
Well arrived at this point I was conducting multiple tests, and I discovered that maybe it was a matter of luck but the device does allow the restart in Fastboot mode since terminal emulator despite not having root rights, for this it is as simple as installing the application and type "reboot bootloader" after pressing enter the device will restart in Fastboot mode and we check it by the letters located in the upper left corner
https://drive.google.com/file/d/1vIE9TQHu5-XF7Ljc0VyITqQUubk7IWsw/view?usp=sharing
Once this was discovered I was searching the internet for some method of procedure to be able to extract the boot.bin through the ADB shell using the Cat command (yes I know that root is necessary for it but I still wanted to try .. and effectively I continued with great luck since I managed to extract the boot.img from my own device.)
Finally, after that, copy the boot, img previously extracted, to the internal memory of the device and install the latest version of magisk manager.apk to patch this file and flash from the pc using Fastboot with the command "Fastboot flash boot boot.img" after it I crossed my fingers on the restart and everything went well I had my Stock ROM with root and magisk working perfectly.
Note !! In order to connect the device to the PC through Fastboot it is necessary to change the type of USB host connection. To do this, go to settings / system / development options (code 3368) and in the upper right corner click on the and the Usb Mode “submenu” appears in Chinese language. We change to the one below and we can now connect the USB of the device with the USB of the PC using a USB type AA cable with its 2 male ends.
https://drive.google.com/file/d/1XCEJtNNWEuMSCWTc1aC2T2xzitc3N2go/view?usp=sharing
(note. !! very important when you finish leaving the host usb in its first option if the connected usb will not work since they would be configured for connection to a pc).
As for your question about the canbus, I have also had problems (in my case I have it mounted on a Ford Focus) and the only thing I have been able to do is try different configurations from the menu “Factory settings / Selection model ”(the access code is 3368) there are the different Can bus configurations to indicate to the device which one you have installed in my case I have been trying to find the most suitable since I have not found much more information so I am sorry I cannot help you more.
@ 102649259 thanks for your help and the provided file, although I found the exposed method.
Despite being much more complex, perhaps someone can help with this information.
I leave you some example websites with information on the extraction of boot.img through ADB (there is a lot of information about it on the network).
https://www.cnblogs.com/shangdawei/p/4514128.html
http://gadget-tweak.blogspot.com/p/how-to-pullextract-boot-recovery-system.html
finally I leave a .rar both with the ADB / Fastboot tools along with its drivers the original Boot.img file and patched with magisk of my device in case anyone could help you at some point I would only have to flash through fastboot.
https://drive.google.com/file/d/12TN65jI9p7EpEs9sBo06PO3x6BD8z735/view?usp=sharing
greetings and thank you all very much for the help.
Hi guys,
I am also the owner of Junsun V1 pro 4G + 64G.
Thanks for sharing your experience with this device,
Do you also have a bluetooth problem?
I have one that I can only pair one device at a time. In addition, it happens that after pairing the phone, all contacts are lost.
Hi @grzech666.
If I also ran into the same problem when trying to link the OBD to use torque. in my case when entering Factory Setting (code 3368) of the last options in the list, OBD was in the off state, I changed it to on and now it allows me the connection, try it.
As for the deletion of contacts, this has not happened to me.
Anyway, I am still trying to get the vendor to provide me with the firmware of my device. If I can get it, I will upload it in this post in case it can help someone.
Greetings.
Thanks for replying,
About software, I already get it from my supplier but I was afraid to use it. If you are interested, I can put it on my Google drive or samwere else.
grzech666 said:
Thanks for replying,
About software, I already get it from my supplier but I was afraid to use it. If you are interested, I can put it on my Google drive or samwere else.
Click to expand...
Click to collapse
yes please!
yes please.
if you can provide a download link along with a photos of your system to ensure compatibility before installing.
you it I would be very grateful.
Note!!in the MCU section The model number G23 or G32 is very important since installing a different version can produce brick very difficult to recover.
my device information:
https://drive.google.com/file/d/1SdvGPIuCNmLJEyVjwzyuUv2pTqx8E1_f/view
https://drive.google.com/file/d/1kuthqiR1Opz8HdnmGnQ3ZOAERMpx39a6/view?usp=sharing
https://drive.google.com/file/d/1mVPpY3BYOfMVjQ_0f83_UJcj9q2310LD/view
Screens of my unit you can find here:
https://forum.xda-developers.com/showpost.php?p=82670707&postcount=16
let me know if you want more info
I also uploaded mentioned firmware:
https://drive.google.com/file/d/1Zja9xorBD1NLnDd7kBC3HX6XrwRJNmcf/view?usp=sharing
grzech666 said:
Screens of my unit you can find here:
https://forum.xda-developers.com/showpost.php?p=82670707&postcount=16
let me know if you want more info
I also uploaded mentioned firmware:
https://drive.google.com/file/d/1Zja9xorBD1NLnDd7kBC3HX6XrwRJNmcf/view?usp=sharing
Click to expand...
Click to collapse
Thank you very much for the firmware, the devices are identical.
Although my device is updated to date 05-03-2020, makes me think if that could be the reason for your problems with OBD contacts and connection?
continue with the problem ?.
Have you tried checking for updates through the device?.
Regards, and thank you very much.
Does anybody know if it is possible to flash an original joying firmware on this unit?
alberto 755 said:
Hola. gracias a todos y siento la tardanza en contestar . @monopilot veras yo estaba igual que tu he ido probando algunas cosas y solventando los problemas sobre la marcha...
empezando por el principio:
en mi caso solo me interesaba el root pero al buscar información sobre el dispositivo no aparece demasiada, y la que aparece tanto en este foro de Xda-deverlopers como en el foro ruso 4pda.ru para mi es muy confusa ya que al parecer hay múltiples dispositivos que parecen compartir similitudes.
Por este motivo me producía mucho temor el flashear algún update modificado con root y que al no ser del todo compatible consiguiese un boatloop. (O tal vez una inscripción roja permanente en pantalla como indican en algunos post por instalar por error un update compatible pero de otro fabricante).
Primero opte por lo mas fácil pero tras intentar comunicarme con el vendedor este no esta dispuesto a facilitarme el firmware de mi dispositivo por lo que no podría recuperarlo de una forma fácil si cometía algún error.
bien llegados a este punto estuve realizando múltiples pruebas, y descubrí que tal vez fue por cuestión de suerte pero el dispositivo si permite el reinicio en modo Fastboot desde el terminal emulator a pesar de no disponer de derechos root, para ello es tan simple como instalar la aplicación y teclear "reboot bootloader" tras pulsar enter el dispositivo reiniciar en modo Fastboot y lo comprobamos por las letras situadas en la esquina superior izquierda.
https://drive.google.com/file/d/1vIE9TQHu5-XF7Ljc0VyITqQUubk7IWsw/view?usp=sharing
Una vez descubierto esto estuve buscando por internet algún método de procedimiento para poder extraer el boot.bin a través de ADB shell utilizando el comando Cat (si se que es necesario root para ello pero aun así quería probar.. y efectivamente continúe con mucha suerte ya que conseguí extraer el boot.img desde mi propio dispositivo.)
Finalmente tras ello copie a la memoria interna del dispositivo el boot,img extraído anteriormente e instale la ultima versión de magisk manager.apk para parchear dicho archivo y flashear desde el pc usando Fastboot con el comando “Fastboot flash boot boot.img” tras ello cruce los dedos en el reinicio y todo salió bien tenia mi Stock ROM con root y magisk funcionando perfectamente.
¡¡Nota!!para poder conectar el dispositivo al pc por medio de Fastboot es necesario cambiar el tipo de conexión USB host para ello vamos a ajustes/sistema/opciones de desarrollo (código 3368) y en la esquina superior derecha pulsamos sobre los puntos y aparece el “submenú” Usb Mode en idioma chino cambiamos al de debajo y ya podemos conectar el USB del dispositivo con el USB del pc usando un cable USB tipo A-A con sus 2 puntas macho.
https://drive.google.com/file/d/1XCEJtNNWEuMSCWTc1aC2T2xzitc3N2go/view?usp=sharing
(nota.!!muy importante al terminar volver a dejar el usb host en su primera opción sino no funcionaran los usb conectados ya que quedarían configurados para conexión a pc).
En cuanto a tu pregunta sobre el canbus yo también he tenido problemas.(en mi caso el equipo lo tengo montado en un Ford Focus) y lo único que he podido realizar es ir probando diferentes configuraciones a partir del menú “ajustes de Fabrica/Selección de modelo” (el código de acceso es 3368) hay están las diferentes configuraciones Can bus para indicarle al dispositivo cual tienes instalado en mi caso he ido probando hasta dar con el más adecuado ya que no he encontrado mucha más información así que siento no poder ayudarte más.
@102649259 gracias por tu ayuda y el archivo facilitado, aunque encontré el método expuesto.
a pesar de ser mucho más complejo quizás a alguien le pueda ayudar esta información.
Os dejo unas web de ejmplos con información sobre la extracción del boot.img a través de ADB (por la red hay mucha información al respecto).
https://www.cnblogs.com/shangdawei/p/4514128.html
http://gadget-tweak.blogspot.com/p/how-to-pullextract-boot-recovery-system.html
por ultimo dejo un .rar tanto con las herramientas ADB/Fastboot junto con sus drivers el archivo Boot.img original y parcheado con magisk de mi dispositivo por si a alguien pudiese ayudarle en algún momento solo tendría que flashear a través de fastboot.
https://drive.google.com/file/d/12TN65jI9p7EpEs9sBo06PO3x6BD8z735/view?usp=sharing
un saludo y muchas gracias a todos por la ayuda.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi. Thank you all and I am sorry for the delay in answering. @monopiLoT you will see I was just like you I have been trying some things and solving problems on the go ...
starting at the beginning:
in my case I was only interested in the root but when looking for information about the device it does not appear too much, and the one that appears both in this Xda-deverlopers forum and in the Russian forum 4pda.ru for me is very confusing since apparently there are multiple devices that seem to share similarities.
For this reason, I was very afraid to flash a modified update with root and that being not completely compatible,would get a bootloop. (Or perhaps a permanent red inscription on the screen as indicated in some post for mistakenly installing a compatible update but from another manufacturer).
First opt for the easiest but after trying to communicate with the seller, he is not willing to provide me with the firmware of my device so I could not recover it easily if I made a mistake.
Well arrived at this point I was conducting multiple tests, and I discovered that maybe it was a matter of luck but the device does allow the restart in Fastboot mode since terminal emulator despite not having root rights, for this it is as simple as installing the application and type "reboot bootloader" after pressing enter the device will restart in Fastboot mode and we check it by the letters located in the upper left corner
https://drive.google.com/file/d/1vIE9TQHu5-XF7Ljc0VyITqQUubk7IWsw/view?usp=sharing
Once this was discovered I was searching the internet for some method of procedure to be able to extract the boot.bin through the ADB shell using the Cat command (yes I know that root is necessary for it but I still wanted to try .. and effectively I continued with great luck since I managed to extract the boot.img from my own device.)
Finally, after that, copy the boot, img previously extracted, to the internal memory of the device and install the latest version of magisk manager.apk to patch this file and flash from the pc using Fastboot with the command "Fastboot flash boot boot.img" after it I crossed my fingers on the restart and everything went well I had my Stock ROM with root and magisk working perfectly.
Note !! In order to connect the device to the PC through Fastboot it is necessary to change the type of USB host connection. To do this, go to settings / system / development options (code 3368) and in the upper right corner click on the and the Usb Mode “submenu” appears in Chinese language. We change to the one below and we can now connect the USB of the device with the USB of the PC using a USB type AA cable with its 2 male ends.
https://drive.google.com/file/d/1XCEJtNNWEuMSCWTc1aC2T2xzitc3N2go/view?usp=sharing
(note. !! very important when you finish leaving the host usb in its first option if the connected usb will not work since they would be configured for connection to a pc).
As for your question about the canbus, I have also had problems (in my case I have it mounted on a Ford Focus) and the only thing I have been able to do is try different configurations from the menu “Factory settings / Selection model ”(the access code is 3368) there are the different Can bus configurations to indicate to the device which one you have installed in my case I have been trying to find the most suitable since I have not found much more information so I am sorry I cannot help you more.
@ 102649259 thanks for your help and the provided file, although I found the exposed method.
Despite being much more complex, perhaps someone can help with this information.
I leave you some example websites with information on the extraction of boot.img through ADB (there is a lot of information about it on the network).
https://www.cnblogs.com/shangdawei/p/4514128.html
http://gadget-tweak.blogspot.com/p/how-to-pullextract-boot-recovery-system.html
finally I leave a .rar both with the ADB / Fastboot tools along with its drivers the original Boot.img file and patched with magisk of my device in case anyone could help you at some point I would only have to flash through fastboot.
https://drive.google.com/file/d/12TN65jI9p7EpEs9sBo06PO3x6BD8z735/view?usp=sharing
greetings and thank you all very much for the help.
Click to expand...
Click to collapse
Hello @alberto 755,
thank you for your write-up. Can you share how you were able to extract boot.img from your unit.
I tried through adb shell but failed without read permission.
Hello. I am glad I found some information about this unit I was following price drops on Aliexpress.
I am looking for the plastic frame version for my peugeot 206cc. Junsun seems to mount same V1 pro 4+64 for all the car versions.
Firmware and root are some of my concerns but the procedure appears to be like standard for phones using magisk method, it is a relieve to know from you that because I did it before for tablets and phones and it is pretty straight forward and easy to archieve.
About the read/write permissions problem may be with sudo plus chmod could do the trick before extracting the boot img, I don't know but there are a lot of magisk procedure information over there and it sholud not be a headache at all.
The question I have for you users from this radio isn't about software but sound and FM. I am from Spain and FM Radio is really a concern to me, for the work over all.
- About the Radio: I want to know how well it performs scan, RDS, AF mode and reception.
- I am going to replace the whole speaker system, it sounds bad for the music I listen to and the old Clarion RD3 DSP doesn't perform many options to get clean lows. Death, black, doom metal is really dificult to adjust with standard settings. What do you think if I get some Alpine good stuff speakers with sepparated ways for the 17 cm front and 10 cm rear speakers? Could I connect an active sobwoofer like those flat from Pioneer or Kenwood? I mean, the RCA out could archieve the sobwoofer out?
I was about to buy a Pioneer SPH-10BT instead an Android Unit because in the past i have troubles with other AHU and this Pioneer sure it makes its job really good. I just want to know if I am going to do a good purchase in the terms of audio quality. In the end, the sound is what most matters.
Thank you for your attention, kind regards
Root can be attained by Magisk patched boot.img but it will mute apps that utilize Google TTS, examples Google Maps, Assistant and Waze. I read somewhere Play store will have problem as well (I didn't test that).
If you are really into sound quality and radio reception, you should pass on this android unit. I have used 2 android units before this one and they sound much better and autoscan picked up all stations.
Autoscan with this unit picks up zero station, I have to manually input the station frequency and it sounds soft and mono. Switching from stereo and mono makes no difference.
I've stopped using the built-in radio and rely on tune-in app permanently, even that doesn't sound as good as before.
You should read how owners have tried to change the built-in amp and radio chip to get better sound, https://4pda.ru/forum/index.php?showtopic=938749&st=5800
Contrary to the Junsun Aliexpress ads, the RCA cable come without mic input. The seller tells me the unit don't support external mic input, the internal mic has improved and unit "updated". So far, voice command and phone calls are okay with normal road noise.
I run focal speakers with DLS Ultimate A3 in the front and an active subwoofer through the RCA subwoofer output in the trunk.
Regarding internal microphone I wasn't happy with them. Fortunately my units came with cable for external mic. I bought additional mic and installed it, now voice is much better.
gpmg762 said:
Root can be attained by Magisk patched boot.img but it will mute apps that utilize Google TTS, examples Google Maps, Assistant and Waze. I read somewhere Play store will have problem as well (I didn't test that).
If you are really into sound quality and radio reception, you should pass on this android unit. I have used 2 android units before this one and they sound much better and autoscan picked up all stations.
Autoscan with this unit picks up zero station, I have to manually input the station frequency and it sounds soft and mono. Switching from stereo and mono makes no difference.
I've stopped using the built-in radio and rely on tune-in app permanently, even that doesn't sound as good as before.
You should read how owners have tried to change the built-in amp and radio chip to get better sound, https://4pda.ru/forum/index.php?showtopic=938749&st=5800
Contrary to the Junsun Aliexpress ads, the RCA cable come without mic input. The seller tells me the unit don't support external mic input, the internal mic has improved and unit "updated". So far, voice command and phone calls are okay with normal road noise.
I run focal speakers with DLS Ultimate A3 in the front and an active subwoofer through the RCA subwoofer output in the trunk.
Click to expand...
Click to collapse
Thank you about the sound opinion, is my most important concern, also FM reception is very important to me, as I said because the work. So I am going to boy a good Alpine or Pioneer stereo sigle DIN and just using Android auto or Pioneer sync app it would do the job. The only thing I could gain with AHU is a bigger display (altough worse than my phone resolution of course and I think they are not good with sun brightness reflections no matter how much chinese cheap IPS has). I keep thinking on SPH-10BT or similar.
Hi! I have a Junsun V1 PRO, 4GB/64GB WI-FI+4G.
It's a fake Android 9.0 it comes with API 27.
I ask to the AliExpress seller and he send to me a .bin file to solve it ¿????
It's a bin file called "Solve MCU error.bin" and the size is only 131kb, so I'm not sure if it will solve anything jajajja
So I don't know if try to flash it or not. If you want it, ask for it privately but I'm not responsible if you break your unit.
I have problems to autostart apps. I want to autostart "Radardroid" and "Blockada" but I think that it only autostart the last used app.
I solved the problem of loosing contacts disabling the Google synch.
Do you know how to change/move/replace the icons on the first screen?
And any way to change the "voice search" button (selected via wheel buttons settings) to "Google Assistant"?
Any app recommendations to use FM? I don't like the one that comes with the head unit.
Thank you!!
Enviado desde mi MI 9 mediante Tapatalk
View attachment 5062851View attachment 5062849
chemixzgz said:
Thank you about the sound opinion, is my most important concern, also FM reception is very important to me, as I said because the work. So I am going to boy a good Alpine or Pioneer stereo sigle DIN and just using Android auto or Pioneer sync app it would do the job. The only thing I could gain with AHU is a bigger display (altough worse than my phone resolution of course and I think they are not good with sun brightness reflections no matter how much chinese cheap IPS has). I keep thinking on SPH-10BT or similar.
Click to expand...
Click to collapse
I have since found Poweramp as an alternative for default radio and audio player replacement while researching USB audio and DSD. I recommend digital radio if mobile data usage is not restricted.
I am getting a matte tempered glass screen protector to cut down the sun's reflection.
The SPH-10BT will sound better, it's a proper head-unit after all.
Buenos días, una semana antes instalé la última evo x rom vía twrp fajita (última versión) y hace dos días mi pantalla dejó de funcionar, en la parte de atrás se puede ver otra imagen de la pantalla del bloque. Intento flashear stock rom pero no funcionó ¿alguien puede ayudarme?
Translation:
Good morning, a week before I installed the latest evo x rom via twrp fajita (latest version) and two days ago my screen stopped working, on the back you can see another image of the block screen. I am trying to flash stock rom but it didn't work can anyone help me?
Click to expand...
Click to collapse
So, the actual hardware is fine, but the screen doesn't work when booting Evolution X?
Or the screen has been damaged after the installation, and you want to flash Stock ROM?
no funciona con la rom de stock ni con la de evo x, estoy perdido y no se que hacer
Mohamedkam000 said:
Entonces, ¿el hardware real está bien, pero la pantalla no funciona al arrancar Evolution X?
¿O la pantalla se ha dañado después de la instalación y desea actualizar Stock ROM?
Click to expand...
Click to collapse
carlosrg002 said:
no funciona con la rom de stock ni con la de evo x, estoy perdido y no se que hacer
Click to expand...
Click to collapse
y la pantalla se ha dañado despues de la instalacion
Does the screen show anything at all? The boot logo? Can you access fastboot/recovery mode?
Try putting some pressure on the top left part of your phone's back. And check if anything shows up.
One Plus 6T comes with Optic AMOLED display, it works fine with all ROMs, but if you somehow replaced it with lower-class LCD display, then it may not display a thing at all.
This used to happen on Galaxy Note3, from what I remember.
If it is true that this is a hardware issue, you'll have to replace your screen with another one.
Mohamedkam000 said:
¿La pantalla muestra algo en absoluto? ¿El logo de la bota? ¿Puede acceder al modo fastboot / recovery?
Intente ejercer algo de presión en la parte superior izquierda de la parte posterior de su teléfono. Y compruebe si aparece algo.
One Plus 6T viene con pantalla Optic AMOLED, funciona bien con todas las ROM, pero si de alguna manera lo reemplazó con una pantalla LCD de clase inferior, es posible que no muestre nada en absoluto.
Esto solía suceder en Galaxy Note3, por lo que recuerdo.
Si es cierto que se trata de un problema de hardware, tendrás que reemplazar tu pantalla por otra.
Click to expand...
Click to collapse
puedo ver la pantalla, si conecto un mouse via usb-c puedo andar en el teléfono. Puedo acceder al modo recovery y al fastboot. Si presiono la parte superior no ocurre nada en la pantalla
carlosrg002 said:
puedo ver la pantalla, si conecto un mouse via usb-c puedo andar en el teléfono. Puedo acceder al modo recovery y al fastboot. Si presiono la parte superior no ocurre nada en la pantalla
Click to expand...
Click to collapse
It seems like an issue that happens with One Plus devices, there's some videos on YouTube regards the issue.
Check:
Video 1.
Video 2.
XDA Thread.
Mohamedkam000 said:
Parece un problema que ocurre con los dispositivos One Plus, hay algunos videos en YouTube sobre el problema.
Cheque:
Video 1 .
Video 2 .
Hilo XDA .
Click to expand...
Click to collapse
tx but its not black screen, its touch screen not working, i can see the phone i can use it if i connect a mouse
carlosrg002 said:
tx but its not black screen, its touch screen not working, i can see the phone i can use it if i connect a mouse
Click to expand...
Click to collapse
Sorry, I thought you meant black screen, translation didn't explain much.
Apologies, not a lot of results showed up regards unresponsive screen, and those which did, was fixed by either rebooting or cleaning proximity sensor.
Mohamedkam000 said:
Lo siento, pensé que te referías a pantalla negra, la traducción no explica mucho.
Disculpas, no se mostraron muchos resultados con respecto a la pantalla que no responde, y los que sí lo hicieron, se solucionaron reiniciando o limpiando el sensor de proximidad.
Click to expand...
Click to collapse
la solucion es un flash limpio o clean el snsor, de que forma?
Dear all,
Kindly post your comments in English and your mother language, you could use translate.google.com to perform the task. Hence, other users could understand the discussion and gain knowledge or contribute to the topic. Thanks.