• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Regarding the OTA from FRG83D to G

mrterry

mrterry

Member
Hello all, bear with my ignorance here if I am missing something in plain sight. I have searched and couldn't find anything relevant.

I have a D1 running a rooted FRG93D, kernel 2.6.32.9-g68eeef5. No ROMs, just a stock root job that I did a couple months ago just to be able to OC, and dabble with wifi tethering.

I used one of the guides here to root (using rageagainstthecage), and it went smoothly and without incident. Really don't have any need to do anything beyond that, so I accepted (happily) that I was able to get SU and run SetCPU, and promptly forgot about it.

Early this morning, sleepless while watching movies, I looked over at my phone in the cradle and my screensaver clock was gone, replaced with what I thought was an error message- til I picked it up and saw it was notification for an OTA to FRG83G. A little googling later and I find that it's an irrelevant (to me at least) update. At the same time I realize that in my laziness after rooting, I never did any sort of backup.

My issue now is that incessant nagging the phone is doing, reminding me the update is available.

I've read that google has been patching the root exploits and that the -G OTA (as I understand it) is also patched against rooting. Now, I really want to keep my phone OC'ed, because it makes such a huge performance difference, but I also have no desire to see these update messages.

I'm kinda stuck here. I fear that if I reboot my phone it will automatically update, and that will be the end of my cpu OC, at least. If, of course, it can even update my rooted phone. As I said, it's just unlocked to give me /su; I have no custom ROMs or kernels going on.

So my questions are: Will I brick the phone if I reboot it with no outside intervention? If so, what are my options here? How may I avert disaster, and this OTA? If it makes a difference, I would like to try one of the new ROMs when it's all said and done- so is it possible to flash a ROM from the point I am now that would avoid the update? And is there some way I can find this OTA update file, which has already been downloaded to my phone, and delete it completely prior to rebooting/flashing?

I'd really appreciate some input, if any of you have some ideas on how to avoid these issues. Thanks folks.

Terry

EDIT:

OK, I went back to the rooting thread and found this http://androidforums.com/droid-all-things-root/234509-how-prevent-frg83d-ota.html#post1983591 . Got the root explorer app, and followed the steps listed in the OP, substituting of course for the current update to -G. I have not rebooted yet, however; waiting to see if someone will confirm this will work as well for the current update, or if I am barking up the wrong tree.
 
Welcome,

First off you can relax as the phone will not auto update unless you hit the install button on the screen. As to losing root I would bet my last dollar that you will if you update. It is likely that the rageagainstthecage will still work but you can't know for sure.

As for the post...when you modify the build.prop file you should also have to update more than just the G. It should also require changing the version number from 2.2.1 to 2.2.2 if that is the new number. As to if it will work I would PM kratos since he did the last one. I don't see why it wouldn't but since you can't make backups and you don't have a recovery that will allow you to install a different ROM should your phone crash I would verify that your modifications are dead on right in regard to version info and version number.

I don't know if the build.prop file is involved in the operation of the OS or not. Another way is download ROM Manager, flash clockwork mod recovery, then accept the update after verifying the flash took and the alternate recovery will block the update. Of course I would also make a backup first. Then recheck your recovery before accepting the update.

You can check it in clockwork mod by powering on the phone and holding the X key when doing so.
 
  • Like
Reactions: (G)
Sorry for the lack of clarity... running on way too little sleep the past couple of days. I did also change the version number, as Kratos posted. Only changes I made were to accommodate the differing versions.
 
Mrterry, I was in the same boat as you, not wanting to lose my root, and not looking forward to the nagging reminders, so what I decided to do was finally take the plunge and flash a new custom ROM. It was just the nudge I needed. I had a couple of issues with Cyanogenmod, and now am happy, happy with Peter's Gingerbread ROM. Just another option to consider.
 
Hello.

I strongly suggest installing ROM Manager from the market. Once you open it, install ClockworkMod Recovery. Then, use ROM Manager to make a system backup.

Once you are done backing up, make the changes to build.prop substituting the new values. (I will update that guide with the new values as well.)

As with any file found in /system, or anywhere other than /sdcard, you should always make a system backup before editing, adding, deleting, or otherwise modifying them. This includes flashing kernels, roms, themes, etc as well.

As for rebooting your phone right now, did you copy the build.prop file to your sdcard before editing it?

Kratos
 
No, I did not. I let it make the backup in /system/. However, I've gone back in and reverted the change back to original.

