Galaxy Tab 10.1 LE (Google I/O) Android 3.1 update is out! - Galaxy Tab 10.1 General

Thanks to Samsung for the prompt update! Thanks to Google for the free tablet!
To update, just go to Settings->About Tablet->Software Update->Check for Updates.
If you don't have a Samsung account, you will have to create one. I'm in the US, but there wasn't a choice for that so I chose UK and it worked just fine.
It will download the update and reboot to install it. The download is pretty quick, but the update takes quite a while to apply. Once it gets to about 73% complete or so, the update inches along very slowly. So just be patient.
After the update, the lock screen background is different but all my settings were preserved.
About tablet (after upgrade):
Android version: 3.1
Kernel: 2.6.36.3
Build: HMJ37.UEKF3 P7510UEKF3
EDIT:
- The upgrade does not make you loose root access. This tablet really is a dream for developers.
- I don't see any evidence of any TouchWiz components anywhere. It still appears to be stock.
- Since this is a WiFi tablet, there's still no access to the Android Video Store (plus I'm rooted). Supposedly that is only enabled on 3G tablets for some reason. Oh well, who cares.
Have fun!

Hi, has it got the awful touchwiz built in or is it still "vanilla" android?
My thanks, like you, to samsung for the update and the tab

I have rooted my IO tab and froze some of the samsung system apps with titanium backup. I'm hesitant to update until I get some more information.

I don't think if touchwiz is ready yet. It will be updated later...

Does this break root or CW recovery? Or can you boot into fastboot after the update?
tau_ said:
I have rooted my IO tab and froze some of the samsung system apps with titanium backup. I'm hesitant to update until I get some more information.
Click to expand...
Click to collapse

Same here, rooted, apps frozen with TB.... not at all worried at the quality of 3.1 update versus 3.0.1 delivered on the tab at IO but would have to fall on my ceremonial sword if I updated and ruined a lovely piece of kit by subjecting it to touchwiz... More than my honour could handle
No disrespect but not interested in comments repeating ill informed speculation from" uninformed" blogs, just want a straight answer, so if you are still online ageitgey can you tell us yes or no as regards TW - thanks

Thanks a ton!

Downloading as we speak.

There is no sign of TouchWiz in 3.1. It looks completely the same as before, except minor differences (new lock screen background, slightly different wifi icon, etc).
Root was preserved after my upgrade. RootExplorer still works fine and was granted root permissions.
I didn't have Titanium installed, so I can't comment on that. But I doubt there would be an issue.

anybody else having issues updating?
I am getting
"Failed to update firmware. Try again useing PC software (Kies) or visit a Samsung service centre."
not really sure what to do from here.

Concur, no sign of touchwiz, root preserved, titanium works fine. Bizarrely background color of text box when writing this has changed from white to blue and font is dark blue. Apps seem to work ok.
Well report other changes as and when found

onovich, you are not alone. I get the same thing.

onovich said:
anybody else having issues updating?
I am getting
"Failed to update firmware. Try again useing PC software (Kies) or visit a Samsung service centre."
not really sure what to do from here.
Click to expand...
Click to collapse
Maybe try what it says and try kies ( latest version of course and make sure you have installed latest drivers for the tab in kies- tools menu-" install driver")

stinky73 said:
Maybe try what it says and try kies ( latest version of course and make sure you have installed latest drivers for the tab in kies- tools menu-" install driver")
Click to expand...
Click to collapse
I did, it doesn't connect via kies. It just spins saying connecting. although windows has no problem recognizing it.

oh thank god, ive been checking everyday for a month
any ideas on how to get the android video store working

any official change log
is usb host mode enabled

mine says the same thing are you rooted with clockwork as your recovery?
onovich said:
I did, it doesn't connect via kies. It just spins saying connecting. although windows has no problem recognizing it.
Click to expand...
Click to collapse

Kies says that "This version of the device cannot be updated".
OTA update doesn't work because I've rooted the ROM and installed busybox.
Probably after reverting to stock ROM via Odin OTA update will work?

Updated here, not too many changes noticeable to the end user. Wonder about USB Host - I suppose we need an adapter of some kind because of Samsung's proprietary 30pin port?

so whats the official word on updating
will it work if you are rooted , or unlocked bootloader, or both

Related

AT&T Now Bricks Modded Galaxy Tabs

