Hi there
I've in the past, rooted some of my android phones. Just got the HTC one M8 and it updated to 5.0.
I would like to get root access (not planning on flashing a new rom). I'd like to get OTA still.
I followed step by step instructions on how to root, but when I go to SU, I get an error message:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!"
Also, my touchscreen / keyboard seems messed up. It starts typing random stuff on it's own I think I might have damaged my phone by keep trying to do it.
I'm a noob and try to usually follow step by step instructions.
Please help - and in basic terms, please
Thanks!
Update
I reset my phone, and now it is rooted and works. Problem is that the screen is still messed up It doesn't type what I want and closes typing screen, opens other windows etc What should I do?
Does the glitchy behavior only happens when you're charging the phone?
My phone has now updated all its apps and the screen is working fine again, but I get the same message again as previously. SuperSU message: There is no SU binary installed, ......".
Seems it worked only until it updated.
Would love to get it rooted. Help would be appreciated please.
TheMabaet said:
Does the glitchy behavior only happens when you're charging the phone?
Click to expand...
Click to collapse
You're right. It was happening while charging. My phone was still linked to the laptop. So that could be it.
Related
So, I recently updated my Glide to ICS via the offical Samsung Kies way.
I was having problems with it to say the least, so i sought out a root, and began to follow the directions here
http://forum.xda-developers.com/showthread.php?t=1378082
I assume this is not for phones with the Official ICS update on it because when i reached step 10. After pushing the Kernel via Odin...and waiting for my phone to reboot. All i get is the Samsung logo across my screen with a ! at the bottom with a yellow triangle around it. It doesn't go anywhere else. I am able to reboot into Download mode so i hope there's a way to fix it.
So if anyone can point me in the right direction on this, i'd be much appreciated.
JrizzleTX said:
So, I recently updated my Glide to ICS via the offical Samsung Kies way.
I was having problems with it to say the least, so i sought out a root, and began to follow the directions here
http://forum.xda-developers.com/showthread.php?t=1378082
I assume this is not for phones with the Official ICS update on it because when i reached step 10. After pushing the Kernel via Odin...and waiting for my phone to reboot. All i get is the Samsung logo across my screen with a ! at the bottom with a yellow triangle around it. It doesn't go anywhere else. I am able to reboot into Download mode so i hope there's a way to fix it.
So if anyone can point me in the right direction on this, i'd be much appreciated.
Click to expand...
Click to collapse
reflash the ics update via odin. should get you back running
Once you get it back on ICS use this guide to root it. http://forum.xda-developers.com/showthread.php?p=30233038 Read the first 2 posts and you should be able to get root with no problems.
inthepit said:
reflash the ics update via odin. should get you back running
Click to expand...
Click to collapse
OK, i used kies to update it to ICS, is there a place i can get the file to push via Odin? through the PDA part right?
http://forum.xda-developers.com/showthread.php?t=1831561
Its what i used to recover from a similar issue
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
Ive got ICS back on my phone, finally. However i keep getting "unfortunately, the process com. android.phone has stopped." And am unable to get service, i did receive a text message, however i was unable to open my messages without the above mentioned error message. Seems pretty hopeless right now.
SUCCESS!!! Thank you everyone. I'm still experiencing some of the same issues i had before i started all this mess. (for some reason people can hardly understand me on the other end of calls, when i put the noise supression on it gets a little better, but meh) Other than that i have no idea if i attained root or not. lol. I did however have CWRM touch working and installed superuser from .zip from it...so i assume that means i also attained root? Thanks again!
First of all let me say THANKS to all of the dedicated folks on this website that I have found to be most useful while looking for help.
My problem may have been discussed previously, but after doing much browsing I must not be using the right keywords to find a resolution.
I am having issues with a SGH-i747 running stock 4.3 that I just purchased, so I have no clue what may have been done to it in the past.
So as the title says - The green android while booting into recovery mode just falls over with red triangle, and underneath it flashes - No command - Error - No command.
Also if I do try to flash anything - I get several RED errors in a row basically saying - E: No data folder found and a few other things before it quickly reboots and I can't see what the other errors are.
Would appreciate any ideas you folks may have - Thanks.
TWRP had an Odin flashable .tar. If you need recovery you should be able to just use that or terminal command to install.
Odin Fails Too
BCSC said:
TWRP had an Odin flashable .tar. If you need recovery you should be able to just use that or terminal command to install.
Click to expand...
Click to collapse
This is how I discovered the android falling over issue.
While attempting to install clockworkmod.tar through Odin which will PASS
But then when entering recovery mode I get the stock recovery with green android falling over & data errors.
I have performed this same procedure on my other phone which is identical make and model but starting off with stock 4.1.2 without any issues.
I have also tried flashing philz_touch_6.0.7.9-d2att.tar.md5, but that creates a whole new set for errors & fails.
Deeeno said:
This is how I discovered the android falling over issue.
While attempting to install clockworkmod.tar through Odin which will PASS
But then when entering recovery mode I get the stock recovery with green android falling over & data errors.
I have performed this same procedure on my other phone which is identical make and model but starting off with stock 4.1.2 without any issues.
I have also tried flashing philz_touch_6.0.7.9-d2att.tar.md5, but that creates a whole new set for errors & fails.
Click to expand...
Click to collapse
Push it in Terminal Emulator app. Instructions here. http://forum.xda-developers.com/showthread.php?t=2170635&highlight=recovery+terminal. This forces it top the memory block, so should work. I'm asuming the phone boots and you are rooted.
BCSC said:
Push it in Terminal Emulator app. Instructions here. http://forum.xda-developers.com/showthread.php?t=2170635&highlight=recovery+terminal. This forces it top the memory block, so should work. I'm asuming the phone boots and you are rooted.
Click to expand...
Click to collapse
Boots up just fine & Unlocked, but is not rooted yet - This is why I tried getting clockworkmod.TAR & CWM_SuperUser_v3.0.7 (1).zip flashed.
But my main concern is getting the android falling over issue fixed at the moment, and I think the rest will resolve itself once that's accomplished.
I realize I am no rocket scientist with android phones (Galaxy S3), or I wouldn't be looking through these help forums, and asking for advice.
But it seems to me it's like fixing your car - You need to figure out the root cause of the issue rather than putting band aid patches on it.
Seems like the operating system has other issues to deal with other than obtaining root access at the moment, or it wouldn't keep giving me errors stating that it can't access the DATA files.
Maybe my way of thinking is way off base? Thanks for all your input anyways & I will click the THANKS button if it lets me.
Deeeno said:
Boots up just fine & Unlocked, but is not rooted yet - This is why I tried getting clockworkmod.TAR & CWM_SuperUser_v3.0.7 (1).zip flashed.
But my main concern is getting the android falling over issue fixed at the moment, and I think the rest will resolve itself once that's accomplished.
I realize I am no rocket scientist with android phones (Galaxy S3), or I wouldn't be looking through these help forums, and asking for advice.
But it seems to me it's like fixing your car - You need to figure out the root cause of the issue rather than putting band aid patches on it.
Seems like the operating system has other issues to deal with other than obtaining root access at the moment, or it wouldn't keep giving me errors stating that it can't access the DATA files.
Maybe my way of thinking is way off base? Thanks for all your input anyways & I will click the THANKS button if it lets me.
Click to expand...
Click to collapse
I understand exactly what you mean, but root access can be a key to you here. Your recovery is broken or at least something in a system file is harming what recovery is trying to do. Problem is these are not accessible without root. Root is not the band aid, it's the scalpel Try fixing that car without wrenches. The problem with recovery is that it is protected. You could flash a new stock one as part of an official firmware, but if you are stock 4.3 you are going to run into bootloader issues (nevermind the fact that Samsung hasn't released one. This leaves your other fix as replacing your recovery and requires access to the root system files.
++On another note, I just found this and don't want to delete everything I just typed. See this thread here and see if it pertains to you. http://forum.xda-developers.com/showthread.php?t=2520115
Either you or someone else have already installed a custom recovery. Without root access recovery will fail, the android will fall and you will see red. Use this to root and fix your phone...http://forum.xda-developers.com/showthread.php?t=1963790
Good point on having no wrenches to fix the car --- I will head your advise, and move forward with getting it rooted.
BCSC said:
the android will fall and you will see red. Use this to root and fix your phone...http://forum.xda-developers.com/showthread.php?t=1963790
Click to expand...
Click to collapse
You nailed it on the head - I'll be sure to also hit the Thanks tab for chainfire also since he deserves credit also.
CF Auto Root did the trick and the poor little green android no longer falls over.
Moderators can mark this thread as resolved & Thanks again for all your help.
Hello guys. I am posting this thread because I rooted my LG G3 and everything was going fine until I saw a system update for my phone and I got it. Turns out that wasn't the smart thing to do and when the system update was finished, when I would try to go on SuperSU it wouldsay that my SU binaries were not up to date and that I would have to manually re-root my phone. When i go on the play store, it says "no connection" even with wi-fi on. I already tried to factory reset my phone the root is still there and since I can't access the play store I can't do most of the things some youtube videos show. Any idea on how to unroot my phone? I would really appreciate if you would show me a step by step process on how to fix this problem?
eddymontalvo said:
Hello guys. I am posting this thread because I rooted my LG G3 and everything was going fine until I saw a system update for my phone and I got it. Turns out that wasn't the smart thing to do and when the system update was finished, when I would try to go on SuperSU it wouldsay that my SU binaries were not up to date and that I would have to manually re-root my phone. When i go on the play store, it says "no connection" even with wi-fi on. I already tried to factory reset my phone the root is still there and since I can't access the play store I can't do most of the things some youtube videos show. Any idea on how to unroot my phone? I would really appreciate if you would show me a step by step process on how to fix this problem?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2799647
That guide is for all variants just follow the one for yours closely. I see this is your first post so I will tell you this before someone who isn't as nice comes along and says it: always search before starting a thread like this. This guide and many others have been available for months and are easily found with a quick Google or forum search. Also, just a word of advice, if you are rooting your phone and/or installing custom recoveries, do not ever take an over-the-air update. You could end up doing some serious damage to your phone that way. From your description of the problem though, it almost sounds as if you have screwed up your EFS partition since you have no WiFi (which is managed through the EFS as well as your IMEI # and other various cell tower connections and their corresponding information). If your EFS partition is shot and you didn't make a proper backup beforehand, then your phone is toast as far as wireless connectivity goes. Your EFS information is device specific so it cannot be obtained from anyone else or restored via the method I posted above. Good luck though man and hopefully it works after returning to stock. Let me know if you have any more specific questions you need help with.
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
mdphoenix said:
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
Click to expand...
Click to collapse
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
debianmain1 said:
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
Click to expand...
Click to collapse
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
mdphoenix said:
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
Click to expand...
Click to collapse
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
debianmain1 said:
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
Click to expand...
Click to collapse
I can always fire up an Ubuntu flash drive if necessary. I'll get working on Fastboot.
Thanks again!
@debianmain1 Hmmm, Fastboot doesn't seem to be functional. I've got download mode. Can I push something to it that way?
I managed to get somewhere yesterday. I tried flashing D85120e_00.kdz and it failed again. I got the "cannot communicate with server" error, then it rebooted and tried running initial setup and failed.
So I tried flashing D85110C_00.kdz. Much to my surprise, it worked! So I ran through initial setup and got the phone working to make sure all was well. I rebooted and got the Red 2. So now here I am. Guides show that I should be able to put it in download mode and reload factory firmware again. But all I get is the "Download Mode" graphic. It never switches over to the updating mode with the circular arrows. I fear the worst at this point, but I really don't know enough about the LGs to diagnose my own doom just yet.
Someone on Reddit pointed me in the direction of Board Diag. Unfortunately it doesn't appear to work on D851. Running out of options. Looks like it'll end up being an expensive learning experience.
Just Rooted LG G3. Have both KINGUSER&SUPERSU. Can't uninstall/replace. PLEASE HELP!
Finally succeeded in rooting my LG G3. Have Sprint LG G3 5.0.1 LS990ZVE. Newer to computers and technology such as this, especially android, as far as entering this deep into information. Hours of research and a couple attempts finally lead to success in rooting phone. Process that I found on this website led me the way. Used 'LG_ROOT_SCRIPT'. Well, after being successful, I am now stuck with both KINGUSER and SUPERSU. I cannot get rid of or replace either one. (all I have read is leading me to believe that SUPERSU is superior to KINGUSER, so I would like to have that on operable.) I have tried numerous strategies that I have found all over internet and nothing seems to work. Some processes I am weary of doing because I do not want to accodently unroot my phone. If someone could help and possibly teach me how to go about this, I would be very grateful. Please keep in mind that even though I am not an unintelligent person, I seem to be very inadequate when it comes to subjects such as these. Thank you for your time. Please help.
seezle said:
Finally succeeded in rooting my LG G3. Have Sprint LG G3 5.0.1 LS990ZVE. Newer to computers and technology such as this, especially android, as far as entering this deep into information. Hours of research and a couple attempts finally lead to success in rooting phone. Process that I found on this website led me the way. Used 'LG_ROOT_SCRIPT'. Well, after being successful, I am now stuck with both KINGUSER and SUPERSU. I cannot get rid of or replace either one. (all I have read is leading me to believe that SUPERSU is superior to KINGUSER, so I would like to have that on operable.) I have tried numerous strategies that I have found all over internet and nothing seems to work. Some processes I am weary of doing because I do not want to accodently unroot my phone. If someone could help and possibly teach me how to go about this, I would be very grateful. Please keep in mind that even though I am not an unintelligent person, I seem to be very inadequate when it comes to subjects such as these. Thank you for your time. Please help.
Click to expand...
Click to collapse
I had that same issue. Then it would not let me update the binaries for supersu and get rid of Kinguser. I take it that it is doing the same to you? You either have to do it manually by getting into the actually files and renaming supersu and flashing it. What I did though is I downloaded an apk called SUPERSUME 6.0 that you can find either here in xda Or just by googling it. There will be a minsstream version that you have to pay for, which would be nice to do if you want to support, there is also an apk version you can download for free, just keep searching. All you would have to do is download and install the program. Open and run it. Don't mind it saying sketchy **** that may make you think twice when you first begin program. (i stopped it at first. Lol) just run the program. At the end it will ask you to open supersu or it will just do it for you. Open it and update and you will have supersu ready and running.
seezle said:
Finally succeeded in rooting my LG G3. Have Sprint LG G3 5.0.1 LS990ZVE. Newer to computers and technology such as this, especially android, as far as entering this deep into information. Hours of research and a couple attempts finally lead to success in rooting phone. Process that I found on this website led me the way. Used 'LG_ROOT_SCRIPT'. Well, after being successful, I am now stuck with both KINGUSER and SUPERSU. I cannot get rid of or replace either one. (all I have read is leading me to believe that SUPERSU is superior to KINGUSER, so I would like to have that on operable.) I have tried numerous strategies that I have found all over internet and nothing seems to work. Some processes I am weary of doing because I do not want to accodently unroot my phone. If someone could help and possibly teach me how to go about this, I would be very grateful. Please keep in mind that even though I am not an unintelligent person, I seem to be very inadequate when it comes to subjects such as these. Thank you for your time. Please help.
Click to expand...
Click to collapse
Hey mate dont be afraid to remove Kingroot..
Since you have a custom recovery, you can always just flash superSU (version for your rom/device) via the recovery, and update the superSU binary within the app when you launch it for the first time. You will receive 2 options. Normal update, custom update.. Choose normal update.. Youll be prompted to reboot.. Do so, and you're rooted . Now you need to open superSU app, and configure some settings to your liking.. You're safe to remove Kingroot/user and delete its app data.. Then reboot phone in to custom recovery and clear cache and dalvik-cache from recovery and reboot back in to system.. And you're done..
***NOTE*** if you plan on installing an app called lucky patcher (cant really discuss it because of its usage purpose). Just make sure you disable "Mount namespace seperation" from superSU settings so that the app can function correctly..
Sent from Sony Xperia Z5 E6653