yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] limaxray:
Having read the updater script and most of the recovery source, I'm 95% sure the next official OTA will fail after applying this update (the remaining 5% being that this turns out to be the next official update). As for working around it, no one can say in any meaningful way until we see the official update.

If an sbf does drop, you'll be all set.

And if not, I'm fairly comfortable we'll be able to work around it, but I won't put a number on it. There are still some outstanding uncertainties that could be show-stoppers (ie the boot image is patched which may make it difficult to get it to pass checksum on the official OTA)

Otherwise, there's little in terms of immediate dangers. If you're rooted and have put stuff on /system, there's a risk you can screw up your camera and recovery, but it's totally fixable.

In other words, I doubt you'll be boned if you use this update. It will probably only mean getting the official update will be slightly more difficult. As long as you understand the risks, I think its well worth the upgrade.
[Motorola Droid 3] limaxray:
Yeah I noticed that. It makes sense since the mbmloader is the only thing that is really different between the devices. The first 512 bytes of the mbmloader is the configuration header which is needed by the boot ROM and probably differs between HS and NS devices.

mbmloader is also really the only signed component - it then checksums mbm, which checksums lbl, which checksums boot/recovery. Once mbmloader is running, everything else is the same so there is no need for multiple version of everything else.
[Motorola Droid 3] despich:
Foto.apk problem

Just FYI in case someone else has this problem. When I tried to install the update I got a Error in system/app/Fota.apk and could not install the update.

Here is all I had done to my phone up to that point.

- Rooted using the psouza4 "one-click root for Droid 3" used the older version before the 9/1 update.

- Updated BusyBox from the market

- Uninstalled and reinstalled Slacker from the market

- Ran the psouza4 "Safe Bloat removal Script" to remove bloatware via the Scriptmanager app the version before the 9/1 update.

- Uninstalled the Slacker I had installed from the market.

- Downloaded the Newer safe bloat removal script (the post 9/1) version and ran the restore Bloat script.

To fix it:

- found my Fota.apk was still Fota.apk.bak (same with Fota.odex)

- Used Root explorer to rename the files back

- Installed the update successfully (did not wipe anything beforehand) first boot took a long time

- Rerooted using the newer psouza4 "One Click Root" the 1.03 "exe" version.

- USing Titanium converted slacker app to user app and then updated from market.
[Motorola Droid 3] kshen1:
I just didn't want everyone to be mad if it came out that we don't get one today. But we will only see!
[Motorola Droid 3] kishin14:
Even if it's not today, my money's on TBH getting a workaround, if not a full blown SBF before the official OTA drops. They are the best dev support team on the planet.

I bought their app for their DX mods and files before it was taken off the market and they were able to find upgrade solutions to EVERY leaked file that ever dropped for that phone. I know moto/verizon are making it harder, but devs are also getting smarter. This leak, even if it wasn't official, could turn out to be the best thing that happened to the D3 if it gives devs insight on what the powers that be are up to.
[Motorola Droid 3] slow88lx:
I love TBH like everyone else, but with p3droid not being able to do any work on the D3 and Verizon keeping the SBF files out of local stores....I will not be holding my breath.
[Motorola Droid 3] kshen1:
dunno if adamogle would like me sharing, but he found another 5.6.999 file last night, apparently the same way scott found 5.6.890. We were extremely excited and he loaded it upHowever, when updating from 5.6.890 to 5.6.999, he bricked his phone and is now stuck in fastboot mode. Apparently one of the files weren't signed or something. Sucks ):
[Motorola Droid 3] kishin14:
Well, I'm still holding out hope. P3Droid seems to be all about the bionic and is selling all his other phones. But he's not selling the D3 since that his wife's phone. And the bionic and D3 share many of the same hardware internals, which might make modding for one a good place to start for the other. Besides, if he is successful doing cool stuff with the bionic, curiosity might get the best of him and he may start tinkering with his wife's phone again. Wishful thinking? Perhaps. But I've always been a glass half full type of guy :)
[Motorola Droid 3] Dmw017:
Your reasoning makes sense (i.e. it's not just blind optimism)

I dunno why the Bionic is becoming so glorified. It isn't exactly the nicest looking phone or (its hardware) anything to marvel at. I hope its just a hype beast (which die out quick).

Divide by zero, I dare you...
[Motorola Droid 3] cellzealot:
We both have D3s and will be getting Bionics as well and fully intend to work with both devices.

P3droid has an extra D3 that is not his wife's phone, so he will be able to play around without risking his marital bliss in the bargain.

It is important for everyone to understand that we cannot provide the same level of support for these newer Motorola devices that we could for previous models like the DX and others because we no longer have access to all of the internal files that we used to. We had everything we possibly needed or wanted for those devices, except an unlocked bootloader of course, directly from the Motorola software development engineers. This gave us a huge advantage and allowed us to do many things we couldn't have otherwise and we had unsecured engineering phones for all of those models as well.

We have a great deal of experience manipulating the firmware and with access tools and methods which we can bring to the table and a good understanding of the radio NVM, but we are not magicians. We will be here contributing to the community knowledge base like many others, but we aren't going to be playing masters of the universe.

We still have a lot of resources and a great deal of trust built up in the community that we value highly, we just want to be sure that people's expectations don't exceed our abilities.

OK? ;)
[Motorola Droid 3] Dmw017:
Sir your post kicked ass.

