Database Users

Tab 4 (SM-T530NU) 4.4.2 = used ODIN & Flashed Kernel 2 Root w/ Towelroot; Flash back?

Tab 4 (SM-T530NU) 4.4.2 = used ODIN & Flashed Kernel 2 Root w/ Towelroot; Flash back?
I have a Samsung Galaxy Tab 4 10.1 (SM-T530NU) Even though I'm running on 4.4.2., I wasn't able to ROOT using Towelroot.APK B/C the Kernel is A0A2. So, following the directions on a website (posted at the bottom of this post) I found my device's Model_ROOT.Kernel.Tar.md5 and it's Model_Kernel.Tar.md5 files the webpage stated I needed in order to ROOT my device via ODIN.
Using ODIN, I was successful in flashing the downloaded ROOT.Kernel.tar.md5 file. After completing the next step I was able to successfully gain ROOT privileges by opening TowelRoot.apk & clicking "Make it Rain"
I used a random Root Checker app I downloaded from the Google Play Store to verify whether or not Towelroot succeeded in ROOTING my device.
YEAH!! I HAVE SUPER USER PERMISSIONS!!
I was so excited to have ROOT access after several days of continuous research that I never proceeded to the final steps on the aforementioned website's tutorial. I didn't use Model.Kernel.tar.md5 to flash my device back. Know it's been 2-3 days since I ROOTED my Tab 4 & to the best of my knowledge, I haven't experienced too many relative issues other than both Lucky Patcher & Freedom apps have been unsuccessful when I attempt to get free In-App Purchases from other Apps & Games. Normally I would just uninstall both apps and shrug 'em off as being incompatible with my device but within the past 8-10 months, I've used both of these apps on 2 of my previously ROOTED devices & they both worked correctly from the start. Not to mention that one of those happened to be another Tab 4 which was the same Make & Model of the Tab 4 10.1 SM-T530NU I'm currently using & writing about - the only differences between the two is their SEstatus & their Kernels: Old Tab4 had Permissive SEstatus & the Kernel ended in AND1 while this new one is set to Enforcing SEstatus and it's Kernel ends in A0A2)
I have a few questions related to the information you just read in this Thread:
* Did I really f**k up when I 4got to Flash back after Rooting w/ Towelroot? (If so, what steps do I take)
* How do I get L.P. & Freedom.apk to work correctly? (Does having 'Enforcing' SE Linux Status an issue? Either way, I would like to know how I can switch my SEstatus to 'Permissive')
* How can I Factory Reset my Tab4 running on Kitkat 4.4.2 without losing ROOT access?)
SITE I USED AS A STEP-BY-STEP TUTORIAL TO HELP ME ROOT MY CURRENT TAB 4:
w0lfdroid DOT com (without spaces) /2014/09/TowelRoot-Samsung-Galaxy-S4-S5-and-Note3-Android-4.4.2-NF-or-Later DOT html
If anyone requires any additional information to be able to answer all/any of my Questions, please feel free to contact me.
Thanks a Million,
- B. O'Kane

a lot of letterssssssss

APKtech said:
* Did I really f**k up when I 4got to Flash back after Rooting w/ Towelroot? (If so, what steps do I take)
* How do I get L.P. & Freedom.apk to work correctly? (Does having 'Enforcing' SE Linux Status an issue? Either way, I would like to know how I can switch my SEstatus to 'Permissive')
* How can I Factory Reset my Tab4 running on Kitkat 4.4.2 without losing ROOT access?)
Click to expand...
Click to collapse
1) Yes. Flash the OA2 kernel the same way you did the root kernel
2) See my answer to your first question. SE Linux has nothing to do with this. If you want SE Status permissive, install a custom kernel or a custom rom
3) You can't
Sincerely,
Another SM-T530NU owner

Rooting Problems (WiFi & SU Binaries)

