PPCGeeks Forums HTC Arrive HTC HD2 HTC Thunderbolt HTC Touch Pro 2 HTC Evo 4G HTC Evo 3D Samsung Galaxy S II Motorola Droid X Apple iPhone Blackberry
Go Back   PPCGeeks > Android > Android Motorola Devices > Moto Droid X
Register Community Search

Notices


 
 
LinkBack Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #1 (permalink)  
Old 07-15-2010, 09:38 AM
reigndropz's Avatar
Halfway to VIP Status
Offline
Pocket PC: Evo
Carrier: Sprint
Location: VA
 
Join Date: Feb 2009
Posts: 550
Reputation: 805
reigndropz knows their stuffreigndropz knows their stuffreigndropz knows their stuffreigndropz knows their stuffreigndropz knows their stuffreigndropz knows their stuffreigndropz knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
E-Fuse - Self Destruct

Man...I don't even know if I believe this but who knows.....supposedly there is some kind of fuse inside the Droid X that will brick your phone if you try to mod it at all. Below is a copy of the article and the source. This really will stop me from going to the Droid X.....unless some of the brilliant minds here figure out how to bypass this.....which I'm sure is inevitable!


Thing that the Android platform is all about freedom and the ability to do whatever you want with your device once you’ve bought it? Think again! Motorola’s Droid X contains a feature that bricks the handset if you try to modify the bootloader.
This is pretty scary stuff, and goes counter to what the Android platform is all about:
The eFuse is coded with information that it either looks for or is passed to it from the bootloader. The bootloader is loaded with information it looks for when it begins the boot-up process. (I have seen the sbf file look for a certain bootloader when it begins so its safe to assume that this is the process).
Once the the eFuse verifies that the information it is looking for or that has been passed through to it by the bootloader is correct then the boot process continues. What type of information is written to the bootloader? So far i’ve been able to verify that the firmware information (what we call ROMS), the kernel information, and the bootloader version.
If the eFuse failes to verify this information then the eFuse receives a command to “blow the fuse” or “trip the fuse”. This results in the booting process becoming corrupted and resulting in a permanent bricking of the Phone. This FailSafe is activated anytime the bootloader is tampered with or any of the above three parts of the phone has been tampered with.
The eFuse can be repaired, but only by Motorola, so if you trip it, it’s a case of sending your handset back for repair.
Bottom line, the freedoms offered by Android go counter to the locked handsets that service providers are happy with. Based on this, the Droid X just became a no-buy for those who like to tinker with their handsets.




Source:

http://www.zdnet.com/blog/hardware/m...-destruct/8906
Reply With Quote
 

  PPCGeeks > Android > Android Motorola Devices > Moto Droid X


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


All times are GMT -4. The time now is 04:54 AM.


Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.6.0
©2012 - PPCGeeks.com