What I find amazing is that there are a few reports of totally stock phones bricking with this update. Moto/Verizon have a headache on their hands as this will reach mainstream news very soon....and I couldn't be happier!!
For those who have bricked your phones, that sucks and hopefully your new phone ships with 2.1.
Stock phones are not being "bricked" they simply need to remove the battery for 1 min, reinstall and reboot and problem is solved.
Go check post #50, his dads phone was stock and was bricked after the OTA. Verizon could not fix it and I am sure they tried a battery pull. Search the forums this is not the only stock phone that had been bricked with the OTA.
What I find amazing is that there are a few reports of totally stock phones bricking with this update. Moto/Verizon have a headache on their hands as this will reach mainstream news very soon....and I couldn't be happier!!
For those who have bricked your phones, that sucks and hopefully your new phone ships with 2.1.
Stock phones are not being "bricked" they simply need to remove the battery for 1 min, reinstall and reboot and problem is solved.
Sent from my DROIDX using Tapatalk
Part of me hopes you are wrong, if Moto screwed up the update by trying to change things to lock the phone down more if serves them right. I do think that most people stuck would have tried a battery pull though. If it does work we should hear some success stories soon enough.
Sent from my DROIDX using Tapatalk
Part of me hopes you are wrong, if Moto screwed up the update by trying to change things to lock the phone down more if serves them right. I do think that most people stuck would have tried a battery pull though. If it does work we should hear some success stories soon enough.
Sent from my DROIDX using Tapatalk
They simply have some bugs that need some work. But yea they employed counter measures for those who used the leaked 2.2...
Part of me hopes you are wrong, if Moto screwed up the update by trying to change things to lock the phone down more if serves them right. I do think that most people stuck would have tried a battery pull though. If it does work we should hear some success stories soon enough.
Sent from my DROIDX using Tapatalk
They simply have some bugs that need some work. But yea they employed counter measures for those who used the leaked 2.2...
Well those bugs are causing legit users to he without phones. And no stores have stock of the droid x to replace with......nor do they have a solution to fix by reflashing. This IS NOT ACCEPTABLE
They simply have some bugs that need some work. But yea they employed counter measures for those who used the leaked 2.2...
Well those bugs are causing legit users to he without phones. And no stores have stock of the droid x to replace with......nor do they have a solution to fix by reflashing. This IS NOT ACCEPTABLE
It happens part of the problem here is the CPU is getting pretty darn hot during this UPDATE as with anything electronic if it gets too hot bad things happen. It is not Verizon Or moto's fault if the CPU was already warmer then normal when the update took place. The stores should have a very minimal supply of X on hand I agree with you on that point.
Well those bugs are causing legit users to he without phones. And no stores have stock of the droid x to replace with......nor do they have a solution to fix by reflashing. This IS NOT ACCEPTABLE
It happens part of the problem here is the CPU is getting pretty darn hot during this UPDATE as with anything electronic if it gets too hot bad things happen. It is not Verizon Or moto's fault if the CPU was already warmer then normal when the update took place. The stores should have a very minimal supply of X on hand I agree with you on that point.
Plus the stores should have the 2.2 sbf file ready so those with this issue they could just flash to 2.2. Obviously theres going to be a small amount of issues. Thats a given. Whats not acceptible is verizon being unprepared to deal with these issue, stores not being prepared in advance with 2.2, and having
the ability to reflash to 2.2 or a replacement on hand at the stores. They knew the update was going out lastnight.......
Yea Moto thought changing the keys was a good idea and now they are going to have to deal with a consumer and media backlash. I hope they get raked over the coals.
I can just imagine Moto blaming people for using their phones and they were to hot for the update. See now they would not be in this position if they just produced phones without encryption like HTC/Samsung and then trying to tighten security again. Really not smart at all on their part and I can't believe for one second that these issues never came up when they were testing the update.
Sent from my DROIDX using Tapatalk
