Database Users

The process com.android.phone has stopped unexpectedly

I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger

Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.

obelisk79 said:
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
Click to expand...
Click to collapse
Will that work on MCR 2.2 as well? I'll look into that. Is it something I can do from recovery?
Ceger

yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.

obelisk79 said:
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
Click to expand...
Click to collapse
Do you need to do both? Wiping the dalvik cache created lots of app fc issues, which would be fine if the phone actually worked. Still won't make or receieve calls.
And thank you for the assistance.
Ceger
Edit. Clearing the boot cashe got rid of the FC issues. However, still have same issue with the phone app. This is so annoying.

honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.

Ceger said:
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Click to expand...
Click to collapse
use these commands to clear cache
rm -r /data/boot-cache/
rm /data/dalvik-cache/
once you finish then reboot.everything should go away...

he's done that already.

then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.

obelisk79 said:
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Click to expand...
Click to collapse
Done and done and no difference.
reddick said:
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
Click to expand...
Click to collapse
Done, even manually moved some files in case they were corrupted at one point. Very bad move, nandroid backup was my friend there.
Guess a wipe will be the only option then. How annoying.
Thanks for all of your inputs.
Ceger

Another thought... would updating my phone with latest kernal compile possibly do the trick? Or how about a replacement process for google.com.phone?
Ceger

Interesting theory.... worth a try.

i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there

toastcfh said:
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
Click to expand...
Click to collapse
Actually, the fix was much simpler. I wiped the SD ext partition and just did a Recovery Wipe. It went back to stock modded rom that remained rooted. I then used Titanium to reinstall my apps with data and then MyBackup to get back some settings such as my scenes, etc. and all was good. Took all of 30 minutes to get my Hero back up and running in better condition than before.
Thanks all for the assists.
Ceger

com.android.phone
com.android.phone
i am facing this prob on cyanogen mod10....when ever i reboot my optimus 2x....i face this damn problem
help plzzzzzzzzzz.....!!!!!

Nexus Imprint Issues After Nandroid Backup Restore

Has anyone had issues setting up Imprint after importing a nandroid backup?
I had to RMA my 6P due to a faulty charging port and I can successfully set up Imprint in the factory state, however, after I import the backup, it won't allow me to set it up.
I've tried to do just a data import, a full nandroid import...pretty much every single option and constantly reflashing to stock to retry. I'm at a loss because it's definitely not a hardware problem as I can set it up during stock.
As soon as I click next to train my fingerprints, it flashes: "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger."
Has anyone ever run into this issue? Thanks for your help!

Never and I mean never restore a nandroid from one device to another. There are device specific files in that nandroid. Just hope you didn't kill your efs partition which kills your IMEI and in turn makes it not connect to any network.

RaysBucsBolts said:
Has anyone had issues setting up Imprint after importing a nandroid backup?
I had to RMA my 6P due to a faulty charging port and I can successfully set up Imprint in the factory state, however, after I import the backup, it won't allow me to set it up.
I've tried to do just a data import, a full nandroid import...pretty much every single option and constantly reflashing to stock to retry. I'm at a loss because it's definitely not a hardware problem as I can set it up during stock.
As soon as I click next to train my fingerprints, it flashes: "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger."
Has anyone ever run into this issue? Thanks for your help!
Click to expand...
Click to collapse
As already stated you should never restore a backup from a different device. If you had a pin and fingerprint setup when you made the backup then it will not restore properly on any device. A thread has been pinned in the general section about TWRP'S issues with lockscreen security and backups.

