Related
SETTING UP ADB FOR WINDOWS USERS
The example shown in the video tutorial is running Windows 7. XP, Vista should run the same way.
1) Download the SDK program for your OS Here..
2) Download the latest Java Platform if you don’t have an updated version.
3) The SDK program will download in a .zip file. Extract that file somewhere easily accessible [like your desktop!]
4) You should now have a folder on your desktop with a name: android-sdk-windows
5) Drag that folder into the root of your HD…
The pathway should be something like: Computer > Local Disk ( C: ) > android-sdk-windows
6) make SURE to install the USB driver package in SDK... this way your device will be recognized when running adb commands later on...
Now that you have placed the SDK program there you can run ADB commands. But you need to run them Manually. Most people go into the tools folder and click adb and expect it to work its magic… you can stare all you want, but all it’s going to do it open a command prompt, run commands, and disappear. Now, don’t go “ZOMG I DON’T KNOW WHAT TO DO! IT WONT WORK!” …. Trust me, it will work..
6) Open a command prompt, go to windows start menu and click “search” or “run…” and in the box type: cmd and then press enter. This will execute the command prompt [terminal]
7) Now connect your Eris via USB. MAKE SURE YOU HAVE USB DEBUGGING ON!! If you don’t, go to settings < applications < development and check the box: usb debugging
8) Don’t mount your SD card yet.
9) Now you are almost ready to execute your first adb command. But first you must re-direct the path in command prompt to be your tools folder in SDK… this is what command should look like before:
C:\Users\YourUserName>
Now type in command: cd
But DON’T press enter… drag and drop the path from your SDK tools into that command line, so it should look like this:
C:\Users\YourUserName> cd C:\android-sdk-windows\tools
Now press enter. NOW your command prompt should say:
C:\android-sdk-windows\tools
Ok, last part… to test adb type in command: adb devices
Now it should return something like:
List of devices attached
HT9ANXXXXX Device
Ok so now you can execute Adb commands. Make sure you always have your command prompt pathway set to SDK tools or it WILL NOT WORK! You can now also execute adb commands directly to your device from it’s shell by typing: adb shell followed by your command.
For Visual people here is my short Youtube video explain it all again... and here is my screen shot to show you what it should look like, pay attention to my command prompt.
Another example: Custom boot animation for NON-ROOT USERS.
1) Find / create a boot animation that works with the Eris
2) name the Zip file bootanimation.zip
3) place .zip file in SDK tools folder
4) Follow above instructions to set path in CMD to tools folder and connect your device
5) execute this command:
adb push bootanimation.zip /data/local
Feel free to PM if you have any questions... I hope this helps
adb
Could someone sticky this please?... and I think themes and apps is a good place for it..unless you think it belongs in general..
Help
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
cornjo said:
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
Click to expand...
Click to collapse
EDIT: See OP at bottom for directions.
how do i install an apk file right to my phone using the "cmd"
jibbz said:
how do i install an apk file right to my phone using the "cmd"
Click to expand...
Click to collapse
adb install whatever.apk
n1ghtwish said:
adb install whatever.apk
Click to expand...
Click to collapse
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Hopefully its this simple
jibbz said:
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Click to expand...
Click to collapse
You probably don't have the .apk file in the same directory as sdk tool folder
try moving it there and see if that works.
ADB:-
Android Debug Bridge
Very useful program made itself by Google for Programmers and developers. Its based on command line and basically communicates with your Android to respond to certain commands. There is vast amount of knowledge about adb but its most useful commands limit to getting:-
Logcat:-
A real time log of what is happening in background of our devices. It is really useful for developers to see which component has malfunctioned and helps to narrow down their search for what failed and what needs to be fixed. Several times users are asked to give logcats of their devices which are giving errors. We will go in detail that how to get logcats in every and easiest way possible.
App Installation and Management:-
adb proves really handy if you want to install apks directly from your PC or want to batch install or delete them.
Shell Execution:-
You must have heard of Terminal Emulator. It is an app for android to execute shell commands(linux commands) which are basically present as applets in /system/bin, /system/sbin or /system/xbin(in our case) folders. A very imporant applet called busybox is installed there mainly used for execution of basic commands during root browsing or ROM installation. Many times updater script of ROMs use busybox commands to install it. Well, these commands can be initiated from your device too but they can be initiated from adb also making it easy for programmers.
Pushing and Pulling:-
Most used commands of adb. adb makes it a piece of cake for new device developers to get an ideo of structure and basic knowledge of devices by pulling command. We can pull out i.e copy any files or folders from our devices to our PC, even the root directories without rooting the devices. It help rooters and ROM chefs of new devices to get an idea and implement their mods on them. Pushing is also very useful command. It copies your files and folders from PC to your device. Very useful in pushing some /system apps and other things
Remounting and setting permissions
Basic commands:-
Of-course basic commands such as rebooting and rebooting in recovery mode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
PC(This is a windows guide, if asked I will add linux and mac guide later)
Java Runtime environment or Java Developing kit
Your Device Drivers
An Android Device
USB Debugging MUST be turned ON in the device for ADB to see it & Developer options is hidden in Android 4.2 and
above, Hitting Build number 10 times in
About Phone/Tablet reveals the menu (Thanks lilHermit for reminding me to add it)
Assuming you all these ready and working properly, we continue
If you are having trouble completing Pre-Requisites, there are several guides featuring them too
Start
1. First Download Android SDK. Roughly about 70 MB
2. There may be any compressed zip file or exe file
If zip file, then extract it to C:\android-sdk
If exe file then double click on it and install it in C:\ Drive(or any other drive you want)
3. Now to get adb and other tools, you need to download 'Platform Tools'
To download them, go to the android-sdk folder and double click on SDK Manager
It will ask you which package to download? However, it is your choice which package to Download, but here, we will only talk about platform
Tools. So, simply tick on Platform Tools and click on install. Once you have done it. Go to the platform-tools folder in the directory where you installed android-sdk. You will find several files there like adb, fastboot, aapt, etc
4. Now, you can backup the whole folder of android-sdk to any external storage that will make you not download package
again if you want to. You can have it placed in any computer and run it as it does not require registry to work
5. Now, you are just one step away from using adb. Next step is SKIPPING SETTING ENVIRONMENT VARIABLE (If you however want to set environment variables. Click on Show Content)
We can easily append the sdk platform-tools and tools folder to your systems environmental path variable directly from command line(cmd) by simply issuing one command and performing a system reboot:
Code:
[COLOR=Black]SETX PATH "%PATH%;[/COLOR][COLOR=Indigo]SDK_Install_Path[/COLOR][COLOR=Black]\platform-tools;[/COLOR][COLOR=Indigo]SDK_Install_Path[/COLOR][COLOR=Black]\android-sdk-windows\tools" -m[/COLOR]
Just replace the "SDK_Install_Path" in the above with the proper path of your SDK installation. Example: C:\android-sdk-windows
(Thanks to WugFresh for telling me :victory
Many guides on internet say that it is to be done for making it easy for users and if you have some basic knowledge of Command Prompt,
you will know that to execute any application with command prompt, you first need to change the directory to the one where application is
placed. And to skip changing the directories every time you open CMD, you need to put that application is environment variable. However, we will not do so.
6. Type cmd in the search bar. Copy cmd.exe from there. Go to the directory where you have installed android-sdk. Go to platform-tools folder. Paste cmd there, right click on it and in the settings, select Run as Administrator.
7. You are done. Now what to do in it?
ADB Commands
Type adb in command prompt. And several commands will show up on your screen. It is very difficult to analyse these all commands, so we will only talk about most used and important commands
Connect your device via USB cable
And open the CMD in platform-tools folder(Make a shortcut of it on desktop). And type the suitable commands
Code:
adb devices
Will show the list of devices attached to the PC andtheir serial numbers. If this shows up correctly on your PC, then it means that everything is fine for continuing.
Logcat
Code:
adb logcat
It will display the real time log of your device
Best time to do it is when your device boots up
Now, many users ask me how to copy the logcat and upload it from CMD
There are several methods:-
1. Right click on the Title Bar of Command Prompt. Hover the cursor over edit and select mark. Select all the things you want to copy and then click enter. All the things will be copied to clipboard.
2. This is the correct way of getting logcat saved.
Code:
adb logcat > logcat.txt
This command will create a logcat.txt document in platform-tools folder with the complete logcat of the device. Ofcourse you can type any name instead of logcat.txt
3. I prefer taking logcat this way as it neatly compiles logs of different time
Code:
adb logcat -v long > logcat.txt
This is a very nice way to get logcat.
Installing Apps
Code:
adb install %PATH OF APK%
This will install an app on your Android
For example, if my app AreeB.apk is in G:\ drive (G:\AreeB.apk)
Then I will type
Code:
adb install G:\AreeB.apk
Be sure your apk is not in a folder that has space in its name, else the command will break at space bar.
For eg:-
G:\Program Files\AreeB.apk
Note:
If you have spaces in path of apk, you can execute the command without breakage if you include the path inside quotes. (Thanks to etcman)
Eg:-
Code:
adb install "G:\Program Files\AreeB.apk"
Mounting
However, I never found any problem in tweaking with system files with adb, but some users said that they couldn't do it, so the problem was that their system partition was mounted as Read Only(R/O)
So, it is necessary now to tell how to mount system partition as Read Write(R/W)
Code:
adb remount
It is easiest way to do so, if it does not work then
There is another method that we will discuss in ADB Shell commands section
Pushing and Pulling
For pushing,
Type
Code:
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Suppose I have an app named SystemUI.apk(PATH = G:\SystemUI.apk) which I want to push in /system/app/ on my android(or in other words, install an app as a system app). Then I would type
Code:
adb push G:\SystemUI.apk /system/app/
More examples
G:\Dance.txt file to be pushed in Dance folder in sdcard
Code:
adb push G:\Dance.txt /sdcard/Dance/
OR
Code:
adb push G:\Dance.txt /mnt/sdcard/Dance/
G:\Movies folder to be transferred in SDCARD in Videos Folder
Code:
adb push G:\Movies /sdcard/Videos/
G:\system\framework\framework-res.apk to be pushed in /system/framework/
Code:
adb push G:\system\framework\framework-res.apk /system/framework/
For pulling,
push command replaces with pull and paths are swapped
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example,
All system apps are to be pulled to G:\ROM\system\app
Code:
adb pull /system/app G:\ROM\system\app\
build.prop to be extracted to desktop
Code:
adb pull /system/build.prop C:\Users\Areeb\Desktop\
However, if a folder is in platform-tools folder, you don't need to type full path
Suppose if I type
Code:
adb pull /system/ system
Then a folder named system will be created inside platform-tools with all the files in system in it
If a file is in platform-tools folder, then also no need to type full path
For example,
There is an app name DeskClock.apk in this folder then, to push it to /system/app, type
Code:
adb push DeskClock.apk /system/app/
ADB Shell Commands
This mode of adb allows you to execute linux shell commands from your PC
These commands can aldo be executed through the mobile using Terminal Emulator
To initiate shell mode
Type
Code:
adb shell
You will get an prompt like this
sh-3.2#
Now you are in shell mode
adb commands won't work here and a new set of commands will work here. But we will only go in a little detail here.
Assuming you are in adb shell mode, I will only type commands that will work on shell. Note:- These commands won't work if you type them alone on cmd. But, these command will directly work on your mobile's Terminal Emulator
As these commands can also work on mobile, I am going to tell you a way of taking logcat on mobile
Type
Code:
logcat
You will see log of your device
To save this
Type
Code:
logcat > /sdcard/log.txt
A file named log.txt will be generated in sdcard
Uninstalling Applications
Code:
cd /data/app
This will change the directory to /data/app
Code:
ls
This will show the list of files in there
Suppose, there is an app named com.opera.browser (Opera Mobile) you want to uninstall it
Type
Code:
rm -r com.opera.browser
This will uninstall the app
Mounting Command:-
Code:
mount -o rw,remount /dev/block/mtdblock3 /system
Miscellanous commands:-
su: Initiates root request
du: Shows file foldrs and size
date: Shows todays date
ls: Shows list of directory
cd: Changes working directory
rm: Removes the file
logcat: Displays logcat
mount: Mounts the partition
busybox: Busybox Applets
Credits
Google: For Android and several searchings
Samsung: For Galaxy Ace s5830I
paxChristos for amazing logcat guide
Broadcom: For their Open Sourceness
XDA Forums : For the precious knowledge
Reserved
Reserved Once More
Last One
Reserve the guide
install full rom
how to install a full rom from adb?
Pretty sure it's impossible. Sorry.
Sent from my E15i using XDA Premium App
Perfect Guide to use ADB Commands..
It is very clear and perfect guide to use ADB commands.. I tested this all and works fine..
You can use apks to do logcats from the phone too, I use catlog.
About Broadcom being open sourced made me laugh hahaha.
open source broadcomm, i see what you did there .
Updated OP
Hey, I have downloaded adb a week ago. I did everything like your tutorial and more but adb doesn't see my device. I already have USB Debugging on and have the USB Drivers, but it doesn't work. This is what I get (Screenshot)
Android-fany said:
Hey, I have downloaded adb a week ago. I did everything like your tutorial and more but adb doesn't see my device. I already have USB Debugging on and have the USB Drivers, but it doesn't work. This is what I get (Screenshot)
Click to expand...
Click to collapse
Probably because of bad drivers
Can you use any other software with your mob
Because when I had this problem, reinstalling drivers fixed it.
iamareebjamal said:
Probably because of bad drivers
Can you use any other software with your mob
Because when I had this problem, reinstalling drivers fixed it.
Click to expand...
Click to collapse
I already reinstalled it like 5 times. Still doesn't work.
Android-fany said:
I already reinstalled it like 5 times. Still doesn't work.
Click to expand...
Click to collapse
Which Windows?
Which ROM?
iamareebjamal said:
Which Windows?
Which ROM?
Click to expand...
Click to collapse
Windows Vista
Stock Rom + Interactive Kernel (If the kernel is important too)
Android-fany said:
Windows Vista
Stock Rom + Interactive Kernel (If the kernel is important too)
Click to expand...
Click to collapse
Ah Vista
That old Nemesis
Frankly telling you bro, Vista sucks big time
I unistalled it as soon as I found out that Android kitchen won't work on it
Sorry bro
I don't know much about Vista
Install 7 or 8
AW: [GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies
iamareebjamal said:
Ah Vista
That old Nemesis
Frankly telling you bro, Vista sucks big time
I unistalled it as soon as I found out that Android kitchen won't work on it
Sorry bro
I don't know much about Vista
Install 7 or 8
Click to expand...
Click to collapse
I can't install Windows 7/8 because it is not my computer.
But Android Kitchen and the other tools works. Just not adb.
Tapatalked by s5830i
Android-fany said:
I can't install Windows 7/8 because it is not my computer.
But Android Kitchen and the other tools works. Just not adb.
Tapatalked by s5830i
Click to expand...
Click to collapse
Very strange
Download My Phone Explorer and check if its working!!
Its just 2mb-6mb
Hey everyone! I put together some information on how to do a few things on your new Ouya! This info is by no means my own original contributions, but rather just a compilation of several different sources that I discovered through my quest to explore my Ouya. All credit goes to the original authors/brave experimenters.
SDK SETUP:
1. Install the Android SDK
2. Open SDK Manager and install the following packages:
- Tools: Including both Android SDK and Android SDK
- Android 4.1 (API 16): SDK Platform
- Android 4.0 (API 14): SDK Platform
- Extras: Android Support Library, Google USB Driver
3. Navigate to /android-sdk/extras/google/usb_driver
4. Open android_winusb.inf in an editor (I use Notepad++)
5. Add the following lines beneath [Google.NTx86]:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
6. Connect your Ouya via micro USB to your computer and turn it on (it needs to be on for adb to work)
7. Open a command window in /android-sdk/platform-tools and run the following commands:
Code:
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
adb devices
8. After 'adb devices' you should see a number, which signifies your connected console
9. You are now ready to use adb to sideload apps
=============================================================================================================
SIDELOADING APPS:
1. Place the desired .apk file to be installed within /android-sdk/platform-tools
2. Connect the Ouya and open a command window in /android-sdk/platform-tools and run the following command:
Code:
adb install [name.of.apk.file.here]
3. Wait for it to complete the installation
4. On the Ouya, navigate to 'Make' and 'Builds' and your app will be there
=============================================================================================================
ADDITIONAL STUFF BELOW
=============================================================================================================
HOW TO SET UP WIRELESS ADB (will allow you to wireless use adb command, without connecting directly to your computer)
1. Connect OUYA console via mini-usb (or using wireless adb) and run the following commands:
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
chmod 666 /system/build.prop
2. Open another terminal (so we can do things locally) and run the following command:
Code:
adb pull /system/build.prop
3. Open build.prop in a text editor, add this line:
Code:
service.adb.tcp.port=5555
4. Return to the second command window and run the following command:
Code:
adb push build.prop /system
5. Now go back to your shell for the OUYA and run the following commands:
Code:
chmod 644 /system/build.prop
(seriously! the console won't boot if you forget this)
Code:
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
6. Disconnect your OUYA, put it where you want it, reboot it.
7. To wirelessly connect to your OUYA, use the following command:
Code:
adb connect 192.168.xxx.xxx
(your OUYA's ip address)
=============================================================================================================
HOW TO INSTALL BUSYBOX, SUPERUSER, AND SU BINARIES
1. Make sure you have ADB set up and working (wired or wireless).
2. Download and unzip the needed files here.
3. Place unzipped files in /android-sdk/platform-tools
4. Run the following commands to put su in the proper place:
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
exit
exit
adb push su /sdcard/su
adb shell
su
cat /sdcard/su > /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chmod 6755 /system/xbin/su
exit
exit
5. Install SuperUser and BusyBox:
Code:
adb install com.koushikdutta.superuser.apk
adb install stericson.busybox.apk
6. Run SuperUser on the Ouya (from Make > Software) and confirm the update (not in recovery).
=============================================================================================================
Again, this isn't my original content, only slightly edited (since I am OCD about writing).
My only intention is to share this knowledge with other users like me, who don't know much about this sort of thing (yet).
If i stepped on any toes, or did something wrong, I apologize. Let me know if you have any questions or concerns.
Thank you to the following people for their work in contributing to this guide:
WinDroidGuy
elmerohueso
The driver section doesn't seem to work on Windows 8 Pro 64-bit. I don't think the Google driver has been updated for Win8 yet.
You're probably right. I'm on Windows 7. I'll see if I can jump on a buddy's computer to play around with it.
Upon a quick Google search, I found this: http://forum.xda-developers.com/showthread.php?t=1161769
Perhaps give this a try? Please let me know how it goes.
I also tried Koush/ClockwordMod's universal ADB driver (adding in the Ouya section to 32/64) but same results about a bad hash in the driver file.
Well it was worth a try. I'll keep my ears open for a Windows 8 solution.
Did you try setting up adb over wireless by any chance? I don't know much about this stuff, but perhaps that's worth a try as well?
cosine83 said:
The driver section doesn't seem to work on Windows 8 Pro 64-bit. I don't think the Google driver has been updated for Win8 yet.
Click to expand...
Click to collapse
My Ouya was listed twice in Device manager and one of them was a driver problem. I manually selected my Samsung adb drivers from the list and it works fine. the easiest way yo get those is to install KIES. This was with 64 bit Windows 7.
TIP: The micro usb port is extra deep and my samsung cables don't work, fortunately I have a Kodak one that does.
It motivated to set up wireless adb.
Not getting very far, first I downloaded the SDK, which will not run on my system, might be the AV/FW or something else, but it attempts to find java (which is in the path), and then it does nothing. So I try to go the ClockWorkMod way using the Universal driver (as I saw that should work), that is better as I at least have drivers and it finds my device, but it also will not install throwing a message: "hash for the file is not present in the specified catalog. The file is likely the corrupt or the victim of tampering." Well duh, I modified the inf to get it to find the hardware for the OYUA. I'd just use Google's if I could get a copy without installing the SDK since that is obviously not going to working on this system. Any suggestions, so far while adb works fine with the G3 on this system it appears impossible to setup for the OUYA.
Please note: in C:\Java\jdk1.7u21 is the JDK in c:\java\jre is the JRE. So they are both present and up to date. If I open a command prompt and type java -version it is located and works fine, so no understanding of what "SDK Manager.exe" is doing.
Also, yes I followed the thread as best I could, first copying java into c:\android makes no sense, but I tried it (did nothing), second the adb driver does not require any extraction, where is the usb driver, it must be in a zip somewhere in the SDK for it to be installable, so can I just manually extract it?
Thanks,
ERIC
egandt said:
Not getting very far, first I downloaded the SDK, which will not run on my system, might be the AV/FW or something else, but it attempts to find java (which is in the path), and then it does nothing. So I try to go the ClockWorkMod way using the Universal driver (as I saw that should work), that is better as I at least have drivers and it finds my device, but it also will not install throwing a message: "hash for the file is not present in the specified catalog. The file is likely the corrupt or the victim of tampering." Well duh, I modified the inf to get it to find the hardware for the OYUA. I'd just use Google's if I could get a copy without installing the SDK since that is obviously not going to working on this system. Any suggestions, so far while adb works fine with the G3 on this system it appears impossible to setup for the OUYA.
Please note: in C:\Java\jdk1.7u21 is the JDK in c:\java\jre is the JRE. So they are both present and up to date. If I open a command prompt and type java -version it is located and works fine, so no understanding of what "SDK Manager.exe" is doing.
Also, yes I followed the thread as best I could, first copying java into c:\android makes no sense, but I tried it (did nothing), second the adb driver does not require any extraction, where is the usb driver, it must be in a zip somewhere in the SDK for it to be installable, so can I just manually extract it?
Thanks,
ERIC
Click to expand...
Click to collapse
By G3 do you mean Galaxy S3? If so then hopefully you already have Kies installed. When I connected my OUYA and started all of this, it did not install properly. It showed up twice in device manager, it was installed as a portable device, but was also listed as "other device" and not installed. After a lot of searching,I saw that people had been able to get out working by manually selecting the Samsung adb drivers that are included with Kies. It worked for me. You need to manually select the drivers (have disk) and install OUYA as a MTP device.
Regarding the SDK I know nothing. It installed just fine on Windows 7 for me.
Good luck
Sent from my SCH-I535 using Tapatalk 2
I was able to get ADB to work on Windows 7 64bit and Windows 8 64 bit by installing Samsung KIES and forcing it to use that driver.
eatmybiglazer said:
I was able to get ADB to work on Windows 7 64bit and Windows 8 64 bit by installing Samsung KIES and forcing it to use that driver.
Click to expand...
Click to collapse
Try this driver, got it to work, by selecting i from the list and forcing it
ERIC
Sideloading it relatively trivial for this. It is on by default (and can be toggled the usual way, you can access setting at manage->system->advanced-> security).
I used Real APK Leecher to snag ES File Explorer's APK, threw it on a web server, then downloaded it using OUYA's browser (make->software->browser). Installed it from settings (manage->system->advanced->storage->downloads)
The app then shows up under make->software
I have not tried a pen drive yet, but you could probably throw apks on a drive and use the USB port and install in a similar fashion.
I'm trying to do step 7. I input C:\Android\sdk\platform-tools into comand promt but get not regognizable message. What am I doing wrong?
You need to open the command prompt from wherever within platform-tools, or navigate to that folder from your command prompt. You can't run the adb command (which is located in platform-tools) unless your in that directory.
thanks. hopefully i'll get my OUYA soon. only 1 state away.
I dont get a number after adb devices. I editited the google usb file. Im using the 64 version of android sdk is that ok?
@tcollum: Perhaps you should add this to the OP, I tested and it worked. You can add that ;Ouya to the amd64 section of the USB driver, too
FrostyWolf said:
Sideloading it relatively trivial for this. It is on by default (and can be toggled the usual way, you can access setting at manage->system->advanced-> security).
I used Real APK Leecher to snag ES File Explorer's APK, threw it on a web server, then downloaded it using OUYA's browser (make->software->browser). Installed it from settings (manage->system->advanced->storage->downloads)
The app then shows up under make->software
I have not tried a pen drive yet, but you could probably throw apks on a drive and use the USB port and install in a similar fashion.
Click to expand...
Click to collapse
I just find it easier to ADB over Network and install from my laptop.
Sent from my Nexus 10 using XDA Premium HD app
TadeoNYC said:
My Ouya was listed twice in Device manager and one of them was a driver problem. I manually selected my Samsung adb drivers from the list and it works fine. the easiest way yo get those is to install KIES. This was with 64 bit Windows 7.
TIP: The micro usb port is extra deep and my samsung cables don't work, fortunately I have a Kodak one that does.
It motivated to set up wireless adb.
Click to expand...
Click to collapse
This was a great post...I did what you suggested and selected the latest Samsung ADB Interface driver in the windows list (think it was 23/1//2013) and voila. Thanks!
uncynd said:
This was a great post...I did what you suggested and selected the latest Samsung ADB Interface driver in the windows list (think it was 23/1//2013) and voila. Thanks!
Click to expand...
Click to collapse
You can also do the original USB driver edit in the OP and add it under the amd64 section in the inf file. Its how I did it.
dibblebill said:
You can also do the original USB driver edit in the OP and add it under the amd64 section in the inf file. Its how I did it.
Click to expand...
Click to collapse
Ahh, did not see your post that would have been a lot faster, good advice and maybe should be added to OP?
0. Prerequirements:
- a PC with adb installed (I prefer linux) follow these tutorial https://www.xda-developers.com/install-adb-windows-macos-linux/
- you must to enable developer options in your smartphone and activate usb debugging (`About emulated device` click ten times on build number and then go to Settings-Accessibility-Developer options and activate usb debugging).
1. Install ADB Change Language on your phone https://play.google.com/store/apps/details?id=net.sanapeli.adbchangelanguage&hl=ro
2. Connect your Phone to PC via usb and check adb with
Code:
adb devices
3. Open a terminal or console and input
Code:
adb shell pm grant net.sanapeli.adbchangelanguage android.permission.CHANGE_CONFIGURATION
command,
4. Open ADB Change Language app on your phone, search your language code (xx-XX or xx ex. pt or pt-rBR etc), press on it and per system/all apps language is changed in that language.
5. It can use from PC console adb commands>
Code:
adb shell am start -n net.sanapeli.adbchangelanguage/.AdbChangeLanguage -e language pt-rBR
6. PS. Not all system settings/apps are fully translated.
Good luck!
Greaaaaaatt!! Working for me on Meizu M6T (Chineese).. Many thanks bro!
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
rldev said:
Remove Sprint from LG G8
We are removing the following files. See bottom for some notes. If you are using the floating bar, disable it or adb may not work.
Caller Id
Carrier device manager
Carrier Hub
MCM Client
Mobile Installer
Sprint Mobile Framework Support
Sprint Service
Software Update
pm uninstall -k --user 0 com.lookout
pm uninstall -k --user 0 com.coremobility.app.vnotes
pm uninstall -k --user 0 com.sprint.w.installer
pm uninstall -k --user 0 com.sprint.ms.cdm
pm uninstall -k --user 0 com.sprint.zone
pm uninstall -k --user 0 com.sprint.ecid
pm uninstall -k --user 0 com.sprint.extension
pm uninstall -k --user 0 com.sprint.care
pm uninstall -k --user 0 com.sprint.ce.updater
pm uninstall -k --user 0 com.lge.sprintnativewfc.smf
pm uninstall -k --user 0 com.sprint.ms.smf.services
pm uninstall -k --user 0 com.lge.sprintserver
pm uninstall -k --user 0 com.lge.lgdmsclientspr
NOTE: The last line will remove the Sprint Activation at boot. There are 3 of these that come up when you search in the app.
I don't know how to get rid of the Sprint bootup. The last one I purchased had it removed, so it is possible. Someone let me know.
Click to expand...
Click to collapse
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
brandontw said:
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
Click to expand...
Click to collapse
Will the device be able to receive software updates after this?
kimush said:
Will the device be able to receive software updates after this?
Click to expand...
Click to collapse
Yep. Just got one today actually.
Hi. thanks for the info and the procedure. all went fine on my LG V50 thinq from Sprint (LM-V450PM). some interesting data is that I could get rid of the Sprint bootup performing a hard reset with the key convination before turning the phone on. I could not say if the device will be able to receive software updates after all these procedures because I already had it updated before to android 10. now the phone seems to be running a clean official rom. hope to hear about some root news for this device.
i am stumped at #9. was the next step" CD<path address>?" because that did not work.
then i tried to skip it to enter abd devices in cmd and that didn't work either.
could someone please answer if it's not too much trouble?
brandontw said:
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
Click to expand...
Click to collapse
Hi, mate!
The Sprint boot up animation is still present after following the procedure. by the way, 2 commands (somewhere in the middle of the list) read "failure (not installed for 0). what does this mean?
i truly appreciate your work, mate.
brandontw said:
Yep. Just got one today actually.
Click to expand...
Click to collapse
Hi mate. So my LG G8X can still receive update, right? Although the LG software update is already gone from the update center section?
biscuitcrust said:
i am stumped at #9. was the next step" CD<path address>?" because that did not work.
then i tried to skip it to enter abd devices in cmd and that didn't work either.
could someone please answer if it's not too much trouble?
Click to expand...
Click to collapse
replace <path address> with (if you simply downloaded it and unzipped it) example: Downloads\platform-tools_r30.0.5-windows\platform-tools so it'll be "cd Downloads\platform-tools_r30.0.5-windows\platform-tools"
Do you think this process will allow WiFi calling to work on T-Mobile?
It worked perfectly but i would like to install stock rom for this device without bloatware and that one that does not have to do these steps every time I reset the phone. Can somebody help me to find that rom 'cause i found a lot of regions and i don't know wich one is the one i need.
when doing this process is there a risk of brick? It is the first time that I will try
Lennylegendary said:
when doing this process is there a risk of brick? It is the first time that I will try
Click to expand...
Click to collapse
modding anything theres always a risk but if it bootloops you might just have to go to recovery and do a hard rest
brandontw said:
I just picked up a "renewed" unlocked G8 thinq (Model LM-G820UM) on Amazon for a pretty good price. I'm using it on ATT prepaid, but its got a Sprint logo on startup. It also complained about network activation at every startup, but otherwise worked fine.
Combined with the fine work of rldev, here's a guide to remove the bloatware and ditch that activation message. It will still say sprint on bootup/shutdown, but other than that, no way I can tell its a sprint phone.
Just wanted to shout out and say thanks! Worked perfectly.
I'll add some info for noobs just to contribute and make it easier for people in the future..
To get ADB working (windows):
Get and install LG USB drivers from here: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Get the ADB binary from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it somewhere on your computer you can keep track of.
On your phone, go to Settings and tap on About Phone. Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it.
Plug your phone into the computer and change it from “charge only” mode to “file transfer (MTP)” mode.
On your computer, open a CMD prompt (windows key, type cmd, hit enter)
Change directory to the folder you unzipped with the adb binary (CD <folder path>)
enter the following command: adb devices
You will see that the system is starting the ADB daemon. If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
Now if you re-run the adb devices command, the terminal will print the serial number of your device. If so, then you’re ready to move on.
Enter the following command: adb shell
Now run each of the commands from the post above
Sources
Click to expand...
Click to collapse
Hello can you assist me
Disabling Sprint Activation for non-Sprint Networks (on Mac)
1) Enable Developer options on G8X ThinQ.
Go to Settings > About Phone > Software info and then tap Build number a few times to enable Developer Mode. Accept warning. In the now available "Developer Options" settings, enable USB debugging.
2) Connect the phone to Mac through USB. No additional drivers need to be installed.
2) Following these instructions to install adb and issue commands on Mac
Install and Use ADB and Fastboot on Mac [How to]
If you want to use ADB commands in Mac terminal, you'll have to download and install ADB and Fastboot on Mac or you'll get 'not found' error.
technastic.com
I placed the unzipped platform tools in the Application folder.
3) list potentially unneeded Sprint packages to uninstall.
./adb shell pm list packages | grep sprint
For all packages:
./adb shell pm list packages
3) Check for the existence of com.lge.lgdmsclientspr, the service which initiates the Sprint activation at boot.
./adb shell pm list packages -f com.lge.lgdmsclientspr
or without -f
./adb shell pm list packages com.lge.lgdmsclientspr
4) Uninstall/Disable com.lge.lgdmsclientspr package
Uninstall
./adb shell pm uninstall -k --user 0 com.lge.lgdmsclientspr
Reinstall later
./adb shell pm install-existing com.lge.lgdmsclientspr
Alternatively,
Disable
./adb shell pm disable-user --user 0 com.lge.lgdmsclientspr
Enable
./adb shell pm enable com.lge.lgdmsclientspr
5) Confirm packages enabled or disabled
List all enabled apps filtered by "sprint":
./adb shell pm list packages -e | grep sprint
List all disabled apps
./adb shell pm list packages -d
6) Reboot the device by ADB command
./adb reboot
In Windows, the adb shell command is started as follows:
Windows Command Prompt: adb shell pm list packages -d
Windows PowerShell: .\adb
question 1: is it recommended to remove the (active european) sim card before injecting those commands or does it not affect the system change anyway?
question 2: although my refurbed G8 from California works with a german sim card, it seems the phone itself still has a country lock, due to not accepting european LG Smartworld login. It only offers login possibility via US, Canadian and Mexican LG accounts. Will this restriction be overridden after the here mentioned debrand codes initiation?