Related
Hi,
I have rooted my Hero with the tutorial on villainroms page but when I try to delete the bootanimation.zip with astro file manager it doesn't work.
zulu1 said:
Hi,
I have rooted my Hero with the tutorial on villainroms page but when I try to delete the bootanimation.zip with astro file manager it doesn't work.
Click to expand...
Click to collapse
Did you remount the system partition as RW first? The app should let you do this
I have just done what was said in the tutorial so I don't think that I have done what you say and actually I don't quite know what that is.
I made myself a bootscreen and I tried to use that but it didn't work so I downloaded a bootscreen available on the web but that didn't work either.
The bootscreen I have at the moment is from here called drawing-froyo maybe it has to do something with that.
Nah, nothing to do with which one you have.
You need to find out how to remount system in astro (google maybe) and do that.
It will then be easy to overwrite
You could use adb, or downloader a popular root explorer for your pc to browse your phone
MacaronyMax said:
You could use adb, or downloader a popular root explorer for your pc to browse your phone
Click to expand...
Click to collapse
Could you provide the adb command to remount with the proper permissions?
Command prompt:
C:\ ..\> adb devices <-- this will detect your phone connect to pc
C:\ ..\> adb remount <-- remount the phone
C:\ ..\> adb shell <-- command to enter shell command, the drive letter C change to # meaning u have enter shell mode
# su <-- superuser permission
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system <-- changing permission of read/rewrite
# cd /system/media/bootscreen/ <-- change directory to /system/media/bootscreen/
# ls -l <-- list of apps/files in current directory, this is not important, just to ensure the file u seek is there..
# rm any_files_u_wanna_delete <-- remove aka delete command(make sure u already backup or pulled it before doing this)
# exit <-- exit shell command, type it again until the # change back to "C:\>"
C:\ ..\> adb push C:\any_files_u_wanna_push /system/media/bootscreen/ <-- push ur files, with directory of the file to push then directory of where the files should be pushed in
C:\ ..\> adb reboot <-- reboot command, reboots the phone, unplug it and see it runs.. if the bootanimation didn't play/just stalled, try redoing all these steps with the old bootanimation, or do a nandroid restore.
as far as I know, bootanimation in /system/media/bootanimation/ folder is not in zip files, it's in multiple files(in my stock 2.1, it's boot.gif, boot.mp3, boot2.gif, boot_animation.xml and boot_bg.gif). so I bet, u have to extract these files from the zip and push it one by one.
Good luck on adb
I am trying to install TapNTap keyboard in Vegan Ginger. (yeah, I know but I want to anyway). I need to copy two files to /system/app and system/lib. I presently have the files stored in /mnt/sdcard/download. I have terminal emulator installed and when I su I appear to get root (prompt changes to #). I was able to create an empty directory in /. When I try to copy the file to /system/app I get a message that it is a Read-only file system. When I do an ls -l the permissions show drwxr-xr-x for the directory. The owner is root and the group is root. It would seem that as su I should be able to copy the file there. Possibly it is mounted as RO. I tried to use a remount command but it failed. I'm not well versed in that so I may have done something wrong. Long and short - how do I get the file copied into the directory?
http://lmgtfy.com/?q=remount+system+rw+android
cannot edit build.prop. i get an error when trying to edit it with es file explorer (there was an error when trying to save this file.)
any help? ive edited it before, but i dont know how. im pretty sure i did it this way but im not sure why its not saving properly this time.
running calk+clemsyn rom/kernel combo.
thanks!
Copy it to another folder edit the copy and then move the edited file in the correct folder.
tried that already, didnt work. got another error
I use Root Explorer to do any editing.
Any other suggestions? I'd rather not have to pay for it
joshtb86 said:
cannot edit build.prop. i get an error when trying to edit it with es file explorer (there was an error when trying to save this file.)
any help? ive edited it before, but i dont know how. im pretty sure i did it this way but im not sure why its not saving properly this time.
running calk+clemsyn rom/kernel combo.
thanks!
Click to expand...
Click to collapse
If the build.prop you want to edit is in /system, then you'll have to mount /system read-write before you can modify any files there:
Code:
$ su [I]Become superuser. Prompt will change to '#'.[/I]
# /system/xbin/mount -w -o remount /system
[I]Edit the file[/I]
# /system/xbin/mount -r -o remount /system
You must have the Superuser app from Market and busybox installed on the gTablet for the commands to work. If you can't edit the file in ES File Explorer because of permission errors, copy the file into /mnt/sdcard via the command line, edit it there (or on the PC after removing the card), then move it back into place in /system and restore the old permissions:
Code:
$ cp /system/build.prop /mnt/sdcard/.
[I]a) The build.prop file in /mnt/sdcard should be editable now in ES File Explorer.
Edit the file, then do:
OR
b) Unmount the SD card via Settings > Storage, then remove the SD card and
edit the file elsewhere. Plug it back in, and, after it mounts do:[/I]
$ su
# /system/xbin/mount -w -o remount /system
# /system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
# chown root.root /system/build.prop
# chmod 644 /system/build.prop
# /system/xbin/mount -r -o remount /system
All this is much easier through adb if you have that setup.
Note: Do not type the prompts--the '$' and '#' characters--in; they're just there to tell you what the Terminal screen should look like.
joshtb86 said:
Any other suggestions? I'd rather not have to pay for it
Click to expand...
Click to collapse
Did you have ES file explorer in Root mode?
In Es file explorer
Settings->Root Options -> both boxes checked, (HiAPK mode for first box)
I usually copy the file to sdcard and modify it, get ES explorer in root mode and copy it back. Do a backup before, in case you mess it up.
I usually use a terminal in su mode for editiing/copying, but that might not be needed.
cbay said:
Did you have ES file explorer in Root mode?
In Es file explorer
Settings->Root Options -> both boxes checked, (HiAPK mode for first box)
I usually copy the file to sdcard and modify it, get ES explorer in root mode and copy it back. Do a backup before, in case you mess it up.
I usually use a terminal in su mode for editiing/copying, but that might not be needed.
Click to expand...
Click to collapse
if i use CM Mod, i cant see any files. if i use HiAPK, all the files have -rw and a lot of stuff before it and i cant read anything, but it does mount. CW had problems mounting the drive. im gonna try out the terminal commands
rajeevvp said:
If the build.prop you want to edit is in /system, then you'll have to mount /system read-write before you can modify any files there:
Code:
$ su [I]Become superuser. Prompt will change to '#'.[/I]
# /system/xbin/mount -w -o remount /system
[I]Edit the file[/I]
# /system/xbin/mount -r -o remount /system
You must have the Superuser app from Market and busybox installed on the gTablet for the commands to work. If you can't edit the file in ES File Explorer because of permission errors, copy the file into /mnt/sdcard via the command line, edit it there (or on the PC after removing the card), then move it back into place in /system and restore the old permissions:
Code:
$ cp /system/build.prop /mnt/sdcard/.
[I]a) The build.prop file in /mnt/sdcard should be editable now in ES File Explorer.
Edit the file, then do:
OR
b) Unmount the SD card via Settings > Storage, then remove the SD card and
edit the file elsewhere. Plug it back in, and, after it mounts do:[/I]
$ su
# /system/xbin/mount -w -o remount /system
# mv /mnt/sdcard/build.prop /system/build.prop
# chown root.root /system/build.prop
# chmod 644 /system/build.prop
# /system/xbin/mount -r -o remount /system
All this is much easier through adb if you have that setup.
Note: Do not type the prompts--the '$' and '#' characters--in; they're just there to tell you what the Terminal screen should look like.
Click to expand...
Click to collapse
when i tried the mv command to move it back, i still got errors in moving it and was not able to
joshtb86 said:
when i tried the mv command to move it back, i still got errors in moving it and was not able to
Click to expand...
Click to collapse
Try
Code:
/system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
instead of plain 'mv'. The default Android mv command is idiotically implemented. (See this post if you're interested in the details):
http://forum.xda-developers.com/showpost.php?p=13956585&postcount=4
Using 'cp' command instead of 'mv' should also work; this way, you'll also have a backup of build.prop in /mnt/sdcard/.
rajeevvp said:
Try
Code:
/system/xbin/mv /mnt/sdcard/build.prop /system/build.prop
instead of plain 'mv'. The default Android mv command is idiotically implemented. (See this post if you're interested in the details):
http://forum.xda-developers.com/showpost.php?p=13956585&postcount=4
Using 'cp' command instead of 'mv' should also work; this way, you'll also have a backup of build.prop in /mnt/sdcard/.
Click to expand...
Click to collapse
thanks so much again. i finally got it to work, but i just wanted to get netflix to work, and it still doesnt. after all that work. ugh.
JoTeC said:
I use Root Explorer to do any editing.
Click to expand...
Click to collapse
Thanks, I tried two other applications and they didn't work. Was able to edit with Root Explorer. didnt fix the Netflix playback. Bummer.
***** changing the Nexus S to HTC Vision and samsung to HTC did the trick.
Root explorer will work, and is a great app. Worht the money.
Also, ADB from a PC will work as well. Just install the android sdk and use ADB.
From windows cmd prompts the commands are just adb remount (to remount as root) then "adb pull /system/build.prop" (this will pull it to the sdk platform-tools folder that adb.exe is in) and then edit to your hearts delite.
"adb push build.prop /system/build.prop" to send it back.
I was able to use ES File System by unchecking the Mount File System option in the Root options menu and then rechecking it. I imagine that it forced a remount of the file system in a writable mode.
This worked on our nabi big tab hd24
We now have true multiuser, where everyone has their own login, files, emails, bookmarks, web history, etc; as it should be.
I first did a factory reset, then installed kingo root, then another reset, did the build prop edit this suggested (es file explorer did not work) but build prop editor did....
We now have the nabi big tab hd 24 running as our primary desktop workstation computer...
No we just wish for a room update to be made available with the latest version of Android.
4.4.2 is getting old, and as is common little manufacturer long term support...
i have wildfire S-OFF and root, using CM7 stable,i installed super manager, gave it superuser permissions,set busybox path to system/xbin,gave R/W acces to system, and tried to copy bootanimation.zip to both data/local and system/media... but when i paste super manager always says not enough free space... but i doubt thats the issue cause the animation is just a few kbs...after it says not enough free space it the sign goes away and the bootanimation.zip appears in the directory as it was copied there but when i reboot i dont have the animation just blank screen.. i tried everything and i dont really have a clue whats wrong
can anyone help me please?
you need to copy the file as root, which means your file manager should have asked for permission. if you cant get it to work you can just fire up a terminal on your phone and run the following commands
su
cp <path to bootanimation you want to use> /system/media/bootanimation.zip
Or via ADB
(Place the bootanimation.zip to where you have adb)
Open up command prompt
cd (location of your adb)
adb shell
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3
# chmod 777 /system
exit
adb push bootanimation.zip data/local
thank you both for your help it works now
Thank you very much.
It works correctly
Hi guys.
I was editing the vold.fstab file using root explorer. When i restarted my phone i got a message "Unfortunately Usb connectivity has stopped working." when i open settings i got message "Unfortunately, Settings has stopped working". I still have my original vold.fstab file left in my sd card but sd card is not working too. I have an Xperia M rooted and unlocked bootloader Please help.
Please tell me if there is a way to reset everything and reinstall the firmware.
Thanks.
Zexter21 said:
Hi guys.
I was editing the vold.fstab file using root explorer. When i restarted my phone i got a message "Unfortunately Usb connectivity has stopped working." when i open settings i got message "Unfortunately, Settings has stopped working". I still have my original vold.fstab file left in my sd card but sd card is not working too. I have an Xperia M rooted and unlocked bootloader Please help.
Please tell me if there is a way to reset everything and reinstall the firmware.
Thanks.
Click to expand...
Click to collapse
You could try to use adb to restore the original vold.fstab to your /system/etc/ folder if your usb debugging is still working:
Code:
adb push vold.fstab /system/etc/vold.fstab
adb shell
su
chmod 755 /system/etc/vold.fstab
exit
adb reboot
If it doesn't work try an other way:
Code:
adb push vold.fstab /data/local/tmp/vold.fstab
adb shell
su
mv /data/local/tmp/vold.fstab /system/etc/vold.fstab
chmod 755 /system/etc/vold.fstab
exit
adb reboot
If any of these ways doesn't work and you have a cwm recovery try to give these commands while you are booted to recovery.
You could also make a flashable zip and you flash it from recovery.
**If you double mounted your sdcard may be corruped and you have to use a partition manager to recreate the partition of your sdcard on PC**
Thanks for the reply.
Well the usb debugging is still working. So i tried the both adb push command, it says "cannot stat 'vold.fstab': no such file or directory" . EDIT: Tried it again, says "failed to copy vold.fstab to '/system/etc/vold.fstab': Read only file system.
I also tried that chmod command but doesn't works, says "cannot chmod system/etc/vold.fstab: Read only file system.".
And about that cwm, i can't get into cwm recovery. I tried all that vol up and down things. I tried using sd card with a card reader, it works fine. Please help.
Thanks in advance.
Zexter21 said:
Thanks for the reply.
Well the usb debugging is still working. So i tried the both adb push command, it says "cannot stat 'vold.fstab': no such file or directory" . EDIT: Tried it again, says "failed to copy vold.fstab to '/system/etc/vold.fstab': Read only file system.
I also tried that chmod command but doesn't works, says "cannot chmod system/etc/vold.fstab: Read only file system.".
And about that cwm, i can't get into cwm recovery. I tried all that vol up and down things. I tried using sd card with a card reader, it works fine. Please help.
Thanks in advance.
Click to expand...
Click to collapse
To apply these changes to system partition you have to make your system partition rewritable.Try to make it rw from Root Explorer or try some adb command:
Code:
adb remount
adb shell
su
mount -o remount,rw /system
If this doesn't work try something like:
mount -o remount,rw -t {your partition type} /dev/block/{your partition name and number} /system
* To see your partition table give the command cat proc/mtd or cat /proc/emmc *
Example:
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
Then try to push the file in the system (Give the "exit" command to quit the shell before try to push the file).
Gatosbil said:
To apply these changes to system partition you have to make your system partition rewritable.Try to make it rw from Root Explorer or try some adb command:
Code:
adb remount
adb shell
su
mount -o remount,rw /system
If this doesn't work try something like:
mount -o remount,rw -t {your partition type} /dev/block/{your partition name and number} /system
* To see your partition table give the command cat proc/mtd or cat /proc/emmc *
Example:
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
Then try to push the file in the system (Give the "exit" command to quit the shell before try to push the file).
Click to expand...
Click to collapse
Okay here's what i did.
I pushed the vold.fstab that i backed up before editing. After that i copied the vold.fstab into /system/etc in R/W Mode.
Then i restarted my phone, and finally everything worked fine.
Thanks for the help mate. You've been big help to me. I couldn't have done it without you.
hello i have a problem similar to this.i edit my vold.fstab file on my emdoor em63 tablet and when i rebooted the sdcard didnt work i was switching the internal to external, I tried to push the file with adb but it says device not found adb works fine for everything else but not for my sdcard i can remount, mount, reboot, but i cant push or pull and on the table when i got to settings/apps or settings/storage force close on me what can i do?