Database Develop

Bionic source code released

http://sourceforge.net/motorola/droidbionic/home/Home/
I am literally in shock right now. I don't know about anyone else, but this just came out of nowhere and blew me away. Does this mean bootloader freedom?

Ooooo not sure what that means but I am not going to get my hopes up.
Sent from my DROID BIONIC using XDA App

Means nothing for the bootloader apparently...but does it possibly mean something for the proprietary firmware?

K.AuthoR said:
http://sourceforge.net/motorola/droidbionic/home/Home/
I am literally in shock right now. I don't know about anyone else, but this just came out of nowhere and blew me away. Does this mean bootloader freedom?
Click to expand...
Click to collapse
+10 i did download rhe file and scanned it and it came out clean. will look further into it

I already got my hopes up
I've got my hopes up already.

Too bad they couldn't accidentally slip the code to unlock the bootloader in there.. can we at least use bits and pieces off it?
Sent from my DROID BIONIC using Tapatalk

Motorola released this sooner than you guys would have thought because the Bionic's replacement will be announced tomorrow.

open1your1eyes0 said:
Motorola released this sooner than you guys would have thought because the Bionic's replacement will be announced tomorrow.
Click to expand...
Click to collapse
Awesome that means more people will get bionics because they will be cheaper

I don't know enough about coding to make an educated guess in this. However I am curious if the release of the kernel source code will make it easier to do research into bootloader unlocking, as the kernel seems like a proverbial key for the lock involved. Can someone who is educated add some clarity to this?

Personally, I view this as a step in the right direction on Motorola's part. Along with the recent release of the D3 source code, it tells me that they are at least half committed to keeping the platform open and developable. My theory is that they're releasing these codes in bits and pieces, while Verizon moves to get a secure hold on the tethering "issue", and that once that process is complete, we'll see all the codes roll out. I say this because I recently tried to run Wireless Tether and, instead of the app simply failing to work properly, it actually activated the VZW Hotspot app, and redirected my phone's browser to the Verizon tethering sign up page. On top of that, it also killed my data, until I did a battery pull and reboot. This tells me that VZW can and does now have a process in place to actively block usage of wireless tethering apps. I think they're in the process of trying to find a patch for the Hotspot radio hack as well, and once that's completed, they'll have little or nothing to fear, and will clear Moto to release full source codes. I may be totally wrong, but it does seem to make a bit of sense…
Sent from my DROID3 using xda premium

It may mean that some devs who like projects may find fixes for some of the nagging issues with the phone (data loss, the buzz of the headphones, etc) if they are related to programming rather than hardware.

Just as jjhiza stated. A step in the right direction. Even though moto will be releasing the razr soon.
Sent from my DROID BIONIC

Great news! Hopefully this (and the Roms coming from it) will help us all fall in love with our Bionics all over again

Crossing my fingers for accelerated development now

Update available tomorrow afternoon??

So...I know I shouldn't believe Verizon reps when it comes down to this ...but I just got off the phone with tech support manager from Verizon trying to get a different phone for my bionic due to data issues. She told if I can hang in there for a day bc new update coming out tomorrow afternoon . I asked her I then can get into a different if it isn't and she me options of any lte device out there or 3g except phone. She told I could then switch to one if update doesn't drop.
I know our community has been given a run around when it comes to updates. Just a fyi that is all.
Oh and it is not ICS its just a update fix for transition 4g-3g and 3g-4g and other "known" problems
Sent from my DROID BIONIC using XDA App

I love the first sentence of this post, lol.
Whatever may be, I hope the update comes. We'll see.
If it doesn't come, at least you can get a nexus
Sent from my DROID BIONIC using Tapatalk

http://www.droid-life.com/2011/12/0...ly-on-the-way-here-is-your-massive-bug-fixer/
Sent from my DROID BIONIC using Tapatalk

so is that the same 5.5.893 found using cheesecake and/or P3Droid posted before?

KidJoe said:
so is that the same 5.5.893 found using cheesecake and/or P3Droid posted before?
Click to expand...
Click to collapse
looks that way

Since it will be there official update, wonder if anything has been tweaked, changed, etc, from the leaked version that some of us have...

refresh my memory... which update broke webtop?

Does anyone know whether or not forever root will still be valid for this OTA (5.5.893)? I remember p3droid saying do not take any further moto updates as the exploits have been patched...but...

I had data drops 27 times today. I counted and kept track.
This update is long overdue.
Sent from my DROID BIONIC

