Develop Bugs

Error: 114, a USB Hub, and the magic #3.

Well, tonight I flashed my XDA Pro with the new O2 ROM and I was given the dreaded ERROR 114. I followed the instructions and tried to do a reset and nothing at all happened. I could see NOTHING on the screen. So, I continued and retried the flash.
Flash #2 started with no radio info and ended with the same Error 114.
I decided to change some wiring as I was using a USB 2.0 hub with 6 other devices plugged into it. I unplugged my XDA cable and inserted it directly into the motherboard's USB port. Begin flash #3.
Flash #3 was successful. Is it that it just takes #3 flashes as so many posts seem to indicate? Or does the flash not work when going through a USB hub?
In any case, if you have the "ERROR 114" problem, remove any USB hubs your phone might be connected to and don't give up until after your 3rd flash.

On the old MDA II it was always said not to use any usb hubs or the upgrade won't work.
So you can figure out yourself now that you don't need 3 flashes before it works.

Unfortunately, I never had the MDA II. So I had to learn the hard way I guess! 8-(

Can't get USB connection to upgrade again

Hi all,
I have this particularily annoying problem that effects my ability to upgrade the rom files on my universal sometimes.
When I put my device into boot mode I don't see USB v1 or even Serial v1, what I get is Serial v2.01
Sometimes when I then connect the USB cable into the universal this changes to USB v2.01 and windows recognises the device and I can perform the rom upgrade. Most of the time however, it stays at Serial v2.01 and windows complains about 'USB Device Not Unrecognized'.
I have tried 2 different USB cables with the same outcome.
Normally after trying s few dozen times I eventually get windows to recognise the universal and perform the upgrade but I have been stuck like this for 3 days now and am getting close to my breaking point which will could shortly result in a broken universal.
Please help.

i cant quite remember the ins and outs but i have faced this problem as well
firstly ensure your connected directly to the computer and not via a hub,
try to do the upgrade if/when you get the message remove the device from the cable and do a soft reset
try the upgrade again and it should be successful this time .
i have had lots of trouble myself with this and i have found a soft reset always gets me there in the end.
goodluck !

I have just retried the upgrade and the display keep changing from USB to Serial about every 10 seconds.
I also noticed that the mouse kept freezing on the screen for a few seconds whilst this was happening. I tried using my other USB cable and the same thing was happening.
Does anyone else have v2.01 displayed on their screen like me?

Update: I stupidly ran Ivan's AKU3.2 upgrade utility whilst the universal was activesynced to my desktop (not in bootloader mode) and now this has executed the EnterBL.exe program which traps you in the booloader unless you upgrade a rom (or use mtty to issue the correct command to escape).
Unfortunately I can't excape via either of these methods as I still can't obtain a USB connection.
I have even tried a different PC but am still stuck.
Maybe both of my USB cables are knackered, so I will obtain another one and try that. If that fails it looks like Orange will be recieving a little parcel from me...

I have now also tried a 3rd USB cable with the same result.

I have a similar problem, I'm stuck in bootloader mode.
I have version 0.60 and if I put a USB in it keeps on saying serial and my computer says he doesn't recognise the device.
I've tried it on 2 different computers as on my new one apparantely all my usb ports are part of a hub. (they come up as all, inluding the ones in my moniter, being part of an usb root hub) But no succes on my other computer either.
I'm thinking that my only option is to do it via a memory card? Can anyone tell me how I'd go about that as I have no clue :shock:
Thanks!
Tim

Success!
I have been plugging in and unplugging my phone all day (with it still stuck in boot mode) and eventually it was recongised by my PC - I then upgraded the radio stack & ce rom and I am up and running again (I know that I could have used buzz's utility but I wanted to upgrade anyway).
The only thing that I did slightly differently this time was that I actually removed the battery from the univeral for a while and then plugged it back in before trying the USB connection. I did try this once of twice before without success though so can't really draw any conclusions apart from I don't know what is going on.

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"

Cannot upgrade ROM: Could Activesync 4.5 Beta 2 be responsible?

I am trying to upgrade from Ivan's ROM beta 13 to beta 15... Using the MAupgrade utility... however, everytime the utility resets the device to start the ROM update i get "USB device not recognised" from my PC and the update fails to start... eventually i get a connection error message.
This used to work just fine... however, recently i installed Activesync 4.5 Beta 2. Could this be causing the problem...? otherwise i'm not sure what else might be causing this...
I have also tried running the tool in bootloader mode with and without "USB connections allowed" ticked in Activesync but with no success...
Can anyone help me please?

Trying to clear registry before upgrading ?
Have you tried to clear registry before upgrading?

Hi Kassel, thanks for your response.
I have done a hard reset prior to upgrading... wouldn't that clear the registry?
If not please let me know what else i can do that might help.

Also, it seems very strange that i can't seem to do the ROM upgrade from bootloader mode.
I think i might be having a problem with GetDeviceData as it seems to stay in the "checking the information on your device... please wait" for forever when i try to upgrade from bootloader mode.
If it does come up, then the panel which says which version is on my device and which version it will be replaced by is blank?
This is not the case if i try to do it through activesync (with the device set up as guest).
What might get in the way of reading the device data? I made sure it went from serial to USB when i plugged the USB cable into the device and i have tried different cables...
My bootloader appears to be V1.00
hmmm... any thoughts?

Same here...
I also have the same problem.
I installed ActiveSync 4.2
Alse after having installed AS, the MTTY program doesn't see the USB port anymore, just some COM ports.

Same to me too
I have ActiveSync 4.5 bata at work (Which couln't upgrade ROM)
while my notebook with ActiveSync 4.2 work fine

Wow, it's great to hear that people are having the same problem...
Is it possible to back track with Activesync? Is 4.1 still available?
If not, i think i still have an older version running at home (i hope!)...
Is this definitely the issue then?

l_pete_l said:
I have ActiveSync 4.5 bata at work (Which couln't upgrade ROM)
while my notebook with ActiveSync 4.2 work fine
Click to expand...
Click to collapse
I have ActiveSync 4.5 and upgrading my Jasjar was successfully done with the ROM Version: (1.90.96 / 1.13.00 / 42.47.P8)

Sorry for not knowing, but is that one of the AKU3.2 ROMs. Not sure if it should make a difference, but just curious.
Also, did you need to use the MAupgrade Utility?
Cheers,

What happens with the USB drivers after installing ActiveSync 4.2
The strange thing is, that I tried connecting my MDA Pro to a PC without ActiveSync on board.
USB ports were visible using MTTY
I installed ActiveSync 4.2 and only COM ports are visible in MTTY, the USB port has vanished.
Can this be caused by the USB driver that comes with the ActiveSync install ?
If I put my device in bootloader mode, it sais USB on the PDA screen, but the utility for the ROM upgrade doesn't see the PDA and comes up with a device not connected error.
I would really like to try out one of the new ROM's by Ivan or JwRight, but am unable to, because of these USB problems.
So please someone help !!!!!!!!

I have the same problem... if i put the device into bootloader mode, "serial" changes to "USB" but the PC comes up with "device not recognized"...

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.