Clearly you have no idea what an eFuse is.

Ever since the custom recovery images started showing up for the DroidX, people have been declaring the eFuse as officially broken.

Well, no, it isn't, and it's not really all that likely that it ever will be. Let me explain. (You might want to grab some coffee, this could take awhile)

New sbf_flash features

(You're viewing an archived post, click here for the latest)

The sbf_flash link has been updated; the new version adds a few interesting new features.

Droid rooting and security.

When the Droid was first rooted it as done through by exploiting the update process and the update.zip files it used. It should come as no surprise that the root immediately followed the 2.0.1 OTA update, that was really the last piece of the puzzle.

Introduction to Droid hacking.

One of the more interesting topics with embedded systems is where to store the data; it's important to understand that often there is no concept of a partition table. To understand what I mean by that it helps to look at the way the Droid boots up.

sbf_flash

(You're viewing an archived post, click here for the latest)

Linux util for flashing sbf files; sbf_flash

The usage is pretty straight forward, simply connect the phone and run:

chmod +x sbf_flash
./sbf_flash filename.sbf

CDT dump