Okay, I want you to answer these questions in detail and to the best of your ability. Please try and stop asking so many questions and instead giving me some answers. I can't help you if you don't. I don't want to jump around - we're going to take this one step at a time, and ensure we don't miss anything along the way. Give me some breadcrumbs, and I can hopefully lead you out of the forest.
1. What device are you using? Please give me at least its generic name, and preferably the exact model number.
2. Were there any tutorials you followed? Can you link them?
3. What did you do, as you understand it, exactly? Give me every data point you can recall, please.
5. What "ROM" did you flash? Please give me a file name.
6.Have you tried the trickle charging trick I mentioned?
Now, some small clarifications:
1. NO, I SAID KINGROOT DOES NOT DO THIS. Please read carefully, because any fix I'm going to be able to offer you will need to be followed exactly, and you are screwing around with things that, as you are painfully aware now, can potentially render your phone a brick.
Root has a special name, but it's just Administrative permissions. They're a native and integral part of the Android OS, available on every device. They're just hidden from the user for security reasons. When you "root" something, you just open up access to Administrative privileges; nothing else. It doesn't alter the device in a way that would cause these symptoms.
You know how on Windows, when you try and do something important, you get that "Admin permission required" asking for a password (if admin has one) and yes/no? Well, Android has that, it just is constructed so that the user never gets that kind of access, because they don't need it. The thing is, and the reason people force it, is because some apps can make use of these high level permissions to do some really neat stuff. A classic example would be an adblocker - the hosts file needed for this is protected on Android. Having admin access, aka, ROOT, lets the app edit and modify this file as required to block ads. If a person doesn't need root, they shouldn't enable it. It's not inherently bad, but it represents a security risk if one doesn't have a purpose for having it enabled.
My point here is simply that it's already a normal part of the operating system, on every single android device on the market. The user just normally does not have direct access to "root", and therefore, blaming this for your problems is not logical, since it'd cause problems for literally every other android user in the world if so.
2. No, uninstalling the Kingroot app does not unroot your phone. Kingroot is basically a "safe" virus that runs security exploits on your phone to get you access to root permissions. I ran it on a Sony phone to get root - it basically just makes the process easier, since for some devices it can be pretty onerous. Once these are obtained, they exist independently of the Kingroot app. There's a way to remove root, but we have other things to deal with right now, so let's stick to that for the time being, OK?
Finally, Please specifically address what I say, instead of just writing a response with more questions. I need to know explicitly that you are doing what I am suggesting, or if you're not. Implicit does not tell me this, as you may have forgotten or opted not to do it, and I need to know that.
It sounds to me like you probably turned your phone into a paperweight, but if you want to try and see if I'm wrong, I'm going to need cooperation.
PEACE!!!
Facebook
Twitter
Instagram