yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 General] VivaLaResistance:
Hey, well I must say that I do not believe I was so lucky anymore!

The LG G2 seems okay and it struggled with the cheap Verizon Ellipsis 8 but finally took. I believe it did a few reboots on its own and still worked. Last night I manually turned it off and then in the morning gets stuck in the Verizon window.

Going to do some more digging into this stuff now but I would definitely be leary about using any "auto root" program from here on out.

Definitely not going to try it on the phone I depend on every day.

UPDATE: After messing with some basic hard reset button pushing with no success I put it down to browse the ever inspiring interwebs and in the meantime "Android is starting... Optimizing app xx of xxx." appeared. So it seems that it did some sort of update or reset under its very own accord now!

Also would like to mention that the removal of KingRoot from my tablet wasn't entirely done through Kingo.

Using the root privileges of Kingroot I actually deleted itself, everything I could find that came from it. That rendered it virtually unusable as the Kingroot has stopped message repeatedly prompted me to press okay.

Then I was able to use Kingo on my PC and it replaced the root and installed it's own superuser without KingRoot to show "blocked silent installation" as the warning kept reading before.
[AT&T Samsung Galaxy S 4 General] jaladhjin:
Anyone know if this works to root a Note 4 SM-N901

A

on 6.0.1 ?
[AT&T Samsung Galaxy S 4 General] CVAngelo:
Simplest way to root a Samsung is FIRST UNLOCK THE OEM setting in the Developer Options (turns off FRP lock), then use ODIN to flash a custom recovery that's compatible with Android 6.0. You can usually find a compatible custom recovery posted on XDA in the forum for your phone.

Once you've got a custom recovery installed, you simplify boot into recovery mode and install the latest SuperSu.zip from your SD card. Done!
[AT&T Samsung Galaxy S 4 General] jaladhjin:
Yeah cf-autoroot doesn't have a build for A nor does TWRP [emoji17]
[AT&T Samsung Galaxy S 4 General] allenp007:
Thank you for this clarification. I'm sure it's been given before but sometimes it's hard to wade through all of the information. I have a question that I'm hoping you or someone else can answer. I am about to get an LG G6 and would like to know opinions about the best way to ROOT that. I would also like to do a custom ROM but will settle for just ROOT.
[AT&T Samsung Galaxy S 4 General] CVAngelo:
Well first of all, the LG G6 is really new and it's running Android 7 I believe. So it's kinda early to expect that the techies have already figured out the exploits.

Second, some of the LG phones have permanently locked bootloaders depending on the operator. In some cases, the LG model has a permanently locked bootloader for all carriers. I had such an LG (might have been the G4) and I was so pissed off about the locked bootloader, I gave that damn phone away and swore I'd NEVER own another LG. I had no idea that the bootloader could not be unlocked until AFTER I used some stupid bootloader unlock website that LG itself provided! It simply said, "sorry, the bootloader cannot be unlocked." Morons.

