Database Develop

How to get the original camera.apk back?

I'm modifiying my own rom, and tring to find a way to recover the HTC camera to the stock one.
I did the following step but failed:
1. delete the /system/app/camera.apk and HTCAlbum.apk
2. paste the original camera.apk to /system/app
3. repack the rom and flash
But nothing happened, even there is no camera icon in the menu.
How should I get the stock one back? There is some bug with the HTC camera...

You can just push it. If you change it within the ROM and flash you must resign it.

alritewhadeva said:
You can just push it. If you change it within the ROM and flash you must resign it.
Click to expand...
Click to collapse
Is there any way to resign it? I want to cook my own rom instead of pushing it every time.

zhouzian said:
Is there any way to resign it? I want to cook my own rom instead of pushing it every time.
Click to expand...
Click to collapse
What OS are you using? Windows or Linux

alritewhadeva said:
What OS are you using? Windows or Linux
Click to expand...
Click to collapse
I'm on Windows...
Now I have find the way to resign the package. But I find there is a odex file following the same name apk file. Should I copy the odex file along with the apk file into the app directory?
My rom does not contain any odex file while another rom have many of them. Could any one tell me why?

zhouzian said:
I'm on Windows...
Now I have find the way to resign the package. But I find there is a odex file following the same name apk file. Should I copy the odex file along with the apk file into the app directory?
My rom does not contain any odex file while another rom have many of them. Could any one tell me why?
Click to expand...
Click to collapse
Odex optimization is just optimization. Copy the .odex file along with the .apk if its available.

The HTC camera has a bug that if you half-push the camera button, it will not only focus but also take a photo, not like the original one does.
I have done the following and both of them failed,
1. copy the camera.apk from JF 1.5, resigned the rom, and flash... There is no icon appearing in the menu
2. copy the camera.apk and odex file from ION build, resign and flash... The phone can not start up at all. It freeze at ANDROID logo.
I'm wondering if I have done in the wrong way... Could you offer some help?
Thanks in advance.

try to get the camera from the crc1 build

The problem is where to get...
All the other builds from CRC1 contain the odex file, which will broke the startup process.

could anyone send me the camera.apk and libcamera.so from CRC1?
just mail me: [email protected]

get it here http://forum.xda-developers.com/showthread.php?t=538456 donwload one of those ROMS

NO...it doesn't work. There is an odex file coming alone with the apk file. If I copy the apk and odex files into the CM rom, it will fail to startup. Seems CM rom can only accept standalone apk file.

Deodexed stock Telus/Koodo rom

I'm looking for a deodexed version of the stock Telus/Koodo (Canada) rom for Galaxy Ace. I have the odexed version, but I'm not sure how to deodex. If anyone knows where I can get the deodexed version, or can help me with deodexing, it would be greatly appreciated.

Quietly, THIS IS DEVELOPMENT SECTION and not Q&A or GENERAL, POST IT THERE, here will be posted roms! READ THE XDA RULES BEFORE POSTING -.-

I only know how to deodex on Windows.
First have/download your SG Ace firmware (Canada)
Extract your firmware contents using MagicISO to: firmware_name\system
Download AutoDEOTool1.0.4 (Just a modified version of the tool, including updated binaries)
Unzip it to a directory without spaces e.g: C:\
Move/Copy your firmware's apps and framework files to: _app & _framework
Run AutoDEOToolMain.bat
Hit 2 to be specific.
To find your bootclasspath, just download Terminal Emulator on your Android phone
Run the command: echo $BOOTCLASSPATH
To save it in your sdcard, run: echo $BOOTCLASSPATH>>/sdcard/bootclasspath.txt​
Open the bootclasspath.txt, remove any "/system/framework/" codes (without the quotes) then save it
Now copy everything in bootclasspath.txt
Then in the AutoDEOToolMain windows, paste your bootclasspath & hit enter
This will deodex all files in _app & _framework
NOTE: If there are still some odexed files left, then use dsixda's kitchen to deodex the remaining files.​
Now copy/move all files in _app to your firmware's /system/app folder
Copy/move all files in _framework to your firmware's /system/framework folder
Now you have a deodexed Canada firmware!
Download these rom_tools and extract it to the root of the extracted firmware (firmware_name)
Now add the boot.img
Zip it and to flash it!

Thanks, I'll try that tonight. What exactly do the rom tools do? I looked at the archive, and I'm pretty sure busybox means root, but what about the rest?

sauron82 said:
Thanks, I'll try that tonight. What exactly do the rom tools do? I looked at the archive, and I'm pretty sure busybox means root, but what about the rest?
Click to expand...
Click to collapse
data folder is optional to include
META-INF folder is to flash the ROM
format.sh formats your Ace/Gio
installbusybox.sh installs busybox
mkfs.ext4 is the tool that format.sh uses

[Q] 5839i odex

