Related
Hi,
from at least 3monts i have some problems with my HTC P3600.
I have a kit bluetooth into my car and an Access Point (WPA2) in my house.
When i do a soft-reset i have always to set-up again the settings for the connections.
Blutetoot lost the parling whit my Bluetooth Car Kit
WiFi ask me the sharedkey
I have tried all available Radio roms and I still have the same problem...
Have someone this problem?
Bye,
Stefano
Ciao Ragazzi,
Da 3 mesi a questa parte ho dei problemi con il mio HTC P3600.
Ho un KIT Bluetooth in macchina ed a casa un Access Point WiFi (con criptaggio WPA2).
Ogni singola volta che faccio un soft-reset perdo tutti i settaggi e devo reimpostarli nuovamente:
Bluetooth: devo rifare il parling
WiFi: mi richiede la sharedkey
Ho provato con tutte le ROM Radio disponibili, ma non è cambiato nulla....
Qualcuno di voi ha lo stesso mio problema e può aiutarmi??
Grazie in anticipo,
Stefano.
Google Traslate:
Hello everyone,
I state that I am a New User Android is the first time you run the root on a HTC device in this case a Legend (Brand FastWeb).
I would like to make my No Brand Legend and then upgrade to 2.2 over the air Froyo
I have a problem with the controls ADB
... I installed the Android SDK by exe
(now I have also tried to simply extract the archive into C
... through the command prompt in Windows 7 by the tools folder ...
But any command "ADB" I post I always returns the following error:
"adb" is not recognized as internal or external command, an executable program or batch file
I'm using the latest version dell'Android SDK (android-sdk_r08-windows) ...
I installed HTC Sync downloaded from the site, I did the sync is working well ...
to create the GoldCard:
I inserted a micro SD card
I clicked on "Unmount SD card"and then "Format"
USB debugging enabled on your phone
Connect your phone to USB cable
I put in charge only mode
I open the command prompt in Windows 7
later in the Tools folder of the SDK
I type "adb devices"
Press enter and it should return the list of phones connected, however the error is that mentioned above:
"adb" is not recognized as internal or external command, an executable program or batch file
I rebooted the PC several times and the Legend, during the various tests I also closed HTC Sync (I read that might give errors) I started SDK Manager and I also created a Virtual Device and I started ... but nothing changes!
PS. Excuse my ignorance on the subject, but "adb" is not a command "dos" of windows as it could ever work? SDK is ke add this command to DOS?
Thanks in advance to all those who want to participate!
Good Evening Mauro
Italiano:
Ciao a tutti,
premetto che sono un Nuovo Utente Android ed è la prima volta che eseguo il Root su un apparecchio HTC in questo caso un Legend (Brand FastWeb).
Vorrei rendere il mio Legend No Brand per poi eseguire l'aggiornamento a Froyo 2.2 tramite OTA
Avrei un problema con i comandi ADB
... ho installato l'Android SDK tramite l'exe
(ora ho anche provato ad estrarre semplicemente l'archivio zip in C: )
...tramite il prompt dei comandi di Windows 7 entro nella cartella tools ...
però qualsiasi comando "ADB" che inserisco mi restituisce sempre il seguente errore:
"adb" non è riconosciuto come comando interno o esterno, un programma eseguibile o un file batch
sto utilizzando l'ultima versione dell'Android SDK (android-sdk_r08-windows)...
ho installato HTC Sync scaricato dal sito, ho effettuato la sincronizzazione è funziona bene ...
per creare la GoldCard:
Ho inserito una scheda micro SD
ho cliccato su "smonta schede SD" e poi "Formatta"
Attivo il Debug USB sul cellulare
Collego il telefono al cavetto USB
Lo metto in modalità solo carica
Apro il prompt dei comandi di Windows 7
entro nella Cartella Tools del SDK
digito "adb device"
Premo invio e dovrebbe restituire la lista dei telefoni connessi, invece l'errore è quello sopra citato:
"adb" non è riconosciuto come comando interno o esterno, un programma eseguibile o un file batch
Ho riavviato più volte il PC ed il Legend, durante le varie prove ho anche chiuso HTC Sync (ho letto che potrebbe dare errore) ho lanciato SDK Manager ed ho anche creato un Device Virtuale e l'ho avviato ... ma non cambia nulla !!!
PS. Scusate la mia ignoranza in materia, ma se "adb" non è un comando "dos" di windows come potrebbe mai funzionare? è SDK ke aggiunge questo comando al DOS ?
Grazie anticipatamente a tutti coloro che vorranno intervenire !!!
Buona Serata Mauro
Check the tools folder for the ADB executable, if it's not there then re-download the SDK, and extract the tools directory to C:\SDK\tools
Ultimo125 said:
Google Traslate:
Hello everyone,
I state that I am a New User Android is the first time you run the root on a HTC device in this case a Legend (Brand FastWeb).
I would like to make my No Brand Legend and then upgrade to 2.2 over the air Froyo
I have a problem with the controls ADB
... I installed the Android SDK by exe
(now I have also tried to simply extract the archive into C
... through the command prompt in Windows 7 by the tools folder ...
But any command "ADB" I post I always returns the following error:
"adb" is not recognized as internal or external command, an executable program or batch file
I'm using the latest version dell'Android SDK (android-sdk_r08-windows) ...
I installed HTC Sync downloaded from the site, I did the sync is working well ...
to create the GoldCard:
I inserted a micro SD card
I clicked on "Unmount SD card"and then "Format"
USB debugging enabled on your phone
Connect your phone to USB cable
I put in charge only mode
I open the command prompt in Windows 7
later in the Tools folder of the SDK
I type "adb devices"
Press enter and it should return the list of phones connected, however the error is that mentioned above:
"adb" is not recognized as internal or external command, an executable program or batch file
I rebooted the PC several times and the Legend, during the various tests I also closed HTC Sync (I read that might give errors) I started SDK Manager and I also created a Virtual Device and I started ... but nothing changes!
PS. Excuse my ignorance on the subject, but "adb" is not a command "dos" of windows as it could ever work? SDK is ke add this command to DOS?
Thanks in advance to all those who want to participate!
Good Evening Mauro
Italiano:
Ciao a tutti,
premetto che sono un Nuovo Utente Android ed è la prima volta che eseguo il Root su un apparecchio HTC in questo caso un Legend (Brand FastWeb).
Vorrei rendere il mio Legend No Brand per poi eseguire l'aggiornamento a Froyo 2.2 tramite OTA
Avrei un problema con i comandi ADB
... ho installato l'Android SDK tramite l'exe
(ora ho anche provato ad estrarre semplicemente l'archivio zip in C: )
...tramite il prompt dei comandi di Windows 7 entro nella cartella tools ...
però qualsiasi comando "ADB" che inserisco mi restituisce sempre il seguente errore:
"adb" non è riconosciuto come comando interno o esterno, un programma eseguibile o un file batch
sto utilizzando l'ultima versione dell'Android SDK (android-sdk_r08-windows)...
ho installato HTC Sync scaricato dal sito, ho effettuato la sincronizzazione è funziona bene ...
per creare la GoldCard:
Ho inserito una scheda micro SD
ho cliccato su "smonta schede SD" e poi "Formatta"
Attivo il Debug USB sul cellulare
Collego il telefono al cavetto USB
Lo metto in modalità solo carica
Apro il prompt dei comandi di Windows 7
entro nella Cartella Tools del SDK
digito "adb device"
Premo invio e dovrebbe restituire la lista dei telefoni connessi, invece l'errore è quello sopra citato:
"adb" non è riconosciuto come comando interno o esterno, un programma eseguibile o un file batch
Ho riavviato più volte il PC ed il Legend, durante le varie prove ho anche chiuso HTC Sync (ho letto che potrebbe dare errore) ho lanciato SDK Manager ed ho anche creato un Device Virtuale e l'ho avviato ... ma non cambia nulla !!!
PS. Scusate la mia ignoranza in materia, ma se "adb" non è un comando "dos" di windows come potrebbe mai funzionare? è SDK ke aggiunge questo comando al DOS ?
Grazie anticipatamente a tutti coloro che vorranno intervenire !!!
Buona Serata Mauro
Click to expand...
Click to collapse
ADB is no longer in the tools folder it is in the platform-tools folder
Hello ...
Exact Problem solved in practice by updating the SDK to run the commands needed to move to the new folder "platform-tools" instead of the usual "Tools"
Tanks
Gentilissimi utenti ed esperti del settore Modding!
Ho un problema, vi spiego, passo passo, ciò che ho eseguito al mio Huawei P8 Lite ALE-L21 della categoria c432b633, cioè SIM singola!
Ho eseguito il root del telefono con successo, pur sapendo che non è più coperto di garanzia, mi serviva poi a poter collegare il joypad della PS3 (che si è collegata alla perfezione). Ma purtroppo, per mia curiosità, volevo cercare di "nascondere" il root per Pokémon GO, mi è stata consigliata, in base alle ricerche eseguite, di dover prima installare il Magisk, e dopodiché effettuare un'impostazione (che in questo momento non me lo ricordo). Ma si tratta dell'installazione del Magisk che mi ha dato problemi.
1 - Il nuovo aggiornamento della Huawei non permette (anche se rootato) l'installazione del Magisk;
2 - In un'altra guida (cosa che dovevo pur stare attento) c'è scritto di rinominare il file di sistema /system/app/HwOUC/HwOUC.apk in HwOPT.bak ed installare una patch update_EVA-B528Patch01.zip
attraverso il TWRP
Fatto questo, Lo smartphone si è briccato, perché non sono stato attento alla compatibilità.
Adesso lo smartphone si accende la spia ad intermittenza, (ROSSO, VERDE, VERDE, ROSSO, VERDE, VERDE, ROSSO, VERDE, VERDE) Poi stop! Schermo nero.
Una cosa analoga mi è capitato ad un tablet rootato ma poi si è risolta che dopo qualche giorno si è ripreso (spero che la situazione sia risolvibile anche per questo!)
A presto.
----------------------------------------------------------------------------------------------------
Very kind users and experts in the Modding sector!
I have a problem, I will explain, step by step, what I have done to my Huawei P8 Lite ALE-L21 of the category c432b633, ie single SIM!
I rooted the phone successfully, even knowing that it is no longer covered by warranty, I then needed to be able to connect the PS3 joypad (which is connected to perfection). But unfortunately, for my curiosity, I wanted to try to "hide" the root for Pokémon GO, I was advised, based on the searches performed, to have to first install the Magisk, and then make a setting (which at this time is not me I remember). But this is the Magisk installation that gave me problems.
1 - The new Huawei update does not allow (even if rooted) the Magisk installation;
2 - In another guide (something I had to be careful with) it is written to rename the system file /system/app/HwOUC/HwOUC.apk in HwOPT.bak and install a patch update_EVA-B528Patch01.zip
through the TWRP
This done, the smartphone got brikked, because I wasn't careful about compatibility.
Now the smartphone turns on the light intermittently, (RED, GREEN, GREEN, RED, GREEN, GREEN, RED, GREEN, GREEN) Then stop! Black screen.
A similar thing happened to me with a rooted tablet but then it was resolved that after a few days it recovered (I hope the situation can be solved for this too!)
See you soon.
ho collegato il mio tel al PC, lo rileva ma visualizza un driver sconosciuto (e per giunta in cinese)
I connected my tel to the PC, it detects it but displays an unknown driver (and in Chinese as well)
I have another device (Honor 6X), but have you already tried with third-party services like FunkyHuawei/DC-Phoenix? They aren't free, but the cost to unbrick the device is irrelevant compared to other costs, plus you'll be able to unbrick the phone through fastboot mode (always if your phone get to that point without issues!). Just google "funkyhuawei unbrick" or "dc phoenix unbrick", and in both cases the first result you'll get will be the one you're looking for. Hope this helps. There are other methods to unbrick the device, like dload method, but it requires to have an accessible internal/external storage in way to copy necessary update.app files on and an accessible recovery in way to flash the files through it. Hope this helps.
This Update is for XL6107 1024x600 with A7 1.3 x 4 Head Unit
Version: XL6107_20211027
It runs much smoother than before and music will now play without annoying random audio-drop-out's.
Installation steps (if the automatic upgrade fails, you could try manual upgrade):
Auto update:
1. Extract downloaded RAR
2. Copy extracted files (update_auto.zip and update_audo.txt to the root directory of the USB device.
3. Insert the USB device into the 6P cable of the car's USB. The machine defaults to USB6P line upgrade.
4. Power on Head Unit (If not on before)
An On-Screen display will appear - notifying about system update is in progress - don't touch anything in this progress,
sit back and wait. Update will take 15 minutes do not power off in the middle, wait to complete the upgrade and then it will automatically restart.
Manual upgrade: Rename update_auto.zip and update_auto.txt to update.zip and update.txt on USB device, open the car settings-about this machine-Android upgrade.
If it won't work you could try to reformat USB device before or use other USB device for update.
789.5 MB file on MEGA
mega.nz
Factory Settings Code: 8888
Android reset code: 159357
Wireless ADB Port: 9876
WARNING about disabling launchers with ADB
Locked launcher could possibly replaced by disabling or changing 'persist.sys.xl.launcher=com.android.launcher8' option in build.prop.
For now i can't tell anything more about behavior, I don't know how XL system apps are working together.
If you would explore how it could work - be careful and be sure you can recover from unexpected behavior of device -
maybe with a script which automatically recovers default state after 3 boot attempts or something. Had no time not try if adb over USB is now available.
By analyzing framework-res.apk in Android Studio it seems to be Android 6.0
Mod edit - translated by https://www.deepl.com/translator:
thank you very much for your help as soon as I have a moment of time I will try to update
**************************
grazie mille per il tuo aiuto appena ho un momento di tempo cerco di aggiornare
Goodmorning everyone,
I hope you can help me.
I also have the same model and I have already made this update all ok until a few days ago when trying to tinker a bit on the build.prop I evidently did some damage in fact now the head unit remains blocked on the boot animation and there is no towards being able to start it.
I'm trying to figure out if there is a way to access recovery mode hoping that from there there is a factory reset / wipe data or something similar but so far nothing.
This model has no physical buttons but only the RST button.
Thank you
I asked my seller for help, maybe he could provide some informations about recovery these devices. You should also ask your seller as i know there is the great -> /dev/block/mmcblk0p22 partition on device where default CAN config is placed in canconf/canconfig.xml. How difficult it is to apply other CAN settings i dont know. In meantime you could try this procedure which is for 8 core Spreadtrum versions -> https://forum.xda-developers.com/t/how-to-enter-in-recovery-mode.3280247/post-84114389 Maybe you could enter recovery mode but i can't tell if it works or recovery has adb or shell support.
panic2k said:
I asked my seller for help, maybe he could provide some informations about recovery these devices. You should also ask your seller as i know there is the great -> /dev/block/mmcblk0p22 partition on device where default CAN config is placed in canconf/canconfig.xml. How difficult it is to apply other CAN settings i dont know. In meantime you could try this procedure which is for 8 core Spreadtrum versions -> https://forum.xda-developers.com/t/how-to-enter-in-recovery-mode.3280247/post-84114389 Maybe you could enter recovery mode but i can't tell if it works or recovery has adb or shell support.
Click to expand...
Click to collapse
thank you very much, I have been exchanging e-mails with the seller who says nothing for days and continues to give me vague answers and offers me a new unit at the cost of EUR45 !!!!
among the thousand tests I also made this one of the key1 or key2 to gnd but nothing to do ....
believe me at the moment I have no more ideas ...
Oh all that is really annoying. It was for me the same behavior until i got the update. I had opened disputes and just annoying them. My seller has read my message but i have no answer till now. Let's wait a few hours. I just can hope he send me an answer. He fooled me with some of device specs in his advertisements, he should know already that i knows. If nothing happens i can open open a dispute for your 45 bucks and send you these. Greatest would be community support from him after all issues before.
uaccio said:
Mod edit - translated by https://www.deepl.com/translator:
thank you very much for your help as soon as I have a moment of time I will try to update
**************************
grazie mille per il tuo aiuto appena ho un momento di tempo cerco di aggiornare
Click to expand...
Click to collapse
@uaccio
As courtesy, I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Italian posts.
Spoiler: Rule No. 4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
panic2k said:
This Update is for XL6107 1024x600 with A7 1.3 x 4 Head Unit
Version: XL6107_20211027
It runs much smoother than before and music will now play without annoying random audio-drop-out's.
Installation steps (if the automatic upgrade fails, you could try manual upgrade):
Auto update:
1. Extract downloaded RAR
2. Copy extracted files (update_auto.zip and update_audo.txt to the root directory of the USB device.
3. Insert the USB device into the 6P cable of the car's USB. The machine defaults to USB6P line upgrade.
4. Power on Head Unit (If not on before)
An On-Screen display will appear - notifying about system update is in progress - don't touch anything in this progress,
sit back and wait. Update will take 15 minutes do not power off in the middle, wait to complete the upgrade and then it will automatically restart.
Manual upgrade: Rename update_auto.zip and update_auto.txt to update.zip and update.txt on USB device, open the car settings-about this machine-Android upgrade.
If it won't work you could try to reformat USB device before or use other USB device for update.
789.5 MB file on MEGA
mega.nz
Factory Settings Code: 8888
Android reset code: 159357
Wireless ADB Port: 9876
WARNING about disabling launchers with ADB
Locked launcher could possibly replaced by disabling or changing 'persist.sys.xl.launcher=com.android.launcher8' option in build.prop.
For now i can't tell anything more about behavior, I don't know how XL system apps are working together.
If you would explore how it could work - be careful and be sure you can recover from unexpected behavior of device -
maybe with a script which automatically recovers default state after 3 boot attempts or something. Had no time not try if adb over USB is now available.
By analyzing framework-res.apk in Android Studio it seems to be Android 6.0
Click to expand...
Click to collapse
Hi
I cannot find persist.sys.xl.launcher=com.android.launcher8 in my build.prop, i only have "
ro.launcher.multimode=true
ro.launcher.dynamic=true
ro.launcher.desktopgrid=true
ro.launcher.notifbadge.count=true
"
This with launcher, do you know how i can change the default launcher (everytime i try to do on the head unit it just close and come back to the stock one) ? Also how to enable split screen ?
Hi was looking for some guidance on how to fix my XL6107s audio issue. I’ve had the unit for a few months and audio has worked great. The other day the audio went completely out. No radio, keyboard clicks, Bluetooth, nothin. A few drives later, the audio came back, then back off for the next drive. I checked all my fuses and even put my old radio back in to ensure the speakers worked. I have tried a factory reset and that didn’t fix the issue either. Has anyone had this issue or know how to fix?
BrownRyan said:
Hi was looking for some guidance on how to fix my XL6107s audio issue. I’ve had the unit for a few months and audio has worked great. The other day the audio went completely out. No radio, keyboard clicks, Bluetooth, nothin. A few drives later, the audio came back, then back off for the next drive. I checked all my fuses and even put my old radio back in to ensure the speakers worked. I have tried a factory reset and that didn’t fix the issue either. Has anyone had this issue or know how to fix?
Click to expand...
Click to collapse
update, i updated my device. The first time the unit booted up after the update, the audio worked flawlessly, however, the next time I started the car, the device was back to no audio. I ran the update again and the same thing happened. Audio worked for the first boot, then nothing again the second time. Any idea what this might be? Thanks
panic2k said:
Questo aggiornamento è per XL6107 1024x600 con unità principale A7 1.3 x 4
Versione: XL6107_20211027
Funziona in modo molto più fluido di prima e la musica ora verrà riprodotta senza fastidiosi cali casuali dell'audio.
Passaggi di installazione (se l'aggiornamento automatico non riesce, puoi provare l'aggiornamento manuale):
Aggiornamento automatico:
1. Estrarre il RAR scaricato
2. Copiare i file estratti (update_auto.zip e update_audo.txt nella directory principale del dispositivo USB.
3. Inserire il dispositivo USB nel cavo 6P dell'USB dell'auto. L'impostazione predefinita della macchina è l'aggiornamento della linea USB6P.
4. Accendere l'unità principale (se non accesa prima)
Apparirà un display su schermo - notifica dell'aggiornamento del sistema in corso - non toccare nulla in questo corso,
siediti e aspetta. L'aggiornamento richiederà 15 minuti non spegnere nel mezzo, attendere per completare l'aggiornamento e quindi si riavvierà automaticamente.
Aggiornamento manuale: rinomina update_auto.zip e update_auto.txt in update.zip e update.txt sul dispositivo USB, apri le impostazioni dell'auto-su questa macchina-Aggiornamento Android.
Se non funziona, puoi provare a riformattare il dispositivo USB prima o utilizzare un altro dispositivo USB per l'aggiornamento.
789.5 MB file on MEGA
mega.nz
Codice impostazioni di fabbrica: 8888
Codice di ripristino Android: 159357
Porta ADB senza fili: 9876
ATTENZIONE sulla disabilitazione dei lanciari con ADB
Il programma di avvio bloccato potrebbe eventualmente essere sostituito disabilitando o modificando l'opzione 'persist.sys.xl.launcher=com.android.launcher8' in build.prop.
Per ora non posso dire altro sul comportamento, non così come le app di sistema XL funzionino insieme.
Se desideri esplorare come potrebbe funzionare, fai attenzione e assicurati di poterti recuperare da un comportamento imprevisto del dispositivo -
magari con uno script che ripristina lo stato dopo 3 tentativi di avvio o qualcosa del genere. Non ho avuto tempo di non provare se adb su USB è ora disponibile.
Analizzando framework-res.apk in Android Studio sembra essere Android 6.0
Click to expand...
Click to collapse
Esiste una guida per disabilitare i lanciatori Bcon ADB?
hoto il produttore e sono riuscito ad ottenere il codice per abilitare la modalità sviluppatore .
panic2k said:
Questo aggiornamento è per XL6107 1024x600 con unità principale A7 1.3 x 4
Versione: XL6107_20211027
Funziona in modo molto più fluido di prima e la musica ora verrà riprodotta senza fastidiosi cali casuali dell'audio.
Passaggi di installazione (se l'aggiornamento automatico non riesce, puoi provare l'aggiornamento manuale):
Aggiornamento automatico:
1. Estrarre il RAR scaricato
2. Copiare i file estratti (update_auto.zip e update_audo.txt nella directory principale del dispositivo USB.
3. Inserire il dispositivo USB nel cavo 6P dell'USB dell'auto. L'impostazione predefinita della macchina è l'aggiornamento della linea USB6P.
4. Accendere l'unità principale (se non accesa prima)
Apparirà un display su schermo - notifica dell'aggiornamento del sistema in corso - non toccare nulla in questo corso,
siediti e aspetta. L'aggiornamento richiederà 15 minuti non spegnere nel mezzo, attendere per completare l'aggiornamento e quindi si riavvierà automaticamente.
Aggiornamento manuale: rinomina update_auto.zip e update_auto.txt in update.zip e update.txt sul dispositivo USB, apri le impostazioni dell'auto-su questa macchina-Aggiornamento Android.
Se non funziona, puoi provare a riformattare il dispositivo USB prima o utilizzare un altro dispositivo USB per l'aggiornamento.
789.5 MB file on MEGA
mega.nz
Codice impostazioni di fabbrica: 8888
Codice di ripristino Android: 159357
Porta ADB senza fili: 9876
ATTENZIONE sulla disabilitazione dei lanciari con ADB
Il programma di avvio bloccato potrebbe eventualmente essere sostituito disabilitando o modificando l'opzione 'persist.sys.xl.launcher=com.android.launcher8' in build.prop.
Per ora non posso dire altro sul comportamento, non così come le app di sistema XL funzionino insieme.
Se desideri esplorare come potrebbe funzionare, fai attenzione e assicurati di poterti recuperare da un comportamento imprevisto del dispositivo -
magari con uno script che ripristina automaticamente lo stato dopo 3 tentativi di avvio o qualcosa del genere. Non ho avuto tempo di non provare se adb su USB è ora disponibile.
Analizzando framework-res.apk in Android Studio sembra essere Android 6.0
Click to expand...
Click to collapse
Ciao a tutti mi chiedevo se esiste una guida per disabilitare il blocco dei lanciatori con ADB?
Ho contatatto il produttore e sono riuscito a ottenere il codice per abilitare la modalità di sviluppo.
superluis84 said:
Esiste una guida per disabilitare i lanciatori Bcon ADB?
hoto il produttore e sono riuscito ad ottenere il codice per abilitare la modalità sviluppatore .
Ciao a tutti mi chiedevo se esiste una guida per disabilitare il blocco dei lanciatori con ADB?
Ho contatatto il produttore e sono riuscito a ottenere il codice per abilitare la modalità di sviluppo.
Click to expand...
Click to collapse
yes, you need to install a launcher then you need adb over wifi, (adb connect "ip adress:9876") and use this command : adb shell setprop persist.sys.xl.launcher "package name of the launcher you want"
and voila the default launcher will be that one
Do you have echo on the other end when using carplay ?
panic2k said:
Oh all that is really annoying. It was for me the same behavior until i got the update. I had opened disputes and just annoying them. My seller has read my message but i have no answer till now. Let's wait a few hours. I just can hope he send me an answer. He fooled me with some of device specs in his advertisements, he should know already that i knows. If nothing happens i can open open a dispute for your 45 bucks and send you these. Greatest would be community support from him after all issues before.
Click to expand...
Click to collapse
пожалуйста, скажите мне, кто-нибудь решил проблему на xl6107? У меня постоянная перезагрузка, что я могу сделать? Помогите, пожалуйста
Mod translation via GT: please tell me has anyone solved the problem on xl6107? I have a constant reboot, what can I do? Help me please
Ciao ho fatto un ripristino alle impostazioni di fabbrica, ma rimane in bootloop sulla schermata Android e si riavvia di nuovo. Come posso sbloccarlo? Mi puoi aiutare?
Mod translation via GT: Hi I did a factory reset, but it stays in bootloop on the android screen and restarts again. How can I unlock it? Can you help me?
sfortunatamente, ho la stessa cosa che non so fare da solo, quindi ho scritto qui
Mod translation via GT: unfortunately, I have the same thing that I can't do on my own, so I wrote here
@Cumati74 & @asker050
Greetings. As a courtesy I have translated your recent posts. Please be respectful and observant of XDA Rule #4 for all of your future posts.
Spoiler: XDA Rule #4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Thank you for your cooperation.
-Regards: Badger50
dandell80 said:
Goodmorning everyone,
I hope you can help me.
I also have the same model and I have already made this update all ok until a few days ago when trying to tinker a bit on the build.prop I evidently did some damage in fact now the head unit remains blocked on the boot animation and there is no towards being able to start it.
I'm trying to figure out if there is a way to access recovery mode hoping that from there there is a factory reset / wipe data or something similar but so far nothing.
This model has no physical buttons but only the RST button.
Thank you
Click to expand...
Click to collapse
hoi dandell attach a usb port to the 6 pin connector only then plug the mouse into the usb then you will be able to access you apps etc on your unit hope this helps
asker050 said:
пожалуйста, скажите мне, кто-нибудь решил проблему на xl6107? У меня постоянная перезагрузка, что я могу сделать? Помогите, пожалуйста
Mod translation via GT: please tell me has anyone solved the problem on xl6107? I have a constant reboot, what can I do? Help me please
Click to expand...
Click to collapse
factory reset may help connect a mouse to the unit then access you apps etc maybe you can factory reset the unit shoul work
you can only attach a usb mouse to the six pin usb not the 4 pin then you will have acess to your unit
Salve a tutti, vi chiedo cortesemente aiuto in quanto con il mio file data reset 6521 parte la procedura di reset dati di fabbrica, ma il problema persiste e credo che qualche aggiornamento automatico mi abbia creato il problema. Lo stesso è successo 2 anni fa con il file sono stato in grado di correggere e modificare le impostazioni di risoluzione. Adesso è impostato su 1080x600 qualcosa del genere, quando in realtà dovrebbe essere su una risoluzione inferiore per risolvere il problema. Qualcuno ha un ripristino del file di risoluzione aggiornato? postato alcune foto del dispositivo, aggiungo anche che ho provato a caricare il file 6531 sulla chiavetta ma non riesco a leggerlo perché forse è da scompattare. ho bisogno di aiuto per favore ho postato in inglese
poseidon1982' said:
Salve a tutti, vi chiedo cortesemente aiuto in quanto con il mio file data reset 6521 parte la procedura di reset dati di fabbrica, ma il problema persiste e credo che qualche aggiornamento automatico mi abbia creato il problema. Lo stesso è successo 2 anni fa con il file sono stato in grado di correggere e modificare le impostazioni di risoluzione. Adesso è impostato su 1080x600 qualcosa del genere, quando in realtà dovrebbe essere su una risoluzione inferiore per risolvere il problema. Qualcuno ha un ripristino del file di risoluzione aggiornato? postato alcune foto del dispositivo, aggiungo anche che ho provato a caricare il file 6531 sulla chiavetta ma non riesco a leggerlo perché forse è da scompattare. ho bisogno di aiuto per favore ho postato in inglese
Click to expand...
Click to collapse
The solution of your problem is:
誰が見てもわかるように、英語で書く。
TorstenH said:
The solution of your problem is:
誰が見てもわかるように、英語で書く。
Click to expand...
Click to collapse
Hello everyone, I kindly ask you for help as the factory data reset procedure starts with my data reset 6521 file, but the problem persists and I believe that some automatic update has created the problem for me. The same happened 2 years ago with the file I was able to fix and change the resolution settings. Now it's set to 1080x600 something like this, when really it should be on a lower resolution to fix it. Does anyone have an updated resolution file restore? posted some photos of the device, I also add that I tried to load the 6531 file on the stick but I can't read it because maybe it needs to be unpacked. i need help please i posted in english
TorstenH said:
The solution of your problem is:
誰が見てもわかるように、英語で書く。
Click to expand...
Click to collapse
Hello everyone, I kindly ask you for help as the factory data reset procedure starts with my data reset 6521 file, but the problem persists and I believe that some automatic update has created the problem for me. The same happened 2 years ago with the file I was able to fix and change the resolution settings. Now it's set to 1080x600 something like this, when really it should be on a lower resolution to fix it. Does anyone have an updated resolution file restore? posted some photos of the device, I also add that I tried to load the 6531 file on the stick but I can't read it because maybe it needs to be unpacked. i need help please i posted in english
poseidon1982' said:
Hello everyone, I kindly ask you for help as the factory data reset procedure starts with my data reset 6521 file, but the problem persists and I believe that some automatic update has created the problem for me. The same happened 2 years ago with the file I was able to fix and change the resolution settings. Now it's set to 1080x600 something like this, when really it should be on a lower resolution to fix it. Does anyone have an updated resolution file restore? posted some photos of the device, I also add that I tried to load the 6531 file on the stick but I can't read it because maybe it needs to be unpacked. i need help please i posted in english
Click to expand...
Click to collapse
Please post the all information of the screen of your 2nd photo. Give further information regarding head unit brand and name. Maybe you can provide data via application CPU-Z like name of CPU...
Soon I will provide all the data in my possession
TorstenH said:
Please post the all information of the screen of your 2nd photo. Give further information regarding head unit brand and name. Maybe you can provide data via application CPU-Z like name of CPU...
Click to expand...
Click to collapse
It's a SC9853 unit which gets sold by different vendors. Important is that it has a G32 MCU and a 480 (instead of 600/720) display height.
You should provide the vendor name and ask your seller in parallel for a firmware.
TorstenH said:
È un'unità SC9853 che viene venduta da diversi fornitori. Importante è che ha un MCU G32 e un'altezza del display di 480 (invece di 600/720).
Dovresti fornire il nome del fornitore e chiedere parallelamente al tuo venditore un firmware.
Click to expand...
Click to collapse
fan COIKA by aliexpress
poseidon1982' said:
Ventilatore Coica
Click to expand...
Click to collapse
?
poseidon1982' said:
fan aliexpress
Click to expand...
Click to collapse
FanCoika
TorstenH said:
?
Click to expand...
Click to collapse
Ventilatore "Coika" aliexpress