My Razr Maxx installed the OTA ICS update today. There were no error messages. Everything seemed to run fine. And on top of that I thought that my root was preserved.
Well, I have an old version (3.0.3.2) of SuperUser intalled that I cannnot uninstall. I cannot mount /system/ as read-write using ADB. I can't mount /system/ as rw using Terminal Emulator on the phone. I tried the one-click script EternityProject EasyRootICS to install root and it seemed to work (no errors reported), but when I edited the batch file to get rid of all of the CLS (clear screen) commands, I was able to see that when it tried to write the new superuser app to /system/bin/ it's failing (with no error reporting).
So what do I do now?
The bottom line is that I need root, but I don't know how I can get root without getting rid of my old SuperUser installation first.
I have the exact same problem..... I can't get rid of Superuser, but I can't get access too use any root applications. SU denies all of them...
Go to this link here and where it says "Note: If you don't get root by other method root attempt with su and Superuser.apk already installed." download from that link.
http://www.mod2xtreme.com/showthread.php?13332-TOOL-ROOT-Razr-EternityProject-EasyRootICS-Win-Linux
It helped with Superuser not working properly.....
Hi all. As flashing SuperUser via CWM doesn't give an uninstall option, would it be better to install
it from the Play Store, or is flashing better for some reason.
Thanks.
I think flashing is better because:when you root your Tab,in addition to Superuser you inject a file named "su" in the folder "bin" of your OS,but if you install Superuser you must put that file there manually...but there is a way:in the flash able zip remove the Superuser APP,and after flashing install Superuser or SuperSU according to your OS.
arashtarafar said:
I think flashing is better because:when you root your Tab,in addition to Superuser you inject a file named "su" in the folder "bin" of your OS,but if you install Superuser you must put that file there manually...but there is a way:in the flash able zip remove the Superuser APP,and after flashing install Superuser or SuperSU according to your OS.
Click to expand...
Click to collapse
Thank you.
I flashed CWM, and then installed SuperUser via Play, but it didn't work. I didn't know about the "su" file.
So I uninstalled SuperUser, and flashed the file I had on hand, which is SuperSU.
Worked like a charm and everything is working.
Got an "update available" message this morning, which was for SuperSU. Updated, and all is well.
Thanks again!
I succesfully updated my Samsung Galaxy S3 from Android 4.2.2. to 4.3 after rooting my Phone.
However, SuperSU doesn't work anymore, giving the message "If you upgraded to Android 4.3 you need to manually re-root".
I cannot find an answer in the forums here on XDA developmers.
Can anyone help me?
Thanks in advance,
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Rooted 4.3 and installed SuperSU
morwit99 said:
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Click to expand...
Click to collapse
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Same problem here
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
otto68 said:
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
Click to expand...
Click to collapse
if you have supersu or super user already than just download update-supersu from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and flash it through the recovery mode( custom recovery preferred).
xprivacy / reboot to recovery
In my case I was getting false alerts as xprivacy has blocked system access. (eg was with AdAway) Cleared those apps in XPrivacy and all worked find then.
Also you can try to go into recovery and the try to reboot. You may get message to reinstate/fix SU.
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
You rock, I had re-rooted my updated Android 4.3 but my SuperSU was not usable anymore. Redownloaded it, allowed it to update SU Binary, disabling Knox, and viola! Root galore
suyash1629 said:
if you have supersu or super user already than just download update-supersu from ...LINK REDACTED.. and flash it through the recovery mode( custom recovery preferred).
Click to expand...
Click to collapse
that fixed it for me..thanks :good:
Tried all these steps on the new 4.3 MK6 ROM. Does not work for me. I cant find the Root access option itself in developer options. I already tried flashing CF-Autoroot multiple times after factory reset, using odin. I CWM still says binaries outdated and SuperSU doesn't work work even after updating from play store. Later i tried flashing supersu via the recovery mode. Still no success. Any suggestions?
Edit:
Another factory reset and flash did it. I don't know how. But it is fixed now.
By following your step, my superuser icon is gone...
Stuck in ODIN
Everytime I try to root S3 LTE via ODIN with CF auto root, it gets stuck there, need some help please, have had to use kies's recovery tool 3 times today because of that
i dont have this function
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
Hi, I dont have this function in my phone, nowhere, please help me?
fragiepacino said:
Hi, I dont have this function in my phone, nowhere, please help me?
Click to expand...
Click to collapse
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
no
tallman43 said:
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
Click to expand...
Click to collapse
the root function in the developers section, nowhere i can tick it
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Sorry I thought you wanted to know how to get into developer settings....This thread is from 2013 i don't have S3 anymore if your trying to get root to work just follow some of the other suggestions posted.:good:
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Here you don't have the "root access" setting ?
Sent from my GT-I9300 using XDA Free mobile app
s3 i9305 supersu binary problem
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
—------------------------------------------------------
I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something.
Please help.
I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker:
Root access not properly configured or granted.
Superuser Application Status
Installed: SuperSU by Chainfire - version 2.46
System Files Status
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User Account Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
Optional: ADB Shell User Status
Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional: System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
_----------------------
So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible.
Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore.
Made sure no double superuser programs running.
Got rid of Knox.
Tried to custom install Supersu update, says invalid certificate.
I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID.
Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now.
Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix.
PS. If this post is i wrong place please advise where itshould be.
Thanks
S :good:
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
I can't find my phone as one of the packages. I have an Alcatel phone.
root my mobile but didn't get access
rooted my phone micromax a116, all proccess done wel as shown in tutorials. But root checker says that "root access is not properly installed on this device". Please tell me what to do?
Hi,
first of all thanks to everyone that works here, I have been visiting this forums for about 3 years.
I currently have a 5.0.2 with htc sense 6.0
Kernel version 3.4.10-gd7bdf6a [email protected] #1 SMP PREEMPT (this is what it read after attempting root)
To root it, I installed drivers (HTC Sync manager, mini-SDK tools, java), unlocked bootloader as instructed on htcdev.com/bootloader, went to fast boot, installed recovery-clockwork-touch-6.0.4.6-m7ul.img, moved UPDATE-SuperSU-v1.94.zip to my sdcard, and went on recovery to install this zip hoping it would be rooted. After all this I noticed Titanium Backup pro didn't have access to root, downloaded Root Checker Basic by joeykrim and in fact it said "Sorry! Root access is not properly installed on this device." Then I went on my apps drawer and noticed that strangely SuperSU is installed, but when I opened it it reads "There is no SU binary installed, and SuperSU cannot install it. This is a problem!".
After all that I tried downloading Superuser instead Superuser-3.1.3_superuserdownload.com.rar, but my device on recovery couldn't even see the RAR file, meaning on recovery that file didn't even show, so I tried extracting files to a folder of the same name and then compressing it again as a zip file. It could read fine and I attempted installing it again on recovery CWM but the installation started and aborted instantly. So I tried reinstalling SuperSU again, after deleting all cache/data/system/delvik, but again same problem. SuperSU is installed, but the same problem message pops up, and Root Checker still reads the device isn't rooted properly.
Strangely, Busybox installer says my device is rooted but after tapping install it said it failed. Root Check by JRummy Apps says device is rooted too.
Thanks in advance, let me know what other questions you have.
Additional info,
Root Check details reads
BINARY /system/xbin/su
PERMISSIONS rwsr-sr-x (6755)
VERSION 1.93:SUPERSU
ADB ROOT Enabled
Use this zip file. Flash it using whatever recovery you have currently. https://download.chainfire.eu/735/SuperSU
UPDATE 6/19
So I installed CM12 12 or 13 require 23C, 24B, or 35 (TWRP 2.8. has those versions mentioned in the fail error script)
I kept getting the boot error and so I started over and flashed KDZ's in order from 10 to 23c
With the 23c you can use the one click program to root but also have the bootloader that CM12 OR CM13 needs
After root the error code did not show up
After bustbox the error did not show up
I used TWRP manager app to install 4 different TWRPs, all gave a boot code error and would reboot to CM or stock but obviously something was wrong
So then after research I found others that had trouble and used Autorec to solve the issue
Autorec:
http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
UPDATE 6/15 - Bootloader error?
It says:
SECURE BOOTING ERROR!
ERROR 1003
So I updated to 24B and I have CM 12.1 running. I did notice a boot error "error 1003" right before TWRP opened to install the ROM and just before the cyanogenmod boot screen popped up - Is that going to be okay, everything seems to be working fine?
How I got the ROM installed
1.) Flashed 24B using KDZ flash tool and file
2.) Root - Only king root from here worked (click unknown sources, also Google stopped the install so I had to out it in airplane mode and open the apk): http://forum.xda-developers.com/lg-g...3129197/page84
3.) Installed busy box, TWRP, SuperSU asked to update the binary.
4.) Download cm 12.1 files tot the TWRP backup files
5.) Reboot into TWRP recovery
6.) backed up phone so you don’t have to get root again
7.) wipe - factory reset - wipe dalvic and cache again
8.) Installed CM 12.1 and rebooted system
Original issue: Failed ROM flash on 12B and TWRP3.0
See recovery log below
The only thing I can think if now is that I need to use a .tot and not the kdz files to get to 100% stock, I'm not saving the files correctly, or I need an older version of TWRP with 10b and 12b?
I'm on 12B and my wife's is 10b and recieving the same error
I downloaded the zip files from Cyanogen's website and copied them via ESexplorer root to the external and internal SD cards
rooted, busybox, TWRP 3.0 (newest on the list)
I followed their install directions but was unsure how to copy the zip file using adb so I just downloaded them to the phone and copied them into folders using root explorer in esexplorer to get the files into hidden folders including TWRP and BACKUPS folders and a couple others just to try (I think this is my issue, how to I copy them to the root SD card) ESexplorer asked for SuperSU rights though)
opened TWRP via the app and manual through the factory reset/yes routes
backed up everything
wipe, factory reset, wipe dalvic/cache and cache again
I tried to install the zip from external and internal SD cards
The errors are
update process ended with error 7: Error installing zip file '/sdcard/cm12.1-rest of file name here.zip"
update process ended with error 7: Error installing zip file 'external_sd/TWRP/"file"
cyanogen mod says to save to /sdcard or adb push to /sdcard/ so it looks like I am in the right folder based on the error's path
I have also saved the zip files in the EXT SD TWRP/BACKUPS folder which conatin my backup from today. They are not in their own folder just files in the BACKUPS folder
UPDATES:
UPdated to 12B using KDZ flash not the .tot, rooted, busybox, TWRP = No change
Manually opened TWRP using the buttons/factory reset/yes and not rebooted from the app = No change
updated SuperSU = No change
100% battery = No change
log says:
couldn't find any tzdata when looking for localtime!
couldn't find any tzdata when looking for GMT!
couldn't find any tzdata when looking for posixrules!
stewbuntu said:
See recovery log below
The only thing I can think if now is that I need to use a .tot and not the kdz files to get to 100% stock, I'm not saving the files correctly, or I need an older version of TWRP with 10b and 12b?
I'm on 12B and my wife's is 10b and recieving the same error
I downloaded the zip files from Cyanogen's website and copied them via ESexplorer root to the external and internal SD cards
rooted, busybox, TWRP 3.0 (newest on the list)
I followed their install directions but was unsure how to copy the zip file using adb so I just downloaded them to the phone and copied them into folders using root explorer in esexplorer to get the files into hidden folders including TWRP and BACKUPS folders and a couple others just to try (I think this is my issue, how to I copy them to the root SD card) ESexplorer asked for SuperSU rights though)
opened TWRP via the app and manual through the factory reset/yes routes
backed up everything
wipe, factory reset, wipe dalvic/cache and cache again
I tried to install the zip from external and internal SD cards
The errors are
update process ended with error 7: Error installing zip file '/sdcard/cm12.1-rest of file name here.zip"
update process ended with error 7: Error installing zip file 'external_sd/TWRP/"file"
cyanogen mod says to save to /sdcard or adb push to /sdcard/ so it looks like I am in the right folder based on the error's path
I have also saved the zip files in the EXT SD TWRP/BACKUPS folder which conatin my backup from today. They are not in their own folder just files in the BACKUPS folder
UPDATES:
UPdated to 12B using KDZ flash not the .tot, rooted, busybox, TWRP = No change
Manually opened TWRP using the buttons/factory reset/yes and not rebooted from the app = No change
updated SuperSU = No change
100% battery = No change
log says:
couldn't find any tzdata when looking for localtime!
couldn't find any tzdata when looking for GMT!
couldn't find any tzdata when looking for posixrules!
Click to expand...
Click to collapse
If you want to install CM13 you need to be on 24B or 35B for the bootstack.
RedWingsFanEd said:
If you want to install CM13 you need to be on 24B or 35B for the bootstack.
Click to expand...
Click to collapse
I was just trying 12.1 for stability, for now
Should I try and go to 24B with TWRP 3.0 and see if that works?
UPDATE
TWRP 2.8 failed and said that CM12 also wanted the bootloader for 23C or greater. I read somewhere that TWRP 3.0 is the cause of the boot error 1003 when flashing CM so I'll try TWRP 2.8
So I updated and I have CM 12.1 running. I did notice a boot error 1003 right before TWRP opened to install the ROM and just before the CM boot screen popped up - Is that going to be okay? I have been running with no issues for half a day now.
I was able to update SuperSU
How I got the ROM installed
1.) Flashed 24B using KDZ flash tool and file
2.) Root - Only king root from here worked (click unknown sources, also Google stopped the install so I had to put the phone in airplane mode and open the apk): http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197/page84
3.) Installed busy box, TWRP, SuperSU asked to update the binary.
4.) Download CM12 or CM 13 files to the TWRP backup files folder
5.) Reboot into TWRP recovery via app
6.) backed up phone so you don’t have to get root again
7.) wipe - factory reset, wipe dalvic and cache again
8.) Installed Cyanogenmod 12.1 and rebooted system