Database Develop

[Q] UPDATED: ODIN wont recognize my phone with USB debugging on, but will without it

Alright, so I was having some problems with my cognition rom and decided go back to stock so I could flash the new cognition. I put my phone into download mode, and it took a few times for ODIN to see my phone. After I got ODIN to see my phone I tried to master clear, it did not work. I had to pull the battery out and try again. I rebooted my phone again, and many program errors came up. I shut off my phone, tried to get into download mode and it wouldn't let me using the volume down + up then insert USB with ODIN open.
Now to get into download mode I must hold buttons with battery out, put USB in, and put battery in and I get download mode instantly, but I cant get ODIN to recognize my phone at all anymore. I tried many different methods(odin open before DL mode, odin closed before download mode, etc). I looked through a few threads and couldnt find anything that would work. Also my window 7 64 now says it doesn't recognize the USB device when I plug it in. Whats going on with my phone?? Im getting very annoyed! Is there any way to go back to stock besides ODIN??? Any help is appreciated!!
***UPDATE***
Seems like I may have a 3 button combo lock, and no USB support of any kind(besides charging).

UPDATE: I used rom manager to flash over my old rom. My phone works again, but it wont go into download mode at all now. Only when I use the cognition menu to send it to download mode will it work. I still cant get ODIN to see my phone. I want to go back to stock still, but without ODIN working, can I?

ziphoward said:
UPDATE: I used rom manager to flash over my old rom. My phone works again, but it wont go into download mode at all now. Only when I use the cognition menu to send it to download mode will it work. I still cant get ODIN to see my phone. I want to go back to stock still, but without ODIN working, can I?
Click to expand...
Click to collapse
under your captivate battery, there is a number like 1008, 1010, what is yours?

I've had the same trouble with download mode + odin on my Windows 7 64 bit pc too.
I have to have odin running, phone off with battery out, and usb cable in. I leave the battery out for about a 10 second count. Then put the battery in and hit all the buttons at the exact same time (power + volume up and down). The key here is that I only had to hit all three buttons momentarily to get it to go into download mode. I didn't have to hold them down for any length of time.
I easily spent 1 hour trying to get odin to work the last time I had to reflash to stock. Only because I forgot how hard it was three last time with my 64 bit machine.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

mengbo said:
under your captivate battery, there is a number like 1008, 1010, what is yours?
Click to expand...
Click to collapse
1006
So should I just keep trying to get into ODIN by just fiddling around with it? Ive tried an XP machine and it wouldnt work either. Does booting into download mode from the cognition power menu any different than entering download mode the manual way? Every time I put the battery in with the USB it takes me to the battery charger screen. At first with that issue, putting in the battery last while holding down volume up and down, would put the phone into download mode(as opposed to the normal ways of getting into download mode). Now that wont even work at all.

first you can try the 3 button fix, just search the forum for that.
you may need to build a jig or buy one online just in case, it will get you into the download mode easily.
http://cgi.ebay.com/ws/eBayISAPI.dl...47234&ssPageName=STRK:MESELX:IT#ht_511wt_1139

im having horrible trouble with adb cmd. I installed the samsung drivers, put my phone in usb debugging, did some tutorials on how to install sdk correctly, went to the correct file paths in cmd promt, and still cant access the adb shell. Any pointers on this?
Also, could I wipe all data off internal storage and use the "reinstall package" option in recovery mode to use rom manager update.zip to restore my rom from my sd card? Im not sure if thats possible. Im getting errors with my rom, and it feels slower since I just reinstalled over the top of my faulty rom.
Seems the only usb function I have right now is to charge it. Hmmm USB brick?

Any help out there???
3g stopped working on my phone when I woke up. I really need to get a fresh rom installed.

