[Q] What is "Trustshare" - Bada Software and Hacking General

As everyone knows in bada 2 when we install an app, some folders appear that were not seen on bada 1.2
trustshare
share
share2
and i saw that they're always empty
and another funny thing
if an installation package includes these folder cannot be installed (application installations package is faulty)
i mean the application packages downloaded from servers does not include these folders and after installing the phone makes them automatically
SO what are they used for? any ideas?

Related

Kenteken Informatie application from Market Place

Hi,
Some time ago I installed "Kenteken Informatie" (from Rajen_Joris) through Market Place. I think I used the grzegorz10 rom at that time, but i'm not really sure.
After that I flashed to the maryone rom and tried again to install "Kenteken Informatie" from Market Place (from the My Applications list). But now the installer fails without a usefull message (only 'install failed').
And if I search on Market Place, I can't find the program anymore, although it's still in "My Applications" as purchased.
Does anybody have a cab installer (or just the nessecary files) for this program or perhaps a way to be able to install it again from Market Place?
Tia, Adriaan
Kenteken Informatie reinstall problem
For me exactly the same problem.
(the other apps from marketplace reinstall fine)
Can anybody help?
Any solution?
I have the same problem. The application shows up, but installation fails. I have a "Kenteken Informatie" and "Kenteken Informatie (1)" in my installed programs list. I can't remove either one, nor can i remove them from the list. They are not registered in the registry, nor can i find anything on the file system.
Anybody got any clue where the registration of these widgets is stored and how i can re-install it?

[APP] Softbankメール(mail) v1.5

Hi,
Since the release of the latest application (v1.6) a lot of users have been upset about the horrible downgrade in software.
It seems that Softbank has still not hired any native English speakers.....
Anyway I'm not here to rant I'll just post the files for v1.5 since a lot of people were asking where they could find a copy for themselves.
I pulled both of these files out of a backup I stored onto my SD card using MyBackupPro. Not sure what the zip file is for, but the APK is there. Maybe somebody could clear that up for me as well.
Zip file
APK
As far as I know there is two ways to get this installed (there may be many other ways).
1. adb push the apk or
2. download MyBackup and do a quick backup of some apps you have installed already. download both of these files and paste them into the directory where MyBackup stores the backups for apps. run MyBackup and choose to restore the Softbank Mail app.
cheers.
iDesire hTC said:
Hi,
Since the release of the latest application (v1.6) a lot of users have been upset about the horrible downgrade in software.
It seems that Softbank has still not hired any native English speakers.....
Anyway I'm not here to rant I'll just post the files for v1.5 since a lot of people were asking where they could find a copy for themselves.
I pulled both of these files out of a backup I stored onto my SD card using MyBackupPro. Not sure what the zip file is for, but the APK is there. Maybe somebody could clear that up for me as well.
Zip file
APK
As far as I know there is two ways to get this installed (there may be many other ways).
1. adb push the apk or
2. download MyBackup and do a quick backup of some apps you have installed already. download both of these files and paste them into the directory where MyBackup stores the backups for apps. run MyBackup and choose to restore the Softbank Mail app.
cheers.
Click to expand...
Click to collapse
Hi, after reading your post I discovered my version of SoftBank Mail is 1.0 but I've never received an update notification - probably because I'm not in Japan.
EDIT: Apparently it's because the version you've uploaded is designed for non-Japanese models and it's incompatible with mine.
I tried simply downloading the app and running a standard installation - it did install, but when I tried to launch it, I got a notification that it cannot be used on my device (Galapagos 005SH).
EDIT: The MyBackup method does not work because simply adding the files in the directory where the backed up APKs are doesn't automatically lead to the new APK(s) showing up in the list of available apps to restore - it's because the information is also written to a dedicated file (MBP extension I think it was). Perhaps that can be edited but...

Application installation locataion other than /system/app and SDCard??

