-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root How to: Go from rooted 2.2.1 to 2.3.3
- Thread starter graywulf
- Start date
4DAIVI PAI2K5
Member
Dont do it.
2.3.3. cant be rooted
2.3.3. cant be rooted
Yes, you can root 2.3.3. This was made possible just a week or so ago.
The experiences of the users on this forum who had 2.1.1 rooted indicate that you can get and apply the 2.3.3 update so long as you did not "uninstall" any of the original applications built into the phone. If you only "froze" them you can unfreeze them and do the update.
I was running 2.2.1 rooted, and just this week updated to 2.3.3 and rooted again.
Just try the update and see if it works. If it fails you lose nothing.
If you get the update......start reading in the "all things root" section.
It contains the info you need to root 2.3.3.
The experiences of the users on this forum who had 2.1.1 rooted indicate that you can get and apply the 2.3.3 update so long as you did not "uninstall" any of the original applications built into the phone. If you only "froze" them you can unfreeze them and do the update.
I was running 2.2.1 rooted, and just this week updated to 2.3.3 and rooted again.
Just try the update and see if it works. If it fails you lose nothing.
If you get the update......start reading in the "all things root" section.
It contains the info you need to root 2.3.3.
Getting your rooted 2.2.1 Commando to update is simple, really. First make yourself a sandwich and grab a cold beer, you're going to be on the phone for a while. Call 1 800 922 0204 from another phone. Once you make it through the layers of automation and actually get to a human, explain that your Commando won't take the update. They will have you do several things, including a hard reset. Eventually they will wear down and offer to send you a replacement, Certified Like-New device. Accept their offer and then decide what kind of shipping you want. They will charge you for over night and two-day shipping via FedEx, or you can opt for USPS First Class mail. Depending on how far you are from Ft. Worth, TX, USPS will be fine. It took two days for the replacement to come to Florida. While you are waiting go ahead and restore all of the carrier apps, delete the busybox from the xbin folder and then unroot the phone.
When your CLN device arrives, activate it and then follow paxchristos' guide to rooting the 2.3.3 commando. Very easy, works as described.
Oh yeah, be sure to send your old phone back or they will make you buy it at full price.
When your CLN device arrives, activate it and then follow paxchristos' guide to rooting the 2.3.3 commando. Very easy, works as described.
Oh yeah, be sure to send your old phone back or they will make you buy it at full price.
What reasons would anyone have to get the update? Seems to me that a rooted 2.2.1 works flawlessly. Aside from that you have full control of everything. Why update something that is not broken?
Wouldn't updates just take up more resources and power to run, leaving your phone with less. I am no technical wiz by any means and I am new to androids in general, but I love where my rooted phone is at. Even looking forward to when ICS comes out, I still see no need to update. I would even question this phones ability to perform well given how powerful the new OS will be. This phone was not designed for ICS.
Wouldn't updates just take up more resources and power to run, leaving your phone with less. I am no technical wiz by any means and I am new to androids in general, but I love where my rooted phone is at. Even looking forward to when ICS comes out, I still see no need to update. I would even question this phones ability to perform well given how powerful the new OS will be. This phone was not designed for ICS.
Nothing wrong with leaving it with 2.2.1.
I prefer the color schemes and Status Bar in 2.2.1 over 2.3.3 anyway.
I would probably go back if I could.
The only improvement I have seen in 2.3.3 is the Voicemail dialer now accepts changes, so you can add your password. I don't use it.....but it does work.
Having to go through that lame VVM advertisement is not worth it; a direct dial shortcut is faster and simpler.
I prefer the color schemes and Status Bar in 2.2.1 over 2.3.3 anyway.
I would probably go back if I could.
The only improvement I have seen in 2.3.3 is the Voicemail dialer now accepts changes, so you can add your password. I don't use it.....but it does work.
Having to go through that lame VVM advertisement is not worth it; a direct dial shortcut is faster and simpler.
The dark colors work for me, there is more contrast
The only reason would be if that you desire to have ICS if it is made available you won't be able to update. Your phone will probably be out of warrenty by the time it comes out and you'll be on 2.2.1 until you upgrade to something new. Of course, since past practice tends to predict future performance, there is no reason to expect a rooted, debloated Commando on 2.3.3 to accept an ICS update either. This would leave you with the same warrenty issue.
I was satisfied with 2.2.1. My reason was simple, my phone would not do something that it should have - accept a factory update. There is no logical reason to create a ROM that will not allow an update just because I've made changes to it. It would seem to me it would be in VZW's interest to allow a rooted phone to accept an update that was not rooted.
As Android matures and the developers of the offical ROMs get more savvy, it will be harder and harder to locate the exploits that allow root access. At some point nobody is going to risk a brick. I've already bricked one of these experimenting and I will not be doing that again. I will follow a proven method, but I can't afford to replace a phone again. Perhaps ICS will be the one that can be broken, who knows.
The only reason would be if that you desire to have ICS if it is made available you won't be able to update. Your phone will probably be out of warrenty by the time it comes out and you'll be on 2.2.1 until you upgrade to something new. Of course, since past practice tends to predict future performance, there is no reason to expect a rooted, debloated Commando on 2.3.3 to accept an ICS update either. This would leave you with the same warrenty issue.
I was satisfied with 2.2.1. My reason was simple, my phone would not do something that it should have - accept a factory update. There is no logical reason to create a ROM that will not allow an update just because I've made changes to it. It would seem to me it would be in VZW's interest to allow a rooted phone to accept an update that was not rooted.
As Android matures and the developers of the offical ROMs get more savvy, it will be harder and harder to locate the exploits that allow root access. At some point nobody is going to risk a brick. I've already bricked one of these experimenting and I will not be doing that again. I will follow a proven method, but I can't afford to replace a phone again. Perhaps ICS will be the one that can be broken, who knows.
I tried to run the update while rooted, recieved an error upon install: IP_Previous_Update_Failed or something along those lines.
So I unrooted and tried the update again, resulting in the same error.
So I rerooted to reinstall all the factory original apps with Titanium Backup. After the root I powered off the phone, and powered back on into a boot loop.
I have not attempted to recover the device at this point as I don't have time, but I did some searching to find out the recovery mode is more or less worthless. Stuck.
So I unrooted and tried the update again, resulting in the same error.
So I rerooted to reinstall all the factory original apps with Titanium Backup. After the root I powered off the phone, and powered back on into a boot loop.
I have not attempted to recover the device at this point as I don't have time, but I did some searching to find out the recovery mode is more or less worthless. Stuck.
Sorry --- I didn't mean to make another post, but edit my first one. Seems you can't delete posts?
I'm guessing I left data that should have been removed between un- and re-rooting, data that is now corrupting new entries, forcing the loop.
Maybe I will buy a card reader and reformat my SD card.
I'm guessing I left data that should have been removed between un- and re-rooting, data that is now corrupting new entries, forcing the loop.
Maybe I will buy a card reader and reformat my SD card.
There won't be much you can do. I would call Verizon and tell them the part about downloading the update and about the bootloop. Just don't tell them anything about the rooting, unrooting, titanium backup, uninstalling or restoring the apps.
Something along these lines:
My phone indicated there was an update, so I downloaded the update. The phone rebooted into a screen that showed a box with an arrow and a little android guy. Then it rebooted and won't boot; it just keeps looping.
Play dumb, "I don't know", "not that I know of", and "what does that mean?" are good answers to a lot of probing questions.
Something along these lines:
My phone indicated there was an update, so I downloaded the update. The phone rebooted into a screen that showed a box with an arrow and a little android guy. Then it rebooted and won't boot; it just keeps looping.
Play dumb, "I don't know", "not that I know of", and "what does that mean?" are good answers to a lot of probing questions.
I went to the local Verizon store and played dumb.
I mentioned the phone's battery died and there had been a "3.-something" update, and it wouldn't start back up.
The rep seemed content concluding that the update was interrupted in mid-sequence and therefore corrupted the OS. He didn't seem suspecting, and was a good service rep. A new phone is in the mail.
Does anyone know what step I missed between un- and re-rooting that caused the boot loop?
Thanks for the help thus far.
I mentioned the phone's battery died and there had been a "3.-something" update, and it wouldn't start back up.
The rep seemed content concluding that the update was interrupted in mid-sequence and therefore corrupted the OS. He didn't seem suspecting, and was a good service rep. A new phone is in the mail.
Does anyone know what step I missed between un- and re-rooting that caused the boot loop?
Thanks for the help thus far.
There is no telling but it is good to know that there could potentially be some issues. Now running 2.3.3 I have found that incorporating a few apps into the ROM causes some problems. Wi-Fi tether, Enhanced Email and the Fancy Widget clock force close when running as a system app. When running as a user app they work just fine. I think I need to get off & leave this thing alone before I blow it up too.