Database Users

K1 - 6.0.1 Rollout Day? AH has just posted....

Android 6.0.1 Update Rolling Out To NVIDIA SHIELD Tablet K1
Anyone see anything yet? Sounds like a few good fixes plus the official Vulcan API..
1.2 K1 Update from Nvidia site
Supports the new Vulkan™ API for high-efficiency access to SHIELD’s graphics hardware
Adds Android 6.0.1 changes
Repositioned Navigation Buttons in Landscape mode & Updated Emojis
Double Tap Power Button to launch SHIELD Camera app
Do Not Disturb Until Next Alarm
Support for Android Doze mode & additional power optimizations
Adds USB MIDI support
Adds memory compression enhancement
Improved Wi-Fi connectivity when waking from sleep
Fixed Compass functionality
Fixed Gamepad Mapper issues
Fixed issues with moving apps to SD card
Fixed Doom 3 HDMI output issue
Repositioned Lasso Capture icons in landscape mode
Update to Android 6.0 Security Patch Level March 1, 2016
Overall stability and security enhancements

I got the update a few hours ago, we finally got the new emojis!
Sent from my SHIELD Tablet K1 using Tapatalk

Just got it here too ..

Anyway original Shield users (Y01) can install this update?

I unrooted and restored stock recovery to get the installation process going (same procedure as always), but unfortunately, I always end up getting the "Error!" message after a while, thus having to manually turn off the system. I didn't have any issue like this with Update 1.1, and I can't really think of any substantial change to my system since then.
Anyone got any tips?

This update seems to have broken loading OBB zips from the external SD.

Ralek85 said:
I unrooted and restored stock recovery to get the installation process going (same procedure as always), but unfortunately, I always end up getting the "Error!" message after a while, thus having to manually turn off the system. I didn't have any issue like this with Update 1.1, and I can't really think of any substantial change to my system since then.
Anyone got any tips?
Click to expand...
Click to collapse
I got the same message.
I could press the Power button and the volume-up button once to get into recovery and it shows me:
Verifying current system...
"EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6699412:2dedcfe2f04<very large hex>" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
After this I also fastboot flashed the boot.img matching the recovery.img and got a different message:
system partition has unexpected contents
This leads me to believe the boot.img, recovery.img and system.img (and maybe the blob) should come from the same release, in my case I downloaded the 1.1.1 release from Nvidia. I don't have time to keep testing this, but will do tomorrow.
UPDATE: I flashed the system.img of the 1.1 update and then the update to 1.2 is successful.

Hi!
techboydino said:
Repositioned Navigation Buttons in Landscape mode
Click to expand...
Click to collapse
Can someone please post a screen shot of what that looks like? There are several complaints about it over at the nvidia forum but no one has described exactly what's bad with the new button position.
If they made it the same as phones where the bar is placed along the right (short) edge in landscape I'm gonna avoid this update like the plague, as a Lefty I hate that.
/lakris

They're more useful when you're holding the tablet with two hands.

DR_HAX34 said:
They're more useful when you're holding the tablet with two hands.
Click to expand...
Click to collapse
Thanks! Looks like I can live with that change.
/lakris

Any guide on Installing this for TWRP users? I would really appreciate that

+1 for a K1 already rooted on android 6.0