nosit1 said:
I had data drops 27 times today. I counted and kept track.
This update is long overdue.
Sent from my DROID BIONIC
Click to expand...
Click to collapse
I'm with you on that, I go most of the day without data. I have to wait till I get home to use wifi, in lucky if my feeds update. hopefully this will correct the reboots as well.

I have been on 5.6 then 5.7.893, never did the first 5.5.893 but my data drop is definitely alot less often. Maybe only 1x or 2x a week. Its been solid for the last week. Usually when the drop occurs and needs a reboot or airplane mode cycle is when it wakes from sleep.

KidJoe said:
refresh my memory... which update broke webtop?
Click to expand...
Click to collapse
If my memory serves me correct it was 5.5. 893. They may have made some tweeks though. Someone on the forum in a previous post got the OTA a few days ago and it was 5.5.

Since it will be there official update, wonder if anything has been tweaked, changed, etc, from the leaked version that some of us have...
Click to expand...
Click to collapse
I too would like to know.
According to Verizon's lastest list of fixes for the new OTA, is suppose to fix the dreaded BSOD.
I have the leaked version and I still get BSOD. and yes, pocket protection is off.

davzava said:
So...I know I shouldn't believe Verizon reps when it comes down to this ...but I just got off the phone with tech support manager from Verizon trying to get a different phone for my bionic due to data issues. She told if I can hang in there for a day bc new update coming out tomorrow afternoon . I asked her I then can get into a different if it isn't and she me options of any lte device out there or 3g except phone. She told I could then switch to one if update doesn't drop.
I know our community has been given a run around when it comes to updates. Just a fyi that is all.
Oh and it is not ICS its just a update fix for transition 4g-3g and 3g-4g and other "known" problems
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Soooo...did you get a new phone?

chay03 said:
I too would like to know.
According to Verizon's lastest list of fixes for the new OTA, is suppose to fix the dreaded BSOD.
I have the leaked version and I still get BSOD. and yes, pocket protection is off.
Click to expand...
Click to collapse
Interestingly enough, I don't get BSODs and my in pocket detection is ON.
I'm on the leaked 5.7.893.

@renocat i have not gotten my new phone yet. I am not sure what i want to get
Sent from my DROID BIONIC using XDA App

What does it theoretically take to get back on OTA path?

So i flashed 5.7.893 to solve my data issues knowing the consequences. I also assumed that some smart dev would eventually formulate a fix to make everything peachy again when the time came. The way I understand it now is this though.
Locked boot loader makes it necessary to have signed files to update via ota path.
OTA files are designed to only update from a certain version. Ex 5.5.893 update can only be applied from 5.5.886 stock install.
So if I upgraded to 5.7.893 no official update is going to ever work because I can't flash my radio to anything official now.
I'm sure I left out or have some details wrong. But if someone has a better understanding ans cares to share it that would be great. Stop the forever speculation about getting on path again and we can all just wait for the actual fix.
The way I'm understanding it now, we need an official release from moto that specifically addresses this problem to fix it. Something I wouldn't think they are inclined to do because they don't want anyone doing it in the first place.
Sent from my DROID BIONIC using XDA App

a replacement phone. Everything else is speculation at this point.

Irony.....
1) Verizon releases a phone with very problematic data problems. For me doesn't really do much to address the issue. Still paid 30$/month for "unlimited" data.
2) Motorola lets files "leak" that could potentially fix these problems.
3) Motorola does not support these files and will tell you your wrong for using them.
Let's think about this for a second. If you put a hot dog in front of a starving man and walk away, do you really have cause to be pissed when you return to see the hot dog gone?
I have owned a wide range of "smart" phones now and come to realize that they all have shortcomings, but they all need to do a few things without fail. Make phone calls, send text messages, and connect to data services. If you are going to charge me 30$ a month for unlimited data, I should have unlimited data.
Where we wrong by using an update that wasn't official? Nah, I was starving and that hot dog had my name written all over it.

Motorola did not "let the file leak", they were pulled from their test servers by very deliberate acts of altering the firmware of the device and then scanning the servers for files and downloading them.
This is akin to stealing them and was no fault of Motorola's other than perhaps a lax cloud server security regime.
The problem comes when such methods are proliferated and made into simple tools and users are encouraged to avail themselves without sufficient warnings about the risks and responsibilities associated with that act.
Nonetheless, these are clearly our own choices and we cannot expect Motorola to even publicly acknowledge the issue, even while we hope for a solution to be provided by whatever means.

