Deleting core applications? - Wildfire Q&A, Help & Troubleshooting

So, I'm trying to delete core applications such as Camera (because, I have a better one) with Terminal. Not success.
I'm typing that:
Code:
su
mount -o rw,remount /system
rm -r /system/app/Camera.apk
it says that:
"rm: can't remove '/system/app/Camera.apk': Directory not empty".
What should I do? Thanks in advance.

try to use RE.

Root explorer didn't help.

Related

Enabling the read/write on fonts folder

Hi everyone,
I have been trying to enable the read and write on fonts folder by chmod
Unfortunately, nothing worked for me
everytime I write chmod 777 system/fonts/ on CMD it gives me an error message saying read only.
My device is rooted.
would appreciate any help
Thanks & Regards
Try adding su before chmod
For example
su chmod 777 directory
Thanks for your help C45hY
But that didn't work also
it says Permission denied
any clues???
/system is mounted read only
I know mopodo
How can I change it to read/write?
mopodo said:
/system is mounted read only
Click to expand...
Click to collapse
Exactly!
What you need to do is go to the terminal and type in the following commands:
Code:
su # gain root shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system #remount the /system partition read/writte
regards

[Q] Install busybox

Anyone knows how to install busybox?
I've tried to follow some guides but ends up with:
Code:
215:Desktop ricardo$ adb push busybox /data/local
580 KB/s (1083568 bytes in 1.823s)
215:Desktop ricardo$ adb shell
$ su
# cd /system/xbin
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cat /data/local/busybox > busybox
cannot create busybox: not enough memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# dd if=/data/local/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Out of memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# ./busybox cp /data/local/busybox /system/xbin
cp: can't create '/system/xbin/busybox': Cannot allocate memory
same here. cannot write to rw-mounted /system.
sucks
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
I have the same problem
ricardoft said:
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
Click to expand...
Click to collapse
What should I do with your files?
Nobody has a solution to this?
I don't think this is a memory issue though, .. added 512mb swap and still it claimed to be out of memory, ..
also I figured maybe hd space .. however when i ln /data/local/tmp/busybox to /system/xbin it had the same error.
I both tried ln from the system and ln from busybox both had same result.
It's not a memory problem! In order to install it you have to be in recovery mode.
Try:
While in recovery mode use adb to connect to our phone. Now transfer the zip file (busybox.zip) to your phone and install it via clockwork recovery -> install zip file -> select my zip file.
can anyone post the proper busybox file cause for some reason the file signature verification failed.
adb push busybox-signed.zip /sdcard/busybox-signed.zip
rebooted phone held down volume button while booting ..
choose recovery, ..
choose install zip from sdcard..
then i see a lot of no and one yes .. so i choose yes but the installation is aborted.
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
it has error during installation at line 4 with your busybox.zip
somethinf like can not chmod
(rooted buzz with stock rom)
Elibongo said:
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
Click to expand...
Click to collapse
Do what this guy said.
titanium install in /sdcard busybox, not in /system/bin (xbin) , so it is not usuable by other apps
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
kevin2516 said:
Do what this guy said.
Click to expand...
Click to collapse
you have read my mind especially since that isn't free software.
hellysmile said:
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
Click to expand...
Click to collapse
i think you need to create aliases however why install it in xbin anyways then, .. if you need to create aliases or links in bin.. ?
example
$ ln -s /data/local/tmp/busybox ls
$ ./ls
if it is in a path that is included in PATH executing a command will auto look for it in all directories defined in PATH env so basicly you could just create all the directories under /data/local/tmp/bin
and just then append that to PATH env echo $PATH then append :/data/local/tmp/bin to it and busybox should work as well.
Ofloo said:
you have read my mind especially since that isn't free software.
Click to expand...
Click to collapse
titanium backup is free software... look on the market, there's a free version and a donate version.
i have aliases in /system/xbin
they was created after busybox --instal -s
but in system allready exists some commands like ls => i want to use ls from busbox, not from system
and terminal emulator dont anderstand ^[ likes bindings
is there a definitive way to do this. There seems to be no clear way of doing it.
matpol said:
is there a definitive way to do this. There seems to be no clear way of doing it.
Click to expand...
Click to collapse
Maybe this helps:
fang0654 said:
To install:
1) extract and push busybox to your sdcard, reboot into recovery
2) mount /system
3) if you don't have /system/xbin (you should), create it
adb shell:
# mkdir /system/xbin (if necessary)
dd if=/sdcard/busybox of=/system/xbin/busybox
cd /system/xbin
chmod 755 busybox
./busybox --install .
4) reboot and done
OPTIONAL - before rebooting replace the busybox installed by the root process in /system/bin
1) mv /system/bin/busybox /system/bin/busybox.bak
2) cp /system/xbin/busybox /system/bin/busybox
Click to expand...
Click to collapse
from this site: http://forum.xda-developers.com/showthread.php?t=702634
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
matpol said:
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
Click to expand...
Click to collapse
You dont have to extract the binary into a folder, just extract the busybox file direct on your sdcard. Than the dd command should work, on my phone it works fine.
But if not, does the command cat in the adb shell work?
If so, try istead of the dd comand:
Code:
mount /sdcard
cat /sdcard/busybox > /system/xbin/busybox
And remember to start your wildfire in the recovery mode, that was the mistake I had done...