I've tried to root my phone using a guide here on XDA, but it's causing too many problems on the device to make it worthwhile! Firstly, the phone no longer remembers WiFi networks, and also takes around 30seconds to toggle WiFi on/off. Secondly, SuperSU keeps nagging me to update the binaries, but cannot update them and refers me to a webpage that isn't much help. I'd greatly appreciate some help with this please.
Phone: Samsung Galaxy S7 Edge
Carrier: AT&T
ROM: SM-935U (Source)
Step1 ROM: I wanted to remove the AT&T bloat on my phone and have a stock Samsung ROM, so I followed this guide and replaced the SM-935A ROM with SM-935U. It works perfectly! Absolutely no issues at all, everything installs as expected and works perfectly, including WiFi and it remembers the WiFi network and passwords.
Step2 Root: Then I wanted to root my device, and this is where the problems begin. I follow this guide to root the device. The guide tells me to flash a file using Odin, which works perfectly and the device reboots ok. I then run the batch file (root.bat) which also runs ok, up until the command "adb shell < supersu.cmds" which tells the device to reboot, before the batch file can finish the remaining 11 commands in the file! I edited the batch file and added a 'pause' there, which allows the device to reboot and then I can continue running the batch file. So, even after I fully complete the root process with NO errors at all, the device now is rooted (according to RootChecker) and no longer remembers WiFi networks or passwords, and also takes about 30seconds to toggle WiFi on/off!
Also, after a reboot, SuperSU gets updated in the PlayStore and wants it's binaries updated, which it cannot seem to do. After a while, it says unable to update, please refer to this page: http://supersu.com/insteadbinaryfile.html I don't know what 'method 2' on that page is referring to when it mentions step 7. What auth app? SuperSU? Anyways, it doesn't work. Sure the device is rooted, but what good is it when it's constantly nagging for binary updates and cannot function with WiFi properly, because it forgets the network everytime it loses connection to it?
To resolve the WiFi issue, I tried a number of things. Forgetting the network, manually adding the network, rebooting into recovery and formatting cache, resetting the phones network settings, factory reset. None worked. I've googled the problem, and cannot seem to find anything relevant that works. Somewhere I saw something about a build.prop edit, but they didn't say what to do or what to change in the prop file.
Thanks for reading all this, and for taking the time to reply.

First, the root instructions say not to update su binaries. I wouldn't try changing to super su either until you hear something else has been made safe. Second is in the discussions under the root thread, someone has posted a zip that's flushable through flash fire that solves lag, Wi-Fi issues, all that. Third, you need to read, read, read what people are saying, inductions, etc...And within a thread, search a word like "Wi-Fi" because the odds are someone rose has had the same problem already. There are even step by step videos on YouTube that came out before that flashable zip on how to manually address those problems. Hope this helps though.
---------- Post added at 08:47 AM ---------- Previous post was at 08:31 AM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=3813819&d=1468620810
That should take you to the zip download. Not sure if you messed things up with your superuser though, do you might want to reflash a stock firmware & go through the root steps again if things start getting weird. Just post pay attention, man. Good luck and all.

Thanks for the pointer. I did actually try searching both the ROM and Root threads for "wifi" without any success.
I get this error from the XDA website: "XDA-Developers
Sorry, we encountered an error processing your request. Please go back and retry or wait a minute.
The Administrators have been notified of this error"
The only way to 'search' is to CTRL+F each page, which on the ROM page takes a while. I skimmed through all the posts in the Root thread, and didn't see any mention of WiFi problems (until my post there), just mentions of lag issues.
I will try the 'fixes zip' they posted there and see how it goes. Thanks again.

Hmm, that's odd. I've only had search problems via dolphin browser on my phone, never on my pc. I didn't realize there were any posts under the rom/kernal/recovery section to search within yet. Just for future reference, you can always check the main s7 forum, the Sprint, T-Mobile, Verizon s7 edge forums for possible compatible solutions, YouTuber "highonandroid,"androidcentral and plain old Google. Sometimes I'll even end my Google search with 'xda' and get great results. But I'm just saying, all these answers have been out for a while, and all over the place. I mean, I even waited to root so I could see what other people were claiming to have issues with before I just jumped in. And if you skimmed through the steps missing the info about not updating the su, you should remind yourself to be more careful moving forward. Rooting and flashing, especially on Samsungng devices is not near as forgiving as it used to be. Glad your phone isn't a brick, man. I know a lot of people on xda would flame you for not finding the answers out there before posting this, or just ignore you. I just wanted to help, and hope you can just be humble and learn from it. I don't claim to be an expert or anything. The developers here are the best though. Anyway, all the best, man.

Here you go buddy,
http://forum.xda-developers.com/ver...sed-unroot-t3411039/post67605246#post67605246
edit: Sorry just realized you're using the U version. Does it need to be unlocked? I'm also on AT&T using the S7 Edge and used this guide to get mine working. I did have a bootloop problem at logo and had to go into recovery and reset clear cache blah blah blah (make sure you have a backup). So, if it's just the root you're after, this will work fine. I did the fix debloat zip and flashed it with flashfire to fix many of the issues you are talking about. (wifi).
Also installed SuperSu this way http://forum.xda-developers.com/att-s7-edge/how-to/root-available-t3411650

