Database Users

Lock bootloader after root and ROM custom

Hello, guys.
Recently, i wanted to install the fulmics ROM (which is awesome) on my LG G6 H870.
So, i've done it, the bootloader has been unlocked, it's rooted right now, and i've got the Fulmics ROM which works perfectly.
But, i still have a question. When i boot up my phone, i've got this message :
"Your device software cannot be checked for corruption. Lock the bootloader. etc..."
This isn't a problem, because i can boot up my phone.
But i just wanted to know if i can remove this message, and how ?
Thank you all for your answers and your help.

This is normal and cannot remove that message. Just ignore it, how many times do you actually reboot for it to be an issue? If you ever need send phone off for repair just flash stock and lock bootloader again.

normal bro don't worry

[/COLOR]
basicreece said:
This is normal and cannot remove that message. Just ignore it, how many times do you actually reboot for it to be an issue? If you ever need send phone off for repair just flash stock and lock bootloader again.
Click to expand...
Click to collapse
dude I've got a question: if you wanted to get your bank's app working again in a custom rom/recovery is it possible to relock the bootloader in order to get older compatibility (mario kart, spotify options, bancoestado) but in a system like PA Quartz 3 or PixelExperience ? Or bootloader wont boot locked another system than LG?
I seriously need those apps but also need Android 10

learning_to said:
[/COLOR]
dude I've got a question: if you wanted to get your bank's app working again in a custom rom/recovery is it possible to relock the bootloader in order to get older compatibility (mario kart, spotify options, bancoestado) but in a system like PA Quartz 3 or PixelExperience ? Or bootloader wont boot locked another system than LG?
I seriously need those apps but also need Android 10
Click to expand...
Click to collapse
Magisk manager and use the magisk hide feature.

Zenfone Max pro m1 after rooting and installing twrp, phones fingerprint and lock o

Yesterday unfortunately I dropped my phone after that I rooted my device and installed twrp! But now my screen light glows very late after unlocking through fingerprint or unlock button or double tap wake up! Is this problem due to hardware issue or this is due to bugs of software after rooting? Anyone help plz

Yes, it's a bug.

its a hardware problem rooting and installing twrp cannot cause the screen to lightup late. unroot flash stock rom lock bootloader and take phone to service center dont take phone to service center rooted and with twrp and with unlocked bootloader.

austinpinto said:
its a hardware problem rooting and installing twrp cannot cause the screen to lightup late. unroot flash stock rom lock bootloader and take phone to service center dont take phone to service center rooted and with twrp and with unlocked bootloader.
Click to expand...
Click to collapse
Bro i unrooted my phone! Now it works fine! But i want to root it back without any bug

flash the latest version of magisc

Essential PH-1 downgrade

Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.

stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service

stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Did you unlock your critical partitions along with the bootloader?

arjunv said:
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
Click to expand...
Click to collapse
Do you think you could link that post for me? I can't seem to find it.
I also don't see any uicc option on my debice. (Not sure or that matters though)

If it's Sprint you need to wait 50 days before you can unlock it. CDMA phones are a pain in the ass to unlock, always buy International if possible!
This thread has some information that might be useful:
https://forum.xda-developers.com/essential-phone/help/unlock-sprint-version-t3720727
Sent from my PH-1 using XDA Labs

SuperBrolySSJ said:
Did you unlock your critical partitions along with the bootloader?
Click to expand...
Click to collapse
This is required for the touch screen firmware to be flashed and OP needs to see this.

Pixel 4 - FAce Unlock issue - Not working

Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad

pdash79 said:
Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad
Click to expand...
Click to collapse
I haven't seen this issue and face unlock works properly even with sun glasses on. Contact Google(chat/call) see what they say.
https://store.google.com/repaircenter

I don't have much issues with Face Unlock, but please keep us informed what the Google Repair Center says about that issue you have, pdash79.
But I have questions about this Face Unlock:
- How much of the face needs to be visible (means, unmasked due to Corona infection preventing rules) to make that thing work?
- Can a second "Face pattern" (one with masked face) be learned so the unlock works even with mask up?

pdash79 said:
Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad
Click to expand...
Click to collapse
Yeah I just did a warranty claim over this issue. Curious did u flash a rom ? Anyway it just stopped working out of the blue

pdash79 said:
Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad
Click to expand...
Click to collapse
I have had the same problem, and I have flashed several times until I realize that the problem is in the update of April 5, flash an old ROM and it is solved

