This is my first time rooting and ive googled all that i can, forgive me if i dont understand right away.
I rooted my L90 D415 TMobile with lollipop 5.0.2 using this on youtube: watch?v=mQoERPnQ8Qk method but with LG One Click v1.3.
Everything went fine and it ended up rooted. And then I went on to install Flashify and flash TWRP with it so that I could install Xposed Framework. I then followed this on youtube: watch?v=bet8K238SSk method to install Xposed. Finished that method and rebooted and I still had root and i also had xposed activated.
The problem started when my phone kept reading low storage space when I had plenty of space, space i usually have left. I remember reading that this was a problem. I followed the method right with Clearing CACHE/Dalvik after flashing xposed zip in TWRP, just like everyone said so I was confused as to why I got it.
So rebooted into TWRP with Flashify and cleared Cache and Dalvik again and rebooted back into system and it still said low storage space and it also said "there is no su binary installed, supersu cannot install it" root checker told me the root wasnt installed right and that my phone was no longer rooted. Now i cannot get into twrp through flashify to flash my recovery either. I am worried because this is my very first time rooting.
I just need my root back.
Can someone please help me and keep it in dumb terms because im new and dont understand all the Root lingo.
biblicachanel said:
This is my first time rooting and ive googled all that i can, forgive me if i dont understand right away.
I rooted my L90 D415 TMobile with lollipop 5.0.2 using this on youtube: watch?v=mQoERPnQ8Qk method but with LG One Click v1.3.
Everything went fine and it ended up rooted. And then I went on to install Flashify and flash TWRP with it so that I could install Xposed Framework. I then followed this on youtube: watch?v=bet8K238SSk method to install Xposed. Finished that method and rebooted and I still had root and i also had xposed activated.
The problem started when my phone kept reading low storage space when I had plenty of space, space i usually have left. I remember reading that this was a problem. I followed the method right with Clearing CACHE/Dalvik after flashing xposed zip in TWRP, just like everyone said so I was confused as to why I got it.
So rebooted into TWRP with Flashify and cleared Cache and Dalvik again and rebooted back into system and it still said low storage space and it also said "there is no su binary installed, supersu cannot install it" root checker told me the root wasnt installed right and that my phone was no longer rooted. Now i cannot get into twrp through flashify to flash my recovery either. I am worried because this is my very first time rooting.
I just need my root back.
Can someone please help me and keep it in dumb terms because im new and dont understand all the Root lingo.
Click to expand...
Click to collapse
Don't feel too bad. We all had to go through it at one time. It took me about 10 days to realize what all it took to do this so I didn't hard brick my phone.
This storage space can become a problem due to the fact that Android only allows certain amount of space for /system partition. With a stock ROM, its almost crammed full then. Add Xposed to it, and I'm surprised the app framework installed.....anyhow...can you boot normally into your OS? If so, use this method to obtain root....I know it says for G2, Flex G2, and G3, but this works for most LGs including the 415. It's the method I've used several times without problem.....http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/
Let me know if that works.
Sent from my LG-D415 using Tapatalk
Related
Hello everyone... I just bought at&t note 3 unlocked version. Problem is that its on kitkat 4.4.2 and doesnt show any ota update so can anyone please provide me a link of stock rooted at&t lollipop rom which i can flash and root method with a proper guide please? I would be very thankful.
What you do is root what you have, install Towelroot https://www.androidfilehost.com/?fid=23991606952593961 (open the app and click "make it rain" and it's rooted). Install Supersu and Busybox, then Safestrap https://www.androidfilehost.com/?fid=23991606952593962, open it and install it and this is rooted lollipop http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2. Just one thing, (not saying you will) but flash the OC1 Kernel in Safestrap before you leave Safestrap. " 5. Flash the file called "SM-N900A_OC1_Kernel_Safestrap_Installer.zip" which is located under /sdcard/OC1_Kernel/ "
Hey Rooted, i have a 1.39gb file on my ext sd card called SM-N900A_0C1_Lollipop_Rooted_rom.zip, is it safe to delete this if i already have rooted oc1? or do i need it to flash safestrap? Also, for the past few weeks my oc1 rooted note 3 has been randomly rebooting itself in the middle of me using it, then entering a bootloop until it successfully boots up. Then sometimes when it successfully boots up, it reboots itself right when i put my password into the lockscreen. Sometimes clearing the cache doesnt help, i clear it multiple times for it to work. The other day i clicked the end button on a phone call, and right when i ended the call it rebooted itself. im lucky it didnt reboot during the call, i was on the phone with a towing company lol! Any idea whats going on?
If it's rooted, yea you can delete the file then. Do you have Xposed install, flash anything else with Safestrap, did you do a clean install of the Rom? When did the rebooting start, after you installed an app?
I do not have xposed framework installed, i heard its not compatible with the oc1 root. I never flashed any custom rom, im running just a stock rooted rom. Im not sure exactly when the rebooting started, its been going on for 2-3 weeks, i cant remember what i did before that. Last night i swapped sd cards to make sure it wasnt that, but i already had 1 random restart today. Do you think swapping sim cards is a good idea?
Hi, I recently rooted my Z3c using KingRoot. I ten installed custom Rom: SLiM ROM 4.9. Works great, but now I found out Kingroot is very untrustworthy. How do I remove/replace kingroot without loosing root?
I rooted as per these instructions:
whattechsays.com/root-xperia-z2-z3-lollipop
So I have SuperSU installed, but KingRoot does not appear in apps list - so no option to uninstall. I can see kingroot folder in internal memory. Is deleting this sufficient to remove kingroot and any potential back-door?
I am new to rooting, so please explain simply if you can.
Many thanks.
Better remove Kingroot, and unroot all at once. You have Slimrom installed so I'm assuming your bootloader is unlocked so simply flash SuperSu Zip via recovery to get back root.
Kingroot is unreliable and shady when it comes to rooting devices in fact its not even endorsed here in Xda
Revontheus said:
Better remove Kingroot, and unroot all at once. You have Slimrom installed so I'm assuming your bootloader is unlocked so simply flash SuperSu Zip via recovery to get back root.
Kingroot is unreliable and shady when it comes to rooting devices in fact its not even endorsed here in Xda
Click to expand...
Click to collapse
I already have SuperSU installed already. And when I run rootcheck it says SuperSU has root. I have ' uninstalled' Kingroot, however kingroot folder/files remain on internal memory and I assume it could still be active and hiding it's process?
Sent from my D5833 using Tapatalk
Came across this thread from Google, but since it doesn't look like you really got an answer, here goes.
When you flashed Slim ROM, you would have replaced the system partition where Kingroot was installed, meaning it is no longer there at all.
The files left on the internal memory would have been written by Kingroot before and can just be deleted.
Frenik said:
Came across this thread from Google, but since it doesn't look like you really got an answer, here goes.
When you flashed Slim ROM, you would have replaced the system partition where Kingroot was installed, meaning it is no longer there at all.
The files left on the internal memory would have been written by Kingroot before and can just be deleted.
Click to expand...
Click to collapse
Oh dear, another Kingroot user stuck, how many warnings about Kingroot need to be posted on the threads before people listen.
Personally, knowing about what Kingroot does and the information it sends to China, I would wipe my phone and start from scratch.
There is a good guide written by bilboa1, which is very easy to follow.
Frenik is right, if you flash a rom, then the system should get wiped also. Just make sure you wipe data as well as dalvik/cache then you might end up with a Slim rom with SuperSU.
http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/
I used the version 2.4 and worked like a charm
Although as above... even though i have stepped on the same rake as you... don't use KingsRoot... there probably is a fake copy of my phone somewhere in china thanks to that...
"use SuperSu Me" app
Sent from my D5833 using XDA-Developers mobile app
Hi fellas. I write ehre in order to not open a new thread. I recently bought one of this little beasts. I'm running 23.4.A.1.264 (stock in phone), Android 5.1.1. I've succesfully rooted it with king root 4.9.5. I've tried to change it to Supersu without success. I've tried supersu me, the script to remove kingroot to supersu from ver 1.8 to 2.4 and always lose root permissions. Could someone tell me what the f*** I am doing wrong?
So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.
I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...
Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?
I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it
Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk
Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?
Did you flash over 2.71. And do you have a su app icon on your scrren.
noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.
Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot
MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!
Welcome bud.
Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother
Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk
Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha
My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk
I think it's normal...maybe...ha Im pretty sure it's the warranty bit
are there root for N910A 5.1.1
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Just looked now. For one example, SuperSU acknowledges AdAway, but when I try to fire up AdAway, it won't work, saying it doesn't have access.
Did you install twrp and did it ask after you booted to twrp if you wanted to root the device.. if so this was a no no.. your already rooted twrp just get a little confused with the new kernels... you must remove root and reinstall supersu and when it ask when you load twrp do not root but reboot do not swipe... unless there is an easier way this worked for me...
I had the same or a similar problem. I didn't lose root completely but at times various apps were unable to gain root (after previously getting it successfully). The phone would freeze while Titanium or Root Explorer for example were waiting fruitlessly for root to be granted. It was haphazard. One time the app would work and next time it wouldn't, or another wouldn't.
Finally it got so frustrating that I installed my favorite rom on it (Tekhd). Now all is stable. I was hoping to keep it stock rooted until mm came out but I couldn't figure out what was going on so I blew it away. I had twrp on it too and would always be prompted "root not detected" but if I allowed it to install SuperSu it would loop.
Sent from my SM-N910T3 using XDA-Developers mobile app
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Eric618 said:
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Click to expand...
Click to collapse
you need to odin the firmware for your phone and then restart fresh
without root twrp won't install rom you will get error..
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Eric618 said:
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Click to expand...
Click to collapse
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Thanks! I'll give that a try when I get home today.
S5Sickness said:
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Click to expand...
Click to collapse
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Eric618 said:
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Click to expand...
Click to collapse
Your Welcome...
Eric618 said:
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Click to expand...
Click to collapse
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
marseillesw said:
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
I had tried that. It was very sluggish, and would frequently drop root access altogether. Since following S5Sickness's advice it's been solid, however.
https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app
Hello!
I'm rooting noob.
I've got a big problem with my phone. I have rooted my device some time ago, now i want to go back to stock. When i choose supersu option to fully unroot nothing hapend. After reboot, supersu is still there. I tried to flash zip with newest version of supersu-nothing. I tried to remove supersu manually it doesnt help either. Supersu seems to miss some of the libaries but when i try to instal it via twrp it shows no md5 file found error. Is there any easy way to return to stock? I mean something like clear all phone memory and just flash stock rom? Getting to fully operating root its also fine.
Go easy on me, im learning hard way. English is not my native language so sorry for all the mistakes i made.