Hi.
I've updated to 6.0.1 ,re rooted and spent some time setting up my apps and stuff.
I want to install exposed again but I want to backup before I do in case anything goes wrong.
I'm sure I read on here that there's a problem with restoring TRWP backups?
I've done a search but I cant seem to find anything definitive, could someone be kind enough to explain what the issue is (if any) and how I avoid any problems?
Thanks
Stret
Any Help ?
Twrp restore caused me bootloop, but after flashing a couple of factory images (e.g. vendor, boot, bootloader) i was able to boot back to my phone, but i can't unlock the phone with the passcode i originally set. Cause could be related to the encryption android originally placed on all our 6p's. You could try removing fingerprint and disabling passcode, but i can't guarantee anything. Or you could be like me, screw the backup and just flash xposed and be on your merry way.
There's little chance of going wrong with flashing xposed, as long as you flash the sdk23 for arm64
Related
I believe this is caused by Xposed, here's what happened. I rooted today, went to xposed and it showed that the current version was wrong or wasn't working or something, so I decided to hit uninstall and then reinstall it after boot. Unfortunately, my phone is stuck at the LG logo now. I don't have a custom recovery installed or anything, I read I need to access the disable xposed zip in order to fix this, but I'm not sure how I can since I can't really use my phone. I also want to know if there's any way of doing this without losing my data, I REALLY can't lose all my data over this, didn't backup or anything lately. Thanks!
I have a nexus 6P running rooted stock rom and I wanted to try out a new rom. Before flashing the new rom, I made a nandroid backup via TWRP. Now, the rom that I was backing up had fingerprint security setup with backup passcode for unlocking the phone.
So I tried new rom and it didn't work (read-too many issues and too many crashes). Decided to revert back to my original setup. Went back into TWRP and restored the backup.
After booting the phone up, I can't log in to my phone anymore. As you know after every reboot, fingerprint sensor doesn't work unless you enter the backup passcode. So I am entering my passcode and its not accepted. I have tried entering passcode many times but to no avail. I know my passcode so possibility of me forgetting it is not valid.
Has anybody else seen or ran into this issue yet?
The step folks are missing is Prior to installing a backup you Must Change security to None before you even start a backup This clears password, pin and saved finger prints. I believe once security is changed it is safe to backup and then install backup. You will need to reenter Pin and Fingerprints.
Born<ICs said:
The step folks ...
... is changed it is safe to install backup.
Click to expand...
Click to collapse
You mean clear the security before making a backup ... right?
if not, how would I change security on a backup file of rom that had security enabled.
I have never used lock screen security before so never ran into this issue.
No, dig through this forum for tech details. But my understanding is anytime you make/install a backup or reflash rom or go back to stock you must reset you Security options in settings to None. You have security now, probably Fingerprints, and the required Lockscreen Pin.
If you try to install backup or Rom or whatever without doing so you get what you experienced. There is a path out of it if you read further.
Pin or Pattern on boot after restoring Nandroid
Born<ICs said:
No, dig through this forum for tech details. But my understanding is anytime you make/install a backup or reflash rom or go back to stock you must reset you Security options in settings to None. You have security now, probably Fingerprints, and the required Lockscreen Pin.
If you try to install backup or Rom or whatever without doing so you get what you experienced. There is a path out of it if you read further.
Click to expand...
Click to collapse
The interesting thing is, I intentionally chose to enter pattern/pin on rebooting. The strange (actually may not be strange .....but strange to me) thing is that even when I move on to different Roms, that initial choice is remembered and embedded since even after choosing not to require pin/pattern when rebooting, I get prompted. Also the pin/pattern works during recovery, it also works on the initial startup after restoring a backup but then fails after successful fingerprint use (it will actually say "wrong pin" or "wrong pattern") at the end of the booting process. The thing is, I have only used one pin and at other times one password ever with this device. Eventually I had to do a factory reset to solve this issue (thank goodness I was able to back up my internal storage to my computer in TWRP recovery mode).
Recipe:
TWRP 2.8.7.2
TWO Nexus 6Ps on 6.0.1
One N6P systemless rooted
Official Android SDK (fastboot)
So I got a replacement N6P from Fi as I noticed some slight bending on my original, and I was working on moving my data over using TWRP so I could keep all my app data, etc. When I backed up my original 6P, I forgot to remove screen and boot security, so when I flashed on to my new 6P, I was locked out (as expected, known bug). I tried this fix to get in to my system, and it worked! I was able to log in. However, I noticed that my old fingerprints were still enrolled and I wanted to start those fresh, so I tried to remove them. When I selected "Delete" for each enrolled fingerprint, nothing happened. This was the first clue. I then tried to enroll new fingerprints and got the following message:
Code:
[B]Enrollment was not completed[/B]
Fingerprint enrollment didn't work. Try again or use a different finger.
The other odd thing is that on the lockscreen, I was getting a red text error message that read something like "Fingerprint hardware not available."
So I figured something got messed up security wise from the fix I tried after flashing a locked nandoird. I then went back and made a new nandroid backup (boot, system, data) on my old phone making sure that all security was turned off. Same thing!
Wondering if the hardware did actually get messed up somehow, I flashed back to official stock 6.0.1 from Google. Fingerprinting then started working!
So nothing I have done since then has made any difference when trying to restore my userdata from my old phone. I've tried wiping cache/dalvik, and removing the locksettings.db file, but these didn't change anything either.
Has anyone had this issue before? It seems really bizarre to me. I'm probably going to end up flashing stock and restoring userdata via TB, but that is a headache compared to nandroid so if possible I'd like to get this to work.
Tried wiping userdata then flashing userdata from my old 6P and that did not work either.
Have you tried wiping data, setting up the device again, and then checking if you can add a fingerprint?
I tried restoring data from a device I had to RMA too, and got that exact message every time - I gave up in the end as I tried wiping everything but the only thing that worked was clearing userdata & restoring my apps from the nandroid via TiBu.
All in all, I presume it's something to do with the fingerprint scanner having a different hardware key/serial to the new one and retaining that info somewhere in the data partition when you back it up.
DanielF50 said:
Have you tried wiping data, setting up the device again, and then checking if you can add a fingerprint?
I tried restoring data from a device I had to RMA too, and got that exact message every time - I gave up in the end as I tried wiping everything but the only thing that worked was clearing userdata & restoring my apps from the nandroid via TiBu.
All in all, I presume it's something to do with the fingerprint scanner having a different hardware key/serial to the new one and retaining that info somewhere in the data partition when you back it up.
Click to expand...
Click to collapse
Yup I did try that, didn't work either. I'm right where you were too, currently restoring apps for TB. Your hypothesis seems plausible to me, I hadn't thought of that. Kind of a bummer for swapping devices if that is the case. I wonder if we could find where the fingerprint key is stored in userdata and back it up prior to flashing the nandroid?
Thanks for the reply!
No problems & yes, it is, though I presume it's either been done for some sort of security, or as a complete oversight - I can't see Google deliberately doing so, especially on a Nexus device.
I think it's probably highly likely that someone will find the hardware/serial file soon and find a way to stop it from being overwritten when TWRP restores the data partition, though it is annoying that it hasn't been discovered yet... Thankfully restoring from a nandroid through TitaniumBackup isn't too bad nowadays!
Srry for necro but I think I might have found a workaround solution to this problem or at least the problem which is very similar to this one. Please check "symptoms" in the description of the solution to make sure we are talking about the same issue.
Here's the link to the solution: http://forum.xda-developers.com/showpost.php?p=68374321&postcount=1446
erikem said:
Srry for necro but I think I might have found a workaround solution to this problem or at least the problem which is very similar to this one. Please check "symptoms" in the description of the solution to make sure we are talking about the same issue.
Here's the link to the solution: http://forum.xda-developers.com/showpost.php?p=68374321&postcount=1446
Click to expand...
Click to collapse
Sorry for another necro, but this doesn't work for me on Android 7.1.1
Edit: Correct fix here: https://forum.xda-developers.com/showpost.php?p=68199207&postcount=9
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.
NM: I've was able to flash 10.3.4...but my internal storage got wiped out. It's saying I have 105GB of 108GB free...I have backups but my backup is corrupted since I forgot to remove my security pattern...oh well...
just4sc said:
HI!
I tried looking in the 255 error thread but couldn't find a solution and was thinking maybe it has something to do with the -32 version of TWRP so I went to the TWRP thread but no answer so here I am hoping someone here can help.
I made a backup however I found out later that I had forgotten to remove my security pattern prior to backup. Don't know if that's the issue but upon doing a restore I'm getting the dreaded 255 error. I also forgot to run magisk uninstall and don't know if that's the issue too (yeah, not a good idea to be working on stuff like this in the middle of the night and lacking sleep).
I haven't rebooted yet fearing I won't be able to get in.
I have since tried running the magisk uninstall (gave me an error - didn't write it down and now I can't see it anymore).
Tried installing magisk again (installed ok).
Install 10.3.4 ROM and that went ok.
Still not rebooted - thinking the install of 1.0.3.4 might have solved my problem I reinstalled TWRP -32 and then tried restoring my backup again. Of course I still have the 255 error.
I hoping someone has gone down my path or have some advise so that I can restore my backup.
Again, I still haven't rebooted yet so maybe that's my issue?
Edit: So, I rebooted and it gives me a crash dump. I can get into TWRP still but tried flashing the full 10.3.4 rom and it completes but it just goes into the crash dump again. I noticed while looking at Filemanager in TWRP all the filenames in storage are jumbled. Does that mean the encryption is messed up and I am hosed? I've tried searching but there's just so much information I'm a bit tired and am hoping someone point me to the right direction and maybe let me know if I can still recover. Thanks
Click to expand...
Click to collapse
Yes you have to format data
Forget the backup it's useless
Format Data install 10.3.4 and magisk to both slots and your back in business
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
Yes you have to format data
Forget the backup it's useless
Format Data install 10.3.4 and magisk to both slots and your back in business
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
Thanks!