Greetings.
First details:
T-Mobile Galaxy S3 (T-999)
Android version: 4.0.4
Baseband: T999UVLEM
Kernel: 3.0.8-611599-user
Build Number: IMM76D.T999UVALEM
Problem:
I attempted to utilize the HyperX camera mod (allowing 30fps, and 30Mbit superfine settings etc) which required copying the Camera.apk over to the /system/app folder, (while deleting/renaming the old samsungcamera.apk and samsungcamera.odex files).
Here's where is gets tricky: Using Root Browser Lite I navigated to that system/app folder and renamed the files to *.apk.old" to keep them in case of problems. but, APPARENTLY I accidently renamed the Odex file to what is now shown as "SamsungCamera.odex?old". Upon using the mod I now get a force close on ALL video so I wanted to revert back, but I can't rename it BACK to .odex because of the question mark in the file name... nor can I delete it, etc. I tried to mv the file through ADB but a LV command shows the filename listed on two seperate lines.. as if it sees the "?" as a line break.
It lists it like this:
SamsungCamera.apk.old
SamsungCamera.odex
old
SamsungIME.apk
etc etc
I can't rename it through ADB because i can't figure out how to get the filename syntax correct and I can't rename it in root browser because it can't handle the file period, now.
Anyone know how to fix this? ultimately either a solution to fix it... or undo it would be amazing... I know the XDA group is amazingly intelligent..... Can anyone help me?
Please?
I can't attach files, just get someone to post the file you need. I think that should work. Also, maybe try a different file explorer like ES.
Update: ES File Explorer shows the file listed as "SamsungCamera.odex old" (note the space). Attempts to rename it through ES result in "file operation failed" popup for a second., Root Browser Lite lists it as "SamsungCamera.odex?old" (note the "?") and attempts to rename or change permissions through that program result in a "superuser permission granted" popup, but nothing changes. end result: neither work.
If the file is truly just "corrupted" or named wrong somehow, then the system isn't seeing it at all, correct?!?!? So a replacement stock odex would suffice?
Hopefully? At this point I just want the stock T-Mobile Galaxy S3 camera functionality (HD video) to work, again. Even in 720p.... However that is possible, I'll do it.
PLEASE?!?!?
ANYONE? Bueller? Bueller? ??
No video on a brand new phone isn't exactly fun..
Can anyone shed some light on renaming this file after this?? or provide the GS3 "SamsungCamera.odex" file?
Problem solved (by using another copy of the stock Odex)
For posterity:
Just to follow up.. The problem was solved with help from a member on this forum who provided the "SamsungCamera.odex" file for my T-Mobile GS3 phone, as followed in this thread.
If anyone else has this problem, or simply just needs the odex file... please see this link to this thread for that attachment.
thank you, again.
Related
Help, I uninstalled "clock 1.0" and can't restore it (system app apparently)
I uninstalled clock 1.0 because i thought it would get rid of the widget of clock pictures I didn't use. I backed up clock 1.0 on titanium backup, but now it won't restore. even after i extract the apk and install it from there manually, it says installation failed.
i don't want to do factory reset because i have already rooted the phone.
help? or point me in a much better clock app than the one that came with the galaxy s2?
Apparenly it was a system app?!? com.sec.android.app.clockpackage
ok, so after some digging i found that com.sec.android.app.clockpackage.apk still existed in system/apps but just wasn't running. I also noticed for almost every .apk, there was a .odex. But for my clockpackage, there was no .odex, maybe that's why it's not working?
on that thought, maybe anyone here can copy their .odex files for the 2 clock .apks and send them to me? Just use Root Explorer to see the system/app folder, mount R/W if you need to, then copy the 2 .odex files and then upload them somewhere? Pls?!?
if you want root explorer, holla at me via pm
jeanclaudevandamme said:
I uninstalled clock 1.0 because i thought it would get rid of the widget of clock pictures I didn't use. I backed up clock 1.0 on titanium backup, but now it won't restore. even after i extract the apk and install it from there manually, it says installation failed.
Click to expand...
Click to collapse
Stupid me did exactly the same and has exactly the same problem. Any help appreciated!
Regards, edi
same problem - thanks in advance
Well, found a solution: installed KE7 through Odin, Rootet again, everything was still there except google account binding...
Regards, Edi
THIS IS HOW I SOLVED IT. This is a superior solution to the one above as you do not need to reflash or reroot and you keep all data and settings. Apologies for not replying earlier.
1)keep your clockpackage.apk in system/apps
2)download this .odex file
3)put the file in system/apps, remember to mount r/w in rootexplorer to enable pasting it in there, then mount r/o when finished
4)turn phone off.
5)turn phone on.
(You need Root Explorer, or a similar app that will let you read/write system files) (Pls also refer to this thread)
Here's the odex file.
No success...
Guys, I did all you said here, following the step-by-step, managed to get both files in system/app folder, but still can't see the icon as if it were installed.
I have Root Explorer and Root explorer installed.
I noticed all files were set as "rw-r--r--" so I changed it on both apk and odex... I'm doing this on a Galaxy W running stock 2.3.6...
What am I forgetting???
All and any help will be deeply appreciated...
[Update]
I managed to get the ClockPackage.apk and the ClockPackage.odex from another device (running on 2.3.5 instead of 2.3.6) and now I get the following error while trying to install the apk:
"Parse Error: There is a problem parsing the package"
Does anybody know what to do?
jeanclaudevandamme said:
THIS IS HOW I SOLVED IT. This is a superior solution to the one above as you do not need to reflash or reroot and you keep all data and settings. Apologies for not replying earlier.
1)keep your clockpackage.apk in system/apps
2)download this .odex file
3)put the file in system/apps, remember to mount r/w in rootexplorer to enable pasting it in there, then mount r/o when finished
4)turn phone off.
5)turn phone on.
(You need Root Explorer, or a similar app that will let you read/write system files) (Pls also refer to this thread)
Click to expand...
Click to collapse
Mate, it might sounds silly, but where's system/apps? Can't find it, no matter what pro version of any software I use (MyBackup Pro, ES File Explorer). It's like it's missing on my phone. Can you help me more? I've the same problem for the case.
fifth_root said:
Mate, it might sounds silly, but where's system/apps? Can't find it, no matter what pro version of any software I use (MyBackup Pro, ES File Explorer). It's like it's missing on my phone. Can you help me more? I've the same problem for the case.
Click to expand...
Click to collapse
Did you do what the instructions said? They clearly say 'use Root Explorer'. If you open Root Explorer, and scroll down, you will find the 'system' folder. Inside there will be another, 'apps'. That's what the post says....
I have a rooted Galaxy M Style phone with stock Gingerbread 2.3.4 firmware. I am trying to customize my stock camera app, but am not sure what I'm doing wrong. I plan to replace the autofocus_ok.ogg with a different tune from my phone. I checked the properties of the autofocus_ok.ogg and saw it's a mono, 44100hz, and 96 bitrate file. The tune that I have has the same properties. So this is what I have done so far:
I backed up camera.apk to /system/app/camera.apk.bak and the camera.odex to /system/app/camera.odex.bak. I left a copy of camera.odex in /system/data. I copied the camera.apk to my memory card and placed the file on my computer. I renamed the file to a .rar. I then deleted the autofocus_ok.ogg and placed the tune that I wanted in that directory. Then I renamed it to autofocus_ok.ogg. I renamed the file back to .apk and transferred the file back to the memory card, then over to /system/app. The camera app will not install/not showing up on my phone. I am transferring the files through root explorer on my phone.
I worked with the original apk file again with apktool. I was able to decompile and replaced and renamed the files that I needed again. I compiled the file and transferred the file to /system/app again, but the apk will still not install. I checked the complied apk file and noticed that the file didn't have the META-INF folder, so I copied that over to. Tried to install it again by copying the file to /system/app, but it still won't show up on my phone. Is there anyway for me to change the autofocus_ok.ogg without a custom rom?
Thanks.
ImAhNoBoDy said:
I have a rooted Galaxy M Style phone with stock Gingerbread 2.3.4 firmware. I am trying to customize my stock camera app, but am not sure what I'm doing wrong. I plan to replace the autofocus_ok.ogg with a different tune from my phone. I checked the properties of the autofocus_ok.ogg and saw it's a mono, 44100hz, and 96 bitrate file. The tune that I have has the same properties. So this is what I have done so far:
I backed up camera.apk to /system/app/camera.apk.bak and the camera.odex to /system/app/camera.odex.bak. I left a copy of camera.odex in /system/data. I copied the camera.apk to my memory card and placed the file on my computer. I renamed the file to a .rar. I then deleted the autofocus_ok.ogg and placed the tune that I wanted in that directory. Then I renamed it to autofocus_ok.ogg. I renamed the file back to .apk and transferred the file back to the memory card, then over to /system/app. The camera app will not install/not showing up on my phone. I am transferring the files through root explorer on my phone.
I worked with the original apk file again with apktool. I was able to decompile and replaced and renamed the files that I needed again. I compiled the file and transferred the file to /system/app again, but the apk will still not install. I checked the complied apk file and noticed that the file didn't have the META-INF folder, so I copied that over to. Tried to install it again by copying the file to /system/app, but it still won't show up on my phone. Is there anyway for me to change the autofocus_ok.ogg without a custom rom?
Thanks.
Click to expand...
Click to collapse
erm... is the permissions set correctly rw-r--r-- ?
MoonBlade said:
erm... is the permissions set correctly rw-r--r-- ?
Click to expand...
Click to collapse
Yup, permissions were set correctly like rw-r--r--. Owner is root:root. Those are the permission that I set on the apk file like they were on the original file. I just realized that the compiled apk's from apktools doesn't show up on my phone. The apk that I created by opening up winrar and just replacing the .ogg files do show up, but I get the error "The application Camera (process com.sec.android.app.camera) has stopped unexpectedly. Please try again."
Anything else I can try or a thread to refer to?
ImAhNoBoDy said:
Yup, permissions were set correctly like rw-r--r--. Owner is root:root. Those are the permission that I set on the apk file like they were on the original file. I just realized that the compiled apk's from apktools doesn't show up on my phone. The apk that I created by opening up winrar and just replacing the .ogg files do show up, but I get the error "The application Camera (process com.sec.android.app.camera) has stopped unexpectedly. Please try again."
Anything else I can try or a thread to refer to?
Click to expand...
Click to collapse
why dont you try to push the modified apk manually using root explorer or so instead of pushing via adb ..
after decompiling apk and modifying it, compile it into some folder and then copy it into you sd card then use root explorer and manually push(copy) the apk into system/app .. give proper permissions and then reboot your phone..
Here are some guides to use apktool
http://forum.xda-developers.com/showthread.php?t=1891686
http://forum.xda-developers.com/showthread.php?t=1989533
MoonBlade said:
why dont you try to push the modified apk manually using root explorer or so instead of pushing via adb ..
after decompiling apk and modifying it, compile it into some folder and then copy it into you sd card then use root explorer and manually push(copy) the apk into system/app .. give proper permissions and then reboot your phone..
Here are some guides to use apktool
http://forum.xda-developers.com/showthread.php?t=1891686
http://forum.xda-developers.com/showthread.php?t=1989533
Click to expand...
Click to collapse
I have been pushing the modified apk through root explorer all this time. I don't even have adb install, haha. The procedure you explained have been the way I have been doing it the whole time, lol. I read the threads you posted and the procedure is the same as I've been doing it, except for the second thread. I can't grab the apktool from 4shared because I don't have an account. I am using the latest apktool 1.5.2. Also, I didn't understand what PulseDroid was talking when he said "We are NOT done just yet, we cannot use the new apk's... we have to take what we did and add it back to the original apk file to keep proper signature use something like 7zip, take the 'resources.arcs' file and any other xml files you edited out of the "-new" apk and copy them into Original apk". So I'm suppose to replace the resources.arcs and the .ogg files that I created from the new apk to the old apk? I didn't mess with any xml file.
Anyways, is there anything else I can try?
EDIT: ........I feel so embarrassed. I checked out this thread http://forum.xda-developers.com/showthread.php?t=2378177 and saw this post "Drag your replacement files into WinRAR and (here's the important part) in the Compression Method drop-down choose "Store"." All this time I have been compressing the file as "Normal" in Winrar, instead of "Store".
All in all, I did not need apktool at all. I used the original apk and opened it up in Winrar. I deleted the files that I wanted to replaced and put in the files that I wanted. Each time I put something in the file in Winrar I get a prompt for compression and instead of "Normal" compression just use "Store". It was that simple.
This helped me, thank you!
Hi,
So the situations is like this:
Just got a new LG Nexus 4, NFC enabled, GREAT!!!!
But then I start using it, and the NFC sound (everytime the phone reads a nfc-tag it makes an sound) annoys me beyond belief.
So I start looking around, it seems there's no solution, except recompiling the app.
So I learn how to compile an app (noob here), using this guide: http://forum.xda-developers.com/showthread.php?t=1860115
I'm up to the point where my apk is decompiled, and I have modified the sound files, located in my decompiled files folder respectively at res/raw/start.ogg & res/raw/end.ogg.
I modded the files using audacity, lowering the volume to zero, used them to replace the original .ogg files. The file size is a bit smaller as the original ones (1Kb difference).
Next I use the recompile command: apktool b decompiled_apk_folder_with_modified_files modded_apk_file.apk
So now I have the new nfc apk file, called NfcNci.apk, with which I replace the original file in /system/app.
Next up I reboot my phone into recovery, wipe all cache and dalvik cache, and reboot again.
First thing that pops up on my screen is a force-close message, saying that the nfc-service force closed.
Anyone who can tell me what I did wrong? Or how I can fix this?
Attached are: my decompiled-files-folder (compressed to zip)
the original NfcNci.apk file
my modded NfcNci.apk file which causes the FC's.
Any help will be greatly appreciated!!!!
S.
Looks like you're still on 4.2
The latest NfcNci.apk has some more files.
And your apk is missing the META-INF folder.
I guess that this is the problem.
But you should use "adb logcat" to ensure we're on the right track.
Micky
1 thing i would recomend is not using the actual apk you just built. instead, open your new apk with a file manager such as 7zip and remove your newly compiled files out of it, then put them into the original apk from your rom using 7zip as well! thus keeping the apk's original signature
try to copy the least amount of files from one to another, so to be safe only pull out your new .ogg files, then put them into your original apk! hope this helps
ldrifta said:
1 thing i would recomend is not using the actual apk you just built. instead, open your new apk with a file manager such as 7zip and remove your newly compiled files out of it, then put them into the original apk from your rom using 7zip as well! thus keeping the apk's original signature
try to copy the least amount of files from one to another, so to be safe only pull out your new .ogg files, then put them into your original apk! hope this helps
Click to expand...
Click to collapse
Hi, I tried this, installed 7zip, and double clicked the original apk, I opende the res/raw/ directory, and only copied the files I was using: start.ogg & end.ogg. Then I close 7zip, and send the file to my phone. But as soon as I it them to /system/apps on my phone, and reboot to recovery, wiping the dalvik cache. I get FC's on reboot (NFC-service has FC'd).
Any reasons for this?
Thanks for the help, both of you!
BTW: I'm on Android 4.3 JB
Howdy.
I'm trying to modify a .so file (libflashplayer.so), but have run into a few problems:
I first tried editing the file after it was installed from an .apk. This appears to work at first, but the edited file is quickly replaced with the original.
I then tried editing the file in the .apk package. This causes the package to fail to install (I'm guessing because the md5 in the certificates no longer matches)
Aldo tried moving a folder with the .so files from the .apk (com.adobe.flashplayer-1 which is what is created when the .apk installs correctly) directly into /data/app-lib/.The directory was created successfully but appears to be immediately deleted.
Is there a way to accomplish what I'm trying to do? If so how?
Other possibly relevant info:
My device is rooted
I did not write the code for anything in the .apk, I got it from a link on xda (pretty dubious i know but I couldn't find another option)
I'm using cyanogenmod 10.2 (based on android 4.2 I believe).
I'm editing the file with a hex editor to change a a few characters ("AND" to "WIN")
Hello there.
Maybe someone can help me...
I am on a rooted Galaxy S9+ with Pie
(see attached pic)
My problem:
My stock file explorer can not create any files or folders it seems as it only has permission for reading.
Every other file explorer has no problem.
It's only the stock one.
In my App list, there are all permission set.
So my question:
Does anyone know how to check the -r-w-x permissions for this stock file explorer?
And how to change them?
What can I do?
All other File Explorer works like a charme...
But I need the stock one, because when I want to print to PDF, it only uses the stock one.
A deinstallation and new installation does not help.
Many thanks!!
Push :-/
edit/
After a dirty flash of my ROM and reflash of Firmware everything works like a charme