[Q] Plan for Bionic root/unroot for ICS, PLEASE REVIEW

---

I'm hoping to get some eyes on this plan I've made for hacking my new Droid so I can avoid bricking it at all costs.

I bricked my old Bionic 2 days ago due a combination of problems with Clockword Recovery Mod and the leaked ICS update, as well as my battery frying for some reason. Thankfully Verizon was none the wiser and they are sending me a new phone and battery in a few days. Although I'm cautious about hacking now, I still plan on rooting the new phone so I can recover my apps and data from the old phone's SD card.

Here are my plans for the new phone. If anyone could tell me if it makes sense or if they see any issues that will arise from following these steps, please let me know:

1. Root new Bionic with Motofail.exe root
2. Restore apps and such with Titanium Backup (restoring individual apps so I don't get any old clockwork garbage or other random stuff)
3. Download Voodoo Root OTA Rootkeeper.
4. Wait for official ICS OTA (don't want to mess around with the leaks anymore) and backup root with voodoo
5. Unroot with voodoo, install ICS and re-root after update (I've read on some posts that Voodoo works with the ICS OTA but I'm not 100% sure)

I'm more concerned with the OTA installing properly than keeping the root after ICS, though while it would be simpler just to not root, I really want to restore the TiBu backup from my old phone.

If anyone sees any flaws with this plan or if you think it sounds like there won't be any problems, please respond! I really don't want to brick a second phone so any help would be invaluable.

No one can say for sure if this will work since no one has the official OTA yet.

That sounds like a plan that may work. Even if OTA Root keeper fails I see a thread with a root method that is working on ICS leaks so it should

[should being the operative word here as stated this is all subjective reasoning from my time and use of Android and many different devices there is NEVER 100% certainty EVEN IF we had access to the OTA and had a method there is no accounting for any errors caused by a multitude of things [download corruption, bad blocks in memory during flash, you missing a step and borking the whole process, etc.] so no one will ever be able to say with 100% certainty that you will not have some rare issue and have a problem even with a tested method [and if someone does try to tell you something is 100% they have not dealt with technology and computers long enough to realize nothing is ever guaranteed even fully certified OTAs have caused bugs not accounted for and been stopped, recalled, or otherwise modified when users try to apply them and have issues ]

Anyways, I did read where you flashed the ICS leak via CWM recovery and everything I have been reading about flashing ICS on a Bionic involves the STOCK recovery and not CWM [most postings even SPECIFICALLY state to NOT USE CWM AND ONLY USE STOCK Recovery [but then again I read a lot] so if I had to trace the issue you had the with the limited information you have provided about your specific experience I would prolly point to that as prolly causing the problem. See the ICS with files thread here and that is again specified as part of procedure [basically format EVERYTHING restore it back to out of the box 902 then using STOCK recoveries to apply .905 then the ICS leak THEN after ICS is running they have a rooting batch file in there as well [so no worries about rooting in .902 and using OTA Rootkeeper to sustain it in .905 and on just get stock .905 unrooted to the phone then flash ICS with stock and root once it is fully completed and drivers and all on computer side are good [dont forget to enable USB Debugging [and in ICS there is an option to allow SU to apps only OR APPS AND ADB and after rooting you may need to enable the ADB side for any super user root checks if checking via ADB] but dunno if that is CM9 only option, but seems to be stock ICS setting in developer [it protects you if you use and leave enabled the ADB over the network function from others who may find your device over a network and getting SU access].

Sorry, I digress, all to say sorry to here you had the issue, but I think you may have missed something in the install process and here's how to address it, and your methodology seems sound in theory, but there is other information already available to augment your procedure and make it easier on you, my bad.

Hope all the info helps....

Here is that thread mentioned above that seems to distill what I have read on numerous boards in to one easy to download pack with instructions that has users replying that they have had great success with it: [Guide} Bionic to ICS w/Files