I digress. So, you need to confirm that your bootloader can be unlocked (and it's not as simple as flipping on the OEM Unlock switch in the Developer Options). Be absolutely careful because if you attempt to root some of these LGs when the bootloader is locked, you WILL end up with a brick!

Last but not least, search XDA for the LG G6 forum and check there to confirm that the root exploit is available. Otherwise, do not risk using KingRoot or any other root app that claims it can get root. Sometimes they don't get full root. Or you may actually soft-brick the device even if the bootloader is unlocked. And there'll be hell to pay! Lol

Bottom line is that I'm not sure if your LG G6 can be rooted. Check on XDA to confirm if and how to root. Sorry that I couldn't give you a definitive answer.
[AT&T Samsung Galaxy S 4 General] allenp007:
Thank you for taking the time to respond. I did look at the LG G6 forum before looking here and it doesn't look hopeful. As you pointed out - it's still early. However, I have little hope that this will have root access. I went through the same thing you did with an LG G4. I only got it because they gave me a $15 a month credit so it only cost $3 a month for two years. The first one I got was easily rooted and I was happy. Then it died with the boot loop issue and I had to replace it. This one had a newer, locked version of the OS and it could NOT be rooted. I was at least as mad as you described. I am leery of going with anything LG but I understand that Samsung is even more difficult to work with now for developers. What to do? That's a rhetorical question. Thanks and have a great day.
[AT&T Samsung Galaxy S 4 General] 20GT:
how do we remove the KINGO navigation bar that it adds? The one with all the shortcuts

HOME, BOOST, CPU......
[AT&T Samsung Galaxy S 4 General] CVAngelo:
That's why I dislike the Chinese rooting apps. They put a ton of crap on your device without asking for your approval to do so.

Have you tried opening the Kingo app and seeing if there's a setting you can alter? If not, flash a custom recovery for your device and then install a SuperSu zip from revovery. This will eliminate Kingo and all its nuisance features.
[AT&T Samsung Galaxy S 4 General] rwilcher:
There is no setting for that. Just replace it with SuperSu which is what I did. I don't trust

the China apps either. Probably security holes.
[AT&T Samsung Galaxy S 4 General] Mandeep Hundal:
Greetings,

Its my first post here.

I have question Kingo root was unable to root Micromax Q326 ver 5.1.

And shows this message after failure :- ERROR CODE 0×120372.

SO How can I root this mobile any suggestion.

It was Android app.
[AT&T Samsung Galaxy S 4 General] CVAngelo:
KingoRoot error codes are meaninglessness to those of us who don't work for Kingo.

Is the bootloader unlocked on your device? It needs to be unlocked. Also, did you unlock OEM and turn on USB Debugging? If not, no rooting agent will work.

If those aren't the problem, then use a different rooting app, for example, KingRoot (there is no O). Or find a custom recovery for your device, flash it to the device, then install SuperSu zip from recovery.

Use Google!
[AT&T Samsung Galaxy S 4 General] Mandeep Hundal:
I enabled USB debugging also OEM unlocking option in the developer settings while this process.

I used king root but it also failed to root.

I searched on Google but there's no custom recovery for MICROMAX Q326
[AT&T Samsung Galaxy S 4 General] CVAngelo:
Google apparently is not YOUR friend. But it's mine.

So go here:

https://xdaforums.com/showthread.php?t=2500437

That's the thread for your device.
[AT&T Samsung Galaxy S 4 General] rwilcher:
I like it because I can use the .apk to

root. Just put on your ext SD and run.

Works for me.
[AT&T Samsung Galaxy S 4 General] berardely:
what are the chances of this bricking my device?

there wasnt a version of TWRP available for my phone.

im currently using an SM-J337V.
[AT&T Samsung Galaxy S 4 General] :
Failed to root my DOOGEE BL5500 Lite ( Android 8.1 ) with KingoRoot v1.5.8: operation stucks at 80% - have tried it several times.
[AT&T Samsung Galaxy S 4 General] Joresyar:
Cant root my watch kingwear kc06 android 6

Why this app did’t support android 6.0(? My watch can’t root(i’ll try pc and apk version
[AT&T Samsung Galaxy S 4 General] 7mada:
After rooting I restarted the phone and it gave me at the startup ... ((Samsung custom))

And the phone didn't start ... then i removed the battery and put it back and it worked .

What was the problem at first?
[AT&T Samsung Galaxy S 4 General] bigcid10:
I had updated to mf3 then rooted using the sdcard way

after that was done I had a custom icon on boot and non official in status

the I used the kingo method to unroot and everything was official(no custom and official in status)

then rerooted with kingo and custom is back

updated su from play store but still custom icon on boot
[AT&T Samsung Galaxy S 4 General] xBeerdroiDx:
Do you have the option to update the binaries from within superSU itself?
[AT&T Samsung Galaxy S 4 General] bigcid10:
In the superSU app it doesn't give me an option to update the binaries

is that a feature of the pro version? also should I uncheck "enable superuser" ?

thanks
[AT&T Samsung Galaxy S 4 General] xBeerdroiDx:
Usually the option exists anda couple of reboots (maybe a cache wipe) clears up the padlock issue. Another option is to reset the counter in triangle away.
[AT&T Samsung Galaxy S 4 General] bigcid10:
cache wioe on which app ,superSU? or the whole system?
[AT&T Samsung Galaxy S 4 General] xBeerdroiDx:
System (recovery).

The gist would be:

Update superSU > reboot > wipe cache > reboot > reset counter in triangle away if necessary.

That sort of stuff...
[AT&T Samsung Galaxy S 4 General] bigcid10:
installed triangle away,then reset counter ,followed instructions

now I have regular boot but in status it still says custom,well I'm half there
[AT&T Samsung Galaxy S 4 General] xBeerdroiDx:
As long as you have superSU installed, that "custom" in status isn't going anywhere.
[AT&T Samsung Galaxy S 4 General] bigcid10:
should I disable superSU or uninstall it then ?

---------- Post added at 04:16 PM ---------- Previous post was at 03:41 PM ----------

also,how do I go about clearing the system cache?
[AT&T Samsung Galaxy S 4 General] xBeerdroiDx:
If you are rooted then your device is custom. That's the general idea. If you want a completely non-custom/all-official device then unroot it and return it to the original firmware.

Read up. Search these questions. You'll find answers.
[AT&T Samsung Galaxy S 4 General] FrameMan:
When I run this program on my AT&T Galaxy S4 active it says "ROOT Failed! FileNotFound"
[AT&T Samsung Galaxy S 4 General] hovax615@hotmail.com:
I rooted with this method and didn't get the custom screen but I installed a scotts ROM and it gave me a custom screen. I deleted that ROM and went to vision x stock ROM and had TiBu backup some files from the vision x rom. Went back into my stock ROM restored the files I backed up from vision x via TiBu restarted and the custom screen was gone. I was trying to fix my stock ROM from me being stupid and uninstalling things via tibu but i don't know which one I deleted that messed up my stock ROM...
[AT&T Samsung Galaxy S 4 General] xBeerdroiDx:
their FAQ says to exit Kingo, reboot and try rerooting again. give that a shot.
[AT&T Samsung Galaxy S 4 General] midas69:
I get the same error on my AIO Wireless S4. The model is actually i337Z. Tried rebooting, didn't help.

I just got the phone yesterday and I'm really disappointed not to be able to root.

I tried contacting the dev via the contact page on the website but it was unclear if the message even went through. It showed an error message but it also said the message was sent. We'll see if anything comes of it.

Hopefully someone comes up with a method soon.

ETA: My software is MH1.
[AT&T Samsung Galaxy S 4 General] xBeerdroiDx:
let us know if the dev replies back. it appears that the i337z is currently not supported by this method. i'll keep my ear to the ground. cheers
[AT&T Samsung Galaxy S 4 General] FrameMan:
Tried rebooting two times and still the same error. My model number is SGH-I537

---------- Post added at 05:45 PM ---------- Previous post was at 05:39 PM ----------

Nevermind, was able to get rooted using this method. http://xdaforums.com/showthread.php?t=2347793
[AT&T Samsung Galaxy S 4 General] Kockowan:
Asus Transformer TF300TL is working...

Tool v1.08 has been tested with:

ASUS Transformer Pad TF300TL Firmware: V10.6.2.8 Only for WW SKU (Android 4.2) = newest version

Un-rooting can be done with same tool, bootloader is still locked, no signs on Asus boot screens.

AdAway*Root, Titanium*Root and TotalCommander with root access to /system are running without any problems.

Thx :highfive:
[AT&T Samsung Galaxy S 4 General] highrolla32:
For some reason, Kingo refuses to recognize my AT&T S4 (it's not an AT&T S4 active). I've re-installed Kingo twice, I've downloaded and installed the updated USB drivers from the Samsung website, USB debugging mode is enabled, my battery is fully charged, and I'm using Samsung's included USB cable.

My computer recognizes the S4 without any issues -- but I can't get past Kingo's "Not Connected" screen.

Any suggestions?
[AT&T Samsung Galaxy S 4 General] atenspro:
One crazy idea

Try getting Kingo up and running first, then connect your phone. It worked perfectly for me on Windows 7 64bit and an AT&T S4 MF3.
[AT&T Samsung Galaxy S 4 General] SciFiJim:
Try a different computer. It didn't work with my desktop, but finally worked with my laptop. If you don't have two computers, how about a friend's?
[AT&T Samsung Galaxy S 4 General] hovax615@hotmail.com:
It took me awhile also. You have to uninstall your USB drivers then restart and it'll install it automatically and after that just run kingo and let it install the drivers itself. Don't install the Samsung drivers or anything it should do it itself.
[AT&T Samsung Galaxy S 4 General] highrolla32:
Thanks for all of the suggestions, I ended up having to dig out my dinosaur winXP laptop, it took a lot longer, but I am now successfully rooted!
[AT&T Samsung Galaxy S 4 General] jdog_12345:
Unroot?

I have searched and from what I gathered it appears that this tool also unroots as well but I just want confirmation by someone that has tried it. Can someone please confirm that they rooted and successfully unrooted using this tool? My phone is relatively new and in case it craps out I want the option to go back to stock. I only plan on freezing the OTA apps and installing some of my favorite root apps (TIBU, Root explorer, etc.). Thank you in advance.
[AT&T Samsung Galaxy S 4 General] hovax615@hotmail.com:
The confirmation is in a few posts back by bigcid10
[AT&T Samsung Galaxy S 4 General] hotsauce32:
Unrooting from within SuperSU also worked for me
[AT&T Samsung Galaxy S 4 General] abudabu:
Works brilliantly!
[AT&T Samsung Galaxy S 4 General] chrismine:
Worked and got root on ASUS TF300TG with latest 10.6.2.10 firmware and locked bootloader.
[AT&T Samsung Galaxy S 4 General] Nightfrost95:
does this work with AT&T S4 with MF3 firmware?
[AT&T Samsung Galaxy S 4 General] xBeerdroiDx:
100%

http://xdaforums.com/showpost.php?p=42320414&postcount=2
[AT&T Samsung Galaxy S 4 General] Nightfrost95:
Excellent stuff

I assume the "Remove Root" doesn't work, right?

(Concerning MF3 firmware)
[AT&T Samsung Galaxy S 4 General] Outlaw_Gamer:
First timer

I have never rooted a phone before, but I am pretty computer savvy. I have a S4 I337 MF3 version, so this root method seems pretty easy to install. My question is once I root it will it erase all my apps, settings, pictures, etc..?? I am not looking to put a custom rom just want to get rid of my bloatware, and be able to install rooted apps.
[AT&T Samsung Galaxy S 4 General] midas69:
Whoo Hoooo

I'm so excited. Saw a new version of Kingo (1.09) was released today and tried it on my i337Z and it worked.

Now I'm off to have some fun!!!!!!! :victory:
[AT&T Samsung Galaxy S 4 General] xBeerdroiDx:
Nothing will be erased. Be sure to read up before you begin removing/freezing apps though. Search around. There's a thread or 2 on what's safe to remove. Wouldn't want you to bork anything. Cheers.

:good:
[AT&T Samsung Galaxy S 4 General] Outlaw_Gamer:
Thank Beer!
[AT&T Samsung Galaxy S 4 General] LZLandingZone:
Successfully rooted my phone with MF3. No custom icon either, and I installed Xposed Framework from the Play Store. Very great thus far.
[AT&T Samsung Galaxy S 4 General] lshishido03:
is this a better way vs. the OTA root that is out?
[AT&T Samsung Galaxy S 4 General] Kockowan:
??? Please link...
[AT&T Samsung Galaxy S 4 General] jd1639:
Learn to search " kingo root s4 xda"

---------- Post added at 08:59 AM ---------- Previous post was at 08:55 AM ----------

Learn to search "kingo root s4 xda"
[AT&T Samsung Galaxy S 4 General] RiPpeR_dUdE:
Unroot on MF3 without causing "custom" is still an issue with this tool.
[AT&T Samsung Galaxy S 4 General] hovax615@hotmail.com:
When I rooted my device with this method I never got a custom lock screen but i unrooted using supersu. But some ROMs will give your device the custom lock screen i had a scottsrom and it gave me the custom lockscreen when i didnt have it at all but I somehow figured out how to get rid of it using tibu and just reinstalling system apps don't know which one threw it back to normal but it worked.
[AT&T Samsung Galaxy S 4 General] zaphodbeeb:
Can the HTC One be rooted without using htcdev to unlock the bootloader with this version?
[AT&T Samsung Galaxy S 4 General] jd1639:
This is the s4 forum. You should ask in the HTC forum
[AT&T Samsung Galaxy S 4 General] ConstantineEX:
Much earlier post seems to have gone unanswered so I'll ask it again. If it's been answered elsewhere since I apologize.

If rooted using this method on MF3, will it still be able to accept OTA updates (no custom roms, just root)

Thanks!
[AT&T Samsung Galaxy S 4 General] phobia09:
You *should* be able to accept OTA's. The only way you couldn't accept an OTA while rooted is if you're in a custom ROM or if you have the OTA apps frozen.
[AT&T Samsung Galaxy S 4 General] anesthesiadoc:
will I be able to update OTA and still maintain root? Or do I have to unroot, update, then re-root?
[AT&T Samsung Galaxy S 4 General] phobia09:
There are sometimes issues updating depending on what apps you uninstall in TiBu (which is why it's best to just freeze). OTA will almost certainly kill root, but generally you don't have to unroot just to update.
[AT&T Samsung Galaxy S 4 General] anesthesiadoc:
So can I install some other rom, like google play edition after I do this? Sorry, I don't understand what it means when you say it won't install recovery. I'm fairly savvy with tech stuff. What would be the best rom to install, that I can easily update, maintain root, and still has majority of functionality of this phone (i.e. camera, remote functions, eye sensing thing)
[AT&T Samsung Galaxy S 4 General] hovax615@hotmail.com:
There's a post about someone retaining root and taking the ota with voodoo root keeper for mf3. If your on mf3 or say the new 4.3 ota when it releases there's no recovery for it because Samsung hasn't released the factory firmwares for mf3 via kies or odin the only way to get your phone back to normal is going to best buy or att or you'd be stuck with a paperweight as a device if you mess up. There's no best ROM its just your preference on what you want either a Google edition ROM or a touchwiz based ROM because if your on mf3 with safestrap all you have to do is go back to your stock ROM and take the ota. Read the post about voodoo root keeper and when the ota comes out try your luck at it and see if you can still retain root. If your on mdl taking the mf3 ota do the same look at the post.
[AT&T Samsung Galaxy S 4 General] ericl619:
rooted my rogers s4

very easy to use:

run program

connect usb

enable debugger

push root button

phone restarts, done

unroot is just as easy

device status goes back to official after unrooting so that i should be able to get official updates (i dont plan to use other roms)
[AT&T Samsung Galaxy S 4 General] dlahmeyer:
I used this last night to root my AT&T S4 with no problems I do do not plan on using any roms I just wanted to use a few rooted apps
[AT&T Samsung Galaxy S 4 General] An Droid:
Kingosoft Technology Ltd.?

Curious - does anyone know who the Kingosoft Technology Ltd. developers are/is?

Can we confirm whether or not anything malicious is taking place with this root method?

Has anyone attempted to see how root is being obtained? I'm assuming if you could monitor the interaction with the device it could be discovered what (debug?) commands/procedure is taking place?

A whois on the domain doesn't reveal anything and possibly raises more questions..

Also, SuperSU is being pushed to the phone - does anyone know whether or not Chainfire was asked permission?

For this reason, I'm hesitant to trust it.
[AT&T Samsung Galaxy S 4 General] mic141414:
i must say that i share your concerns

I have a nexus 4 i would like to root it without wiping it (other tools can root but need to wipe too)

So i am interesting in it but .. exactly .. we don't know many things about how/who .
[AT&T Samsung Galaxy S 4 General] KennyG123:
The people responsible for Kingo Root method have complied with XDA requirements and thread reopened
[AT&T Samsung Galaxy S 4 General] REDFOCZ:
That's good to hear. Easy methods are always welcomed.

Sent from my GT-I9505
[AT&T Samsung Galaxy S 4 General] jd1639:
Not looking for details, but the contacting of China servers is legit and safe?
[AT&T Samsung Galaxy S 4 General] rayburne:
I would like some details....

This post kinda says it all.

I hope something has changed and they share a little more info with their exploit.
[AT&T Samsung Galaxy S 4 General] KennyG123:
From my understanding they have released all source.
[AT&T Samsung Galaxy S 4 General] jd1639:
Any idea where the source has been released? Can't find it on xda
[AT&T Samsung Galaxy S 4 General] KennyG123:
It is linked from their site : http://www.kingoapp.com/open-source.htm
[AT&T Samsung Galaxy S 4 General] rbedell:
Glad to see this wasn't a fluke. It did keep my antivirus from doing real-time scanning though so I uninstalled.
[AT&T Samsung Galaxy S 4 General] MalcolmEvershed:
I don't think this source code is complete

I don't think this source code is complete because of the following:

Their site links to the code for android_run_root_shell (android_run_root_shell_src.7z), but when I run that on my Nexus 7 2013, it is unable to root (because its device database is not aware of the Nexus 7). However, this user (https_//plus.google.com/101083006674105523901/posts/6Ai3JQw6dzk) was able to get Kingo to root his Nexus 7 2013. Thus, if Kingo can actually root the Nexus 7, but the source code for android_run_root_shell cannot, then Kingo must not have released all the source code.

There may be reasons why this theory could be wrong, but this seems suspicious to me.

Thanks.
[AT&T Samsung Galaxy S 4 General] KennyG123:
We just got them to figure out how to post all the source to comply. I don't think they realize they have to update it as they add devices and change code. I will get a message to them.
[AT&T Samsung Galaxy S 4 General] KennyG123:
There is no requirement for them to release device specific exploits. They did at first as a courtesy as it is not covered under the GPL requirements. The parts under GPL are not modified per device.
[AT&T Samsung Galaxy S 4 General] Kockowan:
So nobody can exactly retrace what the exploits are doing!? Installing unkown/malicious software for example...
[AT&T Samsung Galaxy S 4 General] KennyG123:
Exploits have never been covered under any requirements to release source, nor have I ever seen exploit source publicly posted as I imagine the manufacturers would quickly plug that hole. As any manufacturer will tell you, rooting your phone is a risk...period. You open your phone up to security risks by doing so.

Perhaps contact them directly and ask for the specific exploit you are looking for they may accommodate you.
[AT&T Samsung Galaxy S 4 General] kmr669:
Is it good for att network
[AT&T Samsung Galaxy S 4 General] erandhawa:
So I am assuming XDA is allowing Kingo because it seems to be a safe way to root? I read some people had success rooting MF3 can anyone give their input, I am currently using the Safestrap method but can't update to 4.3 yet, has anyone updated to 4.3 with this exploit?
[AT&T Samsung Galaxy S 4 General] hovax615@hotmail.com:
Kingo root will NOT work for 4.3 update. Please read other threads. If you don't care about not having root and want 4.3 update just wait for the official release. It is stable but there are some bugs with the leak that they need to work out first. Its only a couple more weeks. I'd say stay on mf3
[AT&T Samsung Galaxy S 4 General] jeflisboa:
Hello, worked fine on my Nexus 4 JB 4.3

Enviado de meu Nexus 4 usando o Tapatalk 2