yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 General] :
Kingroot does allow your device to retain permanent root after a certain time. However, Kingroot is not as powerful as SuperSU, is very limited in terms of what It can do, and has it's own 'bloatware' titled Purify. I'd honestly stick with SuperSU because it's (probably) the most powerful and efficient way to root your phone. I'd also suggest avoiding having to reboot the tablet at all with temp root because you would have to take 5 minutes to install it again, which was a pain in the butt for me.

As for the kingroot app freezing, that's usually the result of a bad download or a bad root. Plus kingroot is very limited in terms of what you can do on your kingrooted device. SUPERSU is the equivalent of an IOS jailbreak. SUPERSU gives you full control of your device, with no bloatware and limits, unlike kingroot.

Kingroot does sometimes delete the su binaries upon rebooting, which is another reason I don't like it all that much.

Another theory I thought of is that it's not Kingroot that's deleting the binaries, it's actually something that's set to happen when the device boots up. Either the actual Android os or the bootloader searches for and deletes the su binaries to prevent root.

I don't know for sure, I've kinda slowed down work on this device mainly because of a project I've been working on with the Samsung Galaxy S7 AT&T (SM-G930A). I'll look into these things when I get the chance.

Cheers!
[Galaxy Tab 4 General] xjimmy:
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.

---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------

https://xdaforums.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737

*https://xdaforums.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334

A couple of threads I started a long time ago that may be of interest to you.
[Galaxy Tab 4 General] loc626:
Upgrading OS and rooting

I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.

Any help would be greatly appreciated. Thanks in advance!
[Galaxy Tab 4 General] :
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.

Cheers!
[Galaxy Tab 4 General] loc626:
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
[Galaxy Tab 4 General] :
It would be best to unroot before installing to avoid any issues during the installation. Other then that, you're in the clear! Just remember, you cannot downgrade after the install!

Cheers!
[Galaxy Tab 4 General] leeboski44:
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
[Galaxy Tab 4 General] :
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.

Now I'm thinking:

1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.

--OR--

2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).

I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.

(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.

Please, anyone, correct me if I'm wrong.

Cheers!
[Galaxy Tab 4 General] leeboski44:
No that makes perfect sense and thanks for clearing it up.

The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?

And possibly this is what you were saying above and I am misreading it...

***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well. :)
[Galaxy Tab 4 General] :
I'm glad I could be of help, however I don't see where I stated that the signature implementations on the BOOT and RECOVERY partitions was Samsung's idea not the carriers, if you could point that out for me that would be great.:good:

The engineering kernels skip SOME signature checks, both when flashing and booting into partitions, but I do not know exactly which ones they skip. We know it skips some of the signatures for /SYSTEM, but it does not do the same for the 2 other main ones, those being /BOOT & /RECOVERY. We know because "one of our own" attempted to flash their own build of TWRP recovery to the device (SM-G930A to be specific) only to get a signature check fail when booting the phone, which of course means that the phone has a locked bootloader and that the signatures for the /RECOVERY partition are still checked, but I do not know for certain about /BOOT. If I had to assume I'd say that /BOOT isn't checked, given the fact that if your phone is rooted then you would have had to flash the engineering kernel, which, like I said, skips some signature checks.

I hope I've cleared most things up for you.

Cheers!
[Galaxy Tab 4 General] rwww12d:
The firmware you provided saved my sm-t337A tablet from being soft bricked. Although I was able to gain temp root from this method, king root tried to disable the SELinux on my device and after trying to temp root again caused the app to implant itself as bloatware into the /systems folder and was non functional when using the app. Do you happen to know of a custom recovery (TWRP or CWM) which would work for this device?
[Galaxy Tab 4 General] :
Yeah dude, I absolutely hate when Kingroot does that. But when it does happen and there's nothing you can do to fix it, you'll have to flash the system partition again to erase it. And simply reroot it after, then quickly open the supersu install app and replace kingroot with supersu. Not much we can do about it right now, well, not that I know of.

Also, AT&T devices have a locked bootloader, therefore, custom recovery can't work on any AT&T devices, period. Good to know that I helped you recover your device.