What used to be a simple patch to permit AT&T Galaxy Tabs to download apps from sites other than the Google Market is no more. We recently got our Tab back from the Samsung repair facility and it was wiped clean and loaded with a new Android version that now puts your Tab in an endless boot loop if you attempt to patch the config setup to permit downloads from outside Google Market.
Simple solution: DON'T BUY AT&T-BRANDED GALAXY TABS.
If there were some sort of unlimited data plan, this kind of behavior might be warranted but since AT&T charges by the amount of data you consume, there's really no excuse for crippling these devices... other than just being assholes!
Not entirely sure what you're referring to here. I have an AT&T SGT and it works just fine with sideloaded apps.
Did you run SuperOneClick root and then enable non-market apps?
Either way, nuke that horrid stock ROM with one of the Euro roms and you'll never have to worry about AT&T's crippled version again.
Yeah, but...
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
What version of firmware did your Tab come back with?
What method did you attempt to enable side loading?
I find this very hard to believe because every single ATT Android device to date has been able to side load after a simple 1 bit edit of the device settings db.
I believe that you had problems with the SuperOneClick app but there is a much cleaner / safer way to do it.
Sent from my SGH-I987 using Tapatalk
NerdUno said:
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
Click to expand...
Click to collapse
I don't believe my ATT SGT came with a protected bootloader, and if I'm not mistaken, AT&T hasn't released any firmware updates via KIES or OTA. So while there's always the possibility of Samsung "screwing" us all with that mess, it's only been seen on the leaked firmwares. Not that I don't put it past the big blue DeathStar to opt to use something like that to prevent people from avoiding their preloaded garbage....
I'm happy I liberated my device from the clutches of the Evil Empire, and will gladly look to XDA for my future upgrade paths.
Could just be a bad software flash from factory. A number of t-mobile vibrants couldn't get to restore via volume up/down power because of a buggy flash file they put on a certain build date
Sent from my Galaxy Tab

Cannot connect go Kies to update to ICS???

Hi all.. I have a Galaxy Tab 10.1 gt p7500 one month old, and I saw that there is finally an update to ICS. I still dont got it try mobile netowork (t-mobile - Macedonia), so i read that I can update thru kies. The problem is, I cannot connect mu tab to kies??? I dont have an USB option on Wireless and Networks and it connects in MTP mode. Is there any way to fix this problem and if not, how can I update my tablet to stock version of ICS in some other way? Please help...
Regards
It sucks that kies won't work now that ics is out. I'm having trouble updating mine as well.
Kies is not a product
I have tried for almost a year now to get my tab recognised by Kies, but only a factory reset will get Kies to recognise my tablet. The moment I install my own software on it again that disappears.
Kies via Wifi has no firmware upgrade option, sad to say, so best wait for OTA upgrade.
I am waiting too for the OTA as that POS named Kies is not working for me. But it is coming, just be a little more patient. It is rolling out in the US, maybe even in Canada. The rest of Europe will follow, or you can download from samfirmware.com, and do it over USB via Odin (lots of threads covering that)...
Best of luck!
I did a reset in anticipation of the update and was able to do the update through Kies
with no problem.
I had 2 Galaxy 10.1, one of them could only connect wireless for update, not with Kies, the other one could not update OTA, only with Kies... and to connect I had to reset the device, Kies is really worth nothing...
One of the reasons why I am only using custom ROM
I fought with it for a couple hours last night, and finally resorted to a factory wipe. Then it was fine. Just means a few hours of reinstalling and configuring widgets, but still annoying as hell that after 2 years Kies doesn't work with 3.2 stock rom.
ProximaC said:
I fought with it for a couple hours last night, and finally resorted to a factory wipe. Then it was fine. Just means a few hours of reinstalling and configuring widgets, but still annoying as hell that after 2 years Kies doesn't work with 3.2 stock rom.
Click to expand...
Click to collapse
It's far worse: I could never connect to Kies. One day I just wanted to test connecting to Kies, so I did a Backup with Titanium Backup and then a factory reset. Thereafter I could connect without any issues. So I restored all settings - user and system data with everything! - from my TB and expected not to be able to connect after doing that. But oh wonder! I still could connect to Kies!
But about a week later it was again like before: No connection to Kies :silly: That was the last time I started the software on my PC :cyclops:
After the update, and after I updated the apps that are included with the tab, and after I reinstalled all of my apps,
I tied Kies again. Tab connected wih no problems.
Looks like that's one of the things fixed in ICS.
From what I gathered from the internet and other forums the problem with Kies apparetly is that if there is a file with a filename that kies doesn't like, it won't connect. The big problem is find that file or files
Sent from my GT-P7510 using xda app-developers app
Kies kies bye bye
digitalundertaker said:
From what I gathered from the internet and other forums the problem with Kies apparetly is that if there is a file with a filename that kies doesn't like, it won't connect. The big problem is find that file or files
Click to expand...
Click to collapse
That is my understanding too. But when I remove all non-essential files (i.e. "personal" files) from the system it still did not work... So it must be one of the files related to a product.
To find out which one (or which ones...) will take a lot of time, and I do not want to spend that much time on a POS product like Kies... So for now I will wait for the OTA update, or the end of August 2012, whatever comes first. If it still is not there at the end of this month I will go to one of the custom ROMs, and never look back.
XDA is no longer worth my time.
TimOster said:
It doesn't have to connect to Kies in order to do the update. Mine didn't.
Put it in download mode, have Kies running, connect the cable and run the Firmware upgrade and initialization from the tools menu.
Click to expand...
Click to collapse
That IS an interesting concept. Never thought that might work. I have given up, surrendered to Kies, reset the GTab, got Kies working, but alas, no update here in Canuck Territory... So all for naught!
I will try your approach on the other GTabs I've got...
Thanks for the tip!
-- EDIT --
Guess what? When running Firmware upgrade and initialization I get the message: "'GT-P7510' does not support initializing."
And that is all I can do, no upgrade via that path possible...
I did a factory data reset and upgraded to ICS via wi-fi. And my 7510 was still rooted

