after using the dialer menu to update to .187 on my lya-09 i can no longer use face unlock. i deleted the stored faces to see if this would fix it and i can no longer even enroll my face, it just sits at the look directly at the screen part and never goes any further. any ideas?
even after a factory reset i still cannot enrol face. it recognises my face is there but does not prompt me to turn my head like it usually does. i have no idea why
What's the dialer menu update method?
Found it.
djisgod I'm sorry that I can't offer you any help, but if you please keep us posted abot your problem and eventual solution. Thx in advance
It's probably seeing the software as modified and not allowing you to use the secure face unlock feature. Or it's broken by the update which might be why they've delayed it.
I'm not sure it is very strange. Does anybody know which apk or app it is that does the face enrolling so i can try and install a different version?
i have done the update, and face unlock works without any problem for me, but i also have the lya-l29
still no luck with this. i have tried reset to factory settings and reinstalling the firmware. neither work.
and now it has suddenly started working again. lol not sure why it stopped but i am glad its back!
which update file have you used to update your phone?
describe exactly which file you've used to update via dialer menu AND even which model do you use?
I used the update for my phone the lya-09 c432. 9.0.0.187 update file. All is working fine now. Not sure what was going on but face unlock is now working again.
Related
I recently rooted my One and had networking issues so i flashed this rom ( http://forum.xda-developers.com/showthread.php?t=2266025 ) and after flashing though the networking issues were fixed it then had issues with the back and home buttons, as the phone did when i purchased it, so i located and installed the ota patch that tmobile had pushed to fix it, and there was an error installing it, but the buttons were fixed anyway, but now my camera app does not work, i can open it and see nothing but black, the apps buttons do not appear to respond and after some time i get a "unable to start camera: error. i cannot locate a apk or anything similar to try to reinstall the camera app, other apps i launch tell me "error accessing camera", any help would be appreciated
Update: just discovered, the light does not work either
fixed issue by flashing a different rom and flashing back
i had the same problem
I never actually solved it though. It happened when a replacement was already on the way so i didn't bother trying to fix it. I did research a little and came across a few people that said a bad kernel flash could cause this. I was running the stock kernel and stock rom, and it was working just fine before the OTA so i figuered it was probably a hardware issue. If i were you i would try flashing another kernel. If doesnt work call up tmo and they will probably send you a replacement(you can also contact them through the live chat the on the website, much more convenient in my opinion). I had blown speaker and they didnt even ask about unlocking the bootloader or root, i assume it is because it was clearly a hardware issue. If you figure it out, please share.
Hey guys.
Reaching out to see if any has been able to use the Firmware Finder app to update the firmware? Currently I'm on 108 however can download 122 via the app:
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
Now is does say its incompatible at first however you can indeed download either the latest OTA or full firmware, but seemingly can't get the device to acknowledge it. Things I've tried:
- Using the VPN and DNS options in firmware finder, then checking for system updates
- Putting the downloaded OTA zip in a created folder on internal storage called DLOAD, rebooting to recovery, but nothing happens.
- Tried extracting all the contents of the zip into that folder, again recovery doesn't acknowledge it.
It'd be great if we could perform manual updates like this, though annoying if the best we could do is merely download it!
Anyone any suggestions?
Let's see if we can get this working...
*update - seems I was entering recovery (power off and then power on holding power button + volume up) where I should have gone to download mode (hold both volume up and down). It gets to a screen but says Installation Failed. That's with the zip directly in the DLOAD folder and then sigh the contents extracted....
I used to use this app on my Honor 9 Lite, however it hasn't worked for a long time.
The method they used was to spoof the Huawei servers using DNS etc to trigger an OTA but Huawei changed the server location.
This app purely exists now to tell you there is an update available to download, however you'll need to use other methods to get it installed, which probably requires an unlocked bootloader at the very least, then a firmware flash tool.
jusumgeezer said:
I used to use this app on my Honor 9 Lite, however it hasn't worked for a long time.
The method they used was to spoof the Huawei servers using DNS etc to trigger an OTA but Huawei changed the server location.
This app purely exists now to tell you there is an update available to download, however you'll need to use other methods to get it installed, which probably requires an unlocked bootloader at the very least, then a firmware flash tool.
Click to expand...
Click to collapse
Is there a way to establish that new location, to then use the correct proxy/DNS details?
cd993 said:
Is there a way to establish that new location, to then use the correct proxy/DNS details?
Click to expand...
Click to collapse
Apparently not, or at least the developer of that App doesn't seem to think so.
I am also looking to update to the latest firmware too, it has been pushed out to some devices, but nothing for me yet. Although I did get a 3 branded update, I'm hoping that hasn't messed up my OTA's from Huawei
jusumgeezer said:
Apparently not, or at least the developer of that App doesn't seem to think so.
I am also looking to update to the latest firmware too, it has been pushed out to some devices, but nothing for me yet. Although I did get a 3 branded update, I'm hoping that hasn't messed up my OTA's from Huawei
Click to expand...
Click to collapse
See I was on Three but moving over to O2. When I first set the phone up, I used the O2 sim but then put my Three sim in and will use until my number gets transferred over. Ive no Three branding yet
cd993 said:
See I was on Three but moving over to O2. When I first set the phone up, I used the O2 sim but then put my Three sim in and will use until my number gets transferred over. Ive no Three branding yet
Click to expand...
Click to collapse
That's similar to what I did, put my old Tesco(O2) sim in slot 1 - No branding. The next day I also put my 3 sim into slot 2, after a few minutes an OTA pops up.
Checked on here a a few people said it's safe to install, it just activates Wi-Fi calling & the 3 apps.
After reboot it had also installed a 3 splash screen & changed my chrome homepage to the 3 website.
Minor annoyances yes, apparently fixed by a Factory reset. I just hope the change in software version doesn't delay future updates. Hopefully this 122 update pushes out soon.
jusumgeezer said:
That's similar to what I did, put my old Tesco(O2) sim in slot 1 - No branding. The next day I also put my 3 sim into slot 2, after a few minutes an OTA pops up.
Checked on here a a few people said it's safe to install, it just activates Wi-Fi calling & the 3 apps.
After reboot it had also installed a 3 splash screen & changed my chrome homepage to the 3 website.
Minor annoyances yes, apparently fixed by a Factory reset. I just hope the change in software version doesn't delay future updates. Hopefully this 122 update pushes out soon.
Click to expand...
Click to collapse
Cool yeah well I'm on Three network but yet to be branded, but still haven't received an update so likely the branding isn't a cause, perhaps...
Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.
Fingerprint is not working in wickr with android pie on G965F, when i start the app i get the message: Too many attempts. Try again later. i get the message before trying to unlock with fingerprint.
Tried contacting their support and they told me to uninstall restart, create new fingerprints, restart, re-install, restart, enable fingerprint, restart.
I have tried all i can think of except factory reset but ill guess that's next, just wanted to see if any1 have fingerprint in wickr working on pie and G965F
donthomaso said:
Fingerprint is not working in wickr with android pie on G965F, when i start the app i get the message: Too many attempts. Try again later. i get the message before trying to unlock with fingerprint.
Tried contacting their support and they told me to uninstall restart, create new fingerprints, restart, re-install, restart, enable fingerprint, restart.
I have tried all i can think of except factory reset but ill guess that's next, just wanted to see if any1 have fingerprint in wickr working on pie and G965F
Click to expand...
Click to collapse
Same here, using TheGalaxyProject ROM on Pie.
Are you using stock?
Yes. Stock without root.
Ive just tried a complete reset and reinstall with the same problem, so suspect it is with the device.
I'll raise with Wickr Devs - plz do the same so they are aware.
Did you do factory reset? I've already notified their support.
Same for me after upgrading my stock S9 to One UI today. Annoying thing is I can't remember my password. Used to just use finger print unlock. When this happened before I upgraded I would just press the menu key and close the app, restart it and finger print unlock would work. After updating this work around no longer works.
K'+
I got a mail from their support. They are working on it.
It's fixed in the latest version.
It was working fine and I haven't replaced any display or screen protector. The only thing I tried was rooting a phone. But I revert it back and install an official ROM from first and tried some factory reset.
Try using this site, with the latest version of Chrome: https://pixelrepair.withgoogle.com/
At the bottom, use the "Install fingerprint calibration software" button. Apparently that can fix this issue for some.
Jaitsu said:
Try using this site, with the latest version of Chrome: https://pixelrepair.withgoogle.com/
At the bottom, use the "Install fingerprint calibration software" button. Apparently that can fix this issue for some.
Click to expand...
Click to collapse
It says downloading and in step 2 couldn't install.
beevekmgrz said:
It says downloading and in step 2 couldn't install.
Click to expand...
Click to collapse
Could you elaborate on what you mean by that? What's the specific error?
As you told I have already tried repairing "Install fingerprint calibration software" from here. (https://pixelrepair.withgoogle.com/). During those steps there 3 steps .. and the first step is to download it download the files after I connected in fasboot mod..
As it goes to step 2 .. It give an error couldn't install..
@beevekmgrz If I understand you correctly, you tried to root, had an issue, then flashed a stock ROM back to the device? Now you are having problems with the fingerprint scanner and have tried to repair it using the Fingerprint Calibration Software, only to receive an error in step 2?
Have you enabled OEM Unlocking and USB Debugging in the ROM? Either or both could be blocking you from completing this.
Not rooted. Using beta build. Had lots of issues with fingerprint enrollment. Had a privacy screen protector. Had to get rid of that, didn't work, always timed out half way through. Went to one of my old screen protectors clear. Would get about 90% before timing out with a error. Got a different screen protector that said fingerprint friendly. Works. Did redo my 2 of 4 fingerprints without a screen protector. It worked great. The new screen protector actually works but not as good if you don't use nothing at all.
I had the same issue when I got my 6a back from a google warranty repair. Error was 'Can not communicate with fingerprint sensor...consult repair service' ...or pretty close. Had to send it back AGAIN! Really pissed at google atm...EVERY repaired phone should have to pass a FULL diagnostic before being returned to the customer!
Strephon Alkhalikoi said:
@beevekmgrz If I understand you correctly, you tried to root, had an issue, then flashed a stock ROM back to the device? Now you are having problems with the fingerprint scanner and have tried to repair it using the Fingerprint Calibration Software, only to receive an error in step 2?
Have you enabled OEM Unlocking and USB Debugging in the ROM? Either or both could be blocking you from completing this.
Click to expand...
Click to collapse
Yup but I tried root and it worked.. but later I went back to stock..OEM unlocking is bootloader unlocked.and usb debuggis is on too...