This is very weird !
Whenever i open Root Explorer (File Manager), mount my system as r/w and i delete WHATEVER from the system files, when i Power Off and boot or Restart, the file gets back ???
It seems to me, that somehow my HOX is backing up it's files when i restart or power off and boot and they get back.
Oh, and there is a date (time), right ? Well whenever i delete a file and restart or power off and boot - the date (time) changes to when the phone was booted back on.
Help me figure this out, because i do not want certain files.
Thank you in advance.
You're bricked. Sent it to repair service.
Have you tried deleting them from recovery with adb.
Adb shell mount /system
Adb shell rm /system/(path to file you want to erase)
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
Have you tried deleting them from recovery with adb.
Adb shell mount /system
Adb shell rm /system/(path to file you want to erase)
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, i have tried.
Anyway, thank you guys for the help, i fixed my way through by uninstalling BusyBox (i don't know why that worked)
What about this little problem
http://forum.xda-developers.com/showthread.php?t=2206419
Related
I used to use "Root Explorer" on my hero to delete system apps before..doesn't seem to work anymore..
solution??
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
did you mount /system in rw mode? (it's ro by default)
U dont have write access to system partition in normal use if i read the tutorial right. U have to do it with an update.zip (editing the update script) or with adb both u have to do in recovery menu from modaco i think. Tell me if i am wrong.
Sry for my bad english
@cezarL yes I did
@xtcislove I wish u were wrong..seems like pain.. anyway to do it without a pc?
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Damn, you're right. Previously, I had deleted an .apk just to check if it's working, then reinstalled the app right away.
But I just tested now, it looks like after a reboot, the .apk magically reappears, and the application is running as usual
Damn, you're right. Previously, I had deleted an .apk just to check if it's working, then reinstalled the app right away.
But I just tested now, it looks like after a reboot, the .apk magically reappears, and the application is running as usual
Click to expand...
Click to collapse
ye..I'm sure it has something to do with the root limitations Paul mentioned in his rooting guide. hope it'll be fixed soon.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Try this: Boot in recovery menu and try the following commands:
adb remount
adb shell rm /system/app/APP.apk
adb shell rm /data/app/APP.apk
where APP.apk is the filename of the apk with the .apk extention, remember case-sensitive!
for example:
adb remount
adb shell rm /system/app/FriendStream.apk
adb shell rm /system/app/FriendStream.odex
take a look before if your app has a odex or try this: (here u need only one command)
adb remount
adb shell rm /system/app/*FriendStream*
Good luck and have fun =)
Edit: Just find a topic =)
hxxp://android.modaco.com/content/htc-hero-hero-modaco-com/297207/removal-of-apps-via-adb/#entry1124362
(replace hxxp with http)
I'm trying to do these things in windows at the moment. No issues getting in the recovery with the windows scripts. But when I try to open a ADB Shell after I've gone to recovery I can't really do anything with it and the recovery hangs (not controllable with the track pad).
Anyone can tell me what I'm doing wrong?
You're not doing anything wrong, from what I've seen opening a new adb instance on Windows will kill the server created by the .bat file used for recovery... which means the connection to the device is lost. I haven't looked into it further, but it might be fixeable somehow.
Ah I see, so basicly you undo the patched recovery by opening a new session. It does work properly under Linux then? I run ubuntu on my netbook so It's not a big issue anyway. Thanks for the tip, gonna try under linux now!
I'm having the same problems as:
http://android.modaco.com/content/h...co-com/307401/removing-sys-apps/#entry1256015
I removed a load of HTC widgets but I get strange entries on the widget menu. Anyone know how to get rid of these?
Also, I removed Stocks (.apk and .odex), now I get a force close on 'Accounts & sync'. Anyone know how to remove Stocks properly?
Cheers.
After running the bat file to get into recovery, start a new cmd prompt in windows and use again adb-nilezon for shell commands instead of ordinary adb, and it wont be killed.
This has worked for me atleast
blackadder1000 said:
Anyone know how to remove Stocks properly?
Click to expand...
Click to collapse
The best, foolproof, failsafe way is to remove them from the rom before installing it... and remember that some services are still required, weather you use them or not.
But, if a system app is already installed you need to remove:
the apk from /system/app
the data from /data/data/appname
the cache from /cache/dalvik-cache
Do not remove Accounts & Sync...
Thanks for the answer.
I guess now is a good time to bake my own ROM!
blackadder1000 said:
Thanks for the answer.
I guess now is a good time to bake my own ROM!
Click to expand...
Click to collapse
Yep, that's what I do... see my sig...
is there a way to uninstall system apps like FLICKR service?
Maybe via console?
Via ADB with the phone in recovery.
adb shell mount /system
adb ls /system/app
then find the apk file you want to delete and:
adb shell rm /system/app/(app name here).apk
You can also delete the files before you install a new version of the ROM you're using. You can delete .apk files from the ROM.zip file to flash so when you flash it they wont install.
philje123 said:
Via ADB with the phone in recovery.
adb shell mount /system
adb ls /system/app
then find the apk file you want to delete and:
adb shell rm /system/app/(app name here).apk
Click to expand...
Click to collapse
you only have to put yourself in adb shell once,
adb shell
mount /system/
ls /system/app/
rm /system/app/xxxx.apk will do lol
btw roms with the new file overlay system can delete system apps normally now, using a file explorer!! ive done it
AndroHero said:
btw roms with the new file overlay system can delete system apps normally now, using a file explorer!! ive done it
Click to expand...
Click to collapse
sounds great
I use root explorer to do this
sent from my mind to yours using the power of suggestion
I'm in recovery and have no idea how to follow that instructions.
I see my options, don't see what you wrote.
Bump, sry
Sent from my HTC Desire using XDA App
Alright, when I turn my phone on LauncherPro keeps forceclosing on me, and I can't do ****. I just get 'the application LauncherPro doesn't answer', and an option to force close. When I push force close, the same message pops up again, so I can't access my phone. Is there any way I can fix this via adb or something? What I think caused the problem was that I downloaded and adb pushed a LauncherProPlus.apk (don't know the exact .apk name of it) to my phone (extremely stupid, I know).
Also, is there an adb command to view your phones files? Please help me out with this.
Have you tried wiping dalvik from recovery and then rebooting?
If that doesnt work, you could try pushing another launchers apk to /system/app or /data/app.
Or do you have a backup that you can restore?
Sent from my HTC Desire using Tapatalk
Just remove the launcherpro apk again with adb. It's either a normal adb command or you have to use a shell. Make sure you have a other launcher on the phone when doing this.
If this sounds to complicated and you pushed the apk to /system you can reflash your rom without wiping data.
Sent from my HTC Desire using XDA App
mikep99 said:
Have you tried wiping dalvik from recovery and then rebooting?
If that doesnt work, you could try pushing another launchers apk to /system/app or /data/app.
Or do you have a backup that you can restore?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Do you have an adw.apk or something? I'd like to try this first, as I have no recent backup. What do you mean wiping dalvik?
nvm guys, I managed to uninstall LauncherPro by adding a shortcut to installed programs on widgetlocker. I didn't manage to remove it with adb for some reason. Thanks anyways! Appreciate it.
Try wiping dalvik cache through recovery first.
Boot phone with vol down and power. Then choose recovery.
In the advanced menu, there should be the option to wipe dalvik cache.
Reboot.
Sent from my HTC Desire using Tapatalk
Actually, I have one more question. I downloaded this file: http://www.4shared.com/file/EMhprjdn/LauncherPro_Plus_v083.htm and pushed it to my /system/app using ''adb push file name and location /system/app''. Now I can't find any way to delete it, doesn't work with any file manager, neither do I have any adb command. This is a problem because as long as I have this file in my /system/app, I obviously can't use LauncherPro downloaded from the market. Anyone know how?
You need to do...
adb remount
adb shell
cd /system/app
rm launcherproplus.apk
This is going from what I remember. Check the apk name also.
You can do
ls -al before the rm command to list the files in the directory.
Sent from my HTC Desire using Tapatalk
mikep99 said:
You need to do...
adb remount
adb shell
cd /system/app
rm launcherproplus.apk
This is going from what I remember. Check the apk name also.
You can do
ls -al before the rm command to list the files in the directory.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks a bunch, but when I do ls -al, it says the launcherpro.apk name is ''LauncherPro Plus v0.8.3.apk''. An .apk isn't supposed to have spaces I guess? Anyway, when I type in rm LauncherPro Plus v0.8.3.apk I get:
# rm LauncherPro Plus v0.8.3.apk
rm: can't remove 'LauncherPro': No such file or directory
rm: can't remove 'Plus': No such file or directory
rm: can't remove 'v0.8.3.apk': No such file or directory
Can you try putting the apk name in quotes?
rm "xxxx.apk"
Sent from my HTC Desire using Tapatalk
No, that didn't work either... damn
Tried single quotes? rm 'Xxx xx.apk'
Sent from my HTC Desire using Tapatalk
When I tried that I got:
# rm 'LauncherPro Plus v0.8.3.apk'
rm: can't remove 'LauncherPro Plus v0.8.3.apk': Directory not empty
At least seems like a step forward
And you're booted into recovery?
Also, try putting
su
Before issuing the command.
Sent from my HTC Desire using Tapatalk
mikep99 said:
And you're booted into recovery?
Also, try putting
su
Before issuing the command.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Guess like this; su rm 'LauncherPro Plus v0.8.3.apk'
but that gave me permission denied.
I tried booting into recovery earlier, but when I did that ''adb remount'' didn't work.
btw, i really appreciate all your help. thanks a lot mate
Ok, you need to be in recovery.
There's an option in one of the menus to 'mount system' - choose that.
Then try
adb shell
cd /system/app
rm 'xxxxxx.apk'
You wont have access to delete from /system while your phone is booted as I don't think you're S-OFF.
Sent from my HTC Desire using Tapatalk
It worked! Thank you so much! You literally saved my day!
No problem mate, happy to help
Might be worth taking a backup for the future
Sent from my HTC Desire using Tapatalk
Will definitely do that!
Hi Guys,
I am having pretty much the exact same problem as CH3Z, however i'm having problems locating LauncherPro.apk (free ver).
I've tried using the ls -al command and it doesnt show up there so i'm stuck @ the moment on what to do. I understand that i need the exact name of the apk but i dont know where it is. Any help would be appreciated.
Am running SuperNova Gingersense ROM.
I have rooted my HTC One X and want to copy files in /system/xbin folder. My phone shows S-ON. And Eclipse is not able to copy files to /system and adb push from shell is also not working. Is there a way I can copy files to /system/xbin?
I am running stock ROM.
My phone is NOT associated with any vendor.
adb remount
adb push filename /system/xbin
Sent from my HTC One X
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
realunited123 said:
adb remount
adb push filename /system/xbin
Sent from my HTC One X
Click to expand...
Click to collapse
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Additional Question
treebill said:
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
KillerTheLord said:
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Click to expand...
Click to collapse
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
KillerTheLord said:
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
Click to expand...
Click to collapse
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
realunited123 said:
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
Click to expand...
Click to collapse
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
KillerTheLord said:
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
Click to expand...
Click to collapse
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
realunited123 said:
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
Click to expand...
Click to collapse
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I think this app does exactly what you want :
http://forum.xda-developers.com/showthread.php?t=1687590
realunited123 said:
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
Click to expand...
Click to collapse
Well this didn't work either. I hope to switch to some other ROM in future(I hate HTC Sense ). But as of now Root Explorer did the job. I mounted my sdcard and copied files to it and used Root Explorer to move files to /system and then changed permissions.
Thanks for help it really made it easy .
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
NikMel said:
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
Click to expand...
Click to collapse
The problem was not accessing the device using ADB. The problem was I was not able to write to root system. ES Explorer and Root Explorer both did the job for me. I will be putting the final instructions for the process(detailed ones) soon.
Instructions onw how to copy files to root file system on HTC One X with S-ON
1) Unlock and Root your phone. Follow instructions below
http://www.youtube.com/watch?v=gIeq8Jx28cs
and then
http://www.youtube.com/watch?v=80lMHUgxwww
2) Install ES Explorer(File Manager) Link :- https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3) Connect device to computer(even if it is not recognized by ADB/Computer)
4) In Phone select Disk drive option. Now the phone's storage will be mounted on your computer as removable device.
5) Copy the files you want to send to phone's root system to any folder here.
6) Change phone's mode to charge only and wait for 2-3 secs(let phone remount sdcard)
7) Open ES Explorer and open menu(those 3 dots at bottom and select Settings)
8) Tick the following options
Up to Root
Root Explorer
Mount File System
9) A dialog box for permission will open Grant it.
10) Now copy files from /sdcard/<Folder where u put files> to where ever you want o copy files to.
11) Long press on file to change permissions and stuff.
Post here if you are stuck someone will surely help you.
Hello,
Quick noob question. Today I was experimenting with my phone. I decided that I wanted to push an apk through adb (without much experience on adb). I did this by
Code:
adb remount
adb shell chmod 644 /system/app
adb push .apk/system/app
adb push (a lib file).so /system/lib
adb reboot
Since then my phone has been stuck on boot loop. I'm pretty sure maybe it's because I forgot to mount perhaps? Again, I am new to this. Also I've tried mounting system and data through recovery 4ext. Didn't help.
Can anyone explain what I did wrong? Or fix my problem? Thanks!
EDIT: Fixed the problem by flashing another rom, but would like to learn what I did wrong though. Thanks
To install an app, you need to use 'adb install path/to/app.apk'.
Sent from my HTC Vision using xda app-developers app
OriginalGabriel said:
To install an app, you need to use 'adb install path/to/app.apk'.
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
though I'm assuming he wanted to install it as a system app, in which case I would have rebooted into recovery, mounted /data and /system and moved the already installed app from /data/app/ to /system/app/ to make it a system app. (and made sure the appropriate chmod permissions were set). Then rebooted after that was done.
Shouldn't be messing with the /system partition while the phone is booted live.
kbeezie said:
though I'm assuming he wanted to install it as a system app, in which case I would have rebooted into recovery, mounted /data and /system and moved the already installed app from /data/app/ to /system/app/ to make it a system app. (and made sure the appropriate chmod permissions were set). Then rebooted after that was done.
Shouldn't be messing with the /system partition while the phone is booted live.
Click to expand...
Click to collapse
Yes that was my intended purpose. Thanks.
My guess is you broke it by chmod'ing /system/app.
Making it completely not-executable would've stopped the phone from loading any system apps.
-Nipqer
Nipqer said:
My guess is you broke it by chmod'ing /system/app.
Making it completely not-executable would've stopped the phone from loading any system apps.
-Nipqer
Click to expand...
Click to collapse
+1
I think you want something like "chmod 644 /system/app/*" The difference is the /* at the end. Your original command made the directory inaccessible. The new command just changes the files inside. The actaul directory should have 755 permissions - "chmod 755 /system/app" without the /* at the end.