[MOD] Poor streaming performance-AAC audio fix

There was one hack i really enjoyed.....from my Nexus is the Fix poor AAC streaming performance http://forum.xda-developers.com/showthread.php?t=737111&highlight=stagefright
Code:
C:\Users\Mikey\Desktop>adb shell
$ su
su
[COLOR=Red]Watch your phones screen for superuser asking for permission, it you have not granted it in the past.[/COLOR]
# busybox mount -o rw,remount /system
busybox mount -o rw,remount /system
# cp /system/build.prop /sdcard/
cp /system/build.prop /sdcard/
[COLOR=red]I use root manager at this time to edit the file while on the phone, long press on the file and open in text editor.[/COLOR]
From: [B]media.stagefright.enable-player true[/B]
To: [B]media.stagefright.enable-player false[/B]
# cp /sdcard/build.prop /system/
cp /sdcard/build.prop /system/
# busybox mount -o ro,remount /system
busybox mount -o ro,remount /system
# reboot
reboot
C:\Users\Mikey\Desktop>
When the phone reboots run Visionary, for root. http://www.appbrain.com/app/visionary/com.modaco.visionary
In my case i use Enomthers Rom, located here:
http://forum.xda-developers.com/showthread.php?t=806612
In terminal, granting su permission first, then type:
Code:
/data/local/tmp/startrom
Of course you need the proper files in the tmp folder to run Enomthers rom.
can you give info on the changes to prop?! Would like to test this on my nexus and g2 when u get it figured out.
Sent from my T-Mobile G2 using XDA App
Click the link in post 1
Fix poor AAC streaming performance
Click to expand...
Click to collapse
link

ADB Remount not working on AT&T ICS Port