If I recall correctly, the path to where adb is had changed. Check all folders inside the sdk folder. to make my life easier, I put the sdk folder right into the root directory (c and renamed it sdk. Don't know if that well help or not...
Sent from my SGH-I897 using XDA App

I changed the folder to androidsdk from whatever it was.
bueller bueller bueller...anyone?

Well, if your phone is a rev 1006 you "should" have a problem like losing your button combo. I guess that could have happened but I doubt it, I've got a 1007 and never lost it.
So, as for ADB here's what I do. Take the android SDK folder you downloaded and look inside it. There is a folder called tools. I take the tools folder and copy it to the root of my C: drive. Make sure you have all the drivers loaded, speaking of which I would uninstall and reinstall the drivers. Sounds like they flaked out for some reason. Next open up a cmd window, Start > Run > CMD.
Then type,
cd /
cd tools
adb devices <<this shows if your phone is recognized. if it is...
adb reboot download
*or
adb reboot recovery
*or
adb shell
For what it's worth, I have been flashing my phone since I got it in July and the only time I Master Clear is when I have had a problem like a soft brick or something that I was suspicious about the data on my internal SD. Which, so far has been maybe 3 times. I don't think necessary to Master Clear every time you flash to stock.
Also, you shouldn't really have to the pop out the batter to do the download mode trick. I turn my phone off, hold both Vol up and down, then plug in USB and I'm in download mode.

bobbylx said:
Well, if your phone is a rev 1006 you "should" have a problem like losing your button combo. I guess that could have happened but I doubt it, I've got a 1007 and never lost it.
So, as for ADB here's what I do. Take the android SDK folder you downloaded and look inside it. There is a folder called tools. I take the tools folder and copy it to the root of my C: drive. Make sure you have all the drivers loaded, speaking of which I would uninstall and reinstall the drivers. Sounds like they flaked out for some reason. Next open up a cmd window, Start > Run > CMD.
Then type,
cd /
cd tools
adb devices <<this shows if your phone is recognized. if it is...
adb reboot download
*or
adb reboot recovery
*or
adb shell
For what it's worth, I have been flashing my phone since I got it in July and the only time I Master Clear is when I have had a problem like a soft brick or something that I was suspicious about the data on my internal SD. Which, so far has been maybe 3 times. I don't think necessary to Master Clear every time you flash to stock.
Also, you shouldn't really have to the pop out the batter to do the download mode trick. I turn my phone off, hold both Vol up and down, then plug in USB and I'm in download mode.
Click to expand...
Click to collapse
Im having USB driver problems, windows 7 will not recognize my phone. I think this is why adb wont recognize my phone correct? I can only get into download mode now but using the power menu thats custom from Cognition. Is my phone screwed?? Can I flash a ROM without ODIN?

ziphoward said:
Im having USB driver problems, windows 7 will not recognize my phone. I think this is why adb wont recognize my phone correct? I can only get into download mode now but using the power menu thats custom from Cognition. Is my phone screwed?? Can I flash a ROM without ODIN?
Click to expand...
Click to collapse
Like I said, have you tried uninstalling the drivers from windows and reinstalling them? I am running Win 7 x64 and have had that happen. After i flash a rom or flash to stock sometimes windows doesn't recognize my phone at all. The first time I just used my laptop to flash but the second time I uninstalled the drivers and reinstalled. It's also important that you plug into the USB ports directly on the motherboard on the back of your PC. There are known problems when trying the front usb ports or through a hub.

bobbylx said:
Like I said, have you tried uninstalling the drivers from windows and reinstalling them? I am running Win 7 x64 and have had that happen. After i flash a rom or flash to stock sometimes windows doesn't recognize my phone at all. The first time I just used my laptop to flash but the second time I uninstalled the drivers and reinstalled. It's also important that you plug into the USB ports directly on the motherboard on the back of your PC. There are known problems when trying the front usb ports or through a hub.
Click to expand...
Click to collapse
Ive tried uninstalling and reinstalling many many times. I am using a laptop and ive tried all the USB ports but still no luck. I hate having my phone like this, it will drive me insane until its fixed.. or officially considered usb bricked.

ziphoward said:
Ive tried uninstalling and reinstalling many many times. I am using a laptop and ive tried all the USB ports but still no luck. I hate having my phone like this, it will drive me insane until its fixed.. or officially considered usb bricked.
Click to expand...
Click to collapse
Just curious, is it a Dell laptop? My Dell never recognizes my phone unless I power the laptop on with the phone/USB plugged in. If the laptop is on, and I plug phone in it never works, so I leave it plugged in and reboot and it works. It drives me crazy, but whatever it's my work PC.

bobbylx said:
Just curious, is it a Dell laptop? My Dell never recognizes my phone unless I power the laptop on with the phone/USB plugged in. If the laptop is on, and I plug phone in it never works, so I leave it plugged in and reboot and it works. It drives me crazy, but whatever it's my work PC.
Click to expand...
Click to collapse
It is a dell actually, but I just tried your method and it didnt work for me. Thanks for the input though!

Alright, I downloaded kies mini today and it actually installed some drivers correctly. I was able to pull up my internal drive on the computer, but it wouldn't read it. I was able to get ODIN to see my phone(first time in weeks), but it only shows up when my phone is NOT in debugging mode. So im assuming Master Clear will work now. I was using AIO captivate tool box, and my phone rebooted at the click of the button into download mode, but once again it wont see my phone in ODIN while in download mode. Im getting closer!
Why wont ODIN recognize my phone with USB debugging on? Any more suggestions on how to make this happen?

[Q] My Galaxy S not booting after updating via kies

Today I updated my phone using kies. After the update was done the phone tried to boot but it couldn't get past the screen that says "Galaxy S GT-I9000".
So far I have tried to enter recovery/download modes, with no success.
Tried to connect the phone on my computer*, which recognized it (you could hear the "bleep" sound windows makes when a device is connected through usb.) but it didn't appear at Computer menu. Also kies recognized that there was phone connected but it keeps saying "Connecting" under Connected Devices tab.
*I'm using 64bit Windows 7 Ultimate

You'll need to either build or buy a Jig to get it into download mode and then you can reflash with Odin.

Did you ever use a custom rom on the phone? I assume not, but want to make sure.
If not, then you at least have warranty (don't you?) and can send it back for Samsung to revive your phone. Should you consider this, it would probably be wisest to not even try to repair your phone yourself.
However if you want to, here are three tips I found:
1) Connect your phone to your computer, open adb and type 'adb reboot download'. Your phone should reboot into download mode.
2) Originally posted here with a link to the mentioned ZIP: http://forum.xda-developers.com/showthread.php?t=728754 (look under "Manual Method")
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
a) Download the easy reboot recovery.zip script and unzip it somewhere
b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
c) Connect phone with USB cable to pc
d) Wait until all the drivers are installed
e) Start reboot recovery.bat
f) The phone will now start in recovery
g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
3) This is from androidforums.com:
- Plug USB cable
- Remove battery
- Press AND HOLD volume down, power and menu key at the same time
- While pressing and holding the mentioned buttons, reinsert the battery (quite fiddly, I know)
- Let go of the buttons and you should go into Download mode.
Please tell me if anything helped.

