One piece off info I didn't know before from Matt.
"FB file might... the only thing is the official FXZ leak does not include webtop, so I could see that becoming an issue. I purposely removed the cdt.bin from the Droid Razr Utility 1.8/1.81.
If you used the ICS FXZ AND my 1.81 they should be on ICS 211 however."
Sent from my DROID RAZR MAXX.
This is a situation where I would again point to RSD Lite as the preferred method. Don't get me wrong, Matt's utility as said before has been a life-saver for countless hundreds, potentially thousands or more (tens of thousands, hundreds...who knows), and I am in that group as well. The only thing that concerns me about the utility is that due to various versions of the OS and Kernels, and then various versions of the Utility, there presents an opportunity for confusion which may cause someone to make the wrong choice. Each version has its own unique purposes, and each version works in some situation but not in others.
Beyond the immense care and work in research, development and testing to be sure his utility works, Matt also takes tremendous care in preparing notes for each version released which explain all the unique features and situations under which his utility will perform, but then you have to first read them thoroughly and understand them. All you have to do is read the threads each time a new one is released to see how easily inexperienced members can misinterpret the information presented. It seems no matter how detailed and how well laid out it is, and no matter how many warnings are provided regarding what NOT to do, somebody will inadvertently do something wrong and then it's a major catastrophe that everyone gets involved in trying to fix.
Given that Matt's utility is used by perhaps hundreds in the first few days immediately after release, it's virtually impossible for him to reply to or be involved in assisting each and every member from the (several? - I know of at least two) forums he is posting the utility to, and help them get back on track, yet amazingly he still does seem to manage to jump in and comment at key points when necessary. There are certain things his utility can do that can't be done with any known method using RSD Lite, such as "unstick", so his work is invaluable in that respect.
There are also many things that can be confusing about RSD Lite, both in getting it configured properly with drivers, getting the phone to be properly recognized, using the right functions, making sure that the wrong functions are not accidentally activated, (it's far more powerful than most will ever utilize, and can be dangerous if mishandled), and finding and connecting to the Fastboot file for flashing, and since many people here are not technically savvy, Matt's utility takes all that and puts it into a menu driven "rootkit", along with other useful utilities such as root, Voodoo OTA Rootkeeper, and more, so that even the technically inept can perform highly technical processes by simply hitting a number on the menu.
This is why I did the recent roll-back to .211 while on the forum in a play-by-play. I was not even sure that it would work but was willing to give it a try for my own benefit and the benefit of others.
The following is directed at no-one, but everyone:
So to reiterate, let's not stand around and point fingers so quickly at who is right or wrong, remember we've all been on both sides of that situation at times in our lives. I know we are all apprehensive and want to be sure we don't unknowingly misdirect someone, so caution is certainly warranted, however we may find that what we were absolutely sure was one way, is in fact not exactly the way we thought. We are essentially making root level changes to the phone with both Matt's utility and with RSD Lite, as well as by using ADB commands (for the truly brave), even if we're not rooted, so the potential for irreparable damage and a resulting bricked phone is always there. The key is to not proceed unless we are 100% sure we know exactly where we are first, where we want to be, and what needs to be done to get from A to B, and that we can follow instructions to the letter, and that we read, read again, and when we understand, then we read again to be 100% SURE we understand, that we NOT proceed if there is any unanswered questions, and that we can confirm through the successes of others that our planned route of attack is without landmines.
Let's continue to work as a team, and if you feel a team-member, known or unknown (as we're all in this together), may be giving advice that's potentially inaccurate, simply advise the OP or whoever is being helped to remain where they are while the confusion is worked out, then do the research yourself, as I did. Google is your friend, and although this is the best forum out there IMHO, there are other brilliant minds who are at home elsewhere (Motorola's forums, DroidRZR.com, AndroidForums.com, forums.XDA-developers.com, the list goes on and on). Glean what you can and need to either confirm what was being advised is accurate, or isolate the information that details the flaw in the advice and provide the necessary solution. And always, any advice given when doing any kind of flashing, should come with a disclaimer from you that the one whose phone is being worked on should also research to further validate the information you are giving and become very personally familiar with it before proceeding, as it is 100% their responsibility if the advice given is wrong or not followed properly and results in undesirable consequences.
if they refuse I'm going to have to just go back to my droid 3... But thanks again!!