Database Users

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

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

Encrypting after root?

Has anyone been able to encrypt the N3 after rooting? I can't get it to go and it is mandatory for my work email to be pushed to my phone.\
edit: I've now tried manually using the settings menu. Even after setting a "high security password" it just flashed the android encrypt icon, reboots and then goes right back into the system. I've tried doing "fast encryption" as well and that doesn't work either.
edit 2: If anyone is wondering I didn't get this to work, however, after some searching I was able to find that Touchdown does encryption and will enforce all policies within the touchdown app itself keeping it separate from the rest of the phone. So I'm able to get my work email, not have to encrypt my entire phone, and stay within policy compliance. I just wish touchdown integrated with the stock calendar.... can't win 'em all.

Flying_Hellfish said:
Has anyone been able to encrypt the N3 after rooting? I can't get it to go and it is mandatory for my work email to be pushed to my phone.\
edit: I've now tried manually using the settings menu. Even after setting a "high security password" it just flashed the android encrypt icon, reboots and then goes right back into the system. I've tried doing "fast encryption" as well and that doesn't work either.
edit 2: If anyone is wondering I didn't get this to work, however, after some searching I was able to find that Touchdown does encryption and will enforce all policies within the touchdown app itself keeping it separate from the rest of the phone. So I'm able to get my work email, not have to encrypt my entire phone, and stay within policy compliance. I just wish touchdown integrated with the stock calendar.... can't win 'em all.
Click to expand...
Click to collapse
I've noticed this as well. Can't encrypt device when System reports "Custom". Currently it seems the only path to device encryption is restoring un-rooted stock firmware. . . .

This is driving me nuts since I have to encrypt my device do to Coporate net.
encrypt first then root - Don't work
Root first then encrypt- Don't work
can anyone else confirm this ?

greffel said:
This is driving me nuts since I have to encrypt my device do to Coporate net.
encrypt first then root - Don't work
Root first then encrypt- Don't work
can anyone else confirm this ?
Click to expand...
Click to collapse
im not a dev but have read about this issue from S3 and up and the only positive thing i have seen is that it can be possible when TWRP can be installed it "can" support encryption. i dont think you will find a solution without recovery option.

greffel said:
This is driving me nuts since I have to encrypt my device do to Coporate net.
encrypt first then root - Don't work
Root first then encrypt- Don't work
can anyone else confirm this ?
Click to expand...
Click to collapse
Confirmed. I've tried repeatedly to root-then-encrypt. All attempts failed. As soon as I un-rooted and rebooted, I was able to encrypt.

digittante said:
Confirmed. I've tried repeatedly to root-then-encrypt. All attempts failed. As soon as I un-rooted and rebooted, I was able to encrypt.
Click to expand...
Click to collapse
After weeks of trying different things.I Finally figured it out!!
First- Encrypt your device, before rooting
Second- Use the Kingoapp Root method, not Root De La Vega. When i used Root De La Vega, it would not work, and I would get the same error as everyone else. http://www.kingoapp.com/# is the link to the kingo root method. Its a One-Click method that took 10 minutes from start to finish. I just downloaded Multi-Window Manager to test the root, and it worked like a charm.

can you root your phone but still pass the device policy check for gaps for work?

Hi all,
I use my personal phone (specifically a phone that I own) for both home use and work use and I am considering rooting my phone so I can make some changes to the system UI file. I know that one of the checks that the "Device Policy" app checks for is to see if the phone is rooted so I was wondering if anyone has rooted their phone and successfully been able to pass the device policy check? Specifically I am looking to find out if:
1. would something like root cloak work?
2. if root cloak will not work, has anyone rooted the phone, made the changes, and then disable root leaving the phone running un-rooted so that the device policy check still succeeds? (I ask as I do not need permanent root, just access to fix some of the annoyances that come with stock android).
Thanks,
dave

Features availability without root

Hello, I'm trying to figure out if I understand everything correctly
1. Root always means knox counter goes >0
1.1. That always means Samsung Pay won't work even with magisk and stuff?
1.2 What else won't work? I've read Samsung Health might be not working, but I'm not sure why as it's perfectly working on unhidden root devices.
2. Adblocking w/o is possible? Disconnect Pro is only option?
3. bixby button is mappable to anything except actions like "imediately take picture"?
4. removing bloatware is possible with Package Disabler, right?
5. What is optimal non-root backup solution that would backup both app and data? I know Helium does that with USB Debugging, but I think Samsung should have something on it's own, right? Also How good is Samsung solution for non-Samsung phones?
6. Is USB debugging working fine? I'm concerned as heard using Secure Folders disabled it. That's the only thing to be aware of?
Thx