cellzealot said:
Motorola did not "let the file leak", they were pulled from their test servers by very deliberate acts of altering the firmware of the device and then scanning the servers for files and downloading them.
This is akin to stealing them and was no fault of Motorola's other than perhaps a lax cloud server security regime.
The problem comes when such methods are proliferated and made into simple tools and users are encouraged to avail themselves without sufficient warnings about the risks and responsibilities associated with that act.
Nonetheless, these are clearly our own choices and we cannot expect Motorola to even publicly acknowledge the issue, even while we hope for a solution to be provided by whatever means.
Click to expand...
Click to collapse
I call B/S. Anyone that doesn't believe that Moto could have sequestered those files is dead wrong. They were there for a purpose. And they served their purpose.
Their refusal by inaction, to support those of us who "tested" their OTA's for them is at the very least unethical.
That is the way business works in 2011. Screw the consumer, let's make more money.
RMD

cellzealot said:
Motorola did not "let the file leak", they were pulled from their test servers by very deliberate acts of altering the firmware of the device and then scanning the servers for files and downloading them.
This is akin to stealing them and was no fault of Motorola's other than perhaps a lax cloud server security regime.
The problem comes when such methods are proliferated and made into simple tools and users are encouraged to avail themselves without sufficient warnings about the risks and responsibilities associated with that act.
Nonetheless, these are clearly our own choices and we cannot expect Motorola to even publicly acknowledge the issue, even while we hope for a solution to be provided by whatever means.
Click to expand...
Click to collapse
I have read quite a bit of the hard work you've done for us sir, and I would like to say its much appreciated!
A company such as Motorola has the resources to guard the things they don't want others to have. Otherwise HTC, Samsung, LG etc. etc. etc. would always be a step ahead of them. If it was lax security on their part, they still set the hot dog in front of us...

1) The next official OTA is the leaked 5.7.893
2) An OTA down the road doesn't check the boot.img md5 and installs a full boot.img instead of just patching (I think the reason behind the requirement of having the previous version, not to spite the leak installers but to create a smaller download with just a patch).
3) Release singed zips of official OTA radio and boot (not sure why not, its not like anyone could hack these)
I would hope that at least the ICS release will require a new kernel that can't be just a patch but a full install. In that case I would also hope they would take out the md5 check.

How about the 5.9.901 OTA update that Motorola "mistakenly" pushed to users before testing was complete? They are going to have to fix that for those who received the update.
Sent from my DROID BIONIC using Tapatalk

The general thinking I have read is that the 5.9.901 update is a test for an Emergency Notification system that Moto is working on. It was rolled out to random phones for testing and wasn't intended for general release.
---------- Post added at 02:42 PM ---------- Previous post was at 02:36 PM ----------
rduckwor said:
I call B/S. Anyone that doesn't believe that Moto could have sequestered those files is dead wrong. They were there for a purpose. And they served their purpose.
Their refusal by inaction, to support those of us who "tested" their OTA's for them is at the very least unethical.
That is the way business works in 2011. Screw the consumer, let's make more money.
RMD
Click to expand...
Click to collapse
That's kind of a warped way of looking at it. What were people doing poking around in their servers? Are you one of those guys that feels like anything is yours for the taking if the door wasn't locked?

While annoying moto told me that if you applied the leaks it didn't void the warranty so you can send it to them and they will get it back on the update path. Def annoying but there is a way back
Sent from my DROID BIONIC using XDA App

dagostin said:
While annoying moto told me that if you applied the leaks it didn't void the warranty so you can send it to them and they will get it back on the update path. Def annoying but there is a way back
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Very bizarre and impressive that they support this.

Some people in this thread claiming they were able to get back to the upgrade path. From 5.7.893 to .886 stock then ota to 5.5.893
It's alot to read through.
http://rootzwiki.com/topic/12749-getting-back-on-the-ota-update-path/

dagostin said:
While annoying moto told me that if you applied the leaks it didn't void the warranty so you can send it to them and they will get it back on the update path. Def annoying but there is a way back
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Well this is good news if the Moto rep is correct!

Method works. I myself am backon update path now.
Sent from my DROID BIONIC using XDA App

New Leak .235

I didn't upload. @unchoney over at droid hive uploaded to here.
http://www.megashare.com/4392491