hi
just use an application to move some of my application to system when i tried ask me if i want to move the odex file also I found what is odex file but i didnt get it what is better to do copy them or not what is better?
thank you

lklo330 said:
hi
just use an application to move some of my application to system when i tried ask me if i want to move the odex file also I found what is odex file but i didnt get it what is better to do copy them or not what is better?
thank you
Click to expand...
Click to collapse
First of all WRONG SECTION, this is GTS5830 Q&A Thread
If you want to move an app to system partition and your rom is odex you need to move both files .apk+odex, but if you only move .apk it could work too without odex file, try moving only .apk, if it doesn't work move odex file too and don't forget to set the correct permissions

[Q] Rom Development Help

Hi.
I am trying to build a custom rom with base as stock rom(XXLT5).
I went through some tutorials on XDA, but they were only some basic stuff.
I had lot of questions in mind,and after searching for hours didn't get some help,so posted so maybe some one can help.
I flashed my own rom with some build.prop tweaks and changed wallpaper in framework-res.apk.
But it flashed with no problems.
1] I had lost root but I used Philz kernel(copied all stuff into respective folder)
2]I don't get about the META-INF Folder because I tried to put some s4 mods such as sec.settings.apk,s4 status bar,they also had META-INF but I didn't know what to do with it. I copied the apk of sec.settings into preload /syslink/system/app.
3]When the rom started default-wallpaper didn't changed and any mods didn't applied,so don't know what to do.
4]Will this work if I unzipped from md5 file(stock rom) and then Linux reader I extracted all files and modify it?
because in tutorials the mention to extract from rom using terminal emulator
Can please any-one say what should I do,and where to put META_INF folder,because all apks aur mods has META_INF folder and will replace every time I put a mod in it.
Please Help Guys.....:crying:

[Developing Module] framework .jar files are modified but are not loaded by Android

Hi all.
I am developing a magisk module that modifies system/framework/services.jar and some APKs using Magic Mount for Pokemon GO and other games.
I am using the Magisk Module template where I have added relevant files/folders to system.
The APKs I added work successfully.
But the framework .JAR files such as services.jar that I added are not loaded by Android after reboot.
As in, the .JAR files are replaced successfully, but Android exhibits no change, as if it was not using them and using instead the stock .JAR files.
I tried checking via md5sum in the terminal whether the services.jar file had in fact been swapped for the one embedded in my Magisk Module.
It had been successfully changed.
Maybe the OS wasn't loading these .JAR files at all, so as an experiment, I tried swapping services.jar for an empty file.
The phone still booted, and running md5sum and cat confirmed that system/framework/services.jar was an empty file.
My best guess is that framework files are loaded way before system/app APKs, but I found no information regarding my issue via Google.
I hope that someone here could please offer some quick tip or wisdom. Thank you in advance.
P.S.: I checked the open source Magisk modules I could find, and those that used framework .JAR replacements did not implement anything other than the basic template. An example: SonyFramework (My account can't post links yet).

Did you deodex your ROM, or is it a deodexed ROM?
I think you can only patch framework classes on deodexed ROMs.

Fif_ said:
Did you deodex your ROM, or is it a deodexed ROM?
I think you can only patch framework classes on deodexed ROMs.
Click to expand...
Click to collapse
Thank you for the suggestion.
The ROM I'm working on is Stock and Odexed by default.
The .JAR files I am including in the Module are Deodexed mods of the stock ones.
I tried the following as per your reply:
A) deodexing the whole ROM
B) deodexing the whole /system/framework/*
C) deodexing /system/framework/services.jar and removing odex residue (services.odex)
Unfortunately the device won't boot with A or B :S
With C it boots correctly, but the main issue remains.
---
An interesting behavior I found, is that when substituting (stock odex services.jar) with (modded deodexed services.jar),
the /system/framework/oat/arm/services.odex and other odex residue disappears for services.jar.
This along with the md5sum matching the modded version makes me think that maybe /system/framework gets loaded before Magic Mount gets to modify it.
Digging through open source Magisk modules I am yet to find the missing piece.
Thank you for your help Fif_, and to whoever takes the time to read my thread

Have a look at this thread. https://tapatalk.com/shareLink?url=...3793&share_type=t
[MODULE] Smali Patcher 0.8 and compare methods.
The module to replace patched, de-odexed services.jar definitely works.

shoey63 said:
Have a look at this thread (...)
Click to expand...
Click to collapse
Thanks, "Smali Patcher" was indeed a good clue.
What I found in the "Smali Patcher" project:
-> services.odex was being deleted
But I also needed to modify framework.jar
unfortunately there is no "framework.odex" file.
Googling around seems that framework.jar's odex companion is stored in "/system/framework/arm/boot.oat", but boot.oat contains many more unrelated .jars :S
After fully Deodexing the WHOLE ROM, the Magisk Module works.
I wonder if there is a way to remove framework.odex from boot.oat... that would be very useful.
Thank you guys for your help,