gaseoso said:
I have had the same problem, and I have flashed several times until I realize that the problem is in the update of April 5, flash an old ROM and it is solved
Click to expand...
Click to collapse
Hey. Thanks a lot man. I did flash a rom from Jan and it did solve the issue.
Thanks a lot for your advice.
Saved me hell lot of trouble.
Was troublesome to use pin or pattern.
Hope google resolves it in future updates.
But they have not even acknowledged it seems.
Stll hope then fix.
Thanks again.

pdash79 said:
Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad
Click to expand...
Click to collapse
Had this also and the problem was that I installed a custom kernel.
Flashed a new firmware on the phone and it works again.

I had same issue, so i did flash older rom to fix it, just want to know if the may 2020 update solve the problem before i download the update

I had issues with the face unlock twice already while having the phone.
I wasn't able to re-enroll my face and got error messages.
Since my bootloader is unlocked I figured that locking it will wipe it completly (factory reset did not help by itself)
Indeed, after locking, and unlocking the bootloader, the issue resolved. twice.

Just curious is anyone has had this problem with a locked bootloader (never unlocked) and only did OTA updates?

bobby janow said:
Just curious is anyone has had this problem with a locked bootloader (never unlocked) and only did OTA updates?
Click to expand...
Click to collapse
Not me, as I unlocked the bootloader since day one.
But, it did happen to me once after OTA (sideloaded).
Try to unlock and re-lock your bootloader, it should resolve it but all content of the phone will be erased.
The reason I think it works is that the biometric is saved somewhere not reachable but since unlock/lock operations are so data destructive so it is probably erasing old/corrupted bio info.

thehartk said:
Not me, as I unlocked the bootloader since day one.
But, it did happen to me once after OTA (sideloaded).
Try to unlock and re-lock your bootloader, it should resolve it but all content of the phone will be erased.
The reason I think it works is that the biometric is saved somewhere not reachable but since unlock/lock operations are so data destructive so it is probably erasing old/corrupted bio info.
Click to expand...
Click to collapse
So you're not having any issues at all? If I go to the March build it works again but as soon as the phone updates it's broke again! If I use the Android 11 preview it works but they're too many bugs I've tried several times to wipe and lock and unlock the bootloader but nothing will get it working!

The guys from Russian 4pda, made a magick module that fixes face unlock, for whom it does not work on April and May firmware.

OK, I made a module for for Magisk to fix Face Unlock
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP

How to add a link?
---------- Post added at 11:28 AM ---------- Previous post was at 11:27 AM ----------
Displax said:
OK, I made a module for for Magisk to fix Face Unlock
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
я не успел?

DanDroidOS said:
So you're not having any issues at all? If I go to the March build it works again but as soon as the phone updates it's broke again! If I use the Android 11 preview it works but they're too many bugs I've tried several times to wipe and lock and unlock the bootloader but nothing will get it working!
Click to expand...
Click to collapse
I'm on April build and it works.
I had the issue when updating from March to April, did my routine and all is good now.

Displax said:
OK, I made a module for for Magisk to fix Face Unlock
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
Worked perfect, thank you! :good: How did Google manage to break FU with the update and why are only some affected?

Guys, anyone tried May update and see if the problem solved from who's getting the issue before on April update?
I'm still using an old update till someone try and till us

pdash79 said:
Hi,
I started facing an error with Pixel4 since last two days.
Two errors i am getting:
1) When i tried to unlock, it didnt unlock and popped the message, "Hardware Not Found".
2) I tried removing my face data and adding it again, it gave the error: "Face Enrollment didnt work".
I have seen that lot of people are facing these issues.
Why this is an issue is that there is no other biometric way of authentication to get into the phone other than face unlock.
I am having to use PIN or PATTERN to get into the phone.
Anyone here has faced this issue and knows how to get it fixed?
Any news on this would be appreciated.
Thanks,
Prasad
Click to expand...
Click to collapse
go into your camera app settings and disable frequent faces. restart your phone and try out the face unlock

jalado said:
go into your camera app settings and disable frequent faces. restart your phone and try out the face unlock
Click to expand...
Click to collapse
I updated to May 2020 Security update.
Then tried out disabling frequent faces, restarted and tried the face unlock.
Bow it is giving the message that Hardware not found.
I thought of removing face data and re-adding it and then trying.
It does not even let me delete my face data.
Please advise what i can do to fix it.
Thanks,
Pdash

