[Q] Having trouble mounting \system in rw on BAMF 1.5 - Thunderbolt General

Hey guys,
Loaded BAMF 1.5 yesterday and have been enjoying the ROM thus far. However, I've been trying to push my custom widget.txt to the \system\customize\ folder so I can have my own power controls in the notifcation bar. I have tried the Mount rw/ro app from the Market, and have also tried mounting rw using adb (mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system).
Each time, when I use the command: adb push widget.txt /system/customize/ I get the error: failed to copy 'widget.txt' to '\system\customize\': Read-only file system
Where am I going wrong?
Seth

sethschmautz said:
Hey guys,
Loaded BAMF 1.5 yesterday and have been enjoying the ROM thus far. However, I've been trying to push my custom widget.txt to the \system\customize\ folder so I can have my own power controls in the notifcation bar. I have tried the Mount rw/ro app from the Market, and have also tried mounting rw using adb (mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system).
Each time, when I use the command: adb push widget.txt /system/customize/ I get the error: failed to copy 'widget.txt' to '\system\customize\': Read-only file system
Where am I going wrong?
Seth
Click to expand...
Click to collapse
I'm pretty sure the TB is using EXT3, not YAFFS2.
Try
Code:
mount -o remount,rw -t ext3 /dev/block/mtdblock3 /system

Even easier, assuming you have busybox. busybox mount isn't as lame as the standard mount which is provided, so you don't have to tell it as much, it can figure things out on its own:
busybox mount -o remount,rw /system
busybox mount -o remount,ro /system
Click to expand...
Click to collapse

even easier.
sysrw
sysro
Doesn't anyone ever read the first post of my rom?

I'm an idiot. Thanks for the ext3 vs yaffs2 reminder.
I'll try busybox at some point also to check
And to Adrynalyne, apparently I didn't read the first post...my bad. Thanks for reading mine, though. I'll pay closer attention in the future.
Seth

Related

solved: Modified RC30 system file replacement

i have fount how to make the android support more languages (basic support), and it's works great over the Emulator.
i took the font files over "system/fonts" and added the chars i needed.
and now i have the G1 Modified RC30 and i want to take those files and replace them.
but i can't get access to do it.
anyone can guide me how i can replace the files??
solved
Code:
> adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
just need to do this before copying the files
and this when done
Code:
> adb shell mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
hi
how did you manage to change the fonts in the Emulator?
\tools\lib\fonts\default
i tried this one, but it has no use, i suspect that system.img has the system fonts, any help how to access that?
thanks

Script for remounting the file system as r/w?

Ideally, I'd like to have a script that I can keep on my sdcard that when clicked, it remounts the file system as r/w. The idea is to save me from having to manually punch in the command every time. I have DroidSans installed but it seems like overkill to keep the entire program for just that one function.
I'm not new to 'nix, but don't know much about creating scripts.
Thanks to all that help.
You could jus install DroidSans Tweak Tools on v0.87 the first button is to mount as R/W and the one below that is for Read Only.
Just an option I know it's not jus a script but it's what I've been using for the time being till I write a script to use w/ gscript.
couldn't you just use Gscript to run
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
wouldn't that work?
Meltus said:
couldn't you just use Gscript to run
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
wouldn't that work?
Click to expand...
Click to collapse
Yes, you would type:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
In the terminal emulator after being granted superuser access.
Meltus said:
couldn't you just use Gscript to run
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
wouldn't that work?
Click to expand...
Click to collapse
I'll try that. The project page for GScript appears to be down right now for maintenance, but I will try later and see what I get.
Thanks alot.

Blocking the OTA Updates

