Hey guys,
Since i rooted my SGS a while ago and then updated superuser to the last version available in market, that i'm facing an annoying issue i can't manage to solve by myself. Somehow when i applied one of the first update.zip files available in xdaforums to root my phone i got a su binary in /sbin. And now it is conflicting with the newer version. I can delete /sbin/su and its all ok, but once i restart my phone i've to do it again.
Is there a way to remove /sbin/su forever? I was told i had to create a new boot.img without /sbin//su but i found that a bit hard for me to do at this point. Would it be too much to ask, that someone used to it maybe could fix me and update.zip to reverse this?
Thanks in advance
Related
Hi guys, thanks for the forum and i hope to become a part of it. I've been under so much stress since yesterday, my galaxy s3 (on EE in the UK) for the first time decided it's data was corrupted yesterday after my battery died, never done this or anything like it before, and it wouldn't let me access the phone itself unless the data was reset.
I had a lot of very precious pictures in my gallery from the weekend, which unfortunately chose not to backup to google+ for the last few days, even though it always has up until recently. All night/day i've been trying to figure out and get software to recover these photos, which i think is possible as i did it a long time ago on a blackberry, but not android yet. I'm just hoping it can be done so the photos aren't forever lost, the other stuff gone doesn't bother me so much.
The guide i'm following (here: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705) says it needs to be rooted first, and i can't even get past step 1. I've only ever rooted my old galaxy S1 (which worked back then) but i can't seem to get the S3 to do it. And now my phone also believes there's no sim card in and i get no signal now.
this is the guide i followed: http://www.ibtimes.com/how-root-sam...-jelly-bean-official-firmware-tutorial-975812
though i think i need a newer PDA file to flash my i9305 with. I'm on the EE network running 4.3 jelly. It installed Super SU but root checker says it still isn't rooted.
So have i messed this up? And is there any hope for me getting these pictures back?
Thanks in advance for any help, it's much appreciated.
if you are running on 4.3 then you are not following the right guide to root...
use THIS ONE instead... if it fails to root use the workaround part, i used it and worked....used the workaround to install custom recovery and then flashed chainfire zip from his website and updated SU and worked.
are you still able to boot the phone?
Thanks for the response, tried that guide and still getting no signal on my phone (no mobile connection at all, sim card isn't recognised as being there) and i don't think it's rooted right. Still saying SuperSU has stopped working when i try to open it.
I put the Root_SuperSU.1.02-Busybox.1.21.0.zip on the internal SD and tried that too.
Which is the chainfire zip you're talking about, could you possibly link it? I don't really get what you mean by custom recovery, do you mean it's the same as flashing the Busybox thing from recovery mode?
And yeah it still boots up normally...
use that tutorial to install a custom recovery...then install this SuperSU - http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1 - flash it in custom recovery....after that update app with playstore and should work.
but i suggest you get it to a specialized shop to get your photos back...
2 weeks ago I upgraded my phone to a HTC One (M7, on sprint) and I decided I wanted to try and root it. So I followed the htconeroot (dot) com root guide for M7 exactly and everything worked fine up until when it asked to have me boot up SuperSU. It gave me the error "There is no SU binary installed and SuperSU cannot install it". I've looked around for a fix and a lot of searches have led me to this forum, and a lot of the posts did have fixes. But 1. I'm too ignorant and new to all this to fully understand the fixes given, and 2. I want to make sure that the fix I use is for my device.
Anyways, I'm on android 4.4.2 and I believe that may be the issue, but I'm not sure what to do. So if someone can help me out and give me an easy to understand beginners step to step guide on how to fix my issue I would be very grateful. Thanks!!
Edit: Fixed. The guide I used had a written, and video guide for rooting. I followed the video version, but went though the written guide while troubleshooting. It turns out the video guide tells you to put in a certain file that is not needed for users using Android 4.4.2, and that you need to use another file. I switched files and it now works. I'm good now.
edit :fixed
Hello I have the same problem. I have a HTC one sprint and I tried rooting it and I installed root checker and it said no root access and supersu said no binary and stuff and your seems as it is fixed please reply I need you help on how you got it to work and the links to everything . Thanks
I have googled this but all the solution I find are either to factory reset or re-flash your firmware. I'd really like to avoid that.
I have a Z3 compact, rooted and then flashed with the latest firmware I think its the .77 at the end.
Xposed framework with a few mods running beautifully on it.
The last 3 changes I did before the phone got stuck in the boot loop:
- updated minmin xposed module from 1.8.1 to 1.9
- updated another module but forgot its name
- fiddled with the settings of this app: https://play.google.com/store/apps/details?id=org.namelessrom.devicecontrol
I'm pretty sure its the latter as it sets certain kernel parameters at reboot.
Can anyone give me instructions on how to disable this app from booting or how/where to find it and delete it?
Where can I find logs of this boot loop?
I really want to avoid re-flashing, re-rooting, re-flashing and restoring my backup again as that will take half a day.
I've just brought back mine from bootlooping after I've installed several extensions (just discovered that the culprit was DonkeyGuard) and I'm about to do it for the second time, by flashing a Xposed-Disabler-Recovery.zip file that's stored either in the root of your phone or at
/storage/emulated/0/Android/data/de.robv.android.xposed.installer/files/Xposed-Disabler-Recovery.zip
But that would only work in case you messed it up with Xposed.
Thanks, I'll keep that in mind if I encounter this problem again.
Still finding it hard to believe there's no other reply to a seemingly common problem / question, does everyone just pack up and factory reset when boot looping?
Well, it's as common as people repeating to make a nandroid backup, you know
Btw, before I will flash yesterday a black theme (modded system files), I made the backup, so when my Z3C got stuck in a bootloop for the third time, I had nandroid ready. Such a shame, I really liked that mod.
If the kernel is problem, how about just reflashing your kernel?
Believe it or not, I started looking into nandroid backups today already made my first tests.
Until now I relied on titanium backups but that still makes me do a factory restore before I can restore stuff from those backups.
But the issue is, I am not looking for better "protection" I'm trying to find out how I can fix something minor like this i.e. via adb and command line...
Talking about a custom kernel, is there one? I have a rooted xperia z3 compact and wouldn't mind checking out a different kernel but I held back unlocking my bootloader until there is a custom ROM available that can fully replace my rooted stock ROM.
If love to get PAC man ROM for my phone.
I had the same issue, but by using 3C toolbox (similar to the app you've mentioned).
In my case putting back the original build.prop into /system via ADB fixed the bootloop.
As for custom kernel, you can try AndroPlus kernel HERE
@ovizii as @davebugyi said, you could always put some files back via ADB, but you need to have a file that you want to put back, like in davebugyi's case an original file. In your case you don't have it, so unless you know what value you changed, there is nothing much that you could really do with ADB access.
-V-O-Y-A-G-E-R- said:
@ovizii as @davebugyi said, you could always put some files back via ADB, but you need to have a file that you want to put back, like in davebugyi's case an original file. In your case you don't have it, so unless you know what value you changed, there is nothing much that you could really do with ADB access.
Click to expand...
Click to collapse
Hm, I was thinking along the lines of accessing log files, like a system log file, check what went wrong, i.e. auto start of a certain app, or setting of kernel parameters at boot time, then remove the offending apps/entries?
Just not sure if that's possible, hence this question here
Checking out the suggested ap and the kernel! Thanks!
In the past, I have had updated a few times on root without facing a single problem, until yesterday, when I received the Lollipop update which weighs 776.73mb and stops updating in the very beginning before running into some error 0x11110000.
So, question is that is it possible to update ON ROOT ?
I know using SuperSU unroot one can't change the LG RCT check, but what's interesting is that after making a second attempt to update, IT STARTS ALL OVER AGAIN. I mean, downloading 776.73mb multiple times isn't going to reduce your data bills
Any ideas ?
Rooted. Stock ROM.
EDIT
Fixed it by performing a full 'unroot' inside of SuperSU and then using the LG PC Tool to update to Lollipop Well, I'm rather surprised that it worked when the same didn't work on the phone itself. So I'm guessing that the process used by the tool overrides all problems as long as the firmware remains stock.
Oh and I really didn't want to mess up that bad by taking the route suggested in that thread, @lfom, because I don't have an extra phone to fall back on, in case my current one fails to work
Modern SU tools also modify other system files, primarily to try to resist to updates... My bet that what is causing the problem is the same as this other thread (it offers a solution too):
http://forum.xda-developers.com/showpost.php?p=44913304&postcount=8
Actually , i updated my phone with root using LG tool, after update i lost my root but all apps where there, which means there is no need for unroot os something like that.
Hello everyone!
So I rooted my Note 3 back when I first got it and I've been loving it. Well, about a month ago I noticed that an application that I wrote (restarts my phone automatically under certain conditions) would not work correctly, as though its Superuser permissions were revoked, but the SU app said everything was fine. Fast forward to a few days later and I try to access the root of my phone using ES File Explorer and discovered that I had lost root. I tried Kingo Root and Towelroot and they both failed, so I'm stumped as to why I lost root and why I cannot seem to get it back. I know I could go about wiping the phone but that would remove everything on my phone except for my applications and those are the least of my worries.
Any ideas? I appreciate any and all help!
Android Version: 4.4.2
Baseband Version: N900AUCUCMLG
Kernel Version: 3.4.0-257432
Build Number: UrDroid KOT49H.N900AUCUCMLG
Not sure if any of this information makes a difference but it's worth posting just in case.
To anyone who may come across this and is having the same issue, I was able to resolve mine, and hopefully the steps that I took (listed below) will be of some kind of assistance to another.
I still had Safestrap installed, so I was able to install a ZIP version through it, and I rebooted after it was done. I let the phone load back up fully before going back into Safestrap to wipe the Dalvik/Cache, attempt to Fix the Permissions (which failed), and then renamed the data/data/eu.chainfire.supersu folder to eu.chainfire.supersuh (as I thought that maybe the old folder was causing conflicts). After booting back into Android I had root again! I cannot delete the eu.chainfire.supersuh hence why I renamed it, but I've got root back on my phone so I'm satisfied.
I will add that all of these steps may not have been necessary but I do not know what step made it work, this is just what I did to solve my problem.