Hi Guys,
I wanted to let you know of an interesting change potentially applicable to any customized Rom.
I state that I follow the Android world for some time, I have rarely made 'active part' in the media and in forums, but I wanted to tell you this.
Let's talk about change the animations of the graphic interface of android, HTCSense or Aosp-based (like OpenDesire or DeFrost or..).
The change can potentially apply to any rom in use on any phone model.
Owning a Htc Magic 32b and Desire (stupid vodafone, made me wait 2 months for the nexus one, then I send them to hell ..) I present the guidelines for application of animation on this model (HTC DESIRE).
I will not go over, step intended to illustrate the steps to quickly apply these customizations (requires basic knowledge of shell / terminal / command line - call it what you want, depending on the your OS. I use Linux, Windows and OSX - take as an example the Linux OS):
'I am not responsible if something goes wrong'
0) Make a Nandroid Backup
1) Download and install the environment Android SDK, downloadable from here -> http://developer.android.com/sdk/index.html
2) Download the packages for 'Metamorph' from the links contained in this address: http://forum.xda-developers.com/showthread.php?t=774738
There are 4 packages corresponding to the 4 animations.
(Note: These animations can be applied directly as packed by Metamorph (downloadable from the market), only that the transaction requires full access r/w to the directory /system, this is not possible with the HTC Desire (not really a dev- Phone), to write to this device a dir /system it's only possible via recovery)
3) Connect the HTC Desire to the PC with the USB cable and enable the option 'Debug USB' Settings-> Applications-> Development.
4) Open a terminal and stand in the path /tools where you have installed the Android SDK in paragraph 1 (eg -> / home/frank17/android-sdk-linux_x86/tools
5) Now take from the phone file '/system/framework/framework-res.apk', responsible for the appearance of what is displayed by the UI, with this command:
#./Adb pull/system/framework/framework-res.apk
6) Now we will have on the local file 'framework-res.apk', we'll find it in precisely this path '/your_home/android-sdk-linux_x86/tools'. It 's a compressed file, and you can open it with any archive manager, like 7zip).
(Idem (it's the same) for the package downloaded in step 2. If we open one of 4, we can see its contents, and these are all files .xml that modify the animations, which we copy into our 'framework-res.apk' , precisely in the path /res/anim. You have to overwrite all, as explained in the next step)
7) Edit the original file ns 'framework-res.apk', opening with the archive manager, stay in the path /res/anim.
Then we open with another instance of the archive manager of a package of four animations, such as' Flying-animation.zip ', we move in framework-res/res/anim and copy all the files. Xml inside of our same file path 'framework-res.apk'
8) Save the new file framework-res.apk.
9) Reboot the Hct Desire in recovery (still connected via usb), I use clockwork, but Amon_Ra it's the same.
10) Into special section, mount the directory /system
11) From the OS shell on your Pc, we'll push new file framework-res.apk in the path /system/framework of your phone, with this command:
#./adb push framework-res.apk /system/ framework
12) We perform a wipe of Dalvik-cache (fundamental)
13) Reboot your Phone
14) Enjoy the new animation 'Fly effect'. There you can view with any operation to open popup windows (for example, menu-> background-> background = selection will notice that the window on the screen you get when you fly, rather than with the simple zoom effect, they're ispirated everything from compiz)
Sorry for bad English, i'm Italian.
Ispiration: http://forum.xda-developers.com/showthread.php?t=774738
Credit: all animation are created by Stale Bread
You can see the videos here:
Fly In Animations:
http://www.youtube.com/watch?v=craNDI-XWos&feature=player_embedded
Fold Animations:
http://www.youtube.com/watch?v=-zodBUQEUDs&feature=player_embedded
Flip Animations:
http://www.youtube.com/watch?v=dqrBF0TE3Qk&feature=player_embedded
Bounce Animations:
http://www.youtube.com/watch?v=pMNNCjvxyY8&feature=player_embedded
p.s.
My configuration:
HTC Desire A8181
Radio 32.44.00.32U_5.09.05.30_2
ROM: I use this rom:
[15/11] Pre-rooted Stock Froyo (2.10.405.2) [Optional mods]
(Translated in ITA) Nuove Animazioni Android UI
Ciao Ragazzi,
volevo mettervi a conoscenza di una modifica interessante potenzialmente applicabile a qualsiasi Rom Customizzata.
Premetto che seguo il mondo Android da diverso tempo, raramente mi sono reso parte 'attiva' nel supporto e nei forum, ma questa volevo dirvela.
Parliamo di modificare le animazioni dell'interfaccia grafica di android, sia Aosp-based sia HTCSense.
La modifica potenzialmente potete applicarla su qualsiasi rom in uso su qualsiasi modello di cellulare.
Possedendo un Htc Magic 32b e un Htc Desire (maledetta vodafone, mi ha fatto aspettare 2 mesi il nexus one, poi li ho mandati a quel paese..) presenterò la guida per l'applicazione delle animazioni su quest'ultimo modello.
Non mi dilungo oltre, passo direttamente ad illustrarvi i passi per applicare velocemente queste personalizzazioni (è richiesta una base di conoscenza su shell/terminale/riga di comando - chiamatela come volete, in base al Vs OS. Io uso Linux, Windows e OSX - prenderò come esempio l'os Linux):
'Non sono responsabile di eventuali malfunzionamenti, se seguite adeguatamente tutti i passi tutto funzionerà'
0) Fate un backup del sistema con Nandroid
1) Scaricate e installate sul Vs PC l'ambiente Android SDK, scaricabile da qui -> http://developer.android.com/sdk/index.html
2) Scaricate i pacchetti per 'Metamorph' dai link contenuti in questo indirizzo: http://forum.xda-developers.com/showthread.php?t=774738
Sono 4 pacchetti corrispondenti alle 4 animazioni.
(nota: queste animazioni così impacchettate possono essere applicate direttamente da Metamorph (scaricabile dal market), solo che l'operazione richiede accesso full r/w alla directory /system, cosa non possibile con l'HTC Desire (non è propriamente un dev-Phone), per questo device la scrittura in /system è possibile solo via recovery)
3) Collegate l'HTC Desire al pc con il cavo USB e abilitate l'opzione 'Debug USB' da Impostazioni->Applicazioni-> Sviluppo.
4) Aprite un terminale e posizionatevi nel path /tools dove è stata installata l'SDK Android al punto 1 (es. -> /home/frank17/android-sdk-linux_x86/tools
5) Adesso preleveremo dal telefono il file '/system/framework/framework-res.apk', responsabile dell'aspetto di quel che viene visualizzato dall'UI, con questo comando:
# ./adb pull /system/framework/framework-res.apk
6) Ora avremo in locale il file 'framework-res.apk', precisamente lo troveremo in questo path '/tua_home/android-sdk-linux_x86/tools'. E' un file compresso, ed è possibile aprirlo con un qualsiasi gestore di archivi, tipo 7zip).
(Idem per i package scaricati al punto 2. Se apriamo uno dei 4, possiamo visualizzarne il contenuto e questi non sono altro che i file .xml che modificano le animazioni, che dovremo copiare all'interno del nostro 'framework-res.apk', precisamente all'interno del path /res/anim. Dovete sovrascrivere tutto, come illustrato al punto successivo)
7) Modifichiamo il ns originale file 'framework-res.apk', aprendolo con il gestore di archivi, posizioniamoci all'interno del path /res/anim.
Poi apriamo con un'altra istanza del gestore di archivi uno dei quattro package di animazioni, ad esempio 'Flying-animation.zip', spostiamoci in framework-res/res/anim e copiamo tutti i file .xml presenti all'interno dell'omonimo path del ns file 'framework-res.apk'
8) Salviamo il file framework-res.apk.
9) Riavviamo l'Htc Desire in recovery (sempre collegato via usb), io uso clockwork, ma anche Amon_ra va bene uguale.
10) Dalla sezione apposita, montiamo la directory /system
11) Da shell dobbiamo pushare il nuovo file framework-res.apk all'interno del sistema, con questo comando:
# ./adb push framework-res.apk /system/framework
12) Eseguiamo il wipe della Dalvik-cache (fondamentale)
13) Riavviate il telefono.
14) Godetevi la nuova animazione ' Fly effect'. La potete visualizzare con qualunque operazione che apra finestre di popup (ad esempio, menu-> sfondo-> selezione sfondo= noterete che la finestra vi arriva sullo schermo volando, anzichè con il semplice effetto zoom, hanno preso tutto da compiz )
Click to expand...
Click to collapse
Nice. I've included UI animations for one week in my theme ( Blue Sense Theme 1.5 ) and they are working great.
Do you have any screenshots/videos ?
You can see the video here:
http://forum.xda-developers.com/member.php?u=2351605
Fly In Animations:
http://www.youtube.com/watch?v=craNDI-XWos&feature=player_embedded
Fold Animations:
http://www.youtube.com/watch?v=-zodBUQEUDs&feature=player_embedded
Flip Animations:
http://www.youtube.com/watch?v=dqrBF0TE3Qk&feature=player_embedded
Bounce Animations:
http://www.youtube.com/watch?v=pMNNCjvxyY8&feature=player_embedded
This is awesome! Thank you...
What I miss is the orentation rotate animation that was enabled back in Cupcake 1.5...
WOW ! i cant believe it ! Amazing !!! thx a lot
Looking great
Sent from my HTC Desire using XDA App
Shouldnt we be able to use the 'metamorph' technique to apply this if we have S-OFF. I though S-OFF gave us full RW access to the directory/system. Anyone tried it using the Metamorph way on the Desire??
cybermessiah said:
Shouldnt we be able to use the 'metamorph' technique to apply this if we have S-OFF. I though S-OFF gave us full RW access to the directory/system. Anyone tried it using the Metamorph way on the Desire??
Click to expand...
Click to collapse
Yes, with CM 6.1.0 RC1 and CM Nightly. Working great!
Can you write a Italian version for Italian user?can it be applied on sense ROM?
sent from the future
cybermessiah said:
Shouldnt we be able to use the 'metamorph' technique to apply this if we have S-OFF. I though S-OFF gave us full RW access to the directory/system. Anyone tried it using the Metamorph way on the Desire??
Click to expand...
Click to collapse
Used metamorph flashing fold animation and everything works perfect.
Thanks for the work!
Sent from my HTC Desire using XDA App
Applied the fly-in animations using metamorph and my desire went into a neverending bootloop (pinky desire).
Doing the nandroid first is important.
Hi Mattia.. if u want, i can prepare it
Sent from my HTC Desire using Tapatalk
Bootloops in my Desire w/S-OFF running Leedroid 2.2f (already have a custom framework res via UOT kitchen).
Nandroid restored
frank17next said:
Hi Mattia.. if u want, i can prepare it
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
If you want and have enough time why not?
sent from the future
st0kes said:
Applied the fly-in animations using metamorph and my desire went into a neverending bootloop (pinky desire).
Click to expand...
Click to collapse
My one got into a bootloop, too. But I have LeeDroid with the blue carbon theme.
I'm using the Fly In Animations with Metamorp (with latest CM nighly). The phone seems faster with these animations - it's a kind of placebo. I hope CM will use these UI-tunnings.
Something similar happens with the animations in the RodriguezStyle (sp) MIUI rom. It looks nice, i wish i could do **** like this!
As with all Metamorphs, I get a boot loop. defrost 6.0e
Will give it another go after restore.
Do I need to start with a standard framework-res.apk? I currently have one from UOT Kitchen
Edit... Just seen this:
robbiekhan said:
Bootloops in my Desire w/S-OFF running Leedroid 2.2f (already have a custom framework res via UOT kitchen).
Nandroid restored
Click to expand...
Click to collapse
Maybe thats the problem then
DesirableHTC said:
Something similar happens with the animations in the RodriguezStyle (sp) MIUI rom. It looks nice, i wish i could do **** like this!
Click to expand...
Click to collapse
And as for you.... Stop following me around
... or am I following you?
Related
Ive been looking on here and im trying to find the software version for the camera that switches it to lanscape mode when a photo is taken but i cant find it anywhere, is it v.2.70 or something similar?
I did use one hack but it sent my today screen mental so had to do a Hard Reset for the device to work properly again
its Ver 2.7 (build 20117). what i have is the modified version by Ampda (thanks btw Ampda) which includes the speckle reduction.
i tried that but it made my today screen go mad. although that was when i was running the older rom so it may be ok now ive upgraded to the latest one?
could do with him in here really to answer my question lol
Guys, speckle reduction is a registry patch.
I don't get what the difference is in the camera versions: if you want landscape, why not just rotate before starting the camera?
I posted camera.exe from my Magician in the VJlumos thread. Not sure if it's old or new, but it's what I've got..
Keep us informed of your findings jaso2005.
V
vijay555 said:
if you want landscape, why not just rotate before starting the camera?
Click to expand...
Click to collapse
Because there is some software so that when you press the camera button it automatically switches to landscape mode, lets you take the pics and then when you exit it, it switches back to how it was previously!
jaso2005 said:
vijay555 said:
if you want landscape, why not just rotate before starting the camera?
Click to expand...
Click to collapse
Because there is some software so that when you press the camera button it automatically switches to landscape mode, lets you take the pics and then when you exit it, it switches back to how it was previously!
Click to expand...
Click to collapse
Really? Sound very useful...
What program is that?
I use this .cab file that i have found in this forum.. Using this, camera start in landscape mode and it doesn't create any error...
The cab file work correctly on qtek s 100 rom 1.12...ita?Wat's the advantages?
cagio said:
I use this .cab file that i have found in this forum.. Using this, camera start in landscape mode and it doesn't create any error...
Click to expand...
Click to collapse
Just installed it and it made the same error but ive found how to over come it! Install a different theme and then install the theme you were using before and it works fine!
Yes the tricks it's to change the theme with another...
Per Linux:
I vantaggi sono i seguenti:
- all'avvio di camera lo shermo diventa in landscape, quindi molto piu' bello da vedere (e ti sembrera' ti tenere una macchina fotografica digitale in mano..)
- i files (foto e video) vengono salvati non piu' in cartelle giornaliere riportanti la dati, ma direttamente nelle rispettive cartelle /My picture e /My video presenti o nella RAM o nella scheda di memoria (a seconda di dove hai deciso di salvare le tue cose..).. Volendo agendo sul registro si puo' fare in modo che salvi i files in altre cartelle che vuoi tu.
- cosa importante, finalmente le foto vengono salvate in formati del tipo 640*480 e non 480*640 (anche se nel menu' di configurazione ci sono ancora quest'ultimi valori). Questo permette di spedire mms con foto grandi e non con dei moncherini..
Grazie 1000 x l arisposta cagio veramente, ci sono controindicazioni ad installo con rom ita 1.12?E 1 ultima cosa ci sono dei miglioramenti x la qualità delle foto o no?A presto ciao ciao
No no ci sono controindicazioni, anche io uso la tua stessa ROM.. Qualche miglioramento c'è, ma per raggiungere il massimo installa questo file che va ad agire su qualche parametro di registro.. (in pratica toglie il fastidioso effetto neve e rende il tutto un po' piu' luminoso..).
PS: i files che ho postato non sono di mia produzione ma gli ho trovati su questo forum, e quindi sono il frutto di menti lodevoli di altre persone..
Ancora grazie 1000 installato tutto e funge alla grande!!!!A presto ciao ciao
Please.. i installed this new camera.. all works but when i use wisbar+wad and i start camera.. the camera application automatically minimize itself!
I am thinking it's the landscape mode so.. how can i restore just the portrait setting for this new camera app installed?
Please help.. thanks
cagio said:
I use this .cab file that i have found in this forum.. Using this, camera start in landscape mode and it doesn't create any error...
Click to expand...
Click to collapse
I'm using this version of the camera app because it came with the T-Mob 1.13 ROM I'm currently using. What I found is that although I see speckles in the "view finder" when taking pics in low light conditions, the picture will not have any speckles when saved. A major improvement in quality I think.
Camera V3 on Dopod 818 Pro
I had a preview of the Dopod 818 Pro at a shop. The Camera Version is V3 & it is much better quality compared the current version posted by ampda. Not discreditying ampda but It may be because of the new 2Mb camera that cause the improvement.
Hopefully, there's Dopod 818 Pro owner who is kind enough to extract that camera software & the ablum and post here for us to try.
What's the method for uninstall the patch?
There is no way to uninstall this so-called "patch". IMHO it is crap! Only hard reset may help. the feature with theme-changing fix helps, but you must do it after each soft reset!
And there is no way to force to work apps from other devices, like wizard etc.
How about deleting the camera.exe in Windows folder. Windows will automatically recover the file from the ROM of your device.
programatix said:
How about deleting the camera.exe in Windows folder. Windows will automatically recover the file from the ROM of your device.
Click to expand...
Click to collapse
This is the method for uninstall the patch??Thanks
[ENG]
I made some 'progress and my rom is taking shape.
One problem, however, stopped me:
build_rom.bat crashes and brings me the following error:
ROM Kitchen Executable has stopped working.
I do not understand if my problem is the kitchen or if it is a problem of windows.
First of all, I have already managed to create a file 2 times .nbh flashabile (and running).
Build_rom.bat I happened to run it several times by test days ago, and the error above gave me yet another time when the second DOS window.
I solved with a system restore, but now I do not want to repeat it. I would like to understand what is wrong.
Using the kitchen Bepe with Windos Vista on C: \
Please Help.
(Erviuuuuuussss....?!)
-------------------
[ITA]
Ho fatto un po' di progressi e la mia rom stà prendendo forma.
Un problema però mi blocca:
build_rom.bat crasha e mi riporta il seguente errore:
ROM Kitchen Executable ha smesso di funzionare.
Non capisco se il mio problema dipende dalla cucina o se è un problema di windows.
Premetto che sono già riuscito a creare 2 volte un file .nbh flashabile (e funzionante).
Build_rom.bat mi è capitato di lanciarlo più volte facendo delle prove giorni addietro, e l'errore riportato sopra me l'ha dato anche un'altra volta all'apertura della seconda finestra DOS.
Ho risolto con un ripristino di sistema, ma adesso non vorrei ripeterlo. Mi piacerebbe capire cos'è che non và.
Uso la cucina di Bepe con Windos Vista su C:\
I suggest you ask in the threads concerned with the development of these applications...
Here and here.
You may actually get an answer that way...
Thanks for the suggestion l3v5y.
Batista70Phone by Drigerott
PER DOWNLOAD DEI FILE ANDATE QUA : Mod Edit : Link removed, rom containing warez app, and post not translated in english
Vi ringrazio tutti
per il sostegno e le donazioni che fate...
davvero di cuore
-Non sono responsabile se brikkate il telefono, mi raccomando prima di fare qualsiasi cosa leggete bene e fate un backup con nandroid.
ISTRUZIONI
-Consigliato vivamente il Wipe DATA FACTOR (se NON avete mai fatto apps2sd lasciate perdere il wipe sdcard: ext)
-scaricate
-mettere il file b70p.zip nella sdcard
-Flashare la NUOVA 2.1 .BIN 1.100.39(per chi ce l'ha salti il passaggio)
-Flashare la recovery di malez 0.5.4:
-aprire la recovery modificata (adb reboot recovery, o con quickboot scaricabile dal market, o con la combinazione di tasti volume up+ camera+ power)
-selezionare flash zip from sd card
- selezionate b70p.zip e flashate
-riavviate e godetevi la rom
PROBLEMI:
-Se avete riavvii andando in account e sincronizzazione
-se il cell si blocca al bootanimation
-se avete crash imprevisti
SOLUZIONE:
fate un Wipe data factor (dalla recovery, perderete tutti i file)
MD5: 1999F129A3AB7FA665FD5A770CF2EF29
per controllare usate su windows
ChangeLog
changelog 2.0:
modifiche
-basata sulla nuova 1.100.39
-Root 2.2 già incluso
-busybox già incluso
-Boot con OC a 920mhz (pronto per il thetering wifi)
-Tema stock
-Rimosse applicazioni acer
-Tutte le app ottimizzate
-Audio hack per aumentare il volume in chiamata
-Apps2sd funzionante usando la recovery
-Touch sensibile
aggiunto
-LauncherPRO 0.6.72
-Divx player
-nuova bootanimation
-Htc IME 27
-titanium backup
-Root explorer
-quick boot
-Music mod
-Youtube mod
-DTG full
-SetCPU 2.01
-Gscript Lite
Vecchi ChangeLog
SPOILER: LEGGI
Consigli e FIX:
TETHERING (grazie L0cutus)
post105501.html#p105501
Se invece volete anche il tethering semplicemente installate:
LiquidTether (CREDITS to gengaro86)
Dopo aver installato LiquidTether, per configurarlo, andate nella directory
/data/data/net.gengaro.liquid ed editate il file wpa_tether.conf nei campi:
(usate il solito root explorer,se serve, mettete in r/w la directory (bottone in alto))
ssid -> il nome (essid) che volete dare alla vostra rete wifi
wep_key0 -> la password WEP che preferite (13 caratteri alfanumerici)
salvate il tutto e cancellate l'eventuale file di backup creato (wpa_tether.conf.bkp)
lanciate il programma LiquidTether ed attivate il tutto con l'apposito pulsante start
NB: il WIFI _DEVE_ essere disabilitato PRIMA di far partire il tutto !!!
-se volete il cell più reattivo, soprattutto nell'apertura sms, galleria, contatti
non usate autokiller (lasciate i valori di default e non chiudete in continuazione con un task killer)
è tutto istantaneo (purtroppo le prime versione di eclair per il liquid hanno fatto diffondere troppo questo autokiller)
-Apps2sd: E' una funziona che vi permette di installare le applicazione non piu' sulla memoria del cellulare, ma sulla memorycard
istruzioni:
-flashare la b70p
-salvarsi tutto ciò che è sulla sdcard sul pc
-Entrare nella recovery
-selezionare partition/repair sdcard
-selezionare partition sd
-dare la conferma per procedere (la sd verrà cancellata)
-(con il volume) mettete 0mb come swap, 512mb ext2, e date conferma
-ora avete formattato la sdcard
-ora andate in Other
-move apps to SD
voilà ^^
ricordo che:
Solo le app vanno sulla sd...mentre la dalvik.cache( creata dalle app per far si che si aprano più velocemente) rimane sulla memoria interna....quindi ad ogni nuovo programma un po di memoria interna viene riempita....(praticamente solo il file .DEX che c'è negli apk) il resto dell'app va nella SD
Finito ora avete tutte le app nella sdcard
-Maps con navigarore:
-EStrongs TASK MANAGER se volete proprio usare in task killer, è free lo trovate nel market è l'unico che non rimane in background secondo me è il migliore in assoluto
VECCHIE RELEASE
Video Recensione :
Nice, but...
English please?
do not post in italian
its not an italian forum
#1 rule of xda is post in god damn english
Google Translate plus a couple of changes by me:
Thank you all
for their support and donations that do ...
really heart
-I am not responsible if it bricks the phone, I recommend you read before you do anything good and make a backup with nandroid.
INSTRUCTIONS
Strongly Recommended Wipe-DATA FACTOR (if you have never let lose apps2sd wipe SDCard: ext)
-Download
-Put the file in b70p.zip SDCard
NEW-Flashing 2.1. BIN 1.100.39 (for those who have it jump the route)
-Flashing the recovery of malez 0.5.4:
-Open the recovery amended (adb reboot recovery, or downloaded from QuickBoot market, or the combination of volume buttons double up power)
-Select flash from sd card zip
- Selected b70p.zip and flash
-Reboot, and enjoy the Rom
PROBLEM:
-If you restart going into account and synchronization
-If the cell is blocked in bootanimation
-If you crash unexpected
SOLUTION:
Wipe make a data factor (the recovery, you will lose all files)
MD5: 1999F129A3AB7FA665FD5A770CF2EF29
used to check on windows
ChangeLog
changelog 2.0:
changes
1.100.39-based new
Root-2.2 already included
Busybox-already included
-Boot with OC to 920mhz (ready for thetering wifi)
Theme-stock
-Removed applications acer
All-optimized app
Audio-hack to increase the volume in call
Apps2sd-working using the recovery
Touch-sensitive
added
LauncherPRO-0.6.72
-Divx player
New-bootanimation
HTC 27-EMI
Titanium-up
Root-explorer
Quick-Boot
Music-mod
Youtube mod-
Full-DTG
2.1-SetCPU
Lite-Gscript
Old ChangeLog
Tethering (thanks L0cutus)
post105501.html # p105501
If you also want to simply install the tethering:
LiquidTether (CREDITS to gengaro86)
After installing LiquidTether, to configure it, go to the directory
/ Data / data / net.gengaro.liquid and edit the file wpa_tether.conf fields:
(Use the explorer usually root, if needed, put in R / W directory (top button))
ssid -> name (essid) you want to give your wifi network
wep_key0 -> WEP password of your choice (13 alphanumeric characters)
saved everything and delete any backup files created (wpa_tether.conf.bkp)
LiquidTether run the program and activate all the appropriate button start
Note: The WiFi _must_ be disabled before starting the whole!
-If you want the cell more responsive, especially in the opening sms, gallery, contacts
Unused autokiller (leave the defaults and do not close all the time with a task killer)
Flash is all (unfortunately the first version of eclairs for liquid spreading too have this autokiller)
Apps2sd-E 'a feature that lets you install the application no longer' on the phone's memory, but on MemoryCard
Instructions:
-Flashing the b70p
Save-all that is on SDCard pc
Enter-recovery
-Select partition / repair SDCard
Select partition-sd
-Give confirmation to proceed (the sd will be deleted)
- (With volume) put 0MB swap, 512mb ext2, and dates confirmed
-Now you have formatted the SDCard
-Now go in Other
-Move apps to SD
voila ^ ^
remember:
Only to be app on the sd ... while dalvik.cache (created by the app is to be opened more quickly) is the internal memory with each new program .... then a bit of internal memory is filled ... . (practically only the. apk DEX in there) the rest of the JPA is the SD
Now you have finished all the apps in SDCard
-Maps with navigarore:
EStrongs-TASK MANAGER if you want to use in their task killer, is found in the free market is the only one who does not remain in the background I think is the best ever
Thanks to edit your post and put it in English.
(You can still let italian below if you want, but english is MANDATORY on XDA !!!!)
i'm italian but... i HATE italians that write in ITALIAN on this forum.
To the OP:
Couple of things.
1. Post in English. If you must post in Italian, then you must write an English translation of your post.
2. Root explorer (included in your rom) is a paid app. Please remove it from the rom as soon as possible. Failure to comply will result in the thread being closed and your account to be temporarily disabled.
Closed until the OP contact me.
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
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