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...
I moved from an HD2 to the Evo this week (no more TMobile, woot!). I am very familiar with custom WMO ROMS, Hard SPL, blah blah...
I have nearly zero Android development, custom ROM knowledge, etc, however.
I'd like to flash a custom ROM based on the factory, without all the Sprint programs preloaded.
Clearly I need to root; I am on steady ground with that knowledge. After that? Not so clear. There doesn't seem to be a thread with the steps I need to proceed.
Any info would be invaluable, thanks!
(PS - side question: why does Android launch all sort of processes in the background seemingly at random?)
ifiweresolucky said:
I moved from an HD2 to the Evo this week (no more TMobile, woot!). I am very familiar with custom WMO ROMS, Hard SPL, blah blah...
I have nearly zero Android development, custom ROM knowledge, etc, however.
I'd like to flash a custom ROM based on the factory, without all the Sprint programs preloaded.
Clearly I need to root; I am on steady ground with that knowledge. After that? Not so clear. There doesn't seem to be a thread with the steps I need to proceed.
Any info would be invaluable, thanks!
(PS - side question: why does Android launch all sort of processes in the background seemingly at random?)
Click to expand...
Click to collapse
This should be in Q & A.. But unless someone creates a rom with the apps removed. Its easier to just do it yourself.
If you did toasts method of rooting. Boot into recovery and type this
adb remount
adb shell
cd /system/app
ls
This displays all apps on the phone. Do this to delete them.
rm NameOfApp.apk
rm NameOfApp.odex
It is caps sensitive and make sure you type the apk exactly as its written.
Jus10o said:
This should be in Q & A.. But unless someone creates a rom with the apps removed. Its easier to just do it yourself.
If you did toasts method of rooting. Boot into recovery and type this
adb remount
adb shell
cd /system/app
ls
This displays all apps on the phone. Do this to delete them.
rm NameOfApp.apk
rm NameOfApp.odex
It is caps sensitive and make sure you type the apk exactly as its written.
Click to expand...
Click to collapse
any reason adb remount isn't working for me? I do adb devices and my devices is there but when i type adb remount i get "remount faild: Invalid argument"
I started Toasts root directions, placing PC36IMG.zip on the base directory of the SD card. Shut down, loaded with the Vol Down and Power buttons. The bootloader checked the file on the SD card but then stopped on the white screen.
It seems it was supposed to proceed automatically? But I am dropped off with options on the white screen: FASTBOOT, RECOVERY, CLEAR STORAGE, SIMLOCK, and HBOOT USB.
Directions show Vol Up and Down for previous and next and Power for select.
Alright, I resolved this issue. I recopied the file to the SD card and made sure to eject drive before shutting the device down. Seemed to make all the difference! Proceeding with the remainder of Toast's directions now...
p-slim said:
any reason adb remount isn't working for me? I do adb devices and my devices is there but when i type adb remount i get "remount faild: Invalid argument"
Click to expand...
Click to collapse
I'm running in to the same issue...
rgordon3091 said:
I'm running in to the same issue...
Click to expand...
Click to collapse
i fixed it. you have to do this.
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
ls
Getting error trying to remove nascar..
Code:
rm Sprint_NASCAR.apk
rm failed for Sprint_NASCAR.apk, Directory not empty
Any ideas?
That's Linux trying to protect you. Essentially the rm command by default just removes one file at a time.
Try...
rm -r NameOfFolder
...to delete recursively.
Sent from my EVO 4G using Tapatalk
Go see the thread in the apps sub-forum about this. I have a post (#28, I believe) with the exact code to remove the bloatware. You can just copy any paste.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
nick325i said:
Getting error trying to remove nascar..
Code:
rm Sprint_NASCAR.apk
rm failed for Sprint_NASCAR.apk, Directory not empty
Any ideas?
Click to expand...
Click to collapse
you shouldn't have a problem deleting the apk, because an apk is not a directory.
i deleted it without the same message.
p-slim said:
i fixed it. you have to do this.
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
ls
Click to expand...
Click to collapse
'
hmmm i put im adb shell then i got a "#" so i put in "mount /dev/block/mtdblock4 /system"
and i got mount:mounting /dev/block/mtdblock4 /system failed: No such file or directory
so what did i do wrong?
Found the issue. Thanks all
Jus10o said:
This should be in Q & A.. But unless someone creates a rom with the apps removed. Its easier to just do it yourself.
If you did toasts method of rooting. Boot into recovery and type this
adb remount
adb shell
cd /system/app
ls
This displays all apps on the phone. Do this to delete them.
rm NameOfApp.apk
rm NameOfApp.odex
It is caps sensitive and make sure you type the apk exactly as its written.
Click to expand...
Click to collapse
By the way, when I "cd /system/app" and then "ls" I see only NamesOfApps.apk. There are displayed no *.odex files. Is that normal?
thread dead?
IDK if this threads still monitored by anyone, but here's my question: I don't use adb, but I just rused root explorer to locate sprint crap, and added a .bak to the end of all of them to essentially 'disable' them. Is this a safe method? Will Android system waste energy looking for them anymore (they no longer show in app tray, but are they still using resources) ? Thanks much.
scottspa74 said:
IDK if this threads still monitored by anyone, but here's my question: I don't use adb, but I just rused root explorer to locate sprint crap, and added a .bak to the end of all of them to essentially 'disable' them. Is this a safe method? Will Android system waste energy looking for them anymore (they no longer show in app tray, but are they still using resources) ? Thanks much.
Click to expand...
Click to collapse
I was just about to say something similar. I had uninstalled Nascar using Titanium Backup, and the found out that I cant do the 2.2 OTA unless its there. TB didn't have the ability to restore it for some reason, so I got an APK from XDA, and put it in the system/app folder via Root Explorer. Then, I had to reset the permissions to match the other APK's, and it showed up and launched perfectly. Even did an update. Much easier than all that adb stuff, I think.
I used system app uninstaller for a buck on the market.. Easy and all there with the icons for easy to find and delete sprint and gapps.
Sent from my PC36100 using XDA App
scottspa74 said:
IDK if this threads still monitored by anyone, but here's my question: I don't use adb, but I just rused root explorer to locate sprint crap, and added a .bak to the end of all of them to essentially 'disable' them. Is this a safe method? Will Android system waste energy looking for them anymore (they no longer show in app tray, but are they still using resources) ? Thanks much.
Click to expand...
Click to collapse
Thats a good way.. If something goes wrong just have to rename.
Sent from my PC36100 using XDA App
Flash this zip and it should remove most of the Sprint apps. It will back them up to /sdx on your SD card so if anything is removed that you want, it will still be there. It's signed to work with RA.
http://grathwohl.me/uploads/android/evo/Sprint-Apps-Remover-signed.zip
I've seen a few people reference my post, but my post was really just trying to ask if anyone knew if, now that I've renamed them, and they don't run, they shouldn't be using up resources? Right, is that correct, or am I wrong in thinkin this?
And thanks cosine83, that's a really helpful post for a lot of people.
Big props to SAINTH for his guide. Some of my guide is a word for word rip off of his guide. I just copied it and played around to get a simpler way to root. It is still temporary but now when you have "SU" you are messing with the ACTUAL files on the device, NOT a copy on your SD card. Also, programs installed in root mode are still on your device when not in root mode.
I wrote this entire post while tethered to my device using this method.
NOTE: IF SOMEONE COULD GIVE ME A RECOVERY TO FLASH, I THINK WE WOULD HAVE PERMANENT ROOT
OK, I am a dev noob... total noob... please no flaming...
Getting Started: (ONE TIME STUFF)
1) Partition your SD card with at least a 300mb EXT3 partition. I Used gparted in Ubuntu. (ubuntu.com ...download the iso, boot as a live cd, install gparted....google for more details)
2) Download and install from Market: Bar Control. I will explain why in a moment.
3) Download and extract visionroot.zip into your tools directory.
4) Use adb to install programs and transfer files to your device:
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a computer with the Android SDK tools installed and working (adb is included with the SDK, so install the sdk and you will have adb. GOOGLE "adb sdk install" for more details):
adb push busybox /data/local
adb push rage /data/local
adb push root /data/local
adb push rsync /data/local
adb push su /data/local
adb install Term.apk
adb install Superuser.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/rsync /data/local/root
5) Run Bar Control and select Terminal Emulator to run in the task bar. Early on, when I was playing around with this rooting method, temp root would just disappear. I found it stays if I use Bar Control. I think since Terminal Emulator is in the task bar, android is less likely to kill it. I did this whole post using tethering without root ever going away.
Ok. SETUP stage is now over. From this point on is how you will get root each time you boot up your phone.
Getting Root:
1) On the phone, open "Terminal Emulator" from the taskbar and type:
cd data
cd local
./rage
Wait for it to say "[+] Forked NNNN childs." then press the back button until you are back at the home screen. It will be slow for a bit.
2) Open "Terminal Emulator" again from the task bar and it should force close. It's ok if it doesn't. Just skip to #3.
3) Open "Terminal Emulator" one more time from the task bar and the prompt should display "#". This is the ROOT prompt! You are almost golden now! Then type:
cd data
cd local
./root
You may get some "Killall: Can't kill such and such" messages. Not a problem.
DO NOT hit the back button. You want terminal to keep running. Hit the Home Button.
YOU NOW HAVE ROOT! Superuser should be working too. We may find that we dont need bar control and terminal running. Let me know and I will change my post.
What I've Used Root For So Far
Some people are questioning the value of root without custom ROM's. Here is what i have used ROOT for on this ROM so far:
1) Wireless Tether - this alone is worth it! The 9-5 version from this page works amazingly on the G2:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=NexusOne
2) Uninstall Crapware - I used Titanium to uninstall Web2Go. What a pile of steamy poop. EDIT: The software MAGICALLY reappears after reboot. I can't wait to crack this phone!
3) Back up with Titanium - Most awesome backup program out there. Needs root to work.
good stuff bro ima try this.
this is all well and good, but the point of rooting is the custom roms, we've had a Temp root since day one, but no reason to root it.
yes but
Dalamak said:
this is all well and good, but the point of rooting is the custom roms, we've had a Temp root since day one, but no reason to root it.
Click to expand...
Click to collapse
Yes we did BUT that temp root method didn't allow access to the real files of the device. It accessed copies (simply put I know). This temp root gives ROOT access to the entire device which puts us a GIANT step closer to a permanent solution.
Also, the other temp method couldn't handle installing Apps in one mode and using them in another. Some Apps disappeared at reboot. With this method, Apps that are installed in either mode are always accessible.
Basically I did this for my own device and just wanted to share with others
But of course I thank you for your efforts, you are a god, I meant no disrespect
texasaggie1 said:
Big props to SAINTH for his guide. Some of my guide is a word for word rip off of his guide. I just copied it and played around to get a simpler way to root. It is still temporary but now when you have "SU" you are messing with the ACTUAL files on the device, NOT a copy on your SD card. Also, programs installed in root mode are still on your device when not in root mode.
I wrote this entire post while tethered to my device using this method.
NOTE: IF SOMEONE COULD GIVE ME A RECOVERY TO FLASH, I THINK WE WOULD HAVE PERMANENT ROOT
OK, I am a dev noob... total noob... please no flaming...
Getting Started: (ONE TIME STUFF)
1) Partition your SD card with at least a 300mb EXT3 partition. I Used gparted in Ubuntu.
2) Download and install from Market: Bar Control. I will explain why in a moment.
3) Download and extract visionroot.zip into your tools directory.
4) Use adb to install programs and transfer files to your device:
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a computer with the Android SDK tools (adb) installed and working:
adb push busybox /data/local
adb push rage /data/local
adb push root /data/local
adb push rsync /data/local
adb push su /data/local
adb install Term.apk
adb install Superuser.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/rsync /data/local/root
5) Run Bar Control and select Terminal Emulator to run in the task bar. Early on, when I was playing around with this rooting method, temp root would just disappear. I found it stays if I use Bar Control. I think since Terminal Emulator is in the task bar, android is less likely to kill it. I did this whole post using tethering without root ever going away.
Ok. SETUP stage is now over. From this point on is how you will get root each time you boot up your phone.
Getting Root:
1) On the phone, open "Terminal Emulator" from the taskbar and type:
cd data
cd local
./rage
Wait for it to say "[+] Forked NNNN childs." then press the back button until you are back at the home screen. It will be slow for a bit.
2) Open "Terminal Emulator" again from the task bar and it should force close. It's ok if it doesn't. Just skip to #3.
3) Open "Terminal Emulator" one more time from the task bar and the prompt should display "#". This is the ROOT prompt! You are almost golden now! Then type:
cd data
cd local
./root
You may get some "Killall: Can't kill such and such" messages. Not a problem.
DO NOT hit the back button. You want terminal to keep running. Hit the Home Button.
YOU NOW HAVE ROOT! Superuser should be working too. We may find that we dont need bar control and terminal running. Let me know and I will change my post.
Click to expand...
Click to collapse
Dalamak said:
But of course I thank you for your efforts, you are a god, I meant no disrespect
Click to expand...
Click to collapse
LOL hahahah thats funny. I'm def not a god at this
Good job man! This will definitely make it seemer on the folks who aren't Linux friendly or lazy folks like me. Oh and btw... you're the futherest thing from a newb! Hahahha! You've been here longer than me. Its rare that I see the real old school guys here anymore. Weren't you in the wizard or tornado sub forum many years ago. You seem familiar...
Oh btw, someone posted a clockwork recovery that was allegedly compatible with the G2 but I don't think anyone had the balls to flash it. Its in the root think tank thread...
Nevermind. I've decided to retract my comment and just try the process to see what happens.
Method worked amazingly well!
Thank you for this!!
Awesome job!
Sent from my T-Mobile G2 using XDA App
Will this work with the 4 click on-device root apk posted in this thread: http://forum.xda-developers.com/showpost.php?p=8535854&postcount=95 ?
Looks like a great guide as only 1 part is required - this allows me to part in my G1 AmonRa Recovery FTW!~111
(Also a great option if you are worried about booting up your G2 after formatting the SD as any progs looking for files there will be disappointed until you can copy them back ...)
Running a continuous Ping in Term now to see if that does the trick ...
EDIT:
Alright! this is awesome!
Q:
IF all we have to do to keep root is to keep the shell open - can't we run a prog or command to prioritize that prog ... like ... i remember that auto taskiller had settings against apps that were in the forgroud, background, background services etc ...
can we fool the OS into thinking this is allways a foreground process even though it's really running in BG ...or somehow give it highest priority?
EDIT 2:
Installed WirelesTeather.apk and ran and installed binaries - SU came up and granted all permission w/o issue - everything looked good.
Didn't open any other programs and decided to test it later, after noticing the AP didn't show I checked Terminal from the taskbar and it was back to $ (was closed by system)
I am running a fish aquarium for livewallpaper - so I'm sure this is why it closed as I'm running more processes at idle ... however, it looks like opening pretty much anything will cause the terminal to close and kill the "temp root'
Running a continuous Ping in Term now to see if that does the trick
FINAL EDIT:
OK! Ran continuous ping, opened Quake 3 - played for a bit - closed it.
Checked Term from the status bar - My Ping is still running !!1111 (IE the shell didn't close and we still have root)
So ... maybe this helps
You are the man. Downloaded. Tested. It works!
Sent from my T-Mobile G2 using XDA App
GREAT WORK!
Got it up and running, and just got 2.26 down, 1.23 up on my laptop off wireless tether.
so since this works directly with system files what happens if you try to metamorph something..will it revert on reboot or stay
Excellent job!
You are a genius! Your guide worked perfectly! I am typing this while tethered to the G2 - I agree with you, getting Root for tethering is worth the hassle of getting Root access! Keep up the great work!
I had been taking the SIM chip from my G2 to G1 (rooted, of course!) for Internet access - No more! Thanks again!
sino8r said:
...
Oh btw, someone posted a clockwork recovery that was allegedly compatible with the G2 but I don't think anyone had the balls to flash it. Its in the root think tank thread...
Click to expand...
Click to collapse
ive tried, several different ways, even ones that had a good chance of bricking, i.e. messing with ruu, and swapping files in the middle of flashing, just to try and get this perm root
texasaggie1 said:
Some people are questioning the value of root without custom ROM's. Here is what i have used ROOT for on this ROM so far:
1) Wireless Tether - this alone is worth it! The 9-5 version from this page works amazingly on the G2:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=NexusOne
2) Uninstall Crapware - I used Titanium to uninstall Web2Go. What a pile of steamy poop.
3) Back up with Titanium - Most awesome backup program out there. Needs root to work.
Click to expand...
Click to collapse
For Wireless Tether, I'm getting an error where it can't start access point. Anyone else have that problem? My computer won't recognize it without it.
EDIT:
Never mind, access point won't start if WiFi is on, and WiFi Tether isn't automatically shutting it off (like I think it's done on other phones), so if anyone else has the problem, turn off WiFi, then run WiFi Tether.
Which Version?
aacrabtree said:
For Wireless Tether, I'm getting an error where it can't start access point. Anyone else have that problem? My computer won't recognize it without it.
EDIT:
Never mind, access point won't start if WiFi is on, and WiFi Tether isn't automatically shutting it off (like I think it's done on other phones), so if anyone else has the problem, turn off WiFi, then run WiFi Tether.
Click to expand...
Click to collapse
Which tethering apk are you using? If you are using the one from the link I provided it should work. I am not having to turn off wifi first for it to work for me.
This will allow you to use the default Froyo Launcher instead of using the HTC Sense Launcher included with the MT4G for those that prefer it!
This was compiled through the generic AOSP 2.2r1 source with 5 screens. I will make one with 7 screens if anyone would like it.
First of all, you will need root(VISIONary) and adb.
Second, you will need this file: http://www.4shared.com/file/Cd9kUAqL/Launcher2.html
Third, make sure your phone is in "Charge Only" mode when you connect it to your computer.
Next:
1. adb push Launcher2.apk /sdcard/
2. adb shell
Now in shell:
3. su (Superuser might pop up on your device, make sure to press "Allow")
4. stop
5. mount -o remount,rw /dev/block/mmcblk0p25 /system
6. cp /sdcard/Launcher2.apk /system/app/
7. start
8. Wait for the phone to do a "soft boot"
9. Once you pull down the Lockscreen, select Launcher instead of HTC Sense
Now, of course, this will go away once you reboot the phone, but you could use visionary.sh, a file that loads on boot if VISIONary roots your phone on every boot, and make it do these commands.
This was a simple idea I had after seeing Cyanogen's LED Notification Light Mod for the G2: http://forum.xda-developers.com/showthread.php?t=797867&page=4
UPDATE: You might want to re-download the Launcher2.apk. The phone hotseat button now loads the HTC Phone app instead of not working.
UPDATE 2: This also includes the default AOSP wallpapers under Wallpaper > Wallpapers.
thank you very much. i was really looking for this. now all we need is perm root so this doesnt go away on reboot
Greatly appreciated!
Not to seem like I am spitting in your face, but I think I'll stick with LauncherPro if I want to get the stock look. Until persistent root is obtained I don't want to mess with anything that may go away.
JWhipple said:
Greatly appreciated!
Not to seem like I am spitting in your face, but I think I'll stick with LauncherPro if I want to get the stock look. Until persistent root is obtained I don't want to mess with anything that may go away.
Click to expand...
Click to collapse
Ha I understand. I was using LauncherPro before I did this.
Updated Launcher2.apk so that the phone hotseat button now loads the HTC Phone app instead of not working.
travisjames said:
This will allow you to use the default Froyo Launcher instead of using the HTC Sense Launcher included with the MT4G for those that prefer it!
This was compiled through the generic AOSP 2.2r1 source with 5 screens. I will make one with 7 screens if anyone would like it.
First of all, you will need root(VISIONary) and adb.
Second, you will need this file: http://www.4shared.com/file/Cd9kUAqL/Launcher2.html
Third, make sure your phone is in "Charge Only" mode when you connect it to your computer.
Next:
1. adb push Launcher2.apk /sdcard/
2. adb shell
Now in shell:
3. su (Superuser might pop up on your device, make sure to press "Allow")
4. stop
5. mount -o remount,rw /dev/block/mmcblk0p25 /system
6. cp /sdcard/Launcher2.apk /system/app/
7. start
8. Wait for the phone to do a "soft boot"
9. Once you pull down the Lockscreen, select Launcher instead of HTC Sense
Now, of course, this will go away once you reboot the phone, but you could use visionary.sh, a file that loads on boot if VISIONary roots your phone on every boot, and make it do these commands.
This was a simple idea I had after seeing Cyanogen's LED Notification Light Mod for the G2: http://forum.xda-developers.com/showthread.php?t=797867&page=4
UPDATE: You might want to re-download the Launcher2.apk. The phone hotseat button now loads the HTC Phone app instead of not working.
UPDATE 2: This also includes the default AOSP wallpapers under Wallpaper > Wallpapers.
Click to expand...
Click to collapse
Dude is there anyway you can do this with the traditional sense launcher instead to replace the ugly espresso crap?
Omeer said:
Dude is there anyway you can do this with the traditional sense launcher instead to replace the ugly espresso crap?
Click to expand...
Click to collapse
Since Rosie.apk already exist within /system/app, it would just throw an error when trying to copy it from the SD card to the system cache.
Lol yeah I found that out the hard way after semi bricking my phone last night. My question now is can rosie.apk that exists within the system cache be replaced by a custom one? I'm assuming no since the .apk being replaced would be in use atm...
Sent from my HTC Glacier using XDA App
Ooh here's another idea. I saw a thread over at the Desire HD forums and someone ported/modded the themes into .apk files. The installation instructions are very straight forward, just install as normal .apk files or move the files to /system/app. Needless to say that just simply installing it didn't work on the MyTouch 4G. My concern now is can we use this method or any other method to push these .apk files to the /system/app folder to see if it works? A way to theme our devices will hold us eager beavers off till we get a permanent root.
Sent from my HTC Glacier using XDA App
Great work, thanks a ton for this. One question though, is there any advantage of using stock launcher insteat of ADW or LP? I myself love ADW, especially with 3D look that AnderWeb is trying go implement but if there's performance gain with the stock - I'm all for it.
Omeer said:
Lol yeah I found that out the hard way after semi bricking my phone last night. My question now is can rosie.apk that exists within the system cache be replaced by a custom one? I'm assuming no since the .apk being replaced would be in use atm...
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Even when using Launcher2.apk instead of Rosie, it failed to replace. I tried it last night after I saw your suggestion.
Omeer said:
Ooh here's another idea. I saw a thread over at the Desire HD forums and someone ported/modded the themes into .apk files. The installation instructions are very straight forward, just install as normal .apk files or move the files to /system/app. Needless to say that just simply installing it didn't work on the MyTouch 4G. My concern now is can we use this method or any other method to push these .apk files to the /system/app folder to see if it works? A way to theme our devices will hold us eager beavers off till we get a permanent root.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
You might be able to do that with this method. All I can say is, try and see if it works.
borodin1 said:
Great work, thanks a ton for this. One question though, is there any advantage of using stock launcher insteat of ADW or LP? I myself love ADW, especially with 3D look that AnderWeb is trying go implement but if there's performance gain with the stock - I'm all for it.
Click to expand...
Click to collapse
Personally, I haven't seen any advantage to using Launcher2 over ADW or LauncherPro. The only reason I made this was because I like vanilla Android over Sense. But, I don't really see any performance gain. I might do a little bit more testing and get back to you.
travisjames said:
Even when using Launcher2.apk instead of Rosie, it failed to replace. I tried it last night after I saw your suggestion.
You might be able to do that with this method. All I can say is, try and see if it works.
Click to expand...
Click to collapse
OK so I followed this guide exactly as outlined except I replaced the launcher2.apk files with the commonSense.apk file. Everything goes swimmingly until I pull down the lock screen when the screen just hangs for a good a while but ultimately results in no change. What I want to try now is to push .apk files onto the /system/app folder some how and that's not what this method does. I read somewhere that it's now possible to push .apk files to root folders, any ideas as to what that might be?
travisjames said:
1. adb push Launcher2.apk /sdcard/
2. adb shell
Now in shell:
3. su (Superuser might pop up on your device, make sure to press "Allow")
4. stop
5. mount -o remount,rw /dev/block/mmcblk0p25 /system
6. cp /sdcard/Launcher2.apk /system/app/
7. start
8. Wait for the phone to do a "soft boot"
9. Once you pull down the Lockscreen, select Launcher instead of HTC Sense
Now, of course, this will go away once you reboot the phone, but you could use visionary.sh, a file that loads on boot if VISIONary roots your phone on every boot, and make it do these commands.
Click to expand...
Click to collapse
I think if you replace step 6 with
"pm install /sdcard/Launcher2.apk"
it should install to /data/app which should still be fine after a reboot.
Phone doesn't work
Thanks for that!
The left button doesn't work on my desire.
Is the link on #1 up to date?
This is going to be one of those things where some people cry out "Blasphemy!" But I will ask anyways.
I loaded up a ROM on my Evo that contains Sense everything, except the lockscreen. The ROM is perfect other than this problem. Despite my best efforts all I see is people asking how to remove the Sense lockscreen (wut?) and none trying to add it to a ROM after the fact. So I'm wondering if anyone would be kind enough to aid me in restoring the Sense lockscreen. I'd greatly appreciate the help.
Licht_ said:
This is going to be one of those things where some people cry out "Blasphemy!" But I will ask anyways.
I loaded up a ROM on my Evo that contains Sense everything, except the lockscreen. The ROM is perfect other than this problem. Despite my best efforts all I see is people asking how to remove the Sense lockscreen (wut?) and none trying to add it to a ROM after the fact. So I'm wondering if anyone would be kind enough to aid me in restoring the Sense lockscreen. I'd greatly appreciate the help.
Click to expand...
Click to collapse
Restore nandroid
Find the HtcLockscreen.apk and use adb to push it to /system/app/
bcarter2000 said:
Find the HtcLockscreen.apk and use adb to push it to /system/app/
Click to expand...
Click to collapse
If you're not good with adb, you can also use root explorer.
I've placed htclockscreen.apk into system/app but it doesn't enable the lock screen. Possible the APK I downloaded is misnamed.
Licht_ said:
I've placed htclockscreen.apk into system/app but it doesn't enable the lock screen. Possible the APK I downloaded is misnamed.
Click to expand...
Click to collapse
Did you install it?
Sent from my HTC EVO 4G with Tapatalk
Widget locker works well
A drop of Chuck Norris's semen was placed on Android OS. We now have CyanogenMod.
kd0axs said:
Did you install it?
Sent from my HTC EVO 4G with Tapatalk
Click to expand...
Click to collapse
I tried but it says "Application not installed." I assumed that meant that I couldn't install system APKs or something of the like. I'll look for another source for the file. I'm sure this one is just bad. (Random Mediafire link.)
Edit : I downloaded from a better source. But this file also will not install. Placed it into the correct folder and am now rebooting to see if it works.
Edit 2 : Definitely not working. Am I missing something? I just place it in the folder... then nothing happens.
You have to install it after it's place in the folder. Use your favorite file manager and click on the apk file.
Licht_ said:
I tried but it says "Application not installed." I assumed that meant that I couldn't install system APKs or something of the like. I'll look for another source for the file. I'm sure this one is just bad. (Random Mediafire link.)
Edit : I downloaded from a better source. But this file also will not install. Placed it into the correct folder and am now rebooting to see if it works.
Edit 2 : Definitely not working. Am I missing something? I just place it in the folder... then nothing happens.
Click to expand...
Click to collapse
Okay. Take your htclockscreen.apk, using Root Explorer preferably, and place it in /system/app. There is no need to install anything now. What is needed, is that you need to long press on the htclockscreen.apk after you copy it to the system/app folder, and press permissions. You must make sure that the "user" permissions are set "read" and "write". Make sure they're both checked. Once that is complete, reboot your Evo. You'll have the htc lockscreen, every time.
you can also use adb. If you don't have it all set up, there's an easy way around that. Download 'wireless adb' or 'adb over wifi' from the market. Activate that app (you have to have your wifi on), open up a command prompt and connect to your phone, by typing 'adb connect 192.sss.s.ss:8000' (it'd be your IP address and port, which the app will provide to you). Once connected, navigate to where you downloaded the htc lockscreen apk. (say it was in the folder C:\android, you'd type cd C:\android, then hit enter). Then do this. adb remount (hit enter).
adb push HtcLockscreen.apk /system/app (hit enter). Then type adb reboot (hit enter). That would be all you need to do. Either one of those two methods, with adb or the file explorer should solve your problem.
k2buckley said:
Okay. Take your htclockscreen.apk, using Root Explorer preferably, and place it in /system/app. There is no need to install anything now. What is needed, is that you need to long press on the htclockscreen.apk after you copy it to the system/app folder, and press permissions. You must make sure that the "user" permissions are set "read" and "write". Make sure they're both checked. Once that is complete, reboot your Evo. You'll have the htc lockscreen, every time.
you can also use adb. If you don't have it all set up, there's an easy way around that. Download 'wireless adb' or 'adb over wifi' from the market. Activate that app (you have to have your wifi on), open up a command prompt and connect to your phone, by typing 'adb connect 192.sss.s.ss:8000' (it'd be your IP address and port, which the app will provide to you). Once connected, navigate to where you downloaded the htc lockscreen apk. (say it was in the folder C:\android, you'd type cd C:\android, then hit enter). Then do this. adb remount (hit enter).
adb push HtcLockscreen.apk /system/app (hit enter). Then type adb reboot (hit enter). That would be all you need to do. Either one of those two methods, with adb or the file explorer should solve your problem.
Click to expand...
Click to collapse
I've added the permissions as per your instructions and rebooted twice but I still have the stock lockscreen.
Licht_ said:
I've added the permissions as per your instructions and rebooted twice but I still have the stock lockscreen.
Click to expand...
Click to collapse
What ROM are you running? I was under the assumption (for some reason) that it was a nonsense rom (sense based, but most sense elements removed). Are you on an AOSP rom? If you are, I don't believe you can use a sense htc lockscreen at all, and I apologize for the mis information. If you are actually using a sense based ROM, then I'm not sure why it's not working. What file explorer are you using? Root Explorer?
Edit: I re read your OP. I see you are on a Sense based rom. What rom is it? Maybe I'll flash it and see if I can get the htc lockscreen working. I feel like flashing something....
k2buckley said:
What ROM are you running? I was under the assumption (for some reason) that it was a nonsense rom (sense based, but most sense elements removed). Are you on an AOSP rom? If you are, I don't believe you can use a sense htc lockscreen at all, and I apologize for the mis information. If you are actually using a sense based ROM, then I'm not sure why it's not working. What file explorer are you using? Root Explorer?
Edit: I re read your OP. I see you are on a Sense based rom. What rom is it? Maybe I'll flash it and see if I can get the htc lockscreen working. I feel like flashing something....
Click to expand...
Click to collapse
Eternal Prophecy 4.2
It has most Sense elements but just not the lockscreen.
Sent from my Evo 4G using XDA App