Develop Bugs

Problem upgrading to the new special edition ROM

hello,
i recently upgraded my ROM to T-mobile diamond release v1.1
I would like to upgrade to your special edition ROM since some things on the diamond release are not that good...
The problem is that anytime I try to install it the screen says "cannot find pocket pc, make sure your usb cable is connected" or something... it must be connected because active sync starts to run when i enter my pocket pc in his cradle, it also syncronises. I tried to reinstall te usb drivers, rebooted my pc, soft and hard reseted my pocket pc but I still get the same message... could somebody please explain to me what I'm doing wrong here?
thank you
MRJ

the SE rom is not new it's likely that you have one of the new roms which can only be downgraded by using the sd flash way insted of the usb flash way
also your icon say that you have a xda2 and the SE rom is only for xda1

UNIVERSAL in Boatloader mode not recognized by PC-USB

I tried to upgrade my rom but the process crashed. The utility mtty doesn't work because when I connect the universal, boatloader mode by the cable, to the pc, it says "USB not recognized" (sometimes when I connect the computer is frozen till I disconnect the cable of the universal)
Please, I tried to have some solutions in the forum but all the posts indicates is needed previously the usb connection.
Do you know if should be possible to run the flash of the rom in other way, for example using a serial cable connected into the miniusb of the universal, because the boatloader screen says "Serie, v.1.01"
I apprecite what you can say please, I'm really in a hole.

Try this...
Try taking out the battery for a few minutes (10-30mins) and reboot your PC then repeat upgrade process. Hope that helps. Good luck!!!

I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
The only thing I found that worked was to try a different PC, then it was fine...

sl9 said:
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
The only thing I found that worked was to try a different PC, then it was fine...
Click to expand...
Click to collapse
In my case it still happening in other computers. Conclussion: some piece of the software in the universal has been lost. The screen shows "Serial" that means on some way that is opened to comunication but not USB.
My questions are:
- should be possible to put some starting software in SD and do the universal boot on it.
- do you know how to connect to the computer COM! port from the usb miniport of the Universal.
I appreciate, I was not planning to replace now the Universal...

beginner said:
sl9 said:
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
Now works.... I still thinking windows is so stupid software made for distroy our mind ....
Solved after install drivers for a converter usb -rs232 ( I was looking for the way to connect from rs232 the universal)
I'm happy again and I promise don't try to change rom again (at least for a while)
If some person is interested in what brand of software/hardware I installed, send me a mail...
Thanks hearing me ...
Click to expand...
Click to collapse
Click to expand...
Click to collapse

i have the same problem with my friend's uni
does it mean that you don't have to own any adapter, just have to install drivers for USB to RS232 adapter
if yes, where to find it?
thanx
respectfully
ZeD

zedino said:
i have the same problem with my friend's uni
does it mean that you don't have to own any adapter, just have to install drivers for USB to RS232 adapter
if yes, where to find it?
thanx
respectfully
ZeD
Click to expand...
Click to collapse
I want to say that is running after doing some things and obviously some of it solved my problems. I made:
- unistall last version of activesync and go back to version 4.0
- delete all the applications using ports usb.
due the connection still not running (windows message: device not recognized) and because in the screen of universal I saw: "COMM1" I tried to connect from computer port rs232. By that I purchased some special cable, name: hama brand, rs232 serial, 9 pin - usb.
As you can imagine all the steps I followed were followed by the typical restart of windows. In this sense is important to say that the universal, after connect, need to do a soft reset each time (again windows....)
Other comment is that I unmark the option to connect by usb in activesync and mark the connection by com1.
and after all was done, connecting by usb the unniversal, kill wcescomm, windows said "NEw usb device, sync device". I started mtty and now appears the USB option, great! same time the screen in universal changed from comm1 to usb, more great....
and that's all.

does it mean you solve your problem using special USB 2 RS232 connector?
ZeD
PS: it was my first idea , but i still believe i can solve the problem using USB port

zedino said:
does it mean you solve your problem using special USB 2 RS232 connector?
ZeD
PS: it was my first idea , but i still believe i can solve the problem using USB port
Click to expand...
Click to collapse
I think my english wording was not fine. I mean I solved my problem after install the sofware -drivers- of the rs232 connector, but connecting to the universal by usb as on standard way I was syncronizing previous the crack with activesync.

OK, where to get this driver?
thanx

?????????? NOTHING ?????????????

zedino said:
OK, where to get this driver?
thanx
Click to expand...
Click to collapse
Try here.
http://www.hama.de/portal/type*3/action*1026/searchMode*1/q*039703

