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...
Getting the SDK installed didn't come without a couple issues, but I managed finally to get it working. Now, how do I transfer files to and from my g2x? I tried "adb push c:\users\eric\downloads\Pink Floyd /sdcard/music" and nothing happens. It doesn't give me some error in the command prompt or anything it just sits there indefinitely. I saw some videos that showed a success message after the files were transferred.
Should I be in "c:\sdk\" or "c:\sdk\platform-tools" to execute the push/pull commands? Does it even matter? I tried doing it from both and I got the same results from both. I'm thinking it's just something small that I'm missing, but unfortunately I can't seem to find what that may be. HELP PLEASE!
e4e5nf3nc6 said:
Getting the SDK installed didn't come without a couple issues, but I managed finally to get it working. Now, how do I transfer files to and from my g2x? I tried "adb push c:\users\eric\downloads\Pink Floyd /sdcard/music" and nothing happens. It doesn't give me some error in the command prompt or anything it just sits there indefinitely. I saw some videos that showed a success message after the files were transferred.
Should I be in "c:\sdk\" or "c:\sdk\platform-tools" to execute the push/pull commands? Does it even matter? I tried doing it from both and I got the same results from both. I'm thinking it's just something small that I'm missing, but unfortunately I can't seem to find what that may be. HELP PLEASE!
Click to expand...
Click to collapse
For ADB Push/Pull, I place my files in the "platform-tools" folder.
It should be something like this. -
cd \AndroidSDK\platform-tools
adb devices
adb remount
adb push Whatever.apk /system/app
adb remount
adb reboot
I was using the wrong slashes like a moron. Too much Sunday beer I guess.
Sent from my LG-P999 using xda premium
This incorporates the ideas of http://forum.xda-developers.com/showthread.php?t=2144709, so if you want to see how this was resolved for the Nexus 4, check out that thread.
Okay. So you've flashed a spanking new 4.2.2 ROM and ADB no longer talks to your Sensation. What happened?
Well, the fact is that 4.2.2 is significantly more secure, in the good sense. It enforces RSA authentication via ADB. However, RSA authentication is supported only in recent versions of ADB.
What to do?
First, make sure you have the latest version of ADB on your PC.
On Windows you can quickly find out if you your version of ADB is up to date. Check your ".android" folder and see if it holds a file called "adbkey".
On any platform type "adb version" to verify that you have the latest version of ADB. Versions 1.0.31+ support RSA authentication.
-- So now, if you have ADB 1.0.31 or higher. You can skip directly to step 2, then.
-- If you do not have ADB 1.0.31 or higher, and you have the full Android SDK installed, open the SDK manager and update it. If you only have ADB and fastboot installed in a folder on your PC, overwrite files in the folder with those in the corresponding zip file attached (windows or linux -- sorry! I don't have Mac versions at this time). These come from version 16.01 of the android platform-tools package, if you are curious.
-- if you have never installed the SDK or ADB or fastboot, now is the time to do that. I recommend going to http://developer.android.com/sdk/index.html to get started.
[*]Enable USB debugging on your phone
USB debugging is now enabled by selecting Android Debugging in System Settings > Developer Options.
"I don't have the Developer Options items in System Settings!!"
In Android 4.2.x, you need to go to System Settings > About Phone and tap the Build Number item about 6 or 8 times, and Developer Options will reappear.
[*]Plug in the USB cable. Securely.
Dismiss the USB mass storage window.
"I connected the cable, but nothing happened!!"
Okay, chill. You won't get a response until ADB tries to connect to your Sensation. So go ahead and start ADB on your PC. Suggested command:
Code:
adb devices
"Now ADB started, but nothing's happening on my computer!!!"
Uh, didn't I just advise you to chill ? Take a look at your phone...
"What's this pop-up that just popped up??"
(See image below)
Congratulations, that is Android asking your permission to store an RSA key on your Sensation for ADB interaction with your PC.
Fearlessly accept it.
Hint: check the "Always allow from this computer" box to save time later on.
The RSA authentication key you just accepted will be stored on your phone in the file /data/misc/adb/adb_keys.
You are now good to go. Just 3 easy steps with a minimum of panic.
Questions? Problems? Ask away!
Many thanks to XDA member skipjacks for the idea for this post
Hi,
Nice! :good:
People should also not use USB 3.0 slots or USB hubs.
Try several slots if the front ones do not work.
Windows 7 & 8 drivers are HERE in case anyone needs them...
malybru said:
People should also not use USB 3.0 slots or USB hubs.
Click to expand...
Click to collapse
I understand about the hubs, but why not USB 3.0?
Skipjacks said:
I understand about the hubs, but why not USB 3.0?
Click to expand...
Click to collapse
Hi,
I have read a lot of instances of "Device not recognized" when using 3.0 slots.
I am not saying it will never work.
But ,if you use one,and it does not work,then,try it on a 2.0 slot.
Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.
onemanshow85 said:
Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.
Click to expand...
Click to collapse
Hi,
I think there is one solution that will address both issues. Before I mention it, let me ask: are you sure you enabled USB debugging on your Sensation? This is confirmed if, when you plug in the cable to your PC, you immediately get a USB debugging icon in the Notification Bar.
Glad we got that out of the way!
Unplug your device from the PC.
Anyhow, since you already have the SDK installed, the recommended way to update is to use the SDK Manager.
--in Windows, I think this is an executable in the tools sub-folder of your main android SDK folder. Double clock on it.
--in Linux, start up a terminal and type
Code:
android
if that doesn't do it, CD to the /tools directory in android-sdk-linux, or wherever you put the SDK, first. Then type "android".
The window that opens when you start SDK Manager should show that you need an update to (at least) platform-tools. Go ahead and do the update. You will have to accept some license(s) - accept it or them.
Once the install is complete, close SDK Manager.
Now plug your USB cable back in, and try out the "adb devices" command. It should work.
Suppose you still get "device not found", though. Try the following: again unplug.
Type the command:
Code:
adb kill-server
Now plug the phone back in, verify that you have USB debugging, and try "adb devices".
If no go, let me know what platform you are running, etc. I've heard it could be the cable, but I think that you just need to make sure it is plugged in securely.
BTW, the reason you probably won't have to do the adb kill-server step is that the SDK Manager kills running adb processes during the install.
Let me know how it goes!
Yrs,
dkephart
Sent from my HTC Sensation using xda premium
tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot
onemanshow85 said:
tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot
Click to expand...
Click to collapse
Yeah... my random selection doesn't have this problem. But I once seemed to have it with the official cable. You might want to try rebooting both the phone and the PC.
Sent from my HTC Sensation using xda premium
The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.
onemanshow85 said:
The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.
Click to expand...
Click to collapse
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium
dkephart said:
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Some really cheap cables only have 2 wires in them and can only be used for charging. You need the other wires for data transfer.
But some companies only put the charging wires in to save money on the copper.
It must be a REALLY low quality cable though. I mean I get all my cables on Monoprice for like $1-$2 and they all work great for data.
Or, the cable does have all the internal wires and one is just broken inside.
Sent from my HTC Sensation using xda app-developers app
I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.
nemovich said:
I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.
Click to expand...
Click to collapse
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium
dkephart said:
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
no just the serial number
nemovich said:
no just the serial number
Click to expand...
Click to collapse
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium
dkephart said:
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
with adb shell I get $ and with su I get #.
nemovich said:
with adb shell I get $ and with su I get #.
Click to expand...
Click to collapse
Cool! Then you have adb working. To confirm, in the shell, "ls" should come back with a listing of the files on your device. If you do "cd sdcard" and "ls" you get the files on the SD card.
You're good to go.
Sent from my HTC Sensation using xda premium
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Sent from my HTC Sensation using xda premium
nemovich said:
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Click to expand...
Click to collapse
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium
dkephart said:
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
when I cd to the sdk folder ( C:\Users\Documents\adt-bundle-windows-x86-20130219), it gives me command not recognized. I can run sdk manager from the folder and everything is up to date.
I run adb from platform-tools and it gives me the same thing as before.
one thing though, I don't see the "adbkey" file in platform-tools but it is there in ".android" folder. so I run it from the later folder too but the still the same thing, no pop-up.
it's not just android commander, a lot of other apps give the same thing.
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:
Hi
Has anyone tried the XDA Navigation gestures app on the Nokia 7 Plus? If so can you guide me through the process that involves granting permission via adb. I did follow the steps as mentioned, but I am not seeing the desired results.
Thanks
I tried that too. I got "permission denied" or something like that.
yes, i use it without problem, with "8.1 June" and also "P DP2rev2"... for grand use exactly adb command what app show, if you have any problem then i think is with non functional adb and/or with badly rewrite adb command, try post output from terminal/command_prompt after you second try it
btw: you have enabled USB Debuging in Developer Settings on phone right?
edit: info about installing adb is here
I had a problem using the ADB. It kept saying "adb" wasnt a correct command. But I figured out that I had to type ".\adb" to make it work
Using it here without any major issues except sometimes a bit laggy