• 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

Its is sounds to me like is a physical firewall in a way, meaning if the eFuse reads the ROM and it doesn't meet the criteria then it remains in the BL screen until you load a matching ROM with the right criteria to launch it.

It is still just as useless, until you load the right ROM.
 
Jareris said:
I'm sure it'll happen. I am just going to sit here with my custom Rom'd, overclocked Droid and watch.
Click to expand...

+1 I have been going back and forth for a couple of weeks. I plan on waiting a couple of weeks then pick up the X and skip the fascinate. And then I figured out a way to get a new phone in January also so...:D
 
Also suggests it is locked down to the point of real-hard to get roms on the X besides the ones they want.

The way they are describing the fail-safe for original rom reinstall, it seems like this may be a rom area that can not be accessed, even through a VZW update. Probably by design.
 
Has anyone else thought about the fact that we don't even have any "official motorola" approved ROM's to actually bring us out of the BL? Soooo when someone tries to flash a ROM and it gets stuck at the BL what do we load up to fix it? Mine as well be a brick.

Recovery...not bl, my bad. On a side note we are having a giant thunderstorm here in MA.
 
I would think first someone is going to have to extract the Original ROM for the phone, that way we can just flash it back. How you would go about doing that... I am not a hacker, so I wouldn't know.
 
HalfFrozen said:
I would think first someone is going to have to extract the Original ROM for the phone, that way we can just flash it back. How you would go about doing that... I am not a hacker, so I wouldn't know.
Click to expand...
Unfortunately it doesn't work that way. We have already done a system dump of the Droid X but you can't flash it back because it not in the right format (update.zip). You also can't package it into a zip because you won't have the key to sign it with. We need a massive OTA or a leak.
 
CRPercodani said:
Has anyone else thought about the fact that we don't even have any "official motorola" approved ROM's to actually bring us out of the BL? Soooo when someone tries to flash a ROM and it gets stuck at the BL what do we load up to fix it? Mine as well be a brick.

Recovery...not bl, my bad. On a side note we are having a giant thunderstorm here in MA.
Click to expand...

Phew *wipes brow sweat* I thought no one was gonna back me up for a little while there! (http://androidforums.com/motorola-d...ed-bootloader-efuse-thread-9.html#post1155760 ) lol
 
CRPercodani said:
Unfortunately it doesn't work that way. We have already done a system dump of the Droid but you can't flash it back because it not in the right format (update.zip). You also can't package it into a zip because you won't have the key to sign it with. We need a massive OTA or a leak.
Click to expand...
Well, thankfully there will be one coming in August or September for the Froyo update they promised.
 
Be patient...

This kind of thing isn't going to happen over night.

This isn't exactly the easiest thing to do...
 
Ok so i have a question for everyone. When i had my dinc i was able to play mario n excite bike by putting on nesoid n downloading the rom from freeroms. But am i not able to do that with this phone cause i tried it n im not having much luck. Thought. It was only custom roms like a new os that wouldn't work. Wtf. Haha
 
You must log in or register to reply here.
Back
Top Bottom