Related
Does anyone know where i can get .apk apps from the computer and then install them onto my g1??
browse the forum, I know there is a website that lets you view the market and whatnot from your computer, I don't remember what its called but I know its there.
One site to check out what all is available (with ratings) is http://www.cyrket.com. You can't download from that site but at least it gives you a quick overview of what is available. There aren't any PC based options to download apps as of yet. (Unless you download an apk directly from a Developer's site) I did however hear that Google was planning on creating this functionality.
Regards
My signature
When apks are available
WHEN U CAN DOWNLOAD APK FILES U CAN TRANSFER THEM BY THE PROGRAM APPMANAGER. ONE WEBSITE THAT HAS APK FILES IS http://allshadow.com/forum/viewforum.php?f=11. CHECK IT OUT.
MUSER4LIFE said:
WHEN U CAN DOWNLOAD APK FILES U CAN TRANSFER THEM BY THE PROGRAM APPMANAGER. ONE WEBSITE THAT HAS APK FILES IS http://allshadow.com/forum/viewforum.php?f=11. CHECK IT OUT.
Click to expand...
Click to collapse
I DO HOPE THOSE FILES ON THERE ARE FREE AND NOT PIRATE / RIPPED VERSIONS AS THAT WOULD BE AGINST THE T's & C's OF THIS FORUM ...
Oooops .... I forgot the CAPS key on, obviously
I have LUMIA 620 dev unlocked via dream spark.
I downloaded XAP file from marketplace and it seams to be encrypted so they are not installing via DEV tools to my device.
But i searched around some apps which can be installed via DEV tool because the are modified and i want to know what are the changes that are need to be made in XAP files:good:
One thing i have noticed that those XAP files which can be installed on device via DEV can be opend via any archive software like winrar etc...
but those XAP that are not able to install on device via DEV cannot be open with any archive software.
prashantvrm said:
One thing i have noticed that those XAP files which can be installed on device via DEV can be opend via any archive software like winrar etc...
but those XAP that are not able to install on device via DEV cannot be open with any archive software.
Click to expand...
Click to collapse
The XAP files from the store are encrypted. Unless someone figures out a way to break the encryption, it cannot be done.
The XAP files you found are probably home-made apps, which can be sideloaded, because they're deployed by developer tools in an unencrypted format, or WP7 apps. The encryption is applied after you submit the XAP to the store.
There is no known workaround to sideload store XAPs without an SD card, at the moment.
TheGoldrocker said:
The XAP files from the store are encrypted. Unless someone figures out a way to break the encryption, it cannot be done.
The XAP files you found are probably home-made apps, which can be sideloaded, because they're deployed by developer tools in an unencrypted format, or WP7 apps. The encryption is applied after you submit the XAP to the store.
There is no known workaround to sideload store XAPs without an SD card, at the moment.
Click to expand...
Click to collapse
You are correct sir. It sucks that you can't even sideload Xaps that were downloaded manually due to the app being removed from the WP store on a non-SD device. I'm trying to see if I can make a workaround for this though. It would be nice if it worked. In terms of modifying the encrypted XAP, it'll be a while before one of us figures out how to decrypt, but at the same time that opens a whole new can of worms regarding to piracy.
I've looked at the encrypted XAPs a bit myself; they're basically a PlayReady wrapper around the ZIP archive (XAPs are just renamed ZIP files; I usually use 7-Zip to open them). Unfortunately, I don't think anybody has broken PlayReady yet. The various programs which claim to strip PlayReady (usually from music or video) all appear to work by running the file through the decoder built into various programs like Zune and Windows Media Player, and re-capturing the content that comes out of the decoder. That won't work for these files.
We might be able to do something similar if we can get the XAP decoder out of the phone ROM and use that, though it will be ARM code (I don't know if the x86 "emulator" image includes the DRM decoder) and therefore somewhat tricky to work with. It will also probably be obfuscated to deter reverse engineering, and may be difficult to make work independently. A kernel debugger on the phone may be needed to figure it out.
GoodDayToDie said:
I've looked at the encrypted XAPs a bit myself; they're basically a PlayReady wrapper around the ZIP archive (XAPs are just renamed ZIP files; I usually use 7-Zip to open them). Unfortunately, I don't think anybody has broken PlayReady yet. The various programs which claim to strip PlayReady (usually from music or video) all appear to work by running the file through the decoder built into various programs like Zune and Windows Media Player, and re-capturing the content that comes out of the decoder. That won't work for these files.
We might be able to do something similar if we can get the XAP decoder out of the phone ROM and use that, though it will be ARM code (I don't know if the x86 "emulator" image includes the DRM decoder) and therefore somewhat tricky to work with. It will also probably be obfuscated to deter reverse engineering, and may be difficult to make work independently. A kernel debugger on the phone may be needed to figure it out.
Click to expand...
Click to collapse
It would be nice to be able to put one on the emulator itself and see what was going on..
I offer up my Programs folder dumped from my Lumia 928 if it is any help. Devs do with it as you will At the very least under common files you will find the xaps installed on my device which do open with 7zip and include the license xml. As far as installing or side loading I did throw a few xaps at the various emulators with mixed results. Have at it guys!!!
http://sdrv.ms/13tlc0F
tonbonz said:
I offer up my Programs folder dumped from my Lumia 928 if it is any help. Devs do with it as you will At the very least under common files you will find the xaps installed on my device which do open with 7zip and include the license xml. As far as installing or side loading I did throw a few xaps at the various emulators with mixed results. Have at it guys!!!
http://sdrv.ms/13tlc0F
Click to expand...
Click to collapse
Xaps within the Programs directory from a ROM are unencrypted. These will help out a lot though!
Edit: Ohhh... Something interesting. CommonFiles\Xaps\SyncUi.xap is the Verizon Backup Assistant. This has some code to intercept SMS..
<Extensions>
<!-- Email & Accounts UX Integration -->
<Extension ExtensionName="Accounts_Extension_Standard" ConsumerID="{47998C28-3D90-11E1-8E07-8B2B4924019B}" TaskID="_default" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="SMS_INTERCEPT_STANDARD" ConsumerID="{55DB4873-5CDF-43B0-82B4-87EB13E9BF6B}" TaskID="SmsInterceptAppExtension" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="Service_Agent_Application" ConsumerID="{208558CC-4407-40F8-83AE-AE3D567126B3}" TaskID="BackgroundTask" />
</Extensions>
snickler said:
Xaps within the Programs directory from a ROM are unencrypted. These will help out a lot though!
Edit: Ohhh... Something interesting. CommonFiles\Xaps\SyncUi.xap is the Verizon Backup Assistant. This has some code to intercept SMS..
<Extensions>
<!-- Email & Accounts UX Integration -->
<Extension ExtensionName="Accounts_Extension_Standard" ConsumerID="{47998C28-3D90-11E1-8E07-8B2B4924019B}" TaskID="_default" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="SMS_INTERCEPT_STANDARD" ConsumerID="{55DB4873-5CDF-43B0-82B4-87EB13E9BF6B}" TaskID="SmsInterceptAppExtension" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="Service_Agent_Application" ConsumerID="{208558CC-4407-40F8-83AE-AE3D567126B3}" TaskID="BackgroundTask" />
</Extensions>
Click to expand...
Click to collapse
I don't like the sound of that The app is part of the settings on my device but when opened says there is a problem with my account and contact Verizon.
@tonbonz: Thanks for the dump! That could be really handy. I'll explore and see if I can find anything useful. Any direct applications will likely be Nokia-specific (which among other things means I can't test them) but lots of people have Nokia phones, and I may find something more generally useful too.
GoodDayToDie said:
@tonbonz: Thanks for the dump! That could be really handy. I'll explore and see if I can find anything useful. Any direct applications will likely be Nokia-specific (which among other things means I can't test them) but lots of people have Nokia phones, and I may find something more generally useful too.
Click to expand...
Click to collapse
I've enjoyed the benefits of all the devs and their hard work here at XDA since my HTC Trophy. Glad to give back in any way I can. If any other files or folders are needed I would be happy to oblige...and... I thank you sir!!!
Oh what the h*** Rest of the dump files currently uploading. Dump 1, three 7z files altogether, is the Programs folder from earlier post. Left out maps data from Data/shared data folder as it was huge and of no consequence as to what we are trying to accomplish. Also, to be clear, this is a dump from the Lumia 928 variant package not my actual device. Have fun!!!
http://sdrv.ms/13tlc0F
@djtonka Thank you for your tutorial on Nokia Care Suite on wimdowsmania.pl.
@AnDim Extra thanks for ImgMount Tool which was used to dump these files!!!
I'll let you know. Just for curiosity's sake, how are you extracting those files? Is it from a working device, or a ROM image?
EDIT: Just saw your message, thanks for the info!
Initial results are a mix of cautious hope, disappointment, and speculation.
1) The OEM apps use a ton of restricted capabilities (among the most tame, for example, is "ID_CAP_MEDIALIB_PHOTO_FULL", which gives direct access to the image folders and has visibility "public" according to the policy XML files from the Windows directory).
2) The OEM apps can be sideloaded, but you have to remove the PlayReady header and all the restricted capabilities. They aren't very exciting at that point; they may not even start up.
3) Speculation: The so-called "public" restricted capabilities require a (Store-?)signed app when used on a standard phone. It *may* be possible to sign the apps ourselves, install that cert on the phone, and then sideload them, but I doubt it.
4) More speculation: These new, high-privilege capabilities seem to have largely replaced ID_CAP_INTEROPSERVICES. Although the error when trying to sideload them on an interop-locked phone is different than it is for INTEROPSERVICES, it may be that an interop-unlock would allow sideloading apps that use those capabilities anyhow.
5) The OEM apps include WPInteropManifest.xml. It's exactly the same near-empty file as on WP7. However, they don't use COM but instead use the same native-CLR interop as the official SDK advocates (.winmd files that bridge managed code to C++ DLLs). Its presence does not impede sideloading.
6) Speculation: The WPInteropManifest may be needed for apps which intend to use the "raw" win32 API (as opposed to WinRT) in C++. This theory is supported by the presence of things like DLLs that read and write to the registry directly (not through a driver, which would need INTEROPSERVICES), using APIs such as RegCreateKeyW.
7) More speculation: Since we can extract the system libraries from our phones, it should be possible to use the DLL-to-LIB tools to create .LIB files (the official WP8 SDK is extremely short on these) that we can then use to link to the native Win32 API. Although we would still be (cripplingly) limited by the sandbox's low permissions, we could probably do things like write a basic registry browser.
8) The provxml commands to install apps are very simple, but I don't understand all the parameters. Nonetheless, whenever we have an app, its license, and a tool which can process AppInstall provxmls, we should be able to install those apps on any reasonably compatible phone.
9) Speculation: Due to the use of OS-based capabilities rather than OEM drivers, an app that is installed on any given phone *should* work on other OEMs' phones even if it accesses the registry or does similarly privileged operations.
10) There may yet be a vulnerable app which we could exploit (possibly by using a provxml-injection attack?) to write to the registry / move files / do similar stuff. However, it would probably have very limited permissions even so; unlike on WP7, most things which can write to *some* of the registry can't write to *most* of it.
I installed Simple Calendar yesterday from store. The app does not start and uninstalling it didnt remove everything and the app is still present in apps list. The store says I have it installed, so I cant instal it again. Storage sense does not list it, so Im SOT and have this ghost app in my apps lis now.
Can someone please go to the apps folder and take Simple Calendar installation files, so I can make a .xap and try to sideload it to my Ativ and that way fix it so I can uninstal it!
Please guys someone, its easy. Just enable full FS access from SamWP8Tool, navigate to: Data\programs\
Simple calendar folder there is: 977e5d54-01d8-4cf8-9891-da9579ce2692
Copy the instal folder to your pc and send a download link in PM to me. I can try to make a .xap from that and try to fix this without having to hardreset!
I have Simple Calendar folder present, but they are empty so I cant make a .xap from my device.
Please guys someone, it will only take few minutes. THANKS!
Heres a topic about the procedure http://forum.xda-developers.com/showthread.php?t=2462730
Please somebody... Seems that this is the only thing I can try besidess hard reset, if I want to get rid of this app from my programs list.
You do know you can't sideload a XAP with the same Product ID as a store app, right?
Also, you seem a little more desperate than the situation calls for.
GoodDayToDie said:
You do know you can't sideload a XAP with the same Product ID as a store app, right?
Also, you seem a little more desperate than the situation calls for.
Click to expand...
Click to collapse
No I didnt know that, I thought I could "overwrite" it... I think I did it with one app I made a backup from, did the xap and tested it by deploying it over the original installation from the store. If its not possible, maybe I remember it wrong and actually uninstalled it before deploying it.
And yes your maybe right, but I still would like to get rid of this stupid installation if possible, without a hard reset.
Hello,
there is a limitation in my region to download Android Auto. However I've tested it on old phone w/ CM + download from www . apkmirror . com and it works as charm.
Now the question is - I want to install it on my personal Nexus 6, where I'm very cautious what I put and what permissions I give.
Tried to search the net, looks like the site is trusted because of the comminity behind it but still what are my options to ensure myself APK is what Google provided?
When downloading it there is a fingerprint :
"Safe to Download
This APK is signed by Google Inc. and upgrades your existing app.
Fingerprint: 9C:A9:1F:9E:70:4D:63:0E:F6:7A:23:F5:2B:F1:57:7A:92:B9:CA:5D
The cryptographic signature guarantees that the file is safe to install and was not tampered with in any way."
But I'm not sure this fingerprint is Google's, nor that it's really signed with it.
Any help is welcome
If the signature is not same the app won't upgrade your old version and will install as a new app.
So if your updates successfully after installing the Apk then rest assured that the signature are same.
Sent from my Pixel XL using XDA Labs
immiMIK said:
If the signature is not same the app won't upgrade your old version and will install as a new app.
So if your updates successfully after installing the Apk then rest assured that the signature are same.
Click to expand...
Click to collapse
Actually, if the signatures don't match, the update won't install at all.
APKMirror is legit. If I recall, they're owned by the same people who own Android Police.
Thanks guys!
The issue is the following with the flow :
1. You can't find it in Play Store when the APK is not installed (Android Auto)
2. I've tried to install one version below lastest from apk mirror and then if I search for Android Auto in Play Store I can see "not supported in your region/country". Not showing that upgrade is available.
3. From p.1 and p.2 I can't reasure myself that APK is trusted
http://www.apkmirror.com/faq/
What measures do you take to make sure all uploaded APKs are real and created by the respective developers?
All APKMirror.com uploads are verified prior to publishing.
We make sure that the cryptographic signatures for new versions of all previously published apps match the original ones, which means we know if uploaded APKs were signed by the real devs or someone pretending to be them.
a. For new apps that have never been uploaded to APKMirror.com, we try to match the signatures to other existing apps by the same developer. If there’s a match, it means that the same key was used to sign a previously known legitimate app, therefore validating the new upload.
b. If we see no matches, we try to obtain and compare to a version of the same app from the Play Store or another verified location. If it’s a beta, we will try to get into it. If we can’t, we will attempt to contact the developer.
c. If we’re unable to verify the legitimacy of a new APK, we will simply not publish it.
Click to expand...
Click to collapse
apkmirror is trusted as other users have mentioned and they have a good track record. If you don't trust sideloading apks, unroot your phone, take off your custom ROM, flash a stock factory image and never mess with your device again.
Thanks all,
I will use them.
Cheers!
Strephon Alkhalikoi said:
Actually, if the signatures don't match, the update won't install at all.
APKMirror is legit. If I recall, they're owned by the same people who own Android Police.
Click to expand...
Click to collapse
What I meant that it won't install as update and install totally as new application.
OP you can trust apkmirror. Yes it's owned by Android Police.
immiMIK said:
What I meant that it won't install as update and install totally as new application.
Click to expand...
Click to collapse
If you're installing an app for the first time, it will install so long as the signature is valid. An update to that app will successfully install so long as the package name and signatures match. If the package names are different, e.g. com.android.dialer and com.google.android.dialer, the second app will install alongside the first. If the package names are the same but the signatures are different, e.g. ES File Explorer versus my modified version, the update will not install.
That's how I understand things. Has something changed that I don't know about? I'm not understanding your statement, as it contradicts what I know about Android packaging and signatures.
Strephon Alkhalikoi said:
If you're installing an app for the first time, it will install so long as the signature is valid. An update to that app will successfully install so long as the package name and signatures match. If the package names are different, e.g. com.android.dialer and com.google.android.dialer, the second app will install alongside the first. If the package names are the same but the signatures are different, e.g. ES File Explorer versus my modified version, the update will not install.
That's how I understand things. Has something changed that I don't know about? I'm not understanding your statement, as it contradicts what I know about Android packaging and signatures.
Click to expand...
Click to collapse
Nah what you said is correct. That's what i wanted to covey.
Sent from my Pixel XL using XDA Labs
APK of any Samsung system app refuses to install with the message "App not installed", with the exceptions of Samsung account, Samsung Galaxy Apps, Samsung Notes and Samsung Themes.
Here are some observations:
Create shortcut to .apk file and install immediately after reboot (Did not work)
Toggle "Secure Startup" in Settings and reboot (Did not work, it worked on the S8 and S7 devices)
Installing via ADB (Failed with the following error):
HTML:
Failed to install app.apk: Failure [INSTALL_FAILED_BY_BUILDTYPE_BY_SECURITY_POLICY]
Changing the version code of the .apk file with APK Editor (Did not work, causes "App not installed. The package conflicts with an existing package by the same name" error, which is different from the "App not installed" error initially)
For a screenshot of the "App not installed" error, please look at this post by @Teknick.
Searching this error on Google returns few useful results, so this definitely needs more attention. I highly suspect this is a Samsung security policy that is preventing the install. Is there any workaround? (except rooting, of course) I wouldn't be asking this if the Samsung apps could update themselves. Right now, every Samsung app insists that "The latest version is already installed" in the About section when there's a clearly a 2-month-later newer version available. And, no, these .apk files are NOT from the S8 Oreo beta.
Seriously, no one?
It's forbidden to bump your thread in less than 24 hours.
No one is sitting here just waiting to answer your questions.
And why open a new thread, there is already one, and you even posted in it.
Sent from my Galaxy Note8 using XDA Labs
If you are going to lecture people on the forum rules, I suggest you go back and read them yourself.
I'll make it easy and highlight a section for you real quick:
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.Also, if you can point out the 24 hour rule, I'd appreciate it, because the only part I found on bumping threads is this:
You can add updates to your thread (ie new features for an app., etc), BUT only update if you are posting relevant to the topic and NOT with the sole purpose of getting the thread to the top of the page (known as "bumping") otherwise it will be considered as spam.
Dejan Sathanas said:
It's forbidden to bump your thread in less than 24 hours.
No one is sitting here just waiting to answer your questions.
And why open a new thread, there is already one, and you even posted in it.
Sent from my Galaxy Note8 using XDA Labs
Click to expand...
Click to collapse
Nowhere in the forum rules does this appear. If you don't have anything that is helpful/adds to the discussion, why post this? I started this thread because I believe this issue needs more attention like I said before, as well as providing more information for others who might have this problem as well (and might be searching for answers here).
You can install some of them after you got new official update <security/policy update>,
The signature is different for different model, even same app like device maintenance, you cannot install the apk file from phone s8,s8+
For some independent app like samsung account, samsung themes, you can upgrade with installing the apk from the website you mentioned.
If you have 3rd party recovery installed, you can do your flashable file, then update via recovery, that's the way I'm doing usually.
hinnn said:
You can install some of them after you got new official update <security/policy update>,
The signature is different for different model, even same app like device maintenance, you cannot install the apk file from phone s8,s8+
For some independent app like samsung account, samsung themes, you can upgrade with installing the apk from the website you mentioned.
If you have 3rd party recovery installed, you can do your flashable file, then update via recovery, that's the way I'm doing usually.
Click to expand...
Click to collapse
Hi hinnn,
Thanks for the reply! I really appreciate your info. However, I have a few clarifications:
So Samsung indeed has a security check on the system APKs now to make sure it matches the device? Is the "About" section of the system apps correct after all? I'm on the latest AQI1 firmware with August 2017 security patch, and security policy has "already been updated to the latest version". Could you clarify which update you are referring to? Lastly, what is an "independent app" that you mentioned, and which apps are "independent"? Sorry if I ask too much, I came from installing these system APKs on S7 edge, I do not know about the latest mechanisms in S8 & Note 8.
Edit: I tried installing the latest Air Command APK, which also failed with the same error. But as far as I know, S8 has no S-Pen so no Air Command, correct? This should be for Note 8 yet it didn't install
100055 said:
Hi hinnn,
Thanks for the reply! I really appreciate your info. However, I have a few clarifications:
So Samsung indeed has a security check on the system APKs now to make sure it matches the device? Is the "About" section of the system apps correct after all? I'm on the latest AQI1 firmware with August 2017 security patch, and security policy has "already been updated to the latest version". Could you clarify which update you are referring to? Lastly, what is an "independent app" that you mentioned, and which apps are "independent"? Sorry if I ask too much, I came from installing these system APKs on S7 edge, I do not know about the latest mechanisms in S8 & Note 8.
Edit: I tried installing the latest Air Command APK, which also failed with the same error. But as far as I know, S8 has no S-Pen so no Air Command, correct? This should be for Note 8 yet it didn't install
Click to expand...
Click to collapse
Actually, SAMSUNG didn't push through the security policy in that way, usually, we need update to next version like AQI2 or AQJ1, then you can install some of them, otherwise you will get the message saying signature conflict
An existing package by the same name with a conflicting signature is already installed
For "independent app", like standalone app, samsung themes, galaxy apps, samsung account which isn't running with any particular framework , not too much.
P.S. I'm not a professional guy, probably my explainable doesn't make sense, or not correct, just for your information.
Cheers
I have the exact same problem and I didn't find any solution yet. And like you I come from the S7 Edge and I used to update my apps like this. So if someone has any suggestion I take it.
hinnn said:
Actually, SAMSUNG didn't push through the security policy in that way, usually, we need update to next version like AQI2 or AQJ1, then you can install some of them, otherwise you will get the message saying signature conflict
An existing package by the same name with a conflicting signature is already installed
For "independent app", like standalone app, samsung themes, galaxy apps, samsung account which isn't running with any particular framework , not too much.
P.S. I'm not a professional guy, probably my explainable doesn't make sense, or not correct, just for your information.
Cheers
Click to expand...
Click to collapse
Thanks for the clarifications! After some more observations, it seems that any APK released after 26 September 2017 will not install on Samsung devices running Nougat 7.1.1 (except the 4 mentioned in the first post). However, I do not get the "An existing package by the same name with a conflicting signature is already installed" error, I get "App not installed" error instead as shown by the screenshot.
However, changing the version code and re-signing the APK with APK Editor app will produce "An existing package by the same name with a conflicting signature is already installed" error that you mentioned when attempting to install (which is different from the original error)
As for the "framework" concept, could you elaborate a little further? The "Secure Startup" exploit works on all Samsung devices that were not originally on Nougat, but were later updated to Nougat 7.0. (It might work on the S8 and S8+ too, although I'm not sure about that).
@100055
No problem with this as this problem is solved temp only
for example
there are certain apps which are not stable and yes 1 or 2 are stable out of 98% unstable apps as i tried all apps and saw it was unstable and caused lots of problem
from adb
put the following command and install the apk
adb install -l -r C:\Users\anand\Desktop\soundalive.apk
[use red highlighted command line only. green highlighted line is for reference only]
the app will install but if you reboot your device the update of the apk will be lost and more over the previous app update officially done by Samsung will be wiped you have to reinstall the update from the galaxy app store again
if you dont reboot then its fine being using the app of updated one for example i needed only soundalive.apk till today.. so i update it and wont reboot my device so i enjoy the updated sound quality of it
Amit.A said:
@100055
No problem with this as this problem is solved temp only
for example
there are certain apps which are not stable and yes 1 or 2 are stable out of 98% unstable apps as i tried all apps and saw it was unstable and caused lots of problem
from adb
put the following command and install the apk
adb install -l -r C:\Users\anand\Desktop\soundalive.apk
[use red highlighted command line only. green highlighted line is for reference only]
the app will install but if you reboot your device the update of the apk will be lost and more over the previous app update officially done by Samsung will be wiped you have to reinstall the update from the galaxy app store again
if you dont reboot then its fine being using the app of updated one for example i needed only soundalive.apk till today.. so i update it and wont reboot my device so i enjoy the updated sound quality of it
Click to expand...
Click to collapse
Thanks for the solution, it indeed works! But why doesn't the update stay through a reboot though? And why does adding the option -l work?
Thread closed.
Please continue the discussion >>> HERE <<<
Thanks,
Wood Man
Forum Moderator