Database Info

Unable to enrol fingerprint.

I have the Z5 (non premium nor dual sim) and i have flashed a few roms onto it aswell as formatted everything using twrp recovery and still get this annoying message every time i try and setup my fingerprint. "Unable to read fingerprint. please clear some space on the internal storage and try again" or something to that effect. when i check storage it says i have over 10GB available. any help would be greatly appreciated.

i dont even get the fingerprint option my z5 is very strange

vibealite said:
i dont even get the fingerprint option my z5 is very strange
Click to expand...
Click to collapse
Are you from the US? Or did you flashed a US Rom? Because the American Z5 hasn't the fingerprint option.
It ain't an hardware problem, cuz the power button is the same on every Z5 so I guess if you try to flash another Stock Rom it shall enable it?

iam in the uk dunno the rom i flashed says central europe
dunno but ill give it a try should i flash any uk firmware?

You can try to flash whatever Stock Rom you want except the US one whom hasn't the fingerprint enabled.
It may, (Once again am not sure at all but you can give it a try) it may enable you fingerprint sensor.
I'm French and my Z5 Runs on Marshmallow Stock Fr, my FP Sensor is working perfectly.
When you have successfully flashed a new stock Rom check on Settings > security > fingerprint manager (screenshot linked)
I'm just trying to help you and give you somes tracks to follow, but I'm not responsible if you broke/brick your phone

spastikitten said:
I have the Z5 (non premium nor dual sim) and i have flashed a few roms onto it aswell as formatted everything using twrp recovery and still get this annoying message every time i try and setup my fingerprint. "Unable to read fingerprint. please clear some space on the internal storage and try again" or something to that effect. when i check storage it says i have over 10GB available. any help would be greatly appreciated.
Click to expand...
Click to collapse
You tried to flash some custom Rom? How about trying to flash a stock one?
If it's not working try to wipe everything via flashtool.
If those two answers don't help you to fix your problem, I unfortunately don't know what you can do more

Baradoura said:
You tried to flash some custom Rom? How about trying to flash a stock one?
If it's not working try to wipe everything via flashtool.
If those two answers don't help you to fix your problem, I unfortunately don't know what you can do more
Click to expand...
Click to collapse
Yeah I've tried flashing multiple custom Roms. 3 variants of the stock rom. And have wiped the internal storage countless times with twrp. So I'm kind of at a loss now. Is there any other way to clear the storage on the phone without trwp? That's my only other thought since twrp may not be wiping that partition or section of data or what ever it may be

As I said use Flashtool to wipe everything, also if you have twrp I assume that you're root isn't it, so may be the problem can be here, a bad manipulation or if you haven't restored your DRM Keys it probably come from this.
I know that on Samsung phones when you loose DRM your fingerprint sensors is lost so perhaps it's the same thing for Sony?
I don't know but you should try to wipe everything and if you still have the backup of your DRM Keys try to put it back and see if it works

Baradoura said:
As I said use Flashtool to wipe everything, also if you have twrp I assume that you're root isn't it, so may be the problem can be here, a bad manipulation or if you haven't restored your DRM Keys it probably come from this.
I know that on Samsung phones when you loose DRM your fingerprint sensors is lost so perhaps it's the same thing for Sony?
I don't know but you should try to wipe everything and if you still have the backup of your DRM Keys try to put it back and see if it works
Click to expand...
Click to collapse
This is the screen that I am getting. The phone did this earlier at one point after flashing a custom rom then after a while it started working again. I have also made a backup of the keys for my phone.
I will give flash tool another crack this morning and see how it goes but I have done it before so I have very little hope.

So try this :
-Flash a stock Rom ftf file
- Restore the DRM Keys
-Try to set the fingerprint
I didn't root my phone yet so I don't know if you have to restore DRM before flashing a new stock Rom.
Either way I think you know how it works so try this and when it's done come back here to tell if it's OK or not, I'm following this topic until you're fixed don't worry

Baradoura said:
So try this :
-Flash a stock Rom ftf file
- Restore the DRM Keys
-Try to set the fingerprint
I didn't root my phone yet so I don't know if you have to restore DRM before flashing a new stock Rom.
Either way I think you know how it works so try this and when it's done come back here to tell if it's OK or not, I'm following this topic until you're fixed don't worry
Click to expand...
Click to collapse
alright will do this now and get back to here asap. i must say though that i did this last night aswell.

Ok don't worry I'll try my best to help you, go ahead and get back here when it's done.

Baradoura said:
Ok don't worry I'll try my best to help you, go ahead and get back here when it's done.
Click to expand...
Click to collapse
Not sure how this worked but i flashed the stock rom over a custom rom (XZ4 i think it was) but all of my apps are there and the fingerprint scanner seems to be working now.

