Database Develop

How to put ringonte (.mp3) into phone memory?

As above. Anyone knows?

bryant_16 said:
As above. Anyone knows?
Click to expand...
Click to collapse
put it in the media>ringtone folder.

bryant_16 said:
As above. Anyone knows?
Click to expand...
Click to collapse
Ok... I'll bite. Ringdroid from the market. Any other answer will take some info.

As in, the ringroid will put the ringtones in the sd card memory not the phone memory, i tried copy paste over but fail.

To place them into the phone memory you will need to either copy them using the terminal or push them through adb.
using adb, place the file(s) in your tools folder
Code:
adb push filename.mp3 /system/media/audio/ringtones
In the terminal, if you place them in the root of your sdcard
Code:
cp /sdcard/filename.mp3 /system/media/audio/ringtones
I am not sure if you need to remount or not to push/copy into the folder or not.

It says read-only file system as the error.

jairomeo said:
To place them into the phone memory you will need to either copy them using the terminal or push them through adb.
using adb, place the file(s) in your tools folder
Code:
adb push filename.mp3 /system/media/audio/ringtones
Click to expand...
Click to collapse
Try:
Code:
adb remount
That should fix the "read only" problem.

i'm not using adb... I'm using the second method which is in the terminal.

Do yourself a favor and go get Root Explorer from the market. It lets you move any file to anywhere.
Move your files to /system/media/audio/ringtones and remember to check to see if the files that are there are .ogg or .mp3. If they are .ogg just rename your files after you move them.

What you mean I have to rename the files after i move them?

What's the exact application name? I tried searching on market but could not find any.

bryant_16 said:
What's the exact application name? I tried searching on market but could not find any.
Click to expand...
Click to collapse
I like SUFBS but ES (or estrong) file explorer is good also. SUFBS cost a buck or 2 but I think it is worth it. Either way your phone needs to be rooted for this. You do have root right?

Yeah, phone is rooted. I tried ES Strong Explorer but cannot work, it says something about permission or something like that..

bryant_16 said:
What you mean I have to rename the files after i move them?
Click to expand...
Click to collapse
I'm not sure if it's a "hero thing" but sometimes the file extensions in the ringtones folder are not .mp3. They are .ogg. If you look into the folder and see .ogg files just change the extension and you'll be all good.
As for the apps. Look for "Root Explorer". I believe there are both free and paid options. The paid one isn't very much $$ so, considering how much easier it makes things, give up the loot and support a dev.

I tried searching under market, but cant find it..

id use terminal with cmds, would be a tad faster and a bit more reliable, in my opinion, but as of searching on your behalf i have found root explorer a paid version and estrongs free version by searching "root" while in the market. estrongs sounds unstable. If your going to pay for a good file explorer get SU file manager&terminal. (and...SAA?ror)

How do I use terminals? I tried but that say permission thingy..

Did you mount the system?