I can't get an adb remount to work so I can push trebuchet launcher as a system app.
I'm able to perform a adb shell
and then # to get su and my phone shows SU granting root permissions
what am I missing?
and please don't say install it as a regular app, because you'll be ignored
martialbob said:
I can't get an adb remount to work so I can push trebuchet launcher as a system app.
I'm able to perform a adb shell
and then # to get su and my phone shows SU granting root permissions
what am I missing?
and please don't say install it as a regular app, because you'll be ignored
Click to expand...
Click to collapse
i had the same problem. you can put the apk on your sd card, then use adb to copy it, but you'll have to mount the filesystem rw still.
to do this:
Code:
adb shell
su
cd sdcard #or wherever the apk is
busybox mount -o rw,remount /dev/block/mmcblk0p24 /system
busybox cp Trebuchet.apk /system/app
reboot
that gets the Trebuchet.apk in the right folder. however, it's still not letting me use it...
i've also ran chmod on the apk and still no go.
I'm pretty sure it's a kernel issue.. Working on it..
funeralthirst said:
i had the same problem. you can put the apk on your sd card, then use adb to copy it, but you'll have to mount the filesystem rw still.
to do this:
Code:
adb shell
su
cd sdcard #or wherever the apk is
busybox mount -o rw,remount /dev/block/mmcblk0p24 /system
busybox cp Trebuchet.apk /system/app
reboot
that gets the Trebuchet.apk in the right folder. however, it's still not letting me use it...
i've also ran chmod on the apk and still no go.
Click to expand...
Click to collapse
adb shell
su
cd sdcard
cd external_sd
busybox mount -o rw,remount /dev/block/mmcblk0p24 /system
busybox cp Trebuchet.apk /system/app
reboot (this still doesn't work on my phone even from shell or app, have to battery pull to restart... bloody annoying)
YOUR AWESOME!!
Used the above commands and it worked perfectly!!
Was able to change to trebuchet launcher after reboot, and was able to add widgets to home screen without it crashing (which when you install trebuchet as a regular app it freezes on adding a widget to home screen)

help me please I cannot modify system files despite having root

i'm on (pixel 2xl) lineageos 16.0 rooted with magisk, i want to add a script in init.d folder but i can't do it, i tried with root explorer but it doesn't work, afwall also can't mount folder for startup script, any solution?
lg_g3_d855 said:
i'm on (pixel 2xl) lineageos 16.0 rooted with magisk, i want to add a script in init.d folder but i can't do it, i tried with root explorer but it doesn't work, afwall also can't mount folder for startup script, any solution?
Click to expand...
Click to collapse
Why? What error do you get?
Try to move/copy something into /tmp folder. It should work if you're rooted (your shell shows # instead of $).
If it doesn't work, maybe you have to remount your system as rw (read and write):
Code:
mount -o rw,remount /
after you made your modifications, mount it as ro (read only) again:
Code:
mount -o ro,remount /
If it still doesn't work, we need to see the error you get (copy and paste into this forum) while moving/coping something into /tmp.
User699 said:
Why? What error do you get?
Try to move/copy something into /tmp folder. It should work if you're rooted (your shell shows # instead of $).
If it doesn't work, maybe you have to remount your system as rw (read and write):
Code:
mount -o rw,remount /
after you made your modifications, mount it as ro (read only) again:
Code:
mount -o ro,remount /
If it still doesn't work, we need to see the error you get (copy and paste into this forum) while moving/coping something into /tmp.
Click to expand...
Click to collapse
i tried with mount -o rw, remount, but it keeps showing me the file system is read only
.
lg_g3_d855 said:
i tried with mount -o rw, remount, but it keeps showing me the file system is read only
.
Click to expand...
Click to collapse
Can you verify you entered that command as root?
Please do the following:
Do this on your computer to enter your devices shell
Code:
prompt_PC:~$ adb shell
Code:
prompt:~$ whoami
This should give you either "shell" or "root"
If it says "shell" do:
Code:
prompt:~$ su
prompt:~#
It will show a # instead of $ if you're root.
If you're already root (or you are now root due to su command), do:
Code:
prompt:~# mount -o rw,remount /
Now it should be writeable and you can do your modifications.
After you finished you need to change it to ro (read only) again:
Code:
prompt:~# mount -o ro,remount /
After that you can exit the shell:
Code:
prompt:~# exit
prompt:~$ exit
(first exits su, second exits shell)
I'm sorry if you already did that but I wan't to be sure you did it correctly.
If this procedere doesn't work, please copy and past your input and output into this forum as this might help to understand what's going on/failing etc.
User699 said:
Can you verify you entered that command as root?
Please do the following:
Do this on your computer to enter your devices shell
Code:
prompt_PC:~$ adb shell
Code:
prompt:~$ whoami
This should give you either "shell" or "root"
If it says "shell" do:
Code:
prompt:~$ su
prompt:~#
It will show a # instead of $ if you're root.
If you're already root (or you are now root due to su command), do:
Code:
prompt:~# mount -o rw,remount /
Now it should be writeable and you can do your modifications.
After you finished you need to change it to ro (read only) again:
Code:
prompt:~# mount -o ro,remount /
After that you can exit the shell:
Code:
prompt:~# exit
prompt:~$ exit
(first exits su, second exits shell)
I'm sorry if you already did that but I wan't to be sure you did it correctly.
If this procedere doesn't work, please copy and past your input and output into this forum as this might help to understand what's going on/failing etc.
Click to expand...
Click to collapse
yes I'm root, output is file system is read only despite adb commands
lg_g3_d855 said:
yes I'm root, output is file system is read only despite adb commands
Click to expand...
Click to collapse
Well, I'm sorry then... I can't help.
Good luck!

Categories

Resources