Ok good news, so try it a few days and see how your z5 handle it.
To me it seems to be good now we will see with time
---------- Post added at 06:25 AM ---------- Previous post was at 06:23 AM ----------
May be it wasn't your phone, but the ftf file who was corrupted?

Don't we get fingerprint reader on custom roms then just on stock?

vibealite said:
Don't we get fingerprint reader on custom roms then just on stock?
Click to expand...
Click to collapse
I don't think so, what's the point of having a custom Rom without that feature? May be it depends on the ROM you're using?
I'm pretty sure that fingerprint exist in both Custom and stock ROM

Baradoura said:
I don't think so, what's the point of having a custom Rom without that feature? May be it depends on the ROM you're using?
I'm pretty sure that fingerprint exist in both Custom and stock ROM
Click to expand...
Click to collapse
iam on eXistenZ n i dont seem to have it dunno why

Baradoura said:
So try this :
-Flash a stock Rom ftf file
- Restore the DRM Keys
-Try to set the fingerprint
I didn't root my phone yet so I don't know if you have to restore DRM before flashing a new stock Rom.
Either way I think you know how it works so try this and when it's done come back here to tell if it's OK or not, I'm following this topic until you're fixed don't worry
Click to expand...
Click to collapse
hey dude i just tried what u sed flashed a uk firmware i didnt get fingerprint iam starting to fink my device doesnt have one

i have a pixel 2 on Android P

So I have a Google Pixel 2 and I installed the android P preview via sideload but I had my bootloader locked now I can try to toggle OEM unlock and put in my pattern but after I put my password in it still says it's off idk what to do I haven't tried to flash the 8.1 factory image or unlocking yet but idk if I'll be able too there's I'm almost 100,% sure it's not a Verizon model I don't have any Verizon apps and on 8.1 I could toggle this on and it's not greyed out

I am also not able to change this in the preview, maybe you could install the 8.1 OTA (afterwards a factory reset)to go back. Flashing a factory image will not work with a locked bootloaded, OTA also works with locked BL.

EnormoDerClown said:
I am also not able to change this in the preview, maybe you could install the 8.1 OTA (afterwards a factory reset)to go back. Flashing a factory image will not work with a locked bootloaded, OTA also works with locked BL.
Click to expand...
Click to collapse
That wouldn't brick my phone?

Before you attempt anything extreme, I suggest factory reset your phone and do the minimal setup to get into the settings and try toggling

I did still no luck

To be fair: i can not guarantee that, but i can just imagine 3 scenarios:
1. Update fails, OTA install fails
2. OTA installs but a lot of FC´s with apps (factory reset afterwards shoudl get rid of that)
3. Everything installs and is functional without doing anything (i don´t think so).
i would expect, that option 2 would occure

Installation failed, called Google to see if they could do anything they only referred me to the Android beta website, guess I'm stuck till DP2 comes out

AaronGavin said:
Installation failed, called Google to see if they could do anything they only referred me to the Android beta website, guess I'm stuck till DP2 comes out
Click to expand...
Click to collapse
This is a long shot, but try disabling your lock screen security PIN if you have one, then check the setting again. If still greyed out, try setting a PIN, then check again. This typically prompts for your PIN, maybe somehow something got messed up in the sideload.

March update could just be to old, April update could work because of newer data. OTA checks whether the update is older/newer.

quakeaz said:
This is a long shot, but try disabling your lock screen security PIN if you have one, then check the setting again. If still greyed out, try setting a PIN, then check again. This typically prompts for your PIN, maybe somehow something got messed up in the sideload.
Click to expand...
Click to collapse
That actually worked xD thank you

AaronGavin said:
That actually worked xD thank you
Click to expand...
Click to collapse
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.

quakeaz said:
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.
Click to expand...
Click to collapse
It was never greyed out just after I put my password in it wouldn't turn on the slider and at first I just thought maybe it is on but bugged out but after I removed my password it just turned on properly I'm about to test it as soon as the factory image downloads again

quakeaz said:
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.
Click to expand...
Click to collapse
Back on 8.1 ?

Encryption Issues

