Related
I recently updated to 0089_US using CWM patched version & proceeded to perform the device encryption.
Everything went smoothly & the TPT performed as per normal.
However, three days ago, it suddenly started to act up & after a reboot, I started encountering a series of Force Close repeatedly on almost every other application I try to use.
Nothing I tried to do to recover from this problem resolved the problem.
As a last resort, I backed up all the data that I can access & performed a factory reset (Privacy | Factory reset).
After the factory reset, I setup my TPT & tried to perform the encryption again.
This is when I discovered that something is wrong.
I was not greeted with the usual dialogue that I encountered in the first successful encryption process.l
Instead, after confirming that I want to encrypt the tablet, all I get is a green android icon without any indication of any process going on in the background.
Pressing the Home button brings me back to the desktop minus the taskbar (Back, Home & Task switcher) at the bottom.
After the screen or screen lock timeout, the TPT will lock. Unlocking it will bring me back to the green android icon.
This is how it looks like:
Link to picture
This is how it should be if it was working normally:
Link to picture
I've already factory reset the TPT 3-4 times but each time, the situation is the same.
I've just tried reflashing 0089_US again & the situation has not changed.
Can someone advise me what is wrong here?
I've not placed any data back on my TPT at this point.
Please advise me as I need it to be encrypted.
Thanks!
Update: After reading this thread, I got the idea that if I can get my hands on a stock 0076_US NANDROID backup, perhaps I can get it back to the original state. My own NANDROID backups did not work because the data & system files did not successfully convert to .img files after the backup. I got an error that the CWM backup failed to generate the data backup because /sdcard/.android_secure cannot be found.
Konker
PS: I posted this at the Lenovo forum here but did not get any response.
Can I use CWM to restore system.img alone?
I'm wondering if its worth a try to restore a system.img to my TPT? I've since restored my data & apps using Titanium Backup.
I got a feeling that the system files are somehow not properly restored when performing the factory reset. Of course I would need a system.img file to restore so anyone who has a 0089_US system.img file to spare, I'll greatly appreciate it. Not sure if I'll lose root in the process.
Anyone with any clue as to what I'm facing, please point me in the right direction.
TIA!
Konker
Someone posted a nandroid for u in xda
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Thanks!
ker2gsr said:
Someone posted a nandroid for u in xda
Click to expand...
Click to collapse
Thanks!
I just saw it & am downloading now as we speak.
Are there any issues I should be aware of in using this Nandroid backup to roll back to 0075_US on my updated 0089_US TPT?
Please advise me accordingly.
Konker
konker said:
Thanks!
I just saw it & am downloading now as we speak.
Are there any issues I should be aware of in using this Nandroid backup to roll back to 0075_US on my updated 0089_US TPT?
Please advise me accordingly.
Konker
Click to expand...
Click to collapse
I don't think so I've downgraded to my .75 nandroid from the cm9 port everything went ok
Sent from my Galaxy Nexus using Tapatalk
Hey guys,
I tried using Rom Toolbox Pro to change my battery icon... after trying to install, the error "com.android.systemui has stopped working" continually popped up. I had to reboot by holding vol+, vol- and lock.
After rebooting, all soft buttons and the status bar are gone. I can't manage to get them back. I also can't manage to restore the battery icon - RTP prompted me to backup the icons before trying to install the new ones, and I did.
What have I done?
You've borked the system UI. Need to flash a new ROM or flash a factory image, I think.
Sent from my Nexus 7 using xda app-developers app
duloz said:
You've borked the system UI. Need to flash a new ROM or flash a factory image, I think.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Wow, that's so bull**** haha. Thanks for the quick reply
bulldozed said:
Wow, that's so bull**** haha. Thanks for the quick reply
Click to expand...
Click to collapse
So I went to restore my backup through CMW, it failed. Now I'm stuck on the Google screen. How do I flash it back to stock, in order to start all over again? I can get to the CMW page with the Android on his back, with "Start" up the top.
Appreciate any help!
bulldozed said:
So I went to restore my backup through CMW, it failed. Now I'm stuck on the Google screen. How do I flash it back to stock, in order to start all over again? I can get to the CMW page with the Android on his back, with "Start" up the top.
Appreciate any help!
Click to expand...
Click to collapse
That's not the clock work recovery. It's the bootloader. That's where you need to be to flash the image though.
First download the Nexus 7 image from https://developers.google.com/android/nexus/images#nakasijro03d
Once you have downloaded it extract the file twice until you see image-nakasi-jro03d.zip
Take that zip and move it to the directory where you have fastboot on your computer.
Open your command prompt pointing at that directory.
Then, type:
Code:
fastboot devices
if it returns a number you are good to go.
Next type:
Code:
fastboot -w update image-nakasi-jro03d.zip
This will wipe your user data and restore stock recovery. But you should be good to go.
geez, just reflash your rom, youll be ok.
El Daddy said:
snip
Click to expand...
Click to collapse
absolute legend. Thanks for the detailed reply, really appreciate it! I will give that a shot right now.
EDIT: haha took me five minutes to get it reflashed to stock. thanks again!
simms22 said:
geez, just reflash your rom, youll be ok.
Click to expand...
Click to collapse
haha sorry if my posts were a bit over the top, I was just sitting in bed having a play (with my Nexus 7........), then all of a sudden my tablet is seemingly wrecked simply from trying to change the battery icon... I FREAKED
Did something similar myself.
Just downloaded the factory image and flashed just the system.img file using fastboot and rerooted. A few system apps played up, most were fixed by wiping the cache but i had to delete all data from the contacts app, it resynced fine anyway.
To clarify extract the factory image to get the system.img and use the following
fastboot flash system system.img
Just rewrites the system partition.
Sent from my Nexus 7 using Tapatalk 2
The same thing happened to me trying to change the wifi icon. I guess Rom Toolbox doesn't play well with the Nexus 7?
Same thing on Galaxy Nexus... stumbled upon this thread searching for a solution. Was thinking we could restore from the backup that was made when swapping icons, but I guess that's not the case?
bulldozed said:
Hey guys,
I tried using Rom Toolbox Pro to change my battery icon... after trying to install, the error "com.android.systemui has stopped working" continually popped up. I had to reboot by holding vol+, vol- and lock.
After rebooting, all soft buttons and the status bar are gone. I can't manage to get them back. I also can't manage to restore the battery icon - RTP prompted me to backup the icons before trying to install the new ones, and I did.
What have I done?
Click to expand...
Click to collapse
Hello friends,
I am curious why, when such issues occured with your device, you did not contact Rom Toolbox Dev. to ask for help?
I am part of the support team from Rom Toolbox Pro, and I believe the post right before me is from someone who reached out to me to ask me about this, so allow me to explain the solution here real fast:
What happened is that when you changed the icon, it simply didn't work and messed up the UI. This occurs sometimes, and is the right time to restore a backup of the icons.
Problem is that now you can't restore, because the soft keys are all gone, and the Nexus 7 has no hard keys to do the dirty work.
So, here is the solution; you must use Root Browser to switch out the Systemui.apk and framework.apk files from the backup folder to the /system/app folder.
Where is the backup stored, you ask? Well, since it's very easy to break a rom by restoring the framework and systemui to the wrong rom, the backups are actually placed inside the app's data partition. This is to prevent tampering. If you are reading this post, then I assume you know what you're doing and are doing this with the EXACT same rom as the backups were created from.
The directory of the backups is /data/data/com.jrummy.liberty.toolboxpro/files/status_bar_backup/
Simply copy these over and paste them in /system/app, maybe renaming rather than deleting the old ones, just in case, then paste these and reboot your device.
And now your systemui and framework should be all restored.
Hope this helps! Be sure to contact the developer next time you need any help, We have arguably the best customer service of all the Play Store
And be sure to thank the one who referred me to this thread, if this helps!
Master Ramy said:
Hello friends,
I am curious why, when such issues occured with your device, you did not contact Rom Toolbox Dev. to ask for help?
I am part of the support team from Rom Toolbox Pro, and I believe the post right before me is from someone who reached out to me to ask me about this, so allow me to explain the solution here real fast:
What happened is that when you changed the icon, it simply didn't work and messed up the UI. This occurs sometimes, and is the right time to restore a backup of the icons.
Problem is that now you can't restore, because the soft keys are all gone, and the Nexus 7 has no hard keys to do the dirty work.
So, here is the solution; you must use Root Browser to switch out the Systemui.apk and framework.apk files from the backup folder to the /system/app folder.
Where is the backup stored, you ask? Well, since it's very easy to break a rom by restoring the framework and systemui to the wrong rom, the backups are actually placed inside the app's data partition. This is to prevent tampering. If you are reading this post, then I assume you know what you're doing and are doing this with the EXACT same rom as the backups were created from.
The directory of the backups is /data/data/com.jrummy.liberty.toolboxpro/files/status_bar_backup/
Simply copy these over and paste them in /system/app, maybe renaming rather than deleting the old ones, just in case, then paste these and reboot your device.
And now your systemui and framework should be all restored.
Hope this helps! Be sure to contact the developer next time you need any help, We have arguably the best customer service of all the Play Store
And be sure to thank the one who referred me to this thread, if this helps!
Click to expand...
Click to collapse
Hi Master Ramy,
I was the one who emailed JRummy.
I'm not sure I understand what you're saying actually. I guess your reply answers the OP's question - that is, in the event that we get the "com.android.systemui has stopped working" error , then we should do the stuff you said?
My issue is different... I hadn't swapped out my battery icons yet, cos I wanted to test the restore function in ROM Toolbox first before doing so. So I backed up both systemui and framework-res using ROM Toolbox, then simply tried to restore them using ROM Toolbox. But I got a toast notification saying "failed to get icons". I didn't get a big error like the OP's, but it was alarming enough that I didn't even try to change the icons in the end.
Are you saying that I should manually move my systemui and framework-res backups to system/app in order for ROM Toolbox to be able to restore them?
mlj11 said:
Hi Master Ramy,
I was the one who emailed JRummy.
I'm not sure I understand what you're saying actually. I guess your reply answers the OP's question - that is, in the event that we get the "com.android.systemui has stopped working" error , then we should do the stuff you said?
My issue is different... I hadn't swapped out my battery icons yet, cos I wanted to test the restore function in ROM Toolbox first before doing so. So I backed up both systemui and framework-res using ROM Toolbox, then simply tried to restore them using ROM Toolbox. But I got a toast notification saying "failed to get icons". I didn't get a big error like the OP's, but it was alarming enough that I didn't even try to change the icons in the end.
Are you saying that I should manually move my systemui and framework-res backups to system/app in order for ROM Toolbox to be able to restore them?
Click to expand...
Click to collapse
Yes, the post was in response to the OP talking about losing the soft keys and such Due to the different nature of your issue, I've sent you an email instead of responding here, so that we don't clog up this thread
Sorry I do not have enough permission to post in that Cyanogenmod thread. Pardon me.
Here is my issue...
Updated to 4.3 and realised camera and dialer does not work.
So I go back to 4.2.2. It got stuck at the rotating cyanogenmod boot.
Anyone can help? I do not want to lose all my apps data and files!
Thanks in advanced.
subaruwrx said:
Sorry I do not have enough permission to post in that Cyanogenmod thread. Pardon me.
Here is my issue...
Updated to 4.3 and realised camera and dialer does not work.
So I go back to 4.2.2. It got stuck at the rotating cyanogenmod boot.
Anyone can help? I do not want to lose all my apps data and files!
Thanks in advanced.
Click to expand...
Click to collapse
What do you think was going to happen? You can't dirty flash a new Rom, then dirty flash the old one.
This is what I would do:
Reflash 4.3 again in recovery ( this should let you boot back up into the OS)
Download Titanium and backup all apps + data
Go back to recovery
Factory reset your phone
flash 4.3 rom again
Flash the latest gapps from goo.im/gapps
subaruwrx said:
Sorry I do not have enough permission to post in that Cyanogenmod thread. Pardon me.
Here is my issue...
Updated to 4.3 and realised camera and dialer does not work.
So I go back to 4.2.2. It got stuck at the rotating cyanogenmod boot.
Anyone can help? I do not want to lose all my apps data and files!
Thanks in advanced.
Click to expand...
Click to collapse
ok i managed to get back on 10.2
But whenever I click on the Menu icon, I keep getting the error "Trebuchet has stopped.."
I have already clear the data and cache for Trebuchet as advised by many via Google. However, the problem persist.
Any idea?
subaruwrx said:
ok i managed to get back on 10.2
But whenever I click on the Menu icon, I keep getting the error "Trebuchet has stopped.."
I have already clear the data and cache for Trebuchet as advised by many via Google. However, the problem persist.
Any idea?
Click to expand...
Click to collapse
Plug your phone into the computer
download this program:
http://forum.xda-developers.com/showthread.php?p=36499906
use this to backup all your apps + data to your computer
then do the factory reset.
You updated the bootloader and radio as well right?
Sent from my Nexus 4
Best solution will be a total wipe - you can either download stock factory image using android SDK tools or use one of the toolkits such as Wugfresh toolkit. If you can backup your photos and important stuff on your phone besides apps I would go for this
If you want to go back to 4.2.2. Flash factory image, root and flash CM 10.1.2 and if you would like to go for CM 10.2 nightlies than go for the 4.3 factory image. The Wugfresh toolkit will enable you both options. H&
Sent from my Nexus 4 using xda app-developers app
Currently using latest Philz Recovery (problem existed on other recoveries as well) and I'm unable to fully restore from backup. After restoring I get non-stop force closes and not responding errors. Only fix is to perform a Data Wipe after restore, which isn't so bad since Restored Rom is intact even if needing to reinstall all apps and settings from scratch. Problem started after updating via stock recovery to OTA/MJA, which has tripped my Knox. I have tried several things, including clearing cache and battery pulls Wandering if anyone has any suggestions.
Kingmdm said:
Currently using latest Philz Recovery (problem existed on other recoveries as well) and I'm unable to fully restore from backup. After restoring I get non-stop force closes and not responding errors. Only fix is to perform a Data Wipe after restore, which isn't so bad since Restored Rom is intact even if needing to reinstall all apps and settings from scratch. Problem started after updating via stock recovery to OTA/MJA, which has tripped my Knox. I have tried several things, including clearing cache and battery pulls Wandering if anyone has any suggestions.
Click to expand...
Click to collapse
not sure if it would help but here is a link for the mja firmware without the knox bootloader
http://forum.xda-developers.com/showthread.php?t=2338919
I think I'm past that point since I applied mja day 1 of release. I believe I'm stuck with Knox bootloader, for now.
Sent from my SPH-L720 using Tapatalk
Same problem. Data wipe didn't even work for me. I still got system force closes. Had to restore everything from scratch.
Kingmdm said:
Currently using latest Philz Recovery (problem existed on other recoveries as well) and I'm unable to fully restore from backup. After restoring I get non-stop force closes and not responding errors. Only fix is to perform a Data Wipe after restore, which isn't so bad since Restored Rom is intact even if needing to reinstall all apps and settings from scratch. Problem started after updating via stock recovery to OTA/MJA, which has tripped my Knox. I have tried several things, including clearing cache and battery pulls Wandering if anyone has any suggestions.
Click to expand...
Click to collapse
You have to check process SE context JB 4.3 settings in philz recovery UNDER misc Nandroid settings before making back up 
I also uncheck md5 box, but it's all preference I guess, as long as you check the 4.3 box you will be good to go
@prc292
Sent from my SPH-L720 using Tapatalk
That's awesome. Thanks. Been working on a 4.3 flashable zip and can't keep restoring from scratch everytime an install fails. Had me at a stand still. Back in business!
Sent from my SPH-L720 using xda app-developers app
ParkerParker said:
You have to check process SE context JB 4.3 settings in philz recovery UNDER misc Nandroid settings before making back up 
I also uncheck md5 box, but it's all preference I guess, as long as you check the 4.3 box you will be good to go
@prc292
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thanks! I was able to successfully restore a backup with this setting.
Kingmdm said:
Thanks! I was able to successfully restore a backup with this setting.
Click to expand...
Click to collapse
I have the same problem with the Philz backup since the MJA upgrade. Would one of you mind being more specific about what settings change need to be made? I went through all the Philz settings (I have version 5.18.2) but am not sure where to make the change. Thank you.
bcwsfo said:
I have the same problem with the Philz backup since the MJA upgrade. Would one of you mind being more specific about what settings change need to be made? I went through all the Philz settings (I have version 5.18.2) but am not sure where to make the change. Thank you.
Click to expand...
Click to collapse
Go into recovery, go to restore /backup.. Scroll to bottom, there Nandroid settings is located open and use instructions from post above yours,,, I had the Same thing happen to me my first time trying to restore,,, do before making a back up
Sent from my SPH-L720 using Tapatalk
ParkerParker said:
Go into recovery, go to restore /backup.. Scroll to bottom, there Nandroid settings is located open and use instructions from post above yours,,, I had the Same thing happen to me my first time trying to restore,,, do before making a back up
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thank you so much for your prompt reply. I found the settings and changed them. I thought I was the only one who has the restore problem with Philz Recovery.
ParkerParker said:
You have to check process SE context JB 4.3 settings in philz recovery UNDER misc Nandroid settings before making back up 
I also uncheck md5 box, but it's all preference I guess, as long as you check the 4.3 box you will be good to go
@prc292
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I was able to restore successfully from 1 backup after making change (above post) but problem came back when trying to restore from a more current backup made with the settings. Still had to perform a data wipe after restoring rom.
Edit: I just checked and this setting doesn't stick after rebooting, which explains why subsequent backup/restore had errors.
Kingmdm said:
I was able to restore successfully from 1 backup after making change (above post) but problem came back when trying to restore from a more current backup made with the settings. Still had to perform a data wipe after restoring rom.
Edit: I just checked and this setting doesn't stick after rebooting, which explains why subsequent backup/restore had errors.
Click to expand...
Click to collapse
Sorry ya I forgot about that, it happened to me also once, but it is sticking for me now along with my background /theme change,, I still check those settings out of habit every time I restore or back up, md5 box checks itself on and off also occasionally
Sent from my SPH-L720 using Tapatalk
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
ent3rpryze said:
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
Click to expand...
Click to collapse
Are you sure you're hitting the right numbers? They'll be in a different position every time.
Heisenberg said:
Are you sure you're hitting the right numbers? They'll be in a different position every time.
Click to expand...
Click to collapse
I am. 100% certain.
it really seems as if my password was for some reason changed. before someone asks i am definitely using the correct pin. its the same PIN i've been using for years.
how do i regain control of my phone?
ent3rpryze said:
I am. 100% certain.
it really seems as if my password was for some reason changed. before someone asks i am definitely using the correct pin. its the same PIN i've been using for years.
how do i regain control of my phone?
Click to expand...
Click to collapse
i rebooted to recovery mode and i discovered that i moved my backup to my laptop. so now backup file is available.
can i just wipe my phone and reinstall the purenexus rom which is still on my phone
ent3rpryze said:
i rebooted to recovery mode and i discovered that i moved my backup to my laptop. so now backup file is available.
can i just wipe my phone and reinstall the purenexus rom which is still on my phone
Click to expand...
Click to collapse
Yes, if you clean flash the ROM you'll be able to get back into it. Had you restored a nandroid backup recently by any chance?
Heisenberg said:
Yes, if you clean flash the ROM you'll be able to get back into it. Had you restored a nandroid backup recently by any chance?
Click to expand...
Click to collapse
thanks a lot for clarifying that. i guess i have no other option.
has this been known to happen? scrambling PIN causing the pin to change.
I dont have a recent nandroid backup because my purenexus flash is only days old. is there a way to automate nandroid backups? is it wiser to keep the backups on the phone?
ent3rpryze said:
thanks a lot for clarifying that. i guess i have no other option.
has this been known to happen? scrambling PIN causing the pin to change.
I dont have a recent nandroid backup because my purenexus flash is only days old. is there a way to automate nandroid backups? is it wiser to keep the backups on the phone?
Click to expand...
Click to collapse
I've never seen this happen before. I'm pretty sure you can use Tasker to automate backups. I usually advise people to keep at least one backup or ROM zip on their phone, just in case.
IT HAPPENED AGAIN!
Per the ever hepful Heisenberg's recommendation, I wiped my phone and reflashed purenexus. This was yesterday. Everything went smoothly. Recreated my security PIN. Was able to unlock my phone with it without incident...until just now. Incorrect PIN error 3 times.
What is going on?!?!
It should be noted that both times this has happened has come after I turned my phone off. This time I happened to be charging my phone while it was off. I can't recall if it was the same case the first time it happened. Is this a purenexus issue?
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
ent3rpryze said:
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
Click to expand...
Click to collapse
This is usually over necessary after a user has created (and later restored) a nandroid backup without removing lockscreen security first. Are you saying you hadn't done this at all prior to the problem occurring?
Heisenberg said:
This is usually over necessary after a user has created (and later restored) a nandroid backup without removing lockscreen security first. Are you saying you hadn't done this at all prior to the problem occurring?
Click to expand...
Click to collapse
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
ent3rpryze said:
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
Click to expand...
Click to collapse
When making a nandroid (backup) in TWRP remove any pin, patter or fingerprints before backup or getting locked out will continue.
elevatorguy said:
When making a nandroid (backup) in TWRP remove any pin, patter or fingerprints before backup or getting locked out will continue.
Click to expand...
Click to collapse
thanks for that, but i believe i did that because i backuped a clean factory 6.0.1, sans any security setup. not sure if that was necessary but that's what i did.
ent3rpryze said:
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
Click to expand...
Click to collapse
The problem isn't with the ROM, I (along with what I'm guessing is pretty much every other user) use fingerprint and/or PIN/pattern security on Pure Nexus with no issues. A nandroid backup is one of those backups you create with TWRP, so yes it's what you described. But this problem shouldn't be occurring on a clean flash of Pure Nexus, can you please explain in detailed steps how you installed the ROM?
ent3rpryze said:
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
Click to expand...
Click to collapse
On Marshmallow, the scramble pin option is bugged if you use a long pin. Some rom devs choose to leave this out entirely. I haven't played with it to determine the cut off point but 4 digits is fine. I think I tried 8 digits once and it locked me out.
Sent from my Nexus 5X using Tapatalk
ent3rpryze said:
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
Click to expand...
Click to collapse
Awesome.. Thanks a bunch for posting this... I am using Oneplus 3T , Resurrection Remix 5.7.4 ( Marshmallow) . Had turned on Scrambled PIN.. Ran into same issue as yours.. Last option left for me was to do factory reset from TWRP but I was scared to lose Google Authenticator Setup on my phone and many other things... Your solution saved me!! :good::good:
I also had a similar problem:
- freshly installed Carbon ROM with TWRP
- added lockscreen password in phone
- locked screen
- tried accessing using password
The password just fails. Using a shorter password works normally. The failing password is 13 characters long.