Thanks for your help guys!
A.G. said:
1) Connect your phone to your computer, open adb and type 'adb reboot download'. Your phone should reboot into download mode.
Click to expand...
Click to collapse
Didn't work, adb gave me error "device not found", which would probably mean that the device isn't properly connected to my computer even though Windows did that bleep voice.
2) Originally posted here with a link to the mentioned ZIP: http://forum.xda-developers.com/showthread.php?t=728754 (look under "Manual Method")
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
a) Download the easy reboot recovery.zip script and unzip it somewhere
b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
c) Connect phone with USB cable to pc
d) Wait until all the drivers are installed
e) Start reboot recovery.bat
f) The phone will now start in recovery
g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
Click to expand...
Click to collapse
This is something I didn't even try because I can't turn my phones USB debugging on. (can't access my settings )
3) This is from androidforums.com:
- Plug USB cable
- Remove battery
- Press AND HOLD volume down, power and menu key at the same time
- While pressing and holding the mentioned buttons, reinsert the battery (quite fiddly, I know)
- Let go of the buttons and you should go into Download mode.
Click to expand...
Click to collapse
Didn't work.
And no I have never used any custom ROMs on my phone. Probably taking my phone to the place I bought it from and see if I can get it fixed under warranty. Unfortunately that means I'm not going to have a phone to use for a while since I have no time to go there until sometime next week. If I can't get this thing fixed under warranty I'll probably just order a JIG and fix it that way.
If someone has more ideas please post them anyway, I want to fix this problem as fast as I can.

maybe a stupid question but you know how to get in dowload mode......
vol. down / home / power....
here are samsung drivers for your phone, uninstall everythin having to do with kies and install samsung drivers.
see if you can connect to ODIN now.
http://dl.dropbox.com/u/19506141/flash en drivers/SAMSUNG_USB_Driver_for_Mobile_Phones.exe

