Thread Deleted

[Q] Updating unlocked Vox

OP col320ce

8th March 2012, 08:50 PM   |  #21  
tobbbie's Avatar
Senior Member
Flag Stuttgart
Thanks Meter: 239
 
1,395 posts
Join Date:Joined: Jan 2007
More
I could make a gold card for you, but I would need that card-ID. Possibly there are other methods to get that - or even write that to the card.

In revskills is also another (new for me) option which I had never exploited "Get CID using ADB". No clue how that works, probably a workaround for the missing WinMo device.

Strange that native Windows OS cannot retrieve that Card ID.

---------- Post added at 09:24 PM ---------- Previous post was at 09:16 PM ----------

ADB will not work - it seems to be the "Android Debug Bridge", so the Andriod option for what the ITSUtils do on the Windows Mobile side. No option for you...

---------- Post added at 09:50 PM ---------- Previous post was at 09:24 PM ----------

After some more googling it really seems impossible to retrieve the SD Card-ID via native means on the PC. There are some posting code that should work for readers attached directly to the PCI bus but that does not work via USB.

So back to start with Gold Card: you need a WinMo device.


Lets us try to debug the Modaco method in more detail:

The first cab should allow certificate installation, what does it say when you install that one?

Do you know hot get the registry data from your device? Could you post the path:
HKLM\Security\Policies\Policies\*
The Following User Says Thank You to tobbbie For This Useful Post: [ View ]
8th March 2012, 09:11 PM   |  #22  
tobbbie's Avatar
Senior Member
Flag Stuttgart
Thanks Meter: 239
 
1,395 posts
Join Date:Joined: Jan 2007
More
Two more items:

Windows Security Model (mentions Orange to be special...): http://technet.microsoft.com/en-us/l.../cc512651.aspx

Orange supplied certificates from a security SW vendor:
http://de.sophos.com/support/knowled...le/108111.html
I checked if the cab loads on smartphone, but the _setup.xml mentions "PocketPC" as platform, so it does not. I changed that string to "Smartphone" and put that to another cab which installs ok on my smartphone.

Try on yours and see if that opens the door for further getting security restrictions lifted.
13th March 2012, 11:32 PM   |  #23  
OP Junior Member
Thanks Meter: 0
 
22 posts
Join Date:Joined: Dec 2011
Quote:

Lets us try to debug the Modaco method in more detail:

The first cab should allow certificate installation, what does it say when you install that one?

Do you know hot get the registry data from your device? Could you post the path:
HKLM\Security\Policies\Policies\*

Prep cab installed (after reset):
-<wap-provisioningdoc>
-<characteristic
type="SecurityPolicy">
<parm
name="4119"
value="144"/>
</characteristic>
</wap-provisioningdoc>

There are no other messages.

Registry Data:
Not sure if I have done this correctly but see attached screen shot.

Unfortunantly the cab file did not seem to unlock much. It ran ok but I re-did many of the things I have tried without change.
Attached Thumbnails
Click image for larger version

Name:	reg-info.jpg
Views:	13
Size:	80.8 KB
ID:	945822  
14th March 2012, 09:14 AM   |  #24  
tobbbie's Avatar
Senior Member
Flag Stuttgart
Thanks Meter: 239
 
1,395 posts
Join Date:Joined: Jan 2007
More
The registry does not show signs of unlock. The value names are the hex of the policy in the cab, so the 4119 that should be changed to 144 is 1017(h) but that has still 128 as value - so no change done.
The key to remote access is the first policy - this should go to 1.

I think it is not worth to further follow unlocking the Orange locked OS policies. The Gold Card method will for sure work as it replaces the OS - so the only path to follow.
14th March 2012, 12:57 PM   |  #25  
OP Junior Member
Thanks Meter: 0
 
22 posts
Join Date:Joined: Dec 2011
I may have got my wires crossed and missled you. The registry data above was only after the PREP.cab file

I have included a screenshot of the registry after the:
MoDaCo_Fix_Pack_0.5 cab
RemoveSecurity cab
and finally the cab you posted from the Security SW Vendor.

Not sure if this changes anything ...

Ignor this ... they are all the same I think.
Attached Thumbnails
Click image for larger version

Name:	after-MoDaCo_Fix_Pack_0.5.jpg
Views:	8
Size:	55.6 KB
ID:	946611   Click image for larger version

Name:	after-remove-security.jpg
Views:	8
Size:	82.7 KB
ID:	946612   Click image for larger version

Name:	after-certificates-from-a-s.jpg
Views:	9
Size:	84.8 KB
ID:	946613  
Last edited by col320ce; 14th March 2012 at 01:00 PM.
14th March 2012, 02:45 PM   |  #26  
tobbbie's Avatar
Senior Member
Flag Stuttgart
Thanks Meter: 239
 
1,395 posts
Join Date:Joined: Jan 2007
More
The sequence should be this:
  1. install the security SW Vendor cab. This should install additional certificates that allow better admin of the device.
    No matter when you installed that - further actions come only after this.
    Registry will not change here - only certificates that grant access to relevant signed applications.
  2. After this the security config manager from MS should work.
  3. You may also try the HTC Unlock, but I doubt this works right away.
Modaco or other scripts are not signed and will not work until above is done.
Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes