I have a clockworkmod file in the root of sdcard. I can see it in ES File Explorer but I cannot see it when I connect the phone to my computer. I use clockworkmod recovery only by booting into it when I need to...not by flashing it.
Although it dissappears when I delete it in ES File Explorer, if I refresh the screen it is still there. Anyone know what this file is exactly and how to get rid of it for good?
I tried another app called File Manager by Gira.me. It shows this file as ...
Path: /storage/emulated/0/clockworkmod
Type: */*
Size: 0 B
Last modified: Unknown
Permissions: ---
MD5: Unknown
When I try to delete it it says "Not enough permissions". There must be some way to delete this file.
Boot cwm, adb shell, rm the file
beekay201 said:
Boot cwm, adb shell, rm the file
Click to expand...
Click to collapse
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
xda6969 said:
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
Click to expand...
Click to collapse
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Aerowinder said:
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Click to expand...
Click to collapse
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
xda6969 said:
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
Click to expand...
Click to collapse
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Aerowinder said:
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Click to expand...
Click to collapse
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
xda6969 said:
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
Click to expand...
Click to collapse
Yes, you need to be rooted for restorecon command (su). A lot of people had troubles like yours when they moved to Lollipop (me too). Now that the recoveries have been updated, it's no longer an issue for most. You may still need to run the command, though. I suppose if you did a full wipe in stock recovery, it would fix the problem.
Your question about restoring app data with nandroid is vague and could be answered in a few ways. With your issue, the data partition is actually where the problem is, so I wouldn't recommend restoring the partition.
Instead, you might use Titanium Backup or something similar to back up only app data. But you need root for that.
Easiest solution is to root, fix issue, then, if you really want to, unroot. Don't need to wipe anything.
Related
Now that the recovery has been made sticky on the later versions of the One-click-root, how would I go about restoring the original stock Recovery if I ever wanted to?
I'd rather prefer it not to be sticky, or at least the script for restoring it to be renamed rather than deleted, so I can run it manually later to restore the original recovery if needed.
I haven't run the run.bat script yet, and would appreciate help in the process to backup the recovery and be in a good situation for allowing full roll back before I do the rooting.
ggggg1 said:
Now that the recovery has been made sticky on the later versions of the One-click-root, how would I go about restoring the original stock Recovery if I ever wanted to?
I'd rather prefer it not to be sticky, or at least the script for restoring it to be renamed rather than deleted, so I can run it manually later to restore the original recovery if needed.
I haven't run the run.bat script yet, and would appreciate help in the process to backup the recovery and be in a good situation for allowing full roll back before I do the rooting.
Click to expand...
Click to collapse
Assuming you're using this: http://forum.xda-developers.com/showthread.php?t=1138755
Just extract root.zip, go into the updater-script and remove the line:
delete("/system/etc/install-recovery.sh");
Save the file, repack the zip and continue (you can turn off signature verification in CWM)
You can easily rename it using adb, remounting /system manually, or via root explorer or a similar app once rooted.
Excellent, thanks; I'd seen that delete of the .sh , but wasn't sure if removing it would allow the rest of the bat or it would break further down expecting it to have been removed and a reboot to go back to CW.
Thanks!
I cant go to recovery through Rom Manager for some reason. It works manualy( power+volume) but when I click it from the app it freezes, and shows an exclamation point triangle
have you tried to reinstall the app?
Wich CWM do you have?
thy the above post; if that doesn't work, go into recovery manually and fix permissions
that must be why
I was following this video http://www.youtube.com/watch?v=PVyGw6vycFo
and it said I had to wipe my data which I did, and maybe CWM was removed?
Ill try to flash CWM and see what happens.
Worked! thanks
In wich way?
Have you reinstall Rom manager App or reflah CWM Recovery?
actually, theres been a trend going on here....
I went on recovery to check if its working after I flashed it and it worked, after turning it off and removing the usb out of my computer I tried again and it didnt work.
Any ideas why?
Edit: when I had ROM manager I already tried to Flash CWM there if you're wondering.
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Harbb said:
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Click to expand...
Click to collapse
where can I find /etc/install-recovery.sh and what do you mean by file explorer with root capability?
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Harbb said:
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Click to expand...
Click to collapse
fairly new to android so I have no clue what you are talking about sorry... can you give me some steps on how to do that. again I apologize, Im still new
Download this from the market, i'm sure you'll figure it out
quick unrelated question: I tried to apply the ROM and it didnt continue, it said it was aborted or something
Hello,
I am having a minor problem, I am a newbie to rooting and things a like.
I've been trying to setup cwm recovery and I go to stock recovery and I select reinstall packages,
it will work for a second and then it will say "Whole signature failure: Installation aborted"
And then it will automattically reboot. Any help will be appreciated!
ImShiney said:
Hello,
I am having a minor problem, I am a newbie to rooting and things a like.
I've been trying to setup cwm recovery and I go to stock recovery and I select reinstall packages,
it will work for a second and then it will say "Whole signature failure: Installation aborted"
And then it will automattically reboot. Any help will be appreciated!
Click to expand...
Click to collapse
Two things, you must:
1. Have modded recovery binary
and
2. Make sure you are using the correct CWM 3.0.2.8
EDIT:
http://www.mediafire.com/?mex4qna8rr3urck Modded Recovery
http://www.mediafire.com/?jvtpra5ashdmctn CWM
Make sure you change CWMx.x.x.x to update.zip and the modded recovery must be placed in /system/bin
Backup current recovery file and make sure you overwrite with this, using a file explorer that allows you to get to root access.
shadowscott said:
Two things, you must:
Backup current recovery file and make sure you overwrite with this, using a file explorer that allows you to get to root access.
Click to expand...
Click to collapse
One thing to remember about this is that you MUST mount the internal storage as read/write. Ghost Commander (free on Google Play) lets you do this. You have to enable root explorer in its menus, and then go to where your stock recovery is and mount the volume as read/write. Then, paste the modified recovery in the directory and overwrite the stock one. Now, you should be able to get into CWM.
First things first: did you successfully root your phone?
ged92781 said:
One thing to remember about this is that you MUST mount the internal storage as read/write. Ghost Commander (free on Google Play) lets you do this. You have to enable root explorer in its menus, and then go to where your stock recovery is and mount the volume as read/write. Then, paste the modified recovery in the directory and overwrite the stock one. Now, you should be able to get into CWM.
Click to expand...
Click to collapse
Sir, thank you so much! It works now and I can finally flash mods thank you.
Just make sure you wipe everything an go to advance menu an wipe all that
an make sure you nandroid right after helps out a lot
Sent from my SGH-T839 using xda app-developers app
HEY!!
I wanted to change my LCD density on the build.prop file with build.prop Editor. It worked fine.
When I tried to copy the backup back from sdcard and replace the edited build.prop with the stock one, after reboot all I can see is the OnePlus logo with the "POWERED BY ANDROID" text.
I can access TWRP, but when I check the /system directory, there is no build.prop file. So I move it again from sdcard to the /system directory. It stays there until I reboot the phone.
I did EVERYTHING! chmod, mounting, moving using adb shell, and the file just deletes itself when I reboot the phone!!
I don't want to make a factory reset since I don't have a latest backup.
Please don't ask me why did I change the LCD density. I just wanted to check something.
PLEASE HELP!!
Machlev said:
HEY!!
I wanted to change my LCD density on the build.prop file with build.prop Editor. It worked fine.
When I tried to copy the backup back from sdcard and replace the edited build.prop with the stock one, after reboot all I can see is the OnePlus logo with the "POWERED BY ANDROID" text.
I can access TWRP, but when I check the /system directory, there is no build.prop file. So I move it again from sdcard to the /system directory. It stays there until I reboot the phone.
I did EVERYTHING! chmod, mounting, moving using adb shell, and the file just deletes itself when I reboot the phone!!
I don't want to make a factory reset since I don't have a latest backup.
Please don't ask me why did I change the LCD density. I just wanted to check something.
PLEASE HELP!!
Click to expand...
Click to collapse
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Setting.Out said:
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Click to expand...
Click to collapse
no MD5 file found while installing via TWRP. Should I wipe /system?
Setting.Out said:
Reflash your ROM... Don't wipe the data partition and all will be as it was before.
Sent from my OnePlus ONE
Click to expand...
Click to collapse
I wiped system and pushed an md5 file. Still fails with no reason.
I use this ROM -
https://cyngn.com/products/oneplusone/
(On the bottom)
What error are you getting?.. You could try another download (that one may be corrupt) or CM11 ROM, you should still be able to keep your app data as long as you don't wipe that partition.. You only need to wipe system/dalvik/cache..
Sent from my OnePlus ONE
Are you mounting /system with TWRP before doing that?
Also, dont move the file, try cp which works better with crosslink devices
And try chmod 755 /system/build.prop with adb while in recovery and check the build.prop isnt edited in Windows so EOL is Windows-like, then use Notepad++ to change to UNIX-type
easy, you copy pasted so permissions are not the same as the original
reflash system or rom
Sent from my A0001 using XDA Free mobile app
Yep. Permissions should be rw-r-r (or 644). If you don't know what you're doing don't mess around with system files.
Transmitted via Bacon
Hi
Despite several attempts with different file managers and TWRP versions I can't delete my TWRP backups. The only solutions I have is through the recovery mode or a terminal command (rm -rf /sdcard/...).
No issue to delete folders from other directories though.
Is this the same with new backups?
rootSU said:
Is this the same with new backups?
Click to expand...
Click to collapse
Yep
Primokorn said:
Yep
Click to expand...
Click to collapse
odd. i use root explorer, open twrps file, select backups, long press on the backup i want to delete, then press delete(and its gets deleted). what file explorer do you use?
Permissions look right.
Maybe TWRP is doing something funky. For example, if you bacakup your entire /sdcard via adb in recovery then push it back, you won't be able to make changes on /sdcard to any directory. Maybe TWRP is doing something when it backs up. Maybe try a few different versions of it?
rootSU said:
Permissions look right.
Maybe TWRP is doing something funky. For example, if you bacakup your entire /sdcard via adb in recovery then push it back, you won't be able to make changes on /sdcard to any directory. Maybe TWRP is doing something when it backs up. Maybe try a few different versions of it?
Click to expand...
Click to collapse
last night, i deleted my old backup and made a new one. yes, physically deleted using root explorer before i made a new backup.
simms22 said:
last night, i deleted my old backup and made a new one. yes, physically deleted using root explorer before i made a new backup.
Click to expand...
Click to collapse
I mean for @Primokorn not in general
Sent from my Nexus 5 using Tapatalk
@Primokorn try root explorer
I tried with root explorer, solid explorer and ES file. Nothing works with these apps.
Actually I already had this issue with old TWRP versions.
I manage my backups from the recovery mode now but that's really odd...
Maybe doing a new fastboot flash could fix it. Last time I had to use Flashify to upgrade because I didn't have a PC.
Then I'll try with adb if needed.
If all else fails, you could get what you want off the device and format the internal SD. Could be messed up.
KJ said:
If all else fails, you could get what you want off the device and format the internal SD. Could be messed up.
Click to expand...
Click to collapse
Yep. Better yet, flash a userdata.img I reckon
Problem solved after flashing userdata.img. Thanks guys.
I had tbis problem too after flashing NetHunter. I fixed it by deleting the directory using the file manager in TWRP
iliass01 said:
I had tbis problem too after flashing NetHunter. I fixed it by deleting the directory using the file manager in TWRP
Click to expand...
Click to collapse
It's too late for me to try but I keep this in mind. I took the opportunity to clean up my internal memory lol
BTW due to this issue ADB didn't work while being into recovery mode. Everything is fixed now.