Google translation from Russian.
1.When you try to include shows such a query:
2. Hard reset does not bring results, everything remains the same. When loading writes that operating system 6.5.
3. Activesync (winXP) and Windows Mobile Device Center (win7) offer before using the device to unlock it. Code is unknown to me, the computer device is not synchronized.
4. Flash the rom does not work. The reason - they do not see it (as it were). But in Device Manager device determines a driver on a well-established.
___________
I can not find the official windose mobile of 2003. I read somewhere that it can help.
Help please.
Photo for step 1.
Related
Dear everybody,
I have also killed my 2 day old MDA compact 3 by using the PDAMobiz_Dopod_P800W_AKU301_v1.1.2_PowerMap.exe (Feel really frustrated about it)
It will not load windows only
IPL 1.13.0001
SPL 1.13.0001
GSM 02.49.90
OS 1.28.0.0
I've tried a lot but nothing has worked so far. Now my last resort is using XDA tools to make a bootable sd card.
Is there anyone who make a file that the artemis can use of an SD card?
I would be very much obliged!
did you do CID unlock before installing new ROM?
CID unlock is not required for flashing the PDAMobiz Powermap 1.1.2 ROM. Just make sure you follow the right instructions. I did it and you can find it here:
http://forum.xda-developers.com/showthread.php?t=294830&page=2
But make sure that you have synced your Outlook data on desktop as there is something wrong with restoring from backup file the PIM related info (I use Spb Backup, but seems it is same with any backup application)
http://forum.xda-developers.com/showthread.php?t=295295
more info.
ianvanhaaren:
1. Please provide more info what exactly happens when you try to turn on your device.
2. What type of error you have when you try to re-flash device? At what percent it stops.
3. Connect device to USB, disable USB connection in activesync. Start mtty console, choose USB type connection (mtty attached, in case you need it).
4. type set 32 in console. send this output.
If CID area on device is corrupted, for the moment only imei-check who knows how to re-calculate this area. Even so, if device won't boot in windows it will not help. You need to connect to device thru jtag interface, in order to load modified spl into ram and perform writing into security area, to recover it. Imei-check says, they know jtag for Artemis.
It may cost you a bit of money.
If you have an option to send it to service center, do it. It would be your best choice.
Regards.
Hi,
I have tried to upgrade my HTC 3300. I get as far as a white screen on my PDA, but after this i loose the connection with Windows Mobile Center and the machine automatically disconnects.
Then i get the error on my PC:
Error 260
Please help and e-mail to [email protected] if you have a sollution.
Kind regards
Michael
miriedl said:
Hi,
I have tried to upgrade my HTC 3300. I get as far as a white screen on my PDA, but after this i loose the connection with Windows Mobile Center and the machine automatically disconnects.
Then i get the error on my PC:
Error 260
Please help and e-mail to [email protected] if you have a sollution.
Kind regards
Michael
Click to expand...
Click to collapse
Update UPSL v0.1 by Pof
Link here :
http://forum.xda-developers.com/showthread.php?t=311403
And try again..!
Cheers...!
Hmmmm.
What do you mean with:
Update UPSL v0.1 by Pof
Michael
Pof is a user
UPSL is an unlocker utility so you can flash alternative ROM's
check the link - very informative.
reflashing your phone usually takes a weeks worth of reading if you care for your device.
And read it :
http://forum.xda-developers.com/showthread.php?t=312052
maybe it help you..!
Is there an easier way to explain this - Sorry i'm quite good working with my PC, but this was a bit greek:
All you need to do is:
1. Remove your SD card
2. Do a hard reset or clean storage (some programs like battery status block full access to your device)
3. Connect your mobile to PC and make sure that activsync connection is established
4. Start to flash your device with USPL, when DOS part end and your mobile switch to bootloader mode vista will find new device and start instaling new drivers.
5. Wait till vista finish installing new drivers and unplug your device, do a soft reset
6. Next step is to change vista drivers to xp, to do this you need to fallow this instruction:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemi d=27
7. After switching the drivers plug your artemis again and install USPL, there should be no more problems with connection lost (errors 260, 270)
8. When USPL instalation will finish you can flash any rom you want to your arte
Succesfully tested on my T-Mobile MDA UK now I've got WM6 WWE.
Thanks pof for your great release
That explination is about as clear as it gets in 'phone talk'.
Perhaps elaborate a bit on what is exactly, or what step is, throwing you off.
Windows XP
Hi again.
Would i solve the problem if i just installed it from an Windows XP machine at work?
One final thing - Do you know if the GPS will still be working afterwards.
Have a good night from Oslo - Norway
Kind regards
Michael
I have recently installed Windows Vista on my computer and hooked up my also newly formatted PDA HTC TyTN with WM6 and as usual i cannot get them to work together, even speak. This by usb cable.
As i connected it to Vista it popped up asking me for a driver which i chose to install when Windows update said there was an update for it.
Error messages included:
This is my greeting message as soon as i start my computer and login to Vista:
http://www.premier69.com/images/stories/Capture.JPG
Installing the driver like Vista want to:
http://www.premier69.com/images/stories/Capture1.JPG
And the not so helpful error message:
http://www.premier69.com/images/stories/Capture2.JPG
If any of you would like, in order to help i can allow remote controlling of my computer.
I will offer compensation via paypal for anyone who will take the time to remote connect to my computer and fix my problem, i have been trying for a very long time now and i cant figure it out.
we can discuss level of compensation but be aware i am by no means rich.
If I understand u, try this
1- donlod Window device center from here
http://www.microsoft.com/downloads/...f1-e46a-4a5f-a791-09f07aaa1914&displaylang=en
choose for Windows Vista (32-bit) or (64-bit)
& let me know
I have already tried that, i downloaded the x64 version for my vista installation and i start the install file, the progressbar loads fully then retracts and the installations program self-closes. no messages or anything.
i am serious when i say i am really stumped by how my system is acting...
try installing WMDC in safe mode, sounds like a file permissions problem
yup i tried that too, it didn't even open the installation wizard.
Got same problem - fixed with changing registry permissions
hi guys,
i was battling with this for a few days after a reinstall of my laptop. updated to vista sp2 and there you go, couldnt sync and got the error.
after mucking about i saw there were some access denied errors for the registry. this is what i did to fix it:
registry key in question:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost\WindowsMobile
- Right click -> Permissions -> Advanced
- Took owner ship of the registry key
- Gave the Users group Full Control.
Then in device manager:
- Uninstalled my Microsoft Mobile Remote Adapter
- Scan hardware changes
and then it installed properly and am able to sync again
aj
thank you
Thank you thank you thank you thank you thank youuuuuuuuuuuuuuuuuuuuuuuuuuu
i have been in this issue since 2 days,and what got me crazy after i have read your post that I'm the one who restricted the access to this registry using a domain policy(I'm a network administrator) for security reasons,but i don't know why i didn't got it @ first.
I granted my self the permission and it was able to install the drivers and letting WMDC starts.
thank youuuuuuuuuuuuu again and again and again.
ajohan said:
hi guys,
i was battling with this for a few days after a reinstall of my laptop. updated to vista sp2 and there you go, couldnt sync and got the error.
after mucking about i saw there were some access denied errors for the registry. this is what i did to fix it:
registry key in question:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost\WindowsMobile
- Right click -> Permissions -> Advanced
- Took owner ship of the registry key
- Gave the Users group Full Control.
Then in device manager:
- Uninstalled my Microsoft Mobile Remote Adapter
- Scan hardware changes
and then it installed properly and am able to sync again
aj
Click to expand...
Click to collapse
I have a new HTC HD2 device and windows 7 enterprise on my laptop.
I did all, but no use
The Options, Schedule and status items in ActiveSunc are inactive.
Also when I open the ActiveSync, there is a message showed on my phone: "To synchronize your device with a desktop PC, install install synchronization software from your ....."
What can I do??????
Please help
hi i am trying to upgrade my Typhoon to 6.1 but i haver got to the point in the upgrading process in which i need to restart and press 0 for the IU the only issue is i do not recive this message and i cannot get any further.
Edit: my SPL is 2.05.0130
you must go to the patched SPL 1.09 for Typhoon befor you go any further.
yes it is true said tobbie, with 1.09 SPL you can flash any rom like WM6.1 or WM6.5 on your Typhoon
for SPL 1:09 Can you get HERE
oh well ive tried poatching the spl before but i just recive errorr 260 or 240 and i cannont make no progress i have tried using a different computer but to no avail
oh well... if the device is still original, then you must follow a sequence of actions to allow such upgrade.
These should be mentioned in any custom rom thread. Essentially you must get the SPL 1.09 on the device then you can load any custom ROM.
1. application unlock the old OS
2. CID unlock the device with lokiwiz toolset
3. load SPL 1.09
4. load custom ROM
good luck!
I belive i have already application unlocked and supercided it with lokiwiz toolset but i have peforemd a hard reset due to that connection issue, would that haver affected it in anyway? thanks
If you are back the old WM2k3 and you cannot upgrade the SPL, then lokiwiz probably has not super-CID your device. To check, connect your device in Bootloader mode to mtty (with AS having USB disabled) and enter "info 1" (no quotes) then try "info 2" (no quotes) and report both results.
Not sure about above myself as I have no device at hand today to check right now.
Hard reset does not affect the CID or SIM Unlock - these are stored in the encrpyted area of the ROM (64kb Block) that is not affected by Hard-Rest or OS-flashing.
sorry for my noobiness but it will not show in mtty i have tried the usb drivers? but the phone does not show in mtty
You must make sure that Active Sync (Windows XP) or Mobile Device Center is not using the USB port to connect the device. You can disable the use in Active Sync selecting the "Connections" menu and then disabling there.
Reconnect the device and restart mtty. The USB button will be there only if the USB connection is accessible and the device is connected to the USB port.
sorry for the bump but ive came back to my phone and i am having so my trouble superCIDin the phone i have done everything by the book, ive hard reset the phone and tried everything again and now SDA unclokder says "phone is not unlockable" and the lokiwiz.bat will not super cid it.
Look at mediafire in my kitchen folder here:
http://www.mediafire.com/?3tt15dyp4mbuu
the "...one time per device" ZIP has all tools inside. There is another (on board application unlock) that will do the trick. It installs a tool on the device, execute it there first and then start SDA Unlock. No need to reboot as the changed security policies are active immediately.
i downloaded your kitchen and i ran the htcunlock the the sda unlocker still says the phone is unlockable
So these Orange devices are quite resistant to application unlock. Did you notice that the HTC Unlocker kind of "remote controls" a registry editor? It may be that the changes did not really go through.
It is quite complicated and a lot of trial and error what you will have to do and I cannot advise in detail as I have no such device.
Key is that the application that changes the policy on the device is permitted to do so. Usually as well SDA Unlocker (remotely via the RAPI Policy) or the signed Registry editor controlled via HTC Unlocker can do that. It all goes to the registry keys in HKLM\Security\Policies\Policies where the relevant policy IDs have to assigned the right values (role permissions). You can use the free CE-Command (from ghisler.com) which has a registry tool built in or the same registry editor that HTC Unlcok controls to check if the values that the tools try to write are really written or not. I suspect they are simply NOT written. If you cannot find a tool that can change the policy, then there is another way around this:
The Gold Card method. Get the trial version of "revskills" from www.revskills.com and create a gold card with the device for the "Typhoon". With this card in the device, the SPL will allow ANY (also non Orange) signed ROM to be loaded. Use any non Orange shipped ROM for the Typhoon and load it to the device. This OS should allow to change the application lock and also allow the further steps.
Mind that ROMs for the Feeler or Amadeus have different key-handling (especially for the joystick) - so best you get also a Typhoon ROM for that exercise.
I think in the Tornado Forum was once a description how to unlock a Cingular 2125, possibly similar actions may allow you the first step. Not sure here though.
thanks for your help i beelive that your tool changes the registrey values correctly im nnot sure about this i have tried running it a few times but with the same results
Just to reassure that: Your device is not CID unlocked yet after all the trials you did? What does the SPL tell when you enter "info 2" in mtty connected?
Do you know how to work with a PC registry editor and to connect with the device? There are several that can do that, e.g. "Registry Workshop" or "Smartione" or "CE Regeditor". All these can connect to the device via Active Sync and read out the HKLM\Security\Policies\Policies branch.
Could you just post the export of that branch here?
You can also do that on board the device with CECmd, get into virtual two window mode, on one side go to the branch above (exactly, on top of the second "\Policies"), on the other in any file-directory, can also be root. Then on the registry side press "5" for copy and confirm to copy the "\Policies" branch to the other side. You get a text file called "policies.reg" - attach or post it here.
Finally you could search for the Microsoft tool "security configuration manager". This allows to select the security model "Security off" - once applied to the device the lokiwiz should run with success.
I have a Windows Mobile 6.1 device that I need to connect to Windows Mobile Center via Blutooth.
Note: The same steps Works with a Windows Mobile 5.1 device in the same computer, and I tested with two different computers.
I can pair the PC and the PDA without problem.
In the PC I run Windows Mobile Center.
In the PDA I run ActiveSync and select "Connect via Bluetooth".
The PDA open a window with the text "Openning port...".
The text changes to "User authenticated".
The window closes, and a full screen message with title "Synchronization Error" and text "This device is not allowed to connect to desktop computer" appears.
The PDA is a new and clean device. The computer isn't connected to Active Directory Domain. It has Windows 7 (the two computers tested)
I thing this is a security configuration, but I can't disable or grant access. The pair Works without any error, and I can see the pair settings on the PC and on the PDA.
Also: When I try to run an app (.exe) copied from SD Card or install (.cab) an error "This app is not signed with a trusted certificate" is shown, and I wan't to remove this block, but I can't edit register or Access via ActiveSync.
Note: I post similar questions on other forums, different to "xda" without response.
Thanks for your help!
In the end the problem was that the device was locked for security. The manufacturer sent me a cab to disable security, which in this case only annoyed.
If someone has the same problem, send me an email to duefectu(a)sd-a.com and I will forward the file.
Thanks for your time!
In the end the problem was that the device was locked for security. The manufacturer sent me a cab to disable security, which in this case only annoyed.
If someone has the same problem, send me an email to duefectu(a)sd-a.com and I will forward the file.
Thanks for your time!