Related
hi there
i need to replace a few of the original apk on my LG Optimus one P500, italy - does anybody have them so that i can do a clean installation? actually i copied those i needed from my friend's phone, (apk and odex) and tried to install them again but i get an installation error, i have root, etc etc. any clues why?
is there an official repository from LG with the original apps of this phone i can download from somewhere?
thanks
gabrio
if anybody needs it, i have found 2 original repositories for LG Optimus One.
gabriolinari said:
if anybody needs it, i have found 2 original repositories for LG Optimus One.
Click to expand...
Click to collapse
Post them :>
I couldn't reinstall anymore apks deleted from /system/app with amberhome. I had to recoock rom :/
Please, please post the LG Home apk, I foolishily deleted it from my Optimus One and I've heard that the phone may be bricked if I uninstall my third party launcher.
c3vzn said:
Please, please post the LG Home apk, I foolishily deleted it from my Optimus One and I've heard that the phone may be bricked if I uninstall by third party launcher.
Click to expand...
Click to collapse
Try this. Is apk + odex file from my O1 backup.
focos said:
Try this. Is apk + odex file from my O1 backup.
Click to expand...
Click to collapse
Thanks for uploading but I get the message that the application cannot be installed. Got any ideas? I can't seem to move the files into correct directory either.
Try to restore it, maybe work.
I used a website that allowed me to copy your files to the right directory (I can't post it here because I am a new user). However, I cannot actually install the apk which is a worry. But I think the phone wouldn't brick now if I chose to restore or whatever since the files are there. Don't want to take the risk just yet though.
My suggestion was to try restore the LgHome.apk with some app what support backup/restore, like SystemApp Remover. If doesn't work just use other home luncher, don't do a factory reset, because i get LgSetup wizzard error, black screen with no system launcher, and launcer pro was installed. So take care.
Try this one LGHome.apk. Hope is work.
looks like they sent u already. what happened to me was that i deleted it, then the phone would be lock at the android BOOT screen with the flashing logo BUT i managed to connect it to the pc and then launch "adb shell". via adb i pushed the Lg Home.apk to the system/app (i also had to change permissions of the phone file system via linux commands) then it worked, actually downloaded launcher pro right away and i love it, not using LG Home.apk anymore.
regarding uploading the file via adb:
1 adb shell
2 su
3 set permissions of the file system to be mounted r/w, SHOULD be this : mount -t yaffs2 -o rw,remount /dev/block/mtdblock6 /system
4 exit (one for exiting su)
5 exit (exiting)
then exit the shell from the phone.
> adb push LGHome.apk system/app // important, if you have a space in the filename you'll have a problem with adb and have the .apk file locally on the same folder where you have adb.exe otherwise you'll have a problem or you'll have to add adb to the path of your windows/linux path env variables, hence use adb push LG*Home.apk system/app - should work otherwise just rename it w/o space, works anyway.
then reboot it should work!
gabrio
more APKs from italian LG original phone:
http://www.webalice.it/gabrio.linari/LG/LGHome.apk
http://www.webalice.it/gabrio.linari/LG/LGHome.odex
~ gabrio
Yes I have file in the correct directory with correct permissions too, but can you actually install it to the phone? Or does it fail like it does for me?
Have you trying this one?? To me is installing fine, but get error when try to open it, maybe couse i have prime rom with apps2sd. Anyway i dont use LgHome.
That's not the real LG Home its one that's been hacked to use on devices that didn't have it preinstalled. The one you gave before was an original but it doesn't install which is really pissing me off.
c3vzn said:
Yes I have file in the correct directory with correct permissions too, but can you actually install it to the phone? Or does it fail like it does for me?
Click to expand...
Click to collapse
my phone couldn't start anymore (stuck @ android logo) and i copied this one from my friend's LG O1 (same as mine) bought in italy, same store i did, and it worked. actually the home didn't have all icons i had before so looked "weird" but at least i was able to start up the phone. then you can re-add to the home screen the apps and worked.
eventually i installed launcher PRO and im using that one now, much better.
gabrio
c3vzn said:
That's not the real LG Home its one that's been hacked to use on devices that didn't have it preinstalled. The one you gave before was an original but it doesn't install which is really pissing me off.
Click to expand...
Click to collapse
im not sure that all versions are identical, that is what helped me and managed to have the phone start up.
But did you install it or just place it in the directory?
Same LGHome problem here http://forum.xda-developers.com/showthread.php?t=886911. But if you can navigate in the phone and are not stuck in boot logo or black screen, why need LG launcher. Just don't do factory reset cause you will get a phone with no launcher.
Merry Christmas everyone!
c3vzn said:
But did you install it or just place it in the directory?
Click to expand...
Click to collapse
i just copied in system/app
This is for those of you who are currently running cyanogenMOD 6.1 or higher based builds who want to update your market to the latest version with the enhanced UI.
I'm not sure if this has been listed before, i did a search and found nothing, so here it is.
Steps;
1. Download the APK (located below)
2. Locate file using ROOT explorer and copy it
3. Browse to root/system/app & paste the file.
4. Do a full reboot (no hot reboot for users who have the option)
---
Using ADB
Steps;
1. Download the APK (located below)
2. Copy the file into your Android SDK tools folder
3. Push the file with the following commands;
- ADB remount
- ADB push vending.apk /system/app/vending.apk
4. Do a full reboot.
---
Using Terminal
Steps;
1. Download the APK (located below)
2. Copy the file into your SDcard ROOT FOLDER
3. move the file with the following commands;
- SU
- mv /sdcard/vending.apk /system/app/vending.apk
4. Do a full reboot.
Note; I'm running off of memory for the commands for ADB and Terminal, please feel free to correct me if any of these are off.
I still get FC. I've tried several different versions and nothing has worked. Build is HD2ONE 0.3.5.
Update: Just tried one last thing.. created a "root/system/app" directory in the HD2ONE folder and copied it there. Still didn't work so I cleared the market data and cache and tried again. It started and it actually loaded the apps and then immediately FC'd. Ugh so close.
Sent from my HTC HD2 using XDA App
birkholze said:
I still get FC. I've tried several different versions and nothing has worked. Build is HD2ONE 0.3.5.
Update: Just tried one last thing.. created a "root/system/app" directory in the HD2ONE folder and copied it there. Still didn't work so I cleared the market data and cache and tried again. It started and it actually loaded the apps and then immediately FC'd. Ugh so close.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
You jinxed me! LOL I am running JDMS rom and just did the vending file to /system/app folder, and it worked for over 1 hr ++ then after a reboot now it FC each time.
SO after looking into it for a while, the reason why it FC is because its signed different than the other Gapps IE, Google framework apk, and others. What we need is the same Gapps that are all signed the same. Once we have those, it should work 100%, i'm going to start testing it with latest updates from the gingerbread release (which i'm assuming has the same signatures)
Doesn't work for me on the latest HD2ONE build either. I know once they get it to work, the developer for hd2one will add it or offer it.
Hi all,
i often noticed people(including me) who tried to modificate their framework-res.apk resulting in boot loops(e.g. looping at white/green quietly brilliant screen).
So i tried to find out a fast way to get back to my(original) framework-res.apk without usage of recovery console each time my framwork-res.apk did not work as expected.
How it could help you:
It's a fast way to:
check out your moddings when doing numerous modifications in different versions of your modded framework-res.apk on your way to get it to work.
if you want to get back to your original/working framework-res.apk, even when it boot loops!
Click to expand...
Click to collapse
When you do numerous modifications on framework-res.apk and your modded apk leads to a boot loop you will be able to replace the current apk through e.g. the original apk.
At this boot point(boot loop screen) Android nearly finished booting and you have access on ADB commands.
What do you need to do this:
Download and extract/install QtADB from the link below:
QtADB
to replace the erroneous(current) framework-res.apk by the original or a fixed one.
Click to expand...
Click to collapse
There's no need to describe how to get a copy of your untouched framework-res.apk from device, since there are numerous tutorials around here.
Please check this tutorials to get a copy of your apk.
Please note before beating your device:
this probably will work with the most visual moddings of framework-res.apk - but i can't guarantee it works 100%.
It probably will not work when you play around with hardware or connections setting, other apk's or other stuff in other folders, so i am not responsible if it does not work.
always backup your current ROM/settings/whatever and save a copy of your untouched framework-res.apk
There is a little catch in it in comparsion with using recovery:
After you did like described, you have to set your background image and your (google) accounts anew.
But this is just a little work and it's not necessary until your framework-res.apk is doing the modded stuff correctly - or if you want to set the original framework-res.apk back.
Click to expand...
Click to collapse
So let's start to revive your original framework-res.apk.
(Of course you can use this method to push a modded to your device, to check out if your modding works):
Boot your device and let it load until you're at boot loop
(Download, extract,) run QtADB
Navigate in left window(Computer) to your copy of original framework-res.apk(e.g. in root directory of SD card, but i recommend a folder on your computer)
Navigate in right window(Phone) to device folder /system/framework/
Use in left window(Computer) context menu on your original framework-res.apk and select copy or drag&drop it to right window to copy the original framework-res.apk to your device
(just ignore that your device is doing strange stuff then, since it cannot access your framework-res.apk correctly at this point)
Then enter shell of QtADB(at left toolbar of QtADB) and enter the following commands to set the apk's prermissions:su
cd /system/framework/
chmod 777 framework-res.apk
Reboot your device( e.g. by using top menu->tools-ADB->reboot)
Set your background image and your (google/HtcSense) accounts anew.
Hope it helps you a bit on modding,
Greetings, brush2(Stephan)
error
hey man, Im getting an error on this. I changed my transitions effects ( folder anim on framework-res.apk) using the app metamorph. well, now every time I open an app the phone ( xt920) reboot. I ask my friend that have the same phone to send me his framework-res.apk. I try to replace using this method but dont got. I draged and droped the new apk and when I would type the shell's code the last code dont work because it said that the file is a "read-only system". What can I do to have my phone back? Please help.
Thanks.
I don't understand why this isn't a feature of stock Android. They did it with the notification bar, but why not the navigation bar? The main reason for doing this is to prevent the navigation bar from being burned into your screen. There are Xposed modules for Lollipop/Marshmallow that do this exact same thing, making this mod unnecessary on those versions of Android. Since there's no Xposed for Nougat (or if you don't like using Xposed on Lollipop/Marshmallow), doing this mod will make your navigation bar dynamically change color to match your notification bar.
***Please Note***
This isn't perfect. In applications like Google Messenger the navigation bar doesn't change to match the color of the contact you're texting, but it's better than nothing.
Prerequisites:
- Nexus 6 with USB debugging enabled in developer settings
- TWRP
- ADB fully setup and functional
- Text editor (gedit (Linux), NotePad++ (Windows), or whatever you like to use)
- Archive Manager (Linux) or 7Zip (Windows)
- Apktool 2.2.2 (link at the bottom of this post)
- Apktool Windows wrapper script (Windows only)
Step 1: Boot into TWRP
Step 2: Select mount, then select system
Step 3: Connect your Nexus 6 to your computer and fire up a terminal (Linux) or command prompt (Windows)
Step 4: Navigate to the folder containing ADB (platform-tools).
Step 5: Type "adb pull system/framework/framework-res.apk".
Step 6: Type "apktool if framework-res.apk" This installs the framework
Step 7: Type "apktool d framework-res.apk" This decompiles the apk
Step 8: Navigate to res, values, and open styles.xml with your text editor of choice
Step 9: Search for "navigationBar". There will be three instances of it. You only have to change the last two. Change "@colorBlack" to "?colorPrimaryDark" and save your changes
Step 10: Open colors.xml and search for "input_method_navigation_guard". Change "ff000000" to "00000000" and save the file. If you don't change this, the navigation bar will turn black when you open the keyboard
Step 11: Go back to your terminal window/command prompt and type "apktool b framework-res". This recompiles the apk
IF YOU SKIP THE FOLLOWING STEP YOU WILL END UP IN A BOOTLOOP!!!!!!!!!!
Step 12: Delete META-INF and AndroidManifest.xml from the modified framework-res.apk and copy over the ones from your original framework-res.apk
Step 13: Push the modified framework-res.apk to your device with ADB or by boot into recovery, copy it to your phone, and use the TWRP file manager to move it to /system/framework. If you do the TWRP method, be sure to set the permissions to 0644 or your phone will not boot.
Step 14: Boot up your Nexus 6 and test it out!
Link to Apktool
Nice tutorial. However, the reasons you're having issues "reusing" an existing modified copy of framework-res.apk are twofold.
1. You're re-signing a system app. Unless things have changed in the four years since I last modified framework-res.apk, system apps are not signed.
2. The apk can also be moved into /system/framework using a file explorer on the device. It simply cannot be done in one shot as the permissions need to be changed prior to the final move into /system/framework.
The framework is Android version dependent, so an Android 5.x framework will not work in Android 6.x or 7.x. However, replacing the framework on multiple copies of the same version of Android is certainly possible. I have to head off to work, but when I have a spare moment upon getting home I'll generate a "reusable" framework, and a flashable zip as well.
Strephon Alkhalikoi said:
Nice tutorial. However, the reasons you're having issues "reusing" an existing modified copy of framework-res.apk are twofold.
1. You're re-signing a system app. Unless things have changed in the four years since I last modified framework-res.apk, system apps are not signed.
2. The apk can also be moved into /system/framework using a file explorer on the device. It simply cannot be done in one shot as the permissions need to be changed prior to the final move into /system/framework.
The framework is Android version dependent, so an Android 5.x framework will not work in Android 6.x or 7.x. However, replacing the framework on multiple copies of the same version of Android is certainly possible. I have to head off to work, but when I have a spare moment upon getting home I'll generate a "reusable" framework, and a flashable zip as well.
Click to expand...
Click to collapse
1. The first time I did this I didn't sign the app and ended up in a bootloop. After researching the issue I came across a post that said signing the app was necessary. Signing it fixed my problem, so I've signed it ever since out of habit. Next time I do this I'll skip signing it and see what happens. If I don't get a bootloop I'll remove it from the guide. It's possible I had a permissions error or something.
2. While moving it with a file explorer is possible, I just prefer ADB, so that's why I used it in my guide.
I realize that they're version dependant. I wasn't trying to use a modified framework-res from Marshmallow on Nougat or anything like that. For example, when I tried reusing one from the November factory image on the December security update, or one from the November image on Pure Nexus, I get a bootloops, so that's why I assumed it necessary to create a new one each time. It's not like this mod is hard or takes a large amount of time, so why not redo it each time just for fun?
Face_Plant said:
It's not like this mod is hard or takes a large amount of time, so why not redo it each time just for fun?
Click to expand...
Click to collapse
Not everyone likes playing around with app mods. When I last did it, it was to enable the network location service on a Coby tablet running Android 4.0.3. That was NOT fun as it involved smali editing. At least this is only an XML edit.
Strephon Alkhalikoi said:
Not everyone likes playing around with app mods. When I last did it, it was to enable the network location service on a Coby tablet running Android 4.0.3. That was NOT fun as it involved smali editing. At least this is only an XML edit.
Click to expand...
Click to collapse
I didn't mean for all mods, just this one. Like you said, it's only simple changes to two XML files.
After getting some practice by doing this a couple of times it only takes a few minutes to complete, depending on the speed of your computer. It takes me about 30 minutes since my Ubuntu machine is an old early 2000's PC that takes about 10 minutes to decompile the app, 10 minutes to sign it, and 10 more to recompile it... I'll be able to knock 10 minutes of that time if what you're saying is correct and signing it is unnecessary.
I'll try it again after class today and remove the signing bit if all goes well [emoji106]
Great write-up, worked well OP!
You can after recompile of the framework-res folder, you can delete the AndroidManifest.xml in the new APK, and copy the AndroidManifest.xml and META-INF folder from the original framework-res.apk into the newly built APK...hopefully that makes sense.
No need to sign. That's what I did and it worked just fine, eliminates a step. I use 7zip to do all of that BTW.
RMarkwald said:
No need to sign. That's what I did and it worked just fine, eliminates a step. I use 7zip to do all of that BTW.
Click to expand...
Click to collapse
Good to hear. Those steps have been removed from the guide.
I wonder why signing it fixed my problem when I did this on Marshmallow earlier this year... I guess I screwed up something else and the second time around when I signed it I didn't screw up whatever I did wrong the first time.
Face_Plant said:
Good to hear. Those steps have been removed from the guide.
I wonder why signing it fixed my problem when I did this on Marshmallow earlier this year... I guess I screwed up something else and the second time around when I signed it I didn't screw up whatever I did wrong the first time.
Click to expand...
Click to collapse
Could depend on the app maybe? Not too sure there. I started wanting to learn modding apks (mainly making color changes, etc) by guides similar to this, the whole "I wonder if I can do that?" thing. Hopefully this will encourage those looking to try something like this that isn't too difficult to do to give it a shot and try it, just remember to have a backup of framework-res.apk handy, always can be adb pushed back via recovery if something goes south.
Thanks again for this OP, so far working great!
Awesome write up!
Not trying to hijack the thread, but for those not comfy making mods, there is "an app for that" Navbar Apps
Simple app that will dynamically change your nav bar color as well as other goodies.
recompiling it fails. i get this error on Ubuntu 16.10 I even tried using sudo
I: Using Apktool 2.2.0-dirty
Exception in thread "main" brut.androlib.AndrolibException: brut.directory.PathNotExist: apktool.yml
at brut.androlib.Androlib.readMetaFile(Androlib.java:258)
at brut.androlib.Androlib.build(Androlib.java:270)
at brut.androlib.Androlib.build(Androlib.java:263)
at brut.apktool.Main.cmdBuild(Main.java:224)
at brut.apktool.Main.main(Main.java:84)
Caused by: brut.directory.PathNotExist: apktool.yml
at brut.directory.AbstractDirectory.getFileInput(AbstractDirectory.java:105)
at brut.androlib.Androlib.readMetaFile(Androlib.java:254)
... 4 more
how do i deal with this?
i see the yml file right in the folder
kidhudi said:
recompiling it fails. i get this error on Ubuntu 16.10 I even tried using sudo
I: Using Apktool 2.2.0-dirty
Exception in thread "main" brut.androlib.AndrolibException: brut.directory.PathNotExist: apktool.yml
at brut.androlib.Androlib.readMetaFile(Androlib.java:258)
at brut.androlib.Androlib.build(Androlib.java:270)
at brut.androlib.Androlib.build(Androlib.java:263)
at brut.apktool.Main.cmdBuild(Main.java:224)
at brut.apktool.Main.main(Main.java:84)
Caused by: brut.directory.PathNotExist: apktool.yml
at brut.directory.AbstractDirectory.getFileInput(AbstractDirectory.java:105)
at brut.androlib.Androlib.readMetaFile(Androlib.java:254)
... 4 more
how do i deal with this?
i see the yml file right in the folder
Click to expand...
Click to collapse
Is Apktool installed correctly? Have you tried using Apktool 2.2.1? Maybe 2.2.0 isn't compatible for some reason? These are obviously just guesses. I'm no master at reading error logs...
ok i figured that out..
will this technique work on nitrogen version 7.1.1 because the nav bar doesnt change but when i pull the framework-res.apk the xml files are in fact altered.
---------- Post added at 09:13 PM ---------- Previous post was at 08:24 PM ----------
Face_Plant said:
Is Apktool installed correctly? Have you tried using Apktool 2.2.1? Maybe 2.2.0 isn't compatible for some reason? These are obviously just guesses. I'm no master at reading error logs...
Click to expand...
Click to collapse
no the command in the tutorial didnt work. because i was compiling a folder named framework-res and not an apk all i did was remove the .apk from the command supplied and it worked finally
also i dont know if it is an error but the push command has an lsystem for the location to be pushed. that wasnt working either.
thanks for the reply bro
Thanks face_plant. It was working the whole time. I thought I would get the pixel icons lol. My bad
Great tut thanks
kidhudi said:
Thanks face_plant. It was working the while time. I thought I would get the pixel icons lol. My bad
Great tut thanks
Click to expand...
Click to collapse
Pixel buttons are from the Substratum theme I'm using. You can get those too by being on a Nougat ROM that supports Substratum and using Pixel UI theme from the Play Store.
Just a heads up, if you're on 7.1.1 the theme won't work. It needs to be updated to support 7.1.1. Haven't tried it on 7.1, so it may or may not work.
Hi, I am trying to translate this base rom to English and trying to add Apply Car Play and Android Auto apps
Here's what I've done so far
1. I installed APK Tool
2. Downloaded the Stock Rom here https://drive.google.com/file/d/1G_7ZMTh7FN4XHTbManfsoM4DBDhgYBqY/view?usp=sharing
2. Decompile the KC2_SystemUI.apk
3. Edited the xml files and turned it to English
4. Added Apple Car Play and AA to Systems/App
5. Recompiled KC2_SystemUI.apk and Signed it and replaced original KC2_SystemUI.apk
6. Zipped the whole folder
7. Tried to sign it but I can't
any help here?
future thanks!
edit: here's the error message
Code:
**************
Signing File!
**************
Exception in thread "main" java.lang.NoClassDefFoundError: sun/misc/BASE64Encoder
at testsign.addDigestsToManifest(testsign.java:181)
at testsign.main(testsign.java:368)
Caused by: java.lang.ClassNotFoundException: sun.misc.BASE64Encoder
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:606)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:168)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
... 2 more
File signed successfully if no Errors above.
This is the app I used for signing it
Apps - [How-To] Signing ROMs
Hello everyone! This quick guide will teach you how to sign ROMs! WARNING : YOU WILL NEED AT LEAST A BASE KNOWLEDGE OF HOW TO USE COMMAND PROMPT. The knowledge of signing ROMs can prove useful to anyone! By knowing how to sign ROMs, you can modify your favorite ROM to add or delete APKs, so...
androidforums.com
Those keys and how they are used are way too old.
Use attached zip.
As you are on Windows, you need a little extra:
Code:
java -jar <path_to>\SignApkv2.jar -w -v <path_to>\testkey.x509.pem <path_to>\testkey.pk8 NAME_OF_ZIP.zip NAME_OF_NEW_SIGNED_ZIP.zip
rename the new signed zip to what the name needs to be.
But I think this will not work. You signed the SystemUI.apk using test keys, not the original keys. It might be that the SystemUI will not work at all because it is no longer "system signed" with the rest of your firmware.
Google on the use of
Code:
apktool -c b <unpacked apk>
and the difference between "just signing an apk" and "system signed"