View Single Post
  #11 (permalink)  
Old 07-16-2010, 08:08 AM
weedahoe's Avatar
weedahoe
VIP Member
Offline
Location: GA
 
Join Date: Jun 2007
Posts: 3,250
Reputation: 1593
weedahoe is halfway to VIP status based on repweedahoe is halfway to VIP status based on repweedahoe is halfway to VIP status based on repweedahoe is halfway to VIP status based on repweedahoe is halfway to VIP status based on repweedahoe is halfway to VIP status based on repweedahoe is halfway to VIP status based on repweedahoe is halfway to VIP status based on repweedahoe is halfway to VIP status based on repweedahoe is halfway to VIP status based on repweedahoe is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via AIM to weedahoe Send a message via MSN to weedahoe Send a message via Yahoo to weedahoe
Re: E-Fuse - Self Destruct

Last time I read the story (unless i read it wrong) the eFuse was in the TI OMAP processor and not Android OS itself. That would make it hardware based and not software based which makes it a lot more hard to get around.

From the arcticle:

http://www.mobilecrunch.com/2010/07/...try-to-mod-it/

"It requires a hardware fix, apparently, only available through Motorola, of course. This is the equivalent of a MacBook detonating some core component if you try to install an OS to dual boot."

So this is why older Moto devices like the first Droid dont have this issue
__________________
Loving my rooted Droid X

Last edited by weedahoe; 07-16-2010 at 08:11 AM.
Reply With Quote