That is all.

Divide by zero, I dare you...
[Motorola Droid 3] kishin14:
Magicians you may not be but you guys still deserve applause for your risk taking efforts. Good luck and happy modding.
[Motorola Droid 3] kshen1:
Well guys, it looks like Psouza4 is a magician. Just got notice of how to unbrick your d3 using a partial SBF. Hint Hint chinese.

he's still testing it as of now, so

you can get your hopes up! (finally lol)
[Motorola Droid 3] slvrarrow:
would this be making use of that xt862 file i linked to? id be over the moon if it was it was such a nooby google session and i thought this might help :P haha noobs can contribute! (maybe :P)
[Motorola Droid 3] suzook:
Any idea when we might see a release? I want to fool around with my theme on the leaked dev update, but will wait till we have a way to unbrick.
[Motorola Droid 3] kshen1:
theres a lot of stuff that needs to be uploaded, and psouza4's at work right now. after it's done uploading, he needs to test it.

i'd say maybe tonight :P
[Motorola Droid 3] kshen1:
theres a lot of stuff that needs to be uploaded, and psouza4's at work right now. after it's done uploading, he needs to test it.

i'd say maybe tonight
[Motorola Droid 3] ctheory83:
It looks like i'm SOL with this phone anyways at the moment, so i'll be jumping into the IRC chan tonight and whoring myself out to the SBF holders to see if we have something useful.

I knew I shouldn't have dicked around so much :P
[Motorola Droid 3] kshen1:
We have a fix for you on the way. Be patient
[Motorola Droid 3] ctheory83:
Of course brother, i'm a little rusty on the *nix side to help out but if I can be a crash test dummy for you, **** it, i'm in, just let me know what you need.
[Motorola Droid 3] moskey71:
It's not a stretch. I got 16-18 hours of usage everyday. I installed the update and charged the phone when I went to bed. The next day I used the phone like normal, and didn't need to charge when I went to bed. The next day it lasted the entire day. YMMV, but for me... the change was insane.
[Motorola Droid 3] sparkyman216:
I am sol to as everyone by now knows. Lol
[Motorola Droid 3] despich:
Battery great!

For those that managed to get the update and got it installed without issues I just have to put in my 2 cents in to say it was worth it for me. battery life REALLY is much better after the update. I have only had it a couple days but I estimate at least a 25% improvement and I am a pretty consistent user so the fact that I still have 80% battery when I am going home at the end of the day is a huge change for me. I was almost always at less than 50% before.

Battery life used to be my biggest complaint with the phone, not anymore.

Dan
[Motorola Droid 3] suzook:
Did anyone here that did the hotspot app hack have any problem applying the update?
[Motorola Droid 3] kshen1:
I know the hotspot hack messes with some things, such as being unable to access ADB when using the BP tools method
[Motorola Droid 3] cellzealot:
That is entirely untrue. I have had the hack applied on my D3 from the first hour I had it and have both rooted and recovered from softbrick using the BP tools adb access method without any problem whatsoever. There is no reason to believe that the hack would have any effect on an OTA update and it has never prevented nor interfered with any updates on any previous devices.
[Motorola Droid 3] kshen1:
someone in the irc said that they were bootlooping, wiped data(lost adb), and had the hack apply, no matter how many times they did the bp tools on the computer it wouldn't detect the phone

Then he tried it with another d3 and it worked on the same computer
[Motorola Droid 3] somemadcaaant:
I'd say they did something different or correctly on the second D3.

