Related
I backed up my Olympus ROM instance so I could test out the new Hurricane ROM, but now when I go to restore, it is a completely screwed up backup apparently. The background is totally wrong, and whenever I unlock the phone I get SetupWizard FCes, and a completely black and inoperable home screen. Looks like I totally lost my backup that I just made this morning before installing the new ROM.
Has this happened to anyone else?
algorhythm said:
I backed up my Olympus ROM instance so I could test out the new Hurricane ROM, but now when I go to restore, it is a completely screwed up backup apparently. The background is totally wrong, and whenever I unlock the phone I get SetupWizard FCes, and a completely black and inoperable home screen. Looks like I totally lost my backup that I just made this morning before installing the new ROM.
Has this happened to anyone else?
Click to expand...
Click to collapse
Wipe everything 3x and do the restore again. That should work, unless somehow the backup is corrupt although I have never seen that happen.
crawrj said:
Wipe everything 3x and do the restore again. That should work, unless somehow the backup is corrupt although I have never seen that happen.
Click to expand...
Click to collapse
Tried wiping cache, data and dalvik 3 times. Still same thing. Funny, I rebooted after getting the SetupWizard FC and I get the normal loading screen, but I can actually turn the screen off with the power button and see the CRT Off animation, but when I turn it back on I still just see the loading screen and it just sits there.
Guess it's corrupt Oh well.
algorhythm said:
Tried wiping cache, data and dalvik 3 times. Still same thing. Funny, I rebooted after getting the SetupWizard FC and I get the normal loading screen, but I can actually turn the screen off with the power button and see the CRT Off animation, but when I turn it back on I still just see the loading screen and it just sits there.
Guess it's corrupt Oh well.
Click to expand...
Click to collapse
Try wiping than flashing Olympus and than restore data only.
The data's part of the backup may not be corrupted.
Sent from my SPH-D700 using XDA App
Now that someone made this thread, I'll take the time and explain my issue, I have an MD5 mismatch for all 3 backups I made in the past. I know how it mismatched as well, I renamed the backups to something that actually made sense,like Eclair, EC05, & EG22, problem is, tried restoring any of them, I get mismatch, also, advanced restore also says MD5 mismatch.
P.S. To whoever made clockwork mod, you need to add the option to override the MD5 Mismatch, and also, why use MD5? Its an outdated form of Checking for the Integrity of files, there are newer methods.
I had some trouble with a backup once it turned out that my SD card was too full to create the full backup file.
counterfeit187 said:
I had some trouble with a backup once it turned out that my SD card was too full to create the full backup file.
Click to expand...
Click to collapse
Seems like that was it. Had 0 space once I booted to a new ROM.
Thanks
it would be nice if there was a way to pick the name of your backup instead of it auto generating by time/date..
I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS
polish_pat said:
I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS
Click to expand...
Click to collapse
Please help me someone. I tried the EFS fix here with no success. I tried to restore via odin, factory reset, every time i finish initial setup and restore my apps and reboot, it bootloops.
Shot in the dark, but disable auto installing of apps/restoring apps. Could be that it is triggering the bootloop due to an incompatible app with X-Note.
If no good. You gotta be brave and strip that badboy back with a full wipe/dalvik/cache, reflash your stock image (get shot of recovery also) then see if it can get past the bootloop (don't forget to remove your SD Card also if you have one) - Give it shot, see what you come up with.
Also if you're on an N9005 model, head over to Djembays thread and grab an image of him, seems to have gotten a lot of people out of issues (JayTheNut uses his images when he messes up) -
Lemme know how you get on, I'll have a nose around see what else it could be.
radicalisto said:
Shot in the dark, but disable auto installing of apps/restoring apps. Could be that it is triggering the bootloop due to an incompatible app with X-Note.
If no good. You gotta be brave and strip that badboy back with a full wipe/dalvik/cache, reflash your stock image (get shot of recovery also) then see if it can get past the bootloop (don't forget to remove your SD Card also if you have one) - Give it shot, see what you come up with.
Also if you're on an N9005 model, head over to Djembays thread and grab an image of him, seems to have gotten a lot of people out of issues (JayTheNut uses his images when he messes up) -
Lemme know how you get on, I'll have a nose around see what else it could be.
Click to expand...
Click to collapse
I dont think you read the thread. I'm not on xnote anymore, i'm on stock firmware, MJ4, i also have a W8 and the EFS script fix is for international version. I've odined back to stock and all the issues i'm having are also present on stock firmware
polish_pat said:
I'm not on xnote, i'm on stock firmware, MJ4, i also have a W8 and the EFS script fix is for international version
Click to expand...
Click to collapse
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?
I have a feeling background WiFi scanning is enabled in Settings -> WiFi -> Advanced - I don't think any of the newer ROM updates ever managed to have that not bootloop your phone on reboot. In case you're stumped and can't find the setting, you'll have to hit the menu key on the WiFI screen.
radicalisto said:
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?
Click to expand...
Click to collapse
I dont think so, unless flashing Xnote 6.0 or using odin to restore stock does that. Thats pretty much all I did, but i think i might have done something that might have fixed the problem, i'm not sure yet, but i'll confirm shortly
radicalisto said:
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?
Click to expand...
Click to collapse
I use the N900T (T-Mo) version, though I guess it's pretty similar to the W8. Unfortunately I don't know anything about the efs side of things on the N900T or equivalents. I've been avoiding the backup and restore functionality in TWRP since it was widely reported to cause bootloops in the first few weeks after release anyways. Have you tried the bootloop fix method over at the T-Mobile N900T forum? I forget what the process exactly was but people reported great success using it (including those who intentionally recreated the problem to test the fix). I did have a similar boot loop issue on my Note 1 which was fixed doing a complete Odin restore with a full factory image (bootloader, system, modem, kernel, recovery, etc. - the entire complete factory restore). I don't know if such a package exists for the N900W8 and that's something I wouldn't use the wrong variant's version of.
odin was one of the first thing i tried, as mentionned the problem was on 100% stock device. Now i've tried formating SD cards and i was able stop the bootloops but now instead i get a worse problem when my phone keep giving me force closes and everytime i dismiss one, another one pops back up and its just a FC Loop:crying:
I have an W8...I also had terrible boot loop problems and I can't quite remember the cause, but this is what fixed it.
Obviously I can't stress enough to read this and type this in very carefully, and that if your phone stops working, turns into a robot, explodes, or tries to kill your dog I'm not responsible .
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command"
3. Hit "Select" (lower right corner)..Do not select any specific folder, just hit select..
4. keyboard will open, type in the following commands, make sure you put the spaces and / where they need to be, it needs to look exactly as outlined..
mke2fs /dev/block/mmcblk0p12
Hit Go - The command will run.
Clear the box, type the following command
mkdir /efs
Hit Go - The command will run.
Clear the box, type the following command
mount -t ext4 /dev/block/mmcblk0p12 /efs
Hit Go - The command will run.
Do a factory reset, reboot system
Can't remember where I got this from, only saved the text not the forum >.<
stucked
Hello guys .... I wanna say first ... that I tryed all options and all efs backups etc etc ... everything works just fine back up my efs . and restore but .. when I try to register my phone on network ends like this :
- only emergency calls
- when try to insert a new sim card my n9005 just reboot when search for network also ... is charging but allways remain at 8-10% no more up .
I tryed all kind of stuff ... made back ups .... and tryed install stock firmware etc ... rooting and did anything ... I will apreciate any kind of help ...I just wanna tell you I am close to deat ... becouse is my wife phone and still does not know I messed up with
polish_pat said:
EDIT: I'm offering a 50$ bounty to anybody that gives me a solution that fixes my phone, paid in full by paypal
I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS
Click to expand...
Click to collapse
Hey dude i think xnote 6 is mk2 based, so what basically is going wrong is that you're trying to downgrade your bootloader. please try flashing an mk2 stock rom ( or an mj7) via odin, that should fix it ..
just my 2 cents
Hi guys i tried everything my phone was in a constant state of bootloop and wouldnt connect to any carrier. Then i came across this thread http://forum.xda-developers.com/showthread.php?t=2567133 and now my phone is working, still wont connect to a carrier but the phone is now stable which is a good thing. Hope this helps some of you :fingers-crossed:
Thanks for all the input, as of now, i was able to stop the boot-looping on stock rom, but I do still have major issues like i cannot install twrp, by goomanger it tell me its done but when i reboot into recovery, i end up in stock recovery. And yes, i'm rooted. Also i cannot format my SD card from the OS, it keep telling me the card is being checked all the time. I also have a lot of other small issues that should not be there on a fresh install. i honestly dont know what screwed up so bad but i will try some of the solutions mentioned above and report back.
To me that sounds like your partitions are all screwed up have you tried flashing using a pit file?
Sent from my SM-N9005 using xda app-developers app
Steeno78 said:
To me that sounds like your partitions are all screwed up have you tried flashing using a pit file?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Never. I'm def not that newbish. I dont know whats happening but everytime i format the phone it gets a little better.
Sent from my SM-N900W8 using Tapatalk
So I saw the articles and threads on 12/25 reporting do not Disturb until next alarm was gone. After noting mine was gone too I turned off my 6P and went back to using my Galaxy S6 for 2 days.
I turned my 6P back on to get a file off it last night and noticed do not disturb symbol was on the top status bar. I pulled the toggles down saw it was lit with 'alarms only' under it. I clicked the toggle and it does not turn off. I tried double clicking and tried holding down toggle. I Pressed the volume up button and I can change volume for alarms and media, but ring tone slider is faded out so I can't modify it.
Then I went into settings and confirmed in the notifications section that there is no do not disturb schedule turned on and no apps have access to do not disturb. I also could not turn it off from inside settings either. I did a quick Google search and found a thread on 12/23 and 12/14 of this being reported on Android Central. Before this until next alarm disappeared. Every thread has no resolution if there was one.
I tried clearing all user cache and rebooting but it's still turned on. I also booted into twrp and wiped cache in there. It still shows! So it seems to be something in the system. I am rooted (systemless) but completely stock 6.0.1. I's anyone else experiencing this or have any suggestions?
Try reflashing /system only? Or flash the factory image but remove the -w from near the end of the batch file to preserve your userdata. Then just flash TWRP and systemless root again, after verifying it's fixed, of course.
fury683 said:
Try reflashing /system only? Or flash the factory image but remove the -w from near the end of the batch file to preserve your userdata. Then just flash TWRP and systemless root again, after verifying it's fixed, of course.
Click to expand...
Click to collapse
Too bad I didn't do a nandroid backup till last night after this happened. So I was fearing what you said might be the only solution, to just flash back to stock image and root again. Any other suggestions to avoid that?
AndroidPurity said:
Too bad I didn't do a nandroid backup till last night after this happened. So I was fearing what you said might be the only solution, to just flash back to stock image and root again. Any other suggestions to avoid that?
Click to expand...
Click to collapse
If you don't wipe userdata (remove the -w flag as I described) you won't need a nandroid. All your apps will remain intact, if you remove the -w.
Download the factory image, unpack it, edit the flash-all.bat to REMOVE the -w from the file (it's near the end), save the batch file. Put your phone in bootloader mode, run the factory image as you would normally. When complete, you'll be on a fresh install with all your data. This of course assumes the issue is /system related not /data related.
You could still take a nandroid in hopes that you could flash fully clean (without modifying the batch file) and then restore /data only from the nandroid. You'd need to offload that backup somewhere though because it would get wiped with the factory image.
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
fury683 said:
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
Click to expand...
Click to collapse
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
XxMORPHEOUSxX said:
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
Click to expand...
Click to collapse
Thanks, I was not aware. I thought it was just FUBAR if you didn't remove it before making the backup.
fury683 said:
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
Click to expand...
Click to collapse
Haha good thing I didn't attempt yet! Lol! Thanks for coming back with the warning. I'll try everything later tonight or tomorrow. I'll follow up with the results or if I come across any issues.
XxMORPHEOUSxX said:
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
Click to expand...
Click to collapse
Thanks! So just to clarify these are the options for nandroid security lock work around..
1.) Set lock security to nothing (just swipe), then do the nandroid backup
2.) Leaving pin/finger print security setting - delete the locksettings.db file using twrp. But is deleting it done before or after making the nandroid backup? Or after flashing the nandroid backup right before rebooting? Thanks!
AndroidPurity said:
Haha good thing I didn't attempt yet! Lol! Thanks for coming back with the warning. I'll try everything later tonight or tomorrow. I'll follow up with the results or if I come across any issues.
Thanks! So just to clarify these are the options for nandroid security lock work around..
1.) Set lock security to nothing (just swipe), then do the nandroid backup
2.) Leaving pin/finger print security setting - delete the locksettings.db file using twrp. But is deleting it done before or after making the nandroid backup? Or after flashing the nandroid backup right before rebooting? Thanks!
Click to expand...
Click to collapse
I believe @XxMORPHEOUSxX was just saying that if you were to make a nandroid and did not remove your PIN/password first, you can still use it by using his steps mentioned. If you remove it BEFORE the nandroid, you should be able to just restore it without issue. I haven't personally done either of those things, so you may want to wait until someone who has done it chime in, but that was my understanding.
fury683 said:
I believe @XxMORPHEOUSxX was just saying that if you were to make a nandroid and did not remove your PIN/password first, you can still use it by using his steps mentioned. If you remove it BEFORE the nandroid, you should be able to just restore it without issue. I haven't personally done either of those things, so you may want to wait until someone who has done it chime in, but that was my understanding.
Click to expand...
Click to collapse
Yes exactly. If you already made a nandroid and forgot, restore it and then erase that file. I've done it and it works.
fury683 said:
If you don't wipe userdata (remove the -w flag as I described) you won't need a nandroid. All your apps will remain intact, if you remove the -w.
Download the factory image, unpack it, edit the flash-all.bat to REMOVE the -w from the file (it's near the end), save the batch file. Put your phone in bootloader mode, run the factory image as you would normally. When complete, you'll be on a fresh install with all your data. This of course assumes the issue is /system related not /data related.
You could still take a nandroid in hopes that you could flash fully clean (without modifying the batch file) and then restore /data only from the nandroid. You'd need to offload that backup somewhere though because it would get wiped with the factory image.
Click to expand...
Click to collapse
So I downloaded the MMB29M factory image, and ran the flash-all.bat. Unfortunately I forgot to remove the -w. No biggie though I had no important pictures or documents that needed backed up. Just will have to sign into all my apps all over again. Anyways it did resolve the DND being stuck on, I figured it would since it went completely back to stock including user data.
However I am still baffled at how that could have happened when it was fine after the systemless root and never played around with the root files afterwards. No exposed modules or anything. Anyways I am about to flash twrp and install the new 2.65 SuperSU to root again. So I guess only time will tell if it happens again. Thanks for the help gentlemen!
Same problem but im on a stock phone. Not even rooted
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.
Earlier I was on Megapixel Rom running february vendor img. I flashed my PN ROM backup thru flashify then it boots up with my security lock pattern. It shows that my pattern is not correct. I am rebooting to y TWRP but still it doesn't show me any files and I cant flash a zip rom. Someone help me (((
Try using different decryption method...
Your problem seems to be unsolvable right now. This is a known bug or vulnerability in the latest release of TWRP build. I am sorry.
Gameplay_Ethan said:
Your problem seems to be unsolvable right now. This is a known bug or vulnerability in the latest release of TWRP build. I am sorry.
Click to expand...
Click to collapse
wow I am in shock right now, idk what to do.. my computer doesn't recognize my phone even though Im on bootloader/twrp
lesterinidad said:
wow I am in shock right now, idk what to do.. my computer doesn't recognize my phone even though Im on bootloader/twrp
Click to expand...
Click to collapse
factory reset?
v12xke said:
factory reset?
Click to expand...
Click to collapse
idk what I did but the files suddenly shows but it wipes my media.. only problem now is whenever I reboot into TWRP it asks me the password to decrypt and after I booted up it also ask me my password to start my device like a pop up message
lesterinidad said:
idk what I did but the files suddenly shows but it wipes my media.. only problem now is whenever I reboot into TWRP it asks me the password to decrypt and after I booted up it also ask me my password to start my device like a pop up message
Click to expand...
Click to collapse
See the sticky thread in General: https://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
You might be better off flashing the full factory image to start over and then reflash whatever you want in terms of recovery and custom rom. I did that when I was in the same situation as you. But I have never successfully restored a nandroid backup on the 6P and I never had that problem with any other phone I have ever owned. Different versions of TWRP only give me different issues when I try to restore a backup. I've had bootloops. I've had TWRP ask for a password even though I removed security before making the back up as people advise. I've had backups that seemed to restore until I started getting error messages that there was something wrong with my device and I should contact the phone manufacturer. I've given up on Nandroid backups on this phone.