philipp21897 said:
Any guide on Installing this for TWRP users? I would really appreciate that
Click to expand...
Click to collapse
Kasimodo said:
+1 for a K1 already rooted on android 6.0
Click to expand...
Click to collapse
Hi!
I was on vulkan 6.0.1 (dev preview) and kali kernel etc, with TWRP 3.0.0 and Supersu installed, I've only downloaded it from Settings Update( v1.2 I'm on K1 w/o pen) and after that reflashed TWRP's recovery from fastboot and then SuperSu in TWRP's menu (also xposed installer must be reflashed or custom kernel and all other stuff that doesn't survive to OTA)

SHIELD Tablet K1 Software Upgrade 1.2 - FULL |6.0.1 - Release Notes
Full OTA:
productionBL-droid-signed-sb_na_wf-full_ota-40827_689.9034.20160411091106.zip

thank you Zarish.
But how to install it?
FYI, my tablet K1 is updated to 1.1 (Android 6.0) and rooted but I haven't installed TWRP Recovery. I have only boot on TWRP image (with command "fastboot boot twrp.img") and then flashed SuperSu.
Do I have to boot on TWRP with the same command (fastboot boot twrp.img) and then install the "OTA 1.2.zip" you shared?
Sorry for this noob question but I would like t be sure before starting something...
Best regards

Beyond castrwilliam, had anyone run unto issues with this update?

I have made SD card as internal storage can I download update as usual ?

Kasimodo said:
thank you Zarish.
But how to install it?
FYI, my tablet K1 is updated to 1.1 (Android 6.0) and rooted but I haven't installed TWRP Recovery. I have only boot on TWRP image (with command "fastboot boot twrp.img") and then flashed SuperSu.
Do I have to boot on TWRP with the same command (fastboot boot twrp.img) and then install the "OTA 1.2.zip" you shared?
Sorry for this noob question but I would like t be sure before starting something...
Best regards
Click to expand...
Click to collapse
Yes, you could boot TWRP that way and then install the .zip (install SU again also).

DR_HAX34 said:
They're more useful when you're holding the tablet with two hands.
Click to expand...
Click to collapse
Can we use gravitybox to swap the back and recent apps button?

NinjaCoool said:
Can we use gravitybox to swap the back and recent apps button?
Click to expand...
Click to collapse
Don't know. I'm not an Xposed fan, I think it spends way too much battery and causes errors that shouldn't happen to some apps.

[GUIDE] Systemless Root of your Nook Tab S2 710

With Barnes & Noble now selling the Galaxy Tab S2 710 (32gb) for $299 in the U.S. (and an extra 10% off if you're a B&N member), I picked one up yesterday and immediately came here to research rooting and set up. What I found were a lot of guides written a while ago, and a lot of confusing (at least to me) information. So I thought I would consolidate, in one place, in a new thread, what I eventually did, on the assumption that there might be a lot of new Tab S2 owners in the coming weeks. Obviously, you undertake these steps at your own risk, and YMMV. Also, hopefully equally obviously, none of the fantastic tools here are original with me -- credit goes to all those, like chainfire, ashyrx, wanam, engine95 and many more who have built and/or developed them.
1. If your Tab comes with anything but 5.1.1 XXU2BPB1, feel free to take the OTA update. In the US, it's the most current build as of 4.30.16 and you will still be able to root.
2. If you don't already have it, download Odin 3.10.7. You can find it here: http://forum.xda-developers.com/showthread.php?t=2711451
When you run Odin in Windows, probably better to run it in administrator mode (right click on the icon), although I haven't always found that to be necessary.
3. Flash a Custom Recovery using the PDA tab of Odin. Put your Tab into Download mode by turning it off, then pressing and holding the Home, Power and Volume Down buttons all at the same time. When the download screen comes up, press the Volume Up button to continue. Now you're ready to attach your Tab to your PC. Load TWRP 3.0.2-1 from Ashyx's thread here: http://forum.xda-developers.com/tab-s2/development/recovery-twrp-2-8-7-x-lollipop-5-1-1-t3205686 into Odin. Follow his instructions carefully -- once the custom recovery flashes, you have to manually reboot into the new recovery (so untick the auto-reboot option in Odin) or else your new custom recovery gets overwritten and you go back to your stock recovery.
4. Backup your Stock Rom -- While you're still in TWRP (or if you've already rebooted, go back to it), it would make sense to do a full backup of your stock ROM. That way you can restore your Tab to its original state if you ever need or want to.
5. Root -- Here's where I found the most confusion on these forums. You can do a systemless root -- i.e., keeping a stock, SE Enforcing, kernel (as opposed to flashing a permissive kernel and always getting the red SE Noneforcing Kernel message on a reboot and/or needing to use CF-Auto-Root). All you need to do is install Super SU 2.71 (BETA). Get the zip from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and put it on your Tab. Then flash using the "Install" choice within your TWRP recovery. Reboot -- and when TWRP asks you whether you want to install SuperSU because you're not rooted -- you have to say "NO" (OK, that's counterintuitive, but chainfire's instructions are clear).
5. Debloat -- That's beyond this thread's scope, but I recommend Titanium Backup from the Play Store. If you want to get rid of the "Nook" logo on reboot, flash the zip file from post #2 of Engine95's thread (using TWRP) found here: http://forum.xda-developers.com/tab-s2/development/rom-neked-nook-oj1-5-1-1-710-t3317823
6. SD Card Fix -- if you find your third party apps can't write to your SD Card, the attachment below describes how to fix it. If this type of editing scares you (make a backup first!), the Play Store app SD Card Fix supposedly still works with Lollipop and you can try that.
7. Netflix Fix -- for some reason, Netflix doesn't like root on the Nook Tab. The fix for this is as simple as renaming the file "system/lib/liboemcrypto.so" (using a root explorer of your choice) as "system/lib/liboemcrypto.so.bak"
8. Xposed -- I happen to like Xposed and don't find it messes up anything, while giving you a ton of customization options. Installation is a two-step process. First, find the correct version of wanam's Xposed zip from here: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960, and flash it using TWRP. For Lollipop on the S2, I used his SDK 22-arm version (SDK 23 is for Marshmallow). Don't worry if the reboot takes a long time -- that's normal. Then, once rebooted, simply install wanam's Xposed apk (XposedInstaller_3.0_Alpha4) that's available in the same thread.
That's it. I hope this saves some of you a lot of my trial and error, and, if it does, please press the "thanks" button.
EDIT -- Here's a #9 I just discovered --- Microsoft Office apps, although pre-installed on the device, will not open once you're rooted (or maybe it's just flashing TWRP that does it). Moreover, if you uninstall and try a re-install from the Play Store, if you're like me, you'll get a device not compatible message. My solution was to sideload the apks (e.g., Word, Excel and Powerpoint) from my Note 4, but I suspect you could also change your device ID within your build.prop file (backup first!) and get a similar result.
ANOTHER EDIT (5.2.16) -- #10 -- I can't get Google Play Movies to work at all on my T710 after rooting. Tried renaming libemcrypto.so without luck. Tried editing boot.prop to disguise myself as a Nexus 10. Tried the Xposed module Root Cloak. All no good. Any suggestions welcome!

Thanks! I just got a new nook and have started to come into these forums and also noticed the old and randomly updated threads. I appreciate the clear instructions. Are there any roms right now that you are recommending?

rawdikrik said:
Thanks! I just got a new nook and have started to come into these forums and also noticed the old and randomly updated threads. I appreciate the clear instructions. Are there any roms right now that you are recommending?
Click to expand...
Click to collapse
Sorry, I'm trying to stick with stock. Engine95's rom seems to have some happy users though....

how do you manual reboot to recovery mode after download mode? i have tried the (pwr+vol up+home) but it does not work at all.. once i reboot normally the TWRP which i flashed cannot get installed at all. I need HELP!

Stock ROMs Factory v6.1 , v8.3 , v8.4 , v8.5 , v8.7, V9.0, V9.2-patch : v21

CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs

I flashed this but I didn't get the custom boot logo.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.

mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine

Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.

It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo

mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?

Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out

linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0

Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.

Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?

detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.

The app downloaded from f-droid worked for me as well, many thanks!

Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.

Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.

Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!

OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install

Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3

mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.

[RECOVERY][TWRP][Unofficial] Galaxy Tab Active 2 - TWRP 3.2.3-0 [Exynos]

Disclaimer
**** All flashing is done at your own risk! ****
**** While this recovery should not break your device, don't come back here blaming anyone if it does! ****
This is a TWRP 3.2.3 build based on Android 7.1.2 source kernel for the Galaxy Tab Active 2 (codename: gtactive2lte) - Exynos. The "tar" file should be installed using Odin (tested on Odin 3.12.3).
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.(DO NOT GET FOOLED.)
Installation process:
1. Flash Stock ROM.
2. Flash recovery using Odin (AP = recovery.tar).
3. Load recovery immediately after flashing.
4. Format data (Will erase /data partition).
5. Reboot to recovery.
6. ADB push SuperSU to internal storage / insert SD-Card with SuperSU.zip.
7. Flash SuperSU using TWRP install option.
8. Reboot to system (May bootloop several times. Wait untill system loads).
Bugs:
1. ADB sometimes doesn't work in MTP mode. Need to manually change to PTP in order to get adb usage.
2. Bad label in ADB shell + bad characters appearing while writing through AD. Works well out of recovery and on recovery's terminal.
Sources:
Device tree - Device tree
Kernel - Kernel
TWRP sources - platform_manifest_twrp_omni
SuperSU - SuperSU-2.82-SR5
Recovery download:
Recovery
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 08/19/2018 (DD/MM/YYYY)
Contributors:
Many thanks to TWRP's developers for the support on building this recovery.
Special thanks to CaptainThrowback, Bigbiff and Dees_Troy on TWRP-freenode and Ashyx on xda-developers.
Please post any bugs you encounter. I will try to fix any issues that come up.

Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo

slomo2 said:
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
Click to expand...
Click to collapse
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.

Shedaim said:
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Click to expand...
Click to collapse
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?

slomo2 said:
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
Click to expand...
Click to collapse
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.

Shedaim said:
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Click to expand...
Click to collapse
This will be great, let me know if I can help, perhaps document.

slomo2 said:
This will be great, let me know if I can help, perhaps document.
Click to expand...
Click to collapse
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository

Shedaim said:
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Click to expand...
Click to collapse
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
Click to expand...
Click to collapse
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.

7.1.1 is what The T397U should have already been on before you started. Mine is and I have not installed this recovery as of yet. Just wanted to let you know it's where it should be.

slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
Click to expand...
Click to collapse
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.

Shedaim said:
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Click to expand...
Click to collapse
Sorry for delay. I've done the following tests all with the expected results. The only thing I noticed compared to previous installations of TWRP that I've performed ( some years ago ) is that the load time of recovery seems long at 1:15. Also a message about "RECOVERY NOT SEANDROID ENFORCING" which I suspect is normal. Tablet has been working without incident. Thanks again.
Blocking checks
- Correct screen/recovery size
- Working Touch, screen
- Backup to internal/microSD
- Restore from internal/microSD
- reboot to system
-ADB ( yes, if this means being able to access from ADB while in recovery )
Medium checks
- Screen goes off (and on )
- F2FS/EXT4 Support, exFAT/NTFS where supported
- all important partitions listed in mount/backup lists
===> define important ? - depends on the device, i guess
= Assume we can still boot a recovery (aboot/lk is still there for fastboot), can restore everything left ?
- backup/restore to/from external (USB-OTG) storage
- Correct date
Minor checks
- MTP export
- reboot to bootloader
- reboot to recovery
- poweroff
- battery level
- USB mass storage export
- set brightness
- vibrate

Security Policy Updates should not be applied to this system ?
Since this is stock Samsung OS that is rooted I'm guessing this system is still SELinux "enforcing" so does this mean that I can/should say yes to Security Enhancements automatic updates from Samsung ? Any explanation or link on this matter appreciated.

Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?

maddada said:
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
Click to expand...
Click to collapse
Hey, sorry for the very late answer.
I'm currently not working on Android and I've never tried on OREO, so my politically correct answer would be: "Right now there is no plan to work the same magic on OREO, but whoever wants, can try to use the device tree I created with a new official OREO kernel (didn't know they have one already)".
Anyway, keep checking the forum from time to time, I may have found the time to work on it
Links to the device tree and other tools used are in the main page of this thread.
Thank you,
Shedaim

I Pay 100$ for making my Galaxy Tab Active 2 booting when its charging
Hey guys,
i hope somebody can help me.
Im trying since 2 Weeks to make my Galaxy Tab Active 2 booting when its charging.
I try all the ways i found (fastboot, LPM change and Autoboot App) and nothing was successful.
So i hope to find with this way somebody who would help me to get the feature.
I need it because i installed the Active 2 on my Harley Davidson as my navigation.
And the problem is that i make a Novalauncher thats looking like the original Harley Davidson one and starts without a code.
So when i put the Tablet in the Mask i dont get a method to press to power button and when i make a method (hole trough the mask or something) then everybody can start up my tablet and use it.
So if somebody can help me with that i will pay them 100$ for helping!
you can contact me at [email protected].
thanks alot

Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.

sCOTTN916 said:
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
Click to expand...
Click to collapse
I used the methods and recovery here for my tablet which is a T397U...works flawlessly. The same should work for the wifi T390 you have aswell.

Flash process
I am new to the rooting process. This will be my first time. What is the actual flash process? How do I flash the rom on my tablet?

All the links are dead can anyone please post this recovery

i can Flash this twrp-3.2.3-0-gtactive2lte-7.1.2.tar, Odin says pass, but there is no TWRP. it boots into System. when i stop and boot to recovery, there is stll custom recovery from T395XXU5CSH2.
Any hints?

Newbie-friendly: TWRP and Root for Samsung S3 Tablet

Tested SM-T820, for Android O. It is reported that it works for Android P as well, with small modification (see below).
This post is designed to gather information found across this forum to give a step-by-step guide for obtaining a custom recovery TWRP and Root (via Magisk) for the Samsung S3 tablets running Android O. This process works if you are upgrading or staying with Oreo. [If you wish to run Android N, there is a slightly different process.] This process will wipe the contents of the tablet, so make backups as appropriate.
Credit to the software authors, original post creators (especially ashxy) and all those who contributed to the discussions to clarify all the issues. Most of the specifics below were hammered out in https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359.
WARNING Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on. You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering. [credit: jcadduono]
The below instructions are for Android O (Oreo). User BenG7 reports (I have not verified) that the same process, with slight modification, will work for Android P (Pie). See posts #38 and #39 for those modified instructions.
1. DOWNLOAD
a. ODIN​https://samsungodin.com/ (I used 3.13.1)​b. Samsung USB Drivers​https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows​c. Original firmware​Search for SM-T820 and download latest version 8.X at http://updato.com/firmware-archive-select-model​d. TWRP​At some point, it will likely find an official version at https://twrp.me/Devices/. For now, grab the latest beta version at https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359​e. Magisk​Get the latest stable Magisk version from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445​f. Ashxy's oreo encryption disabler https://androidfilehost.com/?fid=890278863836288163​​
2. PREPERATION
a. While running your tablet in Android, go to Settings -> About device. Tap 7 times on Build number to enable Developer options. [credit: jcadduono]​b. Now go to Settings -> Developer options. You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on. Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore. [credit: jcadduono]​c. Turn off your tablet.​d. Get a micro SD card​e. Copy Magisk and oreo encryption disabler onto microSD card​f. Install microSD card into Tablet​g. Install Samsung USB Drivers on Windows machine​h. Unzip ODIN (1a) and Original firmware (1c) on your Windows computer​i. While tablet is off, plug in usb cable between tablet and Windows computer​​3. REFLASH ORIGINAL FIRMWARE (Optional if your tablet is already running Oreo)
a. Enter Download mode, press and hold Home, Down Vol, and Power until you see the Warning screen of the downloader mode. Press Vol up to continue​b. Open up ODIN, confirm that ODIN can see your tablet. We will fill in three files for flashing. Click AP button on Odin. In popup, select AP_[blah blah].tar.md5 (whatever AP file you downloaded in step 1c). After selecting the file, Odin will check the signature of the file you downloaded and appear to freeze up. Let it finish, and it will report: <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. In a similar way, fill in the BL and the CSC files. As these are much smaller, the signature checks will go much faster. [Use the CSC file, not the HOME_CSC file, in the CSC slot. This will completely erase your data on the tablet, which minimizes the likelihood of future problems. You will be erasing all of the /data partition later, so there is no point in saving your data now by using the HOME_CSC file.]​c. Make sure that in the options, Auto Reboot is selected. Then click Start. The screen of the tablet should show a progress bar as your tablet is being restored to its original firmware.​d. At this point, your tablet will reboot into the default recovery mode, with a full blue screen and an android figure with the spinning arrows. The tablet will then self reboot again (perhaps more than once). After a while, you will be greeted with the Welcome screen where you can select your language. Be patient.​e. Power off the tablet using the power button​​4. FLASH TWRP
a. Enter Download mode (press and hold Home, Down Vol, and Power) until you see the Warning screen of the downloader mode. Press Vol up to continue​b. (Re) Open up ODIN, confirm that ODIN can see your tablet,​c. Important We do not want the tablet to automatically reboot after installing TWRP. If the tablet does reboot into Android before completing the steps in Section 4 and 5, there is a good chance the stock recovery will overwrite TWRP. So click the Options tab on the left and deselect Auto Reboot. After doing that, click the Log tab so you can monitor progress​d. Click AP button on Odin. In popup, select twrp-[blah blah].img.tar (downloaded in step 1d), but make sure that the BL and CSC slots are unchecked, i.e. we will only be flashing an AP file this time. Then click Start. You will see the progress bar on your tablet. Watch the log window of Odin and wait for the message "<OSM> All threads completed. (succeed 1 / failed 0)"​​5. ENTER TWRP AND CONFIGURE
a. At this point, from the last section, you should still be in Download mode on the tablet. It is important that, after flashing TWRP, to go straight to TWRP without letting the Android System reboot. To do this, Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] (while still holding [Home] + [Power]) when the screen blanks. [credit: jcadduono]​b. In a few secs, you will see the TWRP first screen, you can let go of all the buttons.​c. If you don't see then TWRP boot splash try again from the start of 4. FLASH TWRP.​d. Swipe to Allow Modifications. (For some reason, TWRP has some issues with the touchscreen for some tablets. If you experience this, expect to make several swipes or taps until it properly registers. You have succeeded when you see the classic 8-button main screen of TWRP.)​e. Click Wipe then Format Data (do not just Wipe data), type yes and let it complete. Then click back until you get to the 8-button main screen of TWRP.​f. Click the Mount button. Select Storage button, and confirm that the Internal Storage shows non-zero MB. If it is, you know that the /data partition is now mounted properly. However, since we put the needed install files on the microSD, go ahead and select Micro SD Card as our storage. Click Back until you are back at the 8-button main screen.​g. Click the Install button, install the Magisk zip file you downloaded in step 1e and copied to your microSD. Once finished, click Back to get back to the install screen (do not reboot yet).​h. Install the oreo encryption disabler zip file from step 1f. When it completes, you can press the Reboot System button and let your tablet reboot into Android. You can also disconnect the usb cable connecting the tablet from the computer. The tablet may reboot itself once or twice, let it do its thing, and eventually you will see the Samsung Welcome! Screen, where you can select your language.​​6. CONFIRM DATA ACCESS IN TWRP
a. Before going into configuring your tablet, go ahead and turn off the tablet and re-enter TWRP (Home, Vol up, Power).​b. *Important* Since you will not be changing your system partition, this time, when you get to the "Keep System Read only?" screen, click the Keep Read Only button.​c. In the 8-button screen of TWRP, click Mount, click Select Storage. Confirm that the Internal Storage is greater than zero MB. If it is, congratulations, you have TWRP installed with /data mounted.​d. Reboot to System​​7. FUTURE USE OF TWRP
a. Unless you are planning to make changes to the System, continue to choose the Read Only System when you return to TWRP.​B. [NOT YET TESTED]If you need to make changes to System, e.g. flash a new ROM, go back to Step 5 and install the ROM just before Step 5g​​
8. Click the Thanks button if my guide helped you.

Good guide. In 5, a, at least for the t-820 and if assume other variants, you can hold power, vol up, and home until it boots to recovery. You don't need to hold the keys to boot the bootloader and then quickly switch to the vol up. It's a little easier for me to do it that way.
Sent from my [device_name] using XDA-Developers Legacy app

Good guide and HNY!
klaberte said:
7. FUTURE USE OF TWRP
.....
B. [NOT YET TESTED]If you need to make changes to System, e.g. flash a new ROM, go back to Step 5 and install the ROM just before Step 5h
Click to expand...
Click to collapse
I would flash magisk *after* flashing a new ROM, i.e. install the ROM just before Step 5g.
Btw, I installed TWEAKED for T820 by @rorymc928 which comes already with encryption disabler.

Great guide!
But, anyway to install SuperSU instead of Magisk?

Frunktz said:
Great guide!
But, anyway to install SuperSU instead of Magisk?
Click to expand...
Click to collapse
I'd ask over here: https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359

klaberte said:
I'd ask over here: https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359
Click to expand...
Click to collapse
Already asked but it SEEMS not possible because SuperSu was discountinued. But somebody has successfully installed it on Oreo 8.

I am new to rooting my Tab s3 so pardon me if any of my questions are redundant. I will be following the directions from post "Newbie-friendly: TWRP and Root for Samsung S3 Tablet". Can someone please confirm the following for me before I root -
1. I am running on the most recent firmware T820XXU2BRL1, do I need to complete process #3 REFLASH ORIGINAL FIRMWARE?
2. After I complete root process will my Tab s3 automatically be set to recognize SD Card as internal storage or will I need to complete another setting or process? This is my main reason to rooting.
3. Second reason is to remove bloatware. Does anyone know of a post advising which bloatware on Tab s3 to remove safely and which ones to leave alone?
4. After completing root process following directions from post "Newbie-friendly: TWRP and Root for Samsung S3 Tablet" has anyone experienced any Tab s3 functions or app not working properly? Is USB-OTG working?

my Tab S3 delivered today and followed ur guide and did in first try! send Thanks!

Great post. Im having an issue. With my tab s3. Yesterday i was updating magisk manager and after i did it stopped charging. I thought my charger came unplugged but it didnt. Now the only way i can charge it is to put it in twrp and let it charge. But its unresponsive when its powered on and when its off it just loops the charging screen. But wont charge. I jave tried to revert back to a previous back up but had no luck. I was plannig on flashing stock firmware when i get back to my computer.. but any input would be greatly appreciated..
Sent from my SM-N960U using Tapatalk

cdeitrich00 said:
Great post. Im having an issue. With my tab s3. Yesterday i was updating magisk manager and after i did it stopped charging. I thought my charger came unplugged but it didnt. Now the only way i can charge it is to put it in twrp and let it charge. But its unresponsive when its powered on and when its off it just loops the charging screen. But wont charge. I jave tried to revert back to a previous back up but had no luck. I was plannig on flashing stock firmware when i get back to my computer.. but any input would be greatly appreciated..
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?

jd1639 said:
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?
Click to expand...
Click to collapse
I had the sony framework module installed for ps4 remote play. But that was it. I cant figure it out.
Sent from my SM-N960U using Tapatalk

jd1639 said:
I don't know why your tab won't charge. Updating magisk should be totally unrelated to charging. Did you have any magisk modules that would have modified charging parameters?
Click to expand...
Click to collapse
https://r.tapatalk.com/shareLink?ur...share_tid=3641443&share_fid=3793&share_type=t
This was my issue. I love this forum.
Sent from my SM-N960U using Tapatalk

Quick question. I'm already on the latest firmware, my bootloader is unlocked so can I just run Odin, flash twrp and then any pre-rooted Rom? Or do I need to follow all these steps? It's been awhile since I've flashed anything and just want to make its done properly. TIA

after rooting, the secure folder works or not

jawalexander said:
after rooting, the secure folder works or not
Click to expand...
Click to collapse
That's correct.

Is that the only drawback?

On reboot I got: Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.
Now what?
UPDATE: Oh I see, I totally skipped e. "Click Wipe then Format Data". Now it's fixed and working properly. Now to remove some bloatware.
David C.

I posted something silly before. Deleted.

THANKS ! Works also for Android PIE
Hi,
thanks,
I did a clean install of Android Pie for my Samsung Galaxy Tab S3, SM-T825.
Altough not yet officially available for my country, I downloaded the version for the Netherlands (PHN-T825XXU3CSH9-20190909091851) from the SamFrew-site [https://samfrew.com/nl/download/Galaxy__Tab__S3__/evss/PHN/T825XXU3CSH9/T825PHN3CSH8/[/URL] . As one can anyway customize languages, etc., no problem.
Then I followed your guide step by step.
I added BusyBox, latest version from XDA developers []https://forum.xda-developers.com/showthread.php?t=1929852 as last step, in 5. g
Altough written for OREO, all this steps work perfectly well on my Android PIE !
Including the use of the Ashxy's oreo encryption disabler of point 1.f
(I didn't find a similar disabler for Android Pie yet... Someone a better idea ?)
Rootchecker confirms that I have Root access and that BusyBox is indeed installed.
Thanks very much - great help !
baudi

baudi said:
Hi,
thanks,
I did a clean install of Android Pie for my Samsung Galaxy Tab S3, SM-T825.
Altough not yet officially available for my country, I downloaded the version for the Netherlands (PHN-T825XXU3CSH9-20190909091851) from the SamFrew-site [https://samfrew.com/nl/download/Galaxy__Tab__S3__/evss/PHN/T825XXU3CSH9/T825PHN3CSH8/[/URL] . As one can anyway customize languages, etc., no problem.
Then I followed your guide step by step.
I added BusyBox, latest version from XDA developers []https://forum.xda-developers.com/showthread.php?t=1929852 as last step, in 5. g
Altough written for OREO, all this steps work perfectly well on my Android PIE !
Including the use of the Ashxy's oreo encryption disabler of point 1.f
(I didn't find a similar disabler for Android Pie yet... Someone a better idea ?)
Rootchecker confirms that I have Root access and that BusyBox is indeed installed.
Thanks very much - great help !
baudi
Click to expand...
Click to collapse
Thanks for the update! Just wondering, why did you add busybox and XDA developers at the end of step 5g? XDA developers could have been installed as a standard app once the tablet is up and running, no?
Why manually installing BusyBox at this point of the setup?