I have had the same problem several times now (search the forum for the thread).
I tried three different PC's/laptops and three different USB cables all with the same error as yourself.
Eventually I got a connection but the laborious process of trying - failing, restarting windows and soft resetting the phone, trying - failing........... until it finally worked. I did nothing differently the time that it worked but the strange thing is that it has worked every time since! Maybe the USB driver the phone has a bug in it that causes it to get 'stuck' in a mode where it will no longer correctly operate but once you have managed to 'kick' it into action it seems toi then carry on working.
It was also a ROM upgrade that caused my USB phone driver to stop functioning. Maybe the fact that the phone has a slightly diffferent software configuration after the upgrade but exactly the same hardware fingerprint causes the driver to fail.
Every time that I have had this problem it is after an upgrade but once I have gotten it to work once with the new ROM, it always continues to function - until the next upgrade.

shrubbery said:
I have had the same problem several times now (search the forum for the thread).
I tried three different PC's/laptops and three different USB cables all with the same error as yourself.
Eventually I got a connection but the laborious process of trying - failing, restarting windows and soft resetting the phone, trying - failing........... until it finally worked. I did nothing differently the time that it worked but the strange thing is that it has worked every time since! Maybe the USB driver the phone has a bug in it that causes it to get 'stuck' in a mode where it will no longer correctly operate but once you have managed to 'kick' it into action it seems toi then carry on working.
It was also a ROM upgrade that caused my USB phone driver to stop functioning. Maybe the fact that the phone has a slightly diffferent software configuration after the upgrade but exactly the same hardware fingerprint causes the driver to fail.
Every time that I have had this problem it is after an upgrade but once I have gotten it to work once with the new ROM, it always continues to function - until the next upgrade.
Click to expand...
Click to collapse
not works, probably is this device lost forever, i have restarted device and PC almost hundred times, still the same result, uni stuck in Bootloader screen top of page "Serial" bottom of page "v1.00"
nothing changed, even if i connect to USB port
if someone have some solution to this s*it pls let me know
thanx

i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck

mrijnvis said:
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
Click to expand...
Click to collapse
no, my problem persist, hundred times i tried to recover friends device using upgrade by original shipped ROM but the device is not recognized by system so there is allways connection error, so this kind of reliving this UNI is not usable
anyway, thanx for raply and suggestion
ZeD

mrijnvis said:
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
Click to expand...
Click to collapse
If you're stuck in bootloader mode only, visit www.buzzdev.netand look for ExitBootloader utility written by the great Buzz. Just follow his instructions or scroll thru' Universal's forum here and there for problems relating to "stuck in bootloader"
hope this helps

no device is not recognized by PC so any trying to use exitbl is not available, anyway this option was one of the first what i have tried
thanx anyway
ZeD

i had the same problem with the QTEK of my principal after I upgraded his ROMs.
(after the hard reset, the pocket remained in bootloader mode).
you can solve this problem in a very simple way:
you have to launch the bootloader installation (BL1.01_RUU_UNI_V.1.2.EXE) from the PC (still connected with the PPC through USB) while the PPC is in bootloader mode (on your display you see "USB > Serial 1.01" or something like that).
then you do a SOFT reset and the pocket boot normally.
very simple.
i hope to be helpful to someone.

zedino said:
no device is not recognized by PC so any trying to use exitbl is not available, anyway this option was one of the first what i have tried
thanx anyway
ZeD
Click to expand...
Click to collapse
I had some problem. After uninstall all usb applications in the pc and install the software for cable usb -rs 232, doing some softreset in the pda connected, it turned the screen message "Com" by "Usb"

Stucked to "Serial" bootloader mode

Hi all,
I was trying to upgrade my Qtek9000 with an official ROM Updater, but my device went immediately into the Serial bootloader mode and I've not been able to do nothing to run out from this mode...
I've tryied the solutions suggested in http://forum.xda-developers.com/showthread.php?t=290234 without any luck...
The problem is that neither Mtty nor the UNI_exitbootloader tool are able to connect to USB.
I'm using no usb hub, I'm running on a Dell Precision M90 notebook, I've disabled USB connection in Activesync (4.2.0) and also tryied with a pc without activesync installed.
Any idea?
Thanks
Paolo

Are you on XP or Vista, and what version of AS/WMDC do you have?

Hi,
I'm running Xp, ActveSync is 4.2.0, don't know what WMDC is sorry, can you please explain?

