Develop Bugs

Deleting system apps after root?? (Root Explorer won't do it)

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...

Framework push not working

Well. Im just trying to do a little modding like notification bar.etc. nothing to wild. I have skyraider mod and i pulled the framework and added the bar color and pushing it back to the phone nothing happens. I've used abd and emulator but nothing seems to overwrite the main one. I tried the reboot recovery but no luck. Im lost and clueless what to do next. Oh the files are the correct name and png. Please help.
Sent from my droidinc

dadsterflip said:
Well. Im just trying to do a little modding like notification bar.etc. nothing to wild. I have skyraider mod and i pulled the framework and added the bar color and pushing it back to the phone nothing happens. I've used abd and emulator but nothing seems to overwrite the main one. I tried the reboot recovery but no luck. Im lost and clueless what to do next. Oh the files are the correct name and png. Please help.
Sent from my droidinc
Click to expand...
Click to collapse
Try going into recovery, mounting the system folder then go to the command prompt and type adb shell (make sure phone is connected to PC) then cd /system/app and then rm framework-res.apk after that type exit to leave the shell and then try your adb push framework-res.apk /system/app

So framework-res.apk/system/app? Sorry i get confuse tere are so many commands in my head that im confusing some lol been at this for a while now sorry for the slow process intake. When i push i type
C:/ adb push /sdcard/framework-res.apk /system/framework/framework-res.apk. im sorry to ask can you type in the command what you would use. Please. Thx again
Sent from my DROIDINC using XDA App

Boot the phone (volume - and power)
wait for the file tests to complete,
switch to recovery,
mount the system partition,
connect the phone,
then open a cmd window on the PC
cd to the folder the apk file is in on the PC.
adb push framework-res.apk /system/framework/framework-res.apk
Disconnect the cable, unmount the system partition, and reboot the phone.

Thx alot. Im sure its te same as clockwork recovery. To do the recovery option. Thx again
Sent from my DROIDInc using XDA App

Not sure what im doing wrong. I mount the phone using recovery. Type in adb shell. Everything connects. Then goes into a # sign.
I type in. Cd c:/androidinc (that's where my framework-res.apk is) but it doesn't change anything it doesn't recognized the file or the path. Doesn't make sense. I tried abd remount and says successful then i do a . Abd push /system/framework/framework-res.apk then just a regular menu comes up when you type just abd. Soooo any help would be great. And i've tried the method on previous post.
Sent from my DROIDinc using XDA App

dadsterflip said:
Not sure what im doing wrong. I mount the phone using recovery. Type in adb shell. Everything connects. Then goes into a # sign.
I type in. Cd c:/androidinc (that's where my framework-res.apk is) but it doesn't change anything it doesn't recognized the file or the path. Doesn't make sense. I tried abd remount and says successful then i do a . Abd push /system/framework/framework-res.apk then just a regular menu comes up when you type just abd. Soooo any help would be great. And i've tried the method on previous post.
Sent from my DROIDinc using XDA App
Click to expand...
Click to collapse
You don't need to go into adb shell. If you do then the cd or any other PC command will not work since it is trying to do it on the phone..
So, just go into recovery, mount system then cd to you PC folder and do the adb push

Hold shift and right click anywhere in the c:/androidinc folder (assuming you are using windows). Select "Open a new command window here". Make sure you mount the system partition in clockworkmod recovery. Now type the following command:
adb push framework-res.apk /system/framework/
After it pushes, unmount the system partition and reboot the device.
Should be good to go from there.

Kindle Fire Sort-of Bricked

Can you get into recovery
You probably should just flash a new rom
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me

Did you try wiping then recovering
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me

For future reference, when you're working from recovery:
adb shell mount system
adb push framework-res.apk /system/framework/
adb shell umount system
adb reboot

Josepho1997 said:
So, I was going to replace my framework-res(don't ask why), but I wanted to keep a backup of it. So, I renamed it framework-res.apk1, and was planning to put the modded one in /system/framework. But, once I renamed it, everything crashed. I got a bunch of Chinese/Japanese writing(don't ask me why ). Now nothing will open and my notification bar is gone. Anyways, I rebooted into recovery and mounted from there(because it wouldn't mount). Now I need to know how to install framework-res.apk to /system/framework using adb. I tried:
I've never needed to install an apk with adb, so I don't even know if thats the right code.
EDIT: I used:
to move it to /system/framework
I tried using
but it just gives me the list of option for adb(like when you first open it)
EDIT:
I tried to make it RW by using:
EDIT:
Great! Now it won't even get to the boot animation. Its stuck on the White and orange Kindle Fire screen(before it gets to the boot animation)
Click to expand...
Click to collapse
Yeah like stated above, you need to use adb push because you are just moving it not actually installing it.

also a tip for replacing your framework.
put new framework.apk on sdcard then with root explorer copy or move to the main directory and fix permissions, then move to framework and paste, it will ask if you want to over write other apk say yes, your phone will reboot with the new framework apk.
if you want a backup just copy the original first and save it somewhere else.
Sent from my Galaxy Nexus using xda premium

Bricked my phone after LCD Density Modder

Hi, First I'm not a clever man, nor do I know what I did to brick it but, I used
"LCD Density Modder" on the market and bricked my phone.
https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&hl=en
My phone is bricked, it won't load anything past "Google", I've taken out the battery and put it back in MULTIPLE times, I've tried to reboot into Recovery Mode and get a red Triangle with an error.
I'm on 4.1.1 GSM model, Rooted and Stock ROM.
Is there anyway to fix this issue without completely wiping out my phone? The last backup I did was a week ago by hand, with click and drag.
Thanks for any help, I would appreciate it.

That's not bricking. And the red android is the stock recovery. Your going to need to flash a recovery and flash another ROM.
Sent From My Toro+ via White Tapatalk

First off, your device is not bricked. Bricked means it is irreparable.
Second, all you have to do is get a hold of the stock build.prop file for your ROM build and replace what you currently have with it.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
First off, your device is not bricked. Bricked means it is irreparable.
Second, all you have to do is get a hold of the stock build.prop file for your ROM build and replace what you currently have with it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Or this
Sent From My Toro+ via White Tapatalk

Oh, wow, thanks, and that will save my files?
Is there a step by step process? I...am not a clever man =| or if there's a keyword I can search. Thanks...
I'm asking because I can't transfer files via USB to my Galaxy Nexus, nor does my computer detect it.

Download CWM, rename it to cwm.img and place it in the same directory as your fastboot.exe file on your PC
Boot your device into the bootloader
Type: fastboot boot cwm.img
In the CWM menu on your device, navigate the mounts menu and click mount /system
Type: adb pull /system/build.prop
Open it up in a text editor, change the value in the ro.sf.lcd_density to 320 and save it.
Type: adb push build.prop /system/
Type: adb shell chmod 0644 /system/build.prop
Type: adb reboot

Ignore the post I just made,
I found it manually, and rebooted the phone but it's still black screen when I pushe d it to the phone.
"build.prop /system/" sounds wrong though...but I am still shocked I was able to pull it.

I hate double bumping but "efrant" instructions, I pushed it via your manner, which still boots into the black screen via build.prop /system" and it goes to black screen...and I tried pushing to "/system/build.prop" still doesn't work.
Any assistance?

smartedpanda said:
I hate double bumping but "efrant" instructions, I pushed it via your manner, which still boots into the black screen via build.prop /system" and it goes to black screen...and I tried pushing to "/system/build.prop" still doesn't work.
Any assistance?
Click to expand...
Click to collapse
So what did you do exactly? Did you pull the file from your ROM first, modify it, and then push it back?

So, I'm not using ADB kit, I'm using Galaxy Nexus Tookit v 7.4. I pull it through there, and modify it from 241 to 320 by hand. Save the file. Push it back up using the toolkit, and it's not sticking to the ROM.
I push it up, reboot, and check it by re-pulling it making sure it stucks but I keep seeing the 241 density not the corrected 320.
Should, I be pushing to /system/build.prop or "build.prop /system/" ?
Both methods aren't sticking to /system/build.prop

smartedpanda said:
So, I'm not using ADB kit, I'm using Galaxy Nexus Tookit v 7.4. I pull it through there, and modify it from 241 to 320 by hand. Save the file. Push it back up using the toolkit, and it's not sticking to the ROM.
I push it up, reboot, and check it by re-pulling it making sure it stucks but I keep seeing the 241 density not the corrected 320.
Should, I be pushing to /system/build.prop or "build.prop /system/" ?
Both methods aren't sticking to /system/build.prop
Click to expand...
Click to collapse
I don't provide support for toolkit use. Either do it the way I mentioned or ask in the toolkit thread for support if you want to use a toolkit.

It's to do with the permissions that get set on the file when you push it back to the device. it needs to be read only for the group and world
It baffled me for a good while. After pushing the file, do the following.
Code:
adb shell chmod 0644 /system/build.prop
Hope that helps
Sent from my HTC Sensation using xda premium

efrant said:
I don't provide support for toolkit use. Either do it the way I mentioned or ask in the toolkit thread for support if you want to use a toolkit.
Click to expand...
Click to collapse
- Didn't know it was a hassle, my apologizes. I'll try to do it the old school method.
trevd said:
Its to do with the permissions that get set on the file when you push it back to the device. it needs to be read only for the group and world
It baffled me for a good while. After pushing the file, do the following.
Code:
adb shell chmod 0644 /system/build.prop
Hope that helps
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I had a feeling it was a permissions issue, but wasn't sure how to fix it.
I'll start pulling up the command prompts...wish me luck, thanks for all the help so far guys. I'll do two backup a week from now on, instead of weekly.

Finally got adb in cmd setup, I get a "failed to copy 'build.prop' to '/system/build.prop': Read-Only file system
I'll try it again, I'm pretty sure I forgot a step.

smartedpanda said:
Finally got adb in cmd setup, I get a "failed to copy 'build.prop' to '/system/build.prop': Read-Only file system
I'll try it again, I'm pretty sure I forgot a step.
Click to expand...
Click to collapse
Probably missed this step:
efrant said:
In the CWM menu on your device, navigate the mounts menu and click mount /system
Click to expand...
Click to collapse

efrant said:
Probably missed this step:
Click to expand...
Click to collapse
LOL, yeah I did, got that, did everything from scratch per your instructions, got up to the lovely adb reboot...and nothing, at all, black screen.
I re-pulled it, to make sure the DPI was changed to 320...and it was, and still black screen...=[ I'm really sad now.

smartedpanda said:
LOL, yeah I did, got that, did everything from scratch per your instructions, got up to the lovely adb reboot...and nothing, at all, black screen.
I re-pulled it, to make sure the DPI was changed to 320...and it was, and still black screen...=[ I'm really sad now.
Click to expand...
Click to collapse
Did you change the permissions like trevd suggested?
While booted in CWM with /system mounted:
adb shell chmod 0644 /system/build.prop
If that still doesn't work after a reboot, I suggest you re-flash grab the system image for 4.1.1 from Google's site, extract the system.img, reboot your device into the bootloader, and type: fastboot flash system system.img. It won't wipe your device, but it should fix anything that was messed up. (It will also remove root and busybox and whatever else you have installed on the system partition.
)

FINALLY! SUCCESS! I forgot the permission like you mentioned, but it didn't work the first two times, guess I mistyped something, it worked the third time.
I honestly appreciate all the help, and all the inputs. My phone is at 100%, and I'm doing a backup as we speak now.

efrant said:
Download CWM, rename it to cwm.img and place it in the same directory as your fastboot.exe file on your PC
Boot your device into the bootloader
Type: fastboot boot cwm.img
In the CWM menu on your device, navigate the mounts menu and click mount /system
Type: adb pull /system/build.prop
Open it up in a text editor, change the value in the ro.sf.lcd_density to 320 and save it.
Type: adb push build.prop /system/
Type: adb shell chmod 0644 /system/build.prop
Type: adb reboot
Click to expand...
Click to collapse
I know this thread is dead but I would like to say that this is the single most useful post I've seen in ages! I was looking around for nearly an hour and every post resulted in saying "reflash rom"...
Then I saw this, and worked!! My phone is her old self again
thumbs up!

[Q] replace framework-res.apk?

Was just wondering if there is a way to replace the framework with just using root without a custom recovery for the stock Rom?
On my s3 I couldn't do it with just root don't know if that would work on this or if I might have missed something.
Sent using xda premium.

re: install apks
TheArtiszan said:
Was just wondering if there is a way to replace the framework with just using root without a custom recovery for the stock Rom?
On my s3 I couldn't do it with just root don't know if that would work on this or if I might have missed something.
Sent using xda premium.
Click to expand...
Click to collapse
All you need is to be rooted, it does not matter if you have custom recovery or not.
You can install any apk's since you do not need to go into recovery to install apks.

When I tried with root only before on a different phone I used root explorer to replace.
But when I went to paste it in the folder the phone locked up and rebooted.
Was that not the right way to do it?
Maybe using adb terminal would be better and not cause it to lock and reboot when I paste over the existing framework-res.apk.
Being in the system directory causes some issue with being that is also a constant used file.
Sent using xda premium.

re: install apk
TheArtiszan said:
When I tried with root only before on a different phone I used root explorer to replace.
But when I went to paste it in the folder the phone locked up and rebooted.
Was that not the right way to do it?
Maybe using adb terminal would be better and not cause it to lock and reboot when I paste over the existing framework-res.apk.
Being in the system directory causes some issue with being that is also a constant used file.
Sent using xda premium.
Click to expand...
Click to collapse
The framework-res.apk should be installed like any other app
unless the OP of wherever you got it from gives instructions
to "copy" it to the /system/app folder.
Why not do it the default normal way? just double click on it
when you are in root explorer and it should install like any
other app. If it gives an error, then you can copy it.
If you "copy" it you have to fix permissions and you have to
change the attributes of the /system/app folder so it's "read and write".
NOTE: if there is an existing framework-res-apk in /system/app
delete it with root explorer before doing any of the above.

Framework-Res.apk must reside in system directory. /system/framework to be exact.
Easiest way to do it without locking up is with adb.
You were right OP that it locks up because it's consistently being used. When I make my mods and such to the framework, this is how I quickly get it to the device.
adb remount (if the kernel supports it in other words, anything but stock)
Turn phone screen on
Adb shell stop (your phone should now have a black screen. This command stops all running threads except the one for adb)
Adb push framework-Res.apk /system/framework
Adb shell chmod 644 /system/framework/framework-Res.apk
Adb shell start
You should now see the boot animation then the prompt "android is upgrading"
If you do not have adb remount option (it returns with permission denied)
Copy new framework Res apk to root of internal sd card.
Adb shell stop
Adb shell mount -o remount,rw /system
Adb shell cp /sdcard/framework-Res.apk /system/framework/framework-Res.apk
Adb shell chmod 644 /system/framework/framework-Res.apk
Adb shell start
Just a pointer, disregard my capitalization. Only capitalize when needed.
This method should get everything copied successfully. Any issues just post back!
Sent from my SGH-M919 using Tapatalk 2

Oh thank you very much.
I will give that a try and sounds exactly like what I was looking for.
Sent using xda premium.

Not sure if this is really relevant but...
When I had the samsung vibrant, I used root explorer to make a copy of my framework-res.apk. I extracted the entire thing, found my battery icon files, replaced them with different images given the same name, then repacked the file. Then I copied it back to the original folder to replace the original apk and my phone immediately shut off and rebooted. When it came back I had my new battery icon working just as I had hoped. I was rooted running stock.

Wait... Are you saying that I can simply copy the framework-res.apk from SlimKat and use it on a Google Play Edition ROM?
I'm going to try it!