[Motorola Droid X2] twitish:
Hey all! Long time no see! Let me clarify a few things in regards to this project and probably this phone. It's dead. Completely dead. I tried my hardest to get it all working and failed. :crying:

Problems:

Getting the ATAGs was serious work. To this day, I'm still not sure how DzK got his and unfortunately he didn't/couldn't/wouldn't (take your pick) share them even with me to try and assist in getting this working, or to check my own. I talked with a number of other developers to try and get things going for myself and to maybe even get on the same page as DzK. I had my own set of ATAGs, however I'm not sure if they are correct. I have three theories as to how he got his: A.) He created a kernel module to give him the correct ATAGs from the device(improbable, but possible), B.) He had access to, or access to someone with, a developer's version of the DX2 or MX2 (which would allow the ATAGs to be read, this was how it was done on the Razr) or C.) He edited the ATAGs pulled from the CDT.bin to create a complete set (what I did with some help from other devs). Regardless, I believe DzK had the correct ATAGs and I did not; and I believe this is where I hit my roadblock. Without these, Kexec is nothing more than a dream.

Once the ATAGs are found, you then have to play with the greatest annoyance that has ever been known to the world of Linux, binary drivers. The Tegra 2 does not have drivers for Android that are open source in earlier versions of the kernel, therefore even if you were able to get kexec working you would be stuck using the kernel from 2.3.5 and the supplied drivers (I believe that was the last one they released) without having to do some serious coding (bringing the drivers from a 2.X kernel to 3.X is not fun) and debugging. Even then, kexec does not guarantee that everything works 100%. My goal to bringing kexec to the DX2 was for a (hopeful) speed increase and better CM support, even if it meant a few less desirable features (to me at least) to not work, like HDMI out (I don't believe the Razr got HDMI out to work with kexec, so I'm taking a reference from that). This is all assuming that you have compiled a kernel that actually begins to boot and your device is hooked up to a uart cable for debugging as well.

Lastly, that leaves me with the biggest problem: the Tegra 2 chip. It is not like other ARM chips, it is picky about how it is controlled by the kernel, it was terribly supported by Nvidia, and overall a pretty bad product. I'll leave it at that before I yell at Nvidia like Linus Torvalds did. :p

Overall, kexec is not impossible on this phone. It is, however, very improbable that this will be completed without DzK's ATAGs. As for the source for kexec and everything that I used, here's a few links.

Kexec-Tools

Kexec for the Atrix (another Tegra 2 device)

kexec-hardboot patch(really good explanation)

Moto Source

I'm not going to give a tutorial on how to set things up or to get where I was. I do not have the ATAGs I used anymore, nor do I have any desire to help with attempting to get them again (sorry!). This will be the last time I post on this thread and in the DX2 forums. The DX2 was my first Android phone and it saddens me to see how it turned out due to Moto and Verizon locking it down. If a mod wants to close this thread they can. I wish you all the best of luck on getting this to work if someone decides to take the helm, and hope you all have a Merry Christmas!