Sorry I translated it by goole
Hello,
After installing the new ROM I was with several problems: the connections to Internet, and mainly the synchronization by means of Good BT. then after work in it a while I have solved it following these steps (I do not know if at this point you have solved it because been I have disconnected of the forums and still I have left something before my return). But just in case, never it is of more sharing it with you who as much you help me.
1. If we have installed XP SP2 we must follow the passages of this Link: http://www.todopocketpc.com/foro/showthread.php?t=39274
2. After having the BT correctly installed in our PC we followed the passages of this other Link: http://www.todopocketpc.com/analisis_ver_articulo.asp?id_articulo=89
3. The problem with this ROM was that it was not possible to be acceded to the synchronization by the ActiveSync from the PDA, him pulsabamos (at least in my case) to synchronize by means of BT and towards the small noise of connection but nothing of anything. This I have solved it, once done the previous thing, installing the patch of the BTTools that I lowered of post nº3 (by my good friend harry1 that this time without knowing it has helped me), I I have installed version 1012.
4. I match the PDA with the PC, and although it gives an error message, we continued and they leave images to us with different services (if conoceís the Bthtools you know to that I talk about), we pressed in Activesync, and later it leaves the pantallita to us again with the 4 squares to match and we give again Activesync.
5. Finally in the Activesync of the PDA it leaves to us now in tools, "I counted via BT with xxxxEl name of equipoxxx).
6. We pressed and listoooo works!!!!!!!!!!!
7. By the way, this version has not installed me any plug in the screen today, unlike other versions. After this my GPS BT it continued working correctly, I do not have the Parrot nor anything that is resembled to him so I do not know if this affects to the configuration of the same one.
I hope that you it has been of utility.
Hola,
Después de instalar la nueva ROM me encontré con varios problemas: las conexiones a Internet, y sobre todo la sincronización mediante BT. Bueno pues después de trastear un rato lo he solucionado siguiendo estos pasos (no sé si a estas alturas lo habéis solucionado pues he estado desconectado de los foros y aún me queda algo antes de mi regreso). Pero por si acaso, nunca está de más compartirlo con vosotros que tanto me ayudáis.
1. Si tenemos instalado XP SP2 tenemos que seguir los pasos de este link: http://www.todopocketpc.com/foro/showthread.php?t=39274
2. Después de tener el BT correctamente instalado en nuestro pc seguimos los pasos de este otro link: http://www.todopocketpc.com/analisis_ver_articulo.asp?id_articulo=89
3. El problema con esta ROM era que no se podía acceder a la sincronización por el ActiveSync desde la PDA, le pulsabamos (al menos en mi caso) a sincronizar mediante BT y hacia el ruidito de conexión pero nada de nada. Esto lo he solucionado, una vez hecho lo anterior, instalando el parche de las BTTools que bajé del post nº3 (por mi buen amigo harry1 que me ha ayudado esta vez sin saberlo ), yo he instalado la versión 1012.
4. Emparejo la PDA con el PC, y a pesar de que da un mensaje de error, continuamos y nos salen unas imágenes con diferentes servicios (si conoceís las Bthtools sabréis a que me refiero), pulsamos en Activesync, y después nos sale la pantallita otra vez con las 4 casillas para emparejar y le damos otra vez a Activesync.
5. Por último en el Activesync de la PDA nos sale ahora en tools, “Conté vía BT with xxxxEl nombre del equipoxxx).
6. Pulsamos y listoooo funciona!!!!!!!!!!!
7. Por cierto, esta versión no me ha instalado ningún plug en la pantalla hoy, a diferencia de otras versiones.
Después de esto mi GPS BT continuaba funcionando correctamente, no tengo el Parrot ni nada que se le asemeje así que no sé si esto afecta a la configuración del mismo.
Espero que os haya sido de utilidad.
Hi,
My "new" GPS Royaltek RBT-1000 bluetooth is not working with my XDA. They are paired, in a first moment with Pocket Bluetooth tools installed and recognized via Bluetooth, but no COM port is assigned in the last step of get pairing process...
When I run TomTom 5 the GPS is not working because no COM port is assigned (I think)... Can anyone help me to make run properly this GPS with XDA II?
GPS Royaltek RBT-1000
XDA II ROM 1.72.03ESN
(I sincronized properly with a PC vía ActiveSync via Bluetooth without any problems...)
Español / spanish:
Tengo un GPS Royaltek RBT-1000 Bluetooth que no consigo hacer funcionar con la XDA II a través de la conexión Bluetooth. En un primer momento se emparejan los dispositivos sin problemas (tengo instaladas las Bluetooth Tools), pero a la hora de asignar éstas un puerto COM al dispositivo GPS no me da ninguna opción.
Cuando ejecuto el TomTom 5 lógicamente no reconoce el GPS porque no tiene un puerto COM asignado, y no se localizan. ¿Alguien me puede ayudar a sincronizar estos dispositivos?
(He sincronizado sin problemas con mi PC de sobremesa vía Bluetooth sin problemas, pero con el GPS, imposible)
Gracias.
Bluetooth GPS....
Instala las famosas bttools, parealo asignando un com en el último diálogo (COM7, creo) y configura el tomtom para usar el puerto serie que ahora si tendras
Tanto con la primera versión de ROM como con la segunda me he encontrado el siguiente problema al sincronizar con mi servidor de Exchange el cual está en la red interna, y tiene el mismo nombre que externamente (mail.xxxx.com), cuando pasaba de sincronizar por UBS correctamente y desconectaba de forma que se conectaba GPRS, activesync se quedaba en el paso de sincronizando cambios.
Tras analizar el problema he llegado a la conclusión de que Activesync no refrescaba la IP de mi servidor de exchange e intentaba seguir conectando por la interna.
Solución, he configurado la conexión de activesync 4.1 de forma que conecta a la red de trabajo y le he dicho a activesync de WM5 que la red de trabajo conecta a internet (yo he configurado proxy por que disponemos de IsaServer 2004), de éste modo cuando pasa de USB a GPRS al ser diferentes tarjetas, para WM5 son diferentes IP de Host y funciona perfectamente todo.
Espero que esto ayude a la comunidad (si existe algún Guru que quiera aportar más datos o corregirme, adelante, todo lo que sea aportar claridad al asunto. será muy bien recibido).
Adjunto un pdf que explica el proceso.
Un Saludo a todos.
:lol:
As much with the first version of ROM like with second I have found the following problem when synchronizing with my Exchange which is in the internal network, and externally has the same name that internaly(mail.xxxx.com), when synchronize by UBS rigth and disconnected so that it was connected GPRS, ActiveSync it remained synchronizing changes.
After analyzing the problem I have reached the conclusion from that ActiveSync it did not refresh the IP of my exchange and tried to continue connecting by the internal IP.
Solution, I have formed the connection of ActiveSync 4.1 so that it connects to the work network and I have said ActiveSync of WM5 that the work network it connects to Internet (I I have formed proxy so that we have IsaServer 2004), in this way when it goes from USB to GPRS to the being different cards, for WM5 they are different IP from Host and works everything perfectly.
I hope that this helps the community (if some Guru that it wants to contribute more data or to correct to me, ahead, everything what is to contribute clarity to the subject. it will be very well received).
Associate a pdf that explains the process.
Regards.
(Sorry for my english )
hi everybody i buyed 1 week ago the htc mini hd i tryed to install tomtom 7 and....bluetooth stopped to work and also the radio.
when i start the mini appear a error message = the file bttce or something is not an application pocket pc...damn...
who can help me?an hard reset can solve that situation?it s new and i haven't so much important data so if i lost is ot a big problem...
please help me...
ps sorry for my english but i m italian i hope you can understand.
Excuse my English,
I read a solution, which I put in Spanish for no mistakes:
"TOMTOM coloca un nuevo dlls BT en la carpeta de Windows que hay que eliminar o renombrar:
\ Windows \ BtSdkCE30.dll
\ Windows \ BtCoreIf.dll
Puedes renombrarlos o eliminarlos y, a continuación reiniciar la pda y todo volverá a la normalidad.
Para localizar los ficheros sólo hay que iniciar el Explorador de archivos, seleccionar la opción 'menú', seleccionar 'Mostrar todos los archivos'.
Yo simplemente renombré estos dos archivos, reinicié la HTC y todo correcto"
Greetings
Hi personally I use ttn7.917.9186_vga_black_NOBT.cab and the bluetooth is working.
With the qvga version tomtom was crashing in landscape. But with this one it is fine.
i use 7.917x.xxx and work fine.
but i cant connect with tomtom home2
.
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.