In DNI3 imposed a bunch of restrictions on CSC, so custom bikes at the moment do not roll in determining the reg ini xml files and provxml new CSCMgrSvc.dll toggles UsePDACSC and loading is done with the internal CSC in Windows.
And it works?
how?Now if you have Wp 8.1.1 DP you can download the new firmware :good::good:
Shouldn't Diagnosis show "(o) ATO" after setting region to "000-AT" in SamWP8?New update for Ativ S with WP 8.0 GDR 3 (no DP for now),
if You have WP 8.0 GDR 3
- Open SamWP8 Tools
-Go on "Tweak" tab
- Set "Region" on "000-AT"
- Check for Update
Unfortunately I have DP :/
1) No. CSC code remains the same.Shouldn't Diagnosis show "(o) ATO" after setting region to "000-AT" in SamWP8?
On my device the old region value is retained in Diagnosis although SamWP8 says it's 000-AT. So I'm wondering what's wrong - ATO is in the CSC list when I check with diagnosis, but the old region is checked. Restarting the device doesn't help.
This is also a DP device with firmware from GDR2.
BTW: DP devices should get the new firmware as well - if region is ATO.
Did you unlock RPC?Thanks for your fast reply!
1) OK, that's surprising for me. That means there is more than one place where CSC is set.
2) Did that (again): Chose "000-AT" and tapped "SET". Closed and restarted SamWP8: Still "000-AT". Checked for updates: No updates.
Changed DeviceManufacturer back to SAMSUNG via Registry, restarted and made sure that it worked in Store. Checked for updates: No updates.
Disabled Developer Preview (in SAMWP8, region still is "000-AT"). Checked for updates: No updates.
Anything else I could do? (I'd like to get the fixed firmware without resetting my phone and without losing interop unlock.) Do I need to change the Region in Settings as well?
If I understand:
- If we are under DNI3, the downgradage on the less version (GDR2, GDR3) work or not?
- The Custom CSC not working on DNI3?
- If we are in the less version than DNI3 (CMK2 e.g) and that we flash a Custom CSC, then update to the new firmware DNI3, the Custom CSC is "broken" (this goes to the previous question)?
1) WorkIf I understand:
- If we are under DNI3, the downgradage on the less version (GDR2, GDR3) work or not?
- The Custom CSC not working on DNI3?
- If we are in the less version than DNI3 (CMK2 e.g) and that we flash a Custom CSC, then update to the new firmware DNI3, the Custom CSC is "broken" (this goes to the previous question)?
Yes I did.Did you unlock RPC?
no let it just sit in the documents folder.Yes I did.
Do I need to remove the "Non-Production Errors.txt" file again?
You must unlock the RPC! be quiet happened to me too and I solved this way:Hi every one,
I am originally on an Interop Unlock Ativ S for a while and on DP.
With SamWP8 Tools, I changed the key from 000-FR to 000-AT to apply the two last updates this week-end (8.10.14176.243 and8.10.14192.280).
But now, I cannot go back to 000-FR key.
If I check the SamWP8 Tools' Unlock section, "Unlock" and "Interop Unlock" are unchecked, "Prevent relock" is checked.
If I try to modify the "Unlock", the "Interop unlock" or "000-FR", close and go back to SamWP8 Tools, no modification is valable, I have stil "Unlock", the "Interop unlock" unchecked and the region set to "000-AT"...
If I try to read and modify the "PhoneMobileOperatorName" key from the SamWP8 Tools' registry editor [HKEY_LOCAL_MACHINE\System\Platform\DeviceTargetingInfo]
, nothing happened...
Is it possible that I lost the InterOp Unlock?
Do somebody has an idea to help me?
Regards
Thanks bro, everything is running now :fingers-crossed::good:You must unlock the RPC! be quiet happened to me too and I solved this way:
create this file: Non-Production Errors.txt (empty) in this location: Phone\data\Users\Public\Documents
You must unlock the RPC! be quiet happened to me too and I solved this way:
create this file: Non-Production Errors.txt (empty) in this location: Phone\data\Users\Public\Documents