Having issues setting up PIN unlock (though haven't tried any of the other security options). I'm running dman's rooted, deodexed, etc. LB3 ROM with Entropy's March kernel. The only other mod I have is the 8-lockscreen / CRT off mod.
When I setup the PIN unlock, I enter my 4 digit PIN once, then hit OK, then confirm a second time, and hit OK. It goes back to the settings screen as if it was accepted. Then I lock the phone and try to unlock it. It tells me my PIN is incorrect.
I've done this three times now, since the first time I thought I might have fat-fingered the PIN on entry; the second and third times I was very careful with my entry. Each time it won't let me in, and I have to restore from a backup done before I put in the security code.
I also tried restoring to an older backup that didn't have the 8-lockscreen mod and got the same response.
Any ideas? I don't normally use a PIN, but I'm going to put a work email account on it and would like to secure it.
Thanks.
possibly just dense?
I'm beginning to think I might just be dense. Had a few moments to try another ROM and see if PIN unlock works, so I flashed Devastation build 2.
Ran qkster's pre-flash wipe script, then flashed, then fixed permissions. Everything booted as it should, so I went straight to settings to try the PIN lock.
I selected Location and Security > Set Screen Lock > PIN. I typed in my 4 digit PIN, then hit the Continue button at the bottom. Typed it in again and hit the OK button at the bottom (not the OK right under the 7 button).
Then to test it I tried to change the screen lock. As it should, it prompted me for my PIN. Once again, it told me "Sorry, try again".
What the #$%# am I doing wrong? Should I be hitting the "ok" button under the number 7 instead of at the bottom of the screen?
The other possibility is that I just have a bad flash in the mix somewhere and I need to heimdall back to stock and start over.
Cheers.
sjroberts98 said:
I'm beginning to think I might just be dense. Had a few moments to try another ROM and see if PIN unlock works, so I flashed Devastation build 2.
Ran qkster's pre-flash wipe script, then flashed, then fixed permissions. Everything booted as it should, so I went straight to settings to try the PIN lock.
I selected Location and Security > Set Screen Lock > PIN. I typed in my 4 digit PIN, then hit the Continue button at the bottom. Typed it in again and hit the OK button at the bottom (not the OK right under the 7 button).
Then to test it I tried to change the screen lock. As it should, it prompted me for my PIN. Once again, it told me "Sorry, try again".
What the #$%# am I doing wrong? Should I be hitting the "ok" button under the number 7 instead of at the bottom of the screen?
The other possibility is that I just have a bad flash in the mix somewhere and I need to heimdall back to stock and start over.
Cheers.
Click to expand...
Click to collapse
This happens with hellraised/leak-build ROMs with a longer-than-4-number PIN or password. At least to me. So either you're lying about the 4 numbers or your phone is weird.
Related
I rooted my Verizon GS3 with Jellybean last week. All went well but now I can not successfully change my Lock Screen PIN or set it to Swipe (no security) When I make any change it is accepted and I can lock the screen and my new PIN works. Then when I reboot the phone it changes back to the old PIN. When I change it to Swipe it will be on my old PIN after reboot. Also it doesn't always happen on the first reboot. I've been playing with it for a while and sometimes It reverts back to the old PIN after the second reboot.
I thought I had resolved this problem by setting the screenlock to none, then reboot, and then entering a new PIN. It seemed to work for about 3 days now it has reverted back to the old PIN.
This is unusual since I have rebooted the phone several times over the last 3 days and it didn't change till today
Any ideas as to resolve this?
Just to clarify, I already had the OTA Jellybean.
When I rooted, I used this procedure -
Step By Step - http://forum.xda-developers.com/showthread.php?t=2046439
angry_fisherman said:
I rooted my Verizon GS3 with Jellybean last week. All went well but now I can not successfully change my Lock Screen PIN or set it to Swipe (no security) When I make any change it is accepted and I can lock the screen and my new PIN works. Then when I reboot the phone it changes back to the old PIN. When I change it to Swipe it will be on my old PIN after reboot. Also it doesn't always happen on the first reboot. I've been playing with it for a while and sometimes It reverts back to the old PIN after the second reboot.
I thought I had resolved this problem by setting the screenlock to none, then reboot, and then entering a new PIN. It seemed to work for about 3 days now it has reverted back to the old PIN.
This is unusual since I have rebooted the phone several times over the last 3 days and it didn't change till today
Any ideas as to resolve this?
Click to expand...
Click to collapse
[SOLUTION] How To Fix "CM Lockscreen Has Stopped Working" Error in OnePlus One 38R
DISCLAIMER: I do not guarantee that this method will work for you, but it doesn't require ROOT or a custom recovery, etc. So, it's safe.
So, three days after OTA updating my OPO to XNPH38R, I randomly got the "unfortunately, CM Lockscreen has stopped working" error, and my phone became virtually unusable. I was devastated! I didn't want to wipe my phone. So, I decided to just got into Recovery and wipe the cache. But my custom recovery was freezing, so I decided to boot up my computer and try to re-flash recovery... And while I was waiting for my computer, I stumbled upon this work-around. I hope it helps someone.
WORK-AROUND METHOD:
Step 1.) Reboot your phone. (You'll have to hard reset it by holding the power button down for 5+ seconds.)
Step 2.) After the phone restarts and you're faced with the persistent error of death again, just press the power button once to turn off the screen. Then, turn the screen back on.
Step 3.) When you turn the screen back on in Step 2, the screen should be totally black with the capacitive buttons still lit. If this doesn't happen, try repeating Step 2 until it does.
Step 4.) Just leave the phone on with a blank screen and lit capacitive buttons for 20+ seconds. This seems to be an important step.
Step 5. Turn your phone screen off and back on again. For me, this fixed the persistent error. Yay! Hopefully it works for you. However, for me, the error came back again in only 5 minutes, and I had to repeat the entire procedure. Which is why we need Step 6.
Step 6.) Disable the lockscreen. This can be done by going to System Settings > Lockscreen > Screen Security > Screen Lock, and then choose "none" to disable the lockscreen entirely. This has kept the persistent error from recurring for me for 12+ hours.
And, that's it! That's all. You get to keep your data and information. And you get to keep the latest OnePlus One software version... However, unfortunately, you lose all lockscreen Security. But, you could maybe try installing a third-party lockscreen like "GO LOCKER" until OnePlus recognizes this problem and fixes it in the next update.
Good luck everyone! Lemme know if this works for anyone else besides me.
Marvelite said:
DISCLAIMER: I do not guarantee that this method will work for you, but it doesn't require ROOT or a custom recovery, etc. So, it's safe.
So, three days after OTA updating my OPO to XNPH38R, I randomly got the "unfortunately, CM Lockscreen has stopped working" error, and my phone became virtually unusable. I was devastated! I didn't want to wipe my phone. So, I decided to just got into Recovery and wipe the cache. But my custom recovery was freezing, so I decided to boot up my computer and try to re-flash recovery... And while I was waiting for my computer, I stumbled upon this work-around. I hope it helps someone.
WORK-AROUND METHOD:
Step 1.) Reboot your phone. (You'll have to hard reset it by holding the power button down for 5+ seconds.)
Step 2.) After the phone restarts and you're faced with the persistent error of death again, just press the power button once to turn off the screen. Then, turn the screen back on.
Step 3.) When you turn the screen back on in Step 2, the screen should be totally black with the capacitive buttons still lit. If this doesn't happen, try repeating Step 2 until it does.
Step 4.) Just leave the phone on with a blank screen and lit capacitive buttons for 20+ seconds. This seems to be an important step.
Step 5. Turn your phone screen off and back on again. For me, this fixed the persistent error. Yay! Hopefully it works for you. However, for me, the error came back again in only 5 minutes, and I had to repeat the entire procedure. Which is why we need Step 6.
Step 6.) Disable the lockscreen. This can be done by going to System Settings > Lockscreen > Screen Security > Screen Lock, and then choose "none" to disable the lockscreen entirely. This has kept the persistent error from recurring for me for 12+ hours.
And, that's it! That's all. You get to keep your data and information. And you get to keep the latest OnePlus One software version... However, unfortunately, you lose all lockscreen Security. But, you could maybe try installing a third-party lockscreen like "GO LOCKER" until OnePlus recognizes this problem and fixes it in the next update.
Good luck everyone! Lemme know if this works for anyone else besides me.
Click to expand...
Click to collapse
This is not working for me as i cant get my phone to the stage where the screen is black with only the buttons lighting up
Alternative solution
I too faced the same problem with the lockscreen after changing my wallpaper.
However the method mentioned above did not work for me.
I tried this instead.
1. Restart your phone by holding down the power button for a few seconds.
2. Turn off the screen.
3. Use the play music gesture: swipe down 2 fingers to start the music player. (tried the camera gesture but did not work).
The lockscreen problem disappeared since then. I have also turned off the lockscreen in the settings in fear of it reoccurring.
Hope this helps any of you suffering from the same problem.
Cheers!
I found another way to get your phone unlocked
So the solution that was provided by Marvelite did not work for me. I tried many many MANY times, but to no avail.
After looking around the interweb, I found some other instructions to root my phone (FYI I had no experience in rooting) and I was able to fix it without flashing or re installing anything.
So... what did I do. All I did was unlock my phone. I got my phone and remember saying it was unlocked, as you could use any carrier. That is not what I mean by unlock. What I mean by unlock is you cannot flash it or erase it. See the command line window below saying the phone is not unlocked and that is why I cannot flash it. I thought I had to flash it or erase it to get everything working. Just unlocking it fixed the CM Lockscreen Has Stopped Working error.
So what will you need to install on your computer and do to your phone.
1) Download adb-setup- 1.3.exe (if you type "adb-setup- 1.3.exe" into google, you will find a download) and install ADB system wide on your computer.
2) Put your phone in Fastboot mode and plug it into your computer. To do this, have your phone completely off and then hold the volume up and power button. You will see the screen of your one plus one in fastboot mode.
3) open up a command line window (as in my attached picture) and type fastboot oem unlock
THIS WILL RESET YOUR PHONE! After I typed in fastboot oem unlock, my phone reset itself and it was though I had hit the factory reset.
You can see from the command line window attachment, that I tried to flash my phone based on this workflow (http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061), but I did not even need to do this, because my phone was not unlocked. Then when I unlocked my phone, the problem was fixed.
I hope this works for those that have this horrible bug.
I unlocked my phone normally several times today using my pattern. Five minutes after I had unlocked it, I picked it back up and drew my pattern and it said it was incorrect. I tried several more times with no change. I was able to unlock the phone using my fingerprint, but I have no idea how my pattern changed without my permission. If my phone dies or restarts for any reason, I will need the pattern to unlock it, as you can't use fingerprint on start up. (I've had the same unlock pattern since my last phone, so I'm sure I am putting it in correctly.)
Has anyone else encountered this bug? Is there any way to create a new pattern using my fingerprint? Finally, how should I go about reporting this to Samsung?
Thanks.
Yes!
Same thing happened to me... S7 working great for first few days when suddenly it didn't accept my unlock pattern. I've been using the same pattern for awhile and unlocked the phone a few times that morning. After a few reboots it finally accepted my pattern again. Immediately disabled it and now using pin instead.
stevecr25 said:
Yes!
Same thing happened to me... S7 working great for first few days when suddenly it didn't accept my unlock pattern. I've been using the same pattern for awhile and unlocked the phone a few times that morning. After a few reboots it finally accepted my pattern again. Immediately disabled it and now using pin instead.
Click to expand...
Click to collapse
Did you just restart again and again until it worked? If it worked for you I might try it instead of the factory reset.
I've had lock screen issues with my LG V10, but not quite like yours. I use a pattern, not a password or fingerprint. Sometimes the screen is locked and I fail the pattern and the phone gets unlocked anyway. Usually, this is associated with having first touched a notification with the screen locked. What happens after the pattern fails (trace shows in red), is that the screen appears as it does when it's not locked and I just swipe and I'm in the application whose notification I touched. The LG V10 has a fingerprint reader on the power button, but I haven't programmed it since I heard it's not that great. This is a major security issue in my opinion, and I haven't read any other posts anywhere about it. So I don't know if it's specific to LG, the V10 or Marshmallow (it started with Marshmallow).
I can start a new thread if you believe our lock screen problems are unrelated (enough). Just let me know.
Bruce
Same thing happened to me. I'm THE ONLY one to ever use my phone and I went to open it and it was saying my pattern was invalid. I was able to use the thumb print pattern still though. However when I went to change the pattern in my settings I entered what used to be my pattern and it locked me out of my phone for an hour. I don't know how to change it.
bluefire2128 said:
Same thing happened to me. I'm THE ONLY one to ever use my phone and I went to open it and it was saying my pattern was invalid. I was able to use the thumb print pattern still though. However when I went to change the pattern in my settings I entered what used to be my pattern and it locked me out of my phone for an hour. I don't know how to change it.
Click to expand...
Click to collapse
Saw you had the same issue, so wanted to let you know. I restarted the phone and the old pattern started working again. Another person with this issue said that they had to restart several times, but it did work. So I'd give that a try, worked for me. Good luck!
It just happed to me. I restarted it and it accepted my pattern. I now have it set with pin instead.
Had the same issue as well! Samsung Galaxy S7, suddenly stopped recognizing my screen unlock pattern. Same solution as well; Restarted my phone and the problem went away.
Is there a way to disable the pattern feature if you are able to navigate the phone? Got locked out of Marshmallow on my MOTO G 3rd gen. phone after a pattern change; I was surprisingly able to just reboot into an unlocked phone. I've turned on adb debug access while I still have the opportunity.
I just had that issue. I was able to unlock with the pin, and reset the pattern and it now works again but it was freaky.
Same happened here. This morning the lock pattern on my S7 edge is forgotten by the phone.. Reboot doesn't help.
have the same problem today. i didn't change my pattern and it happened again. before i was using a PIN and I ended up factory reset and by this time I wouldn't want to do the reset factory settings as the last option.
The pin was also randomly stop working, I have mine set to pin and it did the same thing.
Me too!!!! Wtf!!
Mine has locked as well and I swipe the wrong pattern until it gives me the option to put in the back up pin but when I go to correct the swipe it wont let me in. I have tried everything all of you have suggested except the factory reset, I just can't believe that Samsung hasn't put out a fix for this yet.
Here is how you fix it
Method 1. Use 'Find My Mobile' feature on Samsung Phone
All Samsung devices come with "Find My Mobile" feature. In order to bypass Samsung lock screen pattern, PIN, password and fingerprint, you can just follow the below steps to get it done.
• First of all, set up your Samsung account and log in.
• Click "Lock My Screen" button.
• Enter new PIN in the first field
• Click "Lock" button at the bottom
• Within few minutes, it will change lock screen password to the PIN so that you can unlock your device.
tell me it work ??
Just an update to help out someone who might be going through this. This recently happened to me on my s6 edge.
Like the above comment suggests, go to "Find My Mobile". Once signed in, select the "UNLOCK MY DEVICE" option , (selecting the "Lock My Screen" option does not allow you to change the lock screen type afterwards).
Selecting Unlock my device will immediately unlock the phone and erase any lock screen patterns, fingerprints or pins that you might not remember, thus allowing you to set them up again!
Hope this helps!!
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
Also, one more thing. Doing the above ^ seemed to have solved a problem I was having with "Smart Lock" not working. So just as an FYI, going through that process might help you with that.
This just happend to my gf's s4 also she sent a text and then went to reply again a few moments later and her pin was invalid and it locked her out of her phone for 30 seconds, she just had to restart it once and it worked with the old pin again.
brobbeh said:
I just had that issue. I was able to unlock with the pin, and reset the pattern and it now works again but it was freaky.
Click to expand...
Click to collapse
same issues here, pattern just stopped working. im positive im using the correct pattern.
i can login with my pin, but i cant reset the pattern as it keeps asking for the current pattern.
how can i reset the pattern or change to pin / fingerprint?
ive restartted 2x and trying a 3rd now....
> Use 'Find My Mobile' feature on Samsung Phone
No this didn't work. It still requires my pattern, and tells me I'm doing it wrong...
It DID let me into the phone, which was nice. But the pattern problem persists...
...Update: I restarted the phone, and it came up and accepted my pattern.
This just happened to me on my phone and my tablet. I wound up having to do a factory reset on both! Way to go Samsung. These are the last Samsung devices I'll ever buy.
I've just got done a fresh install of the May update. After I finished restoring my settings, I went to set up my pin/fingerprint. As I was typing in the new pin, a system message appeared saying the settings app timed out, closing the settings app. I went back into the app to enter my pin/continue setting up my pin and it now says I need to put my pin in. So I just assumed my pin went through, I entered my pin and it says it's wrong. However, there is no pin lock on my phone. I can enter my phone from the lock screen, reboot, anything as if I don't have a pin. So I'm locked out of making a new pin, but not locked out of the phone.
Has anyone else came across this issue? I've never had this happen until the may update.
Thanks!
Pesty_Pupil said:
I've just got done a fresh install of the May update. After I finished restoring my settings, I went to set up my pin/fingerprint. As I was typing in the new pin, a system message appeared saying the settings app timed out, closing the settings app. I went back into the app to enter my pin/continue setting up my pin and it now says I need to put my pin in. So I just assumed my pin went through, I entered my pin and it says it's wrong. However, there is no pin lock on my phone. I can enter my phone from the lock screen, reboot, anything as if I don't have a pin. So I'm locked out of making a new pin, but not locked out of the phone.
Has anyone else came across this issue? I've never had this happen until the may update.
Thanks!
Click to expand...
Click to collapse
+1 same thing happened to me :/
hi my one vision every time when i unlock or lock restart device. any help?
normee66601 said:
hi my one vision every time when i unlock or lock restart device. any help?
Click to expand...
Click to collapse
I tried to use Action Launcer on my One Vision, it started doing EXACTLY that (restart after unlock).
The only way I could solve it was entering in recovery and wiping it clean. Here's how to do it:
1. Turn it off (hold Power Button for a few seconds)
2. Hold Power Button + Volume Down for some seconds
3. When you enter fastboot mode (with the android robot on screen), release the buttons
4. Use Volume Down to choose Recovery Mode and press Power Button to enter it
5. It will show the Android Robot with "No Command" on screen, when you get on this screen, hold the Power Button and press Volume Up then release the buttons, you will get into Recovery Mode screen
6. At Recovery Mode, choose Wipe data/Factory Reset and confirm when asked.
This worked on mine.
(link to procedure: https://www.hardreset.info/devices/motorola/motorola-one-vision/recovery-mode/)
It will wipe your phone clean. If after that it don't work right, you better get your phone to warranty.
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
I was wrong... It tried with other launchers, same problema. I've read that some phones with problem in the fingerprint sensor have this behaivor. As soon as you add fingerprint as the unlock option, It may reboot randomly or when you try to unlock.
I've wiped It again and confirmed this behavior on mine. I'm going after warranty on monday.
tys0n said:
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
Click to expand...
Click to collapse
I´ve got the same problem. How did you get it to factory rest?
badadam said:
I´ve got the same problem. How did you get it to factory rest?
Click to expand...
Click to collapse
I made factory reset from recovery.
Sent from motorola one vision.
tys0n said:
I made factory reset from recovery.
Sent from motorola one vision.
Click to expand...
Click to collapse
Thanks, did the same thing. Just had to google my way to finding out how to get into recovery.
tys0n said:
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
Click to expand...
Click to collapse
I've made new tests on my Motorola One Vision... That's the problem. As soon as you set the default USB mode to file transfer, my phone starts to reboot even without plugging in the USB cable...
I've wiped it clean, started with the bare minimum, just logged on Google Play Store. I activated the default USB mode to "File Transfer" on the Dev Options.... With no lock option, it works OK. As soon as you set ANY locking method (pin, pattern, fingerprint) it reboots when you try to unlock the phone...
Seems like the only way to solve it is to keep the default USB mode unchaged.
erick.noleto said:
I've made new tests on my Motorola One Vision... That's the problem. As soon as you set the default USB mode to file transfer, my phone starts to reboot even without plugging in the USB cable...
I've wiped it clean, started with the bare minimum, just logged on Google Play Store. I activated the default USB mode to "File Transfer" on the Dev Options.... With no lock option, it works OK. As soon as you set ANY locking method (pin, pattern, fingerprint) it reboots when you try to unlock the phone...
Seems like the only way to solve it is to keep the default USB mode unchaged.
Click to expand...
Click to collapse
Yes. For now we have to change usb mode from the notification panel each time, untill they got it fixed.
https://forums.lenovo.com/t5/motorola-one-vision/Bootloop-when-Developer-options-are-enabled/td-p/4444229
I disable fingerprint, now works perfect
normee66601 said:
I disable fingerprint, now works perfect
Click to expand...
Click to collapse
You disabled only fingerprint? Are you using any other unlock method, or just swipe? Mine got into bootloop even if I add a pattern.
when device restart swipe down status bar press setings then unlock and remove fingerprint
After you have changed the default USB mode to "transfer" on the Developer Options, you cant do that. If you have any sort of lock in place that's different from "swipe to unlock", your phone will reboot on any try to unlock it, even if you try to get to settings (it will ask to unlock, then when you try, it reboots).
If you get into the "bootloop", the only way to get out of it is to enter recovery and wipe the phone. The only way to avoid the bootloop is to a) don't change default USB mode to "transfer" on Developer Option or b) only have "swipe to unlock" as the lock option.
If you set a) and anything different then b), you get stuck in bootloop.
I was sad because I'd need to make a hard reset on my phone after this bootloop but then I tried to start it connected in my PC through USB and then BAM it worked out, boots without restarting, it worked out for me, it should for yours too!
Just wanted to confirm, for all those falling foul of this little bug, that Riverm4n's previous advice does indeed work. And saves the heartache of a full system reset..
Just wanted to clarify the guidance a little..
So with the phone on, and on the lockscreen, plug into your PC.
Let Windows do it's driver install thing of it's the first time it's been plugged in..
Then type in your unlock code on the phone..
Potentially could still go into the reboot again, just leave it plugged into your PC and the next time the phone comes on typing your unlock code in should see it unlock without rebooting!!
Don't forget to disable the developer settings or change the usb thing back!!!
riverm4n said:
I was sad because I'd need to make a hard reset on my phone after this bootloop but then I tried to start it connected in my PC through USB and then BAM it worked out, boots without restarting, it worked out for me, it should for yours too!
Click to expand...
Click to collapse
tonysonyhtc said:
Just wanted to confirm, for all those falling foul of this little bug, that Riverm4n's previous advice does indeed work. And saves the heartache of a full system reset..
Just wanted to clarify the guidance a little..
So with the phone on, and on the lockscreen, plug into your PC.
Let Windows do it's driver install thing of it's the first time it's been plugged in..
Then type in your unlock code on the phone..
Potentially could still go into the reboot again, just leave it plugged into your PC and the next time the phone comes on typing your unlock code in should see it unlock without rebooting!!
Don't forget to disable the developer settings or change the usb thing back!!!
Click to expand...
Click to collapse
Yeah the problem is because is enable fingerprint and default USB configuration was changed.
Just like to thank OP for this - just received a new Vision - & while setting up I had enabled Developer mode mainly due to problem with PC not seeing phone & 1 tip I read was for 'USB Debugging' to be switched on
- while in that menu I decided to force USB file transfer over 'cos of the annoyance having to select it each time I plugged phone in to transfer some pics/doc etc over
Next time I picked up phone it was in boot-loop & I thought it was broken ... PANIC STATIONS !!!!
Factory reset fixed it
- & since being new phone I didn't lose too much of the stuff I had been reinstalling/replacing (which were mainly apps to replace missing 'functions' I had on old phone such as a 'repeat notification/flash camera LED' if unread)
Did lose some game progress on a couple of games I have/had, which is annoying (wish we had a APK Data backup that didn't need root & which isn't Helium since that seems pretty unstable for me atm but then again it's not been updated for a while) but I think I can live with that
Once again thanks
Well, happened to me. I certainly wanted to avoid factory reset. It's a known bug being reviewed by Motorola/Lenovo. Happens when you change the USB connection default action in developer mode and you have any sort of screen lock.
Here is what I did to avoid factory reset, I had fingerprint lock with code.
1. After boot you get to screen lock. I you try to unlock with the code it reboots.
2. In that code enter screen, use a finger not enrolled. You'll see a message that fingerprint was not recognized.
3. Enter now your code and the device won't reset this time.
4. Go to developer options and rollback the USB default action to "no data transfer".
or
1. Factory reset
or
1. Wait for a ROM update
or
1. Return the device to seller and get another one
Avoiding factory reset!
mauro235 said:
Here is what I did to avoid factory reset, I had fingerprint lock with code.
1. After boot you get to screen lock. I you try to unlock with the code it reboots.
2. In that code enter screen, use a finger not enrolled. You'll see a message that fingerprint was not recognized.
3. Enter now your code and the device won't reset this time.
4. Go to developer options and rollback the USB default action to "no data transfer".
Click to expand...
Click to collapse
Thank you for sharing this, it actually allowed me to fix this without wiping everything! I hope they patch this issue soon. I had just finished setting everything up and I thought I would have to start again.
tys0n said:
Yes. For now we have to change usb mode from the notification panel each time, untill they got it fixed.
https://forums.lenovo.com/t5/motorola-one-vision/Bootloop-when-Developer-options-are-enabled/td-p/4444229
Click to expand...
Click to collapse
I've have the same problem on my Motorola One ACTION XT2013-4.