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...
http://org.downloadcenter.samsung.c...113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe
22.8MB file installing slowly?
First off, I apologize for being paranoid. I downloaded this file and started installing it. It's a 22.8 MB .exe file. I started installing, and it *seems* to be working correctly. After clicking install MSS Installation Wizard is installing Samsung USB Driver for Mobile Phones V1.3.2200.0. Slightly after, desktop toolbar icon popped up Installing device driver software, opened it up showing:
USB Composite Device Ready to use
USB Mass Storage Ready to use
CDC Cerial Waiting for user input
Samsung LTE USB Device Ready to use
Samsung LTE Card USB Device Ready to use
It's been like 10-15 minutes and the MSS Installation Wizard is chugging along, at about 50%. Is this file legit? Is it just my slow ass computer that is making this install take forever? Have other successfully installed this for ADB usage?
Looks to just be the link to Samsung, which yes I have installed. It was a bit slow on my netbook.
Sent from my SGH-T769 using Tapatalk 2
Same here. I installed it yesterday while working on my wife's phone (Blaze also). The first time I tried to install it on my desktop it was slow and there was some sort of error. I had to reboot and redo it before I got it properly installed.
I've never needed the drivers, just downloaded kies.
Sent from my SGH-T769 using XDA
Kies I think installs the drivers for you. You can't properly use the device without the drivers and you definitely cannot use some of the tools without them.
No ADB
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Does anyone know how to get this device working with adb on Debian? I can't for the life of me get the device recognized by adb. I have a 51-android.rules set up and all that jazz. udev sees it and rules are applied properly. I just can't get it recognized. It seems references to accessing this device from Linux are very few and far between. What gives?
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
strungoutfan78 said:
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
Click to expand...
Click to collapse
Can you explain this a bit more, like where to input these commands. Im a bit green and having this issue.
---------- Post added at 01:25 AM ---------- Previous post was at 01:04 AM ----------
theshowman said:
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Click to expand...
Click to collapse
I tried the #7284# and #9090# and got "unable to process request"
any other suggestions?
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
iainwith2is said:
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
Click to expand...
Click to collapse
Install the adb/fastboot drivers. Google is your friend
Firstly thank you for your reply.
I have tried your install but it hasn't worked. I can tell I have been following a smilar update route looking at the pictures you uploaded also, although these screen snaps were obviously from a new OS (windows 7 perhaps).
Whats interesting to note however, is that in my device manager the phone is clearly shown twice, at the top as "Android Device", with "Google Nexus ADB Interface" below it and then again further down as "Other Devices" with MTP below with the familiar yellow exclamation mark.
Significant?
You actually don't need debugging mode if you're intending to manually flash the ROM. Debugging mode is only an android setting and you flash the ROM using fastboot which is outside of android.
Also you don't need the SDK.
I would say go to general > sticky roll-up then read my adb and fastboot thread to start
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
If you used the adb and fastboot installer in my thread, did you use the "install system wide" option?
If not, do.
If you did and it did not work, read more of that section as the manual steps are also mentioned, which you'll need to follow.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
He should already have it from my thread. Its just a question whether he used it correctly or whether it doesn't set up the environment variables on xp properly
Yes installed the 15 second install, Y,Y,N, then installed the Clockmod driver.
I'll go back and read it again, guess I must've missed something.
Have you rebooted? Try that. Is still no, you'll need to manually populate the environment variables.
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
iainwith2is said:
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
Click to expand...
Click to collapse
Don't copy and paste it. The text is generic. You must put your text there....then reboot.
this is what I pasted:
;c:\adb_fastboot
?
iainwith2is said:
this is what I pasted:
;c:\adb_fastboot
?
Click to expand...
Click to collapse
Which is generic. Is the folder your adb and fastboot executables are in called c:\adb_fastboot? If you used the installer, it is not.
Where would the installer put them? I've searched my computer for "fastboot" and its found the exe that I put in a folder on my desktop. This looks a similar address to what I changed the path to previously...
Oy vey
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Oy vey
Pardon?
Click to expand...
Click to collapse
OK so my path is broken so I won't be able to run adb commands?
Did you look at the root of c:? C:\adb perhaps? Its all covered in my thread isn't it? Are you reading it or skimming it? You don't even *need* to put it in the path. Its just easier. Please read to the end of the thread
Also, you don't need to run any adb commands
Yes I've scanned c: drive.
I've read and understood what I can, I'm not an expert so I can only compute what I understand.
I have reinstalled the adb setup a few times and I have noticed that it clearly says "0 files copied" after I select the exe files and system wide options.
I have also tried to run the adb and fastboot devices commands in the command window which gives me the aforementioned error messages.
For some reason, these programs are not being installed onto my machine?
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
- copy apps/APKs between phones
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: https://play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I also ported Fastboot - user should be able to execute fastboot commands
Thanks
Correct me if I'm wrong, but can't you use a local terminal to execute certain commands?
SaadatM said:
Correct me if I'm wrong, but can't you use a local terminal to execute certain commands?
Click to expand...
Click to collapse
Not sure if I understand what you mean with "local terminal". .. Do you mean a shell spawned from regular app running on your phone?
The point of the app is to perform some privileged tasks that cannot be performed by regular apps on non-rooted phone.
You should be able to perform these tasks without the need to install ADB on your PC, or even without having a pc currently at your hands(e.g., if you're on-the-go).
Additionally, you should be able to perform a lot of these tasks with a couple of taps (instead of typing shell commands).
Is it possible to connect to localhost (127.0.0.1), and issue adb commands to the device running this app?
crunchybutternut said:
Is it possible to connect to localhost (127.0.0.1), and issue adb commands to the device running this app?
Click to expand...
Click to collapse
It's actually doing the opposite.
You issue commands from app to the connected device. The app is running the adb components you are running on your pc.
You connect one device that runs the app to another device that you want to debug. You can connect the devices via Wi-Fi or USB OTG.
bugjaeger said:
It's actually doing the opposite.
You issue commands from app to the connected device. The app is running the adb components you are running on your pc.
You connect one device that runs the app to another device that you want to debug. You can connect the devices via Wi-Fi or USB OTG.
Click to expand...
Click to collapse
I get that is the purpose, I was just curious if it was possible to point at the same device. It would make ADB stuff much simpler when no other devices are available.
I get that is the purpose, I was just curious if it was possible to point at the same device. It would make ADB stuff much simpler when no other devices are available.
Click to expand...
Click to collapse
If you made adbd listen on specific port before(adb tcpip 5555), then yes, you can issue adb commands from the app to the same device running the app.
bugjaeger said:
If you made adbd listen on specific port before(adb tcpip 5555), than yes, you can issue adb commands from the app to the same device running the app.
Click to expand...
Click to collapse
I believe you'd need root to do that though, right?
crunchybutternut said:
I believe you'd need root to do that though, right?
Click to expand...
Click to collapse
No, I don't think you need root. I used it a lot on my non-rooted Nexus 5x and once on an old Asus Zenfone during testing and it was working as expected.
That's great . I was just wondering if there was something like this already out there. Thanks for your efforts and I hope you are prosperous.
bugjaeger said:
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I've added the possibility to copy apps/APKs between phones
Thanks
Click to expand...
Click to collapse
I have a question about this app. I have installed it and find a few over internet connections (android box, fire tv) but when i connect my wifes non rooted S9 snapdragon. It asks what i want to use visa otg cable. (Smartswitch ect..)
Maybe the best way to put this is to tell you want i want to do.
I have a rooted note 5 and my wife has a new non rooted S9 from T mobile. The bloatware sucks as i am sure you can imagine. I have read how to remove the bloat with package disabler without root. My issues is i need to make PIP a sister app for package disabler a device owner app. This is done through adb and a few simple commands. My problem to solve my issue is i have no PC in order to use ADB on. I have looked for way to use phone to phone ADB with OTG but never been able to put ADB on my note 5 to use the terminal like from a PC.
Any help would be great thanks.
lodk said:
I have a question about this app. I have installed it and find a few over internet connections (android box, fire tv) but when i connect my wifes non rooted S9 snapdragon. It asks what i want to use visa otg cable. (Smartswitch ect..)
Maybe the best way to put this is to tell you want i want to do.
I have a rooted note 5 and my wife has a new non rooted S9 from T mobile. The bloatware sucks as i am sure you can imagine. I have read how to remove the bloat with package disabler without root. My issues is i need to make PIP a sister app for package disabler a device owner app. This is done through adb and a few simple commands. My problem to solve my issue is i have no PC in order to use ADB on. I have looked for way to use phone to phone ADB with OTG but never been able to put ADB on my note 5 to use the terminal like from a PC.
Any help would be great thanks.
Click to expand...
Click to collapse
So you tried to connect your phone (with Bugjaeger installed) to you wife's phone via USB OTG cable? And the phone with Bugjaeger app doesn't detect any ADB device connection (or other dialogs pop up)? Did I understand this correctly?
You might need to temporarily disable the other protocols that Android offers via USB so that there are no other dialogs popping up (on your wife's phone). On my Nexus with Android 8, I can go to Connected devices -> USB and switch it to only "Charge this device" (so PTP or the other stuff is disabled).
In case there is some other app doing stuff with ADB USB devices, you might also need to change your defaults so that Bugjaeger can handle ADB USB devices.
Then you also need to make sure that Developer options are enabled on your wife's phone (and USB debugging of course).
Once you successfully connected and authorized the phone, you should do the following
- In Bugjaeger app switch to Packages tab and click on Add button top right (the button with the plus sign). Then you should pick the package disabler APK. This should install the package to your wife's phone
- Switch back to Commands tab (first tab) and either click on plus button in top right or shell into the device with the floating action button ("<>").
You can then activate the device owner with something like this
Code:
dpm set-device-owner disabler.package.name/.DisablerAdminReceiver
*Note that I don't prefix the command with "adb shell" here
When activating device owner you also need to make sure that there are no other accounts configured on your wifes phone (e.g. google account) because otherwise it probably won't work.
You can also check my blog post where I describe how to activate device owner with Bugjaeger in more detail (at the end of the blog post)
https://sisik.eu/blog/android/dev-admin/set-dev-owner
Hope that helps
going to give this a try thanks will post later with results,
Hi, I have a problem and I hope your app can help me.
I am without a PC and I have a tablet without root where I installed the application and a Samsung mobile phone that starts only in download mode, otherwise it gives me the message: Custom Binary blocked by FRP lock
Can I install a rom or a custom recovery with the app? I tried to connect them with the cable but it does not find the device.
Crisal said:
Hi, I have a problem and I hope your app can help me.
I am without a PC and I have a tablet without root where I installed the application and a Samsung mobile phone that starts only in download mode, otherwise it gives me the message: Custom Binary blocked by FRP lock
Can I install a rom or a custom recovery with the app? I tried to connect them with the cable but it does not find the device.
Click to expand...
Click to collapse
Hi,
Unfortunately, I don't think my app can help you in this case.
Hi, thanks for the reply. Do you know a way to help me?
please help me!!
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
bugjaeger said:
I'm working on an ADB port which allows ADB(client/server) to run directly on Android device.
The app allows you to connect your phone to another Android device via USB OTG and perform some tasks that you normally perform from your PC(that has ADB installed).
For example
- take screenshots
- check logs
- install/remove packages
- check running processes
- push/pull files (also from locations that are not available to regular apps)
- run shell scripts executed as privileged ADB user
- create ADB backups and inspect backup files
- copy apps/APKs between phones
It's still work in progress(even though it's published), and I'm not even sure what features of ADB I should make available through the UI.
I was hoping to get some feedback here.
What are the main issues with UI? (because adb has so many features, I found it extremely hard to pack it into UI that would be intuitive)
What features would you expect from this kind of app?
Should I also embed fastboot, so that users would be able to flash Android from phone to phone?
Is it even worth to work on another one of these apps? (Maybe most people just prefer to always use ADB features directly from PC)
Bugjaeger Mobile ADB - Develop & Debug via USB OTG
Google play link: play.google.com/store/apps/details?id=eu.sisik.hackendebug
Update
I also ported Fastboot - for now the user can dump bootloader info
Thanks
Click to expand...
Click to collapse
lindser112 said:
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
Click to expand...
Click to collapse
I don't have any wear os watch at my hands right now and I can't test it at the moment. Is the APK compatible with the watch? If you're able to establish an adb connection between Bugjaeger and the watch, try to check the "Packages" tab in Bugjaeger app. There's a "+" button in the top toolbar, which allows you to select apk for installing on the target device.
The official docs are showing how to establish ADB connection with the watch - https://developer.android.com/training/wearables/apps/debugging
In Bugjaeger you then need to tap the connect button (plug with a plus sign in top toolbar), type in the IP address of the device, and tap on connect button. Both devices should be connected to the same WiFi network to make this work.
i figured it out!!!! go to packages, press the plus button, install from apps installed on phone. it was soooo easy. i couldnt get adb to work on my pc!! i am so thankful to you for this app!!!!!
lindser112 said:
will this app install an apk ive downloaded onto my phone onto my wear os watch? i have them both connected and wifi debugging. not sure how to go about installing the apk though. any help would be appreciated. thank you
lindsay
Click to expand...
Click to collapse
lindser112 said:
i figured it out!!!! go to packages, press the plus button, install from apps installed on phone. it was soooo easy. i couldnt get adb to work on my pc!! i am so thankful to you for this app!!!!!
Click to expand...
Click to collapse
Perfect :laugh:
For years, I struggled to get ADB/FASTBOOT installed and working. I've succeeded fairly often but usually have a success/failure ratio of one hundred to one. I'm currently trying it again, so thought I'd make a request for info from someone more experienced than myself.
First of course, is USB Debugging enabled. Done.
Then install OEM USB drivers; in my case Samsung.
Finally install the "short" version of Android SDK Development tools (just adb and fastboot but nothing else).
Am I missing something? I usually have to keep "hacking and whacking" at the damn thing until I finally stumble upon the correct combination of components.
And of course different cables, different computers, different Windows versions, etc, etc, etc ad nauseum.
I even reinstalled Windows 7 for a "fresh" PC and EVEN that did not help.
SO.......... Anyone have any ideas what works "first time, every time". I'm desperate.
Boowho??
boowho said:
For years, I struggled to get ADB/FASTBOOT installed and working. I've succeeded fairly often but usually have a success/failure ratio of one hundred to one. I'm currently trying it again, so thought I'd make a request for info from someone more experienced than myself.
First of course, is USB Debugging enabled. Done.
Then install OEM USB drivers; in my case Samsung.
Finally install the "short" version of Android SDK Development tools (just adb and fastboot but nothing else).
Am I missing something? I usually have to keep "hacking and whacking" at the damn thing until I finally stumble upon the correct combination of components.
And of course different cables, different computers, different Windows versions, etc, etc, etc ad nauseum.
I even reinstalled Windows 7 for a "fresh" PC and EVEN that did not help.
SO.......... Anyone have any ideas what works "first time, every time". I'm desperate.
Boowho??
Click to expand...
Click to collapse
What are you trying to do with ADB
([emoji3590]09-09-18[emoji3590])
boowho said:
For years, I struggled to get ADB/FASTBOOT installed and working. I've succeeded fairly often but usually have a success/failure ratio of one hundred to one. I'm currently trying it again, so thought I'd make a request for info from someone more experienced than myself.
First of course, is USB Debugging enabled. Done.
Then install OEM USB drivers; in my case Samsung.
Finally install the "short" version of Android SDK Development tools (just adb and fastboot but nothing else).
Am I missing something? I usually have to keep "hacking and whacking" at the damn thing until I finally stumble upon the correct combination of components.
And of course different cables, different computers, different Windows versions, etc, etc, etc ad nauseum.
I even reinstalled Windows 7 for a "fresh" PC and EVEN that did not help.
SO.......... Anyone have any ideas what works "first time, every time". I'm desperate.
Boowho??
Click to expand...
Click to collapse
As long as you have the complete USB drivers for your device, USB debugging enabled and the adb 15 second installer installed on PC, it should work. When you connect your device to adb, you "should" get a prompt or notification on your device to allow adb access, if you do, grant it permission.
If you're trying to use fastboot on a Samsung device, you can give up on that notion, Samsung devices can't use fastboot for anything, it isn't compatible at all, you will never get it to work.
But...
ADB works just fine on Samsung.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
As long as you have the complete USB drivers for your device, USB debugging enabled and the adb 15 second installer installed on PC, it should work. When you connect your device to adb, you "should" get a prompt or notification on your device to allow adb access, if you do, grant it permission.
If you're trying to use fastboot on a Samsung device, you can give up on that notion, Samsung devices can't use fastboot for anything, it isn't compatible at all, you will never get it to work.
But...
ADB works just fine on Samsung.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks so much for your thoughts/reply. I found last night that stripping ALL previously installed USB drivers and re-installing the Samsung USB drivers got it working. I plugged the device in BEFORE installing Sammy's drivers and it showed in device manager (without a driver, of course). I then installed the drivers and it connected. At that point ODIN worked just fine. Then I did an "adb devices" and it responded as it should.
For me, all these "packages" (Like 15 second installer or something) with .bat files, etc are not needed at all for ADB and just make things more confusing.
Just the two executables and three .DLL files make ADB and fastboot work in windows; IF you have previously installed Sammy's drivers as mentioned above.
Finally, not to disagree with you (after all it was ME who came here looking for help), but FASTBOOT works just fine on my Samsung device (a Gear Live Watch). I have to use the command "adb reboot bootloader". The watch reboots and from there all fastboot commands seem to work just fine. I flashed several .img files that way.
It's possible (I suppose) that no other Sammy device will accept fastboot, because supposedly Sammy wasn't even involved in creating the firmware for that watch. Google did it ALL.
Oh, and one last thing..... Yes I HAD it all working, but now ADB devices shows the device as "unauthorized". It did not when I first did the ADB devices, but instead put up the popup asking for permission. Now it just says unauthorized and fails to popup the little message
I've gone thru all the "fixes" for this that I can find for this particular problem, but so far no joy.
Maybe it's just me, but setting up ADB/fastoot as ALWAYS been a pain is the ass.
Boowho??
boowho said:
Thanks so much for your thoughts/reply. I found last night that stripping ALL previously installed USB drivers and re-installing the Samsung USB drivers got it working. I plugged the device in BEFORE installing Sammy's drivers and it showed in device manager (without a driver, of course). I then installed the drivers and it connected. At that point ODIN worked just fine. Then I did an "adb devices" and it responded as it should.
For me, all these "packages" (Like 15 second installer or something) with .bat files, etc are not needed at all for ADB and just make things more confusing.
Just the two executables and three .DLL files make ADB and fastboot work in windows; IF you have previously installed Sammy's drivers as mentioned above.
Finally, not to disagree with you (after all it was ME who came here looking for help), but FASTBOOT works just fine on my Samsung device (a Gear Live Watch). I have to use the command "adb reboot bootloader". The watch reboots and from there all fastboot commands seem to work just fine. I flashed several .img files that way.
It's possible (I suppose) that no other Sammy device will accept fastboot, because supposedly Sammy wasn't even involved in creating the firmware for that watch. Google did it ALL.
Oh, and one last thing..... Yes I HAD it all working, but now ADB devices shows the device as "unauthorized". It did not when I first did the ADB devices, but instead put up the popup asking for permission. Now it just says unauthorized and fails to popup the little message
I've gone thru all the "fixes" for this that I can find for this particular problem, but so far no joy.
Maybe it's just me, but setting up ADB/fastoot as ALWAYS been a pain is the ass.
Boowho??
Click to expand...
Click to collapse
Samsung gear doesn't count, as you said, Samsung doesn't have anything to do with creating the firmware. I would think that any android device that Samsung had it's part in making firmware for, doesn't work with fastboot. But, devices that are Samsung "in name" only, may be compatible with fastboot. The question is, is it really a Samsung or is it just wearing the Samsung name?
Sent from my SM-S767VL using Tapatalk