yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] kentoe:
Either way can be debated, often times "a couple" is usually determined as two but at the same time he wasn't specific. It's still frustrating at the fact that it's not here yet and it's coming up on a month along with the emails they promised for the chromebooks as well.

I don't want to sound greedy, I just would like to hear back soon as much as you all would :D
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Oletros:
But "in a couple of weeks" doesn't mean more than a month.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] cisox:
FEW =/= COUPLE

I'm sure it will be dropping soon.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Kitinas:
It does if you have a Nexus One and were waiting for Gingerbread! That was fun.

Still, with some luck it'll hit soon.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] falconeight:
If I were samsung I really wouldn't focus on updating the I/O version that I gave away for free. I would let the dev community figure out how to upgrade it on their own.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] khart214:
I have limited edition model handed out at google conference. I just went and did a manual check for update and mine prompted me to install an update. You guys might want to try the same thing. Mine is downloading now.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] twigster:
Please tell us how that goes and what you end up with. Can you also please mention whether your device was unlocked before and after the update and if it wiped your device.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] el_salvad:
Mine is downloading as well ;) Anyone sure of this is 3.1?? :confused:
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Kitinas:
You guys weren't kidding. Downloading now. At about 15%. Yay for tethering to my phone.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] smaskell:
downloading 3.1 right now! hurray! will make system image asap
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] khart214:
I was not rooted. Mine was still out of the box condition. its a long update process, but it did give me 3.1. It did not wipe my device!!
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] rycus86:
Hi!

Is this update available for the P7100 (10.1v)? Anyone saw it on their device?

I haven't found manual update check in the settings in the about section. Is this elsewhere?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Oletros:
Yeees, 3.1 update done :)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] smaskell:
mine went really fast at the beginning and then got stuck at 76% for quite a while. at 83% now though so don't worry if it seems like it's frozen.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Nimche:
For I/O do you need a Samsung account to update...?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] kdietze3:
3.1 update complete on my Galaxy Tab 10.1 Google IO Limited Edition. It takes some time, but definitely worth it.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] twigster:
I'm in South Africa with the 10.1v, oem unlocked, and when I look in settings, system updates, it just says system is up to date. Still on 3.0.1.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] lawrencegs:
Woho! Yeah, its 3.1! I just post some pictures on my posterous: http://olentz.net/31-update-for-samsung-galaxy-tab-101-limited
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] khart214:
no, it stuck there on mine for a few mins. It takes longer than I thought. But I have noticed much snappier response.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] tigerminx:
Yup, same problem my side. Also from SA.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Kitinas:
Now that's what I'm talking about. So much smoother now. Not having 3.1 was the most painful part of switching from my Xoom to this baby. 3.0 just felt so choppy after 3.1.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] tigerminx:
Can you confirm if the image gallery has been fixed. 3.0 really butchered the images until you zoomed in a little. Is it still like that?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] twigster:
I guess we will just have to wait a little longer. It seems to automatically check for updates at predetermined times on my 10.1v device, so maybe tomorrow we might see some luck. I can't ask it to check for updates.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Archangel:
I assume this breaks root and clockwork recovery?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Kitinas:
I don't really remember running into that before, but as of right now images look just as they should for me, so I'm gonna say it's fixed. Though, the gallery is way the heck faster now, that's for sure.

Hope that's at least somewhat helpful.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] tigerminx:
Thanks dude, basically when you first open an image on 3.0 it's slightly pixelated and blurry and when you zoom in a bit it comes right !!! Weird, but very annoying :)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Blou_Aap:
Yo another oke fr0m South Africa. Can someone dump and upload 3.1 please?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] lawrencegs:
A couple of findings after I play around for a couple of minutes:

everything is so much much smoother

we can set Home Screen Wallpaper and Lock Screen Wallpaper

a set of 5 system wallpapers... replacing the old one, not sure where they go...

resizeable widgets

a little tweak on the wifi icon, its now showing data activity

browser is now being recognized as tablet browser, instead of mobile browser (for example: gmail.com goes to the tablet (#tl) view just like ipad instead of m.gmail.com)

unlike 3.1 on XOOM, the browser does not have Quick Control
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] occb2:
Wow

that was fast!Holy crap! I'm doing it as I type. That was fast. Thanks Samsung.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Archangel:
big thing is can you boot into fastboot after updating???????
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dalaigh:
I/O 10.1 update stuck in a loop

Hi. I just downloaded the new firmware, seemed to install properly (the low-res update screen went to 100%). Now the machine is constantly rebooting after the swishy galaxy screen. I get a glowing Samsung logo - swishy galaxy over and over.

Tried holding down the power button and shutting down. This brought up:

=================

Entering upload mode...

Upload_Cause: Undefined

=================

Anyone know how to do a hard reset? Seems the instructions for the 10.1v don't work on this one.

Grrrr....
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] cosimoss:
Downloaded and updating now. 75% complete.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] lawrencegs:
Mine was on the glowing Samsung logo for quite a while, then it goes to the lockscreen. Was yours still vanilla when you update it?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] falconeight:
putting it on my baby right now woohoo
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dalaigh:
Yes, absolutely. How long was "quite a long time". The logo glows for about 15 seconds then the intro animation. Repeat... repeat... repeat. Did you go through cycles of this?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] mralexsays:
Hmm - first attempt failed. Trying download/install again...
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] lawrencegs:
No, mine didn't go through cycles. Mine just goes like this:

