Hello
I have a problem with my phone. I tried to install a custom recovery (I've failed) and when it reboot it was like on the first time but with one more thing : superuser.apk. The problem is : superuser doesn't work and I can't uninstall it. The phone isn't rooted anymore. I tried with Super One Click Root and with z4root. With SOCR, the software can't install the files required because the phoen doesn't have space left and when I've verified, there is only 60Ko in the system partition of the phone's memory. I don't have rw permissions on the files so I can't delete files which take a lot of memory (it's a zip image of the prime rom which stayed in the file since the first time I tried to install it).
Do you have an idea for me to root the phone or uninstall superuser and delete files ?
Related
Hi guys, I'm new to XDA and I'm sorry if this is in the wrong section or if any thread already exists.
Alright, I own a Samsung Galaxy Tab 10.1v (GT-P7500) and yesterday I set my mind on rooting it. I checked several guides and saw that what almost everyone told was to use Odin3 to be able to use Clockwork mode and root it through flashing.
Well, I downloaded the zip and the recovery and everything seemed to be perfectly fine until, after flashing and booting the tablet I had no root access. Tried several apps for it (from a terminal to a root checker, and yeah, I know I didn't need to do it).
Anyway, after checking a bit I discovered that the su file nor the busybox didn't appear in the root folder (/system/bin o whatever his directory had to be) so I tried to flash it again. Nothing happened so I downloaded some other zips (the first one was like 2MB and the next one I tried was about 300KB), after this the su/busybox files appeared in its location, but when I tried to use the su command in the terminal I got the permission denied message. Used "ls -l /system/bin/su" to see that the permissions were this (if I recall correctly) ---sr-xr-x-.
After tearing my head apart after several hours of investigating and trying stuff I decided to do a factory reset so I could try (I hoped Superuser, su, busybox and all the other files would be erased) to root it again from scratch. Well, my surprise was the one you probably know, the /system files weren't reseted, I still had the Superuser app and all the other files, and su still had the same permissions and whats even more, it was 0KB though I don't know if the first time I tried to root it, it was already 0KB..
Well, this is my story, and if you could throw a bit of light on it I would be grateful.
Thanks in advance
P.S.: Sorry for my bad English
Hi all, i had a problem today morning with my Galaxy S2 (last stock android).
Time ago, I rooted it using phliz touch + supersu mode.
Today, i was having a nandroid backup (using philz as i did in past), when phone crashed.
So i restarted it and i try to delete everything in clockworkmod folder, but i can't remove "blobs" subfolder.
(Total commander show a file named "u95")
I restarted phone in recovery, trying to do a backup again, but it gave error.
Restarted phone again, and opening total commander, it says that my sdcard is read only.
The same happens when i use root explorer.
If i open root explorer, set rw to sdcard, exit and reopen root explorer i see sdcar read only again.
How can i fix that?
Please, help me.
I'm very ignorant about this things.
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
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.
Hello Everyone,
I have an SM-T860 WiFi, with the stock T860XXU3BTJ2 update. I was able to root it with Magisk. When I initially opened Magisk, it needed to reboot to complete the rooting. I then installed a few apps, and got prompted for root. I approved it, and was able to browse root.
Usually I will go for an AOSP rom, but I was considering the idea of just removing the APK's I don't want (Google, Samsung), and replace them with alternatives.
I tried a few different things, but *it appears that* every time I modify the /system/app-priv folder, and I reboot, my Magisk changes to "NA"! For some reason, reflashing the Magisk_modified file I made in Odin doesn't return root to the device.
At one point, I used Material File manager to mount the root directory as read/write, so I could delete the APKs. I assume flashing the CSC file will mean the / mountpoint will mount as read only, moving forward.
I also downloaded and used the debloat Magisk Module. It appeared to complete successfully, but I have the same Magisk problem when I reboot.
Here's how i flash the Odin Image:
1. Downloaded the firmware with Frija (Really amazing app after first trying Sammobile).
2. Modified it on the tablet with Magisk Manager, copied it back off the device.
3. Flashed Device with BL, Modified Magisk AP, and no CSC (without the "HOME" option) (My understanding is this will delete all data on the device).
4. After Odin finishes, I immediately hold Volume + and Bixby. I immediately get to the recovery, and run a factory reset.
5. Go through initial setup
6. Use ADB to install Magisk Manager apk to Device
7. Upon opening Magisk Manager, it doesn't prompt me to reboot and complete installation (like I saw before), it just says "N/A".
I appreciate your help!
edit-- I ran ls -la on / with adb, and got the line below, so I think that confirms we are read only.
drwxr-xr-x 22 root root 4096 2008-12-31 09:00 system
hello,
how did you root it?!
stock T860XXU3BTJ2 for me it dont work?