OK dude. If you're rooted I assume you have somebody's recovery. Boot to recovery and go into console (Alt+x). Now do this.
<enter>
mount /system <enter> (maybe mount /system/media if just /system doesn't work)
mount /sdcard <enter>
cp /sdcard/yourfolder/yourringtone.mp3 /system/media/audio/ringtones <enter>
reboot
You should be good to go.

Can I do that in terminal? As in one of the application in my HTC Dream?

Root explorer to move apps into system

Hey guys, I just used root explorer v 2.2 to delete the annoying apps built into the system (amazon mp3)
I am now trying to move my apps into the system so that they cannot easyly be removed. I want to send over lookout and sim checker. That way a theif would not be able to easily delete the apps.
when I select the "move" option (with sim checker) then go to the system apps dirrectpry and then select "paste", it says paste and shows a progress indicator for like 1 second then when I check to see if it actually did the move, it hasn't can anyone help me out
I know I have full root access as I have clicked to allow it and am remounted as r/w so that's not the problem.
Any help to get those two apps into my read only system directory would be greatly apprecaited.
Oh ya I think ill add that I have also tryed to simply change the permissions of the app to readonly (with root explorer) but that did not stop the basic android app manager from uninstalling it.

Try to use adb to move it.

so i went and installed adb, i know its working as well with a little test, could someone please write out a sample command for me to use for this purpose of moving an app out of the apps to sd location and into the system apps.

asb123 said:
so i went and installed adb, i know its working as well with a little test, could someone please write out a sample command for me to use for this purpose of moving an app out of the apps to sd location and into the system apps.
Click to expand...
Click to collapse
mv /system/sd/app/*lookout* /system/app
mv /system/sd/app/*checker* /system/app
It really depends on the name of the file though, if it has lookout in it, then it will be moved to /system/app. The * tells it to move anything with that in the file name

type adb and it will give you the commands + switches
adb pull
adb push

In response to your first attempt, it sounds like system is not being mounted as rw. If it were, the copying would work (I do this all of the time with SUFBS). Try to mount the system as rw via the terminal then copy.

JAguirre1231 said:
mv /system/sd/app/*lookout* /system/app
mv /system/sd/app/*checker* /system/app
It really depends on the name of the file though, if it has lookout in it, then it will be moved to /system/app. The * tells it to move anything with that in the file name
Click to expand...
Click to collapse
so i have the command prompt cd to andorid adk\tools
when i now type in the above :
mv /system/sd/app/*lookout* /system/app
it doesnt recognize the command
so i have C:\android-sdk-windows\tools> mv /system/sd/app/*lookout* /system/app
and it doesnt recognize mv as a command

cloverdale said:
In response to your first attempt, it sounds like system is not being mounted as rw. If it were, the copying would work (I do this all of the time with SUFBS). Try to mount the system as rw via the terminal then copy.
Click to expand...
Click to collapse
hey, sorry for the noob question but could you tell me the command for this. I know in the app i was using it says remount as rw and i do have access to change the system app folder (delted apps) but how can i remount as RW in terminal whats the command? And after, do i need to manually remount back to what i was so that it is back to being unchangeable?

asb123 said:
so i have the command prompt cd to andorid adk\tools
when i now type in the above :
mv /system/sd/app/*lookout* /system/app
it doesnt recognize the command
so i have C:\android-sdk-windows\tools> mv /system/sd/app/*lookout* /system/app
and it doesnt recognize mv as a command
Click to expand...
Click to collapse
If you have the tools directory in your PATH (as you should) no need to cd to the directory. Anyways, sorry to move it in adb do
adb remount
adb shell
*previous commands*
exit
Bingo!

it says failed on /systen/sd/app/com.lookout.apk - cross-device link

asb123 said:
it says failed on /systen/sd/app/com.lookout.apk - cross-device link
Click to expand...
Click to collapse
Ou have 2 android phones plugged in or an emulator running ath the same time

i dont have two phones plugged in and i dont have an emulator that i know of...
but on the bright side i mannaged to solve my problem using droid explorer. I successfully have gotten lookout entrenhed into the system so that it cannot be uninstalled from the menu.
BUT when i tried the same thing for sim checker it did not work, it would not copy into system\apps
i did manage to get it inot system\app but using the copy rather than move option in root explorer, after reinstalling using the simchecker in system\app
but it is showing up as still uninstallable. I have no idea why simcheck is not working but it worked for lookout...

How to push files into system/data without a pc

hey guys ive been trying to get a apk into system/data/app on my N1 but i cant get it right. so i did some research and saw that i needed to push the files into system/data. I dont have a pc to do it on so how can i do it on my phone with the terminal app? My phone is rooted so it should be a quick and easy deal....Right?

If you have busybox you can:
busybox cp nameoffile.apk /system/app/

Rusty! said:
If you have busybox you can:
busybox cp nameoffile.apk /system/app/
Click to expand...
Click to collapse
Okay but where do i put said file so i can push it? Do i copy it into system/data/app and then push it or what?

Just download it to the SD card.

Use Root Explorer, and just copy the file there. Of course, toggle the /system to be in R/W before you copy (an option in Root Explorer).

Stuart.upton666 said:
Okay but where do i put said file so i can push it? Do i copy it into system/data/app and then push it or what?
Click to expand...
Click to collapse
if busybox is installed you dont need the "busybox cp"
you can do this
put whatever.apk in sdcard(or download it) then do
go to terminal
cd /sdcard
or
cd /sdcard/download (this only if you downloaded the apk from phone)
then do
ls(to check if file is there)
then do
cp /sdcard/download /system/data
most likely your gonna get a error bout read-only so you might want to do this before doing cp
mount -o remount,rw /dev/block/mtdblock3 /system
then try again

Root Explorer
Jack_R1 said:
Use Root Explorer, and just copy the file there. Of course, toggle the /system to be in R/W before you copy (an option in Root Explorer).
Click to expand...
Click to collapse
+1
I agree, this is probably the easiest way.

uninstalling Live Wallpapers?

Hey im just wondering how i could uninstall the stock live wallpapers. Anyone one know how to or can we even do it?

Use some kind of root explorer, adb shell or titanium backup to remove the livewallpaper file.
I think its even called Livewallpapers.apk and located somewhere in system/apps?

i have tried using root explorer to delete the apk file in system/apps but it said the file is read only and cannot delete

Remount as read write, either in adb shell,shell emulator or with sgs tools.
'busybox mount -o remount,rw /system'

Cannot edit build.prop anymore - read-only.

Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...

I encountered a similar situation during the build.prop edit while using ES File Explorer on my NC running CM7 on internal memory.
Possibly, the permissions in the program need to be changed to enable it to "write".
Here's what I did: Menu==>Settings==>Root options. "Check" Root Explorer and if my memory serves me correctly, click "Yes" to get past the "Experimental Feature", toggle the "Cyanogen Mod" (if you're using CM7) radio button, click OK and check the "Mount File System" box to make the system writable.
Now, it should be writable. Hope this helps.

dhyamato said:
... check the "Mount File System" box to make the system writable.
Click to expand...
Click to collapse
Thanks for the tip, that wasn't it
I remember setting those originally. I just checked again and "Root Explorer" and "Mount FIle System" are both checked.

mwilli20 said:
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
Click to expand...
Click to collapse
In 106 SU wasn't working correctly until I reinstalled it. You can't modify build.prop without superuser rights. Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.

DiDGR8 said:
Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
Click to expand...
Click to collapse
Interesting... the OP withdrew his post: (apparently it's back in 107)
http://forum.xda-developers.com/showthread.php?t=1131369
However when I checked it, the SU app was misbehaving, Force closing, refusing to respond to the menu command. So I reinstalled it. Now it's OK.
Unfortunately I still cannot edit the build.prop file.
I don't think it's a superuser problem because without SU access ES cannot even see the system folder!!! I can see it, and edit the file, just cannot save it.

You might try fixing permissions under recovery.

have you tried the app: nook netflix fixer?

I've changed it successfully on the past 6 consecutive nightlies using adbwireless pull/push. However since 106 I've hsd to reflash su. N108 hasn't given me the su issue. Is it fixed?

Same problem with the build.prop file: cannot save changes, or copy over it. Running in nightly 108 today. Tried both Root Explorer and ES File manager.

I think you need to change the build.prop file properties to be rw using chmod. Don't forget to mount system as rw before doing the chmod.
Sent from my Huawei Ascend using XDA App

foltz61 said:
I think you need to change the build.prop file properties to be rw using chmod.
Click to expand...
Click to collapse
Tried that (sudo chmod 666...), get the same message. "file system is read-only"

backup and restore fresh start....?

I'm not great at linux but I do it differently. Try chmod +rw /system/build.prop . Make sure you have system mounted as RW first. I'd also check superuser to make sure whatever terminal/file explorer you are using still has root privileges.
Sent from my Huawei-M860 using XDA App

foltz61 said:
Try chmod +rw /system/build.prop
Click to expand...
Click to collapse
666 is the same thing as +rw in this case...
It looks like the "fresh start" suggestion a couple of posts up is the best

All those numbers always confuse me . Sorry. Good luck.
Sent from my Huawei-M860 using XDA App

bike2002 said:
have you tried the app: nook netflix fixer?
Click to expand...
Click to collapse
Thanks! That did it!
Does anybody know why this app can modify the build.prop file while ES File Explorer cannot?

I had to mount the folder containing build.prop with rw access in order to use chmod. I think the latest version of the netflix fixer may do the same (see my post in that thread). In short, I used;
Code:
su
busybox mount -0 rw,remount /dev/block/mmcblk1p3 /system
in the terminal before using the chmod command in order to give myself rw permissions in the folder. I'm only two days old at this, so it beats me why root doesn't have normal rw permissions on the folder.

NCKevo said:
I had to mount the folder containing build.prop with rw access in order to use chmod...
Click to expand...
Click to collapse
Thanks for the tip. I ran the command successfully (by the way, small typo, I believe it's -o not -0) and was able to chmod and edit the file with vi.
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?

Have you tried just pulling the build.prop
Code:
c:/<target_folder> adb pull /system/build.prop
then editing it with note pad then pushing it back and rebooting>

mwilli20 said:
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Click to expand...
Click to collapse
That is confusing. What are the full (i.e. ls -l) permissions on the file now? (It's possible that it somehow ended up with o+w, but I don't understand how - vi isn't exactly known for changing permissions on-the-fly.)
Rodney