[Droid 2 General] mrcatpc:
timid note

Longtime viewer, seldom poster, forgive a noob please, I am. Hope this helps: Thanks to all of you for your courage and curiosity, I like!

@ ovelayer, here's what's happening, and I don't blame your phone or the SBF or any of that, I blame RSDLite being inflexible with flexing:

RSDLite doesn't like the SBF because it fails checksums and signature verifications, but that's anticipated, according to the thread over at RootzWiki. I have R2-D2 edition D2 and have gone through this process "succesfully" with several similar errors. RSDLite wants a whole SBF to flash but the secret here is that we're technically flashing a "whole SBF with substituted exploited CG66 SMG image" that jolts RSDLite's normal routine. I have found that the main catch here is that the device needs to successfully reboot with a "SW Update Complete" onscreen, and RSDLite can still trigger this even after it errs out. Here's how:

1) Don't panic.

2) When you see RSDLite error, you may view it, OK it, but don't close RSDLite. Click the START button in RSDLite to pretend you're going to reflash the very same SBF, without unplugging the USB cable, and RSDLite will force the update process for the previous SBF flash to close, giving the device permission to do its reboot. RSDLite will soon be waiting for the device to be available (because of the reboot making it inaccessible until bootloader mode can be reached, but meanwhile, you can pull the USB cable out if your device said "SW Update Complete," Then RSDLite can be closed without continuing another flash. Finally once you've seen a normal boot cycle on your device, then do another reboot via soft reset or shutdown/startup to allow the exploit for ADB root access to take effect. Then you're ready for rooting/bootstrap/ROMs/etc.

Don't be fooled by RSDLite throwing an error if it actually does flash the SBF despite verification/checksum problems...

Downloading the package and re-running the steps is a human loop to get stuck in, and the "scary" thing here is disregarding RSDLite's errors, disregarding the "Code Corrupt" errors on-device, tricking RSDLite into releasing the update process and thereby causing the first reboot out of bootloader mode and back into normal boot. I admit it sounds dense, and it looks fantastically wrong, but when I saw Corrupt on screen and RSDLite errors trying this a few times, and others had said, "well, just reflash the SBF or re-download the SBF and reflash it," and another poster mentioned he just clicked Start on RSDLite again instead, I saw the whole thing come together. It's messy, RSDLite is being used to sneak preloader exploit in by SBF image to allow access where other root methods attack the existing few lines of code on the device, but it seems quite effective.

Now I'm about to go register on RootzWiki just to post in that original thread that I for one would really appreciate a 622-based R2-D2 SBF more than attempting to repackage CG66 and mod the preload app area. Rooted D2 621 is great and all, but I'd love to have the R2-D2 themes, sounds, and bootanimation with root (ah, the good old days of Froyo I remember having such access), rather than replacing 622 with 621 SBF overall. My goal isn't to run a custom ROM, or substitute SBF that matches hardware for compatibility between D2 and R2-D2.

Maybe I'm the only one. YMMV. Unless I'm driving alone here. Then MMMV, right?

Oh, and by the way, I've gone back and forth since midnight using RSDLite to flash this 621, the stock 622, and my own miserable attempt to repackage 622 with 621's CG66 SMG, which resulted in, duh, 621 in effect. You SHOULD have no problem running stock SBF reflash as long as it's the proper bootloader version, regarding 621/622 not being compatible with prior SBF builds' bootloaders.

...now once upon a time when I did brick my R2-D2 because the battery was too low after I began the SBF process, then I had to make a dangerous USB battery bypass cable, hold the phone for 30+ min while RSD reflashed the phone with no battery inserted, that was precarious.