Help? Fingerprint Reader Stops Working ONLY After Bootloader Re-lock?!?

Hey guys...I know I posted this in the persist thread, but I figured it might deserve a dedicated post here just in case there's a bigger issue at play or is something that's relatively unknown.
So long story short, unlike many on here I wanted to go back to a stock, locked, unrooted state after being unlocked & rooted (otherwise stock OOS) for a couple months. Unfortunately, upon doing this my fingerprint scanner stopped working (instantly errors with "enrollment was not completed - fingerprint registration error, please try again" when trying to enroll a fingerprint).
So when the guide came out the other day to repair the fingerprint scanner I tried it. I started off by re-unlocking my bootloader (from full stock, locked, unrooted) so that I could grab the persist partition backup that I hadn't done before. After rebooting suddenly, magically my fp scanner started working again. Then after verifying I could enroll several fingerprints, I booted to TWRP (didn't flash it, just booted) and flashed the magisk zip.
After this, I rebooted and backed up my now-working persist.img partition.
I then did a factory reset from the settings menu, which should return the device to 100% stock. After the reset, I verified during initial setup that the fp scanner was still working properly. I then rebooted to fastboot, and upon re-locking the bootloader received a g.co/ABH message in red saying the device was corrupt and that it would not boot.
I then used the latest 10.5.10 MSM tool to re-flash back to full stock again, which caused it to then boot up as expected. At this point, I tested the fp scanner again during initial device setup and it was once again back to not working.
I then re-enabled OEM unlocking in settings and rebooted to fastboot again. Another bootloader unlock. After reboot I tested the fp scanner again during initial device setup. Lo and behold, it's back to working again.
So I stopped midway through the fp enrollment (just hit back, didn't complete) and rebooted back into fastboot mode. Re-locked bootloader again and booted back up. FP scanner again back to not working with the same "enrollment was not completed - fingerprint registration error, please try again" error.
And once again I re-unlocked the bootloader, enrolled a FP during setup, and then used the MSM tool again. After MSM it again produced the same results - FP scanner wouldn't work upon reboot.
And before anyone asks - I am in contact with OP support for either a warranty replacement or a repair...but this whole situation just doesn't make even the slightest bit of sense to me. Basically my FP scanner works perfectly fine with an unlocked bootloader, but any attempt at re-locking it renders it useless. I do have a working persist backup, but obviously can't flash it from a locked state. Anyone else have any suggestions on something to try, or at least have any sort of theory as to why this behavior would be happening? I have never had a phone where attempting to RE-lock the bootloader has been such a freaking pain.

No one has any idea on this, or theories as to what could be taking place and causing this? OP support has been a total trainwreck so far.

Hi, Did you get a solution for this ? I am facing the same issue of fingerprint sensor not working after relocking the bootloader, although in my case I did not have to reflash the persist img. It works when unlocked and stops working when locked. As usual OP after sales are not really helpful. Thanks

Greetings,
same issue here.. has anybody an answer to this problem? It's driving me crazy...
Thank you very much!

shakathesaint said:
Greetings,
same issue here.. has anybody an answer to this problem? It's driving me crazy...
Thank you very much!
Click to expand...
Click to collapse
I've been trying to solve this issue today, as we speak. However, it seems like the guide to restore the FP reader does not apply to our phone (I have the OP8, but it behaves exactly the same) because we still need root to restore the FP reader, and it will be lost upon relock. In other words, we are stuck. OEM repair/replacement seems to be the only solution.

AarSyl said:
I've been trying to solve this issue today, as we speak. However, it seems like the guide to restore the FP reader does not apply to our phone (I have the OP8, but it behaves exactly the same) because we still need root to restore the FP reader, and it will be lost upon relock. In other words, we are stuck. OEM repair/replacement seems to be the only solution.
Click to expand...
Click to collapse
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.

Related, on 11.0.2.2 magisk and unlocked, my fingerprint sometimes won't recognize at all and forces password unlocks. No corrupt persist or delete and re register a finger solved it.

shakathesaint said:
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Click to expand...
Click to collapse
Oh, thank you! I will certainly try!

shakathesaint said:
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Click to expand...
Click to collapse
I'm writing just to update about the tests above: unfortunately neither of them is working, so I'm starting to think there's no other solution than sending the phone to RMA.

Has any one found a solution for this? Im facing exactly the same problem.