Hey gang,
I purchased my SX56 off of ebay, and it was running Windows Mobile 2002. It was a Rogers AT&T Rom, unlocked at the time.
After some careful reading, I decided to upgrade to the Windows Mobile 2003 ROM that Rogers was offerring for free. I downloaded it, installed it, and all was well until I discovered that the SIM was now locked.
Read up some more on the site here, and found that all I had to do was to load either the Special Edition Rom, or one from a kitchen, which I found at http://lumpistefan.dyndns.org/. Apparently, this would allow me to use one of the unlocking tools, and then I could upgrade again to WM2003.
I cooked up a nice ROM for the image, downloaded it, installed it, went through the instructions perfectly.
PROBLEMS...
Once I performed the necessary reset on the SX56, I had an error on the device. "Unrecognized card" it says. "Enter the name of the device driver for this card". Says this about "Unknown card in socket 1". Huh? I click cancel. I'm then sitting at the desktop on the device.
When inserting the device into the cradle/charger, I receive a similarily alarming error, which says "USB Device Not Recognized - One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." When I click the balloon to learn more on this, I'm taken to the device properties, which shows there's no driver loaded for the device. I perform a search on the pc for a driver, and I come up with nothing.
I'm at a complete loss, and have no ideas on where to go, what to try. I really don't wanna be stuck with a useless device, and I can't update the ROM on it until I can get it to connect to the USB. The error on the pc is bad enough about the driver, but I'm more worried about the error on the device itself. Could this be a driver issue there? Is the USB connection crapped out on the actual device?
Any thoughts are MOST appreciated! I'm technically inclined, but XDA's are a new realm to me.
Linger1974 said:
Once I performed the necessary reset on the SX56, I had an error on the device. "Unrecognized card" it says. "Enter the name of the device driver for this card". Says this about "Unknown card in socket 1". Huh? I click cancel. I'm then sitting at the desktop on the device.
Click to expand...
Click to collapse
Hm. Thats unusal. Have had this problems a few times, but my card had always worked....
Linger1974 said:
When inserting the device into the cradle/charger, I receive a similarily alarming error, which says "USB Device Not Recognized - One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." When I click the balloon to learn more on this, I'm taken to the device properties, which shows there's no driver loaded for the device. I perform a search on the pc for a driver, and I come up with nothing.
Click to expand...
Click to collapse
Which version of active sync are you using? Most of the new ROMs require ActiveSync 3.71. You can get it for free at the Microsoft site....
Linger1974 said:
I'm at a complete loss, and have no ideas on where to go, what to try. I really don't wanna be stuck with a useless device, and I can't update the ROM on it until I can get it to connect to the USB. The error on the pc is bad enough about the driver, but I'm more worried about the error on the device itself. Could this be a driver issue there? Is the USB connection crapped out on the actual device?
Click to expand...
Click to collapse
You normaly could make an update of the rom via SD-Card.
This should work...
HTH
Stefan
I had exactly the same problem using the same cooked Rogers. Now my XDA is dead. I only get to the bootloader now. No OS!!!!!!!!!
Even stranger, when I took out my SIM and put it back into my old phone, the SIM is blocked on my service provider (FIDO). I'm going to have to phone them to get a PUK code generated, which will likely cost me $25.
I guess the only thing I can do is to purchase an SD reader/writer and try to load a ROM from the card. - I've been looking around at all the posts in here on how to do that, but there's no mention of my Bootloader version, which is 5.22. - I really don't want to follow instructions on an older bootloader version and make things worse.
Is there a link or something to a DETAILED instruction set for loading a ROM via bootloader?
Thanks for all replies!
I have had the same problem with Rogers rom and Kitchen , a week ago and wrote about it to LumpiStefan. I saved my old Rom to SD CARD via XDA Tools and Card Reader before.
and after errors in cooked ROM, i restored old one.
So now i have only original Rogers ROM that working fine, and more stable than T-Mobile 4.0.1.16
After purchasing an SD card reader/writer, I followed the instructions to the letter on using the bootloader to load a ROM image, and everything is fine now.
One weird problem though is that I still can't use the Rogers ROM I got from them without having the phone locked, and I can't use the Rogers rom from the kitchen, without receiving the "card error in slot 1" error. For now, I'll stick with the 2002 ROM's.
LumpiStefan said:
Linger1974 said:
Once I performed the necessary reset on the SX56, I had an error on the device. "Unrecognized card" it says. "Enter the name of the device driver for this card". Says this about "Unknown card in socket 1". Huh? I click cancel. I'm then sitting at the desktop on the device.
Click to expand...
Click to collapse
Hm. Thats unusal. Have had this problems a few times, but my card had always worked....
Linger1974 said:
When inserting the device into the cradle/charger, I receive a similarily alarming error, which says "USB Device Not Recognized - One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." When I click the balloon to learn more on this, I'm taken to the device properties, which shows there's no driver loaded for the device. I perform a search on the pc for a driver, and I come up with nothing.
Click to expand...
Click to collapse
Which version of active sync are you using? Most of the new ROMs require ActiveSync 3.71. You can get it for free at the Microsoft site....
Linger1974 said:
I'm at a complete loss, and have no ideas on where to go, what to try. I really don't wanna be stuck with a useless device, and I can't update the ROM on it until I can get it to connect to the USB. The error on the pc is bad enough about the driver, but I'm more worried about the error on the device itself. Could this be a driver issue there? Is the USB connection crapped out on the actual device?
Click to expand...
Click to collapse
You normaly could make an update of the rom via SD-Card.
This should work...
HTH
Stefan
Click to expand...
Click to collapse
Hello Stefan,
Same problem, unfortunately I did not read this thread before just installing this ROM. Stefan, it seems that it is setting up the device as a non phone edition device, it puts in bluetooth, turns off the phone completely, turns off the Backlight completely-even if you turn it on it does not work. It is as if someone took the Rogers Rom I gave you and installed it on a PPC with bluetooth\WiFi but no phone and recreated the ROM, very strange. Now I need to buy a card reader as well, since it does not recognize my card or device. Please pull this ROM, immediately.
LumpiStefan said:
Linger1974 said:
Once I performed the necessary reset on the SX56, I had an error on the device. "Unrecognized card" it says. "Enter the name of the device driver for this card". Says this about "Unknown card in socket 1". Huh? I click cancel. I'm then sitting at the desktop on the device.
Click to expand...
Click to collapse
Hm. Thats unusal. Have had this problems a few times, but my card had always worked....
Linger1974 said:
When inserting the device into the cradle/charger, I receive a similarily alarming error, which says "USB Device Not Recognized - One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." When I click the balloon to learn more on this, I'm taken to the device properties, which shows there's no driver loaded for the device. I perform a search on the pc for a driver, and I come up with nothing.
Click to expand...
Click to collapse
Which version of active sync are you using? Most of the new ROMs require ActiveSync 3.71. You can get it for free at the Microsoft site....
Linger1974 said:
I'm at a complete loss, and have no ideas on where to go, what to try. I really don't wanna be stuck with a useless device, and I can't update the ROM on it until I can get it to connect to the USB. The error on the pc is bad enough about the driver, but I'm more worried about the error on the device itself. Could this be a driver issue there? Is the USB connection crapped out on the actual device?
Click to expand...
Click to collapse
You normaly could make an update of the rom via SD-Card.
This should work...
HTH
Stefan
Click to expand...
Click to collapse
Hello Stefan,
Same problem, unfortunately I did not read this thread before just installing this ROM. Stefan, it seems that it is setting up the device as a non phone edition device, it puts in bluetooth, turns off the phone completely, turns off the Backlight completely-even if you turn it on it does not work. It is as if someone took the Rogers Rom I gave you and installed it on a PPC with bluetooth\WiFi but no phone and recreated the ROM, very strange. Now I need to buy a card reader as well, since it does not recognize my card or device. Please pull this ROM, immediately.
Related
Since updating to the T-Mobile Rom for my XDA, nearly everythiung has gone wrong.
And when I tried to downgrade it.... Nothing happens.
I used to use a modified Program A to upload it to my phone but it continues to say that the USB devide gets remotely stopped. the only thing that I can think is that my phone is cancelling the upgrade/downgrade.
I have also tried using a copy of the XDATools program to try and:
Upload another Rom.
Copy the rom to an SD card so I can use the bootloader method.
Change the Bootloader so I can use the SD card method.
None of there are working.
Help :-(
I really want to go back to the ATT rom, it might have the annoying thing with the sound but at least it doesn't mess up as much, doesn't format my SD/MMC cards and lets the alarms actually work for me.
if i'm not wrong, it seems you upgraded using the TMO exe file which updated both ROM & RSU.
check ur boot loader version, if it's 5.22 or higher, i think you need to dowgrade to 5.15 ... use the exe file that comes with the XDAtools in the binaries directory .. its name is fixbootloader.exe .. it should update ur boot loader to 5.15 by which you can use XDAtools or the SD method.
Tried that. I do have XDA tools on my machine and used that program but my CDA still has the bootleader of 5.22
And both of my machines don't like trying to update my XDA :-(
This Rom is the most annoying one I have tried mainly becaise now I can't go back to even my original one that I backed from the XDA when I got it.
Am I stuck with this ROM?
omg, i think i am having the same problem. In my case, since ive installed the new rom, i cannot sync with activesync, well very slow anyway. Activesync on my pc stops responding for a while and suddenly it says connected. However when i then run the executable created by the kitchen, it just flashes a command line window for a second.
When I try XDA-toolz with an nbf file, i get the following message:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
Click to expand...
Click to collapse
Please someone help, because i am really stuck now.
I checked, my bootloader is 5.14, so that shouldnt be the problem, perhaps i need to reinstall activesync, or perhaps lumpistefans kitchen cooks up bad roms. :?:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Biso007 said:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Click to expand...
Click to collapse
I dont understand how i can have a wrong rsu? I didnt update it , as far as i know , i just updated the pda part. I only saw programme A.
Activesync does recognise my xda, because i can synchronize and explore my device. It does however take a long time before activesync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling activesync, this didnt help.
prowling said:
ActiveSync does recognise my XDA, because i can synchronize and explore my device. It does however take a long time before ActiveSync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling ActiveSync, this didnt help.
Click to expand...
Click to collapse
If there is something wrong with the RSU it will defeinitly slow the USB performance, not neceassary by wrong RSU flashing ... otherwise, check the pins of your cradle or the 22-pin connector of the XDA ... maybe one or more pins are bent or weared.
Tried upgrading the radiop stack and although the reception is slightly better... It still won't let me upload,
and its a new cable too :-(
Oh well looks like I am stuck with it.
Another way to upgrade firmware
Are there other ways to upgrade the bootloader from SD card from within the device or even to upgrade the OS from within the phone itself?
You know... as a last alternative?
You can use SD reader/writer from the PC using XDAtools ... once the .nbf file is on the SD card, use the normal SD flashing method.
Or you can use another XDA device from a friend to copy the file to your SD card
I am having the same problem. I have TMO 4.01.16 and since I installed I can't down/upgrade my ROM through EXE or XDA tools, it says my device isn't connected, but I can still connect with Active Sync and all that jazz
ha ha
I can fix all your problems!
How?
Finally got it to work, Although it was a little bit of effort to do so.
I went back to the kitchen and downloaded a NB1 cooked rom with the "B" Signature. Then I basically ran the TMobile Setup again...
Once the setup files were on my computer I overwrote their .NB1 file with the one I just cooked.
But.... I forgot to change the file for the Radio Stack.
The machine worked except for the phone and as something is still stopping me. *it was my first reboot* It wouldn't let me use a new radio stack.
Ended up that i kept on going in to the bootloader and eventually turned my radio off altoghether before trying an update.
Now I am back to a decent rom... (Cooked and modded version of the ATT Wireless rom) and I am almost really happy.
Now to figure out how to stop the annoying sounds starting off really low.
But til then... I'm 90% happy
Thespus2002 said:
How?
Click to expand...
Click to collapse
Use the Sd Method flashing!!
Tmobile roms won't let you upgrade from the usb, here's the link and it will guide you how to flash your device from the SD good luck
http://forum.xda-developers.com/viewtopic.php?t=3274
The way I described.. I had to use the USB method.
my current bootloader (6.22) will not allow me to boot from an SD card.
And XDATools will not allow me to downgrade it... Yet
on ur PC at \xdatools\binaries run this command: pnewbootloader.exe bootloader_5_15.nb0
Wish it was that easy. The phone still appears to be locked in the rom so I can't update the Bootloader. I keep getting a message that says.
Unable to flash in to offset, cannotg disable bootloader write protect.
Ok, i konw there's already been several threads here about downgrading from the wm2003 rom (4.01.16ENG from the rom kitchen to be precise) but i can't seem to get this thing anywhere... as i said i upgraded the rom to the one specified above and found it far slower and unstable than the ppc2002; I wanted to flash the xda with the old rom but there's this strange communicate saying that the connection has been suddenly closed and the "programme a" stops. i tried to flash the old rom directly to the device using the xdatools but also with no success... it keeps on saying that it couln't communicate with the remote application... well then i thought about this bootloader fix (still unsure what bootloadre i have because i can't get the info anywhere) and it said that the memory on the device is write protected.... :/ well, and as for now i am waiting for a sd card to try that, but.... tell me, will the xdatools prepare the card if i insert it into the device? (i have no card reader for my pc) i am woried because each action i take (except normal device usage - activesync, copying and moving files, installing appz) that messes with the roms, shuts down the connection and i have to unplug the device from my pc and plug it again... please help me, i'm in dire need!
I am having a similar problem with the same rom version. I wish i never used that version! I did an update to wm2003 earlier and i could go back and forth with no problems, but this one is a real nasty one!!
the message i get when using osimagetool:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
I am having the same problem ..
and when i power on/off the device it says (Unrecognized Card)
Enter the name of the device for this card. For information, see the card manufacturer's documentation.
and there is a place where i can write something (Unknown card in socket 1)
m112a said:
I am having the same problem ..
and when i power on/off the device it says (Unrecognized Card)
Enter the name of the device for this card. For information, see the card manufacturer's documentation.
and there is a place where i can write something (Unknown card in socket 1)
Click to expand...
Click to collapse
YES!!! Same here!!
How about the phone? I cannot seem to turn it on. When the pin screen comes up it says i should turn on the phone, but i cant dothat anywhere..
Hi All,
The best option for ROM upgrade is always the SD method ... it's much easier and safer. XDAtools doesn't work with some ROMs because of the boot loader version not the ROM itself.
So what do you say guys? will i be able to downgrade it from the sd card? - and first of all, prepare the card having it inserted into the xda itself and using xdatools? i also wish i had never used it, the newest ppc2002 rom from o2 is just soo cool comparing to the wm2003 one i'm stuck with right now...
read more: http://www.softick.com/news.html#83
Re: Softick Card Export II version 2.11! Now working on Wiza
dddrko said:
read more: http://www.softick.com/news.html#83
Click to expand...
Click to collapse
It still makes my wizard to lock up...
Re: Softick Card Export II version 2.11! Now working on Wiza
bolasz said:
dddrko said:
read more: http://www.softick.com/news.html#83
Click to expand...
Click to collapse
It still makes my wizard to lock up...
Click to expand...
Click to collapse
It works for my 838.. I have lockup and unable to switch to SDcard mode only if I connected to my PC and activesync once and unplug. But that seems to be the activesync issue in my 838 which fail to free itself from unplug from PC. So it cannot switch to SDcard mode..and prompt me an error message.
I have already switch to AS4.1 but does not improve my situation.
What is Microsoft doing here?? :roll: A soft reset is the only way to get my device syncup again.. :x
I own this program since I had my XDA mini ...
finally I can use it again to copy some files to my pda and use it as a memory stick...
I also noticed some problems:
1. after I connect the USD cable and the PC recognized my pda as a memory stick, Windows XP asked me to make a reboot in order to be able to use the new 'harddrive'
2. after I copied a .jpg to my pda it looked like the storage card is no longer recognized by WM5. The icons of the shortcuts to programs I installed are missing and I cannot browse with TotalCommander to my storage card.
After disconnecting the USD cable, my storage card could be found again - is this a bug or a feature?!
After the first connect in mode 'Card Export' I switched to 'Active Sync' and the synching went on without any problems.
After agains swithing to mode 'Card Export' my Wizard gave an error message, as follows:
"Cannot switch between Card Export and Active Sanc modes. This may be because of missing dlls or corrupted registry entries."
This looks also to me like an incompatibility between card export and active sync.
Hmpf ... rebootet the phone and connected - voila - my Wizard was again properly verified as Memory Stick and I again could upload another .jpg to my device.
It looks definately unfinished ... but it is working quite acceptable to me, though there is a lot room for improvement, it will get the job done, if I need a memory stick 'on the go'.
My device is a HTC Wizard, O2 german.
i may be wrong on the second point, but activesync alters a file when you transfer it to the pda,
so if you transfer a file to the card (even using a card reader) then put the card back in the pda wm5 will not recognise it properly.
point 1 should only happen the first time of detection.
have no problem with my XDA II...
Chris09 said:
After agains swithing to mode 'Card Export' my Wizard gave an error message, as follows:
"Cannot switch between Card Export and Active Sanc modes. This may be because of missing dlls or corrupted registry entries."
Click to expand...
Click to collapse
I am experiencing the same... Please update this topic if you'll find a solution.
i'm having the missing dlls dialog problem too.
I noticed that once you activesync'ed, you can't switch to card mode and need to reboot the device.
However, mine can't seem to work anymore. It won't even switch. But I also tried disabling my today's screen (pocket plus and pocket breeze) and it works... but only the icon manage to change. My PC can't detect it as a mass storage device though.
Any luck?
Mine is working fine, I got that dll message once but a soft reset fixed it.
Just wondering what roms are you guys using that works with softick? I'm using rom version 1.6.7.1 WWE which doesn't seem to work. I tried hard reset and install softick on the first reboot. The computer detected a new hardware but failed to install the device.
vmirage said:
Just wondering what roms are you guys using that works with softick? I'm using rom version 1.6.7.1 WWE which doesn't seem to work. I tried hard reset and install softick on the first reboot. The computer detected a new hardware but failed to install the device.
Click to expand...
Click to collapse
I get exact problem, detects a HTC device, trys to load the USB Mass Storage Device, hang for a short period and then in Device Manager show up with a problem. Fails to install or display drive letter for SD Card in phone. Have tried everything, happens on XP and Windows 2000 PCs, tried various PC's, same problem.
Can anyone help
p.s - I have the T-Mobile MDA Vario phone, same as imate-kjam I believe.
eilz said:
vmirage said:
Just wondering what roms are you guys using that works with softick? I'm using rom version 1.6.7.1 WWE which doesn't seem to work. I tried hard reset and install softick on the first reboot. The computer detected a new hardware but failed to install the device.
Click to expand...
Click to collapse
I get exact problem, detects a HTC device, trys to load the USB Mass Storage Device, hang for a short period and then in Device Manager show up with a problem. Fails to install or display drive letter for SD Card in phone. Have tried everything, happens on XP and Windows 2000 PCs, tried various PC's, same problem.
Can anyone help
p.s - I have the T-Mobile MDA Vario phone, same as imate-kjam I believe.
Click to expand...
Click to collapse
Same here too!! using ver 2.12
ver 2.11 worked fine with me, so most probably I will downgrade to it now.
I emailed the tech support and waiting for their reply. I will post it here in case I get anything new.
I just tried v2.12, and it didn't work. I found v2.11 on some download site, and installed it. v2.11 worked fine on Qtek's 2.8.7.1 ROM.
I cant get this to work either using 2.12. I get the device manager problem as mentioned previously. Does anyone know where can i get 2.11 from?
found it here:
http://www.softick.com/files/CardExportPPC211c-softick-en.zip
but i get the same problem
You can find previous versions in the "download" section on the left.
I'm having the same issues, used to work fine with 2.11, then it stopped being able to write but could still read (this is on my Mac), and now with 2.12 I can't even get the thing to mount. I'm talking with the developer to see if we can get a fix.
Any 2.12 and 2.11 not working for me... My computer and three others shows me message that they don't have drivers
I posted a query on their forum.
Heres their reply:
http://softick-forum.com/viewtopic.php?p=35#35
pewe said:
I posted a query on their forum.
Heres their reply:
http://softick-forum.com/viewtopic.php?p=35#35
Click to expand...
Click to collapse
I'm a bit confused regarding their reply.
You asked a question about the Wizard and they replied saying they are waiting on delivery of HTC Universal to examine it better. I'm not sure what the Universal has to do with compatibilty for the Wizard as they are completely different devices with different hardware. (Mybe i'm wrong and the hardware components that Card Export uses is actually the same on both devices)
Puckster -
I noticed this on second look, and asked for clarification.
just want to inform everyone that there is a free alternative. it's similar to softick card export that it turns your device into a plug-and-play card reader. it's called wm5torage (yes, the number '5' is the letter 'S')
http://forum.xda-developers.com/viewtopic.php?t=45411&highlight=wm5torage
it does not have the system tray icon that enables you to switch between activesync and export mode, but rather you open the app in your accessories folder and activate/deactivate it from there.
but hey, it's free and it works
Is there a way to install HARDP-SPL from the micro SD card? I am able to flash any rom from my SD-Card, but I am no longer able to connect my Polaris to active sync. Get an error "USB Device not recognized" and I am not able to get synched. Now I have flashed several different rom's and also different radios, that works from the micro sd card. but I am still not able to connect with active sync. When I enter the bootloader mode then I just see that message "POLA100 MFG SPL-2.20.OliNex CPLD-2" So I guess the Hard-SPL is missing. Home I will get some help ;-)
If you step manually to bootlader mode and see the Olinex string, hard-spl is installed!
Thanks for your answer, didn't know that. However, I am not able to connect to active sync even though I have tried different ROM's and different Radios also, flashed from SD-card. Still no connection to activesync :-(
I have the exact same problem for almost a year now, flashing all roms with the micro sd card... and living without active sync :S
Hope someone can help us here
maybe 2 things :
1- your usb cable is ko...try with an another one
2- maybe the usb pins in your device are twisted or broken...
cheers!
ouioui01 said:
maybe 2 things :
1- your usb cable is ko...try with an another one
2- maybe the usb pins in your device are twisted or broken...
cheers!
Click to expand...
Click to collapse
1- the USB cable can't be the problem, already tried a different one, plus using my Touch pro with the same cable on the same computer
2- the pins, I don't know, they look good for what I can tell and it is strange because the phone will be charged with the usb cable
wish I would find a solution.....
fktsndr said:
If you step manually to bootlader mode and see the Olinex string, hard-spl is installed!
Click to expand...
Click to collapse
Can you dumb that down a bit? I don't have access to a windows computer, so I have to rely on the microSD. Is there a way to Hard-SPL the phone with the SD card? I performed a Hard-SPL on my Wing when I first got it, but I think it was an older out-dated version, cuz I get an "Invalid Certificate" error when trying to flash from my microSD.
Thanks,
-Adam
easy solution which I found
If you first install the .nbh file of the .72 stock spl using the micro sd card, then your device will not boot into the OS. Now run the Sony Ericsson update utility (which you can download from their website) and run it. It will try to upgrade the system through usb. After different steps, this software will ask you to reinstall the OS (the spl should match first) and then you can reinstall the stock spl and you are back to square one. Now from here, you can now go anywhere you like.
Note: The above method, I tried it myself and it worked. It might not work for everyone hence use it at your own risk. But if you have a bricked device, then there is nothing to lose.
Just as the topic says. I saw a couple of people claiming to have used the seus to update and decided to try. I had the stock RA2 and wanted RA3.
When I connect the deivce, seus cannot recognize it. It makes several attempts (with the sound for new device found/unplugged) and then says that it could not recognize it. During this time the screen of the X1 flickers from the coloured stripes to a balck screen and there are multiple ActiveSync icons aperaing on the taskbar (all grey).
I have XP Pro SP3 03/09. Most of the topics I found were from people with Vista.
Any ideas? Now, I'm stuck with the stock RA1 until I find a solution.
I noticed something else. Just after the coloured stripes appear, there is a screen that pops up briefly and says "no image file!". After I plug the usb in, the bar with the 0% appears for a short moment, then the scrren goes black and returns to the coloured stripes. The cycle repeats all the time.
What is that "there is no image file!"???
orelsi said:
Just as the topic says. I saw a couple of people claiming to have used the seus to update and decided to try. I had the stock RA2 and wanted RA3.
When I connect the deivce, seus cannot recognize it. It makes several attempts (with the sound for new device found/unplugged) and then says that it could not recognize it. During this time the screen of the X1 flickers from the coloured stripes to a balck screen and there are multiple ActiveSync icons aperaing on the taskbar (all grey).
I have XP Pro SP3 03/09. Most of the topics I found were from people with Vista.
Any ideas? Now, I'm stuck with the stock RA1 until I find a solution.
Click to expand...
Click to collapse
Create a "real" administrator account, log on to that account, installation shall work fine...should work unless your R3A for your country hasn't been released.
Also, your current account is not admin even thought u mgiht think it is. It's usually the case.
i had the same problem, see this...
http://forum.xda-developers.com/showthread.php?t=514953
poetryrocksalot said:
Create a "real" administrator account, log on to that account, installation shall work fine...should work unless your R3A for your country hasn't been released.
Also, your current account is not admin even thought u mgiht think it is. It's usually the case.
Click to expand...
Click to collapse
I am the administrator.
Sapa13 said:
i had the same problem, see this...
http://forum.xda-developers.com/showthread.php?t=514953
Click to expand...
Click to collapse
Thank you for this, but I want to use SEUS for the update.
I had the same problem on my PC using Vista, however when I used my other PC that has XP it worked fine.
Obviuosly I don't know which you are working, but if you can give both a try...
orelsi said:
I am the administrator.
Thank you for this, but I want to use SEUS for the update.
Click to expand...
Click to collapse
http://www.computerperformance.co.uk/vista/vista_administrator_activate.htm
1. Logon to Vista using your normal username and password.
2. Click on the Start button
3. Click on Start Search.
4. Type, cmd.
5. Right-click cmd, select 'Run as administrator' from the shortcut menu.
6. In the black 'DOS box', type the following at the command line:
Net help user
7. The idea of the last command is just to observe the options for Net User. In particular, examine the syntax to set the password.
8. The next instruction is the crucial command. I have chosen password = p£ssworD, you may want to choose different characters.
9. Net user administrator p£ssw0rd
10. Net user administrator /active:yes
11. Check the message : The command completed successfully
12. Switch User, or logoff
13. Logon as Administrator Password p£ssw0rD (Your password may be different!)
Trap1: There should be no space between the word 'active' and the colon.
/active :yes is wrong.
/active:yes is correct.
Trap2: You need a forward slash before /active
Net user administrator active:yes is wrong
Net user administrator /active:yes is correct
Thanks to Rob Hilton for pointing out this trap.
Trapx: Pay close attention to the command, it should be active, not activate.
I thank Ben O'Sullivan for correcting this activate --> active error.
Well, I also thought that I was the administrator until I realised that I was not... I am not sure if this is the case for you but maybe check again?
EDIT: Nevermind, you got an XP, I think it's most likely that you got a lot of software that conflicts with activesync and it's probably impossible to find the culprit
I would just update it with some else's computer..
the "no image file" warning upon boot is because there is an SD card in the phone, but no image on the SD card that can be used to update the phone
orelsi said:
I am the administrator.
Thank you for this, but I want to use SEUS for the update.
Click to expand...
Click to collapse
Report your current ROM. It is possible that your phone is in USB to PC mode instead of ActiveSync mode. It is also possible that your ROM has not been officially released.
kirkie said:
I had the same problem on my PC using Vista, however when I used my other PC that has XP it worked fine.
Obviuosly I don't know which you are working, but if you can give both a try...
Click to expand...
Click to collapse
I said in the OP that I got XP Pro SP3
poetryrocksalot said:
I think it's most likely that you got a lot of software that conflicts with activesync and it's probably impossible to find the culprit
Click to expand...
Click to collapse
I formated the SD. Reinstalled the ActiveSync. Did a hard reset. No change.
ActiveSync is working fne when I connect the phone to the PC. It doesn't work when I try to update it via SEUS.
I t really is getting frustrating . Today I needed my GPS, but when I took the phone I had forgotten that I formatted the card earlier..........
ferjan said:
the "no image file" warning upon boot is because there is an SD card in the phone, but no image on the SD card that can be used to update the phone
Click to expand...
Click to collapse
I formatted the card FAT32. That should solve any issues. In order there to be an image for the update the SEUS should connect to the SD and copy that image in the first place.
poetryrocksalot said:
Report your current ROM. It is possible that your phone is in USB to PC mode instead of ActiveSync mode. It is also possible that your ROM has not been officially released.
Click to expand...
Click to collapse
The phone is in ActiveSync mode. As I said when the SEUS is trying to identify the phone there are multiple ActiveSync icons appearing on the taskbar. All of them are innactive (grey).
I use the official RA2. Updated through SEUS.
I know there is a stupid little issue that I am overlooking. It is something obvious every time. I can't find it this time though....
What I meant was that the ROM for you country/language has not been released. And I meant pc software that conflicts with active sync, if this is not the case then obviously R3A is not release.
poetryrocksalot said:
What I meant was that the ROM for you country/language has not been released. And I meant pc software that conflicts with active sync, if this is not the case then obviously R3A is not release.
Click to expand...
Click to collapse
That shouldn't conflict with SEUS recognizing my device though, right?
Here comes another day of experimenting to find the answer .
hello m8 i had once this problem when i a hardspl and then i wanted to update from seus.
what i did? i run the stockspl -> flashed a stock rom >then update froms seus.
it happened to me 2 times when i tried to flash custom roms or official roms via flash mode. the problem was solved both times
i dunno if that helps but u could try.
lunaticxgr said:
hello m8 i had once this problem when i a hardspl and then i wanted to update from seus.
what i did? i run the stockspl -> flashed a stock rom >then update froms seus.
it happened to me 2 times when i tried to flash custom roms or official roms via flash mode. the problem was solved both times
i dunno if that helps but u could try.
Click to expand...
Click to collapse
The thing is, I never flashed custom ROMs on this device. All the different ROMs I tried were flashed on another X1. The only thing I have done is hard reseting 10+ times and updating to RA2 via SEUS one time. That's it.
I guess it could work, but I will do it as a last resort. There is something wrong with my phone and I want to know what or at least how to fix it.
Like I said, your R3A has not been released. I will keep saying this until you tell me that you know 100% that the R3A for your Xperia has been released.
I too had the same issue. I also couldn't install the bootloader to load a custom ROM either. Skipping several hours of swearing, soft boots and repeatedly trying the same thing, I discovered the problem was with Kaspersky.
After disabling Kaspersky, I was able to load the Generic UK R3A off the SD card. Never got around to trying SEUS again, but have a go at disabling any internet security software you have.
I guess it's windows vista software issues (NOT POCKET PC SOFTWARE).
I have Windows XP on my laptop and whilst i could flash my x1 fine with the older SEUS client, since they upgraded to the new fancy looking client i face exactly the same problems. The x1 goes in USB mode and SEUS is starting/terminating several activesync processes in the background and then it fails.
Clear the Checkbox
I have Windows Vista Business running on my laptop.
I also have the problem of SEUS cannot indentify my X1 (but sometimes, it did recongize though very low succesful rate).
After clear the Checkbox : USB Connection allowed, in the Vista Mobile Devicecenter (before connecting the USB cable to X1), the SEUS can identify my X1 and I have tried it twice successfully.
Hop it can help.
minglee said:
I have Windows Vista Business running on my laptop.
I also have the problem of SEUS cannot indentify my X1 (but sometimes, it did recongize though very low succesful rate).
After clear the Checkbox : USB Connection allowed, in the Vista Mobile Devicecenter (before connecting the USB cable to X1), the SEUS can identify my X1 and I have tried it twice successfully.
Hop it can help.
Click to expand...
Click to collapse
Confirmed this trick. Just yesterday I was trying to update my X1 to R3A, but SEUS couldn't recognize my phone is connected. I've tried to activate built-in windows Administrator account, because it helped me when I was updating to R2A. But this time it didn't work. I was pretty confused, but after few minutes of searching on forum I found suggestion about uncheck that "USB Connection allowed" option. I did it, connected the phone and SEUS recognized it in a second. Tried 3 times and it worked like a charm.
I am running on Vista Home Premium 32bit.