downloading (2-3 minutes) -> Shutting down -> low res progress bar 0-50% (2-3 minutes) -> low res progress bar 51-85% (5 minutes) -> low res progress bar 86-100% (5 minutes) -> samsung "swishy" galaxy animation -> glowing logo (another 5 minutes) -> lockscreen
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dalaigh:
Thanks. Unfortunately it just continues to reboot. And I can't download again because I can't get the OS to boot up! I suppose I'll wait for someone to put the firmware up and I'll do it from fastboot (seems to create a fastboot connection when I plug it into my mac). Never done it before so any advice would be appreciated (especially on a mac). Cheers!
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] mralexsays:
Still having trouble - the update downloads fine (or so it says) then it reboots and the update starts, but it only gets to 13% then reboots (into 3.0 version) and says "Failed to update firmware. Try again using PC software (Kies) or visit a Samsung service centre." I even tried a factory wipe and it still fails at 13%. Is anyone else having this issue?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] cosimoss:
It updated in one go. 70%-99% took a long time then sat at 99% followed by a long reboot and now working like a treat. 3 of my apps need to be updated.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] kylgore:
Ditto, mine dies at 13% and reboots with a failure message as well. Since when does samsung have "service centre"s?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] tau_:
+1, Also failing at 13% with the same behavior. (Reboot, then "Failed to Update Firmware." message)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] mralexsays:
I'm now trying to download via the Verizon hotspot from IO. I was thinking that the download (on my home DSL) took a suspiciously short time (about 90 seconds.) This is taking a lot longer to download on the Verizon network, so maybe its a connection thing. I'll update if this works.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] clubtech:
Fastoot is still there after the update. Root is still there after the update.

Sweet.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] kylgore:
Figured it out. I had backed up some stock apps and removed them, once they were restored, i was able to progress past 13%. at 71% now, it should complete successfully.

I can pull and post apks if you've removed any that you need to restore to complete the update.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] cosimoss:
Looks good and the start screen is just too much:

[img=http://img200.imageshack.us/img200/5394/galtab107.jpg]
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] mralexsays:
That's odd - I didn't remove any stock apps. I even did a factory reset and still have the issue (downloading via Verizon didn't make any difference.)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] kylgore:
Are you rooted?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] mralexsays:
I was (before factory reset.) The only non-stock things I had were root and su.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] mralexsays:
Looks like root is kept even after a factory wipe, so I'm removing Superuser.apk and /system/xbin (busybox) to see if that helps...
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] mralexsays:
Still stuck...Need to give it a rest for a while...
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] el_salvad:
Anyone found a way to get ALLSHARE on your 10.1's?? :confused:
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] doublehoya:
If you wouldn't mind, that would be huge. Idiot that I am, I went thru and deleted some of the samsung apps, and of course I forgot to back them up. I tried to reinstall them from a system dump, but it looks like I might have missed one or 2. I have the same problem- the upgrade fails at 13% and restarts into 3.0.

Thanks for the help!
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] tau_:
I checked my /system/app folder against the system dump posted and I noticed that the system apps (Amazon Mp3, Music Hub, Samsung Apps) I had frozen and then restored with Titanium Backu were not restored with the same names. I copied the apks from the system dump onto the sdcard and then copied them to /system/app with a local terminal, keeping the names intact.

This seems to have fixed the problem and the update has gone past 13%!
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Archangel:
It has to be more than that cause i didnt delete or freeze those apps and mine still says the same thing and didnt update?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] mralexsays:
I agree. I did a diff of my system dump against the posted one and it was exact - no differences in the system image. I still can't get past 13%.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] CrazyCoder:
Check the ClockworkMod Recovery thread. Try flashing stock boot.img and recovery.img via fastboot and then it should go beyond 13%.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] mralexsays:
Yep (the boot partition was the issue.) Thanks!
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] SS2006:
i cant flash in fastboot cause my win 7 64 bit isnt recognizing my tablet in fastboot mode

i installed the samsung usb drivers ...
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] SS2006:
either way seems samsung server are down, says connection failed right away
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] nosaint:
how to check for updates?

