Related
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
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
I just reverted to T-Mobile firmware so I could upgrade to 7.0, since then I've noticed some issues.
I can't use my photos to change my wallpaper, or for the AID.
I can't go to the settings for the camera.
I've had some screen freezing when trying to change the notifications.
Has anyone else had similar issues, or are there other problems I should look out for?
Bildo41383 said:
I just reverted to T-Mobile firmware so I could upgrade to 7.0, since then I've noticed some issues.
I can't use my photos to change my wallpaper, or for the AID.
I can't go to the settings for the camera.
I've had some screen freezing when trying to change the notifications.
Has anyone else had similar issues, or are there other problems I should look out for?
Click to expand...
Click to collapse
My wife's phone is stock and I took the OTA for 7.0. I checked the camera settings and they are fine.
I'm wondering if you might need to flash the update again. If you do, you should wipe davlik and cache to make sure nothing got left behind.
androiddiego said:
My wife's phone is stock and I took the OTA for 7.0. I checked the camera settings and they are fine.
I'm wondering if you might need to flash the update again. If you do, you should wipe davlik and cache to make sure nothing got left behind.
Click to expand...
Click to collapse
I'd hate to do everything over again. I can't imagine how I screwed up either. I ODINed the T-Mobile files, and when the phone restarted, it updated to 7.0 automatically.
Bildo41383 said:
I'd hate to do everything over again. I can't imagine how I screwed up either. I ODINed the T-Mobile files, and when the phone restarted, it updated to 7.0 automatically.
Click to expand...
Click to collapse
When I checked smart switch, it didn't have an upgrade listed. But the phone did. This tells me that it was a TMO update. Since you flashed tmo files, I'm assuming the ones listed in T-Mobile Samsung Galaxy S7 Edge Guides, News, & Discussion, it should have taken. OTA is considered a dirty flash in that it doesn't wipe everything. Flashing with odin wipes everything. I'm just wondering if it didn't wipe everything the way it should.
The other possibility is after you updated, you loaded something that nougat doesn't like. If you do reflash, once it is done, do the bare minimum setup. Then try the items you listed that were a problem. If everything works ok, then you know it is something that got installed after the update. During the initial setup process, I never allow it to restore from another device, or samsung account. I get it setup as a new phone and then reboot. See how everything is working, then use smart switch to restore. If anything is missing, I go to the play store and download. Yes, it's a pain, but I've never had any issues.
androiddiego said:
When I checked smart switch, it didn't have an upgrade listed. But the phone did. This tells me that it was a TMO update. Since you flashed tmo files, I'm assuming the ones listed in T-Mobile Samsung Galaxy S7 Edge Guides, News, & Discussion, it should have taken. OTA is considered a dirty flash in that it doesn't wipe everything. Flashing with odin wipes everything. I'm just wondering if it didn't wipe everything the way it should.
The other possibility is after you updated, you loaded something that nougat doesn't like. If you do reflash, once it is done, do the bare minimum setup. Then try the items you listed that were a problem. If everything works ok, then you know it is something that got installed after the update. During the initial setup process, I never allow it to restore from another device, or samsung account. I get it setup as a new phone and then reboot. See how everything is working, then use smart switch to restore. If anything is missing, I go to the play store and download. Yes, it's a pain, but I've never had any issues.
Click to expand...
Click to collapse
So what you're saying is download the nougat files and install through odin. Gotcha ?
Bildo41383 said:
So what you're saying is download the nougat files and install through odin. Gotcha
Click to expand...
Click to collapse
I should have asked, have you rebooted since the update? There were some things like wifi calling and video calling that were missing after the OTA update. On reboot, it was all back. Try a reboot first. If things still aren't working, reflash.
If you previously backed up your apps and docs and images, etc., with smart switch before the update, then use that one when you restore.
Be sure though that after you do the odin flash, do a minimal setup. Then reboot. Then check everything out. If it is all good, do the restore from smart switch.
Good luck. Let me know how it goes.
androiddiego said:
I should have asked, have you rebooted since the update? There were some things like wifi calling and video calling that were missing after the OTA update. On reboot, it was all back. Try a reboot first. If things still aren't working, reflash.
If you previously backed up your apps and docs and images, etc., with smart switch before the update, then use that one when you restore.
Be sure though that after you do the odin flash, do a minimal setup. Then reboot. Then check everything out. If it is all good, do the restore from smart switch.
Good luck. Let me know how it goes.
Click to expand...
Click to collapse
Will do, thank you.
The keyboard is what has me the most annoyed, it is not as good as it was in Marshmallow. I have the Auto Predictive text Auto replace languages English, and Spanish. Back on Marshmallow, there was no need to switch between languages, you just had to type in either one, and the keyboard itself would switch automatically. And on Nougat, that doesn't happen anymore. I loved that feature on MM. Does anyone else have that problem? is there a way to install the MM Samsung keyboard on Nougat? or is there a solution?
androiddiego said:
I should have asked, have you rebooted since the update? There were some things like wifi calling and video calling that were missing after the OTA update. On reboot, it was all back. Try a reboot first. If things still aren't working, reflash.
If you previously backed up your apps and docs and images, etc., with smart switch before the update, then use that one when you restore.
Be sure though that after you do the odin flash, do a minimal setup. Then reboot. Then check everything out. If it is all good, do the restore from smart switch.
Good luck. Let me know how it goes.
Click to expand...
Click to collapse
Ok, I finally redid the whole thing, and as you suggested, everything works now. Thanks for your help mate.
Bildo41383 said:
Ok, I finally redid the whole thing, and as you suggested, everything works now. Thanks for your help mate.
Click to expand...
Click to collapse
Awesome!
Seriously all I'm waiting for is the Note 8
Should have posted this here... (oh well)
Has anyone else with generic quick charge 2.0 car chargers notice they are not "quick charging" anymore since the nougat upgrade?
I've got a couple of generic ones from ebay in my cars and they worked on the S7E using MM and still work on the note 4. But on the S7E after N7.0 update they aren't quick charging, they are just charging. (does that make sense?)
Last night, I decided to update my unlocked and rooted 2017U from Marshmallow to Nougat. Before I made the move, I've done a full backup from Titanium backup, just like what I've done for so many times before flushing a new ROM. Everything went smoothly. After the initial setup, I wanted to use TB to restore most of my apps. Then the nightmare starts, from the "restore missing apps with data", I have 0 apps. From the Backup/Restore tap, I have hundreds of crossed over files at the bottom (image was attached). I've never had issues like this before. Anybody have idea how to fix this? Thanks.
Yanyan80 said:
Last night, I decided to update my unlocked and rooted 2017U from Marshmallow to Nougat. Before I made the move, I've done a full backup from Titanium backup, just like what I've done for so many times before flushing a new ROM. Everything went smoothly. After the initial setup, I wanted to use TB to restore most of my apps. Then the nightmare starts, from the "restore missing apps with data", I have 0 apps. From the Backup/Restore tap, I have hundreds of crossed over files at the bottom (image was attached). I've never had issues like this before. Anybody have idea how to fix this? Thanks.
Click to expand...
Click to collapse
This is the error I got when using two different versions of TB
I don't think I have a different version of TB.. 8.0.0.1 is the version I have... How did you "fix" the error?
I just took the correct APP. But I also found out, that when you install the missing app, you will be able to restore the setting. And these are the most important, aren't they? ?
Sorry I can't do any more ?
Gesendet von meinem Lenovo K50a40 mit Tapatalk
Thanks for all the help. Unfortunately, most of restore doesn't work very well. Apps will be forced stop. It feels like the marshmallow data is not compatible with nougat's. By the way, I've tried two different builds already, all with the same problem. Damn, hate to say that, but It's time to go back to marshmallow.
Yanyan80 said:
Thanks for all the help. Unfortunately, most of restore doesn't work very well. Apps will be forced stop. It feels like the marshmallow data is not compatible with nougat's. By the way, I've tried two different builds already, all with the same problem. Damn, hate to say that, but It's time to go back to marshmallow.
Click to expand...
Click to collapse
I doubt this is the reason, I went from mm to n with tibu backups working fine, restored like it should and no fc or anything.
I hear you, I've done many restores using TB. This is the first time I am having problem like this. It's so weird.
As stated in the title, I can't load any web pages in Chrome, Firefox, and several other browsers. My wifi is fully functional, but I can't load anything related to web pages. So using the XDA App, I can browse the fourms fine, but if I were to open a link to Google or anything, it will crash and return to the XDA App. This occurs when I try opening links from apps like Facebook as well.
At first, I thought this was a ROM problem or something to do with my apps, so I format and decrypted my phone and clean flashed OOS 5.0.4. It seems to work well for some time, but returned a good hour later. Restarting each time it happens seems to fix it for a short while, but I am quite annoyed of constantly restarting because of this.
I've searched around and it doesn't seem like anyone else has this particular problem with their OP5s so I'd like to fix this up if I can.
I am still on OOS 5.0.4, but now with NewKernel 1.29 from the OP5T thread. I'm also rooted with Magisk beta v16.2 and have the Pixel 2 Oreo WiFi v4, OnePlus Camera M, NotoColorEmoji Patch Modules along with a systemless font module installed.
@StarzSkyz have you tried another network like mobile or other wifi?
strongst said:
@StarzSkyz have you tried another network like mobile or other wifi?
Click to expand...
Click to collapse
Yeah, each time it happens I try swapping from WiFi to data, but no difference. I'm currently trying to see if it was due to restoring a certain backup from Titanium Backup. I did recently find a post speaking of the problem, but for the use of debloater somehow affecting it. So it may also be due to the loss a system app.
StarzSkyz said:
Yeah, each time it happens I try swapping from WiFi to data, but no difference. I'm currently trying to see if it was due to restoring a certain backup from Titanium Backup. I did recently find a post speaking of the problem, but for the use of debloater somehow affecting it. So it may also be due to the loss a system app.
Click to expand...
Click to collapse
You said you did already a clean installtion. So clean install again without any restore of settings and 3rd party apps not provided by the rom :good:
strongst said:
You said you did already a clean installtion. So clean install again without any restore of settings and 3rd party apps not provided by the rom :good:
Click to expand...
Click to collapse
I feel like an idiot for not remembering about doing that.
I've clean flashed and left all the apps enabled and the problem hasn't appeared again. After taking a TWRP backup of that (just in case I mess up something again) I rooted without any modules other than the WiFi Mod(which I did feel like it being one of the causes, but it helped with connection speed) and the systemless font module and tried restoring only user app data(so a fresh install from the play store and then a app data restore, not touching system apps at all) and thankfully it didn't cause any problems, so I got to restore some data back.
Thank you for the advice of actually just clean flashing again, cause I was actually slowly uninstalling and restoring my apps. I apologise for not posting as soon as I found the fully clean installation working, as I really couldn't help myself and try see if it was due to having root and my user apps. Once again, thank you for your help with my problem here. If it appears again, I'll probably post here again if it happens again (hopefully it doesn't).