rubiX Focused on .340 OTA

[akiles]

I think it should work -but I'm no expert. Just in case it doesn't, keep a copy of RSD Lite and a SBF of 2.2 -just in case.
Make sure that your stock rom is, well, stock (cityid, kindle, amzn, etc). The cleanest way according to the experts is SBFing.
After the OTA you will (may??) loose root so make sure you have z4root handy on your card as well as the bootstrapper.

I think your idea should work -maybe more experienced users can confirm. I was going to do exactly that but my stock rom backup did not have cityID, so I went the hard way (it took an extra 15-20mins but it is the cleanest way)

Good luck. Post if you have questions -there are a lot of people that know their stuff here and they're willing to help.

I have a question for you,

What I want to ask is my phone was at 2.3.15 when I rooted my phone, then I did a back up of my system, then loaded Rubix on it.

So if I just did a cache wipe and data wipe and install my stock system Rom back onto my phone from my SD card would that go out after the OTA update that is out there?

And if it did that would take my to the new .340 update, then load z4root from my SD card and reroot?

Or does this not make any sense at all or am I wrong on this, I am asking because I am really new to this only had my Droid sense this October.

Again thank you all very much for your help!!!!

[sephtin]

I have a question for you,

What I want to ask is my phone was at 2.3.15 when I rooted my phone, then I did a back up of my system, then loaded Rubix on it.

So if I just did a cache wipe and data wipe and install my stock system Rom back onto my phone from my SD card would that go out after the OTA update that is out there?

And if it did that would take my to the new .340 update, then load z4root from my SD card and reroot?

Or does this not make any sense at all or am I wrong on this, I am asking because I am really new to this only had my Droid sense this October.

Again thank you all very much for your help!!!!

Sorry for not answering sooner.. I was kind of hoping to hear from someone that's tried it. I took the easy route and just did the .sbf back to clean stock, and did the OTA...

The reason I'm not sure, is because I think one of the files it checks for, is the logwrapper that gets replaced when installing koush's Droid X Bootstrapper application. If it checks that file, it will fail to install the OTA.
(Looking at the install script for the OTA update, doesn't look like it checks it, so it ***should*** work.. but .. only one way to find out!!!

Let us know! Worst case, is that you have to .sbf to a clean 2.2 build, and then you can certainly take the OTA.

GL!

[Growler48]

I have a question for you,

What I want to ask is my phone was at 2.3.15 when I rooted my phone, then I did a back up of my system, then loaded Rubix on it.

So if I just did a cache wipe and data wipe and install my stock system Rom back onto my phone from my SD card would that go out after the OTA update that is out there?

And if it did that would take my to the new .340 update, then load z4root from my SD card and reroot?

Or does this not make any sense at all or am I wrong on this, I am asking because I am really new to this only had my Droid sense this October.

Again thank you all very much for your help!!!!

Sorry for not answering sooner.. I was kind of hoping to hear from someone that's tried it. I took the easy route and just did the .sbf back to clean stock, and did the OTA...

The reason I'm not sure, is because I think one of the files it checks for, is the logwrapper that gets replaced when installing koush's Droid X Bootstrapper application. If it checks that file, it will fail to install the OTA.
(Looking at the install script for the OTA update, doesn't look like it checks it, so it ***should*** work.. but .. only one way to find out!!!

Let us know! Worst case, is that you have to .sbf to a clean 2.2 build, and then you can certainly take the OTA.

GL!

I didn't know about the logwrapper files when I flashed back to my stock backup and un-rooted. I took the OTA and re-rooted w/Z4 w/no problems at all. My phone boots into Clockwork Recovery every time the phone reboots now and I think it has to do w/the logwrapper file. Still trying to do research on it. Just a minor, one button push inconvenience until I can figure out how to fix it.

[sephtin]

I didn't know about the logwrapper files when I flashed back to my stock backup and un-rooted. I took the OTA and re-rooted w/Z4 w/no problems at all. My phone boots into Clockwork Recovery every time the phone reboots now and I think it has to do w/the logwrapper file. Still trying to do research on it. Just a minor, one button push inconvenience until I can figure out how to fix it.

Good to know.
I've had to help others with .sbf a few times, because going back to their orig. backup didn't do the trick, and I made the assumption that it was due to logwrapper again (this WAS an issue upgrading from 2.1 to 2.2 via the OTA)....

Regarding booting into recov, try resetting ClockworkMod Recovery via this method once, it should do the trick:
Help I've lost ClockWork recovery, my phone just reboots back into android

[Zaphod-Beeblebrox]

I have a question for you,

What I want to ask is my phone was at 2.3.15 when I rooted my phone, then I did a back up of my system, then loaded Rubix on it.

So if I just did a cache wipe and data wipe and install my stock system Rom back onto my phone from my SD card would that go out after the OTA update that is out there?

And if it did that would take my to the new .340 update, then load z4root from my SD card and reroot?

Or does this not make any sense at all or am I wrong on this, I am asking because I am really new to this only had my Droid sense this October.

Again thank you all very much for your help!!!!

Sorry for not answering sooner.. I was kind of hoping to hear from someone that's tried it. I took the easy route and just did the .sbf back to clean stock, and did the OTA...

The reason I'm not sure, is because I think one of the files it checks for, is the logwrapper that gets replaced when installing koush's Droid X Bootstrapper application. If it checks that file, it will fail to install the OTA.
(Looking at the install script for the OTA update, doesn't look like it checks it, so it ***should*** work.. but .. only one way to find out!!!

Let us know! Worst case, is that you have to .sbf to a clean 2.2 build, and then you can certainly take the OTA.

GL!

I didn't know about the logwrapper files when I flashed back to my stock backup and un-rooted. I took the OTA and re-rooted w/Z4 w/no problems at all. My phone boots into Clockwork Recovery every time the phone reboots now and I think it has to do w/the logwrapper file. Still trying to do research on it. Just a minor, one button push inconvenience until I can figure out how to fix it.

most of what you need can be found here:
My Brain Hurts: Droid X Recovery (and Droid 2 too!)

In particular, you may want to check the permissions on /data/.recovery_mode and/or delete the file.

That file is a "flag' to the logwrapper. If it exists, it boots into recovery. If it doesn't, it continues normal boot. The file itself is empty.

[Growler48]

I didn't know about the logwrapper files when I flashed back to my stock backup and un-rooted. I took the OTA and re-rooted w/Z4 w/no problems at all. My phone boots into Clockwork Recovery every time the phone reboots now and I think it has to do w/the logwrapper file. Still trying to do research on it. Just a minor, one button push inconvenience until I can figure out how to fix it.

Good to know.
I've had to help others with .sbf a few times, because going back to their orig. backup didn't do the trick, and I made the assumption that it was due to logwrapper again (this WAS an issue upgrading from 2.1 to 2.2 via the OTA)....

Regarding booting into recov, try resetting ClockworkMod Recovery via this method once, it should do the trick:
Help I've lost ClockWork recovery, my phone just reboots back into android

Problem solved! Although the problem I had wasn't particularly addressed in your post, I followed the same instructions and now my phone reboots perfectly without entering Bootstrap Recovery every time. In my case, resetting didn't do the job. Nor did clearing cache, data and force stop. I uninstalled both Boostrapper and ROM Manager at the same time and it worked. I don't know if one or the other would've fixed the problem by themselves. Thanks!