1055 uk version 8.1 june pach
was stack on 8.0. changed plusnet sim (runs on EE network) for ( not working one) from freedompop, but didnt have other so tried) and suddenly 3 updates within hour.
first 8.1 with May security
after reboot somethin 22a fix
another reboot june security patch
must be something EE is doing to updates. i bought sim free from John Lewis but still had EE app installed after turning on phone or it instaled itself without my permision as i have put sim in slot before turning phone on. so deleted it but still couldn't get updates.
put in different sim and updated immediately .
might be bug only, but finally do have last updates
Hi Friends,
My new nokia 7 plus just stopped working suddenly. The device is switched off and whenever I try to switch it on it flashes a message that "com.android.phone stopped working". It goes on doing this in a loop automatically switching off and on and giving this error message. Any clue as to how to resolve this. I had not installed the Nokia P beta update and was on July security patch update. I am unable to use the device now.
TIA
My P20 pro CLT-L29 432 is stuck on 9.0.0.47 and has been for months USB, Hi Suite methods do not work neither has OTG so far bootloader is locked and FRP is locked even after removing google account and resetting the phone
Any Ideas?
I am also stuck on 9.0.0.286 and it doesnt tell me to update from OTA or HISuite..
Also for some reason the update information are missing. It says "no information" instead of " security patch etc"
I also did a factory reset but it didnt help...
Maybe some could give an advice.
same here no info and 9.0.0.286 version in austria
Iv asked huawei service yesterday they say that is no problem and update will be made by imei number and I have to wait so I don't know what to believe
Grazeholder said:
I am also stuck on 9.0.0.286 and it doesnt tell me to update from OTA or HISuite..
Also for some reason the update information are missing. It says "no information" instead of " security patch etc"
I also did a factory reset but it didnt help...
Maybe some could give an advice.
Click to expand...
Click to collapse
no info
patch no information provided
From my observations, if phone is updated through a method other than OTA(Hisuite PC included), there will be no info about update in phone updater. Also, OTA might not work (my phone was stuck on 191 when I bought it second hand, no OTA, but imediately updated to 286 when connected to Hisuite PC. Didn't have update info with 191 and still no info with 286. Never received an OTA this whole time)
Didn't receive OTA for 9.1 and force updated using Firmware finder and modded Hisuite(to 311). Still no info after that.
Today Iv contacted huawei and they've said my serial number is ok and they will push send me the update. Iv tried all methods FF patched hisuit to instal no success.
dejandoggy1 said:
Today Iv contacted huawei and they've said my serial number is ok and they will push send me the update. Iv tried all methods FF patched hisuit to instal no success.
Click to expand...
Click to collapse
Let us know if that will work so i can try do the same and contact them
any luck?
How did you contact Huawei? I used the website a few weeks ago but never got a reply.
Iv contacted Huawei from Hicare app tells you in which huawei centar can you call and you can also chat online with them. Try from hicare app quick services
fatgit said:
How did you contact Huawei? I used the website a few weeks ago but never got a reply.
Click to expand...
Click to collapse
dejandoggy1 said:
Today Iv contacted huawei and they've said my serial number is ok and they will push send me the update. Iv tried all methods FF patched hisuit to instal no success.
Click to expand...
Click to collapse
dejandoggy1 said:
same here no info and 9.0.0.286 version in austria
Iv asked huawei service yesterday they say that is no problem and update will be made by imei number and I have to wait so I don't know what to believe
Click to expand...
Click to collapse
dejandoggy1 said:
Iv contacted Huawei from Hicare app tells you in which huawei centar can you call and you can also chat online with them. Try from hicare app quick services
Click to expand...
Click to collapse
did they push a update?
Tonight received by regular OTA in Austria
I contacted Huawei support via Hicare app (Chat) and told them that I didn't received any OTA update since April security patch this year, the last update I did was via Hisuit from 9.0.0.270 to 9.0.0.286 (which was my/Hisuit mistake because the update was not planned for my device) CLT-L09C432, and I didn't get any OTA since then.
I was told through phone call, after receiving information via Remote Smart Diagnostic, that they have informed the Huawei software development department about the problem, and I should get my update during this week.
I waited till Wednesday but nothing happened, then I backed up all my data via Hisuit, downgraded to 9.0.0270 via Firmware Finder Hisuit (Hacked version ) did a factory reset.
After logging in got notification for 9.0.0.293 did the update successfully, after the update got notification for update to 9.1.0.311, again did updated successfully, and last after the update got notification for update to 9.1.0.328 (August security patch) also installed successfully, and phone is running smoothly.
So who else is stuck on the 9.0.0.286 or older version this might do some trick with updating the phone via OTA eventually.
Have a nice day.
Just my 2 Cents.
sPEADy said:
I contacted Huawei support via Hicare app (Chat) and told them that I didn't received any OTA update since April security patch this year, the last update I did was via Hisuit from 9.0.0.270 to 9.0.0.286 (which was my/Hisuit mistake because the update was not planned for my device) CLT-L09C432, and I didn't get any OTA since then.
I was told through phone call, after receiving information via Remote Smart Diagnostic, that they have informed the Huawei software development department about the problem, and I should get my update during this week.
I waited till Wednesday but nothing happened, then I backed up all my data via Hisuit, downgraded to 9.0.0270 via Firmware Finder Hisuit (Hacked version ) did a factory reset.
After logging in got notification for 9.0.0.293 did the update successfully, after the update got notification for update to 9.1.0.311, again did updated successfully, and last after the update got notification for update to 9.1.0.328 (August security patch) also installed successfully, and phone is running smoothly.
So who else is stuck on the 9.0.0.286 or older version this might do some trick with updating the phone via OTA eventually.
Have a nice day.
Just my 2 Cents.
Click to expand...
Click to collapse
How did u do the hisuite method
TheDevGuy9497 said:
How did u do the hisuite method
Click to expand...
Click to collapse
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/page144 have a look at that, it's very clear and self explanatory, good luck.
sPEADy said:
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/page144 have a look at that, it's very clear and self explanatory, good luck.
Click to expand...
Click to collapse
i just get "failed to update"
I'm stuck on 311. Asks me to update everyday also at the end it says patched 01. I'm on 9.1 now but I've not noticed any changes from emui 8. Nothing sticks out, nothing has improved. I'm thinking it's not installed the firmware which was around 400mb because it takes less than 1 minute to download then less than a minute to install. Once it's installed, it asks to download and install again, every day for 2 months. I don't have access to a pc anyone help with this? Or how can I install beta 10 emui in the UK
Recently I have installed the latest firmware update onto my N950N. Since then my device has been getting the IMS Service has stopped error. I have tried allot of the troubleshooting steps on the internet, which don't work. I have even performed a hard factory reset of the device. That didn't work either. Can anybody provide me with any assistance please?
The recent 11-09-2019 update has resolved this error!! Just wish that they released it earlier so I wouldn't have to purchase a Note 9 N960N!!!!!!!
Lol
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
WhiteReign said:
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
Click to expand...
Click to collapse
Apparently happens to some users when they update to December.
Just delete your old face data as it says and rescan.
WhiteReign said:
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
Click to expand...
Click to collapse
Some have reported the same issue when updating to December via fastboot with a wipe and clean install. Sometimes a factory reset works, other times not. Luckily, the January update is around the corner. Hopefully it is fixed by then
WhiteReign said:
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
Click to expand...
Click to collapse
Mine happened a little different when updating to this version. My Face info was saved from the previous version but wasn't working 100% of the time. I deleted my cached face data and tried to retake but the blocks weren't showing on the face capture. So I then disabled all unlock methods, rebooted the phone and then tried to set up a pin and face again and everything worked as it should.
enrollment was not completed ( face enrolment didn't work)
ibphantom said:
Mine happened a little different when updating to this version. My Face info was saved from the previous version but wasn't working 100% of the time. I deleted my cached face data and tried to retake but the blocks weren't showing on the face capture. So I then disabled all unlock methods, rebooted the phone and then tried to set up a pin and face again and everything worked as it should.
Click to expand...
Click to collapse
It happened for me as well ( Pixel 4) after I've downgraded from Android 11 Beta to the latest stable 10.0.0 (QQ3A.200605.002, Jun 2020) via the Android Flash Tool.
I tried to factory reset my phone few times, even deleted Esim. Nothing helped ( could do register my face during phone setup or later after I skipped it)
I tried different builds but the only 1 which worked for me 10.0.0 (QD1A.190821.007, Oct 2019). I was able to register my face-unlock, lock bootloader and receive the latest OTAs.
I flashed this build with Platform Tools and also changed the configured security key instead of the Pin during setup.
Not sure if this was an issue with Android Flash Tool or Pin security.
Update
xorwin said:
It happened for me as well ( Pixel 4) after I've downgraded from Android 11 Beta to the latest stable 10.0.0 (QQ3A.200605.002, Jun 2020) via the Android Flash Tool.
I tried to factory reset my phone few times, even deleted Esim. Nothing helped ( could do register my face during phone setup or later after I skipped it)
I tried different builds but the only 1 which worked for me 10.0.0 (QD1A.190821.007, Oct 2019). I was able to register my face-unlock, lock bootloader and receive the latest OTAs.
I flashed this build with Platform Tools and also changed the configured security key instead of the Pin during setup.
Not sure if this was an issue with Android Flash Tool or Pin security.
Click to expand...
Click to collapse
Actually it stopped working in a few hours or so. Found out that this issue started from DP4 when you fastboot back to stable.
As a workaround, I opted to Beta again, where Face-Unlock Works. Then I opted out and received OTA stable and issues with Face recognition were gone. Yaaay
The latest Telstra june image fix the face id issue when downgrading from Android 11, the buid number is QQ3A.200605.002.A1
gm007 said:
The latest Telstra june image fix the face id issue when downgrading from Android 11, the buid number is QQ3A.200605.002.A1
Click to expand...
Click to collapse
What is the difference between this one and the standard version?