Cheers!
[Galaxy Tab 4 General] vegoja:
My t337a is rooted permanently with supersu and I have xposed installed easy ?
[Galaxy Tab 4 General] KubotaPartsJoe:
Please share how you have accomplished this feat. A lot of people including myself have been trying to figure it out. Thanks
[Galaxy Tab 4 General] vegoja:
I'm on 4.4.2 never updated beyond that. I I rooted using towelroot then installed supersu from the play store.
[Galaxy Tab 4 General] goatjc:
Any success on 6.0.1?

From what I can tell, I'm in uncharted territory.

Anyone tried this method on 6.0.1? There's a reddit thread linking the Exynos TWRP, however, the XDA TWRP link is only referencing the other 'non-a' models of the Exynos processor.
[Galaxy Tab 4 General] wtupchurch@gmail.com:
Great fix for a\sm-t337a

Before I found this fix, I thought I was going to have to buy a new tablet. The problem was with one app that I use to log onto PS Vue to watch TV. PS Vue changed something at their end. I had no problem logging in with my cell phone that has android 5.1, so I thought if I could upgrade to 5.1 on my tablet, it might work again. It took me a while to understand your instructions, but once I did it worked out great. Thanks for this post and saving my tab. Buy the way PS Vue has been working on a fix for about two weeks with no luck.
[Galaxy Tab 4 General] jenbcute:
Got me stuck on the AT&T screen!

So now I'm stuck on the AT&T boot screen!!! Now what? Should I flash firmware now or do you have another suggestion???

Thanks :)
[Galaxy Tab 4 General] hell_storm2004:
Help!! I rooted my device using the King Root thingy, and now the tab won't start up. It is stuck on the AT&T logo white screen and nothing happens after that. I did a factory reset reset yesterday, thinking it might do the trick, but it didn't. Any suggestions would be helpful.
[Galaxy Tab 4 General] jenbcute:
I know this is an old post but....better late than never? :)

If your stuck at AT&T Logo or in boot loop:

flash it in Odin with this firmware! It always got me back to the beginning & working properly!

T337AUCU2BOH4_T337AATT2BOH4_HOME.tar

FIRMWARE DOWNLOAD LINK

https://mega.nz/#!n8Q3VIIS!OComhygeI5SL5R6n0EXEfiYMBtVn_aOAIcUuLgmYs-k

I always used Odin v3.09 for that device

ODIN DOWNLOAD LINK

https://xdaforums.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539

When rooting device you can follow this (I can confirm it does work great!)

https://xdaforums.com/tab-4/general/root-how-to-root-sm-t337a-supersu-t3553848

Good Luck! :)
[Galaxy Tab 4 General] chris1892006:
So are you saying the t337a has a locked bootloader which hasn't been unlocked ever before?
[Galaxy Tab 4 General] RocknR:
This might be an old post but it is a great post. I bricked my T337A, spent days looking for stock firmware, got it fixed then my brothers T337A bricked, I lost the firmware somewhere in all my file backups. Found this great post and yes I had to use the pit about 6 or 7 times until I received a pass then the AP, BL, CP etc several times until it passed, this tablet was in bad shape but with your GREAT post it's fixed now.

If you're having fails, just keep running it until it passes, this jewel works.

Thank you for such a GREAT post..
[Samsung Galaxy S7 Edge Questions and Answers] ilordvader:
I have Upgrade my S7 Edge to Nougat 7.0

