[Q] 3.2 update hangs at 21% (GT 7500 Europe) - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Well as the title says, I received a message that the 3.2. update was ready. I used the OTA update. The update happens in two parts.
Part 1. You get a message stating files need to be downloaded. After the download finishes, you are asked if you want to install. I said YES. The device reboots, applies the update. This takes a while. Then restarts.
Part 2. Upon restart, the tab immediately connects to the upgrade server again. Once more you are advised that there is an upgrade and that files need to be downloaded. After download, again the question do you wish to install. I said YES. Device reboots. Update is applied and ..... hangs at 21%. It has been there now for more than a half hour.
Really dont know what to do now. Help appreciated.
Edit:
Well, after having waited for what seemed an eternity, not knowing what to do, I pressed the power button until the Tab powered off. Then I prayed to the cosmos. Then I turned the Tab back on. It started applying the patch again, starting at 0% and running to 21% at high speed and, after a brief hesitation as sheep do when deciding to cross a dam, it crossed and completed the update.

Did you have more then 50% battery?
Sent from my GT-P7500 using Tapatalk HD

Mine updated just well with only one reboot. It even fixed the issue I had with the Swype keyboard (Russian numeric keys) after the last OTA upgrade some time ago. I also have the European version.
Sent from my GT-P7500 using XDA App

Nagarebozhi said:
Did you have more then 50% battery?
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
Yes, fully charged.
Problem solved by praying to the cosmos, see OP.

Please use the Q&A Forum for questions Thanks
Moving to Q&A

you have a good luck.

Related

[Q] New Tmobile Update trouble

I have received the Tmobile ota update twice and both times my phones stays on vibrant screen and nothing else. The first time i kept my phone rooted and did the download and the progress bar goes to 100% and the phone reboots and gets stuck on the Vibrant screen and i left it like that for 20 mins. I flashed the stock rom again then a week later i got the ota again. I unrooted this time did the download and the same thing happened again. Has anyone had the same issue or know if i am doing anything wrong?
Why don't you just manually update to the latest update and save yourself the trouble of ota updates
Sent from my SGH-T959 using XDA App
sure they would. no ota will be 100% successful. with such a popular device even a small percentage of failures is still thousands of bricks.
wildklymr said:
sure they would. no ota will be 100% successful. with such a popular device even a small percentage of failures is still thousands of bricks.
Click to expand...
Click to collapse
Right, but we're not evaluating Samsung's overall success. We're on a XDA thread where the majority of people have modded their phone out of warranty. I know 6 people personally with vibrants, i'm the only one who takes the initiative to mod my phone and my 6 friends all installed the OTA just fine, and these people don't know anything about android other than it's "super cool" and they upgraded just fine.
I had the same problem with the OTA update from tmobile on 2 sgs I have. Just flashed the JI6 update they attempted to install using odin and was good to go.
Sent from my SGH-T959 using XDA App
stepp1927 said:
I have received the Tmobile ota update twice and both times my phones stays on vibrant screen and nothing else. The first time i kept my phone rooted and did the download and the progress bar goes to 100% and the phone reboots and gets stuck on the Vibrant screen and i left it like that for 20 mins. I flashed the stock rom again then a week later i got the ota again. I unrooted this time did the download and the same thing happened again. Has anyone had the same issue or know if i am doing anything wrong?
Click to expand...
Click to collapse
Do you already have a file named "update.zip" on your internal storage? That could be the problem. if you do rename it, and then when you get the OTA again it should work. Also I heard customer recovery can cause issues.

[Q] Device Bricked itself?! :-/ (possibly related to OTA update)