How can I manually check for updates?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] smaskell:
Go to "about tablet" in the settings
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] vitriolix:
I was getting the 'connection failed' error at first, but looks like they've fixed their servers, its downloading now :) :)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] cosimoss:
Software details:

Android version

3.1

Kernel version

2.6.36.3

se.infra@sep-58 #1

Build number

HMJ37.UEKF3 P7510UEKF3
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] MrEfflon:
Manage to get the OTA update last night. The download was quick but the update took forever and it looked like it got stuck a few times.

Noticed "books" was added :) and they must have degraded the built in movie support :( . I had a few xvid and mkv's that all worked and now all I get is "not supported" . Anyone else seeing the same downgrade?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] el_salvad:
Anyone know how to get AllShare on your tab 10.1's?? :o
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] nosaint:
It saids last update june 4 your system is uptodate. There is no button for a manual update
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] lacion:
i think you have a 10.1v?

mine is like that and its a 10.1v

i wonder when we well get some 3.1 love
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] cosimoss:
You have the 10.1v and this update is only for the 10.1 I/O (the Google one). This is still no update for the 10.1v.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] gbmitchell:
When I go to check for update it brings up a box that says choose country, and US is not on there, Anyone know why?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] cisox:
The Google I/O tablets are actually the European version. Just select UK and you'll be fine.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] bonzai3558:
I tried the camera and changing to video camera causes force close. Anyone else have this issue?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] cosimoss:
http://xdaforums.com/showthread.php?t=1117897
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] nosaint:
This means we'll have to wait. Thanks anyway
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] novicejeep:
how to unbrick and flash OTA

If you get the "failed to update firmware try again using PC software kies or visit a server centre" message, please make sure you unplug the USB cable. That worked for me.

To Unbrick:

========

I also was stuck in bootloop ( alternate between samsung logo and the swirling electronis) after the 3.1 update.

I had to :

use the boot and recovery from http://droidbasement.com/galaxy/sys-backup/

and the system image from http://dl.dropbox.com/u/3140021/new.img.zip described here http://xdaforums.com/archive/index.php/t-1081325.html

The procedure is as follow:

when off ( make sure it is off and not with the battery charging screen. or from battery chargin screen... keep [power] down to turn off completely ), keep [power] and the [down-vol] keys down until ( this takes only about 4 seconds)

two icons ( USB and Downloading) appears

then

[Down-vol] to highlight USB icon

[Up-volume] to enter fastboot/bootloader mode

c:\dir>fastboot flash system new.img

c:\dir>fastboot flash boot boot.img

c:\dir>fastboot flash recovery recovery.img

c:\dir>fastboot -w <--- to wipe userdata and cache

c:\dir>fastboot reboot
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] cosimoss:
That's interesting because when I first fired up my 10.1 US was available on the update list. The language selection on the TAB is international. I thought this was an international version. Are you assuming its European just because of the update server selection?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dieseldaryl:
I have a Google IO Galaxy 10.1. I updated is last wek to 3.1 which worked great until a few days ago. It ended up on the fastboot screen for some reason and I was able to restart it and it worked for a few hours. Then it ended up going into this "infinite reboot" loop later on in the day and has beeen there since.

I was able to get the proper drivers for Fastboot to show up correctly as "Android ADB interface" in Device Manager (using the mods to the .inf file) but the "fastboot devices" still doesn't show anything. Anyone else run into this?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dracoaffectus:
YES! I updated to 3.1 days ago and everything was going fine until maybe 3 days ago. I came up from work and found my tablet stuck on a screen that said "Entering upload mode...Upload_Cause: undefined" I just held the power button until it came back on.

Again, everything was fine until about 30 minutes ago. I was using my Tab, reading some news, then put it down for a minute, when I came back to it, it was off. The Tab was plugged in and charging, but it had turned itself off, I turned it back on, got the "Upload mode" message again, turned it back on again, it came on but a bunch of apps throw up errors including Browser, Gmail, and Calendar plus a couple others. ALSO, when I tried to turn on Wifi it just said "Error" under the word "WiFi" on the settings menu (not in a separate popup, and no explanation) So I tried restarting again....

Now my Tab is stuck in a boot loop, pressing the power button gives me the message saying, "Entering upload mode... Upload_cause: undefined", pressing the power button again gets me stuck in another boot loop.

