Hey everyone, I'll up front say I'm more a user than a tweaker, so right now my NC (and my wifes) work awesome. I am currently on CM7, but my wife and many folks need to use the stock ROM and until a clean way to update with autonoot and such comes out, hopefully this is useful.
Clockwork Mod won't install an OTA, but I have a feeling that it'll still download it and try to install it, and I'm afraid it will try to install it over and over as long as the file is there. So moving to CWM to avoid the OTA is out.
Renaming otacerts doesn't work, lots of accounts of that.
But in my experience, OTAs always compare the build prop to see if they need to OTA, so what I'm going to do to my NC and my wifes NC is modify the build prop to the new settings and see if that avoids the OTA.
BTW, I know Nookie Froyo, CM7 etc won't OTA, etc, so now that's out of the way....
Due to multiple reports that using Root Explorer has somehow screwed up the system requiring users to manually re-copy their old build.prop back, I suggest you DO NOT use Root Explorer to do this.
First thing is look in /media for the uploader, in case it's already downloaded. Delete it if it's there! If you're paranoid, check when you're done with the following too, just in case it snuck in while you were editing
Note you need to replace YOURBUILD with the appropriate build, Froyo or Eclair, or whatever you named the build.prop..
Now your NC should have thew new build.prop, so now reboot. When you reboot, you should get a pop-up message with a green N saying you've updated to 1.3, but you should not see any update progress dialogs or any indication there was an actual update. Hopefully this makes it not try to OTA to 1.3.0! Please report back! It worked for 1.0.1 with the 1.1.0, as well as the 1.2.0 update out there, and it should work for 1.3.0.
Clockwork Mod won't install an OTA, but I have a feeling that it'll still download it and try to install it, and I'm afraid it will try to install it over and over as long as the file is there. So moving to CWM to avoid the OTA is out.
Renaming otacerts doesn't work, lots of accounts of that.
But in my experience, OTAs always compare the build prop to see if they need to OTA, so what I'm going to do to my NC and my wifes NC is modify the build prop to the new settings and see if that avoids the OTA.
BTW, I know Nookie Froyo, CM7 etc won't OTA, etc, so now that's out of the way....
Due to multiple reports that using Root Explorer has somehow screwed up the system requiring users to manually re-copy their old build.prop back, I suggest you DO NOT use Root Explorer to do this.
First thing is look in /media for the uploader, in case it's already downloaded. Delete it if it's there! If you're paranoid, check when you're done with the following too, just in case it snuck in while you were editing
- Get the new build.prop from here:
If you're still on Eclair: http://dl.dropbox.com/u/334233/build.prop-1.3.0-eclair
If you're on Froyo: http://dl.dropbox.com/u/334233/build.prop-1.3.0-froyo
- Remount the system r/w
Code:
adb shell
su
busybox mount -o remount,rw /dev/block/mmcblk0p5 /system- Push the new build.prop to your system
Code:
adb push build.prop-1.3.0-[COLOR="Red"]YOURBUILD[/COLOR] /system/build.propNote you need to replace YOURBUILD with the appropriate build, Froyo or Eclair, or whatever you named the build.prop..
Now your NC should have thew new build.prop, so now reboot. When you reboot, you should get a pop-up message with a green N saying you've updated to 1.3, but you should not see any update progress dialogs or any indication there was an actual update. Hopefully this makes it not try to OTA to 1.3.0! Please report back! It worked for 1.0.1 with the 1.1.0, as well as the 1.2.0 update out there, and it should work for 1.3.0.
Last edited:
