D
Dark Jedi
Guest
I know my first droid It would not root or do an OTA update. When it would install and reboot to finish the installation it would just stay on the M logo screen and I would have to pull the battery to restart the phone but would revert to the old program. even factory reset would hang on the M screen. I had to get a new phone.I would agree with Dark Jedi. I don't think it was the ROM since he said his phone had not been running right for a bit after it loaded. If loading the ROM did it I would think it would have done it right away. This is not the first time someones phone died after loading or running a ROM they installed that had nothing to do with the ROM and more to do with the phone giving up under the stress of loading the new ROM. This kinda thing happened when they released 2.2 and several people's phones went belly up from loading the OTA issued by Verizon.
Like many has said Every droid is different and reacts to programs differently.
I am running the GPA12 rom with no problems.