-smc
[Motorola Droid 3] rynosaur:
I was never able to obtain root access in BP Tools mode, Windows or Linux, tweaked drivers or udev usb access mode, never mattered. Not all phones of the same model are created equal, everyone should know that by now. Hell, from what I understand not all Moto USB cables are created equal, according to TBH . . . correct me if I'm wrong :)
[Motorola Droid 3] kshen1:
Dunno, you could be right....
[Motorola Droid 3] somemadcaaant:
Agreed and it's always easier second time thru :p

-smc
[Motorola Droid 3] suzook:
Thanks. Ill give it a go tonight.
[Motorola Droid 3] wattnxt:
OK. So I too BORKED my system update. I only found out today when I tried to use my camera and....ta da....same thing.

I could not use the same adb commands, I got errors every time trying to remount. But I was able to do the following:

I extracted the Update Zip to a folder on my PC.

Copied recovery/recovery-from-boot.p to /sdcard

Used Root Explorer to move recovery-from-boot.p to /system/recovery-from-boot.p

changed owner and group to root

changed permissions to rw--r--r

in adb shell:

su
sh /etc/install-recovery.sh

rm /system/bin/su
rm /system/xbin/busybox
rm /system/xbin/su

reboot recovery

easy peasy lemon squeezy! LOL.

Nice to know I had company on my Bork!

Freespace in /system/ should be a check before the update tries to apply.

Hint Hint Moto...could be a lot of borked units.

Thanks Much!
[Motorola Droid 3] rynosaur:
How dare you suggest that the great Moto would take advice from us hacker/slackers ;)

I'll bet they have a third the of phone's NVRAM tied up in /cache like the original G1 did, rather than give /system what it needed ;)
[Motorola Droid 3] wattnxt:
I bow my head in shame at the mere suggestion that the great and almighty Motorola could be anything less than omnipotent and benevolent....

We will see if my battery life now goes up even more now that the slacker/hacker in me has repaired the damage to the great and already perfect Motorola Droid 3 device that Moto has graciously allowed me to purchase and hold in my unworthy hand.......ROFLMAO!!!

We worship his shadow....ha ha ha.

All is right with the world again.
[Motorola Droid 3] Dmw017:
Im fairly certain the big bad Moto you're referring to just makes the hardware while Verizon locks it down and wtfbbqowns it with bloatware

Ssoo.. come at them, bro?

Divide by zero, I dare you...
[Motorola Droid 3] kishin14:
Well what do you know? This IS the official OTA. Here's the link to the support page pic from droid-life:

http://www.droid-life.com/wp-content/uploads/2011/09/droid3-update.jpg

You can clearly see the version number as the same as the leak. Awesome.
[Motorola Droid 3] kshen1:
Yes, but the build numbers might b different. They probably are..
[Motorola Droid 3] somemadcaaant:
Yeah it would have to be different now, if only for VZW to save face about the community finding it, using it and already customizing it before any official acknowledgment / release lol.

Damn good update tho, had an evil thought the blue camera tint was hardware related but sure enough was fixed.

-smc
[Motorola Droid 3] elkay:
Yep, apparently so. Seeing that, I went ahead and bit the bullet and installed the update and re-rooted. No problems at all. Simply unfroze all my apps, applied both, and refroze. We'll see how this update affects battery life.
[Motorola Droid 3] Raa_1:
So question, does this OTA update do the same changes as the full update in the other thread? Like the radio/etc, not just system/file changes?

To answer my own question : yes it updates everything by the looks. Running nicely!
[Motorola Droid 3] suzook:
Did the update yesterday. You guys are nuts thinking the batt life has gotten that much better. The batt life was acceptable before, and imo is exactly the same on the newer sw.
[Motorola Droid 3] `Ghost`:
im extremely disapointed with the OTA. It has made my camera run and look like crap. Pictures dont focus as well, and the video... well pre ota the phone in low light or even a pitch black room would never dip below 20fps.. Now the camera records at 12 fps in the same conditions. unacceptable. I'll take the blue tint over even crappier pictures and video

currently looking for a way to go back to stock.
[Motorola Droid 3] Dmw017:
Yeah I think that's just your device cuz the camera takes pics that are sexy beyond all reason and the camcorder records like a champ with framerates smooth and steady. Try a different camera app

