Meelouw Posted December 31, 2010 Share Posted December 31, 2010 tuto réalisé (j'foiré car j'avais pas lu le tuto sur les adb) démarrage en cours ... prépa d'la sd ... code pin ... et ... tout marche =D RAS merci =) Quote Link to comment Share on other sites More sharing options...
Rakasuki Posted January 7, 2011 Share Posted January 7, 2011 Ta bien de la chance dit donc ! \o J'ai réessayé et j'ai toujours ce plantage de Sense. Quote Link to comment Share on other sites More sharing options...
xazuretsu Posted January 10, 2011 Share Posted January 10, 2011 (edited) Pour le sdk et adb, il faut aller ici. Quelqu'un pourrais mettre en ligne en Screenshots du raccourci market ? Edited January 10, 2011 by XaZuretsu Quote Link to comment Share on other sites More sharing options...
Rakasuki Posted January 10, 2011 Share Posted January 10, 2011 Sur le poste original mon ami ;-) (Sur XDA) Quote Link to comment Share on other sites More sharing options...
Meelouw Posted January 10, 2011 Share Posted January 10, 2011 ça marche toujours pas toi Rakasuki ? Quote Link to comment Share on other sites More sharing options...
xazuretsu Posted January 10, 2011 Share Posted January 10, 2011 Merci, j'avais pas pris la peine de regarder le post de xda. Envoyé depuis mon HTC avec Tapatalk Pro. Quote Link to comment Share on other sites More sharing options...
hadescedric Posted January 11, 2011 Share Posted January 11, 2011 je comprends rien à ce qu'il faut faire... Il faut les taper où les commandes? Quote Link to comment Share on other sites More sharing options...
Meelouw Posted January 11, 2011 Share Posted January 11, 2011 sur l'invite de commande de windows je te conseille de regarder ça : Quote Link to comment Share on other sites More sharing options...
hadescedric Posted January 11, 2011 Share Posted January 11, 2011 J'ai fait tout comme disait le tuto mais il me dit que adb n'existe pas Quote Link to comment Share on other sites More sharing options...
Meelouw Posted January 11, 2011 Share Posted January 11, 2011 c'que t'a mal fait ^^" faut bien se mettre dans le dossier tools avec l'invite : cd c:\[emplacementdudossiertools] Quote Link to comment Share on other sites More sharing options...
hadescedric Posted January 11, 2011 Share Posted January 11, 2011 Merci de l'indication en plus mais j'ai toujours ça : C:\>cd c:\androidSDK\tools c:\androidSDK\tools>adb shell rm /system/app/Rosie.apk 'adb' n'est pas reconnu en tant que commande interne ou externe, un programme exécutable ou un fichier de commandes. Quote Link to comment Share on other sites More sharing options...
Meelouw Posted January 11, 2011 Share Posted January 11, 2011 ta bien tout les fichiers dans le dossier ? qui servent à faire fonctionner l'adb ? Quote Link to comment Share on other sites More sharing options...
hadescedric Posted January 11, 2011 Share Posted January 11, 2011 (edited) ba j'imagine, en tout cas j'ai bien copié le fichier "lib" Edited January 11, 2011 by hadescedric Quote Link to comment Share on other sites More sharing options...
Meelouw Posted January 11, 2011 Share Posted January 11, 2011 serait plutôt le dossier tools qui m'interesse :P Quote Link to comment Share on other sites More sharing options...
hadescedric Posted January 11, 2011 Share Posted January 11, 2011 voila :) Quote Link to comment Share on other sites More sharing options...
Meelouw Posted January 12, 2011 Share Posted January 12, 2011 normal il te manque des fichiers adb.exe adbwinapi.dll adbwinusb.api http://www.megaupload.com/?d=4A55Q24I je t'ai upload les miens ;) tu les rajoutes dans le dossier tools et ça sera bon Quote Link to comment Share on other sites More sharing options...
hadescedric Posted January 12, 2011 Share Posted January 12, 2011 (edited) ah ok lol, merci beaucoup !!! :D Bon bah ça marche pas, j'ai fait ce qui est marquer, pour info j'ai ça dans mon cmd : C:\>cd c:/androidsdk/tools c:\androidSDK\tools>adb shell rm /system/app/Rosie.apk adb server is out of date. killing... * daemon started successfully * c:\androidSDK\tools>adb push c:/androidsdk/tools/Rosie_market.apk Android Debug Bridge version 1.0.26 -d - directs command to the only connected USB devic e returns an error if more than one USB device is present. -e - directs command to the only running emulator. returns an error if more than one emulator is r unning. -s <serial number> - directs command to the USB device or emulator w ith the given serial number. Overrides ANDROID_SERI AL environment variable. -p <product name or path> - simple product name like 'sooner', or a relative/absolute path to a product out directory like 'out/target/product/sooner'. If -p is not specified, the ANDROID_PRODUCT_OUT environment variable is used, which must be an absolute path. devices - list all connected devices connect <host>[:<port>] - connect to a device via TCP/IP Port 5555 is used by default if no port number is specified. disconnect [<host>[:<port>]] - disconnect from a TCP/IP device. Port 5555 is used by default if no port number is specified. Using this ocmmand with no additional arguments will disconnect from all connected TCP/IP devic es. device commands: adb push <local> <remote> - copy file/dir to device adb pull <remote> [<local>] - copy file/dir from device adb sync [ <directory> ] - copy host->device only if changed (-l means list but don't copy) (see 'adb help all') adb shell - run remote shell interactively adb shell <command> - run remote shell command adb emu <command> - run emulator console command adb logcat [ <filter-spec> ] - View device log adb forward <local> <remote> - forward socket connections forward specs are one of: tcp:<port> localabstract:<unix domain socket name> localreserved:<unix domain socket name> localfilesystem:<unix domain socket name> dev:<character device name> jdwp:<process pid> (remote only) adb jdwp - list PIDs of processes hosting a JDWP transport adb install [-l] [-r] [-s] <file> - push this package file to the device and i nstall it ('-l' means forward-lock the app) ('-r' means reinstall the app, keeping its data ) ('-s' means install on SD card instead of inter nal storage) adb uninstall [-k] <package> - remove this app package from the device ('-k' means keep the data and cache directories ) adb bugreport - return all information from the device that should be included in a bug report. adb help - show this help message adb version - show version num DATAOPTS: (no option) - don't touch the data partition -w - wipe the data partition -d - flash the data partition scripting: adb wait-for-device - block until device is online adb start-server - ensure that there is a server running adb kill-server - kill the server if it is running adb get-state - prints: offline | bootloader | device adb get-serialno - prints: <serial-number> adb status-window - continuously print device status for a specifie d device adb remount - remounts the /system partition on the device re ad-write adb reboot [bootloader|recovery] - reboots the device, optionally into the boo tloader or recovery program adb reboot-bootloader - reboots the device into the bootloader adb root - restarts the adbd daemon with root permissions adb usb - restarts the adbd daemon listening on USB adb tcpip <port> - restarts the adbd daemon listening on TCP on th e specified port networking: adb ppp <tty> [parameters] - Run PPP over USB. Note: you should not automatically start a PPP connection. <tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1 [parameters] - Eg. defaultroute debug dump local notty usepeerdns adb sync notes: adb sync [ <directory> ] <localdir> can be interpreted in several ways: - If <directory> is not specified, both /system and /data partitions will be u pdated. - If it is "system" or "data", only the corresponding partition is updated. environmental variables: ADB_TRACE - Print debug information. A comma separated list of the following values 1 or all, adb, sockets, packets, rwx, usb, sync , sysdeps, transport, jdwp ANDROID_SERIAL - The serial number to connect to. -s takes prior ity over this if given. ANDROID_LOG_TAGS - When used with the logcat option, only these de bug tags are printed. c:\androidSDK\tools> et j'ai rallumé mon portable (je suis sous leedroid) et je n'ai plus sense, je suis sous l'autre home... Que dois-je faire? PS: j'ai enlever la batterie mais rien non plus... EDIT: C'est bon!, j'avais oublié un bout de la ligne de commande LOL ^^ Par contre, est ce que c'est normal que j'ai perdu mon bureau d'origine? Enfin je veux dire par la que je dois le re-personnaliser Edited January 12, 2011 by hadescedric Quote Link to comment Share on other sites More sharing options...
Meelouw Posted January 13, 2011 Share Posted January 13, 2011 heu non pas normal fin moi de mémoire j'avais toujours tout pareil =x Quote Link to comment Share on other sites More sharing options...
steftolo Posted February 10, 2011 Share Posted February 10, 2011 Pareil qu' hadescedric il me manquait les 3 fichiers merci Meel. Et pour continuer mon home était aussi différent au reboot ???? Dailleurs je sais pas comment revenir à l'ancien ? Quote Link to comment Share on other sites More sharing options...
mancool Posted March 17, 2011 Share Posted March 17, 2011 Ca ne marche pas sur Reveolution HD 4.0. Le DHD ne finit pas sa phase de boot. C'est normal? Quote Link to comment Share on other sites More sharing options...
Meelouw Posted March 18, 2011 Share Posted March 18, 2011 oui, le rosie.apk ayant été modifié sur gingerbread, les modifs que l'on apporte ne sont plus compatible Quote Link to comment Share on other sites More sharing options...
Arestas Posted March 19, 2011 Share Posted March 19, 2011 j'ai surement du rater quelque chose car cette manip m'a carrément supprimé le launcher de HTC... heuresement que j'avais installé Launcher Plus, sinon je n'aurai eu d'autre choix que de faire un backup Quote Link to comment Share on other sites More sharing options...
Meelouw Posted March 19, 2011 Share Posted March 19, 2011 t'es sur quelle rom? tu es sur que ça c'est bien passer au niveau de l'install ? Quote Link to comment Share on other sites More sharing options...
Arestas Posted March 19, 2011 Share Posted March 19, 2011 (edited) je suis sur Android Revolution HD 3.2 l'étape 5, parfait l'étape 6 (puis : adb push [emplacement dossier tools]\Rosie_xxxxx.apk /system/app/Rosie.apk), l'invite de commande m'ouvre l'explorateur windows car il n'arrivait soit disant pas à lire le fichier "Rosie_contacts.apk" mon erreur vient peut être de "[emplacement dossier tools]"... ne sachant pas trop j'ai mis "c:\android-sdk-windows\tools ce qui me semble le plus logique -edit- je viens de refaire toutes les étapes, je viens de récupérer le launcher HTC d'origine (cool !), mais le bouton droit est inutilisable! en cliquant dessus, il ne se passe rien Edited March 19, 2011 by Arestas Quote Link to comment Share on other sites More sharing options...
Meelouw Posted March 19, 2011 Share Posted March 19, 2011 heu bah si c'le bon endroit tu as bien fait de mettre ça ^^ tu remplaces bien les "xxxxx" ? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.