Related
Question: Is your Superuser app asking for permissions from apps? Mine isn't. On my old rooted Eris, if I ran an app such as Titanium Backup or Root Explorer, I would get a dialog which would ask if I wanted to grant that app root access. This dialog was via the Superuser app. I don't get that now. It seems like any/every app on my phone has su access.
I'm wondering if it's just me or if this is the way the current root exploit works.
DeezNotes said:
Question: Is your Superuser app asking for permissions from apps? Mine isn't. On my old rooted Eris, if I ran an app such as Titanium Backup or Root Explorer, I would get a dialog which would ask if I wanted to grant that app root access. This dialog was via the Superuser app. I don't get that now. It seems like any/every app on my phone has su access.
I'm wondering if it's just me or if this is the way the current root exploit works.
Click to expand...
Click to collapse
It's just you. Try running root explorer or a screen cap program, and verify that you have root access. You may want to use an updated Superuser.apk too, I know the one I'm using (2.3.6.1) asks, (unless I told it not too).
I'm using Superuser 2.3.6.1. When I run Titanium or Root Explorer, everything works without prompting. Now, I'm concerned.
UPDATE: I opened Superuser, went to settings, scrolled to the bottom and updated the su binary. Now, I get prompted when an app needs access. Problem is, when I reboot the su binary is reset. I think this is due to me using the joeykrim root procedure, which uses a version of su that is scripted to be put in place during the boot process. I'm going to take a look at his scripts and change them so I can keep the su binary installed by the Superuser.apk.
Thanks for the info.
Confirmed my issue was due to using the joeykrim method. I backed out his procedure and used Dirrk's method (posted here: http://forum.xda-developers.com/showthread.php?t=779238) and I get a proper Superuser prompt when an application needs access.
I also noticed another flaw in the joeykrim method. Since his procedure was developed for the Epic, he has some incorrect file names in some places.
If you notice in his instructions where he says use playlogos1 instead of playlogos, this is not updated in all of his steps.
To get your boot screen back, you have to change the last line of playlogos1 or playlogosnow (based on whether you did the lag fix or not)
The file that will not show your boot animation will look like this:
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogo-orig
To fix it, change the last line to read:
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogos1-orig
In summary, the playlogos1 file is used to execute other startup scripts. The original playlogos1 file has the boot animation in it. It must be referenced in one of the startup scripts. Since these instructions were used for the Epic, there's a slight typo which keeps the original playlogos1 file from being executed.
Thanks--I came to the forums looking for a solution to the fact that my boot animation was now missing. I tried making your changes but I still can't seem to recover it. Here are what my playlogo scripts look like, keeping in mind I have also installed the lag fix:
playlogos1
Code:
#!/system/bin/sh
sh /system/bin/userinit.sh
playlogosnow
playlogosnow
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogos1-orig
I'll also have a 3rd file called just playlogo (which was very long). Do you know what the issue is? Thanks so much for your help.
theicemonkey said:
Thanks--I came to the forums looking for a solution to the fact that my boot animation was now missing. I tried making your changes but I still can't seem to recover it. Here are what my playlogo scripts look like, keeping in mind I have also installed the lag fix:
playlogos1
Code:
#!/system/bin/sh
sh /system/bin/userinit.sh
playlogosnow
playlogosnow
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogos1-orig
I'll also have a 3rd file called just playlogo (which was very long). Do you know what the issue is? Thanks so much for your help.
Click to expand...
Click to collapse
Judging by what your files look like, things should work. The original file is playlogos1. We never touch the playlogo file from what I can remember, so let's not do anything there.
What I would do is make sure the permissions are straight on all the files listed above (primarily playlogos1). They should be 755 (shown below):
Code:
# cd /system/bin
# ls -l playl*
-rwxr-xr-x root shell 10060 2010-08-12 04:30 playlogo
-rwxr-xr-x root root 106 2010-09-11 18:53 playlogos1
-rwxr-xr-x root root 177 2010-09-11 18:55 playlogos1-lagfix
-rwxr-xr-x root shell 14420 2010-08-12 12:30 playlogos1-orig
-rwxr-xr-x root shell 14204 2010-08-12 04:30 playlpm
#
If all else fails, you can always grab the original file from the system dump off of this link: http://forum.androidcentral.com/fascinate-roms-hacks/32839-fascinate-system-dump.html
DEAR GOD
Well, I'm an idiot.
I tried to take the playlogos1 file from the dump you showed me and copy it to my /system/bin file and, sure enough, I got the boot animation back. Problem is, I didn't think it through (that the edited playlogos1 file pointed to the rest of the modified boot sequence) and then the phone wouldn't boot. It would just loop the animations.
I booted into recovery, did a factory reset, and now I can get to the lockscreen and the very beginning of setup but TWLauncher force closes over and over and over and I'm unable to do anything except pull down the notification bar occasionally. I think this is because I moved some things (like bing, daily briefing, etc.) that TWLauncher wants at the outset, and it doesn't have them. I tried to bluetooth over LauncherPro and run it, but it fails at the last moment.
Does anyone know of a way to get to ADB Shell so that I can fix my mistake? Or if someone had an update.zip I could flash to get back to factory (with all of the system files in place), that would be super! Otherwise, it looks like I'm effed and will need to come up with a good story to tell Verizon...
theicemonkey said:
Well, I'm an idiot.
I tried to take the playlogos1 file from the dump you showed me and copy it to my /system/bin file and, sure enough, I got the boot animation back. Problem is, I didn't think it through (that the edited playlogos1 file pointed to the rest of the modified boot sequence) and then the phone wouldn't boot. It would just loop the animations.
I booted into recovery, did a factory reset, and now I can get to the lockscreen and the very beginning of setup but TWLauncher force closes over and over and over and I'm unable to do anything except pull down the notification bar occasionally. I think this is because I moved some things (like bing, daily briefing, etc.) that TWLauncher wants at the outset, and it doesn't have them. I tried to bluetooth over LauncherPro and run it, but it fails at the last moment.
Does anyone know of a way to get to ADB Shell so that I can fix my mistake? Or if someone had an update.zip I could flash to get back to factory (with all of the system files in place), that would be super! Otherwise, it looks like I'm effed and will need to come up with a good story to tell Verizon...
Click to expand...
Click to collapse
Sorry you're having issues. Bad news is, you can't flash any zip updates because we don't have a custom recovery re our phones yet. However, what you should be able to do is use adb to push the apps from /system/app from the system dump. That is.. if you can get adb to work? If it can work from recovery, that should save you.
Good luck.
I have an unlocked+rooted CM7 Atrix which was working nicely this morning.
I was playing around and decided to install Titanium Backup. I also read somewhere that it needs BusyBox to work better so I decided to install that too.
i tried installing BusyBox in /system/xbin and it gave me an error about BusyBox being already installed
now for some reason I can't seem to do anything in a terminal emulator or adb except "cd" and "su" (Root checker returns success)
I'm getting a "permissin denied" error with basic commands like ls, cp, mv, mount, chmod
any suggestions?
thanks
this is just a shot in the dark but have you tried to fix permissions in cwm... its fixed odd things like that for me sometimes... also cant hurt to clear dalvik cache too jic... that has also helped at times. use a program like root explorer to check if busybox is actually there as well. other then that i have to shrug my shoulders lol
viperlox said:
this is just a shot in the dark but have you tried to fix permissions in cwm... its fixed odd things like that for me sometimes... also cant hurt to clear dalvik cache too jic... that has also helped at times. use a program like root explorer to check if busybox is actually there as well. other then that i have to shrug my shoulders lol
Click to expand...
Click to collapse
actually I was thinking about doing the fix permissions thing last night but I couldn't remember where I saw the option to do that
Anyways, I did try it just now as well as clearing the dalvik cache and they didn't seem to help.
I also tried root explorer last night (bought it just for this purpose) but it doesn't seem to be pulling up any data, it just hangs at a black screen when I open it and then it force closes.
I have a guess though but I have no way of confirming this since ls and explorers doesn't seem to work.
I used to have "su" in /system/bin as well as a couple of self-written scripts but they don't seem to be there anymore. when I try "/system/bin/su" or any of my scripts it give me the "not found" message
While poking around I then realized that there is a "su" in xbin (this is the one that runs when su is called without it's direct path). I'm guessing this works since root checking detects it.
So, I'm thinking maybe my /system/bin got wiped out when the new stuff (eg su) in xbin got created? Then maybe I don't have proper access to xbin? Like maybe when I installed busy box, it wiped out some of my stuff in /bin and copied/created then in /xbin and failed to set permissions?
Does this sound possible? Also, would it be possible to reflash /bin and /xbin to whatever came with CM7 maybe?
Thanks
johnusesandroid said:
I have an unlocked+rooted CM7 Atrix which was working nicely this morning.
I was playing around and decided to install Titanium Backup. I also read somewhere that it needs BusyBox to work better so I decided to install that too.
i tried installing BusyBox in /system/xbin and it gave me an error about BusyBox being already installed
now for some reason I can't seem to do anything in a terminal emulator or adb except "cd" and "su" (Root checker returns success)
I'm getting a "permissin denied" error with basic commands like ls, cp, mv, mount, chmod
any suggestions?
thanks
Click to expand...
Click to collapse
Just so you know busybox is included in atrix roms. There was/is no need to install it again.
You could try to push the folders you want from a cm7 zip file. Or you could just reflash cm7 without wiping data/factory resetting.
_Dennis_ said:
Just so you know busybox is included in atrix roms. There was/is no need to install it again.
You could try to push the folders you want from a cm7 zip file. Or you could just reflash cm7 without wiping data/factory resetting.
Click to expand...
Click to collapse
I ended up reflashing CM7 thanks for the tip
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
nasenstueber said:
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
Click to expand...
Click to collapse
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
mauricio.valladolid said:
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
Click to expand...
Click to collapse
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
nasenstueber said:
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
Click to expand...
Click to collapse
why dont you just install ext4 recovery and flash supersu.zip?
I really dont get it why are you trying to do it the hard way
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?
Hello, im having a couple of problems regarding my filesystem as well as the app supersu and its binary file.
To start, i rooted with kingroot and switched to supersu using terminal emulator commands. There are still kingroot files in my xbin which i will attatch a picture showing the contents of my xbin folder in attatchments (i also have .tmpsu in xbin) please ask if you need more pictures or information of files located in my directories.
The problems i need help with is:
1. I cannot mount /system or any foler in that directory as r/w, i feel that there is a file located somewhere that is preventing me from mounting /system as r/w.
2. I cannot update the su binary, i have tried normal and twrp modes neither work. Ive also tried flashing the UPDATE-supersu-2.78.zip in twrp and that doesnt work either. It says that it installed but nothing changes once i boot back into system, i feel that me not being able to mount /system as r/w is preventing me from updating the su binary.
I need help on how to regain conrtol of my /system and how to update the su binary. Any help? Thank you
Some specs of phone:
Android 5.1
Cpu model - AArch64 processor rev 4
Kernel version - 3.10.65+
Model - blu vivo xl
icy201 said:
Hello, im having a couple of problems regarding my filesystem as well as the app supersu and its binary file.
To start, i rooted with kingroot and switched to supersu using terminal emulator commands. There are still kingroot files in my xbin which i will attatch a picture showing the contents of my xbin folder in attatchments (i also have .tmpsu in xbin) please ask if you need more pictures or information of files located in my directories.
The problems i need help with is:
1. I cannot mount /system or any foler in that directory as r/w, i feel that there is a file located somewhere that is preventing me from mounting /system as r/w.
2. I cannot update the su binary, i have tried normal and twrp modes neither work. Ive also tried flashing the UPDATE-supersu-2.78.zip in twrp and that doesnt work either. It says that it installed but nothing changes once i boot back into system, i feel that me not being able to mount /system as r/w is preventing me from updating the su binary.
I need help on how to regain conrtol of my /system and how to update the su binary. Any help? Thank you
Some specs of phone:
Android 5.1
Cpu model - AArch64 processor rev 4
Kernel version - 3.10.65+
Model - blu vivo xl
Click to expand...
Click to collapse
download root checker from the play store and make sure that u have root access on your device
messi2050 said:
download root checker from the play store and make sure that u have root access on your device
Click to expand...
Click to collapse
It says i have properly installed root access. Something fishy is going on with my root and my system.
icy201 said:
It says i have properly installed root access. Something fishy is going on with my root and my system.
Click to expand...
Click to collapse
then u can try to completely uninstall root from inside super su/king root apps and then reinstall it
messi2050 said:
then u can try to completely uninstall root from inside super su/king root apps and then reinstall it
Click to expand...
Click to collapse
I did try that too, it took around 15-20 minutes to uninstall then when i rebooted the app was gone but my device still had root. I did get it to uninstall root 1 time then i went and flashed the zip file and the same problem occured again. Maybe kingroot just f-ed up my device so root will never work properly again? Maybe a virus? Idk whats going on with it.
icy201 said:
I did try that too, it took around 15-20 minutes to uninstall then when i rebooted the app was gone but my device still had root. I did get it to uninstall root 1 time then i went and flashed the zip file and the same problem occured again. Maybe kingroot just f-ed up my device so root will never work properly again? Maybe a virus? Idk whats going on with it.
Click to expand...
Click to collapse
Your device does not have twrp/cwm port ?
It does, i have twrp(touch) 3.0 for blu vivo xl. Thats the only way i got my device unrooted one time. What i had to do i had to boot into recovery, mount /system, reboot into system then root explorer would allow me to mount /system as r/w but i believe theres a script or something somewhere that is locking the /system into read only mode cause after a short period of time (around 5 minutes or so) i can no longer modify or delete anything in that folder even though it still says its in r/w and if i close root explorer and reopen it it shows that its back in read only mode even though i didnt change it back to that.
Edit: if i mount /system in twrp and boot into system when i boot back into twrp system is not mounted anymore, idk if its supposed to do that or not.
These are the only possible solutions ive been able to find that do kinda make sense.
"It's because you need a boot.img with r.o secure=0 in the build prop" i went and looked and my file says r.o secure=1 that would explain why my system will not mount as r/w.
Another post i found said -
"I've found the source of the problem asking in the MIUI forums, the boot image will not accept a modified /system.
You have to use the adb interface: adb devices then adb disable-verity.
Disclaimer: I'm not responsible for any damage caused by these operations."
The second solution seems more reasonable and alot easier to do. My question now is: will one or both of these solutions possibly fix both my problems? And the second solution disabling verify should that be okay to do without messing up my device? I do have that recovery i could flash but dont wanna do anything that might make the phone not boot into recovery.
icy201 said:
It does, i have twrp(touch) 3.0 for blu vivo xl. Thats the only way i got my device unrooted one time. What i had to do i had to boot into recovery, mount /system, reboot into system then root explorer would allow me to mount /system as r/w but i believe theres a script or something somewhere that is locking the /system into read only mode cause after a short period of time (around 5 minutes or so) i can no longer modify or delete anything in that folder even though it still says its in r/w and if i close root explorer and reopen it it shows that its back in read only mode even though i didnt change it back to that.
Edit: if i mount /system in twrp and boot into system when i boot back into twrp system is not mounted anymore, idk if its supposed to do that or not.
Click to expand...
Click to collapse
Yes that's normal , your problem is because of a buggy root
messi2050 said:
Yes that's normal , your problem is because of a buggy root
Click to expand...
Click to collapse
I just remembered something. I think i know what bugged it. I was trying to do an ota update for my device and it wouldnt let me. I found another app by chainfire called flashfire. I tried to flash the ota update and i had the option "inject supersu" enabled even though i already had supersu installed and everything else i needed for root. I guess doing that messed up all my su files ect.. But how do i fix it? I cant uninstall root cause my /system folder is locked into r/o. If i press full unroot in supersu it will remove the app (although it takes a while!) but all the files needed for root stay.
Guess there just no fixing this phone. Someone really hacked it good i guess, problem is still there and nothing can fix it...
Update - thread can be closed
Problem fixed, to fix the problems i was having i had to download the stock system files for my device and flash them, after that just installed the latest supersu 2.78 zip and remount problem is fixed.