Hi all,
I am part of an IT Client team and we are trying to prep for the deployment of the GS4. The S3 is our current standard and was received pretty well, but some of the features are overwhelming to our sales force. Is there any way that we can disable some of these features perhaps even automatically via ADB and a USB cable?
Also, we are wanting to have our company app preinstalled. Currently it resides in the marketplace but apparently some of our sales force don't understand the Play Store and that they actually have to go find the app and install it. Is there a way to automatically sideload our app? We were also discussing a launcher like launcherpro with an xml file included that contains default locations for icons, data, etc.
Has anyone tried this before? Please advise with ideas/suggestions. We don't want to flash a ROM generated by our company because that would require too much overhead on our part to manage because thousands of phones need to me maintained. We also don't want to root the NatureUI/Touchwiz stock rom that comes with the S4.
metroidnemesis13 said:
Hi all,
I am part of an IT Client team and we are trying to prep for the deployment of the GS4. The S3 is our current standard and was received pretty well, but some of the features are overwhelming to our sales force. Is there any way that we can disable some of these features perhaps even automatically via ADB and a USB cable?
Also, we are wanting to have our company app preinstalled. Currently it resides in the marketplace but apparently some of our sales force don't understand the Play Store and that they actually have to go find the app and install it. Is there a way to automatically sideload our app? We were also discussing a launcher like launcherpro with an xml file included that contains default locations for icons, data, etc.
Has anyone tried this before? Please advise with ideas/suggestions. We don't want to flash a ROM generated by our company because that would require too much overhead on our part to manage because thousands of phones need to me maintained. We also don't want to root the NatureUI/Touchwiz stock rom that comes with the S4.
Click to expand...
Click to collapse
I'm not quite sure about disabling features on the stock ROM. I know there's an Easy mode that can be used for first time smartphone owners. As far as preloading your company app, you can write a script to do so. However, that requires you to manually enable developer mode and USB debugging on every single phone. I'm not sure how practical this is, considering you have so many phones. A better way might be to send a mass text message or email to each of the phones with the play store link to the app. Once again, considering the employees might be unfamiliar with the phone, a text would probably be the simple way to go. I would use side-loading as a way of installing your app in the event that someone had an issue with the text. I believe you'd run into the same issues with preinstalling LauncherPro and associated xml files. It doesn't seem there's a way you can properly deploy what you need to w/o going hands on on all units.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Depending on what functionality you would like to disable, you can go to the App Manager heading in the Settings menu, and disable system apps you don't use. In terms of disabling parts of functionality in certain system apps, that probably wouldn't be possible on stock unrooted devices.
metroidnemesis13 said:
apparently some of our sales force don't understand the Play Store
Click to expand...
Click to collapse
...
I'm not sure how to solve your problem. I was going to say once you are willing to ADB and USB debug you might as well cook up the ROM the way you want it and blast it on with Odin.
However, one thing to be concerned about is the OTA software updates that you probably want your users to be able to receive. If you mod the stock software (either with ADB or a modded ROM) in such a way to make the phone status 'Custom' your users won't be able to get updates and bug fixes from Samsung.
I would just try to hold their hand through getting the app installed (ie. email them a link to it when they get a phone so all they have to do is tap the link and hit install) and leave the rest of the phone alone.
It took us much longer than WP7 did, but the first Interop Unlock hack for WP8 is now available. It's currently limited to SAMSUNG phones, although we're trying to extend it to other phones, of course.
WARNING: Samsung is trying to break this hack! If you take the retail upgrade to GDR3 including the Samsung firmware update, it will not work!
A brief summary, for those unfamiliar with interop-lock: Windows Phone allows a number of high-privilege app capabilities, which can be used to make changes to the OS which are normally not possible for a third-party app. The limitation on whether we can use these capabilities or not is based on what "level" of developer unlock the phone has; standard "ISV" (Independent Software Vendor) dev unlock (max 10 apps or less) is what pretty much everybody gets; OEMs, however, get a special OEM Developer Unlock (300 apps or more) which gives them the ability to use much higher-privilege app capabilities than the standard ISV unlock permits. The name comes from ID_CAP_INTEROPSERVICES, the capability which was most important in WP7. In WP8, however, there are a great many interesting capabilities. Note that Interop-unlock by itself does not enable all of these. However, at least on Samsung phones, it is now possible to enable *all* the capabilities.
Guide for Samsung's ATIV phones:
The instructions are generally well-provided in @-W_O_L_F- 's app (direct link for updated XAP). You will also need the Diagnosis app, which is included (though hidden) on every Samsung WIndows phone.
The instructions are as follows:
Developer-unlock your phone. You will need the Windows Phone Developer Registration tool for this; it comes with the SDK.
Sideload the helper app using Application Deployment (included with SDK) or WPPT. It does not work to just copy the file to your phone, or similar.
Open the Phone dialer (the built-in one) and dial ##634# to install the Diagnosis app (if you hadn't already). You can exit it afterward.
Run the Interop Unlock Helper app and read the instructions, clicking Next until you get to Step 2.
Click the button to generate the toast notification for your phone's Diagnosis app, then tap on the toast to open the hidden registry editor.
Press-and-hold the Back button, and switch back to the helper app without closing the registry editor. Click Next to go to Step 3 in the helper app.
Copy the provided registry paths and values out of the helper app, use the Back-and-hold switcher to return to Diagnosis, paste the values into the registry editor, and write them.
Don't worry if the app says a write failed! Just hit Read afterward to verify the change.
Repeat the previous steps a few times, hitting Next after each set of instructions, until the Helper app says "Finish".
Once all the registry values are written, congratulations; you are interop-unlocked!
At this point, you probably want to run the EnableAllSideloading hack below.
If you want to enable sideloading even more high-privileged apps, you'll want the following:
Install the BootstrapSamsung app attached to this post. This requires having interop-unlock already, and will not work if you have Samsung's ships-with-GDR3 firmware update unless you unblock RPC.
Run the app once, and ensure it displays a success message. You may then exit and (optionally) remove the app.
Install the EnableAllSideloading app attached to this post. This requires the bootstrap step. However, it is not specific to Samsung (we just can't bootstrap anything else yet).
Run EnableAllSideloading once, and ensure it displays a success message. You may then exit and (optionally) remove the app.
At this point, you will be able to sideload any capability, even the ones used for built-in apps and services. However, there appear to still be restrictions, even with a capability such as ID_CAP_BUILTIN_TCB. Multiple XDA members, including @Heathcliff74 and myself, are working to overcome these restrictions.
It may be necessary to repeat these steps after a phone update.
Capabilities which will be enabled, without further modification, by using interop-unlock:
Note: This list is *just* the ones from Interop-unlock; it does not unclude the ones from EnableAllSideloading.
ID_CAP_CALLMESSAGING_FILTER
ID_CAP_CAMERA
ID_CAP_CELL_API_COMMON
ID_CAP_CELL_API_LOCATION
ID_CAP_CELL_API_OEM_PASSTHROUGH
ID_CAP_CELL_API_UICC
ID_CAP_CELL_API_UICC_LOWLEVEL
ID_CAP_CELL_WNF
ID_CAP_CSP_FOUNDATION
ID_CAP_CSP_MAIL
ID_CAP_CSP_OEM
ID_CAP_CSP_W4_APPLICATION
ID_CAP_CSP_WIFI_HOTSPOT
ID_CAP_DEVICE_MANAGEMENT
ID_CAP_DEVICE_MANAGEMENT_ADMIN
ID_CAP_DEVICE_MANAGEMENT_BOOTSTRAP
ID_CAP_DEVICE_MANAGEMENT_SECURITY_POLICIES
ID_CAP_DU_MIGRATOR_STATUS_OEM
ID_CAP_OEM_DEPLOYMENT
ID_CAP_INTERNET_EXPLORER_FAVORITES
ID_CAP_INTERNET_EXPLORER_SEARCH_PROVIDER_KEYS_HKCU
ID_CAP_INTEROPSERVICES
ID_CAP_KIDZONE_CUSTOMIZATION
ID_CAP_MAP_WRITE
ID_CAP_MEDIALIB_PHOTO_FULL
ID_CAP_NETWORKING_ADMIN
ID_CAP_OEM_ADC
ID_CAP_OEMPUBLICDIRECTORY
ID_CAP_PEOPLE_EXTENSION
ID_CAP_PEOPLE_EXTENSION_IM
ID_CAP_PEOPLE_EXTENSION_MOBILE
ID_CAP_PERSONAL_INFORMATION_IMPORT
ID_CAP_RUNTIME_CONFIG
ID_CAP_SMS_INTERCEPT_AGENT
ID_CAP_SMS_INTERCEPT_RECIPIENT
ID_CAP_SYNC_EXTENSION
ID_CAP_VOICEMAIL
ID_CAP_WALLET_SECUREELEMENT
ID_CAP_WIFI_BASIC
One of the goals of this thread will be to explore what we can do with interop-unlock, and look for ways to achieve full permissions. I think I've found one, but it requires the ability to write registry multi-string values. Basically, if we could add a "superuser" privilege, or enable the use of ID_CAP_BUILTIN_TCB, which already has it, this would allow the creation of "root" apps.
Aside from myself, credit for this hack goes to @cpuguy for the Native Toast Launcher tool which permits accessing otherwise-unreachable code, and @-W_O_L_F- for helping put the pieces together. I'm not actually certain which one of us achieved the interop-unlock first; we were both working on it. @Heathcliff74 continues to be a help on the quest for full-unlock.
The source code for the apps below is posted at http://forum.xda-developers.com/showpost.php?p=45606584&postcount=88
Questions and Answers
Can I install WP7 interop apps using this?
They will install, but there's no point. They almost certainly won't actually work. Interop-unlock enables access to parts of the OS which third-party developers were not intended to touch; consequently, there's no backward compatibility. Even the methods used for native code on WP7 (which is different from, but nearly essential to make use of, interop-unlock) won't work on WP8. However, it should be possible to port many of those applications to WP8.
Will this work on Lumia phones / How can I get this on my Lumia / Are you working on this for Lumia phones / What about HTC, or some other OEM?
The current hack relies on a Samsung-specific component. Adding support for other phones will require new hacks. We are looking into it, rest assured; at this time, however, there is no way to gain interop-unlock on any WP8 device other than a Samsung one.
EDIT: It looks like there should soon be a Huawei W1 custom ROM with interop-unlock included. I don't deal with custom ROMs, but you may be able to use homebrew apps on that phone too.
EDIT: Lumia phones *can* be interop-unlocked via JTAG. However, this requires some extra hardware and some phone disassembly. Not an online hack, and not for the faint of heart.
But what if we installed the Diagnosis app on a Lumia phone (using Fiddler proxy or similar) and then followed this guide?
I repeat, Samsung-specific component. Nokia doesn't put the required services/drivers for Samsung's Diagnosis app into their Lumia firmware, so the app would not work!
Can I upgrade my phone to GDR3 if I have this?
Yes. However, be aware: if you install Samsung's updates that come with the retail GDR3 update, it will break your ability to re-unlock, or to use some homebrew apps! (Developer preview updates are fine, as those are purely Microsoft code and don't mess with the Samsung components.)
EDIT: There's a way to unlock the Samsung services for full access again on GDR3. You still need to interop-unlock beforehand, though.
Can I re-lock my phone if I want to?
Yes, easily. The simplest method is to use the Windows Phone Developer Registration tool (the one that comes with the SDK) to de-register the phone (you can then re-register it if you want to get your normal dev-unlock back). This doesn't remove any changes that were made using the interop-unlock, though (for example, it won't undo the EnableAllSideloading hack, not will it set back the Full FS Access hack). Apps that require interop-unlock will still be installed, but may no longer run. To manually remove interop-unlock, you can reset all the registry values that were changed by the interop-unlock hack to their original values, and remove all the apps. There still may be a great many other changes that also need reverting, though, if you want to get back to stock settings. See next question.
Can I get my phone completely back to stock settings without knowing every little thing I changed?
Yes, a hard (factory) reset will undo all changes made by interop-unlock, or any apps (including ones that require interop-unlock), and will remove all apps. If you need to send your phone in for warranty servicing and are worried that they won't take it because you interop-unlocked it, this approach will fix that (they would probably tell you to hard-reset anyhow, if it's conceivably a software problem).
Will the interop-unlock survive a hard reset?
Not using this method! Read the question above. This unlock is purely in software, not firmware; it is reset along with everything else.
Can I upgrade my phone to WP8.1 if I have this?
Tentatively, yes! We're still working on figuring out exactly what WP8.1 means for the homebrew scene. The short version is that most apps and some (but not all) of the hacks they contain seem to still work, though. However, see next question...
Can I interop-unlock my phone on WP8.1?
At this time, I don't believe this is possible (unless you can use a custom ROM). One step of the process appears to have been "fixed" and we will need to find a different way. -W_O_L_F- has indicated that he has one, possibly coming soon...
Apps which use Interop Unlock
SamWP8 Tools Currently includes a basic registry editor and some tweaking tools, including an accent color editor.
Native Access Webserver that requires full capability unlock; still read-only at this time.
PDF to Office enables browsing and moving files.
WPH Tweaks allows easy access to a number of registry tweaks.
AppData Manager allows you to back up the data of an app so you can re-install it (possibly after a hard reset) and not lose its state.
Storage Cleanup allows you to list and delete space-wasting files on your phone.
Reserved for... whatever else is needed.
Awesome!
I suggest first app to the list: my SamWP8 Tools
Upd. I'm little bit late XD
well i ve got an ascend w1 bootloader unlocked if i can help let me know
It's awesome to have my phone Interop Unlocked. I hope to see something to clear my "Other Storage" soon. Its full with faulty Windows Store installation files.. But I guess even with this it will be a lost cause.
Sent from my GT-I8750 using Tapatalk
although the Samsung registry editor will install it will not run on my phone and I believe I was able to interop unlock any idea why it wont run?
@GoodDayToDie your wor is awesome and you are the man
Good luck buddy
@FricoRico: Actually, I'm pretty sure we can clear out those files. I've got a ton of stuff on my plate at the moment, but even if none of the capabilities that work with interop-unlock will natively allow access to the relevant folder (and I wouldn't be surprised if one does; what is the folder in question?) there's a function in the Samsung driver interface to move files; we can move them to a location where we have write access, and then delete them.
@noelito: No idea. If it installs, that means you're unlocked. Make sure your phone didn't re-lock, I guess - try deploying the app again, for example - and make sure you're using the official deployment tool (some of the unofficial ones for WP7 - which may or may not work on WP8 - strip interop capabilities) and then try again. If it still doesn't work, please give a more detailed error report.
I am using the official deployment tool, and I believe the interop unlock does work because I was able to side load operamini, Samsung photo studio, supreme shortcuts and couldn't before BUT that was it they're side loaded but do not work at all ? well actually supreme shortcuts does run but when I try to use a custom shortcut such as brightness it will crash
Sent from my SGH-T899M using XDA Windows Phone 7 App
Aha, an item for the FAQ...
WP7 INTEROP APPS WILL NOT WORK! Interop-unlock lets you develop high-privilege apps, but it's very OS-specific. This is all unofficial stuff; there's no reason for Microsoft to have maintained backward compatibility, and indeed they did not. New apps will need to be developed specific to WP8. That's why there isn't already a bunch of listed apps...
ohhh ok so this interop unlock
is paving the way for future wp8 homebrew apps?
Exactly. Things which I have in mind, beyond the obvious improvements to registry and file system browsing, include options such as sounds customizations, media library access, changing certain "restricted" file/URI associations (alter the default browser?), *possibly* better task management (not sure we have the permissions for that), cleaning up wasted storage space, and as much more as we can manage. There's also a lot of potential for future research which this enables: interop-unlocking more devices, getting even higher permissions, possibly even custom ROMs or at least custom kernel drivers (which is much the same, since once you've got that you can change anything).
Can you write anywhere on the file system?
I can write some places, certainly. We'll see. I've got a couple of ideas for exploits involving writing to System32, but if there's anywhere I *can't* write, it's probably there.
Maybe "test mode" from lumias work like diagnosis app from samsung, really don't know about WP8 because i went from android, but on my motorola some options in fastboot like "Factory Mode" are apk's. Maybe this is a dumb thing (because they are two diferent systems ) :silly: .
Really thank you for your work, u 're awesome.
Sry for my english
GoodDayToDie said:
I can write some places, certainly. We'll see. I've got a couple of ideas for exploits involving writing to System32, but if there's anywhere I *can't* write, it's probably there.
Click to expand...
Click to collapse
Might be able to port @Myriachan 's exploit.
Boss442 said:
Maybe "test mode" from lumias work like diagnosis app from samsung, really don't know about WP8 because i went from android, but on my motorola some options in fastboot like "Factory Mode" are apk's. Maybe this is a dumb thing (because they are two diferent systems ) :silly: .
Really thank you for your work, u 're awesome.
Sry for my english
Click to expand...
Click to collapse
Feature-wise, Test mode is heavily locked on Lumias. One has to authorize to use its the most sweet features.
I'm just curious why every custom ROM comes with several apps hard-coded into them? I think Greenify is an awesome app and I bought it long before I Rooted my phone but I find it odd that in a lot of ROMs it comes pre-installed and you can't remove it. Not that you would want to, I'm just using that as an example. I'm more annoyed by having web browsers, file managers, music players, etc... forced on me. Is there a reason for this? It seems counter intuitive to the whole "take control of YOUR phone" philosophy behind custom ROMs.
Pulprat said:
It seems counter intuitive to the whole "take control of YOUR phone" philosophy behind custom ROMs.
Click to expand...
Click to collapse
You can build your own rom. This is what it means. You are not forced to use any of them.
You can also use TiBu to remove any app you don't like.
Because they want u to use their services.So their branded developers can make some cash or u use their rundown alternatives of? the same app.not all though ?.and carriers just draws data on contract (in case u didn't know)
Sent from my SM-N750 using XDA Premium 4 mobile app
Pulprat said:
I'm just curious why every custom ROM comes with several apps hard-coded into them? I think Greenify is an awesome app and I bought it long before I Rooted my phone but I find it odd that in a lot of ROMs it comes pre-installed and you can't remove it. Not that you would want to, I'm just using that as an example. I'm more annoyed by having web browsers, file managers, music players, etc... forced on me. Is there a reason for this? It seems counter intuitive to the whole "take control of YOUR phone" philosophy behind custom ROMs.
Click to expand...
Click to collapse
they arent hardcoded LOL, they are basic packages, because some people DONT RUN GAPPS, in fact its one of the points in using a custom rom. you can remove any time you want by using a root explorer and deleting their apks at /system/app and /system/priv-app (you can also disable them if you like)
and some apps even, if you dont like, are necessary to the phone start(i.e the launcher)
they cant know that you run gapps or you like X app, the team will build the rom per their standards, and to be functional in every case, using gapps or not, using x 3rd party or not
sure there are roms that dont come maybe with browser or music, but in these case, either the developers tell that they just use 3rd part ones or their gapps or recomendation already install a replacement for those
and no, custom roms arent for your total control, want total control? build your own,even google itself have a tutorial for that
The tablet is owned by someone else and they want to use one app called Landscape Magazine. On the Nexus 7 it runs fine but the battery just went on it and I'm having issues sourcing a replacement battery in the UK so that's where the HD8 comes in. I thought I could just put the Play Store on (plus framework etc) and it would be ok for them. It downloads the app fine, all others work fine but when I try to launch this one app it says it only works on Android tablets. I don't know why they'd code it that way but it is what it is.
Can anyone tell me if there's some way to get an app to run if it's throwing up an error like this?
Dyonas said:
The tablet is owned by someone else and they want to use one app called Landscape Magazine. On the Nexus 7 it runs fine but the battery just went on it and I'm having issues sourcing a replacement battery in the UK so that's where the HD8 comes in. I thought I could just put the Play Store on (plus framework etc) and it would be ok for them. It downloads the app fine, all others work fine but when I try to launch this one app it says it only works on Android tablets. I don't know why they'd code it that way but it is what it is.
Can anyone tell me if there's some way to get an app to run if it's throwing up an error like this?
Click to expand...
Click to collapse
Not easily. It would take experimentation to determine which device or rom characteristic(s) are trigging the behavior followed by additional fiddling to entice the app to run. Tethering that Nexus 7 to a slim power bank may be the best solution.
NEED ROOTED.
/system/build.prop
ro.product.brand = Amazon
ro.product.manufacturer = Amazon
Change to 'Google' or etc.
I think amazon is banned by the app.
The exact error message is "This app is only suitable for the Android platform."
Didn't see the pictures attached by @erono. If you root the tablet (or may be possible in temp root shell) and change the keys he mentioned, the app works after reboot.
Thanks all for replying, especially erono who seems to have found the solution. I'll see what I can do with it because my understanding is that there is still no major Android build for the 2018 HD8. I have a starting point if nothing else and that's more than I had before!
Dyonas said:
Thanks all for replying, especially erono who seems to have found the solution. I'll see what I can do with it because my understanding is that there is still no major Android build for the 2018 HD8. I have a starting point if nothing else and that's more than I had before!
Click to expand...
Click to collapse
You could always root it and just edit BuildProp (excellent guide by bibikalka) . As far as other ways, I'm not knowledgeable enough to know any alternatives. Maybe without root, you might be able to pull BuildProp from the elevated shell and push it back after changing the lines. I'm sure there would be some permissions changes required. Hopefully someone with a bit more experience pops in and can guide you if rooting isn't an option.
nujak said:
You could always root it and just edit BuildProp (excellent guide by bibikalka) . As far as other ways, I'm not knowledgeable enough to know any alternatives. Maybe without root, you might be able to pull BuildProp from the elevated shell and push it back after changing the lines. I'm sure there would be some permissions changes required. Hopefully someone with a bit more experience pops in and can guide you if rooting isn't an option.
Click to expand...
Click to collapse
No need to modify build.prop nor will any notable gains be realized by doing so. Simply follow the guides as written.
Davey126 said:
No need to modify build.prop nor will any notable gains be realized by doing so. Simply follow the guides as written.
Click to expand...
Click to collapse
Yeah, sorry I meant in specific context to having that particular app work on the HD 8 2018. Thanks to @erono (and testing it myself) Lanscape Magazine works with changing brand and manufacturer values in the BuildProp. I know it's possible and easy to do with root. I'm just not knowledgeable enough to know any other methods.
Method without root:
Use 'App Cloner (pro version)' create an cloned app.
You can modify MANUFACTURER and BRAND in 'Developer options -> Build props'.
App was modified, you can't update in Google Play Store or purchase any paid content.
This is not a good way.