basti564 / Oculess

Removes account requirements and telemetry from Oculus Quest devices
The Unlicense
1.81k stars 75 forks source link

Cannot run Device Owner set adb command, even after removing all accounts from inside oculess, ive never had account sharing enabled #33

Closed RUGMJ closed 1 year ago

TheKing349 commented 2 years ago

You have to delete the accounts you added onto Oculus, not just from the Oculess remove account screen. If you signed in from another person's facebook/oculus account to get their account, and still have their account on your oculus, you have to remove their account, then remove the other accounts from inside Oculess

yodaluca23 commented 2 years ago

This is also happening to me, I get this error report:

Error: Command failed: "C:\Users\yodal\AppData\Roaming\SideQuest\platform-tools\adb.exe" -s 1WMHHB61UJ1432 shell dpm set-device-owner com.bos.oculess/.DevAdminReceiver java.lang.IllegalStateException: Not allowed to set the device owner because there are already some accounts on the device at android.os.Parcel.createException(Parcel.java:2046) at android.os.Parcel.readException(Parcel.java:2006) at android.os.Parcel.readException(Parcel.java:1954) at android.app.admin.IDevicePolicyManager$Stub$Proxy.setDeviceOwner(IDevicePolicyManager.java:8392) at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:203) at com.android.commands.dpm.Dpm.onRun(Dpm.java:115) at com.android.internal.os.BaseCommand.run(BaseCommand.java:65) at com.android.internal.os.BaseCommand.run(BaseCommand.java:49) at com.android.commands.dpm.Dpm.main(Dpm.java:41) at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:338) Caused by: android.os.RemoteException: Remote stack trace: at com.android.server.devicepolicy.DevicePolicyManagerService.enforceCanSetDeviceOwnerLocked(DevicePolicyManagerService.java:8653) at com.android.server.devicepolicy.DevicePolicyManagerService.setDeviceOwner(DevicePolicyManagerService.java:7822) at android.app.admin.IDevicePolicyManager$Stub.onTransact(IDevicePolicyManager.java:3270) at android.os.Binder.execTransactInternal(Binder.java:1021) at android.os.Binder.execTransact(Binder.java:994)

TheKing349 commented 2 years ago

The error is fixed by removing any accounts you have on your device, hence what I said above

yodaluca23 commented 2 years ago

The error is fixed by removing any accounts you have on your device, hence what I said above

I did that with the Oculess app but it still does not work.... I followed the video's instructions exactly...

Kirottu commented 2 years ago

I am unable to set the device owner either, even after removing all accounts from the "remove accounts" menu. It gives the same error.

Edit: The OS version is v37

RUGMJ commented 2 years ago

@TheKing349 You have to delete the accounts you added onto Oculus, not just from the Oculess remove account screen. If you signed in from another person's facebook/oculus account to get their account, and still have their account on your oculus, you have to remove their account, then remove the other accounts from inside Oculess

If you read the title, I stated that I had never had account sharing enabled

ShakaBrock commented 2 years ago

having the same issue with the same output error message. Even when i go to my main accounts page on my quest 2. It only shows my account as the admin with no option to remove my account. So there is no other way to 'remove' my accounts other than from within oculess. I'm at a loss

lonelycherry commented 2 years ago

i'm having the same issue, however i can't remove the second account on my oculus because it's one that's also used frequently and i don't want to lose everything from that account. my account on the oculus is the device admin, and i removed both the oculus account and facebook account from mine and when i go back into SideQuest to try and run the command, it just keeps giving me the error message

RUGMJ commented 2 years ago

having the same issue with the same output error message. Even when i go to my main accounts page on my quest 2. It only shows my account as the admin with no option to remove my account. So there is no other way to 'remove' my accounts other than from within oculess. I'm at a loss

Same here

BrianGilbert commented 2 years ago

I removed all accounts using Oculess as per https://youtu.be/aMnHgz2Zo3E?t=76, error shown when I run ADB command:

