efuse
Latest
Motorola bucks its own trend, leaves Xoom bootloader unlockable
Pretty much everything coming out of Moto these days is saddled with a tightly-locked bootloader paired with one tamper-resistant scheme or another, making custom kernels -- the lifeblood of the phone hacking community -- tricky at best, nigh impossible at worst. Of course, there was a glimmer of hope last month when the company said that it was working on a solution that'd cater to the developer community, and it looks like the Xoom might be bearing some of that fruit: the bootloader can be unlocked and relocked at will. Now, we're thinking that Moto might've loosened the reigns a bit here simply because the Xoom is running a completely bone-stock build of Android and, as Honeycomb's launch device, Google might be showing some influence behind the scenes (the Nexus One and Nexus S both have unlockable bootloaders, for instance)... but it's a good sign. [Thanks to everyone who sent this in]
Motorola ready to make sweet love to Android ROM devs and rooters?
HTC is legendary for its tacit support of the Android ROM cooking community. Motorola... not so much, thanks in large part to the company's policy of locking down the bootloader as a means to prevent unapproved software from running on its Droid handsets. An annoyance recently exacerbated by a moderator of Moto's YouTube channel who suggested that customers looking to install custom ROMs should "buy elsewhere." Ouch. The resulting public relations kerfuffle then prompted Motorola to publish a clarification to its bootloader policy on Facebook: We apologize for the feedback we provided regarding our bootloader policy. The response does not reflect the views of Motorola. We are working closely with our partners to offer a bootloader solution that will enable developers to use our devices as a development platform while still protecting our users' interests. More detailed information will follow as we get closer to availability. Obviously, we'll have wait for said details to get official before calling this a shift in strategy. It's certainly an improvement over Moto's previous approach of lawyering-up with cease and desist orders. Perhaps Motorola is taking a cue from Microsoft who seems to have recently discovered that it's better to embrace than to annoy a motivated hacking community -- customers who tend to be a company's most dedicated fans and evangelists.
Motorola says leaked Droid X Android 2.2 build won't be updated to the official release
Can't say this is a surprise, but Motorola posted a note on its support forums today warning Droid X users against upgrading to that leaked Android 2.2 build or any of those custom ROMS that're out there -- they'll be cut off from the official upgrade when it hits in early September and potentially "stuck on the leaked version." Ouch. Of course, that's the risk you take when you start flashing your phone with unofficial firmware, but between this, eFUSE, and those cease and desist letters, it certainly feels like Motorola is decidedly unhappy that anyone would have the gall to hack or tweak one of its handsets, even if the phone in question is the size of a small tank and marketed by aggressive murderous robot hands insisting that it "does" everything one can think of with no restrictions. Contrast that with HTC, which is not only at peace with the hacking community, but even takes the initiative to resolve similar problems. Of course, no one would care about any of this if Motorola would just release stock Android builds for its devices as soon as they're ready, but why learn that lesson when it's possible to waste money developing Blur and adopting painfully annoying staggered OTA rollout schedules at the behest of carriers? That would just be silly. [Thanks, Matthew]
Custom Droid X ROMs starting to break loose, eFuse be damned
Despite Motorola's best intentions to the contrary, the Droid X has been making steady progress toward viable custom ROMs, first with root access, then with a recovery method... and now, at long last, we're starting to get the first few glimpses at legit cooked firmware. The two options we're seeing so far are Sapphire -- originally designed for the Droid of old -- and a so-called "FlyX" ROM from longtime contributor Birdman. In both cases, the benefits of eschewing Motorola's standard builds are pretty obvious: you get Froyo, root, and a host of apps and capabilities preferred by the superuser crowd like surcharge-free mobile hotspot access. The process is a little involved to get these bad boys installed at this point, but with time, we're willing to bet it becomes a pretty painless endeavor. Follow the break for a quick video of Sapphire booting into stock Froyo on the X -- a tantalizing sight, indeed. [Thanks, Clift]
Motorola responds to Droid X bootloader controversy, says eFuse isn't there to break the phone
There's been a lot of chatter going around the interwebs in the past 24 hours about the Droid X's exceptionally well-locked bootloader -- a situation that is going to make running custom ROMs considerably more difficult (bordering on impossible) compared to your average HTC. Specifically, the culprit is said to be a technology known as eFuse -- developed by IBM several years ago -- which allows circuits to be physically altered at the silicon level on demand. Thing is, the term "eFuse" has taken on an unrelated meaning this week, with My Droid World claiming that some chip inside the Droid X is commanded to "blow the fuse" if it's unable to verify the stock bootloader, which permanently bricks the phone. It amounts to a really, really hard slap on the wrist for anyone trying to hack, say, Sense or stock Froyo onto it. Considering IBM's historically non-nefarious usage of the term "eFuse," we suspected something was amiss here, so we reached out to Motorola for an explanation. Read on to see what we got back.
