This is the account of my foolishness and I advice everyone not to follow it.:::
1.installed Linux installer std and complete Linux installer from play store.
2.when the 2nd app failed to unmount and GUI crashed showing some errors with busybox, followed 3rd step.
3. found the embedded busybox from 1st app n directly placed it in /system /xbin
4. the original busybox is gone n everything is fine but got too many errors in reading root directory of phone. None of the file manager is showing me root.
5. I'm suspecting that it has done something wrong with my cwm recovery as well for which I can't take a chance of bricking my phone.
6. NOW I need kind advice of u ppl on how to confirm the presence of recovery.img or whatever it should be to recover my cwm backed up data.
boot into recovery, if recovery do not boot then pull battery and start the mobile it will start normally, download busybox installer from play store (the one from stephen)
install busybox through the app(busybox problem will be solved)
download tass recovery cwm.tar file and flash with odin you will get cwm recovery back
did it
I've already tried busybox installers. non of them worked cause the whole root directory is unreadable to any of my apps except diskusage n similar things those show memory occupied.
then you should flash firmware and root again
Superuser
maybe update superuser binary?
solved
chmod 777 path name n got busybox 1.12
You lost root access because there is no busybox. Reflash the ROM. Easy way out.
nothing lost at all just replaced.
as I've stated the command above u, it was just a busybox w/0 permissions. I was getting permission denied.
thanks to Gael péron for his Help.
hi all,
I was running my TX with advanced kernel v4, rooted:
http://forum.xda-developers.com/showthread.php?t=1922925
yesterday i installed Miui Security from here:
http://forum.xda-developers.com/showthread.php?t=1663222
Then the root is gone. I checked that /system/bin/su and /system/xbin/su are still there but they are inter-linking with symbolic link when i view them with root explorer.
fixes tried:
When i use ADB push trying to replace them, it said "too many symbolic links encountered"
I cannot remove both file as i cannot su in ADB shell.
I booted into CWM recovery but ADB is not enabled in CWM.
I reflashed the flashable zip in CWM to gain root access with no error message prompted, but after reboot into system the SU files are still the same
I reflashed the kernel with flashtools and fastboot, still no change applied to the phone.
Any idea?
finally got it fixed...
I rewrite the updater-script in the CWM flashable zip for root package to force remove both /system/bin/su and /system/xbin/su and rewrite them back.
Thanks for watching...
I've the same problem
Hi guys,
I've the same problem.
I've flashed my Xperia T with MIUI-3.11.22 rom.
I've activated the root permission on Security tab, but my phone doesn't give me the root access (I've tried to install adbd insecure and BusyBox but the result is "problem with root access".
Some ideas?
Thx
Just got HTC One launch day.
Immediately began work on rooting the phone. Installed TWRP and got root access for the most part, but found that this did not give rw access to the system partition.
Found viperboy's post regarding this issue. When I tried to flash the zip file "Sprint_One_Root_Disable_System_RW_Protection.zip" the phone rebooted. After, SuperSU was no longer installed nor was su for root access. TWRP is now no longer able to flash anything at all. The phone still works fine but I seem to be back to ground zero.
Just hoping someone else has encountered this.
- Update -
Upon further exploring I found that all the files were pushed to the android system and that the su file still exists in /system/xbin/, but There is no longer permission to run said command. I tried manually re-pushing all the files but no change.
It seems if anything (even TWRP) tries to access the system partition the phone reboots.
Hello!
I have a problem that when ever I try to mount system as R/W the phone reboots automatically
The root works great for apps but I can't mount system as writable once I try to do that the device reboots it self
My Device Information is as following:
-C5303
-Locked Bootloader
-Firmware:12.0.A.2.254
-Rooted by Doomlord's toolkit
Try this fix
Thanks man that worked!
I've been trying for sometime now to install a custom rom (CM11 or anything else for that matter) on my Atrix HD. I got as far a unlocking my boot loader so now every time I reboot, I get a scary warning message saying, my phone has been tampered with.
I've made several attempts to install CWM and even though it seems to install, if I try to boot my phone by holding the power and volume down buttons at the same time, it seems to do nothing, or it will just boot normally. I did try to hold down the power and volume up and volume down buttons and that leads to a menu. One of the options was recovery. I selected that, but then a display of android robot with a red triangle.
Can anyone give me some tips on what I'm doing wrong. I'm a programmer, but I have no experience with android, so you can stay technical but not too "android specific" technical.
Thanks,
Mark
Are you installing it via fastboot? Once you flash recovery, do not allow the phone the reboot. Try and boot into recovery.
If you still can boot into cwm, boot the phone, install Root Explorer, and rename recovery.sh to recovery.sh.bak, boot to fastboot, install cwm, and boot into cwm.
audit13 said:
Are you installing it via fastboot? Once you flash recovery, do not allow the phone the reboot. Try and boot into recovery.
If you still can boot into cwm, boot the phone, install Root Explorer, and rename recovery.sh to recovery.sh.bak, boot to fastboot, install cwm, and boot into cwm.
Click to expand...
Click to collapse
These are the commands I used.
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
Where recovery.img was the CWM one.
Based on another thread, I attempted to rename ~/system/etc/install_recovery.sh, but even though I'm rooted, ES File Explorer not Root File Explore is able to rename that file.
Any help would be appreciated.
Thanks,
Mark
After renaming the file, stock recovery still comse up?
Sorry, there was a typo. I was NOT able to rename the file.
Use root explorer to do it. That's what I did.
audit13 said:
Use root explorer to do it. That's what I did.
Click to expand...
Click to collapse
I had tried that.
I had installed
ES File Explorer
Root File Explorer
Root File Manager Explorer
All seemed to either give an error or just not change the name. Is there a trick? I'm pretty sure my phone is rooted since I am prompted to ask permission to do these things. I think if I can get past this the renaming issue, I may actually be able to install a new rom. Can you help?
Thanks,
Mark
Did you change the permission in root explorer to r/w from r/o?
Can you be more specific about "root explorer" which app is it. I've used a couple of root file explorers and none of them can seem to rename /system/etc/install-recovery.sh.
I tried to use Root File Manager to change the permissions on that file to have write permissions. The problem is that it says it does, but then when I look again, it's unchecked.
I checked the /system/etc folder and it has write permissions for "owner". I tried to create a test folder in it. It said it was granted permission, but in the end, the test folder was not created.
Maybe my phone is not rooted properly?
I'm not sure at which point in the rooting process I got this, but I have an app named "#SuperSU". If I open it and check it's logs, I can now see an error message saying "SuperSU Pro is required for this feature". Did I screw up with rooting? Should I use something else. Any help to remedy this would be greatly appreciated.
Thanks,
Mark
markdemich said:
Can you be more specific about "root explorer" which app is it. I've used a couple of root file explorers and none of them can seem to rename /system/etc/install-recovery.sh.
I tried to use Root File Manager to change the permissions on that file to have write permissions. The problem is that it says it does, but then when I look again, it's unchecked.
I checked the /system/etc folder and it has write permissions for "owner". I tried to create a test folder in it. It said it was granted permission, but in the end, the test folder was not created.
Maybe my phone is not rooted properly?
I'm not sure at which point in the rooting process I got this, but I have an app named "#SuperSU". If I open it and check it's logs, I can now see an error message saying "SuperSU Pro is required for this feature". Did I screw up with rooting? Should I use something else. Any help to remedy this would be greatly appreciated.
Thanks,
Mark
Click to expand...
Click to collapse
I upgraded to SuperSU Pro. It was only $2.50. Now the log says, "Unable to chmod /system/etc/install-recovery.sh: Read-only file system"
This happened when trying to give write permissions to that file. Am I doing something wrong?
if your adb is setup and working try using this command in adb 'adb reboot recovery' and see if the phones boots to little android with its heart open given a excalmation mark there press all three buttons at the same time and recovery should open
mega_man said:
if your adb is setup and working try using this command in adb 'adb reboot recovery' and see if the phones boots to little android with its heart open given a excalmation mark there press all three buttons at the same time and recovery should open
Click to expand...
Click to collapse
I did that and when the screen you described displayed, pressed the power, and center of the volume up and down rocker switch so I can get but up and down. After a few seconds the screen went blank and I let go. The phone then just booted normally without going into recovery.
markdemich said:
I upgraded to SuperSU Pro. It was only $2.50. Now the log says, "Unable to chmod /system/etc/install-recovery.sh: Read-only file system"
This happened when trying to give write permissions to that file. Am I doing something wrong?
Click to expand...
Click to collapse
Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
audit13 said:
Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
Click to expand...
Click to collapse
Thanks. I purchased that app and when I tried to set the permissions of the file it prompted to mount the volume with write permissions. Once it did that, everything else worked.
Thanks again,
Mark