I have a few Android devices, and I'm trying to install some favorite apps (that I can't seem to get via Amazon Market or Google Market,) Facebook being one of those.
I was able to adb pull Facebook.apk from another tablet I have, however, it's ver 1.5.2. Tablet says that it is running 1.7.2. That means that, not only did the old app stay on the tablet after the Market updated Facebook, BUT the new app is either named differently, or installed in a completely different location (not /system/app nor SDCard - I checked.)
I was working with Redbox as well, and I simply could NOT figure out where it was installed on 2 other Android devices. It is ALSO NOT installed to the SDCard.
I can see both processes running (NOT app_xx processes, btw.) The Redbox app was com.redbox.android.activity and Facebook was com.facebook.katana.
I am seeking enlightenment!
Side-bar: I am wondering if these are NDK applications. Do NDK applications need to be re-compliled for each individual platform? Are they installed differently than SDK applications? (i.e. in different locations in the filesystem)
Tuleen Donai said:
I have a few Android devices, and I'm trying to install some favorite apps (that I can't seem to get via Amazon Market or Google Market,) Facebook being one of those.
I was able to adb pull Facebook.apk from another tablet I have, however, it's ver 1.5.2. Tablet says that it is running 1.7.2. That means that, not only did the old app stay on the tablet after the Market updated Facebook, BUT the new app is either named differently, or installed in a completely different location (not /system/app nor SDCard - I checked.)
I was working with Redbox as well, and I simply could NOT figure out where it was installed on 2 other Android devices. It is ALSO NOT installed to the SDCard.
I can see both processes running (NOT app_xx processes, btw.) The Redbox app was com.redbox.android.activity and Facebook was com.facebook.katana.
I am seeking enlightenment!
Side-bar: I am wondering if these are NDK applications. Do NDK applications need to be re-compliled for each individual platform? Are they installed differently than SDK applications? (i.e. in different locations in the filesystem)
Click to expand...
Click to collapse
Use adb or Android Commander to find them here: /data/app. It is on the root file system. That's where most apps go that are installed from the Market and such.
you will preobably find the facebook app in /data/app you could also look for redbox in /data/app-private

[TRICK] How to stop Google Play Store self update - easy!

