Problems with SEUS - XPERIA X1 General

I've had problems with SEUS before with my X1. The problem is that when I connect the phone according to the guide the update just doesn't start. It just keeps showing the guide on how to connect the phone.
Before I have just reconnected it once or twice and it has started anyway but now I've tried for about 20-30 times with no success.
Anyone that has any idea?
The computer is running Windows Vista Home Premium.

Admin can remove this thread. Found my answer.

I have the same problem. Can I ask you how you resolved it please?

I've got still the same problem, what's the solution?

Hello, you must clear the Checkbox : USB Connection allowed, in the Vista Mobile Devicecenter. Then SEUS will work correctly.
I have no Idea why, but this is the Problem
Sorry ... baaaaad english
------
Hallo, man muss die Hacken " USB Verbindung zulassen " unter Vista im Mobile Gerätecenter entfernen. Dann klappts auch.
T.H.S

This question has been answered lots of times... cannot understand why so many people are too lazy or even dumb to use the search function

Related

Big problema, cannot update...help

hi to everyone,
about a year ago, i patched thr spl...now is 2.13.0000. Yesterday i tried to install to my imate jamin (s200) the new qtek s200 italian rom. The process start successfully and cheked the version. When the phone reboot itself and shows the bootscreen, he program said that there was error 260 and cannot continue; on the phone screen reamin the boot section. When i try to rebbot, it works, but in this way i cannot update my phone. How i can solve this??
i use windows vista and windows mobile device center 1.0 version; also, i used on innotek virtual machine, windows xp with activesync 4.5I would like to inform you, if you can help, theat about a month ago i sent my phone to the assistence because the audio didn't work (is it possible that the assistence did something that block the update??
thanks and please help!!
on the bootscreen, compares RUU on the right-up side,ipl 2.13,spl 2.13 and (all writes are in the red section) and usb on the left-bottom side (on white background)! that's all, i think i've said everything...please HELP!!!
THE PROBLEM IS THAT PROPHET CANNOT CONNECT AT USB IN BOOTLOADER
i've tried, also, to use camera + softreset and when reboot the writes RUU disappear, but still not recognize on usb when in bootloader.
Someone can solve this problem? please....
your problem is vista!
use native windows xp and not VMWare or some Virtual Computer!
have the same strange errors if i flash with vista.
how you have flash your ipl to 2.13??
i used the pdamobiz...i think my ipl was 2.15.0000, and after downgrade, it becomes 2.13.0000. Sound strange? So, do you think the problem is vista and the VM? but i read in this forum that lots of people flash hos phone using xp on virtual machine....but you mean that in vista if you plug the phone (botloader) in to computer, windows doesn't recognize it?
i havent test "win xp vm" on a "vista host". my work laptop has vista and i cant update any rom/firmware. vmware use the host system and his driver to route the usb device. possible the usb-subsystem in vista is changed to much ;-)
test it ... if work ... ok ... we can debug it!
SOLVED
SOLVED! I flashed the prophet on "real" xp. Now my spl changed to 2.20.000 and ipl remain at 2.13.0000. I have another question: if i flashthe phone with one rom of wm6 (which is better?or which is the rom with less bugs?), can i reflash with a wm5 rom without problem?
thanks in advance and thanks for your advice!!

SEUS desn't see x1 in bootloader screen

