I'm trying to delete the audio conf file in system/vendor/etc but it won't let me. I'm rooted and running Pure Nexus.
Also when I go into the recovery and try to use the file manager it doesn't show me any files in that folder even though there are files in there.
I just updated the Rom the other day. What could have gone wrong?
Sent from my Nexus 7 using Tapatalk
you need to mount the system partition as writable first. Issue from the dos command prompt:
adb root
adb remount
and then try again and it should work.
*EDIT* that's from within the normal system. You're also asking about recovery. In that case you need to mount /system first. Click on the 'mount' button inside TWRP and select system and vendor. Then you should be able to delete the file too (make sure you didnt select 'mount system partition read-only'). So that's a solution if you don't have adb installed.
gekkehenkie11 said:
you need to mount the system partition as writable first. Issue from the dos command prompt:
adb root
adb remount
and then try again and it should work.
*EDIT* that's from within the normal system. You're also asking about recovery. In that case you need to mount /system first. Click on the 'mount' button inside TWRP and select system and vendor. Then you should be able to delete the file too (make sure you didnt select 'mount system partition read-only'). So that's a solution if you don't have adb installed.
Click to expand...
Click to collapse
The worked when I did it in the recovery. Thanks so much
Sent from my Nexus 6P using Tapatalk
Related
Now I know I'm rooted. I unlocked my bootloader, flashed CWM 3.0 and installed the Superuser (ef) and even installed Rom manager and gave it permission. But for some reason almost every other rooted app I download and try to use it says that my phone isn't rooted?? I'm using a Nexus S. Anybody had similiar issues and resolved it? Thanks for all responses.
Yes the answer has been posted. Go into the recovery from rom manager or by volume and power. Go to mounts and storage and mount / system. You are see it unmount now so mount the system.
You may also need to zap the system with chmod.
You do this by going into Clockwork Recovery's Mounts & Storage. Mount /system. Then in ADB from your computer type in:
1) adb shell
2) cd /system/bin
3) chmod 6775 su
exit and reboot.
the subject says it all. I've been trying to push apps to my encrypted xoom all afternoon without any luck...
I'll go ahead and admit upfront that I am a noob when it comes to using the sdk... so that could also be a major factor.
adb install (insert exact location+ filename.apk for the app you want to install)
I just tested it out
for example
adb install C:/abc.apk
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
scsa20 said:
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
Click to expand...
Click to collapse
I just tried to execute adb remount (I had not until you mentioned it), but I get a "remount failed: operation not permitted".
Code:
Hannibal:platform-tools dmoore$ ./adb install /Users/dmoore/Documents/android-sdk/platform-tools/AsusReader.apk
1259 KB/s (7747001 bytes in 6.007s)
pkg: /data/local/tmp/AsusReader.apk
Failure [INSTALL_FAILED_DEXOPT]
Additional information: I am on a MacBook Pro using the latest version of the SDK (downloaded it yesterday).
try typing "adb devices" if it does not list your xoom try installing or re-installing the motorola usb drivers
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Sic123 said:
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Click to expand...
Click to collapse
I've already installed the Android File Transfer app... it only allows me to browse the SD card - not the root fs... unless there's something I'm missing...
dmoore44 said:
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Click to expand...
Click to collapse
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Sic123 said:
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Click to expand...
Click to collapse
I have the odex file, so i'm not terribly worried about that.
My major question would be this though... Do I need to go full blown root, or can I just unlock the device?
So yesterday i ''adb push''ed a rom onto my device. I searched for the zip in my recovery, and found out that it was in /sdcard/rom.
This is strange, since i can not find it on my sdcard while booted into android.
However, i located the file and it is located in /mnt/shell/emulated/rom.
When i want to install a rom, and i placed it on my phone while booted into android (so the normal MTP mode) i have to go into my recovery, and navigate to /sdcard/0/rom.
Now i just got one problem, i can not delete the rom zip located in /mnt/shell/emulated/rom!
I'm using rootbrowser, and while it is saying that it deleted the file, it just doesnt.
I've already tried changing the permissions, with no succes.
Does any of you know what i should do next?
I take it your using cwm recovery.
This still mounts the sdcard using the old pre multi user ICS method.
Because of multiuser each user would have their own folder 0,1,2 etc. Which is mounted as /sdcard in android.
The true /sdcard is where you have seen at /mnt/shell/emulated/ the 0 folder which takes you to your files is just the folder for the default user.
Now into your problem.
The easiest way to remove the file would just be to boot back into cwm recovery and run;
adb shell rm /sdcard/rom.zip
Sent from my Nexus 4 using xda app-developers app
Worked like a charm!
Was messing arround before while booted into android, and it gave me errors that it did not have permission to delete the file.
While booted into recovery in deleted wonderfully. Thanks again!
Just got one more question, is it possible to delete the directory aswell?
When i try to use the same command it gives me an error and says that it's and directory.
Which command should i use to delete the directory itself?
-Update- Found the command, rmdir, worked like a charm aswell in recovery!
You can use rm -rf to delete the folder and all files inside.
Looks like you didn't need it as the directory was already empty.
Sent from my Nexus 4 using xda app-developers app
Hi !
I have a problem, my phone (nexus with cyanogenmod10.2) switch off when he have finished to boot, as if there was very low power battery.
So i want to reset all but i need a solution to save all my datas, on "sdcard" and in "system" memory
i read that i can using the cmd : adb pull "device files directory" "PC files directory"
but i don't know how to use it... i'm french and its hard to translate all...
so if there is a French who can explain me its perfect !
if the explanations are clear in english its perfect too
To use any of these command you need to install adb on your computer. Here is a guide: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
After that you open a command prompt window (windows key + r, type in "cmd", press enter). Then you put the phone into custom recovery and use the command "adb pull /sdcard/".
I've done these steps
But my problem is how to write, i need the "trame"(in french).
to be in recovery mode, i just have to boot in fastboot and select recovery mode and press power and next step is to sent my commands right?
the bg gg said:
I've done these steps
But my problem is how to write, i need the "trame"(in french).
to be in recovery mode, i just have to boot in fastboot and select recovery mode and press power and next step is to sent my commands right?
Click to expand...
Click to collapse
Correct.
Chromium_ said:
Correct.
Click to expand...
Click to collapse
Ok, but, i'm in the correct directory to use adb i write : adb pull /sdcard/ E:\Nexus4SDcard\ and nothing happens, as if i made a mistake... and i need to save all, sd card + system, so how can i do? what is the directory?
Someone can help me? 3 days without phone its hard :/
the bg gg said:
Ok, but, i'm in the correct directory to use adb i write : adb pull /sdcard/ E:\Nexus4SDcard\ and nothing happens, as if i made a mistake... and i need to save all, sd card + system, so how can i do? what is the directory?
Click to expand...
Click to collapse
If you looked at that other guide and have added adb to the environment variables
In your command prompt, do the following
E:
cd Nexus4SDcard
adb pull /sdcard
It should now being transferring
Sent from my Nexus 4 using xda app-developers app
finally i didn't write any directory for destination and it works fine but in this directory : C:\Program Files (x86)\Android\android-sdk\platform-tools, but its not a problem, using command prompt : "adb pull /"
how can i save and restore all my sms messages?
If the database is still intact it is located at /data/data/com.android.providers.telephony/databases/mmssms.db
You grab it the same way you tried to pull.
In recovery
adb shell mount /data
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
Sent from my Nexus 4 using xda app-developers app
i have an error :/
"C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell mount /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Device or resource busy"
and when i'm in the recovery mode i can't unmount /data
Sounds a little extreme... chances are, there's a better method.
If you have CM10.2, then no doubt you have a custom recovery already. I'm going to assume that this is not an actual battery issue. Is it crashing and rebooting or flat out turning off? I can't remember if CWM shows battery percentage, but TWRP does. What does it show?
What are you trying to back up? Just your /sdcard? Or your /data as well?
What happened to make it seemingly turn off once it's booted? Did you flash a new nightly?
You could always backup /data in your custom recovery as well and then do the wipe that doesn't erase the "sdcard" and then pick apart your backup later...
Hi. My screen is dead on my phone. I need to somehow disable the alarm.
I cannot seem to find where the alarm data is stored.
I then tried to delete the apk.
I got an ADB by booting into TWRP. Then used ADB SHELL. I attempted to cd into System/App as follows
cd system/app
/sbin/sh: cd: can't cd to system/app
I figured I had a root permission error, so I tried "su" but it couldn't find the command which is odd because I have SuperSu.
I can't navigate the TWRP menus due to my broken screen and don't know what to do.
Ratiocination said:
Hi. My screen is dead on my phone. I need to somehow disable the alarm.
I cannot seem to find where the alarm data is stored.
I then tried to delete the apk.
I got an ADB by booting into TWRP. Then used ADB SHELL. I attempted to cd into System/App as follows
cd system/app
/sbin/sh: cd: can't cd to system/app
I figured I had a root permission error, so I tried "su" but it couldn't find the command which is odd because I have SuperSu.
I can't navigate the TWRP menus due to my broken screen and don't know what to do.
Click to expand...
Click to collapse
you can wipe data.... and to do so you can use a openrecovery script
make a file named openrecoveryscript and push it in /cache/recovery/
in the file put the folowing command
wipe data
and then reboot into recovery and it will execute by itself.
by wiping data the phone will reset to factory/rom defaults. you will loose installed data. everything on "sdcard" will stay in place
darkobas said:
you can wipe data.... and to do so you can use a openrecovery script
make a file named openrecoveryscript and push it in /cache/recovery/
in the file put the folowing command
wipe data
and then reboot into recovery and it will execute by itself.
by wiping data the phone will reset to factory/rom defaults. you will loose installed data. everything on "sdcard" will stay in place
Click to expand...
Click to collapse
I considered wiping it, but wanted to avoid that so I can determine who attempts to call/text me before I can get a replacement.
darkobas said:
you can wipe data.... and to do so you can use a openrecovery script
make a file named openrecoveryscript and push it in /cache/recovery/
in the file put the folowing command
wipe data
and then reboot into recovery and it will execute by itself.
by wiping data the phone will reset to factory/rom defaults. you will loose installed data. everything on "sdcard" will stay in place
Click to expand...
Click to collapse
Get an mhl cable and plug it in to a tv or monitor. It mirrors the display so you can navigate it as usual, unless the digitizer AND the panel are both dead...
Sent from my LG-D803 using xda premium
dirt_squirrel said:
Get an mhl cable and plug it in to a tv or monitor. It mirrors the display so you can navigate it as usual, unless the digitizer AND the panel are both dead...
Sent from my LG-D803 using xda premium
Click to expand...
Click to collapse
I should have clarified. The display works as in it can display an image. It just does not recognize my touch other than in a very small area.
If you have root access with adb...
Run adb root
Then adb shell
Cd to /system/media/alarms and delete all the sounds.
Or search for clock in /data/data
Sent from my LG-D802 using Tapatalk