Tuesday, August 16, 2016

OTA failing. ro.build.fingerprint doesn't match /etc/build.prop

Hi Gang.. I'm stumped.

I'm running stock COS 13.1 and for ages I've been unable to get OTA updates. I tend to wait for and flash the full tar when it comes out. I'd really like to get OTA working. I used to use TWRP and be rooted, but I'd like to keep NFC Payments, so have moved back to stock.

When I run the OTA update, I get a build fingerprint error. It reports my fingerprint as containing "A0001:4.4.2/KVT49L" (obviously I've had this problem for a while!)

/system/build.prop has the correct fingerprint.
ro.build.fingerprint=oneplus/bacon/A0001:6.0.1/MHC19Q/ZNH2KAS254:user/release-keys

I've rooted again and went into adb shell to try and find where 4.4.2/KVT49L is being set. I've done a grep on all files and can't find the string (except in logs, as expected)! Anyone have an idea how it's being set?
Quote:

root@bacon:/ # find / -maxdepth 10 -type f -exec grep -l KVT49L {} \; 2>/dev/null
/storage/emulated/0/TWRP/BACKUPS/e1125860/2016-08-16--00-45-03_MHC19Q/recovery.log
/mnt/runtime/write/emulated/0/TWRP/BACKUPS/e1125860/2016-08-16--00-45-03_MHC19Q/recovery.log
/mnt/runtime/read/emulated/0/TWRP/BACKUPS/e1125860/2016-08-16--00-45-03_MHC19Q/recovery.log
/mnt/runtime/default/emulated/0/TWRP/BACKUPS/e1125860/2016-08-16--00-45-03_MHC19Q/recovery.log
/cache/recovery/last_log.4
/cache/recovery/last_log


from xda-developers http://ift.tt/2blv6zP
via IFTTT

No comments:

Post a Comment