Hi ppl. I'm new in the world of Win. mobile and Smartphones.I have an Xperia ( simlockfree logofree ) in dutch.
KOVS110
SPL-0.72.0000
MicroP1-787
MicroP2-707
ROM versie: 1.02.937.3
ROM Datum: 08/29/08
Radioversie: 1.06.25.29
Protocolversie: 52.43.25.24U
Uitbeidingversie: 1.0.55513.1119
Modelnr: X1i
R1AA017 R8A 1215-3311 GENERIC_NL
The phone seems to have some problems. ( restarts sometimes , loong loading time , frizing...etc ). I got back to the dealer and ask for warranty. He sed that the problem is for shure software and i can make an update SEUS. I tried for 3 days to do it and i can't. I have Vista Ultimate 64-bit SP1. The new and fresh Win mobile device center 6.1, working USB ports , different USB cables.I have no firewall.My phone connects without any problems and makes syncronization with sync center. The problem is in bootloader mode. I hear a connection sound , but the SEUS and the sync center doesn't see it. In system/device manager i see it as - mobile usb sync device ( or something like that ).The phone shows 3 colors and serial message . When i put the usb cable in , it changes to usb message. Doesn't do anything else. I tryed with/without SD card , restart , reinstall , reset , change ports , cables , drivers, win updates......all the advice in the forums except changing PC ( i have only 1).......Nothing.
I wanted to see if it's broken or not. I don't want to try hardspl flashing or anything else until i'm 100% shure that the phone is good. I don't want to give the f$%^&rs any reason to deny the warranty. So my question is : is there a solution to be able to connect to the SEUS in bootmode screen?
PS -- if it works i'll go for an different ROM-- i'm not dutch , and neither english , so pls excuse all the errors in this post.
Ty for taking the time to read this post.
Of curse thar iz. Iz da nurmall way! Use tha search-funkjon! Ya hav ta use tha natif Administrator-Account uf Win Vistaz!
karakay said:
I have Vista Ultimate 64-bit SP1.
Click to expand...
Click to collapse
Thats the Problem. I've got the same Problem with Vista (regardless if 32/64 bit).
This problem occures very often. Try it with Windows XP !
fdmedia said:
Thats the Problem. I've got the same Problem with Vista (regardless if 32/64 bit).
This problem occures very often. Try it with Windows XP !
Click to expand...
Click to collapse
TRY IT WITH ADMINISTRATOR ACCOUNT! Are you guys nuts?
I have the same problem. I've got only 1 account and it has status of administrator. I have run SEUS with admin privilages and no effect ;/
Abuk007 said:
I have the same problem. I've got only 1 account and it has status of administrator. I have run SEUS with admin privilages and no effect ;/
Click to expand...
Click to collapse
This is NOT TRUE ADMIN! Why don't you check this out and solve your problem: http://www.computerperformance.co.uk/vista/vista_administrator_activate.htm
Didn't know that! Thanks It worked (that admin account is very strange looking disabled it after checking what i wanted to check) No new rom (R3AA) in Poland
Abuk007 said:
Didn't know that! Thanks It worked (that admin account is very strange looking disabled it after checking what i wanted to check) No new rom (R3AA) in Poland
Click to expand...
Click to collapse
Yeah it's strange, so far SEUS is the only use for it lol.
Abuk007 said:
Didn't know that! Thanks It worked (that admin account is very strange looking disabled it after checking what i wanted to check) No new rom (R3AA) in Poland
Click to expand...
Click to collapse
My account is admin but I can't still to see X1 goes further after connect mini-USB cable into X1. Any help?
I have admin account . The super-admin account . I did that already...forgot to mention it. Any other solutions?
karakay said:
I have admin account . The super-admin account . I did that already...forgot to mention it. Any other solutions?
Click to expand...
Click to collapse
Perhaps it is a 64-Bit issue. I can tell you from my experiments that under Win Vista 32-Bit it is most likely a problem of the USB driver. At least I don't think it's a software issue (By software I mean an application). If you run Windows XP on VirtualPC with USB "Passthrough", SEUS will not work either. So it must be a low-level problem of Vista. As you may know, Vista has a new driver system. I believe the 64-Bit version differs from the 32-Bit version in function.
Last week I checked SEUS with my Xperia and detected it correctly. But yesterday SEUS didn't recognize my X1. I didn't make any changes on my X1 since last week. I used Hard SPL to remove my custom Vodafone ROM 3 months ago, and I update to the official R2 without problems. I have the same problem that all of people who posted here. We need a solution because it's very strange this. Maybe SE made some change in his SEUS to avoid people who used Hard SPL update by the official way? Thank you very much. Best regards
VISTA is the problem......... With the help of an XP PC i used SEUS with no problems. Anyway....i steel have Vista PC , so if there will be an solution for future updates pls post them here. TY
i don't have Vista, XP but same problem...
Persuader X, does it say to you "loading...no image file"?
Sapa13 said:
Persuader X, does it say to you "loading...no image file"?
Click to expand...
Click to collapse
Yes. When I connect it, the color bars disappear and start the progress bar that appears when a ROM is being installed. After a pair of seconds, Xperia reboot and says "no image file "., and comes to the boot screen with color bars again to rest in that state forever.
Let me quote myself
I heard of some people that SEUS ran on Vista when they removed the tick for the USB-connection in the mobile device center. Maybe that helps.
Other said, that they had to install the new driver for the USB-sync-connection; just let Windows Update run while your X1 is in the bootloader-mode connected with your PC - maybe try this more then once; my Windows Update needed four runs to find the driver
Click to expand...
Click to collapse
One of the two points will help you too, you'll see
Hey guys, I can update finally. Try this, like me.
Restore stock Hard SPL. It's posted in this forum.
Run SEUS in the administrator account of Vista.
If you don't do any of the 2 previous things, it won't work!
Best regards.
Hi!
Solution from http://forum.xda-developers.com/showthread.php?t=519317&referrerid=1836412
Clear the Checkbox : USB Connection allowed, in the Vista Mobile Devicecenter (before connecting the USB cable to X1). After that the SEUS can identify the X1 and continue with the guide.
Regards
Marcus
Thanks to Marcus that was the perfect solution i spent 6 hours trying to figure this out you are the first one to offer a non flash option.
Cheers