Ryotsuke said:
Hello, I'm trying to figure out if I understand everything correctly
1. Root always means knox counter goes >0
1.1. That always means Samsung Pay won't work even with magisk and stuff?
1.2 What else won't work? I've read Samsung Health might be not working, but I'm not sure why as it's perfectly working on unhidden root devices.
2. Adblocking w/o is possible? Disconnect Pro is only option?
3. bixby button is mappable to anything except actions like "imediately take picture"?
4. removing bloatware is possible with Package Disabler, right?
5. What is optimal non-root backup solution that would backup both app and data? I know Helium does that with USB Debugging, but I think Samsung should have something on it's own, right? Also How good is Samsung solution for non-Samsung phones?
6. Is USB debugging working fine? I'm concerned as heard using Secure Folders disabled it. That's the only thing to be aware of?
Thx
Click to expand...
Click to collapse
1.1 About Samsung pay, AFAIK, it won't work. At least for now.
1.2 Secure folder won't work as well.
2. There are many options for root adblocking.. In fact, very few available for non-root devices.
3. AFAIK, no. Need to open the camera app and press the capture button.
4. Hadn't info for that since never attempted one.. Sorry..
5. There is a PC option.. I heard it is named Samsung switch or something else? Never tried it so can't say much.. The last time I'm using backup un-rooted is using helium, and I think it is good one already..
6. Never tried using USB debugging, so can't say much..
Hope this partially helps..

Ryotsuke said:
Hello, I'm trying to figure out if I understand everything correctly
1. Root always means knox counter goes >0
1.1. That always means Samsung Pay won't work even with magisk and stuff?
1.2 What else won't work? I've read Samsung Health might be not working, but I'm not sure why as it's perfectly working on unhidden root devices.
2. Adblocking w/o is possible? Disconnect Pro is only option?
3. bixby button is mappable to anything except actions like "imediately take picture"?
4. removing bloatware is possible with Package Disabler, right?
5. What is optimal non-root backup solution that would backup both app and data? I know Helium does that with USB Debugging, but I think Samsung should have something on it's own, right? Also How good is Samsung solution for non-Samsung phones?
6. Is USB debugging working fine? I'm concerned as heard using Secure Folders disabled it. That's the only thing to be aware of?
Thx
Click to expand...
Click to collapse
2 - https://forum.xda-developers.com/galaxy-s8/themes/adhell-2-rootless-ad-blocking-t3663559
4 - https://forum.xda-developers.com/galaxy-s8/how-to/how-to-remove-oem-bloatware-s8-s8-t3654687
3 -bxactions, click to open and then click again to take pic

Ryotsuke said:
Hello, I'm trying to figure out if I understand everything correctly
1. Root always means knox counter goes >0
1.1. That always means Samsung Pay won't work even with magisk and stuff?
1.2 What else won't work? I've read Samsung Health might be not working, but I'm not sure why as it's perfectly working on unhidden root devices.
2. Adblocking w/o is possible? Disconnect Pro is only option?
3. bixby button is mappable to anything except actions like "imediately take picture"?
4. removing bloatware is possible with Package Disabler, right?
5. What is optimal non-root backup solution that would backup both app and data? I know Helium does that with USB Debugging, but I think Samsung should have something on it's own, right? Also How good is Samsung solution for non-Samsung phones?
6. Is USB debugging working fine? I'm concerned as heard using Secure Folders disabled it. That's the only thing to be aware of?
Thx
Click to expand...
Click to collapse
#1 is not true and a common falsehood repeated here often.

partcyborg said:
#1 is not true and a common falsehood repeated here often.
Click to expand...
Click to collapse
I would appreciate if that was supported by some kind of links. 100% of information I've seen so far is "knox counter is not revertible" and "with knox>0 Samsung Pay, Samsung Health and Secure Folder won't work"

Ryotsuke said:
I would appreciate if that was supported by some kind of links. 100% of information I've seen so far is "knox counter is not revertible" and "with knox>0 Samsung Pay, Samsung Health and Secure Folder won't work"
Click to expand...
Click to collapse
Knox the efuse backed device in your phone which turns 0x1 and is not reversable has absolutely nothing to do with whether your device is rooted or not. It is concerned with only one thing, and that is has your device had unsigned boot images written to it. That's it, full stop. In fact, it is currently 100% for a snapdragon (n America) device to *ever* be 0x1 because the bootloader is locked and therefore it is impossible to flash any unsigned code in the first place.
I can provide you with links saying that a thing is not affected by another thing because, well, they aren't related. I would be hard pressed to find proof that monkeys don't fly out of my ass either, but I can assure you they don't.
The reason for the pervasiveness of this incorrect information is that the installation methods of some root management systems involve the writing of a custom boot image, usually to get around things like selinux without compromising safetynet. However it is that boot image patch&flash that causes 0x1, it would happen whether you also rooted or not, and if you choose a traditional systemroot (and have a signed kernel that is permissive, but all Samsung's do), then you can be rooted all day and knox isn't even capable of knowing much less changing your unsigned flash count

partcyborg said:
The reason for the pervasiveness of this incorrect information is that the installation methods of some root management systems involve the writing of a custom boot image, usually to get around things like selinux without compromising safetynet. However it is that boot image patch&flash that causes 0x1, it would happen whether you also rooted or not, and if you choose a traditional systemroot (and have a signed kernel that is permissive, but all Samsung's do), then you can be rooted all day and knox isn't even capable of knowing much less changing your unsigned flash count
Click to expand...
Click to collapse
But is there a root for S8 (Exynoss one G950FD to be specific) that is not triggering knox->1? I kinda assumed such thing does not exists, would be happy to know I'm wrong. If there is zero-knox root, is it still hideable like magisk to be still able to pass SafetyNet?

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!