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

Do not do the ota update: Brick alert

dbpaddler

Android Expert
Apparently there have been a few bricks with the OTA update reported over at XDA.

Might want to hold off on it for a bit. God forbid you brick it and have to RMA it. Who knows how long it'll take to get back, especially when the techs on the phone seem to be clueless. "Hit F9 at startup". "Try restoring from the CD". Too funny.

Poor bastards. All excited they got in early. Open that box up. Get it up and running. Oh sweet, OTA update. Brick, wtf!.
 
Not sure if its widespread, but there are a lot of users who are updating just fine. Maybe everyone who has updated should post their results here. Only 3 guys on the XDA forums.
 
Well, Eric Lieu, an Asus developer, would disagree with you as it seems to be quite random, but they know it's an issue and are fixing it. Feel free to keep reading the thread. One of his quotes:
From update server records, the success rate is high, but we can not be sure it's accurate or not right now, so, I recommend you can hold the auto update first. Once the SD update file is announced hours later, you can try pressing install button of auto update. No matter it succeed or fail, let me know the result, so that I can calculate the real rate. If it's fail unfortunately, you can use the SD update file to recover your system immediately. Thanks for your kindly help.


Even if it's one bullet in 100 chambers, I wouldn't feel the need to pull the trigger until I knew that last bullet was gone.
 
well it is a little safer knowing they'll have a way to unbrick it. would stink though if you brick and have to wait till it's available.
 
Mine updated no problem, I think the key is to make sure you have an almost fullly charged battery before doing the update.
 
Well if that was the answer, I think the two guys from Asus in the thread would know. Here's a good post to read. Just search on Eric Lieu. The thread is a quick read, maybe page 5 or 6 is when he enters (guessing).

Hey All,

Just to let you know the ASUS Corp. Marketing and Eee Pad teams have noticed this thread and are working with the software team to give you updates as and when they make breakthroughs.

Obviously Eric has been communicating closely with you guys on here, and between him and the whole software team they are still working on it now and over the weekend to check and fix the issue. Despite right now only affecting a very small number of people, obviously we recommend NOT updating until we know the exact issue - Eric has given advise on this on P11. (I realise that doesn't help those who updated already though..
frown.gif
)

Since there's a team of us across the world, the most available (most awake!) person will post update on the Eee FB fanpage as it reaches more people. I know at least a few of you on here frequent there so I'm sure the info will filter through quickly. Eric might decide he wants to update you directly on here, but I guess he also needs some sleep this w/e
wink.gif


We really appreciate your patience and support
smile.gif
 
Keeping up with the XDA thread it would appear they have pulled the update as no one has gotten prompted as of late. While the percentages aren't high with bricking, it is random enough and real. Asus has admitted there is an issue and are fixing it according to the Asus techs in that thread. Some suggest it might be based off of the bootloader version and that some versions might be safer than others. I have a feeling there was some inconsistency with loading up the firmware on the tablet with the various bootloader versions and a few random people getting a tablet with gingerbread on it (I think).

While it sucks to have an issue, it's nice to see employees active in the forums trying to make things right.
 
Mine bricked, I have an Xperia arc and it was rooted using the Generic UK image.

Saw the OTA update available on Monday morning while I was still a little hungover from the weekend and just accepted it. Got half way through and then died.

Tried re-flashing using the old image but no joy :eek:
 
Back
Top Bottom