O2X wont connect to pc as APX device (help needed please)

So I tried to root my phone, it worked, and I wanted to oc it. I used ROM Manager, and bricked my phone, since I installed a program (dont remember what its called) that turned my phone into EXT4, when it needs to run on EXT3 or something. So now its stuck at the LG/ LG with loading bar screen and cannot turn on. I'm trying the flash it with nvflash, but it wont work. I got my phone into APX Device mode once, but I failed and had to try again. But now, my computer won;t recognize my phone and I think I'm doing something wrong, because it wont show my phone as a APX Device. I'm obviously new to this so help would be appreciated.

GhostRai said:
So I tried to root my phone, it worked, and I wanted to oc it. I used ROM Manager, and bricked my phone, since I installed a program (dont remember what its called) that turned my phone into EXT4, when it needs to run on EXT3 or something. So now its stuck at the LG/ LG with loading bar screen and cannot turn on. I'm trying the flash it with nvflash, but it wont work. I got my phone into APX Device mode once, but I failed and had to try again. But now, my computer won;t recognize my phone and I think I'm doing something wrong, because it wont show my phone as a APX Device. I'm obviously new to this so help would be appreciated.
Click to expand...
Click to collapse
Some people have reported that they have to try repeatedly before it will start in APX-mode. So try again and again before giving up, make sure battery is out and that you firmly press both volume-buttons while plugging it in.
If it absolutely, positively cannot enter APX-mode, then your last hope is Smartflash-mode. Does it start in Smartflash mode if you hold volume-down while plugging it in?
Oh, and make sure you're connected directly to a port on the motherboard.
EDIT: You can try deleting the APX-device from the PC too, to get it rediscovered and reinstalled. Unzip the attached archive and run the batch file in it. (It sets a parameter which allows the device-manager to display hidden and "ghost"-devices before starting it.) Select "Show Hidden Devices" from the View Menu, find the APX-device(s) ("NVIDIA USB Boot-recovery driver for Mobile devices") and delete it/them. Then try to reconnect in APX-mode again. (Have the driver ready.)

PLEASE HELP, Computer is not recognizing my Galaxy S

Just got my phone into download mode after using the jig, and i have been able to connect to my pc before i seriously F'd my phone by messing with a setting in cwm. I have downloaded and redownloaded drivers from samsungs website, along with installing Kies and that does not recognize my phone. (also i would like to add i am unable to access the phone since it wont turn on without the jig, without jig it just goes into a boot loop.)
THis is what happens when i plug my phone into the computer:
plug in usb (to computer and phone)
let it do its thing to recognize device...
pop-up stating "unknown device" so i click it.
then right-click the unknown device which opens up another window
from this menu it shows Install driver, Update driver and 3 other options.
when i press install driver and update driver, it tells me that the driver is already installed in "device unknown."
At this point i throw computer at wall after 2 days of trying to figure this out.

so messed around and the problem only happens when it is in download mode. but when it is not in download mode it shows up but no use to me because i am trying to flash it to stock. soo i dont know why the error 43 only shows up when in download mode. any help would be great.

sean.hunt said:
so messed around and the problem only happens when it is in download mode. but when it is not in download mode it shows up but no use to me because i am trying to flash it to stock. soo i dont know why the error 43 only shows up when in download mode. any help would be great.
Click to expand...
Click to collapse
Just follow this to update the drivers http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 , same thing as what you have done earlier but this time , when it searches for new drivers, you can do the selection for it.
But first reboot your PC after pulling out power cord ...and try the quick solutions first