How to Disable the WhatsApp notification Preview in status bar Please :(

After I Upgrade to Nougat 7.0 no Option to do that :(

Settings/ Notifications/ Advance/ WHATSAPP
[Tilt, TyTN II, MDA Vario III General] portos03:
found this thread in general but nobody response to it there..so i just wonder maybe somebody can help..i am having the same problem...:mad: :confused:

Hi all,

I am posting a thread after 3 hours of checking the internet to see if others report the same bug.

I am currently using a Kaiser with WM6. Just to describe my problem, when i enter the SMS application (mailbox) and i click on an SMS to read it, the bottom of the page is displayed first (usually blank screen), so everytime i need to use the scroll bar to see the message content which is on the top of the page.

I know it is not a major issue but it's still really annoying. As i said i have been looking everywhere but so far with no chance. This might be a registry problem, maybe caused by the installation of a program, but i don't have anything fancy on my mobile so far.

Anyway, thanks in advance for your help.

Bye
[Tilt, TyTN II, MDA Vario III General] sWuRv:
Please search these forums before posting a thread. This has been addressed multiple times on this forum. Solution is to disable d-pad navigation in the pocketIE section of kaisertweak.
[Tilt, TyTN II, MDA Vario III General] hans_olo:
Known issue:

Have you Kaiser Tweak installed? Disable D-Pad Scroll Navigation for PocketIE,

beause this tweak causes that behaviour.

This will solve the issue.

Greetz,

Hans Olo
[Tilt, TyTN II, MDA Vario III General] jwbrint:
That is a known issue when you have installed KaiserTweaks and enabled D-Pad scroll navigation for PocketIE. Just set that value to Disabled (Default) and problem solved.
[Tilt, TyTN II, MDA Vario III General] jwbrint:
Beat me to the punch.
[Tilt, TyTN II, MDA Vario III General] hans_olo:
My excuse is that I wrote it at the same time as sWuRv did.

What is yours?

:D :D :D :D
[Tilt, TyTN II, MDA Vario III General] portos03:
thanks alot guys..problem solved...

you'e rock!!!!
[Tilt, TyTN II, MDA Vario III General] jwbrint:
No Excuse :) :) :)
[Android Themes] Sketch2017:
Hello Fellow XDA Readers ,

I would like to bring back to the front some ways to change your boot animation on a Rooted Android phone without having

to use Rom Tool Box. I only started this topic again due to the fact that Rom Tool Box will only change your Boot Animation if your Bootloader is unlocked.

So, Some people have ran into that issue ..

Check XDA for boot animations or Google., for your device. and down load the required files *.QMG files

Once you have them downloaded, move them to your device. and copy them to your System/Media folder. (Pertaining you are Rooted)

Rename your existing boot and bootlogo files, rename them to the extension of (.BAK) minus the caps lock,,,lol

After you do that , make sure you set the permissions to ( -rw-r--r-- )

After you complete those steps. Fee free to Reboot and enjoy your new boot animation.

If you have any questions please post them. I will reply to them and answer them the best I can.

XDA:DevDB Information

Changing Boot Logos on Rooted Phones, Theme for all devices (see above for details)

Contributors

Sketch2017, Sketch2017

Version Information

Status: Stable

Created 2017-02-10

Last Updated 2017-02-09
[HTC One A9] VirusRenamon:
So I'm on a US Unlocked HTC One A9 on 7.0, unmodified.

Every time I reboot or shutdown, all accessibility settings are turned off when I start my phone up. Some apps I use like Tasker, Navbar Apps, and Status need this to work properly.

Does anyone know why this happens and how I can fix it? I wasn't having this issue on 6.0.1
[HTC One A9] VirusRenamon:
Necro bump I know, but if you stumble upon this issue in the future, it has to do with Boost+, just whitelist the apps and problem should be fixed. Just thought I'd post the fix for any who may have the issue.
[XDA Assist] :
Hey there dudes .i just wanna ask something bout this prob of mine now. (Well not actually prob just little issue bout my battery usage) . This thingy just started showing off my smart manager in battery section saying "Learning Usage Patterns" and i really freaked out since i just recently bought this phone last week in an online shop. (It even asked me to update twice) And when i factory reset it yesterday noon (since it lags a bit) i started seeing that thing after the boot and the initialization of the phone.. and i was in panic mode yesterday so that noon its around 6pm i factory reset it again hoping it will fix it. Unfortunately it didnt.. i did tried lookng up the net bout this issue and saw several threads here in XDA and couple of them said wait for couple of days ... and i even contacted samsung support now and they called me telling me i should wait till this 6pm (since it counted as a day) ...so i was wondering if u guys could help me asap... theres no other prob on it. The performance is smooth and all... should i just wait for couple of days? Or is it a prob already in my software?
[XDA Assist] engloa:
Hello and welcome to Assist

