System update problems

Reggie777

Senior Member
Dec 11, 2010
125
8
0
I was notified of a system update on my tablet today. Got it downloaded and started the update. About a third of the way through, the little android fellow keels over, dead, with the dreaded red exclamation.... Error. Tried the update a few times, all with the same result. :confused:

Anyone else having this problem with this update? Any suggestions?

I have to laugh every time I see the dead android... it's just a perfect icon for the situation.
 

Reggie777

Senior Member
Dec 11, 2010
125
8
0
Your tablet is fully stock? No root, no apps removed or frozen?
My baby is fully stock... no root, not unlocked. But come to think of it, I might have disabled a few of the apps. I'll look into that possibility. Thanks for the lead.

Updated: sorry... No go. The blue sphere still slows down and the droid drops dead.
 
Last edited:

loner.

Senior Member
Feb 25, 2013
1,457
289
0
I have rooted stock, and it's been a while since I've update firmware manually on stock that's rooted. I plain forgot how to do it. Can someone refresh my memory please? [emoji15]
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
0
Los Angeles, CA
I have rooted stock, and it's been a while since I've update firmware manually on stock that's rooted. I plain forgot how to do it. Can someone refresh my memory please? [emoji15]

You have to flash the stock recovery back and make sure all the bloatware that came with the rom is installed and not frozen.
The best way to go about this would be probably to flash sbdag's stock rooted rom, then flash the stock recovery from Droidbasement, then manually flash the firmware which you get from Asus downloads.
Not worth the trouble IMHO....
 

loner.

Senior Member
Feb 25, 2013
1,457
289
0
You have to flash the stock recovery back and make sure all the bloatware that came with the rom is installed and not frozen.
The best way to go about this would be probably to flash sbdag's stock rooted rom, then flash the stock recovery from Droidbasement, then manually flash the firmware which you get from Asus downloads.
Not worth the trouble IMHO....
Manually flash is the part I forgot how to do... [emoji15]
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
0
Los Angeles, CA
Manually flash is the part I forgot how to do... [emoji15]
Download the firmware from Asus, unzip it once and copy that file to the root of your internal SD. You may have to reboot for the system to find it, but with stock recovery installed it should give you a notification.
That's how I remember it, but there was a lot of trouble for users trying to flash back to stock with the 4.2/4.3 update - don't quite remember, but I think those got solved when Droidbasement provided the flashable stock recovery.
 

loner.

Senior Member
Feb 25, 2013
1,457
289
0
Download the firmware from Asus, unzip it once and copy that file to the root of your internal SD. You may have to reboot for the system to find it, but with stock recovery installed it should give you a notification.
That's how I remember it, but there was a lot of trouble for users trying to flash back to stock with the 4.2/4.3 update - don't quite remember, but I think those got solved when Droidbasement provided the flashable stock recovery.
I didn't see it in droid basement anymore as of yesterday. This last update is not just a file (ZIP) in a zip update it's the whole Rom.
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
0
Los Angeles, CA
He had the 4.2 posted and I think I still have it on a sdcard somewhere. But the manual update is all I need to do. Have you looked at the new update?
What I've seen so far is mainly complaints about worse battery drain than on 4.3 [emoji12]
Even the version number indicates it's a minor one... Better keep a nandroid [emoji41] [emoji2]
 

Reggie777

Senior Member
Dec 11, 2010
125
8
0
Original problem ... solved.

My original post of the system update not "taking", has been solved.
I got the update from the Asus site, and manually updated my tablet. Thankfully, the little Android guy did not die this time.