[How-To] Force Motorola Droid 2.1 OTA Update (ESE81)

uhhohhs

I'm getting and error. unrooted phone

phone boots, lock screen comes up, but after unlocking, I get the followign error:

"The application Launcher (process com.andriod.launcher2) has stopped unexpectedly Please try again"

All the phone functions work, I can mount it, it is getting service, but this error pops up on front of the screen no matter what

I see I'm the second one this minute!

Universal, did you happen to haev the 5 homescreen mod installed?
 
Last edited:
uhhohhs

I'm getting and error. unrooted phone

phone boots, lock screen comes up, but after unlocking, I get the followign error:

"The application Launcher (process com.andriod.launcher2) has stopped unexpectedly Please try again"

All the phone functions work, I can mount it, it is getting service, but this error pops up on front of the screen no matter what

Same exact thing here. Hopefully someone can help us out. Yes, I did have 5 screen home screen installed.
 
So do we put all the files and folders that are downloaded onto the sd card?
 
uhhohhs

I'm getting and error. unrooted phone

phone boots, lock screen comes up, but after unlocking, I get the followign error:

"The application Launcher (process com.andriod.launcher2) has stopped unexpectedly Please try again"

All the phone functions work, I can mount it, it is getting service, but this error pops up on front of the screen no matter what

Yes, I did have 5 screen home screen installed.
Small sample size, but, might be onto somethign here.
 
how do i root back to 2.0.1 from this? i just wanna wait for the official update lol
 
I am having problems installing this. I'm using a Window computer. I named the file "update" and did the rest of the process. However I'm keep getting "Installation Aborted"..

can someone please help?
 
So do we put all the files and folders that are downloaded onto the sd card to push the update?

META-INF - folder
recovery - folder
patch - folder
system - folder
bp.img
rdl.bin
mbm_consumer.bin
 
Went back to stock 2.0.1 then applied the update. Worked just fine for me.
 
Back
Top