I haven't called Asurion or filed a claim for replacement of the R2-D2 yet, going with a so-so workaround for now: installed Argotronic "Screen Lock / Disable Touch" app from GPlay Market & at least can bypass the touchscreen's berserk spontaneous automatic swipe/touch motions. (:K ...this free app allows touchscreen block & unblock at screen on/off & by shaking phone which both thankfully still operate. Still a bit twitchy, but this is an effective straitjacket I'd say. Good times!
Free app versus deductible for Asurion device replacement, 3rd party replacement device purchase? I'd say free app FTW, temporarily if nothing else! The plan will still be to upgrade R2D2 to a Droid 4 (probably a Droid 4 Maxx, Droid 5, Droid 5 R2-Q5 Edition, or whatever else gets released by the time I can afford to purchase).
Thanks all for your input. R2-D2 says "no touch!"
Hey fellow R2-D2 owners, if you haven't seen this yet, check it out. It's a new way to root our R2-D2/D2's. It requires flashing with RSD Lite, but it is working for me (just installed Liquid ICS 1.5).
New root method for stock 2.3.4 (621/622) found (Droid2, R2D2) - Droid 2 / R2D2 / Milestone 2 / Droid 2 Global - RootzWiki
BTW, @ nineteen43: I see nobody welcomed you here to the forum (my bad not scrolling back a few pages, sorry), but did anyone reply or PM you a possible fix for the "R2-D2 acting stupid?" touch screen touching itself problem?
:icon_ poke: :welcome: (belated)
My R2's brain needs a good washing anyway, I've even considered performing a lobotomy on it, just have to figure out where to drill the hole.
Where I am at this point in retraining R2-D2 about good manners: I have reflashed the original 622 SBF and will soon use that same SBF image to run the 622 root steps recently released (you got that memo, right?). Since the reflash I did so far, erradic behavior is lessened, sometimes. I suspect the following based on continued observation:
- overheated components from sun exposure, outdoor temps, extensive time powered on in car dock and home dock, and the occasional FoxFi tethering session. Evident also in the keyboard replacement overlay beginning to bubble up from battery temps and the pink ELF layer underneath the keys. Oh, and the phone's hot to touch.
- certain regions of the touch screen are absolutely and consistently dead to touch sensitivity.
So I guess my big complaint is that my R2-D2 themed Motorola Droid 2 is actually becoming more and more like the actual R2-D2 character! I totally did not see this coming. :icon_eek:
- after installing the touch screen blocker app, I can shake the screen and toggle touch feature on/off, but when touch screen is active, SOMETIMES the screen behaves *normally.* WHAT?? Other times it begins transmitting text messages that would indicate to any random contact that I must be having a ceizure or stroke. You tell, 'em Sparky/Lassie/Sassy, good boy!
- The screen map, grid, programmed coordinates, nervous system, whatever you call it within the software that pays attention to specific regions of the screen, seems to shift (it has a selective memory or attention span, if I were to ascribe a real personality to this service droid). When I rotate the screen orientation, physical areas of the screen sometimes regain sensitivity touch. So I wonder if the software is having trouble measuring/calculating touch input activity. But again, no stock method to recalibrate via software controls.
Gullible am I.
The dark side is smelling me...
I'm weighing options of installing replacement parts, filing Asurion replacement claim for $99 deductible, or purchasing a replacement device (hello eBay). I'll post what happens following root, but I don't expect it to solve the problem, just to say that the root for 622 was a success for those who want to know the result in my unique (or not) situation.
Thanks to all for pointing toward root compatibility for R2-D2 since VZW's 2.3.4/622 OTA update.
I successfully ran the steps (including anticipated SBF errors in RSDLite already known to be "normal"), and loaded the fixed 621 SBF over my stock 622 SBF, and achieved root using the simple batch file from the Windows instructions. But I'm not totally done yet. Yes, the modified CodeGroup66 (x_CG66.SMG image within the fixed 621 SBF) *does* allow exploit and easy root with full SU installation through the batch file (or your preferred root method) after RSDLite is done pushing the SBF to R2-D2. However, the result is Droid 2 stock rooted GUI, not R2-D2... Fully compatible with the hardware but missing the StarWars ESB theme goodies.
To review: 622 = R2-D2 on 2.3.4, and 621 = D2 on 2.3.4 ...I'm sure you already knew that...
And since I'm going there already: SBF = Moto's "super file" from which RSDLite withdraws SMG image files to flash.
My goal here: rooted 622 "stock" repackaged R2-D2 SBF, not 621 pseudo-D2, not custom ROM. Although, if rooted 622 SBF is possible, then custom ROM for those who want it would also be possible after rooting, I assume.
So I am foolishly digging into the 621 and 622 SMG files using pointers from existing threads at XDA forum and the RootzWiki forum. I have successfully reflashed the original stock 622 SBF without bricking the R2-D2, and I've used SBFCodec to inject the 621 fixed CG66 SMG into a copy of the stock VZW 622 SBF and save as a modified SBF with otherwise all-622-based SMG components in the package. RSDLite flashed the whole mess to R2-D2 (again, verification/signature errors anticipated) and therefore this is all I think I know so far: the fixed/exploited CG66 as isolated is strictly vanilla 621 Droid 2 GUI (app shortcut to "The Best of R2-D2" movie is the only StarWars reference left behind, but it's a broken app link). Process of elimination tells me 622 stock CG66 contains the R2-D2ness since it's the only 621 SMG I dropped into the stock 622 SBF package.
Should note, since it was a prior question: this SBF process is NOT clearing any of my sms history, call history, wallpaper/home shortcut/widget preferences, or anything else personally added to the R2-D2 after RSDLite completes, and I have not performed a factory reset while flashing back & forth with these SBFs.
IF I successfully get the repackaged 622 SBF with root exploit into a working file to share, I may have to ask someone here to host it, but I will definitely share when it becomes a reality. Admittedly I'm no hax0r, so continued pointers and leniency welcomed. I'm digging deep into XDA etc to see how much trouble I can get myself into here. After all, stock 622 SBF or fixed 621 SBF are ready to save me anytime, and this artoo unit's hardware is on life support and due for replacement no matter what happens. Not quite Office Space pinata fax machine beatdown time, but close.
(not mine, below, just sayin')...
PS. I am aware this could all go into the Hacks thread instead, but it's R2-specific and not really of interest AFAIK to non-R2 owners. Are we 127.0.0.1 yet?
NEWS possibly not so new, but NEWS!
Thanks to beh/bhigham sharing the EzSBF+Root bootable ISO & encouraging me to try it out, as of right now I have root on R2-D2 A957 Android 2.3.4 stock Verizon 622 SBF. SWEET!
You have option doing as I did (at your own risk blah blah) running RSDLite 622 SBF approved/signed stock reflash, then booting with the EzSBF Linux boot on CD-R following just the root steps.
If you can get the full 622 SBF & Root ISO bhigham made & published for download today, you can beat me to the race for 1st guineapig brave soul to attempt a streamlined SBF & root from that single bootable disc. I am unable to grab the rapidshare link for it at present (mediafire ISO for "root-only" worked well enough today).
Please thank phifc and beh at http://rootzwiki.com/topic/29930-new...d-droid2-r2d2/ for their fine work on this project.
If I get the full 622SBF+root ISO pulled down anytime soon & run it, I'll post the results here, naturally.
ALSO: In the process of using SBFs for 621(fixed) & 622(stock) on my R2-D2, I have not had to erase my data at all, but VZW reactivation was needed upon reflashing 622 stock SBF. The EzSBF will walk you through bootloader menus using vol/pwr buttons to clear the cache, but my data remained fully undisturbed. I don't know if that would be the case if I didn't already have the 622OTA/SBF installed, so perhaps a note of caution for those who possibly avoided or bypassed the VZW OTA 622 updates until now.
Now to dig into FileExpert on root & rename the spunkyattitude.ogg so bootanimation can't scream anymore. Everything else R2-D2ish I rather enjoy. (:K
MrCatPC, thanks for mentioning that.
I will add one more note here, you should be able to use either CD to simply root the phone, without losing your data.
Of course, any time you do anything, there is the chance of something going wrong, so no guarantees, but at least one member on Rootzwiki confirmed that they were able to root without losing data. They also mentioned that when cache was wiped, that the phone was slow booting up the first time, and a bit unresponsive for a few minutes while it rebuilt the cache, but that it was normal afterwards, with no loss of data. This was on the Droid 2 Global, but the exact same method is used here, so I wouldn't anticipate any difference.
Also, if anyone wants to upload the CD images to another site, they are welcome to. My internet isn't very high speed, so I try not to upload too much, but if anyone uploads one of the images, just let me know the link and I will add the mirror.
bhigham, Success! Thank you for making the EzSBF tool to burn ISO for A957/622SBF/Root. It worked MUCH more smoothly for me than previously using RSDLite to reapply the stock 622SBF for my R2-D2. I used the bootable CD's menu to follow the steps, flashed the SBF, wiped cache (avoided clearing data, just clearing cache only), rebooting as prompted, and successfully rooted. Confirmed that 2nd reboot was much quicker.
I used Root Check Basic by joeykrim to verify Root, then Root Browser Lite to make a root edit:Renamed file in the path ./system/media/audio/notifications/...Rebooted and no more screaming R2-D2 at bootanimation, desc.txt bypasses the audio in its script but allows the notification sound to be used as normal under its new filename...
from Spunky_Attitude.ogg to Notification_Spunky_Attitude.ogg
In other words: "dancedroid!"
voodoo also work well to check root status