Ok sen, so i tried to install the driver manually but i am stuck at the part where i have to install something on my phone to allow it to sync with the computer, since my phone will not even boot up. I am starting to think my dear Capi is going to be a paper weight =(

Stuck in sideload

EDIT FOR THOSE WHO MAY HAVE THIS ISSUE:
If you have accidentally entered sideload mode from CWM, there are 2 ways to get out of it.
1) - the fastest way - flash a rom from it (.zip format eg KA04 xperia revolution etc)
2) - the easiest (but potentially very slow if you have a full battery) - let your battery run empty, the phone will power down when it goes flat. Put it on charge and leave it for a while (it will take a while to get enough charge to be able to boot again so be patient)
If you are going to flash a rom you will need to do some house keeping. I was having big issues with sideload mode as my computer wasn't recognizing the phone properly, and sideload commands were not working. The phone was essentially not responding to any ADB commands or the sideload flash command.
This all turned out to be from left over drivers from my galaxy s 2. For what ever reason, rooting, installing custom recovery, adb, bootloader unlocking and flashtool all work flawlessly with my driver set up, but sideload mode did not like it at all.
I over came the issue by using a computer which had a fresh installation of windows 7, which therefore had no previous drivers for any devices besides that of the PC itself. It worked first time and was very easy.
The steps for flashing a .zip in sideload mode:
- Ideally have a .zip of the ROM you were on. If you are on a stock rom, try to find a rom based on the same version of your stock from and it should be fine. You probably won't need to wipe data/factory reset (I haven't had to wipe going from AUS stock 350 - NL 434 - KA04 xperia revlolution)
- Have drivers configured perfectly
- Have ADB working
- Put the rom .zip in your ADB directory (It would be a good idea to name it update.zip or rom.zip for ease of use.)
- Open file explorer and go to your ADB directory, hold down shift, right-click and select open command window here
enter "adb devices"
- Your device should be listed. If all the drivers are set up properly, is should also list as being in sideload mode
- Type "adb sideload <filename of update.zip>" without quotation marks or < >
- Let it finish. When it's done your device should now be working fine or at least out of sideload mode
- Wipe cache and dalvik cache if you feel it's necessary
I am not sure how this will work for locked bootloaders as mine is unlocked therefore cannot comment on the experience. I suspect that if you flash xperia revolution, it should work as it is compatible with locked bootloaders. It should fail and abort the installation near the end though. This is normal, just wipe cache and dalvik cache and it should work.
In the worst case scenario, you should now be able to access flash-mode to flash a stock rom with flashtool. You shouldn't need to do this though.
Original post:
So I intelligently selected install zip from sideload instead of sd card. Now I am stuck in side load mode, and no amount of button combinations for any period of time are working to hard reset the device. And since the Z has no removable battery I cant just pull that out to shut it off. It doesn't seem to like taking any commands from adb, does anyone have any advice?

DreadPirateDan said:
So I intelligently selected install zip from sideload instead of sd card. Now I am stuck in side load mode, and no amount of button combinations for any period of time are working to hard reset the device. And since the Z has no removable battery I cant just pull that out to shut it off. It doesn't seem to like taking any commands from adb, does anyone have any advice?
Click to expand...
Click to collapse
You can try SEUS:
http://www.sonymobile.com/global-en/tools/update-service/
not sure if it will help but it couldn't hurt to try it out. If all goes well seus will reinstall your device back to original

Odp: Stuck in sideload
adb reboot recovery
check that command
Sent from my GT-S6500D using xda premium

FlooDnl said:
You can try SEUS:
http://www.sonymobile.com/global-en/tools/update-service/
not sure if it will help but it couldn't hurt to try it out. If all goes well seus will reinstall your device back to original
Click to expand...
Click to collapse
I'll give it a crack
UPDATE: It's not letting me go past the connect stage unfortunately

yeah the adb commands are throwing up the error :
"error: closed"
ie;
adb reboot
error: closed
adb usb
error: closed
adb sideload xx.zip
gives me the whole help message.
adb get-state
unknown
very frustrating.

Odp: Stuck in sideload
put power of 8 sec.
Sent from my GT-S6500D using xda premium

Holding the power button for over 30 seconds didn't turn it of, nor did power + vol up, power + vol down, power + vol up & vol down, or vol up + vol down. This sucks lol. Really don't want to have to resort to just leaving it till the battery dies

DreadPirateDan said:
Holding the power button for over 30 seconds didn't turn it of, nor did power + vol up, power + vol down, power + vol up & vol down, or vol up + vol down. This sucks lol. Really don't want to have to resort to just leaving it till the battery dies
Click to expand...
Click to collapse
This worried me a little with purchasing this phone with non removable battery. Tried the hard reset mentioned in the manual to be more relaxed, but was sure that a lock could occur that nothing would work except battery run down, seen it on other devices previously. Now it seems confirmed

