Android 2.1 Update Rolls Out For Motorola Droid!

[NERD01]

Damn I think I'm gonna hit the sack, got school in the morning..

 

[Dave12308]

The update definitely disappears after installation right?

Let's say it doesnt, any idea where it would be hiding?

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

 

[adrynalyne]

I just thought of another way to kinda prove it, just for the unbelievers...
What do you notice?
Blue bars on the left = Yahoo mail.
Ok I'm gonna go snack.
Again sorry to anyone I've disappointed :icon_ nono2:
​

Pull the system with adb. Or at least the build.prop.

 

[sneaky_zekey]

we need to get a system dumb of the update out in the wild so devs can examine it.

 

[adrynalyne]

The update definitely disappears after installation right?

Let's say it doesnt, any idea where it would be hiding?

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.

 

[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.

 

[dezidez87]

Instructions to grab the file are not correct. That's 2 people now reporting that they are not seeing the second "Restart and Install" screen and instead going straight to boot.

BINGO. It just went str8 to work after the 1st question.lol
And One thing I notice is that my gmail stopped giving me audible notifications... I'm getting messages of responses here that I didnt know I had unless I check. hmm
​

Do you have the sdk installed? Can you plug your phone in and run:

adb pull /system system

:icon_eek:
Dont know what sdk is. Sd kard?lol JK but i really dont know what it is or how i would run 'adb pull /system system'.
Remember, i got choked up and spent days tryna root and install an earlier update thingie, sooo I may not be much help.
​

 

[Dave12308]

The update definitely disappears after installation right?

Let's say it doesnt, any idea where it would be hiding?

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.

 

[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?

 

[adrynalyne]

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.

 

[evilxhwnd]

who ever has it, pull /system

adb pull /system system

 

[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....

 

[HermitObserver]

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

 

[OneTenderRebel]

It seems hope is fading fast, the waiting continues.

 

[Guchi]

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?

root access...