Bummer: Full 2.3.5/1.3.418 root is broken

Had to send my X2 in for repair because it was completely messed up. Motorola switched out the main circuit boards, and also flashed it with the newest 2.3.5/1.3.418 software (NOT the dev .412, which is rootable), and now none of the root exploits work; obviously there was no way to use Voodoo since they used an SBF. I tried motofail, zergRush, and other exploits but none have achieved root.

Android version:
2.3.5

Baseband version:
N_03.13.31P

Kernel version:
2.6.32.9-00008-gc406305

So, now comes the waiting game. I know Motorola will implement this into other phones. I'm sure the ICS upgrade for the RAZR will kill root somehow too.

Yeah, I have a feeling Moto updated the bootloader to not be compatible with previous SBFs. I'm not willing to test that out though.

I tried the Milestone X2 2.3.6 root method, and while it does flash the root.img to preinstall, the system will just not allow su to be run at all. All I get is "Permission Denied" in the adb shell. Thanks for posting that though, as I didn't know about it.

So I have su in preinstall, just no way to run it. I wonder if I can do a factory data reset where it automatically mounts and reinstalls the preinstall back onto the phone, if it'd allow it to be run? Grr. Stupid Motorola.

I even hacked the Google ADB driver .inf with the X2 hardware IDs to see if it'd give me more access with the Generic Google Drivers. Nope.

My phone wasn't updated. I sent it in to Motorola for repair because my internal memory was getting I/O errors, the phone started slowing down WAY too much when installing apps (related to I/O), and the home/back buttons got swapped even after SBFing to stock, which was really weird. So, they gave me a brand new circuit board and I believe they flashed it with 2.3.5/1.3.418 as it came to me without being activated with Verizon, so it was NOT an OTA update.

I was just frustrated without root permissions, so I flashed it back to 2.3.4 and updated my build.prop to show the exact 2.3.5 build info so it wouldn't pull the OTA update or notify me of an update. The radio is definitely an older version, but I can live with that. The radio update was likely just the Wireless Alerting System (WAS) stuff.

* The OTA updater doesn't seem to read these values. The most important are the build ids, description, and fingerprint. I reorganized my build.prop. Usually the ro.build.version.full is at the very bottom of the stock Motorola build.prop.