I'm running void, and I need to make some space in /system.
In particular I'm interested in those apps which get updated in the market, but are installed using the "gapps" module:
- gmail (com.google.android.gm-1.apk)
- youtube (com.google.android.youtube-1.apk)
- google search (com.google.android.googlequicksearchbox-1.apk)
- maps (com.google.android.apps.maps-1.apk)
- market (Vending.apk)
Can I remove them on /system/app? They are already in /data/apps it shouldn't be a problem. Thanks
This has been asked a lot of times before, but anyway:
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm *appname*.apk
The real answer of my question is: yes you can safely remove from /system/app all applications that you will find on market.
I tested it yesterday with success
Yeah, but my reply was a verbose version of "yes" Sorry, didn't get it right.
Titanum backup can remove all of those, and its included in one of the void packages... or maybe its already in the void rom. I cant remember which one at the top of my head. But even if you download the free one from market place with ads, it'll still do the job
You really should leave the filesystem they way you found it (read only). I would recommend that you append the above steps with:
Code:
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
It more than likely will be fine without it and on the next reboot it will mount as read only, but proper procedure is to put it back as read only when you're finished with it.
U can use Titaniumbackup to remove them or Root explorer(seach in market).
Sent from my LG-P500 using XDA Premium App
Related
Do you have many apps installed and suddenly your device said that your internal memory is low? While this is happened, you also can't receive any sms...
Usually it happened when your /data partition comes below 22mb free space... But now I realize that I still have 60mb free space in my /system partition...
So to sum it up, I basically just move some of the .apk in /data/app/ into /system/app/
To do this, you can use:
- adb shell > su
- install Root Explorer or SU File Manager (easier)
- add your own method here
Then reboot. Remember that by doing these, your application will now becomes protected application... You can't update it with market and you can't uninstall it (except by using Titanium Backup)... So I just put some of my apps that I thought I will never update (such as some games that I install from SD card )
Now my /system partition only have 100kb free space
You also can freeing up /system free space by uninstalling some unneeded default apps that comes with your devices. For example, default trial RollerCoaster app or uninstall timescape...
More info for uninstalling this protected apps, go to forum.xda-developers.com/showthread.php?t=740338
Or you can uninstall protected apps directly using Titanium Backup... Backup it first in case you want to use it later...
One more thing, root required. To root, go to forum.xda-developers.com/showthread.php?t=739874 or forum.xda-developers.com/showthread.php?t=739845
P.S: I can't post a links yet
Brilliant tip - I might put this on my blog after testing it! Thank you!
Ok, Perfect!
It works. Thanks
Noice one.
Are you absolutely sure that protected apps can't be updated on the market?
Facebook and Maps came pre-installed for me and are protected; they also update regularly from the Market..
I think they'll update - you'll just get the new version installed to /data/ with the older version left in /system/
So when you get an update, you'll just need to manually delete the previous version from system and copy the new version back in its place (if that makes sense)
Very nice post, I have a question, should it be done by rooting your phone first?? Coz u said that u r using adb shell with super user, am I right?
Sent from my Xperia X10 Mini Pro
I found this post and thought that this was very usefull, so i went ahead and tried it out on my missys phone.
1st of all, ive done some heavy modifications to the general look and feel of the phone. Nearly all blue is gone. Changed it to baby pink. My girl likes Twilight saga alot, so i changed nearly all the app icons in the apk's, both the SE ones in /system/app and the ones in /data/app.
The changing of images, icons, bars and buttons, i will try and write another post on under the theme forum later.
So.. I went ahead and tried this:
Obviosly the phone is rooted, else i couldn't change anything in the phone =)
I tried to move MyBackup from /data/app to /system/app.
The app is installed and working like it should and i did:
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
mount -o rw,remounr -t yaffs2 /dev/block/mtdblock3 /data
busybox mv /data/app/com.rerware.android.MyBackup.apk /system/app
reboot
What happens after this is... No icon in menu.. Can't find it anywhere.. Should it be renamed or what am i missing here?
I have then deleted the program. Installed it again from market. Found it in working order and tried things like:
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
mount -o rw,remounr -t yaffs2 /dev/block/mtdblock3 /data
dd if=/data/app/com.rerware.android.MyBackup.apk of=/system/app/com.rerware.android.Mybackup.apk
reboot
Same result..
Another go..
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
mount -o rw,remounr -t yaffs2 /dev/block/mtdblock3 /data
cat /data/app/com.rerware.android.MyBackup.apk > /system/app/com.rerware.android.MyBackup.apk
reboot
Again, no app icon anywhere on the phone..
Last i tried:
Code:
adb push c:\x10\apk\com.rerware.android.MyBackup.apk /sdcard/apk/com.rerware.android.MyBackup.apk
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
mount -o rw,remounr -t yaffs2 /dev/block/mtdblock3 /data
busybox install /sdcard/apk/com.rerware.android.MyBackup.apk /system/app
reboot
Still failing... so, what am i missing?
shadowillusion said:
Remember that by doing these, your application will now becomes protected application... You can't update it with market and you can't uninstall it (except by using Titanium Backup)...
Click to expand...
Click to collapse
All is correct.
But using appbrain - fastweb installer apps, you can see if a "protected" app is up to date or not in the application list of appbrain app too.
So you can uninstall it and re-install the update version (if you want)
I moved a lot of apps to /system
Thank you very very much for this tip
FastDuck said:
I found this post and thought that this was very usefull, so i went ahead and tried it out on my missys phone.
1st of all, ive done some heavy modifications to the general look and feel of the phone. Nearly all blue is gone. Changed it to baby pink. My girl likes Twilight saga alot, so i changed nearly all the app icons in the apk's, both the SE ones in /system/app and the ones in /data/app.
The changing of images, icons, bars and buttons, i will try and write another post on under the theme forum later.
So.. I went ahead and tried this:
Obviosly the phone is rooted, else i couldn't change anything in the phone =)
I tried to move MyBackup from /data/app to /system/app.
The app is installed and working like it should and i did:
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
mount -o rw,remounr -t yaffs2 /dev/block/mtdblock3 /data
busybox mv /data/app/com.rerware.android.MyBackup.apk /system/app
reboot
What happens after this is... No icon in menu.. Can't find it anywhere.. Should it be renamed or what am i missing here?
I have then deleted the program. Installed it again from market. Found it in working order and tried things like:
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
mount -o rw,remounr -t yaffs2 /dev/block/mtdblock3 /data
dd if=/data/app/com.rerware.android.MyBackup.apk of=/system/app/com.rerware.android.Mybackup.apk
reboot
Same result..
Another go..
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
mount -o rw,remounr -t yaffs2 /dev/block/mtdblock3 /data
cat /data/app/com.rerware.android.MyBackup.apk > /system/app/com.rerware.android.MyBackup.apk
reboot
Again, no app icon anywhere on the phone..
Last i tried:
Code:
adb push c:\x10\apk\com.rerware.android.MyBackup.apk /sdcard/apk/com.rerware.android.MyBackup.apk
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
mount -o rw,remounr -t yaffs2 /dev/block/mtdblock3 /data
busybox install /sdcard/apk/com.rerware.android.MyBackup.apk /system/app
reboot
Still failing... so, what am i missing?
Click to expand...
Click to collapse
I think you are forgetting to reboot the phone!
Apps aren't showing if moved and the phone didn't reboot!
Dear,
when I move the file facebook from the folder: data/app to system/app with the root explorer on the mobile phone after reboot I can not see the icon on the screen
regards
juergen
Reboot again and you'll see it
Actually, apps do show without a reboot.
Problem is that there was references somewhere in the phone to the app when it resided in /data/app... So i copied the apk to the sdcard. Uninstalled the app and after root, mount i did a:
busybox install /sdcard/some/path/SomeApp.apk /system/app
it worked like a charm.. And it shows without a reboot..
FastDuck said:
Actually, apps do show without a reboot.
Problem is that there was references somewhere in the phone to the app when it resided in /data/app... So i copied the apk to the sdcard. Uninstalled the app and after root, mount i did a:
busybox install /sdcard/some/path/SomeApp.apk /system/app
it worked like a charm.. And it shows without a reboot..
Click to expand...
Click to collapse
works this also perfect with root explorer, when I not connected my phone to the pc?
Okay so you installed a custom ROM on you xperia x8 and you get this great new market, full of flashy looks and all, but its slow and takes more time than the old android market did? Now if you want your old Android market back do the following and it should work
Before doing this please backup your current market just in case anything goes wrong , you can use Titanium Backup
Now using titanium backup Uninstall the current market and market updater, Check your app drawer market should be gone, now follow these steps
Download this Rar file http://www.filesonic.com/file/1742293344
Extract The files
Plug your Cell phone and Copy these files in you SD card
note: Dont copy them in any folder, copy them directly in the sd card
Restart your cell phone
After cell phone Restarts and becomes stable , Run Terminal Eluminator( most custom roms have them preinstalled) in case you dont have it , download it from the market
Type these lines very carefully in the Terminal Eluminator, use landscape keyboard its safer that way, Type these lines,
Su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cat /sdcard/updater.apk > /system/app/updater.apk
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
reboot(type reboot) do not manually rebooy
After this your phone will reboot. Now, you have installed Updater, you just need to follow same step to install Market main file. So, go back again in Terminal Emulator and type this
Su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cat /sdcard/market.apk > /system/app/market.apk
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
Reboot
Thats it,, after reboot you should have your old android market back
note: type the lines very carefully, they are crucial in order to succes
I posted this in the nook touch forum by mistake. Please read below and let me know what you think.
One of the biggest issues I had with my nook was the 16/1GB division between content I can load and content from B&N/etc. Not being able to use that 16GB how I wanted was something I set forth to fix. Here is my solution to make this usable to non-rooted apps.
1) Root if not already rooted.
2) Make a directory inside of /data. I chose /data/usrdata.
3) remount / as RW with the command mount -o remount,rw -t rootfs rootfs / (credit to Indirect for this, as I could't find the command to do so)
4) mkdir /mnt/internal . We need somewhere to mount /data/usrdata/ and /mnt is public enough.
5) busybox mount -o bind /data/usrdata /mnt/internal. Mounts /data/usrdata to /mnt/internal.
6) For good measure, chmod 777 /mnt/internal and chmod 777 /data/usrdata.
Now, /mnt/internal should have whatever free space /data has, and should be read/write accessible from any program. A quick test with touch+terminal emulator shows new files as being created with RW permissions for all.
Alternatives: When I was initially thinking about ways to do this, my first reaction was to just open up /data to be read only to all, then have my usrdata folder be read/write all. However, I know part of android's app security model depends on some of these permissions. While I can't think of anything breaking or sensitive data being leaked, I decided against it. If anyone has any thoughts as to that scenario, I am very interested in hearing about it.
USB support: This will *not* be mountable under USB. Unfortunately you are still limited to transfering the data from a computer to the B&N internal storage or SDcard first, then moving the data internally. The problem that I see with this is similar to my understanding of the galaxy nexus situation, where the system can't unmount its /data partition and let the USB host take over. Another alternative to this could be to write an image file and mount that over usb (I've done this on my Evo, it worked so-so). Problem with that is that it really wouldn't grow/shrink with the storage. I suppose you could do some shell trickery and pipe it through gzip somehow, but that wouldn't help very much.
Let me know what you think and if you have any ways to improve this.
UPDATE: Persistance:
To make this persistant across reboots, run these commands as root:
1) mount -o rw,remount -t ext4 /dev/block/platform/mmci-omap-hs.1/by-name/system /system
2) echo mount -o remount,rw -t rootfs rootfs / >> /system/bin/clrbootcount.sh
3) echo mkdir /mnt/internal >> /system/bin/clrbootcount.sh
4) echo busybox mount -o bind /data/usrdata /mnt/internal >> /system/bin/clrbootcount.sh
5) echo mount -o remount,ro -t rootfs rootfs / >> /system/bin/clrbootcount.sh
All this does is put the following at the end of clrbootcount.sh
mount -o remount,rw -t rootfs rootfs / #Remounts root as RW. Root is regenerated at each reboot, so /mnt/internal is never going exist on a fresh startup
mkdir /mnt/internal #make /mnt/internal, see above
busybox mount -o bind /data/usrdata /mnt/internal #Binds the directory
mount -o remount,ro -t rootfs rootfs / #remounts root as RO. Unsure if this is necessary, but since it runs as RO, its probably better safe than sorry.
Thanks to eded333 for mentioning a good place for the script.
Click to expand...
Click to collapse
I was the one who wrote the script gameman. >.>'
Very nicely done.
Does Android possess a fstab? If so, could these changes (also) be made there and still be persistent?
this is a good work around
Am I understanding this correctly in that if I follow these guidelines I can move my data over to the Barnes and noble alotted storage that we were complaining about not having available?
Sent from my Nook Tablet using Tapatalk
downsay said:
Am I understanding this correctly in that if I follow these guidelines I can move my data over to the Barnes and noble alotted storage that we were complaining about not having available?
Sent from my Nook Tablet using Tapatalk
Click to expand...
Click to collapse
That is correct, from what I understand as well.
Sent from my BNTV250 using Tapatalk
liquidzoo said:
Very nicely done.
Does Android possess a fstab? If so, could these changes (also) be made there and still be persistent?
Click to expand...
Click to collapse
From what I could tell, it does, but its not the normal /etc/fstab. It looks like they have a daemon or something that mounts the sdcard and the media (1gb) drive. When I first looked at its version of the fstab, it looked like it only took a block device, which doesn't quite work for the directory binding.
downsay said:
Am I understanding this correctly in that if I follow these guidelines I can move my data over to the Barnes and noble alotted storage that we were complaining about not having available?
Click to expand...
Click to collapse
Yes that is correct. You still cannot mount it under USB, however. If you have some other way of getting the files there, however, its open as an option. I've been using swiFTP (in the market) to do that. Could also copy and move from the media/sd cards that do mount to the PC, but thats a two step process. I've thought about getting MTP setup so that you can see that folder via USB, but haven't really had a chance to look into how that would work.
*Note, when using swiFTP and other programs more than likely, you may get some file permissions errors or other odd errors about corrupt files. These are just the file permissions that the program defaulted to, and can be fixed by doing a 'chmod -R 777 /mnt/internal/'. Don't have this problem on sdcard or media because they are just FAT32 formatted, which don't support permissions.
Trying to understand ...
gameman733 said:
I posted this in the nook touch forum by mistake. Please read below and let me know what you think.
Click to expand...
Click to collapse
I don't understand the purpose of the mounts. Why not just create /data/usrdata and put your stuff in there?
I know /data has "access-only/no-read" access for non-system apps, but anything in /data/usrdata/ should be visible (and no need to modify clrbootcount.sh).
If you need "/mnt/internal" (I don't see the need for that either), why not just use a soft link (which is permanent)???
The primary reason for using the mounts was that I was originally planning on trying to mount it in a way that would ignore file permissions, but didn't know at the time that you can't do that with a bind mount. Using a simple link would be just as effective in this case.
However.. / is Read only. Even when remounted read-write, this filesystem is actually regenerated every boot. So nothing in /mnt would stay past the next restart.
The purpose for having it in /mnt (could have been anywhere, I suppose, but it seemed a little more appropriate) was for apps that can't browse /data. For example, gameboid and related programs would get to /data and show nothing, because you can't browse it as a non-rooted app. Having a symlink or bind mount elsewhere in the filesystem where they can browse helps with that. The alternative was to remove the no-browsing permissions from /data. I didn't feel comfortable with doing this, however, as I'm sure there are some security risks to doing this. It probably isn't a big deal, but since we have the tools to do it while maintaining those existing permissions, why not go ahead and do that?
Is there a solution that does not require being rooted?
[I was gonna start a thread about this 1.0 GB vs 16GB issue. Glad someone
beat me to it. ]
A day or two ago, I side-loaded a couple of movies, each about 400-MB in size,
and was surprised to notice that I had only 20% of my 1.0GB remaining.
I haven't 'bitten the bullet', and got brave enough to 'root' my Nook yet.
(Still not sure yet whether my wife will keep it, and it's an XMAS-gift for her.)
But, I'm quite fluent in Linux, so if we DO keep it, I'll definitely get around
to doing the 'root'.
Meanwhile, if anyone does find a way, without rooting, to re-allocate these
built-in assigned storage quotas, please post it in this thread.
Cheers...
gameman733 said:
The primary reason for using the mounts was that I was originally planning on trying to mount it in a way that would ignore file permissions, but didn't know at the time that you can't do that with a bind mount.
Click to expand...
Click to collapse
To solve this issue I've compiled fuse kernel module and bindfs userspace utility. Bindfs is similar to "mount -o bind" but can override permissions and ownerships. I can share how-to instruction and compiled binaries if you want
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?
Thanks!
CelticWebSolutions said:
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?
Thanks!
Click to expand...
Click to collapse
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes
mount -o ro,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify ro
Thank you!
hwong96 said:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes .....
Click to expand...
Click to collapse
I don't have this tablet but a phone with similar problem.
this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.
I get this message:
error
"the item "system" is read only"
I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.
I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.
very annoying...
Jack_Rover said:
I don't have this tablet but a phone with similar problem.
this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.
I get this message:
error
"the item "system" is read only"
I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.
I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.
very annoying...
Click to expand...
Click to collapse
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. Anyway, since you have asked I'll answer. The mount point for /system is different on each phone model. There is no one standard /system mount point. On the Nook Tablet and Nook Color it is mmcblk0p8. On your device it is different, so the command you tried will not work.
You need to find out what the /system mount point is for your phone.
Open terminal from phone and type su.
Press enter.
At the # prompt type cat /proc/mtd
Press enter.
Look at the output on the screen and see what the mount point is for /system.
A the the # prompt type mount -o rw,remount -t ext4 /dev/block/enteryoursystemmountpointhere /system
Note: replace enteryourmountpointhere with your mount point from the previous step.
Change /system to ro when done. Hope this works for you.
Also download root checker app to ensure you rooted properly.
hwong96 said:
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. ......
Click to expand...
Click to collapse
thanks for your responce.
with that "cat ..." I got : "no such file or dir"...
I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /[email protected] /system
but no success, " system read only" stays, and no change.
Jack_Rover said:
thanks for your responce.
with that "cat ..." I got : "no such file or dir"...
I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /[email protected] /system
but no success, " system read only" stays, and no change.
Click to expand...
Click to collapse
Did you use the root checker app to verify for proper root?
hwong96 said:
Did you use the root checker app to verify for proper root?
Click to expand...
Click to collapse
yes.
I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.
I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).
somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.
MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".
maybe kernel related? or boot loader, or .... what?
-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Jack_Rover said:
yes.
I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.
I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).
somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.
MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".
maybe kernel related? or boot loader, or .... what?
-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Click to expand...
Click to collapse
Don't know what else to suggest, except maybe contact Chainfire on G+.
.
Hi,
I've been Google'ing all over and now am really stuck
I have an HTC One with Android 4.2.2 installed on it and the phone is ROOTED
I want to do something really simple however, due to a puzzling Busybox install I keep getting caught out!
So here's the issue; I want to install Archlinux on the phone in a chroot... documentation is here:
<can't post link>
no probs
Though the issue I'm facing is wget can't resolve host, I try nslookup and get the internal loopback address of the phone "127.0.0.1/localhost".
This seems to be due to no resolv.conf file existing in /system/etc... using information described here:
<can't post link>
I attampted:
Code:
mount -o remount,rw -t yaffs2 /dev/block/<output from mount cmd> /system
mount -o remount,rw /system
mount -o rw,remount /proc /system
these seem to work for a while as "mount" shows /system being rw..... only after a while this seems to revert back to ro?
Additionally if I try installing anything like Busybox from Stephen Stericson the phone just crashes and reboots itself?? - using both "normal" and "smart" install methods.
Busybox X seems to work well for the current runtime, however, after reboot it's gone?
I have absolutely no idea how to solve this as I've been reading and reading and reading and the closest thing I came up with is a watchdog timer mentioned on a Sony handset but then if there is such a thing on my HTC how to find the pid to kill it?
Unfortunately standard *NIX commands don't really seem to work well, ie.
Code:
ps aux | grep watch
so I have no idea how to even begin finding it.
I have tried using various GUI apps additionally which also just reboot the phone when checking the "remount /system rw" option.
Has anyone got any advise or suggestions that could help me win the battle??
Many thanks.
.....well I hope this helps someone now but found an app called: HTC One RW which did the trick!
Busybox installed properly, nslookup worked and now running shell script to install Archlinux