It could be a problem with your software or it can go away after a couple of days

I dont own the device so please register an account and seek help in the link below

https://xdaforums.com/t/galaxy-j2-prime

Good luck
[Samsung Galaxy S7 Edge Guides, News, & Discussion] ramheer:
Fellow XDA members I put together a review of the changes to the Galaxy S7 Edge and best features of the Android Nougat 7.0 update. Enjoy Mod Edit
[ZenFone 2 Q&A, Help & Troubleshooting] Miguelkf:
I cant login in snapchat even after i uninstalled the xposed.

I get the same error as i would get if i was using the xposed,

anyone knows what to do??
[ZenFone 2 Q&A, Help & Troubleshooting] mortemxdeus:
Uninstall xposed framework

Log in to Snapchat, take a backup of it using titanium backup

Reinstall xposed, restore Snapchat from titanium back up

Make sure you clear cache after uninstalling xposed. I had issues for not doing that.
[ZenFone 2 Q&A, Help & Troubleshooting] maor23:
it happend to me to

the framework are unabled and still cannot login snapchat
[ZenFone 2 Q&A, Help & Troubleshooting] Miguelkf:
its all uninstalled, and wiped. but snapchat stills not working
[ZenFone 2 Q&A, Help & Troubleshooting] maor23:
maybe we need another version of snapchat?

edit:

i tried now,but still nothing
[ZenFone 2 Q&A, Help & Troubleshooting] Miguelkf:
i also tryied this, download 4/5 different versions and nothing
[ZenFone 2 Q&A, Help & Troubleshooting] @chan:
Have you try to Unroot your phone and install the latest version? After login Snapchat you can root the phone again?
[Samsung Galaxy J5 Themes, Apps, and Mods] Ragazzza:
Just what title says, how to completly disable sound in your camera (recording sound, shutter sound, all)

You don't have to mute all your system sounds to stop camera from making that shutter sound. You can safely disable it using CSC expert.

1) Download CSC Expert (available on google play)

2) Open the app and grant root access.

3) In the top you should see "Used features only", click on that and choose Camera.

4) Now click on Shutter Sound Menu, and type in "true" and than SAVE.

5) Reboot your system and go to camera settings, and there you will see new option called "Shutter Sound", disable that option and that is it.

[Method 2] For those that are not using Touchwiz, and for those that are using it, but just find this method easier:

Locate to /system/media/audio/ui, and rename "camera_click.ogg" to .bak.

Big thank to #Henkate for 2nd method.

Make sure to click on that report button if i helped you :p
[Samsung Galaxy J5 Themes, Apps, and Mods] #Henkate:
There's also other way, which can be used on any ROM, unlike that app which is meant for stock Crapwiz.

Renaming camera_click.ogg to camera_click.ogg.bak or deleting it from /system/media/audio/ui, removes the camera sound. It might be different on other ROMs.
[Samsung Galaxy J5 Themes, Apps, and Mods] Ragazzza:
Oh that is nice, i though only way was changing values. Where do i find those files?
[Samsung Galaxy J5 Themes, Apps, and Mods] #Henkate:
/system/media/audio/ui. I'm sorry for not mentioning it in previous post.
[Samsung Galaxy J5 Themes, Apps, and Mods] Ragazzza:
Np, amyway, is "media" folder? looks like i can't fins it. Only media....xml in there
[Samsung Galaxy J5 Themes, Apps, and Mods] #Henkate:
Oops, /system/media/audio/ui :D
[Samsung Galaxy J5 Themes, Apps, and Mods] Ragazzza:
I found it at /system/media/audio/ui :p

Anyway ty, i'll put this in OP
[Samsung Galaxy J5 Themes, Apps, and Mods] #Henkate:
I've just done it on Slim6 before writing here.

Dunno why I've wrote the path wrong for 3 times lol.
[Samsung Galaxy J5 Themes, Apps, and Mods] BlackAxiom:
I just removed permissions :b also changed all sounds to note 7 sounds :)