josdad00 said:
I didn't upload. @unchoney over at droid hive uploaded to here.
http://www.megashare.com/4392491
Click to expand...
Click to collapse
If you install this you CANNOT go back to GB ever.

mattlgroff said:
If you install this you CANNOT go back to GB ever.
Click to expand...
Click to collapse
And why is that? I've been running SamauriHL's script to keep my data and update since .2233

zoompastu said:
And why is that? I've been running SamauriHL's script to keep my data and update since .2233
Click to expand...
Click to collapse
Because the FXZ back to .902 is BLOCKED on the new release.

Worse yet, you can't go forward without a full 905 or ICS FXZ, either. If you do this leak, you WILL be stuck. If you attempt to FXZ to 902, you will soft brick your phone. You have been warned.

Dumb. You would think that our feedback on the leaks might help MOTO's development. It's as if they locked this one down as some form of revenge...
Glad I didn't update yet. I'lda gone nuclear.

It's the same thing they did on the D4 and RAZR. Except they had an FXZ for the version they were updating to ICS from. We don't. If we had a full 905 FXZ we could make this work to go forward. Once on 235+, however, there's NO going back to GB ever. And right now without an FXZ for 905 or the OTA ICS, 235 ain't going forward, either. That's what I call BAD.

Does someone have some method of completely obliterating data and dropping back the FXZ or some other form of information? Even if it's just some sort thing that only they can do.
Man, I don't get this one.
I'm not doing this one, that's for sure. Is ANYONE going to do that?
Thanks for the warning though!
and I feel bad for the poor fool who had to find out the hard way that it was a finality.

No one HAD to install it to find out. We ran the security checker on it and it showed us what we were dealing with. The person who posted the initial link did get impatient and installed it before we were able to check it. Now he's stuck.

BasPilot said:
...and I feel bad for the poor fool who had to find out the hard way that it was a finality.
Click to expand...
Click to collapse
I almost was that fool. I downloaded the file and hit the refresh button to see if there were anymore posts before updating my phone. Glad I did!

zoompastu said:
I almost was that fool. I downloaded the file and hit the refresh button to see if there were anymore posts before updating my phone. Glad I did!
Click to expand...
Click to collapse
Same here but I was lurking Droidhive and found out there was no going back lol

SamuriHL said:
No one HAD to install it to find out. We ran the security checker on it and it showed us what we were dealing with. The person who posted the initial link did get impatient and installed it before we were able to check it. Now he's stuck.
Click to expand...
Click to collapse
Well that's good for most people, and good that it was able to be spotted before too much damage was done over all...
I am just failing to see the logic of putting out an open source piece of software that locks you into it. The only thing I can see is that the leaks have bothered the OS builder and this is their way of stopping us from using them.

By the way Thank you SamuraiHL for that Awesome script you wrote to update with these leaks. Works GREAT!!

BasPilot said:
Well that's good for most people, and good that it was able to be spotted before too much damage was done over all...
I am just failing to see the logic of putting out an open source piece of software that locks you into it. The only thing I can see is that the leaks have bothered the OS builder and this is their way of stopping us from using them.
Click to expand...
Click to collapse
I can give you the logic. 235 is most likely a release candidate that they feel strongly will be the OTA. And moto has put a frack ton of effort into getting all the ICS builds on the different devices to be the same. This is less of a support headache for them. By locking devices to ICS only, the support costs go down for both moto and VZW because the builds are functionally identical. That's my guess.
---------- Post added at 02:13 PM ---------- Previous post was at 02:12 PM ----------
zoompastu said:
By the way Thank you SamuraiHL for that Awesome script you wrote to update with these leaks. Works GREAT!!
Click to expand...
Click to collapse
You're very welcome.

SamuriHL said:
I can give you the logic. 235 is most likely a release candidate that they feel strongly will be the OTA. And moto has put a frack ton of effort into getting all the ICS builds on the different devices to be the same. This is less of a support headache for them. By locking devices to ICS only, the support costs go down for both moto and VZW because the builds are functionally identical. That's my guess.
Click to expand...
Click to collapse
Can't they just end support for that saying you need to upgrade to our latest software and this will fix most of your problems if not all?
Either way, correct or incorrect on your part, it'll be fun to watch ideas thrown around by people and it will REALLY be fun to see one of you geniuses come up with a way around it. You know you will. 24 hours and one of you will crack the nut.

