[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I didn't want to start a new thread for this, but after consideration I determined that after searching for 3 days and not finding anything dealing directly with this issue that it might be my best bet :confused:

First off I want to say that although the issues I will describe seem to have happened after using JockyW's tools, I don't wish to make his tools the culprit. JockyW has contributed in abundance to the community here and I appreciate it all. I have mentioned part of this issue previously and JockyW had definitively stated that this could not be caused by his tools (assuming instuctions were followed). I do not want to second guess JockyW, however I believe that my experience and my mental capacity is sufficient to say that I followed all instructions 100% and these issues still appeared. I will not pass any judgement on that fact, other than to state it.

When I received my first Tilt a few months ago I CID unlocked it with OliPro's HardSPL and used JockyW's tool to Security Unlock it. When I sent that one back because of an issue with the back cover I performed the same procedures on my second Tilt. Both of these went flawlessly, not a single problem. Since then I have flashed dozens of ROMs and SPLs without issue. This shows that both the tools and my ability to properly use them have been successful for me in the past.

Earlier this week I attempted to use JockyW's Security Unlocker tool and his kaiser-relocker.exe to Security Re-lock my phone. I was doing this as an experiment to show that a phone did not need to be Security Unlocked in order to flash any HardSPL. The experiment proved to be correct, however after I re-locked the device

I found that I could not get into USB mode in the bootloader, and that it was stuck on SERIAL

. I tried all of the following:

1) Remove all USB devices from my XP machine's device manager

2) Reboot phone and PC

3) Remove Battery, SIM and SD cards

4) Reinstall ActiveSync

5) Try another PC

In all instances my phone was always recognized as an "Unknown Device" in Device Manager and would not go from SERIAL to USB mode.

However, when using Jump-SPL the phone would go into USB, so it isn't a problem with the physical hardware in the device. I further messed around with the phone, and did some things that I know I shouldn't have done and this caused the phone to eventually brick. This was not surprising and no one's fault but my own since I was moving into unchartered territory and taking (unnecessary) risks.

The next day my warranty replacement arrived and the first thing I did was load JockyW's original HardSPL 1.1 on it. Had no problems. I then went to use the Security Unlocker tool. The tool ran fine and stated that my device was successfully unlocked, however upon my next boot into the bootloader the device did not show "Security Unlocked" at the top of the screen. In addition I now seemed to have the "SERIAL" issue again on the phone. I performed all the same tests to no avail. If I use Jump-SPL or flash JockyW's 3.28/3.29 HardSPL with "force usb" mode then my USB works. However when I flash back to a Stock SPL, or to the original JockyW or OliPro I cannot get my device into USB mode.

GSLEON3 assisted me in using AT Commander to Security Unlock the phone even though I could not connect via USB. So now my phone is successfully unlocked, but still having the USB problems.

This is not a major issue, since I can still load 3.29 force USB and flash ROMs. I can also load Jump-SPL and flash a different SPL. However I am unable to use some tools that require the original HardSPLs and USB connectivity.

At this point, my questions are as follows:

1) Is there a way to force the device into USB mode when using the original HardSPLs (stock or "hacked")?

2) Does Security Unlocking a phone always mean that it is SIM unlocked as well? Since I am unable to connect via USB I cannot use the available SIM unlocker tools. I would like the phone to be SIM unlocked so I either need to find an answer to #1 or else find another way (possibly with AT Commander) to check and/or SIM unlock the device.

Before the above incidents I used all the available tools with little regard for any danger they could do. I felt that if i followed instructions then there really wasn't much danger I could do to the phone and coached others the same.

These experiences have now made me feel differently. I know that I followed all instructions perfectly, and I know that hundreds (if not thousands) of people have used these tools with no issues, as have I several times before. But some combination of these devices, procedures, and software have caused the issue.

Rather than investigate exactly why it happened, because that is already a proven reality (it did happen). I am hoping I can find some answers out to the above questions. This way if someone else experiences the issue we will have some solutions.

Thanks for any assistance you can provide on the matter.