In /data/app folder make a new folder with name com.android.vending-1.apk
(to make the folder use a file manager app or the command "su" followed by "mkdir /data/app/com.android.vending-1.apk" with a Terminal Emulator app and Busybox installed.
NOTE: Making a new folder in /data partition require root permissions so the Andriod system must be rooted first)
That's it!
Hello everyone,
owners of smartphone with very limited internal storage, like Galaxy Y, will likely end up to be concerned of every single MB of free space lost; and the more the concern as the free space is getting closer to zero.
So there I am too.
I've put lot of effort to optimize the use of my Galaxy Y internal storage (/system, /data and /cache partitions all together) and I'm proud to have more than 50% of internal storage free and I like to have it that way for as long time as possibile.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One day, few weeks ago, I got very disappointed when I realized that I suddenly lost 15% (actually 15MB) of free space for some unknow reason
Later, it turned out that the reason was that the Google Play Store had been silently updated in the background without any notification.
Actually the footprint of newer version of Google Play Store is only 4MB bigger but as the previous version was installed in /system partition then the update process doesn't actually perform a replacement of the old installation with the new one, but it just add the newer app leaving the old installation untouched (that means leaving in place the old apk file along with its davilk-cache file) but marked as disabled.
Uninstalling the update (that in my opinion, for my needs and usage, was useless) was just a matter of tapping one button... but then another background update would have happen soon after.
So, as I didn't find any related option in Google Play Store settings, I immediately started a Google search to find a way to prevent/avoid/stop any further self update.
What I've found is only two solutions:
- one is about to freeze/disable the app that manage the update of Google Play Store; but this app doesn't longer exist or it's used as the latest Google Play Store app handle the self update by its own.
- the other one is to make a "dummy" file in /data/app that will make the installation of the update to fail as the required name for the new apk is already in use by the dummy file.
Unfortunately for those smartphones, like the Samsung Galaxy Y, where the /data partition is formatted RFS (Robust File System from Samsung; basically a FAT 16/32 based file system with a sort of journalling system on it) this solution doesn't work because RFS doesn't support the immutable file attribute and therefore the "chattr +i" command will fail.
If the dummy file isn't set as immutable then the installation task will be able to delete it and make the new apk in /data/app folder.
As an attempt to make the second solution, the "dummy file solution", to work with my Galaxy Y, I made the immutable dummy file in another partition then I created a link in /data/app pointing to that file.
But that didn't work... same as for the not immutable dummy file, the link can be deleted by the installation task that will then proceed till completion.
So what to try next?
From what I've read around seems that there's no solution; owners of Galaxy Y (that didn't reformat the /data partition with a Ext2/3/4) and other smartphone with RFS filesystem are simply out of luck.
True?
No! False!
I then remembered the days I used to make a autorun.inf folder in the root of my FAT32 formatted USB thumbdrive to prevent removable drive spreading viruses to make their own autorun.inf file in the thumbdrive.
So... why not to try the same trick to make the installation of the Google Play Store update to fail due to the impossibility to make it's own com.android.vending-1.apk file in /data/app folder?
Tried it...
and tested...
SUCCESS! :victory:
As a side note I want to point it out that this trick doesn't prevent the Google Play Store to try to self update and download the latest installer in the /cache folder.
Anyway I've observed that after the first failure of the update there are no further update attempts neither new downloads... at least for a while (maybe till next new version will be released?)
I don't know how long it takes, after the first update failure, for the downloaded apk in /cache folder to be automatically deleted... if ever; so I advise you to give a look at the /cache folder and manually delete it if still there.
That's all folks!
Bye!
Why don't you just integrate update to system with link2sd app
It will just replace the system app with the new update - you get the latest update and you not using any extra space with two versions of the app
Root required & restart after integrating (or it will force close)
That could be done, of course, but still there's a loss of 2MB of free space in /data and 2MB in /system due to the bigger footprint of the latest version.
Anyway is completely up to a personal choice if to upgrade or not.
The point here is that if someone doesn't want Google Play Store to self update now there's a known way to do so
Another way to do this is to did a modded play store apk here on XDA. A modded apk has been signed with a different key and therefore it cannot be updated by Google.
Uninstall any updates to the Play Store and put the modded apk in the system apps folder replacing the one on your phone, make a backup just in case. Reboot and you should have a play store that doesn't update.
Sent from my XT1060 using Tapatalk
good trick bro :highfive:
save quota internet
vin2m said:
good trick bro :highfive:
save quota internet
Click to expand...
Click to collapse
:highfive:
Thanks for the highfive bro
Anyway I'm afraid that, as I pointed out at the bottom of my 1st post, even if the trick makes the update to fail (same as per the immutable "dummy file" trick) but it doesn't prevent Google Play Store to download the newer version (9MB of data or more) for the upgrade attempt; so the Internet quota is still affected.
How to stop updating play store WITHOUT root .. I need to have 4.x.x. installed but it auto updates to 5.x.x how to stop it
(cannot root my phone)
thnx
I'm sorry but I'm afraid that without root privileges there's no way to avoid the self update of Google Play Store as this app is designed to self update and doesn't expose any option/settings that the user might use in order to disable that function.
So, as the self update can't be disabled by power of user account, it's required to operate at system level and therefore root privileges are needed.
halnovemila said:
I'm sorry but I'm afraid that without root privileges there's no way to avoid the self update of Google Play Store as this app is designed to self update and doesn't expose any option/settings that the user might use in order to disable that function.
So, as the self update can't be disabled by power of user account, it's required to operate at system level and therefore root privileges are needed.
Click to expand...
Click to collapse
Fuking google bas****ds are they ?
Wow, sneaky! This is obviously a far superior solution to my chattr method. Wish I'd thought of it!
this fix is no longer working it still forced the new version right after the commands
RemixedCat said:
this fix is no longer working it still forced the new version right after the commands
Click to expand...
Click to collapse
Hi RemixedCat,
I've tried just now to install the latest version of GPS (6.0.5) and the installation fails with the usual "Out of space" error (as shown on the video I published) due to the presence of the empty dummy folder.
If the folder is removed the installation completes without errors.
So the trick still works.
If it doesn't work for you maybe your Android configuration is different from mine, or you made a mistake on following the given instruction.
In order to figure out why in your case the update still take places and then try to give you some advices, please tell us:
- what's the Android version running in your phone
- if it's rooted
- what's the GPS version installed
- if the GPS currently installed is an update or not
-if you want to keep the current update or not
- if the GPS currently installed is installed as System app or User app
- what's the apk filename of the currently installed GPS.
You might want to install Link2SD to check the informations related to the currently installed GPS.
LOL
Very funny... all the people that post here or on my video comments saying that the trick doesn't work, once they get an answer from me with few advices on how to make it to work, they almost never care to reply again.
Did my advices worked out so that the initial statement of "it doesn't work" has proved wrong? or they didn't even care to read my reply or to follow my advices or to give positive feedback in case they finally have been able to have the trick to work as supposed?
Only God knows
I'm having trouble with this as well. I have replaced my preloaded GPlay store apk under /system/priv-app/Phonesky with a 8.10.30 apk - and created folders in /data/app/ named "com.android.vending" "com.android.vending-1" "com.android.vending-2" and the same with .apk on the end of the file name. I used terminal emulator and the su command, and even tried chattr +i - but still, google Play Store silently updates itself after a while and I get a new "com.android.vending-3" folder with the new apk in it. I'm at my wits end at this point. I don't want any newer versions of the store because they cause horrible battery drain on my M7, whereas 8.10.30 gives me no trouble. But without the folder trick working, my only hope seems to be to use LuckyPatcher to try and disable autoupdating that way.
And I honestly am yet to see a download source for LuckyPatcher that looks the least bit trustworthy.
Aaren11 said:
I don't want any newer versions of the store because they cause horrible battery drain on my M7, whereas 8.10.30 gives me no trouble
Click to expand...
Click to collapse
Hi Aaren11
I don't know a single thing about M7, except that it's not a Galaxy Y phone and that for sure, according to what you said, the Android version running on your phone is different from the stock Galaxy Y Android version which is Gingerbread 2.3.1.
In Android 2.3.1 user apps apk file are stored in /data/app folder while in your case, according to your post, the app apk is stored in a subfolder of that path, so instead of /data/app/com.android.vending-1.apk you have /data/app/com.android.vending-1/<something_here>.apk
This changes the scenario quite much.
I did a bit of search on Google to figure out what's your Android version and what's the default apps apk store folder without having to ask to you and waiting for your reply.
What I found out is that M7 is an HTC made Android phone, and is running Android KitKat 4.4 or above.
According to what i've found in Android 4.4 the apps apk file path should be like this:
/data/app/com.android.vending-1/base.apk
where the apk file name is not <app_name>.apk but just base.apk.
Is that correct Aaren11?
Is the file name of the apk you found in /data/app/com.android.vending-3 folder, base.apk?
So, let's try to adjust the trick to match your system.
- First of all switch off your phone Wifi and uninstall the GPS update.
- Clean the /data/app folder from all the com.android.vending???? folders you previously made.
- Make this new empty foders /data/app/com.android.vending/base.apk and /data/app/com.android.vending-1/base.apk
- To try if the trick works, instead of waiting for the next auto update that you don't know when exactly is going to happen, go download the GPS apk, move it to your phone via bluetooth, or USB or SDcard and install it.
Btw my Google search didn't result in any GPS version above 6.0.5 which seems to me to be the latest so I really wonder how is possible your GPS version is 8.10.30 unless that's not the GPS version but another related number you read somewhere else.
Anyway you can download the latest GPS version APK from here http://www.androidapksfree.com/apk/google-play-store-apk-latest-version-download/
- Post here the outcome of the attempt.
If the trick works the apk installation should fail with a "out of space" error message.
Good luck!
Thanks for the reply halove,
Honestly I suspected that simply altering the tweak to fit the different file structure might work, but at the same time because every single post on this matter I've seen so far referenced the same set of folders with the .apk extension - I also was under the impression that their precise location was mandatory to the functioning of the fix. I'll try fitting with my current file structure and seeing if I have any success.
Just to answer some of your queries. The M7 runs up to Android 5.0.2, at least that's as far as HTC has deined to bless us with OTA's, anything beyond that requires a custom ROM.
And my google play services is indeeed 8.3.00, I was confusing it and my Play Store version of 5.10.30. Last I checked Play services only goes up to 8.4.89.
Yeah no luck there I'm afraid.
Doesn't matter how many 'com.android.vending' or 'com.google.android.gms' directories with 'base.apk's I make - there is always a new one created, and the update is installed. I went all the way up to 'com.android.vending-5' and it still persists creating a sixth directory and auto updating. Again, I'd have no problem with this, were it not for the fact that I get rediculously high cpu usage on anything above 5.10.30 and 8.1.14 - nevermind the inability to opt out of this update, or the rumours that Google keeps pushing new hidden features that I don't want collecting my personal information.
I've tried even intergrating the 5.10.30 / 8.1.14 apk's into /system/priv-app/ but neither copying the files directly out of /data/app/ and renaming them appropriatley, or using TiBu's 'intergrate to ROM' option seems to work.
I really am at my wits end here.
Hi Aaren11,
well, honestly I wasn't much confident the trick could work in your case (and in any Android 4.4 or above) because the failure would happen if in the folder the package installer is going to save the app apk file, there's already "something" (either a file or a folder) that already uses the same filename of the apk that has to be saved.
But given that the package installer makes a new empty folder where to store the apk, then there inside won't be anything that will interfere with the installer.
In earlier Android versions seems that the package installer doesn't recognize the existence of the dummy folder because, in order to chose the apk file name, the installer check only the existing FILES and there names, so it skip the folders... but when it's time to "write" the file, the presence of the folder with same name will make the installation to fail.
But in Android 4.4 for sure the package installer will check the folders name first, in order to chose the name of the folder that it will make to store the apk file inside.
So the dummy folder will be recognized and "skipped" by making a new empty folder with a different name.
So there's one last hope.
If in pre 4.4 Android the trick works because the installer check for existing files but not for existing folders, maybe in 4.4 the trick could work if the installer check ONLY for existing folders and NOT for existing files.
So here's the plan
Delete all the dummy folders you made.
In /data/app make a dummy file (a empty text file) and give it the name of the folder the installer will likely use (com.android.vending, com.android.vending-1).
If the installer won't recognize it, then likely it will fail when it will attempt to make the folder.
If it recognize it and will delete it first, then you have to make it undeletable by power of the "immutable" flag that you can set on the file using the chattr +i command; given that the /data partition is formatted with an Ext filesystem.
Once again... good luck!
halnovemila said:
Hi Aaren11,
Delete all the dummy folders you made.
In /data/app make a dummy file (a empty text file) and give it the name of the folder the installer will likely use (com.android.vending, com.android.vending-1).
If the installer won't recognize it, then likely it will fail when it will attempt to make the folder.
If it recognize it and will delete it first, then you have to make it undeletable by power of the "immutable" flag that you can set on the file using the chattr +i command; given that the /data partition is formatted with an Ext filesystem.
Once again... good luck!
Click to expand...
Click to collapse
Sadly, still no dice.
Even just using the installer apk for a more up to date version of Play Store, it simply creates a new folder, numerated after the files I've made. I created:
com.android.vending
com.android.vending-1
com.android.vending-2
As blank files without an extension. And the installer simply creates a 'com.android.vending-3' folder and installs there.
I'm going to try again with dummy base.apk files in the appropriate folders - but I doubt it'll work. The installer clearly seems capable of distinguishing dummy folders and files, and simply creating a new directory every time.
Edit: No luck with that route either. The installer still simply creates a new, sequential directory and installs to that. At this stage it looks like the only way to get out of either app auto updating silently would be to block that process from starting entirley, because simply trying to trick it with misleading directories clearly isn't going to work. I think I'm going to have to give lucky patcher another go. Thanks google -_ -
Aaren11 said:
The installer clearly seems capable of distinguishing dummy folders and files, and simply creating a new directory every time.
Click to expand...
Click to collapse
Nah, I don't think the package installer cares about the files and folders it finds in /data/app, either real or dummy... what the installer does is just to check the existing filenames so to make a proper new one.
And the trick works only if the package installer can't "see" the dummy folder/file before its attempt to make the new folder/file.
So, seems that the package installer of Android 4.4 (and above) is a bit smarter than the one that comes with earlier versions.
I was wondering if there's a way to "hide" the dummy folder/file to the package installer so it will end up to make a new folder that will actually match the dummy filename incurring in a system error, and then the failure.
Unfortunately there's no such a "hidden" attribute to files/folders in Android OS.
Removing all the read,write,execute permissions on a file/folder doesn't prevent to list those file/folders along the rest of the directory content.
At this point I only wonder if the package installer might fail because the new folder name it has to make has a "split" number (-1,-2...) that exceed an internal limit.
So, let's say that package installer can handle names till two digits split (-99), what will happen if there's a dummy folder with name com.android.vending-99?
Will the installation fail? or the installer will go further and will make a com.android.vending-100 folder?
How about com.android.vending-999?
Can you try this?
Make dummy folders with name com.android.vending-9, com.android.vending-99,com.android.vending-999,com.android.vending-9999,com.android.vending-99999,com.android.vending-999999 and see what will happen once again

[Help] Installing "Metro" Apps on Windows RT 8.1

Hi, so I have a Surface RT, I was able, after a lot of effort to jailbreak it and enter Test Mode so any desktops apps that are meant for arm are working fine.
The problem is that now my Windows Store went bananas, I tried fixing it with some tutorials I found online, but nothing I can't revive it. Only option I would have would mean I recover the full tablet, install all updates only to later have to uninstall half of them and go trough the pain of installing the jailbreak again. Winch seems alot to get a app to work.
So I tried appx files, I tried installing using the powershell command as seen on some tutorial, winch gives me a bunch of errors, most of them are for libraries that are missing winch I do understand some of them just won't work for rt, others because the "app model" is set to 0 where it should be 1, I tried changing it to 1 but another error pops up saying the recourses.pri is missing or faulty or something on those terms. Tried with other apps but all just eventually ended in the same resources.pri error. Or that the os version it was requesting was higher. Since the appx were from nifty online sources I figured they would not be that compatible.
Later I tried Windows Apps Boss, this time i went to the official windows store (using IE) and downloaded the offficial files for the apps that I knew where compatible with ARM and this device. Anyone wondering I used this https://store.rg-adguard.net/ you just need to copy the URL from the windows store and it gives you the files.
First I tried downloading only the appx files and ran them on windows app boss, install, enable sideload, add package, the same recource.pri error appear, I tought maybe I need all the other files that were on the page meant for arm so I tried adding them as dependencies in windows app boss, added libraries to dependencies, and the other file that was a .blockmap I added to provisioned custom data, still nothing but closer, this time it only told the that the appxmanifest.xml was not on the package root whatever that mean, although I went to the windowsapps folder and the folder for the game in question and the file were there, but I noticed it was in the same path but in a different folder, with this I mean that I add 2 separate programs folders with 2 separate windowsapps folders, ok maybe windows apps boss created this one I thought, so I just moved them to the official folder and tried again, still nothing. Can it be because the original windowsapps folder is hidden? (just thought of this)
At this point I just want to flinch this thing at a wall or into a volcano, because every problem I fix just leads to another one, but since I got it for 50 bucks (I knew what I was getting into), and since now use it as my main pc since I don't have anything else or will have in a later future (its not that bad I just use mainly to watch movies, series now that I have the torrents desktop app, its relatively fast and works really well for basic stuff apart from the fact that Microsoft completely ruin the devices potential),I would like to at least be able to install metro apps or in this case games.
Can please someone help me out in figuring this, or guiding me another way to install them since every information in the internet is scattered and not always compatible with this device?

Categories

Resources