Related
I am running WM6, but my company implemented push email, and the device is now app unlocked after installing some certificates etc. I cannot run half of my programs - I tried the SDA-Application.exe program, which seemed to be succesful, but did not work. I cannot open a registry editor either.
I search all over this forum but cannot find the answer - how can I app unlock my wizard again?
We are also about to be issued HTC Touches which are similarly app locked, so it would be useful to have a method that worked for both!
Thanks
have you tried the lokiwiz and awizard apps?
rgs
No - these don't do certificate/application unlocking do they - I thought just CID/SIM locking?
PS I tried installing lokiwiz but I can't due to the app lock!
Both awizard and lokiwiz don't simply remove the Unsigned App Policies nor RAPI communication restrictions. What they need to work is for the phone to be in that state (app+rapi unlocked) and that's why there are some CAB that go along that are supposed to be run prior.
You can use my tool (WST - check signature) that does it with a click of a button
cheers
Great tool - didn't connect on Vista, connected on XP but says:
Not needed!
Regsitry settings are already set to use RAPI tools.
But I still cannot run unsigned apps! I have rebooted. I know they added a root and user certificate to the device - all apps have to be signed now.
Do you have any ideas?
Thanks
Sure, get yourself a registry editor and browse to HKEY_LOCAL_MACHINE\Security\Policies\Policies and edit two values:
:00001006=dword:1
:0000101a=dword:1
hope it does the trick
I tried mobile reg editor, which lets you edit the registry from a PC, and one of the reg keys was set to 0. But I changed it, rebooted, and same probem
hsclater said:
I tried mobile reg editor, which lets you edit the registry from a PC, and one of the reg keys was set to 0. But I changed it, rebooted, and same probem
Click to expand...
Click to collapse
Ok, looks like they changed some other settings that interfere with the permissions.
Check if HKEY_LOCAL_MACHINE\Security\CertMod\AllowUntrustedApps is set to DWORD: 1
Hang on I figured it out....the 00001006 key was for some reason not applied once I rebooted. Thanks for all the help!
For anyone needing to do the same - I had to download mobile registry editor from http://mobile-registry-editor.en.softonic.com/pocket as that allows you to edit keys from the PC without installing anything.
My new problem, is that on our touch/elf I cannot change this key with this program as it says access denied - so there must be some registry permissions on there.
hsclater said:
Yes that is set to 1. It should be right?
Click to expand...
Click to collapse
I pointed that because when i set it to 0 the phone refused to install apps so i thought it was the responsible registry value.
Must be another one then...
Thanks for all your help - my wizard is now sorted.
Any idea how they restricted the registry on a touch so I can't change that value?
hsclater said:
Thanks for all your help - my wizard is now sorted.
Any idea how they restricted the registry on a touch so I can't change that value?
Click to expand...
Click to collapse
I believe those settings are more related to WM6 than to the specific device so they should be the same.
btw, how did you sort it out? I'd like to know for future use
tx
Mine was just fixed by changing the 1006 value. The first time, the phone didn't take the change, but the second time it did and now works.
But the touch, it won't let me edit the registry remotely - access denied.
Cheers.
upload Cert_SPCS.cab to your phone and run it
PS:
sorry for asking but i didn't read your edit before
I am not able to get my SPC /MSL from my new Sprint Diamond that I have been able to unlock, and flash Juicy 2.2 onto it. Since then I have performed a hard reset and gone back to the factory ROM.
I have tried the following:
1. Performed the instructions for getspc from
http://forum.ppcgeeks.com/showthread.php?t=36639
(Note I did use the PHex Esn and I did use caps on all hex numbers)
2. I was able to install QPST on a on WinXP box and get it to see the phone. I did this to verify that I had the correct hex esn. QPST did read the esn from the phone and display the same hex esn that I had in step 1.
3. I tried the general codes 000000, 123456,111111 and the last 6 digits of the phone number programmed in the phone 000-000-2743.
I am entering the number (6 digits) that getspc.exe tells me in the enter unlock code box that comes up after I enter ##778# and hit edit. It looks like it is working on something then tells me the code is wrong.
What is the way that I can get the SPC / MSL without calling?
The only answer I found
I hate to ask and answer my own questions but if anyone else runs into this problem I want them to have an answer.
I could not get getspc.exe to work in any way.
I found this registry hack somewhere so I am not taking credit for it but it works!!!!
Change the following registry entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ATDbgLog
Enable: 1
LogMode: 1
* Wait a reasonable amount of time and soft-reset (I have noticed that it seems to take longer for this value to take affect, so if you reboot and the registry values are not changed, then you need to do it again and wait longer)
* Check to see that the file \ATDbg0\ATDbg0.txt has been created.
* Return the values back to what they were (most likely 0) waiting the same amount of time as above.
* Look in the ATDbg0.txt file and you should see a log of commands sent to the CDMA radio and there should be something like this somewhere in the file:
|| Begin Code Sample ||
11:9:3 Tx:AT+HTC_RMSL=0\r
11:9:3 Rx:+HTC_RMSL: 354201\r\n0\r
11:9:3 Tx:AT+HTC_ROTKSL=0\r
11:9:3 Rx:+HTC_ROTKSL: 216112\r\n0\r
|| End Code Sample ||
The numbers next to the Rx: +HTC_RMSL line should be your MS
I used resco exploror to change my registry waited about 1 hour and did a soft reset twice during that time.
I found the directory with the output file in the root directory.
Yes, it works
the getspc.exe, don´t work, but the this process work very fine
I am hoping that someone with an Ativ S can download the "DiagnosticTool_Sprint" from the Windows Phone store and upload it here. It is available if you set "oemId=htc" in fiddler. I think there are some hidden pages we can use to interop unlock HTC.
Link:
"DiagnosticTool_Sprint" for Windows Phone http://www.windowsphone.com/s?appid=e69a2877-59b8-43ed-898d-554fbc4b8b2b
Thanks!
To be clear, you are asking that somebody download this HTC app to their phone and install it, then use the MTP full file system access to extract the binaries for reverse engineering? Sounds like a plan, if I could persuade my phone to do the full file system access thing right now I would (away from home, on my Surface RT right now).
compu829 said:
I am hoping that someone with an Ativ S can download the "DiagnosticTool_Sprint" from the Windows Phone store and upload it here. It is available if you set "oemId=htc" in fiddler. I think there are some hidden pages we can use to interop unlock HTC.
Link:
"DiagnosticTool_Sprint" for Windows Phone http://www.windowsphone.com/s?appid=e69a2877-59b8-43ed-898d-554fbc4b8b2b
Thanks!
Click to expand...
Click to collapse
Hi
first to download this app we need someone with a sprint device to grab correct url using fiddler.
like this one:
Code:
http://marketplaceedgeservice....................os=8.0.10512.0&cc=us&lang=en-us&hw=268473858&moid=sfr-fr/
this way we can have correct hw & moid value & install on any device...
@GoodDayToDie yup. that is what I am asking for. Based on what @thals1992 saw when he was playing with this on his 8XT is that depending on what dial codes you put in, the same app loads with different pages.
@xboxmod the only thing that needs to be changed to enable downloading from the store is the oemId. It needs to be HTC. I was able to download it to my T-Mobile Branded 8x (which Sprint doesn't even sell) with no issues. (it's moID is "null" for some reason on my phone after applying GDR3 and hard resetting)
compu829 said:
@xboxmod the only thing that needs to be changed to enable downloading from the store is the oemId. It needs to be HTC. I was able to download it to my T-Mobile Branded 8x (which Sprint doesn't even sell) with no issues. (it's moID is "null" for some reason on my phone after applying GDR3 and hard resetting)
Click to expand...
Click to collapse
Thanks
"null" value was the trick.:good:
xboxmod said:
Thanks
"null" value was the trick.:good:
Click to expand...
Click to collapse
Were you able to get this off your Ativ? I'd love to start ripping into it.
compu829 said:
Were you able to get this off your Ativ? I'd love to start ripping into it.
Click to expand...
Click to collapse
I did manage to extract the DiagnosticTool_Sprint and it's now an unencrypted xap, the data.zip is all the files how I found them on my phone (with the exact path to the program and the appdata).
I will decompile The dlls and Look for hidden pages
Sent from my RM-821_eu_euro2_248 using Tapatalk
bruce142 said:
I did manage to extract the DiagnosticTool_Sprint and it's now an unencrypted xap, the data.zip is all the files how I found them on my phone (with the exact path to the program and the appdata).
Click to expand...
Click to collapse
Thanks!
@GoodDayToDie @xboxmod Apparently there is a capability called <!--Capability Name="ID_CAP_NVREADWRITE" /-->. Too bad it's commented out in their manifest :/ I wonder what it does? (besides the obvious, based on the name)
edit:
I was able to plug in my phone and Windows Updates decided to install drivers! I now have "HTC Diagnostic Interface (Com 6)", HTC NEMA Interface (Com 8)", "HTC USB Modem", and "HTC Remote NDIS-Based Device" (this one is currently Code 10.) Thanks Sprint! >
I'm looking for a solution to store maps on there sd card.
So far, i have found multiple options:
1) Use lumia storage check beta, only this doesnt work for Huawei phones
2) Edit the registrykey UseExternalStorage, unfortunetly this is a dword, I havnt found a tool save dword to registry
Any other suggestions?
letalis said:
I'm looking for a solution to store maps on there sd card.
So far, i have found multiple options:
1) Use lumia storage check beta, only this doesnt work for Huawei phones
2) Edit the registrykey UseExternalStorage, unfortunetly this is a dword, I havnt found a tool save dword to registry
Any other suggestions?
Click to expand...
Click to collapse
Did you interop unlocked ? your device?
I suggest you to interop unlock your device and use mass storage mode to edit registry dwords.
ngame said:
Did you interop unlocked ? your device?
I suggest you to interop unlock your device and use mass storage mode to edit registry dwords.
Click to expand...
Click to collapse
I agree with @ngame, only need to interop unlock your device with WojtasXda Rom: http://forum.xda-developers.com/showthread.php?t=2686053 and then use my guide updating WojtasXda GDR2 to GDR3: http://forum.xda-developers.com/showpost.php?p=51656759&postcount=28 then you can use WPH Tweaks: http://forum.xda-developers.com/showthread.php?t=2486387 to enable option Map2SD.
Hope I helped you
myst02 said:
I agree with @ngame, only need to interop unlock your device with WojtasXda Rom: http://forum.xda-developers.com/showthread.php?t=2686053 and then use my guide updating WojtasXda GDR2 to GDR3: http://forum.xda-developers.com/showpost.php?p=51656759&postcount=28 then you can use WPH Tweaks: http://forum.xda-developers.com/showthread.php?t=2486387 to enable option Map2SD.
Hope I helped you
Click to expand...
Click to collapse
I got a long way, I used your manual for the flashing procedure. Did all the steps now looking at the Huawei logo on my phone with the text:
iWare uniBIOS FFU Application
AllocatePool Status is Success
etc etc....
However I am ready to flash my phone with the .app file, but i got the following error message:
WH62406270ML01
Invalid upgrade file.
Any suggestions
letalis said:
I got a long way, I used your manual for the flashing procedure. Did all the steps now looking at the Huawei logo on my phone with the text:
iWare uniBIOS FFU Application
AllocatePool Status is Success
etc etc....
However I am ready to flash my phone with the .app file, but i got the following error message:
WH62406270ML01
Invalid upgrade file.
Any suggestions
Click to expand...
Click to collapse
I turned to the dark side , i downloaded the russian rom version (mentioned on the german site). This one is flashing just fine. Hopefully this rom will also let me use the registry editor and other tools.
mmm unfortunetly no luck... unable to upload the unableallsideloading app
letalis said:
mmm unfortunetly no luck... unable to upload the unableallsideloading app
Click to expand...
Click to collapse
What's the problem?
ngame said:
What's the problem?
Click to expand...
Click to collapse
I figured it out, used an other ROM and used the tool to interop unlock my phone, now i can run homebrew apps and my cards are on the SD :good:
Now up to wp 8.1
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.