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
(I'm reposting this thread per request. All credit and thanks goes to the original OP and to others that helped compile and write up this helpful info.
This is basic knowledge for the experienced Captivate user, but a treasure of info to the novice user.
Please keep all posts thread related. Thanks.)
***There are three parts to this thread - How to get into download mode, how to get into recovery mode, and how to solve problems connecting your Android device to your computer. I think you should be able to find where each one begins without too much trouble.***
----------------------------------------------------
GETTING INTO DOWNLOAD MODE
----------------------------------------------------
"Just get into download mode and..."
Ever find yourself with a phone that's misbehaving, and you can't seem to figure out how to get it to download mode?
Here's a list of things to try (many thanks AdamOutler and Pirateghost), sorted in a "where are you now" setup:
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol+ and Vol-, then insert your USB cable.
- Press and hold Vol+/Vol-, Insert Battery, Insert USB cable
- Press and hold Vol+/Vol-, Insert USB cable, Insert Battery
- Insert battery, then press and hold Vol-, then insert your USB cable.
- Press and hold Vol-, Insert Battery, Insert USB cable
- Press and hold Vol-, Insert USB cable, Insert Battery
- Use a 301Kohm jig between USB pins 4-5 (can be manufactured jig or homemade chain of resistors)
FROM A BATTERY CHARGING STATE
- With USB cable inserted into Android device, press and hold Vol+/Vol-, then press Power
- With USB cable inserted into Android device, press and hold Vol-, then press Power
- (Advanced Method) Use UART, and during battery charging, type "reboot download"
FROM CLOCKWORKMOD RECOVERY MENU
- Position the cursor (highlighted selection) on "Restart device", Plug in USB cable, press and hold Vol-, then hold Vol+, then press power
- (Where available) Use the "Reboot Download" option in the "Advanced" menu
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot download"
- (Where available) Use the rom's power menu option to reboot into download
- From a terminal, type "su", then "reboot download"
- Download the app "quickboot", follow the app directions to reach download mode.
ADVANCED METHODS - REQUIRE HARDWARE MODIFICATIONS OR MORE IN-DEPTH TECHNIQUES
I'm presenting these largely unedited, as I don't want to incorrectly type an important detail of something that I don't understand myself.
- Apply UnBrickable mod to your device, then remove the battery, insert the battery, and click the "Download Mode" button on the computer
- Use UART (619Kohm resistor between USB pins 4-5, D+=RX, D-=TX, 192500bps 8n1 comms), press and hold ENTER while booting, then type USB
----------------------------------------------------
GETTING INTO RECOVERY MODE (CWM RECOVERY)
----------------------------------------------------
(Thanks to TRusselo for writing this out)
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol+ and Vol-, then press and hold power. hold all 3 for 5 seconds.
- Press and hold Vol+/Vol-, Insert Battery, hold power. hold all 3 for 5 seconds
- Press and hold Vol+/Vol-, hold power, Insert Battery
- Insert battery, then press and hold Vol+, then press and hold power. hold all 3 for 5 seconds.- Press and hold Vol+, Insert Battery, hold power. hold all 3 for 5 seconds- Press and hold Vol+, hold power, Insert Battery
FROM A BATTERY CHARGING STATE
- With USB cable inserted into Android device, press and hold Vol+/Vol-, then press Power
- With USB cable inserted into Android device, press and hold Vol+, then press Power
- (Advanced Method) Use UART, and during battery charging, type "reboot recovery"
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot recovery"
- (Where available) Use the rom's advanced power menu (long press power in android OS) option to reboot into recovery
- From a terminal emulator, type "su", then "reboot recovery"
- Download the app "quickboot", follow the app directions to reach recovery mode.
----------------------------------------------------
UNIVERSAL FIRST STEPS FOR CONNECTION ISSUES
----------------------------------------------------
So you've got Odin/Heimdall up, the phone's in download mode, it's connected to the computer, but Odin/Heimdall is saying "What phone?". You've tried jiggling the handle, checking the blinker fluid levels, and even using the board stretcher, but the Android guy is smirking at you from inside that yellow triangle.
Although it is possible that there is something else at work that's preventing your phone from connecting, I would suggest trying these "universal first steps" to see if you can resolve the connection issues:
1. Turn off both devices - and I do mean full power-down. Go ahead and pull the phone's battery, if necessary.
2. Disconnect your phone from your computer at all points - USB out of phone, USB out of computer.
3. Start up your computer. Don't touch it, don't do anything to it. Let it fully boot and completely settle.
(Obviously, log in if it's necessary, but then let it finish booting before moving on to step 4.)
4. Start up your flashing program (Odin/Heimdall). Let that get completely started and settled.
(If on Vista/Win 7, make sure to "Run as Administrator" in the right-click menu.)
5. Connect your USB cable to a different port than the one you last had it connected to.
(If you're on a Windows desktop, the ports in the back of the computer are generally more stable and should be used. If you're on a laptop, use USB port #1)
Do not connect the phone to the cable yet.
6. Start your phone in download mode. Wait until you see the yellow triangle Android guy with the words "Do Not Turn Off Target".
7. Connect your cable to the phone. Let it sit until Odin/Heimdall recognizes it (which should only take a couple of seconds).
If, for some reason, Odin/Heimdall doesn't recognize the phone at this point, here are a few more things to check/try:
- Repeat steps 1-7 above, making sure to change USB ports. As dumb as it sounds, sometimes the phone or computer just doesn't like particular USB ports.
- With everything still up, switch USB ports.
- Try a different OS (if possible) - sometimes Ubuntu will recognize what Windows won't, and vice versa.
- Try doing this on a different computer - again, different OS, different USB ports, they're all links in a chain and sometimes you'll come across a configuration that doesn't have the weak link.
- Try a different cable. I've had a case where I couldn't do any flashing with one cable, but everything was rock-solid and smooth on the same machine with just a different cable.
- Fully uninstall your drivers, reboot the computer, reinstall the drivers, power down, and then start again from step 2. Sometimes faulty drivers are the problem.
- Remove the drivers for the flashing program you're not using. So, if you're using Heimdall, remove the Odin drivers. If Odin, remove the Heimdall drivers. This will eliminate any potential conflicts.
----Quick explanation of Heimdall / Odin driver conflicts----
If you've used both Heimdall and Odin on the same computer for flashing, you may have noticed that they don't interact nicely when it comes to drivers and ports. What's happening is that when Odin gets the setup it wants, it will overwrite any and all drivers for your phone assigned to any of the USB ports. When Heimdall gets its setup, it will write to the specific port that you have your phone plugged into.
So, to illustrate, assume you have 4 USB ports on your computer. If you use Odin's setup, it will make ports 1-4 "Odin ports". If your first setup is Heimdall, and you put your phone on port #1, you would have port #1 as a Heimdall port with 2-4 unassigned.
Where it gets tricky is if you use Odin or Heimdall after using the other one. Let's say you have a Heimdall port #2 and decide to flash using Odin. Once you set up Odin the way it wants to be set up, you will overwrite all the ports as Odin ports. This means you have no more Heimdall port #2, just Odin ports 1-4. If you use Heimdall after Odin, it will only reassign a single port. So if you had an Odin 1-4 setup and flashed using Heimdall on port #3, you would have Odin ports 1,2, and 4, and Heimdall port #3.
Confusing yet?
Here's the basic rules for planning when using Heimdall and Odin:
- If you're starting from scratch, Odin will write to all ports. Heimdall will write to the port your phone is plugged into.
- If you previously used Heimdall and are now using Odin, all the ports will become Odin ports. To use Heimdall again, you'll have to reinstall the Heimdall driver to the port you're going to use.
- If you previously used Odin and are now using Heimdall, only the port you're using with Heimdall will become a Heimdall port. If you can remember which port you're using and make that a dedicated Heimdall port, you can have the other ports remain Odin ports.
Images
View attachment 1431380 Download Mode screen
View attachment 1431385 Alternate Download Mode screen
View attachment 1431370 (Pre-Gingerbread Firmware upgrade fail screen) Possible alternate download mode. If not, then u need a Jig.
View attachment 1671424 No i897 Gingerbread Bootloaders installed screen. Heed all warnings about flashing bootloaders and then flash the i897 GB BLs to resolve this issue. See post #7 below for info on where to get the BLs.
USB Drivers
Device(Install),USB Driver (Software) (ver.5.02.0.2), Win XP/Vista/Windows 7, Released Jul 15, 2010
Title AT&T SGH-I897 (Captivate) USB Drivers (5.02.0.2)
Applicable Model SGH-I897 (Captivate)
Carrier or Corporate Customer AT&T
Description USB Drivers for use with Media Sync and Mass Storage
Downloaded directly from Samsung Support for SGH-I897...
View attachment SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip
Flashing Tools
Heimdall command line tool, Heimdall Frontend, Drivers...http://www.glassechidna.com.au/products/heimdall/
Note: Heimdall uses its own specific USB Drivers.
Odin Flashing Tool...Odin3 v1.83
Note: Odin uses the Samsung Captivate USB Drivers.
I'm having an issue that resulted from an attempt to flash a rooted kernel. I'm not sure what happened, but the result is an inability to enter recovery mode, and no connection in download mode. Normal boot ends in a screen resembling a scrambled cable channel that reboot loops. I do have heimdall and Odin installed at this point, but i had connection trouble before I tried Odin. I have done some searching but found nothing describing the static screen. If you require more info, I'll provide what I can.
Sent from my Amaze 4G using xda app-developers app
That pixelated screen means u do not have the i897 Gingerbread Bootloaders installed. So u need to flash the Odin or Heimdall i897ucKK4 one click WITH Bootloaders included. Then u can proceed to use regular Odin to flash the .tar version of the KK4 Corn Kernel so that u can get Root and as well have CWM Recovery that is included in that kernel, so then u can proceed with flashin a dev rom of ur choice.
See my signature link below, if u r on a pc or in a web browser, for the links u will need as far as what i just instructed u should do. :thumbup:
The [Utility] KK4 Easy Root by Red_81 that is in my sig link, will guide u to gettin Root and KK4 Corn Kernel. Be sure to hit Red_81's thanks button.
Sent from my SGH-I777 using xda premium
Added an image of the screen that occurs when the i897 GB Bootloaders are not installed. See post #2.
The safest way I have for those who need to get the i897 GB BLs to flash is here... Go to this post and use this Heimdall One Click ---> I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param, and Repartition-Heimdall One-Click.
That's the screen. Thank you very much for your data rich reply. I will give it a go when time permits.
Sent from my Amaze 4G using xda app-developers app
You are awesome. The heimdall one click with bootloader worked like a charm. It was as easy as one click! Thanks again.
Sent from my Amaze 4G using xda app-developers app
Thanks for all the info, however some of the topics placed in various links need an ajustment for Linux.
Don't waste your time using Ubuntu because java is not natively supported anymore for the 12.10 release.. I suggest using opensuse or fedora and visiting java.com to download the rpm as deb are not supported and this is much easier for a newbie to do than to build a deb package from sources..
Just a little tip, if you want to run hiemdall, you will need java runtime somehow, opensuse I know personally 12.2 came with an option to install the java dev kit, which is just as good as java runtime and includes a runtime with it. This will allow you to install android dev kit, another good tool to have for modding.
Sent from my SGH-I927 using xda premium
Samsung Captivate wont completely boot
Hello, I'm having a problem with my Samsung Captivate. It loads all the way to the last screen where the S comes into formation and it says Galaxy S at the bottom, then it restarts and repeats the entire startup. I used "I897UCKK4 CONTAINS Bootloaders" to see if it might fix the problem, but it's still doing it. Any suggestions please? thanks
Maybe a bad download. Try a fresh download. One without bootloaders. Since the bootloaders should be flashed to ur phone.
And try a different micro usb/usb cable. Also check in the phone's micro usb port to make sure it is free of dust, dirt, etc. And u could also try a different usb port on ur pc.
Make sure ur battery has a good charge as well.
Hope one of these helps.
Sent from my SAMSUNG-SGH-I747 using xda premium
Install ClockWorkMode
How to install ClockWorkMode on my Galaxy Captivate i897 mobile?
""Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system ""
This is not working for me. Can somebody help me on this issue.
Plz see and use TRusselo's Guide that is a stickied thread in this forum.
Basically u need to use Odin or Heimdall to flash a kernel that has cwm recovery baked in.
Sent from my SAMSUNG-SGH-I747 using xda premium
My experience to get back from soft brick
Just want to share my experience here:
I had captivate with CM10 installed and decided to flash it back to stocked rom and trade it in for new HTC One ($100 ,
First I flashed it with Odin and somehow when it reboot, it stuck at AT&T page (flashing every 3~5 seconds), and I can't get it back to download mode through all the key combinations recommended 4-2ndtwin without success (I did try all of them).
Then I got a 300kOhm resistor (measured it and showed 298.9kohm), without the hassle to make the USB jag (which was a mistake), use the legs to touch the 4 and 5 of Cappy's USB port, after multiple tries (average about 3 minutes effort that have one success), I was able to get to download mode.
I then tried to flash the "I897UCKK4 Odin One Click - Stock, CONTAINS Bootloaders, Re-partition, Full Wipe" got from this post:
http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
The flash stuck somehow in the middle of flash, it was probably after partition (not 100% sure though) per odin message. I waited for about one hour and decide to pull the battery out. When I reboot, it was not showing AT&T logo, instead went straight to phone --!-- computer screen.
Some posts suggested it is another download mode, but for me, it was not in download mode. Odin no longer responsed when I plug in the phone. Again, I tried all the combination in previous post to get it back to download mode, as well as tried multiple times (should be more than 10 successful trys) using the resistor, it all went back to same phone --!-- computer picture.
I almost gave it up but decided to give it last try by making the jag, it was not that hassle at all after I used a cheap car charge line (it was not even need to be cut, the plastic on the USB line was kind of like clamp shell, after removing four small clips, it completely dissembled and show the 4 and 5 legs, I wished I should have done it earlier!).
Then I connected the 300kOhm resistor to 4 and 5 legs of the USB line, put battery back to phone and plugged the jig into the phone, it still showed me the phone --!-- computer picture, and my computer was not response at all! It seems I had exhausted all the options and may have to give up the $100 trade-in credit.
I decided to switch the sequence and gave it last effort. Pulled the battery out, plugged in the jig, and put back the battery. Guess what, download mode appeared! I then was able to flash the stocked rom (the same rom I just mentioned) back to the phone and everything went well this time! I now can see the $100 gift card from HTC :laugh:
Thanks for all the information for this forum and you guys are great!
This thread and all the wonderful people in it have been very helpful
CM10.1 Boot Loop / Computer Won't Recognize In Download Mode
Hello all -
I think my Cappy has given up the ghost, but I thought I'd throw this out there to see if anyone had an idea.
Yesterday my Captivate (running CyanogenMod 10.1 M3) started looping the boot up screen. It's done this before, and when I just leave it, it will eventually start up normally. Not anymore. Plugging it in to charge starts boot looping the battery charging screen. I can't get it to reboot into recovery. I have tried every possible combination listed above. It just boot loops faster.
No problem, let's just flash the ROM again, right? It still goes into Download Mode fine. Except. I can't get a computer to recognize it at all. PC running Win 7 gives me an "USB device Not Recognized" error. Neither Odin nor Heimdall can see it. I have tried as much of the advice given above in this thread as I understand. I have tried all the different USB ports. I have tried three different machines. I have tried Win 7 and Mac OS X. I briefly tried Ubuntu but I'm too much of an Ubuntu noob to get heimdall running on it. I have tried two different cables. I have taken out the SD card. I have uninstalled and reinstalled the Samsung USB drivers. I don't know how to uninstall Odin and Heimdall drivers. Maybe someone can help me with that?
Thanks in advance for your thoughts.
Hey is there anyway to get captivate into download mode from a completely bricked state, something happened when my Odin finished and my phone screen won't show anything, i mean it just remains black.
Thanks in advance.
dragonfire2008 said:
Hey is there anyway to get captivate into download mode from a completely bricked state, something happened when my Odin finished and my phone screen won't show anything, i mean it just remains black.
Thanks in advance.
Click to expand...
Click to collapse
Won't show anything doesn't always mean bricked. Try this http://samsungcaptivate.wikia.com/wiki/Putting_the_Phone_into_Download_Mode.
Yeah none of those worked, I have tried everything to get the screen to show SOMETHING. Won't turn on, no download mode, no recovery, no nothing, just a black screen.
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).
Please excuse me if I'm repeating a prior question but it seems far too specific to trawl through pages of related threads to make sure.
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
3. All was going swimmingly, I entered fastboot mode absolutely fine, flashed CWM using fastboot which all loaded up absolutely fine.
3. At this stage ADB was not picking up my device at all, tried different cables, ports, all of the usual. What I didn't do was make a backup, and then I wiped all of the things that it's possible to wipe thinking to myself that I was going to get Cyanogenmod on there so all would be fine...
4. Finally I (quite stupidly) restored from memory card (which had already been wiped) from inside CWM, the device restarted and now I am getting no response AT ALL.
5. Sometimes it will load the Sony 'splash' logo that first appears but sometimes not, when plugged in the device is recognised and ADB actually sees the device but lists it as offline... Interestingly at this stage windows device installer actually installs Sony ADB driver for me automatically.
6. All I'm getting at the moment is a red flashing LED although when I plug in via USB the device is again recognised when I type adb devices but again is offline...
If any more information is needed please, I will be more than happy to give a quick reply.
Thank you in advance
JJrmc said:
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
Click to expand...
Click to collapse
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
AkiraProject said:
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
Click to expand...
Click to collapse
I was trying to end up with a rooted device running Cyanogenmod, I've been putting it off and off looking into the whole rooting scene and mistakenly dived in a little too quick without knowing what I was doing.
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
AkiraProject said:
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
Click to expand...
Click to collapse
Firstly AkiraProject thank you for your time on this.
I do realise that in my stupidity I could have loaded the cm-11-20141112-SNAPSHOT-M12-honami.zip to my SD card (if I'd had one or waited and gotten one).
What I did however was wipe everything I possibly could, and then hit restore from sdcard/0/ I believe - it may have been a different directory.
I believe what I have done is restored to a blank image......
WHen not plugged into usb I get a red blinking LED when just pressing the power button once.
When holding volume-up + Power the phone vibrates as if it is trying to boot but is unable to
If I leave it plugged into USB AND then press , the device shows the sony Logo and then proceeds to display a backlit but plain black screen, Sony PC Companion recognises the device as connected but is unable to interact with it. The output of "adb devices" shows my device but says "unauthorized" and windows is attempting to install MTB driver....
The behaviour doesnt seem to be quite the same every time.
I believe the device is soft bricked.... is this likely to be a case of a wiped partition table? Or at least loss of the boot partition?
If I leave the device plugged in via USB it periodically reboots itself, shows the Sony logo, remains on a bank screen then shuts itself down.
Shows in device manager as "USB Input Device" on win 7 x64 pro
Thanks in advance
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
D33KK said:
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
Click to expand...
Click to collapse
I have done quite a lot of reading etc on the subject....
according to This thread, Sony Xperias have the bootloader in non-writable mask ROM... so you should always be able to access Fastboot or Flash Mode?
The problem I am having is that I don't seem to be able to activate EITHER Fastboot OR Flash mode in order to flash some new firmware onto my device....
My device is recognized as a "USB Input Device" on Device Manager and windows tries to install MTP driver. I'm going to have a go at the process with a fresh install of windows 7 x64 and 'windows auto-install drivers' turned off.
What is the maximum damage I could have done here?
Thanks
Update
Hard reset (red button inside of the sim-card slot) resets the phone with three vibrates and it restarts.
The phone powers on and displays Sony splash screen and then displays a back-lit black screen.
The phone gets much hotter than normal and powers on to the blank back-lit screen when on charge.
I have NO ACCESS to flash mode or fast boot. Any combination of buttons leads to the same outcome: single vibrate, red LED and the phone shows the Sony splash screen then blank screen, as if the button combinations are just ignored...
Flashtool DOES NOT recognize the device, although it is recognized as C6903 in device manager (I have Sony adb driver installed and have disabled the MTP driver that windows recommends).
Flashtool gives me the red error text about making sure drivers are installed and making sure the device isn't in MTP mode.
I'm at an absolute loss as to what to try next, can somebody shed any light on this? There are plenty of guides but they all seem to rely on EITHER fastboot or flash mode and I can access neither although the phone powers on!
Thanks in advance!
Maybe the partition was corrupted when you flash "blank" image..........
So....JTAG....or send to Sony service....
Shutdown with power+vol up (will vibrate thrice) and see if it doesn't turn on automatically.
If it didn't turn on now check your task manager on windows, go to process tab, kill adb.exe (every adb.exe)
Back on phone connect usb holding down the vol down button (phone have to be off before you connect usb), if green led turns on and doesn't turn off you are on flashmode.
Check on flashtool or flashtool64 (for 64bits) and see if flashtool detects your device. If it detects and recognizes your phone flash the FTF for your device and let it do its job.
As you messed the phone Sony will charge for repairs.