Divide by zero, I dare you...
[Motorola Droid 3] `Ghost`:
what apps can let me still record in 1080p? maybe its the stock camera program that got all infested with aids from the OTA.
[Motorola Droid 3] Rick#2:
So, has anybody with a Bell XT860 figured out how to get this running on our hardware? I tried to just flash the system.img from the update but obviously that was a bad idea, hehe. Wonder what would need to be done.
[Motorola Droid 3] jfourman:
Was Unclear about which Recovery - Stock CWM

I am requesting some education so I am better informed for the future...

After some trial and error, I was successful in upgrading to the leaked OTA (5.6.890). At first, I kept trying up flash the update from my external SD card using Clockworkmod Recovery. It would find the update.zip, open the package, begin the install and then error. Scanning this thread, I finally discovered how to get into stock recovery using Power + x, hold vol-up while pressing vol-down... Using this method, the upgrade ran to a successful completion. Does the installation of an OTA ROM require using stock recovery or should I have been able to update using CWM? I expect that the instructions of which recovery to use from the OP were probably removed when the download was removed. ...or should I have known this as a matter of course?
[Motorola Droid 3] :
Any idea if this update fixes the camera's blue tint problem?
[Motorola Droid 3] buckmarble:
Do i have to rename the file?
[Motorola Droid 3] suzook:
No. It dosnt.
[Motorola Droid 3] buckmarble:
Can someone help me?
[Motorola Droid 3] rweckhoff:
Rename to update.zip and place in root of SD card. If using Windows, make sure it doesn't name it update.zip.zip
[Motorola Droid 3] scottml:
I should have said in the original post your "external sd card".

There's some confusion over the /sdcard vs. /sdcard-ext.

Put it on your "/sdcard-ext" which is mounted as "/sdcard" in recovery. And the name doesn't matter you'll be able to select it from the directory listing.
[Motorola Droid 3] Abradax:
If you made any changes to your build.prop file, you have to change it back before you can update.
[Motorola Droid 3] aross6:
Anyone try applying this update while rooted WITH the bloatware renamed or deleted? If so, did the update apply successfully? Thanks in advance for the heads up!
[Motorola Droid 3] jab476:
You don't have to rename it to update. It's not like before.
[Motorola Droid 3] Xenoproctologist:
Just tried (inadvertently). The update runs a filesystem check and fails out if the files are missing. Don't know whether it checksums them or not...
[Motorola Droid 3] whoopsiedaisy:
could we somehow swap out apks and junk& make this into a rom?
[Motorola Droid 3] wuwtk:
I deleted a bunch of bloatware to the point were my phone was softbricked, and this update restored all the bloat i deleted and mad my phone back to normal.
[Motorola Droid 3] kep0ne:
tried to flash this...fails on file check i believe.

'assert failed: apply_patch_check("/system/app/BlurTasks.apk", "f4eede470fc50696da8fb4305d2521b86b93fdb3", "c16e3830230ed5ebec5328a8d75a1b3d453174a4"

E:Error in /tmp/sideload/package.zip

(Status 7)

Installation aborted.'

im not sure what this means; i did replace my BlurTasks.apk with the one from the system dump, as well as change the permissions, but still no luck.

this might be the best, as there is no way back to stock from this OTA (for future updates), correct?
[Motorola Droid 3] SnowDeath:
Looks like md5 checksums to me - phone will need to have all stock files that the update includes lest it fail.
[Motorola Droid 3] buckmarble:
Okay, so I can definately tell I came from a d1 because that had no internal storage and when I tried to flash it from the "sdcard" on the d3 it didn't even occur to me that it wasn't an external sdcard and to try an external sd. So anyway, I put the sdcard from my d1 in and put it on there (sdcard-ext) and all is good. I got it flashed just fine and rerooted.
[Motorola Droid 3] ubermetroid:
Yep!

I did the same thing. Good to go. Plus, I never "unfroze" the bloat ware and it worked just fine.
[Motorola Droid 3] 640k:
just curious how big the file is. 250mb (ish)? file sharing sites are blocked @ work and my phone won't let me download the file either (or the site blocks the browser).
[Motorola Droid 3] tcrews:
57.6 MB (60,489,728 bytes)
[Motorola Droid 3] sparkyman216:
I just wish my computer would see my phone
[Motorola Droid 3] bizzshow26:
Renamed all my bloat apps back used rootkeeper and temp unrooted flashed this without a hitch then I restored root with rootkeeper once I was up and running battery life seems a little better on 3g but I have to give this a few days to pass final judgement
[Motorola Droid 3] wuwtk:
I am unable to root after this update, at least using the one click root method, is anybody else having better luck? and if so how?
[Motorola Droid 3] Droid2Life:
This is what happened to me, except it kept hanging up on the MOTOPRINT.apk. I resinstalled all the apk's with pzou4s script but even then it still didn't work. Stumped at this point.
[Motorola Droid 3] jediman:
Here is the million dollar question.