Hi, I hope you guys can help. I have an OPO which is on Android 8 as per this link and it was all working fine (well, it's a bit buggy in places, but I can live with it!).
I have TWRP installed (3.2.3.0), and had no problems with it, was easy to access and install/backup with it; I have reasonably recent backups too (but wait for it....), and phone is rooted using Magisk.
Anyway, in a recent bout of paranoia, I encrypted my phone. It's a long story, but the company I work for recently employed an IT company to manage its systems and I didn't want them poking about where they shouldn't (they are not particularly good).
The encryption worked straight away, and clearly functions as it should; rebooting the phone requires a pattern unlock, and the phone is clearly marked as encrypted.
HOWEVER when I went to try and get into TWRP, I was faced with the same pattern unlock request - I tried it, and my pattern doesn't work. I have seen suggestions about disabling screen lock, or changing it to a PIN, but this doesn't affect the pattern unlock on TWRP. I reckon I can probably access the backups when unlocked via PC file transfer, so presumably can flash these via ADB, but I'm a bit loathe to in case something horrible happens.
So, is there a solution? do I:
try and reflash TWRP/different version of TWRP
flash the backup?
try and decrypt the phone
cry?
with regards decrypting, I can't see any way of reversing the encryption one it has happened - kinda wish I'd known that before I'd done it.
Help would be greatly appreciated. It isn't a major problem, phones working, it's just my modding is kinda curtailed....

Would this one work?
GitManMatt said:
Hi, I hope you guys can help. I have an OPO which is on Android 8 as per this link and it was all working fine (well, it's a bit buggy in places, but I can live with it!).
I have TWRP installed (3.2.3.0), and had no problems with it, was easy to access and install/backup with it; I have reasonably recent backups too (but wait for it....), and phone is rooted using Magisk.
Anyway, in a recent bout of paranoia, I encrypted my phone. It's a long story, but the company I work for recently employed an IT company to manage its systems and I didn't want them poking about where they shouldn't (they are not particularly good).
The encryption worked straight away, and clearly functions as it should; rebooting the phone requires a pattern unlock, and the phone is clearly marked as encrypted.
HOWEVER when I went to try and get into TWRP, I was faced with the same pattern unlock request - I tried it, and my pattern doesn't work. I have seen suggestions about disabling screen lock, or changing it to a PIN, but this doesn't affect the pattern unlock on TWRP. I reckon I can probably access the backups when unlocked via PC file transfer, so presumably can flash these via ADB, but I'm a bit loathe to in case something horrible happens.
So, is there a solution? do I:
try and reflash TWRP/different version of TWRP
flash the backup?
try and decrypt the phone
cry?
with regards decrypting, I can't see any way of reversing the encryption one it has happened - kinda wish I'd known that before I'd done it.
Help would be greatly appreciated. It isn't a major problem, phones working, it's just my modding is kinda curtailed....
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692

The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136

Taurus_XDA said:
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Click to expand...
Click to collapse
Thanks for this, I'll give it a go now

Working again
Taurus_XDA said:
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Click to expand...
Click to collapse
yep, that's awesome, fully up and running now. Just for anyone else experiencing this problem, I downloaded the TWRP version listed above, then flashed it via ADB (unlock USB debugging on your phone, connect it, open a powershell window where you keep your adb files, 'adb reboot bootloader' then 'ffastboot flash recovery [NAME].img' and it will reinstall TWRP with the new version).
Bit of a moment when I rebooted to recovery, as faced with the same decryption unlock window, but this time the decryption worked and was able to access TWRP fully.
Nice one.

Unable to add lock screen

I unlocked the bootloader today without any noticable averse effects. When I was setting up the phone I restored from Google's cloud backup. While I was going through setting up the lock screen and it wouldn't let me. I would go through the motions to add a fingerprint but every time I would add a pattern I would be asked to add the pattern again. No matter what I do, setting up the lock screen will not stick! I also performed a factory reset and didn't restore anything from the cloud backup and no luck. Does anyone else have this problem? If you know how to fix it I would really appreciate it. Here's a couple screen shots, but I don't think they'll help. Here's to trying

I just got Magisk installed after flashing a patched boot image through fastboot and I still can't add the fingerprint or lock screen. Any suggestions are welcome

I was unable to lock my screen with my bootloader unlocked and i need it locked for some of my apps to work so i relocked my bootloader.

Marco0070 said:
I was unable to lock my screen with my bootloader unlocked and i need it locked for some of my apps to work so i relocked my bootloader.
Click to expand...
Click to collapse
Does magisk still work with a locked bootloader?

Mustachetic said:
Does magisk still work with a locked bootloader?
Click to expand...
Click to collapse
I didn't install magisk sorry I don't know
Sent from my moto z4 using Tapatalk

Marco0070 said:
I didn't install magisk sorry I don't know
Click to expand...
Click to collapse
I updated to 105-75 and reinstalled magisk. I am able to add a lock screen. My device passes safety net also

Mustachetic said:
I updated to 105-75 and reinstalled magisk. I am able to add a lock screen. My device passes safety net also
Click to expand...
Click to collapse
Thanks for the update
Sent from my moto z4 using Tapatalk

I ran into this problem as well. It would not let me set any kind of lock screen. I was trying to install the Verizon software in order to get WiFi calling, per the thread elsewhere here in the Z4 forums.
I had thought the issue was related to either Magisk, copying from my old phone, or when I was trying to set the lock screen during the setup process, so I ended up doing the following (going from having bootloader unlock and running on Verizon rom but not being able to add a screen lock)
-Wipe data
-Flash initial Verizon ROM
-Do initial setup but skip trying to set screen lock in the setup process
-After setup, then set screen lock
-Update to latest Verizon ROM
-Flash patched boot image corresponding to the updated ROM
I'm not sure if the problem was Magisk related or if it got screwed up setting the lock screen during the initial setup process and skipping that and doing it later fixed the issue, but those were my two guesses. Eventually it all worked, and I now have lock screen and root via Magisk working along with WiFi calling. It passes Safety Net.

I had the same thing happen when I first got my phone. What ended up resolving the issue for me was that I flashed the image as root in Linux.

Tried to do a factory reset, now I can only book into TWRP

Hello folks,
I successfully installed TWRP and Magisk on G7 Power, without needing to use a stock image, using flug32's guide https://forum.xda-developers.com/showpost.php?p=81305325&postcount=358
(I didn't install Edxposed)
Restored apps and settings via Google Backup, installed ViperFX & CallRecorderFix from Magisk and increased media volume levels in BuildProp.. Everything was working fine for a couple of days, and then the camera kept giving me the Camera Busy error; the usual restore permissions, and restart phone fixes didn't sort it, so wanted to a factory reset. Tried this from settings, but of course, it just boots in TWRP. So then I saw a post that seemed to suggest that you have to do a wipe via TWRP to do this, and now it just boots back into TWRP, I presume that I have wiped something that is needed during normal startup.
Is it possible for me to get it to boot back into the stock image that is/was on the phone, and if so, how do I do a factory reset?
Or am I going to have flash another stock image (the RETGB doesn't seem to be available) following the instructions in this thread https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138

Dark-Eyes said:
Hello folks,
I successfully installed TWRP and Magisk on G7 Power, without needing to use a stock image, using flug32's guide https://forum.xda-developers.com/showpost.php?p=81305325&postcount=358
(I didn't install Edxposed)
Restored apps and settings via Google Backup, installed ViperFX & CallRecorderFix from Magisk and increased media volume levels in BuildProp.. Everything was working fine for a couple of days, and then the camera kept giving me the Camera Busy error; the usual restore permissions, and restart phone fixes didn't sort it, so wanted to a factory reset. Tried this from settings, but of course, it just boots in TWRP. So then I saw a post that seemed to suggest that you have to do a wipe via TWRP to do this, and now it just boots back into TWRP, I presume that I have wiped something that is needed during normal startup.
Is it possible for me to get it to boot back into the stock image that is/was on the phone, and if so, how do I do a factory reset?
Or am I going to have flash another stock image (the RETGB doesn't seem to be available) following the instructions in this thread https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138
Click to expand...
Click to collapse
I think you are going to need to flash a stock rom.
Are you sure it was on software channel Retgb?
Not Tescogb or Eegb
It's a 1955-4 ?
Sent from my mata using XDA Labs

sd_shadow said:
I think you are going to need to flash a stock rom.
Are you sure it was on software channel Retgb?
Not Tescogb or Eegb
It's a 1955-4 ?
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I am pretty certain that it was on RETGB, as it came unlocked from another supplier, and I seem to remember checking after I had rooted it.
If I put Tescogb or Eegb on it, will that lock it to those networks ?
It is a 1955-4, so I presume RETEU is the best option for a compatiable unlocked ROM.

Dark-Eyes said:
I am pretty certain that it was on RETGB, as it came unlocked from another supplier, and I seem to remember checking after I had rooted it.
If I put Tescogb or Eegb on it, will that lock it to those networks ?
It is a 1955-4, so I presume RETEU is the best option for a compatiable unlocked ROM.
Click to expand...
Click to collapse
Using Tesco or EE will not lock it to those carriers
But there maybe some radio issues.
Yes you will likely have batter compatibility with a 1955-4 rom
Reteu does look like the best option.
Sent from my mata using XDA Labs

@sd_shadow
Do I need to use the same version that I was on, 134-4, or shall I use the updated 134-7 one?
Is there anything else that I need to be aware of, or am I okay just following this guide https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138

Dark-Eyes said:
@sd_shadow
Do I need to use the same version that I was on, 134-4, or shall I use the updated 134-7 one?
Is there anything else that I need to be aware of, or am I okay just following this guide https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138
Click to expand...
Click to collapse
Either version should be fine.
But update will have newer security patch.
That guide is good.
Sent from my mata using XDA Labs