[Blue Angel] Upgrade "Connection Error"

Hey Folks,
i have problem while upgrading. I have a Blue Angle flahed last year to WinMo 6.1 CE OS 5.2.20262 (Build 19949.1.2.0Black). I don't remember the release. But now i have i big problem. I cant upgrade to any newer or lower version.
I tried:
- Format Storage
- Hive Registry
- Disabeled und enabled Active Sync
- With/without Bootloader Mode
- three different RUU.dll
Everytime i try to upgrade (not in bootloader mode) i fetches rom version and proceed. But after 20sec it say connection error. In bootloader mode i doesn't fetch version and same message after 20 sec. Both tried with or without AS and on two different Computers und XP SP3.
Any help?
Sincerly - firstabalon
hi,
since you tried so much stuff before and seem to know your way around the device and the general upgrading process and i have hardly anything to suggest to go on trying. probably the only thing left to try is take another blueangel with either one of your pcs.
another thing is, i uploaded my ruu, which has always worked for me and everybody else who tried it.
i hope this helps, but i will keep on thinking and maybe i can still come up with more ideas.
chef tony...
i dont get it...
i dont know how to use this...
sorry...
i'm new in using the BA...
try and read this:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardMain
step by step instructions how to upgrade with everything there is to do and all the files you need. even if you don't get what you are doing, by following it precisely you will get your device flashed.
thanks chef tony...
i'll try doing that later...
i really like the senior members here...you guys are so helpful...keep up the good work...you're the guide here...
firstabalon said:
Hey Folks,
i have problem while upgrading. I have a Blue Angle flahed last year to WinMo 6.1 CE OS 5.2.20262 (Build 19949.1.2.0Black). I don't remember the release. But now i have i big problem. I cant upgrade to any newer or lower version.
I tried:
- Format Storage
- Hive Registry
- Disabeled und enabled Active Sync
- With/without Bootloader Mode
- three different RUU.dll
Everytime i try to upgrade (not in bootloader mode) i fetches rom version and proceed. But after 20sec it say connection error. In bootloader mode i doesn't fetch version and same message after 20 sec. Both tried with or without AS and on two different Computers und XP SP3.
Any help?
Sincerly - firstabalon
Click to expand...
Click to collapse
Couple of things to try out would be to switch USB ports, try a different cradle (if you can get your hands on one), or try using mtty.

