Related
So, I just set a pin lock screen on my Sprint GS5, and I immediately locked it, and went to unlock it (to see what the lock screen looked like), and I entered the pin that I just set on the phone, and it said that it was incorrect. I know what I entered, and the lock screen is not taking it. I have tried multiple combinations involving numbers near the numbers I put in, and nothing has worked. I'd really like to remove the pin lock without erasing anything, as I have things I have not backed up that are not on my SD card. I did not have the device set up with Android Device Manager, nor my Samsung Account. The phone was rooted with Towel Root.
Is there anything I can do other than a factory reset? This is really aggravating me.
Now you know why you should always make a backup first.
You should be able to remove the PIN using Paulyhofman's method.
This requires ADB debugging on or in the alternative, installing a custom recovery.
If the Sprint bootloader is locked and hence you can't do a proper custom recovery, then do a forum search as there are several other PIN bypass methods in existing threads. Actually doing a search should always be the first step before posting any question.
adb shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=65536 where name='lockscreen.password_type';
sqlite> .exit
# exit
adb reboot
.
fffft said:
Now you know why you should always make a backup first.
You should be able to remove the PIN using Paulyhofman's method.
This requires ADB debugging on or in the alternative, installing a custom recovery.
If the Sprint bootloader is locked and hence you can't do a proper custom recovery, then do a forum search as there are several other PIN bypass methods in existing threads. Actually doing a search should always be the first step before posting any question.
adb shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=65536 where name='lockscreen.password_type';
sqlite> .exit
# exit
adb reboot
.
Click to expand...
Click to collapse
I must not have had usb debugging enabled on my phone because ADB says device not found. I was able to copy the settings.db file to my SD card using aroma, but I try to open it in SQLite reader, and it says it is encrypted. Do you know how to decrypt this file? Or anyone?
Okay, I found a solution. Instead of modifying settings.db, I deleted /data/system/locksettings.db, and the lock screen was removed.
I did this from within the aroma file manager. I finally have my phone back! I will be setting up remote controls, usb debugging, and backing some stuff up now.
Hi there,
I had kinda trouble today skipping the "Verify your account" after a recovery Factory Reset.
Long story short, a collegue's daughter locked her phone, and he had to perform a factory reset from recovery.
Since she changed her phone number and lost her password, no google's account recovery were possible.
After a week of trial and error, he decided to let me take an eye.
As you know :
- If you perform a factory reset with recovery, a google's anti-theft feature, called Factory Reset Protection, occurs and force you to login once with a google account that was previously set on this phone.
- If you perfrom a factory reset with android built-in (Settings -> Backup and restore -> Factory reset), you won't encounter this issue.
- If for a reason or an other, you don't know the required credentials, don't have unlocked your bootloader and never checked "Allow oem unlock", you're kinda screwed.
Here is how I figured a way to bypass this feature (BTW, I won't post any link this I didn't wrote any of theses tools. I juste figured a way to use them) :
Disclaimer :
I have not made any of the tools or adb command.
I can't be held responsible for any damage done to your phone.
Don't use any of theses instructions if you don't know the consequences.
Use theses instructions/tools at your own risk.
I achieved this bypass by search and trial.
English is not my native language. Name has been translated and may not be accurate. However, I'm sure you'll find what I meant.
1) Install minimal ADB and fastboot (Google that)
2) Install Motorola's USB drivers (Motorola's website)
3) Power on your phone, set-up a wifi connection.
4) Return to the Wifi wizard, choose a connection you do not want to connect to. Check 'Show password" and enter a random password.
5) Double press the text, choose "Share".
6) Long press "Gmail", you'll be redirected to Gmail's settings.
7) Press "Notification" then "Application settings"
8) Press Option (3 dot menu) then "Manage account"
9) From there, you'll sucessfully enter phone settings. Unlocking the "Developper option" won't work anyway.
10) Press "Users" and create a new one. Don't set it up ; instead, log in the newly created user.
From there, it was Trial and Error and I, somehow, managed to allow Developper option.
11) Try various things such as : Enabling developper option from new user ; Switch to owner and try again ; Open an app and return to settings with the little square (suspended app) with owner and new user.
Search anywhere, be patient, try various things, it'll work somehow ...
From a certain point, you'll be able to unlock the Developper option.
12) In Developper Option, check "Enable USB debugging"
13) Open a cmd in Windows, navigate to the adb folder. Type in the following command :
Code:
adb devices
You should be able to see the phone. If not, ensure you have the correct drivers (From device manager).
If your phone is detected, type in the following command :
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
Thanks to : Matthew Read (android stackexchange)
14) Perform a factory reset from settings.
15) Optionnal : After phone reboot, enable Developper Option, check "Allow OEM unlock" to allow future bootloader unlock and flashing.
That should do it.
Step 11 is very vague but I spent few hours unlocking this phone and I did LOT of things. I spent 1 hour or so on this step and forgot what I precisely did to unlock this option.
If you manage to succeed, please post your instructions.
I WON'T relock the phone in order to discover exactly what worked.
This won't work for long, since this is a security fault and will be patched (as every previous bypass) sooner or later.
Be patient and be curious ! Have fun
Don't waste time here.....
Already Video available on YouTube...
Hi Guys
So, as you all know, Quick capture is disabled in devices connected to an Indian network and this had me pissed off for a very long time.
I looked into the Emergency Affordance Service which is responsible for identifying Indian SIMs and found a way to disable it (at least on the 5t).
But a word first.
DISCLAIMER: The Govt of India has stated that it is mandatory for all phone manufacturers to add this functionality for the right reasons. By disabling the feature you will NOT be able to use the triple-press power button for emergency call. I do not take responsibility for any damage caused due to the actions described in this post.
Alright, lets jump into it.
Step 1. Install a terminal emulator app (or connect via adb shell)
Step 2. Enter the following command without quotes:
"settings put global emergency_affordance_needed 0"
(You may use the "settings get global emergency_affordance_needed" command to confirm if it worked.)
Step 3. Check the OnePlus Camera app - the Quick capture option should be there.
Step 4. Profit!?
Notes:
My 5t was rooted with magisk, but I ran the command on a normal ($) prompt so I'm not sure if this requires root or not. Please try it on unrooted devices and let me know so I can update this post accordingly. Also, I haven't checked if it persists after a reboot.
Not working on non rooted device.
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
any idea how the phone detects that its india? Could we spoof that?
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
zeeshanonlyme said:
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
Click to expand...
Click to collapse
Use ADB shell instead of doing in on your phone
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Edit: Found It
https://www.reddit.com/r/oneplus/comments/6ur1ma/double_tap_power_button_setting/
The devs name is Mishaal Rahman ...Maybe he could help us out.
abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.
Sorry for bumping an old thread but has anybody figured out how do get this working permanently with xposed or magisk ? I bought a OP6 and miss this feature coming from a Nokia 7+
MAGISK Module!
Hi,
Was able to create a magisk module to do this automatically every boot and also got wifi auto turn on to work, check out the thread here.
kashyapha1994 said:
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
Click to expand...
Click to collapse
Might be possible to override this with an overlay (non-root Substratum.)
Every night from 11pm to 6am, my device screen turns itself into night mode(yellow tint). I have set Reading Mode off since the day I bought. Back in previous device(Redmi Note 4, mido) I had Pixel Experience ROM installed. In that I had turned on night mode with the same timing(11pm to 6am). Did Google restored this setting too? I want to turn it off in my K20 device.
Need help!
Redmi K20 Indian version.
I'm having the same issue on my k20. At sunset(~6:30), even though my reading mode settings are off, the display becomes warm/yellow. Can't seem to fix it. Have you managed to solve your issue?
This happens when all your old phone settings synced with your new mobile while setting it up. anyway you may not be aware of that while setting it up.
Here's the solution:-
Download system ui tuner from the playstore.
Give it the permissions it need using command prompt.
You can see some new options in your notification panel which is 'night mode' at click it when the yellow light turn's on.
Turn off the reading mode?
I have no problems here at night. Its only "warm" when its turned on. Maybe you could turn off the time settings also?
Vinay_sandy said:
This happens when all your old phone settings synced with your new mobile while setting it up. anyway you may not be aware of that while setting it up.
Here's the solution:-
Download system ui tuner from the playstore.
Give it the permissions it need using command prompt.
You can see some new options in your notification panel which is 'night mode' at click it when the yellow light turn's on.
Click to expand...
Click to collapse
Thank you a lot. It helps once, but tomorrow it still happens again. Maybe you know how disable this globally?
Prochkailo said:
Thank you a lot. It helps once, but tomorrow it still happens again. Maybe you know how disable this globally?
Click to expand...
Click to collapse
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Any update please
Are you fix this issue please feed me back?
I confirm this too, its warm but not like read mode. It's just more warm
Edit : try with stable xiaomi.eu ans turn yellow at 10pm without read mode activated...
Impossible for me, have :
Security exception: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS
EDIT : It's ok ! just dont have turn all 3 usb debugging options on for miui
Digital wellbeing under settings. Turn wind down off.
Is this issue fixed? I have this issue too. How can I fix this without using adb or pc? Thanks in advance!
Vinay_sandy said:
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Click to expand...
Click to collapse
Thanks a lot, finally I got the solution for this problem. After months thinking that was MIUI bug, I understand now what happened.
When I was on Pixel Experience and returned to MIUI, this yellow screen issue begin.
To run this commands, it's necessary to enable "USB debugging (Security settings)" in developer settings (as I saw on Stackoverflow).
:good:
---------- Post added at 19:44 ---------- Previous post was at 19:37 ----------
Tian_Valderev said:
Is this issue fixed? I have this issue too. How can I fix this without using adb or pc? Thanks in advance!
Click to expand...
Click to collapse
The only way I think it's use another phone with stock android or install Pixel Experience, and revogue the Night Mode from stock android. After a time, when Google account sync , when you return to MIUI this issue probably won't happen again.
Vinay_sandy said:
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Click to expand...
Click to collapse
Thanks bro. It fixes the problem!
Mkriiger said:
Thanks a lot, finally I got the solution for this problem. After months thinking that was MIUI bug, I understand now what happened.
When I was on Pixel Experience and returned to MIUI, this yellow screen issue begin.
To run this commands, it's necessary to enable "USB debugging (Security settings)" in developer settings (as I saw on Stackoverflow).
:good:
---------- Post added at 19:44 ---------- Previous post was at 19:37 ----------
The only way I think it's use another phone with stock android or install Pixel Experience, and revogue the Night Mode from stock android. After a time, when Google account sync , when you return to MIUI this issue probably won't happen again.
Click to expand...
Click to collapse
Yeah man. I came from an android one device and I can confirm your statement.
I am getting this error /system/bin/sh: settings list secure: inaccessible or not found. Kindly help me out. adb devices command return the device list
senthilanandhpv said:
I am getting this error /system/bin/sh: settings list secure: inaccessible or not found. Kindly help me out. adb devices command return the device list
Click to expand...
Click to collapse
Never mind I figured it out. (I had adb folder at two places and I was trying the commands from incorrect place)
Vinay_sandy said:
This happens when all your old phone settings synced with your new mobile while setting it up. anyway you may not be aware of that while setting it up.
Here's the solution:-
Download system ui tuner from the playstore.
Give it the permissions it need using command prompt.
You can see some new options in your notification panel which is 'night mode' at click it when the yellow light turn's on.
Click to expand...
Click to collapse
WTF bhai it actually works, but how to permanently disable yellow tint, even after using "ui tuner" it again goes to yellowish after some time, just what the hell is this thing? completely ruining my Amoled experience
Harshavarbm13 said:
WTF bhai it actually works, but how to permanently disable yellow tint, even after using "ui tuner" it again goes to yellowish after some time, just what the hell is this thing? completely ruining my Amoled experience
Click to expand...
Click to collapse
I have posted the ADB commands for permanent fix earlier in this thread....!
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Vinay_sandy said:
I have posted the ADB commands for permanent fix earlier in this thread....!
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Click to expand...
Click to collapse
Thanx successfully managed to run the command.
Harshavarbm13 said:
Thanx successfully managed to run the command.
Click to expand...
Click to collapse
You're welcome.
About yellow tint problem on Redmi k20 pro
Vinay_sandy said:
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Click to expand...
Click to collapse
I don't know what is adb command and where to type that please help me. do I need to root my device for this? do I need PC for this ?
Is there a way to bypass the lockscreen on a Xiaomi 3S without doing a reset and losing all the data?
When I was living in China I found out my boss had installed a RAT on my phone and was monitoring my location and accessing my messages/photos etc. When I confronted him about it he changed the lockscreen password and said he wanted 15000rmb from me to unlock it. He told me there was nothing I could do about it because he is Chinese and I'm not so the police will believe him. I ended up just getting a new phone because it wasn't worth the fight to me at the time
That was back in 2016 but I have a bit of an emergency situation and I really need to access some data that's save on this phone
A few points worth mentioning
Google account and "lost my phone" methods are not available to me as it's not an international version so has no google functionality
I don't have a xiaomi account so I can't use the xiaomi versions of the above
I have tried the android lock screen crash method here https://www.oreilly.com/library/vie...98/85928bf7-5c5e-40cb-9a9b-5aa4e75d8032.xhtml but I do not get the option to copy/paste data from this text field. So I'm assuming it's the wrong version of Android
I have tried connecting the phone via USB to a computer that has the Android SDK tools installed and using the command "adb shell rm /data/system/gesture.key" but I get an error "this adb server's $ADB_VENDOR_KEYS is not set".
I've tried at least 10 different android unlocking tool piece of software I can find, but as far as I can tell they all just try to format and I need the data on the phone