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.
Related
Little bit of background first...
Finally got my parents (senior citizens) into the smartphone era after StraightTalk starting doing BYOP and I'd had good service so far, but rather than use his old HTC phone which badly needed replacing, he opted to buy the Huawei Sensa (H710VL) branded by TRACFONE and with service via StraightTalk. Fast forward several months, and the old man has discovered a deal for senior citizens from T-Mobile that he likes better, and has opted to switch carriers. Well, he tried to do BYOP with TMOUS and just continue using the H710VL which he likes, but was informed that they wouldn't unlock the phone for another month because they won't do so until you've had it for a year. So therein came my opportunity to promise something I apparently cannot deliver (I told him I'd take the phone home and unlock it for him)!) He (wisely) decided not to wait for me, and went ahead and bought a new phone from TMOUS so he could initiate his new service with them without delay. But I still want to unlock this phone for him, if at all possible!
Fast-forward a few more days--well, I've been screwing around with this phone in the evenings for the past three days, trying to get the bootloader unlocked, and I'm at an impasse. First I had to tangle with the Google account verification, which wouldn't let me even sign into the phone after boot and get to the home screen because I had done a hard reset of the phone first, and didn't have the old man's Google account and password with which to sign back in. Fortunately, intrepid folks who came before me already found a way around that first hurdle. I took the following steps:
1. Went thru HWStartupGuide process until I was able to connect to my home WiFi network. So, internet connection is established.
2. Backed out of there to get to the first setup screen after the TRACFONE splash screen on boot, and used the "emergency calls only" escape hatch to navigate to the stock dialer app.
3. In stock dialer app, entered (without the quotation marks) "*#*#6130#*#*" which took me to the SIM Card Settings screen. Tapped three-dot menu, tapped, "Add SIM Contact," which took me to the native Huawei Contacts app. In Contacts app for the SIM card, tapped "Add Contact," made dummy contact called "Test" with a ph# of 1234. From list of contacts, tapped the "message" bubble icon next to the new "Test" contact, which opened the stock Messages app.
4. In stock Messages app, typed and sent message with the text "www.youtube.com." For obvious reasons the message doesn't send, but it does appear in the messages window, which renders the draft text's content into a hyperlink to YouTube. Bingo! Tapped link and opened up the YouTube app.
5. From the YouTube app, tapped the three-dot menu again, and tapped Privacy Policy from there. Now I'm into Chrome! Opened Chrome without signing in, and navigated to Google.com.
6. From Google.com, searched and then downloaded apk for Test DPC app. Installed Test DPC and set myself up as the new device owner.
7. Now that I'm the device owner, you'd think it would bypass the Google account verification requirement in HWStartupGuide, but no dice. So, rebooted, took same steps to get back into Chrome. From Chrome, I was able to get to the stock Google device search and navigate to the Settings app.
8. From device Settings app, changed settings to allow installations from unknown sources, then I set the option to allow USB debugging, and opened up the dev options to select "Allow OEM Unlock" in preparation for unlocking the locked bootloader, using the unlock code previously sourced from the official Huawei EMUI unlock code site.
So, to sum up, I've got access to the device in general, can use the web and all the apps on the device, and was thus finally able to disable HWStartupGuide to prevent the previous headache from cropping up again. Here's where the impasse starts.
I have Android SDK and everything I need on my laptop (to the best of my knowledge) to facilitate unlocking, flashing, and all the other fun stuff we love to do with our phones.
I was able to confirm the USB and Android drivers are correct and working fine, as I got both fastboot and adb to recognize and list the device when connected via USB cable to the laptop, and it worked both in command prompt and in PowerShell. Fastboot and ADB commands appear to work when facilitated and entered correctly. That is...UNTIL I tried to use the "fastboot oem unlock <unlock code here>" command. It just says "FAILED" with no error code. I tried this from my stock boot options screen (the screen you get when you boot or restart with power and vol-down pressed), and from the stock recovery screen, both to no avail.
This is where I'm all twisted up. There either doesn't appear to be a true bootloader screen to navigate to, or it's purposefully inaccessible, and I don't know how to get to it. If you do a "adb reboot bootloader" command, it just reboots the phone to Android home screen. The only options from the boot options screen are "Power (turn phone off), "Start" (boot to Android home screen), "bar codes" (screen that shows bar codes for the phone's IMEI, Serial #, etc), and "reboot recovery" (stock EMUI recovery screen), where the only options are 'Wipe/Factory Data Reset," "Wipe Cache," and "Reboot."
I feel like if I could get to a true bootloader screen that allows me to enter adb or fastboot command strings in such fashion that you can enter it and then see the process play out on your device screen, then the unlock code from Huawei would probably work and the bootloader would be unlocked, thereby allowing me to root and flash a better ROM, or at least eliminate bloatware and optimize the device for performance. But for whatever reason, and I assume it's purposeful on the part of TRACFONE/StraightTalk, tbh, there isn't a fastboot-capable bootloader screen like my years of using HTC phones taught me to take for granted.
So there I be...stuck, even WITH the unlock code from Huawei! What a crock! I know TMOUS will apparently unlock it in a month or so, but to me, that's not the point. I should be able to accomplish it on my own with the unlock code I got from Huawei. And that's why I'm throwing my hands up and begging for help.
Is there anything else I can try? Is there any other devious way to perhaps flash a different bootloader interface onto the phone that would allow me to use fastboot commands properly? Is it possible to mount the SD card from bootloader and push an apk to it that would install some kind of generic bootloader screen? I'm now a little out of my league, but I am willing to try just about anything that anyone thinks might work. Any advice or suggestions warmly welcomed...not worried about bricking the phone or anything, as it's not much better than a paperweight in its current form anyway.
Thanks!!
smb282
I wrote the method in 1 II for your reference.
The Qualcomm Diagnostic Port command in Xperia 1&5 is as follows.
(setprop sys.usb.config rndis,eng_mode,adb)
And use the EFSTOols.exe program.
It's easier than I mk2.
Screenshot is
1&5 and 1 MK2
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier
Sorry, this is Korea and I am Korean.
However, I will write down the method in English.
Unlike previous 1&5, Qualcomm's diagnostic port cannot be opened.
opening command
I don't even know. I don't think so.
So it's a little different from before.
I tried to force it open.
debugging connection
Open the Command Proposal window.
adb shell input
su input
Do you want to allow shell on your phone?
prompt acceptance of permission
Then the $ shape changes to #.
Now
setprop persist.usb.eng 1
Copy paste entry. Please enter
And you're gonna be out there during tethering.
In My Computer Item
View Device Manager.
Please turn debugging back on.
Of course, no access.
If you turn on debugging again,
I've already set it up, so it looks like that.
Among them, there is a product model named XQ-AT52.
There are four yellow exclamation points in total.
Manually update driver Press [port] to list the manufacturers
It's called Qualcomm hs-usb-diagh and 9091. with this
I need a manual update. gogo
Now run the EFS Express.
Press 0 on the ROW and OK.
(ROW or SF_Default)
Oh, it takes a long time. I thought it stopped.
It opens if you stay still. LOL
It's open. How nice to see you here!
I am the Korean telecommunication company EFS file extracted from xperia1.
I used it. If you need VOLTE,
XPERIA1 (Modem).Extract from SIN file
I will use the Korean communication file.
Just drag it and put it in a folder.
v check and Yes
There'll be folders that don't exist while you're pulling them in.
Then make it and put the file in.
In the folder where you can view this red file,
Drag and drop the file twice.
The reason is that once you do it, you just go in.
The red file is not updated.
That's how the numbers at the back change when you renew.
So make sure to put it in twice.
Files beginning with NV do not have folders.
Put it on top.
It's over now!
Volte Success ^0^ About IMS
VOLTE OK
Confirm Video Calls
It was such a hard time for me!
I was sad because I couldn't get help.
With 5G mobile phones in 2020,
It was terrible to be on the 3G phone.
If there's someone like me,
This information will help you a lot.
Finally, Marktu
Buy! Buy two! I love it.
Interesting. I wonder if the OpenDevice Modem on AOSP works without that Hack in the same Way. Would be cool to know... Pixel Experience for Example enabled VoLTE, Wifi Calling and Video Calls over Carriers on My Xperia 5 without any additions or extra work. It detects the SIM and loads the needed Configs for it on the Modem. Pretty handy hack from the SONY Community to get extended functionality over AOSP or GSIs
Hello there and thank you for your patience, I had previously considered myself smart until yesterday. You see I'm new to all this, just a bb, but I find it fascinating.
So I sold my phone pixel 3 to someone who want to have lineageOS on google Fi and wants to make sure the OEM is unlocked. Phone has sim card slot
Not knowing anything I looked it up completed the steps to get developer options, OEM greyed out, ok so I proceed to look up articles and videos, finally found what seems to be a legit solution here
https://forum.xda-developers.com/pi...izon-pixel-t3796030/post83674835#post83674835
after downloading more software than I needed and making several attempts to access the adb command prompt on my macbook pro, I decided to borrow my friends pc to try and do it
Downloaded https://developer.android.com/studio/releases/platform-tools platform tools, unzipped, shift right click in folder, no command window option
I decided to after following the instructions on the phone, just hit the up volume key and power to turn it on, it says "no command" I'm guessing because I dont have the window up and cant seem to figure out how to get it up
Now I'm. back on my macbook pro and I'd like someone to please help me, preferably on macOS but I'll take any help I can and go back to my friends broken pc if I have to (touch screen broken and keyboard doesnt work, I got a keyboard, but the broken touch screen goes crazy and it's really frustrating.
Anyway sincere gratitude to anyone who can help me as I am desperate
Update: went back to pc unzipped platform tools, shift right clicked and there was an option for powershell window, however it did not recognize any adb commands :/
Nadia927 said:
Hello there and thank you for your patience, I had previously considered myself smart until yesterday. You see I'm new to all this, just a bb, but I find it fascinating.
So I sold my phone pixel 3 to someone who want to have lineageOS on google Fi and wants to make sure the OEM is unlocked. Phone has sim card slot
Not knowing anything I looked it up completed the steps to get developer options, OEM greyed out, ok so I proceed to look up articles and videos, finally found what seems to be a legit solution here
https://forum.xda-developers.com/pi...izon-pixel-t3796030/post83674835#post83674835
after downloading more software than I needed and making several attempts to access the adb command prompt on my macbook pro, I decided to borrow my friends pc to try and do it
Downloaded https://developer.android.com/studio/releases/platform-tools platform tools, unzipped, shift right click in folder, no command window option
I decided to after following the instructions on the phone, just hit the up volume key and power to turn it on, it says "no command" I'm guessing because I dont have the window up and cant seem to figure out how to get it up
Now I'm. back on my macbook pro and I'd like someone to please help me, preferably on macOS but I'll take any help I can and go back to my friends broken pc if I have to (touch screen broken and keyboard doesnt work, I got a keyboard, but the broken touch screen goes crazy and it's really frustrating.
Anyway sincere gratitude to anyone who can help me as I am desperate
Update: went back to pc unzipped platform tools, shift right clicked and there was an option for powershell window, however it did not recognize any adb commands :/
Click to expand...
Click to collapse
I know nothing about macbooks, but according to this article you have to change some system settings to open a terminal window.
https://www.groovypost.com/howto/op...nal-window-specific-folder-windows-mac-linux/
Can you open a terminal window in any folder? If so, just do a cd command to the platform-tools directory.
Regarding your powershell window, it sounds like you are not in the platform-tools directory. Do a dir command. Do you see the adb file? If so, try ./adb. If not, do a cd to the platform-tools directory.
Do you have a Verizon branded phone? If so, you probably cannot unlock the bootloader. The link you pointed to is for a Pixel, not a Pixel 3.
If your OEM button is grayed out you are done, you can't unlock that phone.
Hi All,
Apologies, this is my first post, I cracked something trivial, but didn't find the steps or the same situation anywhere, so posting my version of events. This guide is based on the following situation
Bought a Google Pixel 3 XL - CARRIER LOCKED phone off ebay (Locked to EE)
- Running Android 10 - working fine - pre wiped
- EE SIM installed
- Wifi Connected
- Based in the UK
- I need to root this phone to perform security testing
So, for me, because the phone is locked to EE, when I did tried to enable OEM unlocking in dev options, I got the dreaded OEM unlocking unavailable on carrier locked devices.....:
Details:
Enable DEVELOPER MODE
SETTINGS > ABOUT PHONE > Hit “Build Number“ 7 times > Enter your pin/pattern
Go To Enable OEM Unlocking
SETTINGS > SYETEM > ADVANCED > DEVELOPER OPTIONS > OEM UNLOCKING option
However,
You end up with “OEM unlocking unavailable on carrier locked devices” and the option greyed out and disabled (Silent sobbing in the corner by my wallet)(See attached my mocked up screen shot of this)OEM unlocking is step 2 of every rooting tutorial I’ve seen (the 1st being DEV OPTIONS!) (Silent sobbing in the corner by me!)
Reading many forums, all hope was lost, lots about Verizon phones, and specific IMIE numbers called out for versions to watch out for, blah blah until a passing comment about getting the Carrier (EE) to unlock.
EE do this for FREE if YOU bought the phone from THEM….or they charge £8.99 for 2nd hand phone unlocks
1) So, call EE on 150 (UK)
2) Give them the IMIE number of the phone
SETTINGS > ABOUT PHONE > IMEI number
3) They fill out a form and send to their back office “unlock team”
4a) Short Story – I called back and was advised to update my phone...the end
4b) Long Story - I was told this would take 24 hrs, and they would send me an email with instructions…this never arrived, so I called back, only to be told there was a back log and it would take 1-10 days!! 5 days later, no email, no codes, no love! so I called back begging for an escalation, I was told there was a note on the account saying it was done! and the phone just needed an update….(no code, no email, no call, if I was waiting at a restaurant for you EE, I'd of left!)
5) Next update Android to the very latest version
SETTINGS > SYSTEM > ADVANCED > SYSTEM UPDATES6) Wait the age for it to install and “optimize” the apps
7) I checked for more updates, found “A security patch”, went through the process again….7 more times! (took me a couple hours!)….I repeated this process until there were no more updates to collect (back to step 5 you go!)
8) Check:
SETTINGS > SYETEM > ADVANCED > DEVELOPER OPTIONS > OEM UNLOCKING option = still locked for me at this point.
9) Perform a FACTORY RESET
SETTINGS > SYSTEM > RESET OPTIONS > DELETE ALL DATA (FACTORY RESET)10) Let it Reboot
11) Re-set up
Enable DEVELOPER MODE...againSETTINGS > ABOUT PHONE > Hit “Build Number“ 7 times > Enter your pin/patternGo To Enable OEM Unlocking...againSETTINGS > SYETEM > ADVANCED > DEVELOPER OPTIONS > OEM UNLOCKING option
BOOM! OEM unlocked! (for me at least)
Long oand short of it - get EE to unlock and confirm > update the [email protected] out of the phone > perform factory reset
I hope these saves time for someone out there
D2
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.
Hello, I just broke the screen of my OnePlus8t Verizon network unlocked phone. The computer I previously linked 8t with also has a broken screen. ... Rains it ..... My Phoe has some important information in docs and screenshots I need to get. I just turned off ADB debugging thinking "Oh I don't need that just yet" the very morning I broke the LCD. Good news, I can still answer it. I already have adb.exe except in ADB shell it shows as unauthorized. I need those files like yesterday. I have an otg/ADB flash drive, but I still can not connect to retrieve files. I can see my phone when I directly connect to comp without the flash drive, however, I can not access it. I have tried to put the phone into recovery, but I have no way to enter the pin as I have tried to guess where it is. How can I receive the data I need from my phone?
Thank You.
P.S. I have little knowledge and only learn what I need to know for whatever project, in other words, I can not code and I barely speak dos.
Is the touch screen still working then?
If it's showing "unauthorized" you can try to plug it into your desktop and then hit the "authorize" button on the popup that you can't see.
Here is where ok is on a different phone. It's somewhere near there on yours.
Renate said:
Is the touch screen still working then?
If it's showing "unauthorized" you can try to plug it into your desktop and then hit the "authorize" button on the popup that you can't see.
Here is where ok is on a different phone. It's somewhere near there on yours.
Click to expand...
Click to collapse
I have tried that. The finger print unlock screen only works ⅔ of the time. I have no way of knowing if it's unlocked. I keep my touch sounds silent. I keep trying to find where it might be. I have tried to slide as if answering a call. Is there a way to force the USB settings for media transfer? Maybe through Google? If any platform knows it's my phone is Google. I can go to the play store and push apps onto it. Unfortunately the two adb drivers I have installed on my Android didnt work.
Oh, actually, you've got it easier! The OnePlus 8t supports HDMI over USB Type C.
https://forum.xda-developers.com/t/does-one-plus-8t-have-video-out-through-usb-c.4465629/
Buy an adapter and hook up an HDMI monitor/TV.
Or just use a new monitor on the computer that is already authorized.
Is there any other way. Right now it is not with in the budget to afford any extras even with the price tag of $20. I am hoping there is a way within an adb shell to force turn on the adb debugging. I have developer options enabled. I would just rewrite the documents, except some of those items I need include the text messaging history. If I can't force the adb, can I remotely back up the phone? Is there a trustworthy app for that? I do have quick settings installed and if my memory is correct, I believe I have sideline installed even.