[Droid X General] ridnout:
Have found SBF, but am getting "Critical Errors 1337 & 510B"

The tale...

* Had Milestone X rooted using one of several methods readily available for download.

** Overzealously updated using the OTA about two weeks ago from Motorola without removing Superuser or Busybox.

*** Messed up and tried to flash using a verizon sbf to return phone. (Didn't brick it, but it would stop at the boot loader with errors waiting for a reflash from usb.

**** Got a warranty return!

*****Tried different methods to no avail!

************************************************************

Thought because of the info in this URL that I'd screwed up in returning my phone or trying to flash in the first place (just needed to use the adb interface to uninstall, remove, the files from their locations) and reinstall-->

WARNING for Droid X: Previously rooted DX owners who took an OTA update and then lost root should proceed with caution. This seems to only work flawlessly on SBF'd DX's or fully factory stock ones(read: never been rooted). The problem is with getting Superuser installed because it is already on your phone from when you were rooted previously.

rootzwiki.com/topic/3216-rootunroot-droid-3-root-instructions-one-click-added-for-windows-linux-osx/

Using info contained here might have worked...

psouza4.com/droid3/#droidx

If you are trying to root from the OTA Gingerbread update and you were previously rooted, you will probably experience problems with this root method because of the pre-existence of busybox and superuser.apk. For that reason, you may need to attempt both the script method (for Windows XP users) and program executable method (Windows Vista/7 users). If you are still having problems, please follow these instructions:

Open a Command Prompt in the folder where you extracted the one-click root package (see instructions for rooting). If you are using Windows 7, you can just use Shift+Right-Click on the folder you extracted the package and choose to "Open a command prompt here". For other operating systems or versions of Windows, you may require some DOS experience or need to Google how to change directories.

In the command prompt, type the following command:

adb shell

If you receive any kind of error, then you may not be in the folder where you extracted ADB.exe or you may need to reboot your computer, your phone, or check the connection. You should receive an ADB prompt ending with either a # or a $.

If the line ends with a $, then run the one-click exploit for Windows XP (even if you have Windows Vista or 7) and only complete step 1.

When you have adb shell ending with a #, type the following commands:

mount -o remount,rw /dev/block/system /system

rm /system/bin/su

rm /system/xbin/su

Ignore any messages that warn you about the file not being found/missing. We're removing old copies of su/superuser which are causing this one-click root method to fail.

************************************************************

NOW TRYING TO GO BACK TO 2.2.2 Froyo! Why, so I can try to root uninstalling the Su and Busybox rooting after OTA update. Would reinstall and try later.

************************************************************

Since I've gotten a fresh phone but the 2.3.5 update applied, I'm trying to return it to 2.2.2 stock. I've tried two different SBF claiming to be the correct ones. The one that is recognized by 4.9 RSDLite can be found here-->sites.google.com/site/1kdsdroidx/home/milestone-x-sbf-files

But I get those funky errors for which I can see no end except maybe trying XP. I've placed at the root of C: and given RSDLite administrative privs.

************************************************************

The other one that I've tried is named SHADO_X6_3.2.6_SHADOW_BP_C_02.06.00R_AP_BP_Flex_21_signed_secure_cell_south_1ff_P3_USERBLD.sbf.gz

but isn't even recognized!

Forgot url.

Please Help?!

Oh yes, I may have to crank up Debian or Kubuntu (have been with Debian since Inspiron 8200 and bf2.4 ! Just have gotten spoiled by Kubuntu (apt-get from terminal though) on this same laptop. They're already installed.

Just kinda frustrated. I've done a bit of homework and gotten a bunch of bought sense. Please help me out. Maybe I just get back to 2.2.2 and wait or try to root, remove offenders, and re-root.

Thanks.