Computer fail to recognize the Universal via USB on bootloader mode? [Archive]

View Full Version : Computer fail to recognize the Universal via USB on bootloader mode?

cktlcmd

17th December 2006, 08:49 PM

As the title states: Why does some computer fail to recognize the Universal via USB on bootloader mode?

I recently reformatted my computer, which I usually do once a year. After installing all my apps back and running windows update on my computer, I installed active sync. Performed a normal reset on my computer, attached my Universal and active sync worked.

Here comes the problem: I decided to roll back to my old AKU 2 QTEK ROM. Of course, I know how to use the Ma_Upgrade No ID file. The problem is my computer now fails to recognize my Universal no matter what I do on bootloader mode. To make it worst, I am now stuck at the bootloader mode with my computer not recognizing it. Any suggestions as to why my computer failed to recognize my Universal?

cktlcmd

17th December 2006, 09:05 PM

OK, I was able to get the ROM upgrade going again, by removing my SIM Card and 4GB SD Card. I'll post back if I was able to revive my Universal.

So it seems that my computer failed to recognize my Universal because either the SIM Card or SD Card is causing the conflict.

davicito13

18th December 2006, 12:54 AM

I had the same problem.... I have two computers one with Win Vista (with the same problem) and another with XP sp1. This computer recognize my pda in boot loader, doesn't matter if still SD card and SIM inside....
Sorry for my english and I didn't tell you a solution...

FaCeOff

18th December 2006, 01:25 AM

Hi,

i had the same (very annoying) problems but i always was able to get the Universal back into Windows Mobile.
It was very strange because i started the ROM update and than e.g. it did not go in the Bootloader but back in Windows Mobile so i started it again and than it stucked in the Bl. Hardreset and putting the device again into Bl did not help and i was already very annoyed. I tried to plug in and out the USB-cable but it was always telling me SERIAL and not USB and Windows showed this fucking popup that one device is not recognized or something like that. I tried a trick to let the cable plugged in USB and than reset and it showed me USB but wheter MA_Upgrade (No ID of course) nor mtty were able to find the device. After several trys and resetting and resetting again i was able to bring it into USB but MA_Upgrade did not work.
The only way to bring back the device from the Bl is the method described in XDA-Wiki (http://wiki.xda-developers.com/index.php?pagename=Instructions%20for%20those%20st uck%20on%20Boot%20Screen)
The problem is that this method does work only half. I did the steps until the command "set 14 0" and started MA_Upgrade BUT it always told me that the device is not connected, it never worked. I was already frustrated so i did again the reset and what happend? It started back into Windows Mobile!

So what i think that after using the command set 14 0 AND running MA_Upgrade reactivated the start of Windows Mobile. I tried the steps very often because i tried to find a solution for the contacts between WM5 and AKU 3.2 or higher but the only way is to ActiveSync them. This really works and this is for sure the guaranteed way to get (at least my) the Universal back to Windows.
Btw for the people who are to lazy to use the search function:

The damn ROM upgrade does NOT work on Vista until now! Even not with the Windows Mobile Device Connection Center (or how it's called). I tried several steps on the RTM Vista but it never worked. Don't waste your time on it!

So far from my side, i hope these experience will help some people

cktlcmd

18th December 2006, 07:09 AM

I was so worried. Wheeeeew! Anyway back to normal again. I got it to work.

My observation is: My computer failed to recognize my Universal because I was using Active Sync Version 4.5 Beta 2 to update my Universal. The solution is to completely uninstall active sync using the windows remove program under control panel, and manually deleting the active sync folder from the hard drive. I then installed Active Sync Version 4.1 and all was well again.

So my next question to all the guys/gals who had problems with upgrading their device because the computer FAILED to recognize their Universal via USB is: ARE YOU USING THE BETA VERSION OF ACTIVE SYNC?

agisofttm

18th December 2006, 08:45 AM

cktlcmd

18th December 2006, 12:52 PM

Actually when you try to upgrade with SD card inserted - only then you will get this error - :) I spend so many hours of GOD prays for my Universal - and after that I just remove a SD card and everything is back to normal :)

What is the size of the SD Card you are using? Because when a 2 GB SD Card is inserted, it works just fine. But I experience the error with my 4 GB SD Card.

DuLanTus

7th January 2007, 04:36 PM

SpiriTwin

9th May 2007, 11:05 AM

Unfortunately, i don't share the same luck with all of you.

I've already take out both SD and SIM and try thousand times with ActiVeSync 4.1, 4.2 and 4.5 beta, softreset, hardreset, mtty'ing, but what i got? BIG ZERO.

So my pc always recognise my ppc as "Unknown Device" and there is no, even some slim chance, to get it to work.

Any idea for reviving my uni from black slumber of bootloader screen?

Any help would be appreciated.

use MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual, then If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself
go to
http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52

moixalakix

2nd August 2007, 02:20 AM

i have done all this... but there is something with vista... they do not recognised it when it is on bootlad screen... what should i do can anyone help me??

andymccormack

14th June 2008, 01:06 AM

i have done all this... but there is something with vista... they do not recognised it when it is on bootlad screen... what should i do can anyone help me??
Hi, yes you could be bang on in saying there is a problem with vista, my machine did that as well, I really thought I'd turned the phone into a brick, luckily I've got an xp machine that let me connect with the tools that everybody else is talking about here, the one I used was UNI_ExitBootloader.exe (from this site somewhere) which sends all the codes for you and it only worked from the xp machine, it totally failed on the vista machine.