Just thought to share this...I installed it using root explorer & thought it looked good on here. All credit to proxuser the op
http://forum.xda-developers.com/showthread.php?t=1317542
I moved the original LatinIME.apk into my sdcard, and then moved the new one into /system/apps/. Rebooted, and keyboard doesn't work. Tried reinstalling the apk using hte file in system/app but it fails... Gonna try the flashable now.
-------
Flashable fails, status 0.
Can you explain exactly how you installed it on your device?
uhh186 said:
I moved the original LatinIME.apk into my sdcard, and then moved the new one into /system/apps/. Rebooted, and keyboard doesn't work. Tried reinstalling the apk using hte file in system/app but it fails... Gonna try the flashable now.
-------
Flashable fails, status 0.
Can you explain exactly how you installed it on your device?
Click to expand...
Click to collapse
Did you set the permissions correctly?
cheesebeard said:
Did you set the permissions correctly?
Click to expand...
Click to collapse
rw-r-r correct?
I use root explorer, the permissions box should look like this:
[x] [x] [ ]
[x] [ ] [ ]
[x] [ ] [ ]
cheesebeard said:
I use root explorer, the permissions box should look like this:
[x] [x] [ ]
[x] [ ] [ ]
[x] [ ] [ ]
Click to expand...
Click to collapse
Yup. I'm stuck without a keyboard until detailed installation instructions are posted. Gonna reinstall Eclipse (cause my damned nandroid MD5 is corrupt -.-) and try again later.
Those settings plus a reboot worked for me good find!
Tap'n on my LIBERATED X2
aardvark502 said:
Those settings plus a reboot worked for me good find!
Tap'n on my LIBERATED X2
Click to expand...
Click to collapse
Seems It works on Liberty X2 but not Eclipse. Oh well.....
uhh186 said:
I moved the original LatinIME.apk into my sdcard, and then moved the new one into /system/apps/. Rebooted, and keyboard doesn't work. Tried reinstalling the apk using hte file in system/app but it fails... Gonna try the flashable now.
-------
Flashable fails, status 0.
Can you explain exactly how you installed it on your device?
Click to expand...
Click to collapse
I pretty much did the same thing u did. I went to system/apps, renamed my old keyboard incase I want to switch back later, then installed the new one & changed permissions. Then rebooted & it worked great. Not too sure what's going on with yours tho..I am on liberty rom tho..maybe that's it??.. not sure
EDIT: I did use the single apk...the second download, not the first flashable zip, if that may help
rp076 said:
I pretty much did the same thing u did. I went to system/apps, renamed my old keyboard incase I want to switch back later, then installed the new one & changed permissions. Then rebooted & it worked great. Not too sure what's going on with yours tho..I am on liberty rom tho..maybe that's it??.. not sure
EDIT: I did use the single apk...the second download, not the first flashable zip, if that may help
Click to expand...
Click to collapse
Guess I'll just try again after I partially recover from this SBF
---
Retried and it worked nicely... no idea wtf (for lack of a better phrase) happened the first time.
Related
laymil has posted a much better script for this. As such I will be discontinuing my work on this for now. Not for any hard feelings, but because it is now beyond me to help any further.
As always I am glad to have helped the community in some small way. Thank you all
CHEERS
Geniusdog254 Posted the exact lines in the build prop that needed to be changed. This is a pretty common fix for problems like this between versions of Android. There was some concern however that you may miss some of the newer apps released only for Froyo. I wrote some simple scripts that will fix this for us.
Simply: One puts the Froyo build.prop on your phone. The other puts the modded build.prop on your phone.
Prerequisites
YOU MUST HAVE GSCRIPT INSTALLED
YOU MUST HAVE BUSYBOX INSTALLED
(IF YOU ARE USING PAULS FROYO ROM FROM HERE
http://forum.xda-developers.com/showthread.php?t=686631
IT DOES NOT HAVE BUSYBOX INSTALLED
Also--
There are now 2 downloads.
One will reboot your phone automatically
One will not!
(I recommend this one for anyone that has problems, or doesn't know ADB well.)
Installation
Code:
Download the attached .zip file
Place the "buildprop" folder in the root of your sdcard
Place both "Normal_Froyo.sh" and "Modded_Froyo" files in the gscript folder on your sdcard
Code:
Open Gscript
Press menu and select Add Script
Press Load File button
Select Normal_Froyo file
Press Save button at bottom
Repeat for Modded_Froyo file
After that all you have to do is open gscript and select which one to run.
Normal_Froyo will give you stock froyo build.prop and let you see froyo only apps
Modded_Froyo will give you the market fix build.prop
You can also create shortcuts directly on your homescreen for each script if you wish
-----------------------------------------------
I've decided to skip the update.zip, I've found no way to copy the scripts to the gscript folder on the sdcard this way.
I'm going for an app instead.
P.S. I've never written an app before, java looks like russian to me lol. So if anyone has any tips, or knows any good tut's let PM me and let me know.
------------------------------------------------
fixed no buildprop folder
added NON-autoreboot download.
buildprop switcher v0.3.zip ORIGINAL
buildprop_switcher_no_rebootv0.3.zip NO REBOOT
buildprop swticher v0.3.1.zip DOWNLOAD THIS ONE
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Dayzee said:
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Click to expand...
Click to collapse
So sorry lol Didn't notice until I was making the update.zip that I didn't put the other files in a folder IN the zip. Just make a folder on your sdcard called buildprop. and put them in there.
BTW testing the flashable update.zip method right now
thx, seems to work
so no more *#*#etc.. afterwards?
watercool said:
thx, seems to work
so no more *#*#etc.. afterwards?
Click to expand...
Click to collapse
Right.. the checkin service runs on each reboot. So it is not needed.
Worked just fine, but I did have to do the checkin thing. Possibly had poor signal but checkin hadn't done on reboot. Worked fine after that...
Dayz xx
followinginsanity said:
Right.. the checkin service runs on each reboot. So it is not needed.
Click to expand...
Click to collapse
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Namuna said:
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Click to expand...
Click to collapse
The reboot is built into the script. On my phone, if I checkin, the apps still don't show till I reboot. But show if I only reboot. If checkin alone works for you though, you can remove the reboot command from the script.
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
This worked great for me I also solved my (unrelated) prob with SlideIt by forcing the dictionary to save in the settings, so I'm no longer bothered about losing shortcuts stuff on a reboot.
Dandy!!
tested again with a second n1. works perfect! automated checkin works perfect.
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
Mine did this as well, though I am unsure why just yet. Been busy all day.
Mikey1022 said:
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
Click to expand...
Click to collapse
The only thing I changed from the stock to the "modded" build.prop were these 2 lines
from this
ro.build.description=passion-user 2.2 FRF50 38042 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
to this
ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
I didn't add anything else to these. If you would like other things added to the build.prop files. You are welcome to edit them yourselves, or let me know what things you want changed, and I can include them.
I can make it user friendly. With descriptions for each modded line, then you can simply un-comment the options that you want.
PS: I thought I had the flashable update ready, but the update-script is giving me problems. ANYONE that wants to help please let me know. I'd really like to get this out to everyone.
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
same thing here....ANY IDEAS????????????
This is a great find, inductions were perfect and easy to follow. Not one issue getting all my paid apps back! Thank again!
JDMSirEK4 said:
same thing here....ANY IDEAS????????????
Click to expand...
Click to collapse
To anyone that can't get thier phone to boot all the way after doing this
Its not a big deal. Your phone booted. But the build.prop didn't get copied before the reboot.
If you did a nandroid before you tried it. Restore that!
If you didn't, OR you know how to use adb. Do this
Code:
adb remount
adb push [COLOR="red"]/path/to/build.2.1(or)build.2.2[/COLOR] /system/build.prop
adb reboot
I hope to have this fixed quickly.
ANYONE WHO'S PHONE WILL NOT BOOT AFTERWARDS!
Check and make sure you put the files in the right place.
build.2.2
&
build.2.1
go in
build.prop FOLDER ON YOUR SDCARD
that was the only reason I got the error, i deleted the files off my card when i was testing the flashable update.
If you still get an error. open both files in the gscript folder, and remove or comment out the reboot line. Then tell me what error you get in gscript.
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
r0adki111 said:
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
Click to expand...
Click to collapse
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
dictionary said:
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
Click to expand...
Click to collapse
Nope they're not on SD. I'll try the fc of launcher.
Ok it worked thank you! but my xiia widget still is not back and I'm assuming others. Anything I can do for the widgets?
Ok installed and reinstated the app. Works great thx again.
Update:
Ok after another reboot, apps don't show again. FC the launcher they come back but not the widgets.. Grrrrrr...
Does anyone have the white Swype keyboard from Eclipse 1.3? If not, can someone explain how to pull it from the ROM?
To confirm, what ROM are you currently running?
The SWYPE provided is the STOCK swype provided by a stock X2 build. The black keyboard is Swype beta, and by far better, can I ask why you want to change?
Heres the solution anyway:
YOU WILL NEED ROOT EXPLORER! Or you can make a flashable .zip.
Go to Manage Applications>Delete Data for Swype(everything you can delete)
1. Open Root Explorer
2. Delete data/data/com.swype.android.inputmethod(mount R/W to do this)
3. Delete data/dalvik-cache/[email protected]@[email protected]
4. Delete data/cache/dalvik-cache/[email protected]@[email protected]
5. Delete system/lib/libSwypeCore.so ***You may not have this, but check anyway***
6. Delete data/app ***anything SWYPE RELATED***
7. Delete system/app ***anything SWYPE RELATED***
NOW GRAB THESE NEXT FILES FROM ANY STOCK BUILD OR ROM THAT HAS THE "WHITE" SWYPE KEYBOARD(i.e. Eclipse 1.3.. or so you said it was on that ROM).
You will be putting the files in the EXACT, SAME LOCATION!
8. Grab system/app **swype.apk**
9. Grab system/lib/libSwypeCore.so
10. Set both ^^ file permissions to rw-r-r(see graph below).
Perms:
[X] [X] [ ]
[X] [ ] [ ]
[X] [ ] [ ]
11. Reboot and Enjoy the OG Swype.
Think there is any way to get this working with the newest swype version, cause it looks badass......
http://forum.xda-developers.com/showthread.php?t=1286330
guy won't respond when i ask about it. Is it possible?
Tried this on cm7 dx2 won't Swype but will tap entry. It is switched to Swype keyboard and looks ok just won't Swype.
Sent from CM7 DX2 xda app
Peperm1nt said:
To confirm, what ROM are you currently running?
The SWYPE provided is the STOCK swype provided by a stock X2 build. The black keyboard is Swype beta, and by far better, can I ask why you want to change?
Heres the solution anyway:
YOU WILL NEED ROOT EXPLORER! Or you can make a flashable .zip.
Go to Manage Applications>Delete Data for Swype(everything you can delete)
1. Open Root Explorer
2. Delete data/data/com.swype.android.inputmethod(mount R/W to do this)
3. Delete data/dalvik-cache/[email protected]@[email protected]
4. Delete data/cache/dalvik-cache/[email protected]@[email protected]
5. Delete system/lib/libSwypeCore.so ***You may not have this, but check anyway***
6. Delete data/app ***anything SWYPE RELATED***
7. Delete system/app ***anything SWYPE RELATED***
NOW GRAB THESE NEXT FILES FROM ANY STOCK BUILD OR ROM THAT HAS THE "WHITE" SWYPE KEYBOARD(i.e. Eclipse 1.3.. or so you said it was on that ROM).
You will be putting the files in the EXACT, SAME LOCATION!
8. Grab system/app **swype.apk**
9. Grab system/lib/libSwypeCore.so
10. Set both ^^ file permissions to rw-r-r(see graph below).
Perms:
[X] [X] [ ]
[X] [ ] [ ]
[X] [ ] [ ]
11. Reboot and Enjoy the OG Swype.
Click to expand...
Click to collapse
Thanks but does that mean I have to flash back to Eclipse 1.3? I'm running the MIUI Beta1.
swbf2lord said:
Thanks but does that mean I have to flash back to Eclipse 1.3? I'm running the MIUI Beta1.
Click to expand...
Click to collapse
no, you can grab the files out of the flashable.zip
Also to the theme question, Do you want to color the Beta Swype? or the Stock Swype?
The newest swype beta, you can not like the guy stated so easily. It is more than likely a smali file that would need to be edited. That would give you a start. But the problem is, each time Swype puts out an update, you would more than likely have to change it. This is not 100%, but I would imagine the edits would be smali files now.
For the guy with tapping issues, check to ensure you have correct permissions set, if so, then there is something that did NOT get deleted in the data folder, Try to switch from Stock Keyboard to Swype Keyboard to see if it fixes the error.
I just decided to keep using the beta. I just missed some off the old features. Used to highlight words when you touched them and it uses nuance voice instead of Google. It auto selects the wrong words more often in my opinion
Sent from CM7 DX2 xda app
Have you tried looking in the Swype settings?
Tapin' the Talk on the xSquared
Damn! Thanks for the info guys, guess were stuck with the ugly orange
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
(Note: I apologize if i have posted in a wrong forum, so please guide me here, i haven't had the time to read all the rules coz of this problem that iwant to be fix asap.Thanks and Respect)
I have ah CHINA version of Samsung Galaxy Ace s5831i, and because of the chinese apps that i want to get rid off, i flashed my phone to s5830i. (I think i used the files from youtube video. Everything seems to be fine except for the camera which i read one of the common fault when flashing this version but i also read that it can be replaced by an apk file (Which i think can only be replaced when rooted) So here is what i want to ask you i tried flashing it back to stock rom which use a single file from sammobile but i always get this (See attached picture)
Please be kind to help me in fixing my phone through flashing and getting back its camera if possible without rooting/ with rooting. Thanks!
Gkaizoku said:
(Note: I apologize if i have posted in a wrong forum, so please guide me here, i haven't had the time to read all the rules coz of this problem that iwant to be fix asap.Thanks and Respect)
I have ah CHINA version of Samsung Galaxy Ace s5831i, and because of the chinese apps that i want to get rid off, i flashed my phone to s5830i. (I think i used the files from youtube video. Everything seems to be fine except for the camera which i read one of the common fault when flashing this version but i also read that it can be replaced by an apk file (Which i think can only be replaced when rooted) So here is what i want to ask you i tried flashing it back to stock rom which use a single file from sammobile but i always get this (See attached picture)
Please be kind to help me in fixing my phone through flashing and getting back its camera if possible without rooting/ with rooting. Thanks!
Click to expand...
Click to collapse
First you have posted in correct section don't worry just now follow these thread
http://forum.xda-developers.com/showthread.php?t=1840645
On his first post you ll get to see firmware repacked by him download one from two ,
After downloading unzip it you will be seeing 3Files Modem , CSC, PDA , put that in Odin and flash it , after booting up root it and then Replace the camera apk .
Hitesh2626 said:
First you have posted in correct section don't worry just now follow these thread
http://forum.xda-developers.com/showthread.php?t=1840645
On his first post you ll get to see firmware repacked by him download one from two ,
After downloading unzip it you will be seeing 3Files Modem , CSC, PDA , put that in Odin and flash it , after booting up root it and then Replace the camera apk .
Click to expand...
Click to collapse
I followed the link guide you gave me and it was the same files i used when i flashed my phone. I reflashed it earlier and it was oka, i also rooted it through sd card. How can i replace my camera apk? Would you please be so kind to give a detailed guide for me. Thanks
Try this,
http://forum.xda-developers.com/showthread.php?t=2639940
Sent from my Galaxy Ace GT-S5830 using xda app-developers app
Gkaizoku said:
I followed the link guide you gave me and it was the same files i used when i flashed my phone. I reflashed it earlier and it was oka, i also rooted it through sd card. How can i replace my camera apk? Would you please be so kind to give a detailed guide for me. Thanks
Click to expand...
Click to collapse
Ok so now your phone is working right ?
So now download Root browser from playstore
Then open it and now go to device /system/Apps / here now find Camera.apk and delete it after that go back to your sd card copy camera.apk and move it to again above location and set permissions on it , they must be look like RW-R-R
Thats it your done.
Hitesh2626 said:
Ok so now your phone is working right ?
So now download Root browser from playstore
Then open it and now go to device /system/Apps / here now find Camera.apk and delete it after that go back to your sd card copy camera.apk and move it to again above location and set permissions on it , they must be look like RW-R-R
Thats it your done.
Click to expand...
Click to collapse
Yes, its working now. If it's not too much can you provide some links for that -rw-r-r ? Coz what i find is rwxr-x, and also your talking about permissions (Do i need to tick the check box of Read,Write,Execute on Owner lane?)
I apologize for asking too much questions, thank you for understanding
Gkaizoku said:
Yes, its working now. If it's not too much can you provide some links for that -rw-r-r ? Coz what i find is rwxr-x, and also your talking about permissions (Do i need to tick the check box of Read,Write,Execute on Owner lane?)
I apologize for asking too much questions, thank you for understanding
Click to expand...
Click to collapse
I tried changing permissions of the camera apk (from rwxrr to rw-r-r) and pasting it on the systems folder using root browser like you said then after that i restarted my phone and saw the camera app again. But sad to say it's still not working and saying error message. What should i do next? Did i do something wrong?
Gkaizoku said:
I tried changing permissions of the camera apk (from rwxrr to rw-r-r) and pasting it on the systems folder using root browser like you said then after that i restarted my phone and saw the camera app again. But sad to say it's still not working and saying error message. What should i do next? Did i do something wrong?
Click to expand...
Click to collapse
First delete old one and do one reboot and then check wether it gets deleted or not , then copy the another camera.apk which you have to system/apps and set permissions on it after doing again reboot your phone than see wether the camera.apk is there or not and check it .
Hitesh2626 said:
First delete old one and do one reboot and then check wether it gets deleted or not , then copy the another camera.apk which you have to system/apps and set permissions on it after doing again reboot your phone than see wether the camera.apk is there or not and check it .
Click to expand...
Click to collapse
Followed it sir, still error message
you want the stock odexed camera apk?? the apk is in the attachment and the odexed file is also attached just delete the old camera.apk and the .odex file from the /system/apps directory reboot and then move both the files to /system/apps and change permissions to rw-r-r and then reboot the device and report
HOPE IT HELPS!
[email protected] said:
you want the stock odexed camera apk?? the apk is in the attachment and the odexed file is also attached just delete the old camera.apk and the .odex file from the /system/apps directory reboot and then move both the files to /system/apps and change permissions to rw-r-r and then reboot the device and report
HOPE IT HELPS!
Click to expand...
Click to collapse
There is no odex file attached in your file, just camera apk. I tried deleting both apk and odex in system/apps, Now the camera app doesn't show up after reboot -_-
Gkaizoku said:
There is no odex file attached in your file, just camera apk. I tried deleting both apk and odex in system/apps, Now the camera app doesn't show up after reboot -_-
Click to expand...
Click to collapse
actually the site doen't alows the .odex files to be attached in the attachments
[email protected] said:
actually the site doen't alows the .odex files to be attached in the attachments
Click to expand...
Click to collapse
Its fine, i already reflashed my fone and got the odex file. But same problem, (Camera failed, errorhandlermessage-1)
Gkaizoku said:
Its fine, i already reflashed my fone and got the odex file. But same problem, (Camera failed, errorhandlermessage-1)
Click to expand...
Click to collapse
flash stock rom over again and this time wipe the data, cache and report
[email protected] said:
flash stock rom over again and this time wipe the data, cache and report
Click to expand...
Click to collapse
Still the same..
Gkaizoku said:
Still the same..
Click to expand...
Click to collapse
Try any camera app from play store
Sent from my GT-S5830i using Tapatalk 2
amolgosavi said:
Try any camera app from play store
Sent from my GT-S5830i using Tapatalk 2
Click to expand...
Click to collapse
Doesn't work Force closes
Gkaizoku said:
Followed it sir, still error message
Click to expand...
Click to collapse
Can you tell me more about the error message you are getting?
mahithm said:
Can you tell me more about the error message you are getting?
Click to expand...
Click to collapse
errorhandlermessage -1 camera failed.
EDIT: Found the original bootanimation file in a different thread -- but when I replaced it back in the system/media folder (checking to make sure permissions were set to 0644), it still doesn't work. I'm now officially confused -- any help would be greatly appreciated.
Hey guys -- I tried to change the boot animation with Rom Toolbox but something appears to have gone kablooey. Still boots, no issues there -- just no animation. I've tried restoring the back up I made with RT -- no dice. Also tried putting a manual backup copy of the zip I'd made in the system/media folder, changed the permissions to 644, and rebooted -- also no dice.
Can some kind soul upload the original bootanimation.zip so I can try that one out?
Alternately, if anyone has had any success changing the stock bootanimation -- any idea what I might be doing wrong? Any help is GREATLY appreciated.
Thanks much.
Wall of text so I'm just gunna post
http://forum.xda-developers.com/showpost.php?p=54461479&postcount=3
Bootanimation needs rw-r--r--
Custom animations is recommended to match resolution of the display
marlowe310 said:
EDIT: Found the original bootanimation file in a different thread -- but when I replaced it back in the system/media folder (checking to make sure permissions were set to 0644), it still doesn't work. I'm now officially confused -- any help would be greatly appreciated.
Hey guys -- I tried to change the boot animation with Rom Toolbox but something appears to have gone kablooey. Still boots, no issues there -- just no animation. I've tried restoring the back up I made with RT -- no dice. Also tried putting a manual backup copy of the zip I'd made in the system/media folder, changed the permissions to 644, and rebooted -- also no dice.
Can some kind soul upload the original bootanimation.zip so I can try that one out?
Alternately, if anyone has had any success changing the stock bootanimation -- any idea what I might be doing wrong? Any help is GREATLY appreciated.
Thanks much.
Click to expand...
Click to collapse
I've been using the ones found here
http://forum.xda-developers.com/showthread.php?t=2814467
Nice an easy just renaming the original with a .bak extension, then making sure the permissions are RW-R-R
- Tapatalked from the G3
Mistertac said:
I've been using the ones found here
http://forum.xda-developers.com/showthread.php?t=2814467
Nice an easy just renaming the original with a .bak extension, then making sure the permissions are RW-R-R
- Tapatalked from the G3
Click to expand...
Click to collapse
Thanks for the idea -- I went ahead and tried the ones in that thread, but I can't get anything up and running. Has anyone managed to change the VZW models' bootanimation successfully? If so, I'd love to get a walkthrough of what they did to actually get it running.
But frankly at this point, I'd just love to get ANY animation up and running.
Last question -- would reflashing the entire phone via the TOT method restore the bootanimation? Because frankly I'm willing to.
marlowe310 said:
Thanks for the idea -- I went ahead and tried the ones in that thread, but I can't get anything up and running. Has anyone managed to change the VZW models' bootanimation successfully? If so, I'd love to get a walkthrough of what they did to actually get it running.
But frankly at this point, I'd just love to get ANY animation up and running.
Last question -- would reflashing the entire phone via the TOT method restore the bootanimation? Because frankly I'm willing to.
Click to expand...
Click to collapse
Yea I'm on a Verizon G3
I simply downloaded the one I liked from that thread. Then with ES File Explorer I enabled Root Explorer then I mounted System RW
Then I went and renamed the stock one in /System/Media To BootAnimation.bak
Then I just pasted the downloaded one into that same folder and made sure it's permissions were RW-R-R
Worked just fine, you doing it that way??
- Tapatalked from the G3
That's exactly what I did, except I used FX File Explorer instead of Root Explorer. I also just tried it with RE, no dice either. I am MOST confused.
marlowe310 said:
That's exactly what I did, except I used FX File Explorer instead of Root Explorer. I also just tried it with RE, no dice either. I am MOST confused.
Click to expand...
Click to collapse
Hmmmm you tried ES ? And just curious what SuperUser are you using. I use SuperSu
- Tapatalked from the G3
Mistertac said:
Hmmmm you tried ES ? And just curious what SuperUser are you using. I use SuperSu
- Tapatalked from the G3
Click to expand...
Click to collapse
Haven't yet tried ES, but I also use SuperSu.