I didn't feel like plugging my phone into the computer so I emailed myself an apk file (arctu's Mms.apk) because for some reason...it seems to revert back to stock every reboot...
Anyway, I didn't have any terminal apps so I used Root Explorer to copy then paste over the existing apk. didn't work. Why not? Is there a something different about copy/paste?
If you didn't say you mounted the partition I can only assume it was not mounted as r/w and still at r/o.
copy/paste - visual representation of cp
push - pushing files from computer to phone
They are not the same.
SiNJiN76 said:
I didn't feel like plugging my phone into the computer so I emailed myself an apk file (arctu's Mms.apk) because for some reason...it seems to revert back to stock every reboot...
Anyway, I didn't have any terminal apps so I used Root Explorer to copy then paste over the existing apk. didn't work. Why not? Is there a something different about copy/paste?
Click to expand...
Click to collapse
Yeah, what didn't work? lol.
djmcnz said:
Yeah, what didn't work? lol.
Click to expand...
Click to collapse
the mms app didn't overwrite. But it could have been user error. I'm using Enom's ROM and didn't have the Community Mms Mod checked...so maybe if I had done that first...it would have worked.
Pushing is taking a file from the computer to copy and paste/overwrite the existing file on the phone. What's the difference where the file is being copied over from? Are you sure about what you were trying to explain?
SiNJiN76 said:
Are you sure about what you were trying to explain?
Click to expand...
Click to collapse
k?
I didn't try and explain anything (in this thread at least)?
Either way, yes push literally "pushes" a file to a specified location. However that file needs to be written and if the file system is mounted as read only you will get errors.
If it didn't work you must have received an error message (in root explorer for example), what was that message? If you don't get an error message and the file is still not being written then get a better file manager (ES File Explorer).
The suggestion above by 'evilkorn' was to make sure the file system is in read/write mode before you copy the file over... you can do this in Root Explorer or ES File Explorer.
If your file system is in r/w AND you still don't get an error message AND it still doesn't work then I would try an ADB push as a last resort and if that didn't work, reflash and start from step one I think...
SiNJiN76 said:
What's the difference where the file is being copied over from? Are you sure about what you were trying to explain?
Click to expand...
Click to collapse
Because that was your question in the title, which I answered, they are different terms for different things. You can't push a file on your phone to your phone, you copy it (cp).
You still didn't answer my question... It's hard to help someone when the suggestions fall on deaf ears and all you get is reverb and static back.
evilkorn said:
Because that was your question in the title, which I answered, they are different terms for different things. You can't push a file on your phone to your phone, you copy it (cp).
You still didn't answer my question... It's hard to help someone when the suggestions fall on deaf ears and all you get is reverb and static back.
Click to expand...
Click to collapse
LoL. You gotta ask a question first before I can answer it. You made assumptions, didn't ask questions. LoL. Anyway, I wasn't trying to crawl under your skin. But maybe next time you can read the OP in addition to just reading the title of the thread? Usually, details are given to accompany the title of the thread on the first post. Either way, I guess I wasn't detailed enough. Thanks for your feedback, tho, appreciate it.
@djmcnz - Sorry, my error in quoting the wrong person. Thanks for you explanation, also.
So, to summarize...Push and Copy/Paste should produce the same outcome, right? Cool...like I said earlier...it was my error in not knowing that I had to use the Spare Parts option in Enom's ROM to enable Community MMS.
I use root explorer all the time when I can't use a computer to use adb. It works fine. Usually if its the system partition you have to click the icon that says r/o and it changes to r/w. This will allow you to write files to the partition. Then from what I noticed a reboot usually fixes any issues of stuff not working.
Related
i want to change Effect_tick.ogg in the /system/media/audio/ui
i try to overwrite it or delete it or movie it and im denied even in su mode.
how can i take a ogg of the same name from my sdcard or computer and switch this sucker? this is the sound file for the the screen selection setting and i want to change it.
possible? how? adb push/pull? other than adb?
Your best bet would probably be to unzip your current ROM, throw it in there, zip and sign, and flash. I don't think little files like that can be over-written.
lukekirstein said:
Your best bet would probably be to unzip your current ROM, throw it in there, zip and sign, and flash. I don't think little files like that can be over-written.
Click to expand...
Click to collapse
trying that now. i would have to resign and stuff right? i never done that hmmm
okay i unzipped the rom, took MY effect_tick.ogg and threw it in the unzipped rom, rezipped and signed and the error i got while updating is WRONG DIGEST and it named the system path to my effect_tick.ogg i tried putting in... hmmm im asking cyanogen i first wanted to to it on his ROM. i do realize this is a sound and path not exclusive to his ROMs but its worth a shot thanks for the help
http://androidcommunity.com/forums/...-selection-sound-or-any-other-ui-sound-17949/
That should do it. If you have any good sound files to use as a replacement, can you please upload em so I can take a listen? or maybe suggest where I may acquire some myself possibly?
Seoulboy1 said:
http://androidcommunity.com/forums/...-selection-sound-or-any-other-ui-sound-17949/
That should do it. If you have any good sound files to use as a replacement, can you please upload em so I can take a listen? or maybe suggest where I may acquire some myself possibly?
Click to expand...
Click to collapse
today i set up adb on my work comp (honestly i was lost as to how to get adb working and what exactly is was for the longest haha), just followed your tutorial, and bam! i've got the final fantasy IV screen finger pointer sound as my selection sound.
THANK YOU! oh and i dont have any other good ogg's right now i just wanted taht one. if i make more ill be sure to post em!
thanks again!
I have the original Droid phone. Thus, to tether it to my CN I need to get the CN able to work with Ad-Hoc. I had come to the conclusion the only way to accomplish this was via the ADB shell. The problem is I cannot get ADB to work.
So, that being said, and before I bury another 4 or 5 hours into this, is there another way to get my CN working with my Droid?
Yes, you can do it on your nook using certain apps. I've done it with Root Explorer(paid app), which allows you to alter/replace/change permissions on any system file. Other file manager type programs might be able do this too, maybe even some free ones, but the only one I can verify is root explorer.
pfcwintergreen said:
Yes, you can do it on your nook using certain apps. I've done it with Root Explorer(paid app), which allows you to alter/replace/change permissions on any system file. Other file manager type programs might be able do this too, maybe even some free ones, but the only one I can verify is root explorer.
Click to expand...
Click to collapse
Do you mind posting instructions, or a link to how you did it? I have this exact same situation as the OP (Droid 1/NC).
"Easy Tether" for rooted Droid phones works perfectly for me. It's a Market download and free -- creates an infrastructure network the CN can see and use rooted or unrooted. Rooting your phone (if not already) is pretty quick and easy as compared to rooting the Nook. I have a Droid X.
I have both easy tether and root explorer. Easy tether will not work as it requires a cable connection.
Can you explain what i need to do with root explorer?
jtpryan said:
I have both easy tether and root explorer. Easy tether will not work as it requires a cable connection.
Can you explain what i need to do with root explorer?
Click to expand...
Click to collapse
Place the patched wpa_supplicant file from here http://forum.xda-developers.com/showthread.php?t=868354 somewhere on your sdcard.
Open Root Explorer and navigate to the file on the sdcard.
Copy the file.
Navigate to system/bin
Mount R/W
Rename your original wpa_supplicant file to wpa_supplicant.bak
Paste the new file. (make sure the name is as the original)
Reboot your nook.
Thank you so much!!! Worked great!
Sent from my LogicPD Zoom2 using XDA App
racks11479 said:
Place the patched wpa_supplicant file from here http://forum.xda-developers.com/showthread.php?t=868354 somewhere on your sdcard.
Open Root Explorer and navigate to the file on the sdcard.
Copy the file.
Navigate to system/bin
Mount R/W
Rename your original wpa_supplicant file to wpa_supplicant.bak
Paste the new file. (make sure the name is as the original)
Reboot your nook.
Click to expand...
Click to collapse
Hmmm, won't start wifi at all now. When I pasted the new file should the name be wpa_supplicant or wpa_supplicant.adhocfix? I used the former.
-Jim
Oops. My mistake. Too embarrasing to discuss ;+{
Anyway, all is well. Works the balls!
jtpryan said:
Oops. My mistake. Too embarrasing to discuss ;+{
Anyway, all is well. Works the balls!
Click to expand...
Click to collapse
No please discuss, we're all here to learn from your mistakes! j/k
Glad it worked out for you.
jtpryan said:
Oops. My mistake. Too embarrasing to discuss ;+{
Anyway, all is well. Works the balls!
Click to expand...
Click to collapse
Please explain so i dont make this mistake when i try this later.
Im having the same issue as OP. ill try this method when i get home.
racks11479 said:
Place the patched wpa_supplicant file from here http://forum.xda-developers.com/showthread.php?t=868354 somewhere on your sdcard.
Open Root Explorer and navigate to the file on the sdcard.
Copy the file.
Navigate to system/bin
Mount R/W
Rename your original wpa_supplicant file to wpa_supplicant.bak
Paste the new file. (make sure the name is as the original)
Reboot your nook.
Click to expand...
Click to collapse
Clarify this step for me. Im confused at reading this.
You say to copy then rename original file, then paste. By original file do you mean the one on the sdcard and not the one being pasted?
Could i just pasti into system/bin , and then rename that file? Im just trying to clear this up?
Randomhero27 said:
Clarify this step for me. Im confused at reading this.
You say to copy then rename original file, then paste. By original file do you mean the one on the sdcard and not the one being pasted?
Could i just pasti into system/bin , and then rename that file? Im just trying to clear this up?
Click to expand...
Click to collapse
Yes. You could just paste then rename the wpa_supplicant.adhocfix to wpa_supplicant. I wanted you to renam the original file in your system/bin to wpa_supplicant.bak so you woul have a backup of the original just in case something goes wrong.
Sent from my "NookDroid" using XDA App
Ohhhhhh okay. Sorry if it seemed dumb. Im at work and without my Nc so im not able to see what is in there.
There's never a dumb question when you're learning something from it
Sent from my "NookDroid" using XDA App
racks11479 said:
Place the patched wpa_supplicant file from here http://forum.xda-developers.com/showthread.php?t=868354 somewhere on your sdcard.
Open Root Explorer and navigate to the file on the sdcard.
Copy the file.
Navigate to system/bin
Mount R/W
Rename your original wpa_supplicant file to wpa_supplicant.bak
Paste the new file. (make sure the name is as the original)
Reboot your nook.
Click to expand...
Click to collapse
went home and did this. THANKS!!!! Saw my IP4 MYWI network right away.
It works!! Thanks!
Under 1.1 I found that the ADHOC supplicant was so infuriatingly unstable it was almost unusable, and the lack of reconnect on wakeup was such a pain. this has been the major benefit of moving to Froyo for me - adhoc is seamless.
Hi Im almost done with it but I'm not sure how to rename the file. I'm using root explorer for some reason ADB is not pushing the file. I'm running 1.1 on my nc. I'm in root explorer and I got all the way to copy the file mount r/w and then i'm stuck.
Please help. I'm so close.
Hey bono quick ? when you use froyo is it on the sd card or is on the nook itself. I'm not sure how to get that far. I'm mad because I can't get these files right so that I can connect to my wireless tether through my phone. I'm so close. I finally got ADB to work but I can't push the files to the nook. I'm so lost right now.
Hi guys!
First off sorry for making a new thread about this. I read 3 or 4 on the subject but Im still having no luck.
I dont want to have to mute the volume everytime I want to take a photo
so I prefer changing it in the system.
My model is a Korean Note so that "could" be why I cant diable the shutter sound.
My phone is rooted and in Astro file manager, I went into the appropriate location and added the extension .off, .bak, .backup I tried all three when I tredi to rename the Shutter_01.ogg, and it still doesnt work
Any ideas? Thanks!!!
Try renaming the "ui" directory. If that works, then you'll know it's one of the other OGG files in there. Then if that works, look for something camera-related. I think different ROMs use different sound files.
edanfalls said:
Try renaming the "ui" directory. If that works, then you'll know it's one of the other OGG files in there. Then if that works, look for something camera-related. I think different ROMs use different sound files.
Click to expand...
Click to collapse
ok thx! oh I ried renaming the "ui" folder and it says "insufficient permissions"
How can I get permission? Im confused because I AM rooted
markmessier8888 said:
ok thx! oh I ried renaming the "ui" folder and it says "insufficient permissions"
How can I get permission? Im confused because I AM rooted
Click to expand...
Click to collapse
Which file explorer are you using? Even though your Note is rooted, the file explorer you use still has to run as root (e.g. Root Explorer).
I think in my ui directory, I have a few sound files beginning with "camera". You could try renaming those one at a time (if you have them).
delete Shutter_01.ogg at system/media/audio/ui
edit: sorry didnt read all your post and if u deleted that file it shouldnt give any sound while taking photo,strange :/
EdgaBimbam said:
delete Shutter_01.ogg at system/media/audio/ui
edit: sorry didnt read all your post and if u deleted that file it shouldnt give any sound while taking photo,strange :/
Click to expand...
Click to collapse
oh that worked. But what file should I delete to remove that short beep sound when I take a picture? The shutter sound is gone but not the beep before
Where is th update. Zip file located
I creaed update.Zip file but im not able to find it
Its located in /sdcard
i still not able to find it
when you create the update.zip file, and it's finished, the notification bar will have a notification about the path, check that. If it's not there, may be the zip was not created successfully.
/mnt/sdcard/update.zip
Was this solved? I can't find the file either.. it's not in the root of the sdcard, I've tried to create it twice and searched for it. Any help would be appreciated!
Thanks.
dont you get a notification of completion of the process and when you pull it down, you can see where its located ?
I'm having the same problem. If I look with root explorer, it exists on the root of the SD, but I can't see it in windows? Maybe it's a 2GB file limit thing or something?
but the update.zip is not more than 4MB
nokiamodeln91 said:
but the update.zip is not more than 4MB
Click to expand...
Click to collapse
Yeah, I tried to make a smaller one, and it's still there but I can't see it in windows. I tried renaming it as well and that didn't work either.
the7thson said:
Was this solved? I can't find the file either.. it's not in the root of the sdcard, I've tried to create it twice and searched for it. Any help would be appreciated!
Thanks.
Click to expand...
Click to collapse
Answering my own question - its definitely located in the root, just not visible in Windows no matter what I do. Use a root explorer to grab it and move it to a flash drive or remote network location, that's what I did and it worked great.
Sent from my Nexus 7 using xda app-developers app
I used wifi file transfer. I was able to download the file from there.
I had this problem. Try simply unplugging your phone from the USB cord, wait 5 seconds, then plug it back into your PC. Your PC should now see the update.zip.
One of common prob's with MTP !!
just do a search in root explorer, i got 4 locations of the same file on my galaxy s3 so you can find it in anyone of those.
and yes it is the same file in all of those locations, i even tried to change the name on one of them to check if all of them changed and they did
/data/media/0/update.zip
/mnt/sdcard/update.zip
/mnt/shell/emulated/0/update.zip
/storage/emulated/0/update.zip
Move the file out of the root directory and put it a folder, any folder. It will then show up on windows.
the7thson said:
Answering my own question - its definitely located in the root, just not visible in Windows no matter what I do. Use a root explorer to grab it and move it to a flash drive or remote network location, that's what I did and it worked great.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
This worked for me! Although I used the stock file manager. After moving the update.zip to another location using file manager, I was able to see the file via Windows as well.
just change the file name and retry. worked for me
C:\> adb pull /sdcard/update.zip
J.Michael said:
I don't think that's too big to post without compressing -- just attach the file.
Are you using Windows on your PC?
Did you copy "recovery.log" to your PC?
Did you look at "recovery.log" in a text editor?
Click to expand...
Click to collapse
AquilaDroid said:
No longer relevant.
Click to expand...
Click to collapse
When I asked those questions, I had no interest in seeing the log file. I wanted to pursue what I thought were strange problems doing something that should have been simple.
Spiralling out from the middle, I didn't understand the "file not found, or no read permission". I wanted to pin down whether Windows Explorer was manipulating a file on your phone, which might (although I don't know why) explain the problem.
I asked about you looking at the file just to get confirmation that you had succeeded in copying the file to your PC.
Maybe it has something to do with where you put the file. The context menu option to compress a file is convenient, but gives me no control. (I think it was quite nice in Windows XP; not so nice in Windows 8 or 10.)
The way I remember it, you select the files, but you can't tell it where to put the ZIP file. Maybe the way you copied the file from phone to PC had enough privilege to put it where you put it, but later, in Windows Explorer, you did not have enough privilege to put the ZIP file in the same directory. (And maybe the error message is less than accurate, and it is not "Read" privilege that is lacking.)
If you want to pursue the ability to make ZIP files:
move the file somewhere else and try again. I don't know exactly where you put it the first time, so I can't suggest a clearly different and safer choice. I would think that the personal directory Windows wished on you (maybe C:\Users\Aquiladroid) would be safe.
Look into 7zip: There's a free version. It has both Windows GUI and command line "apps".
{Mod edit: Quoted post has been deleted}
This thread was a sidebar to another thread, to avoid cluttering the other thread with material I thought was off-topic.
You do not describe your 7 GB file, or what you consider "not very effective". Not all files compress "well" (to me, large reduction in size). I expect 7zip has options to control the trade-off between time spent compressing, and amount of compression achieved.
You should start a new thread, asking for advice. There are a lot of people who will notice a new thread, but who do not "watch" this thread.