I've spent too long time to get rid of SIM Toolkit icon on my new Xperia Z5P. I could not unlock bootloader even though I've got unlock code from Sony developer site, so I have stock never rooted ROM. I went to my operator and asked to replace SIM card, they gave me a SIM "without USTK" but that icon still appeared after reboot.
The only way worked I got from XDA member Tomsgt in his post
Connect your Z5P to PC by USB, enable debugging, open command prompt and type :
Code:
adb shell
pm hide com.android.stk
That's it!
Related
OK. I'm going to try and be as thorough as possible here.
I have a Sony Ericsson Xperia r800at. It was on ATT service. I am wanting to switch over to Straight Talk.
I have a Straight Talk SIM card in the phone.
I am running Android version 2.3.3 (build 3.0.1.B.0.285)
In my research on how to unlock this phone, every site I see simply says to Turn off the phone, put in SIM card, and turn the Phone back on. When you go to swipe the phone to unlock it should prompt you to put in the SIM Network Unlock code.
I do not get this. It just lets me right in the phone. The only error I'm receiving is "SIM card not provisioned MM #2" in my notifications and the phone is telling me it can be used for Emergency calls ONLY.
Does anyone have any ideas on how I can get the SIM prompt to appear?
Hi,
I have a SIM unlock code but when I insert a new SIM it doesn't prompt for the unlock code.
I don't know if it has something to do with the fact that my phone asks for the language every reboot and it "covers" the unlock screen.
Is there a hidden menu or USSD code that I can use for type in my SIM unlock code?
Cheers
JD Evora
You installed a KK version and have wrong baseband, kernel or something else wrong. Nothing you can do about it except flashing correctly according to the guide here in the forum.
I flashed the custom KK rom and had the same problem. Only by following the guide on how to install KK with locked dual recovery and root very exact, I got it working.
I thought that I followed the guide step by step but I'll give it another try
Thank you
JDavi
Sent from my D5503 using xda app-developers app
I tried with the UK unbranded JB and KK without luck so far
jdevora said:
I thought that I followed the guide step by step but I'll give it another try
Thank you
JDavi
Sent from my D5503 using xda app-developers app
Click to expand...
Click to collapse
> What about going into "Settings" -> "Security" -> "SIM card lock settings" -> is the "Lock SIM card" checkbox ticked?
> Did you tried it with any other SIM card? If yes, and SIM lock showed up after phone start, then there is something with your SIM.
> Did you tried your SIM card in any other phone? If yes, and SIM lock showed up, then there is probably something with your phone.
BTW: If phone detects SIM properly, then "setup guide" should show up only after first phone start.
Hi,
I don't have the "Sim card lock settings" in my Security menu.
but if I go to the "service Menu" - Service Info - Sim Lock y shows an X on "network" and a 5.
I think it means that it is locked and I have 5 unlock attempts.
BUT if I put a new SIM it doesn't recognize it and it doesn't prompt for an unlock code
Q u,z
Cheers
JD
pcpepik said:
> What about going into "Settings" -> "Security" -> "SIM card lock settings" -> is the "Lock SIM card" checkbox ticked?
> Did you tried it with any other SIM card? If yes, and SIM lock showed up after phone start, then there is something with your SIM.
> Did you tried your SIM card in any other phone? If yes, and SIM lock showed up, then there is probably something with your phone.
BTW: If phone detects SIM properly, then "setup guide" should show up only after first phone start.
Click to expand...
Click to collapse
Try this? I did this to unlock a ZL (Jellybean) last night (not intentionally, this is just the order in which we happened to do it).
1) Put in correct SIM (a SIM that has the carrier in which the phone is locked to)
2) Do the initial setup stuff to get it out of the way (this is so it doesn't bother you with it again and again)
3) Power off, put in illegal SIM, power on. It should ask for unlock code without anything overlapping it.
Baseband/modem I747UCUFNJ2, stock 4.4.2 rooted. Phone from AT&T working ok with Claro Brazil (code unlocked) . After upgrading, lost IMEI. Flashed new modem and IMEI and IMEISV ok now. Checked IMEI number, is the same printed behind battery on phone. But now can not make calls. Got message 'No SIM card'. Ordered a Sim card tray, replaced it, but got same message. Phone has strong carrier signal. After reading a lot, I ordered a paid unlock code, but seller stated that code doesnt work in android 4.2.2. Even though, I tried to insert it once. (#@7465625*638*# - have to use it since phone doesnt ask for code at starting). As stated by seller, got message 'unlocked unsucessfull'. So now, what can I do to unlock the fone ? I have access to a hiden menu by dialing *#197328640# , but dont know how to use it. I have read a lot during this week. Did no find any helpfull information. Any help will be apreciated. Sorry for my bad english.
Sounds like the baseband and bootloader and too new for the ROM. You probably need to upgrade from stock 4.2.2 to stock 4.4.2 or flash a custom ROM based on a TW-kernel.
I edited/corrected my wrong information. The phone is on 4.4.2 stock already.
Try this:
Method 1:
Go to the dial screen and press #7465625*638*#
Once prompted for code, enter 8 digit Unlock Code.
Method 2:
Turn off your Samsung phone
Insert a non-accepted sim card (different from the original carrier) and turn your phone back on.
When prompted for the unlock code type the UNFREEZE code provided. If you are not prompted, go to your dial screen and type the UNFREEZE code, now press enter, send or call. You will receive an unsuccesfull message, don't worry.
Once the phone freeze is disabled, the Network lock or SP Lock screen will appear
For Network lock enter the UNLOCK code provided. For SP Lock enter the SERVICE PROVIDER code
Your phone is now fully unlocked!
If you get "unsuccessful" again then hit Dismiss button and type *2767*3855# on phone keypad and try this procedure again (CAUTION! This will reformat all your data!).
Method 3:
You can try this method without the sim card or with the original sim card
Type #7465625*638*CODE# (CODE is the Unlock Code)
Phone deactivated message means its unlocked
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....
PROBLEM:Under certain scenarios, enabling Quick Unlock on the OnePlus 9 Pro with Android 12 causes semi-bricked phone: the phone will vibrate OVER and OVER again and it is impossible to log in!
If your phone is in this state, here's three possible fixes:
Spoiler: Possible Solution #1
POSSIBLE SOLUTION #1:
Thanks to Caligastia's post, here's another option to resolve.... (quoting from his post)[/B]
Just use the adb command...
Code:
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Click to expand...
Click to collapse
Spoiler: Possible Solution #2
POSSIBLE SOLUTION #2:
Revert to settings_system.xml.fallback file. Do not follow this guide UNLESS your phone is in this vibrate over and over / impossible to login state.
Note: This only works if you have USB debugging enabled on your computer with root enabled. This will not work if you haven't performed adb shell as root before ( com.android.shell ). Doesn't hurt to try!
Boot up phone to system/normal mode.
Type the following in command prompt:
Code:
adb shell
su
ls /data/system/users/0/settings_system.xml
If it says:
Code:
/data/system/users/0/settings_system.xml
Then this fix should work! Otherwise, this probably won't work.
Finally, type...
Code:
mv /data/system/users/0/settings_system.xml /data/system/users/0/settings_system.xml.old
cp /data/system/users/0/settings_system.xml.fallback /data/system/users/0/settings_system.xml
reboot
Your phone will reboot and the issue should be fixed!
By applying this method you may lose a few recently changed system settings, but nothing major.
Spoiler: Possible Solution #3
POSSIBLE SOLUTION #3:
Go to bootloader/fastboot mode on your phone.
Type
Code:
fastboot --set-active=a
fastboot reboot
if it doesn't boot right still, go back to bootloader/fastboot and type
Code:
fastboot --set-active=b
fastboot reboot
There are no settings on the 9Pro A12 called quick unlock. What are you referring to?
I'm referring to the setting called Quick Unlock.
Password and Security > Lock Screen Password.
But what this option do ? ( Quick unlock )
asheroto said:
PROBLEM:Enabling Quick Unlock on the OnePlus 9 Pro with Android 12 causes semi-bricked phone: the phone will vibrate OVER and OVER again and it is impossible to log in!
DO NOT ENABLE QUICK UNLOCK!
Click to expand...
Click to collapse
On my LE2123 OnePlus 9 Pro I do not face this issue with quick unlock. I made a test now once and no issue. Just FYI. I an not rooted.
K1nsey6 said:
There are no settings on the 9Pro A12 called quick unlock. What are you referring to?
Click to expand...
Click to collapse
This option appears if you select Alphanumeric password, using the regular keyboard instead of number pad. Quick unlock will unlock your phone immediately once you enter the password without having to press the enter key.
Interesting, I have the LE2125 with alphanumeric enabled.
I edited the original post to say "Under certain scenarios".
I just updated to Android 12 on my OnePlus 8 and tried out this setting. Now it is impossible to log in to my phone and it constantly vibrates, just like described above.
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
blxyy said:
I just updated to Android 12 on my OnePlus 8 and tried out this setting. Now it is impossible to log in to my phone and it constantly vibrates, just like described above.
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
Click to expand...
Click to collapse
Unfortunately you have to allow the host (your computer), but you can't do that unless you can tap on the popup.
Can you get in with TWRP or anything else? If so you could edit the file that way. Otherwise, try booting to the other slot.
How to check the current slot:
How to Check if You're on Partition Slot A or Slot B? - KrispiTech
Android phones can now have an A and a B partition system for the OS and we can use this fastboot command to check and see which slot is currently active.
krispitech.com
How to change the active slot:
adbcommand.com - adbcommand Resources and Information.
adbcommand.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, adbcommand.com has it all. We hope you find what you are searching for!
adbcommand.com
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
Click to expand...
Click to collapse
@bixyy
Just saw this, hope i'm not too late to help.
If adb shows "unauthorized" it just means that usb debugging permission was revoked between your phone and computer. here's what to do: (assuming you're on windows)
-Unplug your phone from pc. Disable Usb debugging and turn off "disable timeout"
-on your pc, go to C:/users/<username>/.android (it's a hidden folder) and delete adbkey.
-reboot both phone and pc to make sure it takes effect.
-plug your phone again, turn on usb debugging and you should get a new prompt to allow authorization.
adb devices should return your serial number now.
Added possible alternate solution
I ran into the same issue, OP was very helpful.
A bit more info here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Finally fixed it! Very simple solution it turns out. Since the setting is only for alpha numeric passwords once you erase the pass the phone stops acting up.
Just use the adb command
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Caligastia said:
Finally fixed it! Very simple solution it turns out. Since the setting is only for alpha numeric passwords once you erase the pass the phone stops acting up.
Just use the adb command
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Click to expand...
Click to collapse
Thanks for that man! I updated the original post to include your solution and linked to your post for credits!
I had the same issue on my OnePlus Nord, and finally managed to fix it too!
Thanks to @asheroto for your initial guide and @Caligastia for your last comment that gave me the idea of trying with digits only!
Here is how I did it:
After rebooting my phone in recovery mode to activate the USB debugging, I connected to it using adb shell
The locksettings clear --old [PASSWORD] command wasn't allowed on my phone.
==> I'm guessing it was due to some security settings enforced by the enterprise work profile I had installed on my device.
So instead of trying to clear the password, I tried to change it to a PIN code using the command:
locksettings set-pin --old [PASSWORD] [PIN_CODE_HERE]
The command succeeded and after a few seconds of waiting, a digit keyboard finally shown up on my previously bugged lock screen, allowing me to unlock my phone!
I then disabled in the system settings the "Quick Lock" feature and restore my previous password.
_147 said:
I had the same issue on my OnePlus Nord, and finally managed to fix it too!
Thanks to @asheroto for your initial guide and @Caligastia for your last comment that gave me the idea of trying with digits only!
Here is how I did it:
After rebooting my phone in recovery mode to activate the USB debugging, I connected to it using adb shell
The locksettings clear --old [PASSWORD] command wasn't allowed on my phone.
==> I'm guessing it was due to some security settings enforced by the enterprise work profile I had installed on my device.
So instead of trying to clear the password, I tried to change it to a PIN code using the command:
locksettings set-pin --old [PASSWORD] [PIN_CODE_HERE]
The command succeeded and after a few seconds of waiting, a digit keyboard finally shown up on my previously bugged lock screen, allowing me to unlock my phone!
I then disabled in the system settings the "Quick Lock" feature and restore my previous password.
Click to expand...
Click to collapse
can you help me i cant seem to get adb to recognize my phone
Hi,
Is there any possible solution for us who don't have USB-Debugging enabled?
The goal is to not have to wipe the whole phone and loose all data.
Possible solution #1 fails: Wont work because USB debugging is disabled which prevents us from getting adb-shell and run the "
locksettings clear --old [PASSWORD]" command. When trying to figure out how to enable USB debugging from remote it seems to require some fastboot option which would wipe the phone.
Possible solution #2: Same - requires shell, and we cant enable usb debugging because of the bug
Possible solution #3: I can access fastboot but not run the specific commands:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
fastboot --set-active=a
Setting current slot to 'a'
FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Unlocking boot to install TWRP and enable debugging to use ADB shell would wipe the phone as I understand it.
Any suggestions please?
Is your phone locked when you're doing that?
asheroto said:
Is your phone locked when you're doing that?
Click to expand...
Click to collapse
Developer options enabled
OEM bootloader unlock enabled
USB debugging enabled
Default USB Configuration file transfer
Non-TMO variant = boot to bootloader, then fastboot OEM unlock...wipes device. No other way. Unlock bootloader will wipe device period.