I want to know that for all those who suffered from the IMEI 0/ No service problem, and those who managed to fix it, I came to know that the problem will be back as soon as we update the phone with OTA.
Does this problem get a fix with Android 8.1, June Security Patch update?
If not, what's the workaround to avoid 0 IMEI problem after the update.
Just back up your efs when it's working properly and restore it if it ever nesses up.
Sent from my XT1806 using Tapatalk
Related
Note 8 SM-N950F/D after downgrade from 8.0 to 7.1.1 wifi signal is to week
i downgraded from 8.0 to 7.1.1 than my phone lose imei after i fix it with reinstaling 8.0 now my wifi is tooo weeekk i have tried to reset my phone but still same signal does anybody can tell me anything about this??
and now when i check my phone with samsung info apk. i cant see CSC CODE and Frimware CSC code ore available code .
can anybody help me
Try wiping the cache partition in recovery mode. That should help. If it doesn't then you would have to perform a hard factory reset.
i did it but nothing same problem
can i try to reflash again Oreo 8.0 with odin ??
Try using Kies to repair your device. It maybe missing specific drivers that is causing your issue
How did you downgrade? I am also interested in downgrading to 7.1.1
Why are people downgrading to 7.1.1?
NIKKOTUASON said:
Why are people downgrading to 7.1.1?
Click to expand...
Click to collapse
Because they don't like Oreo for whatever reason. Some have mentioned battery issues, or problems with specific apps. For others it works great.
i have dowgraded with odin
i like oreo but battery is much better with 7.1.1
Can you downgrade if yours isn't rooted? I got the crappy boot locked version :[
i can dowgrade without root
if you have bootloader v3 you can downgrade my note is with v3 bootloader some note 8 after oreo update thay have bootloader v4 from v4 to v3 you cant downgrade from v3 to v3 you can
i found a solution I've put sticker film back on my phone and it stops receptions after i removed everything is good now :laugh:
Hello everyone,
Yesterday I flashed my moto g5s plus with flashable android oreo update. Later I found out that the network drops frequently. So I tried to downgrade to Nougat 7.1 and was successful doing so. Then I was amazed to get the official OTA of oreo 8.1 but due to unlocked bootloader I couldnt install that as it eventually gave me an error. So I tried to relock bootloader but failed to do so due to the clear warning of bootloader downgrade(that was because I updated to oreo and downgraded to Nougat). Later I tried locking the bootloader using the oreo files i.e. the extracted files from oreo firmware, althought I was on Nougat but was successful. But the network started to drop frequently and was unable to use the network services. So I rushed to moto service centre where I was first said there could be a problem with the motherboard lol. But I told them to just flash the firmware as I thought it was a s/w issue. The firmware flashing resolved the problem of network droping but the new issue arrised, which was, when I place a call the receiver gets the call but cannot hear anything same goes to my device. Even i couldnt hear anything. The service centre advices to replace an IC, which they say is damaged and he added that my device is showing "fake network".
Can anyone please help me with this?
Thank you!
Give the phone to SC and ask them to do the necessary things as they suggested.
Hi. I have a nokia 7 plus TA-1046 build 00WW_2_22M
The problem is that i have this phone for last year and i am stuck at 8.1 August 1 Security update. I check regularly for updates but besides one security update nothing. I am from Romania dunno if that matters. On every forum i saw people on pie and i am stuck onto oreo. Is there any connection with my network provider or ota is from nokia. I got an android one for the fuss of being up to date. And i am behind so many other phones on updates. I did nothing on the phone downgrade upgrade kernel ROMs. Its clean. I also tries some variants that support from nokia gave me. Like remove sim and conect to wifi and try. Go into safe mode and try from there to. Clean catch from carrier service and remove sim and go and check. None work. Any ideas for a proper non warranty removed method to get an update?
Yes, just download the update and flash it yourself. It isn't very hard and the effect is the exact same as an OTA update so it doesn't void your warranty.
Better stay in oreo cause this latest pie
updates bricked my wifi and sd card
8i advice you to keep the phone with oreo.
ntzntz said:
Hi. I have a nokia 7 plus TA-1046 build 00WW_2_22M
The problem is that i have this phone for last year and i am stuck at 8.1 August 1 Security update. I check regularly for updates but besides one security update nothing. I am from Romania dunno if that matters. On every forum i saw people on pie and i am stuck onto oreo. Is there any connection with my network provider or ota is from nokia. I got an android one for the fuss of being up to date. And i am behind so many other phones on updates. I did nothing on the phone downgrade upgrade kernel ROMs. Its clean. I also tries some variants that support from nokia gave me. Like remove sim and conect to wifi and try. Go into safe mode and try from there to. Clean catch from carrier service and remove sim and go and check. None work. Any ideas for a proper non warranty removed method to get an update?
Click to expand...
Click to collapse
Buna seara / hello,
I think you should manually update. Follow this
https://forum.xda-developers.com/nokia-7-plus/development/ota-nokia-7-plus-ota-links-t3818774/page99
I have a TA-1046 dual SIM, international version (yours is probably the same).
I was stuck first on Oreo 8.0 in April and I had to manually update to 8.1. After that I got OTAs without any problems until the Pie update.
In September I had to manually update to Pie, but since then I got every OTA.
Everything works fine, no issues with WIFI. I do not use an SD card. Pie is better than Oreo and you need the latest security patches.
Mult succes.
It's interesting that some people don't have any issues with last updates but quite a lot of people have the same issues i have,today i tested my friend's phone and has the same firmware like i do but yet no issues for him
Btw: before you upgrade, august is last version can be unlocked
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?
Yesterday afternoon I received a 2.3 GB update, which turned out to be the security patch for April. It installed normally but immediately started causing system and app failure. The problem arises when scrolling, as if the update time on the screen is reduced. It is a continuous stutter. I have restored the factory settings and the problem persists. Did something similar happen to them? Solutions? The truth is, I don't know what to do anymore. Will it be hardware? The phone has 3 months of use and prior to the update it worked perfectly.
Sorry if my post violates any forum rules, I'm new to this.
You could try going in to the system update again. Then click the menu top right and download latest package and try flashing it again