[ROOT][HOW TO] Win/Linux/OS X [Latest DX .602/.605]

[matjs1]

Ive been reading and learning about ROOT and SBF for the last few months. I flashed my DX from Verizon to Cricket about 2 months ago and although there wasnt really much change, the phone still has lock up issues. Also after the flash I cannot send pix messages but can receive them and do everything else a fully flashed phone can do. Anyway I followed the instructions and Pete's Motorola Root Tool worked PERFECTLY. I bought a few and downloaded some ad sponsored root only apps and am very pleased. Now im downloading some custom ROMs and just wanted to say THANKS to everyone who posts on here for all your words of insight.

[Droid-X-Forums]

[roderick5881]

here is what happened. and now it is stuck on the boot animation...

[msscull]

Not sure what this message means, besides I have root:

Root Message 02-06-12 #1.JPG

What is busybox?

Never mind, it took 2 more root attempts, 1 unroot, & then 1 more root attempt to get full root & no error messages.

[jaiden]

Good day, my apologies if this was answered but I couldn't find an explanation.

Using the Mac method (on a MacBook Pro) to root my DX, part 1 seems to work fine, but at part 2 I get this:

* Running exploit [part 2 of 3]...
failed on '/data/local.prop' - Permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
*
* Rebooting the phone... when the reboot is complete, you may need to unlock the phone to continue.
*
error: protocol fault (no status)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
! ERROR: root was not obtained.
!
! You might want to try rebooting your phone and trying again.

Any suggestion? Did I miss something? Thanks.