I am going to bring this up to the group. I am looking for the method to block the OTA updates. I enjoy my rooted Evo phones. It is a freedom I enjoy and plan to protect.
I am getting tired of pressing cancel every day. If I want to update, I want to be the one to control it.
I have been looking for a method to disable the OTA update prompts. From the board, I was able to find this.
Thread 6450334
I have tried it on my Evo with no luck
adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
# cd /etc/security
cd /etc/security
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
# ls
ls
otacerts.zip
cacerts.bks
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
Anyone know why otacerts.zip is in use and cannot be renamed. I did some different methods, but no luck.
Has someone done this before or knows of a better method of blocking the OTA updates from Sprint. I am open for a solution.
check with chuckhriczko, he successfully completed what you are trying to do. Also check out his ROM...it already has this action implemented into the ROM
techie4971 said:
I am going to bring this up to the group. I am looking for the method to block the OTA updates. I enjoy my rooted Evo phones. It is a freedom I enjoy and plan to protect.
I am getting tired of pressing cancel every day. If I want to update, I want to be the one to control it.
I have been looking for a method to disable the OTA update prompts. From the board, I was able to find this.
Thread 6450334
I have tried it on my Evo with no luck
adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
# cd /etc/security
cd /etc/security
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
# ls
ls
otacerts.zip
cacerts.bks
# mv otacerts.zip otacerts.zip.bak
mv otacerts.zip otacerts.zip.bak
failed on 'otacerts.zip' - Directory not empty
Anyone know why otacerts.zip is in use and cannot be renamed. I did some different methods, but no luck.
Has someone done this before or knows of a better method of blocking the OTA updates from Sprint. I am open for a solution.
Click to expand...
Click to collapse
I am assuming you are in the system when doing this? If so, you need to back out into recovery and do it. We currently don't have write access to the system partition while Android is running. Only in recovery. Highly recommend you look up Rom Manager on the market and use that to install the "fake-flash" recovery. It's truly the best recovery we have atm.
But you are doing it correctly except you wrote cd /etc/security. It should be /system/etc/security. The following is all you need.
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
You can ls to make sure it worked but that should do it. Reboot and voila. Never press cancel again.
chuckhriczko said:
But you are doing it correctly except you wrote cd /etc/security. It should be /system/etc/security. The following is all you need.
Click to expand...
Click to collapse
from my brief experience last night with this, /etc is a symlink to /system, so /etc or /system/etc is the exact same thing, doesn't matter.
i took the build.prop in the PC36IMG.zip which shows itself with test-keys, removed those and used release-keys, and the OTA appeared when it hadn't before!
now it downloaded the OTA but verification failed. i had to copy over ota-certs.zip from a stock EVO and those allowed the OTA update to pass verification.
if you wanted to reverse the process and prevent OTA updates from downloading, you can manually change your build.prop to show you as already having .6 software package loaded and it won't show any OTA available anymore.
it might be better to actually load the .6 software though which will adjust the build.prop, but thats my personal recommendation and not related to your request. im also running PC36IMG.zip on .1 software and also get the OTA update prompt but i plan on loading .6 software soon.
another factor to consider is the radio version also ...
joeykrim said:
from my brief experience last night with this, /etc is a symlink to /system, so /etc or /system/etc is the exact same thing, doesn't matter.
i took the build.prop in the PC36IMG.zip which shows itself with test-keys, removed those and used release-keys, and the OTA appeared when it hadn't before!
now it downloaded the OTA but verification failed. i had to copy over ota-certs.zip from a stock EVO and those allowed the OTA update to pass verification.
if you wanted to reverse the process and prevent OTA updates from downloading, you can manually change your build.prop to show you as already having .6 software package loaded and it won't show any OTA available anymore.
it might be better to actually load the .6 software though which will adjust the build.prop, but thats my personal recommendation and not related to your request. im also running PC36IMG.zip on .1 software and also get the OTA update prompt but i plan on loading .6 software soon.
another factor to consider is the radio version also ...
Click to expand...
Click to collapse
Oh I didn't know about the symlink. Good call.
Good point. I forgot to mention I did change the build number in the build.prop to be .6 instead of .1 so maybe that helps.
chuckhriczko,
I first tried it in system and no luck, then I went to recovery. I figured the active system partition was the issue.
Now I know I was in the wrong place. I will get Rom Manager and take a look at your customized ROM.
Nice job on the ROM. Love to say goodbye to those Sprint Apps.
Thanks for the quick response.
C:\Program Files (x86)\android-sdk\tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount: mounting /dev/block/mtdblock4 on /system failed: Invalid argument
# exit
exit
C:\Program Files (x86)\android-sdk\tools>adb devices
List of devices attached
HT05VHL13839 recovery
C:\Program Files (x86)\android-sdk\tools>
I get stuck there. I am rebooted into recovery mode and properly attached as you can tell from the adb devices command. Any ideas?
Problem solved:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
chuckhriczko said:
But you are doing it correctly except you wrote cd /etc/security. It should be /system/etc/security. The following is all you need.
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
You can ls to make sure it worked but that should do it. Reboot and voila. Never press cancel again.
Click to expand...
Click to collapse
Will this work on the Incredible as well?
SteelH said:
C:\Program Files (x86)\android-sdk\tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount: mounting /dev/block/mtdblock4 on /system failed: Invalid argument
# exit
exit
C:\Program Files (x86)\android-sdk\tools>adb devices
List of devices attached
HT05VHL13839 recovery
C:\Program Files (x86)\android-sdk\tools>
I get stuck there. I am rebooted into recovery mode and properly attached as you can tell from the adb devices command. Any ideas?
Problem solved:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/etc/security
mv otacerts.zip otacerts.zip.bak
Click to expand...
Click to collapse
So to reverse this could I use cmd
mv otacerts.zip.bak otacerts.zip
??
Thanks.
How about:
adb shell
su
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService
pm disable com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService\$Receiver
This should disable the OTA updates without removing any files from system.

[Q] XT720 NAND writing permissions

I have Motorola XT720. Device is rooted, but I don't have possibility to change any file in system folders. I need it for overclocing/undervolting. Is there any way to change it? I used root explorer and it give me info that system is read only.
In root explorer you must click the r/w mount button on the top of the screen. Why not just get milestone overclock for you over/under clocking needs.
I'm an idiot I simply didn't see that option... Thank you very much. Reason why i do not want use milestone overclocking is, I want to set undervolting for all frequencies and add conservative governor.
Dont feel bad I didn't see it either at first.
in adb shell
$ su
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
$ rm /system/'filename'
$ $ mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
$ sync
$ reboot
teruyume said:
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
Just be careful that your /system may be mounted off a different partition, depending on your rom. Like mine is /dev/block/mtdblock7.

Filesystem issues

Whelp, I screwed up my filesystem. So I was messing around with commands and tried to remount /data and /cache in rw mode.
I used this command
mount -o remount,rw /
Forgot to finish typing and pressed enter, and it mounted the rootfs into rw mode.
Tried to fix so I ran
mount -o remount,ro /
Probally shouldn't have done that now that I think about it.
It mounted all of the partitions in ro mode including the sdcard.
So I was like lets go to recovery and do a nandroid restore, well it somewhat worked. It fixed all the partitions, I think, except /sdcard
Now when I try to: mount -o remount,ro /sdcard I get an error saying there is no such object.
Same with mount -o remount,ro /storage/emulated/0
Is there a command to fix this or do I need to reflash firmware?

Categories

Resources