I accidentally deleted the htc clock and i am having problems trying to get it back. I have pushed the apk with root explorer and adb, and i have tried it with and without the odex file. does any body know if there is another way besides flashing the rom, because the rom automatically wipes data
Push it then make sure you set the correct permissions then reboot the phone. Should be as simple as that. Make sure you push the .odex as well and that also has the correct permissions.
Related
So far, I've settled on Sense-Able as the ROM I like the best. I really don't like the dialer's theme though... Black text on blue gradient background isn't the most contrasting choice, IMO. I'm color-deficient with shades of darker colors too so that doesn't help.
How can un-theme this dialer ? I'm guessing that's not practical, so replacing the dialer is my next option (?). How do I do that ?
Download Dialer one off market its free. you can theme that. its awesome. I am using ivans. there is a thread someone made a zip that delete the old dialer and replaces with dialer one, its great
Deletes the HTC dialer?
No, based on what I read (likely the same thread), it doesn't delete it. People said that the HTC dialer still comes up after a call is placed, i.e. when you hit the "keypad" button so you can input numbers when prompted.
I do have Dialer One already. I have no general complaints about HTC's so I'd rather un-theme it or replace the Sense-Able version.
Have you tried pushing phone.apk and changing the permissions? I did this with a new rosie to an old version of aloysius and it worked fine after I changed the permissions with root explorer.
I've tried nothing. I don't have a clue where to start, hence my thread here.
Do you have root explorer? If so, make sure you have a nand before you experiment. What I did with my rosie was basically copy the new one to my sd card from my computer that I had earlier pulled from a new version from a rom. So, with the new version copied, open root explorer, copy the new phone.apk. navigate to your system/app and remove the old phone.apk and paste the new one. Long press new apk and open permissions. Set all that apply and then reboot when done.
If you dont have RE you can use adb shell. Same process really, push new apk to sdcard (can also be pushed from tools folder also). rm old apk from system/app. push new apk from sdcard or tools. next thing is the chmod command that I am not sure of. Something like adb shell chmod 755, but im not sure since I used RE. Hopefully someone else can chime in that knows this part.
Hey Guys,
I have been attempting to mod my framework-res.apk to try and add a percent battery icon (unsuccessfuly so far). Here is my issue, after finding that my modded framework file isnt working properly, I go to try and restore the original. After restoring the original I still get tons of FC's and the only way to get things back to normal is to restore my backup from CWM.
The method I am using to replace my framework-res.apk is to use a root explorer (ES File Manager) to copy the file to /system/ then from there I modify the permissions and then move the file to the framework folder, overwriting the existing file. After this, I reboot the phone.
My question is, why is my original framework-res.apk file causing force closes? It is starting to make me think that even my modded files are ok, but that the issue is arising in the manual transfer.
Sorry if the answer is posted elsewhere, I googled and was only finding issues with the apk not being compiled correctly, but that shouldnt be an issue with the original apk.
*EDIT* I figured it out. It appears it was because Jkay Deluxe was installed. I decided to reflash the rom and try with a fresh copy of the framework-res.apk and everything appears to be working now.
While I was trying to clear the data of the file manager, I inadvertently uninstalled the file manager.
I am rooted on Virtuous Prime. I tried to use Titanium to extract the file manager from a nandroid backup; this did not work.
I do not have a titanium backup of the file manager.
Surprisingly, I like this stock file manager.
Is there a way I can get it back? A download?
Can I use adb to push the file manager to the device after extracting it from a ROM?
I don't know if this is the right one, but we can try it. It's the only one I could find.
I also have another file called filemanager2.odex
Im thinking that's just the data in my file manager....if you need that 2nd file, let me know
Added the file...had to change odex to zip to upload....just delete zip and change it back
robertg9 said:
I don't know if this is the right one, but we can try it. It's the only one I could find.
I also have another file called filemanager2.odex
Im thinking that's just the data in my file manager....if you need that 2nd file, let me know
Click to expand...
Click to collapse
If you are on a stock ASUS firmware, most of your system APKs will be odexed. You need both the APK and the odex file for the app to run.
A lot of custom ROMs have deodexed files for several reasons. Some people swear that deodexed ROMs are faster, some swear the opposite. Modifying deodexed ROMs is theorectically slightly easier also as you only need to deal with one file rather than 2.
This is a rather simple, nonsensical explanation of the situation, and I'm sure other folks will chip in with more accurate definitions, however, getting back to the point, YOU WILL NEED THE ODEX FILE ALSO IF ON STOCK.
Hi guys, before I start I'll say that I have searched all over the internet and here on the forums and I couldn't find my particular issue. Well the thing is that I edited the line in my build.prop "ro.build.version.codename=REL" to "ro.build.version.codename=L" so I could get the material design on the Google Now Launcher pulled from a Android L build here's the thread I got that app: http://forum.xda-developers.com/android/apps-games/app-android-lollipop-apps-launcher-apps-t2912905
I did that and now my device will boot up normally then I will reboot by itself then show the boot animation then repeat the same process again and again until I force the phone to recovery or fastboot.
By the way my device is the LG Optimus G (E970) running GEE 3 ROM 1.2 and TRWP 2.6.3.0 and I have a backup of the original build.prop on my PC. I don't want to lose my data and apps since I forgot to make a backup (silly me).
I would like to know if there is a way to push the build.prop file on my PC to my phone so I could just replace it, or create a flashable zip.
Please help me, and thanks in advance.
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
question
AntonyOrtega said:
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
Click to expand...
Click to collapse
how were you able to do it when you couldnt get past booting.
I treid to edit this file to get better video/photo/audio quality a while back but when I did edit it and rebooted I was stuck in a boot loop.
I want to give it a go again but do not want to end up in a boot loop again if I can help it.
Is there settings I should not edit or permissions I need to set etc to stop a boot loop? What causes the bootloop in the first place? I would of thought that editing this file would stop the camera from working and not the whole phone but hey what do i know
Can anyone provide some insight?
Cheers
most likely permission error
permission should be rw-r-r (read,write for root, read for group, read for global) or 644 depending on what you are used to
anyway, before you make changes, backup system in TWRP then do your stuff
in case something went wrong, simply restore system and no probs