Don't look at me! I'm not one of those geniuses. You're talking about people like mattigroff, cellzealot, p3droid, dhacker, etc. Those are the guys who will crack this issue. What we REALLY need to solve this is the damn 905 FXZ. I've put out a request for it but I have no idea if I'll hear back from the person I asked or even if they have it. If we had that, we have a way forward.

BasPilot said:
I am just failing to see the logic of putting out an open source piece of software that locks you into it. The only thing I can see is that the leaks have bothered the OS builder and this is their way of stopping us from using them.
Click to expand...
Click to collapse
Agreed.

Open source doesn't mean that you can change the finished builds of the software or roll back after you install an update, it just means that you can make your own version using the source. The OS itself is open source, but the phones don't have to be fully open, and none of Motorola's since the DROID have been, at least on VZW.

BasPilot said:
Well that's good for most people, and good that it was able to be spotted before too much damage was done over all...
I am just failing to see the logic of putting out an open source piece of software that locks you into it. The only thing I can see is that the leaks have bothered the OS builder and this is their way of stopping us from using them.
Click to expand...
Click to collapse
The problem is your trying to talk logic while talking about Moto. Experience shows the two don't play well, people have been warning this would probably happen sooner or later throughout the ICS leak cycle.

Well, some of us theorize this marks the end of the ICS leak cycle and represents what's likely to be the soak candidate, but, we'll have to wait and see.

VZW Halts OTA

I just got off the phone with VZW. Apparently, they've stopped rolling out the OTA because of "software issues," though he didn't specify beyond that. So, for all of you who have been waiting for the OTA over the past few days, off the top of his head, the tech guesstimated it'll be around a month before they begin rolling it out again. Lame.
Edit: You can still install the .217 leak...but if the update has been pulled for software issues, that obviously means .217 is no longer the official OTA.

What? thats BS! even though im on Eclipse ICS 1.2, its still BS for anyone still on GB!

alex94kumar said:
What? thats BS! even though im on Eclipse ICS 1.2, its still BS for anyone still on GB!
Click to expand...
Click to collapse
Yeah, I've been mashing the "systems update" option habitually now for a couple days, but also avoided just manually updating to the .217 leak for this very reason. Either way, it is kind of disappointing.

honestly, if I were you, I would jump on either the 217 leak, or if you want a custom rom that's slightly themed and has extra features/no bloat, go with Eclipse

It wasn't supposed to be released for the general OTA, they did that on accident, only people who were signed up for the motorola feedback network test were supposed to get it, but for some reason they pushed it to all devices. It should be officially pushed in a week or so, because it appears the soak test isn't showing up any major issues.
Sent from my DROID4 using xda premium

EDIT: Did NOT work
I called VZW tech support earlier today because it was not working and they did not mention anything about it being halted, but it probably depends on which tech you speak with.
I am not sure if this works or not but the guy I spoke with did tell me that performing a factory reset can sometimes trigger the upgrade. I don't have anything on there that I can't live without or easily re-install so I am going to go ahead and give it a shot.
EDIT: Just tried above. Did NOT work

Rafterman414 said:
EDIT: Did NOT work
I called VZW tech support earlier today because it was not working and they did not mention anything about it being halted, but it probably depends on which tech you speak with.
I am not sure if this works or not but the guy I spoke with did tell me that performing a factory reset can sometimes trigger the upgrade. I don't have anything on there that I can't live without or easily re-install so I am going to go ahead and give it a shot.
EDIT: Just tried above. Did NOT work
Click to expand...
Click to collapse
As mentioned above, there was no planned general release yet. Moto did a release for "a few thousand" phones, of which only a small portion are official MFN soak testers. The test will end soon, and it looks like no show-stopper issues have been found, so, if things go as usual, the general release will roll out, probably in groups, over the next several days.
Sounds like the OP spoke to someone in VZ who really didn't know why the release wasn't available and made something up. (And I bet you never thought a VzW rep would do that!)

Keep in mind, even if they had decided to halt it due to a showstopper bug, they've already released it to several thousand owners. Which means they're obligated to provide anyone on .217 with a way to get back onto the upgrade path, if they decide to release a newer update down the road.
All in all - if you're impatient, just install the current .217 files - you'll still be able to upgrade again later if you need to.
Btw: I'm on it now, and I ABSOLUTELY HATE the Dialer and Contacts being split apart into totally separate apps. I always hit the Dialer icon first, and then if I can't remember a person's phone number, I now have to back out of it and look up the contact first. Whereas on GB I just had to select the Contacts tab and go on. So from a human interface perspective, this new design sucks.

