After following a process elsewhere on XDA to set up a pin lock, (here: http://forum.xda-developers.com/showthread.php?t=1848962&highlight=lock) I've been locked out of my device, with the response Too Many Pattern Attempts.
It says: "to unlock, sign in with your Google account." But I do that, and receive an invalid login response. (This is without active wi-fi, which I can't access for the settings!) I'm not certain that it's trying to connect online, but that's my only explanation for why my google credentials aren't working.
I was hoping I could use ADB to reset the PIN again, but ADB doesn't appear to recognize the Nook; maybe it's not opening up the device to USB until it gets unlocked. And ADB Wireless is something I can't even access until I get past this!
I'm currently on the road so I can't go back to my home wi-fi... and I'm not even sure that the nook would connect to the home wi-fi anyway.
At the very least, I'd love to find out how to boot it in recovery mode, maybe re-install and re-root everything. I've seen a few posts online about rebooting in recovery mode, but nothing consistent.
Any suggestions?
Related
I got an Madcatz MOJO Console, it is good and interesting. But on a day, when I start up the console, it asked me enter a password to unlock home screen, indeed, i don't know what happen since don't have any area for setting password of it. So, at the moment, I can not do anything with this.
You can see my problem in attached picture.
Could anyone pls let me know how to solve the problem.
Thank you so much in advance.
Regards,
Tom
tryied just hiting enter (empty password)?
Someone must have set it to activate the lock?
maybe this would help you:
http://droidlessons.com/how-to-reset-your-android-lock-screen-password/
Thank you for your reply.
But problem is when I'm checking on other console, i could not find place to set password for device.
I search on internet to find how to bypass the lock code at home screen, I tried all but unsuccessful since almost methods required root permission.
Luckily, I still connect and debug device via my computer, I tried reboot into recovery, but it only shows the android robot and yellow triangle then stuck.
If like android phone, we can hold volume+power button to show command line in recovery but I couldn't do like this with my console . On console doesn't have any physical button.
I also send an email to support center on Mad catz website but stil not receive any feedaback.
tomrockie said:
Thank you for your reply.
But problem is when I'm checking on other console, i could not find place to set password for device.
I search on internet to find how to bypass the lock code at home screen, I tried all but unsuccessful since almost methods required root permission.
Luckily, I still connect and debug device via my computer, I tried reboot into recovery, but it only shows the android robot and yellow triangle then stuck.
If like android phone, we can hold volume+power button to show command line in recovery but I couldn't do like this with my console . On console doesn't have any physical button.
I also send an email to support center on Mad catz website but stil not receive any feedaback.
Click to expand...
Click to collapse
Were you ever able to figure this our. I have a M.O.J.O. that has the same issue
Still not yet. I contacted with Mad catz and seem that I have to return device for inspecting.
Apologies for the inconvenience. :C
As precaution for others, you can setup the Android Device Manager to remotely lock/reset password for your MOJO -- similar to Find my iPhone on Apple devices. However, it will need to be set up while you still have access to the device.
To set up, go to a http://play.google.com while on a PC, and then go to "Settings > Android Device Manager". Ensure the MOJO is connected online, and then locate the device and choose the "Setup Lock & Erase" option. A notification should pop up on the MOJO. Click on it to finish allowing Android Device Manager access to the device.
Once setup, you'll be able to remotely ring, lock, erase, and reset lock screen password as necessary. More info can be found here:
https://support.google.com/accounts/answer/3265955?hl=en
Hi all, the other night i went to be and my phone woke us up making a ticking noise. i looked at the screen to find it suddenly asking for a password/pin to decrypt. i have NEVER encrypted or even looked at the menu to encrypt my phone. the phone is also completely stock from verizon, although as i understand the vzw variant claims to be rooted. i do not have a pass or pin to unlock. it also says i have 0/10 attempts left to enter my pass/pin. if i enter one at random, the attempts remaining changesto 1/10. this seems backwards to me. if i enter any more false passwords the number does no go up or down anymore. i can access the hard factory reset screen by using the vol down +power key combo but when i confirm the device to wipe i get e cannot mount cahce and e cannot open cahce log. it also says unknown error 150. if i try to wipe cache it says the same thing. i tried to use the sideload from adb option and my computer recognizes an adb connection but it only allows me to run the adb sideload command, which fails due to the mounting errors as well. if i try to run any other adb commands it immediately says "closed" in my command prompt. i cannot load any images from sd card either since the phone has no sd card slot and i cannot access the internal storage in any way ive tried. i went to use the lg flash tool to try and just flash a new image and everything goes fine until the 15 or 16 second mark and then it tells me it fails because the erase command is unsuccessful.
im getting ready to send it in to lg or verizon but i just hate being beaten by such a mysterious problem. can it not mount or give me access to overwrite with the flash tool because of encryption? or is it "encrypted" due to a faulty chip causing an issue? its weird that it can still boot to this pass/pin screen, it has the standard soft keys on bottom of the screen, so it looks like th UI is actually still being recognized. also, i am/was connected to a corporate exchange server but we have never had a policy in place to require encryption and there is another android user in our office who has not had this happen. i am the tech guy and i have verified this. can anyone help me at least understand what the problem might be? i just hate not knowing, even if i still have to send it in. is it truly hardware? or is it just software gone crazy?
Long shot as this shouldn't be possible, but I figured I'd try asking here anyways. Is there any way to unlock a 6P that's pin-locked by Android's Device Manager?
The goal is to get the pictures off this phone. It was my brother's phone before he passed away and I've been holding on to it for the past few months - just haven't had the energy to try to deal with it...
-I have access to the gmail account.
-I tried changing the pin through Google's device manager, but since the phone was already locked, the new pin did not take. I get the message on the phone about the new pin, but it doesn't unlock it.
-Developer mode is not enabled (i.e. USB debugging).
-Not rooted or anything like that and most likely has the latest updates (t-mobile). As a matter of fact, the lock screen says that a new system update has been downloaded.
Thanks.
Try putting twrp in your adb folder, boot into fastboot and use "fastboot boot twrp.img"
clappe said:
Long shot as this shouldn't be possible, but I figured I'd try asking here anyways. Is there any way to unlock a 6P that's pin-locked by Android's Device Manager?
The goal is to get the pictures off this phone. It was my brother's phone before he passed away and I've been holding on to it for the past few months - just haven't had the energy to try to deal with it...
-I have access to the gmail account.
-I tried changing the pin through Google's device manager, but since the phone was already locked, the new pin did not take. I get the message on the phone about the new pin, but it doesn't unlock it.
-Developer mode is not enabled.
-Not rooted or anything like that and most likely has the latest updates (t-mobile). As a matter of fact, the lock screen says that a new system update has been downloaded.
Thanks.
Click to expand...
Click to collapse
The only way I can think of is by installing twrp on the phone. The only way it wouldn't work would be if he didn't have USB debugging enabled, which if he didn't then you might be out of luck... I'm so sorry.
Ghstudent said:
The only way I can think of is by installing twrp on the phone. The only way it wouldn't work would be if he didn't have USB debugging enabled, which if he didn't then you might be out of luck... I'm so sorry.
Click to expand...
Click to collapse
Unfortunately, I am pretty sure USB debugging is not enabled...sorry that's what I meant when I wrote developer mode (I've tinkered with making apps, so I know what it is).
Thanks.
Same situation here and I try to figure a solution for many days.In my opinia the only way to bypass is a modified google account manager ! Could anybody help?
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
RoyJ said:
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
Click to expand...
Click to collapse
Connecting the device to a Windows 10 PC, it will recognize the 6P, but using Windows Explorer will show no files.
Running 'adb devices' lists no devices.
When I power on the 6P, first I get the 'Google' text logo, then the colorful 'spinny' android logo, then the 'android' text logo. Then it goes to the usual lock screen (shows the time, background, etc). On this screen are the normal shortcut buttons on the bottom - microphone, padlock, camera. After a few seconds it shows the 'Locked by Android Device Manager' screen, this has a padlock symbol in the middle along with the pin code that I set online through Google's device manager.
Thanks.
Might be worth a shot to try to contact Google. You'll need proof of your identity, and the passing of your brother though. Best of luck. Sorry about your loss.
If you end up not being able to get a rep that can help via email or phone calls; you might have to do a hardmod.
tr4nqui1i7y said:
Might be worth a shot to try to contact Google. You'll need proof of your identity, and the passing of your brother though. Best of luck. Sorry about your loss.
If you end up not being able to get a rep that can help via email or phone calls; you might have to do a hardmod.
Click to expand...
Click to collapse
Hardmod? I did a quick search and the only hardmod I found was to deal with temperature.
Thanks.
RoyJ said:
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
Click to expand...
Click to collapse
Did you have a chance to try it?
Thanks.
Hey guys, I need your help. I'm unable to unlock bootloader. I downloaded everything I need, I got my unlock number from huawei site etc. When I run adb it detects my phone, I write down adb reboot bootloader, it switches my phone into that white screen where it says LOCKED. Then I run this command - fastboot oem unlock (my unlock number from huawei site) and it replies with- Waiting for any device and nothing happens. Phone is still locked, I cannot write more commands and even if I wait for some period of time, nothing changes and I am forced to reboot without unlocking
Do you guys have any suggestions?
PS: another problem...probably week and half ago my wifi stopped working..it detects different wifi routers, but I am unable to connect and if I connect, the internet is not working. I've read on other forums it could be hw issue. I've also tried every possible step to solve this problem but flashing new ROM, since I haven't been succesful with unlocking bootloader.
Thanks.
sainG said:
Hey guys, I need your help. I'm unable to unlock bootloader. I downloaded everything I need, I got my unlock number from huawei site etc. When I run adb it detects my phone, I write down adb reboot bootloader, it switches my phone into that white screen where it says LOCKED. Then I run this command - fastboot oem unlock (my unlock number from huawei site) and it replies with- Waiting for any device and nothing happens. Phone is still locked, I cannot write more commands and even if I wait for some period of time, nothing changes and I am forced to reboot without unlocking
Do you guys have any suggestions?
PS: another problem...probably week and half ago my wifi stopped working..it detects different wifi routers, but I am unable to connect and if I connect, the internet is not working. I've read on other forums it could be hw issue. I've also tried every possible step to solve this problem but flashing new ROM, since I haven't been succesful with unlocking bootloader.
Thanks.
Click to expand...
Click to collapse
In fastboot(white screen with Android logo saying locked) type fastboot devices.
If it displays YOUR phone serial no of your phone then everything is fine. If no serial number appears then your phone isn't connected to minimal adb. Also it can be a driver/cable issue.
I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Hello,
I have the same exact same issue, have you been able to unlock it?
Thank you!
I can fix it remotely the last hope
Same Issue here,
Any one had any luck with MDM T307U. Please assist.
rittnerb said:
I have a Samsung Galaxy Tab A (2020, SN-T307U) that I got from work. It's an old Doordash tablet that Doordash didn't want back, so I'm trying to reset it and it's driving me crazy. I have followed so many tutorials trying to get this thing to work, I keep getting caught on something.
- Simply factory resetting does not work, gives an error that MDM does not allow it.
- I cannot put in the wrong password 15 times to factory reset, even though I get a warning it just lets me continue trying after 15 fails.
- I cannot enter the bootloader, rebooting to bootloader just reboots to the OS.
- I cannot enter safemode, same as above.
- I cannot enable developer options, so no OEM unlock or USB debugging. Tapping build number gives me an error that the MDM does not allow this option.
The device is recognized by Odin, can I just brick this thing and repartition from scratch? Can someone who knows what they're talking about walk me through that? I'm not really sure what I'm doing here, learning as I go over these last 2 days.
Click to expand...
Click to collapse
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
lewmur said:
If you look at all of the previous post, it should tell you that no one has found a way to disable an MDM lock. Which is as it should be. Otherwise the lock would be useless.
Click to expand...
Click to collapse
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
mindlery said:
That's not true as of today's date. (In the event this post is viewed after this exploit can be successful).
I am not taking credit and perhaps the op has discovered it. Anyway...
I am in Canada and noticed the carriers here stop at BL 8 while the USA has BL 9.
The unit i had was on BL 9 (csc TMB).
This probably works for Canadians on BL 8. I don't recommend flashing to BL 9 as that may affect your service or experience.
ANYWAY! This guide won't explain any prerequisites. They are adb, installing unsigned drivers, and you aren't able to use the device and are the owner
1) if not already, power off device with vol down+power and ensure battery is at least 50%.
2) enter recovery and factory reset. If you're having difficulty entering recovery, plug into your pc and as soon as you hear the audible disconnect, switch to vol up+power. Or jam on all three buttons for dl mode.
If in dl mode you can check firmware version and just flash it with bl, ap, cp and csc (NOT home csc). Use exact current version. Don't worry about userdata if it is USA
3) at welcome, connect wifi and imnediately go back to first screen. Don't use data sim
4) dl samfw app and on misc tab, check driver status and your pc will reboot.
*you must not have secure boot enabled
5) plug phone into pc. In the app, mtp and select youtube. If done right, click the pop up on your phone and navigate to chrome. Should be automatic.
6) search for vnrom frp. Once there download package disabler pro and notification app. They are side by side. Install notification app and set it up so you can swipe quick settings from top of screen.
5) unplug your phone from pc and plug it back in. Should be able to get back to the package app various ways to install it. Before install, turn wifi off. Now run package disabler and when it prompts for device admin, turn wifi on. It'll glitch a bit but should start.
6) locate samsung setup wizard. Don't confuse with the other. It'll have a green icon. Disable it and clear the storage. At bottom left, tap the back arrow and you should be back at final setup.
7) when asked to add samsung account, turn off wifi. Complete setup and don't add any accounts.
8) you should arrive at home screen. Your phone is re-plugged right? Good. Now turn on usb debugging and use the remove knox from the app. Done.
*i think i turned wifi on just before enabling debugging. I forget.
*if you are sloppy... you'll need to start over. You'll see, or already know
*you can do ota (if there still is any) but factory resetting or odin flashing will put you back to managed.
Click to expand...
Click to collapse
This method works up to step 7 for me. I can't seem to enable usb debugging before knox kicks in. With or without wifi. I'm experimenting to see if I can get past that step.
How to Remove MDM Control from Android?For anyone suffering from this issue, the following are the steps to bypass Samsung Knox factory reset protection:
First of all, create a password for the device.
Make sure that your device is charged to an 80% or greater charge.
Next, you’ll need to go to Settings and Security Encrypt Device tabs respectively.
Set a PIN/password for your device.
After you have secured your device and it’s gone through. Reboot the device, and when it boots, it will ask you to enter a password in order to access your device to view encrypted data. If you type the wrong password 15-20 times (it depends on your device), it’ll wipe your device of any information and will restart and then appear like you’re registering as a brand new device after a factory reset.
Thats the 2th!!! Try it
Video - Samsung SM-T307U Galaxy Tab A 8.4 2020 Knox Remove || Tab a 8.0 MDM Remove
the Tool from the Video Tutorial is here >> SamFwToolSetup_4.3