Android 2.1 Update Rolls Out For Motorola Droid!

[adrynalyne]

could it be somewhere weird and unexpected like /system/etc/security stuffed in there with the otacerts file?

Not unless somehow the OTA process has root access.

I'm not really sure i'd have any reason to believe that wouldn't be possible? It could be hardcoded into the OS to work that way; much like some Windows processes run as "System" and have full access to everything.

I just find it unlikely.

Better yet, impossible.

The reboot into the recovery partition formats /system, then flashes the new /system and baseband. Nothing can be installed from /system.

It would have to be /data (unlikely), /cache (very possible), or /sdcard.

 

[Goat]

Thanks for posting pics....this actually looks real now. This guy on droid life speaks truth! The instructions are wrong b/c verizon changed the process so that the update wouldn't be put out too quickly...

"I work for Verizon Wireless. I'm guessing they somehow fixed the update it so you couldn't get it off the card. After all they have held this update up many times, and they're running an incredibly slow update process, so to me that means they have some concerns about issues with the update process and want to have a 24 hour period to see if they get any complaints of bricked phones. With those kinds of concerns I'm sure they'd do anything to keep it from getting out en masse on the internet"

And I'll repost here again...


1. Verizon has ZERO control over the OTA process, that would be Bitfone.
2. It is impossible to force an install, and would be cause for any number of lawsuits.
3. Even if they did do a force, the odds of an OTA NOT hitting a dev level owner out of the first 1000 updates would be astronomical these days...meaning a linux power user would have zero issues pulling the build no matter the location prior to install.


And a bonus round.

4. The OTA process is created in the Plateform level of the code, which is Moto's code that is compiled from their BaseROM builds. This code will only be applications built on top of the base Android code plus the OTA, modem, FW, MCU, app, etc and OTA code. The OTA code for this project is done by Bitfone and HP company located in Cupertino, CA. They dictate all processes related to SD and OTA updates.

Their code does not lock out the ability to copy from the NAND or SD of the device.

Lulz.


If it reboots automatically after downloading it, you don't really get an opportunity to get to the file, which IS deleted after the flash. No, nothing steps you from copying it, but it sure makes it a pita and easy to mess up.

An auto reboot would be a cashcow for lawsuits...

And it doesn't auto reboot, there is a confirmation

 

[kellex]

Theron posted his video of the his update...we almost had it!

[video=youtube;yKcZ9rIwrWM]http://www.youtube.com/watch?v=yKcZ9rIwrWM]YouTube - Verizon Updated Motorola Droid[/video]

 

[adrynalyne]

And I'll repost here again...


1. Verizon has ZERO control over the OTA process, that would be Bitfone.
2. It is impossible to force an install, and would be cause for any number of lawsuits.
3. Even if they did do a force, the odds of an OTA NOT hitting a dev level owner out of the first 1000 updates would be astronomical these days...meaning a linux power user would have zero issues pulling the build no matter the location prior to install.


And a bonus round.

4. The OTA process is created in the Plateform level of the code, which is Moto's code that is compiled from their BaseROM builds. This code will only be applications built on top of the base Android code plus the OTA, modem, FW, MCU, app, etc and OTA code. The OTA code for this project is done by Bitfone and HP company located in Cupertino, CA. They dictate all processes related to SD and OTA updates.

Their code does not lock out the ability to copy from the NAND or SD of the device.

Lulz.


If it reboots automatically after downloading it, you don't really get an opportunity to get to the file, which IS deleted after the flash. No, nothing steps you from copying it, but it sure makes it a pita and easy to mess up.

An auto reboot would be a cashcow for lawsuits...

And it doesn't auto reboot, there is a confirmation

Its been confirmed once you start the process, it reboots you.

Are you just making this stuff up as you go?

 

[redmccarthy]

Is there some reason we couldn't use a Nandroid backup of somebody's phone that got the update to bypass the whole update.zip thing?

Lack of root access might be a problem....

