Is there any one can help me?
I have a wireless connection stored on my ppc. This connection requires a security key. I don't know that key because my friend entered it for me. Now i want to know "what the key is".
asterix
there's a program called asteriks logger ( http://www.nirsoft.net/utils/astlog.html ) install it, open it and it will reveal the password behind the asteriks on your computer. Good luck with
Zhaan said:
there's a program called asteriks logger ( http://www.nirsoft.net/utils/astlog.html ) install it, open it and it will reveal the password behind the asteriks on your computer. Good luck with
Click to expand...
Click to collapse
I've tried it, but unsuccessfully. Can you show me?
asteriks
The asteriks logger works only on PC's . Sorry didn't noticed that your hidden key was on PPC............. Then I think it not possible with this program!! Sorry mate.
It lives in the registry at :
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WZCSVC\Parameters\Interfaces\######
###### will depend on the particular WiFi chipset driver in your phone.
Under this key are several keys of the form Static#nnnn where n goes from 0000 to 9999 and ActiveSetting which is acopy of the last active connection. The name of the SSID is visible in the key if you try to modify it. The WEP/WPA key is further in there somewhere, but here is the catch. It has been encrypted, and is not recognisable as such.
Can anybody else can cast any further light?
What's a good VNC or VNC-like client for the TP2? I've tried a few and all fail. I'm running realVNC server on my home computer, I know the IP and port, have the password set, etc.
· I try to connect with this VNC client and it does nothing (after clicking connect, nothing is running, no screen comes up) - http://www.cs.utah.edu/~midgley/wince/vnc.html
· I try to connect with this other VNC client and it just hangs in the background as a hidden process. No visuals. -
http://sourceforge.net/projects/dotnetvnc/files/
· Additionally I tried a different app instead of VNC, Omnipresence. It's made for the diamond but I was hoping it'd work for me. I ran the server on my PC, installed the cab on my phone, ran the app, and attempted to connect.. I get this lengthy error: "Error while connecting: An error message is available for this exception but cannot be displayed"... blah blah blah blah blah.
Also, the omnipresence zip contains a dll but no instructions on what to do with it. I dunno if it goes on my phone or PC or what. I have .net compact framework version 3.5 (or later) installed on my phone. I have .net framework 4 on my PC.
What will it take to get an exact representation of my desktop showing on my phone screen? Preferably one that doesn't have to be resized to the lowest possible resolution? Ideally one that allows for panning around on the desktop by sliding across the screen (as omnipresence seems to do)?
==========================================================
You don't have to read anymore, but I thought I should share the various bits and pieces I had to figure out to get remote desktop (not VNC but almost as good) running on WM 6.5 (connecting to windows 7)...
1. On the PC, click start, type remote in the search box, and choose the option that says allow remote access to your pc. Of the three options in the middle, choose the one that says allow connections from any version of remote desktop. Note: To change this settings you need to enable windows firewall. You may have made a habit of disabling it (it used to be a nuisance in XP)... to re-enable, click start --> type services.msc in the search box and click on the result. Go to the w's for windows firewall. Double click it, change the startup type to manual and click apply (unless it already is) then click start. OK to close.
2. If you normally login to windows with a blank password, (maybe skip the login process entirely) click start, type gpedit.msc, click the result, navigate to computer config - windows settings - security settings - local policies - security options and find the entry near the top: Limit local use of blank passwords etc. ...double click that and change it to disabled.
3. Not sure if it's strictly necessary, and some may balk at the idea, but you might choose to shut down the firewall once that settings in step one is changed. Same steps, except you click stop instead of start.
4. On the phone, start the client and type in your IP in the first blank. Make sure it's your external IP, i.e. the one you get when you visit this site: http://whatismyip.com . For the user name blank, use your windows user name. If you need to double check it (i.e. you automatically login and forgot) click start on your PC. It'll be at the top right.
5. On the phone, go to settings --> all settings --> connections --> connections and then go to the advanced tab, then select networks --> change both dropdown boxes to your phone's internet connection (in my case, Sprint. Possibly "My ISP" could work?)
6. Here's the dumb part that had me bashing my head against the wall. The phone's connection to the internet needs to be 'goosed' before remote desktop can work. You need to open your web browser and browse to any site. Possibly some other internet-using app would work. Once you load any site, you can exit the browser and finally... FINALLY connect.
7. Fire up remote desktop, change the options to your liking, click connect.
Got it going with some help from ppcgeeks. Also got VNC working. If anyone is having trouble, I recommend reading this post:
http://forum.ppcgeeks.com/htc-touch-pro-2/134014-remote-desktop-vnc-guide.html
hi!
in my work computer i can't login with the desktop app. i get the error "failed to connect server -23000". although i can't login the app can check for updates..
is there anything i can do? like changing some ports?
thanks
Sacob said:
hi!
in my work computer i can't login with the desktop app. i get the error "failed to connect server -23000". although i can't login the app can check for updates..
is there anything i can do? like changing some ports?
thanks
Click to expand...
Click to collapse
Hey Sacob;58210707,
I have about the same problem as Chrome cant fine the https://www.192.168.1.xxx:8890 (where xxx is my private 3
digit number.)
Have you tried the https://www.192.168.1.xxx:8890 (replace the xxx with your 3 digit numer before the 8890) listed on the page after Activate "FIND" page?
Should be done ONCE, and NOT popping up every time we login to airdroid.
And . . .
Can't connect via USB which would be the BEST of the ways to connect to Airdroid in the first place since we
1. wouldn't be transferring in the net using up battery that WIFI uses on both devices, android and pc.
and
2. Would be charging our phones, which is super biggy plus.
And. . .
When airdroid downloaded its very own new update today, it said that it couldn't install because of parsing something.
Ain't that a hoot?
And. . .
When I went on airdroid.com> signed in> and finally found an Icon called "Widgets" it went to a calendar and NO, (that is absolutely no,) way to get out of the calendar page,
Even frantically tapping the big "" X "" on the lower left of their "calendar" page.
Ctrl with Arrow Back didn't work either cause some web builder thought that key combo should be shut OFF.
So I had to completely log out and log back in, (username and password again,) to go to the page the mean little "Widgets" Icon was located.
So.. . . to sum up . .
The ONLY thing that works on this app, so far, is that I can use ONLY, is the on-board Android "Apps" part on my S3 itself, and NO way to communicate with my pc.
Which by the way was handled greatly with any Android File managers.
Where do we find support?
Thanks for this topic!
Team,
I have a nice S4 that is not used anymore so I started experimenting different stuff, there is not any warranty active so I tested the root/unroot, different images etc.
It all went well till I tried to start working with the wlan0 configuration. I tried all possibile solutions found around, on the busybox/term even if every command does not return an error nothing changes. I've tried differents apps they all claim is fine but nothing changes, even modifying the efs/wifi files does not have any result.
I tried rebooting after changes... the max I was able to achieve was turn off wifi, change the files, reboot, check max 02:00:00:00:00, turn on wifi... mac back to original.
Is there anyone can help me? is it a problem related to the image? or to the phone?
Thanks,
M
m.savazzi said:
Team,
I have a nice S4 that is not used anymore so I started experimenting different stuff, there is not any warranty active so I tested the root/unroot, different images etc.
It all went well till I tried to start working with the wlan0 configuration. I tried all possibile solutions found around, on the busybox/term even if every command does not return an error nothing changes. I've tried differents apps they all claim is fine but nothing changes, even modifying the efs/wifi files does not have any result.
I tried rebooting after changes... the max I was able to achieve was turn off wifi, change the files, reboot, check max 02:00:00:00:00, turn on wifi... mac back to original.
Is there anyone can help me? is it a problem related to the image? or to the phone?
Thanks,
M
Click to expand...
Click to collapse
If you are getting problem in Macoptimizer you can perform following steps:
Open up settings and then go to WiFi.
Now, you will see gear on the top of this screen, click it. But if you don’t see it, look for “Configure WiFi” option and click it. Some Android system have Advanced option in WiFi, MAC address can be found there also.
You can find the MAC address on the bottom of this screen. Keep a note of it.
In order to get the interface name, you will have to install Terminal Emulator for Android. Go to Google Play Store and download it or click the link to get it.
Then open it and type the following command : ip link
You screen will be filled with lot of information, useful and useless. Now, remember I told you to keep a note of your MAC address. Just look for this MAC address under “link/ether” for all the cases.
The one that matches our MAC address, is the connection name. For most of the devices it is either “wlan0” or “eth0”.
Now, that we know our MAC address and the connection name, we can go on to change the MAC address with this terminal emulator only. Before that you should have a valid MAC address in your mind or generate one from this link. Once, you have a new MAC address, just get on with the below steps:
Launch the Terminal Emulator
Just type the following command: ip link set wlan0 address XX:XX:XX:YY:YY:YY, where wlan0 is the name of the interface and XX:XX:XX:YY:YY:YY is the MAC address you want to set.
Important thing to keep in mind that the manufacturer name should be kept unchanged while changing the MAC address i.e. XX:XX:XX (first 6 digits) should be same as before, otherwise you might face a lot of authentication issue.
This is only a temporary change and when you restart your device, your previous MAC address will be retrieved back."
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.