[PSA] Information Regarding Firmware Version 5.1.1 A.K.A. ROOT

Root Method​Amazon has just released a new firmware update, blocking the fastboot commands necessary for root/custom ROMs (fastboot boot). We need more information about this update. If people could update their tablet to this latest version without getting it stuck in the botloop, we could see the information regarding the update and get root out for this ROM ASAP. Thanks to anyone who sacrifices root/ROMs for development.
List of things you can't do:
Downgrade to an earlier release
Boot a .img from Fastboot
List of things you can do:
Install and use the Google Play Framework and Services
Root
Install Custom ROMS via FlashFire
Remove Lockscreen Ads
Remove Amazon Bloatware
Feel free to comments things that worked/didn't work on your device.
ANYONE WHO IS ON 5.0.x AND WANTS TO GO TO 5.1.1 WITHOUT ANY COMPLICATIONS AND KEEPING TWRP, GO TO THIS LINK: http://forum.xda-developers.com/showthread.php?t=3265594
Can anyone test if the Google Framework Install tutorial works on this update?
It does.
However, DON'T TRY TO DOWNGRADE BACK TO THE 5.0.1 FIRMWARE. IT WILL BRICK YOUR DEVICE. I found that out the hard way. It's stuck in a preloader reboot-loop.
Added list of what you are able to do on the update.
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
You have to go through the setup, but originally I just skipped that part, even though I was next to a Starbucks, and it didn't connect.
Doesn't Starbucks wifi require you to click to agree to their terms of use before you can freely browse or download? So Internet would not actually be available initially to the update script.
Pretty much, I trust amazon on this issue, as far as I can throw them. I don't want to presume that a OTA proccess won't silently connect, while the Fire otherwise appears to be waiting for the ok to connect to wifi.
Bloat removal
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
craigs23 said:
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
Click to expand...
Click to collapse
Thanks, added.
This is bullsh!t. the ENTIRE reason about 5,000 people bought this tab last week is because of root, fastboot and CM. If I get my tab soon I can offer any assistance you need. I'm not sure if it will be possible to dump any part of the system, boot, etc. without fastboot or twrp, but I'm sure we could figure something out.
blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
When I setup mine it asked to turn on wifi I skipped it and said later.
Sent from my SM-N910T3 using Tapatalk
Has anyone tried kingroot on 5.1.1?
Experts please take a look at this
What was changed in OS 5.1.1?
If anyone can get the frimware update or capture it id like to test it out
running 5.1.1 & all I could manage to load was Google Account manager. The rest (Framework Services, etc) says something like "App not installed" & nothing else, every time I try.
scratch that..... found found a couple that did load for me.
Damn! I did this (tried to downgrade, got bricked) a day before you posted this. I should probably replace mine...
My unrooted Fire upgraded to 5.1.1 last night before I had any idea it was coming. I'm willing to try whatever is needed to assist with further research if I could be of any help.
unlikely it would work, but did anyone on 5.1.1 try
Code:
fastboot -i 0x1949 boot twrpfilename
Sent from my KFFOWI using Tapatalk
5.1.1 update file
Here is the 5.1.1 update file
snap42.com/update-kindle-full_ford-37.5.4.1_user_541112720.bin.zip

New Galaxy Tab S5e user - Not pulling updates

