• 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

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... :(

Which is why earlier in this thread I and a few other ppl mentioned about not updating the phones just yet.

I already mentioned that a few days ago in the other forum where the eFuse info got started. And like I mentioned, there was still a way around the eFuse issue on the 360.
 
No efuze, bootloader shouldn't be too hard to unlock. Believe me or not, but it WILL happen. Locking this phone down isn't as big of a deal to Moto as many of you think.
 
If the X really is hopeless then I wonder where Cyanogen/Koush and Pete are going?

Currently they are days away from releasing CM6 for the EVO, and after seeing a preview its SICK!! They have totally UNLOCKED everything.

As far as getting the X unlocked, I think it speaks volumes when cyanogen and his team have gone on record and said they aren't touching the X. Moto has changed the game it seems like.

Pete is developing for the EVO and the Droid, but I did hear he won a X so he may try his hand at it, after all when it explodes he got it for free so not much of a loss.

Droid X actually self-destructs if you try to mod it

some more info on the issue
 
Currently they are days away from releasing CM6 for the EVO, and after seeing a preview its SICK!! They have totally UNLOCKED everything.

As far as getting the X unlocked, I think it speaks volumes when cyanogen and his team have gone on record and said they aren't touching the X. Moto has changed the game it seems like.

Pete is developing for the EVO and the Droid, but I did hear he won a X so he may try his hand at it, after all when it explodes he got it for free so not much of a loss.

Droid X actually self-destructs if you try to mod it

some more info on the issue

Yeah I saw how he had a couple of tweets that said he had ported over the sound recorder app and another one I can't remember from the X. I will just say at the time being I can't wait BB 0.5
 
No efuze, bootloader shouldn't be too hard to unlock. Believe me or not, but it WILL happen. Locking this phone down isn't as big of a deal to Moto as many of you think.

I think you're seriously underestimating the type of protection installed in this phone. I would recommend you take a look at the OP and check out the update I posted today: the 2nd arrow is what I'm suggesting you take a look at. If you do the suggested reading that I link to, you most likely will change the way you're thinking. :/
 
Hello all.

I have decided to email Motorola informing them of my distaste for their practice of locking bootloaders. I think that if enough people do this, we could convince them to change their ways. So let's all email them! I'm including a copy of the email I sent to them. (PS, I know I have some grammatical problems, I was stupid and failed to proofread before I sent the email)

"Hello,

I would just like to express my disappointment with your company's decision to lock down the bootloader of the Droid X. I have had numerous Motorola phones, including the Zine ZN5 and the original Moto Droid. My family have been using Motorola cell phones for more than 15 years. It was my intention to purchase a Droid X within the next month.

That has all come to an end. Your decision to lock the bootloader is completely anti-consumer. It is not harmful to you at all to allow consumers to modify their phone. You may think that you are only alienating the hardcore developers, but that is far from the truth. I myself am not a developer at all, merely someone who enjoys customization of phones.

Not only are you losing myself and my family members, whom I often advise on phone purchases, as customers, but you are also losing a wonderful reference. Because I frequently change phones, many people come to me for advice on what phones they should purchase. I will no longer recommend any Motorola phone. Just today a co-worker asked if she should purchase the Droid Incredible or the Droid X. I told her that she should not support a company that needlessly restricts the use of a consumer's own property. In any other product but a cell phone, this would not be tolerated. Even in the computers made by Apple (the oft-lauded most restrictive companies), they allow the installation of alternate operating systems. Remember, these mobile phones you sell are really miniature computers.

Further, I know for a fact that this is not brought on by pressure from the telecoms. I previously worked with a company that was working to release an Android smart phone (though it seems unlikely to see the light of day at this point), and none of the telecoms we had worked with had any complaints of having unlocked bootloaders. This includes Verizon, on whose network the Droid X will be released.

You are not doing this to avoid warranty repairs on phones that had been improperly modified, because doing so voids one's warranty. This is something that all who install custom ROMs understand. There is no discernible reason for you to be locking these bootloaders. All you are doing is alienating your customer base.

I hope you understand that I am far from the only person who feels this way, and you will be losing many, many sales because of this. You had a chance to recreate yourself, and bring yourself back to the top of the mobile phone industry. You have shown that you care nothing about consumers, and do not deserve to regain your leadership position.

By doing this, you are proving yourself to be no better than Apple.

You can change all of this by releasing unlocks for the bootloaders of your phones, including the Droid X, and by not locking the bootloaders of your future phones.

Yours truly,

A former fan of Motorola smart phones,

XXXXXXXXXXXX"
 
I think you're seriously underestimating the type of protection installed in this phone. I would recommend you take a look at the OP and check out the update I posted today: the 2nd arrow is what I'm suggesting you take a look at. If you do the suggested reading that I link to, you most likely will change the way you're thinking. :/

Nothing there I didn't know already. The only thing new to me is that the devs are wussing out. Until someone bricks their phone from the "efuse" than I am convinced that its nothing more than a rumor started by birdman, which he has since retracted. I do hope the devs don't give up, because developing a true homegrown workaround would be much better and easier to distribute than the... dirtier... method that will come about.
 
Which is why earlier in this thread I and a few other ppl mentioned about not updating the phones just yet.

I already mentioned that a few days ago in the other forum where the eFuse info got started. And like I mentioned, there was still a way around the eFuse issue on the 360.

Yes there was a way around the efuse issue in order to JUST play burned games, but to fully unlock the console via JTAG and basically have a dev kit was imopossible once the efuses were blown (no efuse = no cpu key information provided by the dashboard = no custom built nand for JTAG). I am not trying to argue here, this whole issue sucks I am just saying that there still has been no workaround for these newer xbox consoles that have the blown efuses, and there never will be. Of course, that is not to say there could one day be a hack for it
laugh.gif
 
As far as getting the X unlocked, I think it speaks volumes when cyanogen and his team have gone on record and said they aren't touching the X. Moto has changed the game it seems like.

Last info I saw posted, Cyanogen didn't discount developing for the X:

Droid X Hacks - Droid Forum - Verizon Droid & the Motorola Droid Forum...

@cyanogen Hey, are you guys going to be attempting to root/load custom roms to the X at all? Didn't know if you were going to try X stuff

@guts311 eventually, the DroidX I have right now isn't mine to keep though
 
Yes there was a way around the efuse issue in order to JUST play burned games, but to fully unlock the console via JTAG and basically have a dev kit was imopossible once the efuses were blown (no efuse = no cpu key information provided by the dashboard = no custom built nand for JTAG). I am not trying to argue here, this whole issue sucks I am just saying that there still has been no workaround for these newer xbox consoles that have the blown efuses, and there never will be. Of course, that is not to say there could one day be a hack for it
laugh.gif

I'm not trying to argue either :p But with the DVD Drive hack there was still a way to run modified software on it in spite of the eFuse.

Even tho u still had to open up the 360 to get at the DVD Drive....I'm thinking the SD Card might hold the key for the X. Or the USB port.

I still think it can happen, it just wont be as easy as before. The issue might be trying to make and restore backups of the phone if someone can somehow get around the eFuse thing. (I just remembered about the Nandroid reading your post....) :o

Your post got me thinking: The 360 DVD Drive had its own firmware, the console had its own firmware. That may be the key for the X to get cracked open. Or somehow have a bootloader run from the SD Card like someone mentioned a few pages back. Dual boot?

Hey, the more we all throw out ideas, the better chance someone with the knowledge and know how can try to do this. So your last post has been helpful...lol
 
Nothing there I didn't know already. The only thing new to me is that the devs are wussing out. Until someone bricks their phone from the "efuse" than I am convinced that its nothing more than a rumor started by birdman, which he has since retracted. I do hope the devs don't give up, because developing a true homegrown workaround would be much better and easier to distribute than the... dirtier... method that will come about.

Ok... well maybe I'm alone here, but when someone who is known to have inside access to Motorola has posted the following, it tends to bother me (a lot):

It is a given it will brick. I actually have a picture from a contact of min of 50 Droid 2 that were all bricked by this new design while they were testing the feature out. And per my contact they are all going back from scrapping as they are now useless. Moto has purposely designed it so when the eFuse pops the device will not boot and turns it into a paperweight."

^ Source of quote: How the Droid X is locked down? Let me tell you what I know.

"It is in fact in use and more then likely will be on all future devices. the only device it was never put in use on was the Droid and that was a specific arrangement between the 3 companies involved so the device could be released when it needed to be. Be that as it may I've seen it in action and many bricked ( Droid 2's and Droid X's) units already."

^ Source of quote: How the Droid X is locked down? Let me tell you what I know.
 
I dont have to read anything. all i roam is this and the fascinate section, and quite honestly i have read enough.

seriously even if your name was GOD, i wouldnt follow you.So, thanks but ill pass. i have to go watch the grass grow

I don't want you to follow me or read a different thread they are all in this one. If you don't want to understand what I was saying and prefer to take something out of context then why bother to comment in the first place?

Take care and have fun watching the grass grow.
 
But even still with that, instead of trying to defeat the eFuse, why not find a way around it? Ignore the official boot loader and go to a plan B?

And all it will take is for a bad official OTA update to brick the phone for Motorola to be in serious hot water.
 
This article doesn't make it easier to hack.. So don't get your hopes up.

It makes it easier by lessening the time it will take.

Now that Moto said it WILL NOT BRICK, I am sure people are going to rip that encryption soon enough.
 
It makes it easier by lessening the time it will take.

Now that Moto said it WILL NOT BRICK, I am sure people are going to rip that encryption soon enough.

How does it make it easier by lessening the time? I may be wrong, but isn't the main issue here the encryption itself in that chances are slim to none of cracking it?
 
How does it make it easier by lessening the time? I may be wrong, but isn't the main issue here the encryption itself in that chances are slim to none of cracking it?

I think what he is trying to say is, it will allow the DEVS to try different things without the fear of totally locking up the phone. I agree, it's not easier, just safer now.
 
How does it make it easier by lessening the time? I may be wrong, but isn't the main issue here the encryption itself in that chances are slim to none of cracking it?

It is lessening what hackers are worrying about. All we need now is the Encryption, if i'm not mistaken..
 
I think the title of Phandroid's article puts what Motorola said in perspective:

"Motorola Responds to eFuse and Bootloader Talk: Doesn’t Brick, But Still Just as Useless"

Focus in on the "still just as useless" part. Why do I say that? Well, almost everything I'm reading indicates that relatively little is known about exactly how THIS eFuse works. All that Moto told us is that it doesn't brick the phone outright (aka it is still salvageable). What I think what we're forgetting is that the eFuse (AFIAK) still seems to make a PHYSICAL change (to the hardware). While we know that the result of the change is continual booting, we have little insight into how to correct the issue: it seems unlikely to me that hackers would be able to correct a physical change.

In other words, if a physical change has indeed occurred, I'm betting that only Moto or Verizon will be able to correct it.

Now I know some of you like to shake your finger at anyone who you think is making things up so let me say this: while it may sound like I'm making wild guesses here, but please take into account that I have invest an enormous amount of time reading this thread, organizing the OP and and exploring other forums and blogs on this specific subject. At the very least, what I'm saying here qualifies as an educated conjecture.
 
Back
Top Bottom