yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] tcrews:
Great, lost root.

one click reports success, no root.

manually I gain root via adb shell, push su chmod it, push superuser, etc...no root for any applications nor do I have the ability to grant SU to any apps.

Reboot, no root.

**EDIT**

Had to use the temp ADB shell root access to completely remove su, Superuser and busybox. Rebooted then re-ran the one-click. rebooted when all was done, ROOT access is mine again!!

Adding SU access to my root apps again.
[Motorola Droid 3] scottml:
This file *IS* what the soak users got as their update.

So, if Motorola decides that they want to keep working on the update and release an even newer one later, instead of pushing 5.6.890 to the masses then they will have to have an upgrade process for the soak users which have already updated to 5.6.890.

I know when I was debugging the "check_for_upgrade" service, it submits your build version when it performs the upgrade check, so the response back is personalized to your current build.

So the process goes like this for 2 different users:

User A(running 5.5.959) checks for upgrade and gets the verizon.en.US.5.5.959->US.5.7.0-update.zip

User B(running 5.6.890) checks for upgrade and gets the verizon.en.US.5.6.890->US.5.7.0-update.zip
[Motorola Droid 3] Xenoproctologist:
I had the same issue. Turned out I had redundant copies of su in /system/xbin and /system/bin, thanks to Superuser.apk pushing its upgraded version of su to a different location than I had originally put it. Once I set permissions and ownership properly on the copy in /system/bin, everything worked just fine.
[Motorola Droid 3] moskey71:
Here is my experience with the OTA I downloaded from this thread.

I had my phone rooted and used Titanium backup to backup and then freeze all the bloat I didn't want.

Installed the update.

Redid the one click root. It worked on the first try. When I loaded up Titanium backup, everything I originally had frozen was still frozen.

AWESOME!
[Motorola Droid 3] wuwtk:
How would go about setting up the temp ADB shell root access? Im still new at this and learning :(
[Motorola Droid 3] reaverclan:
alright when i go into recovery (power + x) i get the android with a exclamation point only why? the file is update.zip on root of my sdcard-ext.
[Motorola Droid 3] jediman:
So here is what I ended up doing.

1 - used the script from psouza and restored the bloat apks

2 - rebooted

3 - ran one-lick root (cause I wanted to make sure I had done it right)

4 - booted into recovery mode and flashed the update

5 - kept fingers crossed and everything came back up

6 - noticed that the camera opens smoother now and per my eyes it looks like the blue tinting is kinda gone now..whites are whiter anyways

7 - Re-rooted
[Motorola Droid 3] tcrews:
Hold Volume + and then (still holding) tap Volume -

That gets to the menus in Recovery.
[Motorola Droid 3] reaverclan:
Thanks it worked.
[Motorola Droid 3] magicelf:
After reading this entire thread, I am still a little unclear and would like it cleared up before I attempt this update:

I used the original (not v.7) one click root and psouza's bloatware renaming script.

1. Other than using the reverse script to restore the apks, do I need to do anything else before applying this update?

2. Do I need to un-root (and if so, how do I do that)?

3. Do I need to reinstall the NFL, Zumocast, or VCAST that were removed using the script?

4. Will I have to redo all my settings after updating? (If so, will freezing all my apps using Titanium be the best way to restore or is there an easier way to keep my apps safe?)

5. If an OTA is released that is better than this update, will we still be able to update to it?

Thanks for your help in answering these questions. I love that this community is so open to helping us all out!
[Motorola Droid 3] limaxray:
Ok, so how about this one:

Is anyone else's recovery hosed? Trying to boot to recovery yields fastboot with what appears to be a verification error.

I haven't done anything to touch recovery, other than this update. I see in the updater script that recovery is flashed - maybe its not a signed recovery?
[Motorola Droid 3] pyro6128:
You dont want to freeze your apps to restore them, you wanna back them up. Run a batch backup of all your apps. Then when you do everything and reroot, install titanium again and restore all your apps. Everything should be just as you left it
[Motorola Droid 3] aross6:
Lemme see if I can help you out here...

1.) No, as long as all your apps that came on your D3 from factory are there it will pass the system check and proceed with the update

2.) You do NOT need to un-root to do the update but you will have to RE-Root after wards

3.) You will need the NFL, Zumocast, & VCAST apps if they were removed because without them the update will fail the system check

4.) You will not have to re-do your settings, but you will have to re-root

5.) We should be able to so long as the build version is at least one number higher, but this is the (only) one I will straight-say I'm not 100% on

On a side note, battery is killer now and the phone feels faster on the whole... this is my $.02 after applying this update to 3 Droid 3's :D
[Motorola Droid 3] psouza4:
My one-click unroot will fix (a) frozen apps, (b) missing files, (c) renamed files, (d) redundant/duplicate copies of su/busybox/Superuser.apk.

http://www.psouza4.com/Droid3/PetesMotorolaRootTools_v1.03.zip

Use the un-root option, apply the update, then use it to re-root. Done and done.
[Motorola Droid 3] ckarrow2:
Same experience here.. I never did delete anything from the phone... only used TBU to freeze them... worked like a charm!
[Motorola Droid 3] reaverclan:
this works amazing, my cell standby is now only 2%, and my gtalk works wonders with the new PRL, this is just awesome in my area. thank you.
[Motorola Droid 3] limaxray:
So, can anyone boot into recovery after applying this update?

After further inspection, it looks like recovery is never touched, but mbmloader, mbm, and lbl are. I can do an SHA1 sum on my recovery and it matches the flash dumps posted in another thread, yet it won't boot.

There is a script copied to /etc that patches the recovery. The SHA1 sum it expects does NOT match the production recovery.

I'm thinking lbl is expecting an entirely different recovery image. In other words, using this update is a bad idea. (not that it has ever been anything but a bad idea)
[Motorola Droid 3] psouza4:
Yes, we still can. The boot menu had a new option added to it as well.
[Motorola Droid 3] reaverclan:
oh oh im gona go check that that would suck.
[Motorola Droid 3] limaxray:
Can you tell me the output of

sha1sum /dev/block/recovery

Edit - That is if you can boot into recovery
[Motorola Droid 3] ckarrow2:
I'm able to boot into recovery after applying the update.. no prob.
[Motorola Droid 3] Visegrad:
I do not have the video with my gtalk. Everything else went fine. I double checked system/app and Talk2.apk is there, the lib is where the lib should be, but no video option. I did look under status and the option is even there. It is on my wifes, but not mine :( Is there any other lib I could have previously lost that didn't get replaced with the update? This is so agravating. I've even gone back and did the update again, cleared data....I'm just out of ideas at this point. I will say that I did not unroot when I did this, I used the app to back up root, temp unrooted, did the update and then used the root app to restore root.... maybe that's it, but could I safely unroot now and update again, and if so, how?

Update: Get ready to laugh. So my Talk has still been working, but in desperation I went to system/app, tapped Talk2.apk, it had install as an option...I did... it works

Sent from my Hitchhiker's Guide mark 2
[Motorola Droid 3] Xenoproctologist:
/ # sha1sum /dev/block/recovery

266973a9d06650d5f90c94cf72503b569bd4c739 /dev/block/recovery
[Motorola Droid 3] limaxray:
I think I found the cause of all my problems - I ran out of space on /system.

If you haven't wiped your cache yet, you can grab the log from /cache/recovery/last_log - mine is loaded with errors.

One of the errors is it failed to copy the new recovery image to /system so it could be flashed on the following boot.

It also removed, but never replaced, all of the camera firmware and thus my camera doesn't work.

I only have 1M free on /system. Can anyone please provide me with the output of:

df /system

and

du -sh /system/*

Thanks!
[Motorola Droid 3] limaxray:
Thanks. Yup, that's not at all what I have.
[Motorola Droid 3] tcrews:
Of note...

"Cell Standby" is no longer the highest usage of battery. After being on all day (after updating), "Cell Standby" is only sitting at 5% of battery use now, almost the lowest item listed for me.
[Motorola Droid 3] 640k:
Did the update today myself and I agree. I honestly think its an adjustment in how the battery manager tracks usage/apps. Using a high usage app shouldn't be pegged at high 90% of usage and everything else low, low %s.

Placebo effect: phone is fast as hell now. Waiting for accurate battery analysis.

One thing is for sure, the recent update puts to bed the misconception that the pentile screen is some major battery saving tech, to where it only uses 5% of power (whatev).
[Motorola Droid 3] kuipou:
does flashing the update wipes the phone?
[Motorola Droid 3] rtbrjason:
No, though it's usually not a bad idea to wipe data and cache. I didn't though and so far so good.
[Motorola Droid 3] limaxray:
Ok, I fixed both of my problems - recovery and camera.

The problem was too much junk on /system. One of the tools I use installed several binaries to xbin, which was just enough to prevent all of the update files from being copied over.

So first off, I removed all the extra junk from /system that I had added so I had enough space to run the update.

To fix the recovery, I extracted the update package and copied recovery/recovery-from-boot.p to /sdcard and ran the following on the phone:

su
system -o rw,remount /system
cp /sdcard /system/recovery-from-boot.p
sh /etc/install-recovery.sh

After that, I was able to restart into recovery and reinstall the update successfully. My camera now works and all seems dandy.

The moral of the story kids - make sure you clean up after yourself before you apply this update!
[Motorola Droid 3] snareplayer1993:
Just tried to download the zip and link is broken. Can someone post a new link?
[Motorola Droid 3] wattnxt:
DITTO!

Link to ZIP file is dead. Anyone rehost Please?
[Motorola Droid 3] buckmarble:
DELETED
[Motorola Droid 3] onethreeteeh:
if you're missing any of the /system apps that get patched, it will fail when trying to verify the current system
[Motorola Droid 3] DroidXY:
Battery life seems to be the same, they just changed the behavior of the battery symbol in the notifications bar, at 90% it still shows 100% full etc.
[Motorola Droid 3] 640k:
but the problem is how moto interprets the battery and sends the info to Android. because at 90%, you might actually be 91% or 98%. the point being as soon as you got off of that 100%, the battery meter dropped. if there are only 10 lines for the meter to drop, it should only drop AFTER the threshold of each line (< 90, drop, < 80, drop, etc.).

the did the same thing with the OG DROID.

EDIT: after thinking about it... they may have gone too far with it. my battery level says 70%, but the meter looks like 80 or even 90%. i remember last night, the meter looked 50% but I was actually at 30%.
[Motorola Droid 3] limaxray:
While I haven't had enough time to really judge battery usage yet, I do feel the phone is running significantly cooler. I feel that it would previously get fairly warm after only minimal activity, but after screwing around with it for a few hours yesterday, it has remained cool. Then again, its really still too soon to tell.

Of course, less heat dissipated means less power consumed.
[Motorola Droid 3] DroidXY:
I saw that too, it does a jump from half into orange whats around 30%
[Motorola Droid 3] jediman:
MAJOR improvements to battery life and cell standby.

Standby is like 6% and I've been off the charger for 6 hours and some odd minutes and only @ 80% and thats WITH moderate use. By now i'd be half dead.

Nice update!
[Motorola Droid 3] DoubleYouPee:
I've probably got this wrong, but I would've thought that a high cell standby would be better, because it means your phone isn't busy with other stuff like bloatware
[Motorola Droid 3] spectrumfox:
I updated with the OTA and didn't root or remove any bloatware and I'm seeing better battery life and lower cell standby. So the update is definitely an improvement as far as that goes.
[Motorola Droid 3] rtbrjason:
Fairly certain this was more a change in reporting of cell standby use rather than any huge battery improvement. I'm at 6 hours and down to 50-60% same as always.
[Motorola Droid 3] tcrews:
Seems to be better for me...though I'll need to go the rest of the day to judge better..though I do agree that they corrected the error with cell standby reporting such high usage. I remember seeing this needing to be fixed in early Froyo as well (which Koush of CyanogenMod fixed in their repo).

90% 5h 34m 11s on battery.

WiFi - on connected

GPS - on

Sync - on

Bluetooth - off

Usage chart

Android OS - 51%

Wi-Fi - 17%

Maps - 9%

Phone Idle - 7%

Voice Calls - 7%

Cell Standby - 6%

Display - 5%

And after typing this in and then backing out, going back to Battery......showing 80% so I was just in the 90% range (increments of 10%).

Will need to run a few days of normal usage to gauge it better.
[Motorola Droid 3] dco717:
Say we apply update and if there is another version could'nt we apply the new one the same way as a zip file on sd card??
[Motorola Droid 3] solid009:
Applied update and noticed a pretty decent improvement in battery life. Down to 70% after 6 hours, would normally be around 50% by this time. I also rooted and removed bloatware, so that may have helped too, although when I rooted and cleaned up before update, it didn't give me much improvement at all in battery life, so I'd have to say it's the update that's improving it.
[Motorola Droid 3] snowblind64:
Rooting and removing the bloat made a world of difference for my battery life. I have not updated and just ran for 36 hours on a single charge with normal usage. That's up from 12-18 hours before bloat removal. Incredible how much battery the bloatware was using just trying to run in the background.

That said, I will not be using this leaked update (though I would like to) as it leaves no method of updating when the official OTA gets pushed. Anybody who had a DX or D2 knows what I'm talking about. So unless a .sbf gets leaked I would not recommend using this update.
[Motorola Droid 3] psouza4:
That's currently speculation and not substantiated at this point, but I would also caution people to not apply the update if they're not comfortable with the risk of this potential.

There's a way to get GTalk w/camera on the old phone too (it requires an update to the APK and there's an SO module). I did this before we decided it was relatively safe to patch.
[Motorola Droid 3] solid009:
I updated my gtalk with video before I applied the update and it did work perfectly. I decided to go with the patch because I know it fixed some battery issues as well, and I can still root, so I figured if I was stuck with it for longer than normal, I'd still be happy cause I have everything I want...besides unlocked bootloader, but by then, I won't have to worry about OTA updates :)
[Motorola Droid 3] colbyb25:
Do I have to unroot to flash or can I just be back to stock with bloatware?
[Motorola Droid 3] snowblind64:
Speculation, perhaps it is. However my speculation is backed by a solid history. Every leaked update for the DX and D2 has prevented an official OTA update. There is no reason to believe the D3 will be any different in this regard. Just the other day I had to use a .sbf on my old D2 (now my girlfriends) which was running the leaked Gingerbread build from a few months ago. Flashing back to the official release was the only way to pull/apply the update.

Edit: My point stands. If you apply this update there is a

very strong

possibility that you will be stuck with it until an .sbf file is released.
[Motorola Droid 3] somemadcaaant:
The camera blue tint is fixed in this update for me, i noticed some people said that it hasn't but i've done lots of testing today with indoor / outdoor images / video and I can say a definite yes the blue tint nightmare has gone, it's like night and day.

The update camera apk has changed from what I can see which i've deodexed, can't wait to see the final version in the official update.

-smc
[Motorola Droid 3] somemadcaaant:
@ snowblind64

I wouldnt worry about not being able to update mate, thats is just another hurdle for us to over come as with previous hurdles we've had... for the camera fix alone this pre-update is worth the muck around.

-smc
[Motorola Droid 3] Dmw017:
I just updated on a rooted D3 with all bloatware frozen and custom bootanimation.

Gotta admit that the update process scared the crap out of me for a moment because it took almost 4-5 minutes to boot up initially after updating. I thought I was stuck in a bootloop or something.

Anyways I was able to use the one click root right after updating and my D3 is right back to the way it was before, except now hopefully the battery will stop sucking so much ****
[Motorola Droid 3] kishin14:
Normally, I'd agree, but this is not a leak of a beta build that a "source" somehow managed to sneak out of Moto's offices and send to somehow in the android dev community. This was ripped straight from Moto's OTA server. It's a soak test leak that likely went out to not just devs but to registered Moto support forum members that volunteered for it. That's exactly what happened with the DX gingerbread OTA that was soak tested back in May. In fact, here's the link that shows the email Moto sent to DX volunteers:

http://phandroid.com/2011/05/23/motorola-sending-email-to-droid-x-users-about-project-gingerbread/

Like it was already said in a previous post, there's not way that Moto would NOT let folks that volunteered for the soak to not take the official OTA, should it be different. Who would ever volunteer for another soak test after that?
[Motorola Droid 3] royolpunk:
So if we flashed it...what now?
[Motorola Droid 3] kishin14:
No need to apologize, to me anyway. It was my phone, my risk. I knew exactly what I was doing. I have no regrets at all and would do it all over again.

And I sincerely, hope you did not remove the post due to pressure from Motorola and it was, in fact, as you state because of a genuine change in judgement.

Thanks for taking the risk to post it in the first place. Motorola should be thankful too. Because the only reason I even bought their lockdown, bloat-infest phone in the first place was because I knew the hacking community would make it usable for me. But my judgement has changed too, I don't plan on buy another product by them ever again.
[Motorola Droid 3] somemadcaaant:
@ royolpunk

WTF is scottml doing? Nothing wrong with the post and files, only benefits from it... that's the strangest thing i've ever seen on here.

-smc
[Motorola Droid 3] somemadcaaant:
@ kishin14

Agreed and with everey1 else here also im sure.

-smc
[Motorola Droid 3] Androidsims:
He obviously took some heat from Verizon or Moto for this. ****ing Nazis.
[Motorola Droid 3] Dmw017:
Im surprised they found out who leaked it or even that they cared. Stuff gets leaked so often I naturally assumed taking unreleased information was an easy task and/or fairly simple with little to no consequences. I mean with stuff like leaked pics and videos previewing phones, you'd think testers would be worried that verizon (or whoever) could identify them by their hands or maybe their face being reflected in the glossy screens or some other way to	ID someone.

I guess it all just gave off a very nonchalant type of image, leaking stuff (although logically, yeah, stealing stuff, especially from corporate, would naturally have serious implications)
[Motorola Droid 3] royolpunk:
i have no idea what you just said
[Motorola Droid 3] reversenext:
can someone please pm me a link to the update?
[Motorola Droid 3] Dmw017:
I had to reread it once or twice but its not really that hard to figure out..

Thanks for the heads up though
[Motorola Droid 3] rweb:
Another question:

Anybody who primarily uses the phone on GSM/UMTS applied this update?

I hesitate, because I'm really happy with the stock GSM/UMTS performance and fear an update could worsen something here.
[Motorola Droid 3] royolpunk:
Its been 7 hours and my battey is still at 90% :)
[Motorola Droid 3] royolpunk:
Yeah I got him now hahaha.
[Motorola Droid 3] magicelf:
Is there a way to revert back from this update? Not that I want to (it really seems to have improved a lot of issues) but I'm just curious if there is a way back if needed for future updates...
[Motorola Droid 3] Dmw017:
No but I dont think it will be necessary to downgrade should future OTA updates be released.
[Motorola Droid 3] NaVVy:
I only use it on GSM 3G here in Aus and the update has had no negative effects.
[Motorola Droid 3] Darksurf:
Ok, call me dense, but im not sure what's going on here after reading this time after time. Did he get chewed out by someone over this release? I think what he did was pefectly fine. It was our choice to update. How is it his fault that moto and verizon are slow to fix the problems we all want fixed and that should have been fixed when we bought the phones. Don't get me wrong. I love my droid3, but we want unlocked bootloaders and WORKING software and hardware. Im tired of random reboots constant cell tower bouncing and unnecessary battery usage.
[Motorola Droid 3] Dmw017:
Hi dense :D

He got in trouble by moto/verizon for leaking the update... which he wasn't supposed to do

Now they made him take it down and "apologize" for doing it lol.
[Motorola Droid 3] Androidsims:
Verizon can suck my balls. Running the update now, sue me.
[Motorola Droid 3] spacecasespiff:
Moto needs to get the #&%$# together if they want to keep customers. Fix things faster instead of playing with them selves.
[Motorola Droid 3] Dmw017:
I think Motorolas **** is together, Verizon needs to pick up the slack a bit but overall they are pretty cool too (compared to the others).

People need to stop demanding so much in such a short amount of time. Im pretty sure no corporation wants to fail and have their hands full already.
[Motorola Droid 3] kishin14:
The only thing I'm demanding is that Moto/Verizon do some real quality testing before releasing a phone that has some of the key problems the D3 had right out of the box. The fact is, if they had, there would have been NO need for this update or for everyone to take the leak as soon as it was available.

Things like the phone NOT coming out of airplane mode after turning it back on from sleep mode, and thus requiring a reboot, is unacceptable. And what's the point of having a front facing camera if you can't do **** with it. And let's not even talk about the blue tint crap from the camera. Those problems alone tell me how poor the testing was on this phone.

You can defend Moto/Verizon if you want. But I paid good money for this phone and while some problems are expected, the ones I mentioned are pretty damn glaring and affects way too many people for them not to have known about before release.