On my Droid 3, I recently flashed the Google Now zip and followed the instructions on this site. It has been working great so far.
I noticed that the zip itself matches the folder hierarchy of the phone system folders. Am I correct in understanding that if I were to replace the Velvet.apk with the newest version of Google Search (after renaming it properly) that if I flashed this new zip, it would give me the updated Google Search/Google Now?
Related
Hi all,
I'm trying to add APK files to custom rom (my last try was Pyramid3D v7.3.0 ROM).
In each ROM file (ZIP file), I noticed APK files were installed in two folders:
data\app: which, as far as I understand, contains applications which can be unistalled after flashing
system\app: for applications which cannot be deleted after flashing (except using ADB commands or tools such as Titanium Backup)
I tried both to add my apk files to each of those folders using WinRAR without unzipping the ROM (simply using Drag N Drop). Then flashed (with signature verification disable), but among all APK files I put, only one is successfully installed (french apk file called "Page Jaune").
Of course, I can install remaining APK files after flashing but I really don't understand why some are installed and some not...
Any idea?
Try this thread http://forum.xda-developers.com/showthread.php?t=1198035
lol google search sent me to this page, thanks for the link it's exactly what I was looking for
Here's the deal...I downloaded youtube v2.4.4 from here. I opened it in 7zip and extracted the res folder so I could re-theme it. I made my changes then put the res folder back into the original apk. Now this is where the problem occurs. I can't for the life of me figure out how to re-sign the .apk! I have tried every single apk-signer out there to no avail. I have put it in apkManager then decompiled it optimized PNGs recompiled then signed then zipaligned but EVERY time I install it on my phone I get either "Application not installed." or "There is a problem parsing the package." I have uninstalled all versions already on my phone through Titanium Backup prior to installing my themed one. I have manually put it in /System/app and changed permissions and rebooted. NOTHING I do works. I have adb and java installed and in the PATH. I have tried every possible solution I have found on the internet and none work. Any help would be appreciated. Thank You!
P.S. I have an HTC Thunderbolt running the latest build (3/17/12) of ThunderStick Full Blown Sense 3.0 (Thread for this ROM here)
Here is the edited res folder - Maybe someone can look at or use it for troubleshooting.
Thanks again for any input on this problem.
go to market and search and download zipsigner2. open it and navigate to the app and then chose and output and save it as an .apk file and it should install like normal
I created a zip for people who dont want to use a custom rom, but want Google on their device.
This zip contains stock odex files for a working Google Play Setup.
DOWNLOAD GOOGLE PLAY SET UP
Before the eye rolling starts, please note i've Googled and searched for a solution on XDA extensively, with very little help concerning creating a flashable Zip file for Lollipop. Most of the guides and results dealt with KK and lower...
I'm attempting to create a flashable zip for the modified version of the Lollipop AOSP MMS app (located here: https://www.androidfilehost.com/?fid=95832962473398790). I've done this in the past with Jellybean and KitKat, but this time the app, for whatever reason just simply won't flash. No errors come up in recovery, but upon reboot, the app won't be installed.
I've concluded that the reason the app won't flash is the way I have my flashable zip structured.... Or the Updater Script is written wrong.. I've had this problem in the past and rectified it by placing the corresponding META-INF file into the apk itself before placing it in a flashable zip, but this hasn't fixed the issue this time around. The apk in the link above installs itself into the following directory when installed using a file explorer:
Code:
/data/app/com.android.mms-1
If I place the modified apk into the same exact directory in a flashable zip (along with the META-INF folder). An example of what I've done can be downloaded Here, for those interested in dissecting the zip. The only difference is the apk loaded in that zip is the original apk that I know works, not my modified one, as it isn't complete yet.
For reference, I took a look at the CM12 Gallery flashable zip which installs itself in this directory:
Code:
/system/app/Gallery2
Please note that the apk decompiles and recompiles with no issue, so unless APKtool (newest version) screws something up without throwing an error, I doubt that's the issue.
Really need some guidance on this one. I'm excited to see what I can do with this MMS app as I have done in the past with the KK AOSP MMS application. Any help would be greatly appreciated.
Resolution:
I've constructed a perfectly functioning flashable zip (not the ones above) after a few more trial runs. The problem actually seems to be with Apktool not compiling or decompiling the apks correctly. Basically the problem is APKtool.
From CM Gapps page it says
It is possible to perform a "backup" of the Google Apps on your device and then "restore" them, but this does take additional steps which are not covered here.
Click to expand...
Click to collapse
I'd like to know how can I do this.
I've searched all across the forum but had no luck. It looks like some kind of trade secret.
I know that it's not just a matter of pulling the apk files. Because I can see that the zip has .apk, .jars, .so, configuration and certificate files.
I'm guessing this is done by extracting the files from a system.img.
But how is this done?
Is there some script available to build a gapps zip from a system.img file?
Another thing is that my OnePlus phone doesn't has an official LP update yet (although CM12 and their gapps work fine) so I suspect this would have to be done using the stock ROM of another device, maybe a Nexus. Is this correct?
Any help is appreciated.
Thanks