Hi everyone.
I just recently got a used S5e, mostly for the Dex capability. I am a consultant, so sometimes I'm in a location where I need a desktop, but don't always have room for my 15" laptop. I haven't had a Samsung device in years... preferring brands with easy root and a nearly limited skinning (currently, OnePlus devices... basically).
I had kind of resigned myself to not having root on this device, since it is a Samsung, so I was surprised when I came on here to see if anyone else was having the update problem, I found root threads. Currently, my device looks like it's on the May 2019 update (One UI 1.1, Android 9, Build PPR1.180610.011.T720XXU1ASED).
Still trying to resist rooting the device, especially since I saw the no-root debloat thread. But I would like to know how to get this stupid thing updated. From what I've read, it has to do with an XML file containing a Samsung URL that returns a 404 when queried manually. The software updater doesn't reflect that, though... and just says you're up-to-date.
So if I can root this and flash a debloated ROM, that would serve a few purposes. Otherwise, if there's a way to force an OTA (or find it and download it to the SD card), that would be fine, too.
Any advice.
Flapjack said:
Hi everyone.
I just recently got a used S5e, mostly for the Dex capability. I am a consultant, so sometimes I'm in a location where I need a desktop, but don't always have room for my 15" laptop. I haven't had a Samsung device in years... preferring brands with easy root and a nearly limited skinning (currently, OnePlus devices... basically).
I had kind of resigned myself to not having root on this device, since it is a Samsung, so I was surprised when I came on here to see if anyone else was having the update problem, I found root threads. Currently, my device looks like it's on the May 2019 update (One UI 1.1, Android 9, Build PPR1.180610.011.T720XXU1ASED).
Still trying to resist rooting the device, especially since I saw the no-root debloat thread. But I would like to know how to get this stupid thing updated. From what I've read, it has to do with an XML file containing a Samsung URL that returns a 404 when queried manually. The software updater doesn't reflect that, though... and just says you're up-to-date.
So if I can root this and flash a debloated ROM, that would serve a few purposes. Otherwise, if there's a way to force an OTA (or find it and download it to the SD card), that would be fine, too.
Any advice.
Click to expand...
Click to collapse
If I'm understanding you right, you just want an OTA update applied? If that's the case, Frija is what you want to get the latest firmware for your device, and Odin will be your flasher. For stock rom flashes you don't even need an unlocked bootloader, much less root!
There are a ton of guides for Odin available, but still, if you have any questions please post!
Thanks for the reply!
I've used Odin quite a bit in the past, but I do know different situations need different files, so I'll probably do a quick refresher.
As for root, it definitely is a nice-to-have, mostly to remove bloatware, but if the debloat thread here works pretty good (and someone has info on just how much I can remove and keep Dex functionality), I would love to know that as well.
So, I am having a new problem. Using Frija, I downloaded the latest update. However, no matter what I do, I can't get a PC to recognize the tablet in download mode. It just says something about Windows not being able to recognize the device. In Device Manager, it says: "Device descriptor request failed". I've tried with and without the Samsung drivers, with three different USB cables, on two different PCs.
I'm worried that something is physically wrong with the USB port. That doesn't really make sense, though... as it charges fine, and shows up in Windows correctly once it's fully booted to Android.
**EDIT**
False alarm. I needed to press "up" again after getting into download mode and connecting the PC. So odd. It's updating now!

Will taking OTA update on S8 affect my ability to root or install custom bootloader?

Hi!
I picked up a second hand Galaxy S8 (SM-G950UI 64GB) over the summer with plans to root it and install a custom ROM. I haven't activated it yet, but I was using it on my home WiFi and was notified that it downloaded an OTA update and it would be installed on the next boot. Since then I haven't touched it because I know that some updates can complicate or nullify the ability to root or install a custom bootloader, ROM, etc. I've done some searches on how to prevent the install, but haven't found anything except for how to disable your phone from downloading it to begin with. Now that the update is downloaded to my phone, is there a way to halt it's installation before I move forward with activation and customization? Or is this even a concern I should be worried about?
Thank you!
bump
factory reset, if no gogle account. if there is google account the phone is doomed.
or just neglect the update and directly boot in download mode, uncheck auto reboot in odin options tab, and flash twrp. also s8 can potentially get to Android 11, but latest is 10, you can ask me if needed
PEZ Dispenser said:
bump
Click to expand...
Click to collapse
updated already?
jjgvv said:
updated already?
Click to expand...
Click to collapse
I'm not entirely sure, it may have updated in the past and I didn't notice and now it has another update. I just removed google account and factory reset which seems to have cleared the update, thank you. Unfortunately I'm reading that my g950ui is pretty locked down as far as custom recovery and roms are concerned to begin with, so this is kinda irrelevant after some further research this morning.
PEZ Dispenser said:
I'm not entirely sure, it may have updated in the past and I didn't notice and now it has another update. I just removed google account and factory reset which seems to have cleared the update, thank you. Unfortunately I'm reading that my g950ui is pretty locked down as far as custom recovery and roms are concerned to begin with, so this is kinda irrelevant after some further research this morning.
Click to expand...
Click to collapse
Probably type on build number 7 times and send me A screenshot? Is oem unlock greyed out?
also remember to also delete samsung account if there is,and remove screen lock.
this?
jjgvv said:
this?
Click to expand...
Click to collapse
There is no samsung account and I removed screen lock.
OEM Unlocking isn't even a greyed out option on my phone. It's completely removed from the menu.
maybe try flashing G950F firmware in odin?
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
Wilk it rebrand or Just bricked?

Resources