I updated my phone to 4.3, and since then the problem of changing the locale is annoying me. How do I change it? It's asking to use the "pm" command, but I can't find it how to use it. I learned that there is a way to add a permission to change the locale from ADB Shell, but when I connect my phone, nothing happens. I can't find a good starting point, can't find good documentation on how to connect my phone to change the permission from command prompt. I tried Better Terminal, but it didn't help. Please, people, I need your help. In case I won't be able to find how to unlock it, I'll have no other choice but to root my phone in hope MoreLocale will be able to get the permission by itself. And in case the phone would get bricked, I'll be blaming Google for ruining my phone.
Related
Hello,
I was given a Galaxy Wonder to repair, the problem is the kid who's phone it is, forgot the lock screen password/code nor did he have a google account on the device. And the best part, is he want's the data!
I would backup and flash the device, but adb commands requiring root privileges won't work directly - it complains that "adbd cannot run as root in production builds"...
I got ADB up and running and installed "su" (root privileges in shell).
I've tried many suggestions with changing and deleting entries in the "data/data/com.android.providers.settings/databases/settings.db" file on the device.
There are no more references left in the "system" or "secure" tables to any kind of "locking". According to many posts the lock screen should not be present after reboot or it should be anything random (or nothing).
Also, I've deleted the gesture and password files from /data/system/...
Nothing has worked to remove the screen lock. Please help.
~confuded
My father in law died last weekend and we don't know the pincode of his stock Nexus 5X. We can access his Google account and we know the pincode of his sim card. I hope someone can help us out to get access to his phone. Things we've tried:
- The vingerprint reader was setup but we've tried a lot of possible pins. We've tried his vinger yesterday but because of the attempts the pin is also required now.
- With a pattern lock you'll get a possibility to unlock through the Google account password after some attempts but his phone was secured with a vingerprint and/or pincode. Only the delay between attempts get increased, currently 16 minutes between them.
- The lock option from https://www.google.com/android/devicemanager, but because there is already a pin lock it doesn't work. The pin doesn't change.
- I've tried to access the phone through ADB, booted into the recovery but "adb devices" doesn't see the phone. When I choose to "install update through adb" I see the devices with "adb devices" but I can't use "adb shell", only sideloading works.
- Installing a custom recovery could work but the bootloader is locked, when I unlock it a full wipe will be performed so we still can't access the data.
- From the Play store in the browser on my Mac I've installed the androidlost.com app on the phone, but the app needs to be opened once before it can be used.
- A rubber ducky could help us out, but I don't have one and the time between attempts get increased and increased... it would take weeks, months or years to unlock.
What other possibilities do I have?
First sorry for your lost!
Second, i don´t know for sure, but maybe get the phone to the store where you bought it and explain the situation, maybe they will give a correct advice or like you said the phone is registed in google ( device manager) maybe if you contact them they will help you with that ( the problem is they probably will take a long time to reply or don´t reply at all) or wait for a more expert user than me here in xda,
again, sorry for your lost and hope you solve this problem,
cheers
If the phone was rooted with a recovery installed, YES, you could delete the passcode files and get into it, without root/recovery, you cannot get into it without the password, that is the point of encryption and passwords and all that jazz.... Yes there is probably a way for some high level hacker to do it but good luck finding that.... If you just want to be able to USE the phone, do a factory reset from recovery....
I've had this phone for a few months now and have tried finding a way to root. I have found some tricks that haven't been posted before. Hopefully this will lead to something for everyone using this phone. Anyway here's what I've found. We can enable diag port without the MSL using an app called anycut by opening the app, click make shortcut, choose activities and find the one named diag. There are 2 so if the first one asks for an MSL just repeat the steps and choose the other diag. Another trick I found was that when the phone is in safe mode you can run a few commands that you normally couldn't. You must use adb shell since you can't use an installed terminal emulator in safe mode. Hopefully this can get things rolling.
adb shell
ToastDrummer said:
I've had this phone for a few months now and have tried finding a way to root. I have found some tricks that haven't been posted before. Hopefully this will lead to something for everyone using this phone. Anyway here's what I've found. We can enable diag port without the MSL using an app called anycut by opening the app, click make shortcut, choose activities and find the one named diag. There are 2 so if the first one asks for an MSL just repeat the steps and choose the other diag. Another trick I found was that when the phone is in safe mode you can run a few commands that you normally couldn't. You must use adb shell since you can't use an installed terminal emulator in safe mode. Hopefully this can get things rolling.
Click to expand...
Click to collapse
which commands, if you don't mind me asking? Also, what do I do after I lauch "diag."?
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire Phone so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
Code:
"alexa_enabled"
"assistant"
"voice_interaction_service"
"voice_recognition_service"
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Code:
adb shell settings put secure assistant com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
adb shell settings put secure alexa_enabled 0
If the last command doesn't work, go to the Settings Database Editor app and tap on secure tab. Locate the alexa_enabled setting and tap it. change the 1 to a 0 and save the setting.
6. Open the Google App and go to settings > voice > Configure 'Ok Google" or your Assistant.
The more who confirm this, the better
How can I disable double tap of home button who activates the "voice input", who is no longer avaible as Amazon decided... THANKS THEM
DragonFire1024 said:
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire Phone so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
The more who confirm this, the better
Click to expand...
Click to collapse
Hi DragonFire1024,
Thanks for this very interesting post I was just wondering by to see if anyone had unlocked the bootloader :laugh:
Problem with the fire phone is probably 98% of users here use one of @ggow custom ROM's LineageOS 11 or the AOSP based SlimKat and Nexus Rom. Those running the Stock ROM are likely not interested in development hence why no reply's.
To be honest I never even gave the Fire OS a chance before rooting and switching to the Nexus ROM. I am not sure our fire OS has Alexa :silly: or at least as we know it today yes you heard correct a Premium Amazon Device and they see fit not push it out to Amazon device owners. In fact they just went one better and removed the voice service altogether. https://forum.xda-developers.com/fire-phone/general/amazon-voice-services-fire-phone-t3681235 Pretty amazoning :laugh
I was kinda hoping it was to make way for Alexa and a Massive OS Update but I guess thats just wishful thinking. :laugh:
Hello,
I'm hoping that someone here will be able to help to do one or more of the following things:
1) Complete data recovery of Samsung Galaxy S9 snapdragon
2) Bypass pattern lock
A partner against whom I have a restraining order purchased this phone for me and I have since become aware that there is software installed on it which I cannot access which is recording my location, communications, etc.
All I installed is Mxplorer, OS Monitor, and Logcat, all of which were recommended by users on these forums and which were Google Play verified. When I started going through what I could access and recording the logs, my phone went crazy and a bunch of root files began to delete themselves. Now it is locked by a pattern and I never set a pattern.
Is it possible for me to bypass this pattern without deleting all the data on the phone, or to backup all the data on the phone including root files even if I cannot download the phone itself?
Alternatively, is anyone aware of any organization that would help me to examine the phone, as I do not feel that I have the technological ability to do so myself?
Also, I understand that the best thing to do for my own security is to use a different phone and to reset the passwords for all the accts that were saved on that phone from a different device and I am already doing that but it is very important to me to identify and preserve the spyware that was installed on this phone in order to 1) ensure the continuation of the restraining order 2) know what information he has had access to and 3) share the information that I find with organizations that are involved in combatting the development/sale/use of this kind of stalkerware.
Thank you.
PS C:\Users\Genevieve\Desktop\platform-tools_r30.0.5-windows (1)\platform-tools> .\adb shell
starqlteue:/ $ cd /data/data/com.android.providers.settings/databases
/system/bin/sh: cd: /data/data/com.android.providers.settings/databases: Permission denied
2|starqlteue:/ $
2|starqlteue:/ $
This is what I'm coming up against when I try to bypass the screen lock using adb, just for reference.
Permission denied on that path is not unusual, some devices simply don't support accessing that path over ADB. To delete that path, USB debugging needs to have already been enabled in the device's developer options so you can delete the gesture.key file and regain access. I've had a similar fight with an older Android device, trying to retrieve photos from a phone with an unlock pattern the owner had forgotten.
In the end I managed to gain access to the filesystem, but I had to do it through recovery mode by flashing an alternative recovery image to the device which bricked it for normal use.
I'd be surprised if this other person managed to install commercial spyware/malware without rooting the device, which would also give you access to that path.
That sort of 0day vuln is either darknet for $$$ (at which point, just wipe the cache partition, reflash the stock firmware and start from scratch) or nation state actor complexity.