I created a backup from TWRP tonight and I noticed that the serial number of my phone has changed from ZX1G2***RS to 65***e28. Is this an issue I have to worry about? I have made multiple TWRP backups and the serial number has always been the first serial number. Even when going to Settings > About Phone > Status it now shows the second (new) serial number. I haven't factory reset or wiped the phone in quite a while, I've only installed the monthly security updates.
I have the same problem after updated to the latest 2017.10.06. LineageOS build, i have a new serial number in bootloader, TWRP and in Android itself (ZX1G*****G changed to 9d1****7). I have to reactivate my mobile banking app because of this.
The same thing happened to me after sideloading the October 5, 2017 security update.
8zabi said:
I have the same problem after updated to the latest 2017.10.06. LineageOS build, i have a new serial number in bootloader, TWRP and in Android itself (ZX1G*****G changed to 9d1****7). I have to reactivate my mobile banking app because of this.
Click to expand...
Click to collapse
stevemw said:
The same thing happened to me after sideloading the October 5, 2017 security update.
Click to expand...
Click to collapse
Weird. Thanks for your replies!
Related
Please help.
After updating to a new ROM, my Note 4 serial number changed in about> device>status and when I press *#06# there is no serial number showing at all. The fingerprint scanner has stopped working. Can anyone please help? Please look at the picture. The IMEI number is showing fine.
Ganbara_Knight said:
Please help.
After updating to a new ROM, my Note 4 serial number changed in about> device>status and when I press *#06# there is no serial number showing at all. The fingerprint scanner has stopped working. Can anyone please help? Please look at the picture. The IMEI number is showing fine.
Click to expand...
Click to collapse
If you made EFS backup then just restore it.
Or flash stock firmware from odin.
This happened after I switched to the latest twrp, and it wouldn't load that partition...so I didn't backup that partition (never expected this to happen).
Ganbara_Knight said:
This happened after I switched to the latest twrp, and it wouldn't load that partition...so I didn't backup that partition (never expected this to happen).
Click to expand...
Click to collapse
Have you solved this problem?
Yes, I resolved it. I happened to have a back up of my NOTE 4 from two years back. I had to flash that backup via TWRP, this fixed the issue for me and got the fingerprint back on the NOTE 4. That was the only way for me to do it.
Ganbara_Knight said:
Yes, I resolved it. I happened to have a back up of my NOTE 4 from two years back. I had to flash that backup via TWRP, this fixed the issue for me and got the fingerprint back on the NOTE 4. That was the only way for me to do it.
Click to expand...
Click to collapse
Can you send me a copy of EFS partition please? I have same issue, but i have no backup ( IMEI is good but serial not match and fingerprint don't work. When open settings it says something like "fingerprint is having problem. If you see it often then reboot your device."
Sorry for my bad English.
VoCs_007 said:
Have you solved this problem?
Click to expand...
Click to collapse
Same things occurred to me. The only way I resolved it was to have a backup from months back that I flashed again. The only thing I could not do was use the finger-print scanner. Flash a backup you have prior to the error occurring to resolve it.
Ganbara_Knight said:
Same things occurred to me. The only way I resolved it was to have a backup from months back that I flashed again. The only thing I could not do was use the finger-print scanner. Flash a backup you have prior to the error occurring to resolve it.
Click to expand...
Click to collapse
So fingerprint is working after restore?
Yes.
Must say that i found my old backup of custom ROM that was fith this phone and flashed it back. FingerPrint is working now but the rom is uncomfortable so i gone back to my rom) The mean is that FingerPrint is working in hardware) Problem is in custom roms.
(Sorry for bad my English)
Had my xz1c updated to 47.1.F.1.80 before then I reset my phone. It stayed on the same build number but I was not able to update it. Companion says not supported, see attached screenshot
long time reader of the site first time poster. i love xda and i havent seen this method of frp for ths device mentioned anywhere and i saw it as maybe a opportunity to contribute back to the site
anyways what i did was during inital setup and what not use the talkback method to get to the language download page and i just clicked a bunch of different languages download button and eventually opened up the samsung app store and was able to downloiad my way into the settings from there i just disabled the most of google apps and cleared the cache was able to add my gmail account and voiila
device info:
sm g960u on 8.0.0
samsung expeirence version 9.0
baseband g960usqs3brj6
build# r16nw.g960usqs3brj6
security patch is november 1 2018 (ive only updated it once since frp )
i hope i posted this correctly
exnfox said:
long time reader of the site first time poster. i love xda and i havent seen this method of frp for ths device mentioned anywhere and i saw it as maybe a opportunity to contribute back to the site
anyways what i did was during inital setup and what not use the talkback method to get to the language download page and i just clicked a bunch of different languages download button and eventually opened up the samsung app store and was able to downloiad my way into the settings from there i just disabled the most of google apps and cleared the cache was able to add my gmail account and voiila
device info:
sm g960u on 8.0.0
samsung expeirence version 9.0
baseband g960usqs3brj6
build# r16nw.g960usqs3brj6
security patch is november 1 2018 (ive only updated it once since frp )
i hope i posted this correctly
Click to expand...
Click to collapse
Hi! So, you did this with November 2018 security patch?
that or a earlier one.;..
SOLVED - see 2nd post
I upgraded two (2) Nexus 6 phones to LineageOS 16. One was running LineageOS 14, the other was running stock. I installed the corresponding bootloader and radio images via fastboot.
On both phones, the SIM card is not detected. They both had functioning cellular before the update. One has an AT&T GSM SIM, the other has a Sprint ICCID card.
The SIM status menu reports "Not available" for all fields. Also noteworthy is that the IMEI is "Unknown".
I've checked the SIM cards and they're good. Airplane mode is off. Security is off (screen unlock is disabled, and no filesystem encryption).
Searched through the forums and haven't found anything that helps. Hoping someone may have run into this before with Lineage 16. TIA
Reverting to stock 7.1.1 (N6F27M, Oct 2017) restores IMEI and SIM card detection. This confirms that it's a firmware issue, not hardware.
From there I ran fastboot -w, re-installed bootloader, radio and LineageOS 16. The SIM card was still not detected, and no IMEI was shown.
Reverted to factory image again and IMEI was recognized. This time I installed LineageOS 16 only (wiped system, data, dalvik, cache of course). I did not update the bootloader or radio. Finally success! IMEI and SIM are recognized.
This happened on 2 Nexus 6 devices. Other people have also reported this, so it can't be a device-specific issue. I recommend mentioning this in the OP to help save a lot of headache for others.
chefp said:
Reverting to stock 7.1.1 (N6F27M, Oct 2017) restores IMEI and SIM card detection. This confirms that it's a firmware issue, not hardware.
From there I ran fastboot -w, re-installed bootloader, radio and LineageOS 16. The SIM card was still not detected, and no IMEI was shown.
Reverted to factory image again and IMEI was recognized. This time I installed LineageOS 16 only (wiped system, data, dalvik, cache of course). I did not update the bootloader or radio. Finally success! IMEI and SIM are recognized.
This happened on 2 Nexus 6 devices. Other people have also reported this, so it can't be a device-specific issue. I recommend mentioning this in the OP to help save a lot of headache for others.
Click to expand...
Click to collapse
if you have the latest firmware you dont need to flash bootloader and radio again just clean flach lineage os 16 ( clean flash )
AmirHRC said:
if you have the latest firmware you dont need to flash bootloader and radio again just clean flach lineage os 16 ( clean flash )
Click to expand...
Click to collapse
Understood, and I was able to confirm that's the only way to upgrade to LineageOS 16 and have the SIM card operational.
The issue stems from upgrading older firmwares to Lineage 16. My 2 phones had stock 6.0 and Lineage 14. I did not upgrade them to stock 7.1.1 because the instructions implied that I could flash the bootloader and radio separately, and go straight to Lineage 16.
Seeing a new update for the Verizon Note 9. It is saying update 13. Tried searching for a log and to see why it's about. All it's saying is for security. Any ideas?
Version number? Patch date? C'mon give us some info
Got it yesterday. It's a security update. Haven't seen anything new on my phone, and performance hasn't changed.
CSI3 for VZW and CSI5 for SPR but it's only october security patch ,nothing new