I then dl'ed ROM manager, flashed CWM, and rebooted, seemingly with no issues. Still rooted, still overclocked, and still with the system update nag. build.prop is copied to the sd card, both a copy of the original and the modified one marking it as 2.2.2/FRG83G.

Currently downloading CyanogenMod 6.1.2. Am I correct in assuming that Cyanogen will prevent further update nags?

Also, where will I find the update file that's already been downloaded? I'd like to delete it if possible.
 
mrterry said:
No, I did not. I let it make the backup in /system/. However, I've gone back in and reverted the change back to original.

I then dl'ed ROM manager, flashed CWM, and rebooted, seemingly with no issues. Still rooted, still overclocked, and still with the system update nag. build.prop is copied to the sd card, both a copy of the original and the modified one marking it as 2.2.2/FRG83G.

Currently downloading CyanogenMod 6.1.2. Am I correct in assuming that Cyanogen will prevent further update nags?

Also, where will I find the update file that's already been downloaded? I'd like to delete it if possible.
Click to expand...

Every custom ROM I have used has blocked the updates. In fact, most (if not all of them) remove the functions that check the servers for updates. CM, Ultimate Droid, Bugless Beast, etc will all prevent the update automatically.

However, if you are wanting to stay stock with root, you will need to edit the build.prop file. If you flash a custom ROM, you will be overwriting all the system files and will not need to delete the update. However, if you stay stock, you will need delete it. The location changes from time to time, but is usually in a temp, etc, or something like that folder.

I cannot seem to find the release keys and until I find those, I cannot give you all the info you need to edit the build.prop file. I'm still looking hard though.

Kratos
 
Man, this is an EXTREMELY good discussion. Very enlightening to those of us who are on the fringes of understanding all this stuff.

Thanks to all.
 
Everything went well. CM 6.1.2 runs smoother and faster than my stock OC'ed rom, and I am very pleased. My only reason for concern is that my contacts did not restore properly. Any non-facebook contact I had is gone from my contacts list- and I dont even have fb installed in this build. I even tried a nandroid backup, to no avail. I'm wondering where I missed something because everything else seems to be as it was beforehand. Haven't tried any games to see if the saves are still there but those are irrelevant in the grand scheme of things since I really dont game much on the phone.

edit: It appears that market is fc for some reason. Dont have time to mess with it right now though, will give an update later in the day after I have some time. For the record, I restored 2.2.1 market from TiBu because CM didn't have it. Think I must have chosen the barebones CM download.
 
Can someone post what string goes into the build.prop file this time to stop the nag? I just got my first nag screen an hour ago. I'm out of town and don't want to take a chance messing with an upgrade right now.
 
mudtoe said:
Can someone post what string goes into the build.prop file this time to stop the nag? I just got my first nag screen an hour ago. I'm out of town and don't want to take a chance messing with an upgrade right now.
Click to expand...

I have updated the guide with this info: http://androidforums.com/droid-all-...t-guide-updated-march-15-2011-9-58pm-cst.html

Here is the thread: http://androidforums.com/droid-all-things-root/298424-how-prevent-frg83g-ota-update.html#post2429622

Kratos
 
You can stay stock - I have a thread about it called "Stock rooted 2.2 Froyo". I bought my droid 1 right when it was released, and have stayed stock and rooted since the first update. You don't need to download custom roms, rom managers, or anything like that.

My guide sucks, but try the newer version on my web site. It is pretty easy once you get the hang of it - you need an older buggy version of recovery that will let you patch OTA updates with a hack that adds su, and then you can use official OTA updates every time once they get a small hack added to them (you add the hack yourself at a dos prompt on your computer).

Edit: I delete the update from /cache after manually upgrading with a hacked OTA to prevent nags. You can probably just delete it from /cache and be done with it if you don't want to upgrade.
 
mrterry said:
Well, oddly enough, I seem to have gotten lucky... I put in this rom http://androidforums.com/droid-roms...ad-android-2-3-3-build-gpa13.html#post2432106 just to see... and it is exactly what I wanted! On top of it meeting my needs perfectly, it restored all of my contacts in the process.

Quite the roundabout fashion to achieve success but I got where I wanted to be. Thanks for the help guys :)

And no update nag haha!
Click to expand...

Glad to hear you found something that works.

Kratos
 
You must log in or register to reply here.
Back
Top Bottom