danw_oz said:
This worried me a little with purchasing this phone with non removable battery. Tried the hard reset mentioned in the manual to be more relaxed, but was sure that a lock could occur that nothing would work except battery run down, seen it on other devices previously. Now it seems confirmed
Click to expand...
Click to collapse
It's certainly looking that way, I just pull out my gf's old vista laptop (considered it may be a windows 7 or 64bit issue) but it's the exact same story there. I'm currently booting up my old/her new laptop which just recently got a fresh win7 install. Nothing at all adroid related has ever been on it since then so if it doesn't work still on that I can essentially rule out that it's a driver or os issue
UPDATE: Ok looks like the old/new/fresh laptop is doing the trick! When I type adb devices, this time it is listing the z as being sideload, instead of host (what it said on the other 2 laptops). So allthough reboot commands still come back as error, I was able to start sideloading cm10.1 zip.
AH just checked on it and it's done! I am out of the terrible menu. Now to try rebooting system.. hopefully I haven't made things worse .
CM logo is swirling away.. good start.
And now it's booted to CM . Thank god that is over!
Hopefully if anyone else falls into a similar trap this thread might help them. There must have been some sort of conflicting drivers messing with my adb set-up. Funny that I was able to root and unlock the bootloader completely hassle free in the same setup though
So to anyone having similar issues and doesn't have the option to pull out the battery - try a fresh pc that hasn't had any android devices installed to it.
And a big thanks to those that tried to help me up to this point much appreciated. :victory:

DreadPirateDan said:
It's certainly looking that way, I just pull out my gf's old vista laptop (considered it may be a windows 7 or 64bit issue) but it's the exact same story there. I'm currently booting up my old/her new laptop which just recently got a fresh win7 install. Nothing at all adroid related has ever been on it since then so if it doesn't work still on that I can essentially rule out that it's a driver or os issue
UPDATE: Ok looks like the old/new/fresh laptop is doing the trick! When I type adb devices, this time it is listing the z as being sideload, instead of host (what it said on the other 2 laptops). So allthough reboot commands still come back as error, I was able to start sideloading cm10.1 zip.
AH just checked on it and it's done! I am out of the terrible menu. Now to try rebooting system.. hopefully I haven't made things worse .
CM logo is swirling away.. good start.
And now it's booted to CM . Thank god that is over!
Hopefully if anyone else falls into a similar trap this thread might help them. There must have been some sort of conflicting drivers messing with my adb set-up. Funny that I was able to root and unlock the bootloader completely hassle free in the same setup though
So to anyone having similar issues and doesn't have the option to pull out the battery - try a fresh pc that hasn't had any android devices installed to it.
And a big thanks to those that tried to help me up to this point much appreciated. :victory:
Click to expand...
Click to collapse
I really didn't get it could you please help me more ! I have the same problem but I have no idea how to fix this I made a big mistake

Tell me if I'm wrong, but...
Dumiftw said:
I really didn't get it could you please help me more ! I have the same problem but I have no idea how to fix this I made a big mistake
Click to expand...
Click to collapse
I believe DreadPirateDan was saying:
Have a computer with adb installed. It has had an Android device connect to it before. It wouldn't recognise the device.
Have a second computer with adb installed. It has had an Android device connect to it before. It wouldn't recognise the device.
Have a third without adb installed.
Installed adb.
Attached device, which invoked device driver installation.
Started using adb and it was recognised, allowing reinitialisation of the device.
Maybe?
If you don't have that many computers, try a fresh virtual machine (VirtualBox and Ubuntu don't cost money if you don't have the licenses for VMware and Windows).

Yes what Johbremat said is correct. My bad I haven't checked xda for a few days otherwise I would have posted sooner! I hope you managed to solve your problem :fingers-crossed:
I edited the first post so if anyone else runs into this there is hopefully more clear instructions on how to get out of it. Let me know if there is anything I said incorrectly (I was going from memory pretty much), or if you don't understand something I have said and I will offer my assistance when I can and/or edit the post.

Hi, I just had this problem while putting Cyanogenmod on my Nexus10. I don't know if it will work on the Xperia but even when adb sideload update.zip was getting error: closed I was still able to do adb reboot recovery to get out of it. Also my error: closed problems went away when I used CWM to format my sdcard (kind of extreme, I know).