Yeah, I used the .621 root tool and flashed MIUI V4 back pretty much immediately after I got the phone. So long as I don't end up with another hardware failure I should be golden until something that piques my interest comes out. Crazy how much new devices still cost even afther they're "old" technology.
@ MissionImprobable: Agreed, cost-prohibitive for replacement device & I am not keen on $99 paid to Asurion if my R2-D2 could be rehabilitated less expensively, although I have no deep bias against refurbished devices. Oddly I've been running rooted 621 for a couple days now with no further "don't look now but my screen is touching itself" specific issues, but *dead* (numb) areas of the touch screen remain. None of those regions which have lost response to touch input show any signs of magical rejuvenation so far. So I chalk the prior "possessed" behavior up to either software glitch(es) or that the hardware/electrical components have finally settled (or entirely given up on) bad/false input. I suppose long-term heat could cause certain ICs to quit & therefore be ignored by digitizer. Like the surgery that can be done to fry a nerve causing irregular heartbeat (see August 2001 general interest story "Doctors Fried My Heart," Readers Digest, p134). I don't hope to regain full touch screen functionality on this hardware.
Originally Posted by MissionImprobable
If I put in any replacement parts, I'll take pics of the hardware as I go & link back to this thread, at least as a mention of alternatives to replacing the whole device. The chrome outer frame is already here in a box, so I'd be investing in the digitizer/glass if not additional components to repair.
I'm disengaging from the What is wrong with my phone? It is possesed thread under Droid 2 Global unless I have any more relevant digitizer replacement valuable notes to share.If I replace the device entirely, I'll continue to post that on the "Official R2-D2 Owners Thread" as well as if I discover any deeper connection between the stock SBFs (621 for D2 vs 622 for R2-D2), rooting, 3rd party screen calibration app, or restoring any functionality of this current device using software methods. I'm about to reflash the stock 622 SBF to see what happens (I'll lose root again doing this until there's a fixed_622 SBF, or reflash fixed_621, or if I successfully cobble together a fixed_622_ish SBF haphazardly fumbling with the blunt instruments on hand, a la reverse-engineering, I gotz zero skillz yo).
Sidenote: RootzWiki forum still hasn't sent my profile activation message for e-mail verification, so I don't have a formal request into beh & phifc yet to build and host the 622-based ezSBF CD (to automatically flash, exploit, and root) specifically for R2-D2 A957 devices, but I intend to post a request over there as soon as possible. Thanks MissionImprobable for your encouragement at RootzWiki to continue after the RSDLite error(s), if I didn't already say thank you for that. It's true this 621 root solution is good enough if intention is to install a custom ROM or not wanting the R2-D2 Edition featureset (per what themib/sd_shadow says, I can also vouch that 621/622 SBFs are interchangeable on this hardware), but additional 622 complete solution would be great for those who want Root2-D2 (ahem, maybe I'm the only freak who does).
Anyso, when RootzWiki verifies my profile I'll give thanks over at that forum where it's due. Ditto over at XDA-Developers forum where I'll point back if the 622 is possible and I can verify it works when available. I am sure those folks have forgotten more than I'll ever hope to learn about the dark side of coding.In case other readers land here and want a live demo of what the screen can do on its own after damage/exposure/age in the context of this Motorola series of devices (Droid 2 A955, D2 Global A956, and R2-D2 Edition A957), take a peek at this other poster's video embedded on Official R2-D2 Owners Thread for great example of the paranormal activity eerily similar to behavior my own R2 was displaying.
This post is mainly to explain I didn't intend to run parallel threads as the adventure continues, and where appropriate I could start a new thread, of course, so please redirect or moderate me as needed). Thanks to all for continued interest and advice!
(I still talk too much, no hope there yet, maybe duct tape)
Quick update: pointing back to Official R2-D2 Owners Thread, beh/bhigham's EzSBF 621 Root CD did the magic for me with minimal fuss to root my A957 after stock 622 SBF reflash (beh made it even easier with a complete 622+root for A957 users, but I can't seem to download it from RapidShare for now). I'm posting back here to say the screen is still behaving without any of the previous twitchy spooky self-destruct craziness, but it will continue to have dead-to-touch areas for touch input until I replace the hardware. So I can safely say all the software gremlins are tamed, but parts is parts. Yep. Trying to save the funds to buy parts or suffer until upgrading is within my budget. Bleh!