...Yeah, I didn't consider that. Installing the update isn't going to revert the BIOS-like program where you do backup/restore to stock, is it?

 

[Goat]

Lulz.


If it reboots automatically after downloading it, you don't really get an opportunity to get to the file, which IS deleted after the flash. No, nothing steps you from copying it, but it sure makes it a pita and easy to mess up.

An auto reboot would be a cashcow for lawsuits...

And it doesn't auto reboot, there is a confirmation

Its been confirmed once you start the process, it reboots you.

Are you just making this stuff up as you go?

No, you download and then a pop up come up asking to update now or later.

 

[adrynalyne]

I'd have to go back a few pages, but its confirmed that this DOES NOT HAPPEN. Not this time. It goes straight into download, reboot, install.

 

[dawoomi]

Go to sleep. It's too tired just waiting.
Good night guys.

 

[CaliKing]

I really hate to sound negative but this seems reeally useless. If the update lacks flash, who cares. Wow pinch to zoom, really?

 

[adrynalyne]

Is there some reason we couldn't use a Nandroid backup of somebody's phone that got the update to bypass the whole update.zip thing?

Lack of root access might be a problem....

...Yeah, I didn't consider that. Installing the update isn't going to revert the BIOS-like program where you do backup/restore to stock, is it?

You mean the recovery image? It will do it automatically. It will download, reboot, you will see an unmodified recovery image, and it will auto run.

Or am I misunderstanding you?

 

[Dave12308]

Is there some reason we couldn't use a Nandroid backup of somebody's phone that got the update to bypass the whole update.zip thing?

The phones with the update don't have SPRecovery cuz they aren't rooted I'd like to know if it's possible

The problem is, i'm thinking there's an EASY way to get SPRecovery on there (at least there was with ESE53) - the hard part is finding someone out of a relatively small pool with the knowledge to actually attempt it. You NEED ABD access, so the folks who don't even know what the SDK is are unfortunately of little help.

If anyone who has the update wants to TRY, here are the instructions:

How-To: Root ESE53 .sbf

pretty straightforward, as long as ADB works. Since you've already got the custom recovery installed, you will be able to install the update.zip for superuser.

Once this is done, you would be able to create a Nandroid backup and pop it up on a file host.

 

[MiXoLoGiSt]

An auto reboot would be a cashcow for lawsuits...

And it doesn't auto reboot, there is a confirmation

Its been confirmed once you start the process, it reboots you.

Are you just making this stuff up as you go?

No, you download and then a pop up come up asking to update now or later.

I dont think you have been paying attention... THERE IS NO POP UP ASKING IF YOU WANT TO REBOOT NOW OR LATER! Tons of people have confirmed this.

 

[Shadez]

Its 2 am go to bed people!!

:d

 

[adrynalyne]

Is there some reason we couldn't use a Nandroid backup of somebody's phone that got the update to bypass the whole update.zip thing?

The phones with the update don't have SPRecovery cuz they aren't rooted I'd like to know if it's possible

The problem is, i'm thinking there's an EASY way to get SPRecovery on there (at least there was with ESE53) - the hard part is finding someone out of a relatively small pool with the knowledge to actually attempt it. You NEED ABD access, so the folks who don't even know what the SDK is are unfortunately of little help.

If anyone who has the update wants to TRY, here are the instructions:

How-To: Root ESE53 .sbf

pretty straightforward, as long as ADB works. Since you've already got the custom recovery installed, you will be able to install the update.zip for superuser.

Once this is done, you would be able to create a Nandroid backup and pop it up on a file host.

Yeah that would be nice, but what are the chances that adb root was left open?

 

[Dave12308]

I just find it unlikely.

Better yet, impossible.

The reboot into the recovery partition formats /system, then flashes the new /system and baseband. Nothing can be installed from /system.

It would have to be /data (unlikely), /cache (very possible), or /sdcard.

It's 2AM *LOL* I'm half asleep........ I completely missed that very obvious fact.....