Related
Hey all. Sorry if this is in the wrong forumsection, feel free to move it if so.
I am having problems syncronizing my TyTn II with my PC. I am using Activesync 4,5. I read somewhere that this can occur if you change the usb port from the one you were using the first time, and i think that is what i might have done.
Has anyone else had this problem? What can i do to fix it?
This (registry change) did the trick for me
http://www.aximsite.com/boards/activesync/120851-activesync-4-1-sygate-personal-firewall-pro.html
Thanks mate, that seems to be a solution to the problem. Only problem now is that as far as i know i dont have a regedit program on my phone. Which one should i use and how to i go about using it? How do i get the program onto my phone when i cant use Activesync?
Appreciate any help..
I just started a thread like this in the Hermes forum
http://forum.xda-developers.com/showthread.php?t=361633
here's what i got, haven't tried it yet.
cyberscribe said:
Try this procedure step-by-step
1. make sure your phone is not connected to the computer in any way
a. Bluetooth off
b. WIFI off
c. USB cable not connected
2. Run spybot S&D (I always do this when the computer misbehaves - and make no mistake your computer is misbehaving)
3. Terminate all other running programs
4. Hook your phone to the usb cable and the usb cable to the computer. (don't worry if it syncs or not)
5. Open Device Manager and select Network Adapters
6. Uninstall the Windows Mobile Device
7. Disconnect the Phone
8. Open the Control Panel "Add/Remove Programs" and uninstall Active Sync
9. Reboot the computer
10. Connect to the internet and get a fresh copy of Activesync 4.5 and install it.
At this point if you can back up your PIM to the storage card or something it would be great because I suggest you do a hard reset of the phone. go to the settings page and select System. Tap the clear storage icon and follows the instructions to reet the phone.
11. Reset phone as above
12. When phone reboots, connect it to the computer via the usb cable.
Phone should sync from now on.
Good Luck
PS.
MrVanx is right, that could help but it will limit your phones capability. However if my method fails that may be your only option short of reflashing the phone with some other ROM.
Click to expand...
Click to collapse
Thanks for the tip there, sook. I just tried it and it didnt work for me.
I did all the steps except for these:
5. Open Device Manager and select Network Adapters
6. Uninstall the Windows Mobile Device
The thing is i cant find my mobile device anywhere in the device manager or in the network adapters subcategory. Any ideas?
Is there any way to edit the registry on my phone without having to download and install something? Like a built-in program or something..
SeqHTCTyTnII said:
Thanks mate, that seems to be a solution to the problem. Only problem now is that as far as i know i dont have a regedit program on my phone. Which one should i use and how to i go about using it? How do i get the program onto my phone when i cant use Activesync?
Appreciate any help..
Click to expand...
Click to collapse
Download through wlan or copy it to the memory card with pc...I used TascalSoft TRE:
http://www2r.biglobe.ne.jp/~tascal/download/pocketpc/tre_e.htm
I tried everything: SDA_ApplicationUnlock, HTC_ApplicationUnlock, SdkCerts.cab, SP_AllowCertificateInstall.cab, default_signed_disablesecurity.cab.
Of course experimented with hard reset, different Active Sync versions.
Just cannot install PocketUAE, PocketSNES and other unsigned apps.
use VS2008 to adjust your security level.
http://forum.xda-developers.com/showthread.php?t=400122
Hm you can use Security Configuration Manager to turn security off!
Install it to your PC and connect your Phone via ActiveSync. Then choose Security Off and click promote! After a little while it's done!
Download from MediaFire
Thank you very much!
Would you please renew the link for this program.
Having the same problem with "...trusted certificates"
Thanx in advance
Here you go: http://www.mediafire.com/?k1egbyo05gs
Gosh! Vielen Dank! Thanks a lot!
Wil it work with WM 6.1? Any instructions?
Will be much appreciated.
It should work with 6.1, same instructions as above.
This program is 100% working!!!
It was just perfect, man! As you said, I chose "Security Off" and it gave me report that "tool.cab" was successfully installed!
You saved my life, I'm really grateful!
Strongly recommended to everyone who has a problem with "Trusted Certificate" and *.cab files installation!
Once again, Vielen Dank!
On Windows 7 that program is garbage... Any solution?
Help with HTC Snap - same problem
frauhottelmann said:
Hm you can use Security Configuration Manager to turn security off!
Install it to your PC and connect your Phone via ActiveSync. Then choose Security Off and click promote! After a little while it's done!
Click to expand...
Click to collapse
I downloaded the Security Config Mgr to PC, connected phone with ActiveSync, ran program to turn Security Off but getting same error on phone to Security Mgr access "program or setting cannot be installed because it is not digitally signed with a trusted certificate".
Its a new phone through work so I didn't know if they could lock up security/access in other ways.
Any thoughts?
If it helps, the Security Mgr indicates the current config on the phone is "One-Tier Mobile2Market Locked".
When I click on provision, I get a pop up on my phone to install Tool.cab, I click yes, but it said the install was unsuccessful and error comes up on my PC.
+1 Also having problems with the program on Windows 7. Any alternatative way to update the security settings on the phone?
this program works great.. you saved my day, buddy
Cheers
hc000 said:
When I click on provision, I get a pop up on my phone to install Tool.cab, I click yes, but it said the install was unsuccessful and error comes up on my PC.
Click to expand...
Click to collapse
For anyone having a problem with this program on 7. It's likely that youre running x64 and it's also likely that this is 16 bit software. Install XP mode from microsoft.com and youre set
Hi, i seem to be having the same problems with this issue, i am currently using XP (sp3) and like with the folks that was having problems getting the pop up on the phone to install the Tool.cab and the unsccessful and error comes up on the PC, any further suggetions? Thanks for you help so far
I'm haing the same problem. My phone got automatically application locked after updating the ROM, God knows why!? I have Xp SP3 (secutiry manager wownt run under 64 bit systems) and when I click on "provision" after adjusting the security level for certificates I get a message in the phone "Installation of Tool.cab was unsuccessful". Going crazy... now I cannot run Andriod becuase it's not a "trusted application".... @#$%# you bill gates.
hc000 said:
When I click on provision, I get a pop up on my phone to install Tool.cab, I click yes, but it said the install was unsuccessful and error comes up on my PC.
Click to expand...
Click to collapse
The same here could anyone help me???
dEaK said:
I tried everything: SDA_ApplicationUnlock, HTC_ApplicationUnlock, SdkCerts.cab, SP_AllowCertificateInstall.cab, default_signed_disablesecurity.cab.
Of course experimented with hard reset, different Active Sync versions.
Just cannot install PocketUAE, PocketSNES and other unsigned apps.
Click to expand...
Click to collapse
I found the solution Special THANKS to JZ SmartMort
Following simple steps:
1) Download following file: http://www.internet-tools.co.uk/blog/wp-content/uploads/2008/11/sda_unlock.zip
From archive we need only SDA_ApplicationUnlock.exe
It allows Registry to be edited from PC.
Run it with working Activesync connection
2) Download Mobile Registry Editor: http://www.zipsoft.ru/catalog/mobile_registry_editor-v1_11.html
Also run with working Activesync connection
3) and modify the following keys to the values listed.
("HKLM","Security\Policies\Policies","0000101b","1 ")
("HKLM","Security\Policies\Policies","00001005","4 0")
("HKLM","Security\Policies\Policies","0000101a","1 ")
("HKLM","Security\Policies\Policies","00001001","1 ")
("HKLM","Security\Policies\Policies","00001017","2 4")
It perfectly worked with HD2, but I guess it should work with all WM devices.
FYI, here are some other useful software packages that relax the security.
http://forum.xda-developers.com/showthread.php?t=285344
http://www.internet-tools.co.uk/blog...tegory/mobile/
http://www.internet-tools.co.uk/blog...sda_unlock.zip
http://sedacka.saman-cz.com/ppc/inde...unlocking.html
http://forum.xda-developers.com/showthread.php?t=338433 --- the first file in this article.
4) Restart
P.S. Special THANKS to JZ SmartMort
I've been working on a step-by-step CLOSE-UP VIDEO guide to Flashing a ROM, including how to HARD SPL, to make available to users here. Here are things I'm still not clear on.
(These were posted recently to the Guide written by mskip in the Kaiser forums. He answered some questions, but these are still unanswered. )
Flashing via ActiveSync with USB Lead
2. Pull out the battery and reinsert it (this step IS important) *DONT turn phone back on yet*
Click to expand...
Click to collapse
** When is this step necessary & required (whether during initial HARD SPL or FLashing a ROM post-HardSPL) , as opposed to simply "Best Pratices"? What is this step accomplishing?
8. After a few seconds the tri colour screen will appear on the phone and "USB" will be displayed at the bottom
9. Unplug the usb cable for 30 seconds and then Replug (phone will not re-sync but still says "USB" on the screen)
Click to expand...
Click to collapse
** Please explain #9, what it is accomplishing & thus why recommended?
"Active Sync" vs "USB connection"
Please tell me if this is accurate or not:
(1)When installing via PC vs installing via Storage Card: After data has been backed up to PC by way of "Active Sync", thereafter, when performing any ROM updates (HardSPL or flashing a new ROM) the app "Active Sync" is technically no longer involved in the flashing process, but rather, what's necessary is simply having a USB connection from device to PC, correct? Is the distinction that Actice Sync can foul up the basic data connection from phone to PC necessary to flash a ROM. I want to be very clear. Is this accurate?
10. Right click on the Activesync icon in the bottom corner icon on the computer, goto connection settings, deselect "Allow USB connections" and click "ok"
11. Microsoft ActiveSync icon will now have a red cross in it and the program will say "Connection Disabled"
12. Run the ••••••RUU.exe file on your PC thats in the same folder as the HardSPL .nbh file and follow instructions (ticking boxes and clicking Next) *DO NOT reenable USB Connections in Activesync*
Click to expand...
Click to collapse
** same as above: Are these just more compensations in order to disable MS's incorrect assumption that the insertion of a USB cable always equals "launch an Active Sync session" ?
15. Unplug USB cable from phone then REPLACE SIM & SD CARDS !!
**Remember to re-enable "Allow USB connections" in Activesync connection settings after a successful flash**
Click to expand...
Click to collapse
Why, exactly, is it required to unplug the USB cable? Is it, again, a "Best Practices" precaution to prevent any kind of accidental read/write of data?
A few questions re entering Bootloader mode, various scenarios:
1. In some older guides, even for when flashing a rom to phone device from your PC , sometimes a step is specified to "enter Bootloader mode by holding & pressing the xxxx and xxx keys on your phone, and then xxxxx".
2. But if you have an RUU folder that includes the Bootloader.exe app, along with the RUU.exe and .nbh file, then by running the RUU.exe app, the entering bootloader mode is handled automatically, sending the commands to phone, which automatically place the phone into the tri-color screen mode? -- as opposed to one having to manually press xxxx and yyyy on phone to enter bootloader mode? Correct or not?
3. If correct: then, does it matter on which screen or in which mode your phone is currently on in order to begin the flash-ROM process? Could I just as well be on a Total Commander app screen or on a TouchFlo Today screen?
4. Some guide-writers recommend users hard reset their phones before starting a new flash-rom session, just for "best practices". Others consider this superfluous & irrelevant, and what matters most is a Hard-Reset be run immediately AFTER flashing a new ROM. ... Any opinion on this?
Flashing Via ActiveSync
<snip; this is deep into the flashing process >
2. Turn phone back on and wait until it syncs with your PC
Click to expand...
Click to collapse
** Would it be more accurate to say here "until your PC confirms it has a USB connection to your phone"? (You're not looking to run a sync session, but rather just getting a USB connection for files to be transferred from PC to phone.) I think the term "Active Sync" often creates more confusion than helpfulness in this whole realm of moving files from PC to phone. )
Question re RUU.exe file on PC:
From what I have seen in the ROMS I have used in years 2008-2009, the extracted ROM folders I've downloaded from the chefs have typically all had the file " Bootloader.exe " within the RUU folders, and that (in the case of mskip's Flash Guide for Kaisers) KaiserCustomRUU.exe calls the Bootloader.exe app which sets the phone into bootloader mode from the PC, without one needing to manually set the phone into bootloader mode.
But this is your response from your initial quick-reply, which confuses me"
The customRUU automatically puts the phone in bootloader mode thus there is no need for the seperate file (bootloader.exe).
Click to expand...
Click to collapse
** This confuses me. I am principally trying to distinguish between when one needs to manually set phone into bootloader mode -- and when this step is handled by the PC's RUU.exe process. In the older (around year 2007) "How to flash" guides, users were often told they needed to create a folder, make sure they have the correct RUU.exe file inside it, make sure they have the correct .nbh file, make sure they don't have files that are there for those with soft SPL phone, etc. And as far as I can recall, in those older Guides, this bootloader.exe file was not included. And thus users were instructed to manually put their phones into bootloader mode...
The difference being that for the past year or more, chefs currently are now providing the whole contents of the RUU folder in the .rar file, so that if you've hard-SPL'd, then that .rar file has eveything you need, and all you need to do is launch the RUU.exe -- never having to set your phone manually into bootloader mode.
Yet you are saying
Quote:
thus there is no need for the seperate file.
Click to expand...
Click to collapse
I'm not a coder, but I don't get this. Why would bootloader.exe be inside practically every RUU Folder nowadays if it were unnecessary to set the phone into bootloader mode to initiate the flashing process? You were saying the RUU.exe app itself would contain some method of setting phone inot bootloader mode without even needing that bootloader app present in the folder.
Could someone please clarify.
And secondly: Does it matter one bit of difference which screen your phone is on when you commence with running RUU.exe ?
And third : If users happen to be confused, and think they must manually set their phone into bootloader mode, as part of running RUU.exe, and they do manually set their phone inot bootloader mode and get the tri-color screen: Does that conflict with or hamper in any way the running of the RUU.exe program from the PC? Or does the RUU process just simply proceed, and send an "enter bootloader mode" instruction to the phone, which then causes the phone, already in tri-color screen, to be reset again into bootloader mode (and there is no problem that the phone was already in bootloader mode) ?
After New Rom is Completely Installed and You Have Customized Your Phone:
** I think it in dutty's guide where he says "after customizing your phone, power down your phone, then power it back up". Is this power-down/ power-up cycle equivalent to just doing a soft-reset? What is the difference as it pertains to that specific step after customization?
Quote:
Flashing Via MicroSD Card
<snip>
3. Goto the Roms Folder and rename the .nbh file to KAISIMG.nbh
4. Copy the KAISIMG.nbh file to your MicroSD Card
Click to expand...
Click to collapse
** Where does one get the correct 4-LETTER CODE for their phone if one has a DIFFERENT phone than Kaiser and wants to flash via MicroSD card?
-----
Thanks to anyone who can please clarify these points
2. Removing the battery is not required in any level of flashing a ROM. removing the battery for Hard-SPLing is not required on all devices. For instance, my polaris doesn't require removing the battery.
9. Not sure why you need to do that but it IS necessary (you can pm Olipro about it) but i'm pretty sure it has to do with updating the connection between the PC and the PDA since while in Bootloader the PDA doesn't act as a plug-and-play device.
11. I don't recall this being an important step as I flashed hard-spls and roms without changing the AS state. you HAVE to have an activesync connection with your PC in order to flash (doesn't have to be synced, but the PDA has to be recognized by activesync, hope this is clear).
15. Yes, it is not a MUST. you can flash roms and spls while leaving the cable connected.
---------------------------------------------------------------------------------------------------
2. Yes, if you have the full library containing bootloader and everything you can flash without entering bootloader manually prior to flashing.
3. flashing doesn't require a specific state. you can start the process whenever.
4. Hard-reseting before MIGHT make a difference... in some cases which i'm not familiar with. maybe there's an app which can disturb the flashing process.
Hard-reseting after is pointless as flashing a rom performs exactly that WHILE switching the OS.
-about the syncing.. yeah, you don't need an actual sync-session. a usb connection is enough (AS LONG AS the comp identifies the hardware of course)
-it doesn't matter if you have the bootloader.exe file inside or not (I assume it depends on your device as well.. but not sure). RUU runs bootloader automatically. about HARD-SPL.. yeah, i haven't seen a hard-spl which doesn't contain bootloader.exe.. (i again suggest you pm olipro about this)
-again, it doesn't matter which screen you're on when running the ruu
...
-about the phone codes for flashing... you can find all codes for all phones in the forum
for instance,
Polaris -> POLAIMG.nbh
Hermes -> HERMIMG.nbh
Blackstore -> BLACIMG.nbh
Diamond -> DIAMIMG.nbh
Raphael -> RAPHIMG.nbh
Trinity -> TRINIMG.nbh
yada yada...
you can search, and i'm pretty sure not ALL devices have this option..
the wifi also contains info about flashing from SD card.
also, wonderful initiative and i hope you will agree to post this in the GUIDES thread.
preface for the people not reading ... some quick answers:
- our page on this Hard-SPL is always here: http://rhodiumw.htc-unlocks.com/hard-spl.php
- license: you will just have to run the program on the PC with phone connected, normally you will not notice anything about the licensing, it is totally free for personal use!
- if you need help with license issues (when it says you already unlocked a device), you can send your message at: http://support.htc-unlocks.com
[SIZE=+2]Hard-SPL Release Time!!!! [/SIZE]
[SIZE=+2]NOTE: This is NOT a SIM unlocker - it also doesn't unlock Security for other radios. if you need that, GO HERE[/SIZE]
[SIZE=+2]NOW UPDATED -> if you already installed HardSPL, you will not need this update. but if you are going to HardSPL only now, it applies to you (package will lead you to update link anyway).[/SIZE]
Preface: okay, it was released only this weekend! but trust me the wait was worth it as it works really great and smooth now!
Licensing information: it's like with previous Hard-SPL unlockers - every user gets one free use of the Hard-SPL, further use is subject to paying a small amount per device.
however, if you are a private user, you can have other uses free on request if needed, such as using it on a replacement device.
the license is valid forever and all this works as transparently as possible, so for normal users nothing is noticable; while businesses who need to unlock more devices than that, can use the link inside the program to send payment or contact cmonex or Olipro if you want to discuss bulk unlocking.
contact info is: via support link at our site
IMPORTANT: please do not use this contact info for asking help for problems unrelated to licensing unless you are a paying customer. other messages will not be answered - instead you can use this thread to post about your issues!!!
Preparations:
0) this package is for Rhodium CDMA-GSM worldphone version only (CDMA Touch Pro 2, not the original Touch Pro) devices. only RHOD400, RHOD500 modelids are accepted. this Hard-SPL supports WM6.5.
1) if you have Vista / Windows 7, WMDC update to 6.1 (or whatever is latest) is recommended.
Instructions: read this if unsure how to install Hard-SPL... if you are an experienced user then you'll probably not need to read most of this but if you are unsure or run into an issue, then you should read the following!
Steps:
1) download newest RhodiumW Hard-SPL package and extract this to an empty folder.
2) you must Have Phone Synced with PC in Windows Mobile!!! the device needs to be connected to Activesync or WMDC via USB cable. and it must not be in Flight/Airplane mode (i.e. the phone part should be on).
3) internet access is required as the program checks online for updates and for the license.
4) run Rhodium-HardSPL.exe on your PC, make sure it's launched from a local drive (not through network drive, etc.). running it on XP requires Admin logon, and Vista/Windows 7 will automatically prompt to allow it to run in Admin mode, so allow it please.
important: if you get an antivirus warning, please ignore it, it contains no harmful code (just used a packer to compress it). if you encounter DEP errors, then add it to the exception list in DEP settings.
5) follow steps as prompted in the Hard-SPL program. if this is the first run of Hard-SPL on a device after hard reset, you must select Automatic flash mode (the first button in Welcome screen).
notes: you should usually go for Automatic flash mode; the Manual flash option is only to be used as noted below - any other errors triggered while running in Autoflash mode will have to be fixed as instructed in the error message.
6) it will ask you to wait while it prepares for the flashing, press OK.
7) now it should go through without any error messages, if one does pop up, then please follow the instructions included in the error text. if no specific instruction is shown, then ask for help in the forums, but this should not ever occur (as this means a really fatal error occurred).
at this point the device did hopefully went to a black screen. this is the SSPL version, which is temporary. then RUU (Rom Update Utility) will instantly launch.
9) some notes: when RUU says it will perform a hard reset and cause data loss, do not worry, it is not going to do this. also when it says the flash will take 10 minutes, ignore that, it will only take a minute or so.
10) SPL flashes, device automatically reboots, job done.
11) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.00.OliNex, which is the current Hard-SPL version.
More Notes:
NOTE 1: you will not see the SPL version during normal boot, that is the OS version, not SPL!
to enter SPL to check version, you need the following key combination: Power Button + Volume Down + Reset Button. means, do a soft reset while holding the "volume down" key and power key on the side of the device. hold these keys until you see a special tricolour screen which is the bootloader mode.
NOTE 2: this is unsigned Hard-SPL. no limitations on flashing ROMs (except of course some Radio roms). also, this has overwrite protection against HTC RUU's overwriting HSPL with a stock one, so if someone needs to revert to stock SPL for warranty reasons, a stock SPL downgrade package is posted on our site. use this relocker *only* if you need to return the phone for warranty, and only use it as last step - after reflashing stock OS and radio. see steps in the next post about how to reflash stock SPL.
NOTE 3: anyone having USB connection problems with the device after it already entered SSPL mode, please copy SSPL-Manual-Rhodium.exe from SSPL-Manual-RhodiumW.zip (available on our site), copy it to the device and run it. then once the screen has gone black, run the Hard-SPL package on the PC and you must select Manual flash option. *important*: make sure that the USB cable is plugged in and device is synced to Windows Mobile even if doing manual method.
NOTE 4: do not use this RUU for anything other than SPL flashing (i.e. hardspl or stock spl restore)!!! nothing other than SPL's made by Olinex team will flash to make SSPL more secure. if you want to flash some other rom, then use shipped RUU or a customRUU if you need to flash cooked ROMs.
NOTE 5: supported OS versions: both 32-bit and 64-bit XP, Vista, Windows 7RC and later. Windows 2000 was untested, and pre-RC win7 (lower than build 7100) is explicitly not supported. also, the program may be unstable or not work on Virtual systems, so it's recommended to try outside Virtual OS software.
Troubleshooting: and Step by Step on reflashing stock SPL: are in next post below!
Credits:
first, "OliNex" is a team which means: cmonex + Olipro
Olipro -> concept of EXE program that runs on the PC, Hard-SPL concept, server-side license code and maintaining the licenses.
cmonex -> HSPL package on PC, SSPL loader for windows mobile and SSPL binary. Hard-SPL binary. (SSPL loader: partially based on haret and old pof&Olipro jumpspl code),
[SIZE=+3]Donations are always appreciated, the Hard-SPL program will provide you with a link at the end of the process to make it easier. any little helps!!! Thank you![/SIZE]
and now enjoy!
-continued from first post-
Manual SSPL download: (added soon)
Troubleshooting:
firstly:
- read the instructions above.
- read the instructions above.
- read the instructions above.
nothing happens on the device, does not enter black screen mode:
- anyone having problems with the device crashing instead of entering SSPL, make sure you've used Automatic flash mode before to put the device in SSPL (if you hard-reset your device, you have to repeat Automatic flash mode at least once).
- please make sure you watch the device screen if it asks about running files (it probably won't, I made sure of that, but just in case, check, for example it can warn about model incompatibility).
- also you can try unticking advanced usb/network functionality in settings on the device. exact location of this will probably be: start menu / settings / connections / usbtopc applet.
general usb connection error problems:
- if you get connection error in RUU after the device goes to black SSPL screen: make sure device was still synced via USB to the PC at the point of it entering SSPL (the black screen) and do not try replugging please, that will probably just crash SSPL.
- it will take a few seconds for the RUU to detect the device, but do not worry, as soon as the USB connection is established in SSPL, RUU will see device. if not (happens very rarely), wait for RUU to time out (or wait a few minutes). then remove back cover, reset, it will boot OS again, then you can retry unlocking process.
- anyone having problems with the device entering SSPL without functional USB port ("ERROR 260 CONNECTION" RUU error), you can get SSPL-Manual-Rhodium.exe from attachment in this post, copy it to the *device* itself and run it. then once the screen is showing black, run the Hard-SPL package on the PC and select Manual flash option. please do not use Manual flash option for any other purposes
- try a different USB port
- try different USB cable
- do not touch USB cable during the process especially if it is already a bit dodgy
- also do not use USB hub
- you can also try rebooting your PC
- and you can try using another PC.
- another reason for USB connection error: if your PC takes too long to load the drivers (if your device is in bootloader for the first time it needs to do that), then if RUU times out, but device is still in black screen, just leave it there and re-run the Hard-SPL package when driver installation finishes - you must use Manual Flash option in such a case. I recommend to wait for Windows to take its time searching for the USB drivers, then click Next in RUU only when they are installed.
- finally, you can try disabling antivirus or firewall programs on the PC.
ModelID checking: if SSPL loader says it's for a different model or device, please make sure you are using the correct HardSPL package. currently this SSPL accepts only RHOD400, RHOD500 modelids i.e. the CDMA-GSM worldphone version, but if we get notified of another compatible RhodiumW version, we will instantly modify it to allow those models. check modelid by entering SPL tricolour screen manually and note what it says (RHOD400, RHOD500, or something else). note: RHOD1xx, 2xx, 3xx are not going to be compatible at all!
other issues:
- if device reports that Enterbootloader.exe fails to run (says missing component or corrupt signature or similar), try a hard reset.
- if device reboots instead of going to SSPL screen (black), which is very unlikely to happen, then contact us by PM to cmonex. do not PM OliNex user, that is not monitored frequently (and PM's to it are disabled now anyway).
- if none of the above help, read thread for further suggestions, if still nothing, make a post in thread describing all details about the exact situation.
how to reflash Stock/Shipped SPL: - STEP BY STEP - FOR WARRANTY REASONS ONLY!
0. please make sure you already flashed stock ROM and radio, because stock SPL flash is *always* the last step before sending the device in.
1. download the Relocker by clicking here, extract the zip and run the EXE on your PC
2. if you wish to replace RUU_Signed.NBH that got extracted, feel free to do so, but not necessary (this Hard-SPL will only allow overwrite with a SPL made by us). the included one is the 0.63.0000 stock SPL. 3. flash
4. verify if it flashed by checking version in tricolour screen, it should say 0.63.0000, not 1.00.OliNex.
About UPDATES:
-new release coming soon, fixes a specific problem for a small group of people-
-more troubleshooting tips soon-
Consider yourself... sticky
Thank you Olinex. Great WORK
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
buggs1a said:
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
Click to expand...
Click to collapse
In a nutshell, this basically will allow you to flash custom made roms and other assorted customizations.
Hey, thank you.
Does using this and then not putting a custom rom on it right away do anything bad? Like waiting for a 6.5.1 rom or something. Sorry if this isn't the right place. Forgive me please.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
You can wait as long as you want to flash another rom, custom or carrier. So no worries in holding off.
Thanks so much for answering.
Here's something.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
I just tried. I don't get it.
My mcafee doesn't have a trust app add feature that i can see so i turned off real time scanning to extract the file and then run it. Then the hard spl crashes when i try to run it. I hit auto flash and immediately it crashes.
What specific error message(s) are you getting?
Nothing specific. It just crashes and the windows app crash pops up. That's all that I can remember. Should I try again and look for something specific?
Also I would like to say that I connected the phone to my pc via usb cable and that's it. On phone opened the disk mode or active sync selection but I didn't touch anything in time then it disappeared. The phone showed up as a hard drive in explorer. I didn't do anything else when trying to run the hard-spl exe. Should I have?
Thanks a million.
You need to make sure you're connected to your computer and sync up with ActiveSync. Once that's all connected properly, then you can run hspl.
but how do i do that? i noticed just now i reconnected phone and active sync was selected on the phone, but nothing comes up on windows vista except the auto run and it says synch with media player or open to view files or do nothing.
Oh, Vista. Right. You'll need to use Windows Mobile Device Center then. Install that, reboot, then sync up with that (it's ActiveSync's replacment for Vista and Windows 7). Then you should be able to run hspl fine.
That you very much Oli, and to all the people who worked so hard on this! I just put it on my Verizon Touch Pro 2 and it went like a snap, but what software from you doesn't A nice donation is coming yer way me matey!
thanks. that did it.
i got to the part where it said make sure the battery has 50% or more. i said cancel and now my phone is off and won't come on. I disconnected usb and tried to turn it on and nothing happens. reconnected phone and tried to do this again and it told me i need to active synch again. but i can't turn on phone right now. I don't know what to do now.
Have you tried taking out the battery of the phone, reinserting it and turning it back on?
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
buggs1a said:
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
Click to expand...
Click to collapse
Glad you got it figured out. Have fun finding a good rom that suits you.
edit: since we don't really have much of a CDMA TP2 selection just yet, I'd recommend checking here. He makes a great ROM. Just be sure not to discuss ROMs in this thread.
I posted this at PPCGeeks also, but here is a problem I am having while trying to unlock in Windows 7 x64 using WMDC.
1. Ran the .exe
2. Screen pops up "Preparing to flash, press ok to wait. I press ok.
3. The screen goes black (like it's supposed to), Active Sync DISCONNECTS, and a box pops up: "Welcome to the ROM update utility...". I check the box "I understand the caution..." and click next.
4. The next box pops up "Follow the instructions..." and I check the box "I completed the steps..."
5. A box pops up: "Verifying the information on your PDA phone...please wait..."
6. About 30 seconds go by, and an error box pops up: Error [260]: Connection...
7. The screen remains black and the phone non-functional. I have to soft-reset the device at this point.
When I soft-reset in #7 above, the computer dink-donks like when you disconnect the UBS cable, so there's still some sort of connection the PC is recognizing. I tried a second time after installing the enablerapinew.cab (using auto mode) and got the exact same errors.
Any thoughts?
hi , AS ABOVE.
i've tried to read all the possible solution and tried it out already
change the host file , try changing the regedit method , tried using device manager to troubleshoot the device driver.
it just cant work. im doing the correct steps . i even flash wp7 again to double confirm my steps.
i have my key already , im just lacking this step to proceed further.
help ? :/
HELP ??
The instructions you can find here are all pretty clear and they work.
I went according to this one:
1. Install WP7 sdk Windows Phone Developer Tools;
2. Install zune;
3. Make partneship with zune and phone;
4. Attach the ChevronWP7.cer(you found in the toolkit) to your email and send the email to your email itself (On PC);
5. Login to your email account (On Phone), Open the email, Select attachment and install the cert;
6. Connect your phone to pc and make sure zune is running in background;
7. Run the unlocker (ChevronWP7.exe) and click unlock button(Make sure your phone date is set correctly)
(you need to close skype and disable network adapter.. hamachi.. wireless.. Dropbox.. etc)
6. Install toms .xap installer;
7. Deploy Connection Setup.xap, Touch Xplorer.xap and XBMODDeployer.xap (Install it on the phone and run XBMODDeployer.xap);
8. Copy the .provxml from the ringtons folder to the windows folder (on the phone using touch explorer app);
9. Run connection setup to install the .provxml;1. Install WP7 sdk Windows Phone Developer Tools;
2. Install zune;
3. Make partneship with zune and phone;
4. Attach the ChevronWP7.cer(you found in the toolkit) to your email and send the email to your email itself (On PC);
5. Login to your email account (On Phone), Open the email, Select attachment and install the cert;
6. Connect your phone to pc and make sure zune is running in background;
7. Run the unlocker (ChevronWP7.exe) and click unlock button(Make sure your phone date is set correctly)
(you need to close skype and disable network adapter.. hamachi.. wireless.. Dropbox.. etc)
6. Install toms .xap installer;
7. Deploy Connection Setup.xap, Touch Xplorer.xap and XBMODDeployer.xap (Install it on the phone and run XBMODDeployer.xap);
8. Copy the .provxml from the ringtons folder to the windows folder (on the phone using touch explorer app);
9. Run connection setup to install the .provxml;
You are probably just missing a step
you must be doing something wrong ..cause as i just stated above all the tool and unlocker still works as it did 3 months ago...check some of tutorials in the forum...
http://forum.xda-developers.com/showthread.php?t=916497
hi there , it still doesn't work.
install
1. Install WP7 sdk Windows Phone Developer Tools;
just installing the software only right ?
lionhart1001987 said:
hi there , it still doesn't work.
install
1. Install WP7 sdk Windows Phone Developer Tools;
just installing the software only right ?
Click to expand...
Click to collapse
hi , i connected my phone using wpconnect , im still having same problem
Check your hosts file.
If it contains following entry, Chevron will not work:
127.0.0.1 developerservices.windowsphone.com
I cant remember where I read this but it helped.After completing the above instructions,Open task manager(Ctrl ,Alt &del).Go to processes ,select zune launcher and click on end process.reboot pc ,connect phone , wait for it to sync wit zune ,if it doesnt ,run zune then run chevron and you are done.I did this for 3 phones and it worked.hope this helps.good luck.
another confirmation that the unlocker still works for me without any problems at all...i dont nor havent deleted any host files or changed any setting at all within the machine. I have had one or two problems with it not working, the first problem i ever had when i first started using the unlocker was the registry key not being edited correctly... and for the second time it didnt work, all i did was unplug device and let re sync...tick, tick BOOM unlocked!! Besides those couple times it has always worked for me...Bought a new machine today and installed tools, then zune software and created account " naming phone " and installed chevron, opened and unlocked....if you have sdk tools installed and have the unlocker installed, with zune software completely set up and phone communicating with zune, not as guest...and you will change the relationship from guest to " whatever you name your phone " during setup... haven a complete and main relationship with phone " not guest " is one of the most important parts with zune!!! The other most important part is making sure the registry is edited and should look like this...
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsPhone\ProxyPorts]
“DeviceReg”=dword:000069C5
the window phone developer tools will edit reg for you...i have learned that if you relock the phone it sometime can takes a little while for things to click and be able to unlock again!!
So there is nothing wrong with any of the tools or unlocker, so if your having problems tripple check your zune settings to accomplish a non guest relationship, and check your reg. edit.....most problems i have seen and heard about are ppl and their zune!
jasontac said:
another confirmation that the unlocker still works for me without any problems at all...i dont nor havent deleted any host files or changed any setting at all within the machine. I have had one or two problems with it not working, the first problem i ever had when i first started using the unlocker was the registry key not being edited correctly... and for the second time it didnt work, all i did was unplug device and let re sync...tick, tick BOOM unlocked!! Besides those couple times it has always worked for me...Bought a new machine today and installed tools, then zune software and created account " naming phone " and installed chevron, opened and unlocked....if you have sdk tools installed and have the unlocker installed, with zune software completely set up and phone communicating with zune, not as guest...and you will change the relationship from guest to " whatever you name your phone " during setup... haven a complete and main relationship with phone " not guest " is one of the most important parts with zune!!! The other most important part is making sure the registry is edited and should look like this...
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsPhone\ProxyPorts]
“DeviceReg”=dword:000069C5
the window phone developer tools will edit reg for you...i have learned that if you relock the phone it sometime can takes a little while for things to click and be able to unlock again!!
So there is nothing wrong with any of the tools or unlocker, so if your having problems tripple check your zune settings to accomplish a non guest relationship, and check your reg. edit.....most problems i have seen and heard about are ppl and their zune!
Click to expand...
Click to collapse
hi , im sure ive done all the steps above .
like i mention , im not those ask before looking through thread.
yes it was not guest r/s with phone - zune .
i sync first before doing it and the r/s was not in guest.
regedit.exe was use to change the registry key before all. any other alternative ?
what kind of machine and os are you using?
jasontac said:
what kind of machine and os are you using?
Click to expand...
Click to collapse
window vista 32bit enterprise and home edition
jasontac said:
another confirmation that the unlocker still works for me without any problems at all...i dont nor havent deleted any host files or changed any setting at all within the machine. I have had one or two problems with it not working, the first problem i ever had when i first started using the unlocker was the registry key not being edited correctly... and for the second time it didnt work, all i did was unplug device and let re sync...tick, tick BOOM unlocked!! Besides those couple times it has always worked for me...Bought a new machine today and installed tools, then zune software and created account " naming phone " and installed chevron, opened and unlocked....if you have sdk tools installed and have the unlocker installed, with zune software completely set up and phone communicating with zune, not as guest...and you will change the relationship from guest to " whatever you name your phone " during setup... haven a complete and main relationship with phone " not guest " is one of the most important parts with zune!!! The other most important part is making sure the registry is edited and should look like this...
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsPhone\ProxyPorts]
“DeviceReg”=dword:000069C5
the window phone developer tools will edit reg for you...i have learned that if you relock the phone it sometime can takes a little while for things to click and be able to unlock again!!
So there is nothing wrong with any of the tools or unlocker, so if your having problems tripple check your zune settings to accomplish a non guest relationship, and check your reg. edit.....most problems i have seen and heard about are ppl and their zune!
Click to expand...
Click to collapse
how do you ensure that it is not GUEST?
i seem to be unable to get it to sync with ZUNE
Wow... you can come and work on our helpdesk any time, they log calls about as badly as you explain a problem lol.
You've said it's "not working". Why isn't it working? Where are you getting up to? Are you getting an error message?
Have you deleted all entries of Developerservices... from your host file?
make sure you have corrected date and time
and if possible use SIM Card with "big operator" in your country (well known operator)
sorry for bad english, using google translate
Host File?
pkoper said:
Check your hosts file.
If it contains following entry, Chevron will not work:
127.0.0.1 developerservices.windowsphone.com
Click to expand...
Click to collapse
What Do I Do In This Case?
I gave up with it am not thick had my previous Android phone with root and was loading new roms on daily but just won't work with this get the same thing over and over,
Sorry I'm having trouble communicating etc etc.
Please make sure its connected using USB ( yes it is)
Please start the Zune application ( its open and running)
No matter what I try resetting phone it would never work so thought bugger it what a load of crap, currently on the look out for a nice Android phone had my fill of this.
had sam problem, went and deleted
xx.xx.xx.xx developerservices.windowsphone.com
from host file, and now it works aging.
pkoper said:
Check your hosts file.
If it contains following entry, Chevron will not work:
127.0.0.1 developerservices.windowsphone.com
Click to expand...
Click to collapse
it does on mine... w7 ultimate... dont have to delete anything
Try to reset your phone. It worked for me.