What to do once 2.2 is officially released?

[hookbill]

Yeah I'm not 100% sure what blocks the OTA. I've heard SPR will block it and I've heard the ROM can block it. Somebody smart will have to educate us on that. But I do know if you allow the OTA it will get rid of SPR... but I guess that depends on whether out not it's SPR that blocks the OTA or the ROM... So maybe I didn't answer anything at all...lol.

Sent from my Droid using Tapatalk

Well, that made everything very vague.

But thanks for "contributing" to the thread.

 

[jntdroid]

Yeah sorry about that...it made perfect sense in my head the first time I thought it through...

Sent from my Droid using Tapatalk

 

[RW-1]

No problem Hook ...

I believe we who have SPR will not have that update ran automatically, because one has to manually allow the update install, so it will fail.

Because the froyo's we are on don't modify otacert, we'll possibly receive notification, which I believe is dependant on whether or not our phones respond to the query (they may say they have 2.2 and the update doesn't occur).

 

[jntdroid]

So then it could be similar to 2.1? Where you would be notified on a regular basis, but it never happened?

Sent from my Droid using Tapatalk

 

[hookbill]

No problem Hook ...

I believe we who have SPR will not have that update ran automatically, because one has to manually allow the update install, so it will fail.

Because the froyo's we are on don't modify otacert, we'll possibly receive notification, which I believe is dependant on whether or not our phones respond to the query (they may say they have 2.2 and the update doesn't occur).

I don't think it will run automatically. My main concern is how do I get it to stop bugging me. I know there was a way to do it with 2.1. I guess I'll cross that bridge when I get to it.

 

[rkeller62]

Well, how in the heck can you have an OTA stock ROM and be rooted? I don't see it as being possible.

I fully believe this version going OTA will be the exact same onee that we already have. Once they change it, even a little bit it should change the version number.

And if it isn't, it's close enough for me.

I guess it would me more accurate to call it 'almost stock.' All you need to change is the recovery by loading sprecovery via sbf file. Then you can use adb to push su and superuser.apk. voila, aa rooted, mostly stock ROM.

As for the 2.2 version - it sounds like the release version includes things the leaked frg01 rom did not. Namely support for exchange security profiles, longer unlock passcodes and remote device wipe. I agree that the version number should have changed and maybe it did. Wouldn't be the first time the people that update the website used an outdated version number.

 

[RW-1]

"I guess it would me more accurate to call it 'almost stock.' All you need to change is the recovery by loading sprecovery via sbf file. Then you can use adb to push su and superuser.apk. voila, aa rooted, mostly stock ROM."

That is what I want ... So it may be worthwhile for me to go back, and at the very least, if I don't like the result, I can reload my current loadout.

 

[hookbill]

Well, how in the heck can you have an OTA stock ROM and be rooted? I don't see it as being possible.

I fully believe this version going OTA will be the exact same onee that we already have. Once they change it, even a little bit it should change the version number.

And if it isn't, it's close enough for me.

I guess it would me more accurate to call it 'almost stock.' All you need to change is the recovery by loading sprecovery via sbf file. Then you can use adb to push su and superuser.apk. voila, aa rooted, mostly stock ROM.

As for the 2.2 version - it sounds like the release version includes things the leaked frg01 rom did not. Namely support for exchange security profiles, longer unlock passcodes and remote device wipe. I agree that the version number should have changed and maybe it did. Wouldn't be the first time the people that update the website used an outdated version number.

They should change the device number, this still isn't enough to make me want to remove root. I wouldn't be able to overclock and I'd lose many apps.

 

[hookbill]

"I guess it would me more accurate to call it 'almost stock.' All you need to change is the recovery by loading sprecovery via sbf file. Then you can use adb to push su and superuser.apk. voila, aa rooted, mostly stock ROM."

That is what I want ... So it may be worthwhile for me to go back, and at the very least, if I don't like the result, I can reload my current loadout.

You lost me there. adb?? I know how to use SPRecovery, I could see maybe taking the update file and loading it that way? Unzip it and just grab the three files out of the folder and put it in your Nandroid file.

I mean wouldn't that work?

 

[RW-1]

Yes Hook, you could do it via an update.zip.

ADB is the part of the Android SDK, and can also load the files directly.

 

[hookbill]

Yes Hook, you could do it via an update.zip.

ADB is the part of the Android SDK, and can also load the files directly.

So just load it to the SD card without unzipping and use SPRecovery to install?

Or unzip as I mentioned, put the files in one folder and do a restore from Nandroid?

 

[RW-1]

No, using ADB you actually mount the droid system directory and place the files (pushing) where needed while it's conneced to your computer.

 

[ChugIt]

I'm a little worried about this thing pestering me every 30 minutes. I hope a work-around actually works if we need it.

 

[RW-1]

Here's what will happen, we'll be updating to a new ROM based upon the OTA release if nothing else. But I'm not worried about it nagging, likely not going to happen, I've never received any of them ...

 

[hookbill]

No, using ADB you actually mount the droid system directory and place the files (pushing) where needed while it's conneced to your computer.

Again, and I've said this before I still don't know what ADB is. Is it for a PC because I use a Mac. Or is this on my Droid already.

Color me