After successfully restoring backup on the new phone the fingerprint doesn't work.
Details about restore process are here: https://forum.xda-developers.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413/page10
Before TWRP backup I did set two fingerprints. After restoring on new phone if I try unlock screen with fingerprint I'm getting message "Fingerprint hardware not available"
I can unlock screen using PIN but I can't add new fingerprint nor delete two existing.
When I delete one fingerprint, it greyed out (screenshot attached) but when I return back to Fingerprints it's still there.
Adding new fingerprint starts fingerprint setup but right before end I'm getting message (screenshot attached):
Enrolment was not completed.
Fingerprint enrolment didn't work. Try again or use different finger
Fear not, this is not hardware issue. I went back to stock image and I can setup and use fingerprint and delete fingerprints.
So, I went back to square one and flashed stock image, boot, reboot, TWRP, flashed StatiXOS, boot. At this point checked, fingerprint is still working in StatiXOS.
Rebooted to TWRP, wipe and restore my StatiXOS backup and still having the same issue with fingerprint.
Reading some threads my guess is that fingerprint should be disabled before backup. The fingerprint info is probably saved on fingerprint chip and factory reset should fix the issue.
Turther search lead to other threads about same issue and it seems deleting some files/folders in data partition reset fingerprint settings.
Unfortunately none of them doesn't match 3a. Have no time now but will investigate further other solutions. Pixel 3 threads might have the answer.
I had exactly the same prob on AOSiP on my Pixel 3 XL. Was not able to find it out or to solve it. Back to Stock and it worked fine w/o any probs. Since some days I am on DU and also no probs so far.
gogoffm said:
I had exactly the same prob on AOSiP on my Pixel 3 XL. Was not able to find it out or to solve it. Back to Stock and it worked fine w/o any probs. Since some days I am on DU and also no probs so far.
Click to expand...
Click to collapse
Same here, gave up and flash stock again. I was trying some stuff and noticed if I create another account and switch I can enable fingerprint but only for that account. So, something is screwed up in default account settings.
The best advice I can offer is from this Pixel XL thread: https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
MAKE SURE YOUR LOCKSCREEN IS OFF... No fingerprint set up... Not a pin set up... No pattern set up. If your more secure than swiping up to open your screen your not getting in to TWRP 3.2.0-0 decrypted.
Click to expand...
Click to collapse
Unfortunately I don't have another Pixel 3a around to test, but it make sense.
So you already tried data/system/ & change locksettings.db to locksettings.db.bak ? It should create a new locksettings.db after you go into phone settings to set up a new pin/fingerprints then go & delete locksettings.db.bak or you can leave it...either way.
SketchyStunts said:
So you already tried data/system/ & change locksettings.db to locksettings.db.bak ? It should create a new locksettings.db after you go into phone settings to set up a new pin/fingerprints then go & delete locksettings.db.bak or you can leave it...either way.
Click to expand...
Click to collapse
I have some spare time today and will try. Need to test my backup first to make sure I can go back.
Even if it work on my phone it might not work on different phone. If I'm in charge of security on Pixel 3a project I will at least compare hardware fingerprints (i.e. serial numbers, MAC address, etc) of the phone with previous data save in encrypted file in some very protected area
However, it could be useful to all dummies like me who screwed their phones.
Pogo said:
I have some spare time today and will try. Need to test my backup first to make sure I can go back.
Not much luck today. I have created two backups on rooted StatiXOS:
- one with fingerprints and PIN unlock
- one without fingerprints and swipe unlock (no protection at all)
Before running backup checked all boxes in Backup option (Boot, System, System Image, Vendor Image, Data)
Note: only Boot, Data and System Image are actually required, but just in case
After that I've tried the following:
1.
- flash factory ROM to make sure there is no traces of my settings
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to TWRP, wipe Dalvik/Art, System and Data
- copy my backups to TWRP as well as all other folders originally on sdcard
- go to restore and select my backup with fingerprints
- only check Boot, Data and System Image boxes
- reboot, all good so far. PIN and fingerprint works, only needed to re-enable fingerprint in apps that use it like my banking app
2.
- back to fastboot, deleted file data/system/locksettings.db
- rebooted, there is no lock or PIN, just swipe
- "Pixel is starting..." message show up on display
- launcher and apps are not available, but Settings are available from status bar
- can add new fingerprint, delete fingerprint but the message on home screen won't disappear
- gave up after 10 min of waiting
3.
- flashed factory ROM again
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to fastboot, delete file data/system/locksettings.db
- reboot, there is no lock or PIN, just swipe
- same as before but the message is now "Phone is starting..."
- gave up after 10 min of waiting
Need to actually USE my phone, so I stopped here and restored my trusty backup.
So, you can restore your backup with fingerprint. Judging by my experience restore is fully functional only on the physically same phone (same s/n, same MAC, etc, no hardware modifications).
Deleting data/system/locksettings.db did remove lock but still didn't make phone fully functional. However it's promising.
Click to expand...
Click to collapse
Pogo said:
Pogo said:
I have some spare time today and will try. Need to test my backup first to make sure I can go back.
Not much luck today. I have created two backups on rooted StatiXOS:
- one with fingerprints and PIN unlock
- one without fingerprints and swipe unlock (no protection at all)
Before running backup checked all boxes in Backup option (Boot, System, System Image, Vendor Image, Data)
Note: only Boot, Data and System Image are actually required, but just in case
After that I've tried the following:
1.
- flash factory ROM to make sure there is no traces of my settings
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to TWRP, wipe Dalvik/Art, System and Data
- copy my backups to TWRP as well as all other folders originally on sdcard
- go to restore and select my backup with fingerprints
- only check Boot, Data and System Image boxes
- reboot, all good so far. PIN and fingerprint works, only needed to re-enable fingerprint in apps that use it like my banking app
2.
- back to fastboot, deleted file data/system/locksettings.db
- rebooted, there is no lock or PIN, just swipe
- "Pixel is starting..." message show up on display
- launcher and apps are not available, but Settings are available from status bar
- can add new fingerprint, delete fingerprint but the message on home screen won't disappear
- gave up after 10 min of waiting
3.
- flashed factory ROM again
- perform initial setup, enable ADB debug, setup PIN and one fingerprint
- back to fastboot, delete file data/system/locksettings.db
- reboot, there is no lock or PIN, just swipe
- same as before but the message is now "Phone is starting..."
- gave up after 10 min of waiting
Need to actually USE my phone, so I stopped here and restored my trusty backup.
So, you can restore your backup with fingerprint. Judging by my experience restore is fully functional only on the physically same phone (same s/n, same MAC, etc, no hardware modifications).
Deleting data/system/locksettings.db did remove lock but still didn't make phone fully functional. However it's promising.
Click to expand...
Click to collapse
In the future (I've done this on the last several phones running AOSP or similar) I always change locksettings.db to locksettings.db.bak before doing a nandroid because I've had issues restoring ROMs then my PIN won't work, etc. Once I've unlocked my phone on a restore I change it back to locksettings.db
Click to expand...
Click to collapse
Related
I have installed the XenonHD few weeks ago so i am not using the most updated version.
http://forum.xda-developers.com/show....php?t=1667442
today when i am using the phone as normal, it suddenly rebooted.
when it is started, it didnt show any launcher screen or wallpaper but it required me a password to start up the phone.
It shows " Type password to decrypt storage".
As i remember there is a button for activating the encrypt storage function in the system setting/ rom setting.
I am 100% sure that i didnt press it. This function is activated somehow after the sudden reboot......
Is there a way to get the password or extract the data from the phone before i flashing a new rom.....
maybe you should try wiping dalvik cache, or just randomly try to unlock, eventually it should ask you what your google account is, and you should be able to unlock. or else you have to do this: make a nandroid backup, then, flash a new rom, use titanium backup to extract the apps and their data from the nandroid. hope this helps.
Because on https://twrp.me/google/googlepixel.html it says:
Decrypting Android 9.0 Pie when using a PIN / pattern / password does not work yet. We do not have an ETA for fixing decrypt. Restoring a backup made with an alpha using RC1 may result in loss of data including internal storage. If you need your backups from those versions, restore the backup using alpha2, then install RC1 and run a new backup with RC1.
Click to expand...
Click to collapse
I just flashed the official Android 9/P/Pie release (it did not fix the randomly dying microphone issue) and I want to do a full nandroid backup before I take my Pixel into UBreakIFix for a $0-80 fix because they require a locked bootloader and factory reset.
So do nandroid backups work or not?
SOLVED!
Answering my own question...
roirraW "edor" ehT said:
Since internal storage, where user apps and user and system app data are stored can't be decrypted, you'd definitely have to at least disable the pin/pattern/password, although you should confirm that doing so makes the storage readable in TWRP - it should.
Click to expand...
Click to collapse
According to this person, you must disable pin/pattern/password in order to decrypt the file system and allow nandroid backup & restore.
However, I just did a fastboot boot TWRP.img and it prompted me with my unlock pattern, and then it said "Data successfully decrypted". I checked, and I have access to the filesystem, and it even mounted to my connected laptop. So I'm testing this out. Backups completed successfully. I'll be trying a restore soon.
Archangel said:
The overwhelming response to what areas to tick when you back up has been system, boot, vendor and data,,,no images just the partitions. But that struggle is still on going LOL.
Click to expand...
Click to collapse
Backup & restore these 4 partitions (no images):
System, Boot, Vendor, and Data
(Note: for system and vendor you have to uncheck "mount system as readonly")
UPDATE:
Restoring my System and Vendor TWRP backups caused boot to hang at the G logo with an endless progress bar below the G.
However, doing a fastboot flash of System and Vendor factory images then restoring only my TWRP Data backup successfully restored my phone!
Except for one issue: fingerprints don't work. I think I may have screwed myself here by not disabling pin/pattern/password when I did the backup. For some reason TWRP had no problem decrypting then. But now, trying to restore, TWRP can't decrypt unless I disable pin/pattern/pass. It wont let me delete my old fingerprints or set new ones. Trying to unlock with fingerprint, it either doesn't respond at all or says "Fingerprint hardware not available"
UPDATE 2:
Followed instructions to clear the fingerprint data: [Guide] Delete fingerprint profils via TWRP. Everything is perfectly restored now! (Note: if you disable pin/pattern/pass before backup, you shouldn't need to do this)
Dear community, I am facing several troubles with my OP7pro which I think can be quite easily handled but my knowledge is just too little.
I am running OOS 10.0.2 with Renovate ICE, rooted with Magisk and on TWRP 3.3.1-70 - stock kernel and normally encrypted. I am facing various troubles that started after upgrading from 9.5.13 tot Android 10. I do not know if they are directly related. I do have Nandroids, BUT the phone is my daily driver, also for work, and a factory reset will just take too much time.
What are the troubles you ask?
- I am not able to enter the menu Buttons&Gestures/navigation/set up navigation bar. The screen blinks and I am back in the upper menu. If I press this menu again I get a "Settings stopped". This sucks, because I want to set up my on-screen buttons
- I used to use Plus Beat in combination with RICE on Android 9. Worked perfect. Whatever I set up, Plus Beat just does not work. That sucks big time.
- I am not able to set on screen buttons to for example switch between recent apps or get anything else but horizontal recents (which is slow and to me sucks). QuickSwitch via Magisk doesn't bring anything.
NOW TO THE QUESTIONS:
I GUESS (! but am not sure!) that a factoryreset could and should solve these problems. I could and would do that, but, I need to be up and running and have my settings back quickly. Internal memory (root) I could copy to PC and paste back afterwords. But is there some way I could put my settings (in the menu) and all my apps (250+) back via Nandroid data?
I have the following things backed up in TWRP:
- Boot
- System Image
- Vendor Image
- Data
- Modem
- EFS
If I do a complete new factory set-up (for example via Maurefranio's tool), to refresh my system (I guess the failure is in there), can I put back other parts of the Nandroid to have all the rest back? Also in the menu-settings, color-setting etc. etc. etc.?
I know it sounds rooky, but I hope someone takes time to help me a little. I do use Titaninium etc. but I can't spend hours and hours on a recovery. In that case I'd probably decide to keep using the OP7pro as I do, but it's frustrating that RICE and Plus Beat don't work fully and some other errors. The usability to me is 4 out of 10 - where in Android 9 it was surely 9 out of 10.
Greetings,
existenz
Are you running a substratum theme? That could be the settings issue. But that's about all I could help with. Never restored anything using twrp on this phone. Most I've done is backup my apps with swift backup, factory reset, or MSM tool, and restore my apps.
How quickly do you need your phone up and running? You could backup with swift backup, factory reset and only restore what you need for now then do the rest when you have time.
@GeekMcLeod: no, Substratum not even installed. All this trouble started after the regular update to Android 10.
But more my question is: IF I flash the whole phone back to factory setting (not a reset because the errors might still be there so a complete whipe and re-flash) - which part of Nandroid is usefull to get SETTINGS and APPS back? Just that. The internal memory I can copy and paste back.
I really hope someone can give me a quick instruction of how this works. Much appreciated!
exis_tenz said:
@GeekMcLeod: no, Substratum not even installed. All this trouble started after the regular update to Android 10.
But more my question is: IF I flash the whole phone back to factory setting (not a reset because the errors might still be there so a complete whipe and re-flash) - which part of Nandroid is usefull to get SETTINGS and APPS back? Just that. The internal memory I can copy and paste back.
I really hope someone can give me a quick instruction of how this works. Much appreciated!
Click to expand...
Click to collapse
In that case, I would just use swift backup, backup to your device. Transfer SD card contents to your computer, factory reset. Transfer SD card files back. Swift backup can backup all apps and data. I believe that would work for what you want.
I, however, do not know what parts of the nandroid do what as I usually just don't bother with it.
GeekMcLeod: appreciate your advise, but Nandroid is there for a reason.
Is there anyone who can please help me what to do best? I mean, one of those Nandroid-partitions holds the clue, right?
I am also facing overnight Batterydrain of about 30% (from 80 to 50 in about 7-7,5 hours).
No Nandroid specialists in the house?
You need to wipe your data. Use Swift to backup apps, messages and call logs. Google will do it's best to restore settings upon setup. Your problem is almost guaranteed to be in data. If you need that data, I would recommend going back to whatever version of pie you were on before. Swift won't restore app permissions, as far as I know so be sure to double check if you restore apps with Swift.
After my experiment of trying out Beta 3 of Android Q failed apocaliptical I tried to restore the backup I made minutes before. But no matter what I do, I keep getting:
- bootloops (straight rebooting after showing the unlocked bootloader warning)
- restart into recovery
- Oxygen OS loading animation stuck and animation being very slow
- not getting it anymore but had it yesterday in the early stages of my disaster management: Qualcomm Crash POST
Despite that the backup was generated succesfully (at least thats what TWRP said)
I tried almost every guide out there.
- switching to rm -rf
- restoring only data, only boot, only system and a mix of those
- flashing the OTA before restoring backup
- uninstalling magisk und reinstallating magisk (with and without separate reboots)
-multiple wipes of single partitions and data formatting
The only good thing is that I don't get the 255 error anymore I had at the beginng, allthough I don't really know anymore how I did it.
At the end I am only able to restore everything with the MSNTOOL out there.
Is there any golden hint to get the data the be restored? The backup of /data is critical as there my authenticator and banking data are in there.
Thank you in advance
Edit: As I am slowly getting fed up with OnePlus and the problems (proximity sensor, adaptive brightness, whatspps microphone, twrp issues, lacking tech guides if at all) I thought about migrating to Pixel 5. Is it possible to migrate the data partition? Or are all backup partitions strictily device specific?
anphex said:
After my experiment of trying out Beta 3 of Android Q failed apocaliptical I tried to restore the backup I made minutes before. But no matter what I do, I keep getting:
- bootloops (straight rebooting after showing the unlocked bootloader warning)
- restart into recovery
- Oxygen OS loading animation stuck and animation being very slow
- not getting it anymore but had it yesterday in the early stages of my disaster management: Qualcomm Crash POST
Despite that the backup was generated succesfully (at least thats what TWRP said)
I tried almost every guide out there.
- switching to rm -rf
- restoring only data, only boot, only system and a mix of those
- flashing the OTA before restoring backup
- uninstalling magisk und reinstallating magisk (with and without separate reboots)
-multiple wipes of single partitions and data formatting
The only good thing is that I don't get the 255 error anymore I had at the beginng, allthough I don't really know anymore how I did it.
At the end I am only able to restore everything with the MSNTOOL out there.
Is there any golden hint to get the data the be restored? The backup of /data is critical as there my authenticator and banking data are in there.
Thank you in advance
Edit: As I am slowly getting fed up with OnePlus and the problems (proximity sensor, adaptive brightness, whatspps microphone, twrp issues, lacking tech guides if at all) I thought about migrating to Pixel 5. Is it possible to migrate the data partition? Or are all backup partitions strictily device specific?
Click to expand...
Click to collapse
Try, booting into twrp... Format data. Type yes to format. Restore. Should boot.
@soka said:
Try, booting into twrp... Format data. Type yes to format. Restore. Should boot.
Click to expand...
Click to collapse
I did just exactly that on stock 10.0.0.11 to no avail, the TWRP restore went through fine but upon system reboot the phone stayed on the bootloader unlocked warning for about two minutes, then it rebooted straight into stock recovery.
It's beyond my understanding yet how the user data partition can cause the whole system to effing die.
My only hunch is that it has something to do with Magisk I had installed during the backup (encryption was disabled btw). But as I said I already tried running Magisk installer and uninstaller on different occasions with the same result. Also the only thing that should happen is that after restore and reboot the phone should tell me that Magisk isn't installed anymore.
Edit: So for now I reverted to full stock 10.0.11 and for the sake of experimenting I made a backup with system, boot and data of this stock rom and restored it succesfully. When I restore my actual data backup I get the same old restart and then it throws me back into TWRP. Is there any log I can check to see what's happening there?
Sorry for double post, but I think this might be very interesting for people with a similar problem as this seems to be very common with OnePlus phones.
So I found a very dirty and hacky way to get a least my most importants app running in the state they had during my backup I was trying to restore. Here's what I did, without any guarantee it might work for you or be stable in the end.
Code:
1. Revert the phone to a clean stock rom and update to the latest stable version (at the time of writing 10.0.11), it should be fully factory reset, aka like new. I am not sure but it may be necessary that you install the apps you want to restore first since the I am not sure the partition we use later contains the app AND the data too.
2. Unlock bootloader and flash latest TWRP, may it be official or mauronofio's
3. Make a backup of that current stock data partition
4. Restore data partition from your actual needed twrp backup (if it ends with 255, try to format data partition before in TWRP)
5. With the TWRP file manager navigate to the /data/data folder and copy everything to an external storage (I chose USB)
6. Restore the stock data partition
7. Now again with the TWRP file manager navigate to the /data/data folder on your external storage (should be /usbstorage) and search for the apps you need to restore (probably banking apps, authenticator, etc.), the name will be something like com.google.authenticator2.
8. Copy the folder of any needed app into the /data/data folder on your phone. Best you do it one by one just to make sure.
Now you can reboot to system. The apps should be fully restored. In my case it worked with Google Authenticator, Blizzard Authenticator, Consorbank Secure Plus (shows undefined error yet), Hue Pro. Maybe I will try more.
Edit: Consorsbank Secure Plus as you might guess is a tan generation banking app. When entering the pin when opening the app it shows "An error has occured". Dunno why, maybe a security checksum error or something. I found com.android.keychain and copied for the sake of trying too but it didn't help.
If you have any questions, suggestions or improvements, feel free to post!
Hi!
I think I managed to get two layers of encryption on my storage let me explain :
I had a pattern+fingerprint password. While changing my screen I also had to change the fingerprint sensor which lead to interface bootloop as I forgot to remove FP before changing sensor.
I tried a TWRP method to remove password from the device, consisting in removing some system files (which I didn't backup) without success, so I reopend th phone to plug the old sensor. This allowed me to remove my fingerprints and plug back the new sensor.
Now, I think my data is encrypted but the password is not prompted AND if i set the same password as before, I still can't access the data (even in TWRP as I think the encrypted data gets encrypted again)
Is there a way in TWRP (or other) to force a first decryption as I know both passwords?
Well, I removed my password and TWRP didn't prompt any pattern, and I can access my data.
However, My user remains encrypted with a password, and I can't figure it out.
I think the easy way is to copy my data and factory reset the phone.
Another way would be to clone full system partition to try recover the deleted files I think