I have a note 5 downloaded towel root an super su but says bianary occupied what do i do.

Custom Recovery for ATT Samsung Galaxy TAB 4 8.0

Hello. Sorry if I sound like a COMPLETE noob here and if I posted in the incorrect place.
I am going to start from the very beginning so I can explain myself.
I am currently on a mission to be able to play Pokemon GO on my tablet and spoof my GPS without getting banned. Ill be running it on an account that I wouldn't care if it was banned so please do not just tell me to not do it.
First of all I had manually installed an update to lollipop (5.1.1) when first receiving the tablet. This was still Samsung official OS. In order to obtain my goal I had to root it. So after trial and error I managed to get my device rooted using KingRoot. Couldn't understand a damn thing because it was in Chinese but it was still successful.
This allowed me to install my GPS spoofer hider (supposed to hide GPS spoof from GO). Now it seemed promising until it told me I needed Xposed framework installed. Went to go install it however now I need a custom recovery manager to install that. I have checked with both ROM Manger and TWRP but I cant find my device. I assume its not supported by either.
Is there any decent custom recoveries that will work for my device or have I hit a complete dead end? Maybe someone might even have a COMPLETELY different approach to accomplish my goal. I don't know if you need this to answer my questions but here is everything that seems relevant in about my device.
----------------------------------------------------------------------------------
Model Number: SAMSUNG-SM-T337A
Android Version: 5.1.1
Baseband version: T337AUCU2BOH44
Kernel Version:
3.4.0-5608828
[email protected]#1
Thu Aug 13 17:01:34 KST 2015
Build Number: LMY47X.T337AUCU2BOH4
-----------------------------------------------------------------------------------
I would also like to say thank you. Not just for helping me directly in my situation but for everything. MANY of times I have wanted to do something on my phones and other android devices and I would always end up in these forums and get everything I needed. You guys are the best!

Update.
I have been reading deep in the threads. This tablet seems to be one of THE MOST frustrating android devices to try and work on.
This is what I have tried to this point.
Doing a little more research I found that I could use flashfire to get Xposed working. Thats when I ran into another problem. flashfire will not work with kingroot and will with SU.
Despite all the warnings, I tried to use SuperSUme and install superuser over the kingroot to remove it.
Softbrick..
Put it into download mode and reinstalled 5.1.1 which fixed it, buuuut now I have no root.
This led me to look into kingroot a little more and much like others, I have found kingroot to be a little too shady for me. I will not be using the kingroot path again.
1 step forward, 10 steps back.

I am currently working with someone else on the forums here to see if we can work on a way to get TWRP to work on the tablet. If we are successful then chances are I will be able to downgrade the OS back to 4.2.2 KitKat. My understanding is that OS is rootable for this tablet. After that I am going to look into a way to unlock it so I could possibly use it for cricket. I don't exactly have high hopes for it but it is worth a shot.

Custom recovery may be achievable but please do not kid yourself, you will end up with a brick if you try to downgrade the os

(Soft?)-Bricked My S7 with a Flashfire Update, Need Help to Fix It?

So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.

Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."

Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here

*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!

Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.

DeGoogle SM-P555 without MicroG or Nanodroid?

My goal is to remove Google bloatware and trackers from my tab while still being able to use GMail and Google Drive, generally improve my privacy. However I ran into multiple issues following this tutorial for my SM-P555:
I don't know and I don't think I successfully unlocked the bootloader. There is no OEM unlock option and I can't reboot my device into fastboot and use the fastboot command to unlock it.
Can't check info through dialing codes like *#*#7378423#*#*. Calling it says that the number isn't registered on my network.
Rebooting into bootloader reboots into download/Odin mode
Fastboot can't detect my device
When I installed Magisk through TWRP (seems like a successful installation) but when I check the Magisk app, it says "Installed N/A"
Direct installation of Magisk fails
Selecting and patching my ROM's boot.img fails in Magisk too
However, when checking with a Root Checker app, it says that my device has root access.
When running SmaliPatcher, it generates folders and not a ZIP (but that's probably because the Knox patch class wasn't found and just isn't supported and maybe I should just uncheck it)
My tablet is now getting hot even though there is no background activity
These are the issues that I can remember from the top of my head. I've been at this for more than 2 days now. Can anyone help me?
To anyone also with the same model and issues, please feel free to share them.