Related
I just got Chis's GB rom and as usual it is lacking Google apps, I understand that I must flash them or use adb push, but every time i try adb push it never works!!
I copy the apk files and paste it under androidsdk/tools
then i go to command: cd\androidSDK\tools\adb push androidmarket.apk /system/app/.
then when it should show the file size and download time, it just says directory not found, I've watched tons of tuts, but it does the same every time. What am I doing WRONG!?!
and i know i spelled gingerbread wrong, sorry!
try
cd {path to your android sdk tools} (just drag it to your terminal) enter
androidSDK/tools/ adb root enter
androidSDK/tools/ adb push {path to your .apk, again just drag} /system/app/ enter
it should push then, where did you download the latest gapps from?
I picked them up from the cyanogen guys, u cant flash them all as u normally would because you will get a boot loop.
gullygossner said:
cd {path to your android sdk tools} (just drag it to your terminal) enter
androidSDK/tools/ adb root enter
androidSDK/tools/ adb push {path to your .apk, again just drag} /system/app/ enter
it should push then, where did you download the latest gapps from?
Click to expand...
Click to collapse
I tried this method, but for some reason adb is acting up because almost everything i do it says "permission denied"
You need to mount the file system as rw first.
thanks to both of you guys, i successfully pushed the market on the nexus, however, IT KEEPS CRASHING!!!! It truly never ends! any ideas for this one?
Trying to be charitable and cautious, I'm trying to back up my EFS folder before I go messing around and it is consistently failing. I'm using:
SGS Tools Vz 0.5.7
Busy Box Vz1.17.2
On my previous captivate this works just fine. Now I get
"could not create backup folder /sdcard/SGSToolbox/backup (date string)" and then the bluebox saying creating backup. This never goes away and to clear I have to reboot.
Any helpful hints?
I tried to download the latest and greatest SGS Tools but Google knows I have it installed and won't let me get the newest one. Haven't figure out how to get around that unless I just have to un-install my current one.
Rooted 2.2, KB2, running existz KB1 kernel.
Knowing there are no successful backups... just successful restores.
If you're willing to use your computer and can get the Android SDK and ADB going, just get into a command prompt in the ADB directory and type "adb pull /efs". That will back it up to your computer.
Or you could open a file explorer and copy the directory from there to your sd card
You could use an app called nitrality
Sent from my SGH-I897 using XDA App
Try to update your su binary, the simpliest way is use Root Explorer to backup whatever u want
Well just to be daring, I tried to install the ADB tools. Had to install the Java development software first. After I installed what I thought was the ADB suite, I can't seem to find the place to type in commands, dumb as that sounds. I may not have gotten the right package. Going to tinker with it though.
My SU is up to date.
I can see the folder with Super Manager so I guess I'll just copy with that. Interesting though I can't see anything in the /efs directory. Probably just something else I don't understand.
Still curious though as to why SGS Tools is failing... part of my nature.
Thanks to all that replied.
Make a note of where adb is installed (e.g. c:\users\person\Android-sdk-windows\platform-tools). Then hit the windows key and R, and type cmd. Once in the prompt, type CD (directory from before, no parentheses) and hit enter. From there, type your adb commands.
Ahhhh.... I get it. Was expecting something a bit more elegant. Gotta love DOS commands.
Well..there are a couple more elegant ways to do it.
Open up a new note in NotePad, just type:
Cmd
Exit
And save, but instead of a .txt file extension save it as a .bat, now drop that into your adb directoty, then just double click on that to open a prompt in that directory, so you don't have to do the cd command every time.
Or..the most elegant way is to add adb to your environmental variables so you can enter adb commands from anywhere
That's a good solution. I've got a set of files put into my C:\Users\(my username) folder called "adb", "adbr" (adb reboot), "adbrd" (adb reboot download), and "adbrr" (adb reboot recovery).
Each of these is a .bat file with a version of this text in it:
@ echo off
cd "C:\Users\(me)\Other\tools\android-sdk-windows\platform-tools"
adb reboot
That way, all I have to do is hit Win-R and type one of those file names and it does that command for me. Or, I can type cmd, then adb, and automatically be where adb is installed without cd'ing through a long file list.
My suggestion is Root Explorer. I was able to backup the EFS directory without problems also create a .tar file.
I used root explorer to do my backups, another option is the explorer inside the rom tollbox aplication its also very good
Now I have another adb question...
First off, now I'm just trying to learn and get better. I've built my bat files and I can get adb working. Thanks to those that helped with that. When I tried to pull the /efs folder it said there was no device recognized. I was in "mass storage" mode at the time.
Whenever I've seen people talk about using adb, I don't recall anything being said about if it should be in Download, debug or what. One of those assumed knowledge things.
So what do I have to do to the phone to let adb recognize it?
gnawing on the bone....
I'm also thinking of pulling a logcat or something when SGS tools fails... just to see. That's my next step.
Enable usb debugging in settings> applications> development
SGS Toolbox doesn't work with efs backups. Are there easier ways to do the backup?
Adb or root explorer.
I did both... just to say I did it and finally got adb working.
Had to factory reset kfhd7 and when I did, it booted up like an android phone. ... Now there's no browser and I can't get play to work. Usb debug is enabled but when I connect to the computer to try and push a browser, my computer doesn't recognize it. I have all the newest drivers installed and just about every program that I can think of (adb, sdk, jdk) What I don't have is a fastboot cable. Any ideas?
Missing my kindle
Edit* So I do have chrome installed but when I open it, I get an error message saying "critical functionality required to run chrome is missing; either your chrome installation is incomplete, or not compatible with this version of android"
Terminal emulator installed too but when I try to open it I get a "terminal emulator has stopped" error.
Super SU installed, works.
No es file explorer
edit#2
Ok, so I decided to open cmd just to see if I can recognize my device.... and it did! So how can I fix my kindle if adb is connecting?
Edit#3 adb devices shoes device but when running a command, it says "device offline"....
Edit#4 plugged usb into another port and reloaded drivers = adb connects, device is online. I have tested by pushing an app to the sdcard. My goal now is to be able to push es file explorer to /system/app/ .... or ..... /data/app/ ...... or where ever it will become active for use. (you know what I mean?) I don't know how to change the permissions via adb and push to system folder. I believe I have successfully pushed es file explorer to the /sdcard/ but I have no idea where to go next.
Now what..... ?
How to Install Packages using adb install
Krsmqn said:
Had to factory reset kfhd7 and when I did, it booted up like an android phone. ... Now there's no browser and I can't get play to work. Usb debug is enabled but when I connect to the computer to try and push a browser, my computer doesn't recognize it. I have all the newest drivers installed and just about every program that I can think of (adb, sdk, jdk) What I don't have is a fastboot cable. Any ideas?
Missing my kindle
Edit* So I do have chrome installed but when I open it, I get an error message saying "critical functionality required to run chrome is missing; either your chrome installation is incomplete, or not compatible with this version of android"
Terminal emulator installed too but when I try to open it I get a "terminal emulator has stopped" error.
Super SU installed, works.
No es file explorer
edit#2
Ok, so I decided to open cmd just to see if I can recognize my device.... and it did! So how can I fix my kindle if adb is connecting?
Edit#3 adb devices shoes device but when running a command, it says "device offline"....
Edit#4 plugged usb into another port and reloaded drivers = adb connects, device is online. I have tested by pushing an app to the sdcard. My goal now is to be able to push es file explorer to /system/app/ .... or ..... /data/app/ ...... or where ever it will become active for use. (you know what I mean?) I don't know how to change the permissions via adb and push to system folder. I believe I have successfully pushed es file explorer to the /sdcard/ but I have no idea where to go next.
Now what..... ?
Click to expand...
Click to collapse
Krsmqn,
Sorry for the delayed response, we have been real busy the last few days. You may use the
following command to install or reinstall software on the Kindle:
Code:
adb kill-server
adb start-server
adb devices
android update adb
If adb is working move on to install software:
Code:
adb install package-whatever.apk
You need to make sure the .apk software package in in the same directory as adb. If
you can not get the Kindle stable you may need a USB Factory Cable, you may order
one from XDA User SkOrPn just send him a PM with the subject Factory Cable Info Please,
include your ship to country and number of cabled needed. He will respond with a PayPal
Invoice. The cable is about $15 USD and is worth every penny since it allows quick
recovery of your Kindle.
prokennexusa,
I want to thank you for all your help. Unfortunately, my issue was kind of a rare issue. I had deleted some amazon apps that were system apps. I tried your solution time and time again to no avail. I was stumped until I remembered a thread I saw in development.
http://forum.xda-developers.com/showthread.php?t=1886189
I was able to download and unzip the 7.2.3 update version and simply install the apks that I was missing. Then, as far as google play went, I just went into System>Applications>Installed Applications>Appstore (Amazon)> Force stop, clear data & cache. Reinstalled Vendor.apk and then updated. Viola!
The USB notification came back, as well as all the other options in settings. Problem solved. Hope this helps future users.
Follow Up - Feedback
Krsmqn said:
prokennexusa,
I want to thank you for all your help. Unfortunately, my issue was kind of a rare issue. I had deleted some amazon apps that were system apps. I tried your solution time and time again to no avail. I was stumped until I remembered a thread I saw in development.
http://forum.xda-developers.com/showthread.php?t=1886189
I was able to download and unzip the 7.2.3 update version and simply install the apks that I was missing. Then, as far as google play went, I just went into System>Applications>Installed Applications>Appstore (Amazon)> Force stop, clear data & cache. Reinstalled Vendor.apk and then updated. Viola!
The USB notification came back, as well as all the other options in settings. Problem solved. Hope this helps future users.
Click to expand...
Click to collapse
Krsmqn,
Great post Krsmqn, I am glad to hear your problems are solved! We offer a fresh copy of the /system/app
folder here: https://dl.dropbox.com/u/54456659/app.zip
Anyone who is experiencing odd issues can download this folder and side load it back to the Kindle through
adb or ES File Explorer. Thank you again, I was getting a bit worried.
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?
There is a file size limit when you're using ADB, it's usually fine for sideloading apps, if you try to sideload a full rom though, for example the stock rom when you're trying to restore the device back to default, you might get an error saying it can't "read" the file.
Try using this fix on your adb.exe :
http://www.moddb.com/downloads/large-address-aware1
Point it to your adb.exe and run it and it should let you sideload a large file properly.
64bit adb might also work if that doesn't help:
https://www.asus.com/zentalk/thread-119788-1-1.html
djsubterrain said:
There is a file size limit when you're using ADB, it's usually fine for sideloading apps, if you try to sideload a full rom though, for example the stock rom when you're trying to restore the device back to default, you might get an error saying it can't "read" the file.
Try using this fix on your adb.exe :
http://www.moddb.com/downloads/large-address-aware1
Point it to your adb.exe and run it and it should let you sideload a large file properly.
64bit adb might also work if that doesn't help:
https://www.asus.com/zentalk/thread-119788-1-1.html
Click to expand...
Click to collapse
For me, I got the new adb/fastboot from the new android sdk