• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Leaked 5.7.893 Full update (.886 --> .893)

Well none of it is working for me.
I did the complete stock restore, rooted and forever rooted.
(had some issues there but figured them out)
Tried the file from the first post and got basically the same error as dberthia:
"Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:boot:8388608: REALLY LONG STRING")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted."

Tried each of the individual files in the second part of the OP and all of those gave me the same type of errors as well.

Maybe I'm just getting bad downloads, but I usually have good luck from here at work.

Anyone else have any ideas?

I'll try again from home and update.

Same message for me :( I'm not rooted, just a a straight "stocker"..hehe..
I went straight to 5.7, not installing the older .zip files too, so maybe that's it??
 
Upvote 0
So here's my tale on this adventure:

I was rooted running a stock .886 (never updated) and had Bootstrap installed.

I deleted Bootstrap first following the instructions listed above.
I forever rooted my phone using option 3 of the R3L3AS3DROOT because I didn't want to wipe data.....forever root was successful
I tried to go directly to the 5.7.893 update using option one in the instructions on the first post and I got the Status 7 error that others have mentioned above.
I tried to then use the 2nd option listed in the first post by installing the updates one by one.....when I tried to install the first of the 3 I got the same Status 7 error.
Finally, with no where else to go it seemed, I went back to the R3L3AS3DROOT and chose option 1 to do a wipe, revert, and re-root. Then I went back to option one of this thread and it seems to be working....I'll update if it goes wrong, but for now it is progressing just fine.
 
  • Like
Reactions: SNeitzel
Upvote 0
Had anyone noticed that this resolves the headphones buzzing issue? I'm at work with no headphones to test with

A few have reported that the buzzing has gone away.

I followed the first set of instructions, which failed, then I followed the second, which succeeded, but why must I go back and follow the first set again?

EDIT: ah, is it for the webtop files?

Yes - the incremental method screws Webtop - the 5.5.886 --> 5.7.893 does everything correctly.

Okay over cautious concerned question inc!!

I have a rooted stock rom just have some stuff frozen... When I do step 1 to "revert" will I lose any important date? To me that means apps, contacts, etc...?

Thanks :)

-Corey

You don't need to revert - unfreeze everything and try applying the full 5.7.893 update onto your phone (after setting up 43v3r root) and it should go well.

if it does not, then use the incremental method and then revert to 5.5.886 stock (with 43v3r root) and then apply the full.

Well, I did the option 2 on forever root so I didn't lose any date... I then did the update.. Everything went through perfect... However date issue is there and worse, at least for me... I shut off my wifi and the 3g never even popped up... Did airplane on and off, 3g came up but would not turn blue and still no connection, airplane on and off again, no 3g.. rebooting now and hoping this was just a fluke...

-Corey

Edit: rebooted, still NO data at all without wifi on... So my data was better before the update, at least it worked, lol...

Edit AGAIN: well, I got data working.. I had to go into the ##program menu and set my data back to cdma, evdo, and lte.. I had lte turned off as I'm not in a 4g area, but evidently it was causing issues with 3g.. however if I just turn lte off in the regular settings menu it works fine...

Thanks for that - but that is why we said everything has to be stock - including all customizations you make to the system.