Error: Command failed: "/Users/brian/Library/Application Support/SideQuest/platform-tools/adb" -s 1WMHH86DG41234 shell dpm set-device-owner com.bos.oculess/.DevAdminReceiver java.lang.IllegalStateException: Not allowed to set the device owner because there are already some accounts on the device at android.os.Parcel.createException(Parcel.java:2046) at android.os.Parcel.readException(Parcel.java:2006) at android.os.Parcel.readException(Parcel.java:1954) at android.app.admin.IDevicePolicyManager$Stub$Proxy.setDeviceOwner(IDevicePolicyManager.java:8392) at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:203) at com.android.commands.dpm.Dpm.onRun(Dpm.java:115) at com.android.internal.os.BaseCommand.run(BaseCommand.java:65) at com.android.internal.os.BaseCommand.run(BaseCommand.java:49) at com.android.commands.dpm.Dpm.main(Dpm.java:41) at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:338) Caused by: android.os.RemoteException: Remote stack trace: at com.android.server.devicepolicy.DevicePolicyManagerService.enforceCanSetDeviceOwnerLocked(DevicePolicyManagerService.java:8653) at com.android.server.devicepolicy.DevicePolicyManagerService.setDeviceOwner(DevicePolicyManagerService.java:7822) at android.app.admin.IDevicePolicyManager$Stub.onTransact(IDevicePolicyManager.java:3270) at android.os.Binder.execTransactInternal(Binder.java:1021) at android.os.Binder.execTransact(Binder.java:994)

Oculess version: Oculess v1.3.2 Quest System Version: 22310100587300000 Version 37.0.0.147.109.3463379382 Runtime Version 37.0.0.147.110.346379395 OS Version: user-22310100587300000

yodaluca23 commented 2 years ago

Same problem here, so far only solution seems to be factory reset... if u wanna do that...

[https://res.spikenow.com/c/?id=njmx19njiu20eyx4&s=48&m=c&_ts=1fo4tb] HotMailhttps://spikenow.com/r/a/?ref=spike-organic-signature&_ts=1fo4tb [1fo4tb]

From,

Luca LeBlanc

On February 22, 2022 at 3:50 GMT, Brian Gilbert @.**@.>> wrote:

I removed all accounts using Oculess as per https://youtu.be/aMnHgz2Zo3E?t=76, error shown when I run ADB command:

Error: Command failed: "/Users/brian/Library/Application Support/SideQuest/platform-tools/adb" -s 1WMHH86DG41234 shell dpm set-device-owner com.bos.oculess/.DevAdminReceiver java.lang.IllegalStateException: Not allowed to set the device owner because there are already some accounts on the device at android.os.Parcel.createException(Parcel.java:2046) at android.os.Parcel.readException(Parcel.java:2006) at android.os.Parcel.readException(Parcel.java:1954) at android.app.admin.IDevicePolicyManager$Stub$Proxy.setDeviceOwner(IDevicePolicyManager.java:8392) at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:203) at com.android.commands.dpm.Dpm.onRun(Dpm.java:115) at com.android.internal.os.BaseCommand.run(BaseCommand.java:65) at com.android.internal.os.BaseCommand.run(BaseCommand.java:49) at com.android.commands.dpm.Dpm.main(Dpm.java:41) at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:338) Caused by: android.os.RemoteException: Remote stack trace: at com.android.server.devicepolicy.DevicePolicyManagerService.enforceCanSetDeviceOwnerLocked(DevicePolicyManagerService.java:8653) at com.android.server.devicepolicy.DevicePolicyManagerService.setDeviceOwner(DevicePolicyManagerService.java:7822) at android.app.admin.IDevicePolicyManager$Stub.onTransact(IDevicePolicyManager.java:3270) at android.os.Binder.execTransactInternal(Binder.java:1021) at android.os.Binder.execTransact(Binder.java:994)

Oculess version: Oculess v1.3.2 Quest System Version: 22310100587300000 Version 37.0.0.147.109.3463379382 Runtime Version 37.0.0.147.110.346379395 OS Version: user-22310100587300000

— Reply to this email directly, view it on GitHubhttps://github.com/basti564/Oculess/issues/33#issuecomment-1047398806, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQAX2V2EPHJNMXD54D3ARITU4MBWNANCNFSM5O3S2EHA. You are receiving this because you commented.Message ID: @.***>