If you can get into adb try this after restoring:
rm /data/system/locksettings.db
rm /data/system/*.key
If this doesnt work, go to twrp file manager and manually delete the files.
As mentioned above, before backing up you should always remove security.

It was mentioned in the TWRP thread that you should NEVER make a Nandroid Backup before disabling the fingerprint and swipe gestures. If you did a Nandroid Backup without having removed the security options first, you won´t be able to use it.

I am having the same issue after getting my new phone and trying to do the same thing. Each device seems to have some kind of Sensor ID or something else that stops the scanner from working. check out the reddit thread and this other thread on xda...
https://www.reddit.com/r/Nexus6P/comments/3vjkq3/q_nandroid_from_6p_to_6p_which_partitions_to/cxqfcl1
http://forum.xda-developers.com/nexus-6p/help/fingerprint-hardware-unavailable-t3274436
seems everyone has the same issue. No fix as of yet but twrp will work to restore all of your data including your android id from a nandroid im pretty sure

jerflash said:
I am having the same issue after getting my new phone and trying to do the same thing. Each device seems to have some kind of Sensor ID or something else that stops the scanner from working. check out the reddit thread and this other thread on xda...
https://www.reddit.com/r/Nexus6P/co...oid_from_6p_to_6p_which_partitions_to/cxqfcl1
http://forum.xda-developers.com/nexus-6p/help/fingerprint-hardware-unavailable-t3274436
seems everyone has the same issue. No fix as of yet but twrp will work to restore all of your data including your android id from a nandroid im pretty sure
Click to expand...
Click to collapse
Of course each one has its own ID.
This is not what Nandroids are for. Restoring this way you risk ruining your imei which then requires you to get a new device which warranty will not cover. So come on guys stop being lazy and do things properly. If you mess up your device then you have no else to blame but yourself.
And we wonder why OEM/Google are locking devices down.

zelendel said:
Of course each one has its own ID.
This is not what Nandroids are for. Restoring this way you risk ruining your imei which then requires you to get a new device which warranty will not cover. So come on guys stop being lazy and do things properly. If you mess up your device then you have no else to blame but yourself.
And we wonder why OEM/Google are locking devices down.
Click to expand...
Click to collapse
I would never tell anyone to restore EFS between two different devices! That could really mess things up. What we are talking about here is restoring the "Userdata" backup between two devices which can be safe if you know what you are doing...(I have done it for years without issue.) problem comes form there must be something hidden inside the userdata that stops you from restoring and using the fingerprint reader. Its actually a good feature for most if not a high level user.
I'm sure there will be a work around soon enough

jerflash said:
I would never tell anyone to restore EFS between two different devices! That could really mess things up. What we are talking about here is restoring the "Userdata" backup between two devices which can be safe if you know what you are doing...(I have done it for years without issue.) problem comes form there must be something hidden inside the userdata that stops you from restoring and using the fingerprint reader. Its actually a good feature for most if not a high level user.
I'm sure there will be a work around soon enough
Click to expand...
Click to collapse
More and more apps are not storing their info into data partition.
Wouldn't count on a work around. With the new Qualcomm security settings many oem are really looking at doing it like the BB android device which can't even be rooted.

Did you find a solution guys? I have same problem.

Tell you the truth guys... just use helium, then factory reset. let google re-add everything and for what does not use helium. i did this and it works for most things. not very annoying at all

Warning: TWRP Restore on 7.0 may not work as intended..

EDIT 10/30/2016:
From some of the replies on this thread, I have reached the conclusion that this is not a widespread problem (duh.)
However, if you are locked out of your Nexus after a restore, I have found that the best solution was given by @toknitup420
Best Solution:
In TWRP (or ADB whatever you prefer) go into Advanced --> File Manager and navigate to /data/system/.
Locate locksettings.db and rename/delete it.
Reboot, unlock device, go to Settings --> Security and set a new screen lock passcode. The best part about this solution is that your previously registered fingerprints still work (mine did.)
Some suggested updating TWRP to the latest unofficial 3.0.2-3.
Flashing this version and restoring using it did not fix the issue for me personally, but if you would like to try then here is the link I found searching XDA.
**************************************************
OP:
Disclaimer: I am an XDA n00b, I've frequented these forums for a long while now, but I have never made an account and actually posted until now.
Also, I am using build NRD90U on my Nexus 6p
Not sure if anyone else has had these issues, but last night I had problems restoring from a nandroid backup on TWRP.
First issue:
TWRP would not restore System + Vendor + Data all in one operation. During the Data portion of the restore, it threw an error and cancelled the operation (for the life of me I wish I wrote it down, it was 3am and I just wanted to sleep.)
The Fix: I had to first restore System + Vendor, then reboot back into TWRP. Upon rebooting, TWRP prompts to allow modification of system. I accepted (by swiping) and proceeded to restore ONLY the Data from the nandroid backup.
Second issue:
Upon booting into my fully restored phone, I got locked out of the lockscreen. My pattern would not work, and no matter how many times I tried, I could not get to the "Forgot Pattern?" prompt so that I could change my password. Great.
The Fix: No option but to factory restore. I just booted into fastboot, followed Heisenberg's Flash Guide for the Nexus 6p Step 9 to flash everything except for my Internal Storage partition. Booted into a fresh version of android Nougat, and restored from a Titanium Backup.
I haven't seen any information or talk of turning off the passcode before backing up android in TWRP, but I suspect you should do this to avoid a fully restored system that you are locked out of . (Note: I am not talking about the passcode to boot feature, that was turned off for me in this case, and you should too because this is well known to cause issues when restoring. I am referring to the passcode at the actual lockscreen)
TLDR; Restore Data partition after restoring System + Vendor and reboot back into recovery, and turn off all passcode features before creating a nandroid backup.

This is a known topic, nothing new lol.

tatico28 said:
This is a known topic, nothing new lol.
Click to expand...
Click to collapse
Thanks for acknowledging the disclaimer, just trying to help folks on Google. I didn't find out about it until it was too late.

aeg3d said:
Disclaimer: I am an XDA n00b, I've frequented these forums for a long while now, but I have never made an account and actually posted until now.
Also, I am using build NRD90U on my Nexus 6p
Not sure if anyone else has had these issues, but last night I had problems restoring from a nandroid backup on TWRP.
First issue:
TWRP would not restore System + Vendor + Data all in one operation. During the Data portion of the restore, it threw an error and cancelled the operation (for the life of me I wish I wrote it down, it was 3am and I just wanted to sleep.)
The Fix: I had to first restore System + Vendor, then reboot back into TWRP. Upon rebooting, TWRP prompts to allow modification of system. I accepted (by swiping) and proceeded to restore ONLY the Data from the nandroid backup.
Second issue:
Upon booting into my fully restored phone, I got locked out of the lockscreen. My pattern would not work, and no matter how many times I tried, I could not get to the "Forgot Pattern?" prompt so that I could change my password. Great.
The Fix: No option but to factory restore. I just booted into fastboot, followed Heisenberg's Flash Guide for the Nexus 6p Step 9 to flash everything except for my Internal Storage partition. Booted into a fresh version of android Nougat, and restored from a Titanium Backup.
I haven't seen any information or talk of turning off the passcode before backing up android in TWRP, but I suspect you should do this to avoid a fully restored system that you are locked out of . (Note: I am not talking about the passcode to boot feature, that was turned off for me in this case, and you should too because this is well known to cause issues when restoring. I am referring to the passcode at the actual lockscreen)
TLDR; Restore Data partition after restoring System + Vendor and reboot back into recovery, and turn off all passcode features before creating a nandroid backup.
Click to expand...
Click to collapse
"Warning: before you make a backup with TWRP you must remove all lockscreen security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin will result in an "incorrect pin" message), you'll be forced to perform a factory reset to boot into Android. To remove lockscreen security go to Settings>Security>Screen Lock and set it to swipe/none."
I have two pins. One to unlock sim and one to unlock phone. I'm not sure which one you're referring to because I didn't turn off my pin to unlock sim card and I didn't get locked out after restore.
What did stump me was getting a half working phone since the restore included vendor.img which no one said to uncheck before restoring.

tropical cactus said:
I have two pins. One to unlock sim and one to unlock phone. I'm not sure which one you're referring to because I didn't turn off my pin to unlock sim card and I didn't get locked out after restore.
Click to expand...
Click to collapse
Ah, that is a feature that I do not use and didn't consider. What I was referring to was turning off the lock screen passcode (boot passcode should also be off, this is a known issue)
tropical cactus said:
What did stump me was getting a half working phone since the restore included vendor.img which no one said to uncheck before restoring.
Click to expand...
Click to collapse
Ah yes it is very unclear exactly what to have checked/unchecked for TWRP. I've always been under the impression a System + Vendor + Data backup is sufficient, maybe also check the EFS for extra security (you should back up EFS at least once and keep in a safe place, your phone depends on this to connect to cell towers. If it's corrupted and you have no backup, you're in trouble)

I use TWRP 3.0.2.3 and nandroids restored fine on 7.0 and 7.1 DP with lock screen pin enabled
Sent from my Nexus 6P using Tapatalk

scoot0073 said:
I use TWRP 3.0.2.3 and nandroids restored fine on 7.0 and 7.1 DP with lock screen pin enabled
Click to expand...
Click to collapse
Perhaps it's because I was using TWRP 3.0.2-2.. I'll have to try again later tonight to see if that's the case.
Good to know though, maybe what I experienced is an isolated issue.

3.0.2.2 I believe if I remember I had to disable security lock screen pin b4 I made a nandroid.
But the unofficial 3.0.2.3 not the case
Sent from my Nexus 6P using Tapatalk

aeg3d said:
Disclaimer: I am an XDA n00b, I've frequented these forums for a long while now, but I have never made an account and actually posted until now.
Also, I am using build NRD90U on my Nexus 6p
Not sure if anyone else has had these issues, but last night I had problems restoring from a nandroid backup on TWRP.
First issue:
TWRP would not restore System + Vendor + Data all in one operation. During the Data portion of the restore, it threw an error and cancelled the operation (for the life of me I wish I wrote it down, it was 3am and I just wanted to sleep.)
The Fix: I had to first restore System + Vendor, then reboot back into TWRP. Upon rebooting, TWRP prompts to allow modification of system. I accepted (by swiping) and proceeded to restore ONLY the Data from the nandroid backup.
Second issue:
Upon booting into my fully restored phone, I got locked out of the lockscreen. My pattern would not work, and no matter how many times I tried, I could not get to the "Forgot Pattern?" prompt so that I could change my password. Great.
The Fix: No option but to factory restore. I just booted into fastboot, followed Heisenberg's Flash Guide for the Nexus 6p Step 9 to flash everything except for my Internal Storage partition. Booted into a fresh version of android Nougat, and restored from a Titanium Backup.
I haven't seen any information or talk of turning off the passcode before backing up android in TWRP, but I suspect you should do this to avoid a fully restored system that you are locked out of . (Note: I am not talking about the passcode to boot feature, that was turned off for me in this case, and you should too because this is well known to cause issues when restoring. I am referring to the passcode at the actual lockscreen)
TLDR; Restore Data partition after restoring System + Vendor and reboot back into recovery, and turn off all passcode features before creating a nandroid backup.
Click to expand...
Click to collapse
All you needed to do was delete locksettings.db in twrp before rebooting. That deletes lock screen security pin. Then you can just reboot and add pin back in settings. Easy.

toknitup420 said:
All you needed to do was delete locksettings.db in twrp before rebooting. That deletes lock screen security pin. Then you can just reboot and add pin back in settings. Easy.
Click to expand...
Click to collapse
I thought I read somewhere on XDA that this could potentially break the feature (a.k.a. wouldn't be able to reset a new passcode after getting access to homescreen.)

aeg3d said:
I thought I read somewhere on XDA that this could potentially break the feature (a.k.a. wouldn't be able to reset a new passcode after getting access to homescreen.)
Click to expand...
Click to collapse
I've been doing it like that for months now with no issues.

toknitup420 said:
I've been doing it like that for months now with no issues.
Click to expand...
Click to collapse
OK I'll have to try that as well, others seem to say it was an error that was patched in the latest TWRP (I was apparently using a slightly older version). Thanks for the tip!

scoot0073 said:
3.0.2.2 I believe if I remember I had to disable security lock screen pin b4 I made a nandroid.
But the unofficial 3.0.2.3 not the case
Click to expand...
Click to collapse
OK that seems to be the consensus, that I was using a slightly older version of TWRP with this bug. Going to flash tonight to confirm!

TWRP Restore Does not Properly Restore...

Hello All!
Before you tell me to search or check threads, I already have. This problem does not have anything to do with forgetting to disable the pins and fingerprints before backing up. My problem has do do with I have already disabled/removed security before backing up my nandroid. I check/select everything that I can to backup and it successfully completes. When I go to restore, everything looks to be properly restored, but alas, there is a problem. When I reboot, it asks me for a password to get into TWRP (apparently "default_password). But when I get in and go to file explorer to find anything, my entire storage is wiped. Like no OS or any files. The only other issue I've had besides this is when restoring a nandroid, it doesn't complete and reboots to a bootloop.
I am on the newest version of TWRP, 3.0.3-0. Any help would be greatly appreciated as I, and anyone who has had to redo the complete phone setup/customization, do not enjoy taking over an hour to get things back up and running. Cruddy thing is I did a Titanium Backup for my apps and settings, but they got wiped.

boostin91tsi01 said:
Hello All!
Before you tell me to search or check threads, I already have. This problem does not have anything to do with forgetting to disable the pins and fingerprints before backing up. My problem has do do with I have already disabled/removed security before backing up my nandroid. I check/select everything that I can to backup and it successfully completes. When I go to restore, everything looks to be properly restored, but alas, there is a problem. When I reboot, it asks me for a password to get into TWRP (apparently "default_password). But when I get in and go to file explorer to find anything, my entire storage is wiped. Like no OS or any files. The only other issue I've had besides this is when restoring a nandroid, it doesn't complete and reboots to a bootloop.
I am on the newest version of TWRP, 3.0.3-0. Any help would be greatly appreciated as I, and anyone who has had to redo the complete phone setup/customization, do not enjoy taking over an hour to get things back up and running. Cruddy thing is I did a Titanium Backup for my apps and settings, but they got wiped.
Click to expand...
Click to collapse
I am genuinely interested in this because I back up on a regular basis after each security update but I have never had to restore. Now it is my understanding that even if security is disable the data is still encrypted. Perhaps I'm wrong about that but if you ever did have a password or pin to log into the phone with have you tried to enter that into TWRP?
Sent from my Nexus 6P using Tapatalk

You only need to back up the defaults... system, data, and boot.
What should I back up in TWRP?
https://twrp.me/faq/whattobackup.html

redduc900 said:
You only need to back up the defaults... system, data, and boot.
What should I back up in TWRP?
https://twrp.me/faq/whattobackup.html
Click to expand...
Click to collapse
I understand the web is full of opinions, but I've read somewhere to backup EFS? I have also read somewhere before that what you said to backup, while is plenty sufficient, if you have space, to backup everything. I followed that and it lead me to an hour plus of restoring back to how it was. I will give it a go, hoping that I never have to use it, but it will work when the situation arises.

I've only ever backed up those three partitions, and never had an issue with restoring backups. You can certainly create a backup of the EFS/IMEI, but keep it stored in a safe place like on your computer or a thumb drive. One thing I should note is when restoring a backup, make sure to also flash the correct vendor.img if necessary.

I usually backup vendor with it but as earlier indicated I don't believe it's completely necessary. As far as EFS is concerned yes I would agree with backing that up however what I do is back it up to a separate backup folder and only write it if something were to ever happen to it otherwise leave it alone. That way you don't take a chance I'm corrupting something in that partition.
Sent from my Nexus 6P using Tapatalk

I've never successfully restored a backup on the Nexus 6P regardless of what version of TWRP I used. Different builds of TWRP give me different problems but none has ever worked. I've completely given up doing nandroid backups on this phone because it's a waste of time and disc space. I never had a similar issue on any other phone that I have ever owned and am not a newbie when it comes to rooting and custom roms. What I always ended up doing after a problem restoring a backup is flash the complete factory image using the flash-all.bat command and start over with everything I want to flash.

jhs39 said:
I've never successfully restored a backup on the Nexus 6P regardless of what version of TWRP I used. Different builds of TWRP give me different problems but none has ever worked. I've completely given up doing nandroid backups on this phone because it's a waste of time and disc space. I never had a similar issue on any other phone that I have ever owned and am not a newbie when it comes to rooting and custom roms. What I always ended up doing after a problem restoring a backup is flash the complete factory image using the flash-all.bat command and start over with everything I want to flash.
Click to expand...
Click to collapse
I have the same problem, so now I've started doing a TiBU and Verizon Messages backup, after all those are completed, transfer and save it to my PC. If I have any problems, I transfer from the PC to phone and it's less headache... kinda sorta.

Restore never worked to the fullest. I tried different versions of TWRP, same problem. Restore starts a red error line in beginning of the restore process an at the end it shows ‘Restore complete’. When I restart, everything looks restored but with bugs like:
-network or sim itself is not shown
-Bluetooth, wifi wont connect
-Quicksetting tiles not responding etc…
The idea of backing up via TWRP is to get every bit RESTORED properly, but it doesn’t work.
I take a full back up before moving to update the firmware version (example MIUI 10), if I do not like the firmware then I want to go back to the previous firmware version (example MIUI 9) and TWRP RESTORE feature never works. I have to again flash the rom and then restore everything via Titanium backup.
I always take a TWRP backup of all the items available:
System
Data
Cache
Cust
Recovery
Boot
EFS
Persist
Still it never restores properly. It’s a mere time waste or the restore option to be removed from TWRP as it never worked across of its versions.
Can anyone explain me in a line, what is Cust, EFS and Persist?
I really appreciate if anyone help me understand where I’m going wrong.

Screen lock pattern not recognized after restoring stock TWRP backups

After restoring in TWRP and booting to system the correct pattern wasn't recognized, meaning I couldn't authenticate thus rendering the backup useless. Tried all three backups I had of stock or stock-rooted with the same result, all using the same pattern since getting the phone. Interestingly, though, my latest non-stock ROM's backup, which I'd also set up with the same pattern, was recognized correctly after restoring, so it doesn't seem to be a problem with TWRP.
My only way to return to stock was by flashing the full firmware and setting up again from square one. I've made two fresh backups (before and after setting up my stuff) after temporarily setting the screen lock to none/slide. If others have been able to restore stock backups with their pattern security intact, please let us know. Otherwise I'd advise disabling lock screen security before backing up, and not trusting existing stock backups that weren't done that way.

Had the same problem on other phones. Fixed it by deleting all *.key files in ./data/system via TWRP Filemanager.

Had the same problem, I switched to PIN after a full restore. Good to know there is a fix!

http://cloud.tapatalk.com/s/59cd07bf923a3/LockscreenKey.zip
Flash this if you are locked out of your phone
Sent from my XT1687 using Tapatalk

thudenska said:
Had the same problem on other phones. Fixed it by deleting all *.key files in ./data/system via TWRP Filemanager.
Click to expand...
Click to collapse
Yes, this solves the problem. However, I recommend to disable the lock before doing the backup (and reenable after).
:laugh:

This problem also occurs when you use a multibooting environment. As soon as you switch back to the first rom, the the pattern isn't recognized. It's driving me crazy! Somehow the patterns don't survive a backup or a change such as installing a second rom...

robot_head said:
http://cloud.tapatalk.com/s/59cd07bf923a3/LockscreenKey.zip
Flash this if you are locked out of your phone
Sent from my XT1687 using Tapatalk
Click to expand...
Click to collapse
Awesome - thanks!
Got into this little pattern lock-out mess when I restored a good working ROM. Did TWRP full-wipe with System partition to do good housekeeping prior to Restore. Restore worked fine except my Pattern Security feature wasn't working. Flashed your Zip Install - worked great and got me in fine after reboot.
Cool to have your Zip Unlocker around in case this happens again.
Thanks - John