Hello,
Does anyone know how create a very simple "updater.zip" file that does nothing except run the "set_perm_recursive" function and set the "/storage/sdcard0/DCIM" folder and all files/folders under it to 777?
I recently screwed up my wife's phone trying to install an app, and didn't have a backup. Now it is stuck on the bootup image screen and won't finish booting up. I am trying to download her photos.
I connected using ADB pull, but since I don't have root on the phone... I don't have permissions to access the /storage/sdcard0/DCIM folder.
So I thought it might be possible to create a simple "updater.zip" script that I can run from the recovery screen, which would give world read/write permissions to the /storage/sdcard0/DCIM folder. Then I can use ADB pull to get a copy of all her pictures to my computer.
Thanks for any help!
Related
I have Root Explorer installed and it says that it has root access and that the mount is read/write yet I am unable to permanently delete or add files to the root/system directory.
I was hoping to replace the current system/media/video/shutdown directory with one of my own and add a bootanimation.zip file to system/media but although the delete/copy/move commands execute without error, no changes actually occur.
I'm so frustrated and have no idea what I'm doing wrong. Any insight will be greatly appreciated.
Thanks
I had the same problem...ended up downloading su file manager. Works perfectly for deleting stubborn system apps.
Sent from my SGH-T959 using XDA App
Have you tried pressing the Mount R/O button on the top right corner and then trying again?
ok so today i tried to use a new boot animation zip and at first i tried to do it through an explorer but that didnt work as astro didnt let me paste the zip file so instead i went the adb route thought i didnt know how to use it.
i installed the files from here: http://sites.google.com/site/androidsamurai/Home/adb-for-dummies-1 and opened cmd, i used cd to get to the directory of my adb then i used adb devices to see if my phone was recognized which it was. then i used adb push bootanimation.zip /data/local and it said it copied since it gave me the speed stats, the file size and the time it took. i used astro to look inside the folder but it was empty. i then proceeded to do a few random things like remount and such and repush and the zip would just not appear in the /data/local folder. i then tried adb shell bootanimation just for kicks and it seemed to work, though i didnt know how to stop the animation besides closing my cmd. after that i tried to reboot and it got stuck at the bootanimation so then i used the 1.8.1 update and reinstalled it and i got past boot loop and for some reason the boot animation is the one i tried to install (the stock dell one that is in the themes forum) but the folder still doesnt exist in /data/local.
like i said im an adb noob, so please guide me through the entire proper way to push a bootanimation to my phone and to figure out where i pushed the previous to since it seems to be somewhere but i tried using astro search but cant find it. any help would be appreciated, thanks!
I'm not super talented at ADB either, but i believe that you should copy the boot animation zip into the same folder as ADB on your computer and then run this:
adb push bootanimation.zip /data/local
Also, there is a file manager called Root Explorer, you should use that instead of Astro because astro doesn't allow you to go into some of the system level directories (exactly what your dealing with in this case) but Root Explorer does. That's probably why you can't find what you flashed before.
Hope this helps
- pat
yeah apparently it seems that astro cant view some root files/folders
copy and paste with root explorer is easiest - like you though I am teaching myself how to use adb - get adb wireless btw - its cool if you dont have your cable to hand
I've messed with some of my files on my phone through ES File manager, and I kept getting errors with a specific folder, I then realized that, it's only happening with the folder I created while pushing a file through adb. ESFM has root permissions enabled, but I could not find where to view the permissions for a folder, only files. I also managed to change the stuff in the folder while in recovery. Do I need to set the permissions for the folder through adb right after i create it, or is it a bug somewhere with the ROM/device, or just a random error? If someone could provide an explanation it would be nice.
Viper 1.2.0
s-off
ML417 said:
I've messed with some of my files on my phone through ES File manager, and I kept getting errors with a specific folder, I then realized that, it's only happening with the folder I created while pushing a file through adb. ESFM has root permissions enabled, but I could not find where to view the permissions for a folder, only files. I also managed to change the stuff in the folder while in recovery. Do I need to set the permissions for the folder through adb right after i create it, or is it a bug somewhere with the ROM/device, or just a random error? If someone could provide an explanation it would be nice.
Viper 1.2.0
s-off
Click to expand...
Click to collapse
See if you can duplicate the error while pulling a logcat. That will help out in solving your problem.
if you dont wanna do that just adb remount and chmod the folder either through adb or adb shell access then restart phone
It's specific to only the folder i created through adb. I'm wondering if anyone else experienced it, or if it is only on my phone
what type of folder and either way you should be able to just adb shell then su then chmod /path to folder
t1gartist said:
what type of folder and either way you should be able to just adb shell then su then chmod /path to folder
Click to expand...
Click to collapse
I created the folder on the /sdcard while pushing a file from my computer. The folder was still accessable, I just wasn't able to copy anything into it/edit it. What permissions would be given to a folder like that if i didn't specify them?
you should have been able to read and write by default all of mine are... erm.... delete the folder and create it via root browser or what ever explorer you have and you should be able to long press and access permissions
Using a Blu life x2 rooted TWRP and using a custom rom called Drax from blox2.
Having a heck of a time getting access to the root system directory. I can browse it just fine via Root Explorer app. I can see all the notification sounds and ringtones that are default. (im ultimately trying to put some new notifications/ringtones directly on the internal storage vs installing something like zedge to manage ringtones (and trying to learn as i go).
Using ADB and fastboot im able to copy files. at least i thought. Booted into TWRP, i can see my device via "adb devices" I try to copy the first time and it fails as it doesnt see the directly (which is odd to me because its clearly there, i can navigated it when booted into android and browsing via Root Explorer. I then see that adb created a directly, i try again and it says it copied. As you can see on the screen shot.
since i cant submit a link yet.... drive.google.com/open?id=0B1halGed5ltCMVY0VzduRk5kTHM
So i think im golden, i go into Android try to change the notification and .. bubkiss. Nothing. I then try to see the file in android via root explorer and its not there.
I think i have a permissions issue as i've tried copying files directly in android using Root Explorer and I get operation failed or permissions complaints.
Any insights on this?
Simplegreen99 said:
Using a Blu life x2 rooted TWRP and using a custom rom called Drax from blox2.
Having a heck of a time getting access to the root system directory. I can browse it just fine via Root Explorer app. I can see all the notification sounds and ringtones that are default. (im ultimately trying to put some new notifications/ringtones directly on the internal storage vs installing something like zedge to manage ringtones (and trying to learn as i go).
Using ADB and fastboot im able to copy files. at least i thought. Booted into TWRP, i can see my device via "adb devices" I try to copy the first time and it fails as it doesnt see the directly (which is odd to me because its clearly there, i can navigated it when booted into android and browsing via Root Explorer. I then see that adb created a directly, i try again and it says it copied. As you can see on the screen shot.
since i cant submit a link yet.... drive.google.com/open?id=0B1halGed5ltCMVY0VzduRk5kTHM
So i think im golden, i go into Android try to change the notification and .. bubkiss. Nothing. I then try to see the file in android via root explorer and its not there.
I think i have a permissions issue as i've tried copying files directly in android using Root Explorer and I get operation failed or permissions complaints.
Any insights on this?
Click to expand...
Click to collapse
bump
Hi, how are you? I'm stuck with a screen lock problem. No USB or developer options enabled (and It cant be enabled, I can only access to de stock recovery mode).
I have been reading and I need to empty the gesture.key file located at /data/system/. But I cant get in to the phone vía adb shell, it only is recognized in sideloadmode.
I know that I can do factory reset and it will solve the problem, but inside the phone there are pics and videos from my girlfriend's pregnancy and that kind of tender stuff that I would like to do not lose with the factory reset. So I was thinking, as I can't connect in other way than adb sideload, that maybe I cant overwrite the gesture.key file by uploading a file with the same directory structure. I am thinking in a update.zip file that contains an empty gesture.key file and the /data/system/ directory.
It would be possible? Maybe if I overwrite the file lock screen pattern will disappear.
I can't find how sideload works (I've been reading a lot but haven't found detailed explanations about what I need, so I post here.
I think that if sideload uploads and decompress the file with the correct directory structure will overwrite the file... it is possible?? Thank you very much for your help