Motorola DROID 2 Pre-Release Thread

[Sqube]

Why would that be necessary? You could put updated guts in a D1 body and test FroYo that way. I'm sure Google could flash vanilla 2.2 on a Droid X. It doesn't make any kind of sense to do.

[redpanda2]

It's certainly possible the only hold up is Motorola getting Froyo ready for the device, considering Google only recently released the code. I guess of all the phones that could be the first to launch with Froyo, this would be a good candidate.

That's what I'm assuming at this point, but it's just the weirdest marketing tactic, since other phones are going to have 2.2 before the Droid 2 launches. Why would I be impressed that it's the first to ship with 2.2 if the Droid 1 is already running 2.2 before I can get my hands on one?

If the August 23 launch date is accurate, we probably shouldn't expect an official announcement until the last week of July, so I'm trying not to get worried until then. But I admit the fact that all the leaks suddenly stopped after the Droid X was announced is kind of... creepy.

[ronaldheld]

Things may get better after the X is out for a month.

[Fresnel]

If the August 23 launch date is accurate, we probably shouldn't expect an official announcement until the last week of July, so I'm trying not to get worried until then. But I admit the fact that all the leaks suddenly stopped after the Droid X was announced is kind of... creepy.

I have to admit that worries me too.

[rafarquhar]

Things may get better after the X is out for a month.

I hope so. I feel like a lot of the leaks have to be at least somewhat intentional due to their frequency and also because they create so much hype.

They might try to keep the D2 leaks down until the 30 day return period of the DX is up. What I really want to know is if the D2 will have a locked down bootloader.

[bizzshow27]

Yes it will. Looks like those wanting full root should wait or look at other phones

[karnovaran]

Yeah the latest news doesn't sound good for the D2 bootloader.

http://www.mydroidworld.com/forums/d...at-i-know.html

So this post is a mix of hard information and a bit of conjecture on my part (guesses). But I thought I would share it with you guys anyways.

First, Motorola is using an old technology (introduced in 2004) in a new way. You can read here a quick write up on here.

Now once information is written to a chip, that information is static but using an eFuse chip on the board Motorola is able to write information to it after it has been placed in use.

SO HOW DOES THIS EQUAL A HARDWARE LOCKED BOOTLOADER?

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 is a rewrittable module and thus once it has been tripped it can be repaired but this procedure can only be done by Motorola. It requires hardware (I'm not sure what type) and the program (I'm not sure what Motorola is using) written in JTAG.

The normal process of using an sbf file to upgrade has also been made more difficult as they have been tagged and if not properly applied or not device/build/increment specefic then they will trip the eFuse.

As you can see this is indeed going to be a tough nut to crack.

A secondary question that i've been asked, is about the future devices. I can't speak to other future devices but I have been told that this method of protection has been applied to the Droid2.

[redpanda2]

You know, I wouldn't mind the encrypted bootloader if they stick with stock Android. But if they put the same custom skin as is on the Droid X, I may look into going to Sprint for the Epic 4G.

[Natty_lite]

You know, I wouldn't mind the encrypted bootloader if they stick with stock Android. But if they put the same custom skin as is on the Droid X, I may look into going to Sprint for the Epic 4G.

I feel the same. but I could still see me using it with the overaly as long as it was updated to 2.2. Plus root is still a possibility, so other root related applications are still in play.

[ushneb]

A pic, courtesy of Android Central

[thescreensavers]

http://www.boygeniusreport.com/galle...ery=47&pid=686

Boy Genius Report just got its hands on the Verizon Wireless 2010 Summer Catalog. And surprisingly, the Droid 2 is showing its face "officially" for the first time, as it has found its way onto the "Devices" page! Of course, the cover only had room for its big brother, the Droid X, but it is great to finally see the Droid 2 made "official" by Verizon Wireless. Besides that, there really are no other surprises in the Summer Catalog. The "technical specs" page lists the exact specs we have expected (and confirmed?) for quite a long time: 1Ghz CPU, 5MP camera (no 720p capture), slide-out QWERTY, 8GB ROM/512MB RAM, 8GB SDcard, and 3G Mobile Hotspot. There is no mention of its version of Android, but we suspect that by the time it launches (latest rumors have it at the end of August), it will be running FroYo.

Ok so Confirmed that its coming out lol, I am already getting the X, hope the X is out of stock until the D2 comes in stock, then I could possibly get the D2 if I like it better.

[theryguy512]

A pic, courtesy of Android Central

Just when I was losing hope, it finally gets 'confirmed.' =D

[i2aNe]

^ Same here =D. Now all I wanna know is if it's got an encrypted bootloader (dunno if that's the word). I really wanna try out custom ROMs. Hopefully it's not the way of the DX, but if the Droid X is encrypted, the D2 would be as well right?

[theryguy512]

Ya know, at first, i was thinking, "now why is the Droid 2 shown with Bejeweled on its screen?" But now, I'm thinking, "hey, wait a sec, isn't Bejeweled a flash game?"

You all know what flash means...Froyo.

[Paznos]

^ Same here =D. Now all I wanna know is if it's got an encrypted bootloader (dunno if that's the word). I really wanna try out custom ROMs. Hopefully it's not the way of the DX, but if the Droid X is encrypted, the D2 would be as well right?

Yup pretty sure that's the way Motorola is gonna do with all their Android phones now, especially if it has their widgets/skin on the phone.