Hey guys,
Hoping someone can help out here, although I'm guessing I will need to do this: http://forum.xda-developers.com/showthread.php?t=991072
My phone has been prompting for the last 36 hours or so to do the OTA update which I had been putting off due to wanting to retain root (done with SuperOneClick) and not having time to follow the instructions for that. I had wireless turned off last night, and this morning when I turned it back on it downloaded the update without asking, but still asked before attempting to install. It's been asking me every hour since and I've said 'Later' every time.
Anyway, I stepped away from my desk for half an hour at work this afternoon and came back to find my device boot-looping. I don't expect anyone at work would have touched it, I just don't know what led up to this behaviour. I get the Motorola animation, then the AT&T "Rethink Possible" animation, and then the screen goes blank and the LED blinks red about 120 times at about 3 times the speed of a normal notification and then it starts over again.
The only reason I'm concerned about doing the SBF flash is that this is a SIM-Unlocked device on Telstra network in Australia and I really don't want to loose wifi functionality. Other than that I'm quite comfortable doing so. The phone had only been rooted, I hadn't done the deodex ROM or any mods.
Does anyone have any suggestions?
WheelieBin said:
Hey guys,
Hoping someone can help out here, although I'm guessing I will need to do this: http://forum.xda-developers.com/showthread.php?t=991072
My phone has been prompting for the last 36 hours or so to do the OTA update which I had been putting off due to wanting to retain root (done with SuperOneClick) and not having time to follow the instructions for that. I had wireless turned off last night, and this morning when I turned it back on it downloaded the update without asking, but still asked before attempting to install. It's been asking me every hour since and I've said 'Later' every time.
Anyway, I stepped away from my desk for half an hour at work this afternoon and came back to find my device boot-looping. I don't expect anyone at work would have touched it, I just don't know what led up to this behaviour. I get the Motorola animation, then the AT&T "Rethink Possible" animation, and then the screen goes blank and the LED blinks red about 120 times at about 3 times the speed of a normal notification and then it starts over again.
The only reason I'm concerned about doing the SBF flash is that this is a SIM-Unlocked device on Telstra network in Australia and I really don't want to loose wifi functionality. Other than that I'm quite comfortable doing so. The phone had only been rooted, I hadn't done the deodex ROM or any mods.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Seems like if it did try to install it failed somewhere not allowing for full boot... have you tried pulling the battery also try and find out if it is running 1.5.7 also try booting in recovery and factory reseting. And also don't you only lose wifi when flashing 1.5.2? I might bw wrong about that though
Sent from my MB860 using XDA Premium App
drock212 said:
Seems like if it did try to install it failed somewhere not allowing for full boot... have you tried pulling the battery also try and find out if it is running 1.5.7 also try booting in recovery and factory reseting. And also don't you only lose wifi when flashing 1.5.2? I might bw wrong about that though
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Sorry, I should have specified... yes, I have pulled battery - issue persists. I hadn't gone as far as a factory reset, but it's definitely less dramatic than a reflashing, so trying that now...
OK, factory reset seems to have done the trick - it was still on 1.2.6, I'll do the update to 1.5.7 with the v2 Root Process now and see how I go.
WheelieBin said:
OK, factory reset seems to have done the trick - it was still on 1.2.6, I'll do the update to 1.5.7 with the v2 Root Process now and see how I go.
Click to expand...
Click to collapse
Congrats friend! Glad to hear you're out of that boot loop.
Sent from my MB860 using XDA Premium App

[Q] Does anyone getting this error when restarting the tab?

From time to time (not always) I receive the following error message when I restart. It appears twice:
the application Samsung account (process.osp.app.signin) has stopped unexpectedly. Please try again.
In my accounts & sysnc Samsung account appears always as sync off, and I cant enable it. Is that normal?
I've got it as well. I assume its because the Samsung login servers are down or something.
Thanx for the reply. I thought this was also connected to a different problem. I am not getting the menu items in KIES to sync with the PC and a message telling this version cannot be updated. Maybe a different topic but nobody replied to my previous post. Thanx again.
Yes, I have gotten it when restaring with quick boot.
Sent from my Galaxy Tab 10.1 via Tapatalk
I get it too. Every time it happens I report it. Does anyone report force closes in here? I think the more reports the higher the priority is, hopefully they fix it soon.
Sent from my GT-P7510 using XDA Premium App
I am also getting it. It seems pretty common.
Sent from my GT-P7510 using XDA Premium App
lordwinkevin said:
I get it too. Every time it happens I report it. Does anyone report force closes in here? I think the more reports the higher the priority is, hopefully they fix it soon.
Sent from my GT-P7510 using XDA Premium App
Click to expand...
Click to collapse
Hopefully because I report it everytime as well. I thought I would have to return mine but I'm glad to see I'm not the only one getting this. Seems to happen when I boot with wi-fi on and it can't access it because the wi-fi is secure.
I get it every time..sometimes twice every time I boot.
It started today for me after installed rscovery and rooted.
I am getting the same error too when starting up sometimes, always comes up twice. Usually after the second reboot it doesn't happen.
same here
Yep... twice every time I turn on the tablet. It's super annoying. I report it every time; I hope they fix it at some point.
Also, I have the GoogleIO edition. Does it happen on retail too?
Yes. I have retail version. I rooted my devices and then unroted it. I read someone did the same? Did everyone in here rooted their device?
Sent from my GT-P7510 using XDA Premium App
Seen ONE TIME, on an unrooted retail unit (BB preorder, 32GB)
I get have seen the message maybe 5 times (2 messages each time). Unrooted retail Galaxy Tab 10.1 32GB Grey.
Same here, unrooted retail 32GB gray. Can't believe this happens as often as it does and wasn't addressed by Samsung before launch.
jeffdgr8 said:
Same here, unrooted retail 32GB gray. Can't believe this happens as often as it does and wasn't addressed by Samsung before launch.
Click to expand...
Click to collapse
second that....
I get this error all the time as well. To my memory when i first started using the tablet i never got it, im not sure though.
bradrobster said:
I get it every time..sometimes twice every time I boot.
Click to expand...
Click to collapse
I am also getting this. Twice usually. I also press report. I have the gray 32gb that was shipped unlocked, does this make a difference? I am also rooted.
First post here.
I receive this twice on every bootup. I emailed Samsung Support yesterday using the email [email protected]
Samsung Galaxy Tab 10.1
eric6b12 said:
First post here.
I receive this twice on every bootup. I emailed Samsung Support yesterday using the email [email protected]
Samsung Galaxy Tab 10.1
Click to expand...
Click to collapse
What did they say?
I get this too, twice on every boot. The message says you can restore to factory defaults, which will wipe out your accounts and resolve the issue temporarily until you add your samsung account again. This is why we didn't get this message when on first boot.