highlandsun said:
Keep in mind, even if they had decided to halt it due to a showstopper bug, they've already released it to several thousand owners. Which means they're obligated to provide anyone on .217 with a way to get back onto the upgrade path, if they decide to release a newer update down the road.
All in all - if you're impatient, just install the current .217 files - you'll still be able to upgrade again later if you need to.
Btw: I'm on it now, and I ABSOLUTELY HATE the Dialer and Contacts being split apart into totally separate apps. I always hit the Dialer icon first, and then if I can't remember a person's phone number, I now have to back out of it and look up the contact first. Whereas on GB I just had to select the Contacts tab and go on. So from a human interface perspective, this new design sucks.
Click to expand...
Click to collapse
When your in at the dialer screen just push menu then search it goes to your contact list. So its a matter of hitting 2 buttons but you can get to it from dialer. I also miss the other way but im getting used to this and it doesnt bother me anymore
Sent from my DROID4 using xda premium

It's happened to me twice now in the last two days that I was unable to hear the people calling me. Switching to speaker mode or rebooting the phone fixed this. Actually only rebooting. Alternating between speaker and normal mode is just a temporary fix as long as I'm in speaker mode. Plug in the headset and it works. Take it out en again no sound... I think it happens after I use BT.

Maybe people who are on this update officially could raise a bit of fuss about this and ask to be put back onto Gingerbread?
As we all know this currently can't be done due to the highly restrictive bootloader, perhaps we could wangle a better bootloader out of this?

Lum_UK said:
Maybe people who are on this update officially could raise a bit of fuss about this and ask to be put back onto Gingerbread?
As we all know this currently can't be done due to the highly restrictive bootloader, perhaps we could wangle a better bootloader out of this?
Click to expand...
Click to collapse
Well, we can certainly dream, but given a choice between unlocking the bootloader and shrugging apologetically and insisting nothing can be done, I'm dead sure Verizon will require Motorola to do the latter. :crying:

Installing OTA right now on my wife's D4
Sent from my DROID BIONIC using xda premium

Seems like more people are getting it now. I just got too antsy and went ahead and installed the .217 leak floating around, I bet if I had waited another day I could have gotten the OTA. Hopefully I did not ruin my ability to get future OTA updates.
Sent from my DROID4 using xda app-developers app

Rafterman414 said:
Seems like more people are getting it now. I just got too antsy and went ahead and installed the .217 leak floating around, I bet if I had waited another day I could have gotten the OTA. Hopefully I did not ruin my ability to get future OTA updates.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
You didn't. .217 is .217 no matter how you got it. Anyone on the "leaked" .217 is on the official update path as that is what was pushed as OTA.

tcrews said:
You didn't. .217 is .217 no matter how you got it. Anyone on the "leaked" .217 is on the official update path as that is what was pushed as OTA.
Click to expand...
Click to collapse
If you had a nickel for every time you had to tell somebody that you could probably retire! LOL
Droid 4 - AOKP K1L0

Update fails anyway
I received the update this morning, and after attempting to install, it fails within 30 seconds and reboots. I factory reset, erasing everything, downloaded the update again, and same result. Anybody have any information on this? I pressed the volume up button and it says:
Verifying current system...
assert failed: apply_patch_check("/system/app/music2.apk", "cbb199983ab1cb9beee6b20ec4db659ccd49d757", "25d8789a15715fdd931ef2a2ee93b637bfef06b0")
E:Error in /cache/Blur_Version 6.13.219.XT894.Verizon.en.US.zip
(Status 7)
Installation aborted.

Saloobian said:
I received the update this morning, and after attempting to install, it fails within 30 seconds and reboots. I factory reset, erasing everything, downloaded the update again, and same result. Anybody have any information on this?
Click to expand...
Click to collapse
Just install from a PC via FastBoot.
ROM: http://sbf.droid-developers.org/cdma_maserati/list.php
Instructions: http://www.droidforums.net/forum/dr...otorola-droid-4-xt894-stock-windows-only.html
Note. Do not download one of the two ROMs that post suggests, use the 217 ROM from my link above. Do not attempt to downgrade via this method either, it will not work. You might also want to skip steps 6-9 if you don't want to reset your data. Not sure how well this will work after an upgrade.

The soak test is over and "the software is officially released and will be rolling out in stages"....
Sent from my DROID4

:good:
Fantastic! I restored to stock and downloaded the update again, and it's currently installing without a hitch! Thanks!