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.
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
I need to follow these instructions -
Originally Posted by Robbie Hood
i will upload a revert back too mtp mod once the party is over.
If you really need it now then do this :
go to /system/build.prop and open it with a rooted text editor ( most file explorers have one) and remove this line:
Code:
persist.sys.usb.config=mass_storage,adb
then go to /system/etc/init.d and remove the S98MassStorage script.
Reboot and it should work fine.
If not , then you need to check rom customizer/. manage system apps / uninstalled tab and install anything kies, usb or mtp related
I have done the first part and removed - persist.sys.usb.config=mass_storage,adb but I can't change/delete/edit/move the S98MassStorage script, I have tried Root Browser Lite, ZArchiver and ES File Explorer.
Can somebody help me please, recommend a method/app?
Try "su -"
Then "rm whateverscript.sh"
To delete the file.
Assuming u got root perms.
Sent from my GT-N7000 using xda app-developers app
Make sure your /system is mounted read-write. It should be, since you edited build.prop, but you can double-check (there's an option in ES File Explorer to mount /system as read-write).
Need to load an app on my phone that can detect the presence of superuser.apk and su, so I'm trying to delete those items. I installed them by flashing a zip in recovery. However, due to the kernel level r/w protection on /system, I can't delete superuser or su by normal means (i.e., a root file explorer).
Anybody know how I can get rid of them? I assume I need some sort of a flashable zip, but haven't found one. Thanks.
Edit: Never mind. Figured out that if I just delete the /system folder from the SuperSU zip, the updater script automatically deletes all old superuser files, and then has no source for the new files. So basically it just removes SuperSU and su. I think that got the job done.
Does anyone know what files to replace/permissions to set in the system image when updating SuperSU and busybox, and where to get these files?
Yes.
644
root:root
You extract them out of the SuperSU package.
Have a look at my attachment, this unzip to /system/xbin/
arohrmann said:
Yes.
644
root:root
You extract them out of the SuperSU package.
Have a look at my attachment, this unzip to /system/xbin/
Click to expand...
Click to collapse
Thank you! I had to place the busybox file into both bin and xbin in order for busybox installer to recognize the updated version, but other than that, I followed your instructions exactly. So now my question is if I just updated the supersu binary to the latest version, why is supersu still telling me that I need to update the binary? Did you extract these from 2.46?
Two more questions: how did you extract them, and where did you get the version of busybox that you included in your previous post?
busybox is just in priv-app not in app - it works.
I don't know, why that update message comes up. It's the latests SU
You can open apk's like ZIP to extract. But you can find Update-ZIP to flash with recovery, to extract
That's the latest busybox I installed on an other android. Just moved to the System-Images.