Related
the USB driver for windows is available at:
http://dl.google.com/android/android_usb_windows.zip
It seems to work... I will update this thread with what I find.
Thanks for posting the driver!
I've tried a few things with adb, and so far I can't get an install to work over usb. I tried the following command.
C:\...\android-sdk-windows-1.0_r1\tools>adb install OperaMini.apk
579 KB/s (0 bytes in 278155.000s)
pkg: /data/local/tmp/OperaMini.apk
Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED]
Click to expand...
Click to collapse
http://www.android-freeware.org/tutorial/how-to-install-apk-files-on-android-device-emulator Had some basic info about the emulator, not sure what would be different for the G1.
The "adb shell" option allows you to access a shell on the phone over USB, which is really great but it appears you don't have root privileges. Any ideas on how to obtain root priveleges? Also, is there a command to install from the android shell? When i cd to /sbin i get access denied. I'm trying to figure out some kind of way to invoke an install either from the device or over USB.
I have the same problem... working on it now...
I don't know about the USB installs, but it seems to be something with the APK as well. I also have the OperaMini.apk and it does nothing. I downloaded the iTunes remote via the G1 and it installed just fine without getting a PC involved.
It looks like you have to put the phone into a "Debug on USB" mode to use ADB. It's working for me now.
http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Thank you dagentooboy!
Can someone explain this for this not so savvy person?
chrimage said:
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Click to expand...
Click to collapse
I think that is caused by an issue with the the AndroidManifest.xml file within the APK having to do with going from "beta" to "live" Android. The same reason most of the apps were pulled from the store. I don't believe it takes a major change to make it compatible, but it's fully compiled so, unless you have a decompiler, I think we may be out of luck on that particular one. I have installed other apk's successfully using the same method.
Mikey1022 said:
Can someone explain this for this not so savvy person?
Click to expand...
Click to collapse
ADB is the Android Debug Bridge that comes as a part of the SKD. I don't think it was really intended as an end user tool. It has to be called from a command line. I know people have built basic UI's for it for file manipulation when the SDK was the only thing out there. If a better solution isn't found shortly I think we'll see one be made, or else I'll make one myself. In the end it seem to make a big difference of what you're trying to install some things work and some don't, there are some differences between the beta SDK and the G1.
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Valicore said:
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Click to expand...
Click to collapse
the su command and sudo su returns "no permission" or "access denied" or something like that. That is also the same message i get when typing arbitrary commands that shouldn't be anything. And like i said earlier, /sbin along with many other directories are inaccessible. Hopefully someone will find a way to access the root account on the G1 pretty soon.
yes... must... have.... root...
Also a normal shell would be helpful esp when looking thru /proc/ for information.
Please help (ahhhhhh)
Okay So I am pulling my hair out here... I just booted android on my Vogue for the first time, everything works great, voice calls and sms.. But I can get a Inet connection but I am using Cricket not sprint so I added the username and password lines in default.txt and can connect, but Cricket uses a proxy for all http connections. So I found this article http://fggarcia.blogspot.com/2007/11/setting-up-proxy-for-android-emulator.html , which basicly says to use the adp app that comes in the sdk to add some lines to make the proxy. NOW, here is my problem... I can not for the life of me get my come (in windows or linux) to see my vogue while its in android..
In windows it does not appear ANYWHERE in the device manager... So I cannot install the driver, and in Linux it doesnt make a blip in dmesg..... USB debugging is marked and so is use adb....
It does charge when plugged in to the comp running linux.....
Can anyone please help me... And thanks to DZO and everyone else for there hard work on this project..
check too make sure your Android isnt listed under usb mass storage devices in device manager.
Ya USB isn't possible on Vogue yet, I just extracted data.img and added the proxy that way, but it still doesn't work. My Problem is I need all connection to use the proxy wap.mycricket.com:8080. I am not trying to be cheap or anything like the tzones thing for tmobile. Its just the only data plan cricket have use this proxy. So any Ideas would be greatly appreciated.
my computer already had a driver installed and when i try to update it with this one it says there is no better match for my hardware
anyone got a solution for this
Im really sorry to bump this old thread up but i need the r3 drivers and i dont know why they are nowhere to be found on the official page... i think its a region lock thing...
Hi,
i am trying to upgrade cupcake to donut (google navigation doesn't work on 1.5). The adb doesn't find my handset. I downloaded and installed this sdk. Since i have cupcake, should I use sdk 1.5?
Thanks for any help!
Frank
Do you have installed the adb usb drivers? It´s needed to work´s in adb.
connecting my handset to the computer brings up the new hardware wizzard. I locate the C:\androidsdk folder. After a while a message pops up that ADB cannot be installed.
The correct folder is: C:\your-current-sdk-dir\usb_driver\x86
so the usb_driver\x86 folder should come along with the sdk package (android-sdk_r3-windows.zip), but it's not.
frank&frank said:
so the usb_driver\x86 folder should come along with the sdk package (android-sdk_r3-windows.zip), but it's not.
Click to expand...
Click to collapse
How about the STKSETUP.EXE ?!?!
Also this belongs into general. -.-""
*A lil pissed off*
sdk-full
frank&frank said:
so the usb_driver\x86 folder should come along with the sdk package (android-sdk_r3-windows.zip), but it's not.
Click to expand...
Click to collapse
Try download this adb version. Is full packet (included usb drivers).
http://developer.android.com/sdk/1.6_r1/index.html
problem solved. Just installed the htc sync. Works fine now.
Thanks a lot for helping!
fabioccoelho said:
Try download this adb version. Is full packet (included usb drivers).
http://developer.android.com/sdk/1.6_r1/index.html
Click to expand...
Click to collapse
Doesnt work, the 1.6_r1 link redirects you to this one: android-sdk_r3-windows.zip
1. DOWNLOAD USB DRIVERS
Motorola ADB Driver 32bit
Motorola ADB Driver 64bit
2. INSTALL THE SDK
-Download latest SDK http://developer.android.com/sdk/index.html
-Extract Archive to C:\SDK\ (or C:\Android, or whatever you want)
3. Enable debugging on your phone (thanks naplesbill)
-Goto Settings > Applications > Development > and Check the USB debugging option
4. Optional, but recommended
-Setup Enviroment Variables:
On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ directory to the path AFTER A SEMICOLON (;C:\SDK\tools\) .-Setup Droid Explorer:
Goto Droid Explorer Downloads and snatch the latest version, then install. (mine showed an error during install i believe due to the lack of HTC drivers. If you installed motorola's drivers it should still be in your start menu and work fine)
If for some reason you can't figure it out, install the drivers then try this installation guide: ADB For Dummies Guide
ADB APK Install instructions
j101399j said:
1. Create a folder called adb on your C drive
2. Extract all files to your adb folder
3. Copy the cmd.exe file (copy the file don't make a shortcut to it or move it) from your "C:\Windows\System32" folder to the adb folder
4. Install the downloaded USB driver
4. Once you have the driver installed, on your phone enable debugging mode (Menu --> Settings --> Applications --> Development --> Check USB Debugging)
5. Copy the apk files you want installed to your "C:\adb\tools" folder. The adb.exe and cmd.exe should be in that tools folder.
5. Open the cmd.exe file
6.Type the following command:
Code:
Code:
adb install [B]application.apk[/B]
Where application.apk is the name of the apk to install
Your app should now be installed
Please note that you cannot install apps used on 1.6, 2.x builds
Click to expand...
Click to collapse
BACKFLIP SYSTEM DUMP http://forum.xda-developers.com/showthread.php?t=642684
BACKFLIP SOURCE CODE http://forum.xda-developers.com/showthread.php?t=645369
Don't you still need root?
I fail to see how this can help without rooting the Backflop unless Droid Explorer has some way of overriding that setting.
Charrion said:
I fail to see how this can help without rooting the Backflop unless Droid Explorer has some way of overriding that setting.
Click to expand...
Click to collapse
It doesn't help deleting the protected apps, but it makes it easier to install apks. This is especially helpful since the backflip doesn't allow anything to be installed through phones interface except through the market.
Ok, it works, but only if you turn on the Applications, Development, USB Debugging in the settings menus.
Well, that's kind of a given as ADB won't work without USB Debugging on.
Charrion said:
I fail to see how this can help without rooting the Backflop unless Droid Explorer has some way of overriding that setting.
Click to expand...
Click to collapse
We meet again Charrion! This is like the third time today I've run into you.
Don't need to have root to install APKs via ADB. Even us poor Milestone owners can do it via 'ADB install <app.apk>.'
I am just pointing that out for those that aren't familiar with that. I imagine there will be users who wouldn't normally bother with this, doing it just to be able to install non-market apk files.
naplesbill said:
I am just pointing that out for those that aren't familiar with that. I imagine there will be users who wouldn't normally bother with this, doing it just to be able to install non-market apk files.
Click to expand...
Click to collapse
Ah, fair enough. Sorry about that.
Unimaginative said:
Well, that's kind of a given as ADB won't work without USB Debugging on.
We meet again Charrion! This is like the third time today I've run into you.
Don't need to have root to install APKs via ADB. Even us poor Milestone owners can do it via 'ADB install <app.apk>.'
Click to expand...
Click to collapse
I'm on a crusade
OK, so you can install apks through adb even without unknown sources being enabled.
Has anyone determined if the option to enter debug mode is still available on the backflop? I wouldn't be at all surprised if they disabled that option also.
I'm also curious whether the backflop has a signed mbm like the Milestone to prevent loading custom roms.
Charrion said:
I'm on a crusade
OK, so you can install apks through adb even without unknown sources being enabled.
Has anyone determined if the option to enter debug mode is still available on the backflop? I wouldn't be at all surprised if they disabled that option also.
I'm also curious whether the backflop has a signed mbm like the Milestone to prevent loading custom roms.
Click to expand...
Click to collapse
The use debug mode is indeed available, I just forgot to mention turning it on.
From what I understand, this phone will be rooted like the cliq.... unfortunately for that to happen certain key files need to be leaked.
@moosefist;
Thank you so much for posting this.
I am now able to install non-Market apps
moosefist said:
The use debug mode is indeed available, I just forgot to mention turning it on.
From what I understand, this phone will be rooted like the cliq.... unfortunately for that to happen certain key files need to be leaked.
Click to expand...
Click to collapse
So; I'm new to the whole Android stuff; but what files need to be "leaked" in order to do this?
Squeaky369 said:
So; I'm new to the whole Android stuff; but what files need to be "leaked" in order to do this?
Click to expand...
Click to collapse
According to Skrilax_CZ a modmymoto moderator:
If we are up to root it; we need the shx/sbf flashfile, which must be leaked. Then I can see if the CLIQ RAMDLD exploit is present in here or whether has it been fixed as on the new CLIQ firmwares.
Click to expand...
Click to collapse
It was those files being leaked that allowed the CLIQ to be rooted...
I will be watching this thread closely I'm tired of having edge on my android....I need 3g for once!
Has anyone given this a try under Linux? I read the ADB beginners guide, but it didn't mention anything about drivers or whatnot. I'd really like to get this phone, but if I can't develop for it on my platform of choice, I don't think I need it that badly.
JK_the_Slacker said:
Has anyone given this a try under Linux? I read the ADB beginners guide, but it didn't mention anything about drivers or whatnot. I'd really like to get this phone, but if I can't develop for it on my platform of choice, I don't think I need it that badly.
Click to expand...
Click to collapse
This is from androidforums.com about this spicifically
http://androidforums.com/motorola-b...on-market-apps-via-adb-solved.html#post419647
On MacOS, ADB doesn't need a USB driver for your phone. Just download the SDK, and you can execute ADB from a terminal.
On Linux, all you need to do are to follow the instructions here:
Developing on a Device | Android Developers
Specifically the bit about creating and chmod'ing an /etc/udev/rules.d/51-android.rules file.
Hope AT&T fixes this issue soon, it's ridiculously stupid to attempt to disallow non-market apps given that ADB works.
Click to expand...
Click to collapse
j101399j said:
This is from androidforums.com about this spicifically
(URL deleted for forum reasons)
Click to expand...
Click to collapse
Thanks much, I'm just getting started on navigating all these forums. =)
Would it be possible for someone to create a utility to turn this option on, then load it via ADB? Or would this require root access?
BetterCut or AnyCut?
Charrion said:
I'm on a crusade
OK, so you can install apks through adb even without unknown sources being enabled.
Has anyone determined if the option to enter debug mode is still available on the backflop? I wouldn't be at all surprised if they disabled that option also.
I'm also curious whether the backflop has a signed mbm like the Milestone to prevent loading custom roms.
Click to expand...
Click to collapse
I don't have a Backflip, but it may be possible to find hidden settings / controls by using BetterCut or AnyCut. Both are in the Market.
I'd be interested in knowing. A crippled phone is a tiny electronic soul yearning to breathe free and live free.
I have a backflip, and just installed anycut. Do you know what I would need to fill in as the new shortcut to get to that option? I'm at work now, but will be doing the development method to install apks later under linux (gowalla app, most likely)
This is my first android phone, so I'm pretty excited to get it broken open and crapware free.
I just ordered the Backflip. Yes, I'm a newb at all this andriod, and rooting stuff. But, I'm in the process of learning more. I think it will be easier when I have the phone in hand to play with.
But, do you guys really think that someone will take the time to root the backflip, considering, (what I have read) that it is alittle out dated?
I'm going to attempt the non-market app install, once I get the phone. This forum is great, from what I've seen so far. I'll definatly be staying tuned to this thread.
Thanks guys,
J
Hi, since I cannot post to Android Dev, I'll post my question here; hopefully a mod will move my thread over to the Dev section.
I'm trying to find out which serial device is the phone's modem, running "cat /proc/tty/drivers" gives me a list of devices, which hang upon sending AT commands.
How could I identify the correct serial device?
Is there some kind of tracer I can run that could show me which device the RIL is calling?
Since the Nexus 5 is relatively new, not much info is available yet.
pcstyle said:
Hi, since I cannot post to Android Dev, I'll post my question here; hopefully a mod will move my thread over to the Dev section.
I'm trying to find out which serial device is the phone's modem, running "cat /proc/tty/drivers" gives me a list of devices, which hang upon sending AT commands.
How could I identify the correct serial device?
Is there some kind of tracer I can run that could show me which device the RIL is calling?
Since the Nexus 5 is relatively new, not much info is available yet.
Click to expand...
Click to collapse
Hi pcstyle,
I'm looking for the same procedure on Nexus 5.
Any Success/Progress on it ?
Saurabh
saurabh_meshram said:
Hi pcstyle,
I'm looking for the same procedure on Nexus 5.
Any Success/Progress on it ?
Saurabh
Click to expand...
Click to collapse
I am also very interested in finding a way to enable (by the means of recompiling the kernel or by writing an adapter) serial (tty) modem on Nexus 4/5 or by any other way.
romangs said:
I am also very interested in finding a way to enable (by the means of recompiling the kernel or by writing an adapter) serial (tty) modem on Nexus 4/5 or by any other way.
Click to expand...
Click to collapse
I suppose you don't have to recompile the kernel.
Since you are just writing to a file (can be any /dev/ttyX).
Have you checked your device under Window, in device manager. Does it show any COM or Modem port.
Please see the attached image.
Above snapshot is for my Huawei Modem, if Modem port is enabled for the device we can see this.
If the modem port is obtained, we can pass AT commands to it directly using Hyperterminal-like software.
Please let me know.
saurabh_meshram said:
I suppose you don't have to recompile the kernel.
Since you are just writing to a file (can be any /dev/ttyX).
Have you checked your device under Window, in device manager. Does it show any COM or Modem port.
Please see the attached image.
Above snapshot is for my Huawei Modem, if Modem port is enabled for the device we can see this.
If the modem port is obtained, we can pass AT commands to it directly using Hyperterminal-like software.
Please let me know.
Click to expand...
Click to collapse
Thank you for your reply. I am looking to access phone's modem from phone's terminal through /dev/tty like device. I've tried connecting and sending AT commands to most devices /dev/... with no success receiving any response.
This is where it is discussed in high details.
forum.xda-developers.com/showthread.php?t=1471241
As it currently stands there is no known way to access phone's modem using serial device like /dev/tty or similar. At least not on Nexus or Galaxy phones.
romangs said:
Thank you for your reply. I am looking to access phone's modem from phone's terminal through /dev/tty like device. I've tried connecting and sending AT commands to most devices /dev/... with no success receiving any response.
This is where it is discussed in high details.
forum.xda-developers.com/showthread.php?t=1471241
As it currently stands there is no known way to access phone's modem using serial device like /dev/tty or similar. At least not on Nexus or Galaxy phones.
Click to expand...
Click to collapse
I too am facing the same issue where I am not able to find which /dev/ttyX to write for Nexus 5.
However could you tell us about the following.
Which device are you using ?
Is the device rooted? Since writing to /dev files require root permission.
What platform are you working on ? Linux or Windows ?
You should not only look for a /dev/ttyX file, as shown here
http://stackoverflow.com/questions/7022525/at-command-in-android
Your modem related file can also be /dev/smdX.
Using ADB shell, Try ls -l /dev/smd* on your device, check for users and groupname by radio (See attached)
Try out some combinations there. Didn't work for me, might work for you.
Note: This may vary with devices, attached shot is on a Moto G.
In case of windows : This can also be a driver issue. If appropriate drivers are not available it may not expose Modem port in Windows.
I have tried for several phones but no luck. With a Dongle it works fine, able to pass AT commands.
pcstyle said:
Hi, since I cannot post to Android Dev
Click to expand...
Click to collapse
Dev isn't for questions. It's for development projects.
Sent from my Nexus 5 using Tapatalk
saurabh_meshram said:
I too am facing the same issue where I am not able to find which /dev/ttyX to write for Nexus 5.
However could you tell us about the following.
Which device are you using ?
Is the device rooted? Since writing to /dev files require root permission.
What platform are you working on ? Linux or Windows ?
You should not only look for a /dev/ttyX file, as shown here
http://stackoverflow.com/questions/7022525/at-command-in-android
Your modem related file can also be /dev/smdX.
Using ADB shell, Try ls -l /dev/smd* on your device, check for users and groupname by radio (See attached)
Try out some combinations there. Didn't work for me, might work for you.
Note: This may vary with devices, attached shot is on a Moto G.
In case of windows : This can also be a driver issue. If appropriate drivers are not available it may not expose Modem port in Windows.
I have tried for several phones but no luck. With a Dongle it works fine, able to pass AT commands.
Click to expand...
Click to collapse
1 – I tried connecting to almost all devices. I was trying to get response to ATZ, ATI commands and also tried to see my commands using logcat –b radio. I tried it on Nexus 5 and Nexus 4 with both stock and cyanogenmod ROMs.
2 – Yes, phones are rooted.
3 – Mainly Ubuntu 14.04 and sometimes Win 7 x64
I tried to connect 3G dongle to Nexus 5 – no go. Device does not see it. Did you connect USB 3G dongle to Moto G phone?
According to E:V:A “As you probably have seen already there are essentially two main ways to locally communicate with AT command interpreter. One is by some Shared Memory device /socket, and the other is through the Java OEM_HOOK_RAW_REQUEST through RIL.
Only rarely is there an accessible serial terminal device enumerated. Usually on MTK based modems and on some older FIrmware using Qualcomm based ones.”
Hi folks. im currently unable to use adb in cmd, only fastboot. So if anyone can help me upgrade my usb drivers to use adb with my windows 10. My device is seen currently as Kedacom USB Device, Google,inc driver. Android Bootloader Interface is using Microsoft winusb.sys (driver), wdfinstaller01009.dll(control), winusbCoinstaller2.dll(control)which are Windows 7 (old) Those are the best Microsoft and Dell can provide.
I know theres h91810 (i) LG_UP.dll floating around but Tmo is anti-rollback. So H91810( j ) LG_UP.dll would be the goto file set (i hope) Btw, the (i) is corrupt anyways? File extracted had error showing for me while it was in the .zip
Either one of these will help me with progressing towards getting my device working
twidledee said:
Hi folks. im currently unable to use adb in cmd, only fastboot. So if anyone can help me upgrade my usb drivers to use adb with my windows 10. My device is seen currently as Kedacom USB Device, Google,inc driver. Android Bootloader Interface is using Microsoft winusb.sys (driver), wdfinstaller01009.dll(control), winusbCoinstaller2.dll(control)which are Windows 7 (old) Those are the best Microsoft and Dell can provide.
I know theres h91810 (i) LG_UP.dll floating around but Tmo is anti-rollback. So H91810( j ) LG_UP.dll would be the goto file set (i hope) Btw, the (i) is corrupt anyways? File extracted had error showing for me while it was in the .zip
Either one of these will help me with progressing towards getting my device working
Click to expand...
Click to collapse
Uninstall the driver. Unplug your internet. Plug in your phone. Profit
Might have to select to install driver from a list. Then select Google.
lightninbug said:
Uninstall the driver. Unplug your internet. Plug in your phone. Profit
Might have to select to install driver from a list. Then select Google.
Click to expand...
Click to collapse
Ill try that
twidledee said:
Ill try that
Click to expand...
Click to collapse
Next time post in the appropriate section.
lightninbug said:
Next time post in the appropriate section.
Click to expand...
Click to collapse
Isn't this recovery thread?
twidledee said:
Isn't this recovery thread?
Click to expand...
Click to collapse
No... You made your OWN thread in the roms and development forum..... Can't you see that? ?
lightninbug said:
No... You made your OWN thread in the roms and development forum..... Can't you see that? ?
Click to expand...
Click to collapse
Your right. I'll slow down my brain a little. Adult adhd and my mind is in 10 spots at once. It's been challenging to focus very Long. I'm almost like the fish that gets distracted in Finding Elmore.
Except I get on one project and I end up doing 10. Ivr got an excellant excellent memory. I retain information really well hehe.
My apologies to folks in Roms-Recovery-Developement-and other projects )
Sent from my zeroltetmo using XDA Labs