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

Root **Official** Droid X encrypted bootloader and efuse thread

Excellent post. Someone WILl get root. if someone else doesn't get it. then I will at some point if I have to learn the ins and outs of android and figure it out myself.
 
What are the chances someone breaks the lock-down on the HDMI-out that only lets you output "user-generated content" (i.e. only video shot by the camera, not a movie you downloaded)? That would be the main reason I would want to root the X.


Custom ROM. however it remains to be seen if it locks it down that far or if it only does the usual lock down due to standard DRM that is built into HDMI.
 
Pretty much its over for the Droid X. Plenty of places reporting with moto reps saying that they wont release unlocked phones.
 
I think all these sites posting and blogging about how the "bootloader is locked and we can't get root" is, in a way, reverse psychology. I think they know that android devs will see this as a call to arms and try that much harder to crack this thing!
 
I think all these sites posting and blogging about how the "bootloader is locked and we can't get root" is, in a way, reverse psychology. I think they know that android devs will see this as a call to arms and try that much harder to crack this thing!

I don't want to get everyone down - but everyone is way too optimistic about getting into this bootloader. Trust me - chances are slim to none. Not only did Motorola encrypt the bootloader as they did with the European Droid named the Milestone (the Milestone still has not been cracked after over 7 months), they seem to have implemented a feature developed by IBM known as eFuse. (Per P3Droid via My Droid World - a very reliable source so far with anything Motorola.) eFuse is used to completely write over the memory of the device - actually tripping the circuit eFuses and changing the hard coded memory. This can be used by manufacturers for positive outcomes, but in this case it is quite nefarious. The process can be reversed - but by Motorola of course. In this case, it is cross-referencing the kernel, bootloader, and firmware... try to get into any of these and eFuse will make sure you have a brand-new shiny paperweight to play with. That's where the real issue is. Not trying to break the encryption, but the threat of bricking your device in the process.

(I do know what I'm talking about. I have written plenty of kernels and ROMs for the original Droid and I have been following this from the beginning. This is the final straw for me - I'm done with Motorola unless they pull a 180
 
I don't want to get everyone down - but everyone is way too optimistic about getting into this bootloader. Trust me - chances are slim to none. Not only did Motorola encrypt the bootloader as they did with the European Droid named the Milestone (the Milestone still has not been cracked after over 7 months), they seem to have implemented a feature developed by IBM known as eFuse. (Per P3Droid via My Droid World - a very reliable source so far with anything Motorola.) eFuse is used to completely write over the memory of the device - actually tripping the circuit eFuses and changing the hard coded memory. This can be used by manufacturers for positive outcomes, but in this case it is quite nefarious. The process can be reversed - but by Motorola of course. In this case, it is cross-referencing the kernel, bootloader, and firmware... try to get into any of these and eFuse will make sure you have a brand-new shiny paperweight to play with. That's where the real issue is. Not trying to break the encryption, but the threat of bricking your device in the process.

(I do know what I'm talking about. I have written plenty of kernels and ROMs for the original Droid and I have been following this from the beginning. This is the final straw for me - I'm done with Motorola unless they pull a 180
 
U think eFuses stopped the Xbox 360 hacking scene? They found a way around it. Granted this may not have another way like the DVD drive (I think a way could be thru the SD Card tho. External Storage wasnt really an option on the 360. The Wii is done thru the SD Card...) but I think there is still a way.

Keep hope alive!!!
 
U think eFuses stopped the Xbox 360 hacking scene? They found a way around it. Granted this may not have another way like the DVD drive (I think a way could be thru the SD Card tho. External Storage wasnt really an option on the 360. The Wii is done thru the SD Card...) but I think there is still a way.

Keep hope alive!!!

+1 there
 
I will still be getting the Droid X for just the OTB features.

I went since the day of launch from the Droid Original to just about 2-3 months ago NOT knowing what Rooting was, or that it even existed, and I was honestly STILL blown away by how great of a phone it was, and still is.

Sure not being able to root the DX will suck tremendous balls, but hey, Majority of people who are buying the phone aren't 'tinkerers'.

And you have GOT to look at it from a business standpoint, if we are able to root our phones, and make them outlast their 'predetermined by the manufacturer phone renewal date' you are taking quite a bit of money out of their pockets by not upgrading to the latest and greatest.

All it ever is, is business.
 
I don't want to get everyone down - but everyone is way too optimistic about getting into this bootloader. Trust me - chances are slim to none. Not only did Motorola encrypt the bootloader as they did with the European Droid named the Milestone (the Milestone still has not been cracked after over 7 months), they seem to have implemented a feature developed by IBM known as eFuse. (Per P3Droid via My Droid World - a very reliable source so far with anything Motorola.) eFuse is used to completely write over the memory of the device - actually tripping the circuit eFuses and changing the hard coded memory. This can be used by manufacturers for positive outcomes, but in this case it is quite nefarious. The process can be reversed - but by Motorola of course. In this case, it is cross-referencing the kernel, bootloader, and firmware... try to get into any of these and eFuse will make sure you have a brand-new shiny paperweight to play with. That's where the real issue is. Not trying to break the encryption, but the threat of bricking your device in the process.

(I do know what I'm talking about. I have written plenty of kernels and ROMs for the original Droid and I have been following this from the beginning. This is the final straw for me - I'm done with Motorola unless they pull a 180
 
U think eFuses stopped the Xbox 360 hacking scene? They found a way around it. Granted this may not have another way like the DVD drive (I think a way could be thru the SD Card tho. External Storage wasnt really an option on the 360. The Wii is done thru the SD Card...) but I think there is still a way.

Keep hope alive!!!

Not to be Negative Nancy here, but the eFuse being blown in Xbox's Summer update in 2009 (and in dashboard revisions from June 2009 on) actually disallows for the xbox to be JTAGd, meaning no fun developing on those consoles... :(
 
well according to the birdman even the droid had the dreaded efuse so it seems to me like a bunch of smoke is being blown up our rears

Exactly, efuse is in every OMAP processor. It CAN do this, but it wasn't turned on in the Droid and no one knows if it was turned on in the Milestone because the bootloader hasn't been cracked.

Which is why this is all moot anyway as no one is going to hack the bootloader if they haven't been able to get into it on the Milestone yet.

My only problem real problem with this (although i do like cutom ROMs) is that if the X ever stops get OS updates, there won't be any way to put a newer version on the phone.
 
Well I just found the thread that AdamZ was probably referring to:
How the Droid X is locked down? Let me tell you what I know.

WARNING: If you decide to take the plunge and read that entire thread like I did, you are most likely going to lose any hope you gained from Birdman's tweeting.

Pay close attention to p3droid and Aixelsyd. I won't go over p3droid's credentials, as AdamZ already covered that, but Aixelsyd was one of the 3 guys (the other two were Bill and Winston) who were leaking Droid X and Droid 2 info at Howard Forums. The vast majority of the time, Aixelsyd was leaking info that turned out to be correct.

Like I said, if you really were getting your hopes up with Birdman's tweets, this thread will almost certainly crush those hopes: I honestly may hold off on buying the DX now (and I even have screen protectors on the way for it!) fml

OP is being updated.
 
Exactly, efuse is in every OMAP processor. It CAN do this, but it wasn't turned on in the Droid and no one knows if it was turned on in the Milestone because the bootloader hasn't been cracked.

Actually I have to assume that if the efuse was active in the Milestone, the hackers would have already tripped it. They have been sucessful in booting other kernels already. It's just that it isn't working well enough to be released. For example, the cell receiver doesn't work - which is pretty important considering this is a cell phone. :)
 
Back
Top Bottom