[https://bolt.im/t/?Y7WWqyyCjD2iBy4g4wg3w11f-ZjXwb50n1lSDCZ3qqKzuaUAIyMXQnjJvvNL9AGsZ9sa_S9huP-UMIo57qb4ig]

BrianGilbert commented 2 years ago

I can confirm factory reset of Quest 2 resolves this problem.

Kirottu commented 2 years ago

If factory reset does indeed fix the issue, is there any way to backup installed apps/games and their data?

BrianGilbert commented 2 years ago

If factory reset does indeed fix the issue, is there any way to backup installed apps/games and their data?

Maybe if you have cloud saves enabled it will all come back after the reset?

Kirottu commented 2 years ago

One game has cloud saves yes, others not so much.

BrianGilbert commented 2 years ago

Sidequest has a way to backup and restore games, not sure if that will include save states or not though

BurntTOEst commented 2 years ago

I had the same problem I just deleted apps I don't use often and it worked!

Kirottu commented 2 years ago

What kind of apps did you uninstall?

BurntTOEst commented 2 years ago

What kind of apps did you uninstall?

I uninstalled things like poker, remote desktops, and streaming services, anything with 3rd party accounts linked that I don't use very often

vinists commented 2 years ago

I uninstalled BigScreen and Prime Video and it worked! Thanks for the tip @BurntTOEst

You mentioned streaming services, did you have Prime Video as well? Could it be the culprit?

BurntTOEst commented 2 years ago

I uninstalled BigScreen and Prime Video and it worked! Thanks for the tip @BurntTOEst

You mentioned streaming services, did you have Prime Video as well? Could it be the culprit?

I'm so glad I could help! I did! I had both but I bet you're right Although I'm sure there's a lot of different apps that could cause a problem too

yodaluca23 commented 2 years ago

I uninstalled BigScreen and Prime Video and it worked! Thanks for the tip @BurntTOEst

You mentioned streaming services, did you have Prime Video as well? Could it be the culprit?

OMG IT IS!!! PRIME VIDEO IS THE CULPRIT I HAD THE FOLLOWING APPS INSTALLED:

Prime video VR Oculus Store Oculus Browser Oculus File Viewer Oculus TV Beat Saber LIV (App-Lab) Vader Immortal (1-3) VR Chat Oculus Move Facebook Recroom Youtube VR Couch (App-Lab) Gorilla Tag (App-Lab) Explorer Alcove Ariko (App-Lab) Half Half Echo VR Oculus Setting Oculus Score Jurassic Park Big-Screen Oculus Files Oculus Events Gravity Sketch Horizon Venues Facebook Watch Oculus Voice Commands Oculess (Side-Load) Discord (Side-Load) Pojav Launcher (Side-Load)

I WAS GETTING THE SAME ERROR AS ALL OF YOU BUT THEN!!! I UNINSTALLED PRIME VIDEO AND TRIED IT AGAIN AND BOOM!!!! THE COMMAND WORKED

Althexia commented 2 years ago

Okay so... What do I do when I don't have Prime Video installed? lol. I'm at loss here. I'm on v37 and deleting the accounts via Oculess works, but then the command fails.

solarblossom commented 2 years ago

Okay so... What do I do when I don't have Prime Video installed? lol. I'm at loss here. I'm on v37 and deleting the accounts via Oculess works, but then the command fails.

Try uninstalling any and all streaming apps you have, like Youtube, Netflix, Big Screen, etc. After i uninstalled those apps i rebooted my oculus, removed the 2 other accounts in oculess and tried it again and it actually worked

reynonic commented 2 years ago

Can confirm removing Prime Video worked for me. Didn't have to touch Netflix or Big Screen. Thanks for the info all!

Emily42069 commented 2 years ago

It's not working with me as well when I try i get this

hollywood:/ $ adb shell dpm set-device-owner com.bos.oculess/.DevAdminReceiver pm set-device-owner com.bos.oculess/.DevAdminReceiver <

/system/bin/sh: adb: inaccessible or not found 127|hollywood:/ $

MightyOcelot commented 1 year ago

Don't forget to remove accounts from INSIDE Oculess itself... Had the same issue, but thought it was removing all accounts on the headset that was supposed to fix it... don't laugh... but annoyed, I scrolled though the oculess settings (the window u sometimes get after hitting 'remove all accounts', saw the accounts tab, entered it, thought 'man, im stupid,' removed accounts there, ran the command again, and that fixed it. Hope this helps some other poor fools like myself :)