Given that this is from the soak test going on, and given the quick track record of pushing out a soak test version as an official ETA, would it be really safe to flash to this or just wait?

Safest bet is to always wait but I wonder if a)this is technically the official OTA or b)is there an upgrade point from there.. I would think there is an upgrade point given it's being used in a soak test.
[Motorola Droid 3] buckmarble:
I used the v7 script to root and worked just fine. Just have to make sure you unlock the phone pretty much as soon as it boots back up or the script messes up.
[Motorola Droid 3] thingonaspring:
@jediman

If this is a soak test version - won't it be available as an SBF in due course?

For my part, I'd prefer to wait until an SBF is released before fiddling with my phone any further (already rooted and de-bloated).

Having no ability to flash back to a good version of the phone makes me very nervous - especially as I live in UK and imported my D3, so I can't send it back to verizon for repair.
[Motorola Droid 3] limaxray:
I applied the update to my D3. I restored everything I previously removed and removed su prior to the update. It applied without issue and was able to reroot and debloat afterwards.

I am having trouble with the camera. It fails to start and causes the camera app to crash. Is anyone else having these troubles?
[Motorola Droid 3] Darksurf:
Does this mean if we flash this, we cannot flash the sbf when verizon has their update?
[Motorola Droid 3] 640k:
are you sure you didn't de-bloat too much? it's difficult to determine if something is wrong with the update after you've made modifications.
[Motorola Droid 3] limaxray:
I agree, but I used psouza4's bloat removal script and have since restored it to no prevail.

I'm more concerned about the binaries I replaced with links to busybox, which I should have undone previously.

So does this mean everyone else's camera works just fine?

In other news, the GPS is fixed so in now gives satellite data.
[Motorola Droid 3] spectrumfox:
Yes, my camera works fine for pictures and video after applying the update.

I am also not rooted and haven't removed any bloatware.
[Motorola Droid 3] 640k:
can someone host the update temporariliy so i can dl the file? all free file sites ae bocked here. tried hosting it from home, but also blocked. even tried back door.

phone doesn't even attempt to download it.... unless...

EDIT: ahh...looks like the browser hates .zip extensions. renamed to .txt and am dl'ing now.
[Motorola Droid 3] whoopsiedaisy:
dl the app linda file manager and turn the dl plugin on
[Motorola Droid 3] kep0ne:
thats the thing, it does have all the stock files, from the system dump. so im not sure why it would fail.
[Motorola Droid 3] jediman:
This is what I wan't to know.

If this is from the soak test for sure, then I would imagine that they could SBF to the official stuff and have an upgrade point from there as Moto/Verizon would have to support those users.
[Motorola Droid 3] tcrews:
Wow...I hate to sound stupid but are there any indications or options in Recovery?

On my old Droid, the stock recovery would show something going on. Clockwork gave you menu options.

I put the file on my /sdcard-ext (at the root of that folder) and boot in to recovery and it just sits at the Triangle/! and Droid. Nothing going on that I can tell and no keys seem to bring up any menu choice (install from /sdcard, etc..).

Missing step??
[Motorola Droid 3] Abradax:
On that screen push and hold volume up, then hit volume down.
[Motorola Droid 3] aross6:
Just a side not to anyone who is considering doing this... if you renamed your bloatware to .bak you must rename it back to .apk before doing the update; if not, the check sum of the system files fails and it aborts installation. It doesn't hurt the phone if you miss renaming one either... it just aborts installation and then you can reboot, rename, boot into recovery and update. Just a heads up :D
[Motorola Droid 3] aross6:
If there was a SBF floating around out there the Dev's would surely have it by now... but (personally) I don't think we'll have any issues updating to the official release so long as the system version number in the official release is higher than the one in this leaked release! Plus, eventually, we'll have bootstrap and custom recovery for our handsets so we can upgrade/downgrade roms as we see fit too!