Tablet keeps restarting after ICS

First I had nothing but boot loops for an hour, then by some miracle, ICS finished installing. However, now i keep getting "refresh failed", and the tablet will lock up and restart itself. Should I drain the battery and let it die? What should I do to try and fix this?
mine is locking up and restarting too but only once every 30 minutes on average.... lol this is lovely.
This is driving me insane. My prime was perfect before this update. Right now it won't even boot, just bout boot loops. Already tried factory wipe too.
Sent from my Galaxy Nexus using Tapatalk
did you update via the OTA file some posted or did you download the update from asus directly through the tablet?
Directly through the tab, and I had a serial number too.
Sent from my Galaxy Nexus using Tapatalk
Getting the same thing.
Well someone from Asus development just sent me a pm asking for my serial number so they can look into it. I didn't contract them first. Hopefully something can be done. I love this tablet, but I have no use for a $500 paper weight
Sent from my Galaxy Nexus using Tapatalk
for now
just to help,
what you could do for now is downgrade by following the first part of this thread:
http://forum.xda-developers.com/showthread.php?t=1426280
I hope this will at least get it back to a working state.
let us know what happens

Firmware update is available now! JB!!!

As per title.
some people start updating already.
I am in asia region, yet to get FOTA.
please feedback if you hit any problem or bug.
hihihehe said:
As per title.
Click to expand...
Click to collapse
Nothing in UK yet or on the UK support site. I hate waiting games....
Not here in nz with my Taiwan bought prime.
Sent from my Transformer Prime TF201 using xda app-developers app
Nothing in Melbourne Australia
Nothing in Norway.....
Sent from my LG-P880 using xda app-developers app
nothing in Belgium
downloaded and running fin in maui ill put more updates in a bit
Went i tried to give it a hard work out during the first boot scrolling opening apps web browsing. there was some lag but nothing closed or had the dumb wait box pop up. after boot everything is pretty smooth. Ive been trying to get the browser to lock up and havent had any problem yet. Seems to be pretty good so far.
Vellamo metal bench 343 about par with stock ics
Well I have it here in Florida, USA so I'm happy for that. I'm just nervous to go ahead and update. I dont want to lose my root and preformace tweaks, so I'm on the fence about it at the moment.
screwed up my update
My update failed! in US. It started updating then there was a dead android with a red exclamation on it. I forced rebooted and I am now back to 4.0.3. Now I cant even get the update when I check for update. It says no update available. I already factory reset it still no update showing.
The update lost root & Voodoo Rootkeeper restored root.
Sent from my Transformer Prime TF201 using Tapatalk 2
Great news!
Can somebody check for rumored java-applet?
Sent from my Nexus 7 using xda premium
zeecfc said:
Nothing in Melbourne Australia
Click to expand...
Click to collapse
Nothing here in Australia.
Well I had an upadate failure, it got half way through installing it and then showed the red exclamation point and restarted. Not sure what is wrong but I'm going to hold off for now.
[email protected] said:
Nothing here in Australia.
Click to expand...
Click to collapse
Well yes, I know that
sgandy2989 said:
Well I had an upadate failure, it got half way through installing it and then showed the red exclamation point and restarted. Not sure what is wrong but I'm going to hold off for now.
Click to expand...
Click to collapse
I had the same thing. Now it cant find the update anymore.
sgandy2989 said:
Well I had an upadate failure, it got half way through installing it and then showed the red exclamation point and restarted. Not sure what is wrong but I'm going to hold off for now.
Click to expand...
Click to collapse
I had the same issue with one of the past updates. I recall that I installed the update manually through Asus website. However, the JB update is not in there yet.
sgandy2989 said:
Well I had an upadate failure, it got half way through installing it and then showed the red exclamation point and restarted. Not sure what is wrong but I'm going to hold off for now.
Click to expand...
Click to collapse
I had the same thing happen i just rebooted but the check for update button was blacked out but when i looked in the notifications it was downloading. dont know if that helps
Nope not working
Mine doesnt get past the update screen, update blanks out, failure message and nothing in notifications........... Bugger
UPDATE got it to update after a few more tries. It seems laggy at first but gets better as it settles in. I had some troubles getting wifi to connect and system notifications were missing initially. All corrected itself with time so be patient peoples. Impressed so far

Categories

Resources