Don't worry about WMDC - it's only relevant if you have Vista.
Are you using the proper cable that came with the Universal? Some cables don't have all the pins wired. That (or a broken USB port) would explain why your Universal isn't going to USB mode when you plug in the USB cable. Have you looked carefully to see if it changes from saying "Serial" to "USB" at the top of the Bootloader screen when you plug in the cable?
If it does change to "USB", I would try upgrading to ActiveSync 4.5 - go to http://www.microsoft.com/windowsmobile/activesync/activesync45.mspx
Make sure you disable USB Connnections in the Connection settings before plugging in your Universal. Then try flashing the CE ROM again.
Good luck
BTW did you try doing a hard reset to get out of bootloader (both soft keys and then the reset button, then select 0).

Good advice, especially with upgrading to AS 4.5, it's a full release now on Microsoft Update site, and I have a feeling the WM6 ROMs may require it... Good luck with it, keep us posted.

Ok, thanks all!
This morning I connected the PDA to my office's PC with it's original cable and it instantly switched to USB mode...
So, I launched the upgrade and it's now in progress... let's hope!!!
It might really be a cable problem, yesterday night I tried with 2 different PC and a not original cable (I think it's my camera one...)
Thanks a lot, by now... I'll let you know own this story will end...

Ok, new ROM is up and running!
Thanks all!
Bye
Paolo

Good stuff.

error 260

ROM: Big Black ROM 1.3 from here.
Radio: 1.46.00.11
SO: Windows XPSP2
ActiveSync 4.5
I have this weird problem. I want to flash a new ROM, it doesn't matter which one.
When I ran ROMUpdateUtility, I click on next..next..and when is just about to flash and enter in bootloader mode, the connection with PC is lost, and it says in the bottom of the screen Serial, not USB.
Ok, so let's manually go on bootloader mode, and flash from there. Same error, it doesn't recognize the USB cable, it says Serial.
The ROMUpdateUtility gives error 260: Connection..check usb..
But it syncs through ActiveSync perfectly when I load WM, no errors received. I can copy in it, from it, with WM5 Storage or CardExport.
What to do?

What OS
upgrade said:
ROM: Big Black ROM 1.3 from here.
Radio: 1.46.00.11
SO: Windows XPSP2
ActiveSync 4.5
I have this weird problem. I want to flash a new ROM, it doesn't matter which one.
When I ran ROMUpdateUtility, I click on next..next..and when is just about to flash and enter in bootloader mode, the connection with PC is lost, and it says in the bottom of the screen Serial, not USB.
Ok, so let's manually go on bootloader mode, and flash from there. Same error, it doesn't recognize the USB cable, it says Serial.
The ROMUpdateUtility gives error 260: Connection..check usb..
But it syncs through ActiveSync perfectly when I load WM, no errors received. I can copy in it, from it, with WM5 Storage or CardExport.
What to do?
Click to expand...
Click to collapse
What operating system are you using?

Windowx XP SP2. I said in the first post.

Hello,
don't worry, happens the same to me and i repeat the procedure, click to updateROMutility and .....voilá !! Flash the ROM
Regards
Marco
upgrade said:
ROM: Big Black ROM 1.3 from here.
Radio: 1.46.00.11
SO: Windows XPSP2
ActiveSync 4.5
I have this weird problem. I want to flash a new ROM, it doesn't matter which one.
When I ran ROMUpdateUtility, I click on next..next..and when is just about to flash and enter in bootloader mode, the connection with PC is lost, and it says in the bottom of the screen Serial, not USB.
Ok, so let's manually go on bootloader mode, and flash from there. Same error, it doesn't recognize the USB cable, it says Serial.
The ROMUpdateUtility gives error 260: Connection..check usb..
But it syncs through ActiveSync perfectly when I load WM, no errors received. I can copy in it, from it, with WM5 Storage or CardExport.
What to do?
Click to expand...
Click to collapse

I wish it was that simple. I did that, same error, different ROM's and I try with olipro 1.20, which gave the same error.

Another suggestion
Did you try with a different machine? Make sure that your firewall is not stopping connection.

jmermel said:
Did you try with a different machine?
Click to expand...
Click to collapse
No, I will try tomorrow.
Make sure that your firewall is not stopping connection.
Click to expand...
Click to collapse
Nope, I tried that, too.
The orange led which shows charging, it turns off in exact moment when the phone enters bootloader mode. It's very weird, as I said before, probably a soft problem. I'm going to play a little bit with ActiveSync versions. I'll take any advice from you guys. , don't hesitate to do that.

Problem solved. It was a hardware issue.
I looked closely to the miniUSB port and I noticed that a pin was missing, it was only 4 of them! But at a closer look, the fifth pin from the miniUSB port (when you look at the port with the screen up, from left to right) was moved from the his channel above the other pins in the back. So, with a needle and a little patience, I bring him back to his channel.
It's interesting the role of this pin, among other things, probably. Is responsible with syncing the phone with USB port in bootloader mode.
Me, very happy now.

Cannot connect to PC after ROMupdate

I hard-SPLled my device and unpreded ROM Miri v3.0 on it. After the upgrade the device could not connect to my PC via ActiveSync or Mobile Center.
I tried with several PCs, laptops and many cables.
It should be 'soft'ware, since the problem started after ROM upgrade.
So, I figured it was because of the ROM, so downgraded to official 6.1 ROM, but connecting is still not possible. The official ROM included bootloader, radio and OS, btw.
Now I am stuck with a device that cannot connect to any PC! I always get a message of an unknown device that connects, later on followed by a message of an unknown USB device.
And yes, tried to remove the speed-up of ActiveSync. Also tried as USB storage, but I get the unknown USB device all the time...
Please help, I don't know what to try now!

Try a different USB cable. Might be a good idea to buy a brand new one. They tend to go corrupt easily.

Bright.Light said:
I hard-SPLled my device and unpreded ROM Miri v3.0 on it. After the upgrade the device could not connect to my PC via ActiveSync or Mobile Center.
I tried with several PCs, laptops and many cables.
It should be 'soft'ware, since the problem started after ROM upgrade.
So, I figured it was because of the ROM, so downgraded to official 6.1 ROM, but connecting is still not possible. The official ROM included bootloader, radio and OS, btw.
Now I am stuck with a device that cannot connect to any PC! I always get a message of an unknown device that connects, later on followed by a message of an unknown USB device.
And yes, tried to remove the speed-up of ActiveSync. Also tried as USB storage, but I get the unknown USB device all the time...
Please help, I don't know what to try now!
Click to expand...
Click to collapse
Have you tried using a differant usb port? I had to do that with a miri rom on my "old" Blackstone. I did have trouble with miri roms doing that on my Touch HD,for some strange reason.
You could also go to the threads in that forum and read what people have done to remedy that problem on the HD, as it should also work on our Tilt 2.
Later..............

Bright.Light said:
I hard-SPLled my device and unpreded ROM Miri v3.0 on it. After the upgrade the device could not connect to my PC via ActiveSync or Mobile Center.
I tried with several PCs, laptops and many cables.
It should be 'soft'ware, since the problem started after ROM upgrade.
So, I figured it was because of the ROM, so downgraded to official 6.1 ROM, but connecting is still not possible. The official ROM included bootloader, radio and OS, btw.
Now I am stuck with a device that cannot connect to any PC! I always get a message of an unknown device that connects, later on followed by a message of an unknown USB device.
And yes, tried to remove the speed-up of ActiveSync. Also tried as USB storage, but I get the unknown USB device all the time...
Please help, I don't know what to try now!
Click to expand...
Click to collapse
try rebooting your pc, also try a different usb port on your comptuer and then try another usb cable. i have read somewere that some computers do not put out enough voltage on the usb ports, so this said, after you try the previous suggestions grab your cable and try another computer, after you install activesynce of course .

Thanks for thinking with me!
I tried several PCs, so, yes, different USB ports.
Also tried several cables that proved to be ok with other devices, including one ExtUSB cable.
Of cause resetted PCs before connecting and first installing ActiveSync or Windows Mobile Center (depending on OS: WinXP or Vista)
When connecting to USB connections that worked before now sometimes the Touch tells me there is insufficient power... That's strange too! It would mean the device needs more than 500mA in some cases (because it's the only device connection to the USB) - but this is on more USB ports of different computers!
So I tried everything qua hardware... Don't know what to do now.

Bright.Light said:
Thanks for thinking with me!
So I tried everything qua hardware... Don't know what to do now.
Click to expand...
Click to collapse
Have you considered -- or tried -- flashing to a different ROM via the sd-card method? The method where you put the RHODIMG.nbh file in the root of your sd card (by removing card and using a card reader attached to PC), then put the TP2 in bootloader and it flashes the new ROM from the sd card...something like that?
I probably didn't describe this quite right -- I haven't done it myself -- but lots of people prefer this rom-flashing method. Find/check-out the procedure elsewhere on this forum.
If it works then maybe you'd get away from the problem-rom...if the rom is really the problem.