HELP, HELP!!!!!!!

I have the following problem:
I can not cap in my MEGA connect to my PC via USB already have Windows installed new, my ROM with the new SD geflash but it does not work ..
please explain again you cannot cap in a mega connect?
did you tried the connecting options when you connect mega to usb?
Connections:- Usb to Pc:- Active Sync and faster transfer (if memory card inserted).
what about selecting ActiveSync. try that and report.
Windows says the message that my USB device not getting detected. Active Sync does not recognize my device.
I have already tried the following:
- Active Sync running fast connection on and off.
- Try to start Active Sync from MEGA.
- Uninstalled and reinstalled Active Sync.
- Windows 7 (x64) installed on second hard drive and install Active Sync.
- Gone through all USB ports.
I've just tried again. Now it's back a day later ...
Hallo Chris,
German: und was passiert bei Verbindung als Wechseldatenträger ?
English: and what happens when connected as a removable disk ?
rsc1974 said:
Hallo Chris,
German: und was passiert bei Verbindung als Wechseldatenträger ?
English: and what happens when connected as a removable disk ?
Click to expand...
Click to collapse
It will now work again. But yesterday I spent hours to find the error. I have tried all the options, the phone was not recognized windows ...!!!
Es funktionier jetzt wieder. Aber gestern habe ich stunden damit verbracht den Fehler zu finden. ich habe alle optionen ausprobiert, das Handy wurde von windows nicht erkannt...!!!
Glad it is solved ...activeync is sometimes crappy.....but it use to be much worse.....
Today activesync saw my phone as a new device.... so I paired them up again.....
With windows 7 you better download and use 'windows mobile device manager', not activesync.
I had a similar problem.Often even when properly paired with Activesync(or windows mobile device manager) connection failed after a few days.
Since I have done the following-I have no connection problems:
Try:
1.Uninstall Activesync and his drivers.
2.if you use Internet Security (f.ex.Norton I.S) remove from the Settings / Network Settings / control programs / =WCESMgr.exe,wcescomm.exe,rapimgr.exe.
3.Install Activesync(or wmdc).
4.Change the USB cable (f.ex-Hama USB 2.0 cert.cable)
5.Change to the USB port to connect directly to the motherboard (back of the computer-not through a hub,or additional slot on the front).
6.In the firewall, select everything that is related to Activesync on the deny (not automatic!).
greetings
trebuh said:
With windows 7 you better download and use 'windows mobile device manager', not activesync.
Click to expand...
Click to collapse
Sorry, I meant Windows Mobile Device Center, not Active Sync
teriero said:
I had a similar problem.Often even when properly paired with Activesync(or windows mobile device manager) connection failed after a few days.
Since I have done the following-I have no connection problems:
Try:
1.Uninstall Activesync and his drivers.
2.if you use Internet Security (f.ex.Norton I.S) remove from the Settings / Network Settings / control programs / =WCESMgr.exe,wcescomm.exe,rapimgr.exe.
3.Install Activesync(or wmdc).
4.Change the USB cable (f.ex-Hama USB 2.0 cert.cable)
5.Change to the USB port to connect directly to the motherboard (back of the computer-not through a hub,or additional slot on the front).
6.In the firewall, select everything that is related to Activesync on the deny (not automatic!).
greetings
Click to expand...
Click to collapse
I have Windows Mobile Device Center already uninstalled and removed the drivers. I even have Windows installed to start it again without antivirus programs. I use ESET Smart Security 4, I've also disabled ESET and it had not worked ... It had worked with any USB port, not directly to the motherboard ....
Chriss1983 said:
I have Windows Mobile Device Center already uninstalled and removed the drivers. I even have Windows installed to start it again without antivirus programs. I use ESET Smart Security 4, I've also disabled ESET and it had not worked ... It had worked with any USB port, not directly to the motherboard ....
Click to expand...
Click to collapse
Let me explain what I've encountered a few times(with tg01 and mega/touch2 also after reflashing, of course on XP&active sync):
a problem same to yours, solved by one simple method(at least for me, working everytime)=change device ID(in Settings/system/about/device id).
Maybe it's just me, but it worth a try...
bib*oops said:
Let me explain what I've encountered a few times(with tg01 and mega/touch2 also after reflashing, of course on XP&active sync):
a problem same to yours, solved by one simple method(at least for me, working everytime)=change device ID(in Settings/system/about/device id).
Maybe it's just me, but it worth a try...
Click to expand...
Click to collapse
I will try it next time ... Thanks for your help

