Honestly, I'd prefer that wasn't the case. I figure if someone knows how to flash a rom, they should know taking an ota will remove root and also know how to reroot. Just my take.
Mr.B, you're more then free to edit the build.prop file inside of the recovery module. Bear in mind thou, that each new build, you'd have to update the build.prop with the new number to get the next update. This is why the install-recovery.sh script exists when an update gets flashed. It's to make sure the recovery files get updated as well and report back the correct info to the update do the asset check. For example, here is what the V4 to V5 update looks for:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Verizon/lge_iproj/VS920:2.3.5/GRJ90/VS920ZV4.4797A970:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Verizon/lge_iproj/VS920:2.3.6/GRK39F/VS920ZV5.47B73CE9:user/release-keys");
assert(getprop("ro.product.device") == "VS920" ||
getprop("ro.build.product") == "VS920");
Now you mention that you don't mind root being gone, but you also have to take into consideration that because install-recovery.sh ran, you also have lost CWM recovery, so if anything went wrong in the update (like you had a system file frozen that is now required to run) you are stuck with a semi-bricked phone. I realize that we have ways around this, but that is even more headaches that I would rather not deal it.
Upvote
0