As many of you may know, there's currently no native way to screenshot an Android Wear device, and at this point it's pretty cumbersome to need to get to a computer to run ADB just to get a screenshot.
I've managed to at least remove the need for a computer, as long as your phone (or whatever your watch is paired with) is rooted (your watch does NOT need to be rooted), through a simple script I threw together, wearcap. It properly loop-back connects to your device and then connects to the watch over ADB. I'm sure this can be made into an actual app, but I don't care enough or have the time to do it. All you need to do is run it as root with whatever terminal app you desire. Wearcap assumes you've done all the necessary USB debugging settings, which can be found below. Screenshots are saved in /sdcard/Pictures/Screenshots/ on your device and then removed from the watch.
Everything else is pretty self-explanatory, just push the script onto your device, give it executable permissions and be on your way. As noted in the script itself, make sure your screen is on during the connection process, my Moto 360 would typically fail to connect if it was off.
For a reminder of how to setup USB debugging for the devices: http://www.androidpolice.com/2014/0...nlock-the-bootloader-and-root-the-lg-g-watch/
And here is the Google+ thread: https://plus.google.com/u/0/113601948978986762347/posts/6dD6xBrvpjs
"This paste has been removed"
Spere said:
"This paste has been removed"
Click to expand...
Click to collapse
Sorry about that, it's been attached as a text file now.
an apk will be wonderful
I can wrap it into app tomorrow if CEnnis91 is OK with it, I'm thinking to add change of the density as well through adb.
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Kyocera-E4710 - T-Mobile Tethering
I too have purchased one of these excellent flip phones. I really want to be able to tether using T-Mobile's service. Has anyone risen to the challenge yet?
kotton666 said:
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Click to expand...
Click to collapse
Rooting Kyocera E4710
Is it possible to root this phone? I would like to install an Android SIP client, the operator said it's not possible to install anything on it. Even though I enabled apps from Unknown Sources.
kotton666 said:
the Kyocera-E4710 is probably the best flip phone on the market. It's made in Japan and sold in the U.S. and Canada via a few carriers. But many people from other nations purchase it for it's rugged features that make it usable where a smartphone just can't be used. Unfortunately, some of the features, like tethering, won't work because, although it's been unlocked, it still needs the settings for the carrier (like AT&T).
I don't understand how this works but I'm sure someone on here does? I'm hoping some bright person on XDA can help the many people who have purchased this awesome handset in other nations, to be able to unlock the tethering feature. As well as to perhaps remove some features, such as the incredibly annoying AT&T address book that pops up every time you go to your contacts or add apps to the android operating system.
Any help with these issues would be so greatly appreciated!!
Click to expand...
Click to collapse
Not sure if anyone still needs to remove the AT&T address book on this phone without root BUT I managed to do it.
Enable Developer mode on the phone by clicking:
"Menu" from the home screen. Choose Settings-->System-->About Phone.
Scroll down to "Build Number" and hit the "ok" button a few times until it tells you that you're a developer.
Back up one menu and go into "Developer Options".
Enable USB Debugging. (I also enabled OEM Unlocking but I don't think this is necessary)
Next install the Universal ADB drivers onto your computer. Google will help you find them. (I used the ones from clockworkmod but I'm sure any of them would be fine.)
Connect your phone and ALLOW any of the prompts that come up.
Open up an administrative command prompt/terminal and then type "adb devices". Make sure you can see a device listed. I'll look something like:
* daemon started successfully *
6689467283 device
Next run the command:
adb uninstall --user 0 com.borqs.aabsync
You should see a "success" below.
If so run the command: adb reboot
Your phone will reboot and you can disconnect the phone from the computer at this point.
Give it a moment to start up and then hit the "down" arrow on the keypad as normal. You will likely see an empty contact list. Press the key for "Options" then choose "Contacts to display" and choose wherever you have the contacts saved. Let it load them in and you're done.
Hope this helps someone!
david11717 said:
Not sure if anyone still needs to remove the AT&T address book on this phone without root BUT I managed to do it.
Enable Developer mode on the phone by clicking:
"Menu" from the home screen. Choose Settings-->System-->About Phone.
Scroll down to "Build Number" and hit the "ok" button a few times until it tells you that you're a developer.
Back up one menu and go into "Developer Options".
Enable USB Debugging. (I also enabled OEM Unlocking but I don't think this is necessary)
Next install the Universal ADB drivers onto your computer. Google will help you find them. (I used the ones from clockworkmod but I'm sure any of them would be fine.)
Connect your phone and ALLOW any of the prompts that come up.
Open up an administrative command prompt/terminal and then type "adb devices". Make sure you can see a device listed. I'll look something like:
* daemon started successfully *
6689467283 device
Next run the command:
adb uninstall --user 0 com.borqs.aabsync
You should see a "success" below.
If so run the command: adb reboot
Your phone will reboot and you can disconnect the phone from the computer at this point.
Give it a moment to start up and then hit the "down" arrow on the keypad as normal. You will likely see an empty contact list. Press the key for "Options" then choose "Contacts to display" and choose wherever you have the contacts saved. Let it load them in and you're done.
Hope this helps someone!
Click to expand...
Click to collapse
Thanks for posting your solution above.
Unfortunately for me I got as far as installing the adb drivers on my PC, reconnecting the phone, and no prompts came up, neither on the phone nor the PC.
I opened a command prompt window and typed "adb devices" and got the following message:
adb devices is not recognized as an internal or external command,
operable program or batch file.
Any suggestions?
As long as ADB driver isn't made system-wide accessible ( i.e. got added to PATH environment variable of Windows OS ) you get the message mentioned.
My Kyocera E4710 outer screen has an alarm that I can't get to go away. I can't see who is calling me because the alarm blocks the caller info. I have a few alarms but they are all turned off and there is not a way to delete them. I've gone through the user manual and it doesn't show how to get rid of this alarm (which shouldn't show since there isn't one enabled). Does anyone know how to get rid of this alarm on the outer screen? Thanks.
Alright, I was reading around about the Wear24 the issues the Verizon bloatware was causing (Crucial WearOS features being limited/disabled). I decided enough was enough and decided to share this method with you. It involves the "user 0" method. You will still be able to get OTA updates and all that good stuff! If you factory reset the watch, you might have to do this again.
First (Highly recommended), factory reset your watch. Then set it back up and update WearOS (Don't worry about updating anything else) via the play store (You can sideload it too).
Second, after setting up your watch, go to settings -> system -> about then tap on your build number until you have unlocked developer settings.
Third, go to your developer options and enable ADB debugging and debug over Wi-Fi.
Connect to your Wi-Fi and click on the Wi-Fi network you are connected to, it should show your IP address (Take note of your IP address) and MAC address.
Assuming you already have ADB setup on your machine type:
Code:
adb connect your.watch.ip.address:5555
Then
Code:
adb shell
After that you should see something like this: dorado:/ $
If that shows, great! If not, make sure you have authorized your PC on your watch.
Moving on, you want to get the list of Verizon apps installed on your watch so type:
Code:
pm list packages | grep 'verizon'
And you should get the list of Verizon apps in the form of package names that is currently installed.
Next you'll want to uninstall them (All 5 or 4 of them. I can't recall as I have already done this). so here is the command to do so.
Code:
pm uninstall -k --user 0 com.verizon.crapware.mesagesplus
I hope you got the gist of that.
After you have uninstalled the packages, reboot your watch, and you should be able to see the apps that you have installed in the app drawer, and you should be able to set Google Messages as your default! Also as an extra measure, just disable all of the Verizon apps. They'll still show in your system apps, but if you click on permissions, it'll say "App isn't installed".
I'm sorry if the format is crappy. Also, mods, if you feel that this doesn't belong here, feel free to delete this post.
If you are having troubles doing this, I can clarify and help you guys out if need be!
Thanks for this! Just picked up two Wear24's, going to debloat them right away.
I've had this watch since Jan 2018 and I'd like to try this out, however, no matter what I do I can't connect to the watch over adb. Same wifi network, abd is working fine on Note9, debugging over wifi is turned on, just constantly get this error "An attempt was made to access a socket in a way forbidden by its access permissions. (10013)". Any suggestions?
I was just tooling around in my new Quest 2 and, while my level of technical expertise is sufficient to be dangerous, I don't have any real idea what I'm doing as far as rooting, bootloader mods, etc. However, I seem to have stumbled into the regular Android settings after an app I was trying asked for usage permissions, which it seems Oculus doesn't expect any of its bespoke apps to do.
The Android settings behave oddly, though, but more like there's some kind of watcher app that's preventing access to most of these non-Oculus options. Case-in-point, the app that wants usage access, when I enter the Usage permissions screen and select the app from the menu to be taken to the screen where it displays what the app will do with usage permissions and presents the toggle for it, the screen comes up only briefly before the settings dialogue disappears entirely with an error saying that "System has stopped responding". I'm pretty sure if I were fast enough, I could probably toggle it in time, but I could also try to grant those perms via adb (which I only now remembered I could do and thus haven't done yet).
I also found and enabled the actual Developer Options, not the basic one Oculus gives us if we sign up as a developer organization. I am certain that they have actually been enabled: Even though the "{ } Developer Options" menu item keeps reloading the page that its on, settings that you'd expect to find within now turn up in the settings search dialogue.
One of these options is to enable OEM bootloader unlock. Selecting that options from the search results screen (or any other search result you'd find within Developer Options) however does like before, drops you at the menu page with the "{ } Developer Options" option.
It would be absurd if it were to be as simple as enabling that option to gain access to the bootloader and do whatever, even moreso if it was me that first wrote about it -- but, since I'm under the impression that the settings aren't actually broken so much as they are being suppressed, is there a way to toggle these various developer options, including the OEM bootloader unlock, via adb?
(Another point in favor of suppression rather than breakage, the Oculus refuses to take a screenshot of anything I'm doing with a message stating that the device is forbidden from doing so, although in less nefarious language.)
tl;dr -- how might I go about programatically toggling developer options on the device to find out what happens? More broadly, what's a good place to start being more dangerous vis-à-vis my Android technical expertise? I find its structure in every way baffling and nightmarish.
And then just for kicks, there's some oddities, like how the machine name in adb shell comes back as "hollywood" (which I found a bit Baader–Meinhof-y, since I was watching a bunch of Modern Vintage Gamer vids including his one on the Wii and its "Hollywood"-benamed graphics coprocessor). Also, fastboot oem unlock returns a curious error directing the user to visit https://oculus.com/unlock, which doesn't exist, and as far as the Wayback Machine is concerned, has basically never existed.
This settings menu is (or at least it was) fully accessible on my Quest 1 last time I tried it. There does not seem to be an entry point on Quest 2 though.
I am currently enjoying the "Bugjaeger" app from the play store. That is a good ADB solution for the Quest 2. Have fun.
rickthecabbie said:
I am currently enjoying the "Bugjaeger" app from the play store. That is a good ADB solution for the Quest 2. Have fun.
Click to expand...
Click to collapse
Could you please elaborate? Link to any guides or anything?
dwkindig said:
I was just tooling around in my new Quest 2 and, while my level of technical expertise is sufficient to be dangerous, I don't have any real idea what I'm doing as far as rooting, bootloader mods, etc. However, I seem to have stumbled into the regular Android settings after an app I was trying asked for usage permissions, which it seems Oculus doesn't expect any of its bespoke apps to do.
The Android settings behave oddly, though, but more like there's some kind of watcher app that's preventing access to most of these non-Oculus options. Case-in-point, the app that wants usage access, when I enter the Usage permissions screen and select the app from the menu to be taken to the screen where it displays what the app will do with usage permissions and presents the toggle for it, the screen comes up only briefly before the settings dialogue disappears entirely with an error saying that "System has stopped responding". I'm pretty sure if I were fast enough, I could probably toggle it in time, but I could also try to grant those perms via adb (which I only now remembered I could do and thus haven't done yet).
I also found and enabled the actual Developer Options, not the basic one Oculus gives us if we sign up as a developer organization. I am certain that they have actually been enabled: Even though the "{ } Developer Options" menu item keeps reloading the page that its on, settings that you'd expect to find within now turn up in the settings search dialogue.
One of these options is to enable OEM bootloader unlock. Selecting that options from the search results screen (or any other search result you'd find within Developer Options) however does like before, drops you at the menu page with the "{ } Developer Options" option.
It would be absurd if it were to be as simple as enabling that option to gain access to the bootloader and do whatever, even moreso if it was me that first wrote about it -- but, since I'm under the impression that the settings aren't actually broken so much as they are being suppressed, is there a way to toggle these various developer options, including the OEM bootloader unlock, via adb?
(Another point in favor of suppression rather than breakage, the Oculus refuses to take a screenshot of anything I'm doing with a message stating that the device is forbidden from doing so, although in less nefarious language.)
tl;dr -- how might I go about programatically toggling developer options on the device to find out what happens? More broadly, what's a good place to start being more dangerous vis-à-vis my Android technical expertise? I find its structure in every way baffling and nightmarish.
And then just for kicks, there's some oddities, like how the machine name in adb shell comes back as "hollywood" (which I found a bit Baader–Meinhof-y, since I was watching a bunch of Modern Vintage Gamer vids including his one on the Wii and its "Hollywood"-benamed graphics coprocessor). Also, fastboot oem unlock returns a curious error directing the user to visit https://oculus.com/unlock, which doesn't exist, and as far as the Wayback Machine is concerned, has basically never existed.
Click to expand...
Click to collapse
Would you mind explaining how you got the settings page to open on the Quest 2? I am an OG root dev and just picked up a Quest 2 myself, would love to crack into this.
Oh, dang, yeah, sorry things have been mad hectic and I didn't see these responses. I'll provide a write-up tomorrow, ping me again if I don't reply later cause I'm a forgetful idiot.
dwkindig said:
Oh, dang, yeah, sorry things have been mad hectic and I didn't see these responses. I'll provide a write-up tomorrow, ping me again if I don't reply later cause I'm a forgetful idiot.
Click to expand...
Click to collapse
All good, I actually figured out how to launch the settings page from this command:
adb shell am start -a android.intent.action.VIEW -d com.oculus.tv -e uri com.android.settings/.DevelopmentSettings com.oculus.vrshell/.MainActivity
Everything works in this page, except for launching the Developer settings option. This crashes the app as you mentioned, even though I can see the OEM Unlock option in the settings search bar.
This repo is also very helpful, I am getting told to visit the same non-existent page you were as well when running fastboot oem unlock.
GitHub - QuestEscape/research: Sharing our security research on the Oculus Quest
Sharing our security research on the Oculus Quest. Contribute to QuestEscape/research development by creating an account on GitHub.
github.com
Honestly Annoying said:
All good, I actually figured out how to launch the settings page from this command:
adb shell am start -a android.intent.action.VIEW -d com.oculus.tv -e uri com.android.settings/.DevelopmentSettings com.oculus.vrshell/.MainActivity
Everything works in this page, except for launching the Developer settings option. This crashes the app as you mentioned, even though I can see the OEM Unlock option in the settings search bar.
Click to expand...
Click to collapse
Oh, cool, I spent some time myself looking for a similar command, but I don't know much about the inner workings of Android. Do you know if there's a way to programmatically toggle the OEM Unlock switch?
I'll still post my circuitous method of getting there tonight (US/Central), maybe it will be enlightening in some way. I can't take screenshots or video of the process, cause the security policy configured by Facebook disallows it in those places.
Honestly Annoying said:
This repo is also very helpful, I am getting told to visit the same non-existent page you were as well when running fastboot oem unlock.
GitHub - QuestEscape/research: Sharing our security research on the Oculus Quest
Sharing our security research on the Oculus Quest. Contribute to QuestEscape/research development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay, things are a bit different since when I first posted -- I can grant packages usage access without crashing back to Android settings (`com.android.settings`). However, I can launch Android settings directly using App Manager (https://muntashirakon.github.io/AppManager/). Still can't screengrab, though, and still can't access the Developer Options, can only search for them. Interestingly, the breadcrumbs in the search results refer to the uppermost level as `null`.
So i connected my Quest 2 to Android studio and used the debug and the log tool to see why the settings app crashes when trying to enter the developer settings. I got the exception and maybe i can paste it in here when i get home. Also i managed to sign out of my Facebook account and remove the oculus system administrator but that made the headset useless. I also created an app for the oculus that search for all the installed packages and when you click on one of them it's trying to launch the package in vr shell and found some interesting things such as a oculus assistant and a battery charging mode setting.
Honestly Annoying said:
This repo is also very helpful, I am getting told to visit the same non-existent page you were as well when running fastboot oem unlock.
GitHub - QuestEscape/research: Sharing our security research on the Oculus Quest
Sharing our security research on the Oculus Quest. Contribute to QuestEscape/research development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
maybe the page does exist, but you don't have the authority to visit it, so oculus redirect you to somewhere else
maybe its not helpfull, but when you start wireless wifi on the Q via a wired adb host , you can install the app 'remote adb shell' (blue cast icon, pstore) on the quest and connect to localhost. so you have an on device adb shell for pm commands. it has to be this remote app because of lack on adb shell command without magiskmodule (termux crashes to the tv channel). i dont know how the activitys are called in android so maybe you got luck. also are the developer options part of the settings.apk? i think they pulled it out like that so why not making a new settings.apk where the devops are available? on this way there is sure an option to have a lock on the wifi adb too so it doesnt shutdown anytime you reactivate. edit: seems that with the new multitasking feature, its possible to hold up a wifi connection even the hmd was locked, just run the remote shell, connect and dont close it. you can connect via pc too without need to use adb tcpip again. before i setup adb tcpip via ' setprop service.adb.tcp.port 5555 ' again on the remote shell app. i now let it locked, and look how long it can holdup the wifidebug without reactivating via cable.
raeumler said:
maybe its not helpfull, but when you start wireless wifi on the Q via a wired adb host , you can install the app 'remote adb shell' (blue cast icon, pstore) on the quest and connect to localhost. so you have an on device adb shell for pm commands. it has to be this remote app because of lack on adb shell command without magiskmodule (termux crashes to the tv channel). i dont know how the activitys are called in android so maybe you got luck. also are the developer options part of the settings.apk? i think they pulled it out like that so why not making a new settings.apk where the devops are available? on this way there is sure an option to have a lock on the wifi adb too so it doesnt shutdown anytime you reactivate. edit: seems that with the new multitasking feature, its possible to hold up a wifi connection even the hmd was locked, just run the remote shell, connect and dont close it. you can connect via pc too without need to use adb tcpip again. before i setup adb tcpip via ' setprop service.adb.tcp.port 5555 ' again on the remote shell app. i now let it locked, and look how long it can holdup the wifidebug without reactivating via cable.
Click to expand...
Click to collapse
.
if someone knows a working terminal for the quest (the original crashes the keyboard after a while). to replace the remote adb shell app, we could use an adb binary that holds up the wifi with adb shell to localhost (shell commands), while another terminal (local, pc or smartphone) can connect through the adb binary over wifi to localhost/quest-ip (for adb commands). but setting up an adb server (not the service) via adb binary and on-device terminal (even via adb shell) is not possible without root (but the remote adb shell app starts one or does it somelike different without root and on-device). when we know how we could put that logic together in a script or apk then). but anyways:
so its setted up now on my quest for holding up debug over wifi (sideload connection) and have an ondevice shell. it runs minimum 23 hours without needing to activate it via cable (adb device to check connection)
1. download/sideload remote adb shell app
2. connect quest2 to a host via usb
3. open cmd on host: adb tcpip 5555
4. disconnect usb
5. start remote adb shell on the quest and type quest-ip:5555 OR localhost:5555 and click connect
6. type in remote adb shell: setprop service.adb.tcp.port 5555
7. minimze the remote adb shell app and let it run
(8). to disable wifidebug: setprop service.adb.tcp.port -1
now there is no need for reactivating until reboot. if you want to run a command go to -> apps -> unknown sources -> open remote app (as there is no recent button).
you can connect to any adb host via wifi (local, pc, smartphone) even after lock or a matter of time (min 23 hours)
the remote adb shell app:
Remote ADB Shell – Apps bei Google Play
Eine Verbindung mit ADB auf einem anderen Android-Gerät läuft über das Netzwerk
play.google.com
with terminal shortcut app you can make settings-scripts then and run them via iconlist for textureresolution and gpu level or whatever ....
ps: maybe im in the wrong subforum now. should i make a thread?
pps: the app 'autostart and stay' adds an autostart option to the quest, which allows to run a launcher before original launcher comes up. (buggy)
ppps: the app SSH Server can set up a SFTP connection for wireless filetransfers
edit: could be that it just work to the first whyeverdisconnect then the quests tracking is beside and you have to reboot
double
Honestly Annoying said:
All good, I actually figured out how to launch the settings page from this command:
adb shell am start -a android.intent.action.VIEW -d com.oculus.tv -e uri com.android.settings/.DevelopmentSettings com.oculus.vrshell/.MainActivity
Everything works in this page, except for launching the Developer settings option. This crashes the app as you mentioned, even though I can see the OEM Unlock option in the settings search bar.
Click to expand...
Click to collapse
This still works today! I have a Quest 2 running V35, and recently un-linked my Facebook and Oculus accounts. After finally getting my Quest 2 back up (still needed to use the old Oculus apk from an Android device and Quest 1 device selection), the timezone was off, so I used the above adb shell command to access settings, and changed the timezone fine.
I also changed the Device Name, although I'm unsure what ramifications that might cause later.
Edit: Don't change your Oculus account password after doing the FB account bypass. You'll break the log-in session, and have to factory-reset and start over.
you can have more settings when you use SetEdit (Settings Database Editor) from pstore. some props are editable, some need root.