I had rooted my Tab before getting the 3.1 update, I didn't run into problems during the update process. Any ideas what I can do to fix it? Please ask any questions if you need more information.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] gbmitchell:
I don't know what is causing it, but try holding down both volume buttons and the power button until it power cycles.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Aleutia:
I have this exact same problem, all my apps suddenly failed and required force close. Turned it off, then it wouldn't turn back on and continued to loop the Samsung swishy logo and glowing and upload_cause error.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dracoaffectus:
Hmm, after holding it for about 5 seconds the device turned off. I kept holding it to see if anything else would happen but nothing did after about 30 seconds of holding all the buttons. What's the next step?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] gbmitchell:
Just hold the power button down for a while once it is off. I think this is what I did. If that does not work try a different button combination, my memory may be fuzzy. Also you may want to make sure it is charged.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dracoaffectus:
It just boot loops again when i do that. thanks for offering that suggestion, i'll keep trying.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dracoaffectus:
I got stuck in a boot loop, and i followed your directions to get my Tab working again, but I just noticed that my storage space has been greatly reduced. I used to have 32GB total storage, now the total is 13GB. Any idea why that happened?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] borinque:
I was stuck in this loop, the last two steps alone worked for me. Thankfully I had a backup. Glad it happened now, I was about to take a trip with just the 10.1 and no computer. Looks like the rooted Nook Color is going on a road trip instead!
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] _avatar:
I had this problem too, and was stuck in a boot loop / upload mode screen all night last night. Try the following:

1. Power off the device by holding POWER + VOLUME UP + VOLUME DOWN for 4-5 seconds.

2. Let the device sit for a while -- at least 2 minutes. Be patient.

3. Plug the device into *the wall charger.* It's important you plug it into the wall, and not just into the computer. Let it sit and charge for a minute or so. Don't turn it on yet!

4. Press the power button once, shortly; this should turn the screen on and you should see the "charging" battery meter. (This appears to be important -- you want to make sure you have the charging meter visible before moving on to the next step. I have no idea why, and it doesn't really make sense to me...)

5. Once you see the charging meter, press and hold the POWER button. About a half second later, begin holding the LEFT VOLUME ROCKER button as well.

If you do this correctly you should enter the bootloader, and not the UPLOAD MODE screen.

Also, to fix the boot loop I had to reflash my system and do a fastboot -w to wipe the data and cache partitions. Good luck!
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] ppwicho:
How make it works on MAC and other systems.

Well this steps i follow in OSX , but also i think can works on all systems.

The problem with fastboot its that the NVIDIA vendor usb id code isnt in the binary from HTC.

Whit the help of lsusb in ubuntu i dettect that the GALAXY TAB 10.1 has an NVIDIA usb vendor id ( http://developer.android.com/guide/developing/device.html ).

Galaxy ppwicho$ $ ls
boot.img	fastboot-mac	new.img	recovery.img

Galaxy ppwicho$ fastboot-mac flash system new.img -i 0x0955
< waiting for device >
sending 'system' (341796 KB)... OKAY
writing 'system'... OKAY

Galaxy ppwicho$ fastboot-mac flash boot boot.img -i 0x0955
sending 'boot' (8192 KB)... OKAY
writing 'boot'... OKAY

Galaxy ppwicho$ fastboot-mac flash recovery recovery.img -i 0x0955
sending 'recovery' (5120 KB)... OKAY
writing 'recovery'... OKAY

Galaxy ppwicho$ fastboot-mac -w -i 0x0955
erasing 'userdata'... OKAY
erasing 'cache'... OKAY

MacBook-Pro:Galaxy ppwicho$ fastboot reboot -i 0x0955
-bash: fastboot: command not found

MacBook-Pro:Galaxy ppwicho$ fastboot-mac reboot -i 0x0955
rebooting...

;) Just add the -i 0x0955 after the fastboot command.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] borinque:
Gah, in boot loop again. 2nd time in almost as many weeks. Anybody know the cause?

Thinking I might stick to 3.0, doing a restore and copying media back over isn't as fun as it sounds.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] adamrmcd:
I/O Galaxy Tab 10.1 boot-loop; 3.0->3.1 App snafu

I had the same problem for the first time last night (Entering upload mode... Upload_Cause: undefined) on my I/O Tab 10.1 running Android 3.1. I too have no idea what caused it, but it was working fine about an hour before I noticed it.

To resolve it, I followed the above steps. Flashing boot.img and recovery.img didn't correct it so I had to also flashthis system "new.img". Incidentally, this probably the worst possible filename to describe such a vital component. A better name would have been "blah.img".

Anyway, I did make one fatal mistake in this process, and I hope that my example serves as a warning to all those too anxious to correct this problem:

Those aforementioned *.img files are from a I/O Tab 10.1 with Android 3.0.

They did install correctly, and did restore my system to a 3.0 state. At the first opportunity I launched the 3.1 upgrade process under Settings -> About.

Once the 3.1 upgrade finished and booted, *all* of my free Android Market apps were lost!

I suspect that after first booting the 3.0 instance, I did not let the Market finish automatically reinstall my free apps (the paid apps were unaffected). Launching the 3.1 instance sent a signal to the Android Market of all the downloaded apps I currently had installed, which was none, and as such that was what was saved in my profile.

Don't be like me!