Bummer: Full 2.3.5/1.3.418 root is broken

[Jason.DROID]

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.

 

[themib]

and I'm sure, SBFing back, will brick

Sent from my DROID X2 using DroidForums

 

[Jason.DROID]

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.

 

[Jason.DROID]

Here's the information from RSD:

Technology: CDMA 1X-EVDO
Software Version: 4.5.1A-DTN-200-18
Flex Version: XSAMB87001VRZNA01D.0R
Bootloader Version: 0007
DRM Version: N/A

I have all of the SBFs up to the initial release. The bootloader version is the same as my old circuit board and 2.3.4. The Milestone X2 had 0010 or something like that.

I'm curious to see if it'll flash back to DTN-150-30 (2.3.4).

... so far so good.

SUCCESS!! Yes!

I've also edited the build.prop so that it won't pull the OTA update.

 

[themib]

so you used 2.3.4/ 1.3.338 SBF


Sent from my DROID X2 using DroidForums

 

[tjoh311]

@JASON.Droid
Was this after the 2.3.5 update?

Sent from my DROID X2 using DroidForums

 

[Jason.DROID]

@JASON.Droid
Was this after the 2.3.5 update?

Sent from my DROID X2 using DroidForums

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.

# Build Properties
#
ro.build.id=4.5.1A-DTN-200-18
ro.build.display.id=4.5.1A-DTN-200-18
ro.build.version.incremental=0
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Tue Aug 23 21:45:08 CDT 2011*
ro.build.date.utc=1314153908*
ro.build.type=user
ro.build.user=hudsoncm
ro.build.host=il93lnxdroid52
ro.build.tags=release-keys
ro.product.manufacturer=Motorola
ro.product.model=DROID X2
ro.product.brand=Motorola
ro.product.name=daytona
ro.product.device=daytona
ro.product.board=daytona
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=daytona-user 2.3.5 4.5.1A-DTN-200-18 0 release-keys
ro.build.fingerprint=verizon/daytona/daytona:2.3.5/4.5.1A-DTN-200-18/0:user/release-keys
ro.build.version.full=Blur_Version.1.3.418.MB870.Verizon.en.US
# end build properties

* 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.

 

[Jason.DROID]

 

[Jason.DROID]

It was:

hudsoncm@il93lnxdroid80, IIRC

 

[Jason.DROID]

" Kernel version: 2.6.32.9-00008-gc406305 hudsoncm@il93lnxdroid80, IIRC " Just like that?

IIRC = If I Remember Correctly

Kernel version:
2.6.32.9-00008-gc406305
hudsoncm@il93lnxdroid80

Is how it's displayed.

 

[ConcreteB]

so has anyone else sbf'd a 2.3.5 v1.3.418 droidx2? I'm looking for more confirmation before I do mine.

 

[Jason.DROID]

so has anyone else sbf'd a 2.3.5 v1.3.418 droidx2? I'm looking for more confirmation before I do mine.

You won't find many as the update hasn't been released yet.
However, I am now back on it and rooted.

I kept root via Voodoo OTA.

 

[BladeMaverick]

Just got my replacement phone from Verizon pre-built with the 418 OS. Honestly I thought I wouldn't be able to root, but I managed to SBF back to 2.3.4 using the DTN-150. Oddly enough it didn't factory-reset the phone like it normally does, and I was stuck in Roaming Mode until I did that myself. After the reset, re-activated my phone without issues, my previously 2.3.5 - 418 OS now back to 2.3.4 380. Everything seems to be working fine now.

With one exception, how did you update back to 2.3.5 418? I'm checking System Updates and keeps saying my phone is up to date. And I mean 418. xD

Above : Finished Product

 

[themib]

You won't find many as the update hasn't been released yet.
However, I am now back on it and rooted.

soak test started friday

 

[ConcreteB]

Got froggy and SBFd to 2.3.4. with the DTN-150. All looks good at first glance. I'll update here if I find problems.

PS, I never deleted the data/cache either, so my info is still in tact, which is a major bonus

Edit: Everything looks good so far. Im now rooted and working on restoring apps from SD.

I'd love more info on how to work VooDoo. After install and running the initial file, the "settings/about phone/system updates" is faded out and not available for the OTA