Same message for me :( I'm not rooted, just a a straight "stocker"..hehe..
I went straight to 5.7, not installing the older .zip files too, so maybe that's it??

That should be it for you.

I followed the instructions in the original post and got to 5.7.893.
Then I installed the th3ory rom shifter 2.1 and ended up back
at 5.5.893. WTF?

Shift3r is based upon 5.5.893, so that is what you are going to see.

The Radio and LTE updates are permanent, though, so they are still there.

So here's my tale on this adventure:

I was rooted running a stock .886 (never updated) and had Bootstrap installed.

I deleted Bootstrap first following the instructions listed above.
I forever rooted my phone using option 3 of the R3L3AS3DROOT because I didn't want to wipe data.....forever root was successful
I tried to go directly to the 5.7.893 update using option one in the instructions on the first post and I got the Status 7 error that others have mentioned above.
I tried to then use the 2nd option listed in the first post by installing the updates one by one.....when I tried to install the first of the 3 I got the same Status 7 error.
Finally, with no where else to go it seemed, I went back to the R3L3AS3DROOT and chose option 1 to do a wipe, revert, and re-root. Then I went back to option one of this thread and it seems to be working....I'll update if it goes wrong, but for now it is progressing just fine.

FWIW - I never removed bootstrap when I did the incremental approach.

When I revert to pure stock via R3L3AS3D Root, after installing the 5.7.893 update, I restored bootstrap via TiBu.....

No issues here at all.
 
Upvote 0
You got lucky - I did the same thing when I went from 5.6.893 to 5.7.893, and nothing *seemed* to be affected - but when I reverted to pure stock I left it pure stock, rooted, and applied the 5.7.893 full update just to be sure.

Never know when that may come to bite you in the arse.

The reason I say that is that if you start having all sorts of weird issues down the road b/c an app was not updated when it needed to be updated, you'll have to take into account that you had them frozen when you performed the update, which simply adds another set of points of failures (one point of failure per app frozen).

Since I've had a lot of experience with this stuff, I want to eliminate all the possible points of failure, so that if I do end up having to troubleshoot, I have few points to go over, making my job that much easier.
 
  • Like
Reactions: SNeitzel
Upvote 0
I'm unrooted and followed the instructions in post 1 to the letter. Everything went fine. Only thing I had to do was to reboot the phone a second time in order to restore my data connection. Thanks to all for the effort in making this painless.

UPDATE:

Took 3 reboots of the phone to make everything work correctly. It required a second reboot to restore my 3g data connection. With the connection back I noticed that the screen was very dim (brightness set to auto) and that adjusting the brightness did nothing. A third reboot fixed this.
I have noticed that the camera seems to focus more quickly than before the update.
 
Upvote 0
Well none of it is working for me.
I did the complete stock restore, rooted and forever rooted.
(had some issues there but figured them out)
Tried the file from the first post and got basically the same error as dberthia:
"Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:boot:8388608: REALLY LONG STRING")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted."

Tried each of the individual files in the second part of the OP and all of those gave me the same type of errors as well.

Maybe I'm just getting bad downloads, but I usually have good luck from here at work.

Anyone else have any ideas?

I'll try again from home and update.
UPDATE:
Got home and DL the full update file again.
Failed.
Tried the 3 individual update files.
Failed, Failed, Failed.
Restored and 4r3v3r rooted using R3L3AS3DROOT, tried all 4 files again.
Failed, Failed, Failed, Failed.
Tried RSDLite to go back to stock, Flashsing Failed, (SH**)
Got lucky, and R3L3AS3DROOT's method was able to get me un stuck.
Tried the full update again.
Failed

Then, I tried the CWR Recovery file from the OP in this post.
http://androidforums.com/bionic-all-things-root/434407-how-flash-893-update-maintain-root.html
Tried the full update file.
Failed.
Tried the first individual update file.
Failed.
Tried the 2nd individual update file.
SUCCESS!!!!!
Tried the 3rd individual update file.
SUCCESS!!!!!!!!!!
Tried the full update file.
SUCCESS!!!!!!!!!!!!!!!!!!!!

Restoring programs etc now....

WHEW!!!
Thank Yous coming to all those posts that helped me and to everyone else who has chimed in.
 
Upvote 0
Additional question.
After getting everything back to normal from the update, I went back in one last time and checked the mount_ext3.sh file.
It was missing the final line of code that was added by FOR3V3R ROOT:
chmod 4755 /system/app/Superuser.apk
I added that entry, but then went and looked in /system/app and superuser.apk is not there.
Should it be???
I still have root since I can edit the mount_exte.sh file and the bootstrapper works as well.
 
