To get missing ("incompatible") apps to show up in the Market you will need to edit your build.prop.
You will need root (unlock your bootloader at htcdev.com) and Root Explorer (can do it through adb but Root Explorer is easier).
Open Root Explorer and go to /system and find build.prop. Long press on it and choose Open in Text Editor. Find these lines
ro.product.model=PH39100
ro.aa.modelid=PH3910000
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
and change them to
ro.product.model=HTC Pyramid
ro.aa.modelid=PG5811000
ro.product.brand=htc_wwe
ro.product.name=htc_pyramid
ro.product.device=pyramid
ro.product.board=pyramid
Press the Menu key, Save and Exit. Reboot.
I'm on RumRaider Beta 10 so I'll upload my build.prop if you want to just copy/paste it over your current one.
http://www.multiupload.com/YAMH40C8LW
EDIT:
Apparently, modifying this line
ro.product.device=holiday
Click to expand...
Click to collapse
Is causing issues with the camera making it take shots/recocrd in blue. So, I recommend still following the directions above, but only modify ro.product.device=holiday when you need to update/download apps and once done, change it back to ro.product.device=holiday to use the camera again.
Do not use these settings if you own a rogers/Bell HTC raider! Changing them will turn all of your X710a's pictures/video blue! I can not speak for other versions of the raider but the x710a is affected. I just figured this out after playing with all the settings in the camera app, and I even contemplated calling HTC!!! I had to revert the values back to original to get the camera to work normally.
Hmm, I noticed that issue to but just thought it was the Rom. That's interesting. Anyways, I fiddled around with the settings and discovered that it was this line that messing up the camera
ro.product.device=pyramid
So I'd recommend the switching this back to 'holiday' and when you need/want to download (or update) an app, simply switch this back to 'pyramid' and when your done restore it back to holiday.
What are the apps that we are expected to gain? Can you give us an idea what we are missing out on?
You can't know your limits until you exceed them.
The apps I gained were GTA3, Order and Chaos Online, Snapdragon GameCommand, and Desert Winds.
has anyone tried playing order and chaos after changing the file name back to correct the camera issue? I have read elsewhere that the game will give you issues on rooted devices
Spartoi said:
To get missing ("incompatible") apps to show up in the Market you will need to edit your build.prop.
You will need root (unlock your bootloader at htcdev.com) and Root Explorer (can do it through adb but Root Explorer is easier).
Open Root Explorer and go to /system and find build.prop. Long press on it and choose Open in Text Editor. Find these lines
ro.product.model=PH39100
ro.aa.modelid=PH3910000
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
and change them to
ro.product.model=HTC Pyramid
ro.aa.modelid=PG5811000
ro.product.brand=htc_wwe
ro.product.name=htc_pyramid
ro.product.device=pyramid
ro.product.board=pyramid
Press the Menu key, Save and Exit. Reboot.
I'm on RumRaider Beta 10 so I'll upload my build.prop if you want to just copy/paste it over your current one.
http://www.multiupload.com/YAMH40C8LW
EDIT:
Apparently, modifying this line
Is causing issues with the camera making it take shots/recocrd in blue. So, I recommend still following the directions above, but only modify ro.product.device=holiday when you need to update/download apps and once done, change it back to ro.product.device=holiday to use the camera again.
Click to expand...
Click to collapse
This method doesn't seem to work anymore.. in the play store it will still list it as incompatible.. unless there is something else needed to be done?
Hi,
with all those Lumia posts I'm wondering if it is also possible to interop-unlock a Samsung Ativ S with the latest software (8.1 Update 1 or later) on it *without* a prior downgrade to 8.0 GDR2/GDR3. If it is possible please tell me how or where to find the answer (my search yielded no result so far).
With interop-unlock I mean accessing the 'full' file system and registry and having additional capabilities just like it was/is possible with 8.0 GDR2.
Thanks.
Unblock RPC (file called "Non-production errors.txt" in the Documents folder of the phone, if I recall correctly). There are now two options:
First option: use chamber hijacking.
* Move an app with ID_CAP_INTEROPSERVICES (I like to use HTC's silly "Converter" app; it should still be available on all devices, but other targets are more popular) to the SD card.
* Either sideload or unzip and copy the contents to the SD card an app that uses Samsung RPC to write to the registry. You may need to remove ID_CAP_INTEROPSERVICES from the app before sideloading.
* Use any of the several tools for app hijacking, or do it manually (remove the Hidden and System flags from D:\WPSystem, then rename D:\WPSystem\apps to something like D:\WPSystem\apps1, then delete the files from the install folder of the app that you're hijacking, then move or copy the files from the install folder of the app that uses RPC into the install folder of the app you're hijacking; don't forget to un-rename the apps folder afterward).
* Run the hijacked app; it should by the registry editor app you replaced it with instead, and you can now interop-unlock the phone.
Second option: Use @djamol's "Root Tool" app from the Store, or another app that can modify its own capabilities via SD card tricks.
* Install "Root Tool" from the store; it should show up in Search.
* Move it to the SD card if it wasn't installed there to start.
* Run the app, hit Help, and follow the instructions (several of them are similar to the manual instructions above, but at the end you have to move the app from SD back to Phone before the trick works).
Note that in either case, the EnableAllSideloading app won't work (technically BootstrapSamsung will, but you shouldn't use it since it assumes EnableAllSideloading will be used afterward). Microsoft basically removed the capability that EnableAllSideloading relies on.
Thanks for your reply! So basically the same way works with Ativ S that works with Lumia and you don't need the Samsung diagnosis tool anymore. You just need SamWP8 or a similar tool that uses Samsung RPC after unblocking RPC.
I'll give this a try on the next weekend(s). :good:
Yeah, basically just that. The diagnosis app no longer has the registry editor, and the steps needed to launch to a specific page in an app (such as the reg editor) are technically still possible but are identical to just installing an interop-based registry editor (via hacks), so do that instead.
GoodDayToDie said:
Yeah, basically just that. The diagnosis app no longer has the registry editor, and the steps needed to launch to a specific page in an app (such as the reg editor) are technically still possible but are identical to just installing an interop-based registry editor (via hacks), so do that instead.
Click to expand...
Click to collapse
But after is it possible to unlock all capabilities?
How to interop-unlock now?
Mattemoller90 said:
But after is it possible to unlock all capabilities?
Click to expand...
Click to collapse
I'm curious about that as well.
I tried the second option from (you) GoodDayToDie: It is not possible to use Samsungs Registry Editor component from Root Tool after following the instructions (moved app to SD, deleted the two files, moved stuff from HACK-subfolder to its parent, moved app to phone memory; file "Non-Production Errors.txt" exists in Phone\Documents -- BTW: Is the file name case-sensitive?). The general registry editor from Root Tool works, but with this one it is not possible to write several important keys (e. g. MaxUnsignedApps).
After this I tried the first option: I can successfully deploy CustomPFD (replacing Preview for Developers by hand or with CustomWPSystem). But what to do then?
I tried replacing Preview for Developers with SamWP8, but the app won't start then (getting "Loading ..." for about ten seconds then it closes); also tried commenting some capabilities of SamWP8 and repeating, but has no effect.
Deploying SamWP8 or IO Explorer using application deployment tool obviously fails because of missing interop capability.
This is a fresh and clean installation of WP 8.1 Update 2 now if it should matter.
Any further hints would be appreciated.
My Samsung died months ago (spontaneous hardware failure; I wasn't even hacking on it at the time) so I can't test Samsung-specific things anymore.
The steps as described (by both you and me* *should* work - I assume you rebooted the phone afterwards - so if it's not then I'm confused. The registry editor in Root Tool is mildly terrible and sometimes gives error messages when stuff actually works, but if it's really not working then I'm not sure what you do about that.
As for unlocking all capabilities, that's going to take a little work. The hack used by BootstrapSamsung unlocks one capability, and technically it could be applied to *all* the capabilities, but it changes the registry value type and loses a couple of NULL bytes at the end of the value every time you do it, which is potentially going to break things if you do it to all the capabilities / leave the capabilities in that state for long.
For what it's worth, if you're willing to hard-reset, the OemSettings.reg method mentioned in a few other threads should work too. It requires writing to a normally-unreachable part of the file system, but the Samsung RPCComponent class allows you to do this. I haven't tested it, though, and it does require a hard-reset.
Im interested in this too
If it does not work then what to do if im on 8.1 update already?
@up
AFAIK path is
Unblock RPC Functions proved easy. You just need to create an empty file:
Phone \ Data \ Users \ Public \ Documents \ Non-Production Errors.txt
Click to expand...
Click to collapse
Maybe that's why it didn't worked if you put it just in documents.
I just want to change black/white background-color and accent color in registry. That's all.
Regards
GoodDayToDie said:
My Samsung died months ago (spontaneous hardware failure; I wasn't even hacking on it at the time) so I can't test Samsung-specific things anymore.
Click to expand...
Click to collapse
Ouch, too bad. Would be really useful to have your helping hands on getting this done.
The steps as described (by both you and me* *should* work - I assume you rebooted the phone afterwards - so if it's not then I'm confused. The registry editor in Root Tool is mildly terrible and sometimes gives error messages when stuff actually works, but if it's really not working then I'm not sure what you do about that.
Click to expand...
Click to collapse
I did reboot.
Is there an app with a basic registry editor out there so I could at least change phone manufacturer like I could with Root Tool (Root Tool doesn't seem to be available in the store anymore)?
As for unlocking all capabilities, that's going to take a little work. The hack used by BootstrapSamsung unlocks one capability, and technically it could be applied to *all* the capabilities, but it changes the registry value type and loses a couple of NULL bytes at the end of the value every time you do it, which is potentially going to break things if you do it to all the capabilities / leave the capabilities in that state for long.
For what it's worth, if you're willing to hard-reset, the OemSettings.reg method mentioned in a few other threads should work too. It requires writing to a normally-unreachable part of the file system, but the Samsung RPCComponent class allows you to do this. I haven't tested it, though, and it does require a hard-reset.
Click to expand...
Click to collapse
I tried to use ROMRebuilder, but it just gave me "Failed " when tapping "Backup". But with full file system access I copied OEMSettings.reg zip-file out of the known C:\Windows subdir, extracted the .reg-file, appended all the unlock stuff, repacked and put it back to its original place overwriting the original file (with Root Tool, because in Windows Explorer I didn't have the right to write - Root Tool told me it was successful. I didn't double check ). But after resetting (About - Reset phone) no unlock or access to C:\ was there. Looks like the stock ROM. What went wrong..?
Edit: Used CustomPFD for registry access. Looking at "This PC\Samsung ATIV S\Phone\Windows\Packages\RegistryFiles\OEMSettings.reg" I can see that it is the original file, not my modified one. Is this file restored from somewhere upon reset or did my copy action fail?
Edit2: Tried using vcREG_1_2_BOOTSTRAP (replaced Extras & Info). It gives me an error about missing ID_CAP_INTEROPSERVICES, so it can't do anything.
And CustomPFD can't write MaxUnsignedApp. :-/
Not sure if ROMRebuilder is smart enough to use Samsung's RPC instead of Nokia's for moving the file into place, but regardless it requires interop itself (at least, I'm not sure how it could work otherwise). Root Tool definitely requires interop in order to overwrite Windows files, although it can do so. For the record, for stuff like just reading files or registry values, you can use the (normal-caps) version of my webserver; might be a bit easier.
vcREG should work, assuming it supports Samsung RPC - I think so, but I haven't checked - and you use the whole app hijacking thing correctly. Did you launch the hijacked app after the installation? Pretty sure Extras+Info has interop, so that *should* work.
EDIT: Assuming that the Samsung RPC service is working at all. I don't know of any easy way to test that short of just trying to do things with it, though. I don't think they "fixed" the RPC unblock, though...
GoodDayToDie said:
Not sure if ROMRebuilder is smart enough to use Samsung's RPC instead of Nokia's for moving the file into place, but regardless it requires interop itself (at least, I'm not sure how it could work otherwise). Root Tool definitely requires interop in order to overwrite Windows files, although it can do so. For the record, for stuff like just reading files or registry values, you can use the (normal-caps) version of my webserver; might be a bit easier.
Click to expand...
Click to collapse
Okay, so it probably didn't replace the file at all but only showed a success message. Grmbl. Which file manager would you recommend for moving the file to its place or in general?
vcREG should work, assuming it supports Samsung RPC - I think so, but I haven't checked - and you use the whole app hijacking thing correctly. Did you launch the hijacked app after the installation? Pretty sure Extras+Info has interop, so that *should* work.
Click to expand...
Click to collapse
Ohhh, you mean if I started the app that's about to be hijacked before actually hijacking it? No, I did not. (Not sure what Extras+Info would do on a Ativ S...)
But I do have to?
Edit: Removed Extras&Info (with dummy.xap), installed it again, started it (it actually works) and replaced it with vcREG_1_2_BOOTSTRAP.xap. Started vcREG, but it still gives me "error initializing. check if you have correct permissions (ID_CAP_INTEROPSERVICES). registry functions disabled".
I've also deployed CustomPFD and original preview for developers to sdcard. I have access to the registry but can't write values
Have you tried to hijack Extra+Info permissions with CustomPFD? It does not work with original PFD but it may work with Nokia one. I can't find Extra+Info xap to test, sorry.
Ok tried to deploy ROMRebuilder and hijack original PFD permissions. ROM Rebuilder just crashes on start (no message) WP 8.1 14157.
Installed ROMRebuilder with deleting Capabilities from xap and deployed it from deployment tool.
Manually removed PfD with SD hack and replaced it with ROMREbuilder.
It starts but when pushing "Backup" it says FAILED
Jesus im so tired with this phone...
ROM flasher does not work at 8.1 x64 even with test mode..
Ezio21 said:
Have you tried to hijack Extra+Info permissions with CustomPFD?
Click to expand...
Click to collapse
Yes I have. CustomPFD doesn't start in this case (it does when I'm replacing Preview for developers).
cerebos said:
Edit: Removed Extras&Info (with dummy.xap), installed it again, started it (it actually works) and replaced it with vcREG_1_2_BOOTSTRAP.xap. Started vcREG, but it still gives me "error initializing. check if you have correct permissions (ID_CAP_INTEROPSERVICES). registry functions disabled".
Click to expand...
Click to collapse
Your phone can't initialize Lumia RPC.
So what can we do?
What apps are there that use Samsung RPC to write to the registry? I know SamWP8 and IO Explorer. Any more?
@cerebos
Huh im sorry but it seems that only one way to get that Interop unlock is to flash GDR3
I flashed GDR3 but there is NO WAY to unlock your phone anymore. WP 8.0 developer registration is down. You can't install developer unlock helper and can't interop unlock your phone.
Also because of Samsung firmware update you can't install custom rom on wp8.0
How to interop unlock WP 8.0 without developer unlock? Any way? Or we're locked forever?
As far as I know you can still use beta apps on windows store. Is there anyone with personal developer account reading and could upload Interop_Unlock_Helper_Debug_ARM.xap as BETA to the store and send me the link? I would be very grateful (
@-W_O_L_F- maybe?
We're in very bad situation now. Thanks for any help or advices
Based on the Posting here (by @-W_O_L_F-) it looks like 8.1 Update 2 can't be interop-unlocked. So I'll need to downgrade first.
Edit: Assuming vcREG could write to Samsung Registry is only true for a small set of values, it is never true for interop-unlock. For this you need a registry editor with Samsung's RPC components.
There's no feature in sounds or anywhere in settings. Also if I need device rooted to do that, please let me link to how to vid, as I've never done that.
As far as I kbow, if you have a G800F device you can do it using a custom kernel:
http://forum.xda-developers.com/galaxy-s5-mini/orig-development/kernel-custom-kernel-t3130662
For other models, probably using an Xposed module. Both need root.
Damn. I don't get it, why the f they removed it from settings after kitkat...
tried to activate in H with build.prop, and all the vibration was gone
Use SQLite editor. There is a database in package Settings storage named settings.db, find hapic_feedback_enabled name in system category and change the value from 0 to 1 then restart the phone. I think this will help ))
First of all, I found this guide under the S7 Edge section on XDA. I tried it and it worked on my rooted A70, so I wanted to share it here.
There are two methods. One of them needs root access, and the other doesn't. I didn't try the one which doesnt need root access.
METHOD 1 (NEEDS ROOT)
1- Install a file explorer which can access and edit system folders.
2-Find build.prop and copy it.
3-Paste it to your main storage.
4-Open it with a text editor and go to the end of the lines.
5-You will see a line which says "ro.config.tima=1". Turn it into "ro.config.tima=0".
6-Save and copy new edited build.prop.
7-Paste it to it's original place and overwrite it.
8-Reboot your phone and check Samsung Health.
Rootless method is not working but if you want to test it, test it:
METHOD 2 (DOESN'T NEED ROOT)
I DIDN'T TRY THIS AND I AM NOT SURE IF IT WORKS
1-Uninstall the Samsung Health App.
2-Install Samsung Health version 4 https://www.apkmirror.com/apk/samsung-electronics-co-ltd/s-health/s-health-4-5-1-0011-release/s-health-4-5-1-0011-android-apk-download/
3-Launch the app and follow the steps to complete setup.
4-Update it via Google Play.
Thanks to @CuBz90
The non root method doesn't seem to work. App not installing.
sreedevtali said:
The non root method doesn't seem to work. App not installing.
Click to expand...
Click to collapse
Thanks for testing, I wasn't already giving it chance. I will note that it is not working.
How did you edit the /system? I am having trouble mounting it with read write privileges. My phone is rooted. Unable to "adb root" or mount system r/w. My multiple file explorer apps have had root access granted by magisk but I am still not able to replace it. I tried deleting it to see if I would be able to. I was able to but unable to paste the updated build.prop back into system. Had to reflash ??
cealaska said:
How did you edit the /system? I am having trouble mounting it with read write privileges. My phone is rooted. Unable to "adb root" or mount system r/w. My multiple file explorer apps have had root access granted by magisk but I am still not able to replace it. I tried deleting it to see if I would be able to. I was able to but unable to paste the updated build.prop back into system. Had to reflash
Click to expand...
Click to collapse
I think you're having trouble with pasting (overwriting) the edited build.prop.
I am using FX File Manager with root addon. You can try it. And, do NOT forget to give read/write acces to fx. To do so, when you open /system section you will see a lock icon on somewhere (top right) as I remember. Click it and give permission. Then paste the edited build.prop onto the original one.
Write here if you have any other problem.
Samsung Health
It’s very strange - my old Lenovo tablet, A3300 a firmware ResurectionRemix, Android 7, calmly sees and sets Samsung health from the playmarket. WADW? (What am I doing wrong?):смех: