Using the new 4.3 Stock/Sense 5 ROM, trying to replace SystemUI.apk with the one from Sinistertensai (post 794). After mounting /system in TWRP and renaming the existing file to SystemUI.apk.bak, I am pushing the new apk over ADB to /system, then chmod 644 (I'm doing this on the phone using TWRP, so typing in 0644), and then moving it to /system/app. I can confirm that the new SystemUI.apk resides in /system/app right next to the .bak version, both are 644. When I reboot, I immediately get "Unfortunately, System UI has stopped" and it just keeps popping up again when I close it.
What am I doing wrong?
(Note: For now I'm using the Sense 5 Toolbox, which is great, but I'd still like to know what I was missing in trying to replace my SystemUI.apk.)
Your using a deodexed Rom I am hoping. Did you update owner? chown root.root. did u wipe caches?
try checking ur permissions using a file explorerView attachment 2585976
detcup4evr said:
Your using a deodexed Rom I am hoping. Did you update owner? chown root.root. did u wipe caches?
Click to expand...
Click to collapse
Cache may have been the issue. I might give it another go to get my learning in.
I ran into the same issue when I naively tried to use this mod on my odexed RUU install. whoops!
tommy_riley said:
I ran into the same issue when I naively tried to use this mod on my odexed RUU install. whoops!
Click to expand...
Click to collapse
Fortunately, that was NOT my issue.
I'm still looking for a solution to this. My latest attempt:
In recovery:
rename SystemUI.apk to SystemUI.apk.bak
adb push modded SystemUI.apk to /system/app/
chmod 644
chown root.root
clear cache and dalvik
Still FCs continuously on boot. I've tried it just the way several other threads suggest, but I'm having a hard go of it.
tommy_riley said:
I ran into the same issue when I naively tried to use this mod on my odexed RUU install. whoops!
Click to expand...
Click to collapse
So how did you end up getting it to work? Or did you?
I have not found a solution. Obviously flashing the mod on odexed isn't a solution and I've had major stability issues with exposed framework , so I am just sticking with stock root for now.
Sent from my EVO using xda app-developers app
Hmm... Xposed and Sense 5 Toolbox work well for me on deodexed, but I was interested in trying the modded apk just for kicks.
Sent from my EVO using xda premium
I used Root Explorer to move the SystemUI.apk into the /system/app/folder location. Rebooted afterwards and it worked fine:thumbup:
Sent from my EVO LTE
FinZ28 said:
I used Root Explorer to move the SystemUI.apk into the /system/app/folder location. Rebooted afterwards and it worked fine:thumbup:
Sent from my EVO LTE
Click to expand...
Click to collapse
Well I must be doing something wrong. I used Root Explorer to copy SystemUI.apk to /system/app (mounted RW) and replaced the existing one. I noticed the permissions were strange (like ---RWXR-X or something) but I rebooted it anyway. It didn't FC, but I didn't have a notification bar at all on reboot. So I went in and changed permissions to 644, then the FCs started on the next reboot.
I'll keep researching, but I don't know how I could be going this wrong. I must be missing something. I've copied it manually and using adb, in the system and in recovery, every combination I can think of, unless there's a different set of permissions I should be using or a different method. Or perhaps it just doesn't work with the .3 ROM for some reason (can't imagine why).
Don't know what to tell you. I'm using .3 and it worked fine for me.
Sent from my EVO LTE
FinZ28 said:
Don't know what to tell you. I'm using .3 and it worked fine for me.
Sent from my EVO LTE
Click to expand...
Click to collapse
Just want to confirm: You copied the new apk directly to /system/app and overwrote the stock one, right? What permissions do you see?
SilverZero said:
Just want to confirm: You copied the new apk directly to /system/app and overwrote the stock one, right? What permissions do you see?
Click to expand...
Click to collapse
That's correct. I didn't bother messing with any permissions. Looking at it now, it's rw-r--r--.
Finally figured this out. I never replaced services.jar with the sig-check-disabled version. Now it works.
Can someone upload the systemui.apk from chubbz's 5.5 v3? Just updated to v4 and I'm not liking the center clock. Thanks!
Sent from my EVO using xda app-developers app
johamsandwich said:
Can someone upload the systemui.apk from chubbz's 5.5 v3? Just updated to v4 and I'm not liking the center clock. Thanks!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Here you go. Push to /system/app via a root explorer, and set permissions to match the others. Look at the screenshot at the beginning of this thread to see the proper permissions. Then reboot.
aarsyl said:
Here you go. Push to /system/app via a root explorer, and set permissions to match the others. Look at the screenshot at the beginning of this thread to see the proper permissions. Then reboot.
Click to expand...
Click to collapse
Thank you, I've been searching for a way to do this. Worked perfectly.
Sent from my EVO using XDA Premium 4 mobile app
Thanks for uploading! Got my clock back in the corner again
Sent from my EVO using xda app-developers app
Related
I didn't see a thread on how to do this anywhere in the MT4G forum, so I thought I would share.
If you want swype, but are not on their beta test program, do not want to muck about with their "installer" app, or deal with the reminders of beta status and app expiration; you can pull swype from a stock ROM and use it on your device.
As per the rules, you should not do this on a phone that does not have swype installed stock.
Also, this involves messing around in the "system" partition. While the risk is very low, you do this at your own risk.
First you will need to extract the needed files from a stock ROM. If you are still running the stock software, you can use a file explorer app to make a copy onto your SD card. Just copy and paste. You can also pull the files from the stock image or from the Iced glacier ROM. Pulling from Iced Glacier is the easiest method. Just unzip the ROM file and find the needed files.
There are two files, both in the system partition. The first is "Swype.apk" and is in /system/app folder. The second is "libSwypeCore.so" and is in /system/lib/ folder.
Edit: 7/25/11
It seems you must also conciser the source ROM and destination ROM when obtaining the files. Swype does a device/licence check when running, and if it fails the check then Swype will not work. The build.prop lists "t-mobile/htc/ect" as product.brand and Swype seems to check this before running. So use a version of Swype from a ROM with the same build.prop or edit the build.prop manually.
Now to install Swype:
There are two ways to do this, ADB or root explorer. (or other file manager with RW)
Any extra info to help explain what is going on for any new guys will be in green text.
For ADB:
First put the files you extracted into the tools folder of the android SDK, then open an ADB shell to your phone. When that is done, use the following commands. (each line is a separate command)
Remember Linux commands are case sensitive.
First is to mount /system as RW. (this allows you to save files to /system)
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Then you need to push (save a copy) the files to the correct locations.
Code:
adb push Swype.apk /system/app/Swype.apk
adb push libSwypeCore.so /system/lib/libSwypeCore.so
It may give the files the wrong permissions. (how much access to the system they have) Just to be safe we need to give the files the right permissions.
Code:
chmod 644 /system/app/Swype.apk
chmod 644 /system/lib/libSwypeCore.so
sync
reboot
Your phone will reboot and then you are done.
For Root Explorer:
Extract a copy of the needed files and put them on the SD card.
Then open root explorer and open the "sdcard" folder.
Next find "Swype.apk" and long press it and select "copy" (or if you have already completed this step once, copy "libSwypeCore.so")
Use the back button to go back to the root of the folder tree (up top where it shows your current location, it will show "/" this is where you started from when opening the app)
Locate and open the "system" folder.
You then need to tap the button up top marked "Mount R/W" (this will allow you to make changes and copy the files to the right locations) (this step should not be needed if you have already done so before)
Next open the "app" folder. (or if you are moving "libSwypeCore.so" open the "lib" folder)
Hit the "paste" button to copy the file.
Next long press the file you just copied "Swype.apk" and select "permissions" (or "libSwypeCore.so" as appropriate)
You will see a bunch of check boxes. The will be labeled "read" "write" "execute" across the top and "user" "group" "others" down the left side.
For "user" select the "read" and "write" boxes
For "group" and "others" select the "read" box only. Then select "OK"
When done with the first file, repeat the above steps again with the second file. Observe any changes to the steps that are in orange text.
Next open up a "terminal emulator" app and then run the following commands.
Code:
su
sync
reboot
Your phone will reboot and then you are done.
Hope this helps someone.
When I pushed the files to CM7 I completely forgot about checking permissions when it didn't work.
I do however prefer the newest Swype from the beta program since it has speech recognition. Your information should help me porting my Blackout Swype themes over to the MT4G with creating a proper flashable zip that will work with any ROM, and for that I thank you.
creator2456 said:
When I pushed the files to CM7 I completely forgot about checking permissions when it didn't work.
I do however prefer the newest Swype from the beta program since it has speech recognition. Your information should help me porting my Blackout Swype themes over to the MT4G with creating a proper flashable zip that will work with any ROM, and for that I thank you.
Click to expand...
Click to collapse
No problem, I was thinking of creating a flashable zip for my cousin, he doesn't like to mess around with this stuff... but he lives on the computer, go figure. I just need the signing app, actually its not needed with the new recoveries that allow unsigned zips to be flashed, but it would be nice.
I cant get the swype from iced glacier onto cm7. I follow all the steps perfectly and can select the swype keyboard but when I try to type nothing happens except a flashing blue border around the keyboard. Its pretty annoying.
Jacezo said:
I cant get the swype from iced glacier onto cm7. I follow all the steps perfectly and can select the swype keyboard but when I try to type nothing happens except a flashing blue border around the keyboard. Its pretty annoying.
Click to expand...
Click to collapse
Thats odd, I used this to get it on to CM7 and it works fine. Where did you source the files from? Permissions are rw-r-r?
Thanks so much for this! I don't use the voice feature and I always hit it on accident, so I've been missing the stock version. I also didn't care for the blue all that much.
I am new to this. Could I use this technic for the others stock apps (calendar, clock/weather widgets...)? Thanks!
A23E said:
I am new to this. Could I use this technic for the others stock apps (calendar, clock/weather widgets...)? Thanks!
Click to expand...
Click to collapse
No, the apps you are speaking of are HTC apps. They are integrated into the HTC Sense framework.
Moving default apps between ROMs that have custom UIs, like sense, can be problematic. Many default apps have been setup to work with the custom UI and framework only.
Marine6680 said:
Thats odd, I used this to get it on to CM7 and it works fine. Where did you source the files from? Permissions are rw-r-r?
Click to expand...
Click to collapse
I took the files from an iced glacier rom and fixed the permissions. I'm on cm7 rc1 with the dumguq smartass kernel.
Sent from my HTC Glacier using XDA App
Jacezo said:
I took the files from an iced glacier rom and fixed the permissions. I'm on cm7 rc1 with the dumguq smartass kernel.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
All I can think to do is try again. It may be the kernel as well.
great help and easy to follow, thanks
Glad it helped.
hav'nt tried your way, but what i did was got those 2 files form new mytouch 2.3.4 (swype 3.7) and copied it to panache stock custom then cooked and flashed, but now it says wrong licence.....
atifsh said:
hav'nt tried your way, but what i did was got those 2 files form new mytouch 2.3.4 (swype 3.7) and copied it to panache stock custom then cooked and flashed, but now it says wrong licence.....
Click to expand...
Click to collapse
Probably has a device check, and the ROM you are using is giving the wrong device.
I believe the panache is the Canadian version, so it may be that the licence is regional as well.
License issues for me.on virtuous unity 1.29 and fauxkernel
Sent from my HTC Glacier using XDA Premium App
valve timing said:
License issues for me.on virtuous unity 1.29 and fauxkernel
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Same, I wonder if it's something to do with our build.prop?
Sent from my HTC Glacier using XDA App
Sadness i want swype guess ill go.back to beta
Sent from my HTC Glacier using XDA Premium App
valve timing said:
Sadness i want swype guess ill go.back to beta
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
I figured it out for us (those of us on Virtuous Unity)!!! Haha, I'm so stoked. K, so I changed my build.prop of ro.product.brand to =tmobile, I think it's originally htc_wwe or something (This was after extracting my system backup for stock froyo and comparing the differences). Then uninstalled swype, rebooted, and then followed the terminal steps listed in the OP. Good luck.
Sent from my HTC Glacier using XDA App
eliasadrian said:
I figured it out for us (those of us on Virtuous Unity)!!! Haha, I'm so stoked. K, so I changed my build.prop of ro.product.brand to =tmobile, I think it's originally htc_wwe or something (This was after extracting my system backup for stock froyo and comparing the differences). Then uninstalled swype, rebooted, and then followed the terminal steps listed in the OP. Good luck.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I can confirm that this works
http://forum.xda-developers.com/showthread.php?t=977912
Does anyone know if there is a working version for the Atrix? Id love to get this to work.
Thanks.
I'm no expert, and it's not my style, but I'll give it a try and report back in a few minutes.
EDIT: I got it partially working, I installed the apk in the zip, and moved the files in the system/lib directory of the zip file to /system/lib. after that you can use the wallpaper without a force close, but it doesn't fill the screen. I'll try one more thing and include a screenshot.
you'll need to pull the files from an htc device that is qhd. I think the sensation is qhd, but I'm not sure.
Sent from my MB860 using XDA App
downtrodn said:
http://forum.xda-developers.com/showthread.php?t=977912
Does anyone know if there is a working version for the Atrix? Id love to get this to work.
Thanks.
Click to expand...
Click to collapse
What part do u like about it?
I used Alien ROM + theme + Sensual GingerBread
Looks alot like it. check them out
I just want the live wallpaper since I'm a camera man, I love the bokeh
My gf has the evo 3D tried to don't the apk but only found android live wallpaper apk.
Sent from my MB860 using Tapatalk
i pulled the files from an HTC Sensation rom and sure enough it works fine, and is the right resolution for our screens. I can't make an update.zip though, i tried a few dozen times and only get errors.
uiskibum said:
i pulled the files from an HTC Sensation rom and sure enough it works fine, and is the right resolution for our screens. I can't make an update.zip though, i tried a few dozen times and only get errors.
Click to expand...
Click to collapse
Anyway to install as a apk? I appreciate the hard work
Sent from my MB860 using Tapatalk
nope it's not as simple as an apk install. I'll write up something tomorrow and include the files in a .zip.
Sent from my MB860 using XDA App
If you stuff your phone I take no, zero, none, nada, zip, zilch responsibility for it.
The following method is for adb, you could most likely use root explorer of file expert, but you need a file manager that lets you remount system as read/write. It assumes you know how to get the files to your phone/sd-card and have the android sdk, and know how to use it. I also assume that you know how to backup, have backed up and know how to restore (nandroid, rom manager, tibu, whatever).
1. Start a windows command prompt; if you can't do this, then stop right here.
2. type 'adb shell'
3. see code block below
Code:
su (accept prompt on phone if needed)
mount -o remount,rw /dev/mmcblk0p12 /system
cd [PATH TO FILES]
cp Mode10Wallpapers.apk /system/app
chmod 644 /system/app/Mode10Wallpapers.apk
cp libicule.so /system/lib
chmod 644 /system/lib/libicule.so
cp libiculx.so /system/lib
chmod 644 /system/lib/libiculx.so
cp libmode10_alpha.so /system/lib
chmod 644 /system/lib/libmode10_alpha.so
cp libmode10_wallpapers.so /system/lib
chmod 644 /system/lib/libmode10_wallpapers.so
cp libmode10Graphics_alpha.so /system/lib
chmod 644 /system/lib/libmode10Graphics_alpha.so
You should now see the HTC Sense LWP option in your live wallpaper selector. If not reboot and see if that does it. Setting the permissions is key.
You can do the same with root explorer/file expert by copying the files to the appropriate folder (apk to /system/app and the *.so to /system/lib) and changing permissions, you just have to remount /system as read/write for the files to actually copy over.
If you stuff your phone I take no, zero, none, nada, zip, zilch responsibility for it.
First time I tried this I did a bulk chmod on /system/lib and on the next reboot
I was stuck in recovery. So as painstaking as it is the one by one method of copying and permission setting is the safest (for me at least).
THIS IS NOT CWM FLASHABLE
Thanks for this!
Im lost! when I get to "cp Mode10Wallpapers.apk /system/app" dos tells
me that there is no such file, and doesn't do anything..
I have it on my C:\ just sitting there... no special file or folder.
Anyways, what does the "CP" stand for? just curious...
Thanks!!! Looking so forward to this
ssmr2t said:
Thanks for this!
Im lost! when I get to "cp Mode10Wallpapers.apk /system/app" dos tells
me that there is no such file, and doesn't do anything..
I have it on my C:\ just sitting there... no special file or folder.
Anyways, what does the "CP" stand for? just curious...
Thanks!!! Looking so forward to this
Click to expand...
Click to collapse
.......
are the files on your phone? I had mine in /sdcard/download/htclwp. so the line of "cd [LOCATION OF FILES]" for me is cd /sdcard/download/htclwp
all the commands listed are for once you have an adb shell session running.
I'll update my post to include that bit.
cp is a linux/unix command for copy.
Hey thanks a lot, it worked. I see the LWP in my wallpaper drawer, but it FC's on me... I also checked off all permissions.
Oh well...
Is there any way to port over the "weather" LWP from the new Evo 3d? ? NOW THATS A WALLPAPER that would be sick to see on our devices!!!
ssmr2t said:
Hey thanks a lot, it worked. I see the LWP in my wallpaper drawer, but it FC's on me... I also checked off all permissions.
Oh well...
Is there any way to port over the "weather" LWP from the new Evo 3d? ? NOW THATS A WALLPAPER that would be sick to see on our devices!!!
Click to expand...
Click to collapse
if it's force closing then you should recheck the permissions on all the files (and make sure they all copied over), and try a reboot. this does work.
uiskibum said:
if it's force closing then you should recheck the permissions on all the files (and make sure they all copied over), and try a reboot. this does work.
Click to expand...
Click to collapse
You are Awesome! It worked via root explorer. I want to thank you for your time, hard work, and being a Guinea pig. as a result of a semi brick, i think thats what that was?
If you want to do any more htc wallpapers i have all the stock ones from the HTC Evo 3D. Again..............
Thank you! you rock!
uiskibum said:
if it's force closing then you should recheck the permissions on all the files (and make sure they all copied over), and try a reboot. this does work.
Click to expand...
Click to collapse
What should the permissions be?
Sent from my MB860 using XDA Premium App
I didn't set any permissions. Just copied over the files to the correct folders mounted and rebooted.
Sent from my MB860 using Tapatalk
Permissions (if set by root explorer or other) should be:
HTML:
Read Write Execute
Owner X X
Group X
Others X
uiskibum said:
Permissions (if set by root explorer or other) should be:
HTML:
Read Write Execute
Owner X X
Group X
Others X
Click to expand...
Click to collapse
Thanks, is that for all the files?
Sent from my MB860 using XDA Premium App
ssmr2t said:
Hey thanks a lot, it worked. I see the LWP in my wallpaper drawer, but it FC's on me... I also checked off all permissions.
Oh well...
Is there any way to port over the "weather" LWP from the new Evo 3d? ? NOW THATS A WALLPAPER that would be sick to see on our devices!!!
Click to expand...
Click to collapse
God, that's one annoying signature you got there, lol.
msd24200 said:
Thanks, is that for all the files?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
yes, for all the copied files.
Sent from my MB860 using XDA App
Tried installing but won't work
Which version are you referring to ???
Locked & Loaded
" Shooter on Deck "
Just grab the apk, make sure you are using a deodexed or odexed per the rom you are using. Then copy the apk to your system/app folder, then change permissions to match the other apps in the system folder then reboot. You should be good to go. Or if you are familiar with adb then do this:
adb remount
adb push Vending.apk /system/app
Once you do that you should be good to go.
Transformer Sent
THE OLD GREEN MARKET
Sent from my PG86100 using xda premium
pbedard said:
THE OLD GREEN MARKET
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Just go to System/Apps and Delete the Current Vending.apk, and Replace it with whatever version you want, and Change the Permissions! Also although you really Don't have to... But you might want to Clear the Data/Cache in Settings/Applications/ManageAPPS!
I used root explorer to move some system apk & its corresponding odex file from /system/apk to sdcard. I rebooted and found that I have moved some essential app like the stock dialer (it wasn't possible to figure out from the apk name). So now the dialer was gone. I then moved them back from sdcard to /system/app using root explorer thinking that it would undo the mess.
However the apps didn't come back, for example the dialer. The phone still tells me that there is no dialer.
What do I need to do?
Maybe you copied framework or something that dialler need to work... Try put bac all files. If that doesn't help see if the dialer is inn apps.
Gregrin said:
Maybe you copied framework or something that dialler need to work... Try put bac all files. If that doesn't help see if the dialer is inn apps.
Click to expand...
Click to collapse
I didn't move anything from any other directory. I moved back each and every file to /system/app that I had moved from it earlier. Still no luck.
I didn't delete anything in this process. I don't see dialer in app drawer either.
Reboot?
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2
Markuzy said:
Reboot?
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yes, umpteen number of times.
Fix permissions. if u copied everything back to original location, it should work. then remove ONLY unwanted apps
RavinduSha said:
Fix permissions. if u copied everything back to original location, it should work. then remove ONLY unwanted apps
Click to expand...
Click to collapse
Yes, you are so right.
The apk permissions have screwed up after all the moving. I issued ls -l command in adb shell and this is what I found out.
-rw-r--r-- 1 root root 3973 May 7 2012 HTMLViewer.apk
-rw-r--r-- 1 root root 8784 May 7 2012 HTMLViewer.odex
----rwxr-x 1 system sdcard_r 562553 Feb 9 04:31 LatinIME.apk
----rwxr-x 1 system sdcard_r 327896 Feb 9 04:31 LatinIME.odex
-rw-r--r-- 1 root root 14569 May 7 2012 LiveWallpapersPicker_gles20.apk
-rw-r--r-- 1 root root 21392 May 7 2012 LiveWallpapersPicker_gles20.odex
LatinIME.apk is the keyboard with screwed up permission.
Now how do I fix it? What command do I issue?
fix permissions in recovery. or in connectbot or another shell program:
chown root:root /system/app/*.apk /system/app/*.odex
chmod 644 /system/app/*.apk /system/app/*.odex
reboot
You can also change permissions in Root Explorer itself. Hold down on the files, choose permissions and tick the first column and the first box of the second one. Leave the rest blank and press ok. That's it. If it still doesn't show, reboot. Fixing permissions in recovery does exactly this, but for all files in /system/app, /data/app and /data/data. Every time you copy something to /system or /data, you have to set the right permissions. Either in a root explorer app, adb shell, terminal emulator or fixing permissions in recovery.
LatinIME is the stock Android keyboard btw.
Sent from my Desire HD using xda premium
calisro said:
fix permissions in recovery. or in connectbot or another shell program:
chown root:root /system/app/*.apk /system/app/*.odex
chmod 644 /system/app/*.apk /system/app/*.odex
reboot
Click to expand...
Click to collapse
Issued the above commands. They all now show the same as others and are back.
Unfortunately the dialer still doesn't appear. Which apk is the dialer? My phone has gingerbread.
sashank said:
LatinIME is the stock Android keyboard btw.
Click to expand...
Click to collapse
You are right. LatinIME is the keyboard. That too had got screwed up. But by changing permission, now its back.
However as I mentioned above the dialer is still absent. Under all applications, the dialer shows up. But not in drawer.
Is there any android application or windows tool to help identify which apk corresponds to which android application. Some apk files have no bearing to the actual application name. Hence all this mess happened.
Well if you open the apps folder in a root explorer, the icons of all the apps will show. So you can identify from there. It works this way in Solid Explorer for me. Also in system apps most of the apps are named according to what they are. Example, dialer is Phone.apk, contacts are Contacts.apk etc. For other Play Store downloaded apps, which names starting with com.xxxxx, you can see their icons too.
Dialer is Phone.apk in Gingerbread. The screenshot I've put below is of the /system/app folder in Solid Explorer. I think even Root Explorer shows icons like that.
Sent from my Desire HD using xda premium
sashank said:
Well if you open the apps folder in a root explorer, the icons of all the apps will show. So you can identify from there. It works this way in Solid Explorer for me. Also in system apps most of the apps are named according to what they are. Example, dialer is Phone.apk, contacts are Contacts.apk etc. For other Play Store downloaded apps, which names starting with com.xxxxx, you can see their icons too.
Dialer is Phone.apk in Gingerbread. The screenshot I've put below is of the /system/app folder in Solid Explorer. I think even Root Explorer shows icons like that.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I can see two apks in my phone with dialer icon.
Phone.apk (& Phone.odex)
TelephonyProvider.apk (& TelephonyProvider.odex)
How do I get back the dialer? This is a dual sim phone and only the stock dialer gives the option to select sim before dialing. None of the market dialers provide this option.
phone.apk is the file.
I like using fix permissions from recovery. it fixes every permission within few seconds.
RavinduSha said:
phone.apk is the file.
I like using fix permissions from recovery. it fixes every permission within few seconds.
Click to expand...
Click to collapse
I have CWM v5.0.2.8. Pls let me know how to fix permissions from recovery.
ontherocks62 said:
I have CWM v5.0.2.8. Pls let me know how to fix permissions from recovery.
Click to expand...
Click to collapse
advanced section. look through. it should be self explanatory.
ontherocks62 said:
Issued the above commands. They all now show the same as others and are back.
Unfortunately the dialer still doesn't appear. Which apk is the dialer? My phone has gingerbread.
You are right. LatinIME is the keyboard. That too had got screwed up. But by changing permission, now its back.
However as I mentioned above the dialer is still absent. Under all applications, the dialer shows up. But not in drawer.
Is there any android application or windows tool to help identify which apk corresponds to which android application. Some apk files have no bearing to the actual application name. Hence all this mess happened.
Click to expand...
Click to collapse
the dialer is Phone.apk
calisro said:
advanced section. look through. it should be self explanatory.
Click to expand...
Click to collapse
Fixed permission. Still dialer doesn't appear. :crying:
ontherocks62 said:
Fixed permission. Still dialer doesn't appear. :crying:
Click to expand...
Click to collapse
reflash the rom. easy peasy. next time careful what you delete! sry guy.
if u have a backup just restore only system partition
RavinduSha said:
if u have a backup just restore only system partition
Click to expand...
Click to collapse
I have a backup. Unfotunately, I took a backup after messing up. So after re-flashing it with the backup, it boots in the messed up state.
I downloaded one gingerbread Phone.apk yesterday. I renamed the Phone.apk and Phone.odex in my phone to Phone.apk.bak & Phone.odex.bak. Then copied the downloaded Phone.apk to /system/app. Then fixed permissions via recovery and rebooted.
To my horror, not only did the dialer didn't appear, but also the phone wouldn't detect the sim cards. It would say no connection available...
So Phone.apk is affecting other stuff too. So I deleted the new Phone.apk and renamed the .bak to its original names, fixed permissions via recovery and rebooted. The phone still wouldn't detect the sim cards.
Then I went back to recovery, cleared Dalvik cache & user data, and performed clear data & factory reset. After reboot, the phone started detecting the sim cards again.
So this leads me to believe that something else other than permissions has a role to play.
Ok, I have been trying for a while now to change the HTC lock rings and there is a really cool thread on here by mohit1234: http://forum.xda-developers.com/showthread.php?t=1262990, anyway it has a heap of lock rings. Originally I could not put them on as he made them for a different phone model. So then I uploaded my fusion.apk and sent it to him. He made me custom lock rings with both the Earth and the Captain America Shield. So everytime i try to flash it to my phone nothing happens. So I made a copy of the .zip and extracted the fusion.apk and went to copy to the /system/apps directory with both "ES File Explorer" and "Root Browser Lite". But whenever I try to copy it the phone either crashes and restarts or says copy succesful and nothing happens. This also happens when I copy a droidsansfallback.ttf (modded with the emoji icons). But the font works when it says successful. Does anyone know what is happening? Mohit1234 also suggested to push using adb, would this help at all?
Do you have flar2's remove system write protection kernel mod installed and loaded?
Sent from my HTC Desire X using xda premium
No, I don't. How would I go about installing such a thing? Is that why the font keeps reverting every half hour?
vogonpoetlaureate said:
Do you have flar2's remove system write protection kernel mod installed and loaded?
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
nickstarrs said:
No, I don't. How would I go about installing such a thing? Is that why the font keeps reverting every half hour?
Click to expand...
Click to collapse
You can find it here.
Without that patch, you can't muck about with /system
Total Crashing
Ok, I flashed a zip designed for my phone with the kernel you suggested, and my phone crashed twice (again) when copying the fusion.apk and the droidsansfallback.ttf doesn't even work when I copy it any more. Also when I plug it into my PC and choose "mount as hard disk" my phone crashes and reboots. So I am thinking I should just start again. I think I am going to flash hasoon200's "stock, rooted, deodexed" ROM.
I have tried to install this thing like 4 times, it is in my /system/lib/modules but I can't get it working. I have tried copying droidsansfllback.ttf modded with emoji into the /systom/fonts folder but when I restart it is reverted back to the old one. And seeing as I am new to this I can't decipher the instructions on how to install this.
vogonpoetlaureate said:
You can find it here.
Without that patch, you can't muck about with /system
Click to expand...
Click to collapse
nickstarrs said:
Ok, I have been trying for a while now to change the HTC lock rings and there is a really cool thread on here by mohit1234: http://forum.xda-developers.com/showthread.php?t=1262990, anyway it has a heap of lock rings. Originally I could not put them on as he made them for a different phone model. So then I uploaded my fusion.apk and sent it to him. He made me custom lock rings with both the Earth and the Captain America Shield. So everytime i try to flash it to my phone nothing happens. So I made a copy of the .zip and extracted the fusion.apk and went to copy to the /system/apps directory with both "ES File Explorer" and "Root Browser Lite". But whenever I try to copy it the phone either crashes and restarts or says copy succesful and nothing happens. This also happens when I copy a droidsansfallback.ttf (modded with the emoji icons). But the font works when it says successful. Does anyone know what is happening? Mohit1234 also suggested to push using adb, would this help at all?
Click to expand...
Click to collapse
Listen all you need to do is
Extract the fusion.apk from his zip and paste it manually using aroma file manager.
I did it using aroma and now you can see my lockscreen.
Sent from my HTC Desire X using xda premium
ranalakshay36 said:
Listen all you need to do is
Extract the fusion.apk from his zip and paste it manually using aroma file manager.
I did it using aroma and now you can see my lockscreen.
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
I have tried this using both "ES File Explorer" and "Root Browser Lite". Anyway where could I download aroma? I looked for it on Google Play but couldn't find it. If I find it I will try it, and yes I have extracted the zip and tried to copy it that way.
EDIT:
I installed Aroma, all went well with that and I copied fusion.apk as told to the /system/apps directory and bam when I restarted nothing happened, still stock ring. Can you send me the fusion.apk you used so I can try that, it would be greatly appreciated
nickstarrs said:
I have tried this using both "ES File Explorer" and "Root Browser Lite". Anyway where could I download aroma? I looked for it on Google Play but couldn't find it. If I find it I will try it, and yes I have extracted the zip and tried to copy it that way.
EDIT:
I installed Aroma, all went well with that and I copied fusion.apk as told to the /system/apps directory and bam when I restarted nothing happened, still stock ring. Can you send me the fusion.apk you used so I can try that, it would be greatly appreciated
Click to expand...
Click to collapse
Dude aroma launcher is a recovery based launcher...
Not an apk type..
Sent from my HTC Desire X using xda premium
ranalakshay36 said:
Dude aroma launcher is a recovery based launcher...
Not an apk type..
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
I know, i installed it in the recovery and it opened up etc. BUT my system is still write protected when I reboot or startup my phone it reverts to its original /system state. which brings us back to how to install the kernel. In short Aroma doesn't work until I remove write protection. I may be a noob, but I know that this simply wont work.
Not true.
Flowed from my HTC branded muffin...
nickstarrs said:
I know, i installed it in the recovery and it opened up etc. BUT my system is still write protected when I reboot or startup my phone it reverts to its original /system state. which brings us back to how to install the kernel. In short Aroma doesn't work until I remove write protection. I may be a noob, but I know that this simply wont work.
Click to expand...
Click to collapse
Aroma will work. The write protection is disabled in recovery.
Sent from my awesome fridge
nickstarrs said:
So everytime i try to flash it to my phone nothing happens. So I made a copy of the .zip and extracted the fusion.apk and went to copy to the /system/apps directory with both "ES File Explorer" and "Root Browser Lite".
Click to expand...
Click to collapse
Post here the file he made for you or the updater-script, I take a look at it. Maybe the mount point is wrong for DX.
---------- Post added at 04:32 PM ---------- Previous post was at 04:29 PM ----------
nickstarrs said:
I know, i installed it in the recovery and it opened up etc. BUT my system is still write protected when I reboot or startup my phone it reverts to its original /system state. which brings us back to how to install the kernel. In short Aroma doesn't work until I remove write protection. I may be a noob, but I know that this simply wont work.
Click to expand...
Click to collapse
In recovery, mount system first before you start the Aroma File Manager.
ckpv5 said:
Post here the file he made for you or the updater-script, I take a look at it. Maybe the mount point is wrong for DX.
Click to expand...
Click to collapse
db.tt/NEhtEyMS
ckpv5 said:
In recovery, mount system first before you start the Aroma File Manager.
Click to expand...
Click to collapse
How do I do such thing?? What does mount system even mean? Sorry for being such a noob, I'm very new to all of this
MaartenXDA said:
Aroma will work. The write protection is disabled in recovery.
Sent from my awesome fridge
Click to expand...
Click to collapse
Ok, aroma does work (I tried it with an emoji modded droidsansfallback.ttf) so that means that the fusion.apk is stuffed up. I have downloaded a desire x system dump and I am going to ask the guy to try and do it to that fusion.apk, thanks for the help everyone
nickstarrs said:
db.tt/NEhtEyMS
Click to expand...
Click to collapse
Check your PM... I post a modded zip for you.
It's nothing wrong with the zip file that you posted. It flashed ok on my ROM
Your problem I guess is due to the stock ROM that you have where you do not have busybox installed.
So I mod the updater-script so it can be installed without busy box.
nickstarrs said:
How do I do such thing?? What does mount system even mean? Sorry for being such a noob, I'm very new to all of this
Click to expand...
Click to collapse
Which recovery that you have installed ?
CWM - usb and mount - mount system
TWRP - mount - mount system