Upvote 0
So I update to 893 just fine. But after a reboot, the 3g/4g indicator never shows. But if i use "restart connections" it will show.

So I guess 3G/4g issue isn't fixed? Or at least on my phone.

Any thoughts?

Have you tried rebooting your phone a couple of more times? I got this when it rebooted immediately after the install, but only the one time. I rebooted a second time and it came up without any extra steps or tricks. I did notice that it felt like the phone took longer to "find" the connection, then even longer to turn blue, but once it was showing in white, I was able to access 3g.
 
Upvote 0
Have you tried rebooting your phone a couple of more times? I got this when it rebooted immediately after the install, but only the one time. I rebooted a second time and it came up without any extra steps or tricks. I did notice that it felt like the phone took longer to "find" the connection, then even longer to turn blue, but once it was showing in white, I was able to access 3g.


I am having all kinds of data issues with this update, its actually worse than ever. I cant get any data whatsoever. Reboots, battery pull, airplane mode etc etc, nothing works. Eventually when I get the 3g Icon its white so I cant get data, i cant get it to turn blue.

Tech support is useless (if thats news to anyone). I may just go back to my og droid and wait for the official ota, if that doesnt work I will put up a stink until they let me exchange it for a working 4g phone.
 
Upvote 0
wow, that worked. Thanks!!!!

Doesn't that mean that it was caused buy a poorly seated SD card?

I think the SD connections are pretty flimsy and a slight shock can make the connection bad.

I saw this when I dropped my Bionic about 18 inches onto a short pile carpet. One of the cards was visibly not squarly seated.

... Thom
 
Upvote 0
Well, I did the option 2 on forever root so I didn't lose any date... I then did the update.. Everything went through perfect... However date issue is there and worse, at least for me... I shut off my wifi and the 3g never even popped up... Did airplane on and off, 3g came up but would not turn blue and still no connection, airplane on and off again, no 3g.. rebooting now and hoping this was just a fluke...

-Corey

Edit: rebooted, still NO data at all without wifi on... So my data was better before the update, at least it worked, lol...

Edit AGAIN: well, I got data working.. I had to go into the ##program menu and set my data back to cdma, evdo, and lte.. I had lte turned off as I'm not in a 4g area, but evidently it was causing issues with 3g.. however if I just turn lte off in the regular settings menu it works fine...

what do you mean by "##program menu" I have stuck 3g signal in white and i dont have data, and I've exhausted all options
 
Upvote 0
Still all locked up on a white 3g icon, I will try to restore, reroot, forever root and install the 886 to 7.893 zip and see if that fixes it. At least webtop will work after this lol

Did you try a sim card pull like rdefino? Didn't see that on your last list of things you tried. If you did, my bad. :)

Doesn't that mean that it was caused buy a poorly seated SD card?

I think the SD connections are pretty flimsy and a slight shock can make the connection bad.

I saw this when I dropped my Bionic about 18 inches onto a short pile carpet. One of the cards was visibly not squarly seated.

... Thom

It can be something hardware related like that or sometimes a SIM card pull resets the data connections causing it to reconnect. That's what I always try to restore data when airplane mode doesn't work.

So,what does this update give us?

Just wondering?

Check out the http://androidforums.com/motorola-droid-bionic/438220-holy-crap.html Thread. lol
 
  • Like
Reactions: p8ntballah21
Upvote 0
Did you try a sim card pull like rdefino? Didn't see that on your last list of things you tried. If you did, my bad. :)



I did not list it, thanks for the suggestion but I have tried that. I have tried everything I could think of. I got a level 2 tech for vzw and he can't figure it out, he tried resetting my phone a few different ways with my battery pulled and he came up with nothing, he said he would work on it some more and that was 7 hours ago.

I am hoping that reflashing 5.7.893 after a reset to 886 will do the trick, wont know until I can get home and try it.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones