October 6th, 2011, 02:03 PM
Join Date: Dec 2010
Location: North Florida
Device(s): Motorola Droid Razr Maxx
Carrier: Not Provided
Thanked 33 Times in 29 Posts
With the one click rooting tools, there is little risk of bricking your phone. The problem is what you do afterwards. Most Android phones have a recovery program that if you screw your phone up you just reboot into recovery and fix it. Actually, you would need to download and install a custom recovery to be able to restore a phone during a crisis.
An example would be to install Clockwork recovery. Then you can manipulate your phones operating system, having always saved a "Nandroid" beforehand. If what you did had a bad outcome you would simply reboot into recovery and restore your nandroid. This gets done everyday by who knows how many people.
The problem with the Commando is two things:
1. There is no key combination known that allows the owner to boot into recovery from the off state. If you are stuck in a bootloop you can briefly control the phone with adb, and tell it "adb reboot recovery" and it will reboot into recovery. So what...
2. Once in recovery there are no known keys or buttons that will actually do anything. That's why I said so what. You can get the phone into recovery but you can't do anything with it.
There are no custom recoveries developed for this phone, and there probably won't be. Well, maybe one, GNM developed one but it probably won't be released because of #2 above. There is no reason for a developer to really spend time doing one because the bootloader controls what the buttons do in recovery, and there is no way to manipulate the bootloader.
So basically if you root your phone and then decide to, I don't know, replace the libaudioflinger.so with one from another phone, or freeze a settings app and your phone chokes on it then you are pretty much out of luck.