• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Hacking the Droid X

So Being involved in xbox 360 community I was apart of the group of hackers who broke one of Microsoft's highly secured signatures, and continued to stay up with them. So now that I see Motorola/Verizon want to limit root access to the droid it brings me back to day everyone panic about the 360.
So useing the skills that I have picked up from that experience I would like to apply them to the Droid X problem.

When a company encrypts a rom its denying access to you unless you have the correct key. the xbox 360 had no cracks in this encryption so we had to work with what we had at the time. the only way we could gain access was to use the extensions that the rom would allow us to use. for the xbox 360 it was .xex. we would take our software and mimic it with the .xex extension so when the device read it, it would allow it.

so the droid extension is .nbh if i'm not mistaking (I dont have my droid x yet) what we could do is a make a similar firmware to attach to the rom and make our favorite droid hacks look like friendly software that anyone could just download.

A new firmware would not be that difficult to mimic it would be the flashing it to the rom that makes me scratch my head.

I've convinced myself that simply connecting my droid x phone to my pc and gaining access to the encryption "gate" so to say just might be enough to flash it with. the other option is taking the phone apart (which to my understanding is not too difficult, just requires a t-5 screwdriver) and physically flashing it.

well its worth a try anyway, i will only have 10 day to play with this before I go to the Naval Academy Prep School, (no electronics for 3 weeks) so maybe this can be a starting block for some of you too
 
Is there a good reason they don't just let users do whatever they want with their phones?

Yes it potentially costs the manufacture more money. Let says John Smith wants to flash a custom rom and some how it bricks his phone. He takes it back to Verizon and says it doesn't power on. There isn't a way Verizon can test the phone in store to find out if it was bricked because of tampering or not so they will replace it under warranty even though it isn't their or Motorola's fault the phone is bricked.

Just an example.
 
Upvote 0
.nbh is what HTC uses IIRC, and Motorola uses .sbf. However the kind of OTA updates we get are always in a zip format. Making a .sbf isn't enough as we still need to sign it with whatever method they use. Also the OMAP uses M-Shield which is a piece of actual silicon on the SoC but I don't know if Moto is actually using it or not. You definitely seem motivated and talented so best of luck to you, just know Android is a whole other beast then the 360.
 
Upvote 0
Upvote 0
All I saw was eFuse to know this wont be easy....this is the thing JTAG helps bypass in a way. But if its similar to the 360, it has to be done while an exploit is there before the fuses get blown. eFuses can get blown with updates too.

Again, I'm basing all this off of how it works on the 360.

eFUSE - Wikipedia, the free encyclopedia

Dammit. So whoever has a phone with firmware ending with .514 has a better shot then the phones released at retail. Those come with .516 and I read there will be an OTA update to .604

Motorola DROID X MB810 (Xtreme/Shadow) Pre-Release Thread Part 3 - Information Only

Whatever the case is.....this will not be easy.....
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones