Root Warning to Those Updating to 2.2

[anaphora68]

IF you all update to the official 2.2, I would tread very lightly.

Until I can confirm that we are still able to use the Bootstrapper (and be able to flash ROMs, etc), I am staying with my leaked build for the time being. CVPCS and co. are making progress on getting an AOSP ROM to work, but it will likely not work with the new release.

I have a sinking feeling that Moto updated the bootloader to completely disable someone getting into engineering mode without flashing something from moto that is properly signed. Ergo, new update, even more locked down.

These errors people are getting are not errors. It looks like Moto fired back at the hacking community by updating the bootloader and signing the official OTA with a new signature.

I'm not saying there won't be a way around, there always is. What we have works now though, so I would stay with the leak and see what plays out.

Just my two cents. I'll be the first to say I can't program, but I can apply logic to what's happening.

So, if you can, HOLD OFF on the upgrade. If you're running a leak, you already have 2.2. I can understand the desire to have the latest and greatest on your phone, but when moto includes an encrypted bootloader, they can change the game at the drop of a hat and screw all of us over.

 

[nitsuj17]

yeah from what birdman and others have been saying on twitter, basically motorolla fired a big shot back by updgrading the bootloader.

Looks like if you take the ota, your chances of ever seeing custom roms or overclocking take a massive hit and the devs may only work on the older bootloader and leaks.

Sucks, and hopefully they do find a work around but it looks like the bootloader exploit was a one time massive motorolla/ti oversight that thankfully people a lot smarter than me found and are working on.

 

[anaphora68]

I'm sure Birdman and Co. will figure something out, but the reason I caution is that a ton of progress has been made with the bootloaders that have the same signatures. This new one changes the game, and if any updates were made to MBM, the Bootstrapper could have been taken out of commission as well.

The whole point of my post is this: remain wary, wait to update to the official until we know more.

For me, if I can get an AOSP ROM, there's no point to ever updating to the official OTA.

 

[mazz0310]

I'm sure Birdman and Co. will figure something out, but the reason I caution is that a ton of progress has been made with the bootloaders that have the same signatures. This new one changes the game, and if any updates were made to MBM, the Bootstrapper could have been taken out of commission as well.

The whole point of my post is this: remain wary, wait to update to the official until we know more.

For me, if I can get an AOSP ROM, there's no point to ever updating to the official OTA.

Yeah, I am waiting to see what Birdman says. I definitely don't want to risk losing the unlocked bootloader.

 

[derpudel]

Yes, they are working on it, but struggling. Don't look for a quick fix for recovery back to 2.1 anytime soon. In fact, this may discourage these guys from spending more time trying to crack the new signed Bootloader.
Dunno...just a hunch.
I am VERY glad I did not do the OTA update. Still on 2.1 and happy with that.

 

[anaphora68]

The bootloader is still locked on the older release(s), just to clarify that point.

I just want to make sure that the Bootstrapper works, etc, on 2.2. If someone can confirm that, and the ability to still boot into a custom ROM, then I'll gladly roll back to 2.1 and then to official 2.2 and root, etc.

 

[derpudel]

The rub is IF you don't like the OTA 2.2. There isn't anyway to roll back to 2.1 from the OTA update right now. If you try, you will brick your phone.

 

[mazz0310]

The rub is IF you don't like the OTA 2.2. There isn't anyway to roll back to 2.1 from the OTA update right now. If you try, you will brick your phone.

This is true, but why wouldn't you like the OTA? The only reason I can see to downgrade is if any progress is made with the bootloader.

 

[Pointguard1122]

I am so glad I didn't update right away. It sounds like the best thing to do is stay where we are until we hear from Koush or Birdman. I am sure someone will release a cleaned up rooted version without the bootloader update soon. Sorry for those who took the plunge. Hopefully we will get a 2.2 SBF soon.

 

[mazz0310]

I am so glad I didn't update right away. It sounds like the best thing to do is stay where we are until we hear from Koush or Birdman. I am sure someone will release a cleaned up rooted version without the bootloader update soon. Sorry for those who took the plunge. Hopefully we will get a 2.2 SBF soon.

That's what I'm going hope/wait for. Hopefully someone can make an update.zip without the updated bootloader.

 

[OMJ]

very smart of motorola to change the keys so the CDT is different. I am willing to bet this ruins going back to the 27.01 bootloader as well

 

[mazz0310]

very smart of motorola to change the keys so the CDT is different. I am willing to bet this ruins going back to the 27.01 bootloader as well

Yeah, I'm upset with Motorola, locked bootloader was bad enough, but changing the keys to F us all is even worse.

You defeated me until next time Motorola!!

 

[anaphora68]

Well, let's not all lose hope so quickly. There are a few really dedicated people working on our "issue," so you never know. I'm not saying there's hope that we'll unlock the bootloader, but I'm sure we'll get around what Moto has done.

Yikes, as a community, us Droid X users are horribly impatient. It's only been 8.5 hours since the OTA rolled. For those of rooted, we have a team of people who are working on it, and we will know more soon.

 

[Travisimo]

1) This shouldn't have been a surprise to anyone as Motorola clearly was not happy when the first leaks came out. They sent takedown notices all over the place and warned everyone not to use the leaks. Why then should we not be surprised to find that this 2.2 OTA locks the phone down further and attempts to prohibit further hacking? I was not surprised one bit.

2) Patience is the key for anyone who chooses to mod their phones. Unless you are very knowledgable or don't mind headaches getting things back, NEVER be the first to download a new update/modification. Always read and learn before attempting it yourself. I'm no expert at all, but I knew not to install this OTA update. For anyone who rooted and installed any of the leaked 2.2's, there was no hurry to upgrade to the OTA anyway. There's clearing very little difference (aside from the phone being locked down even further now). All we had to do is wait for further updates from Birdman and the rest of the mod crew.

3) Why would anyone want to SBF back to 2.1 after installing the OTA 2.2 anyway? It's already possible to root the OTA 2.2. Obviously, if you want to install roms and the like, you were probably already using a bootstrapped leaked 2.2 and could have just waited for an update.zip of the new build or another rom. For those who were rooted and already using 2.2, there was never a good reason to SBF to 2.1 and then install the OTA.

I feel bad for those who have bricked phones because of this, but no one should really be surprised. And by doing your homework and being patient, you can always avoid this sort of thing...

 

[Lars]

Anyone tried the Droid 2 root on the new OTA or been able to preserve root after the OTA?

 

[mazz0310]

Anyone tried the Droid 2 root on the new OTA or been able to preserve root after the OTA?

Yes, Droid 2 root method works. It's been posted.

 

[Piiman]

The bootloader is still locked on the older release(s), just to clarify that point.

I just want to make sure that the Bootstrapper works, etc, on 2.2. If someone can confirm that, and the ability to still boot into a custom ROM, then I'll gladly roll back to 2.1 and then to official 2.2 and root, etc.

Yes it's still locked but they do know it can be kicked into engineering mode which is basically unlocking it. They just need to determine what it is the causes it to go into that mode and then its open.

Why do you or anyone want to go back for an updates that the same as we have now? It's the same update as the latest leak. It's only missing the new keys that just lock you out, probably for good? I don't get it.

 

[Piiman]

This is true, but why wouldn't you like the OTA? The only reason I can see to downgrade is if any progress is made with the bootloader.

When and if it happens who said you have to downgrade to get the unlocked boot loader? The new OTA though will differently make it so you can't. What does everyone think is so different from the leaked version and the OTA? they have the same version numbers.

 

[OMJ]

When and if it happens who said you have to downgrade to get the unlocked boot loader? The new OTA though will differently make it so you can't. What does everyone think is so different from the leaked version and the OTA? they have the same version numbers.

as far as I can tell the only difference is a new baseband

 

[anaphora68]

Piiman,

Functionally, it's identical to the leak from last week. I'm not touching the official OTA.

I tweeted with P3Droid this morning, he basically said that Team Black Hat is still rolling ahead with what they were going to release.

 

[Justintoxicated]

How hard is it to unroot the OTA 2.2 once rooted? If it is difficult or not possible and the SBF no longer works then by getting OTA 2.2 and rooting you it would be more difficult to restore for warranty reasons.

I guess it's time for me to grab that p3droid 2.3.15

 

[northernmoris]

How hard is it to unroot the OTA 2.2 once rooted? If it is difficult or not possible and the SBF no longer works then by getting OTA 2.2 and rooting you it would be more difficult to restore for warranty reasons.

I guess it's time for me to grab that p3droid 2.3.15

+1... Leaked Froyo ftw.

 

[Justintoxicated]

+1... Leaked Froyo ftw.

Yep I just need to find an easy approach to doing this now from 2.3.13.

Another useful idea would be a post on how to upgrade from 2.1 to 2.3.15 (leaked and rooted). Not OTA. Covering the easiest way to do this. (universalandroot, Rom Manager etc)

 

[akita]

1) This shouldn't have been a surprise to anyone as Motorola clearly was not happy when the first leaks came out. They sent takedown notices all over the place and warned everyone not to use the leaks. Why then should we not be surprised to find that this 2.2 OTA locks the phone down further and attempts to prohibit further hacking? I was not surprised one bit.

2) Patience is the key for anyone who chooses to mod their phones. Unless you are very knowledgable or don't mind headaches getting things back, NEVER be the first to download a new update/modification. Always read and learn before attempting it yourself. I'm no expert at all, but I knew not to install this OTA update. For anyone who rooted and installed any of the leaked 2.2's, there was no hurry to upgrade to the OTA anyway. There's clearing very little difference (aside from the phone being locked down even further now). All we had to do is wait for further updates from Birdman and the rest of the mod crew.

3) Why would anyone want to SBF back to 2.1 after installing the OTA 2.2 anyway? It's already possible to root the OTA 2.2. Obviously, if you want to install roms and the like, you were probably already using a bootstrapped leaked 2.2 and could have just waited for an update.zip of the new build or another rom. For those who were rooted and already using 2.2, there was never a good reason to SBF to 2.1 and then install the OTA.

I feel bad for those who have bricked phones because of this, but no one should really be surprised. And by doing your homework and being patient, you can always avoid this sort of thing...

I agree with this post other than feeling bad for people bricking their phones. That's exactly what people get for not being patient and the fact that some are going back to Verizon demanding a replacement is just icing on the cake. Im not about supporting "the man" but stupidity and ignorance should not be rewarded.

 

[Breezer23]

F**k Motorola. Never buying another one of their phones again. Not like they have anything to hide. I still feel this is Verizon's doing as they probably are tired of replacing broken phones due to rooting gone wrong.