MDA II (HTC Himalaya) Disconnection error during flashing.

Greetings developers and enthusiasts!
I was flashing my MDA II (HTC Himalaya) as i did in the past very often. Everything was fine but this time the USB/Disconnection error appeared (Screen shows only Serial/USB & v.1.02). I tried of course the usual steps:
1 - first fully charged battery.
2 - install mobile device center or active sync ( as per your OS )
3 - Enter in to the bootloader mode
4 - connect USB cable with ppc device.
5 - wait for detection of the device
6 - drivers are automatically installed if you are using windows7 it shows
driver installed successfully & device is ready to use.
7 - extract the rom update utility from the posts whichever you like ( remember choose it carefully as per your device )
8 - just double click on upgrade icon in extracted folder and yeah you done.
Click to expand...
Click to collapse
But I’m not able to flash the device with a new rom anymore. I don´t know what went wrong and why I’m not able to reflash the device.
Windows 7/64 identifies the USB-Device correctly. But the updater (ROM) says there is a connection problem/101.
May be I´m missing something.
Thanx in advance!
-Agesilaos
UPDATE:
I tried another PC with Windows 7/32
Same Problem again with error 101 and device still in bootloader mode.
Agesilaos said:
Greetings developers and enthusiasts!
I was flashing my MDA II (HTC Himalaya) as i did in the past very often. Everything was fine but this time the USB/Disconnection error appeared (Screen shows only Serial/USB & v.1.02). I tried of course the usual steps:
But I’m not able to flash the device with a new rom anymore. I don´t know what went wrong and why I’m not able to reflash the device.
Windows 7/64 identifies the USB-Device correctly. But the updater (ROM) says there is a connection problem/101.
May be I´m missing something.
Thanx in advance!
-Agesilaos
UPDATE:
I tried another PC with Windows 7/32
Same Problem again with error 101 and device still in bootloader mode.
Click to expand...
Click to collapse
You must Update (downgrade) your driver for flashing in Win7!!!!
See in my signatur english thread and look in the HowTo section i know it is for Blue Angel but it works
d-two said:
You must Update (downgrade) your driver for flashing in Win7!!!!
See in my signatur english thread and look in the HowTo section i know it is for Blue Angel but it works
Click to expand...
Click to collapse
Greetings d-two!
Herzlichen Dank für Deine Hilfe!
Thanks a lot for your help!
I remember i did an upload of the usb driver back in 2009 during the windows7-BETA but i forgot that step!
It works very fine now due to your nice manual!
This threat should be sticky don´t you think?
Best regards from Athens,
-Agesilaos
Agesilaos said:
Greetings d-two!
Herzlichen Dank für Deine Hilfe!
Thanks a lot for your help!
I remember i did an upload of the usb driver back in 2009 during the windows7-BETA but i forgot that step!
It works very fine now due to your nice manual!
This threat should be sticky don´t you think?
Best regards from Athens,
-Agesilaos
Click to expand...
Click to collapse
Thanks, I know that this is important but no one wants to make as a sticky!

Categories

Resources