Hi,
I am using an orange Pixel4 mobile phone. After upgrading to Android11, I went back to Android10. The face unlock module cannot be used normally, and got the message ‘Enrollment was not completed Face enrollment didn't work’, And i used the Telstra version in June and it cannot solve this problem. In addition, I tried to use the January/March/April and the latest July ROM, but the problem could not be solved. Using April's ROM and using the Magisk module(https://forum.xda-developers.com/pixel-4-xl/how-to/module-fix-broken-unlock-t4095233) also could NOT solve this problem. Does anyone know the reason? (And my white and black version of Pixel4 could solve the problem of face unlock when using the June Telstra version or the July ROM)
Thank you.
Working fine here after downgrading from a11 b2.5 to a10 July image.
How did you downgrade?
gianton said:
Working fine here after downgrading from a11 b2.5 to a10 July image.
How did you downgrade?
Click to expand...
Click to collapse
I can confirm, all fine here
gianton said:
Working fine here after downgrading from a11 b2.5 to a10 July image.
How did you downgrade?
Click to expand...
Click to collapse
Thank you for your reply,
And I had downgrade Android 11 DP4 to Android10 (QQ3A.200605.001, Jun 2020)
That is from ./flash-all.sh the image of
Android11 DP4: flame-rpp4.200409.015-factory-8012c549.zip
to ./flash-all.sh the image of
flame-qq3a.200605.001-factory-8f1b5911.zip
My other white Pixel4 and black Pixel4 had also been downgraded from Andoird11 to Android10, and the image in July can solve the face unlock break, but except for this orange one.
d414d4 said:
Thank you for your reply,
And I had downgrade Android 11 DP4 to Android10 (QQ3A.200605.001, Jun 2020)
That is from ./flash-all.sh the image of
Android11 DP4: flame-rpp4.200409.015-factory-8012c549.zip
to ./flash-all.sh the image of
flame-qq3a.200605.001-factory-8f1b5911.zip
My other white Pixel4 and black Pixel4 had also been downgraded from Andoird11 to Android10, and the image in July can solve the face unlock break, but except for this orange one.
Click to expand...
Click to collapse
Try with the online flash tool instead, worked great for me.
gianton said:
Try with the online flash tool instead, worked great for me.
Click to expand...
Click to collapse
Thanks for following up.
I had try online flash tool instead, but it would not work for me.
I plan to wait for the August image to have a try, and send this issue to support of google.
Thank you.
Related
I just fresh flashed stock 8.0.0 (OPR6.170623.019, Sep 2017) and I keep getting "No SIM" it started yesterday 2 times, and 4 times so far today, before this build I had 8.0.0 (OPR6.170623.013, Aug 2017 and started getting the same thing, then it wouldn't boot at all, so I full wiped and installed 8.0.0 (OPR6.170623.013, Aug 2017 again, which was updated to Sept build right after the first boot, the phone has been fine for about a week, now it's giving my the SIM error again GRRRRRR
Any ideas? While I was down before the full wipe I was using my old Nexus 5, and never got the error, so, to me that rules out a bad SIM
idbl_fanatic said:
I just fresh flashed stock 8.0.0 (OPR6.170623.019, Sep 2017) and I keep getting "No SIM" it started yesterday 2 times, and 4 times so far today, before this build I had 8.0.0 (OPR6.170623.013, Aug 2017 and started getting the same thing, then it wouldn't boot at all, so I full wiped and installed 8.0.0 (OPR6.170623.013, Aug 2017 again, which was updated to Sept build right after the first boot, the phone has been fine for about a week, now it's giving my the SIM error again GRRRRRR
Any ideas? While I was down before the full wipe I was using my old Nexus 5, and never got the error, so, to me that rules out a bad SIM
Click to expand...
Click to collapse
Did you try an older radio.img, some people use the boot.img from the previews. If You check the thread search from any Oreo thread you'll see you're not alone.
I believe if you flash boot.img from developer preview 4 can fix this issue.
Exodusche said:
I believe if you flash boot.img from developer preview 4 can fix this issue.
Click to expand...
Click to collapse
Where might one obtain this?
idbl_fanatic said:
I just fresh flashed stock 8.0.0 (OPR6.170623.019, Sep 2017) and I keep getting "No SIM" it started yesterday 2 times, and 4 times so far today, before this build I had 8.0.0 (OPR6.170623.013, Aug 2017 and started getting the same thing, then it wouldn't boot at all, so I full wiped and installed 8.0.0 (OPR6.170623.013, Aug 2017 again, which was updated to Sept build right after the first boot, the phone has been fine for about a week, now it's giving my the SIM error again GRRRRRR
Any ideas? While I was down before the full wipe I was using my old Nexus 5, and never got the error, so, to me that rules out a bad SIM
Click to expand...
Click to collapse
It might not be anything you did, when I installed the OTA for september and Oreo update I also got a no sim message a few times. Completely stock / unrooted phone. I restarted and it went away but popped up once since. This phone is brand new (just got it as a 6P replacement through a google store RMA) so I know my phone hasn't been messed with, I think they might have a bug in the build. You on projectFi by any chance?
Bounty44 said:
You on projectFi by any chance?
Click to expand...
Click to collapse
No, I am on AT&T
idbl_fanatic said:
No, I am on AT&T
Click to expand...
Click to collapse
Ah alright. Well I just wanted you to know you aren't alone at least lol. Hopefully the october update will include some fixes.
I can't seem to find the reteu stock rom with august patch. I tried flashing back to stock with May patch but It keeps saying up to date. This is because something got messed up I guess when unlocking the bootloader and flashing roms. I know how to flash back to stock I just can't find the August version of RETEU stock rom
use search function
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
siddhesh9146 said:
use search function
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
Click to expand...
Click to collapse
Thank you for your reply. But that's the indian version. I need the RETEU (europe) version with august patch.
InsaneNexuS said:
Thank you for your reply. But that's the indian version. I need the RETEU (europe) version with august patch.
Click to expand...
Click to collapse
it doesn't matter it is RETAIL or RETEU; until it is on same security patch and boot-loader version then its okay to flash
siddhesh9146 said:
it doesn't matter it is retail or reteu; until it is on same security patch and boot-loader version then its okay to flash
Click to expand...
Click to collapse
flashing now! If this works you're my hero!
it works! it says reteu and I have august patch but software channel is same as indian version. but hey! It works thanks!!!!
I try to install Oreo Beta 2 and it says older time stamp and degrade is unavailable. I researched a bit and found that I need to flash back to older firmware. I downloaded it from the STOCK thread but I couldn't sideload it. It says footer is wrong, sig verf failed and other stuffs. Im currently on the lastest firmware
Have you updated to the latest firmware with January security update if so that's why
r8dooo said:
Have you updated to the latest firmware with January security update if so that's why
Click to expand...
Click to collapse
Yes, I have.
So there is no way to do it now?
You should be able to downgrade if your bootloader is unlocked.
loctuantran said:
Yes, I have.
So there is no way to do it now?
Click to expand...
Click to collapse
I updated to latest security patch for January and unlocked bootloader and flashed to Oreo beta 2 no issues. Essential.com and do it step by step and should have no issues.
Hi guys, I recently read about 7.1.1 being officially released, the thing is I already updated to Nougat via the soak test uploaded last year, should I revert to stock rom and get Nougat officially? How it is on performance quality?, Also, I'm on September security patch, do i have risk of bricking?
If you flash this through fastboot you will get 1 November 2017 security patch without having to downgrade. Then you may get December and February updates
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
igna.98 said:
If you flash this through fastboot you will get 1 November 2017 security patch without having to downgrade. Then you may get December and February updates
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
How is your GPS on that firmware? Also, do you know if that firmware will work on the XT1607?
zahna said:
How is your GPS on that firmware? Also, do you know if that firmware will work on the XT1607?
Click to expand...
Click to collapse
I'm not able to tell you how GPS works because I don't own the phone, I installed it in a friend's phone. And AFAIK it can be installed on all models except Verizon's XT1609. Tell me if it works for you
igna.98 said:
If you flash this through fastboot you will get 1 November 2017 security patch without having to downgrade. Then you may get December and February updates
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
will it work on xt1607 ?
UPDATE: I will try it, when i get back home.
Hello i am on March 1, 2018 8.0.0 with Root and TWRP , what is the best way to update to the latest stock rom and not break my phone. Thanks a lot
Better update to Nov 2018 8.1
.:Addicted:. said:
Better update to Nov 2018 8.1
Click to expand...
Click to collapse
Can u tell me how to do that without losing my data? i have twrp and magisk installed, i know i have to reflash magisk but i just install the image from twrp and i am good to go ?
I would return to clean stock ROM of the same version as you're running (restore stock boot image or reflash the whole ROM) and let the OTA engine handle the selection of necessary updates. You might receive the latest full Pie ROM or it will update incrementally, hard to say
.:Addicted:. said:
Better update to Nov 2018 8.1
Click to expand...
Click to collapse
_mysiak_ said:
I would return to clean stock ROM of the same version as you're running (restore stock boot image or reflash the whole ROM) and let the OTA engine handle the selection of necessary updates. You might receive the latest full Pie ROM or it will update incrementally, hard to say
Click to expand...
Click to collapse
Best way is to flash with Mi Flash Tool?
bibos85 said:
Best way is to flash with Mi Flash Tool?
Click to expand...
Click to collapse
The best way is to use flashing script manually, as you should remove bootloader unlock/lock commands from it.