I have rooted HTC Desire and i tried to remove system app in many ways but nothing worked. Pls give any advice how can i done this.
First i tried with Root Explorer, i mounted R/W mode i deleted the app, the app is deleted from /system/app but present in menu and when i restart the phone it comes back in /system/app
Second i tried with Terminal Emulator: "#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" "#rm /system/app/appname.apk and i got the same result again :\
Third i tried with Titanium Backup Pro, when i Uninstall the app i got the same result but when i try to freeze it that's the only way i can remove from the menu :\
Thanks
Root Explorer only works if you're S-OFF
Easiest way, download the Android SDK and use adb in Recovery to remove them
Remove the apps from the ROM before flashing it?
Be carefull as removing certain apps can make the ROM unstable.
Sounds like the OP has only rooted and isn't using a custom ROM, hence my suggestion
Otherwise, yes, download a custom ROM and remove what you don't want prior to flashing
EddyOS said:
Sounds like the OP has only rooted and isn't using a custom ROM, hence my suggestion
Otherwise, yes, download a custom ROM and remove what you don't want prior to flashing
Click to expand...
Click to collapse
I've recently come across two very interesting Windows apps which make the process easy.. Android Commander and QtADB...Both are GUI frontends for ADB, so once rooted, removing it should be easy in these. However, I believe that some may be removable only in Recovery mode, unless you have S-OFF
My devise is rooted and i use custom rom, Oxygen 2 atm but its not S-OFF, how can i S-OFF? I used unrEVOked to root my phone.
Thanks
v.pakard said:
My devise is rooted and i use custom rom, Oxygen 2 atm but its not S-OFF, how can i S-OFF? I used unrEVOked to root my phone.
Thanks
Click to expand...
Click to collapse
With Alpharev
Second i tried with Terminal Emulator: "#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" "#rm /system/app/appname.apk and i got the same result again :\
Click to expand...
Click to collapse
Did you boot to clockwork recovery first? You must and then run
adb shell
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
rm anythingyouwant.apk
rm anythingyouwant.odex
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
reboot with trackball
This is how I do it in linux. You can boot with live distro linux, connect your desire and start console. I think it should work. I do it from virtualbox.
Thanks alot, S-OFF was the problem, my phone was rooted but not S-OFF. Now everything is fine.
Thanks,
pakard
Related
first time posting to these forums and would like to contribute my findings i was able to gain root on the uscc htc desire in adb using some other guides for the evo 4g unlock. but now i need some help on how to get the modified su in the right place to make this work for the apps. these are the steps i used to gain temporary root.
1) installed android sdk to get adb
2) set up the phone in debug mode
3) downloaded the rageagainstthecage-arm5.bin file(attached)
4) ran this from the sdk folder containing adb.exe
Code:
adb.exe push C:/PATH/TO/FILE/rageagainstthecage-arm5.bin /data/local/tmp
adb.exe shell
cd /data/local/tmp
chown 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
5) adb shell will exit retype adb.exe shell and now you have root
this is as far as i have got so far now i need to know where to put su which i could not find in /system/xbin
also i am new to the android scene so sorry if this is a bad question, but if i were to flash a recovery image of the gsm desire to my cdma would this work to enter adb in recovery mode or would this brick my phone, i didnt know if the recovery affected that or if that was the rom.
I think you need to put su and Superuser.apk on you sdcard (adb push file /sdcard/)
Then
in your su shell prompt
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/su > /system/bin/su
chmod 06755 /system/bin/su
Please let us know if this works.
I hope this works out!
Sent from my USCC HTC Desire using XDA App
i found out that this command doesnt actually make the system directory writeable
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
and running it a second time causes the device to reboot.
any sugetions to make it writable, im willing to work on this, but like i said i have no experience with android although i am very familiar linux.
You are aware that while booted into Android the /system is not writeable?
You have to boot into recovery mode to do this.
i am now, i tried the method for the incredible but it seems to not run adb on bootup at least after about 15 tries it didn't work, any suggestions? is there a way to flash the recovery without effecting the radio or rom because there isn't any roms for this phone as of yet, or could you point me in the right direction to start my research on how to write a rom? would it be the same as rolling your own linux distro?
also though this to be worth mentioning there seems to be no su file currently on the phone.
i got some time this morning to dig around in the payload-update.zip files for the incredible and was wondering if i could use this to install su because it looks like it doesn't flash anything (atleast looking at the script it looks like it doesn't, i cant say that for the binary file what does that do?) just wondering if there would be any adverse affects by applying this in recovery.
It might be worth talking to AmonRA, or Koush (I believe he works on Clockwork Mod) for a custom recovery. As for installing superuser, you could try the unrevoked team. (unrevoked.com) I wish I knew more in terms of development to help but I hope this leads you in the right direction.
blitz2190 - Here is a link to Superuser.apk and su. Link
I think you need to put su and Superuser.apk on you sdcard (adb push file /sdcard/)
Then
in your su shell prompt
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/su > /system/bin/su
chmod 06755 /system/bin/su
I am very interested to know how this works out. If you need anyone else to help test things let me know. I am not a linux buff, but i can follow commands...
CreepingDeath said:
I am very interested to know how this works out. If you need anyone else to help test things let me know. I am not a linux buff, but i can follow commands...
Click to expand...
Click to collapse
Do you have a USCC Desire?
northmendo said:
Do you have a USCC Desire?
Click to expand...
Click to collapse
Yes I do, and I am willing to help out where I can.
CreepingDeath said:
Yes I do, and I am willing to help out where I can.
Click to expand...
Click to collapse
A couple q's fof you.
Do you have a Mac or PC?
Do you have adb installed?
I will help if I can. I have the phone and a Mac and don't have adb installed.
Sent from my USCC HTC Desire using the XDA App
dhh93 said:
I will help if I can. I have the phone and a Mac and don't have that apply.
Sent from my USCC HTC Desire using the XDA App
Click to expand...
Click to collapse
Cool first install adb. Follow these instructions to install it on Mac.
HERE
Ok doing that right now.
dhh93 said:
Ok doing that right now.
Click to expand...
Click to collapse
Great. I would start by trying the the method from the first post give me about 5 mins and I will post them in a mac friendly format.
Ok will wait on that
http://psfreedom.com/wiki/index.php?title=OpenDesire4.0.4
http://www.ps3hax.net/showthread.php?p=123003
Im trying to install this recovery so i can jailbreak my PS3, but when i try to use unrEVOked, it hangs while pushing the recovery
When i try to use adb on both my phone and my computer it says i have no space!
what should i do?
EDIT:
fastboot erase recovery
fastboot flash recovery recovery.img
sounds like it would work, bu t i dont want to risk that lol
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
SwordOfWar said:
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
Click to expand...
Click to collapse
Alright, thats good to know. Ill look around
http://forum.xda-developers.com/showthread.php?t=770663
"You can only write to system on the desire via adb from recovery."
So i do what? boot into recovery, plug in my phone and adb it again?
flash_image recovery image.img?
Hmm, guess not.
I booted into recovery. Plugged my phone in and did an adb devices. It said one device called recovery
i did mount /sdcard (apparently i dont have to mount it to a location)
i cd'd into thte sdcard and did a flash_image recovery psfMod.img and it said i had no space
I was also looking at this
http://forum.xda-developers.com/showthread.php?t=770663
but i still cant get it to work.
do i have to have s-off?
Hi All,
Sorry if this is question may sound stupid but I have searched for so long and I couldn't find any solution.
What I want to do is just replace my boot screen for Samsung Galaxy S. I found out that it is not easy. So I rooted my phone using the one click root that I found here which is SuperOneClick.
So once rooted I immediately tried the following:
Code:
C:\sdk\android-sdk-windows\platform-tools>adb remount
I got an exception saying:
Code:
C:\sdk\android-sdk-windows\platform-tools>adb remount
remount failed: No such file or directory
So I tried the following:
Code:
C:\sdk\android-sdk-windows\platform-tools>adb shell
$ su
su
# mount -o remount,rw /dev/block/stl9 /system
mount -o remount,rw /dev/block/stl9 /system
exit
$exit
C:\sdk\android-sdk-windows\platform-tools>adb push bootanimation.zip /system/media/bootanimation.zip
In which I got the following exception:
Code:
C:\sdk\android-sdk-windows\platform-tools>adb push bootanimation.zip /system/media/bootanimation.zip
failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': Permiss
ion denied
So I tried searching again and some say that I have to install busybox. So what I did is I installed it in my Samsung Galaxy S which has a SpeedMod kernel and tried again using the command above.
As of the moment I tried it again to no avail. My Usb debugging is turned on so I don't really know the reason why I'm not able to push.
I appreciate any help.
Thank you.
if you used speedmod kernel, theres no need to apply SuperOneClick
because speedmod already has builtin Lagfix and root, options are accessible by booting into the Recovery Menu
How to root
Q: I followed the procedure above but my bootanimation doesn't work?
A: In version K9 and earlier, bootanimation only works if you have root / superuser installed. Install superuser from the Recovery Menu > ULK > Install Superuser. Later versions fix this problem.
Click to expand...
Click to collapse
http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-speedmod-kernel-faq.html
specialex said:
if you used speedmod kernel, theres no need to apply SuperOneClick
because speedmod already has builtin Lagfix and root, options are accessible by booting into the Recovery Menu
How to root
http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-speedmod-kernel-faq.html
Click to expand...
Click to collapse
I just did your suggestion and installed the latest speedmod but when I do the command that I posted above still gives the same error in Windows, any other suggestion? many thanks.
Just use a file tool and copy it to data/local.
It need to use root.
**Using my own JPU kernel, z4mod, 339MB Ram and ext2 filesystem**
Hey guys,
I flashed the 4.0.4 factory image today and was wondering how i can get root access without flashing a custom recovery since i want to stay stock atm.
I already tried the method i usually used (on 4.0.1 & 4.0.2)
Sorry can't post links... it's the normal method with fastboot and adb
and another method where you fastboot cwm recovery and then use adb commands but both didn't work for me
I can't post links so that's what i did there:
Temporarily boot into the Clockwork Mod Reovery using fastboot (on the computer)
fastboot boot cwmt-recovery-5.8.0.2.maguro.img (or whatever version you are using)
Mount /system using Clockwork Mod (on the phone):
mounts and storage -> mount /system
Chmod su using adb to turn on the setuid bit (on the computer)
adb shell chmod 6755 /system/bin/su
adb shell chown root:root /system/bin/su
adb shell ls -l /system/bin/su (permissions should now be -rwsr-xr-x)
Reboot. Super user should be working as expected (and your stock recovery is still intact)
Anyway,
I already spent much time to search on this forum and google so i was wondering if anyone knows any method which i could use.
You can root using this toolkit http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Mojochief said:
Hey guys,
I flashed the 4.0.4 factory image today and was wondering how i can get root access without flashing a custom recovery since i want to stay stock atm.
I already tried the method i usually used (on 4.0.1 & 4.0.2)
Sorry can't post links... it's the normal method with fastboot and adb
and another method where you fastboot cwm recovery and then use adb commands but both didn't work for me
I can't post links so that's what i did there:
Temporarily boot into the Clockwork Mod Reovery using fastboot (on the computer)
fastboot boot cwmt-recovery-5.8.0.2.maguro.img (or whatever version you are using)
Mount /system using Clockwork Mod (on the phone):
mounts and storage -> mount /system
Chmod su using adb to turn on the setuid bit (on the computer)
adb shell chmod 6755 /system/bin/su
adb shell chown root:root /system/bin/su
adb shell ls -l /system/bin/su (permissions should now be -rwsr-xr-x)
Reboot. Super user should be working as expected (and your stock recovery is still intact)
Anyway,
I already spent much time to search on this forum and google so i was wondering if anyone knows any method which i could use.
Click to expand...
Click to collapse
Download this file to /sdcard, boot CWM like you posted, and then, once in CWM, flash the file you downloaded. Done.
EDIT: All that file does, is copy su and Superuser.apk to your device and set the appropriate permissions.
You can root using this toolkit http://forum.xda-developers.com/show....php?t=1392310
Sent from my GNex {GSM} T-Mobile
Click to expand...
Click to collapse
Thanks I'll try it, but I'm actually not a big fan of one click thingies where you don't know what you're doing.
Download this file to /sdcard, boot CWM like you posted, and then, once in CWM, flash the file you downloaded. Done.
Click to expand...
Click to collapse
Thank you I really prefer that over toolkits!
Mojochief said:
Thank you I really prefer that over toolkits!
Click to expand...
Click to collapse
This is what that file does:
Mounts the system parition
Copies Superuser.apk to /system/app
Copies su to /system/xbin
Sets permission on Superuser.apk to 0644
Sets permission on su to 06755
Sets a symlink for /system/xbin/su to /system/bin/su
Unmounts the system partition.
This is what that file does:
Mounts the system parition
Copies Superuser.apk to /system/app
Copies su to /system/xbin
Sets permission on Superuser.apk to 0644
Sets permission on su to 06755
Sets a symlink for /system/xbin/su to /system/bin/su
Unmounts the system partition.
Click to expand...
Click to collapse
Just tried it and it worked just fine
And thank you for the explanation!
So actually you could do it w/out booting cwm just with fastboot+adb right?
Mojochief said:
[snip]
So actually you could do it w/out booting cwm just with fastboot+adb right?
Click to expand...
Click to collapse
No. You need root access on boot to execute those commands. CWM boots android with root access by default, so this allows you to execute the commands. If you do not use CWM, you can use any other boot image that gives you root access on boot.
No. You need root access on boot to execute those commands. CWM boots android with root access by default, so this allows you to execute the commands. If you do not use CWM, you can use any other boot image that gives you root access on boot.
Click to expand...
Click to collapse
Yeah i meant with another boot image which gives you root access, like the one i used to root the earlier builds.
Mojochief said:
Yeah i meant with another boot image which gives you root access, like the one i used to root the earlier builds.
Click to expand...
Click to collapse
Yes, you can use another insecure boot image, but it needs to be a 4.0.4 compatible kernel. Older ones won't work.
Sent from my Galaxy Nexus using Tapatalk
Hi guys, as I wanted to change a permissions in my /system/lib directory, I accidentally disabled the "Execute"-Permission for my /system/lib folder. I know, im stupid as ****. I usually am not that dumb.
Currently, my G3 (855, 32gb) is only booting in recovery. I'm looking for a solution to change the permissions of the /system/lib folder, but it seems impossible.
Thanks for every single advise!
Use adb with recovery booted and then:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 644 /system/lib
It should work
oposiasty said:
Use adb with recovery booted and then:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 644 /system/lib
It should work
Click to expand...
Click to collapse
Thank you for your answer, but I think I'm not able to configure it via ADB. It isn't recognized in recovery, and when I'm putting it into that ADB Update mode, ADB just says "error: closed"...
RichiN said:
Thank you for your answer, but I think I'm not able to configure it via ADB. It isn't recognized in recovery, and when I'm putting it into that ADB Update mode, ADB just says "error: closed"...
Click to expand...
Click to collapse
wich recovery do you have? TWRP or stock?
KingOfDope said:
wich recovery do you have? TWRP or stock?
Click to expand...
Click to collapse
Thank you too. I had stock recovery installed. I had BusyBox installed and could have changed the permissions via script, but I decided to
flash stock and unlock my bootloader afterwards. Everything went fine, so we can consider this thread as solved.