[Motorola Droid RAZR] Ohmster:
Sad to see you go, Scott

Oh Scott, if this Turbo is the only Android device you have, I am going to miss you with your smart quips and helpful attitude. I was "On the Turbo Bandwagon" myself, what with all the hype and this "incredible Verizon deal on the table". But, you know, something about all of this "Didn't feel right". It is all happening way too fast. Grab this phone, NOW, or miss out on the deal of the century. And the Turbo is quickly rising to the Top Ten Phones list awful fast. I had to do some research and stop letting emotions direct my actions.

There are several members here with Edge plans and really have no choice but to take this upgrade. The phones they have are old and either broken, or are outdated and crappy. This is the only affordable update they have and they must take it. For these members, they really have no choice. And the Turbo is clearly a better phone. But now they have to play by Verizon rules. :crying:

But, my research into the XDA Turbo forums quickly focused on rooting the device. Everyone is biting their nails, waiting for this "root that is possibly right around the corner". Without root, there will be no more ad blocking, no more romming, no way to remove bloat and ad ware, and no more "free WiFi Hotspot". That is a LOT to give up and any XDA member would never give it up, willingly.

As my root post indicates, there are "Root Friendly" devices and those that are NOT "Root Friendly". The root friendly devices are supported by the manufacturer. The more devices they sell, the more money they make. And rootable devices are an easy sell. But Verizon and it's manufacturers have particular issues with rooting and romming the devices for the reasons listed above. Almost all of the Droid roots I have used took advantage of an exploitable portion of the filesystem or OS. Once found by someone like Dan Rosenberg, he could then create a rooting script to run on the device. But that is no easy task and it could take a developer or coder

years

to find an exploit in a device, if any exists. And Motorola/VZW is taking severe steps to make sure that does not happen. The boot loader is locked and cannot be unlocked unless the gating diode for it is blown open. And since the OS and file system are so perfectly locked down, getting that diode to blow is nearly impossible. No way to gain root, but once you have it, your future is wide open.

No doubt there will be a lot of attention focused on this new phone and finding an exploit, and I do hope that I am wrong and that it happens for the dear members in here that have taken the updated phone. But all the research I have done does not indicate it. I hope I am wrong, Scott.

---------- Post added at 07:24 PM ---------- Previous post was at 07:21 PM ----------

Tom, the fact that every update does not fix anything and possibly makes it worse reveals that you have a very serious issue, buried deep in the system, somewhere. Go back and read the EDIT on the post you are replying to. You might find some answers in that Edit. :fingers-crossed:

The backup to Safe Strap, delete/recreate rom slot, flash cm11 and pa-gapps should all take about an hour or so. You will know when you finish the Setup Wizard if there is still a problem. Go to the play store, turn off automatic updates as suggested in the Meneldur post, and install some things. If you do not get "run out of memory" messages, you are good to go. Back it up in Safe Strap often as you follow the steps given in the Meneldur post so that if/when something goes South, you can restore a backup from before that issue occurred.

Altogether this is not going to take all night. You will know in just over an hour if you are on the right track or not. If you do not like it or have issues, you can of course restore the Safe Strap backup you made just prior to destroying the rom slot. If you are not ready to take such action, save or print this post for when you are finally fed up enough to try the next step.

Meneldur Don't MicroManage the Phone!

If this going completely clean and testing does not work, we can pretty much rule out system corruption and start looking at the phone hardware. Good luck Tom. :)

-Paul