Forgot your password?
typodupeerror
Cellphones

Droid X Gets Rooted 97

Posted by Soulskill
from the root-root-root-for-the-home-team dept.
An anonymous reader writes "The Droid X forums have posted a procedure to root the new Motorola Droid X, putting to rest Andoid fans' fears that they would never gain access to the device's secrets due to a reported eFuse that would brick the phone if certain boot files were tampered with. Rooting the phone is the first step in gaining complete control over the device."
This discussion has been archived. No new comments can be posted.

Droid X Gets Rooted

Comments Filter:
  • by spleen_blender (949762) on Friday July 23, 2010 @04:14PM (#33007874)
    This is the hardware manufacturer implementing Android, not Android itself, that is causing this disgrace.
  • by EjectButton (618561) on Friday July 23, 2010 @04:30PM (#33008024)
    First of all there was never any sort of self-destruct device in the phone. The phone contains a bootloader that only loads signed roms which so far has prevented people from loading custom roms such as Cyanogen. The Motorola Milestone (european Droid) has the same issue, has been out for 8 months, and has yet to be cracked.

    It's funny that the summary for this article has the text "putting to rest Andoid fans' fears that they would never gain access to the device's secrets due to a reported eFuse that would brick the phone" and links to a Slashdot story titled "Droid X Self-Destructs If You Try To Mod". So Slashdot posts a story with a bogus headline, and then later has another story saying how fear was created when it was "reported" that the phones would be bricked. Never stopping for a second to reflect on the fact that Slashdot itself was the one doing the bad "reporting".

    While gaining root access is good news this particular exploit is one that has been around for a while and is ported from another version of Android on another phone. Not to dismiss the work that has been done here but the biggest problem for this device is and has always been the bootloader.
  • by Lifyre (960576) on Friday July 23, 2010 @04:31PM (#33008038)

    Except you don't need to root to tether an Android phone. There are many programs in the Market that will do that for you without needing root in any way.

    So your completely ignorant point is completely worthless. Good thing you're a Coward.

  • by h4rr4r (612664) on Friday July 23, 2010 @04:35PM (#33008094)

    Root is available, but not new rom images. Root is just a small first step. It will not really help in getting around the signed bootloader.

  • by assantisz (881107) on Friday July 23, 2010 @04:51PM (#33008324)
    That's exactly the problem. Getting root is simple. Getting custom "ROM"s and bootloaders on the DROID X and Milestone is an entirely different thing. The latter two are digitally signed. The Milestone has been out for quite a bit now, has been rooted, but so far custom OSs are still not running on that thing. The most promising approach at this moment is using kexec [and-developers.com]. Somebody will be able to get this all to work eventually but it is not very elegant.
  • by Lifyre (960576) on Friday July 23, 2010 @05:01PM (#33008460)

    Android the OS comes open but most of the phone makers lock down their hardware (likely due to pressure from carriers like Verizon and ATT). It has legitimate purposes such as making it hard for luzers to accidently do bad things to their phone. Rooting is pretty much the same thing as jailbreaking, I think there are some subtle differences.

    Once you've got root you can usually (not in the Droid X or Milestone's case) run custom ROMs based upon the actual Android source (AOSP) or pretty much any other hardware too. It lets you add features to the phones such as overclocking, setting up wifi tethering, and adding newer wizz bangs to older phones that the maker no longer deems worth updating.

  • by kaiser423 (828989) on Friday July 23, 2010 @05:21PM (#33008692)
    Everyone, literally everyone knew that the device was going to be rooted. That was the simple part.

    Not everyone is sure that the bootloader can be cracked. It's fully encrypted, Trusted Computing style. Some UK hackers have had a go on a similar phone and haven't made it happen. We're hoping that since the Droid X has a much broader base that the extra talent workign on it will finally break it.

    Basically, as usual, the summary was horribly wrong. Everyone thought Rooting would be simple and done within a week or two (and it was). Everyone was and still is worried about the bootloader, and how you might brick your phone or just not be able to find a weak spot. Messing with the bootloader is what could trigger the eFuse if it was enabled, but Motorola has specifically said that they have not turned it on. The only thing keeping everyone out of the bootloader is the encryption right now.
  • by andydread (758754) on Friday July 23, 2010 @05:26PM (#33008770)
    This is one of the reasons Linus kept the kernel GPL2 rather than moving to GPL3. He did not like the DRM clause and the Tivoisation clause. As far as Linus is concerned the manufacturers should be able to use DRM to block you from loading an OS they do not want you to load http://www.linux.com/archive/articles/51826 [linux.com]
  • by notknown86 (1190215) on Friday July 23, 2010 @07:27PM (#33009942)
    In relation to the Motorola Milestone, which shares the locked bootloader with the Droid X.

    Motorola are now "deciding" whether to push out Android 2.2 (with, you know, the Flash support *promised on the box*) to the device at all

    For me - I've "decided" that they aren't getting more of my business - as far as I am concerned, they can go f*** themselves.

    From James King, Motorola Marketing Director:

    Next European Milestone and 2.2 (Froyo). I have expressed over the last few days that the decision is pending. The team here has been collating key pieces of information and views from this community in the last month and providing input to relevant teams in Motorola so they are aware. I am pushing for that decision to be made as quickly as possible, and we can then all go from there. Some others ask why the decisions on upgrades take so long, and why does implementation then take much longer still. What I can say and have stated recently is that upgrades are not a walk in the park. Sure there are short cuts that people can take, but when you have to integrate software to a specific hardware, then test it and integrate with third party applications, let alone any innovation from ourselves, plus then get approvals to make this all official and safe its is a big undertaking that requires planning and resource and third party coordination to see this all through. As I say, once we have decision, we will inform. JK

The difficult we do today; the impossible takes a little longer.

Working...